QLM Users

Corrective Action

The purpose of a Corrective Action is to repair the consequences of an incident, a Non-conformance or a Control Deficiency.

The Corrective Action can in its properties be described with

  • a short description
  • link to the one responsible for it
  • link to related Non-conformances (or incident/control deficiency)
  • Link to relevant  Goals
  • description of recommended corrective actions
  • the date of the recommendation
  • the due date of implementing the recommendation
  • estimated cost of the recommended corrective action
  • link to the person responsible for making the recommendation
  • the start and end date of the implementation of the recommended action
  • link to the person responsible for the implementation of the recommended corrective action
  • actual cost of the non-conformance (or incident/control deficiency)
  • actual cost of the corrective action
  • a description of the corrective action taken
  • the closing date of the non-conformance/incident/control deficiency

Control Store

A ControlStore is used to model a temporary storing of control information.

It is possible to see the ControlStore as a buffer that stores control information until a Process is ready to receive it.
It is also possible to see the ControlStore as a semaphore where f.ex. binary signals can toggle the value of the ControlStore between ‘positive’ and ‘negative’.

An example of the use of ControlStores is the use of queue semaphores in a kernal of an operating system.

Control Process

A ControlProcess is producing output flows from interpretations of input flows. Usually the flows will be of the type ControlFlow.
An output ControlFlow is used by the ControlPocess to activate a Process.
An input flow indicates to the ControlProcess that another process has finished its activities. It can also indicate that an event has happened that the ControlProcess has to act upon.

Control Flow

A ControlFlow represents the flow of control information from one component to another. ControlFlow is usually used to introduce event driven aspects of a functional model.

Connection Point

A connection point can be either a physical socket or a logical connection point.

Connection

Graphical connection between two graphical objects.

Concept Relation

A concept relation is a connection on a ConceptualDataModel. It is used to relate InformationConcepts and defining the roles and cardinality of such relations.

A relation between two information concepts

Quality Control

A quality control is used to describe how a Result is to be validated/controlled in the case of reviews, inspections or any other kind of quality controlling activities. The quality control is used to describe the acceptance criteria, the questions to be asked, the roles of the parties involved etc.

QualityControl properties

The QualityControl tab

Property  Metamodel name Description
Short Description ShortDescription A short verbal description
Acceptance Criteria AcceptanceCriteria Description of criterias that must be met so acceptance can be granted.
Audit Roles AuditRoles This field is used to describe the roles of the different parites involved in the quality control activities. This includes f.ex. the external auditor, the customer or even the internal quality department.

The Techniques tab

Property  Metamodel name Description
Use technique UseTechnique Links to technique instructions
Links to: Document, ExternalDocument, Technique.
Tool Tool Link to tool-specifications for this result
Links to: ExternalDocument, InformationSystem.
Good Practice examples GoodPractice Link to files showing good examples
Links to: All templates.

The Action tab

Property  Metamodel name Description
Macro Macro This field is used to create a command language program that can be executed when the user double clicks on the symbol.
Execute on Double-click ExecuteOnDoubleClick Macro is always executed when double clicking on the symbol.
Initial value is off.