Siemens WinCC Unified screens: tag binding and faceplate

For Siemens TIA Portal V18+.

WinCC Unified is the V18+ HTML5-rendered HMI runtime. Screens, faceplates, dynamic tag binding — the workflow differs from WinCC Comfort. This page is the working engineer's read — what the menu paths actually are in TIA Portal V18+, what the keystrokes do, and the mistakes that bite once the program is on a real CPU. We program S7-1200 / S7-1500 ourselves, daily; we are not a Siemens sales channel.

What this is and when you need it

WinCC Unified is the V18+ HTML5-rendered HMI runtime. Screens, faceplates, dynamic tag binding — the workflow differs from WinCC Comfort. The walkthrough below is the same sequence we use when teaching this on the simulator. Every step names the exact menu path or keystroke; if a name has changed in your version of TIA Portal V18+, it is called out. The simulator runs the same logic flow without the licence cost — ladder, FBD, and ST in a browser, with a virtual CPU you can download to.

Walkthrough

1. Add a Unified panel to the project

In the project tree, right-click Devices > Add new device > HMI > SIMATIC HMI Unified Comfort. Pick a panel size (MTP700, MTP1000, MTP1500, MTP1900, MTP2200). Unified panels render HTML5 over WebGL; the editor in TIA Portal previews the same way the runtime does, which is a meaningful upgrade from Comfort's WinForms preview.

2. Build the tag list and PLC connection

Under HMI tags > Default tag table, add tags. Each HMI tag binds to a PLC tag via Connection (the PLC connection is auto-created when the HMI is in the same project as the PLC). Choose acquisition mode: Cyclic in operation (read continuously), Cyclic continuous (read even when screen not active), or On change (read when value changes — preferred for high-update tags).

3. Drop a faceplate on a screen

Faceplates are reusable HMI components — a motor faceplate with start/stop buttons and a status indicator. Right-click Faceplates > Add new faceplate. Design the inner layout. Define faceplate Properties (the parameters exposed to the screen), faceplate Events (button clicks fire here), and faceplate Scripts (JavaScript in Unified, not VBScript like Comfort). Drag the faceplate onto a screen — bind each Property to a PLC tag via the Properties dialog.

4. Wire dynamic appearance

Select a screen object, open its Properties pane, and click the dynamic icon (lightning bolt) next to a property like 'Background colour'. Choose 'Tag' for a binding to a tag value, or 'Script' for JavaScript that returns a colour. Value ranges map to colour: tag = 0 -> grey, tag = 1 -> green, tag = 2 -> red. Save with Ctrl+S; the runtime preview updates immediately.

// Dynamic colour binding (pseudo)
// Tag: Motor1_Status (Int)
// Range: 0 -> #888888 (idle)
// Range: 1 -> #2da44e (running)
// Range: 2 -> #d1242f (fault)

5. Compile, download, and test in browser

Ctrl+B compiles the HMI. Errors appear in the Inspector. Download via the toolbar download icon — the runtime restarts automatically. Unified runtime exposes the screens via HTTPS on port 4848 by default; open Chrome to https://<panel-ip>:4848 to see the runtime in a browser, which is useful for testing without standing at the panel.

Common mistakes

• Trying to copy WinCC Comfort VBScript into a Unified faceplate — Unified runs JavaScript, the languages are not compatible and porting needs a rewrite
• Forgetting to set the acquisition mode and ending up with a screen that polls every tag every 100 ms — runtime stutters and the panel CPU gets hot
• Binding the same PLC tag twice via two HMI tags — the runtime makes two reads per cycle and you waste connection bandwidth
• Skipping the HTTPS certificate setup — Chrome refuses to connect to a self-signed runtime certificate without an explicit accept dialog each session

Each of these mistakes shows up in real projects every week. The simulator catches the first three at compile time; the fourth one only surfaces on hardware, which is why we recommend running the cert packs against a real CPU once you have completed the curriculum modules.

