See how open protocols enable roaming, pricing, authorization, and real-time EV charging operations.

Being an eMobility leader in various projects across multiple startups, Piotr was responsible for OCPI and OCPP integration as well as EMP and CPO platforms development. With extensive expertise in the open standards field and eMobility tech solutions, he is leading teams of experienced developers and contributing with invaluable knowledge and experience.

Piotr Majcher

Every new EV charging network begins with the same question. How do we make our stations visible, usable, and trusted across multiple EV charging systems without drowning in custom integrations? The answer sits in the 

 run the data exchange that keeps charging locations discoverable, sessions authorized, tariffs clear, and roaming partners synced. They help CPOs, eMobility Service Providers, and enterprise teams launch scalable charging services without rebuilding the wheel for every partner.

The next sections break down how OCPI and OICP work and why they matter for the future of efficient charging networks.

Why open standards matter for EV charging networks

EV charging businesses grow through partnerships. You run charge points, connect with eMSPs, exchange data with roaming platforms, and support EV drivers who expect accurate information at all times. Every partner depends on clean data and fast synchronization. When each system uses its own logic, integrations slow down and operations get messy.

Open standards fix this. OCPI and OICP give the market a shared way to exchange charging point locations, tariff information, session data, authorization, and 

 commands. They help CPOs and eMSPs expand coverage, cut down onboarding time, and keep billing consistent across different EV charging networks. For electric vehicle owners, this means predictable access to charging stations with a single account and a unified experience across multiple networks.

Open communication protocols keep EV roaming stable, operations efficient, and allow any 

 to scale without building one-off workarounds for every partner.

Open Charge Point Interface (OCPI) is a structured protocol designed to let EV charging systems exchange data precisely and reliably. It defines how CPOs, eMSPs, and roaming partners share information on charging stations, live status, 

, pricing, tokens, and session progress. Instead of building custom logic for each partner, companies follow one standard that keeps data aligned across different EV charging networks.

The strength of OCPI comes from its clarity. It defines how platforms connect, how they sync real-time updates, and how they handle the charging process from discovery to billing. This removes a large amount of technical overhead and cuts integration time for any operator entering new markets.

OCPI runs in real time and is known for transparent data exchange, which helps service providers deliver accurate information to EV drivers. It also has global recognition and is actively maintained by the EVRoaming Foundation, which ensures the protocol remains open, neutral, and aligned with industry needs. As the foundation states, 

“OCPI facilitates roaming by enabling seamless data exchange between market players,”

 a rule that keeps modern charging infrastructure scalable and predictable.

Learn more about OCPI versions (OCPI 2.1., OCPI 2.2, OCPI 3.0) in our 

OCPI works through a set of modules that cover the full charging journey. Each module solves a specific part of roaming, authorization, smart charging, or billing. Together, they give CPOs, eMSPs, and roaming partners a reliable way to exchange data across different EV charging networks.

This module sets up trust between partners. It handles the tokens that allow two platforms to open a secure connection.

Both sides confirm which OCPI version they support and which modules are available. It keeps the integration clean from day one.

This module shares static charge point information and real-time details about availability, connector types, power levels, and opening hours. Drivers depend on this data to find the right charging point.

It tracks the entire charging process. You get time stamps, energy usage, charging status, and session progression. This data powers smart charging decisions and session monitoring.

The module allows operators or eMSPs to send actions like remote start or stop. It supports smart charging commands that keep the process smooth for drivers and reliable for network operators.

This module manages authorization. It verifies RFID cards, app users, Autocharge IDs, or any identifier needed to start a charging session.

Tariff information helps eMSPs and CPOs keep pricing clear. It defines energy rates, time-based fees, parking time, and flat components that shape the final charging cost.

Charge detail records represent the financial truth of a charging session. They include signed meter data, tariff details, timestamps, and energy consumption.

With these modules, OCPI supports peer-to-peer connections, direct bilateral connections, and EV roaming through platforms that rely on the protocol. It keeps data consistent across charging stations, service providers, and charging management systems.

Implementation starts with exchanging initial tokens and confirming the OCPI version through the Credentials and Versions modules. After that, both sides map their internal data to OCPI models and expose the required endpoints.

Once the handshake is active, partners test key flows such as location updates, session authorization, smart charging commands, and CDR delivery. When tests pass, the connection moves to production, and the roaming data sync begins.

’s protocol for roaming between many EV charging networks through a single connection. It sits in the backend layer of the EV charging ecosystem. This means it does not operate at the moment when the car 'talks' to the charging station. That handshake is handled by OCPP and the charger’s hardware. OICP steps in after that point, when platforms exchange data about charging locations, availability, 

