News

18.06.26

Digital twins: Simulation as a driver of innovation

Digital twins link real-world products, plant and processes to a virtual replica that evolves alongside them throughout their entire life cycle.

Combined with simulation, this enables robust decision-making – from the initial design through to virtual commissioning and ongoing operation.

The result: lower risks, faster approvals, higher availability and targeted improvements.
For industrial companies, the digital twin is therefore a strategic driver of innovation.

What digital twins really are – far more than just a 3D model

A digital twin is a virtual representation of a physical object or process. It comprises geometry, material and state data, behavioural models and simulation results. A key feature is the continuous synchronisation of data between the real world and the virtual model. If anything changes in the product, the production line or the application scenario, the digital twin is updated – and conversely, insights from the twin feed back into design, production and service. This creates a learning system that not only documents decisions but actively improves them.

The core idea: the integration of simulation and real-time data makes assumptions explicit, allows variants to be compared without risk and identifies conflicting objectives at an early stage. This improves the quality of decisions – and speeds up implementation.

Why is the lever simulated?

Without simulation, the digital twin remains a static representation. It is only the ability to run through ‘what-if’ scenarios that unlocks its full potential. Typical questions that can be answered using digital twins and simulation:

  • Design: Will the component withstand thermal and mechanical loads? How does the system react to tolerances and manufacturing variations?

  • Production: What cycle time is realistic? Where do bottlenecks arise in the material flow? How do layout changes affect throughput and buffers?

  • Operation: How does the condition of a plant evolve? Which parameters provide early indications of wear and tear? Which maintenance strategy minimises downtime?

The advantage: Decisions are not based on gut feeling, but on model-based, repeatable results.

Three Perspectives on Digital Twins

1

Product twin

Visualisation of geometry, materials, functions and simulation results (e.g. structural, thermal, fluid flow, electromagnetic). Benefits: evaluate design variants more quickly, identify conflicting objectives, and ensure that bills of materials and parameters remain consistent.

2

Production twin

Virtual representation of production cells, lines, logistics and control systems – including simulation of cycle times, layout, resources and control logic. Benefits: virtual commissioning, predictable ramp-up, lower changeover costs.

3

Performance twin

Linking the model to field data (e.g. vibration, temperature, energy, quality). Benefits: predictive maintenance, optimised operating strategies, fact-based improvements in design and production.

Business benefits: Drivers of innovation for efficiency, quality and sustainability

1

Faster decisions

Variants can be evaluated digitally before expensive hardware is produced. This shortens development and approval cycles.

2

Greater plant efficiency

The digital twin identifies bottlenecks, optimises changeover and set-up times, and stabilises processes.

3

Lower risks

Changes are validated virtually; the simulation shows which side effects are to be expected.

4

Transparent quality

Measurement data and model knowledge provide a complete chain of evidence from requirements right through to the test result.

5

Sustainability

Resource and energy consumption are quantified; scenarios point the way to reductions in CO₂ emissions and material use.

Architectural building blocks for robust digital twins

A robust setup comprises three layers:

  1. Domain models & multiphysics simulation
    : Disciplines such as structural, thermal, fluid flow and EM are modelled individually and in combination. This enables realistic load cases and boundary conditions to be represented.

  2. Data platform & time series
    : State and event data are securely recorded, versioned and assigned to the digital twin in context (variant, batch size, load collective). This is the only way to keep simulation and reality in sync.

  3. Governance & Security
    Roles, access rights, certificates, versioning and compatibility of the digital twin states are defined. This prevents siloed solutions, protects IP and enables auditability.

Use cases throughout the life cycle

Concept & Design

  • Simulate variants in a comparative manner (material, dimensions, tolerances)

  • Define target parameters (e.g. weight, stiffness, thermal behaviour)

  • Identify interdependencies (e.g. thermal behaviour ↔ service life)

Detailing & Verification

  • Check couplings (structure/thermal/fluid) for boundary cases

  • Compare simulation results with reference cases

  • Manage change control via requirements ↔ model ↔ test

