SIMATIC PCS 7 Open OS Licensing and Architecture Guide for Dedicated OPC Server and Client Stations

In SIMATIC PCS 7 V7.1, deploying a dedicated Industrial PC (IPC) functioning simultaneously as an OPC Server (exposing PCS 7 data to third-party systems) and an OPC Client (importing external third-party PLC data via Open OS) requires specific software licensing distribution across the Engineering Station (ES), Operator Stations (OS), and the dedicated OPC node. The Open OS Engineering package (MLFB: 6EQ2001-1XX17-3BA5) must be installed on the ES, while the Open OS Runtime package (MLFB: 6EQ2001-2XX17-3BA0) and appropriate WinCC Process Object (PO) licenses must be installed on the target OS Server. The dedicated OPC IPC requires SIMATIC NET and WinCC OpenPCS 7 licenses depending on communication direction.

SIMATIC PCS 7 Open OS Architecture and Use Cases

In hybrid industrial manufacturing facilities, the central DCS must frequently interact with non-Siemens controllers (such as Allen-Bradley ControlLogix, Modicon, or GE Fanuc):
* The Traditional Challenge: Standard PCS 7 AS-OS compilation expects native S7-400 controllers. Third-party PLCs cannot compile directly into the PCS 7 plant hierarchy.
* The Open OS Solution:
* SIMATIC PCS 7 Open OS bridges third-party automation systems into the standard PCS 7 OS environment.
* It translates third-party OPC tags, alarms, and data structures into standard PCS 7 APL-compliant block icons and faceplates.
* Dual OPC Role: A dedicated IPC can simultaneously act as an OPC Client (ingesting third-party PLC telemetry via Open OS) and an OPC Server (exporting plant telemetry to Manufacturing Execution Systems via OpenPCS 7).

Software License Distribution: ES, OS, and Dedicated OPC IPC

Correct license placement across the engineering infrastructure is critical for licensing compliance:

Engineering Station (ES):
* SIMATIC PCS 7 Open OS Engineering V7.1 (6EQ2001-1XX17-3BA5): Installed on the ES. Authorizes the Open OS engineering tool (DB-Converter and Component Configurator) to import third-party tag lists and create APL-style technological objects.
* Base PCS 7 Engineering licenses (AS/OS Engineering).
Target Operator Station (OS Server / Single Station):
* SIMATIC PCS 7 Open OS Runtime V7.1 (6EQ2001-2XX17-3BA0): Installed on each OS Server hosting third-party data.
* WinCC Runtime PO Licenses: Sufficient capacity to cover both native S7-400 process objects and third-party Open OS technological blocks.
Dedicated OPC IPC:
* If running as an OPC Server to external systems: Requires OpenPCS 7 V7.1 (6ES7658-0CX17-0YB5).
* If connecting via Industrial Ethernet: Requires SIMATIC NET SOFTNET-S7 / IE communications software.

Procurement and MLFB Reference Guide for Open OS V7.1

When preparing procurement lists and equipment schedules for PCS 7 Open OS systems:

Official Ordering Numbers:
Open OS V7.1 Engineering License: 6EQ2001-1XX17-3BA5
Open OS V7.1 Runtime License: 6EQ2001-2XX17-3BA0
OpenPCS 7 V7.1 Server License: 6ES7658-0CX17-0YB5
WinCC RT PO PowerPack: Depending on tag count (e.g., 6ES7658-2CX17-0YD0 for 1000 PO upgrade).
Always consult the official Siemens ST PCS 7 catalog and validate quotations with authorized Siemens industrial distributors before placing commercial orders.

Configuring OPC Server (OpenPCS 7) and OPC Client (Open OS)

To establish the dual-role communication workflow:

Configuring the Inbound OPC Client (Open OS):
* On the ES, use the Open OS Component Configurator to import the CSV tag database generated by the third-party PLC (e.g., Rockwell tags).
* Map third-party variables to PCS 7 APL block templates (MonAnL, MotL, VlvL).
* Compile OS: WinCC generates tags bound to the OPC Channel (OPC.ServerAE and OPC.ServerDA).
Configuring the Outbound OPC Server (OpenPCS 7):
* Install OpenPCS 7 on the dedicated IPC.
* OpenPCS 7 automatically reads WinCC process values, alarms, and historical archives from the OS Server cluster and exposes them via standard OPC DA, OPC HDA, and OPC A&E interfaces to MES/SCADA clients.

Comparison of PCS 7 Third-Party Connectivity Options

The table below compares third-party connectivity architectures in SIMATIC PCS 7.

Architecture OptionSoftware PackageTelemetry ProtocolPCS 7 Faceplate SupportTypical ApplicationPCS 7 Open OSOpen OS Eng + RTOPC DA / A&EFull APL FaceplatesComplete third-party DCS integrationOpenPCS 7 ServerOpenPCS 7 RTOPC DA / HDA / A&EN/A (Server interface)Exporting DCS data to MES / ERPWinCC OPC ChannelNative WinCCOPC DAManual static graphicsSimple raw tag exchangeModbus TCP / RTUOpen Modbus / PNModbus ProtocolCustom blocksSubstation & chiller packages

Verification

To confirm that Open OS and OPC communications operate properly:
1. On the ES, verify that the Open OS Engineering license (6EQ2001-1XX17-3BA5) reports OK in Automation License Manager.
2. In WinCC Explorer on the OS, open the OPC Channel Diagnosis: verify that the OPC connection state reports Connected with zero communication errors.
3. Open a WinCC overview graphic: verify that third-party motor and valve icons animate dynamically and clicking them opens standard APL faceplates.
4. From a remote third-party OPC client test tool (such as Matrikon or Kepware OPC Quick Client), query the OpenPCS 7 server: confirm that PCS 7 process tags and alarm events read cleanly.
5. In ALM on the OS Server, confirm that Process Object consumption accounts for both native and Open OS objects without exceeding license limits.

Limitations and Operational Precautions

Open OS relies on OPC DA (Data Access 2.0/3.0) and OPC A&E (Alarms & Events), which utilize Microsoft DCOM; ensure Windows Firewall and DCOM security permissions are configured using the SIMATIC Security Controller.
DCOM communication across different Windows workgroups requires matching local user accounts and passwords on both the OPC Server and Client nodes.
Open OS technological blocks consume standard WinCC Runtime Process Object (PO) licenses; verify that your PO capacity is sufficient before downloading.
Always validate final license quantities, MLFBs, and software compatibility against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Where should the Open OS Engineering license be installed?

The Open OS Engineering license (6EQ2001-1XX17-3BA5) must be installed directly on the Engineering Station (ES) where SIMATIC Manager and the Open OS Configurator execute.

Does Open OS support redundant OS servers?

Yes. Open OS fully supports redundant OS Server pairs; in a redundant system, an Open OS Runtime license (6EQ2001-2XX17-3BA0) must be installed on both Master and Standby OS servers.