Design decision
Dynamic load management constrains charging using a measurement boundary, available site capacity and a priority rule. A local controller can react to other building loads; a cloud scheduler alone cannot be assumed to protect a feeder during loss of connectivity. Define the control interval, communication timeout, measurement direction and conservative fallback current, then test loss of the meter, controller and network separately.
When this approach fits · Limits and alternatives
Useful where vehicles remain parked long enough to shift energy delivery, this approach may not meet every urgent departure when the connection is saturated. Allocate minimum energy and departure priorities, and show what happens when demand exceeds capacity. An electrical protection design is still required: software scheduling does not replace overload or fault protection. Request logged limit-compliance tests and a recovery sequence after outages.
Procurement checks
- Confirm metering integration and the site import power limit
- Document failure behavior if the meter or communications go offline
- Agree response time, priority rules and commissioning tests
Evidence to request
Define the installation country, supply, arrival and departure times, energy per session and operating constraints. Ask for an electrical design, exact configuration, test evidence and acceptance plan. Include support responsibilities and data ownership in the written scope.