PowerBank: Transforming charge points into Grid-Balancing assets

The global electricity grid, as we know it, was never designed to handle the exponential rise in electricity demand. With renewable energy’s inherent volatility and shifting consumption patterns, we now face the challenge of balancing an increasingly unstable grid. At Monta, we believe this challenge presents an opportunity—and our solution is PowerBank.

What is PowerBank?

PowerBank is a groundbreaking service enabling charge point owners to support grid balancing while creating new revenue opportunities. By momentarily pausing ongoing charges at PowerBank-enabled charge points when grid imbalances are detected, Monta allows these charge points to participate in balancing and flexibility markets. This transforms them into valuable assets for ancillary grid services.

The result? A win-win for everyone. The grid gains stability, charge point owners unlock an additional revenue stream, and renewable energy becomes more reliable.

How PowerBank works

Monta is developing PowerBank to deliver Primary Reserve (FCR), a critical grid service that demands ultra-fast data monitoring and response. Here’s how it works:

• Power updates from charge points are measured locally once per second and forwarded to Monta.
• These updates are sent when a configurable power change is detected (e.g., 200 W) or at configurable intervals (e.g., every 15 minutes) to minimize unnecessary data traffic.

This precision ensures grid balancing can occur swiftly and effectively without overburdening hardware manufacturers or Monta’s systems.

Technical overview for hardware manufacturers

To enable charge points to support PowerBank, we’ve outlined key technical specifications:

1. Real-Time Monitoring: Power values must be measured locally at least once per second during charging.
2. Efficient Data Transmission: Power updates should be forwarded to Monta when:
   • A configurable power change occurs (e.g., a 100 W change).
   • At a configurable interval (e.g., every 5 minutes) if no change is detected.

We’re already collaborating with several charge point brands that meet—or are close to meeting—these specifications. However, our vision is to include all our hardware partners, ensuring no one is left behind.

Why PowerBank matters

PowerBank isn’t just another feature; it’s a market-disrupting technology poised to redefine how charge points interact with the grid. Charge point owners are already signing up, and the positive feedback underscores its potential.

By enabling flexibility services, manufacturers can position their charge points as future-ready and indispensable for a sustainable energy grid. Together, we can build a grid system that supports renewable energy growth and creates a more reliable infrastructure for EVs.

Join us in revolutionizing the grid

We invite all hardware manufacturers to make their charge points compatible with PowerBank. Whether you’re ready to integrate or need support in meeting the technical requirements, Monta is here to help. Let’s collaborate to ensure your hardware is equipped to deliver flexibility services and drive this innovation forward.

For more details or assistance, reach out to Alex Iriondo, Product Manager - Grid Services, at alir@monta.com.

Together, we can make PowerBank a cornerstone of the modern electricity grid.

Appendix - Technical specifications 

Abbreviation table can be found at the end of the document. 

In order for a CS to participate in grid flexibility markets, three requirements must ideally be met: 

1. During a charging transaction, the power meter values for each of its EVSEs must be able to be measured locally at least once per second. 

2. During a charging transaction, the power meter values for each of its EVSEs must be forwarded to the CSMS within one second whenever a configurable change in power has been detected, down to a minimal configurable change of 100 Watts. 

3. During a charging transaction, the power meter values for each of its EVSEs must be forwarded to the CSMS at a configurable interval down to once per 5 minutes. 

Requirement 1 is a prerequisite for requirement 2 and 3 and is not directly visible in OCPP protocol implementations. 

Depending on the OCPP standard used, we suggest to map requirements 2 and 3 to OCPP as follows:

OCPP 1.6 

Requirement 2 

OCPP 1.6 does not, out of the box, support configuring a CS to send meter values whenever a configurable change in power has been detected. 

We suggest that manufacturers add the following writable configuration key: 

Suggested key configuration for OCPP 1.6 compatibility

Manufacturers should support the trigger to send a MeterValues.req PDU to the CSMS at least once per second when the configuration is active and a charging transaction is active. 

Manufacturers should support setting a delta value down to 100 (Watts). 

The delta value signifies the value change in the overall Power.Active.Import since the last time a MeterValue class was sent (in a MeterValues.req or StopTransaction.req PDU) containing the overall Power.Active.Import measurand or one of the phase Power.Active.Import measurands.

Requirement 3 

OCPP 1.6 already supports configuring a CS to send meter values at set intervals using the ChangeConfiguration.req PDU (OCPP 1.6, section 6.9) with the following configuration key: 

MeterValueSampleInterval (OCPP 1.6, section 9.1.19.) along with MeterValuesSampledData (OCPP 1.6, section 9.1.17.) for sending meter values within transactions at set intervals. 

Manufacturers should support MeterValueSampleInterval down to 300 (seconds). Manufacturers should support the measurand Power.Active.Import(OCPP 1.6, section 7.31). OCPP 2.0.1 

Requirement 2 and 3 

OCPP 2.0.1 supports advanced monitoring using the Device Management Monitoring feature (OCPP 2.0.1, Part 1, section 4.4.). This allows a CSMS to set both periodic and delta-based monitoring on the power of each EVSE of a CS, if supported by the manufacturer. 

Manufacturers should therefore support the following Device Management Monitoring features (see (OCPP 2.0.1, Part 2, section N.2.): 

• N02 Get Monitoring report 
• N04 Set Variable Monitoring on the variable Power of each EVSE of a CS (OCPP 2.0.1, Part 2, appendix 3.2.30.) with the Delta and Periodic monitor types (OCPP 2.0.1, Part 2, section 3.55).
• N06 Clear / Remove Monitoring 
• N07 Alert Event 
• N08 Periodic Event

Manufacturers should support setting the periodic interval down to 300 seconds and the delta value down to 100 Watts. 

Manufacturers should support the delta trigger to send a NotifyEventRequest.req PDU to the CSMS at least once per second during a charging transaction when the monitoring is active.

Abbreviations