Locating SIMATIC BATCH Process Cell (PCell) Documentation and 'Create New Project' Logic in PCS 7
To locate official documentation for SIMATIC BATCH Process Cells (PCells) and understand the 'Create new project' checkbox during 'Save As' in SIMATIC PCS 7 V9.1 SP2, consult the 'SIMATIC BATCH Process Cell Architecture' manual and the 'PCS 7 Engineering System' manual on Siemens Industry Online Support (SIOS). When executing 'File' -> 'Save As...' on a multiproject, enabling the 'Create new project' checkbox generates brand-new internal Globally Unique Identifiers (GUIDs) for the multiproject, OS projects, and BATCH Process Cells (PCells), preventing database ID collisions when running duplicate projects on the same network.
Table of Contents
- Executive Summary
- Architectural and System Mechanics
- Step-by-Step Engineering and Implementation Procedure
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
When duplicating engineering projects to create parallel production units or test benches in SIMATIC PCS 7 V9.1 SP2, engineers frequently use the 'Save As...' function in SIMATIC Manager. In batch facilities, customers often specify saving the project in a manner that creates a new 'PCell' (Process Cell). However, locating exact documentation on the term 'PCell' on SIOS can be frustrating because it is an acronym embedded within SIMATIC BATCH architecture manuals. Furthermore, PCS 7 V9.1 SP2 introduced an explicit checkbox: 'Create new project'. This article explains the technical mechanics of PCell GUID generation, clarifies the exact role of the 'Create new project' flag, and provides direct SIOS reference documentation.
Architectural and System Mechanics
Process Cell (PCell) Architecture and GUID Management in SIMATIC PCS 7:
- ISA-88 Process Cell (
PCell) Concept: - In ISA-88 batch standards and SIMATIC BATCH, a Process Cell (
PCell) represents the top-level equipment container enclosing all units, equipment modules, and recipes for a production area. - Every PCell possesses a unique internal binary GUID in the SIMATIC BATCH database and WinCC SQL database.
- The Risk of Simple File Duplication:
- If an engineer copies a project folder using Windows Explorer or executes a standard 'Save As' without ID regeneration, all internal GUIDs remain identical to the original plant.
- If both projects connect to the same terminal bus or network domain, WinCC Simatic Shell and SIMATIC BATCH servers cross-talk, leading to catastrophic database synchronization errors.
- The 'Create New Project' Option in PCS 7 V9.1 SP2:
- Introduced in V9.1 SP2 to streamline project replication.
- When checked, SIMATIC Manager automatically re-keys all internal database identifiers, generates new PCell GUIDs, and resets OS server packages, ensuring the cloned project operates as a completely independent automation entity.
Step-by-Step Engineering and Implementation Procedure
Step 1: Execute Save As with 'Create New Project' in PCS 7 V9.1 SP2
- Open SIMATIC Manager with the master multiproject active.
- Select 'File' -> 'Save As...'.
- Choose the target destination directory and enter the new project name.
- Check the box 'With reorganization (slow)'.
- Check the box 'Create new project' (introduced in V9.1 SP2).
- Click OK; SIMATIC Manager reorganizes database tables and writes new project GUIDs.
Step 2: Regenerate SIMATIC BATCH Process Cell Data
- In SIMATIC Manager, switch to Plant View.
- Right-click the top-level Plant Hierarchy folder (representing the Process Cell) -> 'SIMATIC BATCH' -> 'Open BATCH Configuration...'.
- In the BATCH configuration dialog, select 'Compile / Transfer'.
- Verify that SIMATIC BATCH registers the new Process Cell name and generates fresh recipe headers.
Step 3: Locate Official Siemens Manuals on SIOS
To review official documentation directly, search SIOS using exact Document Entry IDs:
- SIMATIC BATCH System Manual: Entry ID 109746526.
- SIMATIC PCS 7 Engineering System Manual: Entry ID 109746514.
- SIMATIC PCS 7 V9.1 SP2 What's New: Entry ID 109812242.
Step 4: Verify Network Isolation and Simatic Shell
Open Simatic Shell on the new station; confirm that the newly generated PCell and OS projects register as distinct nodes without conflicting with the source project.
Verification
To verify proper PCell generation:
1. In SIMATIC BATCH Control Center (BatchCC), open the plant view; confirm that the Process Cell displays the new project name.
2. Open the BATCH database properties; verify that the internal Process Cell ID is distinct from the source plant.
3. Verify that creating and releasing a test recipe executes without database lock conflicts.
Limitations and Operational Precautions
Operational precautions:
- Reorganizing a large multiproject with 'Create new project' can take 30 to 60 minutes; do not interrupt the process.
- After generating a new project, you must update the Computer Names in WinCC Explorer properties to match the new physical/virtual hostnames.
- Never connect cloned automation stations to the plant bus while the source system is online until IP addresses and MAC addresses are updated in HW Config.
Engineer FAQ
Q: What does 'PCell' stand for in PCS 7?
A: 'PCell' stands for Process Cell, the highest equipment level defined in ISA-88 and SIMATIC BATCH representing the batch plant.
Q: What does the 'Create new project' checkbox do in V9.1 SP2?
A: It generates entirely new internal project GUIDs and resets database identifiers, preventing cross-talk with the source project on the same network.
Q: Why is 'With reorganization (slow)' recommended?
A: It purges deleted database records, rebuilds indices, and ensures clean database structures before generating new project IDs.
Q: How do I search for exact manuals on SIOS?
A: Search using the 8-digit Siemens Entry ID rather than generic keyword strings to retrieve exact document versions.
Q: Do I need to re-license SIMATIC BATCH for a new PCell?
A: SIMATIC BATCH licensing is based on the number of configured batch units (Unit POs) across the plant, not the number of PCells.
Technical References
- SIMATIC Process Control System PCS 7 SIMATIC BATCH Manual
- SIMATIC Process Control System PCS 7 Engineering System Manual
- PCS 7 V9.0 SP3 Licenses and Configuration Limits
Related Articles
- Resolving SIMATIC BATCH Recipe Editor Lockout Error 'Object Being Used by Another Application'
- Resolving Multiproject Archiving Failures and File Lock Conflicts in SIMATIC PCS 7
- Implementing Multi-User Engineering and Multiproject Workflows in SIMATIC PCS 7
Related Tags
SIMATIC BATCH, PCell, Process Cell, Save As Reorganization, PCS 7 V9.1 SP2