Skip to main content
A process describes a type of production work, such as cutting, assembly, welding, painting, inspection or packaging. Use processes to connect operations to stations capable of executing them. The process is not the actual work. Actual work appears as an operation in a recipe or order.

​
Key differences

Example: Cutting can be a process. The Cut board operation uses that process within a recipe and can run on Saw 1 or Saw 2.

​
Station compatibility

Each process can relate to one or more stations. That relationship lets you plan operations on compatible resources. There should be only one primary station per process. If several stations do the same work, configure the others as auxiliary.

​
Personnel attendance

Configure Staff attendance for each process-station combination. An attended operation requires personnel presence; an unattended operation lets the machine work on its own. When you change this setting, Bold automatically updates the execution mode and planned labor of operations that use that process and station and have not yet started. It also updates operations in groups that have not started. Started or canceled operations retain their execution mode. Waiting processes use timed wait mode; personnel attendance does not determine their execution mode.

​
Relationship with skills

Employee skills are also based on processes. If an employee has the Cutting skill, work mode can use it to show cutting operations relevant to that person. The skill does not replace station compatibility. An operation still needs consistent stations, resources and restrictions for execution.

​
Granularity

Define processes at the level your team uses to plan, measure and analyze.