Preventing CPU Download Conflicts and Configuring Multi-User Engineering in SIMATIC PCS 7

Connecting two separate, uncoordinated Engineering Stations (ES) to the same SIMATIC PCS 7 automation station causes severe online synchronization conflicts. If two independent offline project copies download to the same S7-400 CPU, timestamp and symbol table discrepancies declare the offline and online databases out of sync, blocking Changes-Only downloads and forcing an operational CPU STOP. In PCS 7, multi-engineer collaboration must be configured using official Multi-User Engineering, where a single central Engineering Station hosts the master Multiproject and secondary engineering clients access distributed sub-projects with chart-level reservation locking.

Dangers of Uncoordinated Multi-ES Access and Online Database Conflicts

In SIMATIC PCS 7 architectures featuring redundant OS servers and distributed clients, plants frequently question why standard guidelines specify a single primary Engineering Station (ES).

What Happens When Two Unlinked ES PCs Access the Same AS?

The Unique Project Database Principle: When CFC charts are compiled and downloaded to an S7-400 or S7-410 controller, the compiler generates a cryptographic download timestamp and unique memory allocation tables for instance DBs and internal cross-references.
Loss of 'Changes Only' Download Capability: If Engineer A downloads logic from ES 1, the CPU registers ES 1's unique timestamp. If Engineer B on ES 2 then attempts to download a change from an independent project copy, the compiler detects a timestamp mismatch. The engineering system declares that the offline program does not match the online CPU. The only way to proceed is a full download with CPU STOP, shutting down running plant production.
WinCC Tag Management Inconsistencies: Compiling the OS from two separate engineering stations introduces tag prefix and DB offset collisions in the WinCC SQL database, causing faceplates to disconnect or report incorrect tag values.

DANGEROUS UNCOORDINATED SETUP:
+-------------------+           +-------------------+
| Engineering PC 1  |           | Engineering PC 2  |
| Independent Proj  |           | Independent Proj  |
+-------------------+           +-------------------+
          |                               |
          +--------------+ +--------------+
                         | |
                         v v Simultaneous Uncoordinated Downloads
             +-------------------------+
             | SIMATIC S7-400 / S7-410 |
             | Database Conflict Occurs |
             | Changes-Only BLOCKED!   |
             | FORCED CPU STOP CRASH!  |
             +-------------------------+

Architecture and Configuration of Multi-User Engineering

To allow multiple engineers to work simultaneously without database corruption, SIMATIC PCS 7 provides Multi-User Engineering:

RECOMMENDED MULTI-USER ENGINEERING:
+-------------------------------------------------------------+
| Master Engineering Station (Server ES)                      |
| Hosts Master Multiproject on Network Share                  |
+-------------------------------------------------------------+
               |                               |
       Network Share                   Network Share
               |                               |
               v                               v
+-----------------------------+ +-----------------------------+
| Client ES 1 (Engineer A)    | | Client ES 2 (Engineer B)    |
| Opens AS1 (Charts Locked)   | | Opens AS2 (Charts Locked)   |
+-----------------------------+ +-----------------------------+

Prerequisites

Dedicated central Engineering Server (or Primary ES) hosting the master Multiproject.
Fast, switched gigabit Industrial Ethernet connection across all engineering stations.
Consistent software versions and identical hotfix levels across all ES PCs.

Step 1: Configure Multiproject Sharing on the Engineering Server

On the primary ES, locate the Multiproject directory in Windows File Explorer (e.g., D:\PCS7_Projects\Master_MP).
Right-click the folder and select Properties -> Sharing -> Advanced Sharing.
Share the folder (e.g., as Master_MP$).
In permissions, grant Full Control to the local/domain group SIMATIC HMI and authorized engineering user accounts.

Step 2: Open Sub-Projects from Engineering Clients

On secondary engineering laptops/PCs (Client ES), open SIMATIC Manager.
Select File -> Open -> Multiproject.
Browse via the UNC network path to the shared project:
\\Server_ES\Master_MP$\Master_MP.s7p
SIMATIC Manager opens the master project over the network.

Step 3: Utilize Chart Reservation and Cross-Editing Rules

SIMATIC PCS 7 manages concurrent access via internal database locks:
* Chart-Level Locking: When Engineer A opens CFC Chart FC_101, PCS 7 places a lock on that specific chart. If Engineer B attempts to open FC_101, it opens in read-only mode.
* Divided AS Responsibilities: Best engineering practice dictates assigning different automation stations to different engineers (e.g., Engineer A configures AS1, Engineer B configures AS2).
When downloading changes to a specific CPU:
* Only the engineer actively responsible for that specific AS initiates the CFC compilation and download.
* Because both engineers operate against the same shared Multiproject database, compile timestamps remain perfectly synchronized.

Verification

In SIMATIC Manager, confirm that both engineering client stations can open charts across different sub-projects simultaneously without file lock error popups.
From Client ES 1, execute a minor logic change in AS1 and perform a CPU -> Download -> Changes Only in RUN mode. Confirm clean download completion without timestamp mismatch warnings.
From Client ES 2, open an AS1 chart: verify that live dynamic test values display and that the chart reflects the edits made by Client ES 1.

Limitations and Operational Precautions

Network Stability: If the network connection between a Client ES and the Master ES drops while a chart is open, the chart may remain locked. Use SIMATIC Manager's File -> Reorganize tool on the master station to clear orphaned lock files.
Never Use USB Flash Drives for Split Editing: Never copy a project onto a flash drive, edit it offline on a laptop, and attempt to copy it back over a running project; doing so overwrites master database indexes and ruins online synchronization.
Central OS Compilation: WinCC OS compilation and Server Data generation should always be executed from the primary Master ES to maintain consistent SQL tag dictionaries.

Engineer FAQ

Can two engineers download to the same CPU at the exact same second?
No. STEP 7 serializes communication to the CPU; simultaneous download attempts will be rejected with an error stating that the communication port or database is busy.
Does Multi-User Engineering require extra licenses?
Each PC running SIMATIC Manager and CFC requires an engineering license (PCS 7 Engineering or CFC Engineering), but the project sharing mechanism itself is built into standard STEP 7 / PCS 7.
What happens if someone edits an offline backup copy at home?
Changes made to disconnected offline copies cannot be merged automatically. They must be manually recreated on the master project or merged using the Version Cross Manager (VXM).
Can an OS Client be used as a secondary Engineering Station?
An OS Client can function as an ES only if it has the complete PCS 7 Engineering software toolset and required engineering licenses installed.
What is the maximum recommended number of concurrent engineering clients?
For optimal network and database performance, Siemens recommends limiting concurrent engineering clients to between 3 and 5 per master Multiproject.

Technical References

Siemens Industry Online Support Entry ID 109801081: SIMATIC Process Control System PCS 7 - Multiproject Engineering.
Siemens System Manual: Multi-User Engineering Guidelines and Project Distribution.
Siemens Technical Guide: Version Cross Manager (VXM) and Project Synchronization.

Preventing CPU Download Conflicts and Configuring Multi-User Engineering in SIMATIC PCS 7