, session authorization, and CDRs across different networks.

In practice, a car connects to an EV charger, the charger connects to the CPO backend, and the CPO backend uses OICP to communicate with Hubject. The hub routes roaming requests to the correct eMSP or partner network. This setup removes the need for direct connections between each pair of operators.

OICP covers the core roaming use cases: discovering charging stations, authorizing sessions, passing smart charging commands, and delivering CDRs. Companies that join Hubject gain access to many networks with one integration, which speeds up market expansion and simplifies operations. It is a strong fit for businesses that value reach and fast scaling across multiple countries.

OCPI vs. OICP within the EV charging industry

OCPI and OICP solve the same problem, but they take different routes.

OCPI uses a peer-to-peer model. Each CPO or eMSP connects directly to another partner. This gives you strong control over data exchange and flexibility in how you shape business models. It works well for organizations that want tight integrations, custom agreements, or clear ownership of every roaming link.

OICP leans on the power of the hub. You integrate with Hubject once and gain access to a wide network of charging partners. This cuts technical effort and speeds up expansion. It fits companies that focus on reach and simplicity rather than managing every connection themselves.

OCPI brings granular control. OICP brings scale through a central hub. Many operators use both to cover different charging networks and meet market demands. The choice depends on your roadmap, partner strategy, and the level of control you expect over roaming flows.

How CPOs and eMSPs implement these protocols

CPOs and eMSPs use OCPI and OICP to sync their EV charging infrastructure with roaming partners and keep charging sessions flowing without friction. The process starts by exposing the correct endpoints and aligning internal data with protocol models. Charging locations, connector details, tariffs, tokens, and session data must match the structure expected by the partner or roaming hub.

Once the handshake is active, the platform begins to exchange key data in real-time. Charging stations share status updates, smart charging commands flow between systems, and session authorization happens through tokens or app-based IDs. After a session ends, CDRs with signed meter data, timestamps, and costs move between systems to support billing and reporting.

CPO platforms use these protocols to publish charging station data and accept authorizations from roaming EV drivers. eMSP platforms use them to display accurate charging locations, manage payments, and start or stop sessions on external networks. Together, these standards help companies expand their footprint and operate across many charging networks with predictable data and clear financial flows.

What this means for your charging business

OCPI and OICP give you a practical way to grow your charging network without juggling endless custom integrations. These standards help your platform stay compatible with roaming partners, keep tariffs clean, and maintain the real-time data flow your operations depend on. They support clear pricing, accurate CDRs, authorization, and the smart charging features EV drivers expect from a modern network.

If you run a CPO business, these protocols make your stations visible, accessible, and ready for roaming. If you run an eMSP platform, they help you present reliable charging locations, manage payments, and start sessions on external networks without friction. Teams that adopt OCPI or OICP early onboard partners faster, scale across multiple networks, and keep operations predictable.

Solidstudio builds EV charging software systems that match this reality. Our CPO Platform and eMSP Platform support OCPI, OICP, and major roaming partners out of the box. You get a production-ready system with charging station management, roaming configuration, tariff handling, payments, smart charging features, and the admin tools your team needs to run a growing EV charging business.

If you want to build or scale your EV charging offer with infrastructure that’s already aligned with industry standards, explore 

Learn how OCPI and OICP power roaming, data exchange, and scalable EV charging networks for CPOs, eMSPs, and enterprise charging businesses.

OCPI and OICP Protocols for EV Charging Networks Explained

Learn how utilities use OCPP Proxy to manage EV chargers across multiple backends. 

Aldona is a Content Manager whose ultimate goal is to tell you a good story, not compromising on the knowledge-sharing part.

Aldona Krysiak-Adamczyk

Utilities are leading the shift to electrified mobility. But when it comes to EV charging, the technology stack often gets in the way.

Mixing charger brands, backend systems, and data platforms quickly turns interoperability into a full-time job.

 changes that. It gives utilities control over charger–backend communication, allowing them to switch, scale, and monitor their networks without reconfiguring a single charger.

Expanding into EV charging as part of the energy transition

For most utilities, entering EV charging is a natural next step. It connects directly to grid management, renewable integration, and long-term energy strategy.

But expanding into charging also means stepping into a fragmented ecosystem. Every charger OEM, backend vendor, and platform integration adds another layer of complexity and a growing risk of vendor lock-in.

 enables utilities to maintain control as they scale. By sitting transparently between chargers and backends, it keeps communication flexible and interoperable across all vendors. That means new hardware or software can be added without redesigning the network or breaking what’s already working.

