Migrating HMI to WinCC Unified: procedure, pitfalls and how to save time
Moving from Comfort panels or WinCC Runtime Advanced to WinCC Unified is more than swapping a device in the project. What TIA Portal converts on its own, what has to be done by hand, and in which order to proceed so the migration does not turn into a completely new project.
Why WinCC Unified
WinCC Unified is the new generation of Siemens visualization in TIA Portal. It replaces Comfort panels as well as WinCC Runtime Advanced and Professional. Screens are vector-based, scripts are written in JavaScript, and you can connect to the runtime from a web browser without any additional client.
For the operator this means a more modern user interface, remote access via a browser and future support. For the engineer it means that part of the old project has to be reworked.
What TIA Portal converts on its own
When you replace a Comfort panel with a Unified Comfort Panel, TIA Portal converts a large part of the project automatically:
- HMI tags and their connections to the PLC,
- screens and most basic objects: texts, buttons, I/O fields, rectangles and lines,
- discrete and analog alarms and text lists,
- simple colour and visibility dynamizations.
Whatever cannot be converted is listed by TIA Portal in the migration log. It is worth reading the whole log before making the first change to the screens.
What has to be done by hand
Scripts: from VBScript to JavaScript
Unified uses JavaScript; VBScript scripts are not converted. Most scripts, however, only switch screens, set tags or calculate simple values. Such scripts are quick to rewrite and can often be replaced by a system function or a dynamization without any script.
Faceplates
Faceplates from Comfort panels are not carried over to Unified. Unified has its own faceplates as library types with an interface and properties. It pays to design them once for the whole plant, for example a motor, valve, analog value or controller, and then just place instances and connect them to data blocks in the PLC.
Screen resolution and layout
The new panel often has a different resolution or aspect ratio. Screens need to be rescaled and checked by hand, especially headers, navigation and areas with densely placed elements.
Graphics and symbols
Bitmap images from the original project still work, but vector symbols look better in Unified. For process diagrams it pays to use an SVG symbol library and dynamize the colour of the symbol directly.
Trends, recipes and logging
Trends, value and alarm logging and recipes are configured differently in Unified than in Comfort panels. Check that the logs use the right storage and retention period and that the trends show the right tags.
Users and security
User and permission management works differently in Unified. Roles and permissions have to be set up again, and you need to decide who will log in at the panel and who from a web browser.
Recommended procedure
- Inventory: a list of screens, tags, scripts, faceplates, alarms, recipes and logs. Only then can the effort be estimated.
- Choice of target: a Unified Comfort Panel or Unified PC Runtime. The number of screens, logging and remote access decide.
- A trial migration on a copy of the project and analysis of the migration log.
- Faceplates and the type library before editing the screens.
- Editing screens, rewriting scripts and configuring alarms, logs and users.
- Testing in simulation against PLCSIM or a real PLC, new screenshots and an updated operator manual.
- Commissioning and a short training of operators on the new interface.
How to speed up the work
A large part of a migration is repetitive manual work: reconnecting tags, replacing text in scripts, checking hundreds of screens and taking new screenshots for the manual. We do this work with TIA MCP, a tool that lets an AI agent work directly with the project in TIA Portal:
- bulk replacement of tag references and text in scripts across the whole project,
- generating faceplates for typical devices and placing them on screens,
- checking the Unified project: missing tags, empty events, unused screens,
- rescaling screens to a different resolution,
- screenshots of all screens from the simulation straight into the manual.
The engineer spends time on decisions and review, not on clicking.
Checklist before handover
- All screens open in runtime with no errors in diagnostics.
- Alarms are displayed, acknowledged and logged.
- Trends show the right values and logs have a retention period set.
- Users and permissions match the plant's requirements.
- The operator manual matches the new screens.
- Backups of both the original and the new project are stored at the customer's site.
Planning a migration?
Send us the project or a description of it. Within a few days you will get an effort estimate and a list of things that will need manual work.