SAP Signavio provides several standard process diagram types, each tailored for a different purpose in process modelling, analysis, and optimization. Below is a clear list of the most common diagram types you will encounter in SAP Signavio Process Manager and Journey Modeler, along with what they are used for.

 1. BPMN 2.0 Process Diagram (Business Process Model and Notation)

This is the primary and most widely used diagram type in SAP Signavio.

BPMN (Business Process Model and Notation) diagrams are used to visually represent business processes in a standardized, easy-to-understand way. They allow both business users and technical teams to understand how a process works end-to-end.

• Modelling end-to-end business processes
• Executable workflows
• Standardized communication between business and IT

Includes elements like:
Events, tasks, gateways, pools/lanes, data objects, subprocesses, message flows.

1. Documenting Business Processes

BPMN diagrams help organizations clearly document how work is done.

Examples:

• Order-to-Cash
• Procure-to-Pay
• Hire-to-Retire
• Customer support escalation

2. Process Analysis & Improvement

Teams use BPMN diagrams to identify:

• Bottlenecks
• Redundant tasks
• Delays
• Opportunities for automation

3. Fit-to-Standard Workshops (SAP Projects)

In SAP implementations (like S/4HANA), BPMN diagrams are used to:

• Compare current processes vs SAP Best Practices
• Capture gaps (→ Cloud ALM requirements)
• Align business teams around a unified process

4. Workflow and Automation Design

BPMN is the standard notation for designing automation flows used in:

• SAP Build Process Automation
• SAP Signavio Workflow Accelerator
• RPA bots
• Integration flows

The model becomes the blueprint for technical implementation.

5. Training and Communication

Because BPMN is visual and standardized, it is used for:

• End-user training
• SOP documentation
• Cross-team communication

6. System Integration & Monitoring (Cloud ALM)

In SAP Cloud ALM, BPMN diagrams help map:

• Business process steps → monitoring events
• Interfaces → message flows
• Exception handling paths

This allows process-centric monitoring.

2. EPC (Event-Driven Process Chain)

Used mostly by organizations from SAP Solution Manager / ARIS backgrounds.

Used for:

• High-level process documentation
• SAP S/4HANA transformation projects
• Linking events → functions → rules
  1. High-Level Process Documentation (Level 1–2 Processes)

  In Signavio, EPCs are often used to represent high-level, conceptual business processes before going into detailed BPMN modeling.

  Why:

  • Easier for executives and business users
  • Shows process logic without technical detail
  • Good for workshops and business alignment
  1. Documenting AS-IS Processes for SAP Transformations

  Many organizations migrating to S/4HANA use EPCs to document current-state processes, especially if they previously used:

  • SAP Solution Manager
  • ARIS
  • SAP Blueprint methodology

  Why EPC here:

  • Mirrors older SAP documentation formats
  • Simpler representation than BPMN
  • Faster to model at a high level
  1. Building End-to-End Process Landscape / Architecture

  EPCs work very well for process landscape mapping, such as:

  • Level 0 Value Chain
  • Level 1 Core Processes (O2C, P2P, H2R)
  • Level 2 Subprocesses

  In Signavio, many customers model their entire enterprise process hierarchy using EPCs.

  1. Pre-BPMN Modelling for Detailed Design

  Many Signavio users follow a two-step modelling approach:

  Step 1 → EPC:
  Capture conceptual flow (events + functions)

  Step 2 → BPMN:
  Convert detailed flows into executable workflows

  This avoids making BPMN diagrams overly complex.

  5. Fit-to-Standard Workshops (High-Level View)

  During SAP Fit-to-Standard discussions, EPCs can be used to:

  • Introduce the process at a business-friendly level
  • Compare AS-IS to SAP Best Practice TO-BE
  • Identify gaps before creating Cloud ALM requirements
    6. Represent Processes Without Technical Details

  EPC is preferred when:

  • No need to show message flows
  • No need to model system integrations
  • The process is non-automated or conceptual
  • Only business decision flow matters

  This makes EPC the simpler choice compared to BPMN.

  Why Organizations Use EPCs in Signavio Even Today

  Reason	Explanation
  ✔ Business-friendly visuals	Functions + events are simple to read
  ✔ Legacy familiarity	Many SAP customers used EPC for 10+ years
  ✔ Good for high-level processes	Ideal before jumping into BPMN
  ✔ Works well with process landscapes	Great for level 0–2 diagrams
  ✔ Not as technical as BPMN	Suitable for non-IT stakeholders

  EPC vs BPMN in Signavio — When to Use Which

  Use Case	Recommended
  High-level process overview	EPC
  Conceptual business flow	EPC
  SAP AS-IS documentation	EPC
  End-to-end process landscape	EPC
  Detailed flow (roles, systems)	BPMN
  Workflow automation	BPMN
  Detailed technical integration	BPMN

   Example EPC Diagram (Signavio Style)

  

   

   

3. SIPOC Diagram (Supplier – Input – Process – Output – Customer)

Used for:

• Lean Six Sigma
• Defining high-level process boundaries
• Mapping suppliers, inputs, outputs, customers

4. Journey Models (Customer / Employee Journeys)

Used for:

• Mapping customer or employee experiences
• Identifying pain points and opportunities
• Aligning processes with customer expectations

6. DMN Decision Model (Decision Model & Notation)

Used for:

• Business rules modelling
• Decision tables
• Automation and rule evaluation

Often linked to BPMN processes for decision logic.

7. Organization Charts (Org Chart)

Used for:

• Mapping roles, departments, reporting lines
• Connecting organizational units to processes

8. Diagram for Process Data / Dictionary Models

(Not a visual diagram like BPMN—more of a structured data model)

Used for:

• Maintaining global process documentation assets
• Centralizing terms, IT systems, roles, KPIs

Summary Table

How BPMNs Connect with SAP CloudALM implementation and Operations (Chapter 2)

Using Signavio in S4/Hana Conversion along with SAP Activate methodology(Chapter 3)