ADMS for medium- and low-voltage networks
The distribution grid, as it really is.
GRIDNEURO is the distribution management system (ADMS) for medium- and low-voltage networks. It turns your GIS, SCADA and smart-meter data into one verified network model, then runs operations, analysis and outage management on it. On your own servers, air-gapped if you need it.
From your utility GIS to a verified network model- IEC CIM100One standard network model for every module
- Checked against OpenDSS and pandapowerLoad flow on IEEE test feeders, IEC 60909 short circuit
- IEC 60870-5-104 and MQTTTelemetry intake in one direction only
- No field commandsOperators decide; the system keeps the record
- On-premise or air-gappedSigned release bundles, installed on your servers
Built on open standards
- IEC CIM100
- IEC 60870-5-104
- IEC 60909
- IEEE test feeders
- MQTT over TLS
- LDAP / Active Directory
- OpenID Connect
- TOTP
- CycloneDX SBOM
- CEF / syslog
- Kubernetes (K3s)
- PostgreSQL
- Kafka
- ClickHouse
GIS integration
From GIS to a working grid model.
Importing the utility's GIS is where most ADMS projects lose months to hand-built network models and mapping scripts. GRIDNEURO does it with its own pipeline: your GIS export in, a verified, versioned, electrically valid network model out.
Your GIS, as delivered
- Line ends that miss their junction
- Lines that only touch another line mid-way
- Switches without a known position
- Phase codes as A/B/C, R/Y/B or L1/L2/L3
- Layer and column names unique to this utility
Mapping profile (example)
VOLT_KV→voltage_kvFASE_COD→phasesTIPO_SEC→kindOBJ_ID→id
A first mapping is suggested from layer and column names. Value maps translate your codes. The profile is saved for the next delivery.
Validation and conversion report
- autoLine ends snapped to their junctions within the tolerance
- autoLines touched mid-way split into branches (GN-GIS-108)
- checkedVoltage levels and phases checked per node and winding
- reviewSwitch position unknown: reported, never assumed closed (GN-GIS-030)
Fixed by rule where the rule is unambiguous; everything else is a finding with a code and a location.
Identity map and versions
- GIS id to mRID, deterministic and stable across deliveries
- Each delivery diffed: added, removed, changed
- Immutable version with a content hash; activation is explicit and reversible
The operating model
- Live topology traced on the registered version
- AC power flow on the same model
- SCADA telemetry bound to the same GIS identities
Fits your schema
Mapping profiles adapt to any utility's layers, columns and codes, and are remembered for the next delivery.
Nothing guessed
Snapping, connectivity, voltage and phase checks end in a report. Unknown values are findings, not assumptions.
Stable identities
Deterministic mRIDs and immutable versions: re-import without losing history.
Synthetic demo measurement: the Berlin demo network (about 141,000 nodes, 66,000 buildings, 702,000 customers) was prepared in about 110 s and registered in about 6.6 min on one server. The live demo grid was imported through this same GIS preparation, mapping and validation flow.
Most control rooms run on a grid that no longer exists.
GIS, SCADA, outage and analysis tools each keep their own copy of the network. The copies drift apart. Then the hard questions arrive.
Five systems, five versions of the truth
The map, the load flow and the outage tracer disagree about one switch, and nobody can say which of them is right.
Low voltage in the dark
Below the transformer, the network is often a drawing, not a model. Outages there are found when customers call.
Decisions nobody can reconstruct
When an incident review or a regulator asks why, the data, model and switch state behind the decision are gone.
GRIDNEURO puts one verified model under all of it.
From raw data to a decision you can defend.
Four stages, with one model version running through all of them. Every result can be traced back to the data and the model it was computed on.
- 1Data
Take in what you already have
GIS exports in the formats your GIS team already produces, live telemetry over IEC 60870-5-104 and MQTT, smart-meter events and customer calls. Intake is read-only.
- 2Model
Build one network model you can trust
Electrical rules check phases, voltages and switch positions, and connectivity is derived from geometry. The result is a versioned IEC CIM100 model. Gaps become findings, never silent assumptions.
- 3Analysis
Calculate on that exact version
Load flow, state estimation, IEC 60909 short circuit and restoration analysis run on a recorded model version and switch state. Every result carries its inputs and engine version, so it can be run again.
- 4Operation
Operators decide, the system keeps the record
Live network map, alarms, outage management and switching plans. GRIDNEURO prepares the evidence and the workflow; crews act in the field, and every switch state is recorded.
Numbers we can show you.
Each figure comes from the product’s own test suite or sizing measurements, and we walk you through it in a briefing.
- 200,000
- network nodes in one three-phase load flow, measured at 38 seconds
- 3
- IEEE test feeders (13, 34 and 123 bus) checked against OpenDSS
- 10−6
- per-unit agreement with OpenDSS on identical networks
- 0
- field commands. GRIDNEURO reads the grid; people operate it.
Nine product families. One data model. One login.
In most utilities GIS, SCADA, DMS, OMS and analytics are separate products with separate models that drift apart. In GRIDNEURO they share one registered model version, one switch-state chain and one identity.
Analysis
Operation
It reads the grid. It never operates it.
GRIDNEURO never issues field commands. It reads telemetry, builds the evidence and prepares switching plans; people approve them and crews carry them out.
- Field equipmentRTUs, SCADA front-end, smart meters, MQTT devices
- GridConnectReads IEC 60870-5-104, MQTT and meter data, in one direction
- GRIDNEUROModel, analysis, outage evidence, switching plans
- OperatorReviews the evidence and approves the plan
- Field crewCarries out the switching on site
The loop closes through people: the operator records what was done in the field.
Model first
Every calculation, outage assessment and switching plan is tied to a recorded, immutable model version.
Uncertainty is never guessed
A switch with an unknown position is not assumed closed. A transformer without nameplate data is not invented.
Reproducible by design
Every analysis stores its exact input, engine and algorithm version and input hash.
Calculations checked against reference tools.
The load-flow and short-circuit engines are compared with independent open-source tools in the product’s own test suite, on public IEEE test networks.
| Calculation | Reference | Test network | Result |
|---|---|---|---|
| Unbalanced three-phase load flow | OpenDSS | IEEE 13-, 34- and 123-bus test feeders | Identical network: agreement within 10⁻⁶ pu |
| Short circuit to IEC 60909-0 | pandapower | IEEE 13-bus feeder; single-, two- and three-phase faults | Ik″ tested to 10⁻³ relative; measured deviation below 10⁻⁵ |
On the official feeder definitions, some elements are represented by equivalents. The resulting deviation is measured per feeder, documented and guarded against regression; it stays below 0.021 pu.
Security your OT team can check line by line.
We describe what is implemented and what is not, so your security team can plan the controls around it.
Sign-in that fits your directory
LDAP and Active Directory, OIDC single sign-on and TOTP multi-factor authentication. Roles and region-scoped permissions in GridAdmin.
Deny by default
Operational commands pass a policy gate that refuses unless a rule allows them. If the policy service cannot decide, they fail closed.
Field data you can trust
IEC 60870-5-104 quality bits are kept and uncertain values quarantined. MQTT telemetry arrives as HMAC-signed envelopes over TLS; retained messages are refused.
A verifiable switch-state record
GridLedger chains every model and switch-state revision with hashes, so a past state can be verified and replayed.
Signed releases
Air-gap release bundles are signed and verified before they are loaded. Images are pinned by digest and delivered with an SBOM.
Evidence for your SOC
The audit chain exports as CEF or JSON lines and forwards to your SIEM over syslog. In production, services refuse to start on default credentials.
What we do not claim
GRIDNEURO has not been assessed against IEC 62443 by a third party. Our hardening guide maps each IEC 62443-3-3 requirement to the code that implements it, marks it met, partial or open, and names the controls you supply.
Your network. Your servers. Your control.
GRIDNEURO installs on your own infrastructure, connected or fully air-gapped. Start on one server; move to a highly available cluster when operations depend on it.
Single server
The full stack under Docker Compose on one Linux host: the delivery target for pilots and first deployments.
High availability
A hardened K3s cluster with default-deny network policies, HTTPS-only ingress, three PostgreSQL instances, three Kafka brokers and replicated ClickHouse.
Operated like infrastructure
- Signed release bundles that install without internet access
- A guided installer with preflight checks and three sizing tiers
- Upgrades that check schema versions and keep a rollback path
- Scheduled backups that verify themselves before pruning
- IQ/OQ checks and a FAT/SAT catalogue for acceptance
- Audit export, SIEM forwarding and a self-redacting support bundle
Connects to what you already run
Read next.
Use cases for distribution operators
Control room, outages, DER hosting, LV visibility, model clean-up, maintenance and reporting.
ReadStandards and interoperability
IEC 61970/61968 CIM, IEC 60870-5-104, IEC 60909 — what is implemented, and how.
ReadOn-premise and air-gapped deployment
One Linux server, connected or fully air-gapped, with backup and rollback.
ReadSee your own network in GRIDNEURO.
Bring a GIS export. We walk you through the validation findings, the connectivity model and what your control room would see — on your data, in a technical session with engineers.