Ride-through studies in hours, not weeks.
EMT Pilot predicts, runs and documents PRC-029 compliance studies for solar, wind and battery plants. Claude-powered agents drive the EMT simulator, catch model setup errors before you hit run, and write the report your utility expects.
The bottleneck in every interconnection queue
Every inverter-based plant connecting to the US grid must prove it rides through faults, frequency excursions and phase jumps (NERC PRC-029). That proof is an electromagnetic-transient (EMT) study: dozens of simulation cases, each needing a tuned initial operating point, correct profiles, correct measurement channels, and a report hundreds of pages long.
Expensive iterations
A single mis-copied parameter or missing profile file is discovered only after an overnight batch finishes. Tuning the plant controller to the required power factor takes several full re-runs per operating point.
Scarce engineers
EMT studies need specialists who know the simulator, the OEM inverter models and the standard. Most consultancies have a backlog measured in months.
Manual reporting
Extracting hundreds of plots, checking each against the ride-through curves and assembling a consistent English report is still done by hand.
What EMT Pilot does
Three modules that sit beside your existing simulator and OEM models. Nothing is replaced; the simulator remains the source of truth.
Offline predictor
Reads the project files alone, no simulation, and predicts the point-of-interconnection voltage trace for every case, plus the controller set-points needed to land on the target power factor.
- Source impedance derived from the circuit, not from labels
- Peer check flags parameters that differ from sibling cases
- OEM current-injection rules (SMA, PE) from vendor manuals
Simulator agent
A Claude agent operates the EMT simulator through an MCP server: generates the case set from a rules file, tunes the base cases, builds and runs parallel simulation sets, and reads the results back.
- Works with PSCAD™ today; EMTP and PSS®E CONEC planned
- Relay and breaker logic traced from the model, not assumed
- Every action logged for engineer review
Compliance report writer
Extracts the required channels, overlays the standard's ride-through curves, explains anomalies in plain English, and assembles a report in your firm's template with retrieval over the current NERC standard text.
- 300-page, 160-figure report produced from one command
- Each explanation cites the clause it relies on
- Human sign-off is required before release
How it works
An engineer stays in the loop at every stage. EMT Pilot removes the waiting, not the judgement.
Built on Claude
Claude Code and the Claude API are the operating layer of EMT Pilot. Claude reasons over the model structure, chooses the correct event construction for each case, explains results against the standard, and drafts the report. The numerical predictor and the simulator do the physics; Claude does the engineering workflow.
# one command: predict, check setup, export hand-off package emtpilot predict --models ./plant_model.zip --export ./handoff # agent session (Claude Code + simulator MCP server) > tune the three base cases to PF 1.00 / 0.95 lag / 0.95 lead, > then generate and run the 106-case PRC-029 set ✓ 6/6 base cases converged in 2 iterations ✓ 106 cases, 18 parallel sets, 106 result files ✓ relay scan: 0 trips · 94 recovered · 12 flagged for review
Validation to date
Predictions were made from model files only, then scored against the simulator output. Figures are mean absolute error of point-of-interconnection voltage in the event window, per unit.
| Plant type | Inverter OEM | Grid | Cases scored | Mean error (pu) |
|---|---|---|---|---|
| Solar, 345 kV | Power Electronics | SCR 50 | 53 | 0.0027 |
| Solar, 138 kV | SMA | SCR 50 | 56 | 0.0015 |
| Wind, 345 kV | GE | SCR ≈ 50 | 53 | 0.0067 |
| Wind, 345 kV (earlier revision) | GE | SCR ≈ 50 | 52 | 0.0076 |
| Wind, 345 kV | GE | Stiff bus | 53 | 0.0005 |
| Solar, 345 kV | Sungrow | Stiff bus | 53 | 0.0001 |
| BESS, 345 kV | SMA | Stiff bus | 106 | run & reported |
Predictions are a planning and error-catching tool. They are not evidence of ride-through compliance, which still comes from the simulator run with the OEM's validated models. We say this in every report we produce.
Team
Power-systems engineers who have spent the last year running PRC-029 studies by hand, and decided to automate the parts that do not need a human.
Request a pilot
We run a free prediction pass on one of your existing study models and show you what we would have caught. One week, no simulator licence needed on our side.