Request a quote
Benešl Automation / Articles / AI and WinCC Unified
Technical article · AI and WinCC Unified

AI and WinCC Unified: what can and cannot be automated on screens

An HMI programmer spends a lot of routine work on WinCC Unified screens: creating tags, placing faceplates, setting up dynamizations and, after a migration, looking for what broke. AI connected directly to TIA Portal can handle a large part of this. Some things, however, cannot be done through the official TIA Portal Openness interface, and others the AI should not do. We summarise both, based on our practice with TIA MCP.

Ing. Tomáš Benešl · 21 October 2026 · 6 min read

How AI works with WinCC Unified

A chat on its own cannot see a screen. AI connected through TIA MCP reads and changes the project in TIA Portal via the Openness interface, much like a script. For WinCC Unified it has tools for screens, objects, HMI tags, dynamizations, scripts, faceplates, alarms and configuration checks. It calls them based on a request in plain language, and you see the result directly in the project.

Every write starts with a backup. WinCC Unified screens cannot be exported to XML, so before a change TIA MCP saves a snapshot of the screen in JSON format and can rebuild the screen from it. This matters because changes made through Openness cannot be reverted with the Undo button in TIA Portal.

What can be automated well on WinCC Unified screens

Overview and search

The AI lists screens with their sizes and object counts, finds objects by name, type or text across all screens and shows their dynamizations and event scripts. This helps with someone else's project or when you are looking for every place a particular tag is used.

Bulk edits

  • The same properties for all objects matching a filter: colour, font, alignment or visibility.
  • Shifting or centring screen content and rescaling screens to a different panel resolution.
  • Replacing text in all scripts and redirecting tag references in dynamizations and faceplate interfaces.
  • Switching faceplate instances to a new type version while keeping their interface.

Tags, faceplates and alarms

  • HMI tags in bulk from CSV, including connection, PLC tag and acquisition cycle. A backup of all HMI tags of the device is saved before writing.
  • Faceplates for motors, valves, analog measurements and PID controllers: the generator maps the members of a UDT or data block to faceplate signals and by default only shows a preview without writing. It can also place instances of an existing type from the project library and connect their interface.
  • Bit alarms from a list in Excel: a data block in the PLC, HMI tags and WinCC Unified discrete alarms in one go.
  • Drawing objects from a description: rectangles, texts, I/O fields, buttons, colour dynamizations and event scripts. The screen is created if it does not exist yet.

Checks and tests

Even before compiling, the AI runs a check that finds non-existent tags with a suggested fix, unconnected faceplate containers, scripts with migration leftovers and objects outside the screen. Validation through Openness additionally checks script syntax, connections, alarms and runtime settings. The AI returns compile errors as an overview with the path to the object. An automatic HMI test then clicks the buttons in simulation and checks that values are written to the simulated PLC in PLCSIM Advanced.

What cannot be automated or is not worth it

  • The faceplate type. Openness cannot create a faceplate type or read or change its content. The AI draws a draft on a working screen and prepares the procedure, but you copy it into the type in the library by hand in TIA Portal.
  • The real appearance. Openness does not render a screen. TIA MCP can produce a schematic SVG preview to check the layout, but you only see what the screen really looks like in runtime or in simulation.
  • The operating concept. What the operator should see, in what order and how to react to a fault is a decision for the process engineer and the programmer. The AI can make suggestions, but it does not know the plant.
  • Undo in TIA Portal. Changes made through Openness are reverted from the backup TIA MCP makes before every write. Before a large bulk change it is also sensible to have a project archive.
  • Runtime at the machine. The automatic HMI test runs only against a simulation on your computer. It cannot test the runtime project at the machine and refuses to start in that case.

Example requests for the AI

Write requests the way you would give the task to a colleague. State the device, the screens and what must not change.

Go through HMI_1 and list the screens where the tag Motor_12_Run is used. For each one, state the object and the property the tag controls. Do not change anything.
On all screens of HMI_1, set font size 16 and centre alignment for buttons whose name starts with btnNav. Show the list of changes first and write only after my confirmation.
From DB_Motory in PLC_1, prepare motor faceplates for the array Motor[1..12] and place them on the Motory screen in two rows. Use the existing type from the project library. Do a dry run first, then show me the uncertain signal matches.
After the migration from the Comfort panel, run the check and validation of HMI_1, compile the device and list the errors by screen. Suggest fixes, but do not write anything without my approval.

What to watch out for

  • Preview first. For bulk tools, ask for a dry run and a list of changes. Only then write.
  • Read-only mode. TIA MCP can block all writes to the project. It is a good choice when you start working on someone else's project.
  • Tag names after migration. Migration from Comfort changes the names of tags from data blocks. The automatic reference fix covers typical patterns; tags the migration did not find have to be added by hand.
  • Texts and languages. Texts in WinCC Unified are multilingual. After a bulk change, check all runtime languages, not just the one you work in.
  • The final check is yours. Before downloading to the panel, compile the project, go through it in simulation and make sure the operators get what they expect.

Summary

AI connected to TIA Portal saves work mainly on repetitive tasks on WinCC Unified screens: bulk edits, tags, faceplates, alarms and checks after a migration. The faceplate type, the final appearance and the operating concept remain with a human.

You will find an overview of the tools on the page AI for WinCC Unified and the procedure for migrating from Comfort panels in the article Migrating HMI to WinCC Unified: procedure, pitfalls and how to save time.

Frequently asked questions

Can AI create a screen in WinCC Unified?

Yes. Through TIA MCP the AI creates a screen and draws objects on it from a description: shapes, texts, I/O fields, buttons, dynamizations and event scripts. The result needs to be checked in simulation.

Can AI create a faceplate type?

No. The TIA Portal Openness interface cannot create or edit a faceplate type. The AI prepares a template screen and the procedure; you convert it into a type by hand in TIA Portal. The AI places and connects instances of existing types.

How do I revert a change the AI made on a screen?

Before every write, TIA MCP saves a snapshot of the screen in JSON format and restores the screen from it. The Undo button in TIA Portal does not revert changes made through Openness.

Does it work for Comfort panels too?

For Comfort panels TIA MCP offers screen export and import and tools for migrating to WinCC Unified. Most of the tools described in this article, however, are intended for WinCC Unified.

Related articles and pages

Try AI on your own HMI project

TIA MCP connects ChatGPT, Claude, Copilot or Gemini to TIA Portal V17–V21 on Windows. A PRO licence costs €295 per year per computer excluding VAT, and the first 7 days are free.

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