Configuring Substation SCADA with Siemens WinCC V12 Limits

Configuring Substation SCADA with Siemens WinCC V12 Professional

Substation monitoring sits at the boundary between factory automation SCADA and energy automation SCADA. WinCC V12 Professional, released as part of SIMATIC TIA Portal V12, is a competent factory/process HMI/SCADA product, but its native protocol stack and library set are designed for PLC-centric plant networks rather than IEC 61850 substations. This reference explains the boundary, walks through what can still be done with WinCC V12 when no budget exists for a new platform, and documents the proper Siemens product lines (SICAM PAS, SICAM SCC, PCS 7 Power Control, SIMATIC Energy Suite) for full substation SCADA deployments.

1. Why the Question Comes Up Repeatedly

Engineers familiar with WinCC Comfort/Advanced/Professional often assume that because the runtime can connect to a SIMATIC S7-1500 over PROFINET, and because the same S7-1500 can be programmed to talk to almost anything, the same path will work for a substation. That assumption breaks in three places:

• Protocol mismatch. Substation IEDs (Intelligent Electronic Devices) speak IEC 61850 MMS, IEC 61850 GOOSE, and IEC 60870-5-101/103/104, not S7 or PROFINET. None of those four utility protocols are in the WinCC V12 driver catalogue.
• Data model mismatch. IEC 61850 carries a fixed, object-oriented data model (Logical Device → Logical Node → Data Object → Data Attribute) with a strict naming convention (e.g., PROT/PIOC1$ST$Loc$stVal). WinCC V12 tags are flat, tag-database structures with no native LN hierarchy.
• Determinism and time synchronization. Substation SCADA relies on IEEE 1588 / IEC 61850-9-2 sampled values with sub-millisecond time stamping. WinCC V12 PC stations are Windows-based SCADA hosts that do not provide the hard real-time, PTP-aware, multicast-supporting substrate GOOSE/SV require.

2. WinCC V12 Professional – Technical Profile and Channel Set

WinCC V12 Professional is the SCADA/HMI runtime bundled with TIA Portal V12 (released Q4 2013, mainstream support ended in 2018). Engineers considering its use today should weigh the lifecycle position against modern TIA Portal releases.

The driver list is the deliverable defined in the TIA Portal V12 Help under "WinCC Professional – Communication – System connections". If the source device is not in this list, WinCC V12 cannot read it directly.

3. Substation Protocol Stack – What the IED Actually Speaks

Before any SCADA choice is made, document the actual IED list. Most modern protection relays in a greenfield substation will advertise at least the following:

The standards are documented at the IEC Webstore (IEC 61850-6 SCL, IEC 61850-7-4 LN catalogue, IEC 61850-8-1 MMS mapping, IEC 60870-5-101/103/104). Treat them as documents to verify against for every project – the editions, conformance blocks, and logical-node revisions evolve.

4. Architecture Options When WinCC V12 Must Be Used

Three viable architectures exist. Pick the one that matches the project's risk tolerance and the available hardware.

4.1 Architecture A – OPC UA bridge from a SICAM PAS substation controller

+----------+   IEC 61850 MMS   +-------------+   OPC UA    +-------------------+
| SIPROTEC | <--------------> | SICAM PAS   | <---------> | WinCC V12 Pro     |
| 5 relays |   IEC 60870-5-104| (substation |             | OPC UA Client     |
| meters   |                  | controller) |             | driver            |
+----------+                  +-------------+             +-------------------+

This is the recommended "soft" path. SICAM PAS (Power Automation System) acts as the substation controller; it terminates IEC 61850 from bay-level IEDs and exposes the cleaned-up data model through its built-in OPC DA / OPC UA server. WinCC V12 Professional imports that server via the OPC UA client channel. Refer to the SICAM PAS product documentation for available OPC items and licensing. Because SICAM PAS also handles IEC 60870-5-101/103/104 toward upstream control centres, it can run alongside a WinCC V12 monitoring station without protocol conflict.

4.2 Architecture B – S7-1500 gateway with IEC 60870-5-104 library

