Digital Twin
A digital twin is a software model of a physical asset (a machine, a production line, a building, a vehicle, a city) that mirrors its current state in near real time. Combining design-time models (CAD, BIM), live operational data (IoT sensors, OPC UA) and analytical layers (ML, simulation), digital twins enable virtual experimentation, monitoring and optimisation without touching the physical asset. For DACH manufacturers, digital twins are a foundational element of Industrie 4.0 strategies, with the Asset Administration Shell (AAS) specification driving standardisation.
Types of digital twins
Three categories of digital twin are commonly distinguished. (1) Digital twin of a product: software model of a specific manufactured product instance, used through its lifecycle for warranty service, predictive maintenance and performance optimisation. (2) Digital twin of a production system: model of a machine, cell or full production line used to simulate process changes, optimise throughput and train operators. (3) Digital twin of infrastructure: model of buildings, energy networks, ports, smart cities. The first two are most relevant to ERP-bearing manufacturers. Twin fidelity ranges from simple data dashboards (live values, no simulation) to high-fidelity simulation models that can predict behaviour under hypothetical conditions.
Asset Administration Shell (AAS)
The Asset Administration Shell (AAS) — Verwaltungsschale in German — is the standardised digital-twin specification developed by the German Plattform Industrie 4.0 and the Industrial Digital Twin Association (IDTA). AAS defines a uniform structure for representing asset information, with submodels for technical data, maintenance, energy consumption, sustainability metrics and more. The specification is open, vendor-neutral, and increasingly adopted across DACH machinery and automotive supply chains. The VDMA-driven umati specification complements AAS at the machine-communication layer through OPC UA. Companion specifications exist for specific machine categories, allowing standardised digital twins across vendors.
ERP integration
Digital twins are upstream of ERP rather than embedded in it. The typical flow: twin platforms (Siemens Xcelerator, PTC ThingWorx, GE Digital APM, Microsoft Azure Digital Twins, Bosch IoT Things) maintain the live model; the ERP consumes aggregated metrics for asset accounting, maintenance scheduling and capex planning. Specific integration patterns: (1) Asset lifecycle: ERP-managed asset records reference the twin for current condition and remaining useful life. (2) Maintenance triggers: twin-detected anomalies create work orders in the ERP's plant-maintenance module. (3) Sustainability reporting: per-asset energy and emissions data flow from twin to ERP for CSRD reporting. (4) Service-business support: machinery vendors selling outcome-based contracts (pay-per-use, performance-guaranteed) use twins to monitor customer-side asset performance.
DACH adoption status
Adoption is uneven. Large industrial OEMs (Siemens, Bosch, ABB, Schneider) operate mature digital-twin platforms for their own and their customers' assets. Tier-1 automotive suppliers and large machinery exporters increasingly invest in twins for after-sales service and predictive maintenance. Mid-market manufacturers are mostly at pilot or early-production stage, with regulatory and sustainability reporting pressure (CSRD, EU Machinery Regulation) accelerating adoption from 2025 onwards. The umati and AAS specifications driven from German Plattform Industrie 4.0 provide a vendor-neutral foundation that lowers the lock-in risk historically associated with digital-twin platforms. For DACH ERP-bearing manufacturers, digital-twin readiness is becoming a standard topic in IT-strategy discussions, even where mass deployment is several years away.
Related Topics
Frequently Asked Questions
Do I need a digital twin for predictive maintenance?
Not strictly — predictive maintenance can run directly on raw sensor data without a structured twin model. But a digital twin provides the structured asset context (which sensor belongs to which component, what is its normal range, what is its history) that improves PdM model accuracy and explainability. Most mature PdM programmes evolve toward digital-twin foundations.
What does a typical digital-twin implementation cost?
Highly variable. A simple asset-monitoring twin for a single production line can be deployed in 3-6 months for 100,000-300,000 EUR. A high-fidelity simulation twin of a complete factory can cost 5-15 million EUR and take 2-4 years. Most DACH mid-market manufacturers start with the simpler end and accumulate fidelity over time.
Is AAS interoperable across vendors?
Increasingly yes. The IDTA-led standardisation has driven major industrial platforms (Siemens, Bosch, SAP, Microsoft) to support AAS submodels. Real-world cross-vendor interoperability still requires mapping work, but the situation is materially better than the closed-platform era of the early 2010s.