Prototype · live iGal trip data · · Autonex Pte Ltd
How to use this page (click to hide)
What this is
A working prototype built on real iGal trip-sheet data (27 Sep – 28 Oct 2026). For every crew on every day it compares the
manual sequence (coordinator's Job_Seq) with an AI-optimised sequence of the same jobs, same crew. Nothing in iGal has been changed.
How to explore
Pick a day from the drop-down, then a crew (the number shows jobs that day). Good start: 16 Oct · MH.
Compare the two cards – Manual Trip Sheet vs AI-Optimised Trip Sheet: distance, drive time, yard trips and customer time windows met.
Choose the AI plan (orange buttons): Each crew keeps own jobs only re-orders each crew's trip sheet; Move jobs between crews also hands jobs to another in-house crew of the same vehicle type when that saves driving or gets customers served on time (available on days with 2+ such crews). Jobs taken over are tagged "from MH", and an orange line shows the whole day across crews.
Read the map: dashed grey = manual route,
blue = optimised route, Y = Galmon Yard.
Numbers are the optimised stop order (delivery, collection).
"8·9" means two stops at the same site. Tap a marker for site, ETA and time window.
Scroll to the trip sheet – switch between AI-Optimised Trip Sheet and Manual Trip Sheet. Each stop with a time window shows on time or minutes late. Flags such as JI PASS, PSA PASS, EPTW, CLEARANCE and PRE-CALL are picked up from Remarks automatically.
How to read the figures
Crew-day
One crew's route on one day. "Crew-days compared" = number of real routes tested (excludes days with 1 job or incomplete Job_Seq).
Distance / drive time
Estimated from map distance adjusted for roads and time-of-day traffic. Manual and optimised use the same model, so the comparison is fair. Lines on the map are straight connectors, not actual roads.
Yard trips
Returns to Galmon Yard to load deliveries / unload collections.
Time windows met
Jobs with a time requirement in Remarks/timings (e.g. "MUST B4 10AM", "(2PM-4PM)-OK") reached in time. Even 1 minute late counts as missed – check the minutes-late tag on each stop for near-misses.
Working assumptions – please challenge
Truck load per trip: up to 4 battery or 6 diesel machines (mixed loads pro-rata).
30 min on site per job (10 min for each extra machine at the same site); 20 min per yard stop; day starts 07:00 at Galmon Yard.
Each crew keeps its own jobs – only the order changes. Moving jobs between crews is the next step and should add further savings.
Why postal codes matter
The optimiser is only as accurate as the addresses it receives. Today the Del_ZipCode field in iGal is empty on every trip.
Locations had to be worked out from free-text site names: about half contained a postal code; the rest needed guessing from building or road names,
and roughly 1 in 7 sites could not be located at all on the first pass. Each wrong or missing location distorts the route, the ETA and the savings figure.
Addressed sites: enter the 6-digit postal code in Del_ZipCode when creating the DC – about 2 seconds per job.
Unaddressed sites (construction, events, port gates): paste a Google Maps pin (e.g. 1.3521, 103.7458) in Site_Location with a short description.
Recurring locations (PSA gates, airport terminals, F1 zones): agree one standard name and postal code / pin for each.
With correct postal codes every stop is placed exactly, routes and ETAs become reliable, and the same data gives drivers one-tap navigation.
Not yet in this prototype
Moving jobs between crews · real road routing · daily automatic run · write-back of the approved sequence to iGal (by design, only after sign-off).