How to Connect a Third-Party OPC System to PCS 7 V9.0 SP1

For a PCS 7 V9.0 SP1 system with redundant WinCC OS servers, the documented OpenPCS 7 architecture exposes OS-server data to an external OPC client. The third-party client connects to an OpenPCS 7 station or its configured OS-side OPC server; it does not normally use the S7-410-5H as the OPC endpoint in this design. Select OPC UA or OPC DA according to the third-party client and the installed PCS 7 configuration, and engineer write access only for approved OS tags.

Choose the OPC Endpoint

PCS 7 V9.0 SP1 documentation describes third-party access to one or more PCS 7 OS servers through an OpenPCS 7 station. The station provides an OPC interface to process values and, depending on the chosen interface, messages and archived data. This places the external interface at the OS/server layer, where PCS 7 has process tags and operator-system data, instead of coupling the external system directly to CPU memory.

For the described redundant OS arrangement, a separate OpenPCS 7 station is a documented topology. Siemens notes that running OpenPCS 7 on an OS server adds load to that server and recommends a separate station for large PCS 7 plants. The five OS clients are not automatically the OPC endpoint; the OpenPCS 7 station is separately configured or added to an existing PC station.

Select the Protocol and Data Scope

The V9.0 SP1 OpenPCS 7 manual supports OPC Data Access (DA), OPC Historical Data Access (HDA), OPC Alarms and Events (A&E), and OPC UA. Choose a protocol the third-party client supports and verify that the exact PCS 7 V9.0 SP1 installation includes and licenses the selected server functionality.

OPC DA provides access to live OS process variables and supports writes to process-variable values. OPC UA in OpenPCS 7 provides access to OS tags, tag archives and OS messages; write access applies to a tag's Value attribute when permitted. Historical data access is for reading archives; Siemens explicitly states that write access to archived data through OPC HDA is not enabled. Decide which live tags, alarm data or archives the client needs before building the interface.

Check Software and Licenses

The PCS 7 V9.0 SP1 manual describes two OpenPCS 7 license choices: OpenPCS 7 station / OS, which adds OpenPCS 7 functionality to an existing OS station, and OpenPCS 7 station, for a separate OpenPCS 7 station. Each OpenPCS 7 station requires a single license on the machine where it runs. The manual also requires a PCS 7 OS license for access to PCS 7 data; with the OpenPCS 7 station / OS license, the PCS 7 OS must be in process mode.

For installation, choose the PCS 7 setup package that matches the desired station topology. The manual distinguishes a standalone OpenPCS 7 station from OpenPCS 7 functionality added to an OS client, OS server or OS single station. Confirm exact media, Windows support and license availability against the PCS 7 V9.0 SP1 Readme and the project's licenses.

Configure a Separate OpenPCS 7 Station

The Siemens V9.0 SP1 Function Manual documents this engineering sequence:

Confirm the PCS 7 project contains the OS servers and their server packages.
In SIMATIC Manager Component View, select the project and choose Insert > Station > SIMATIC PC Station.
Set the PC station name and computer name in its object properties.
Open the station's Configuration object in HW Config. From SIMATIC PC Station > HMI, insert the SPOSA application into the configuration table.
Save and compile the station configuration.
Open the OpenPCS7_Station(1) object properties and set the download path on its PLC tab.
Right-click the OpenPCS7_Station(1) object, choose Assign OS Server..., and assign the PCS 7 OS server packages that the OPC client needs to access.
Save and compile the station configuration again, then download the OpenPCS7_Station(1) object to its target PC.
Configure the OPC client outside the PCS 7 project and connect it to the OpenPCS 7 server using the selected OPC interface.

These menu names and steps are for the V9.0 SP1 OpenPCS 7 manual. Network, computer names and assigned server packages must match the actual project and station deployment.

Plan Read and Write Access

Start with a list of OS tags the third party must read or write, their data types, engineering units, update needs and safe value ranges. Confirm the client can browse and read each intended OS tag, then verify quality and timestamps where exposed by the selected protocol. For write access, confirm the OS tag and server allow writing and that the PCS 7 project's control logic, permissions, interlocks and operating procedures constrain the command appropriately.

Treat external writes as control commands: use designated command or setpoint tags, define who owns each value and how bad quality, stale data and communication loss are handled. Do not expose arbitrary internal tags or use OPC writes to bypass permissives. Historic records are not a write-back channel; HDA write access is disabled in the cited manual.

