“I need 80% by 07:00.”
The driver states a requirement, not a charging schedule. Everything else—priority, site limits, price and available power—becomes a software decision.
Vampire.Energy is designed to work backwards from the fleet schedule, prioritising readiness without sizing every decision around simultaneous full-power charging.
Vehicle 14
Required energy identified · Charger 03
Vehicle 08
Connected later than planned · Priority raised
Vehicle 21
Lower energy need · Flexible charging window
Illustrative operational view
Schedule drives charging priority
Readiness
Readiness is the metric that matters.
Charger availability alone cannot tell operations which vehicles need energy, how much they need, when they must leave, which charger they can use or whether the site has enough capacity.
01
electric_carVehicle need
Energy required for the next assignment.
02
departure_boardReady time
When that vehicle has to return to service.
03
scheduleCharging window
The time actually available to deliver energy.
04
electrical_servicesSite constraint
Capacity shared with chargers and other loads.
05
low_priorityCharging priority
Allocate available power around operational need.
06
fact_checkReady or exception
Confirm the plan or surface the risk.
Vehicle priority
Not every vehicle has the same priority.
Charging decisions should follow the fleet schedule, not first-come-first-served charger usage.
01Prioritise by departure time and required energy.
02Account for vehicle availability and charger capability.
03Re-evaluate priorities when the operating plan changes.
Illustrative priority queue
Ordered by readiness risk
Vehicle 08 · earliest departure
Connected late with a larger remaining energy need.
Vehicle 14 · active session
Charging progress remains aligned with its route plan.
Vehicle 21 · flexible window
Later departure leaves room to defer charging.
Depot capacity
Use the power you have where it matters most.
The operating plan has to fit inside the site connection, shared charger capacity and other depot loads. When power is limited, the vehicles with the closest operational need should receive it first.
Solar or local generation can contribute where relevant, but readiness and site limits remain the governing constraints.
See how platform energy control works arrow_forwardConnection
Site limit
Other loads
Protected first
Charging
Allocated by need
Departing first
Highest readiness priority
Later departures
Enough window remains
Flexible vehicles
Can move to a later window
Operational exceptions
Manage the exceptions, not every charging session.
Operations needs to know which vehicle is at risk, what changed and where to look next. Routine sessions can stay in the background.
Vehicle connected later than planned
The available charging window is now shorter than expected.
Recalculate priority and check readiness risk.
ReviewCharging did not start
The vehicle is connected, but the expected session is not active.
Surface charger and session context for action.
Action neededAvailable site capacity changed
Other depot load reduced the power available for charging.
Protect near-term departures and adjust later windows.
Plan adjustedCharger, vehicle and session evidence explains the exception; the fleet view keeps attention on the operational consequence.
Explore diagnostics arrow_forwardEnergy cost
Meet the schedule without ignoring energy cost.
Once readiness requirements are known, charging can move within the available operating window in response to tariff periods, electricity price, site load and renewable availability. The required vehicle outcome remains the constraint.
18:00
Vehicle returns
Window opens
20:00
Site busy
Other loads active
22:00
Preferred window
Charging prioritised
00:00
Available capacity
Continue delivery
04:00
Verify plan
Check readiness
06:30
Departure
Required outcome
Infrastructure context
Charging decisions need context from the operating plan and the infrastructure underneath it.
Readiness depends on more than a schedule. Charger capability and behaviour, session status, available energy and the vehicle plan all affect whether operations can rely on the outcome.
See the underlying platform architecture arrow_forwardCharger context
Capability and current behaviour.
Session status
What charging is actually doing.
Energy constraint
Power available at the site.
Operating schedule
When vehicles return to work.
From charging cost to mobility control
The business case improves in stages.
The first objective is not flexibility revenue. It is to protect vehicle availability, then measure whether control changes peak demand, energy cost or infrastructure requirements.
01 / Observe
Measure the operating pattern.
Connect vehicle need, return time, charger state, site capacity and actual energy cost.
02 / Optimise · near term
Protect readiness at practical cost.
Prioritise the vehicles that matter, move flexible charging and expose exceptions before departure.
03 / Measure
Prove the business case.
Compare readiness, peak demand, energy cost and infrastructure requirement before and after control.
A practical starting point
Start with one depot or fleet group, establish the baseline and agree what the controlled phase needs to demonstrate.
Test controlled charging against a real fleet operating pattern.
Start with a real operating pattern and measure what changes when charging follows readiness instead of plug-in order.
See how deployments are commercially scoped arrow_forward