Core platform · Analytics
GDEA joins the connectivity model from ArcGIS with real-time SCADA telemetry and the utility’s AMI meter reads and events, and serves one operational picture across electricity, gas, and water — with power-flow and hydraulic solvers, a what-if scenario sandbox, a complete large-load interconnection workflow, and a library of analysis checks on top — in the family’s shared shell, with a published API contract behind it.
The network eye
The connectivity model knows what each network is; SCADA and AMI know what is happening to it. GDEA joins them — permanently, at full scale, for electricity, gas, and water — then puts real solvers on top: power flow per electric feeder, hydraulic solves for gas and water. Every analysis falls out of that join: where the fault is, which regulator will fail on the next cold morning, which water district is leaking, and what building the next project would actually fix. And when a data-centre-scale request lands on the interconnection queue, GDEA answers it end to end — from honest queue totals to the engineering at the point of connection.
Vector tiles keep millions of assets fluid at every zoom, with live telemetry and events overlaid on the model — and every meter modelled at a real addressed building.
SAIDI, SAIFI, CAIDI, MAIFI, and CEMI computed to IEEE 1366 from the utility’s own event history.
From measured fault current, and independently from which meters went dark — both shown on the map.
Feeder headroom with the binding constraint named, conservation voltage reduction analysis, and demand broken down by customer class.
Transformer thermal ageing from loading and ambient temperature, plus a per-asset probability of failure from a trained model.
The data-centre queue as a register: duplicate-candidate netting with two honest totals, point-load feasibility per ramp step, and a ladder of connection options solved against one base and ranked by cost per megawatt admitted.
Continuous checks on the imported GIS model — connectivity, phasing, and data gaps, found before they mislead an operator.
The comms topology from field device to utility, separating telemetry outages from power outages.
Unaccounted-for gas, regulator performance measured as droop, odorant and pressure integrity, line pack, and a graded leak register with due dates.
Minimum night flow per district metered area against what its properties can account for — the 03:00 reading that says a district is leaking.
Reconductor a feeder, replace a main, re-set the city gate — base and scenario solve in the same call, so the difference is the change and nothing else. A refusal, with reasons, is a first-class answer.
What a failure in one network does to plant in another — the de-energised feeder carrying a pump station — inferred from geometry and labelled as such.
Candidate projects ranked against the constraints the analytics actually found — what to build, and in what order.
A published OpenAPI document for every operation, derived from the running code so it cannot drift: bearer credentials, the roles each operation requires, the 503 the registration gate returns, and the RFC 7807 problem envelope every error uses.
How it works
The connectivity model arrives from ArcGIS — assets, topology, phasing, geometry — checked by continuous model-quality analysis.
The gateway speaks DNP3 and IEC-104 to the SCADA estate, translating one way: inward — and AMI reads and events arrive already validated from the Grid Data Management Platform.
Telemetry lands against the model through a high-throughput Kafka-to-database path — timescaled for history, tiled for the map.
Power flow runs per electric feeder; hydraulic solves run for gas and water — and the scenario sandbox reuses the same solvers for what-if.
The same joined picture powers the control room, the planner, the reliability engineer, and the executive dashboard.
Use cases
One live map of what the network is and what is happening to it, right now.
Fault locations from two independent methods shorten patrols and restoration.
IEEE 1366 indices computed from source data, defensible in front of a regulator.
Capacity headroom, CVR analysis, and the scenario sandbox show where the next EV fleet or solar farm can connect — and what to build if it cannot.
Failure risk, thermal ageing, and ranked project planning turn replacement budgets into defensible lists.
Model analysis turns the GIS clean-up backlog into a ranked worklist.
Triage the request queue with honest totals, test feasibility per ramp step, and rank the connection options that admit the most megawatts per dollar.
Unaccounted-for gas, regulator droop, line pack, and the graded leak register — one platform.
Night-flow analysis per district ranks where leakage recovery pays back first.
Every family application shares one identity platform, one design system, one registration pattern, and one deployment path.
Meter-side truth beside GDEA’s network-side view.
Embeds GDEA insight into dashboards and wallboards.
Supplies SCADA and meter feeds in every test environment.
A working demonstration takes thirty minutes — on our environment or yours, with realistic simulated data.
8100 Penn Ave S, suite 150j, Bloomington, MN – 55431
+1 (763) 353-4363