Operating the Software‑Defined Factory: How Audi Runs Virtualized Production

KEYWORDS: EC4P, Operations, Software‑Defined Factory, Manufacturing KPIs

Overview

What motivated Audi to redesign its traditional shop floor architecture? The automotive industry is changing rapidly in the face of new cost structures driven by the electric vehicle transition and fierce competition from China. In Audi’s view, the traditional model of delivering production equipment floor is outdated, and the future is software-driven production.

Audi calls it “IT-based factory automation,” a concept that is turning IT/OT convergence theory into practice at the premium automaker. To achieve this, Audi kicked off an initiative back in 2018 called Edge Cloud 4 Production (EC4P). The goal is to replace thousands of shop floor industrial PCs with a much more efficient and flexible IT architecture of scalable local servers, effectively uniting the cloud and the edge on the shop floor.

This ARC View is part of a series of reports that dig deeper into the cultural and technical aspects of EC4P.

Key Takeaways

• Virtualization makes production availability an end‑to‑end concern. Reliability is no longer determined by individual systems, but by the interaction of shop floor assets, networks, virtualization platforms, and applications.
• A structured operating model is critical. Clear cross‑layer responsibilities, integrated observability, and coordinated incident response are prerequisites for stable, virtualized production.
• Operational complexity shifts rather than disappears. Standardized IT technologies increase flexibility and scalability, but introduce new dependencies that must be explicitly managed.
• Manufacturing KPIs remain the primary success metrics. Lost units, rework, and takt time impact continue to anchor performance management and operational priorities.

Why Virtualized Production Requires a New Operating Model

Audi is fundamentally redesigning shop floor operations to support electric, software-defined vehicles amid rising cost pressure and intensifying global competition. The legacy operating model consisting of isolated industrial PCs, tightly coupled hardware, and “fix-on-site” maintenance cannot deliver the flexibility, scale, security, or speed now required. Edge Cloud 4 Production (EC4P) shifts automation workloads to a virtualized edge cloud platform, enabling standardized deployment, rapid change, and automated failover rather than rip-and-replace recovery.

EC4P introduces virtualization, data center technologies, and cloud principles into production. These capabilities improve flexibility and efficiency, but they also add operational complexity and blur responsibility boundaries. Availability is now an end-to-end outcome across shop floor assets, networks, virtualization platforms, and applications.

Audi’s new operating model for virtualized automation aligns layers, ownership, tools, and KPIs to ensure resilient, scalable production. It emphasizes integrated monitoring, cross-layer incident response, and linking technical health to manufacturing impact (lost units, rework).

From Hardware Centric Automation to Software Defined Production

Automotive manufacturing is experiencing a structural transformation from hardware‑centric automation to software‑defined production. Historically, reliability depended on robust PLCs, isolated networks, and local troubleshooting. When a component failed, maintenance often had to “rip and replace” hardware on the line.

Virtualization changes both the architecture and the recovery model. Moving automation workloads into data center environments improves standardization, scalability, and speed, but introduces IT complexity and tight coupling across shop floor, network, virtualization, and application layers. As a result, maintenance becomes service centric. Some components are designed with redundancy. If one fails, workloads fail over to backup capacities and move automatically to keep production running. Audi’s EC4P initiative demonstrates this shift in a real, mission‑critical, safety‑relevant production environment.

Layered View of the Virtualized Production Environment

In a software-defined factory, production reliability depends on coordinated operations across four tightly coupled layers.

Shop Floor Layer

The shop floor is diverse and complex, spanning many devices, robots, vendors, and operators. Visibility is limited, and troubleshooting often depends on experience and manual intervention; visualization and predictive maintenance remain important.

Networking Layer

Networking becomes mission critical. Air-gapped assumptions no longer hold as production depends on continuous connectivity across private and public clouds. If communication fails, production stops, so the network must be resilient and quickly repairable.

Virtualization Layer

Virtualization brings IT technologies into production: commodity infrastructure, strong monitoring/logging, and defined failure domains. However, SLAs typical for IT operations and response times often fail to meet manufacturing needs, especially seconds-level expectations.

Application Layer

