Displaying Process Values at Batch Phase Completion in SIMATIC BATCH Reports

In SIMATIC BATCH, displaying the final process value at phase completion in a batch report—without showing it as an editable setpoint in the recipe—is accomplished by parameterizing the value as a 'Process Value' or 'Measured Value' rather than a 'Setpoint' in the SFC Type interface. When an engineer erroneously configures an analog value as a Setpoint (SP) and links the actual value to AI, SIMATIC BATCH treats it as a recipe setpoint and prints both 'Actual setpoint' and 'Process value' columns. By defining the parameter under category 'Process Value' (actual value) on the SFC Type and latching the final reading in the SFC 'COMPLETING' step action, the parameter remains hidden from recipe authoring while printing cleanly in the batch report.

Parameter Categorization in SFC Types and SIMATIC BATCH

In SIMATIC PCS 7 batch automation, data transfer between controller execution logic and supervisory electronic batch records is governed by the interface definition of the SFC Type. The SFC Type characteristics editor allows engineers to declare technological parameters across distinct functional categories:

Parameter CategoryDirectionAppearance in Recipe EditorRecording in Batch ReportTypical ApplicationSetpoint (SP)BATCH -> ASVisible & EditableTarget Setpoint & Actual SetpointRecipe target (e.g. Target Temp: 85.0 °C)Process Value (PV)AS -> BATCHHidden from RecipeActual Process Value ColumnLive measurement (e.g. Reactor Temp)Archive Value (PI)AS -> BATCHHidden from RecipeCyclically Archived Trend CurveHistorical continuous process curve

When an engineer wants to report a final reading (e.g., end-of-phase pH or final temperature) without permitting operators or recipe authors to treat that value as an input target, the parameter must strictly be declared as a Process Value.

Why the Setpoint (SP) Approach Clutters Recipe Parameters

A common engineering workaround is to define a Setpoint parameter on the SFC Type and interconnect the field transmitter's analog input to the setpoint's accompanying _AI (Actual Input) terminal. While this successfully routes the number into the SIMATIC BATCH database, it introduces severe operational drawbacks:

Unwanted Recipe Parameters: The variable appears in the BATCH Recipe Editor as an editable parameter field for that phase. Technologists writing master recipes are confused by having to enter a setpoint for a measured output variable.
Cluttered Report Format: In the generated electronic batch report, SIMATIC BATCH prints a redundant comparison table listing 'Target Setpoint', 'Actual Setpoint', and 'Deviation', which is meaningless for passive sensor measurements.
Compliance Ambiguity: In validated pharmaceutical facilities (FDA 21 CFR Part 11), displaying unneeded setpoint fields creates validation review findings regarding unverified recipe entries.

Step-by-Step Configuration Workflow for Latching Phase End Values

To report a single, clean final process value at phase completion without recipe clutter, execute the following workflow:

Define Process Value in SFC Type Interface:
- In SIMATIC Manager, open the Master Data Library and open the target SFC Type.
- Navigate to the Characteristics tab and select Inputs/Outputs or Process Values.
- Insert a new parameter named End_Temperature of data type REAL.
- Set its attribute category strictly to Process Value (Output from AS to BATCH).
Implement Latching Logic in SFC Steps:
- In the SFC Type sequence editor, locate the COMPLETING step (the state immediately prior to phase completion).
- In the Step Actions tab, insert an assignment instruction:
text End_Temperature := Live_Temperature_Input;
- This locks the instantaneous process reading at the exact moment the phase finishes processing.
Compile SFC Type and Update Multiproject:
- In the SFC editor, select SFC -> Compile.
- In SIMATIC Manager, update block types across the multiproject (Options -> Charts -> Update Block Types).
Recompile SIMATIC BATCH:
- In SIMATIC Manager, select Options -> SIMATIC BATCH -> Compile / Download.
- BATCH imports the updated SFC Type interface, noting End_Temperature as a reporting process value.
Configure BATCH Report Template:
- Open BATCH Control Center -> Report Template Designer.
- In the Phase Execution summary table, add the column for End_Temperature. The report will print exclusively the captured process value without setpoint columns.

Verification

Verify process value recording and report presentation through these testing steps:

Recipe Parameter Check: Open the Master Recipe in BATCH Recipe Editor. Inspect the phase properties; confirm that End_Temperature does NOT appear in the list of recipe parameters.
Execute Test Batch: Start a test batch in BATCH Control Center. During phase execution, vary the simulated temperature. Allow the phase to reach COMPLETED.
Generate Batch Report: In BCC, generate the Batch Report (PDF). Inspect the Phase Summary section. Confirm that End_Temperature prints with its exact captured value (e.g. 84.7 °C) with zero setpoint columns.

Limitations and Operational Precautions

When designing batch reporting interfaces, adhere to these technical precautions:

Latching State Selection: Always latch the value in COMPLETING or HOLDING step actions; reading continuous values in the COMPLETED state can cause timing jitter if the phase transitions into IDLE before the BATCH server reads the buffer.
Batch Report Template Versioning: When modifying report templates in Crystal Reports or Advanced Report Designer, maintain strict document version control to preserve validated formatting.
Data Type Formatting: Ensure units of measurement (°C, kg, bar) are defined in the SFC Type characteristics so that SIMATIC BATCH formats the report with correct engineering units.

Engineer FAQ

Why can I not just make the setpoint invisible in the recipe?

Hiding a setpoint parameter in the recipe editor is possible via user authorizations, but SIMATIC BATCH still prints the setpoint column in standard reports. Declaring it as a Process Value is the only method to eliminate setpoint headers completely.

Can I record multiple process values at the end of a single phase?

Yes. You can declare multiple Process Value parameters (e.g. End_Temp, End_Pressure, End_Agitator_Speed) on a single SFC Type.

Does a Process Value consume an OS tag license?

Process Values transferred to SIMATIC BATCH are communicated via internal BATCH communication channels and do not consume additional WinCC Tag Logging archive tags.