Building Routes
Flow is the material and information routing layer of a process. While the process hierarchy (Product → Operation → Step → Action) defines what work is done, the flow layer defines how material moves between operations — the sequence, branching, and logistics path that a workpiece follows from start to finish.
Flow Node Types
Flow diagrams are built from 14 node types: terminals (Input, Output), scan & inspection nodes, routing nodes (Decision, Gateway, Merge), container handling (Pack, Extract), and storage/packaging.
For the complete reference of every node type — its ports, bindings, and rules — see Flow Items.
Creating a Flow Diagram
Flow nodes are placed on the canvas from the Flow Items panel. Drag a node type onto the canvas to create it.
Each node has:
- Ports — connection points for incoming and outgoing edges. Ports have a direction (input/output) and a role (flow, condition, merge, trigger, result)
- Comment — localized annotation explaining the node's purpose
- Quality — an item quality level (writeOff, bad, undef, common, normal, good, AAA) that marks the expected quality state at this point
Connecting Nodes
To create a route, connect the output port of one node to the input port of another. The resulting edge represents a physical or logical link:
- Material moves along this edge
- You can specify a time cost for traversal
- You can assign a cost record (accounting code and amount)
- You can mark quality impact (what quality state the material acquires after traversal)
Attaching Flow to Operations
Flow nodes can be attached to operations via the `attachedTo` property. This links the flow routing layer to the process hierarchy — when material reaches a given node, it implies the corresponding operation is being performed.
This binding is what connects the "what work is done" world (process tree) to the "how material flows" world (flow diagram).
Flow Entities
A flow entity represents a single item or batch moving through the flow diagram:
- Label — identifier for tracking
- Payload — carries type, batch size, and processing status (idle, processing, done, error)
- History — records which nodes the entity has visited
- Quality Flags — accumulated quality state from each checkpoint
- Characteristics — accumulated measurement data from scan nodes
Flow entities make it possible to trace the path of a specific workpiece through the entire routing network.
Practical Tips
- Start with Input and Output nodes to define the boundaries
- Place operations in between and connect them with edges
- Use Decision nodes for quality gates (pass → next operation, fail → rework or scrap)
- Use Storage Point to model buffers between operations with different cycle times
- Use Pack/Extract nodes when modelling containerised logistics
- Attach flow nodes to their corresponding operations to maintain the process–flow link