Integrating Standalone WinCC Projects into SIMATIC PCS 7 Multi-Projects: AS-OS Transfer and Read-Only Tags

In SIMATIC PCS 7, importing a standalone WinCC project into an S7 multi-project locks tag addressing into 'Read-Only' in WinCC Tag Management because PCS 7 enforces Automation Station (AS) logic as the single source of truth. In an integrated PCS 7 system, engineers do not manually type memory addresses in WinCC; instead, the OS compilation wizard automatically derives structure types, tags, and addresses from CFC technological blocks marked with 'S7_m_c'. To establish communication, configure the PC Station in HW Config with a WinCC Application and network adapter, configure a Named Connection in NetPro, and execute Compile OS.

The Architectural Divide: Standalone WinCC vs Integrated PCS 7 OS

Engineers transitioning from standalone Siemens WinCC (SCADA) to SIMATIC PCS 7 often experience paradigm shock when attempting to manage tags:
* Standalone WinCC Paradigm (Classic SCADA):
The engineer opens WinCC Tag Management, creates an S7 Protocol Suite channel driver, manually creates tags (e.g., Motor1_Start), and explicitly enters the PLC memory address: DB100.DBX0.0 or MW 20.
* The Integrated PCS 7 Paradigm (DCS Architecture):
In PCS 7, WinCC is not a detached software package; it is an integrated Operator Station (OS) component managed entirely by SIMATIC Manager.
* The Core Principle:
All technological entities, tags, alarm messages, and archive parameters originate in the Automation Station (AS) within Continuous Function Charts (CFC). The OS compilation engine acts as an automated bridge, generating WinCC tag dictionaries automatically.

Why WinCC Tag Management Addresses Display as Read-Only in PCS 7

When an engineer imports an existing WinCC project into a PCS 7 multi-project and opens Tag Management:
* The Symptom: Clicking on a tag's address field reveals that the memory address property is grayed out, displaying the notification:
The address parameter is read-only. It is managed by the engineering system.
* The Architectural Reason:
Once a WinCC project is bound to a SIMATIC PC Station inside an S7 Multi-project, SIMATIC Manager sets an internal database lock flag.
* Preventing Data Corruption:
In PCS 7, the CFC compiler dynamically assigns Data Block (DB) numbers and memory offsets during compilation. If an engineer were permitted to manually change an address in WinCC (e.g., changing DB50 to DB60), the next CFC delta compilation would overwrite that memory, severing operator control or sending commands to the wrong field actuator. Therefore, manual address editing is strictly prohibited by design.

The Role of the S7 Multi-Project as the Single Source of Truth

In a compliant PCS 7 project, every operator interface element begins in the S7 Program:
1. The Attribute { S7_m_c := 'true' }:
Function Blocks (such as MotL, VlvL, or custom SCL blocks) declare { S7_m_c := 'true' } on their block definition and on specific parameters (e.g., StartAut, SP, PV_Out).
2. Plant Hierarchy Organization:
CFC charts are placed inside technological hierarchy folders (e.g., Plant1 > AreaA > Boiler).
3. The AS/OS Transfer (Compile OS):
During OS compilation, the wizard:
* Translates the plant hierarchy into the WinCC Picture Tree Manager.
* Creates WinCC Structure Types matching the block definitions.
* Generates instance Structure Tags linked via Named Connections.
* Compiles WinCC Alarm Logging messages with exact CPU timestamps.

Configuring the SIMATIC PC Station and NetPro Named Connections

For an imported WinCC project to successfully compile and connect to an S7 controller, its communication pathway must be established in the engineering tools:

The SIMATIC PC Station:
In SIMATIC Manager, insert a SIMATIC PC Station. Its name must match the physical computer name of the OS machine.
Hardware Configuration (HW Config):
Slot 1: WinCC Application (represents the runtime SCADA engine).
Slot 3: IE General (or CP 1623, representing the plant bus network adapter).
NetPro Connection Routing:
In NetPro, select WinCC Application and insert an S7 connection (or Named Connection) targeting the S7-400 CPU's S7 program. This establishes the symbolic communication endpoint (S7$Program).

Comparison Table: Standalone WinCC vs Integrated PCS 7 OS Architecture

The following table contrasts the standalone WinCC workflow against integrated PCS 7 OS engineering:

