IMDTouchKnowledge BaseShop main store

Explainer

What WinCC Does in an HMI and SCADA System

HMI and touchscreens Published 7 min read

Short answer

WinCC is Siemens' visualization and supervisory software: it draws operator screens, shows live controller values, manages alarms, logs history and sends operator requests to the PLC. It does not execute machine logic. The controller keeps permissives and protection, so every WinCC button is a request the PLC is free to refuse.

On this page
  1. HMI, SCADA and the PLC: who does what
  2. What the WinCC runtime actually does
  3. A button is a request, not a command
  4. Drivers, protocols and the path to the controller
  5. Tags, scaling and a worked check
  6. Alarms, trends and the numbers behind them
  7. WinCC or WinCC flexible
  8. Decisions to fix before the first screen
  9. Questions asked

WinCC is Siemens' visualization and supervisory software for HMI and SCADA systems: it draws the operator screens, shows live values from the controller, raises and records alarms, archives process history and passes operator requests down to the PLC. It does not run the machine. The PLC executes the sequence, holds the permissives and drives the protection, so every button on a WinCC screen is a request the controller is free to refuse. That split — the visualization shows and asks, the controller decides and acts — is the whole platform in one sentence, and it places every function in your project. This page covers the division of labor, the runtime functions, the communication path to the controller, tag scaling with a worked example, and where WinCC flexible stops and full WinCC starts.

HMI, SCADA and the PLC: who does what #

An HMI is the operator's local window on one machine or line: the operator watches conditions, adjusts setpoints and answers alarms through it. SCADA is the same idea at supervisory scope — many controllers, centralized history, reports and several stations looking at the same plant. The PLC is the part that actually executes. WinCC serves both ends, which is why the question is never whether WinCC can display something, but where the function should live.

The rule is simple enough to commit to: anything the machine must keep doing when the operator station dies belongs in the controller; anything that exists to be seen, entered or recorded belongs in the visualization.

Function Where it lives
Showing values, states, units and validity WinCC
Start, stop and setpoint entry WinCC presents the control; the PLC validates and executes it
Permissives, interlocks, protection PLC, always
Alarm display and history WinCC presents and records; the PLC supplies the fault conditions
Archives, trends and reports WinCC

What the WinCC runtime actually does #

Once a project runs, the runtime does six jobs: it draws screens with graphics animated by live tag values, it trends those values over time, it raises, displays and collects acknowledgments for alarms, it accepts operator entries and writes them to the controller, it archives process values and events for later analysis, and it serves remote or web clients where the product provides them. None of that appears just because the project starts — each function is configured, and what is available depends on the WinCC product and the components installed alongside it.

The runtime host is a separate decision from the software: a panel at the machine, a PC in the control room, or a server feeding remote clients. Settle that choice early, because the host decides what the project may contain — the options are laid out in where WinCC Unified runtime can run and its remote HMI options.

A button is a request, not a command #

Three events happen between a finger and a motor: the operator activates the control, the controller receives the request, and the equipment changes state. Your screen design must let the operator see all three as separate facts — command issued, request accepted, and feedback taken from the actual equipment state, not from the command bit echoed back.

One safety note, and it is the one that matters: protective interlocks belong in the controller, because a script in the visualization only executes while the runtime and its connection are alive, so protection implemented there disappears exactly when things go wrong. Treat communication loss the same way — when the connection drops, mark displayed values invalid rather than freezing the last value in place, so a dead reading cannot pass for a live one.

Drivers, protocols and the path to the controller #

A communication driver translates between the WinCC runtime and the controller or data server. Pick it from the endpoint, not from the cable: Ethernet on both ends says nothing about which application protocol carries the data. PROFIBUS, PROFINET, Modbus, OPC and EtherNet/IP are different mechanisms with different availability across the product line, and they are not interchangeable. PROFINET is the native path to current Siemens controllers; Modbus TCP or OPC is the usual route when a third-party controller or a plant data server defines the endpoint — and an OPC server adds a box of its own to configure and to diagnose between the screen and the controller.

Bring the channel up before the graphics. Read a known controller value and watch it move, then enable writes under a controlled test; the procedure is covered in testing an HMI simulation against a live PLC. When a connection fails, read the diagnostics at both ends before touching a single screen object.

Tags, scaling and a worked check #

A tag is the named variable that ties a process value or an internal value to everything on screen — the number in the field, the fill in the tank, the alarm limit, the archive row. For an external tag you match the controller address or symbol, the data type, the engineering units and the scaling. A healthy connection with a wrong data type or span still displays confidently wrong numbers, so verify scaling with real arithmetic.

A 0–150 °C transmitter on 4–20 mA feeds an S7 analog input, which represents that loop as 0 to 27648 counts: 4 mA reads 0, 20 mA reads 27648. The tag shows 20736 counts.

  • Fraction of span: 20736 ÷ 27648 = 0.75
  • Loop current: 4 mA + 0.75 × 16 mA = 16.0 mA
  • Engineering value: 0.75 × 150 °C = 112.5 °C

