SIMATIC BATCH System Limits: Master Recipe Capacity and Performance Boundaries

In SIMATIC BATCH, there is no hardcoded software limit on the total number of Master Recipes that can be created in the database. Master recipes, control recipes, and library operations are stored as relational records in Microsoft SQL Server (SBDatabase), meaning capacity is bounded only by hard disk storage and client memory. However, practical engineering performance guidelines recommend keeping the active recipe database structured cleanly: large installations typically operate hundreds to several thousand master recipes efficiently, provided that obsolete recipes are archived into the SIMATIC BATCH Archive database and runtime batch concurrency remains within licensed limits.

Executive Summary

Recipe management in batch processing requires high flexibility to accommodate diverse product formulations, campaign variations, and packaging sizes. When designing enterprise batch automation architectures using SIMATIC BATCH, plant software architects frequently inquire whether Siemens imposes hard architectural constraints on the number of Master Recipes permitted within a single project. While practitioners often assume an arbitrary cap (such as 256 or 1,000 recipes), the underlying relational architecture supports virtually unlimited recipe storage. This article outlines the system limits of SIMATIC BATCH, analyzes database scaling factors, and provides operational best practices to maintain high-performance recipe management.

Architecture and Fundamental Mechanics

SIMATIC BATCH Relational Architecture, SQL Server Storage, and Concurrency Limits:

Architecture of SIMATIC BATCH Recipe Storage:
In SIMATIC BATCH, Master Recipes are not stored as static flat files; they are complex object graphs stored within the Microsoft SQL Server relational database (SBDatabase).
Each Master Recipe comprises normalized relational tables defining header metadata, Unit Recipes, Recipe Operations (ROP), Recipe Phases (RPH), formula setpoint tables, and transition conditions.
Because modern 64-bit Microsoft SQL Server (2014/2016/2017) supports database sizes up to hundreds of gigabytes, the system can technically store tens of thousands of Master Recipe definitions without database file overflow.
Concrete Documented System Limitations in SIMATIC BATCH:
While recipe storage is unconstrained, Siemens documents specific structural and operational boundaries in the SIMATIC BATCH Limits and Specifications manual:
1. Concurrent Active Batches: Bounded by the purchased runtime license (packages available for 10, 30, 60, up to 120 simultaneously running batches per BATCH Server).
2. Recipe Hierarchy Nesting: Maximum 10 hierarchy levels (Procedure > Unit Recipe > Recipe Operation > Recipe Phase > Steps).
3. Number of Units per Process Cell: Typically up to 64 or 128 physical Units per SIMATIC BATCH project.
4. Maximum Number of Phases per Unit: Technically up to 256 Equipment Phases per Unit.
Practical Performance Boundaries in BatchCC:
When an operator opens Batch Control Center (BatchCC), the client queries SQL Server to build the visual recipe tree.
If thousands of unorganized recipes reside in a single flat folder, the UI tree expansion may experience rendering delays (several seconds of latency).
Structuring recipes into hierarchical category folders and archiving obsolete versions ensures instantaneous UI responsiveness.

Step-by-Step Implementation Procedure

Organize Master Recipes Hierarchically:
* In BatchCC, do not place all recipes in the root 'Master Recipes' folder.
* Create logical category folders (e.g. Product_Line_A, Product_Line_B, Cleaning_In_Place_CIP, Development_Trials).
* Distribute master recipes into their respective category folders to optimize database index queries.
Manage Recipe Versioning:
* When modifying formulations, use the built-in SIMATIC BATCH versioning system (Major/Minor versioning, e.g. V1.0, V1.1).
* Release recipes formally (Status: Released for Testing -> Released for Production).
Archive Obsolete and Superseded Recipes:
* When a recipe formulation is retired, change its status to Invalid or Revoked.
* Periodically execute the SIMATIC BATCH Archive Utility to move completed batch records and expired recipes into the detached BATCH_ARCHIVE database, keeping SBDatabase compact and high-performing.
Verify BATCH Server Resource Sizing:
* For facilities managing over 500 master recipes and high batch turnover, ensure the BATCH Server IPC is equipped with minimum 16 GB to 32 GB RAM, high-speed NVMe/SSD storage, and dedicated RAID-1 protection.

Verification

In BatchCC, expand the Master Recipes navigation tree; confirm that expanding folders with hundreds of recipes loads in under 2 seconds.
Create and release a new test Master Recipe; confirm that recipe validation completes with zero database constraint warnings.
Initiate batch creation from the new recipe; verify that the control recipe generates and allocates unit resources seamlessly.

Limitations and Operational Precautions

While recipe definitions are unlimited, active batch concurrency is strictly enforced by license keys (SIMATIC BATCH BATCHes). Attempting to start more concurrent batches than licensed causes BatchCC to queue batch starts with a license shortage warning.