Secure and Verify the Connection

For OPC UA, configure endpoint security, trust the client and server certificates through the approved certificate process, and restrict the network path to the required peers and services. Siemens' V9.0 SP1 manual describes UA certificate-based mutual authentication and notes that incorrect server configuration can cause malfunctions or security gaps. For OPC DA, the manual identifies DA as a DCOM application and calls for client, firewall and DCOM configuration; keep Classic OPC traffic inside a controlled network segment and allow only necessary communications.

Verify the complete data path: the external client connects to the intended endpoint, reads a known live OS tag, and receives a controlled test write on an approved noncritical tag. Confirm the write reaches the intended process value and that normal PCS 7 logic and operator indication respond. Test alarm or archive access separately if those services are required. Record recovery behavior for network loss and redundancy switchover.

Verification

Confirm the OpenPCS 7 station is licensed, configured, compiled and downloaded; the relevant OS server packages are assigned; and the OS servers are operating. Verify the OPC client can reach the station over the intended network path and browse the expected OS namespace. Test representative live values, permitted writes, and any required messages or archives. The final acceptance test should include the actual redundant-server behavior and client's response to a server/network interruption.

Limitations and Operational Precautions

The source system's exact OPC client, target protocol, tag list, network zones and desired write semantics are not specified, so these design choices require project-specific engineering. The cited OpenPCS 7 Function Manual is for V9.0 SP1; use Readmes and security guidance matching the installed build. OPC HDA archive writes are disabled. OpenPCS 7 on an OS server adds performance load; Siemens recommends a separate station for large plants. Writing process values can change plant operation, so use approved tags, access control, interlocks, change management and tested fallback behavior.

Engineer FAQ

Does the third-party system connect directly to the S7-410-5H? The documented PCS 7 V9.0 SP1 OpenPCS 7 arrangement gives the client access through the OS-server layer. A direct CPU connection would be a separate design that requires its own support and security review.

Can the client read and write PCS 7 values? OpenPCS 7 supports process-tag access, and write access is available for permitted live values. Engineer the writeable OS tags and control behavior explicitly.

What does the redundant OS architecture change? Assign the appropriate OS server packages to the OpenPCS 7 SPOSA application and validate the client against the redundant-server design and switchover behavior.

Do I need a separate OpenPCS 7 PC? Not in every topology. V9.0 SP1 supports OpenPCS 7 on supported OS station types, but the manual recommends a separate station for large systems because hosting it on an OS server adds load.

Which license is needed? The manual lists OpenPCS 7 station / OS and OpenPCS 7 station; the choice depends on whether functionality is added to an OS station or installed on a separate station. PCS 7 OS licensing also applies.

Can OPC HDA write archived values? No. The V9.0 SP1 manual says write access to archived data through OPC HDA is not enabled.

Should the client use OPC UA or OPC DA? Choose the protocol supported by the third-party client and the target PCS 7 build. Confirm supported interfaces, security, tag access and the required license before implementation.

What network work is required for OPC DA? The manual identifies OPC DA as DCOM-based and calls for appropriate client, firewall and DCOM configuration. Restrict those communications to the required stations and networks.

How should external writes be tested? Test a deliberately selected noncritical OS tag under controlled conditions, verify that the value and intended control response occur, and confirm access restrictions and failure behavior.

Can I use an OS client as if it were an OpenPCS 7 station? Only if it has been installed and configured with the OpenPCS 7 functionality and license. An OS client by itself is not evidence that the OpenPCS 7 endpoint is configured.

Technical References

Siemens, OpenPCS 7 (V9.0 SP1) Function Manual, 10/2017, A5E39222196-AB: sections 4.2–4.4 (station installation and licensing), 5.1 (SPOSA configuration), 6.3 (OpenPCS 7 with OS), 7.3 (OPC UA), and 7.4–7.6 (OPC DA, HDA, A&E). Open the Siemens manual.
Siemens, SIMATIC PCS 7 V9.0 SP1 Licenses and Configuration Limits, A5E39222309-AB, section 4.3, “Software and license keys for Operator Stations.” Open the Siemens licensing manual.

How to Connect a Third-Party OPC System to PCS 7 V9.0 SP1