Resolving BatchCC 'Cannot Update the Process Cell' and Grayed-Out Menus After SFC Changes

In SIMATIC PCS 7, when Batch Control Center (BatchCC) prompts that an update of the process cell is required following SFC modifications, but the menu option 'Update Process Cell' is grayed out or rejected, the condition is caused by active batches running in the process cell, missing Windows user group permissions, or stopped SIMATIC BATCH server services. BatchCC strictly prohibits modifying the process cell model while any batch is in RUN, HELD, or PAUSED state. To resolve, inspect the active batch list in BatchCC and terminate or complete all active batches. Ensure the logged-in Windows user belongs to the local 'SIMATIC BATCH' and 'SIMATIC HMI' user groups on both the client and server PCs. Finally, verify that the SIMATIC BATCH Server runtime service is actively running and reachable via Simatic Shell.

Executive Summary

Following minor engineering modifications to Equipment Phases (SFC types) in SIMATIC Manager, engineers compile and download changes to the AS, OS, and BATCH servers. Upon opening Batch Control Center (BatchCC) on the operator client, a prompt appears stating that the process cell configuration must be updated. However, the engineer discovers that 'System -> Update Process Cell Data' is grayed out, alongside most recipe and batch creation menus. Even administrative accounts appear locked out. This technical article analyzes the architectural prerequisites for updating process cell data in SIMATIC BATCH, explaining active batch interlocks, Windows security token requirements, and communication dependencies.

Architecture and Fundamental Mechanics

The process cell update mechanism in SIMATIC BATCH protects operational data integrity through several rigid interlocks:
1. The Active Batch Execution Lock:
- When BatchCC executes a process cell update, the BATCH Server reloads the core ISA-88 equipment database (sbdata).
- If any batch in the entire process cell is currently in an active state (Planned, Ready, Running, Held, Paused), the server rejects schema modifications to prevent runtime recipe pointer corruption.
- As a result, the 'Update Process Cell Data' menu item is disabled in the GUI.
2. Windows Security Groups and User Tokens:
- SIMATIC BATCH relies on Microsoft Windows Security Groups to authorize administrative actions.
- The operating user must be an active member of:
a. SIMATIC BATCH (grants general BATCH permissions).
b. SIMATIC BATCH Administrator or configured Superuser role in BATCH User Management (sbuser).
c. SIMATIC HMI (grants inter-process communication rights).
- If user permissions were modified while a session was active, the Windows security token does not update until the user logs off and logs back in.
3. BATCH Server Service Availability (sbserver.exe):
- BatchCC communicates with the BATCH Server via proprietary DCOM and TCP socket channels.
- If the BATCH Server service is stopped, starting up, or desynchronized across a redundant link, BatchCC defaults to read-only lock mode, graying out administrative commands.

Step-by-Step Implementation Procedure

Inspect and Clear Active Batches in BatchCC:
a. Open BatchCC on the Batch Client station.
b. In the tree view, navigate to Batches.
c. Filter for any batches in states: Running, Held, Paused, Starting, or Stopping.
d. Allow production batches to finish, or manually terminate test batches by right-clicking each batch and selecting Control -> Abort or Stop.
e. Archive or close all terminated batches so that zero active batches occupy the process units.
Verify Windows User Group Memberships:
a. On both the Batch Client PC and the BATCH Server PC, open Computer Management -> Local Users and Groups -> Groups.
b. Inspect the group SIMATIC BATCH and SIMATIC BATCH Administrator.
c. Confirm that the current Windows user (or domain user) is explicitly added to both groups.
d. If newly added, Log off Windows and log back in to apply the updated security token.
Verify BATCH Server Service and Runtime State:
a. On the BATCH Server PC, inspect the system tray for the SIMATIC BATCH Start Coordinator icon.
b. Verify that the BATCH Server status is green and indicates 'Running'.
c. If the server is stopped, right-click the coordinator and select Start.
Execute 'Update Process Cell Data' in BatchCC:
a. Reopen BatchCC.
b. Log in with the administrative credentials.
c. Click System -> Update Process Cell Data (the menu should now be enabled).
d. In the confirmation dialog, click 'Yes' to reload the updated process cell configuration from sbdata.
Validate Process Cell Synchronization:
a. In the BatchCC status bar, verify the prompt clears and displays 'Ready'.
b. Confirm that all units, equipment phases, and recipe menus are active and clickable.

Verification

In BatchCC, verify that System -> Update Process Cell Data executes and completes with the message 'Process cell updated successfully'.
Open an existing Master Recipe: verify that all recipe elements report healthy status without red cross error overlays.
Create and release a new test batch: confirm the batch transitions to 'Ready' and can be started without licensing or cell errors.

Limitations and Operational Precautions

Never force an update of the process cell by manually manipulating SQL databases or deleting sbdata while batches are executing. Doing so can cause unrecoverable recipe execution deadlocks.

Engineer FAQ

Why is 'Update Process Cell Data' grayed out in BatchCC?

It is typically disabled because one or more batches are currently running or held in the process cell, or the user lacks SIMATIC BATCH administrative rights.

Must all batches be completed before updating the process cell?

Yes. SIMATIC BATCH strictly requires zero active (running, held, or paused) batches across the entire process cell before adopting new cell configurations.