What smart charging means for a fleet or commercial site

Fleet smart charging coordinates many vehicles within operational, electrical and commercial limits. The cheapest possible session is not the objective if a van misses its route. The system must deliver the required energy before departure while respecting site capacity and any tariff or demand constraints.

For CPOs, the central control layer is normally a charge point management system, also called a CSMS or CPMS. It turns policies into charger instructions, monitors the result and records the session across one or more sites.

How the CSMS and OCPP work together

The CSMS receives charger status and transaction data, calculates or receives a charging plan, then communicates limits through OCPP. In OCPP 1.6, charging profiles can set power or current limits for a charger and time period. OCPP 2.0.1 adds a broader smart-charging model. Support still varies by charger, firmware and backend, so the exact functions must be tested.

A CPO may use the CSMS to apply rules across a mixed estate. Direct charger-to-CSMS communication can reduce dependence on a manufacturer intermediary, but it does not remove integration work. Credentials, connectivity, clock handling, units, profile precedence and recovery behaviour all need validation.

The CPO operating loop

The process is continuous. The CSMS observes connected chargers, applies the operator’s policy, sends limits, then checks whether chargers followed them. Exceptions such as a faulted connector, an unplugged vehicle or a manual override trigger a new plan. Operations teams need alarms and evidence that explain the change, not only an optimiser producing new numbers.

Where an external energy service requests flexibility, the CPO should accept it only within contracted site limits and fleet commitments. The CSMS remains responsible for translating that request into feasible charger instructions.

What data shapes the charging plan?

A commercial plan can combine:

  • vehicle departure time, route and required energy;
  • charger availability and connector state;
  • the fixed site capacity and live building load;
  • electricity prices, capacity charges or contracted limits;
  • onsite solar, batteries or other flexible loads;
  • driver, customer or service-level priorities; and
  • network or flexibility instructions where a contract allows them.

The CSMS does not automatically know a vehicle’s state of charge. That data may come from the vehicle, telematics, an ISO 15118 exchange or an operator estimate, depending on the architecture and permissions.

Site control and portfolio control are different

A local energy-management system can protect the connection and react quickly to building demand. The CSMS can coordinate sessions, users and policies across the portfolio. The two may exchange a site ceiling, while a local controller enforces the immediate limit and the CSMS distributes the available capacity between chargers.

This division matters during an internet outage. The site should retain safe local limits and defined offline behaviour. The CSMS can reconcile stored transactions and resume higher-level optimisation when communication returns. Read how dynamic load balancing handles the local constraint.

How CPOs prioritise vehicles

Equal power is simple but often inefficient. A practical policy may prioritise vehicles leaving first, those below a minimum energy target, emergency or high-utilisation vehicles, or paid service tiers. Lower-priority vehicles can receive power later if their departure requirement remains protected.

The CPO should define overrides for dispatchers and support teams, plus an audit trail showing why a vehicle received less power. Plans also need headroom for cold weather, delayed arrivals and charger faults.

What must be tested before rollout?

Test the actual charger, firmware and CSMS or CPMS with realistic numbers of vehicles. Confirm charging-profile behaviour, phase limits, local load data, session recovery, offline operation and what happens when two systems send competing limits. Measure whether vehicles meet departure targets, not only whether a dashboard shows a schedule.

How amina fits

amina supplies focused hardware for CPOs and works with specialist software and energy partners. Current amina C/C2 and M/M2 product information states local OCPP 1.6J and hardware readiness for OCPP 2.0.1. Hardware readiness does not confirm every OCPP 2.0.1 smart-charging function in a specific deployment. Choose a tested combination from the current integration partners and prove the intended profiles before scaling.

This is one commercial use of smart charging. The charger, CSMS, local controller and energy service each need a clear job.