No hand-maintained contingency lists.
Exhaustive N-1 on the live case, simultaneous N-2 from your defined common-mode list, and sequential N-1-1 on by default.

Sentinel runs N-1 and N-1-1 from the State Estimator case your control room already has, and surfaces the contingencies a curated list does not catch. Each finding comes with a certificate.
Which single trip pushes a data center or chip plant outside its ride-through profile. Which N-1-1 sequence leaves no path back within NERC limits. Planning did not study these conditions on today’s topology, and the EMS list will not catch them.
Your control room is running yesterday’s assumptions on tonight’s grid. The State Estimator solves a high-fidelity picture every few minutes — and then your tools approximate everything they do with it.
Sentinel takes the SE case you already have, screens every credible contingency at planning-grade physics, validates whether the system can actually recover within NERC limits, and hands you back a short, defensible list of what actually matters — before the next interval ticks.
And it does it without rip-and-replacing your EMS. No new SCADA. No new contingency lists to maintain. No fidelity traded for speed.
Every solved State Estimator case becomes an exhaustively screened N-1 plus defined N-2 study — recovery-validated, certifiable, and written to SAL.
RAW, PSLF, or native State Estimator exports — no rip-and-replace.
N-1-1 default after intervening recovery. Simultaneous N-2 is the defined common-mode list.
Full-AC Newton-Raphson with strict Q-limit enforcement.
Each flagged contingency is checked for a path back within NERC limits using available reserves and controls. Only unrecoverable cases are surfaced.
Every filtering decision is grounded in defensible physics.
One file carries the operating state forward into planning. Every cycle also writes SAL.
Exhaustive N-1 on the live case, simultaneous N-2 from your defined common-mode list, and sequential N-1-1 on by default.
From the current operating point, Sentinel surfaces the few contingencies with no path back within NERC limits using available reserves and controls, and states the reasons.
Planning-grade studies on the exact current operating state, at the cadence the control room already runs, recovery-checked against LTE and Normal windows.
Every cycle writes the Sentinel Archive Library (SAL): the solved case as a canonical .rpf, plus replayable events. Planning gets cases from actual operating conditions, not stylized studies.
Works with existing RAW, PSLF, or native State Estimator exports. No rip-and-replace of the EMS and no deep SCADA integration.
Voltage ride-through and campus transfer are evaluated from load profiles on the live case, for large, voltage-sensitive, fast-changing loads under NERC Level 3.
Each flagged contingency comes with the reasons, so the desk can act on it and audit it later.
with strict Q-limit enforcement. A converged solution that violates generator Q limits is marked infeasible — non-negotiable physics.
Planning-grade N-1 and defined N-2 studies on the live operating point, at the cadence the control room already runs.
Automatic contingency selection that augments operator judgment, with no hand-maintained lists.
IBR, FACTS, and PST devices are carried in the case. We do not claim device-level control modeling inside the solver.
Each flagged contingency is checked for a path back within NERC limits using available reserves and controls. Q-limits stay enforced. Only unrecoverable cases are surfaced. RAS/SPS is enrichment, not closed-loop execution.
when dynamics data is available — on the same solved operating point. Large-load rejection scenarios today; inverter-centric models expanding.

Data centers and other large, electronically coupled loads behave nothing like traditional demand. Sentinel treats them as first-class citizens — so operators and planners get a defensible, physics-based view of system risk without waiting on EMS vendor roadmaps.
Modeled natively at the bus, not assumed away with a generic load.
Rapid ramp and load-reduction schemes carried with the operating point in .rpf.
Large loads are included in N-1 and defined N-2 screening, not assumed away.
IBR-tagged screening. FACTS and PST devices are carried in .rpf; device-level control modeling is not claimed.
Which contingencies push a large load outside its ride-through profile, from the load profile on the live case.
Every operating state Sentinel evaluates ships with the computational-load profile attached — seasonal envelopes, buildout ramps, voltage guardrails, and reduction schemes.
Phase 2 carries the same core forward in time. Using expected topology, commitment, and large-load forecasts, it will recommend battery and reserve positioning ahead of the hour that needs it.
Same bolt-on deployment, same .rpf record, same certificates.

Pick a recent operating point. We run N-1 and N-1-1 from that State Estimator case inside your environment and walk through what your current list does not show.
info@raptrixpower.com · Founder direct: matthew.musto@raptrixpower.com · github.com/RaptrixPowerFlow