Implementing Multi-User Engineering and Multiproject Workflows in SIMATIC PCS 7

Implementing Multi-User Engineering and Multiproject Workflows in SIMATIC PCS 7

In SIMATIC PCS 7, collaborative engineering across distributed teams is achieved through Multi-User Engineering and Multiproject workflows rather than cloud-style check-in/check-out repositories. While TIA Portal uses a Multiuser Server with local session branching, PCS 7 utilizes a centralized multiproject hosted on an Engineering Station (ES) server. Multiple engineers concurrently edit distinct Continuous Function Charts (CFC) or Operator Station (OS) graphics across network shares, while global technological operations—such as NetPro compilation, cross-AS interconnections, and OS compiles—are centralized on the primary ES server.

Table of Contents

Comparison: PCS 7 Multiproject Engineering vs TIA Portal Multiuser

Automation engineers transitioning between TIA Portal and SIMATIC PCS 7 must understand their divergent collaborative architectures:

  • TIA Portal Multiuser Engineering: Built around a centralized Project Server repository. Engineers create local working sessions on their laptops, work offline, test logic in PLCSIM, and execute a "Check-In / Refresh" routine that merges changes into the server database using automated conflict resolution.
  • SIMATIC PCS 7 Multiproject Architecture: Built around a shared, live distributed database structure. A Multiproject binds multiple single Automation Station (AS) projects, Operator Station (OS) projects, and a shared master library into a single logical umbrella. There is no automated branch-merge engine; instead, engineers work directly on shared project files across authenticated Windows SMB network shares or temporarily remove and re-insert subprojects.

The Central Engineering Station (ES Server) Architecture

A robust PCS 7 multi-user engineering setup requires an Engineering Station (ES Server) configured to host project repositories:

  • Operating System Selection: While smaller projects can technically be hosted on Windows 10/11 Pro workstations, plant environments should host central multiprojects on Windows Server (e.g., Server 2016, 2019, or 2022) to avoid Windows desktop SMB client connection limits (maximum 20 concurrent connections on Windows 10/11).
  • Network Permissions:
  • Multiproject folders must be shared across the Terminal Bus.
  • Engineers must authenticate with Windows user accounts belonging to Administrators and SIMATIC HMI on the host server.
  • Share permissions and NTFS security must grant Full Control.
  • Simatic Shell Synchronization: All engineering workstations must bind Simatic Shell to the same network interface and share identical network encryption settings.

Distributed Editing of CFC Charts and Multi-Client OS Engineering

PCS 7 supports concurrent engineering across different technological domains:

  1. Concurrent CFC Editing:
    * Multiple engineers on separate ES clients can simultaneously open SIMATIC Manager, browse the shared multiproject, and edit different CFC charts within the same automation station.
    * Real-time database locking prevents two engineers from opening the exact same chart simultaneously.
  2. OS Multi-Client Engineering:
    * Engineers can simultaneously edit WinCC process graphics (.pdl), C-actions, and VBS scripts in Graphics Designer on client workstations while the master project resides on the ES server.
    * Modifying technological block types or generating block icons requires centralized coordination.
  3. Subproject Check-Out Model (Remove from Multiproject):
    * For major commissioning work, an engineer can right-click an AS project in SIMATIC Manager and select Multiproject -> Remove from Multiproject.
    * The subproject is moved locally to the engineer's laptop, edited, compiled, and tested offline, then re-integrated using Multiproject -> Insert into Multiproject.
+-------------------------------------------------------------------+
|               PCS 7 Multi-User Engineering Model                  |
+-------------------------------------------------------------------+
|  Central ES Server (Windows Server)                               |
|  - Master Multiproject Database & Shared Master Data Library      |
|  - Coordinates Global Compilations, NetPro, & AS-Wide Links       |
|                             |                                     |
|        +--------------------+--------------------+                |
|        | (SMB Share / Terminal Bus)              |                |
|        v                                         v                |
|  ES Client 1 (Engineer A)                  ES Client 2 (Engineer B)|
|  - Editing CFC Charts in AS1               - Designing WinCC OS   |
|  - Online Test Mode in Unit 1              - Modifying Graphics   |
+-------------------------------------------------------------------+

Centralized Global Tasks: NetPro, Cross-AS, and OS Compilation

