| Status | |
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Introduction
Purpose
This document establishes the SyWay standards for business process modelling using SAP Signavio to ensure consistency, quality, and clarity in process documentation across all business processes.
Objectives
List specific goals this standard aims to achieve. Include objectives like ensuring model reusability, standardizing process flows and improving model accessibility.
Key Restrictions
Outline any limitations or restrictions that apply.
Introduction
Context
Define the purpose and context of Process Models specifying how it will be used within the organization
Business Process
Process Model Definition and Usage
The SyWay project drives the implementation of new business processes across Syensqo’s organisation, utilising SAP Signavio to promote simplicity and effectiveness throughout.
Syensqo implements elements of the BPMN 2.0 process modelling framework in SAP Signavio, utilising a modular hierarchy of process models to create the Syensqo Business Process Architecture. This architecture is a framework that visually maps how Syensqo's business processes, systems, and data work together to achieve its business goals. The methods by which Syensqo’s business processes are modelled are described here and defined as the Business Process Modelling Standard (BPM Standard).
Syensqo’s Business Process Architecture is a logical structure of business processes defined in a modular hierarchy. Assigned to that binds business process with IT, reflecting the integration and standardisation requirements of Syensqo’s operating model. Focusing on good Business Process Management (BPM) leads to a greater, company-wide understanding of how the organisation works together in a continuous flow of value-creating processes.
Syensqo defines a business process as a series of logically linked activities, with a clear beginning and end, as well as clearly defined inputs and outputs. It is therefore a structure for action.
Process Landscape
Describe the organization of the Process Landscape in Signavio.
Process Hierarchy
Explain the hierarchical structure of processes within Signavio from high-level functions to detailed sub-processes. Provide specific instructions on assigning each model to the correct level (e.g. L1, L2, L3, etc).
Dictionary and Master Objects
Describe the role of the Dictionary in Signavio as the central repository for Master Objects.
Model Types
Document the different model types used (e.g., BPMN Process Diagrams, Value Chain Diagrams, Journey Models) and their applications within the organization.
Diagram Naming
Standardized naming conventions for each diagram to facilitate easy identification and consistent alignment with organizational processes.
Process Diagram Variants
Outline variants of Process Diagrams to capture different process scenarios (e.g. regional, functional or system-specific variations).
Layout and Process Integration
Ensure consistent layout and alignment in all Process Diagrams, incorporating necessary integration points to other related models and diagrams in the Process Landscape.
Process Modelling
Relationships
Detail how relationships between objects within Process Models should be established to accurately reflect dependencies and sequence flows.
Objects
Outline the use of specific Signavio objects, such as Process Steps, Tasks, Roles, and Logical Component Groups, and describe their roles within process flows.
Elements of a Process or Process Step
Define all relevant Attributes, Links, and process-specific Elements associated with Process Steps or Tasks.
Configuration Items
Explain how Configuration Items (e.g., configuration workbooks, technical documentation) should be documented as Master Objects in the Dictionary.
Diagrams and Documentation
Provide guidelines on attaching relevant documentation to diagrams and Dictionary objects.
End User Roles
Describe the approach for defining End User Roles in the Dictionary and how they should be assigned to relevant Process Steps or models to avoid duplication.
Process Links
Describe how links should be used to establish a cohesive Process Landscape.
General Process Layout and Format Conventions
Outline layout and format standards including font style, color coding and swimlane usage. These standards ensure readability and a unified look across models.
Naming Conventions
Describe standardized naming conventions for objects, process steps, and Dictionary items. Include examples and any abbreviations or prefixes to be used.
E2E Scenario Diagrams
Provide guidelines on developing End-to-End Scenario diagrams to represent cross-functional or cross-system processes.
Diagram Development Lifecycle
Describe the full lifecycle for developing diagrams, from creation and review to approval and publication. Specify roles and responsibilities for each stage.
See also
Provide links and references to any related documents or standards that support understanding this business process modeling standard and its implications.
