GRID-IN: an analytical system for reducing losses in 0.4 kV networks
For the technical staff of a distribution company: what the system takes as input, what it consists of, what it delivers and how it fits into daily work.
1. Purpose
GRID-IN detects non-technical losses and calculates technical losses in 0.4 kV distribution networks from metering data (AMI), billing and network diagrams. The result is a list of objects for field inspection with estimated unmetered energy and probability of confirmation, plus the network state and losses by section.
- Scale: individual substations, a district or a whole branch.
- Users: metering and energy-transport departments, revenue protection, district managers, field inspection crews.
- Hardware: none — data already being collected is used.
2. Input data
| Data | Purpose | |
|---|---|---|
| Load profiles of consumer meters and the substation input meter | basis of all methods | required |
| Balance groups (which meters belong to which substation) | if absent, assembled automatically | desirable |
| Consumer register: meter, address, account, CT ratio | target addresses, metering reconciliation | desirable |
| Meter event logs | event analysis | desirable |
| Monthly billing | billing analysis, metering reconciliation | desirable |
| Single-line diagram of the 0.4 kV network | network state and technical losses | desirable |
Details — on the “Data requirements” page.
3. Components
PREPdata preparation
GRIDCObalance groups
GRIDJObalance without a diagram
GRIDSOevents and billing
GRIDTOnetwork state from the diagram
FUSIONone list
Deliveryweb, phone, files, API
PREP — data preparation
Input
- profiles, events, billing
- register, diagram, map
Action
- filtering and finding errors in the data
- reconciling metering with the register and billing
- comparing the map and the diagram
Output
- clean data, digital diagram
- meters not reporting; meters with mismatches
- houses without a service connection on the diagram
GRIDCO — balance groups
Input
- profiles of consumer and transformer meters
Action
- no groups — assembles them
- groups exist — verifies them
Output
- assignment of meters to transformers
- list of mismatches with the diagram and records
GRIDJO — balance method without a network diagram
Input
- balance group: substation input and consumer meters with profiles
Action
- balance method based on correlation and regression
- does not lose accuracy as the imbalance grows
Output
- unmetered consumption with an energy estimate
- faulty and “extra” meters
GRIDSO — analysis of events, billing and profiles
Input
- meter event logs
- billing, profiles
Action
- analysis of patterns and events
Output
- unmetered consumption
- meter faults
- cryptocurrency mining
GRIDTO — network state calculation from the diagram
Input
- single-line diagram and profiles
- phasing, node voltages and refined line lengths are determined by the module itself
Action
- calculation of the network as a physical circuit
- search for anomalies by section
Output
- currents, voltages, losses and load by section and node
- anomalous sections and meters
FUSION — combining the results
Input
- results of GRIDCO, GRIDJO, GRIDSO, GRIDTO
Action
- combining the findings of all methods into one score
Output
- one list of targets with type of irregularity, energy and probability
Each method works with the data available and does not wait for the others. A finding confirmed by several methods gets a higher score.
4. What the user gets
Field target register
- for each target — address, meter, type of irregularity (theft, extra meter, fault), estimated unmetered energy for the period, probability of confirmation, explanation and on-site procedure;
- targets are grouped by location for the crew route; group size is set by distance and number of points;
- order by return: groups, substations and consumers with the most unmetered energy per metering point come first; the order can be changed by hand and reset to automatic;
- filter by type, search, sorting, PDF export, target numbers on the map.
Workspace
- tree “district → substation → meter” with target counts and estimated savings in kWh per year;
- per substation — targets, imbalance, network diagram coloured by losses and load, meter and section cards, profile charts;
- project map: substations, consumers, targets;
- interface in English and Russian; works in a browser on a computer and on a phone.
Technical losses
- technical losses of the substation and of overhead and cable sections — for the period and by hour;
- current load of sections relative to the continuous rating — overloaded sections;
- node voltages and voltage drop to remote consumers.
Visit outcomes
The crew records for each target: “confirmed”, “not confirmed”, “no access”. Outcomes are visible in the register and in the project summary.
5. Working with data
- exports are accepted as files in the form the metering system produces them: Excel, CSV, ZIP and 7z archives; an unfamiliar column layout can be mapped by hand once;
- new periods and substations are added to a project; only changed substations are recalculated;
- the network diagram is drawn in the GRID-IN editor on a map or uploaded as a file; the editor also works on a phone, linked to the current location;
- for every uploaded file the user sees what was recognised and what is wrong with it.
6. Integration
A REST API with key access: data upload, project creation, calculation start, task status, calculation summary, target list, visit outcomes. GRID-IN plugs into the metering system, billing or a field-work management system without manual exports.
7. Deployment and access
- cloud service or installation on the distribution company’s server;
- roles: administrator, manager, inspector; each account sees only its own organisation’s projects;
- scope by contract: number of metering points and term;
- log of logins and actions: who uploaded data, started calculations or recorded outcomes, when and from where.
8. Roll-out
| Stage | Content | Result |
|---|---|---|
| 1. Pilot | export for several substations over one period; if available — diagrams, events, billing | target register and technical losses per substation |
| 2. Verification | field visits by the register, outcomes recorded | share of confirmed targets |
| 3. Roll-out | a whole district or branch, regular uploads by hand or via the API | continuous loss control |