The Purpose of the the AuditProgram template is to collect a set of audits in a plan/program.
You can create an AuditProgram from the Compliance Desktop on the Web, or via the Repository Explorer.
An auditprogram have a dedicated focus, e.g. “ISO9001 audits Q3-2022” and collects a set of audits each having their own details and governance flow, cf. the QualityAudit-template.
Read more about how to manage audit programs here 
The Acknowledge list function enables you to keep track of and document which of your employees have read which relevant documentation.
An acknowledge list is used to select a group of people who must digitally acknowledge that they have read or studied specific sets of documentation. This can for example be a diagram, a document, or a set of regulations. An acknowledge list can be a one to one or a many to many relationships between objects and people. This means that you can have several people, InterestGroups, OrganizationalUnits or several objects listed in the same acknowledge list.
Once a user is assigned to acknowledge an object, the user will get a govenance task, and an “Acknowledge” action-button is shown in relation to e.g. the Diagram:
The Acknowledge history can be seen on the “Acknowledge History” tab:
A user can access their ackowledge task(s) via their “My task” action button in the top right
And from their “To Do list” from the desktop.
The QualityAudit object is used to document audits in an organization. This can be either internal or external audits of any type.
An audit can be part of an audit program and can be controlled by a governance workflow (click here to see the standard flow).
Read more about how to manage audit here
The QualityAudit tab
| Property | Metamodel name | Description |
| Short Description | ShortDescription | Short verbal description for this audit |
| Lead Auditor | HasLeadAuditor | Link to an entity who is LeadAuditor in this QualityAudit Links to: BusinessConnection, InterestGroup, Person, Position, Role. |
| Auditor | HasAuditor | Link to an entity who is auditor in this QualityAudit Links to: BusinessConnection, InterestGroup, Person, Position, Role. |
| Auditee | HasAuditee | Link to an entity who is audited in this QualityAudit Links to: BusinessConnection, InterestGroup, Person, Position, Role. |
| Audit Date | AuditDate |
The Subject tab
| Property | Metamodel name | Description |
| Target process | TargetProcess | Target for the QualityAudit Links to: BusinessDiagram, BusinessProcess, BusinessProcessNetwork, WorkFlowDiagram. |
| Target regulation | TargetRegulation | Target regulation for the QualityAudit Links to: Regulation, RegulationDiagram. |
| Questions | AuditQuestions | List of questions relevant for the audit |
The Findings tab
| Property | Metamodel name | Description |
| Non-Conformance | NonConformance | Link to NonConformance detected during this audit Links to: NonConformance. |
| Change Request | ChangeRequest | Link to ChangeRequest generated during this audit Links to: ChangeRequest. |
| Conclusion | Conclusion | Verbal conclusion for this QualityAudit |
| Group | ||
| Lead Auditor | LeadAuditorApproval | Link to the lead auditor who approved this QualityAudit Links to: Person, Position. |
| Process Owner | ProcessOwnerApproval | Link to the process owner who approved this QualityAudit Links to: Person, Position. |
| Auditee | TargetEntityApproval | Links to: Person, Position. |
The Breaks Down To tab
| Property | Metamodel name | Description |
| Breaks down to | BreaksDownTo | Link to sub-audits for this QualityAudit Links to: QualityAudit. |
Purpose: The purpose of the Workflow Diagram template is to document the Business Processes of an enterprise at the activity level.
Concerns: The Workflow Diagram template should be used to document the Activities, Roles, Business Events, Activity Paths and Workflow Conditions of a Business Process. Available in the default modeling syntax are also Business Objects, External Objects, Information Systems, Database, Inventory, Information Flow and Logistical Flow. The syntax can be easily extended to include more objects such as Requirements, Business Rules and Goals. Below you can see an example of a Workflow Diagram with multiple Roles that are modelled vertically:
Relation to other templates: The Workflow Diagram does not support BPMN, if using that notation, you should model in the Business Process Diagram template. The Workflow Diagram can link to other Workflow Diagrams and are typically linked to by Business Process Networks. In the picture below, you can see another example of a Workflow Diagram. Here the Roles are modelled horizontally and you can see the links to and from other diagrams at two Business Events (‘ECR completed’ and ‘Rework’):
Other functionalities: In QLM, you can control which buttons related to risk management are shown below activities. You can choose to hide or show Risks, Controls and Key Controls. Both Controls and Key Controls are a type of Activity. From the Risk related toolbars (available via the “Actions” tab on the right-hand side of the Canvas in QLM) choose the following button to control what button panels appear on the Activity objects:
Properties and metadata: The Workflow Diagram can for example retain the following information:
In the picture below you can see the Workflow Diagram’s properties dialogue window, where the diagram’s properties can be viewed and edited:
Purpose: The Rule Family Table template is used as an auxiliary template to document Rule Family symbols from Decision Models in more detail.
Core concerns: The Rule Family Table template should be used to model Rule Family symbols in more detail, describing the decision in more detail and listing each eventuality relevant to the Rule Family. Each row represents a possible combination of rules in the Rule Family. For example, in the eventuality that there are 3 rules with 2 possibilities each, there will be 2^3=8 rows in the Rule Family Table. Below are two examples of Rule Family Tables:
Relation to other templates: The Rule Family template is used to detail Decision Models and should not be used to document decisions in a stand-alone context. It should always be used as an extension to Rule Family symbols.
Properties and metadata: The Rule Family Table can for example retain the following information:
In the picture below you can see the Rule Family Table’s properties dialogue window, where the properties can be viewed and edited:
Purpose: The purpose of the Regulation Diagram template is to document those regulations the enterprise is subject to in detail, so it can be identified how the enterprise must adhere to them. Regulation diagrams is often used to document compliance by use of compliance matrices.
Core concerns: The Regulation Diagram template can model Regulations, Licenses, Business Scopes, Activities, Business Objects and their Connections. With this pallet of objects, you can model an overview of the regulations your organization must adhere to and break them down to more detailed diagrams describing their paragraphs. We recommend you keep it simple and link the regulations to the relevant Business Processes rather than modelling them in a complex diagram. Below, you can see two example of how you could model a Regulation Diagram for the ISO 9001:2008 standard:
Relation to other templates: As mentioned, the regulations can be linked to the relevant Business Processes or Activities, that typically are detailed in a Workflow Diagram or Business Process Diagram. The Regulation could then be shown as a link below the relevant Business Process or Activity:
How the enterprise will live up to the requirements from the different regulations can also be modelled in a Requirement Model.
Properties and metadata: The Regulation Diagram can for example retain the following information:
In the picture below you can see the Regulation Diagram’s properties dialogue window, where the properties can be viewed and edited:
Purpose: The purpose of the Product Rule Table template is to document the rules pertaining to a specific product.
Core concerns: The Product Rule Table is used as an auxiliary template and functions like a matrix that contains Product Rules.
Below, you can see an example of a Product Rule Table for a balcony:
Relation to other templates: The Product Rule Table is related to templates such as Manufacturing Routing Network, Product Architecture, and Product Variant Master.
Properties and metadata: The Product Rule Table can for example retain the following information:
The above picture shows the properties dialogue window for the Product Rule Table where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
Purpose: The purpose of the Product Canvas template is to present the relevant information related to a specific product.
Core concerns: The Product Canvas template enables you to gather relevant Business Charts and model Personae, Product Demands, Markets, Locations and Products. Additionally, you can model a SWOT analysis that details the Strengths, Weaknesses, Opportunities and Threats the product is affected by.
Below, you can see two Product Canvases. The first has its focus on a product within two markets, showing the expectations two different customer segments have to the product.
The second example shows information related to a specific market, Poland, including product architecture and business assessment:
Relation to other templates:
The Product Canvas Template is inherently related to the Product Architecture, Product Roadmap and Product Variant Master, in the sense that all these models focus on different aspects of the lifecycle of a product. Furthermore, you can create additional Business Charts for the Product Canvas by using the dedicated template. Another view on projects and initiatives are provided from the Enterprise Investment Portfolio. There, the reasoning behind the investment in the project is visualized by connecting the initiative (in this case a new product) to the specific goals of the enterprise that it contributes to. Another view on how the product meets customer needs can be documented in the Value Proposition Canvas.
Properties and metadata: The Product Canvas can for example retain the following information:
The above picture shows the properties dialogue window for the Product Canvas where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
Purpose: The purpose of the Manufacturing Routing Network is to specify the steps used in manufacturing a product. Below is an example of a Manufacturing Routing Network of an Item including Assembly, test and final control. At the right-hand side, you can see that different specifications have been attached as well:
Core concerns: The Manufacturing Routing Network template enables you to model Work Operations, Products, Business Objects, General Concepts, and Production Lines. You are also able to distinguish between Activity Paths, Assembly Flows and Transport Systems. If you wish to attach External Documents, they should be attached to the Work Operations they pertain to. Below is another example of a Manufacturing Routing Network that describes the process from assembly to shipping:
Relation to other templates: The Manufacturing Routing Network template is related to the various different models for products such as the Product Viewpoint template, the Product Variant Master template, the Product Rule Table, the Product Roadmap and the Product Canvas. Each template offers a different viewpoint of the product in various stages of its lifecycle.
Properties and metadata: The Manufacturing Routing Network template can for example retain the following information:
In the picture below you can see the Manufacturing Routing Network’s properties dialogue window, where the properties can be viewed and edited:
Purpose: The purpose of the Life Cycle Assessment Diagram template is to document the relations for an activity or product in a lifecycle context.
Core concerns: The Lifecycle Assessment Diagram concerns itself with modelling elements in a company that interact with the environment. The template enables you to model Environmental Aspects and Objectives for Activities in your organization. This template allows you to model Business Objects, Activities, Performance Indicators, Business Connection, Goals, Policies, Critical Success Factors, Change Requests and Problems. These elements can be grouped into Categories and connected by Impact Quantity, Recycling, Logistical Flows, Information Flows, and Activity Paths.
Below, you can see an example of a Lifecycle Assessment Diagram for a Product, from production to packaging, focusing on reducing unbiodegradable waste:
The elements used in this example are Business Objects as input and output, Activities showing Logistical Flows and Recycle under Process. Under the Environment Category, Environmental Aspects, Impact and Objectives are identified and Policies for reaching the Objectives are also included. The diagram focus on a single Environmental impact: Waste. You can also choose to map out several Environmental impacts that are relevant to a specific activity or product.
Relation to other templates: The Environmental Aspects and Impacts from the Lifecycle Assessment Diagram can be further explored in the Environmental Impact Diagram. The Lifecycle Assessment Diagram is also related to the Business Process Diagram and Workflow Diagram, in the sense that they all are related to detailing aspects of processes. The Lifecycle Assessment Diagram can also be decomposed from the Inventory object shown in, for example, the Production Site template.
Properties and metadata: The Lifecycle Assessment Diagram template can for example retain the following information:
The above picture shows the properties dialogue window for the Lifecycle Assessment Diagram template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
For more information: You can learn more about Lifecycle Assessment on the US Sustainable Facilities Tool website or turn to ISO standard 14040.