01
Outage approval
Evaluate planned outages against the actual recent operating state, with exhaustive N-1 + defined N-2 and Q-limit enforcement, not a stylized study case.
Raptrix Forge · Short-term planning
The planning side
of the same physics.
Forge checks outage and next-day decisions against the operating states the live system actually produced, not only a stylized case.
The risk this closes
Outage decisions made on a case the system will not be in.
An outage approved on a stylized case can meet an operating state no one studied. Forge checks the decision with N-1 and N-1-1 on states the system has actually been in, before the outage is taken.
Planning teams have always had to settle for stylized cases. The real grid moves faster than the planning case can be refreshed, and the gap between “the model we study against” and “the system we actually operate” only widens with every IBR, every data-center interconnection, every dynamic load.
Forge closes that loop. It runs on the same full-AC Newton-Raphson engine that powers Sentinel, with the same strict Q-limit enforcement, and with IBR, FACTS, and PST awareness. The difference is what you feed it: real operating states from Sentinel, replayable as canonical .rpf files.
Outage approval, next-day reliability studies, what-if asset evaluations — all happening on a high-fidelity model of what your operators saw last shift. Not stylized. Not approximated.
What Forge is for
Short-term planning, finally on the right baseline.
02
Next-day studies
Run reliability and transfer-capability studies on tomorrow’s expected topology with the operating state your control room saw last night already loaded.
03
What-if scenarios
Test asset additions, retirements, control settings, or IBR build-out against real-system contingency behavior, not against a polished baseline that hides the corner cases.
04
Reliability + economic
Transfer limits and corrective N-1 and defined N-2 studies inform reliability margin and economic evaluations on the same engine. Each flagged contingency is checked for a path back within NERC limits using available reserves and controls.
One physics core
Sentinel and Forge are the same engine, with different jobs.
There is no “ops model” and “planning model” anymore. There is one grid, one solver, one interchange format — and two teams that finally see the same picture.
Same solver
Full-AC Newton-Raphson with strict Q-limit enforcement.
Same .rpf
Read Sentinel’s real-time output directly. No format conversion.
Same audit trail
Provenance and Q-limit results travel with every case.
Same deploy story
On-prem (RHEL 10 and Windows certified), air-gapped, or cloud.
Pilot inside your environment
Pilot Forge on a real operating point.
Pick a recent operating point. We run the outage or next-day study from that State Estimator case inside your environment and walk through what a stylized case does not show.
info@raptrixpower.com · Founder direct: matthew.musto@raptrixpower.com · github.com/RaptrixPowerFlow