The system in service
is not the case that was studied.
For operations leaders and reliability executives: the exposure is already on the system, and the tools in the control room were not built to see all of it.
N-1 and N-1-1 on the topology that is actually in service.
Planning cases describe a system someone assembled for a study. The control room is running a different one: today’s outages, today’s dispatch, today’s large loads.
What stands in for a full look is a curated list, a manual process, and limits set conservatively enough to cover what the list does not. Those lists go stale as soon as the topology changes.
No one is studying the full set of credible N-1-1 contingencies on the live system: not the EMS list, not the reliability coordinator, not the ISO/RTO. None of them will catch it for you.
An 8,760-hour study still misses the operating point.
Planning studies peak days and builds scenarios from them. Even an 8,760-hour study runs on cases someone chose, not on the topology the system will actually be in.
The combinations of outages the real system can be in are effectively unlimited. So real-time operations keep running into states no one studied.
Fidelity on the wrong system does not close the exposure.
Use the model you already paid to build.
Raptrix takes the current State Estimator case — the EMS model the utility already maintains — and runs N-1 and N-1-1 from that operating point. It alerts on risks the current tools do not show, and it returns recovery-validated results with a certificate for each finding.
Operators do not have to hand-define every N-1-1 contingency as a prerequisite. Screening augments judgment and does not replace the desk.
What operators would see that they cannot see today
- Which single trips would push a data center or chip plant outside its voltage ride-through profile.
- Which N-1-1 sequences would leave no path back within NERC limits, before the first outage happens.
- Voltage and thermal exposure, plus transient screening where dynamics data is available.
The events that make the news are the visible ones.
Two recent public events show the pattern:
- In outage season, several facilities were already out ahead of a planned switching operation.
- At high load, a single trip sent a large block of data-center load to backup power at once.
The exposure is not only thermal. These events involved voltage and transient behavior. Many more like them cost money and credibility without national coverage.
These are the class of exposures the platform is built to surface from the current operating point.
Your model stays on your network.
- 01
Pick a recent operating point with your team.
Choose the case that matches how the system is actually running.
- 02
Run inside your environment.
Raptrix runs N-1 and N-1-1 from that State Estimator case inside your environment, on-prem or air-gapped. Your model does not leave your network.
- 03
Walk through what the list missed.
We walk through what the current list does not show, with the certificate for each finding.
No workflow change. No day-one commitment to act on outputs. Pilot in weeks.