InteractiveMap of Operations Research
Back to Modern OR Practice
ApplicationApplied06.07
Modern OR Practice

Digital Twins & What-If Systems

Living simulations connected to operational data.

Overview

Digital Twins & What-If Systems focuses on living simulations connected to operational data. In the map of OR, it connects State estimation, Scenario testing, Calibration to decisions that must be modeled, solved, explained, and revised as evidence changes.

Digital twins combine data pipelines, simulation, optimization, and monitoring to test decisions before changing a real system. The practical use case is clearest in Factories, Warehouses, Hospitals, Energy systems, where the method helps turn constraints and tradeoffs into a decision artifact someone can inspect.

Core ideas

State estimation

State estimation is a core checkpoint for Digital Twins & What-If Systems: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Scenario testing

Scenario testing is a core checkpoint for Digital Twins & What-If Systems: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Calibration

Calibration is a core checkpoint for Digital Twins & What-If Systems: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Simulation

Simulation is a core checkpoint for Digital Twins & What-If Systems: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Dashboards

Dashboards is a core checkpoint for Digital Twins & What-If Systems: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

How to use it

  1. 1Start with Factories: write the decision, time horizon, actors, and objective in operational language.
  2. 2Translate the problem into State estimation, Scenario testing, and Calibration; define units and data sources for each one.
  3. 3Build a small instance of Digital Twins & What-If Systems that can be solved or simulated by hand inspection before using full production data.
  4. 4Compare the recommendation against a baseline policy, not just against mathematical optimality.
  5. 5Document assumptions, sensitivity results, and the conditions under which the recommendation should be revisited.

Applications

FactoriesWarehousesHospitalsEnergy systems
  • Factories: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Warehouses: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Hospitals: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Energy systems: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.

Common pitfalls

  • Applying Digital Twins & What-If Systems because the label sounds appropriate while leaving the actual decision boundary vague.
  • Treating State estimation as a technical detail instead of a modeling choice that affects the recommendation.
  • Reporting one answer without showing sensitivity to demand, capacity, costs, or behavioral assumptions.
  • Ignoring implementation details such as data quality, explainability, ownership, and how users will override bad recommendations.

Resources