Using SIMATIC BATCH with S7-300 Controllers - Product Phase-Out and Industry Library Package Unit Architecture

SIMATIC BATCH does not support direct recipe execution or equipment phase control natively on standalone S7-300 controllers in modern SIMATIC PCS 7 releases (v8.0, v8.1, v8.2, v9.0, and newer). While a dedicated add-on package titled 'SIMATIC BATCH for WinCC' (v7.1) previously permitted recipe management on S7-300 and WinAC systems, Siemens declared this product completely phased out and discontinued in June 2013. In current PCS 7 architectures, SIMATIC BATCH strictly requires S7-400 or CPU 410-5H controllers to execute the ISA-88 Batch Interface Blocks (BIF / IEPH / IEOP). To incorporate S7-300 machines or skid packages into a SIMATIC BATCH process, engineers must integrate the S7-300 as a Package Unit via the SIMATIC PCS 7 Industry Library (IL), interfacing the skid to a supervisory S7-400 controller.

Historical Context: Phase-Out of SIMATIC BATCH for WinCC

Historically, Siemens offered two distinct product branches for recipe and batch processing:
1. SIMATIC BATCH for PCS 7: The fully integrated batch management package native to the PCS 7 DCS environment, operating in tight synergy with CFC, SFC, and S7-400 hardware.
2. SIMATIC BATCH for WinCC (Standalone): An independent WinCC option package (prominent in v7.0 and v7.1 SP1) engineered for standalone WinCC SCADA systems. This option allowed recipe execution on S7-300 controllers, S7-400 PLCs, and WinAC RTX software controllers using simplified communication blocks.

In June 2013, Siemens officially declared SIMATIC BATCH for WinCC phased out (end of product lifecycle). Consequently, no updates were produced for WinCC v7.2, v7.3, v7.4, or v7.5, and no compatibility exists with 64-bit modern Windows operating systems. As a result, implementing a new batch control system directly on S7-300 using SIMATIC BATCH software is commercially unavailable and unsupported.

Technical Constraints of S7-300 with ISA-88 Batch Control

The architectural limitation preventing SIMATIC BATCH from running directly on S7-300 in modern PCS 7 stems from controller resources and communication mechanisms:

Memory and Work Area Demands: Modern SIMATIC BATCH interface blocks (IEPH, IEOP, BIF_ET, UNIT_PLC) require extensive local DB storage, multi-instance data structures, and significant communication buffer depths. The S7-300 work memory architecture (typically 128 KB to 2 MB) cannot support large-scale ISA-88 state machines alongside standard process automation logic.
Communication Protocols: SIMATIC BATCH relies on asynchronous event-driven BATCH messaging via high-speed S7 communication primitives and raw data transfer (BSEND/BRCV over S7 Named Connections). S7-300 communication processors (CP 343-1) possess limited concurrent S7 connection endpoints and do not support PCS 7 Named Connection routing.
CFC / SFC Type Integration: In PCS 7, SIMATIC BATCH synchronizes directly with SFC Types (Sequential Function Charts configured as Equipment Phases). SFC Types are exclusively compiled and executed on S7-400 and CPU 410 systems; they cannot be targeted to S7-300 CPU hardware in PCS 7.

Modern Architecture: Integrating S7-300 via PCS 7 Industry Library

When a plant requires small skid systems or S7-300 package units (such as CIP skids, dosing skids, or blending units) to operate within a master SIMATIC BATCH recipe, Siemens provides a standardized architectural solution: the SIMATIC PCS 7 Industry Library (IL).

