Managed EV Charging
Coordinated control of EV charging to meet vehicle needs while respecting site, cost, or grid constraints.
Share this

The problem
Why MECG exists
This section requires approved editorial content.
No substitute explanation has been generated for why Managed EV Charging exists.
Operating model
How MECG works
The approved explanation should connect physical systems, communications, data, security, and operating responsibility.
Managed EV Charging schedules or adjusts charging power using vehicle requirements, charger availability, electricity prices, site capacity, or grid signals. Fleet and V2G platforms use it to reduce peaks, avoid infrastructure overload, and prepare vehicles for service. It is distinct from bidirectional charging because control can apply to one-way charging.
Documented activity
Real-world applications
Examples come from verified deployment relationships rather than template-generated use cases.
This section requires approved editorial content.
No substitute explanation has been generated for real-world applications.
Knowledge database
Explore the ecosystem
Counts are navigation into the records supporting this technology profile.
Technology map
Related technologies
These records share a documented category. Their placement does not imply technical dependency or compatibility.
This section requires approved editorial content.
No substitute explanation has been generated for related technologies.
Evidence and relationships
Supporting database
Structured records connected to this technology through reviewed Directus relationships.
Interoperability
Standards
IEC 63110-1
IEC 63110-1 defines management architecture and use cases for charging and discharging infrastructure. It matters to V2X because it gives independently developed systems a common technical contract.
IEEE 2030.5
IEEE 2030.5 defines application messaging between energy devices and utilities, including distributed-energy and managed-charging functions. It matters to V2X because it gives independently developed systems a common technical contract.
OCPP 1.6
OCPP 1.6 defines management messages exchanged between charging stations and central systems. It matters to V2X because it gives independently developed systems a common technical contract.
OCPP 2.0.1
OCPP 2.0.1 defines charging-station management with device modeling, security, smart charging, and ISO 15118 support. It matters to V2X because it gives independently developed systems a common technical contract.
OCPP 2.1
OCPP 2.1 defines newer charging-station management functions including bidirectional charging and distributed-energy integration. It matters to V2X because it gives independently developed systems a common technical contract.
OpenADR 2.0b
OpenADR 2.0b defines automated exchange of demand-response events and reports between energy-service operators and participating resources. It matters to V2X because it gives independently developed systems a common technical contract.
OpenADR 3.0
OpenADR 3.0 defines a modern web-API model for communicating demand-response and distributed-energy events. It matters to V2X because it gives independently developed systems a common technical contract.
SAE J2847/1
SAE J2847/1 defines messages used between plug-in vehicles and the grid for managed charging use cases. It matters to V2X because it gives independently developed systems a common technical contract.
Institutions
Organizations
research_institution
U.S. national laboratory researching energy systems, buildings, computing, and grid-interactive transportation.
research_institution
U.S. national laboratory researching renewable energy, transportation electrification, grid integration, and managed charging.
industry_consortium
Industry alliance promoting automated demand-response standards used in managed charging and grid integration.