Flow & Environment Recipes
Practical patterns for building logistics routes and structuring the organisational environment around your process.
Simple linear route
Input โ Operations in sequence โ Output. No decisions, no branches. Connect each Operation's output to the next. Example: raw material โ machining โ deburring โ painting โ final inspection โ shipping.
Quality gate with rejection loop
- After a processing Operation, place a Decision node
- Route "pass" to the next Operation
- Route "fail" to a Rework Operation, then loop back to the Decision
- For scrap cases, branch from Decision to Output marked as waste
Incoming inspection
Input โ ScanOnReceipt โ Decision (accept / reject) โ accepted material enters the first Operation. Use ScanOnReceipt at every receiving dock to model bar-code or RFID verification.
Parallel processing with merge
Use Gateway to fork the flow into parallel branches โ e.g., two sub-assemblies built simultaneously. After both complete, add a Merge node to synchronise before continuing.
Packaging and dispatch
Operations complete โ FunctionalScan โ PackIntoContainer โ StoragePoint โ Output
This models: functional check โ consolidation into shipping containers โ warehouse staging โ dispatch.
Flow items do not carry time โ they define the logical route between Operations. Time lives in the process hierarchy. For the full node catalogue see Flow Items. For branching rules see Branching Logic.
Small workshop environment
- Company โ one Factory
- Factory โ one Production area
- Production โ 4โ6 Workplaces
- Each Workplace โ bound to Operations via env bindings
- Staff elements โ individual workers or crews
- Equipment elements โ machines at each Workplace
- Profession elements โ required qualifications (CNC operator, assembler, inspector)
Multi-site enterprise
- Holding โ parent group
- Company A โ domestic manufacturer โ Factory (Production lines, Warehouse, R&D)
- Company B โ international subsidiary โ Factory, Sales, Logistics
- Company C โ engineering office โ Office, R&D
Binding Operations to resources
Each Operation can reference environment elements via bindings:
- Workplace โ physical location where the Operation runs
- Profession โ skill requirement for the operator
- Equipment โ tools and machines needed
These bindings drive the Passport report โ they answer "where is this done, by whom, with what?"
Build the environment tree first, before filling process details. It provides the domain context that makes Operation bindings meaningful. See Environment Structure for the full hierarchy and Resources for resource details.