VEHICLES. QUEUES. ENERGY.
Plan a better charging stop.
Explore how arrivals, charger capacity and queue priorities shape a hub’s demand.
Study & arrivals
Choose the study period and where truck arrival times come from.
Random Poisson arrivals. A seed repeats the same sample; it does not make the sample representative of real operations.
No file selected.
Or paste truck CSV
Upload one directional count-day. Road traffic is converted using your assumed electric share, charging need and hub choice. This is not a live DfT feed.
No traffic file selected.
Or paste road-traffic CSV
Vehicle & charging
Choose a mixed fleet below, or turn it off to use common vehicle values. Explicit scenario overrides take precedence over CSV / class values.
Mixed fleet for the main scenarios
CSV imports bypass this generator. The target SOC below applies to all generated classes.
Time occupying the bay
A truck can finish charging before its driver is ready. The minimum bay time is a firm break from connection. Extra post-charge time can model optional idle occupancy; configure the yield rule per scenario. These are study assumptions, not a driver-hours compliance check.
Priority & journey assumptions
These control experimental urgency ranking and next-hub reachability checks.
Advanced · repeated runs & export intervals
Truck CSV imports use one replication. Synthetic replications use independent seeds, paired across scenarios.
HUB OPERATIONS · ROAD → QUEUE → ENERGY
Your charging hub, at network scale.
Run the main comparison, or load an approach scenario, to activate the operations view.
Operations view guide & assumptions
Diagram only: no geographic map or measured road positions. Grid values represent the supplied load model, not a power-flow solution.
Vehicle journey & forecast
Arrival, charging start, energy completion and bay release at the selected model time.
Supply, load & headroom
Grid-side demand, battery-side charging and the site supply limit.
Solid line: computed demand up to this time. Dashed line: scenario forecast. Other scenarios appear as faint comparison traces. These are load calculations; voltage, faults and network constraints need the grid team's power-flow model.
Approach & dispatch board
Vehicles waiting, charging or approaching within the forecast window. Times beyond the study cutoff can be unknown.
Next operational events
Known scenario / observation forecasts, not charger bookings.
Scenario comparison at this moment
Switch scenario without losing the selected time. Every scenario uses the same base arrivals; its own vehicle, priority and occupancy rules still apply.
Who charges next—and can they use another hub?
Assess a recorded moment using the selected queue policy and supplied hub snapshots.
Advanced · edit alternative-hub snapshots
Run a comparison, then assess a time. No assessment has been made.
Next charger priority
Rank is a dispatch decision at this moment, not a promise of an immediately free bay.
Upcoming arrivals
Supplied/generated arrivals, not live vehicle ETA predictions.
Stay or travel to another hub?
Compare travel + forecast wait + charging back to the same SOC target. A positive energy margin preserves the configured arrival reserve.
Approaching trucks & live observations
Road distance → arrival battery → ETA → queue forecast.
Load a demo or supply truck and hub observations. This workspace runs independently of the comparison tabs.
Import trucks CSV or observation JSON
Truck routes & hub snapshots (JSON)
Road approach view
Schematic road progress, not a geographic map. Simulated / estimated distance is measured along the supplied route.
Arrival and charging forecast
Queue by hub
Charging order follows each hub’s queue policy at dispatch time. Approaching trucks do not reserve bays. Current queue membership in live mode is extrapolated from the supplied snapshot.
Alternative hubs from the truck’s position
Requires a separate road route to each hub. Each diversion is evaluated independently; no trucks are automatically transferred.
Transfer uses physically reachable trucks needing charge, including below-reserve arrivals. Review warnings first. Only simulation mode can transfer; existing comparison settings stay editable.
Compare the outcomes
Run a comparison first.
Mean and p95 wait include only trucks that started charging. Read them alongside the remaining queue. Bay utilisation includes post-charge occupancy; active-charging utilisation does not.
Waiting-time distribution · trucks that started charging
Per-truck results · times, energy, SOC and bay release
Repeated-run variability
Independent seeds across replications; paired samples across scenarios. Standard deviation requires at least two valid replications. Detailed plots show replication 1.