| Engineering Dimension | Standalone WinCC SCADA | Integrated PCS 7 Operator Station (OS) |
|---|---|---|---|
| Tag Creation | Manually entered in Tag Management | Automatically compiled from CFC (S7_m_c) |
| Address Parameter Editing | Fully editable (Read/Write) | Strictly Read-Only (Managed by AS) |
| Alarm Configuration | Manually entered in Alarm Logging | Automatically generated from Alarm_8P in CFC |
| Communication Driver | Standard TCP/IP / S7 Protocol Suite | Named Connections (via NetPro) |
| Screen Navigation | Manually drawn buttons & scripts | Automatically generated via Picture Tree Manager |
| Delta Engineering | Manual updates on both PLC & SCADA | One-click automated delta compile across AS & OS |
| Recommended Deployment | Simple machine HMIs / third-party PLCs | Full-scale industrial DCS installations |

Step-by-Step Procedure to Integrate and Compile an OS in PCS 7

Follow this verified engineering procedure to properly integrate and compile a WinCC OS project:

Insert SIMATIC PC Station in SIMATIC Manager:
* Right-click the Multi-project > Insert New Object > SIMATIC PC Station.
* Rename the station to match the Windows Computer Name of the OS machine.
Configure Virtual Rack in HW Config:
* Open HW Config for the PC Station.
* From the catalog, insert WinCC Application into Slot 1.
* Insert IE General (or CP 1623) into Slot 3 and bind to the Plant Bus subnet.
* Save and compile HW Config.
Configure Named Connection in NetPro:
* Open NetPro.
* Select the WinCC Application in the PC Station.
* Insert New Connection > Select S7-400 CPU > Connection Type: S7 connection (Named Connection).
* Save and compile NetPro.
Link Existing WinCC Project:
* In SIMATIC Manager Component View, expand the PC Station > WinCC Application.
* An OS object appears. Right-click > Open Object (opens WinCC Explorer).
* If migrating an existing project, use File > Open within WinCC to link the database.
Execute OS Compilation:
* In SIMATIC Manager, right-click the OS object > Compile.
* Advance through the wizard: Select the target S7-400 AS, select the Named Connection, and choose Scope: Entire project.
* Complete the wizard; verify that all tags and alarms compile with 0 errors.

Verification

Verify that OS integration and communication operate deterministically:
1. In WinCC Explorer, open Tag Management; verify that all structure tags display the green connected symbol and point to the Named Connection (S7$Program).
2. Open WinCC Channel Diagnosis (WinCCChannelDiagnosis.exe) in runtime; verify that Named Connections reports status "Ready" with active cyclic telegram exchange.
3. Open a process graphic; confirm that block icons and numeric displays show live plant measurements without gray overlays or question marks.
4. Trigger an alarm in CFC; confirm that the alarm instantly displays in the WinCC Alarm Control with accurate CPU timestamping.

Limitations and Operational Precautions

Never Break Database Integration: Never attempt to convert an integrated PCS 7 OS project back into a standalone project by deleting internal database references. Doing so breaks plant hierarchy links and corrupts faceplate script bindings.
Computer Name Consistency: The SIMATIC PC Station name in SIMATIC Manager must match the physical Windows Computer Name exactly (case-sensitive). A mismatch prevents Station Configuration Editor from activating the virtual rack.
Redundant Server Packages: In redundant OS server systems, always execute OS compilation targeting the Master OS server, and generate server data packages for client stations.
Commercial Accuracy: PCS 7 OS Engineering and Runtime packages (6ES7658-2CX58-0YB5) are tiered by Process Object (PO) volume. Validate license allocations with an authorized Siemens distributor quotation.

Engineer FAQ

Can I create internal tags manually in an integrated PCS 7 WinCC project?

Yes. You can freely create internal WinCC tags (tags residing in the 'Internal Tags' folder) for local scripting and navigation. The read-only restriction applies exclusively to external S7 communication tags managed by the AS/OS compiler.

What happens if I rename an S7 block in CFC after compiling the OS?

Renaming a block in CFC changes its technological path. During the next OS compilation, the compiler generates a new set of tags matching the new name and deletes the obsolete tags from WinCC Tag Management.

Why didn't my connection appear in the OS Compile wizard initially?

The connection only appears in the wizard if a valid S7 connection or Named Connection has been configured between the WinCC Application and the S7 CPU in NetPro, and saved and compiled cleanly.

Can a non-Siemens PLC be connected to an integrated PCS 7 WinCC station?

Yes. You can add third-party channel drivers (such as Modbus TCP or OPC DA/UA) into the integrated WinCC project to communicate with third-party PLCs, while PCS 7 controllers communicate via Named Connections.