zevOS

01Features · Operations

Fit more chargers behind the same sanctioned load

Most sites run out of sanctioned load long before they run out of parking. Smart charging lets you install more connectors than the connection could serve at full tilt, and share what you have between the cars actually plugged in. zevOS pushes real OCPP charging profiles to the hardware, so the limit holds even if the network drops.

Smart charging & load management

  • TxDefault + Tx

    Profile types

  • Amps or watts

    Units

  • On every boot

    Re-applied

Capabilities

What this gives you

01

Per-EVSE default limits

Set a power or current ceiling for each EVSE once. zevOS stores it, sends it as a TxDefaultProfile, and re-sends it automatically after every BootNotification — so a charger that was power-cycled by a site electrician comes back with your limit intact, not the factory maximum.

  • Limit in kW or in amps, per your DisCom paperwork
  • Auto-apply on boot, with the last-sent timestamp and status shown
  • Clear a profile to hand full capacity back
02

Site-level load sharing

Distribute a site’s available capacity across active sessions rather than first-come-first-served. When a car finishes, its share is returned to the pool and the remaining vehicles speed up.

  • Static allocation against a sanctioned site limit
  • Even or priority-weighted distribution between connectors
  • Headroom reserved for non-charging site load
03

Time-of-day shaping

Pair charging limits with time-of-day tariffs so the network naturally pulls harder when power is cheap and eases off during peak DisCom windows. The commercial signal and the physical limit stay in agreement.

04

Session-level overrides

Cap an individual session when a fleet policy or a site rule demands it, without disturbing the defaults the rest of the network runs on.

Specifications

The technical detail

The things a procurement team or an integration partner will ask for, stated plainly.

OCPP messages
SetChargingProfile, ClearChargingProfile, GetCompositeSchedule
Profile purposes
TxDefaultProfile, TxProfile
Rate units
A (current) and W (power)
Re-apply trigger
BootNotification, manual push

Not yet

On the roadmap

Listed separately because a roadmap item is not a feature, and treating it as one is how procurement decisions go wrong.

  • Dynamic load management driven by a live site meter feed
  • OpenADR-style demand-response signals from utility partners

Questions

What operators ask about this

What if the charger ignores the profile?

The charger’s response to SetChargingProfile is recorded, and the composite schedule can be read back to confirm what the unit believes it is enforcing. Models that reject profiles are flagged so you do not rely on a limit that was never accepted.

Does load management need extra hardware?

Static allocation against a sanctioned limit needs nothing beyond the chargers. Live load balancing against real building consumption needs a site meter that can report to the platform.

See smart charging & load management working

A walkthrough against your own chargers and tariffs, rather than a demo tenant with tidy data.