Skip to main content

Operations

Operations page

An operation is an ordered set of phases that accomplishes a specific task within a unit procedure. Operations represent the major steps in a process, such as "Heat and Mix", "Prepare Ingredients", or "Clean In Place".

Operations sit at the third level of the ISA-88 procedure hierarchy:

Page layout​

The Operations page (Admin > Procedures > Operations) displays:

  • Dashboard cards: total, active, and inactive operation counts
  • Filter bar: search, inactive toggle, column visibility controls
  • Data grid: all operations with their phase counts and inline actions

Operation fields​

FieldRequiredDescription
NameYesDisplay name (max 255 characters)
CodeYesUnique short identifier (max 50 characters), e.g., HEAT_MIX, CIP_RINSE
DescriptionNoLonger explanation of what the operation accomplishes (max 1000 characters)
ActiveYesWhether the operation is available for use in unit procedures

Creating an Operation​

  1. Click Add Operation above the data grid
  2. Enter the Name and Code (both required)
  3. Optionally add a description
  4. Click Create

Create operation dialog

Managing phases within an operation​

The core purpose of an operation is to arrange phases in a specific sequence. Click the list icon on an operation row to open the Manage Phases dialog.

Manage phases dialog

Adding a Phase​

  1. Select a phase from the dropdown (only active phases not already linked are shown)
  2. Optionally toggle the Optional switch if the phase is not mandatory
  3. Click Add

The phase is appended at the end of the sequence with the next available sequence number.

Reordering phases​

Use the up arrow and down arrow buttons on each phase row to change its position in the sequence. The sequence order determines the execution order of phases within the operation.

Removing a Phase​

Click the red trash icon on a phase row to remove it from the operation. This does not delete the phase itself; it only removes the link.

Optional Phases​

Toggle the switch on a phase row to mark it as optional or required. Optional phases may be skipped during execution depending on the recipe or production order configuration.

:::tip Reusable phases The same phase can be used in multiple operations. For example, a "Rinse" phase might appear in both "Pre-Clean" and "Post-Clean" operations. Each operation maintains its own sequence order independently. :::

Editing an Operation​

Click the edit button (blue pencil icon) on any operation row. Update the name, code, description, or active status and click Update.

Deleting an Operation​

Click the delete button (red trash icon). A confirmation dialog appears. Deleting will fail if the operation is still linked to any unit procedures.

:::info Prefer deactivation over deletion If an operation is no longer needed but has historical references, set it to inactive instead of deleting it. Inactive operations are preserved in the system but hidden from selection dropdowns. :::

Grid Columns​

ColumnDescription
NameOperation display name (bold text)
CodeUnique code shown as a chip
DescriptionOptional description text
PhasesCount of linked phases (chip)
StatusActive/Inactive chip
ActionsManage Phases, Edit, Delete buttons

The Created At and Updated At columns are available in full-column mode.

Phase Sequence Example​

Here is an example of the "Heat and Mix" operation with its phase sequence:

#PhaseCodeOptional
1Set TemperatureHEATNo
2AgitateMIXNo
3HoldHOLDYes

The sequence order (1, 2, 3) defines the execution order. Phase #3 (Hold) is marked as optional, meaning it can be skipped in certain recipe configurations.

Best Practices​

  1. Name operations by purpose: use names that describe the goal (e.g., "Heat and Mix") rather than the mechanism (e.g., "Step 3").
  2. Keep operations focused: each operation should accomplish one meaningful task. If an operation has more than 6-8 phases, consider splitting it.
  3. Use optional phases sparingly: optional phases add flexibility but also complexity. Only mark a phase as optional if it genuinely varies between product runs.
  4. Use descriptive codes: codes like HEAT_MIX, CIP_RINSE, FILL are easier to work with than OP001, OP002.

Prerequisites​

Next steps​