A simulation tells you what the system should do. A digital twin tells you what the system is doing — and keeps updating that answer for as long as the real system stays switched on.
ETAP has earned its place in every serious power system study — load flow, short circuit, protection coordination, arc flash, transient stability. None of that is in question. What is worth being precise about is where that kind of study stops, and where a digital twin picks up a different job entirely.
A digital twin answers: "What is happening right now?"
Confusing the two leads to two different mistakes: expecting a static study to catch a live equipment fault, or building an expensive real-time platform for a question a one-time study would have answered in an afternoon.
01What traditional simulation actually is
A tool like ETAP works from a model — buses, lines, transformers, loads, relays — built once, then run against a defined scenario. The engineer sets the conditions: this load level, this fault location, this switching sequence. The software solves the equations and returns a result for that one scenario.
- Load flow analysis
- Short-circuit studies
- Protection coordination
- Arc flash assessment
- Transient stability
- Motor starting studies
The model is a snapshot of how the network is designed to behave. It does not know that a transformer has been running ten degrees hotter than normal for the past three weeks, or that a breaker's operating time has drifted since it was last tested. It knows what the equipment was rated to do — not what it is actually doing today.
02Where the study stops
A traditional study is inherently offline and single-scenario. Run it, get an answer, close the file. The network keeps changing after that — loads shift, equipment ages, switching happens — and the study does not know any of it happened.
That is not a flaw in the tool. A protection coordination study or an arc flash report does not need to run continuously — it needs to be right for the design conditions it was built to check. The gap only appears when a one-time study is asked to do a monitoring job it was never built for.
03Where the digital twin begins
A digital twin starts from the same kind of network model, but adds something a traditional study never has: a live, continuous data connection back to the real equipment. Sensors, meters, and protection relays feed measurements into the model in near real time, and the model updates itself against what is actually happening on site.
The twin is not asking "what would happen if this transformer overloaded" as a hypothetical. It is watching the transformer's real loading, real temperature, and real trend line, and comparing that against what the design model expects — continuously, without anyone re-running a study.
04The three differences that matter
Time
A study is a point-in-time answer for one defined scenario. A twin is a running process that never stops comparing model to reality.
Data direction
A study takes assumptions in and produces a result. A twin takes live measurements in continuously and produces an updated state — the data flow never closes.
Purpose
A study answers a design or planning question: is this protection scheme coordinated, will this bus survive this fault. A twin answers an operational question: is this asset degrading, is this load pattern drifting from what the design assumed, should maintenance happen before or after it fails.
05They are not competitors
A digital twin does not replace ETAP-style analysis — it depends on it. The twin's baseline model, its fault thresholds, and its expected operating envelope are themselves built from traditional load flow and short-circuit studies. Without that groundwork, a twin has live data and nothing correct to compare it against.
How the two fit together in practice
Build the design model
Load flow, short-circuit and protection studies establish the correct baseline in ETAP.
Validate against commissioning data
Real measurements at energisation confirm the model matches the physical network.
Connect live data feeds
Meters, relays and sensors are wired into the model as a continuous data source.
Run the twin against the baseline
Real-time readings are compared to the design model's expected behaviour.
Flag deviation, not just failure
Gradual drift in loading, temperature or timing is caught before it becomes a fault.
Feed findings back into future studies
What the twin observes over time refines the assumptions used in the next design study.
A concrete example
A distribution transformer feeding an industrial load, sized and protected using a standard ETAP short-circuit and protection coordination study at design stage.
What each approach can and cannot tell an engineer:
- ETAP confirms the transformer and its protection are correctly rated for the worst-case fault at commissioning.
- ETAP has no way of knowing the load profile six months later has shifted due to a new production line.
- A digital twin, fed by real loading and temperature data, flags that the transformer is now running consistently closer to its thermal limit than the original study assumed.
- That flag prompts a targeted re-study — not a guess, and not a wait until failure.
Neither tool alone produces that outcome. The study without the twin misses the drift. The twin without the study has no rated limit to compare the drift against.
What each one is worth
Where this goes
Traditional simulation is not being replaced — it is being extended. Every digital twin worth deploying still needs a correctly built ETAP-style model underneath it. What changes is that the model no longer closes when the report is generated. It stays open, keeps listening to the network it describes, and starts doing a job no static study was ever meant to do.
The twin tells you whether it still is.