Complete Scenarios
End-to-end examples showing how all building blocks come together — from environment setup through process hierarchy to flow routing.
Manual assembly station
Goal — model a workstation that assembles 5 components into one housing.
- Environment: Workplace "WS-12", Equipment "pneumatic screwdriver", Profession "assembler"
- Product: housing assembly, batch size 100
- Operation: "Assembly", bound to WS-12
- Steps:
- "Tool change" (type: Setup) — fixture adjustment
- "Assembly" (type: Main) — 5 Actions, one per component
- "In-process check" (type: Auxiliary) — dimensional verification
- "5S cleanup" (type: Workplace Maintenance) — end-of-shift cleaning
- Actions in the Main step: each contains a "pick-move-install" template with microelements for that component
- Flow: Input → this Operation → FunctionalScan → Decision → next Operation or Rework loop
- Control Plan: 2 characteristics — torque on screws (instrument: torque wrench, ±0.5 Nm) and visual check for scratches
CNC machining with overlap
Goal — model an Operation where the operator loads parts while the CNC runs.
- Step type: Main
- Action "Load": Reach → Grasp part → Move → Install into chuck → Press pedal (clamp). Tags: Production / Physical / Value-adding
- Action "CNC cycle": Machine time element (120 s). Enable overlapped employment — operator time runs in parallel
- Action "Unload": Release chuck → Grasp part → Move to conveyor → Release. This runs during the next CNC cycle
- Result: P = max(operator load+unload, machine cycle) + non-overlapping remainder. Calculated automatically
Incoming goods with scan and storage
Goal — model material receipt through to warehouse shelving.
- Flow: Input → ScanOnReceipt → Decision (accept / quarantine)
- Operation "Receiving": bound to Workplace "Dock 3"
- Step "Unload" (Main) — unload pallets from truck
- Step "Verify" (Auxiliary) — scan bar codes, compare to manifest
- Operation "Put-away": bound to Workplace "Aisle B"
- Step "Transport" (Main) — drive forklift to shelves
- Step "System entry" (Auxiliary) — confirm receipt in WMS
- Environment: Factory → Warehouse → Workplaces "Dock 3" + "Aisle B", Equipment "forklift", Profession "warehouse operator"
Start from the physical reality: what does the worker see, touch, move? Model that first with microelements. Then wrap structure (Actions, Steps, Operations) around the physical work. Finally add Flow and Environment to complete the picture.
Anti-patterns
- Skipping hierarchy levels — do not put microelements directly into a Step; always wrap in an Action first
- Giant Actions — if an Action has more than 15–20 microelements, it likely represents two logical actions; split it
- Template overuse — do not turn every single microelement into a template; templates shine for sequences of 3+ elements that repeat
- Wrong step types — leaving all Steps as "Main" distorts the time structure; setup work and maintenance must use the correct type so P, PR, ST split correctly
- Empty flow nodes — placing ScanOnReceipt or Decision without a real process counterpart creates visual noise; only add nodes that correspond to actual checkpoints
- Environment without bindings — an elaborate environment tree is useless unless Operations are bound to it; bind early, bind consistently
The system is a model of reality. If the model does not match what happens on the shop floor, the calculated times are fiction.