While chart editing is decentralized, certain architectural operations must strictly be executed locally on the Central ES Server:

  1. AS-Wide Interconnections: Interconnecting signals between two different automation stations across the plant bus requires central compilation to generate communication communication buffers (S7_COMM).
  2. NetPro Network Compilations: Compiling global network routes, S7 connections, and subnets must be performed on the host server to ensure consistent cross-project connection tables.
  3. OS Compilation (Compile OS): Never execute an OS compile from a remote ES client over network shares. Network latency dramatically slows down SQL Server table writes, turning a 20-minute compile into a multi-hour process. Always initiate OS compiles locally on the ES server.

Verification

Confirm multi-user engineering collaboration:

  1. Concurrent Access Test:
    * Have Engineer A open CFC Chart 1 on ES Client 1.
    * Have Engineer B open CFC Chart 2 in the same AS project on ES Client 2.
    * Confirm that both charts open in Read/Write mode without lock collisions.
  2. Lock Enforcement Test:
    * Have Engineer B attempt to open CFC Chart 1 while Engineer A has it open.
    * Confirm that PCS 7 displays the lock prompt indicating that the chart is currently being edited by Engineer A.
  3. Shared Library Synchronization:
    * Update a block type in the Master Data Library on the ES server.
    * Execute Options -> Charts -> Update Block Types... across the multiproject. Confirm that all subprojects receive the updated block header.

Limitations and Operational Precautions

  • No Branch Merging: PCS 7 does not support Git-style branch merging; two engineers cannot edit different parts of the same CFC chart and merge changes automatically.
  • Network Latency Sensitivity: Multi-user engineering over high-latency VPN or Wi-Fi links causes database lock timeouts and file corruption. Remote engineering should utilize Remote Desktop (RDP) into local ES clients rather than direct SMB file sharing.
  • Version Parity Mandate: Every participating engineering station must run the exact same PCS 7 version, service pack, and CFC hotfix level.

Engineer FAQ

  • Does PCS 7 have a multi-user check-in/check-out server like TIA Portal?
    No, PCS 7 utilizes a shared Multiproject architecture where engineers work directly on shared network databases or remove/re-insert subprojects.
  • Can two engineers edit the same CFC chart at the same time in PCS 7?
    No, PCS 7 enforces object-level locking; only one engineer can open a specific CFC or SFC chart for editing at any given moment.
  • Can multiple engineers edit different charts in the same AS project concurrently?
    Yes, multiple engineers can open and edit distinct CFC charts within the same automation station simultaneously.
  • Why should OS compilations never be started from an ES client?
    Compiling an OS across network shares introduces severe network latency into SQL database transactions, drastically increasing compile times.
  • What operating system is recommended for the central Engineering Station?
    Windows Server (2016, 2019, or 2022) is recommended to prevent Windows 10/11 desktop SMB connection limits (max 20 concurrent connections).
  • What is the purpose of the Master Data Library in a multiproject?
    The Master Data Library holds standard corporate block types, SFC types, and templates, ensuring all subprojects utilize uniform technological blocks.
  • How do AS-Wide interconnections work in a multiproject?
    Engineers can interconnect block pins across different automation stations; PCS 7 automatically generates underlying S7 communication drivers during compilation.
  • What happens if an ES client abruptly disconnects while editing a chart?
    The host server holds the SMB file lock until network timeouts expire, requiring manual handle closure in Computer Management (compmgmt.msc).
  • Can WinCC graphics be edited by multiple engineers concurrently?
    Yes, engineers can simultaneously edit different process pictures (.pdl) across client workstations via OS multi-engineering.
  • What software is used to track engineering changes in PCS 7?
    SIMATIC Version Trail and Version Cross Manager track project archives, revisions, and detailed block/parameter differences.

Technical References

  • Siemens Industry Online Support (SIOS) Portal: What should you watch out for in multi-user engineering in PCS 7? (Entry ID: 22258957).
  • SIMATIC PCS 7 Engineering System Configuration Manual, Siemens AG.
  • SIMATIC PCS 7 Compendium Part A - Configuration Guidelines, Siemens AG.

Related Articles

Related Tags

PCS 7, Multi-User Engineering, Multiproject, TIA Portal, Engineering Station, CFC, Master Data Library, Collaboration

20 respuestas