Meter says 16.0 mA and screen says 112.5 °C: the tag is configured correctly. Screen says 75.0 °C at the same counts: the span was entered as 0–100 °C, since 0.75 × 100 = 75.0 — fix the range and audit every tag cloned from that template.

ANSI/ISA-18.2 is the alarm management standard, and in plain terms it requires every alarm to be defined before it is needed: a documented cause, a consequence, the operator's response and a priority, with the system presenting and recording alarms so the important ones reach the operator first. WinCC supplies the mechanism — limits on tags, alarm classes, priorities, acknowledgment and the alarm archive — but deciding which alarms exist at all is rationalization work you own, not a feature you switch on.

Archiving has its own arithmetic. At a 1 s acquisition interval, ten minutes of trend holds 600 samples (600 s ÷ 1 s per sample = 600), and the shortest change you can reliably see is about 2 s, because you need two samples on it. A 0.4 s excursion can fall between samples and never touch the archive at all. Commit per tag: set the interval from the fastest event that tag must catch, sampling at least twice during that event.

ISA-101 applies the same discipline to graphics: decide what decision each display supports and fix the hierarchy from overview to detail before drawing anything. The practice is laid out in designing HMI screens for clear operator decisions.

WinCC or WinCC flexible #

The name WinCC dates from Windows Control Center, and the family has two practical branches. WinCC flexible engineered Siemens operator panels and could also carry a smaller stand-alone SCADA with limited functions — variable monitoring, screens, basic logging. Full WinCC is the PC-based SCADA platform for the bigger jobs: large archives, reporting and multiple clients. Decide by the job. One machine, one station, no central history: an engineered panel carries it. Several controllers, archives, reports and stations in more than one place: build a PC runtime. The trade-offs for small systems are compared in WinCC versus WinCC flexible for a small PC SCADA system.

Decisions to fix before the first screen #

  • List every operator control and the PLC logic that accepts or refuses it.
  • Name the driver and endpoint for each controller, and the access direction of each tag group.
  • Fix each archive tag's acquisition interval from the fastest event it must catch.
  • Give every alarm its cause, consequence, response and priority.
  • Define what each display shows on invalid data, and test it by dropping the connection during an approved outage.

Questions asked

Can WinCC control the machine by itself, without a PLC?

No. WinCC is the visualization and supervisory layer: it displays values, logs history and sends requests. Sequence, permissives and protection belong in the controller, which keeps executing with its interlocks intact even when the visualization is down.

What happens on the plant floor if the WinCC runtime stops?

The controller keeps executing its logic, so the machine or line continues under its own permissives and protection. What you lose is visibility and the ability to issue requests from that station: no live values, no new setpoints and no alarm acknowledgment until the runtime is back.

Which communication path should I use to a Siemens controller?

PROFINET is the native route to current Siemens controllers over Ethernet. Use Modbus TCP or an OPC server when a third-party controller or a plant data server defines the endpoint, and remember that an OPC server adds its own configuration and diagnostics between the screen and the controller.

How do I verify tag scaling before startup?

Check three points on one loop. With 4 mA, 0 counts, the screen must show 0 °C. With 16.0 mA, 20736 counts, it must show 112.5 °C on a 0 to 150 °C transmitter. With 20 mA, 27648 counts, it must show 150 °C. Any other number means the span, offset or data type is wrong.

Is WinCC flexible the same product as WinCC?

No. WinCC flexible engineered Siemens operator panels and could also act as a smaller stand-alone SCADA with limited functions, such as variable monitoring and basic screens. Full WinCC is the PC-based SCADA platform for larger archives, reporting and multiple clients.

Keep reading

  • Selection guide

    How to Choose HMI Software for a New Control System

    Count operator stations, controllers and connections first, keep sequencing and permissives in the PLC, and pick the smallest architecture that meets the full requirement. One station with no logging duties takes a dedicated panel; multiple stations needing simultaneous control or sustained history take a PC-based runtime.

    HMI and touchscreens

  • Comparison

    WinCC vs WinCC Flexible for small PC SCADA applications

    WinCC Flexible can build a small SCADA application that runs on a PC, but only the Advanced edition does it — Standard stops at operator panels. Treat two decisions separately: the Advanced engineering license buys the PC runtime capability, and each PC that runs the finished application still needs its own runtime license. Beyond single-station scope, the WinCC family is the SCADA tool.

    HMI and touchscreens

  • Selection guide

    Choosing Web-Based HMI and SCADA Architecture for Production Lines

    Run one web HMI/SCADA server per production line, so a server outage costs one line its screens instead of the whole plant. Add a central server only after writing down the outage cost per hour and the redundancy that cost justifies, and keep office viewers on status-only roles enforced at the tag write.

    HMI and touchscreens

What a SCADA Operator Interface Must Do: Core Functions