Raptrix Sentinel

Security studies on
the system you are running.

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.

The risk this closes

The contingencies your EMS list does not catch.

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.

How Sentinel works

Six stages. One physics core. No shortcuts.

Every solved State Estimator case becomes an exhaustively screened N-1 plus defined N-2 study — recovery-validated, certifiable, and written to SAL.

  1. 01

    Ingest

    Solved SE case · default 5 min

    RAW, PSLF, or native State Estimator exports — no rip-and-replace.

  2. 02

    Screen

    Exhaustive N-1 + defined N-2

    N-1-1 default after intervening recovery. Simultaneous N-2 is the defined common-mode list.

  3. 03

    Solve

    Full-AC Newton-Raphson

    Full-AC Newton-Raphson with strict Q-limit enforcement.

  4. 04

    Recover

    LTE / Normal-window recovery

    Each flagged contingency is checked for a path back within NERC limits using available reserves and controls. Only unrecoverable cases are surfaced.

  5. 05

    Certify

    Auditable per case

    Every filtering decision is grounded in defensible physics.

  6. 06

    Hand off

    Canonical .rpf out

    One file carries the operating state forward into planning. Every cycle also writes SAL.

What makes Sentinel different

What operators get that static lists and EMS screens cannot deliver.

01

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.

02

A short list of what cannot recover.

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.

03

Visibility operators do not have today.

Planning-grade studies on the exact current operating state, at the cadence the control room already runs, recovery-checked against LTE and Normal windows.

04

Planning gets a library of real operating states.

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.

05

A bolt-on, not a replacement.

Works with existing RAW, PSLF, or native State Estimator exports. No rip-and-replace of the EMS and no deep SCADA integration.

06

Large loads modeled the way they behave.

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.

Auditable by design

Every flagged contingency ships with a certificate.

Each flagged contingency comes with the reasons, so the desk can act on it and audit it later.

Recovery certificate
Illustrative example · synthetic test case
Still insecure
N-1 · 345 kV line outage
Steady state + large-load trip15 min · Rate B
  1. 01 Large loadsNine data-center campuses (1,800 MW) switch to backup power on their own.
  2. 02 OverloadFlow shifts onto a 138 kV line at 113% of its emergency rating.
  3. 03 RecoveryReserve redispatch inside the 15-minute window moves 729 MW. Loading falls to 102.6%.
VerdictStill over the limit after recovery. The campuses stay off until a manual reset.
Replayable · 31 stepsFingerprint 7c4a9e…b201
Technical details

Engineering choices that hold up under review.

  • Full-AC Newton-Raphson

    with strict Q-limit enforcement. A converged solution that violates generator Q limits is marked infeasible — non-negotiable physics.

  • Full-system coverage at real-time cadence

    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

    Automatic contingency selection that augments operator judgment, with no hand-maintained lists.

  • IBR, FACTS, and PST awareness

    IBR, FACTS, and PST devices are carried in the case. We do not claim device-level control modeling inside the solver.

  • Recovery within NERC limits

    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.

  • First-swing stability screening

    when dynamics data is available — on the same solved operating point. Large-load rejection scenarios today; inverter-centric models expanding.

NERC Level 3 · Large Loads

Built for the grid that’s arriving — not the one we modeled in 2010.

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.

Voltage sensitivity

Modeled natively at the bus, not assumed away with a generic load.

Up / down ramps

Rapid ramp and load-reduction schemes carried with the operating point in .rpf.

Contingency impact

Large loads are included in N-1 and defined N-2 screening, not assumed away.

IBR interaction

IBR-tagged screening. FACTS and PST devices are carried in .rpf; device-level control modeling is not claimed.

Voltage ride-through

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.

carried in .rpf
Roadmap

Sentinel Phase 2 — look-ahead advisory.

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.

Pilot inside your environment

Pilot Sentinel on a recent operating point.

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