Implementing Multiuser Engineering and Central Project Sharing in SIMATIC PCS 7 V8

To implement collaborative Multiuser Engineering in SIMATIC PCS 7 V8 across multiple Engineering Stations (ES1 and ES2), the project must be structured as a Multiproject and hosted on a dedicated central Engineering Server running Windows Server with PCS 7 Engineering software installed. Generic file shares, NAS appliances, or unmanaged servers are strictly unsupported because STEP 7 and WinCC rely on Microsoft SQL Server instances and operating system file locking. Multiple engineers can concurrently edit separate subprojects within the shared multiproject. To prevent authentication deadlocks, ensure all engineering workstations and the central server belong to the same Windows domain with matching user privileges.

Executive Summary

Large-scale automation projects executed in SIMATIC PCS 7 V8 require concurrent engineering: multiple software engineers must author CFC charts, configure hardware, develop SFC sequences, and design WinCC graphics simultaneously to meet tight commissioning milestones. Automation leads frequently consider hosting the master project archive on a centralized corporate file server (or commercial NAS storage) accessible over the local area network. However, engineers frequently encounter database corruption, file lock errors, or access denial dialogs when attempting to open a single project from multiple PCs. Understanding the architectural constraints of SIMATIC Manager, the mandatory deployment of Multiprojects, and the role of an Engineering Server ensures safe, concurrent multi-developer workflows.

Multiuser Engineering Architecture in SIMATIC PCS 7

PCS 7 Multiuser Engineering is governed by relational database rules:

Distributed Project Framework: SIMATIC Manager organizes plant automation into a Multiproject, which serves as an umbrella container housing multiple independent User Projects (e.g. AS_Unit1, AS_Unit2, OS_Server, Master_Data_Library).
Independent Database Containers: Each user project maintains its own isolated database tables and folder structure.
Concurrent Access Rule: Multiple engineers can open the master Multiproject simultaneously, provided each engineer edits a distinct subproject.

Why Generic NAS Appliances and Simple File Shares Fail

Attempting to host PCS 7 projects on unmanaged Network Attached Storage (NAS) or Linux Samba shares fails catastrophically:

Microsoft SQL Server Dependencies: WinCC OS projects embed Microsoft SQL Server databases (*.mdf / *.ldf). SQL Server strictly prohibits mounting database files over standard SMB/CIFS network shares.
Windows Locking Protocols: STEP 7 cross-reference tables rely on Windows opportunistic locking (oplocks) and precise COM class serialization that Samba cannot emulate.
Required Solution: The central storage repository must be a certified Engineering Server PC running Windows Server with the PCS 7 Engineering Station software package installed.

Multiproject vs Single Project: Concurrency and Database Locks

If an automation system is configured as a Single Project (non-multiproject):

Only one engineer can open and edit the project at any given time.
If Engineer 1 opens a chart, the entire chart folder is locked. A second engineer attempting to open the project receives an immediate error: 'The project is already in use by another application or workstation'.
Solution: Convert the single project into a Multiproject by creating a new Multiproject container and moving independent AS controllers and OS projects into separate subprojects.

Multiuser Engineering Topologies Comparison

The following table compares architectural topologies for collaborative PCS 7 engineering:

Engineering ArchitectureStorage PlatformSupported ConcurrencyWinCC OS Editing Allowed?Data Integrity RatingCentral Engineering ServerWindows Server with PCS 7 ESMultiple Subprojects (High)Yes (via Network Project)100% Certified / SafeBranch / Merge (Check-out)Local ES PCs (Git / SMMC)Offline Branch EditingYes (Local)High (Merge via VXM)Generic NAS / Samba ShareLinux NAS / Shared DriveNone (Database Corruption)Prohibited by SQL ServerSevere Corruption RiskSingle Project Network ShareWindows Workstation ShareStrict Single-User OnlySingle-User OnlySafe, but zero concurrency.

Step-by-Step Procedure to Configure Shared Multiproject Engineering

Method: Setting up a Central Engineering Server Environment

Provision a high-performance central PC as the Engineering Server running Windows Server 2008 R2 and PCS 7 V8.1 ES.
Join the Engineering Server and all client Engineering Stations (ES1, ES2) to the same active Windows Domain.
Create a dedicated project directory on a high-speed local drive (e.g. D:\PCS7_Multiprojects\).
Share the folder across the network with Full Control permissions granted to the domain user group SIMATIC HMI.
In SIMATIC Manager on the Server, select File > 'New...' > Multiproject.
Insert separate subprojects for each physical Automation Station (e.g. AS01_Project, AS02_Project) and the Master Data Library.
On client workstation ES1, open Windows Explorer, map a network drive to the server share (Z:\), and open Z:\Multiproject.s7m.
Engineer 1 opens and edits AS01_Project.
On client workstation ES2, Engineer 2 opens Z:\Multiproject.s7m and edits AS02_Project concurrently.
Inter-project connections and cross-references update dynamically without file locking conflicts.

Verification

To verify concurrent multiuser engineering functionality:

Simultaneous Access Check: Open the shared multiproject on both ES1 and ES2 simultaneously. Confirm that SIMATIC Manager opens with zero access warning dialogs.
Concurrent Chart Editing: Open a CFC chart in AS01 on ES1, and a CFC chart in AS02 on ES2. Edit and save logic concurrently; confirm successful saves.
Cross-Project Compilation: From the Server, execute Options > Charts > Compile All. Confirm that all subproject charts compile cleanly into their respective target containers.

Limitations and Operational Precautions

Never Edit the Same Subproject Concurrently: Two engineers cannot edit the same S7 subproject or CFC chart folder at the same time; coordinate subproject assignments across the engineering team.
Master Data Library Ownership: Designate one lead engineer to manage the Master Data Library (MDL) to prevent conflicting block type updates.
Domain Authentication: Avoid mixed workgroup/domain environments; NTLM credential mismatches trigger remote DCOM access failures during cross-station compiling.

Engineer FAQ

Can two engineers edit the same WinCC OS project simultaneously?

No. A WinCC OS project is bound to a single SQL Server database instance; only one user can edit Graphic Designer or Tag Management at a time.

What tool compares changes if engineers work on offline detached copies?

The SIMATIC Version Cross Manager (VXM) allows graphical block-by-block comparison and synchronization between detached projects.

Can Engineering Clients compile the entire multiproject over the network?

Yes, provided network latency is low; however, compiling large multiprojects is fastest when executed directly on the central Engineering Server.

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=multiuser-engineering
https://industrialautomation.net/search?query=multiproject
https://industrialautomation.net/search?query=engineering-station

6 respuestas

Implementing Multiuser Engineering and Central Project Sharing in SIMATIC PCS 7 V8