EXPERIMENT 01

Journeys, energy
& decisions.

Observe how vehicle agents move through a shared charging network.

SYNTHETIC RESEARCH SCENARIO

↻ Every setting in this panel changes study inputs and clears results until you press Run experiment. Replay speed, map view and selections never change computed results.

01 Driving & restPolicy basisStudy duration hoursUp to 96 hours (four days). Long studies retain one-minute demand/history with five-minute map snapshots.Cohorts are new vehicles and drivers each day (independent arrivals). A single truck with a long multi-stop route instead carries its own battery and driving history across days.Driving interval before break minStandard case: 270 minutes driving / 45-minute break; 540-minute daily driving limit and 660-minute regular daily rest. Split breaks, extensions and reduced rests are outside this model. Policy reference ↗ (checked 28 Oct 2026)Driver break duration minUse separate rest parkingA truck holds its bay during an unfinished driver break unless an authorised mover and a free rest-parking space are available.Authorised staff can relocate trucksExplicit study assumption: a separate operator moves a charged truck while its driver continues resting. Default off.

02 Battery & chargingCharging trigger SOC %Charge decisions also consider energy needed for the onward journey.Target battery level SOC %Arrival energy reserve SOC %Charging curveVehicle power = DC acceptance × charging-power factor × curve(SOC). Taper: 100% to 60% SOC, 70% at 80%, 40% at 90%, 15% at 100%. It is an illustrative shape, not a measured curve; a truck can supply its own curve (SOC:fraction pairs) in its editor or CSV.Each truck retains its supplied battery capacity, state of health and charging-power factor. Age is recorded; no uncalibrated ageing law is inferred.

03 Dispatch & diversionQueue policyWaiting-age override minRanking: (1) trucks that cannot reach the next hub with the reserve; (2) within each class, trucks that have already queued ≥ this time, in queue-entry order; (3) others by lowest SOC; (4) FIFO, then input order. “Waiting age” is minutes since joining this queue, not battery age. Charging is never interrupted.Allow feasible hub diversionMinimum predicted saving to divert minChecked every 5 minutes while all bays are occupied. An alternative must keep the arrival reserve, need no break first, link onward and save at least this time. Max two diversions per journey; no revisiting a diversion hub.

04 Shared chargingAllow cars / other vehicles on spare baysOnly hubs with “shared bays” > 0 and a compatible connector admit them. A car starts only when no HGV is waiting and the guard below stays free; it is never interrupted and leaves on completion.HGV guard free baysCar maximum wait minCar arrivals come from the study input or the arrival generator. Booking, payment and charger rental are future integrations.

05 Scenario comparisonRun paired comparison casesSame fleet, routes and drivers in every case; only the listed change differs. The map always replays Current settings.Each extra case adds a full run. Arrival-level and future-year cases: generate a fleet below, run, export, then change and rerun.

Study inputs & reproducibility

Import a study or full exported report. Data is processed in this browser.

Import JSONNetwork & fleet JSON

Rule-based vehicle agents · Python computation
Simulated trucks are not live vehicles

GREAT BRITAIN / STUDY NETWORK

The charging corridor

NETWORK READY

Run the experiment to follow journeys
and inspect the decisions behind each stop.

DrivingQueueChargingRest / held bayBlockedDiversionObserved (imported)Hub ring: bay use · bar: grid load

SIMULATION CLOCK08:00t = 0 minCOMPUTED REPLAY · 1 MIN STATES

1× = 1 simulated minute per real second (60× faster than real time) · 12× = 12 simulated minutes per second · speed follows elapsed wall time, so a slow frame skips ahead rather than slowing the clock · Wheel or +/− to zoom · Drag to pan · Click a truck to follow, or a hub to inspect

Study start 08:008 hour study

Physical states, traceable decisions.Run an experiment to compute outcomes.

Decision record

Vehicle movements, charging decisions and driver-rest events appear here after computation.