Process Item Recipes
How to structure the process hierarchy — Product, Operation, Step, Action — with the right properties and tags for accurate time modelling.
Product — single-variant assembly
Create a Product with part number, version, and physical properties (weight, dimensions). Attach an opening Operation for incoming materials and a closing Operation for final inspection.
- Set minimum batch size to control how PR (preparing) time is amortised
- Set processing capacity to reflect how many units a single setup produces
Operation — workstation-bound stage
Each Operation maps to a distinct workstation or logical stage. Add Environment bindings — Workplace for the station, Profession for the required skill, Equipment for machines.
- Use the operating code (4–8 digit) to match your company's routing system
- Set batch parameters and staffing limits for capacity planning
- Attach a Control Plan if the operation includes quality checkpoints — see Control Plan for details
Step — choosing the right type
The step type determines its time group. Choose carefully:
- Main or Auxiliary → contribute to cycle time (P per unit)
- Organizational, Workplace Maintenance, Preparing, Rest & Personal Needs → contribute to shift fund (PR per shift)
- Setup, Technological Needs, Equipment Maintenance → contribute to first-start (ST per batch)
Rule of thumb: repeats every unit → Main/Auxiliary. Repeats every shift → Preparing group. Happens only at batch start → Setup group. See Step Types for the full list.
Action — tag strategy
Purpose, Medium, Flow — three classification axes that do not affect time:
- Purpose — pick the primary intent. "Production" for value-adding assembly. "Delivery" for logistics. "Inspection" for quality checks. "Idle" for unavoidable waits.
- Medium — most assembly is "Physical". Data entry is "Digital". Decision-making is "Cognitive".
- Flow — Value-adding if the customer would pay for it. Supporting if necessary but not directly adding value. Waste for anything that should be eliminated.
A well-tagged process illuminates lean waste. Filter Actions by Flow = Waste to see what can be eliminated. See Lean Tags for the lean analysis workflow.