Flow Items
Overview
Flow items are visual components on the MPTS canvas that describe the logistical and manufacturing route of a product. They form a directed graph — from start to finish — enabling modeling of movement, inspection, packaging, branching, and storage of objects in a real manufacturing process.
Each flow item is a node. Nodes are connected by edges through connection points. Flow items are bound to process hierarchy elements (Product → Operation → Step → Action), linking the logistics model to labor time standards.
Flow Node Types
1. Start
- Purpose: Entry point of the flow. Defines where objects enter the system.
- Connection: one output.
- Binding: to Product.
- Rule: every flow should have at least one Start node. Typically positioned above the Product element.
2. End
- Purpose: Exit point of the flow. Objects leave the system.
- Connection: one input.
- Binding: implicitly associated with Product.
- Rule: every flow should have at least one End node.
3. Scan On Receipt (Scan In)
- Purpose: Scanning an object upon receipt. Records the arrival of an object at the site.
- Connection: one input and one output.
- Binding: to Action or Template.
- Rule: used when an object first enters the tracking perimeter.
4. Scan Point (Scan)
- Purpose: A checkpoint scan. Records that an object has passed through a specific stage.
- Connection: one input and one output.
- Binding: to Product, Operation, or Step.
- Rule: universal pass-through control element.
5. Intake Scan
- Purpose: Intake scanning — one or more objects are added to the main flow item.
- Connection: one input and one output.
- Binding: to Action or Template.
- Behavior: defines which objects to include and under what condition.
6. Functional Scan
- Purpose: Scanning tied to control parameters (CP). Activates inspection or repackaging.
- Connection: one input and one output.
- Binding: to Operation.
- Behavior: links to control parameters; can activate CP checks and trigger repackaging.
7. Gateway
- Purpose: Branching the flow into multiple paths based on conditions.
- Connection: one input; multiple conditional outputs (e.g. OK / Fail).
- Binding: not bound directly.
- Rule: each output has its own condition. The object follows one of the paths.
8. Merge
- Purpose: Merging multiple paths back into one.
- Connection: two inputs; one output.
- Binding: not bound directly.
- Rule: all incoming paths must be valid. The merged flow continues through the single output.
9. Decision
- Purpose: Branching the flow based on a decision table using control parameters.
- Connection: one input; multiple conditional outputs.
- Binding: to Action.
- Behavior: a set of rules determines which output the object is directed to.
10. Extract From Container (Unpack)
- Purpose: Extracting object(s) from a container.
- Connection: one input and one output.
- Binding: to Action or Template.
- Behavior: specifies the container and objects to extract; can process each individually.
11. Pack Into Container (Pack In)
- Purpose: Packing object(s) into a container.
- Connection: one input and one output.
- Binding: to Action or Template.
- Behavior: specifies the target container and which objects to pack.
12. Storage Point
- Purpose: Intermediate or final storage of an object.
- Connection: one input. No output — the object stays.
- Binding: not bound directly.
- Behavior:
- Limited or unlimited capacity
- Extraction order: stack (LIFO), queue (FIFO), or batch
- Accepts individual units and/or containers
- Optional maximum storage duration
Connections
Ports
Each node has ports — connection points for input and output. Ports define the direction (input or output) and the semantic role of the connection (flow, condition, merge, trigger, or result).
Edges
An edge connects an output port of one node to an input port of another. Edges may carry transition conditions (for Gateway and Decision nodes) and additional parameters such as time cost, cost record, quality impact, or characteristic impact.
An edge can only be created from an output port to an input port.
Binding to Process Elements
Flow items are bound to elements in the process hierarchy. Each node type has specific allowed bindings:
| Node Type | Allowed Bindings |
|---|---|
| Start | Product |
| Scan On Receipt | Action, Template |
| Scan Point | Product, Operation, Step |
| Functional Scan | Operation |
| Extract From Container | Action, Template |
| Pack Into Container | Action, Template |
| Decision | Action |
| End, Gateway, Merge, Storage Point | Not bound |
When bound, a decorative dashed connection line appears between the flow element and the process element. The connection line can be toggled between straight and right-angle routing styles.
Elements bound to a cloned process element become read-only: dragging, binding changes, and edge deletion are blocked.
Working with Flow Elements
Creating a Node
Drag an icon from the Flow Elements panel onto the canvas. The node is immediately ready for connecting and binding.
Deleting a Node
Shift + click on a node to delete it along with all connected edges.
Deletion is blocked for nodes attached to cloned process elements.
Connecting Nodes
- Switch canvas mode to Connect.
- Press and hold on the source node → drag to the target node → release.
- A preview line appears during the drag.
- On release, an edge is created with markers (dot at start, arrow at end).
Inserting a Node into an Edge
Drag a free node over an existing edge. The original edge is split into two new edges — one from the original source to the inserted node, and one from the inserted node to the original target.
Binding to a Process Element
When you drop a flow node onto a process element, binding is performed automatically if the target is valid. The node moves visually inside the process element.
Detaching from a Process Element
Detaching moves the node back to the canvas, preserving its position.
Flow Entities
Flow elements operate on entities — abstract objects passing through the route. Each entity carries:
- A unique identifier and label
- Payload: type, batch size, current step, status, operator, timestamp
- Node passage history
- Accumulated time and costs
- Quality flags (write-off, defective, normal, good, etc.)
- Arbitrary characteristics
Validation
The built-in validator checks:
- Errors: structural graph violations.
- Warnings:
- A node is not connected to any edge (except Start and End).
- Missing Start node.
- Missing End node.
Rules Summary
- Nodes are created by dragging from the panel.
- Connections — only in Connect mode: from output port to input port.
- Binding — only to allowed process element types (see table above).
- Cloned elements — read-only: dragging, binding, and edge deletion are blocked.
- Undo/Redo — full support for all operations.