In this architecture:
1. Autonomous Skid Control: The S7-300 executes autonomous machine control, interlocks, and local sequence logic using standard STEP 7 or TIA Portal code.
2. Package Unit Interface Block (Panel/Controller): Technological blocks from the Industry Library (such as S7AnIn, S7DiIn, S7Mot, or custom package unit interface FBs) reside on the S7-300.
3. Supervisory S7-400 Controller: The S7-300 connects via Industrial Ethernet (PROFINET or ISO-on-TCP) to a central S7-400 or CPU 410-5H controller.
4. Proxy SFC / Phase in S7-400: On the S7-400, an SFC Type or Equipment Phase (IEPH) is instantiated. This phase maps recipe control commands (START, STOP, HOLD, ABORT, Setpoints) to the S7-300 via data blocks, and reads back phase states and actual process values.
5. SIMATIC BATCH Allocation: SIMATIC BATCH Server allocates the supervisory S7-400 Unit and Phase, orchestrating recipe execution seamlessly while treating the S7-300 as an underlying subsystem.

Comparative Architecture Matrix for Batching Solutions

The table below outlines available Siemens solutions for small-to-medium batching systems:

ArchitectureController HardwareRecipe EngineISA-88 ComplianceCurrent AvailabilityFull SIMATIC BATCHS7-400 / CPU 410-5HSIMATIC BATCH ServerComplete Class / Unit / Phase HierarchyStandard PCS 7 Solution (Active)Package Unit IntegrationS7-300 Skid + S7-400 Super.SIMATIC BATCH Server (via AS 410)Fully integrated through AS proxy phaseStandard Industry Library Solution (Active)SIMATIC BATCH for WinCCS7-300 / WinACWinCC BATCH Option v7.1Limited Phase InterfacePhased Out June 2013 (Discontinued)WinCC User ArchivesS7-300 / S7-1500Custom WinCC VBS / C-ScriptManual Table-Based SetpointsSupported Option for Basic BlendingTIA Portal Recipe PackageS7-1500 / Comfort PanelHMI Advanced RecipesParameter sets only (Non-ISA-88)Supported in TIA Portal / WinCC Unified

Verification

To verify proper operation of an S7-300 Package Unit integrated into SIMATIC BATCH via an S7-400 supervisor:
1. Verify Communication Heartbeat: Confirm that the lifebit counter between the S7-400 proxy phase and the S7-300 communication DB increments reliably in both directions.
2. Phase State Synchronization: In SIMATIC BATCH Control Center, start the batch recipe step and confirm that the state command (e.g., START = 1) is received by the S7-300 within 500 ms.
3. Fault and Interlock Handling: Simulate an emergency stop or motor trip on the S7-300 skid; verify that the S7-400 proxy phase transitions immediately to HOLD or ABORT in the SIMATIC BATCH batch monitor.
4. Actual Value Logging: Confirm that final dosed quantities and batch parameters reported by the S7-300 are correctly archived into the Electronic Batch Record (EBR) PDF report.

Limitations and Operational Precautions

Engineering teams must observe the following constraints:
- Do not attempt to install legacy SIMATIC BATCH for WinCC v7.1 licenses on modern 64-bit operating systems; the software is incompatible with Windows 7, Windows 10, and Windows Server 2012/2016.
- Always validate final license quantities and MLFBs against the applicable Siemens catalog and authorized distributor quotation. Software packages must be purchased for active, supported releases.
- S7-300 controllers lack hardware redundancy (non-fault-tolerant); if high process availability is required, the batch skid must be engineered using redundant S7-400H or CPU 410-5H controllers.

Engineer FAQ

Can an S7-1500 PLC run SIMATIC BATCH directly?

No. SIMATIC BATCH is an integral component of SIMATIC PCS 7 and cannot run natively on S7-1500 controllers. However, an S7-1500 can be integrated as a Package Unit to an AS 410 supervisory controller using the PCS 7 Industry Library or OPC UA, similar to an S7-300.

Can I buy replacement licenses for SIMATIC BATCH for WinCC V7.1?

No. The product is phased out. Siemens technical support and manufacturing no longer supply new licenses or software media for SIMATIC BATCH for WinCC. Migrating to full PCS 7 or WinCC User Archives is required.

What is the maximum number of units supported by SIMATIC BATCH?

SIMATIC BATCH scales from small installations (starting at 6 units) up to large multi-client enterprise architectures supporting hundreds of units via scalable SIMATIC BATCH Unit Expansion licenses.