- 3 minutes to read

C4 Examples Overview

Use these examples to learn C4 in Nodinite with a complete Order-to-Cash scenario and import-ready Mermaid diagrams.

The examples are designed to help you build and validate a complete Diagram Set step by step.

  • ✅ Start with realistic Order-to-Cash examples that map to BPM and Repository Model entities.
  • ✅ Learn each C4 perspective with focused examples for System Landscape, Context, Container, Component, Dynamic, and Deployment.
  • ✅ Import quickly with ready links to setup guidance and related features.

Example Catalog

Type Example Description
BPM Order-to-Cash Example Overview Main Order-to-Cash walkthrough with business flow, message samples, and demo data generation.
C4 System Landscape Diagram Example Enterprise-level landscape view for the complete Order-to-Cash environment.
C4 L1 Context Diagram Example High-level system boundary and external actors.
C4 L2 Container Diagram Example Internal structure and container responsibilities for the core system.
C4 L3 Component Diagram Example Detailed implementation components inside a selected container.
C4 Dynamic Diagram Example Runtime interaction flow for a concrete Order-to-Cash path.
C4 Deployment Diagram Example Infrastructure and deployment topology view.

Required Scope Assignments for O2C Imports

Use these scope values when importing the examples to keep a valid C4 chain for one selected architectural branch.

Diagram level Scope to select Purpose in the chain
L1 Context System: Portal Defines the parent system branch for the O2C walkthrough
L2 Container System: Portal Keeps L2 linked to the same L1 branch
L3 Component Service: INT1337-RCV-Order-Incoming Provides the L3 zoom-in under the same O2C branch

This is the canonical single-scope chain for O2C examples. Keep this chain focused on one architectural branch so inferred links and zoom behavior remain predictable.

Important

The O2C PowerShell generator creates the Repository identities used by these examples. Do not rename generated O2C Systems, Services, Integrations, Domains, or message type names during import. Keep those identities and adjust diagram structure or selected scope instead.

If you want additional branches, add sibling diagrams with their own scope values (for example, separate L2 diagrams scoped to ERP, WMS, or ERP-Finance).

Optional Expanded Multi-Scope Pack

If you want a broader, "full landscape" demonstration, add extra diagrams as sibling branches rather than mixing scopes inside the canonical chain:

Additional branch Recommended scope Example intent
ERP branch System: ERP Planning and ERP-centric L2/L3 walkthrough
WMS branch System: WMS Logistics and fulfillment-focused L2/L3 walkthrough
Finance branch System: ERP-Finance Invoicing and finance-focused L2/L3 walkthrough

Keep each branch internally consistent (L1/L2/L3 aligned to that branch scope), and keep generated O2C Repository identities unchanged.

Page Why open it
Creating Your First C4 Diagram Step-by-step import and binding workflow.
Import Supported source formats and import behavior.
What is C4 Diagrams? Conceptual overview and terminology.
BPM Examples Overview Entry point for BPM-focused examples, including Order-to-Cash.

Next Step