How-to
Reuse a legacy HMI program and graphics in a new runtime
Short answer
You cannot import a vendor HMI project into a PC HMI or SCADA runtime, and you cannot layer the new runtime on top of the panel. Run the new runtime beside the panel on the same PLC, carry over only the tag addresses and exported images, rebuild screens, alarms and users fresh, then strip write access from the old panel so the audit trail covers every operator write.
On this page
No. A PanelView, Comfort Panel, C-More or EasyBuilder Pro project does not import into a PC HMI or SCADA runtime, and you cannot install the new runtime on top of the panel to wrap it. Two things survive the migration: the PLC tag addresses the panel reads and writes, and the graphics the vendor tool exports as image files. Everything else — screens, animations, scripts, alarm definitions, users — is rebuilt in the new runtime. The working path is to run the new runtime beside the panel on the same PLC, rebuild what operators need, then make the new runtime the only write path so access control and the audit trail cover every operator action. The steps below each end with the check that proves them before the old panel loses its writes.
Why a vendor project does not import into a PC runtime #
Three separable locks stop the import, and a converter would have to beat all three at once.
- The panel will not host the runtime. Most operator panels run a fixed embedded operating system chosen by the vendor, with no PC-class application layer for a third-party runtime to install into. A PC HMI or SCADA runtime needs a PC-class machine.
- The file does not decode. Each vendor stores its project in its own format, and the objects inside carry behavior — animation bindings, faceplate navigation, scripts written to that runtime's model. A converter would have to translate behavior, not just shapes, which is why no general cross-vendor converter exists.
- A Windows panel is not a drop-in either. A Windows-based panel PC can host a PC runtime, but it hosts its own vendor's runtime, not a competitor's project.
The one real exception stays inside a single engineering-tool family: a project built in TIA Portal for a Siemens panel can be retargeted to WinCC Runtime Advanced on a PC, because panel and PC are both targets of the same tool — the mechanics are covered in running a TIA Portal V14 HMI on WinCC Runtime Advanced. Across vendors there is no such path, so plan this as a rebuild with a data migration, not a file conversion.
What carries over and what gets rebuilt #
Sort every element of the old panel into one of three fates before you promise a schedule. The tag list is the asset; the visuals are either exported files or redraws.
| Panel asset | Carries over | Action in the new runtime |
|---|---|---|
| Tag names, PLC addresses, data types | Yes, as data | Export from the vendor tool or read out of the panel, then import into the new runtime's tag database |
| Bitmaps, logos, static backgrounds | Usually, as files | Export every image the tool allows; redraw what it will not give up |
| Screen objects, animations, faceplates | No | Rebuild with the new runtime's own components and templates |
| Panel scripts and macros | No | Move the logic into the PLC where it belongs, or rewrite it in the new runtime's scripting language |
| Alarm definitions | No | Redefine against the new runtime's tags and alarm system |
| Users, roles, passwords | No | Define fresh around the access model you actually want |
The exported tag list is also the scope of the whole job: every row is something to rebuild, verify and audit. Where the new runtime accepts a CSV import, that export maps straight onto the workflow in importing a PLC tag CSV into an existing HMI tag database.
The rebuild procedure #
Run the steps in order; each one ends with the check that proves it.
-
Read the old program while the panel still runs. Pull the project, or at least its tag table, off the panel and build the scope sheet: tag name, address, data type, and whether operators write to it. Label what you recovered, too — an editable source project rebuilds screens, while a device restore backup or an export of selected data does not. When the panel has no source file at all, the procedure in reading an old HMI program before panel replacement recovers one. Check: the sheet's row count equals the tag count in the panel's configuration, with no unnamed gaps.
-
Export the graphics. Save every image the engineering tool will hand over: logos, static backgrounds, bitmap indicators. Vector shapes, text and dynamic elements do not export; they get redrawn in step 4. Check: every exported file opens cleanly at the new runtime's target resolution and the scope sheet references nothing missing.
-
Stand the new runtime up beside the panel. Install it on a PC-class machine with a network path to the PLC, matching the installed runtime version to the version the project's device configuration expects, and configure the PLC driver for that controller and protocol. Create every tag from the sheet as read-only. Before the second client connects, confirm the controller's documented connection or session capacity covers both clients — a controller near its limit can drop the existing panel session when the new runtime joins. Check: tag quality reads Good, and five sampled tags, at least one boolean and one analog, match the panel's displayed values at the same instant. A bad-quality tag while the device shows connected points to an address or data-type mistake in the tag definition, not to the driver.
-
Rebuild the screens operators actually use. The old panel is the visual specification: trace its layout, build one template per equipment type and instantiate it, and place the exported images from step 2. Leave screens nobody has asked for unbuilt until somebody asks; the parallel run covers the gap. The screen-side mechanics match importing legacy HMI screens when migrating to a new panel. Check: with the new screen open next to the panel, every numeric, status and alarm indicator agrees through a normal run and one induced abnormal condition.
-
Configure users, roles, alarms and the audit profile. Define the role hierarchy, bind write permission to every write-capable element, redefine alarms on the new tags, and switch the audit profile on before any write is enabled. Where the audit trail exists to satisfy 21 CFR Part 11, the regulation requires secure, computer-generated, time-stamped records of operator entries — which is exactly why the writes have to flow through this runtime. Where the screens must follow ISA-101, design to that standard's screen-hierarchy and alarm-presentation discipline rather than tracing the old panel pixel for pixel. Check: a low-privilege login can open the screen but cannot reach or trigger any setpoint control.
-
Move every write onto the new runtime, then off the panel. Enable writes on the new screens first and verify them, then set the panel's write elements to display-only and download its project again. One safety note: no setpoint comes off the panel until its replacement exists on the new runtime and operators have used it — a dead control on a running line is a stop-the-line problem, not a software detail. Check: the same write attempted from the panel is refused, or the element no longer accepts one. If the old panel is failed or obsolete rather than a keepable fallback, this is the point to specify the replacement station as one of the industrial panel PCs that run the HMI runtime at the machine.
-
Run both layers in parallel and close out. Keep the panel as a read-only reference while operators work from the new runtime. The migration closes when a full shift runs with no value mismatch against the panel, no audit gap, and no new connection faults at the PLC — including after a restart of the runtime machine, which must come back with tag quality restored and earlier audit entries intact.
Worked example: when the cutover is genuinely done #
The scope sheet turns the audit requirement into arithmetic. The numbers below are illustrative inputs, not a benchmark; substitute your own sheet.
Say the panel scope sheet totals 340 tags and 62 of them are operator-writable. After step 5, the new runtime carries all 62 write paths. What decides the cutover is the panel side:
- Panel write paths left after step 6 is done fully: 0. Audited coverage = 62 ÷ 62 = 100%.
- Half-measure, with 14 rarely used setpoints left writable on the panel: (62 − 14) ÷ 62 = 48 ÷ 62 ≈ 77%. Those 14 writes execute outside both the access control and the audit log.
- Panel left untouched: all 62 writes sit outside the audit trail, coverage 0%, and the new runtime is decoration.
The rule that falls out is countable, so commit to it: the cutover is complete on the day the number of writable elements on the old panel is zero. A percentage blurs; a zero count does not.
The decision, case by case #
- Working panel, and you only need access control plus an audit trail: stand the new runtime up beside the panel on the same PLC, rebuild the screens operators use, strip the panel's writes, keep the panel as a read-only fallback. That is the entire project; there is no import shortcut hiding in a file converter.
- Upgrade inside one vendor family: retarget instead of rebuild. The TIA Portal panel-to-WinCC Runtime Advanced path is the documented pattern — verify the PC runtime's target support and licensing before promising a date.
- Panel dead, obsolete or source-less: recover what step 1 can recover, then run the same rebuild; do not spend days trying to convert a file no tool will open.
Every case lands in the same place: tags and exported images carry over, screens, alarms and users get rebuilt, and the new runtime ends up the only thing on the network that can write a setpoint to the machine.
Questions asked
Can the old panel and the new runtime both stay connected to the PLC for good?
They can both stay connected as long as the controller's documented connection or session count supports two clients — that limit is permanent, not just a commissioning check. Two connected clients are fine; two writing clients are not. Once one setpoint can be written from both screens, the last writer wins and the audit trail shows only one of them, which is why the panel keeps read-only duties after cutover.
Does the audit trail record changes the PLC program makes on its own?
No. The runtime's audit profile logs operator actions made through the runtime — logins, setpoint writes, acknowledges — with the user, value and time. Values the controller logic writes internally, or that any other client writes, sit outside that log. If those changes need a record too, that record lives in the controller program's change management, not in the HMI.
Do I need anything special to read the program off the old panel first?
You need the matching vendor engineering tool, its license, a cable or network path, and the panel's transfer password if one is set. A lost transfer password is recovered only through the vendor's documented recovery procedure; there is no legitimate way around it. If the upload is refused and no recovery path applies, fall back to rebuilding the tag list from printouts, electrical drawings and the PLC program itself.
Can I rebuild screens faster by screenshotting the old ones?
Screenshots help as tracing references, but a pasted bitmap is not an operator interface: it has no tags bound to it, no alarm state and no write permission. Use the screenshot as the layout reference in the design tool, place live components on top of it, then delete the image layer before commissioning. Static backgrounds like logos and line drawings are the only images worth keeping as flat pictures.