Displaying SIMATIC BATCH Controls on Web Clients: Limitations and Web Center Architecture

In SIMATIC PCS 7 (including V8.0 and V8.1), native SIMATIC BATCH ActiveX controls (OCXs) such as the Batch Control Center (BCC) and Recipe Editor faceplates cannot execute inside standard WinCC Web Navigator clients. WinCC Web Navigator publishes standard WinCC graphics over HTTP/HTTPS, but native BATCH OCX controls require local SIMATIC BATCH Client binaries and direct SQL/DCOM communication with the BATCH Server. To access batch formulation, control, and electronic batch records via web browsers, engineers must deploy SIMATIC BATCH Web Center or utilize thin-client Remote Desktop / Citrix architectures.

Architectural Anatomy of SIMATIC BATCH OCX Controls

In recipe-driven batch processing plants (pharmaceutical, specialty chemical, food and beverage), SIMATIC BATCH coordinates recipe execution, phase sequencing, batch tracking, and FDA 21 CFR Part 11 electronic batch records (EBR).

On standard PCS 7 Operator Stations (OS Clients), SIMATIC BATCH integrates through specialized OLE Custom Controls (ActiveX OCXs):
* @Batch_Control.pdl: OS screen hosting the central Batch faceplate control.
* Batch Control Center (BCC): Dedicated application for creating, releasing, scheduling, and starting batches.
* Batch Recipe Editor: Graphical editor for developing master recipes compliant with ANSI/ISA-88.
* Batch OS ActiveX Controls: Embedded graphical components in WinCC screens displaying current batch name, recipe phase, target setpoints, and step completion status.

These controls are heavy Windows desktop components. They interact directly with local Windows DLLs, maintain persistent TCP/IP socket connections to the SIMATIC BATCH Server (sb_server.exe), and execute local SQL queries against the batch database.

Why WinCC Web Navigator Rejects BATCH OCXs

Engineers frequently configure a WinCC Web Navigator Server on an OS Server/Client to allow managers and mobile operators to view plant graphics from remote commercial PCs. While standard WinCC graphics, PID faceplates, and trend controls display seamlessly, BATCH OCX controls appear completely blank or trigger ActiveX execution errors.

Technical causes:
1. Missing Web Publishing Wrappers: WinCC Web Navigator requires ActiveX controls to be packaged as signed cabinet (.cab) files designed for web containment. SIMATIC BATCH OCXs are proprietary desktop binaries not architected for Web Navigator browser containment.
2. DCOM and SQL Database Isolation: A remote Web Navigator client communicates strictly over port 80 (HTTP) or port 443 (HTTPS) to the Web Navigator IIS server. It does not possess direct DCOM or SQL port access to the back-end SIMATIC BATCH Server.
3. Local Component Absence: Standard Web Navigator clients do not have the complete SIMATIC BATCH Client software suite installed, preventing the OCX from instantiating its underlying COM objects.

Supported Web and Remote Client Architectures for SIMATIC BATCH

Siemens provides two fully supported architectural approaches to access SIMATIC BATCH functionality remotely:

Solution 1: SIMATIC BATCH Web Center

Starting in PCS 7 V8.0, Siemens introduced SIMATIC BATCH Web Center:
* A dedicated web portal hosted on Microsoft Internet Information Services (IIS).
* Exposes pure web-based interfaces for recipe overview, batch scheduling, batch status monitoring, and Electronic Batch Record (EBR) reporting.
* Clients require only standard web browsers (Internet Explorer, Microsoft Edge) without local BATCH software installations.

Solution 2: Terminal Services / Citrix Remote Desktop

For full engineering access (including Recipe Editor and direct BCC operations):
* Deploy a SIMATIC BATCH Client on a Windows Server Terminal Server (Remote Desktop Session Host or Citrix XenApp).
* Remote users launch thin-client sessions running certified BATCH desktop clients over encrypted RDP/ICA channels.
* This provides 100% feature parity with physical control room stations.