+----------+   IEC 61850      +-------------+   S7 comm   +-------------------+
| SIPROTEC | <--------------> | S7-1500     | <---------> | WinCC V12 Pro     |
| relays   |   via 3rd-party  | with 104    |             | S7-1500 driver    |
|          |   or SIP5 CM    | library     |             |                   |
+----------+                  +-------------+             +-------------------+

This architecture is fragile and should only be chosen when no SICAM PAS hardware can be procured. The S7-1500 can terminate IEC 60870-5-104 using a third-party communication library (such as the libIEC61850 stack compiled into a S7-1500 user program, or commercial add-ons). Maintenance of these libraries is on the integrator. For IEC 61850 MMS specifically, the SIPROTEC 5 Communication Manual 7KE85 describes the SIP5-COM module that can map a limited MMS dataset to S7-tag-compatible formats.

4.3 Architecture C – Replace WinCC V12 with SICAM SCC

If the budget and project scope allow, the cleanest path is to replace the WinCC V12 SCADA host with SICAM SCC (Substation Control Center) or SICAM WEB. These products speak IEC 61850 and IEC 60870-5-101/103/104 natively, ship with electrical-symbol libraries, and provide bay-control, alarm-of-record, and sequence-of-event recording already aligned with IEC 61850 reporting models. Switching from WinCC V12 to SICAM SCC requires retraining on the SICAM SCC configurator and re-acquiring license dongles, but eliminates every protocol-conversion risk.

5. Configuration Procedure – Architecture A (OPC UA bridge)

The following procedure assumes Architecture A with a SIPROTEC 5 bay, SICAM PAS 8.x, and WinCC V12 Professional on Windows 7 / Windows Server 2008 R2.

5.1 Prerequisites

• TIA Portal V12 SP1 Update 5 or later installed.
• WinCC V12 Professional license (16, 256, 1024, 4096, 65k PowerTags variants).
• SICAM PAS 8.x installed on a separate engineering/server PC, with the OPC UA server role licensed.
• SIPROTEC 5 DIGSI 5 project with IEC 61850 dataset configured (at minimum dataset Dataset_control and Dataset_measurement exposed by the relay).
• Network: bay-level IEC 61850 traffic on a managed switch VLAN separate from the office VLAN; OPC UA traffic on the SCADA VLAN; firewall rule allowing TCP 4840 between SICAM PAS and WinCC host.

5.2 Step-by-step

1. Configure the IEC 61850 dataset in DIGSI 5. Open the SIPROTEC 5 project, navigate to Communication → IEC 61850 → Datasets, and ensure the following logical-node data objects are exposed:
   • CTRL/CILO1$ST$Loc.stVal – bay-level local/remote status
   • CTRL/CSWI1$CO$Pos$Oper – controllable breaker
   • MMXU1$MX$TotW – active power total
   • MMXU1$MX$TotVAr – reactive power total
   • MMXU1$MX$Hz – system frequency
   • PIOC1$ST$Str$general – protection start (GOOSE)
   Compile and download to the relay.
