Parameter Interconnections and Setpoint Propagation in SIMATIC BATCH Master Recipes

In SIMATIC BATCH, the 'Parameters' tab in master recipe properties defines recipe-level setpoints that link directly to lower-level Recipe Operations (ROP) and Recipe Phases (RPH), mapping to technological SFC type setpoints in the AS. When an SFC type is configured in CFC with 's7_tagcollect', its setpoints (such as Target_Temperature or Dosing_Weight) become available in the BATCH Recipe Editor. Using the 'Source' and 'Destination' parameter interconnection mechanism—indicated by smiley face status icons—engineers propagate parameters upward to the Recipe Procedure (RP) or Header. Setting a parameter as 'Source' in the recipe header allows an operator to enter the setpoint once at batch creation, automatically distributing the value down to multiple equipment phases across the plant.

Executive Summary

In flexible ISA-88 recipe management with SIMATIC BATCH, multi-step chemical and pharmaceutical recipes require consistent process parameters across numerous equipment phases. Manually entering identical setpoints (such as jacket heating temperatures, agitation speeds, or chemical mass targets) in every individual phase is error-prone and violates recipe abstraction principles. SIMATIC BATCH solves this via parameter propagation, linking phase setpoints to high-level master recipe header parameters. This technical guide explains how SFC type setpoints map into the BATCH process model, details the 'Source/Destination' parameter binding mechanics, and explains how to configure global master recipe parameters.

Architecture and Fundamental Mechanics

The parameter architecture of SIMATIC BATCH reflects the hierarchical ISA-88 recipe model:
1. AS-Level Setpoint Definition (SFC Types):
- Setpoints originate in the AS inside SFC types classified as Equipment Phases (EPH) or Equipment Operations (EOP).
- Inputs configured with system attribute s7_tagcollect := 'true' and technological data types (e.g., REAL, DINT) are compiled into the BATCH Type Description.
2. The Recipe Hierarchy Tiers:
- Recipe Phase (RPH): Lowest execution level. Contains direct setpoint inputs to AS blocks.
- Recipe Operation (ROP): Sequences multiple phases within a unit.
- Recipe Unit Procedure (RUP): Manages sequence of operations within an equipment unit.
- Recipe Procedure (RP) / Master Recipe Header: Highest technological level representing the complete process recipe.
3. The Source and Destination Binding Engine:
- Parameters can be transferred between recipe elements using Source/Destination links:
a. Source Parameter: The master value provider. Can be located at the Recipe Header (operator input), a preceding phase (calculated value), or an external formula.
b. Destination Parameter: The consumer. Receives its runtime value dynamically from the assigned source.
- In the BATCH Recipe Editor, successful parameter bindings are visually flagged with green smiley face icons; unbound or broken references display yellow or red warning icons.

Step-by-Step Implementation Procedure

Verify Setpoint Collection in SFC Type:
a. In SIMATIC Manager, open the SFC Type in the SFC Editor.
b. Navigate to Type -> Characteristics -> Setpoints.
c. Confirm the parameter (e.g., SP_Temp) exists, has data type REAL, and has attribute s7_tagcollect enabled.
d. Perform BATCH compilation: Generate Types, Propagate Types, Merge Instances, and Download to Server.
Open Master Recipe in BATCH Recipe Editor:
a. Launch Batch Control Center (BatchCC).
b. In the tree view, navigate to Master Recipes and open the target recipe.
c. In the graphical recipe chart, double-click the Recipe Phase (RPH) that requires the setpoint.
Configure Source/Destination Link in Recipe Phase:
a. In the RPH properties dialog, switch to the Parameters tab.
b. Select the setpoint SP_Temp.
c. Under 'Reference', set the parameter type to Destination.
d. Under 'Source', select the option to create or link to an upstream parameter at the Recipe Operation (ROP) or Recipe Header level.
Define Header Parameter in Master Recipe Properties:
a. In the Recipe Editor main menu, select Recipe -> Properties.
b. Navigate to the Parameters tab.
c. Click 'New' to create a global recipe parameter named Header_Target_Temperature.
d. Set the default value (e.g., 75.0 °C), low limit, and high limit.
Bind Destination Phase to Master Header Parameter:
a. Return to the Recipe Phase parameter properties.
b. In the 'Source Parameter' drop-down list, select Header_Target_Temperature.
c. Observe the icon: confirm the binding displays a green smiley face icon, indicating valid propagation.
Validate and Release Recipe:
a. Execute Recipe -> Check Recipe Consistency.
b. Confirm 0 Errors and 0 Warnings.
c. Select Recipe -> Release for Testing / Production.

Verification

In BatchCC, create a new batch using the released master recipe.
In the Batch Creation wizard, observe the Recipe Header parameter prompt: enter a test value (e.g., 82.5 °C).
Start the batch and monitor the active control recipe: verify that when the designated Recipe Phase starts, its setpoint automatically receives 82.5 °C without operator intervention.

Limitations and Operational Precautions

Parameter data types and engineering units must match exactly between the Recipe Header and the target Recipe Phase. Connecting a REAL setpoint to a DINT destination will cause recipe validation failure.

Engineer FAQ

What does the smiley face icon indicate in the BATCH Recipe Editor?

A green smiley face icon indicates that a parameter has a valid, unbroken Source-to-Destination binding across recipe hierarchy levels.

What is the difference between an SFC type parameter and a recipe parameter?

SFC type parameters are low-level controller inputs; recipe parameters are high-level formulation targets that distribute setpoints to one or more phases.