Controlling BatchCC Recipe Start Execution and Verifying SFC Preconditions in SIMATIC BATCH

In SIMATIC BATCH Control Center (BatchCC), the native 'Start' button cannot be arbitrarily grayed out via direct boolean logic from an automation controller because the BatchCC graphical interface is governed by application security permissions rather than AS interlock tags. To prevent an operator from starting a batch when required SFC unit phases are not in an idle, ready, or automatic state, engineers utilize three standard methods: 1. Configure the initial step transition in the recipe to verify controller equipment status flags before allocating units; 2. Implement the SIMATIC Industry Library BatchIf function block in CFC to programmatically evaluate all SFC conditions and autonomously trigger batch creation, release, and start; or 3. Restrict BatchCC operator roles and use WinCC SFC Multichart Controls on the OS.

Executive Summary

In process manufacturing plants governed by ISA-88 and SIMATIC BATCH, initiating a control recipe when field equipment or Sequential Function Chart (SFC) phases are in an improper state (such as Manual mode, Stopped, or Holding) can cause recipe execution stalls or premature aborts. Plant engineers frequently seek a mechanism to dynamically disable or gray out the 'Start' button in the Batch Control Center (BatchCC) user interface based on real-time programmable controller status. However, BatchCC is an administrative client whose button states are strictly dictated by batch lifecycle states and SIMATIC Logon user permissions. This article explains why direct AS hardware interlocks cannot modify the BatchCC GUI toolbar and details verified architectural alternatives: recipe precondition transitions, the Industry Library BatchIf interface block, and the WinCC SFC Multichart Control.

Architecture and Fundamental Mechanics

SIMATIC BATCH Command Architecture, UI Interlocking Constraints, and AS Interfacing:

BatchCC UI State Machine vs Automation Interlocks:
The Batch Control Center (BatchCC) GUI client interacts with the SIMATIC BATCH Server via a dedicated communication service and SQL database.
In BatchCC, control buttons such as 'Start', 'Hold', 'Stop', and 'Abort' are enabled or disabled exclusively based on two criteria: the internal lifecycle state of the batch object (e.g. Planned, Released, Running, Paused) and the active user's authorization rights configured in SIMATIC Logon.
There is no direct OPC, Industrial Ethernet, or AS tag link that maps a boolean flag from an S7-400 CPU to the grayed-out property of the native BatchCC toolbar buttons.
Method 1: Recipe Precondition Interlocking (ISA-88 Transition Logic):
The standard DCS methodology for equipment validation is embedding precondition checks directly into the recipe structure (ROP / RPH).
The very first Recipe Operation (ROP) or phase within a unit recipe is preceded by an initial transition. This transition evaluates equipment status words (BA_STATE, BA_EN, or custom ready flags) transmitted from the SFC types.
If an SFC phase is in Manual mode or not ready, the batch starts in BatchCC, but the recipe engine pauses at the initial transition. It will not allocate equipment, dose raw materials, or advance until all equipment interlocks clear.
Method 2: Programmatic Batch Control via Industry Library (BatchIf):
The SIMATIC PCS 7 Industry Library (IL) includes the BatchIf function block (derived from Braumat technology).
BatchIf resides directly in the AS CFC charts and communicates with the SIMATIC BATCH Server via system messages.
The automation program continuously monitors all unit SFCs, safety interlocks, and utility supplies. Only when all conditions are satisfied does the AS logic assert the start pulse on BatchIf, which instructs the BATCH server to create, release, and start the batch automatically without operator action in BatchCC.
Method 3: WinCC SFC Multichart Control and Role Restrictions:
Operators typically run batches from the WinCC OS runtime client rather than raw BatchCC.
By configuring the WinCC SFC Multichart Control (@SFC_Multichart_Control.pdl), operators can view a consolidated dashboard of all plant SFCs, verifying that all units are in Automatic and Idle before clicking an OS-level batch dispatch button.

