OSCP Overview

OSCP (Open Smart Charging Protocol) 2.0 coordinates grid capacity and flexible resources (EVSE, PV, batteries, buildings) so Capacity Providers can set safe limits while Flexibility Providers optimise device behaviour. It separates upstream capacity signalling (OSCP) from downstream device control (e.g., OCPP 2.0.1).

The purpose of OSCP is to enable safe, efficient, and scalable management of distributed energy resources by standardising communication between Capacity Providers and Flexibility Providers. It support the delivery of capacity forecasts (CC/GC/FCC/FGC/Optimum) so FPs can steer FRs safely while enabling optimisation; handshakes negotiate heartbeat interval and required behaviour before other messages.

Key roles include:

• Capacity Provider (CP) defines capacity boundaries;
• Flexibility Provider (FP) manages Flexibility Resources (FRs) and enforces capacity limits;
• Capacity Optimiser (CO, optional) computes Optimum targets.

Navigation

• Topology & Architecture
• API
• Use Cases & Flows
• Data Models
• Implementation Details
• References

Versions

VEMO support OSCP 2.0 (see OSCP 2.0 Specification); OSCP 1.x is not supported.

Terminology

Term	Description
Group capacity	Maximum allowable current/power for a group before causing overload.
Capacity Provider (CP)	Defines capacity boundaries (often DSO/EMS).
Flexibility Provider (FP)	Controls Flexibility Resources (FRs) such as EV chargers or batteries.
Flexibility Resource (FR)	Physical energy device that consumes or produces electricity.
Capacity Optimiser (CO)	Optional actor computing Optimum forecasts.
Consumption capacity (CC)	Power flowing into FRs (positive).
Generation capacity (GC)	Power flowing from FRs back to the grid (negative).
Fallback capacities (FCC/FGC)	Safe offline import/export limits.
Optimum (O)	Preferred import/export target within GC/CC bounds.
Offline situation	Loss of communication triggering FCC/FGC.