Operation Binding
Operation binding connects the process hierarchy to the environment — it answers "this operation is performed at this workplace, by this profession." Without binding, operations exist in an abstract space; with binding, they are anchored to specific physical and organisational contexts.
How Binding Works
Each operation has an `envBindings` property — a map from domain ID to a binding object:
- Domain — a Holding or a Company
- Workplace — the specific workstation within that domain
- Profession — the professional role required to perform the operation
An operation can be bound to multiple domains, meaning it can be performed at different workplaces depending on production scheduling.
Setting Up Bindings
Step 1 — Create Environment Elements
Place the required Workplace, Equipment, and Profession elements on the canvas, inside the Company (or Holding) they belong to.
Step 2 — Open Operation Properties
Select the operation on the canvas. Open the properties panel.
Step 3 — Add Domain Binding
In the environment bindings section, select the domain (the Company) and assign:
- The workplace within that domain
- The profession required
Step 4 — Verify
The operation now shows its binding in the properties panel. The environment element also reflects that it hosts this operation.
Operation Parameters Affecting Binding
Several operation-level parameters interact with equipment and personnel binding:
Batch Configuration
- Minimum Batch Size — the smallest number of units that justifies starting the operation. Affects setup time distribution.
- Processing Capacity — how many units can be processed simultaneously in one cycle. A multi-station fixture might have capacity = 4.
Personnel Requirements
- Minimum Operators Required — the fewest operators needed to run the operation
- Maximum Effective Operators — adding more operators beyond this number provides no benefit
- Operator Presence Required — whether the operator must be present during the entire cycle (relevant for automated equipment)
- Operator Handover Allowed — whether a different operator can take over mid-cycle (relevant for shift changes)
Cycle Constraints
- Non-Interruptible Cycle — the operation cannot be paused once started (e.g. heat treatment, chemical processes)
- Shift Carryover Allowed — whether the operation can continue across a shift boundary
Why Binding Matters
Capacity Planning
When an operation is bound to a workplace, you know which workstations are required. Combined with cycle time (P) and batch size, this enables capacity calculation — how many workstations are needed to meet a production target.
Staffing Analysis
Binding operations to professions creates a staffing requirements map. Aggregating across all operations reveals the total headcount by trade and grade.
Layout Optimisation
Operations bound to workplaces anchored in areas and production lines create a spatial model. The flow diagram shows material movement between these locations, enabling transport time analysis and layout improvement.
Cost Modelling
With resources (equipment cost, depreciation, labour rates) attached and operations bound to specific environments, the model supports cost per unit calculation:
- Labour cost from staff grade and salary
- Equipment cost from depreciation rate
- Material cost from component quantities and prices
Multi-Domain Operations
A single operation can exist in multiple domain bindings. This models real-world flexibility:
- The same turning operation can be performed at Workplace A (3-axis lathe) or Workplace B (5-axis CNC) — different equipment, potentially different cycle times
- During capacity overload, work is redistributed to an alternative workplace
- Different shifts may use different workstations for the same operation
Each domain binding is independent — the workplace and profession can differ per domain.