Web-Modeler Enabled Diagram | QualiWare Center of Excellence

Product Canvas

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:

A description of the diagram
Link to the owner of the canvas
Link to the one responsible for the canvas
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 Product Canvas where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Product Architecture

Purpose: The purpose of the Product Architecture template is to document the building blocks of a product. Below is an example of a product architecture:

Core concerns: The Product Architecture template enables you to model a Product and connect different parts of it with three different connection types: Part of Product, Kind of Product, and Product Interface. See below for an example of a Product Architecture where each Product object is represented graphically:

Relation to other templates: Depending on whether the product is in production or in its development phase, it could be further described in a Product Viewpoint template, have a Product Variant Master, Product Rule Table or be represented in a Product Canvas. It may also be illustrated along with other products in a Product Roadmap, just as its production may be detailed in a Manufacturing Routing Network.

Properties and metadata: The Product Architecture 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
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.

In the picture below you can see the Product Architecture’s properties dialogue window, where the properties can be viewed and edited:

Organization Diagram

Purpose: The purpose of the Organization Diagram template is to document the Organizational structure for a company or part of a company. Below, you can see an example of an Organizational Diagram describing the different departments of a company:

Core Concerns: The Organization Diagram template focuses on the documentation of organization units, positions and their interrelationships. The relationship between units illustrates responsibility. The example below of a regional office illustrates the levels of responsibilities between its different departments:

Relation to other templates: The Organization Units in the Organization Diagram can link to diagrams such as Business Process Networks, Business Process Diagrams, Workflow Diagrams, Business Canvas, Strategy Model and more. You decide what kind of information you want to be accessible through the organization diagram. To model the organization in relation to its environment for strategic purpose, you can use the Business Ecosystem template.

Properties and metadata: The Organization 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 accuracy of 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
Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

In the picture below, you can see the Organization Diagram’s properties dialogue window, where its properties can be viewed and edited:

Manufacturing Routing Network

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:

A description of the diagram
Link to the owner of the diagram
Link to the one responsible for the accuracy of 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
Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

In the picture below you can see the Manufacturing Routing Network’s properties dialogue window, where the properties can be viewed and edited:

Lifecycle Assessment Diagram

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:

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 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.

Integration View

Purpose: The purpose of the Integration View template is to document the routing of integrations between systems.

Core concerns: The Integration View template enables you to model Information Systems, System Components and External Entities (a source to or a receiver of information from a system), and connect them using Integration Flows.

Below is an example of an Integration View concerning the flow of test data:

Relation to other templates: The Integration View belongs to the Application layer of the architecture and is as such related to the Application Architecture Diagram, the Data Flow Diagram and the Component Diagram.

Properties and metadata: The Integration View template can for example retain the following information:

A description of the model
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 Integration View template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Innovation Canvas

Purpose: The Purpose of the Innovation Canvas is to model ideas for Innovation detailing their goals and ideas for action.

Core concerns: The Innovation Canvas allows you to model an innovation detailing the ideas that exist in relation to it. In the example below, the goals of the innovation have also been defined and attached. Goals, vision, mission and many more strategic objects are available in the default extended syntax for the diagram, enabling you to model your ideas for innovation in as much detail as you prefer.

Relation to other templates: The Innovation Canvas is a strategic template and the elements modelled in it can easily be connected to other strategic templates such as a Strategy Model, Enterprise Investment Portfolio, Business Canvas or Business Capability Model.

Properties and metadata: The Innovation Canvas 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
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.

In the picture below you can see the Innovation Canvas’ properties dialogue window, where the properties can be viewed and edited:

Infrastructure Diagram

Purpose: The purpose of the Infrastructure Diagram template is to document the physical infrastructure of the enterprise, which includes but is not limited to databases, wires, firewalls, computers etc.

Core concerns: The Infrastructure Diagram enables you to model your organizations infrastructure including: Computer Categories, Computers, Firewalls, Printers, Networks, Connection Points, Peripherals, Locations, Information Systems, System Components, Databases, Network Connections, Object Dependencies, Technology Domains, Technology Capabilities and Technology Components.

The models below exemplify how you would construct this type of diagram:

Relation to other templates: The Infrastructure Diagram template should not be used to document logical architecture, as the connections available in an Infrastructure Diagram are predominately geared towards documenting physical information about IT infrastructure. The Infrastructure Diagram can through its components be linked to other architectural diagrams such as the Application Architecture Diagram, and the data they contain. This way, if a firewall is breached, you would be able to very quickly identify what data has been vulnerable.

Properties and metadata: The Infrastructure 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 Infrastructure Diagram, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Freehand Diagram

Purpose: The purpose of the Free Hand Diagram template is to document using drawings that do not match any of the other structured diagram templates.

Core concerns: The Freehand Diagram template enables you to, for example, insert a General Concept, paste a picture file on it and describe it using Freehand symbols. You can also link to other diagrams from it. The Freehand symbols used can be placed either on or behind the Picture you choose and present information or links when clicked on.

Objects available in the Freehand Diagram template:

The Free Hand Diagram template should not be used to document any information that can be documented in other templates.

Below, you can see two examples of Freehand Diagrams, where the Freehand Objects are made visible:

Relation to other templates: The Freehand Diagram can, because of its flexibility, be related to any of QualiWare’s diagram templates. It can be a decomposition of Logistical Flows, Business Functions, Lines of Buisness, Business Scopes, Activities, Inventory and Information Systems.

Properties and metadata: The Freehand Diagram template 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 Freehand Diagram template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Firewall

Purpose: The purpose of the Firewall template is to document network zones designated by firewalls.

Core concerns: The Firewall template enables you to model Zones, Computers, Networks and Firewall Policies to create a model of a firewall. A firewall is used to control the communication between different networks, typically for security reasons.

Graphical representation of objects:

A Firewall diagram will typically show the Zones of the firewall and the communication policies/rules (Firewall Policies) that exist between the zones. Below, you can see an example of a Firewall diagram containing Zones and Servers (represented by the Computer object):

Relation to other templates: The Firewall template is a technology template and related to the Infrastructure Diagram.

Properties and metadata: The Firewall template can for example retain the following information:

A description of the diagram
Link to Vendor and Hardware
Link to servers
Contract information
Details about resources, costs and benefits
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 Firewall template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.