The hard deadline for a Jakarta ride-hailing fleet is every vehicle charged and available by 07:00. Morning demand peaks then, so an unavailable vehicle is a missed opportunity that cannot be recovered. Daily range and charging cost are secondary constraints.
Why 07:00 Sets the Structure for Everything Else
Jakarta's commute pattern concentrates demand from roughly 07:00 to 09:30, more sharply than in most other Southeast Asian cities. Office commutes, school runs, and transit connection trips drive a steep ride-hailing spike at 07:00 that remains high for about two hours before easing.
For a small EV fleet, a vehicle unavailable at 07:00 misses the day's most valuable period. One finishing charge at 08:30 has missed the peak and enters service as demand begins to fall. For fleets of 10 to 20 vehicles, two missing vehicles during the morning peak can materially affect daily revenue.
The 07:00 deadline also connects to PLN tariffs. Off-peak rates run from roughly 22:00 into the morning, making that the preferred charging window. The challenge is completing off-peak charging early enough for vehicles to reach target SOC and the ready zone before 07:00, rather than remaining plugged in when first-trip requests arrive.
How We Build the Overnight Schedule Around the Deadline
RideBlitz treats 07:00 readiness as fixed and plans backward from it. For every vehicle, we calculate the factors that set charging time: SOC when it returns to the depot after its last trip, the target SOC for the morning schedule, the charging rate at its assigned port, and any planned maintenance that keeps it out of service.
Using those inputs, the model finds the latest charge start that can reach target SOC with a buffer before 07:00. The buffer covers travel from the charger to the ready zone, plus connection and vehicle-readiness checks. We use a 30-minute buffer, so sessions target completion by 06:30.
The schedule places sessions within the off-peak window, favoring start times that limit PLN peak-tariff exposure while meeting the 06:30 completion target. A vehicle returning at 23:00 with 30 percent SOC and a 22 kW charger can start at 01:00 and finish comfortably. One returning at 22:30 with 15 percent SOC and a 7 kW charger has less room, possibly requiring an earlier start or a lower completion target SOC.
Port Contention: The Constraint Within the Constraint
A fleet of 12 vehicles with 4 charging ports cannot charge all 12 at once. That resource limit makes scheduling difficult. Simply queuing vehicles by arrival creates a first-in-first-out order that largely ignores which vehicles most urgently need charging for the next morning. A vehicle returning at 22:00 with 80 percent SOC may take priority over one returning at 02:00 with 20 percent SOC, despite the opposite being more appropriate for morning readiness.
We assign ports using three factors: urgency, meaning how much charging each vehicle needs to reach target SOC, the port's availability window based on existing bookings, and the vehicle's morning schedule. A vehicle assigned to a long-distance airport job may need 90 percent SOC, while another may need only 60 percent for its planned route.
This can create counterintuitive schedules. A vehicle at 70 percent SOC with a 50 km morning run may charge before one at 50 percent SOC assigned only short trips. The first vehicle needs earlier charging because of its trip, despite starting with more SOC.
What Happens When the Evening Schedule Runs Late
Fleets do not return exactly on schedule each night. A vehicle expected at 23:00 may arrive at 01:30 after a delayed passenger or traffic detour. A charger due to open at 00:00 may also remain occupied because the driver did not move the vehicle after charging ended.
The schedule must respond to these changes in real time instead of becoming outdated after the first deviation. RideBlitz rechecks the schedule when vehicles arrive. If one arrives late, the system recalculates whether it can still meet the 06:30 target. If not, it alerts the dispatcher to a possible morning availability miss, leaving time to change the morning assignment.
This is not a perfect solution. A vehicle arriving at 03:00 with very low SOC cannot meet the 07:00 target if no ports are free at that time, regardless of optimization. An early warning is still far better than discovering the problem at 06:45 while the morning dispatcher is building the day's queue.
The Cost of Getting It Wrong
A fleet that regularly misses 07:00 readiness loses revenue during a concentrated daily window. Early-access pilot data shows that the morning peak contributes a disproportionate share of daily trip revenue because demand per unit time and trip acceptance rates are highest then. For a small fleet, missing two vehicles at the 07:00 peak four days per week creates a meaningful gap between potential and actual weekly revenue.
Charging cost matters, but it comes second. Saving on off-peak rates while missing morning readiness addresses the smaller issue at the expense of the larger one. We made morning readiness the primary scheduling constraint, with tariff optimization as a secondary goal applied only after readiness is secured. Fleet operators weighing these tradeoffs should use the same priority.
