M1
PERFORMANCE ANALITICS | Storage Performance Analysis
Turn operating data into comparable,
traceable system performance
Use the energy boundary as baseline and let measurements speak. Bring battery DC, PCS, transformer, grid metering, and auxiliaries into one energy ledger so every efficiency, availability, and improvement conclusion can be reviewed, verified, and traced.
M2
M3
M4
M5
BOUNDARY
HVAC / cooling system MAUX-1
Fire Systems / Fire Systems MAUX-2
Control & Standby/ Control Standby. MAUX-3
M1 · Battery DC:
Battery system direct flow total input/output boundary. As the starting point for the RTE master account on this page, cumulative energy is 21,448.7 MWh.
Calculating period (monthly)
2025-05-01 — 2025-05-31
Net output M5
18,732.6 MWh
RTE RTE
87.35%
System availability
98.62%
Measuring data integrity
99.18%
Data availability
99.72%
01 Defining performance boundaries and measurement points
| Measures | Name | Annotations |
|---|---|---|
| M1 | Battery DC | BCMU / DC measurement chain |
| M2 | PCS DC In | PCS DC input side |
| M3 | PCS AC Out | PCS AC output side |
| M4 | Transformer | The transformer downstream / before netting |
| M5 | Revenue Meter | Clear-scale network measurement |
| MAUX | Auxiliary Load | Refrigeration, firefighting, control and standby systems |
Time frame:
The metrology chain uses a uniform time synchronisation; analysis of the particle size is 15 minutes, and original SCADA/EMS data retain a second time stamp.
02 Energy reconciliation and data availability
Original Measurement
SCADA / Meter / BCMU
Quality verification
Completeness/ Time series/ Scope
Data Cleaning
Missing / Repeat / Abnormal
Reconciliation
Border coherence
Analytical data sets
Interval Dataset
99.72%
Available
Effective data 99.72%
Missing data 0.20%
Anomalous data 0.08%
Missing / Abnormal
One minute.
Allow for the repair of shortage points based on proximity
1-6 hours
Match and maintain mass tags using the same profile
> 6 hours
Not entering formal performance conclusions
Principles
Keep source and algorithm versions of any recovery data
• Efficiency and loss landscape Energy flows this month.
(b) Auxiliary energy consumption is an explanation of the loss, without double deduction.
21,448.7 MWh
Battery DC · M1
100.00%
21,345.2 MWh
PCS DC In · M2
99.52%
19,740.9 MWh
PCS AC Out · M3
92.03%
19,102.6 MWh
Transformer · M4
89.06%
18,732.6 MWh
Revenue Meter · M5
87.35%
Batteries differ from straight-stream sides
103.5 MWh
0.48%
PCS conversion losses
1,604.3 MWh
7.48%
Depletion of transformers
638.3 MWh
2.98%
Lines and support differences
370.0 MWh
1.72%
Measuring RTE
87.35%
Total losses
2,716.1 MWh · 12.65%
Line / Supplementary Difference
1.72%
04 Availability Timeline This Month
Available Run
Limit running
Planned maintenance
We're down.
Invalid Data
| Event Type | Length | Do I count down? | Annotations |
|---|---|---|---|
| Planned maintenance | 4.0 h | By contract calibre | PCS / Refrigeration |
| Unplanned failure | 6.3 h | Yes. | Protect Action / System Restore |
| Power Limit | 18.4 h | Yes | The system is still in service |
05 Power response assessment Example of an FM event
Command tracking success rate
99.18%
Response delay
1.23 s
Ten percent rise time.
4.21 s
Superb
2.18%
Steady state error
0.73%
06 Normalization approach For comparability
T
Temperature homogenization
Map to 25°C base
SOC
SOC Window
20-80 per cent unified window
P
Load / Multiplier
Match similar power ranges
MODE
Run Mode
Charge / discharge / standby
DQ
Data integrity
Availability 99%
The same Benchmark object enters a horizontal comparison only after SOC, temperature, power, mode of operation and data quality meet the matching conditions.
07 Horizontal comparison Once it's consolidated,
| Object | Power / Capacity | RTE | Availability | Command tracking success rate |
|---|---|---|---|---|
| Site A | 100 / 200 | 87.35% | 98.62% | 99.18% |
| Site B | 100 / 200 | 86.21% | 97.94% | 98.71% |
| Site C | 50 / 100 | 85.08% | 97.21% | 98.12% |
• Decomposition of losses Example: RTE is below baseline 1.85 pct
Break “low efficiency” into actionable engineering causes instead of stopping at a single KPI.
| Loss item | Offset | Main reasons | Associated device/ system | Evidence |
|---|---|---|---|---|
| PCS efficiency deviation | -0.48 pct | Inadequate efficiency between low loads | PCS-03 / 06 | Efficiency Curve / Run Distribution |
| The transformer's out of control. | -0.92 pct | Increased low load running time | Master TR1 | Enter / Output Measurement |
| Energy consumption of auxiliary systems | -0.31 pct | Refrigeration system operation strategy | HVAC / EMS | Secondary measures |
| Lines and other | -0.14 pct | Busbar / line loss | AC / DC Line | Border reconciliation |
09 Improve tracking
| Found / Problem | Measures taken | Baseline period | Improvement period | Validate proceeds | Responsible persons | Evidence |
|---|---|---|---|---|---|---|
| Optimization of PCS low-load efficiency | Optimizing low-load control logic and improving efficient area coverage | RTE 87.02% | RTE 87.92% | +0.90 pct | Run Manager | Policy Change / Efficiency Curve |
| The cooling system's auxiliary energy is high. | Adjust cooling temperature differentials and start-up strategies | Auxiliary energy consumption 0.56% | Auxiliary energy consumption 0.49% | -0.07 pct | Transport Manager | Control Parameter / Energy Consumption Trends |
| The transformer has a lot of low load time. | Optimizing PCS schedule and transformer load distribution | Loss 1.05% | Loss of 0.87 per cent | -0.18 pct | Dispatch manager | Power Distribution / Energy Reconciliation |
10 Border description
This page shows Measured Performance / Actual PerformanceI don't know. Any projection, optimization target or Benchmark conclusion must be clearly distinguished from measured data.
DATA
Performance measurement
This Page
OPT
Plan for optimization
Improvement targets
BENCH
Benchmark
Normalization
• Output list
✓
Performance analysis reports and monthly findings
✓
Measurement Pixmap and Meter Map
✓
Interval Dataset after reconciliation
✓
Details on efficiency and losses
✓
Evidence of availability and downtime events
✓
Power response test report
✓
Description of the methodology
✓
Horizontal Comparison Data Set
✓
Improvement of validation reports for measures
Data and compliance
Data sources
SCADA / EMS / BCMU / PCS / Revenue Meter
Data saving
3 years
Time Sync
NTP / PTP, deviation 1 s
Audit tracking
All calculations and changes recoverable
Compliance principles
Borders, algorithms, data versions are controlled.