Step-by-Step Implementation Procedure

Implement Equipment Ready Transitions in SIMATIC BATCH Recipe Editor:
* Open SIMATIC BATCH Recipe Editor on the Engineering Station.
* Open the master recipe and locate the initial Recipe Operation (ROP).
* Insert a Transition immediately following the recipe start marker.
* In the Transition Properties, configure conditions querying the SFC Type process status parameters (e.g., Unit1_Ready = TRUE and Unit1_Mode = Auto).
* Save and validate the recipe, then release it for production.
Configure the Industry Library BatchIf Block in CFC (Optional Automated Approach):
* From the PCS 7 Industry Library, insert the BatchIf block into a dedicated coordination CFC chart.
* Interconnect the status outputs of your unit SFC types (BA_STATE, QIDLE, QAUTO) into an AND logic block.
* Connect the output of the AND logic to the StartEn / StartReq input of BatchIf.
* Parameterize BatchIf with the Recipe Name, Recipe Version, and Order Category.
* When field conditions are met, trigger the batch start input to initiate execution from the controller.
Enforce Role-Based Permissions in SIMATIC Logon:
* Open SIMATIC Logon Administrative Console.
* Under the SIMATIC BATCH user group, inspect the 'Operator' role.
* Restrict permission for 'Start Batch' so that unauthorized personnel cannot initiate recipes outside prescribed operational procedures.
* Configure the requirement for Electronic Signatures or Supervisor release before batches can transition to 'Released' state.
Deploy SFC Multichart Control on WinCC OS:
* Open WinCC Graphics Designer on the OS project.
* Place the SFC Multichart Control object onto the unit overview graphic.
* Link the control to the respective SFC charts for each equipment module.
* Train operators to verify the green 'Ready/Idle' status across the Multichart overview prior to batch dispatch.

Verification

In SIMATIC Manager, place one of the required unit SFC types into Manual mode or an active Hold state.
In BatchCC, create and start a batch using the modified master recipe.
Verify that the batch starts in BatchCC, but immediately halts at the initial transition condition.
Verify in the BatchCC Control Recipe View that the transition indicates waiting for SFC readiness.
Switch the SFC type back to Automatic and Idle; verify that the recipe automatically satisfies the transition and advances.

Limitations and Operational Precautions

Direct manipulation of BatchCC native application menus and toolbar buttons via external PLC logic is not supported by Siemens SIMATIC BATCH architecture. Implementing automated batch generation via the Industry Library BatchIf block requires a separate engineering and runtime license (SIMATIC PCS 7 Industry Library). Utilizing the SIMATIC BATCH COM/.NET API interface requires software development expertise and separate API licensing. Recipe transition interlocking means the batch is recorded as 'Running' in BatchCC while waiting at the initial transition; if equipment remains faulted, the batch must eventually be aborted if the waiting timeout expires.

Engineer FAQ

Can I gray out the Start button in BatchCC using a CFC tag?

No. BatchCC toolbar button states are dictated strictly by internal batch lifecycle states and SIMATIC Logon user rights, not by automation controller tags.

What is the Industry Library BatchIf block?

BatchIf is a function block from the SIMATIC PCS 7 Industry Library that allows the S7-400 automation controller to programmatically create, release, and start batches on the SIMATIC BATCH Server.

What happens if a recipe starts while an SFC is not ready?

If recipe transitions are configured properly, the recipe starts in BatchCC but waits at the initial transition, preventing material dosing or unit allocation until the SFC becomes ready.

What is the WinCC SFC Multichart Control?

It is an ActiveX/OCX control in WinCC that displays the status of multiple SFC charts in a consolidated window, allowing operators to verify states and change modes across multiple units.

Does SIMATIC BATCH offer an API to control recipe dispatch?

Yes, the SIMATIC BATCH API provides programmatic interfaces (COM/.NET) allowing custom software to inspect equipment states and trigger batch commands.