
β‘ Energy & Utilities Β· Data Flow
How readings from millions of smart electricity meters reach billing and customers: head-end system, meter data management and analytics.
Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.
Drawing diagramβ¦
Data flow for smart electricity meters (AMI): smart meters send 15-minute interval readings over RF mesh to data concentrator units, which forward them to the head-end system. The meter data management system validates, estimates and edits the data (VEE), then sends billing determinants to the billing system, usage data to the customer app, and feeder-level data to an analytics platform for loss detection. Outage alarms go straight to the outage management system. Number the processes.
flowchart LR
subgraph EXT ["External entities"]
sm["Smart meters"]
dcu["Data concentrator units"]
hes["Head-end system"]
cust["Customer app"]
bill_sys["Billing system"]
analytics["Analytics platform"]
oms["Outage management system"]
end
subgraph PROC ["Processes"]
p1("1.0 Collect interval readings")
p2("2.0 Aggregate and forward readings")
p3("3.0 Perform VEE processing")
p4("4.0 Calculate billing determinants")
p5("5.0 Generate usage insights")
p6("6.0 Aggregate feeder-level data")
p7("7.0 Process outage alarms")
end
subgraph STORE ["Data stores"]
d1[("D1 Raw interval readings store")]
d2[("D2 VEE validated readings store")]
d3[("D3 Outage log store")]
end
sm -- "15-minute interval readings" --> p1
sm -- "Meter outage alarms" --> p7
p1 -- "RF mesh interval data" --> dcu
dcu -- "Aggregated interval data" --> p2
p2 -- "Forwarded interval data" --> hes
hes -- "Raw meter interval readings" --> p3
p3 -- "Unverified interval readings" --> d1
d1 -- "Raw interval readings" --> p3
p3 -- "Validated, estimated and edited readings" --> d2
d2 -- "VEE interval data" --> p4
d2 -- "Validated usage data" --> p5
d2 -- "Feeder interval data" --> p6
p4 -- "Billing determinants" --> bill_sys
p5 -- "Usage data" --> cust
p6 -- "Feeder-level data for loss detection" --> analytics
p7 -- "Alarm event record" --> d3
d3 -- "Processed alarm data" --> p7
p7 -- "Outage alarms" --> omsA data flow diagram with 14 processes and outside parties, 3 data stores and 18 data flows.
Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.
What a power utility does from the moment an outage is detected to restoring supply and closing the incident.
The software behind a modern power grid: SCADA/EMS for transmission, ADMS for distribution, smart meters, DER management and the customer portal.
How an electricity or water bill is produced and paid: meter reads, validation, tariff calculation, bill delivery and payment posting.
Where monitoring runs for a renewable energy portfolio: inverters and turbines at each plant, a plant controller, and the central monitoring cloud.
How electricity flows from generation sources to the grid and on to consumer segments, including losses.
How a power utility runs a public EV charging network: chargers, a charge-point management system, grid load control and billing.