Introduction: Storage Policy Is Moving from Targets to Project Delivery
On 26 June 2026, the first EU-level tripartite agreement dedicated to scaling up the energy-storage sector was signed in Luxembourg.
The agreement provides a clearer indication of Europe’s storage-deployment challenge. The European Commission estimates that approximately 200 GW of storage capacity will be needed by 2030, compared with around 55 GW installed at the beginning of 2026. It also refers to an indicative annual deployment pace of 30 GW, as outlined in the AccelerateEU Communication. Seventeen EU countries had already submitted storage pledges for 2026–2028, while another five were expected to do so by the end of 2026.
These figures should not be treated as one universal battery target or metering specification. The Commission’s published national pledges mix power values in MW and energy values in MWh, and the pledges are not legal obligations. Project requirements will continue to vary by country, connection level, storage technology, market role and commercial structure.
The EU agreement covers multiple storage technologies, including batteries, pumped storage and industrial thermal storage. This article focuses specifically on electrical metering and EMS data for C&I battery storage and renewable-energy co-located BESS projects.
The central project question is:
As storage deployment accelerates, what metering and data architecture is needed to make C&I and co-located projects operable, maintainable and repeatable?
Accelerating storage deployment is not only a capacity challenge. It is also a system-integration and data-consistency challenge.
1. Why the EU Storage Agreement Matters for Project Design
For metering and EMS design, the important point is that capacity growth increases the number of projects that must distinguish:
- rated storage power in MW from usable energy in MWh;
- battery-side DC energy from PCS-side AC energy;
- gross BESS output from auxiliary consumption and downstream losses;
- internal operational data from accepted POI or settlement data;
- installed flexibility from measured and verified response during an applicable interval.
The 200 GW estimate therefore strengthens the need for scalable, documented data architectures. It does not remove the requirement to define each project’s measurement boundaries, interval rules, data ownership, validation process and final acceptance authority.
Future growth will not be limited to standalone utility-scale BESS projects. Important deployment areas include:
- C&I behind-the-meter battery storage
- Co-located PV and BESS projects
- Industrial energy-storage systems
- Hybrid renewable projects
- Multi-user energy projects
- Storage connected to power-purchase agreements
As project volumes increase, repeatable technical architecture becomes more important than isolated equipment selection.
A scalable project portfolio requires clear answers to four questions:
- Where is electrical energy measured?
- Which system is the source of each value?
- How are units, directions, timestamps and register maps standardised?
- How is the complete meter-to-EMS data chain commissioned and documented?
2. C&I Storage and Co-Located Storage Are Different Architectures
Different storage projects require different measurement priorities.
|
Project architecture |
Main objective |
Typical metering focus |
|
Standalone grid-scale BESS |
Dispatch and grid services |
PCS blocks, auxiliary loads and POI |
|
C&I behind-the-meter BESS |
Peak reduction, cost optimisation and backup |
Main incomer, site load, BESS and PV |
|
Co-located PV and BESS |
Renewable shifting and export management |
PV output, BESS, curtailment data and POI |
|
Multi-user energy project |
Allocation and remote reporting |
Project boundary, user data and contractual allocation |
|
Industrial hybrid system |
Reliability and production-energy control |
Production load, storage, generation and backup |
A C&I project may reduce site demand without exporting energy to the grid. A co-located PV-BESS project may route energy between renewable generation, storage, site loads and the external network.
The measurement architecture should therefore follow the actual coupling topology, electrical single-line diagram and contractual purpose of the project.
3. Five Common Measurement Boundaries
These five boundaries are common reference points rather than a universal architecture.
More complex projects may also require:
- Individual PCS- or BESS-block metering
- Step-up transformer high- and low-voltage-side metering
- Collector-feeder metering
- Shared-bus metering
- Revenue-metering boundaries
- Multi-tenant or multi-contract allocation points
3.1 Renewable-Generation Boundary
The renewable-generation boundary may provide:
- Actual renewable-energy output measured at the defined electrical boundary
- Active and reactive power
- Voltage
- Current
- Power factor
- Energy delivered to a shared AC bus
- Controller- or model-reported available generation before curtailment
- Curtailment setpoint and status
- Calculated curtailed energy where required
Available generation and curtailed energy are generally derived or controller-reported values. They should not automatically be treated as direct outputs of the energy meter.
These values may come from:
- PV inverters
- PPC systems
- SCADA platforms
- Weather and production models
- Curtailment-control logic
- Approved baseline or calculation methods
3.2 Battery DC Boundary
Where required by the project architecture, the battery DC boundary may provide:
- DC voltage
- DC current
- Battery-side power
- DC charge energy
- DC discharge energy
- Battery-side energy throughput
- Charge and discharge direction
Battery SOC, SOH, temperature, cell status and battery alarms normally come from the battery BMS rather than from an energy meter.
DC-side data should be clearly distinguished from AC-side charging and discharging values because conversion losses occur between the battery and PCS AC terminals.
3.3 PCS AC Boundary
The PCS AC boundary may provide:
- AC charge energy
- AC discharge energy
- Active power
- Reactive power
- Voltage
- Current
- Frequency
- Power factor
- Operating direction
- PCS-side import and export values
Battery DC energy, PCS AC energy and POI energy should not be treated as interchangeable. Each refers to a different boundary and may include different conversion, transformer, cable or auxiliary losses.
The project should state whether “charge energy” means:
- AC energy entering the PCS
- DC energy entering the battery
- Net site energy allocated to storage charging
- Another contractually defined value
3.4 Site-Load and Auxiliary Boundaries
The site-load boundary may include:
- Production equipment
- HVAC
- Refrigeration
- EV charging
- Critical loads
- Flexible loads
- Tenant or departmental circuits
Storage auxiliary loads may include:
- Battery cooling and heating
- Pumps and fans
- Control systems
- Fire-safety equipment
- Communication equipment
- Station-service equipment
Main transformer and collector-system losses should be treated according to the defined performance boundary rather than automatically classified as auxiliary consumption.
Separate site-load and auxiliary measurements help distinguish:
- Normal facility consumption
- Storage-system parasitic demand
- Gross BESS output
- Net site benefit
- Grid-facing exchange
3.5 Point of Interconnection
The POI meter may measure:
- Grid import energy
- Grid export energy
- Net site power
- Active and reactive exchange
- Voltage
- Frequency
- Power factor
- Grid-facing energy
The export-limit setpoint or status normally comes from the PPC, EMS, DSO interface or plant controller.
The POI meter measures actual export and can support verification of whether the plant remained within the applicable limit. It does not generate the export-control setpoint or perform the export-limitation function.
A storage project cannot be accurately analysed unless renewable generation, storage operation, site load, auxiliary consumption and net grid exchange are clearly separated.
4. What EMS Needs from the Metering Layer
EMS requirements should be grouped by data purpose.
Energy-Accounting Data
Relevant values may include:
- Import energy
- Export energy
- AC charge and discharge energy
- DC charge and discharge energy where required
- PV generation
- Site-load energy
- Auxiliary consumption
Operational Data
Operational values may include:
- Active power
- Reactive power
- Voltage
- Current
- Frequency
- Power factor
- Maximum demand
Context and Time Data
Each data record may also require:
- Timestamp
- Timestamp source
- Time zone
- Clock-synchronisation status
- Maximum permitted clock drift
- Device identifier
- Measurement-point identifier
- Unit
- Scaling
- Direction convention
- Data origin
Data Origin, Availability, Validation and Processing Status
Records may need to identify whether data is:
- Actual
- Available
- Validated
- Missing
- Estimated
- Substituted
- Corrected
- Rejected
These attributes are not necessarily mutually exclusive.
Integration and Version Data
The EMS integration record may also require:
- Register map
- Register-map version
- Polling interval
- Internal meter-refresh interval
- Gateway status
- Missing-data treatment
- Firmware version
- Configuration version
- Calculation-method version
- Data-retention period
Not every EMS value comes from an energy meter. SOC, SOH, battery temperatures, alarms, available-power estimates and dispatch capability normally come from the battery BMS, PCS, plant controller or EMS model.
5. Meter Data, PCS Data and BMS Data Must Not Be Mixed
|
Data source |
Typical data |
Primary role |
|
Energy meter |
kWh, kW, V, A, PF, kvar and direction |
Electrical measurement at a defined boundary |
|
PCS |
Operating mode, power command and conversion data |
Power conversion and equipment control |
|
Battery BMS |
SOC, SOH, temperature and battery alarms |
Battery condition and safety |
|
EMS |
Optimisation, schedules and dispatch logic |
System coordination |
|
POI meter |
Net import and export |
Grid-boundary measurement |
|
PPC |
Plant-level setpoints and export control |
Plant power coordination |
No single device provides every data category required by a modern storage project.
The project should define a source of truth for each important parameter and state whether the value is:
- Directly measured
- Controller reported
- Model derived
- Calculated through energy balancing
Internal PCS values may support control and operational monitoring, but they should not automatically be treated as equivalent to independently metered values at a defined electrical boundary.
6. Why Co-Located PV and BESS Need Directional Energy Data
A co-located system may contain several simultaneous energy paths:
PV generation
├─ Site load
├─ BESS charging
└─ Grid export
Grid
├─ Site load
└─ BESS charging
BESS
├─ Site load
└─ Grid export
The POI meter records the net result, but it cannot independently explain the internal source of each energy flow.
Energy-source attribution may be measured directly at separate electrical boundaries or calculated through an approved energy-balance method.
In a shared AC-bus architecture, the POI meter and BESS meter alone may not be sufficient to prove whether a specific charging interval was supplied by PV generation or grid import.
Where renewable charging, PPA allocation, export compensation or contractual settlement depends on energy origin, the project should define:
- Physical measurement boundaries
- Energy-allocation method
- Simultaneous-flow treatment
- Data interval and timestamp alignment
- Missing-data rules
- Calculation-method and methodology version
- The party responsible for approving the result
Bidirectional measurement and clearly defined sign conventions are essential for interpreting energy flows.
7. Why Project Replicability Depends on Data Standardisation
Project replication becomes difficult when each site uses different naming, scaling and configuration practices.
Common problems include:
- Different device names
- Reversed import/export conventions
- Inconsistent CT ratios
- Different engineering units
- Uncontrolled register-map changes
- Missing commissioning records
- Inconsistent EMS point names
- No configuration or firmware history
A repeatable architecture should include:
- Standard device list
- Measurement-point naming convention
- Data dictionary
- Register-map version
- Unit and scaling convention
- Direction convention
- Timestamp standard
- Commissioning checklist
- Acceptance criteria
- Configuration backup
- Change-control record
A scalable storage portfolio depends on consistent documentation as much as consistent hardware.
8. Commissioning: From Meter Installation to Valid EMS Data
Commissioning should verify the complete data chain rather than simply confirm that values are visible.
Recommended steps include:
- Confirm wiring, phase mapping and phase sequence.
- Confirm CT polarity, direction and ratio.
- Test zero-power conditions.
- Test positive and negative power flow.
- Confirm import/export and charge/discharge conventions.
- Verify byte order, data type, unit and decimal scaling.
- Compare meter, PCS, PV and POI values.
- Test charging and discharging.
- Test simultaneous PV generation and BESS operation.
- Test communication interruption and recovery.
- Verify record order after communication recovery.
- Check missing, duplicate, substituted and corrected-data flags.
- Confirm timestamp alignment and clock drift.
- Reconcile PV, BESS, load, auxiliary and POI energy.
- Define the acceptable measurement or calculation tolerance.
- Save final point lists, register maps, firmware versions and configuration records.
Commissioning should reconcile the energy balance across relevant boundaries within a project-defined tolerance rather than merely confirm that individual values are visible in the EMS.
A meter can measure accurately while the EMS still displays incorrect values if scaling, direction, byte order or register mapping is wrong.
9. Common Risks in Accelerated Storage Deployment
Common risks include:
- Selecting equipment before defining measurement boundaries
- Treating PCS values as independent metering without confirmation
- Ignoring auxiliary consumption
- Combining PV, BESS and grid import into one unexplained net value
- Assuming energy origin can be proven from POI data alone
- Using inconsistent direction conventions
- Mismatching EMS polling and meter-refresh intervals
- Failing to record firmware or register-map changes
- Omitting data-quality and processing flags
- Using different commissioning templates across projects
- Assuming Modbus support guarantees platform compatibility
- Using a technically suitable meter without confirming billing or settlement acceptance
10. Buyer Checklist for C&I and Co-Located BESS
|
Review area |
What to confirm |
|
Project type |
C&I, PV+BESS, standalone, hybrid or multi-user |
|
Coupling topology |
AC-coupled, DC-coupled or hybrid |
|
Measurement boundary |
PV, battery DC, PCS AC, load, auxiliary or POI |
|
Meter role |
Operational, internal allocation, billing, revenue or settlement |
|
Import/export |
Direction definition and register logic |
|
Sensor type |
Direct, CT, shunt or another compatible sensor |
|
Data interval |
Monitoring, EMS, billing or settlement |
|
Communication |
RS485, Modbus or project-specific interface |
|
Register map |
Address, data type, unit, scaling and version |
|
Time source |
Meter, gateway, EMS or central system |
|
Data quality |
Actual, missing, estimated, substituted, corrected or rejected |
|
Derived data |
Curtailment, self-consumption and energy-source allocation method |
|
EMS responsibility |
Which data comes from meter, PCS, BMS or PPC |
|
Billing acceptance |
Whether the meter and data source are accepted for the intended contractual use |
|
Data retention |
Storage, recovery, audit and correction period |
|
Cybersecurity |
Authentication, access control, firmware and configuration management |
|
Commissioning |
Charging, discharging, PV, energy-balance and recovery tests |
|
Documentation |
Wiring, point list, register map, firmware and configuration version |
|
Legal metrology and certification |
Requirements confirmed by model, country, meter role and intended use |
11. How YTL Can Support Initial Meter Evaluation
Zhejiang Yongtailong Electronic Co., Ltd. (YTL) can support the initial evaluation of selected AC and DC energy meters, CT-operated meters, DIN-rail meters, panel meters and communication-enabled metering products for selected C&I, PV-storage and power-distribution applications.
Depending on the selected model and project requirements, YTL can support:
- Initial model selection
- Voltage and current-range review
- Initial technical discussion of customer-proposed measurement points
- Review of customer-proposed CT ratios, shunt inputs and meter-side sensor requirements
- Import/export measurement review
- RS485 and Modbus option confirmation
- Register-map, unit, scaling and data-format review
- Sample evaluation
- Sample-level meter-to-gateway interface evaluation
- Review of the proposed meter-to-EMS data interface
Communication capability, interval functions, accuracy, certification scope and EMS compatibility must be confirmed according to the selected model and project architecture.
YTL does not define the project’s:
- Energy-allocation methodology
- Curtailment calculation
- Renewable-charging attribution
- Self-consumption calculation
- POI, PCC or settlement boundary
- Export-control strategy
- Billing or settlement acceptance criteria
- EMS optimisation logic
- Asset-control strategy
- Final commissioning tolerance or acceptance
These matters remain the responsibility of the project developer, EPC, EMS or PPC provider, PCS and BMS suppliers, system integrator, utility, meter operator and relevant contractual parties.
YTL supports the field-level electrical-measurement and data-output layer.
Conclusion
Europe’s storage acceleration will create more C&I, PV-plus-storage and hybrid projects, but deployment targets alone do not guarantee successful delivery.
Projects need:
- Clear measurement boundaries
- Defined source-of-truth responsibilities
- Directional energy measurement
- Approved energy-allocation methods
- Consistent register maps and scaling
- Time-aligned EMS data
- End-to-end commissioning
- Controlled documentation and version management
Energy meters are not complete storage-control systems. They form part of the field-level data foundation that allows EMS, SCADA, PCS, PPC and BMS platforms to work with consistent electrical information.
Europe’s storage acceleration will depend not only on how many gigawatts are installed, but also on whether each project can produce consistent, traceable and usable energy data from commissioning through long-term operation.
References
- European Commission, Tripartite Agreement for Energy Storage, 26 June 2026.
- European Commission, EU-Level Tripartite Agreements—Tripartite Agreement for Energy Storage, updated 2026.
- European Commission, Tripartite Agreement for Energy Storage—Project Examples, 26 June 2026.
- European Commission, AccelerateEU to Strengthen EU Energy Resilience, 2026.

English
简体中文







.png?imageView2/2/w/500/h/500/format/png/q/100)





