The Purpose of the the AuditProgram template is to plan audit programs.
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.
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, an “Acknowledge” action-button is shown in relation to e.g. the Diagram:
The Acknowledge history can be seen on the “Acknowledge History” tab:
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 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.
Purpose: The purpose of the Environmental Impact Diagram template is to document the environmental aspects and impacts for an Activity or Business Process.
Core concerns: The Environmental Impact Diagram enables you to model Business Functions, Activities, Business Objects, Environmental Aspects (Environmental Aspect, Environmental Impact, Health and safety impact) and Business Scopes. These elements can then be connected by Impact Quantities.
Below, you can see an example of an Environmental Impact Diagram, detailing the Environmental aspects and Health and safety impact:
The diagram shows all identified aspects and modes of impact for one or more specific processes.
Relation to other templates: The Environmental Impact Diagram is related to the Lifecycle Assessment diagram as well as templates containing Activities, Business Functions, Lines of Business, and Logistical Flows. As such, it is related to, for example, Business Process Diagrams, Workflow Diagrams, Business Diagrams, and Strategy Models.
Properties and metadata: The Environmental Impact Diagram template can for example retain the following information:
The above picture shows the properties dialogue window for the Environmental Impact Diagram, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
Purpose: The purpose of the Business Process Network is to at document a mid- to high-level view of Business Processes and their interrelationships.
Core concerns: The Business Process Network template enables the documentation of top to mid-level processes. The core objects available to model with are Business Processes, Business Events, Business Objects, Business Scope, Information Systems, and different types of connections. Below you can see two examples of a Business Process Network modelled in different styles.
High level process view without business events or connections between processes:
High-level process view where business events and connections indicate a flow between processes, stakeholders and customers:
Relation to other templates: The top-level processes would typically be broken down to one or more levels of mid-level processes. The last level of Business Process Networks can then be broken down to several Workflow Diagrams or Business Process Diagrams detailing the activities contained within the business process
Properties and metadata: The Business Process Network can for example retain the following information:
In the picture below you can see the Business Process Network’s properties dialogue window, where the diagrams properties can be viewed and edited:
Purpose: The purpose of the Business Process Diagram template is to enable workflow modelling using the industry standard BPMN (Business Process Modeling Notation).
Core concerns: The Business Process Diagram template supply you with the BPMN icons that enable you to draw a workflow diagram. These icons include different types of events, activities, gateways, connectors, as well as pools, lanes and artifacts such as data objects and messages. The Business Process Diagram is typically used to illustrate business processes and software processes used in requirement documentation. Below is an example of a classic BPMN diagram with swimlanes:
To ensure the right BPMN syntax, the Business Process Diagram template will continuously perform Graphic Syntax Checks while you model. When a graphic syntax error occurs, you will be met with an error message like the one shown below:
Other functionalities: The Business Process Diagram can enable the execution and automation of a process when the diagram is converted into XML type files.
If you don’t wish to have a visible pool in your diagram, you can choose to have a ‘default pool’ that doesn’t have to be graphically represented. You can see an example of a diagram without pool and lanes below:
Relation to other templates: The Business Process Diagram template is exclusively aimed at modeling using the BPMN standard. If the BPMN is not chosen as a mandatory standard, the WorkFlow Diagram template, which has fewer syntax limitations, can be used instead.
The Business Process Diagram is typically linked as a decomposition of a Business Process contained in a Business Process Network template.
Properties and metadata: The Business Process Diagram can for example retain the following information:
In the picture above you can see the Business Process Diagram’s properties dialogue window, where the diagram’s properties can be viewed and edited:
For more information: about the BPMN standard please visit OMG’s dedicated website.
Purpose: The purpose of the Business Excellence Diagram template is to describe a measuring tool based on The European Foundation for Quality Management Excellence Model (EFQM).
Core concerns: The Business Excellence Diagram enables you to model Business Scopes, Criterion and Sub Criterion. These aspects can then be connected by Criterion Influencers.
Below, you can see an example of a Business Excellence Diagram for the Leadership of an organization. The diagram is structured according to the EFQM and shows the overall scores for the leaderships performance:
Other areas covered in the EFQM are Policy & Strategy, People, Partnerships & Resources, Processes, Customer Results, People Results, Society Results and Key Performance Indicators.
Relation to other templates: The Business Excellence Diagram is a strategic template that is complimentary to the Business Capability Model, Stakeholder Model, Business Canvas, and Strategy Model
Properties and metadata: The Business Excellence Diagram can for example retain the following information:
The above picture shows the properties dialogue window for the Business Excellence Diagram template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
For more information: To learn more about the EFQM, please visit their website, where you can also find an overview of the EFQM Excellence Model.
Concerns: Identification of competencies, authority, and responsibilities
Purpose: Designing, deciding, informing
Scope: Single layer/Single aspect
The organization viewpoint focuses on the (internal) organization of a company, department, network of companies, or of another organizational entity. It is possible to present models in this viewpoint as nested block diagrams, but also in a more traditional way, such as organizational charts. The organization viewpoint is very useful in identifying competencies, authority, and responsibilities in an organization.
Concerns: Relationships and dependencies between applications, orchestration/choreography of services, consistency and completeness, reduction of complexity
Purpose: Designing
Scope: Multiple layer/Multiple aspect
The application cooperation viewpoint describes the relationships between applications components in terms of the information flows between them, or in terms of the services they offer and use. This viewpoint is typically used to create an overview of the application landscape of an organization. This viewpoint is also used to express the (internal) cooperation or orchestration of services that together support the execution of a business process.
Abstraction Level
Coherence, details
Layer
Application layer
Aspects
Behavior, active structure, passive structure