It’s a small architectural change with big strategic impact; one that lets utilities evolve their charging networks at their own pace, not their vendors’.

Interoperability with multiple charger OEMs and backends

Utilities rarely operate in a single-vendor world.

Utilities often operate charging networks built from different hardware vendors and connected to several backend systems. In many cases, these systems run in parallel across regions or business units.

That’s where the challenge begins. Each vendor comes with its own interpretation of 

, connection quirks, and integration processes. Without a flexible control layer, every addition or change introduces risk, delays, and new dependencies.

The OCPP Proxy simplifies this landscape by standardizing how chargers communicate. It routes OCPP traffic consistently, regardless of manufacturer or backend platform, ensuring that all components stay interoperable.

Instead of building new integrations for every vendor combination, utilities can focus on scaling, confident that their network will remain compatible as it grows.

Switching or adding backends without touching charger configurations

Switching backend platforms shouldn’t mean reconfiguring thousands of chargers. Yet for many utilities, that’s still the reality. Every time a new 

 is introduced, whether for testing, migration, or vendor change, each charger needs to be manually updated.

It’s slow, error-prone, and disrupts network operations.

The OCPP Proxy eliminates that bottleneck. Decoupling chargers from the backend allows utilities to redirect traffic centrally, without touching a single device in the field. Switching or adding a backend becomes a configuration change, not a field project.

This flexibility enables testing new systems, migrating gradually, or operating multiple platforms side by side. For utilities, that means faster decisions, cleaner transitions, and 

Running multiple backends in parallel to support diverse use cases

Utilities rarely move all at once. Pilots, regional rollouts, and parallel testing are part of how large networks evolve. But traditional OCPP setups make this almost impossible - a charger can connect to one backend at a time, and switching means downtime.

The OCPP Proxy changes that dynamic. It allows OCPP traffic to be routed, duplicated, or segmented across multiple backend systems simultaneously.

Test a new backend in production conditions

Run analytics or staging environments in parallel

