Skip to main content
An operation is an executable stage of a recipe or manufacturing order. It can have inputs, steps, checks, resources, times and restrictions.

What defines an operation

When it becomes planned

An operation becomes Planned when it has:
  • a workstation;
  • a target date;
  • a selected tool, if the operation requires a tool characteristic.
Material availability is shown separately. It is not part of these minimum planning requirements.

Restrictions

Restrictions link a preceding operation to a following one. Configure separately when the following operation can start and how many units it can record. In a recipe or MO diagram, Recalculate positions orders blocks according to their restrictions. Confirm the dialog to save the new arrangement. You need write permission for recipes or manufacturing orders, respectively; recipe versions must be editable. In the operations table of a recipe or MO, the # column numbers operations according to their restrictions: each one appears after its predecessors. Operations that do not depend on each other are sorted by name, with numbers in numeric order, so “Op 2” comes before “Op 10”. The table opens in this order, and the API returns operations in the same order. If you sort by another column, sort by # to get the sequence back. In an MO diagram, right-click an operation to open it with View details or use the actions its status allows: Start, Pause, Resume, Record progress, Complete (timed waits), or Undo finish. Record progress opens the same record as the operation page. As in work mode, you choose Record without finishing or Record and finish when you confirm. After saving, you return to the screen you opened it from. The start condition stops applying when the following operation starts. A finished or canceled preceding operation stops imposing restrictions. The limit counts good and rejected units recorded in the following operation. Rejected units from the preceding operation do not release units. With several preceding operations, the lowest limit applies. For example, if an operation has 10 sheets planned and the following one has 40 pieces, one good sheet releases 4 pieces. When the preceding operation finishes, it stops limiting quantities even if it completed less than planned.

What happens if it is not met

For the start condition, choose between three options: Warn but allow shows an information indicator and keeps the operation visible when you enable Hide restricted. Hide by default, but allow with a warning shows a warning and lets that filter hide the operation while it has not started. Both require the same confirmation to continue; there is no additional step or required reason. To exceed the available quantity, choose between two options: Quantity limits saved with the old confirmation option use Warn but allow. Bold records which restrictions you bypassed and their enforcement at the time of the action. The backend also applies blocks to API calls that start or record units in an individual operation. Group actions are exempt from these restrictions in both management and work mode. The indicator shows whether you can continue, units are missing or conditions remain pending. In Information, you can review each condition and open the preceding operation to check whether progress still needs recording. The shortcut to the preceding operation only appears while work mode lists it: unblocked and planned, in progress, paused, or finished less than 12 hours ago. If an operation started before its start condition was met, the condition shows as unmet even after the preceding operation finishes. It names the milestone that was not awaited, including with Warn but allow. When the preceding operation has progressed, Bold only detects that its first units were not awaited if it started later than the following operation. The Hide restricted filter hides only operations that have not started and have pending start conditions of type Hide by default, but allow with a warning or Hide and forbid. It also hides operations that exceed a quantity limit configured as Forbid. Operations that have already started remain visible.

Early preparation and waits

To prepare an operation while the preceding one produces, choose to start when the preceding operation has started. Decide whether to receive units as they are completed or the entire lot at the end. A timed wait does not offer At any time. Automatic start respects all its start conditions, including those configured as Warn but allow. If it starts before its preceding operations end, it does not complete automatically until its duration has elapsed and all preceding operations have closed. If you pause a timed wait or undo its completion, it stays paused until you resume it manually. Paused time extends its duration before automatic completion. With write permission on manufacturing orders, you can bring a wait forward from work mode: Start starts it without waiting for the automatic start, and Complete finishes it before its duration elapses and marks its pending units as completed. You can also complete it from the operation page or from the context menu of the MO diagram. Without that permission, you cannot start, record progress on, or finish a wait manually, including through the API; work mode does not show these actions. A wait consumes no materials, produces no co-products and has no controls, so Bold does not show those sections on its operations or on recipe operations. Sequencing follows conditions regardless of enforcement. Precedence configured as Warn but allow can also order the plan. Restrictions should not be duplicated or create cycles. A cycle would prevent determining which operation unlocks another and can block sequencing.

Continuity

Continuity keeps the same resource across several operations of one manufacturing order. It is defined with a text key, such as M1 or U1: operations with the same key form a group. Keys are defined on the recipe’s operations and passed to the orders created from it. You can also change them on an order’s operations. The same key in two different orders does not link them, and keys ignore upper and lower case. You can set a key from the operation’s page or, on the diagram, by clicking several operations while holding Shift or Ctrl, which outlines them in blue, and choosing Continuity… in the context menu of one of them. Operations with continuity show a label in their key’s color. Hovering over it, or over the diagram’s Continuity panel, highlights the operations of the group. If your company has lines, an MO diagram lets you choose the Color of its operations: Status, as always, or Line. With Line, the right border of each operation takes the color of its workstation’s line, gray when it is in none, and a legend shows the lines of the MO. When you change the workstation or the tool of an operation with continuity, Bold also changes the other operations of the group that have not started, and shows you which ones before you confirm:
  • With workstation continuity, they all move to the new workstation.
  • With line continuity, if the new workstation is in another line, each operation moves to its workstation in that line. A change within the same line only affects that operation.
  • With tool continuity, they all use the new tool.
Started, finished, or cancelled operations never move. If one of them is already on another resource, or an operation of the group cannot use the new one, Bold does not make the change. To move an operation on its own, for example after a breakdown, remove its key. Without a key, a change of workstation or tool only affects that operation. On the order, the Continuity panel marks as Broken a continuity whose operations do not share the same resource. When an order is created from a recipe, each group gets a common resource, following the Workstation of new operations rule of the process of its first operation:
  • A workstation continuity gets one workstation that all its operations can use.
  • A line continuity gets one line where each operation has a workstation, and each one then takes its workstation in that line. With the least pending work rule, successive units of the order go to the least loaded line.
  • A tool continuity gets a tool only when exactly one tool can be used by all its operations.
If no resource is common to the whole group, each operation is assigned on its own and the panel shows the continuity as Broken. Production plans also keep each group on a common resource.

Final operation

The final operation is usually the one without outgoing restrictions. Bold can use it to derive the order’s completed, rejected and pending quantities. Define the final operation carefully when there are parallel branches, co-products or final checks.

Operation statuses

Read Manufacturing statuses to compare operations with orders, groups and plans.

Undo completion

You can use Undo finish on a finished operation. You must specify a pause reason. Bold reopens the operation and creates an interruption from its completion date. Consumption already recorded is not removed. Review it before continuing if the earlier completion generated records that no longer apply.

Granularity

Choose the level at which you need to measure progress, consumption, quality or responsibility.