Nodinite Expected BPM Layout - Order-to-Cash Flow
Visualize the 7-step Order-to-Cash process flow with the Nodinite Business Process Model (BPM) matrix, showing how Services, Domains, and connections flow across the Sales, Planning, Logistics, and Finance swimlanes.
On this page, you will:
- ✅ See the expected BPM matrix layout with 4 domain swimlanes and 7 business steps
- ✅ Understand process flow and service connections across Systems
- ✅ Learn how divergence and convergence points work in the flow
- ✅ Explore how Services map to business milestones with automated visualization
- ✅ Reference the exact topology that the PowerShell demo script creates

Animated walkthrough: the BPM INT1337 - Order-to-Cash Flow in the BPM Designer. It highlights the four Domains (Sales, Planning, Logistics, Finance), then the seven step Services in order, and ends on the full BPM. The gray box in Planning, Step 7, is the sub-process BPM BPM 1337 - Order-to-Cash Flow from the Hierarchical BPMs walkthrough; the demo script doesn't create it.
Understanding the BPM Layout
The Repository Binding in each Log Event from the demo data script places a Service in a Domain row (swimlane) and a step column. The connectors come from the ServiceRelations in the binding.
Portal"] S3["fa:fa-envelope Step 3: Confirmation Sent
Portal"] end subgraph Planning["Planning (Index 1)"] S2["fa:fa-server Step 2: Order Entry
ERP"] S4["fa:fa-calendar Step 4: Production Scheduled
ERP"] end subgraph Logistics["Logistics (Index 2)"] S5["fa:fa-box Step 5: Ready for Transport
WMS"] S6["fa:fa-truck Step 6: Order Delivered
WMS"] end subgraph Finance["Finance (Index 3)"] S7["fa:fa-file-invoice-dollar Step 7: Order Invoiced
ERP-Finance"] end S1 -->|"Order Entry"| S2 S2 -->|"Confirmation Sent"| S3 S2 -->|"Order Planned"| S4 S3 -->|"Order Planned"| S4 S4 -->|"Ready for Transport"| S5 S5 -->|"Order Delivered"| S6 S6 -->|"Order Invoiced"| S7 style S1 fill:#2678BD style S3 fill:#2678BD style S2 fill:#E47528 style S4 fill:#E47528 style S5 fill:#3F827B style S6 fill:#3F827B style S7 fill:#9E59BB
The seven BPM steps grouped by Domain swimlane: Sales (blue), Planning (orange), Logistics (teal), and Finance (purple). Step 2 diverges into confirmation and planning, and Step 4 converges both paths.
Matrix Layout in the BPM
The same layout as it appears in the BPM matrix, with Domains as rows and steps as columns:
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ BPM: INT1337 - Order-to-Cash Flow │
│ │
│ Matrix Layout: Domains (Rows) × Steps (Columns 1-7) │
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Domain Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7
(Index) (StepNumber=0) (StepNumber=1) (StepNumber=2) (StepNumber=3) (StepNumber=4) (StepNumber=5) (StepNumber=6)
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Sales ┌─────────────────┐ ┌─────────────────┐
(0) │ Order Received │ │ Confirmation │
│ │ │ Sent │
│ Portal │ │ │
│ RCV-Order- │ │ Portal │
│ Incoming │ │ SND-Confirm- │
└─────────────────┘ │ Outgoing │
│ └─────────────────┘
│ "Order Entry" ▲
│ │
▼ │ "Order Planned"
Planning ┌─────────────────┐ "Confirmation Sent" │
(1) │ Order Entry │────────────────────────────────► │
│ │ │
│ ERP │ "Order Planned" │
│ ENT-Order-Entry │─────────────────────────────────► ┌─────────────────┐
└─────────────────┘ │ Production │
│ Scheduled │
│ │
│ ERP │
│ PLN-Order- │
│ Scheduled │
└─────────────────┘
│
│ "Ready for Transport"
│
▼
Logistics ┌─────────────────┐ ┌─────────────────┐
(2) │ Ready for │ │ Order Delivered │
│ Transport │ │ │
│ │ │ WMS │
│ WMS │──────►│ RCV-Order- │
│ PKG-Order- │ │ Delivered │
│ Packed │ └─────────────────┘
└─────────────────┘ "Order Delivered"
│
│ "Order Invoiced"
│
▼
Finance ┌─────────────────┐
(3) │ Order Invoiced │
│ │
│ ERP-Finance │
│ INV-Order- │
│ Invoiced │
└─────────────────┘
Process Flow Summary
| Step | Domain | Service | Display Name | Connects To |
|---|---|---|---|---|
| 1 | Sales | INT1337-RCV-Order-Incoming | Order Received | → Step 2 |
| 2 | Planning | INT1337-ENT-Order-Entry | Order Entry | → Steps 3, 4 |
| 3 | Sales | INT1337-SND-Confirm-Outgoing | Confirmation Sent | → Step 4 |
| 4 | Planning | INT1337-PLN-Order-Scheduled | Production Scheduled | → Step 5 |
| 5 | Logistics | INT1337-PKG-Order-Packed | Ready for Transport | → Step 6 |
| 6 | Logistics | INT1337-RCV-Order-Delivered | Order Delivered | → Step 7 |
| 7 | Finance | INT1337-INV-Order-Invoiced | Order Invoiced | (End) |
Key Process Characteristics
- Divergence Point: Step 2 splits into two parallel paths (Confirmation + Planning)
- Convergence Point: Step 4 receives connectors from both Step 2 and Step 3, both labeled "Order Planned"
- Linear Backbone: Steps 1 → 2 → 4 → 5 → 6 → 7 form the main sequence
- Business Events Only: Each cell holds the step's business Service; the forwarder Services log Log Events too, but have no BPM entry
- Arrow Direction: All flow goes left-to-right (SourceAttachmentPoint=3, TargetAttachmentPoint=1)
Next Steps
- Order-to-Cash Demo Overview – Complete guide including Repository Binding and automatic landscape generation
- Generate O2C Demo Data Script – PowerShell script that creates all 14 Services and the BPM visualization
Related Topics
- Integration Landscape – Diagram of all Systems and service connections
- Business Process Model (BPM) – Learn how to use BPMs for process visualization and monitoring
- Repository Binding – Repository Binding configuration that automates landscape creation
- Services – How Services run and integrate across Systems
- Message Types – Standard O2C Message Types (JSON, XML, CSV, PSV)
- Domains – Business Domains used in the BPM swimlanes