How this fits the broader curriculum

Siemens WinCC Unified screens: tag binding and faceplate basics is one of the building blocks. The full Siemens curriculum on the simulator covers: programming-language fundamentals (ladder, FBD, ST), tag and variable scope, HMI tag binding, comms setup (Profinet / EtherNet/IP / Modbus depending on the platform), and the brownfield troubleshooting pathway. Each is its own module with worked examples and a portfolio piece. The cert packs at the Pro tier align to the ISA CCST exam content outline. Reference: isa.org.

For the platform-pick decision — when Siemens is the right call versus a different brand — see the brand hub. For region-specific context on where Siemens dominates the SA install base, see the relevant city pages under /brands/siemens/training-in-* and the sector pages under /industries.

Where this sits in a working week

A technician who has finished this module typically spends the next three to four working days running the same logic flow on hardware. The simulator's value is the dry run — getting the keystrokes and the IDE conventions into muscle memory before you sit down with a live CPU. The first time you build this on hardware, expect the IO mapping and the addressing conventions to slow you down for a session or two; the simulator's project tree mirrors the same shape so the transition is short.

The full Siemens curriculum runs roughly 60 to 100 hours of focused practice. That breaks into bit logic and timers in the first 20 hours, FBs and structured data in the next 20, comms and HMI in the next 20, and a portfolio piece in the last block. Pace yourself — three or four hours per session, four sessions a week, and you finish in eight weeks. Most of our learners report that the bottleneck is not understanding the IDE, it is building reflex around the conventions: where Siemens expects you to put state, how it scopes variables, what naming patterns the OEMs in the sector use.

Vendor reference

Siemens's own documentation is the canonical reference once you are working on real hardware: Siemens Industry Online Support. The simulator covers the basics; the vendor docs cover everything specific to a hardware revision, a firmware update, or a CPU-specific quirk. Bookmark both. The IEC 61131-3 standard that governs all the Siemens programming languages is at iec.ch.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. Our completion certificates are course-level only — they describe what you covered, not an NQF Level X qualification. The CCST cert from ISA is the portable industry credential we recommend; we are not an ISA cert delivery partner either, but our cert packs are CCST-aligned. The walkthrough above is brand-specific because Siemens's tooling has its own conventions; do not assume the same menu paths exist in another brand's IDE.

How to start

You can be running siemens wincc unified screens: tag binding and faceplate basics in the simulator in 5 minutes. Free tier covers the basics, no card, no install. Once you are 20 minutes in you will know whether the platform fits how you learn. The full Siemens curriculum is the Basic tier (USD 12 / month). The cert packs and portfolio export sit in the Pro tier (USD 29 / month). For institutional buyers — TVET colleges, private training providers, in-house engineering training departments — the bulk-licence option is the Teams tier, USD 199 per seat per year, minimum 5 seats. The training-centres page has the institutional pitch and the contact form.

Honest expectations on the local job market

Petrochem, mining, FMCG, automotive, and water-utility sectors all carry Siemens install bases somewhere in their stack. Knowing the IDE conventions on this page does not get you a job by itself; it gets you past the first technical screen. The portfolio piece — a working program you built yourself, with a wiring track, a tag list, an HMI screen, and a short README explaining the design choices — is what lands the second interview. The simulator's portfolio export bundles all of that into a single folder you can hand a hiring engineer. Recruiters in this space skim the README first; if your design choices are coherent, they read the code.

Load-shedding has reshaped what gets built first in Siemens programs across SA. Power-recovery patterns — controlled shutdown on UPS hold, state recovery from retentive memory, sequenced restart of motor groups — now belong in the same module as the basics. Siemens WinCC Unified screens: tag binding and faceplate basics fits into that shape: every line of code you write needs to consider what state the controller is in when it powers up after a 2.5-hour cut, not just what state it is in when running. The simulator's restart-from-cut mode lets you exercise this without bricking real hardware.