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

Key Restrictions

License Types

Modelling Restrictions

Syway Modelling Conventions

Introduction

Context

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. 

Scope

These standards apply to all business process models created and maintained in SAP Signavio, including:

• Process landscapes
• Value chains
• Process diagrams (BPMN 2.0)

Signavio Key Users

Each Pod has three Signavio Key Users who receive Enterprise licenses and are granted additional levels of access to Signavio functionality.

They are responsible for most of the process modelling in Signavio, as Collaboration license holders may only create models via Quickmodel, they may not edit process models. 

The SKU group and the BPM members of the Integration team meet weekly to discuss Signavio, to share knowledge and lessons learned, and to solve any BPM issues.

Key Design Principles and Guidelines

• Clarity First
  • Every model should be immediately understandable to its intended audience
  • Avoid unnecessary complexity
  • Focus on communicating the process flow clearly
  • Important for employees to understand how their work areas interface with others as part of process orientation, or if employees from different project phases are to work together successfully
• Standardisation
  • Use consistent modelling patterns, symbols, and layouts
  • Apply the same level of detail for similar processes
  • Ensure uniform naming and labelling
  • Creates a basis for effective communication between employees in different departments
• Appropriate Detail
  • Include only information relevant to the model's purpose
  • Maintain consistent levels of detail and granularity within a model
  • Create sub-processes for highly repeatable strings of activities within an L4, in order to facilitate ease of legibility and comprehension. See section 3.3.5. Sub-Processes
• Maintainability
  • Design models to be easily read and updated
    • Consider separating large and complex processes into smaller Level 4’s
    • Do not map optional paths
    • Maintain a neat and orderly layout of objects
  • Document modelling decisions and exceptions
• Key Benefits
  • Improved model readability and comprehension 
  • Consistent process documentation
    • Models can be used as a key foundation upon which training documentation can be built and maintained
  • Enhanced collaboration across teams
    • Security requirements can be captured through the use of swim lanes
    • Risks and Controls can be captured and linked appropriately
    • More comprehensive use of automated testing tools
  • Simplified model maintenance 
  • Accelerated onboarding for new modelers 
  • Efficient process analysis and optimisation
    • Allows for ongoing process improvement long beyond the project lifecycle

Process Landscape

Process Hierarchy

Dictionary and Master Objects

Model Types

Diagram Naming

Process Diagram Variants

Layout and Process Integration

Process Modelling

Relationships

Objects

Elements of a Process or Process Step

Configuration Items

Diagrams and Documentation

End User Roles

Process Links

General Process Layout and Format Conventions

Naming Conventions

E2E Scenario Diagrams

Diagram Development Lifecycle

See also

Change log

Workflow history