2. Map the IEC 61850 points into SICAM PAS. In SICAM PAS Manager, run IEC 61850 import, point it at the IED's CID/SCD file exported from DIGSI 5, and assign each data object to a process tag in the SICAM PAS information model.
3. Activate the OPC UA server in SICAM PAS. Under System Configuration → OPC, enable the OPC UA server, configure the server endpoint (default opc.tcp://<host>:4840), and generate a user certificate with read/write rights for the WinCC V12 host.
4. Configure the OPC UA client channel in WinCC V12. In the TIA Portal project tree, open Devices & Networks → [WinCC station] → OPC UA Client and add a new connection. Enter the SICAM PAS endpoint URL and import the OPC UA namespace exported from SICAM PAS as a CSV / UANodeSet XML.
5. Map OPC UA nodes to WinCC tags. Use the bulk editor to map each OPC UA node to a WinCC tag. Recommended tag-naming convention: [Substation]_[Bay]_[Signal], e.g., SUB1_INC1_BKR_Pos, SUB1_INC1_TotW.
6. Build the HMI screens. Use the WinCC library "SICAM Electrical Symbols" if available (separately licensed), or import a third-party electrical symbol set. Keep the alarm log window open during commissioning to verify OPC UA subscription state changes.
7. Configure user rights for control operations. In WinCC V12 User Administration, create a "Bay Operator" group with permission Operate only for the CTRL/CSWI1 tags. Never grant operate rights to anonymous or default users – IEC 61850 control commands are reversible only within the relay's SBOEs (Select-Before-Operate) timeout window.

6. Sample Tag Mapping and Alarm Class Configuration

For alarm classes, the WinCC V12 default taxonomy (Errors / Warnings / Information) is inadequate for substation operations. Configure custom classes aligned with the IEC 61850 quality flags: "Protection trip", "Breaker failure", "Bay alarm", "Measurement out-of-range", "Communication loss", and "Control select-timeout".

7. Verification and Commissioning Checks

Before declaring the WinCC V12 substation SCADA ready, run the following checks and record the results in the commissioning report.

1. OPC UA connection state. Force a network disconnect between SICAM PAS and the WinCC host for at least 60 s, restore, and verify that WinCC automatically re-subscribes within the configured keep-alive timeout (default 10 s). Check the OPC UA Client – Diagnostics view for session state transitions.
2. Report latency. Trigger an IEC 61850 data change in the relay (e.g., toggle a status input) and measure the time from the physical change to the alarm appearing in WinCC. Expected budget: ≤ 2 s for MMS reporting with buffering-on-deregister disabled. If higher, reduce the Buffered-Report integrity period in the IED configuration.
3. Control authority conflict. Issue a "Select" command from WinCC, then attempt a second select from the local panel. The relay should reject one of the two per ControlModel = sbo-with-enhanced-security. Verify the alarm Authority conflict fires on the rejected request.
4. Time synchronization. Confirm the WinCC host is synchronised to the substation master clock (typically PTP grandmaster or IRIG-B). Check MMXU1$MX$Hz$mag$t timestamp accuracy against the master clock; deviation should not exceed 100 ms. WinCC V12 cannot be the PTP master; deploy a dedicated PTP grandmaster on the substation network.
5. Redundancy test. If the project uses PRP or HSR redundancy (IEC 61850-3), shut down one network path and verify zero loss of SCADA reporting. WinCC V12 only consumes redundancy at the OPC UA layer, so this test verifies SICAM PAS redundancy, not WinCC.
6. Data-model audit. Cross-check every IED data object listed in the SICAM PAS information model against the WinCC tag list. Missing tags are the most common cause of "the SCADA shows nothing for this bay" reports during commissioning.

8. Modern Alternative – SIMATIC Energy Suite and PCS 7 Power Control

Engineers planning a new project should consider the products Siemens has introduced since TIA Portal V12, even if WinCC V12 remains in place for legacy reasons.

• SIMATIC Energy Suite (introduced with TIA Portal V15.1) adds energy-data acquisition and load-management function blocks for S7-1500 CPUs. It does not replace a substation SCADA, but it is the right choice for plant-side energy monitoring that needs to share values with both the WinCC SCADA and a corporate energy dashboard. See the SIMATIC Energy Suite system manual.
• PCS 7 Power Control adds IEC 61850 MMS library support to the PCS 7 process-control system. PCS 7 with Power Control is the correct platform for industrial substations that need both process and electrical SCADA on a single engineering toolchain. PCS 7 V9.1 supports IEC 61850 Edition 2 with logical-node extensions through the PowerControl library.
• Spectrum Power (now marketed as Gridscale X Power Grid) is the Siemens platform for transmission-system control centres. It is out of scope for plant substation monitoring but is the correct product for utility-grade network control.

9. Migration Path from WinCC V12 to a Substation-Native SCADA

If the existing WinCC V12 deployment is being outgrown, plan the migration in phases to keep the substation energised:

10. Troubleshooting Matrix

11. Frequently Asked Questions