Co-locating Batch Control Center (BatchCC) on BATCH Servers vs OS Clients

In SIMATIC PCS 7, installing the SIMATIC BATCH Client software package directly on a dedicated BATCH Server to run Batch Control Center (BatchCC) locally is officially supported and standard practice for single-station or compact multi-user architectures. While large distributed production plants typically install BatchCC exclusively on separate OS/Batch Client stations to isolate server processing from operator interactions, co-locating BatchCC on the BATCH Server provides significant diagnostic and commissioning advantages. Installing the BATCH Client on the server does not require extra runtime licenses beyond standard BATCH Client licensing in Automation License Manager. Validate client-server licensing requirements with an authorized Siemens distributor or the Siemens Industry Mall.

Executive Summary

When designing SIMATIC BATCH architectures in PCS 7, system integrators often face architectural decisions regarding the placement of operator tools: should Batch Control Center (BatchCC) and the Recipe Editor (BFAPI) be restricted to operator client PCs, or can they be installed directly on the physical BATCH Server? Engineers frequently question whether installing client components on the server introduces performance degradation, software conflicts, or licensing penalties. This technical guide evaluates the operational differences, security considerations, installation workflows, and licensing rules governing the deployment of BatchCC across server and client stations.

Architecture and Fundamental Mechanics

The modular software topology of SIMATIC BATCH distinguishes server runtime engines from client presentation tools:
1. SIMATIC BATCH Server Component (sbserver.exe):
- Executes batch control logic, state machines, unit allocation, recipe step dispatching, and historical batch logging (sbdata).
- Operates as a background Windows service, requiring high availability, low CPU latency, and minimal interactive desktop interference.
2. SIMATIC BATCH Client Component (BatchCC / Recipe Editor):
- Provides the graphical user interface for recipe creation, batch scheduling, electronic batch records (EBR), and real-time execution monitoring.
- Communicates with the server runtime via local inter-process communication (IPC) if co-located, or via TCP/IP and DCOM across the terminal bus if remote.
3. Architectural Topologies:
- Distributed Multi-User System: BATCH Server runs on a dedicated PC (or redundant pair). Multiple OS/Batch Clients run BatchCC across the control room. This isolates server processing from operator actions and enforces strict security zones.
- Single Station / Combined Station: BATCH Server and BATCH Client co-reside on the same machine (e.g., combined OS/ES/Batch Server). Siemens explicitly tests and supports this topology.
4. Licensing Considerations:
- SIMATIC BATCH licensing separates Server licenses (e.g., BATCH Server (PO 100/300/1000)) from Client licenses (BATCH Client).
- Opening BatchCC on the server consumes one standard BATCH Client license key from Automation License Manager, identical to running it on a remote client.

Step-by-Step Implementation Procedure

Determine Plant Architectural Requirements:
a. For small-scale skid units or package plants: select the Co-located Server/Client topology to reduce hardware costs.
b. For full-scale production facilities with 24/7 operator control rooms: deploy BatchCC on OS/Batch Clients, but install the Batch Client package on the server for engineering diagnostics.
Install SIMATIC BATCH Client on the BATCH Server:
a. Mount the SIMATIC PCS 7 installation media on the BATCH Server.
b. Run Setup.exe and select 'Package installation' or 'Custom installation'.
c. Under the SIMATIC BATCH tree, check both BATCH Server and BATCH Client.
d. Complete installation and restart the server PC.
Configure Automation License Manager (ALM):
a. Open ALM on the BATCH Server (or centralized license server).
b. Ensure that both a SIMATIC BATCH Server license key and at least one SIMATIC BATCH Client license key are available and installed.
Configure Windows User Groups on the Server:
a. Open Computer Management -> Local Users and Groups.
b. Ensure operator and maintenance accounts are members of SIMATIC BATCH.
c. For engineers creating and modifying recipes locally, ensure membership in SIMATIC BATCH Administrator.
Test Local BatchCC Execution:
a. Launch Batch Control Center via the Windows Start Menu: Siemens Automation -> SIMATIC -> BATCH -> Batch Control Center.
b. Verify that BatchCC binds locally (localhost or local computer name) to the BATCH Server runtime.
c. Confirm that process cells, master recipes, and active batches render with full administrative access.

Verification

Launch BatchCC on the BATCH Server: confirm connection establishes within 5 seconds without DCOM or network timeout alerts.
In Automation License Manager, check license status: confirm one BATCH Client license shows 'In use'.
Create and release a recipe locally: confirm that the recipe updates immediately and reflects on remote OS/Batch clients across the plant.

Limitations and Operational Precautions

Allowing operators to perform extensive recipe modifications or view high-resolution historical trends directly on an active BATCH Server can cause transient CPU and disk spikes. Standard plant operations should always be conducted from dedicated OS/Batch Clients.

Engineer FAQ

Is it officially supported to install BatchCC on a BATCH Server?

Yes. Siemens fully supports co-locating the SIMATIC BATCH Client package on the BATCH Server.

Does running BatchCC on the server consume a BATCH Client license?

Yes. Opening BatchCC consumes one SIMATIC BATCH Client license key from Automation License Manager regardless of whether it runs on a client or server.

Why do large plants separate Batch Clients from Batch Servers?

To protect server computational performance, prevent accidental desktop disruptions, and restrict physical and administrative server access to authorized personnel.