Connect a Third-Party OPC Client to PCS 7 V9.0 SP1 with OpenPCS 7

For PCS 7 V9.0 SP1, use the documented OpenPCS 7 interface to expose OS process data to a third-party OPC client. The normal path is external client to OpenPCS 7 to the assigned OS servers, rather than directly to the CPU 410-5H's PROFINET I/O interface. Select the required OPC protocol and data scope, provide a compatible station and the appropriate OpenPCS 7 license, assign OS server packages, then commission reads and any explicitly authorized writes separately.

Choose the OS Data Interface

For the stated CPU 410-5H, two redundant OS servers and five clients, the documented OpenPCS 7 V9.0 SP1 architecture places the third-party OPC client on the OS-data side. OpenPCS 7 obtains data from the assigned OS servers and presents an OPC interface; it is not a direct OPC connection to the CPU's PROFINET I/O interface.

First agree whether the external system needs live values, historical values, alarms/events or writes. These are different interface requirements. OpenPCS 7 does not provide direct access to SIMATIC BATCH or Route Control data. OpenPCS 7 manual, chapter 3.1

Select the Station and Licenses

Siemens documents a separate OpenPCS 7 station as its preferred arrangement, with other supported placements on an OS client, single station or server subject to PC requirements.

DeploymentDocumented OpenPCS 7 licenseSeparate OpenPCS 7 computerOpenPCS 7 stationExtend an existing operator stationOpenPCS 7 station / OS

For V9.0 SP1, each OpenPCS 7 station requires its own single license, transferred locally using Automation License Manager; the manual excludes use of a license server for these licenses. The station / OS variant requires the PCS 7 OS to be in process mode. Existing OS-client licensing remains separate when that functionality is used.

The OS-internal Classic OPC servers also require one of the documented OpenPCS 7 licenses on the OS station and add OS load. Do not assume that the presence of redundant OS servers or five client licenses already licenses the new interface. Manual, chapters 4.2–4.4

Configure the OpenPCS 7 Station

After selecting compatible PC hardware, software and licensing, Siemens documents this engineering sequence for V9.0 SP1:

With the OS servers created and server packages generated, select the project in SIMATIC Manager's component view.
Choose Insert > Station > SIMATIC PC Station and set its station/computer names in object properties.
Open its hardware configuration. From SIMATIC PC Station > HMI, insert the SPOSA application.
Select Station > Save and Compile.
Expand the SPOSA application in SIMATIC Manager. In the OpenPCS 7 object's properties, configure the download path on the PLC tab.
Use Assign OS Server... to assign the required OS server packages.
Save and compile the station configuration again, then use the object's PLC > Download command.

The target needs the installed OpenPCS 7 software, configured TCP/IP terminal-bus connection and access to the required shared folder. The manual states that configuration changes take effect after restarting the OpenPCS 7 station; plan that restart as part of interface commissioning. Manual, chapters 5.1 and 5.4

Configure the External Client for the Chosen OPC Interface

The third-party OPC client is configured in its own software, not inserted as another PCS 7 PC station.

For the documented OPC UA interface, configure the client against the actual OpenPCS 7 host and configured endpoint. The V9.0 SP1 manual gives opc.tcp://[HostName]:[Port], with 4863 as the historical default port. Confirm the real configuration, network access, application-certificate trust and user authentication; a default endpoint is not evidence that the client is authorized.

For OPC Classic, the manual identifies client-side OPC core components and DCOM/firewall configuration as relevant. Do not apply Classic DCOM instructions to UA or assume the external system supports both.

Agree a restricted write list with operations and the third-party supplier. Read/write behavior must be verified for the selected items and interface; a browsable namespace does not authorize arbitrary controller writes.

Verification

Begin with agreed read-only test items. Browse the assigned server data and compare changing values, quality and timestamps against the PCS 7 OS. Add archive or alarm checks only where those interfaces are required.

For an authorized write test, use a designated test item, verify the operation result and observe the intended application response. Confirm limits and interlocks remain effective. Test the required OS redundancy scenario without assuming that OS redundancy also makes a single OpenPCS 7 PC redundant. Preserve the client reconnection and data-quality observations.

Limitations and Operational Precautions

This procedure is specific to PCS 7/OpenPCS 7 V9.0 SP1. It is an interface-commissioning baseline; the external client's product, supported OPC protocol and required data/write scope were not supplied.

Keep a project backup and a rollback plan for station configuration and restart. Do not expose the plant bus directly to an external system merely because the CPU has Ethernet. Apply the site's approved network boundaries and access policy. A successful OPC write response alone does not prove that a process command was accepted or safely executed.

Engineer FAQ

Is the external OPC client connected directly to the CPU?
In the documented OpenPCS 7 solution, it connects to the OpenPCS 7/OS-data interface, not directly to the CPU's I/O network.

Can an existing OS server host the interface?
The manual permits that placement subject to requirements and licensing, while identifying a separate station as the preferred arrangement.

Technical References

Siemens — OpenPCS 7 V9.0 SP1 Function Manual, October 2017, A5E39222196-AB — chapter 3.1 architecture; chapters 4.2–4.4 installation/licensing; chapters 5.1, 5.3–5.4 engineering and loading; chapter 7.3 UA endpoint and security configuration.

PCS 7 OPC integration

Connect a Third-Party OPC Client to PCS 7 V9.0 SP1 with OpenPCS 7