Process & production planning

  • Simulate material flow, buffers, cycle sequences and layouts with a wide range of variants

  • Prepare control logic for virtual commissioning

  • Run through ramp-up scenarios and mitigate risks

Operation & Service

  • Feed the performance twin with field data

  • Derive condition forecasts and service windows

  • Establish feedback loops in design and production

Process model: Creating your first digital twin in 90 days

1

Weeks 1–2 – Defining the use case

Define objectives, KPIs and scope (e.g. reduction in set-up time, energy efficiency, throughput). Clarify data sources, sensor technology and the security model.

2

Weeks 3–4 – Setting up the architecture and tools

Select twin type(s) (product/production/performance), outline data paths, and define the modelling plan and responsibilities.

3

Weeks 5–8 – Modelling & Simulation

Build domain models, run scenarios, carry out initial validations against measured values, and create reporting templates.

4

Weeks 9–10 – Field coupling

Integrate live data, calibrate deviations, define early-warning rules (e.g. thresholds, trends, residuals).

5

Weeks 11–12 – Industrialise

Finalise versioning, roles, processes and dashboards; incorporate lessons learnt into templates; agree on a rollout schedule.

Governance: Quality, Security, Traceability

  • Traceability: Requirements ↔ models ↔ results must be consistently linked and versioned.

  • Validation: Each model is assigned reference cases and acceptance criteria; regular plausibility checks ensure the twin remains reliable.

  • Security by Design: Role-based access, segmentation and certificate management are mandatory – particularly for twins spanning multiple sites.

  • Compatibility: Naming and versioning conventions, interface standards and regression tests ensure seamless collaboration between different teams and systems.

KPIs for Digital Twins as Drivers of Innovation

  • Time-to-Decision (time taken to reach a sound decision)

  • First-pass yield (initial approvals without rework)

  • Iterations until approval (digital vs. physical)

  • Throughput / OEE in production

  • Reduction in the number of prototypes (units & costs)

  • Ramp-up curve (time to rated output)

  • Downtime minutes per month and Mean Time Between Failures
    These key performance indicators link the Digital Twin directly to business objectives and make progress measurable.

Common pitfalls – and how to avoid them

  • “A pretty twin without data”: Without reliable time series and contextual data, the benefits are lost. Plan the data pipeline first.

  • Siloed twins: Product, production and performance twins must be linked end-to-end, otherwise there will be no feedback.

  • Security considered too late: Access rights, certificates and versioning need to be addressed at the outset – not as an afterthought.

  • No business fit: The use case needs clear KPIs; otherwise, the twin becomes a demo rather than a value driver.

  • Lack of implementation: Results must be translated into layouts, work plans and service processes – including assigned responsibilities.

Practical implementation: roles, processes, tools

  • Digital Twin Product Owner: responsible for the target vision, KPIs and roadmap.

  • Domain experts (mechanics, thermodynamics, EM, flow): model and validate the simulation.

  • Data/IT Team: responsible for data collection, storage, backup and provision.

  • Operations/Service: uses the digital twin for decision-making; feedback is fed back into the model.

  • Quality/Compliance: ensures traceability and auditability.

A two-track approach has proven effective in terms of process: an ‘Exploration Track’ for new models and use cases, and an ‘Industrialisation Track’ for transitioning to standard operation. This ensures the Digital Twin remains both innovative and stable.

Outlook: Systematically scaling digital twins

Those who consistently implement digital twins alongside simulation will build a lasting competitive edge. Industry benefits from faster cycles, more robust processes and transparent decision-making – across design, production and operations. The key lies not in a single tool, but in the combination of reliable models, a clean data foundation and clear governance. With this foundation in place, the digital twin becomes a continuous driver of innovation.

Topics

General

Mehr entdecken

Weitere Beiträge.

Es sind keine weiteren Posts zu diesem Thema vorhanden.
Beiträge werden geladen...