Orderly Charging

Orderly scheduling of charging load

Definition

Managed Charging (Ordered Charging Load Scheduling) refers to guiding the charging periods and power of electric vehicles through a platform or scheduling strategy, transferring the charging load to off-peak periods of the grid to achieve peak shaving and valley filling, reduce grid pressure, and lower user charging costs (in conjunction with time-of-use electricity prices). Managed charging is an important way for charging stations to coordinate with the grid, preventing transformer and distribution overload caused by large-scale charging load accumulation.

Managed charging strategies include: Time Slot Control (setting charging during off-peak periods), Power Adjustment (dynamically adjusting charging power), and Demand Response (responding to grid dispatch instructions). Optimization needs to consider load forecasting, time-of-use electricity prices, and user charging demands.

Technical Features

Managed charging relies on real-time communication between charging stations and the scheduling platform. Charging stations report real-time power, SOC, and charging plans through IoT SIM cards and receive power adjustment or time-slot control instructions issued by the scheduling platform. Protocols such as OCPP support remote control. Residential managed charging can be implemented with smart charging stations and load aggregators.

Use Cases

Managed charging is widely applied in residential charging stations, public charging stations, V2G, and energy storage scenarios. Charging stations communicate with the scheduling platform via IoT SIM cards to receive load forecasts and peak-valley dispatch instructions. SimtoLink provides a stable network connection and dedicated APN for the managed charging system, ensuring real-time issuance and execution of dispatch instructions.


When a dispatch command can reach the charger

Orderly charging means the charger reports current power, the vehicle's request, and remaining energy, then applies the time window or power cap the platform sends. The IoT SIM carries that loop. It is not the tariff itself. A command takes effect only when the charger is dispatchable: the connector is seated, the vehicle allows its power to be limited, and local protection has not locked the output. Moving the start time into the off-peak period, without the charger reporting actual power, leaves the platform unable to tell whether the load really moved. A time-of-use tariff is only a price signal. Whether the driver accepts a delay also depends on a "latest departure" time in the order. Without that time, dispatch postpones the car until after the driver has already unplugged.

The neighborhood transformer capacity is a hard limit. If many chargers all receive "you may charge" and each still starts at rated power, the total load piles up again in the off-peak period. Dispatch must therefore be issued against site capacity, not against one charger. If a charger does not receive a new command before timeout, it should fall back to a pre-agreed safe power, not hold the previous high power. When the vehicle asks for less power, the charger should report actual output, so the platform sums the meter, not the command value.

Off-peak treated as a guaranteed charge

It is easy to treat the off-peak period as a promise that the battery will fill. A low off-peak price does not mean the transformer still has spare capacity, and it does not mean the vehicle stays plugged in. If the platform only sends "start at midnight" and charger clocks are a few minutes off, a batch of vehicles starts together and creates a new spike. Another mistake is a local floor that outranks the remote power cap: the charger pulls current to the maximum for the driver's experience, yet the receipt still says "executed," and the load curve does not match the command.

The default behavior when the link drops must be written down in advance. If the charger holds full power after the link breaks, orderly charging fails at the moment it is most needed. If it stops charging outright, the driver blames the SIM. A clearer rule is to drop to an agreed low power, keep the start and end locally, and backfill the actual energy after recovery. Acceptance should not stop at the command log. Compare the charger meter: command power, receipt power, and meter power in the same minute must agree before dispatch has actually landed. Unplugging mid-session should end this plan. Do not hand the leftover allowance to the next vehicle without calculating it again.

Meter power is the evidence that a command landed

After a power cap is sent, watch the command value, the charger's receipt, and how the meter moves in the next minute. If the receipt says executed and the meter still sits at full power, a local floor or the vehicle's request has overridden dispatch. The start of the off-peak period should be staggered across chargers, not one clock time for every charger. When the vehicle unplugs, this plan ends. The leftover allowance must not transfer automatically to the next vehicle. An order with no "latest departure" time should not be postponed until after the driver has left.

If the uplink drops, the charger should fall to the pre-agreed low power, record the start and end, and backfill actual energy after recovery. Do not estimate the outage as completed from the command value. Transformer capacity constrains the whole site. One charger showing that it may charge does not mean the whole site may run at full power together. A charger whose clock cannot be set should refuse a new time plan, so a batch of vehicles does not start by mistake during the peak. Orderly charging has actually run only when the meter, the receipt, and the command agree.

Related Terms

Back to the IoT SIM Card Glossary