Start a recipe at any specific point with active step changes (ASC)
Use the following procedure to start at any point in the recipe. You must accommodate recipe logic where parallel PFC branches exist.
When changing the active step to a part of the recipe that has not yet become active (an operation or phase in a non-active unit procedure, for example) you have to activate the higher recipe level first and then drill into the new active step and perform active step changes from there, down to the recipe level you want to run. In effect, you are performing multiple active step changes (without starting the steps) until you reach the final step you want to run.
Important Considerations
- When performing an active step change, you cannot have any two steps active at the same time that wouldn’t be active during the normal course of the recipe.
- The logged in user must have the Batch_Active_Step_Change key.
- The step you are performing the active step change from must be in a terminal state; that is, Complete, Stopped, Aborted, Stopped_NC, or Aborted_NC. If it is not, the execution of the ASC will issue a STOP to any steps marked as Deactivate.
- The parent steps of the one you are changing from must be in one of the following states: Held, Running or Ready.
- The active step change cannot be performed if the batch or the parent step is in a terminal state (Complete, Stopped, Aborted). However, the operator can reset the batch into the Ready state if the batch is in a terminal state (and the operator has the appropriate key)
To activate a step in a part of the recipe that is not yet active, follow these steps:

