Siemens is mid-transition on the HMI side: the Comfort/WinCC-classic world is mature and everywhere; Unified is the future and now genuinely usable. Choosing per project beats ideology.
What Unified changes
Unified Comfort Panels run a web-technology runtime: vector graphics that scale, HTML5-based remote access from any browser, JavaScript scripting instead of VBScript, and a faceplate system that finally supports proper structured engineering. The panels are faster hardware, and features arrive here first — classic Comfort development is effectively frozen.
The costs: a different engineering experience with its own learning curve, migration from classic WinCC that is a re-implementation rather than a conversion for anything nontrivial, and — in early versions — gaps that classic users notice. Recent versions have closed most everyday gaps.
Our per-project guidance
- New machines with a 10+ year life: Unified. You are buying the platform with a future.
- Fleet extensions and clones of existing machines: stay classic — consistency across a fleet is worth more than features.
- Retrofits where the panel is dying but the PLC stays: panel-for-panel classic replacements are the low-risk path; jump to Unified when the PLC generation changes too.
FAQ
Can Unified and classic coexist in one project? Yes — one TIA project can hold both panel types, which is exactly how phased fleets migrate.
Is VBScript gone? On Unified, yes — scripting is JavaScript. Budget time for rewriting the scripts nobody documented.
Zone Otomasyon engineers both platforms and will tell you honestly when the boring choice is the right one. Ask us.