Project Overview
As part of the Information Management coursework at FH Südwestfalen, I participated in a Business Process Modeling project using SAP Signavio — one of the leading enterprise-grade process modeling tools used by global corporations.
The project tasked me with modeling the product sortation process of a real-world logistics environment: the Amazon DTM9 Sortation Centre in Witten, Germany — a facility I had direct operational knowledge of through my part-time role there.
Why this matters: Business Process Modeling is the foundation of process improvement, automation (BPA/RPA), and ERP implementation. In Controlling and Finance, understanding how to document and analyse business processes is essential for identifying cost drivers, inefficiencies, and automation opportunities.
The DTM9 Sortation Centre
DTM9 is an Amazon Sortation Centre that receives products from multiple fulfilment centres and sorts them by delivery destination before dispatching to last-mile delivery stations.
The centre operates with five distinct organisational units, each with clearly defined responsibilities in the sortation workflow:
Inbound Team Lane 1
Receives trucks from fulfilment centres, unloads products, and performs initial weight-based sorting. Products under 15 kg proceed to the Sortation Area; products over 15 kg are redirected to the Non-Con (non-conveyable) Area.
Sortation Team Lane 2
Receives products from the Inbound Area and sorts them by delivery destination. Products with issues are escalated to the Problem Solving Team via a collapsed sub-process.
Problem Solving Team Lane 3
Handles exception cases — damaged products or incorrect labels — identified by any team. Collects, identifies, fixes, and returns products to the buffer area. Modeled as a separate reusable sub-process.
Buffer & Quality Team Lane 4
Scans container labels, checks destination accuracy, fixes issues where found, and approves containers for loading. Acts as the quality gate before outbound dispatch.
Outbound Team Lane 5
Scans labels and checks CPT (Critical Pull Time). Urgency-based gateway determines whether containers are loaded immediately or held in the Buffer Area. Dispatches trucks to delivery centres.
Process Architecture
The main process was modeled as a Pool representing the DTM9 Sort Centre, with five Swimlanes for each organisational unit. This structure visually communicates both what happens and who is responsible — a key principle of BPMN 2.0.
Simplified Flow — Amazon DTM9 Sortation Process
Team
→ Non-Con
Team
Inbound
Destination
Buffer Area
Solving
Sub-process
Buffer Area
Quality
Labels
Destination
Loading
Team
by Scan
Delivery Centres
The diagram uses Exclusive (XOR) Gateways at key decision points — weight check, problem detection, and CPT urgency — and a Parallel Gateway in the outbound flow. This precisely models the conditional logic inherent in real warehouse operations.
SAP Signavio Diagrams
The following diagrams were created in SAP Signavio Academic Edition, exported as process documentation. The main diagram (Revision 11) represents the final, validated version submitted as part of the coursework.
Key BPMN Elements Used
The model applies the full range of core BPMN 2.0 constructs, demonstrating proficiency with the notation standard used in enterprise process management:
| Element | Type | Lane | Description |
|---|---|---|---|
| Trucks Arrive from Fulfilment Centres | Start Event | Inbound Team | Triggers the entire sortation process |
| Unload Trucks / Sort by Weight | Task | Inbound Team | Sequential physical tasks at inbound dock |
| Weight? / Problem? / Urgent? | XOR Gateway | Multiple | Exclusive decision points branching the flow |
| Problem Solving Sub-process | Collapsed Sub-process | Problem Solving | Reusable exception-handling process (Rev. 5) |
| Parallel Gateway | AND Gateway | Outbound Team | Manages parallel urgency-based loading decisions |
| Trucks leave for Delivery Centres | End Event | Outbound Team | Marks successful completion of the sortation cycle |
Problem Solving Sub-process
A key design decision was modeling the problem-solving workflow as a separate, reusable collapsed sub-process — a best practice in BPMN that keeps the main diagram readable while preserving full detail.
The sub-process is called from both the Inbound and Sortation lanes whenever a problem gateway returns YES. It follows a structured five-step flow:
Receives data from problem carts → Collects damaged / wrong-label products → Identifies the issue → Fixes the issue → Takes products back to Buffer Area → End: Products reach Buffer Area
This design reflects real-world practice: problem-solving teams at Amazon's sortation centres operate as a decoupled support function, receiving escalations from any lane and returning resolved items to the main flow without interrupting it.
Key Learnings
This project bridged theoretical BPM knowledge with real operational context, producing insights directly applicable to Controlling and process improvement roles:
BPMN 2.0 Proficiency
Hands-on mastery of events, gateways, tasks, pools, lanes, and sub-processes — the universal language of enterprise process documentation.
SAP Signavio Tooling
Practical experience with the same collaborative process modeling tool used by SAP customers globally for S/4HANA implementation and process governance.
Exception Handling Design
Learned to model complex exception flows (Problem Solving sub-process) cleanly without bloating the main process — a key skill in enterprise BPM.
Process → Automation Thinking
Understood how a BPMN model becomes the blueprint for BPA/RPA implementation — translating documented processes into automation candidates.
Cross-functional Coordination
Modeling five interdependent teams revealed how handoffs between organisational units create both efficiency opportunities and risk points.
Real-world Grounding
Applying the model to a facility I worked in directly validated the theoretical framework against operational reality — strengthening both model accuracy and personal insight.