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:
Description of the diagram
Link to the owner of the diagram
Link to the one responsible for executing the processes in the diagram
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
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:
Description of the diagram
Expression and query language
Link to the owner of the process
Link to the one responsible for executing the process
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
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:
Concerns: Dependencies between business processes, consistency and completeness, responsibilities
Scope: Multiple layer/Multiple aspect
The business process cooperation viewpoint is used to show the relationships of one or more business processes with each other and/or with their environment. It can be used both to create a high-level design of business processes within their context and to provide an operational manager responsible for one or more such processes with insight into their dependencies. Important aspects of business process cooperation are:
Causal relationships between the main business processes of the enterprise
Mapping of business processes onto business functions
Realization of services by business processes
Use of shared data
Each of these can be regarded as a “sub-viewpoint” of the business process cooperation viewpoint.
Purpose: The purpose of the Business Object Model is to present a structured view of an organization’s products and services.
Core concerns: The focus of this template is the Business Object that can be described through Decomposition, Generalization, Association and Dependency with other Business Objects. Notes can be used to group Business Objects, for example as High-Growth Revenue Products, as seen in the below model:
The modelling syntax can be extended to also include strategic elements such as: Requirements, Problems, Change Requests, Goals, Performance Indicators and policies. They can be connected to the Business Objects through Strategic Alignment.
Relation to other templates: The Business Object Model belongs to the Information domain where it offers a conceptual and logical view of an organizations products and services. As such, it is related to templates such as Product Canvas, Product Roadmap and Product Variant Master
Properties and metadata: The Business Object Model can for example retain the following information:
A description of the diagram
Link to the owner of the diagram
Link to the one responsible for the diagram
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
The above picture shows the properties dialogue window for the Business Object Model, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
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.
Properties and metadata: The Business Excellence Diagram can for example retain the following information:
A description of the diagram
Link to the owner of the diagram
Link to the one responsible for the diagram
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
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.
Purpose: The purpose of the Business Ecosystem template is to enable an organization to understand itself from an outside-out perspective by modelling the environment in which the organization is embedded.
Core concerns: The Business Ecosystem supplies five elements to model with: Business, People, Things, Business Interaction and Business Moment. The Business Ecosystem template should primarily be used for modeling entities outside the enterprise to identify new business opportunities in the form of Business Moments.
Above you can see a model of a Business Ecosystem. The blue areas are Business Moments, where the interactions between People, Businesses and Things create business opportunities for your enterprise.
Relation to other templates: The Business Ecosystem model is based on the Enterprise Design theories and is as such in the same family as the Customer journey map.
Properties and metadata: The Business Ecosystem can for example retain the following information:
A description of the diagram
Link to the owner of the application architecture
Link to the one responsible for the application architecture
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.
For more information: If you want to learn more about Enterprise Design, we have a four-part webinar by Milan Guenther available for viewing. You can also visit Milan’s website, where you can learn more about the Enterprise Design framework.
Purpose: The purpose of a Business Diagram is to show the functional structure and relationships of the whole or part of an organization.
Core concerns: The Business Diagram template enables you to model Business Functions, Information Systems, Inventory, Business Scope, Lines of Business, Information Flow and Logistical Flow. The diagram’s syntax can be extended to also include strategic elements such as Goals, Objectives, Stakeholders and Performance Indicators.
The Business Diagram should be broken down into several levels of recurring Business Diagram templates. In the model below, you can see an example of a high-level Business Diagram showing Business Functions and their Information Flows and Logistical Flows – describing the flow of products and services – in this case for a car rental service.
The Business Functions are placed with the operational functions in the bottom together with the Logistical Flow and with management control at the top of the Business Diagram.
On lower levels (decompositions) of Business Diagrams, Information Systems are placed close to the Business Functions that are responsible for or own the Information Systems.
Relation to other templates: The Business Diagram can be used as an addition to a Business Process Network and Strategy Models, giving a practical view of how the organizations functions fit together, illuminating interdependencies.
Properties and metadata: The Business Diagram can for example retain the following information:
A description of the diagram
Link to the owner of the Diagram
Link to the one responsible for the Diagram
Indication of the diagram portrays an as-is situation or a to-be situation
The Perspective can be defined as either: Holistic, Sub-functional, Process, or IT Focused.
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
The above picture shows the properties dialogue window for the Business Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
For a quick introduction to BusinessCharts please see the video below as it explains how to create a BusinessChart based on Pie charts.
The video contains:
How to use the QML to create charts
How to customize the charts
An introduction to the versatility of using charts in QualiWare
Purpose: The purpose of the Business Chart template is to create different graphs and charts using information from other diagrams and templates. The Business charts can then either be published on a Dashboard and/or stored.
Core concerns: The Business Chart template is concerned with analyzing other templates and models. Therefore, it is not modelled like a typical template, but created using the Chart Wizard found in the template’s property window:
Below, you can see the Chart Wizard that helps you create your Business Chart:
The Business Chart template can for example be used to generate a chart over how the capabilities or Key Performance Indicators of an enterprise are performing over time or compared to desired values. Additionally, Business Charts can be used to analyze static data entered in a Matrix model. You choose the input to your Business Chart as a ‘Data Source’ in the templates metadata (see figure under Metadata).
Below, you can see two very different examples of business charts:
Relation to other templates: The Business Charts are published using the Dashboard template.
Properties and metadata: The Business Chart template can for example retain the following information:
A description of the diagram
Link to the owner of the business chart
Link to the one responsible for the business chart
Link to data source
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
The above picture shows the properties dialogue window for the Business Chart Template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
Purpose: The purpose of the Business Capability Model template is to provide an overview of the of the state and health of an enterprise in the form of its Capabilities.
Core concerns: The Business Capability Model is a simple template that by default only allows for the modelling of Capabilities with the possibility to add notes if needed. The metadata of the Capabilities – such as status and importance can then be graphically displayed in the business capabilities to create a useful overview.
The stripe on the left side to represent Business Importance and two dots representing Business Maturity and Target Maturity. The new design scales better and provides management with a single view of important strategic capabilities with a plan for improvements. Also it allows the business architect to highlight a set of capabilities by coloring the symbol’s background – a widely used technique.
Business Capability model with new symbol design
In the picture above you can see an example of a Business Capability Model. Here the Business Capabilities are grouped in different areas and the status and importance of them are shown by their green, yellow or red colorings.
In this Business Capability Model (shown above), more attributes are shown at the right-hand side of the Capability. This way you can get a more detailed view of the state of your enterprises Capabilities.
Other functionalities: Using the Analysis tool, the information from the Business Capability Model template can generate maturity- and score heat maps, hierarchies, score views, capability contexts, gap analyses, dashboards, and what-if-, impact- and investment analyses.
Relation to other templates: The Business Capability Model is a strategic template and is as such complimentary to for example the Strategy Model and Work Model. It can be used to illustrate a change process going from one set of capabilities to another. A Capability can link to the Business Processes that uses it as well as the resources it employs. This way it can also be analyzed which Business Processes would be affected by the improvement or worsen of a given Capability.
It is easy to update and analyse the capability models via the standard views on the web:
The capabilities in a Business Capability Model can easily be scored and presented in filterable and editable lists via the spreadsheet functionality in e.g. the Properties view
The capabilities can be presented in a Capability heatmap
From the Delivered by view you can analyze and update relations between capabilities and initiatives, processes, applications and information-objects.
Properties and metadata: The Business Capability Model can for example retain the following information:
A description of the diagram
Link to the owner of the diagram
Link to the one responsible for the accuracy of the diagram
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.
The above picture shows the properties dialogue window for the Business Capability Model where you can edit the diagram’s properties.
Note that the Capabilities’ metadata that are exhibited in the Business Capability Model is not further described here as they belong to the Capability object and not the Business Capability Model template.
Purpose: The Business Canvas, is a strategic management and entrepreneurial template. It allows you to describe, design, challenge, invent, and pivot your business model.
Core Concerns: The core elements of the business canvas are framework cells that define a strategic or organizational entities and, if needed, connections between them. The Business Model can be structured any way you wish. The most well know structure of a business model is Alexander Osterwalder’s Business Model Canvas.
The above picture shows a blank Business Model Canvas where each area is represented by a framework cell.
The strategic or organizational entities can then be enriched with an extended portfolio of strategic symbols such as vision, mission, goals, stakeholders, information systems and business processes.
Full content list of the extended portfolio:
Vision
Mission
Business Object
Market
Competitive Advantage
Technology
Competence
Capability
Performance Indicator
Business Function
Business Process
Organization Unit
Stakeholder
Information System
External Entity
Location
Channel
Goal
Opportunity
Threat
Trend
Material Asset
Intellectual Capital Asset
Business Rule
Key Performance Indicator
The picture below shows a Business Model Canvas that is filled out with symbols from the extended portfolio.
