Why it matters now: With the global PLC market surging toward an estimated USD 25.26 billion by 2034 and manufacturers facing a critical engineering talent shortage — as many as 1.9 million unfilled positions projected by 2033 in the US alone — the industry urgently needs tools that make automation engineering faster, more accessible, and aligned with modern software practices. Siemens' latest launch directly confronts both the productivity gap and the workforce bottleneck.
Analyst Insight: Siemens' move to extend SIMATIC AX into HMI engineering represents more than a feature release — it signals a structural shift in how industrial automation projects will be built, reviewed, and maintained. By bringing visualization engineering into the same VS Code–based, Git-enabled environment that handles PLC logic, Siemens is effectively unifying the entire control system development lifecycle under one IT-aligned toolchain.
What Is SIMATIC AX WinCC Unified Elements?
Announced on July 28, 2026, and available immediately in the United States, SIMATIC AX WinCC Unified Elements is a new engineering application that extends Siemens' SIMATIC AX platform into the realm of HMI and visualization. Previously, the SIMATIC AX family focused exclusively on PLC programming — leaving engineers dependent on TIA Portal for screen design and HMI configuration.
That gap has now closed. SIMATIC AX WinCC Unified Elements gives automation engineers a single, unified, IT-style environment where both control logic and its operator interfaces can be developed side by side, using the same workflows that IT software developers have relied on for years.
Two Ways to Build: Visual Design Meets Code-First Engineering
One of the defining features of the new tool is its dual-mode design approach. Engineers can build HMI screens in two distinct ways within the same AX Code environment — which is itself built on Microsoft Visual Studio Code, already familiar to millions of developers worldwide.
Visual Design Mode: For engineers accustomed to traditional HMI development, the tool offers a graphical interface reminiscent of TIA Portal's familiar screen-building approach. Drag, configure, and deploy — all within the modern AX Code shell.
Code-First Mode (YAML): Every screen, faceplate, and HMI element can be defined entirely in human-readable YAML files. This unlocks capabilities that were never possible with traditional binary project files: diff comparisons between versions, pull request reviews, AI-assisted code generation, and full integration into CI/CD pipelines.
Market Trend: The convergence of IT and OT — a cornerstone of Industry 4.0 — is accelerating. Tools like SIMATIC AX WinCC Unified Elements that bring Git-based version control, modular reusable libraries, and text-based project definitions to factory-floor engineering are no longer experimental. They are becoming the baseline expectation for competitive manufacturing operations.
Why Version Control Changes Everything
Traditional automation projects have long been plagued by a fundamental limitation: binary project files that cannot be meaningfully compared, merged, or reviewed outside the proprietary engineering tool that created them. SIMATIC AX WinCC Unified Elements changes this paradigm by making the entire project — PLC code and HMI definitions alike — text-based and version-control-friendly.
When a commit captures both a tag change in the PLC program and the corresponding binding in the HMI, code review becomes holistic. One pull request reviews both halves of a feature. This dramatically reduces integration errors and accelerates the path from development to deployment.
Key Technical Innovations
Full Project Generation from YAML
At the software's core, engineers can build complete automation projects by combining AI-generated code, configurations, scripts, and reusable library packages into a ready-to-deploy build — all defined in human-readable YAML files that can be version-controlled, shared, and reviewed.
Unified IDE Experience
AX Code — the VS Code–based development environment — now hosts both SIMATIC AX (PLC logic) and WinCC Unified Elements (HMI) side by side in the same Explorer panel. Engineers can work on PLC code and HMI screens within a single window, eliminating the friction of switching between disparate tools.
Single Git Repository
One .git folder at the parent level tracks both PLC and HMI projects together. A single commit can span control logic changes and their corresponding operator interface updates, enabling genuine feature-branch workflows for automation projects.
AI-Assisted Development
The text-based YAML format makes SIMATIC AX WinCC Unified Elements inherently compatible with AI code-generation tools. Engineers can leverage AI to generate, validate, and refine automation code — a capability Siemens has been actively expanding with its Eigen Engineering Agent initiative.
What This Means for Industrial Automation Teams
The launch addresses a structural challenge facing manufacturing globally: an aging automation workforce and difficulty attracting younger engineering talent. By adopting IT-style workflows — VS Code, Git, YAML, CI/CD — Siemens is making industrial automation engineering more accessible to software-trained professionals who may never have used traditional OT tools like TIA Portal.
"For decades, we've helped manufacturers automate their production lines; now we're automating the automation itself," said Adrien Amar, global business development manager at Siemens. "With SIMATIC AX WinCC Unified Elements, engineers can generate, validate and deploy automation projects at software speed — using AI generation, CI/CD pipelines and the version control that IT teams have relied on for years."
Availability and Next Steps
SIMATIC AX WinCC Unified Elements is available now, exclusively in the United States, marking a strategic initial rollout in one of the world's largest and most automation-intensive manufacturing markets. Siemens is offering a free trial to qualified industrial customers through its website at www.siemens.com/unified-elements/.
Analyst Insight: The US-first launch strategy is telling. With approximately 400,000 manufacturing job openings and an estimated 3.8 million additional roles needed by 2033, the American industrial sector faces acute labor shortages that can only be addressed through productivity-boosting tools like SIMATIC AX. Expect global rollouts to follow as Siemens validates the US market response.
Frequently Asked Questions
How does SIMATIC AX WinCC Unified Elements differ from TIA Portal?
TIA Portal is Siemens' traditional OT engineering platform that uses binary project files and a proprietary interface. SIMATIC AX WinCC Unified Elements is built on VS Code, uses human-readable YAML for project definitions, integrates with Git for version control, and supports IT-style workflows such as CI/CD pipelines, pull requests, and AI-assisted code generation — none of which are natively available in TIA Portal.
Can I use SIMATIC AX WinCC Unified Elements alongside my existing TIA Portal projects?
Yes. Siemens has designed SIMATIC AX to work in tandem with TIA Portal. Technology objects and hardware configurations can be defined once in TIA Portal, while the control logic and HMI elements are developed in the AX environment. A direct (delta) download to the PLC is supported, enabling hybrid workflows that leverage both platforms.
What skills do I need to start using this tool?
Engineers familiar with Visual Studio Code, Git-based version control, and text-based configuration formats like YAML will find the environment immediately intuitive. For traditional TIA Portal users, Siemens provides a visual design mode that mirrors familiar HMI-building workflows, lowering the barrier to entry while allowing gradual adoption of code-first approaches.
Is SIMATIC AX WinCC Unified Elements available globally?
As of its July 28, 2026 launch, the product is available exclusively in the United States. Siemens has not yet announced a timeline for expansion into other regions, though the company's pattern with previous SIMATIC AX releases suggests broader availability will follow after the initial market validation phase.
