Procedure Best Practices

PreviousNested Steps and Nested Standard Steps NextRuns

Last updated 1 month ago

Was this helpful?

Use Case: Implementing Nested Steps

The purpose of this use case is to show how nested standard steps can be utilized in tandem with the hold status in runs. This combination ensures that high-level builds are executed sequentially and with the most up-to-date information. By placing certain steps on hold, you allow planners to schedule production work even when some process details are not fully defined.

The example provided will reference the diagram below, where the purple bubbles represent each step in the pathway to enabling this use case.

Identify a process where nested standard steps can be helpful

This can be a very high level situation such as final integration, testing, and delivery (as shown above).
Equally this can be a common process performed 10s of times a day such as securing body work which may involve standard steps like torquing, sealing, and inspecting.

Identify the groups of work to be performed.:

Start with a top-level procedure containing multiple standard steps. For example, assume you have four standard procedures within the top-level procedure.

Evaluate Standard Steps:

Evaluate each standard step:
- If standard steps have completed work instructions and are released technicians can start working on those procedures.

Create Placeholder for Incomplete Instructions:

Some procedures may still be undefined and thus you will not want for work to begin on those steps within runs in which the standard step is called out.
Put a placeholder, hold, on the fourth standard step to prevent technicians from starting it prematurely.

Put the Standard Step On Hold:

Navigate to the standard step on the run that needs to be placed on hold and indicate that hold status
This blocks work from beginning until the work instructions are complete and valid for execution

Release Hold When Updated Standard Step is Ready:

Once the work instructions for the held procedure are finalized, release the updated standard step and take the run instance of it off hold.
Technicians can now start working on the procedure now that the instructions are finalized and updated within the run to reflect the latest released standard step.

By integrating nested procedures with the hold feature, you can maintain workflow flexibility while ensuring that all necessary steps are completed in order.

Use Case: Implementing Nested Steps

The example provided will reference the diagram below, where the purple bubbles represent each step in the pathway to enabling this use case.

Identify a process where nested standard steps can be helpful

This can be a very high level situation such as final integration, testing, and delivery (as shown above).
Equally this can be a common process performed 10s of times a day such as securing body work which may involve standard steps like torquing, sealing, and inspecting.

Identify the groups of work to be performed.:

Start with a top-level procedure containing multiple standard steps. For example, assume you have four standard procedures within the top-level procedure.

Evaluate Standard Steps:

Evaluate each standard step:
- If standard steps have completed work instructions and are released technicians can start working on those procedures.

Create Placeholder for Incomplete Instructions:

Some procedures may still be undefined and thus you will not want for work to begin on those steps within runs in which the standard step is called out.
Put a placeholder, hold, on the fourth standard step to prevent technicians from starting it prematurely.

Put the Standard Step On Hold:

Navigate to the standard step on the run that needs to be placed on hold and indicate that hold status
This blocks work from beginning until the work instructions are complete and valid for execution

Release Hold When Updated Standard Step is Ready:

Once the work instructions for the held procedure are finalized, release the updated standard step and take the run instance of it off hold.
Technicians can now start working on the procedure now that the instructions are finalized and updated within the run to reflect the latest released standard step.

By integrating nested procedures with the hold feature, you can maintain workflow flexibility while ensuring that all necessary steps are completed in order.