SIMATIC BATCH V9.0 Hierarchical Recipe Editor: Resolving Equipment Phase (EPH) Visibility When Inserting Recipe Operations (ROP)

In SIMATIC BATCH V9.0, an Equipment Phase (EPH) configured as an SFC Type does not appear directly when inserting a Recipe Operation (ROP) because the ISA-88 recipe model enforces a strict hierarchical nesting: Procedure -> Recipe Unit Procedure (RUP) -> Recipe Operation (ROP) -> Recipe Phase (RPH/EPH). A Recipe Operation is a container structure, not an executable phase. To select your EPH, open the ROP container and insert a Recipe Procedural Element (RPE) or Recipe Phase inside the ROP. Within the nested operation level, the Recipe Editor evaluates the allocated Unit's candidate equipment modules and exposes all compiled EPH phase instances.

ISA-88 Hierarchical Recipe Model in SIMATIC BATCH V9.0

SIMATIC BATCH adheres strictly to the ANSI/ISA-88.01 (IEC 61512-1) standard for batch control systems. Under the ISA-88 procedural control model, recipes are organized in a four-tier hierarchy: Recipe Procedure (RP) at the top, subdivided into Recipe Unit Procedures (RUP), which are composed of sequential Recipe Operations (ROP), which in turn contain individual Recipe Phases (RPH).

In SIMATIC PCS 7, physical plant equipment is mapped directly into this hierarchy via the Plant Hierarchy (PH). When using AS-based recipes with Sequential Function Chart (SFC) Types, an SFC Type declared for SIMATIC BATCH represents an Equipment Phase (EPH). A common point of confusion for recipe authors in Batch Control Center (BCC) is attempting to bind an EPH directly to an ROP container.

Why Equipment Phases Cannot Be Selected at the Top-Level ROP Node

When an author creates a hierarchical recipe in the SIMATIC BATCH Recipe Editor, allocates a Unit (e.g. Reactor_01), and inserts a new Recipe Procedural Element (RPE), the editor initially labels the placeholder as a NOP (No Operation) or standard ROP:

The Container Concept: An ROP represents a major technological operation (such as 'Dosing', 'Heating', or 'Reaction'). An operation does not directly stroke valves or start motors; it coordinates a sequence of individual phases.
The Selection Dropdown Filter: At the ROP level, the Recipe Editor dropdown only offers structural choices (such as 'NOP' or 'Unit parameters'). It intentionally conceals all Equipment Phases because binding a physical phase directly to an operation node violates ISA-88 hierarchy rules. Authors assume their SFC Types failed to compile into BATCH, when in reality they are querying the wrong hierarchical level.

Nesting Recipe Procedural Elements (RPE) Inside Recipe Operations

To access and parameterize compiled Equipment Phases (EPHs):

Open the ROP Container: Double-click the ROP element in the graphical recipe topology, or navigate into its child sequencer window.
Insert Child Recipe Element: Inside the operation canvas, insert a Recipe Phase (or Recipe Procedural Element).
Automatic Technological Filtering: At this child tier, the Recipe Editor queries the active Unit's equipment properties. It identifies all SFC Type instances declared under the Unit's subordinate Equipment Module (EMOD) hierarchy folders and displays the EPHs in the drop-down list.
Control Strategy Selection: Once the EPH is selected, the author can select the specific Control Strategy (CS) (e.g. 'Fill Slow' vs 'Fill Fast') and assign recipe setpoints.

Plant Hierarchy Alignment: Process Cell, Unit, and Equipment Module (EMOD)

For EPH phases to appear inside the Recipe Editor, the underlying STEP 7 project must adhere to strict technological hierarchy rules:

Process Cell Level: The root hierarchy folder must have the property 'Process Cell' enabled.
Unit Level: The unit folder must contain the block UNIT_PLC (FB266) from the SIMATIC BATCH library and have the property 'Unit' checked.
Equipment Module Level: Subordinate folders must contain the SFC Type instances with the attribute 'SIMATIC BATCH' activated.
Batch Configuration Dialog (BFCONCFG): Before opening BCC, execute Propagate, Generate, Merge, and Download in the BATCH configuration dialog, followed by Process Cell -> Update in Batch Control Center.

Comparative Structure Matrix: ISA-88 Recipe Elements in SIMATIC BATCH

The following table compares the roles and properties of hierarchical recipe elements in SIMATIC BATCH V9.0:

Recipe Hierarchy LevelISA-88 DesignationTechnological Binding in PCS 7Assignable ParametersRecipe Procedure (RP)Complete RecipeProcess Cell ContainerGlobal recipe header; batch sizeRecipe Unit Procedure (RUP)Unit RecipeTechnological Unit (UNIT_PLC)Unit allocation; equipment selectionRecipe Operation (ROP)Process OperationOperation ContainerOperation sequence logic; step timingRecipe Phase (RPH / EPH)Equipment PhaseSFC Type instance in EMODControl Strategies (CS); setpoints (SP)No Operation (NOP)PlaceholderEmpty sequence nodeUnassigned placeholder element

Step-by-Step Procedure to Insert and Parameterize an EPH in BCC

Follow this sequence to build a valid hierarchical recipe in Batch Control Center:

Open Batch Control Center (BCC) and select Recipes -> Master Recipes.
Create a new Master Recipe; specify product code and nominal batch size.
In the recipe topology canvas, insert a Recipe Unit Procedure (RUP). Right-click the RUP and assign your target Unit (e.g. Reactor_01).
Inside the RUP, insert a Recipe Operation (ROP).
Double-click the ROP to open its internal operational flow.
In the ROP canvas, insert a Recipe Phase (RPH).
Open the properties of the RPH; in the Phase drop-down list, select your compiled Equipment Phase (EPH).
Select the required Control Strategy, input recipe setpoints, and click Validate Recipe to confirm 0 structural errors.

Verification

Verify correct EPH resolution and recipe validation:

In the Recipe Editor, click the Validate button (checkmark icon); confirm that the recipe status displays 'Valid'.
Release the Master Recipe for production (Status -> Released).
In BCC, create a test Batch Order from this master recipe and release it to the active batch list.
Start the batch in S7-PLCSIM or physical AS; verify that when the sequencer reaches the ROP, the child EPH activates, sets the correct Control Strategy on the SFC Type in CFC, and executes to completion.

Limitations and Operational Precautions

Adhere to the following operational precautions:

Unit Allocation Enforcement: If an RUP is not allocated to a Unit, the child ROP cannot evaluate equipment candidates and will not display any EPH phases.
Batch Process Cell Update Mandatory: If SFC Types are added or modified in CFC, always perform Process Cell -> Update in BCC; otherwise, new EPH instances remain invisible in the Recipe Editor.
AS-Based vs PC-Based Recipes: AS-based recipes require SFC Types running inside the controller; ensure the SFC Type compiler setting is set to 'AS-based' in the Batch Configuration Dialog.

Engineer FAQ

What is the difference between a Recipe Operation (ROP) and a Recipe Phase (RPH)?

An ROP is a high-level operational container (e.g. Dosing), whereas an RPH is the individual executable phase (e.g. Fill Valve Open) mapped directly to an SFC Type in the controller.

Can an Equipment Phase belong to multiple Units in SIMATIC BATCH?

Under ISA-88, an Equipment Module belongs to a single Unit. If multiple units share equipment (e.g. a shared dosing pump), use Common Units or BATCH Allocation Elements.

Why did a phase show up when no unit was selected, but disappeared when a unit was assigned?

Because unallocated phases are treated as generic phase types; once a Unit is assigned, BATCH strictly filters phases to match only the EMODs physically located within that specific Unit.