A bank of chargers can draw more than the service behind it was sized for, and the building's own load moves through the day. OCPP has carried Smart Charging since 1.6, with charging profiles that limit the current or power a station offers a vehicle. Someone still has to decide the split.
Charge Balancing reads each station's status, transactions, and meter values from your OCPP management system, the service-entrance meter over Modbus TCP, and the building's major loads from the building platform. It works out the headroom left under the capacity you set and proposes a current limit per charger: a charging profile in OCPP, an installation current in Zaptec, or a shedLoad call in ChargePoint. Approving it applies the limits; a receipt keeps the meter reading and the split.
This is a reference listing. It documents what Fibric would read from Charge Balancing and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Inputs
StatusNotification, StartTransaction, StopTransaction, and MeterValues in OCPP 1.6, or TransactionEvent and connector status in 2.0.1
Charger load from the management system: stationLoad and group sgLoad in ChargePoint, or charger state and availableCurrent in Zaptec
Service-entrance kW, current per phase, and kWh over Modbus TCP, on the polling schedule you define
Major building loads and their run state from the building platform, so headroom accounts for chillers and kitchens
The service capacity, the per-phase limits, and the minimum current each charger needs to keep a session alive
Sessions in progress, with energy delivered so far, so a vehicle near full is not the one held back
Proposed actions
Target capability: propose a charging profile under OCPP Smart Charging that limits the current or power a station offers
Target capability: propose a new availableCurrent or per-phase currents on a Zaptec installation
Target capability: propose a shedLoad by allowedLoadPerStation for a ChargePoint station group, and clearShedState when headroom returns
Target capability: propose which sessions keep full current when headroom is short, from energy delivered and time plugged in
Target capability: propose a ChangeAvailability for a station whose meter values show it drawing outside its profile
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Keep a parking deck under its feeder rating
Read station status and MeterValues over OCPP and the feeder meter over Modbus TCP, and get a proposed current split whenever the sum nears the rating. Approve it and the profiles go to the stations.
When the building platform shows the kitchen and chillers stepping up, the operator proposes shedLoad on the ChargePoint group for that hour and clearShedState after.
Per-phase currents from the site meter feed a proposed per-phase availableCurrent on the installation, paced to Zaptec's guidance and shown with the meter reading that called for it.
An OCPP management system connector, or a ChargePoint or Zaptec connector, for the stations you want balanced
A Modbus TCP connector polling the service-entrance meter, with per-phase current available
The service capacity and any per-phase or feeder limits, written down and agreed with the electrician of record
Stations that implement the profile or current command: an OCPP station may leave out SetChargingProfile
Authentication
Acts through your OCPP, ChargePoint, or Zaptec connector's own credentials, reads meters through the Modbus connector's register allow-list, and reads the building platform read-only; every limit is an approved proposal.
Limits
Zaptec recommends changing installation current no more than once every 15 minutes, and the operator paces its proposals to that.
Stations implement subsets of OCPP. One may answer a profile with NotSupported, and it then stays at full draw.
It balances against the meter it can read. Loads on a feeder without a meter are estimated from the building platform, not measured.
It proposes limits. It does not stop a session, release a connector, or bill anyone.
Access and pricing
Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
Each proposed split: the meter reading, the headroom, and the limit per charger. You can approve a standing rule for routine splits within the capacity you set, and the operator then proposes only the exceptions: a station ignoring its profile, or headroom gone.
What record is left for each limit?
A receipt per change: the meter reading and sessions at the time, the limit sent to each station, the station's response, who approved it, and the command that restores full current. Stations that answered NotSupported are named.
Does it ever cut a driver off?
It never does. It lowers the current a station offers, down to the minimum you set per charger, and never sends a stop, a connector release, or a reset on its own. Ending a session needs a separate approval.
Ask about Charge Balancing
Ask about the capabilities and requirements in this listing.
This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy