Energy Management
What powered the site last night.
Energy Management is the part of MLNetworks that reads grid, generator, battery and fuel data for each tower site on one time line and shows where a site uses more energy than it should.
MLNetworks reads grid, DG, battery and fuel data together, compares actual with expected, and prepares the next maintenance step for a person to approve.
Talk to an ExpertRidgeview RDG-0417
Tower site, 36 m
Energy balance
+0.12 kWBalancedSupply and draw add up within tolerance at the latest reading.
Contributing components
Contributing values span 4s.
From the meters to a maintenance job
01
Grid, DG and battery, hour by hour
Grid, DG and battery readings share one time axis. Pick any moment in the last 24 hours and the site view shows its state then.
Site Energy StateRidgeview RDG-0417Last 24 hours
LiveGridLost 7 timesGeneratorRan 6 timesBatteryDischarging 7 times00:0006:0012:0018:0024:00State at 16:10
- Grid
- Lost
- Generator
- Standby
- Battery
- Discharging
- SoC
- 33%
02
Actual against expected
Each check puts the reading beside the expected value and names what the data cannot confirm. A reading with no value stays empty, never zero.
Site Energy StateRidgeview RDG-0417Validation
Each check judges the observed reading against what was expected.
- Generator run on outage 1Matches
Observed
Run recorded
Expected
Run recorded
- Generator run on outage 5Differs
Observed
No run recorded
Expected
Run recorded
- Battery discharge on outage 5Differs
Observed
SoC dropped to 33%
Expected
Brief discharge
- Grid return after outage 5Matches
Observed
Voltage restored
Expected
Voltage restored
Energy balance
-0.90 kWUnaccounted drawWhat the data cannot confirm
Why the generator did not start. The readings show that it did not run, not the cause.
03
An exception, then a job
A finding opens as a case with its readings attached. The record recommends a maintenance action and a person decides. Nothing runs on its own.
ExceptionsRidgeview RDG-0417Exception
Generator did not run on a grid outage
Ridgeview RDG-0417
HighOpenEvidence
- Grid lost at 15:24, restored at 17:24measured
- No generator run recorded in that windowmeasured
- SoC dropped to 33% by 16:10measured
- Start circuit fault suspectedinferred
Decision
Held for a person to decideDecision required. Nothing here executes on its own.
Recommended: Create maintenance work order
Inspect generator start circuit. Battery reserve was used in full on this outage.
Create work orderReject
The systems that measure your energy
Integration scope is defined for each deployment, and each source is validated with your team before it is named as supported.
- Site controllers and telemetry
- Energy meters and sensors
- Fuel and delivery records
- Site and asset records
The battery and DG behind the numbers
- Discharging
Battery bank 1
Ridgeview RDG-0417
SoC33%SoH88%- Autonomy
- 2 h 10 min
- Temp
- 29 °C
- Cycles
- 412
Battery condition
SoC, SoH, charge state and autonomy sit together for each battery bank, so a weak bank shows before the next outage.
Generator
Standby- Control Mode
- Auto
- Runtime
- 1,840 hrs
- Engine Battery
- 11.2 V
- Shutdown Alarm
- None
- Updated
- 2 min ago
Generator condition
Run state, run hours, engine battery and shutdown alarms are read from the same site, beside the outage history.
From exception to site visit
An approved action becomes a work order with the finding attached. The energy record follows the job until the site is read again.
Workforce & SchedulingException
Generator did not run on a grid outage
Ridgeview RDG-0417
Work order
Inspect generator start circuit
Attached to the work order
- Outage window and SoC readings
- Generator run history
- Link to INC-2041
After the visit
Next outage: generator run is compared with expected
Built so an engineer can check the numbers
Missing is not zero
A reading with no value shows as empty, with its state. A balance that cannot be assessed says so instead of showing a figure.
Measured apart from inferred
Each exception marks which readings were measured and which were inferred, and what the data cannot confirm.
People keep the decision
Recommendations wait for a person. Accounting and fuel payment stay in your ERP.
FAQ
Questions from energy teams
Which power sources can it read?
Grid, DG, battery, solar and fuel data can be read for one site. What a site reports depends on its controllers and meters, and is defined for each deployment.
How is actual compared with expected?
Each check sets the observed reading beside the expected value and shows the result. How expected values are set depends on the site and the data available, and is agreed for each deployment.
What happens when data is missing or stale?
The reading shows as empty with its state, such as Stale or Disconnected. When the data is not good enough, the balance is marked as not assessable instead of estimated.
Does it act on its own?
No. It prepares a finding and recommends an action. A person decides, and the decision is recorded on the case.
Does it replace our energy or fuel accounting?
No. It reads from the systems you already run. Accounting and payment stay with your ERP.
Energy Management
Which site would you like to look at first?
Bring a real case. An MLNetworks expert will walk through it with you.
Talk to an ExpertMore of the platform
Every part uses the same sites and assets. Start where the need is greatest and add the next when you are ready.