Batch Remote Access Architecture Comparison Matrix

The following matrix evaluates remote access architectures for SIMATIC BATCH:

Evaluation AttributeWinCC Web NavigatorSIMATIC BATCH Web CenterTerminal Server / CitrixBatch OCX ExecutionNot Supported (Blank Screen)Native Web ReplacementFull Native ExecutionClient InstallationWeb Navigator Plugin onlyZero Footprint (Pure Web)RDP / Citrix WorkspaceRecipe EditingNoneLimited / View onlyFull Master Recipe EditingBatch Control (Start/Stop)NoneSupported via Web CenterFull Operational ControlFDA 21 CFR Part 11 AuditNon-compliant for BatchFully CompliantFully CompliantNetwork ProtocolsHTTP / HTTPS (80 / 443)HTTP / HTTPS (80 / 443)RDP (3389) / ICA (1494)Licensing RequirementWinCC Web Navigator LicenseSIMATIC BATCH Web Center LicenseBATCH Client + RDS CAL

Step-by-Step Implementation of SIMATIC BATCH Web Center

To deploy SIMATIC BATCH Web Center:
1. Verify System Prerequisites:
- Ensure the target server (BATCH Server or dedicated Web Server) has Microsoft IIS installed with ASP.NET extensions enabled.
- Install SIMATIC BATCH Web Center from the PCS 7 installation media.
2. Configure Web Center Site in IIS:
- Open IIS Manager. Verify the BatchWebCenter virtual directory is bound to the appropriate IP and SSL certificate (port 443 recommended).
3. Configure User Security and SIMATIC Logon:
- In Windows Computer Management, add authorized batch operators to the SIMATIC BATCH Windows user groups (SIMATIC BATCH Administrator, SIMATIC BATCH Operator).
- Configure SIMATIC Logon to authenticate web users against the plant Active Directory domain.
4. Access Web Center from Remote Browser:
- On the remote client workstation, open the browser and navigate to: https://<BatchServerName>/BatchWebCenter.
- Log in with authorized Windows credentials.
5. View Batch Records and Active Processes:
- Navigate the web tabs: Batch Planning, Batch Control, and Batch Reports to monitor active plant batches and review completed batch archive records.

Verification

Verify remote batch monitoring and reporting:
1. Start an active batch on the physical control room OS Client.
2. From the remote client browser, log into SIMATIC BATCH Web Center.
3. Verify that the newly started batch appears in the Active Batches table with identical recipe step status, batch ID, and unit allocation.
4. Verify that recipe phase setpoints and process values dynamically refresh.
5. Generate an Electronic Batch Record (EBR) PDF report through Web Center and confirm digital signatures and audit trails are intact.

Limitations and Operational Precautions

Operating SIMATIC BATCH over web interfaces requires robust network cybersecurity; never expose Web Center directly to public internet without VPN or DMZ reverse proxy firewalls.
Full graphical recipe creation requires the desktop BATCH Recipe Editor; do not attempt complex recipe restructuring via web interfaces.
Licensing note: Deploying SIMATIC BATCH Web Center or Terminal Server clients requires dedicated software licenses (e.g. 6ES7657-0...); validate licensing quantities against authorized Siemens distributor quotations.

Engineer FAQ

Can I view basic batch text tags on WinCC Web Navigator?

Yes. Standard WinCC text and integer tags populated by BATCH (such as @Batch_ID or @Batch_Name) can be displayed in standard WinCC static text fields and I/O fields on Web Navigator. Only the specialized BATCH OCX faceplate controls fail.

Does SIMATIC BATCH Web Center support mobile tablets?

Yes. In PCS 7 V8.2 and V9.x, BATCH Web Center supports modern web browsers, enabling batch status inspection on certified industrial mobile tablets.

Can an operator start a batch from SIMATIC BATCH Web Center?

Yes, provided the logged-on user has the required operational privileges configured in SIMATIC Logon and the recipe has already been validated and released in the Master Recipe Editor.