Request a quote
WinCC Unified · Comfort · WinCC RT Advanced · HMI tags · alarms · JavaScript

AI for WinCC Unified: screens, faceplates and HMI migration

AI for WinCC Unified works directly with the HMI in the project open in TIA Portal. Through TIA MCP your AI assistant (ChatGPT, Claude, Copilot, Gemini or a local model) reads screens, changes objects, dynamizations and scripts, creates HMI tags and alarms from a table and checks the HMI without compiling. It also helps finish a migration from Comfort panels. A backup is made before every change.

What AI does with WinCC Unified

You give instructions in plain language. The AI picks the TIA MCP tools, works with the HMI objects in the project and shows the result. You review and approve.

Screens and objects

An overview of screens with object counts, object properties, their dynamizations and scripts. Searching for objects across screens by name, type or text.

Editing and designing screens

Object properties one by one or in bulk, new objects, shifting and centring content, rescaling screens to another panel resolution. From a description it draws a draft of a screen or symbol.

Dynamizations

Colour by bit, binding a property directly to a tag, expressions, flashing, text or graphic lists and script dynamization with a syntax check.

Faceplates

It places a faceplate from the project library and binds its interface to HMI tags, switches instances to a newer type version and finds empty or unbound containers. From a UDT or DB in the PLC it prepares a screen for a motor, valve, analogue value or PID.

HMI tags and alarms from a table

Export and import of HMI tags via CSV for Excel or YAML, tag tables and groups. Bit alarms from a list in Excel or CSV: a data block in the PLC, HMI tags and Unified discrete alarms in one go.

JavaScript scripts

Event and dynamization scripts, global script modules, bulk find and replace. When a screen is renamed it also fixes the ChangeScreen calls in the scripts.

Checks without compiling

It finds containers without a type, non-existent tags with a suggested fix, migration leftovers and objects outside the screen. Validation checks screens, tags, connections, alarms and script syntax. Alarms are checked against ISA-18.2.

Previews and screenshots

A schematic SVG preview of a screen without a running runtime. With the simulation running, screenshots of the screens via the web client, also for the operating manual.

Settings beyond screens

HMI connections to the PLC, alarm classes, data and alarm logs, logging tags, runtime settings and text and graphic lists.

Example requests for AI in WinCC Unified

No commands or syntax. The AI finds the device and screen names in the project.

List the screens on HMI_1 with the number of objects and faceplates on each.

On the Pumps screen colour the indicators by the running bit: green running, grey stopped.

Create the alarms from alarms.xlsx in the PLC and in WinCC Unified. Show a preview first.

After the migration from Comfort fix the screen names and tag references and list what is left to fix by hand.

Find empty faceplate containers and fill in the type and interface from the Comfort panel.

Check the HMI without compiling and sort the findings by severity.

Migrating from Comfort and WinCC RT Advanced to WinCC Unified

The device conversion itself is done by TIA Portal. But work remains afterwards: empty faceplate containers, broken tag and screen names, empty symbols and truncated texts. TIA MCP has tools for that. For bulk fixes the AI shows a preview first and changes the project only after your approval.

Screen and tag names

It renames screens with a backslash in the name, including in the scripts. It redirects tag references broken by the migration to existing HMI tags.

Faceplates after migration

For each instance from Comfort it finds the empty container in the same place and sets the type, name and interface. Simple indicators can be replaced with a circle coloured by a bit.

HMI tags of UDT type

Tags that were of a UDT type in Comfort get the matching HMI UDT from the project library and their address from Comfort back.

Symbols from the Symbol library

Symbol library graphics that stay empty after the migration are converted to Unified SVG widgets. Colours, rotation, appearance animations and events are carried over.

Truncated texts

Texts on buttons and in fields that no longer fit after the migration are measured with the Comfort font. It removes inner padding or reduces the font size. The change can be reverted from a backup.

Alarm texts

It fixes characters in alarm texts that the migration encoded twice and that would show up as code in runtime. All languages, alarm text and info text.

The TIA MCP web interface has a guide for completing the Comfort → Unified migration. It goes through the fixes in the right order, shows a preview for each, applies a fix only after your approval and finally checks and compiles the HMI.

The AI can also read Comfort and WinCC RT Advanced panels and export and re-import the whole classic WinCC (screens, tags, lists, VB scripts). This is useful for versioning in git or moving to another HMI. The whole migration procedure is described in the article HMI migration to WinCC Unified.

Automatic HMI test in simulation

From the WinCC Unified project the AI builds a test plan: navigation buttons, buttons writing to the PLC, display and input in I/O fields, and alarms. It then verifies the plan against an HMI simulation connected to S7-PLCSIM Advanced and saves a report with screenshots of failures.

Testing the PLC program and HMI in PLCSIM

What AI does not do in WinCC Unified and what to watch out for

It does not create a faceplate type

The TIA Portal Openness interface cannot create a faceplate type or change its contents. The AI prepares a template screen and you create the type from it in TIA Portal by hand.

Screen backups as JSON

Unified screens cannot be exported to XML. Before a change TIA MCP therefore saves a JSON snapshot of the screen and can restore it from that, including dynamizations and scripts.

Some things are left to you

Tags that are completely missing from the project after the migration are only listed by the AI. Moving an existing screen into a group or creating new tag thresholds is not possible via Openness.

You start the runtime

Screenshots and the HMI test need a running WinCC Unified simulation on the same computer. You start the simulation, or the AI does with your explicit confirmation. A runtime at the machine is not tested this way.

A person judges ergonomics

Checks and validation find technical errors, not a cluttered screen. A design from the AI is a starting point. Compile and review the HMI before loading it to the panel.

Writing under your control

You switch off writing to the project with read-only mode, and only a person can switch it back on, not the AI. You can approve changes one by one. Every write is logged.

Article: AI and WinCC Unified in practice

All TIA MCP tools by area

FAQ about AI for WinCC Unified

Can AI design a WinCC Unified screen?

Yes. From a description it draws a screen or symbol from rectangles, texts, I/O fields and buttons, including dynamizations and scripts. It is a draft: check the layout and look and adapt them to your standard.

Does TIA MCP convert a Comfort panel to WinCC Unified?

The device conversion is done by the migration in TIA Portal. TIA MCP helps with what is left afterwards: faceplates, HMI tags of UDT type, screen names, tag references, symbols, truncated texts and alarm texts.

Does it also work for Comfort panels and WinCC RT Advanced?

Partly. With classic WinCC the AI reads, exports and imports screens and other objects and can create text lists and VB scripts. Editing individual objects, dynamizations and faceplates is for WinCC Unified.

Which TIA Portal versions are supported?

TIA Portal V17 to V21 on Windows. Some functions are V21 only, for example graphic lists, plant views or the integrated HMI connection via hardware.

Do I need a running runtime to work with the AI?

Not for reading, editing, checking and the SVG preview; an open project is enough. Screenshots and the automatic HMI test need a running WinCC Unified simulation on the same computer.

What if the AI breaks something in the HMI?

A backup is made before every change and can be restored with one command. Bulk fixes have a preview without writing. You can switch off writing to the project completely with read-only mode and approve changes one by one.

How much does it cost?

It is part of TIA MCP. A PRO licence costs €295 per year per computer, excluding VAT, and you can try TIA MCP free for the first 7 days. For companies with several computers we offer an Enterprise licence.

Siemens, SIMATIC, TIA Portal, WinCC and S7 are trademarks of Siemens AG. TIA MCP is a standalone product of Benešl Automation, is not a Siemens product and communicates with TIA Portal through the official TIA Portal Openness interface.