Why operators are re-architecting around AI dispatch
// updated 14:22 UTCThe transmission and distribution layer of the UK and EU grid was engineered for a world where roughly four hundred large rotating machines produced electricity and several million passive consumers absorbed it. That world is gone. Today, more than thirteen million distributed energy resources — rooftop PV, residential heat pumps, EV chargers, behind-the-meter batteries, aggregator-controlled flexibility — sit on the edge of the network. Each of them imposes a forecast burden, a settlement burden, and a control burden that classical SCADA and EMS systems were never designed to absorb.
The cost of that mismatch is no longer theoretical. National balancing actions in the UK now exceed two billion pounds per year. Curtailment payments for wind plants located behind transmission constraints have grown six-fold since 2018. Operators are increasingly being told to run their assets against contradictory signals: maximise renewable absorption, maintain reserve margins, hold reactive headroom for voltage, respect inertia floors — and do all of it in fifteen-minute settlement windows while the underlying short-run marginal price flips sign twice an hour.
FATHOM exists because that gap cannot be closed by adding more screens to the control room. It is closed by a tightly composed pipeline of probabilistic forecasting, constrained stochastic optimisation, and real-time anomaly detection — all running on field-deployable inference engines that respect the latency, security, and observability that real grid operators require.
The dispatch board, condensed
// three lanes, one decision loopFATHOM Forecast
Probabilistic generation and demand forecasts at sub-second cadence, calibrated against five years of UK BMRS settlement data and pan-European reanalysis weather ensembles.
→ module-fathom-forecastFATHOM Dispatch
Stacked-revenue optimisation across wholesale, balancing, ancillary, and capacity markets. Co-optimises across cycle-life budgets, network constraints, and reserve obligations.
→ module-fathom-dispatchFATHOM Sentinel
Asset-level anomaly detection on transformers, switchgear, inverters, and BESS modules. Surfaces incipient faults weeks before SCADA threshold alarms would trip.
→ module-fathom-sentinelWhat a working day looks like on the platform
// LANE-3 narrativeBuilt for the operators who actually run the grid
// LANE-4 audiencesBattery portfolio operators
Two-cycle-per-day BESS portfolios increasingly need to stack wholesale arbitrage, dynamic frequency products, capacity market obligations, and TNUoS-driven location revenue. FATHOM Dispatch returns a single co-optimised schedule per asset, per half-hour, per market — with a documented degradation cost in pence per kWh of throughput.
target: 10MW – 500MW portfoliosDistribution network operators
DNOs face a constraint-management problem that classical load-flow tools cannot answer at the speed of LV solar reverse-flow events. We pair physics-informed neural network surrogates with conventional ENWL/SSEN data feeds to forecast feeder-level violations one to six hours ahead, with calibrated probability intervals.
target: 11kV / 33kV feedersIndustrial flexibility aggregators
Cold-store, water-treatment, cement, and data-centre flexibility looks like a juicy 5–40 MW resource on paper, and a nightmare to dispatch in practice. We provide a constraint-aware aggregation layer that respects each site's local process limits while presenting the aggregator's optimiser with a clean envelope of available MW × duration × notice.
target: virtual power plant operatorsRenewable IPPs
Independent power producers running mixed wind/solar/storage portfolios need a single forecast and dispatch backbone that handles PPA off-take obligations, curtailment compensation accounting, and route-to-market exposure. FATHOM plugs into the existing trading shop rather than replacing it.
target: 100MW+ IPPsWhere the AI actually lives
// architecture in one paragraphMost "AI for grid" pitches collapse into a single LSTM trained on the wrong feature set. We took the opposite path. FATHOM's forecasting layer is an ensemble: gradient-boosted trees on engineered weather and market features carry the median; a temporal convolutional network handles fast-moving sub-hourly dynamics; a small transformer head reconciles them against the most recent ten minutes of SCADA. Quantile regression gives us calibrated 5/50/95 percentile bands, which is what the optimisation layer actually consumes — not point forecasts.
The dispatch layer is a mixed-integer stochastic programme with rolling-horizon recourse. We solve it on commodity hardware with HiGHS and Gurobi backends, but the interesting work is in the warm-start heuristic: a graph-attention policy network trained on five years of solved dispatch instances proposes an initial integer solution that the MIP solver verifies and refines, cutting wall-clock time from minutes to seconds.
The anomaly layer uses physics-informed autoencoders. We do not throw raw waveforms at a generic deep model and hope. We embed the thermal model of a power transformer, the equivalent circuit of an inverter, and the electrochemical model of a Li-ion cell directly into the loss function, so reconstruction error has a physical meaning rather than a statistical one. That is what lets us flag a developing turn-to-turn winding fault four to seven weeks before a dissolved-gas threshold would trip.
Recent field notes
// from the engineering logStacked-revenue batteries: what actually pays the bills
A walk through twelve months of co-optimised wholesale + DC-L + capacity revenue on a real 50 MW / 100 MWh asset in the East Midlands. Spoiler: the answer is not what the marketing decks say.
→ read noteSub-second forecasting for FFR contracts
Why ten-second SCADA is too slow for modern frequency response delivery, and how we built a sub-second forecast head that lives on the same RTU as the BMS.
→ read noteCatching a transformer four weeks before it fails
Anatomy of an anomaly: how a physics-informed autoencoder picked up a developing winding fault on a 33/11 kV transformer that DGA had not yet flagged.
→ read noteTalk to the dispatch desk.
Pilots typically start with one site and one market product, and grow from there. If you have a portfolio you want benchmarked against a stacked-revenue dispatch run, the fastest path is a thirty-minute call with the engineering team.