Migrate gradually instead of all at once (check how 

This multi-backend setup keeps operations stable while innovation continues in the background. For teams balancing reliability with experimentation, it’s the safest way to move forward without slowing down.

Retaining ownership of data independent of backend providers

For utilities, data is a core strategic asset that drives every operational decision.

 to customer analytics, visibility into OCPP communication directly supports smarter energy management.

In many vendor-dependent setups, that data sits within backend systems outside the utility’s direct control. Access is often limited, delayed, or restricted by the vendor, making it difficult to create unified insights or stay fully compliant.

The OCPP Proxy changes that. It acts as a transparent communication layer, capturing and routing all OCPP traffic between chargers and backends. That gives utilities full visibility into message flows, performance metrics, and connection states in real-time.

With this control, data ownership stays where it belongs: within the utility’s infrastructure. And that means analytics, optimization, and strategic planning can move forward without dependency or compromise.

Scaling pilots and rollouts without migration headaches

For most utilities, EV charging starts small - a pilot here, a local rollout there. But scaling those early projects into a national or regional network often exposes the limits of the original setup.

Every new site adds chargers, vendors, and configurations. Without a flexible communication layer, expanding the network can mean rebuilding integrations or managing 

The OCPP Proxy removes that barrier. Once deployed, it serves as a stable control layer that supports continuous scaling. New chargers or backend systems can be added through configuration changes, not infrastructure overhauls.

That means pilots can evolve naturally into production networks - no downtime, no migrations, no technical debt. Utilities can grow their EV operations at the speed of strategy, not the pace of system reconfiguration.

Expanding into EV charging doesn’t have to mean handing over control to vendors or rebuilding infrastructure every time your plans evolve. The most successful utilities are the ones treating flexibility as part of their foundation, not a feature to add later.

 gives you that control. It keeps your network interoperable, your data independent, and your rollout strategy on your own terms.

If you’re planning to scale your EV charging operations or preparing for your next backend integration, our engineering team can help you design the right setup for your environment.

 to see how the OCPP Proxy can fit into your architecture, and make flexibility a built-in part of your EV strategy.

Learn how utilities use OCPP Proxy to manage EV chargers across multiple backends. Gain flexibility, retain data ownership, and scale without downtime.

How Utilities Use OCPP Proxy for EV Charging Control 

Learn how the OCPP Proxy simplifies backend switching, monitoring, and multi-system integration.

Krzysztof is our Head of Products and he leads the technical development behind the suite of our ready-made solutions. Throughout the years in Solidstudio, he gained an invaluable insight into the eMobilty industry’s requirements and is now more than qualified to share his knowledge with others.

Krzysztof Ciombor

, you already know the promise: open standards, vendor independence, seamless interoperability.

As soon as you start mixing charger brands, backend systems, and testing environments, one small change can ripple through the whole setup. Want to switch a backend? You’ll need to reconfigure every charger. Want to test a new platform in parallel? Good luck without creating chaos.

In most networks, each charger is still manually tied to a single backend. That static setup means every small change, like switching systems to test new platforms, becomes a full reconfiguration exercise. The flexibility promised by OCPP gets lost in the process.

This is exactly where a smarter approach comes in: 

It doesn’t reinvent OCPP, but it adds the missing piece that makes interoperability 

On paper, OCPP is supposed to make your life easier. In practice, it can feel like you’re wiring a house with spaghetti.

: each charger knows exactly one backend, and every change means touching configuration at the edge. It works fine when you’re managing a few dozen units. But scale that up to thousands, across sites or vendors, and suddenly you’re juggling:

Charger reconfigurations for every migration or test

Compatibility quirks across OCPP versions or vendor stacks

Vendor lock-in, where flexibility turns into dependency

And let’s not forget visibility. Once a charger connects to a backend, the communication flow becomes a bit of a black box. If something breaks, you’re relying on limited logs or guesswork to find out 

So even though OCPP gives you a common language, what’s missing is a 

, in other words, a way to route, observe, and manage that traffic dynamically, without ripping apart your setup every time requirements change.

That’s exactly the gap an OCPP Proxy fills.

The OCPP Proxy functions as an intermediary layer that manages communication between chargers and backend systems.

It operates transparently between the two, routing and duplicating OCPP messages without modifying their structure or content.

In other words, it doesn’t interfere; it orchestrates.

Technically, it’s a transparent middleware layer that handles JSON-over-WebSocket communication between chargers and one or more backends. But the real value is in the control this architecture provides.

Switch backends dynamically, without reconfiguring chargers or interrupting sessions

Run multiple backends in parallel for testing, analytics, or multi-tenant setups

Monitor and debug live OCPP traffic without touching production systems

Stay compliant with OCPP 1.6 and 2.0.1 across vendors

Deploy efficiently, whether on-premise, in the cloud, or in hybrid environments

You can think of it as a lightweight, scalable, and fully transparent OCPP broker. The Proxy doesn’t alter messages; it simply manages where they go and how they flow.

A utility operating thousands of chargers wants to test a new backend while keeping the old one live. Traditionally, that means reconfiguring every charger or running two isolated networks. With the OCPP Proxy, engineers can define new routing rules, and the switch happens in real time. Some chargers connect to Backend A, others to Backend B. No downtime, no disruption.

It’s the kind of flexibility OCPP was designed for, but rarely achieved in production.

The result is a more flexible and future-proof architecture, one that gives operators full control over OCPP communication without touching the chargers themselves. But the real impact of this pattern becomes clear when you look at how different organizations use it.

The OCPP Proxy has become a practical enabler of interoperability across the EV charging landscape, including utilities running multi-vendor networks, integrators building complex infrastructure projects, or backend migration projects, avoiding unnecessary downtime

How the OCPP Proxy fits into real-world operations

The OCPP Proxy isn’t tied to one business model or network size. Its role is to make complex OCPP communication manageable, regardless of how your charging ecosystem is built. Here’s how different types of organizations are already using it in practice.

Many operators eventually face the same challenge: moving from one backend system to another. Whether it’s due to scaling, vendor changes, or platform consolidation, backend migrations have a reputation for being slow, risky, and disruptive.

In a traditional OCPP setup, migrating means reconfiguring every charger, scheduling downtime, and hoping no connection breaks in the process. The OCPP Proxy makes that process far more controlled.

Decoupling chargers from the backend allows live backend switching through dynamic routing. Operators can direct a subset of chargers to the new system, keep the old one running in parallel, and observe message flows before committing fully. Once validated, the transition can happen without interrupting service or touching a single charger configuration.

For many organizations, this becomes the first real proof point of what a decoupled OCPP architecture can do: deliver operational flexibility without sacrificing uptime.

For utilities expanding into EV charging, interoperability is everything. Their networks combine chargers from multiple OEMs, often managed across different backend platforms. The OCPP Proxy allows them to switch, segment, or duplicate traffic between those platforms in real-time without touching the chargers.

During backend transitions, the proxy lets teams operate new and legacy systems in parallel, verify message flows, and cut over when ready. The result is a flexible architecture where utilities retain ownership of their infrastructure and data, independent of backend vendors.

Turnkey providers deliver end-to-end charging services such as equipment, installation, software integration, and operations. What slows them down is the integration complexity: every client has unique hardware and backend preferences.

With the OCPP broker in place, these providers can unify communication between diverse charger models and backend systems, supporting multi-tenant or client-specific setups.

It turns custom integration work into configuration, shortening deployment timelines, reducing maintenance, and allowing fast iteration across projects.

Technology and mobility service providers

Fleet management, telematics, and energy optimization platforms increasingly include EV charging as part of a broader offering. But integrating chargers into those digital ecosystems usually means rewriting parts of the backend or building custom connectors.

The OCPP Proxy eliminates that friction. It routes and replicates OCPP traffic between chargers and internal systems, enabling data sharing and analytics without backend rewrites.

This approach keeps platforms modular, scalable, and backend-agnostic, ideal for fast-growing technology environments.

For system integrators working on industrial sites, transport infrastructure, or citywide charging projects, reliability and transparency matter more than anything.

They need visibility into OCPP traffic during deployment and commissioning, and they often deal with layered or distributed networks.

The proxy provides a controlled communication layer, allowing engineers to manage routing, inspect message flows, and debug in real-time. It replaces ad-hoc middleware with a proven, production-ready component that reduces development risk and improves stability at scale.

Operators managing multiple depots or regional networks face another challenge: maintaining stable connections across mixed hardware and backend systems.

With the Proxy, they can segment traffic by region, manage backend transitions without downtime, and centralize monitoring across the entire network.

It ensures consistent operation and visibility even as the fleet grows and infrastructure evolves.

OCPP Proxy is designed to stay out of the way. It doesn’t replace your backend or change the OCPP protocol. It simply manages how communication flows between chargers and central systems, transparently and in real time.

The architecture follows a lightweight, scalable model built around a few key principles:

The proxy passes OCPP messages exactly as they are, maintaining full protocol compliance. Both the charger and the backend remain unaware that a proxy is sitting in between.


Routing rules define where traffic goes: per charger, per backend, or per message type. Those rules can be adjusted at runtime, without restarting the OCPP broker or reconfiguring hardware.

Each instance can handle thousands of concurrent WebSocket connections with minimal resource overhead. The proxy runs as a containerized service and scales horizontally using standard load balancers or orchestration tools.

It runs anywhere Docker does, be it cloud, on-premise, or hybrid. This makes it simple to integrate with existing CI/CD pipelines or infrastructure setups.

Routing rules and connection states are stored in a lightweight, persistent layer so that configurations survive restarts or redeployments.

In short, the OCPP Proxy adds control without adding complexity. It’s a modular building block that can sit neatly inside almost any EV charging architecture giving engineers the flexibility to manage, migrate, or monitor at scale.

At the end of the day, managing EV charging infrastructure shouldn’t feel like juggling cables in the dark. If switching backends, adding systems, or troubleshooting OCPP traffic still feels complicated, that’s a sign your architecture is doing too much heavy lifting on its own.

A simple routing layer, like the OCPP Proxy, can take that complexity off your plate. It gives your team control without chaos, visibility without risk, and the freedom to evolve your setup at your own pace.

If you’re ready to make your OCPP environment a little smarter 

, let’s talk about where this fits in your network.

Manage and scale EV charging networks easily. Learn how the OCPP Proxy simplifies backend switching, monitoring, and multi-system integration.

OCPP Proxy: Simplifying EV Charger Management

Learn how OSCP gives your platform grid-aware control, flexibility, and no vendor lock-in

Managing EV charging infrastructure today means managing energy systems. 

 platforms are expected to coordinate power distribution across locations, align with grid capacity, and support remote control in real time. Static scheduling or station-level commands are no longer enough.

To meet these demands, platforms need protocols that support forecasting, flexibility, and system-wide communication. 

The Open Smart Charging Protocol (OSCP) provides that layer.

 It enables charge point operators and service providers to work with Distribution System Operators (DSOs), adjust load intelligently, and scale charging infrastructure without vendor lock-in.

This article outlines how OSCP fits into a modern CPMS or EMSP architecture, and why it's becoming a foundational part of smart EV charging infrastructure.

Why smart charging needs a protocol like OSCP

OCPP handles communication between a charging station and the management system. But it doesn’t account for the condition of the grid, forecasted capacity, or any external constraints that affect how and when energy should be delivered.

As charging networks expand and power grids become more dynamic, platforms must do more than send start and stop commands. They need to monitor available capacity, adjust charging profiles in real-time, and coordinate behavior across hundreds or thousands of distributed charge points.

This is where smart charging protocols come in. 

OSCP provides a structured way to share data between energy providers and charging platforms.

 It introduces a control layer that helps CPMS and EMSP systems distribute energy more efficiently, prevent overloads, and reduce costs during peak hours.

What is Open Smart Charging Protocol (And why it’s different)

The Open Smart Charging Protocol (OSCP) is a communication standard that connects charge point platforms with energy systems. It was developed by the Open Charge Alliance, the same group behind 

, to enable real-time coordination between Charge Point Operators (CPOs), Distribution System Operators (DSOs), and energy management systems.

The core function of OSCP is to deliver a 24-hour forecast of local grid capacity. This allows charging platforms to shape energy usage proactively, based on actual grid constraints. Where OCPP handles station-level messaging, OSCP operates at the system level, guiding when and how much energy can be delivered across the entire charging network.

Version 2.0 of OSCP expands on the original by introducing a more flexible domain model and clearer terminology. It also broadens the protocol’s scope beyond electric vehicles, allowing integration with other flexible energy resources like batteries or heat pumps.

The OSCP architecture: Roles and terminology

OSCP introduces a domain model designed to reflect how real-world energy systems interact with charging infrastructure. It defines four key roles:

A device that can consume or produce energy in a controllable way. This includes EVs, battery storage systems, and heat pumps.

An entity that manages one or more flexibility resources. For most platforms, this means the CPMS or the EMSP acting on behalf of site operators.

A Distribution System Operator (DSO) or Energy Management System (EMS) responsible for managing grid capacity. They provide the 24-hour capacity forecasts that drive OSCP behavior.

A service that helps the flexibility provider make better decisions, like an aggregator or energy analytics engine.

Each role is abstracted to support a variety of use cases, from EV fleets to distributed energy systems. This architecture lets platforms operate within a grid-aware context without hardcoding vendor-specific logic.

At the core of OSCP is its ability to share a 24-hour forecast of available grid capacity. This forecast is sent from the Capacity Provider (typically a DSO or EMS) to the Flexibility Provider (the CPMS or EMSP). The data is time-based and includes specific limits on how much energy can be consumed or fed back into the grid in each interval.

 – the maximum energy that can be consumed in a given period.

 – the maximum energy that can be fed back to the grid.

 – baseline limits used if the connection to the Capacity Provider is lost.

 – the ideal amount of energy to use or return, based on current grid conditions.

With this information, the CPMS can shape charging schedules, delay or reduce load when needed, and prioritize charging sessions based on available capacity. This supports real-time demand balancing, prevents grid overloads, and allows platforms to integrate with 

OSCP isn’t just about passive forecasting. It also enables active, real-time communication between the Flexibility Provider (e.g., CPMS or EMSP) and the Capacity Provider (e.g., DSO or EMS). This allows the system to respond to actual conditions as they change.

When the Flexibility Provider anticipates a need to exceed the forecasted limits, such as increased charging demand at a site, it can send an AdjustGroupCapacityForecast request. The Capacity Provider can respond in one of two ways:

, allowing the additional load and updating the capacity forecast accordingly.

, returning a GroupCapacityComplianceError, which signals that no extra capacity is available.

This mechanism gives platforms a structured way to negotiate resources while maintaining grid stability and compliance. It also supports more intelligent scheduling, especially in scenarios involving high load variability, fleet coordination, or sites with mixed charging hardware.

Learn how the Open Smart Charging Protocol (OSCP) helps CPMS and EMSP platforms manage grid capacity, reduce load, and scale EV infrastructure with full flexibility.

Let’s read our posts

How AI Secures EV Charging Networks and Prevents Fraud

Recommended

eMobility Fundamentals - the eBook

Why does software matter in eMobility?

The Ultimate Guide to EV Charging Software Migration - the ebook

How Utilities Use OCPP Proxy for EV Charging Control

OCPP Proxy: Simplifying EV Charger Management

Open Smart Charging Protocol (OSCP) for CPMS & EMSPs Explained

Range Anxiety Is Real, But It’s Not the Problem You Think

Smart Charging: Making EV Energy Use More Efficient

Telcos and EV Charging: An Unlikely Pair That Makes Perfect Sense