Applications move from local PCs to data centers and/or local data rooms and must communicate across all layers to control machines and processes, support human working steps, and ensure quality. This increases failure complexity and blurs ownership. When a manufacturing process stops, the cause may sit in the app, virtualization, network, or shop floor.

Operating a Virtualized Automation Architecture

Operating a virtualized automation architecture presents new challenges. Without a clear operating model, organizations face longer downtime from unclear ownership, siloed monitoring, and SLAs typical for IT operations that don’t match manufacturing expectations. The tightly coupled layers described here increase operational dependencies and complexity. Disruptions in any layer can cascade and impact other layers. As a result, issues can’t always be resolved within a single domain, and production behavior emerges from cross-layer interactions. Addressing this requires a structured operating model that aligns teams, tools, and responsibilities, enables cross-layer visibility, and delivers the responsiveness automotive production demands. Reliability is therefore defined by the resilience of the integrated stack, not individual components.

Evolving the Operations Team

Virtualized production environments require a fundamentally different operations model. At Audi, this includes remote operations teams available 24/5 with reaction times of seconds rather than minutes. This represents a significant shift from traditional OT and IT practices and places new demands on skills, collaboration, and tools.

Effective incident handling requires close collaboration between operations teams and neighboring domains such as networking infrastructure and platform teams. Joint fault detection and resolution across layers is essential to minimize downtime. Ideally, teams are alerted to potential issues before they impact production, for example, when an application approaches resource limits.

Tools and Observability in a Multi Technology Environment

Technology vendors typically provide tools for their specific domain, such as virtualization management suites, networking infrastructure monitoring, and APIs for individual device monitoring. However, these tools are often siloed and optimized for individual layers rather than end to end production visibility.

In a virtualized shop floor environment, operational complexity can only be managed through integrated monitoring and observability. Dashboards and management packs are used to correlate data across layers to support rapid root cause analysis. The example scenario of a virtual PLC stopping due to an expired license caused by a lost connection to a management system, demonstrates the need for cross‑domain visibility.

Production Relevant KPIs and Performance Management

From a manufacturing perspective, performance management must remain anchored in production outcomes. A classic automotive KPI is “lost units,” which counts vehicles that cannot be built due to disruptions, while quality and rework metrics capture the extent to which corrective actions occur either within the takt time or downstream at the end of the line.

In virtualized production, these KPIs must be tracked alongside technical health indicators across the stack. Because layers are tightly coupled, a localized issue in networking, virtualization, or an application can quickly degrade end-to-end availability and production reliability. This interdependence elevates redundancy and fault tolerance from infrastructure choices to production safeguards. While they add architectural complexity, they are essential to prevent small technical failures from cascading into measurable production losses.

Culture and Change Management

Technology alone is not sufficient to ensure success. Culture plays a critical role in enabling virtualized production. At Audi, an operating mindset and early alignment between IT and OT stakeholders were key success factors. Securing buy-in from OT maintenance teams early, and running joint operating/architecture working sessions with ecosystem partners, helped break down silos, standardize ways of working, and create shared ownership for availability, incident response, and continuous improvement in the new architecture.

Conclusion

Audi’s Edge Cloud 4 Production initiative demonstrates that software‑defined production can be successfully applied to mission‑critical automotive manufacturing when supported by an appropriate operating model. Virtualization fundamentally changes how availability, reliability, and responsibility must be managed. Production performance is no longer determined by individual systems, but emerges from the interaction of shop floor assets, networks, virtualization platforms, and applications. As a result, stable production depends on clear cross‑layer ownership, integrated observability, and operational response capabilities aligned with manufacturing time horizons.

Audi’s experience shows that IT/OT convergence is as much an operational and organizational challenge as it is a technical one. Technically, it requires designing and securing a tightly coupled, virtualized stack across shop floor, network, platform, and applications. Operationally, it demands integrated observability, disciplined change and recovery, and incident response aligned to manufacturing time horizons. Organizationally, it depends on clear cross‑domain ownership, escalation paths, and shared accountability across IT, OT, and partners. Together, structured operations, cross domain accountability, and production anchored performance management form a practical blueprint for industrial organizations pursuing virtualized, software defined production architectures.
 

ARC Advisory Group clients can view the complete report at the ARC Client Portal.

Contact Us if you would like to speak with the author.

Obtain more ARC In-depth Research Market Analysis.