Analysts get their apps out in days.
The rules on the way out are your engineers'.
Siting studies, interconnection intake, load forecasting, EIA filings. Grid engineering keeps the rulebook. Compliance keeps the audit trail. The analyst gets to move quickly, and can't ship around either group.
A product, not a services engagement.
The rulebook, the templates, and the path to production are all in the box, so a second customer doesn't need the same white-glove rollout the first one did. We'll be straight with you about this — we've proven it once, not five times.
Siting blocks
Setback checks, wetland classification, viewshed and glint. Written and maintained by grid engineering.
Interconnection intake
Queue position, cluster study inputs, curtailment assumptions — captured in a form your engineers already trust.
Load forecasting
Weather-normalized and DER-adjusted. The forecast has to reconcile back to what SCADA is actually reporting.
Reporting scaffolds
EIA-861, FERC 715, state PUC filings. The audit trail behind each number is there from the first draft.
External calls
fetch:noaa, fetch:eia, publish:internal — declared up front, checked when the app is built and again when it makes the call.
Day-two monitoring
Already wired up. If usage drops off, there's a defined path back. The analyst never has to stand up monitoring on their own.
A siting call the model likes and the engineer wouldn't.
Class III wetland, 82 meters from the array. The analyst's model is satisfied. The grid engineer's rule isn't, and that's the one the gate is checking against.