UAF Traffic Console

\n

\n Solves · manual handover · unrecorded night jobs · no job ID\n

Job Inbox

\n

Every job enters here and gets a standard ID. Customer Service keys it once at source — the Traffic Planner never retypes it. Night jobs get the same treatment instead of going unrecorded.

\n

\n \n

\n\n

\n

Awaiting planning7Wave 1 · by 11:00

\n

Entered by CS3No planner retyping

\n

Night jobs2Previously unrecorded

\n

Linked to MAWB7Joins back to FreightMaster

\n

\n\n \n\n

\n \n \n \n

Job ID	Source	Customer	Address	Type	Pcs	Kg	Window	Handling	Status

\n

\n\n

\n

Why this screen matters

\n

Today CS uploads to OneDrive, Power Automate emails the planner, and the planner retypes the job into Excel. The same data entered twice, and anything arriving after 17:00 is planned by Export staff with no capacity to record it. One entry point with one job ID removes the double handling and closes the night gap.

\n

\n Solves · no trip entity · time windows buried in remarks · unknown capacity\n

Trip TRP-26-0812-05 — West run

\n

The 16-stop Tuas and Jurong run from 12 August as a real trip. Today it exists only as sixteen adjacent spreadsheet rows separated by a blank line.

\n

\n \n \n

\n

\n\n

\n

Stops162 cancelled

\n

Load1,918kg of 3,500

\n

Time windows3Hard constraints

\n

Planned distance98kmQuadrant order

\n

\n\n

\n \n \n \n

Seq	Customer	Address	Type	Pcs	Kg	Window	Note

\n

\n\n \n \n

\n

\n Solves · first in, last out · cargohand guesswork at the tailgate\n

Load Plan — YR2880Y

\n

Once the stop order is fixed, the loading order follows from it. Last stop loads first and deepest; first stop sits at the tailgate. The cargohand gets one sheet instead of a mental model.

\n

\n \n

\n\n

\n

Vehicle profile

\n

Entered once per truck and saved. Applies to outsourced vehicles too.

\n

Bed length (m)

\n

Bed width (m)

\n

Bed height (m)

\n

Max payload (kg)

\n

Pallet footprint

\n

Max stack height (m)

\n

Pallet positions on floor10

\n

With stacking20

\n

Tiers that fit1

\n

\n\n

\n

Truck bed — load in this order

\n

Front of bed is against the cab. Load front-first, unload tailgate-first.

\n

\n Loaded first — deepest\n Middle bay\n Loaded last — at the door\n

\n

\n\n

\n \n \n \n

Load	Bay	Customer	Address	Pcs	Kg	Drops at stop

\n

\n\n

\n

What this is and is not

\n

This is sequence-aware bay allocation — reverse stop order across three bays. It gets most of the practical benefit for a cargohand with a trolley.

\n

It is not true 3D bin packing. Optimising the stacking of irregular cargo by volume and weight distribution is an NP-hard problem with dedicated commercial software, and it sits in Phase 3 of the proposal rather than this capstone.

\n

\n Solves · no live status · Ops phoning drivers for updates\n

Driver App

\n

What Yeo and Kumar see in the cab. Tap Start, Arrived, Complete on the live stop. Works offline and syncs when signal returns — Tuas and Loyang have dead spots.

\n

\n\n

\n

08:42YR2880Y

\n

Today · 14 stops

\n

Yeo Poh Huat & Kumar · West run

\n

Every tap writes a timestamp. Truck utilisation, real service durations and driver and cargohand OT hours all come from these three taps — none of which exist today.

\n

\n\n

\n

Report exception

\n

Replaces \"CANCELLED\" and \"CANCEL BY MUNIRAH\" typed into a remarks column.

\n

Reason\n

\n

Note

\n \n

\n

Recorded byDriver, on stop

\n

TimestampServer-side on receipt

\n

Ops notifiedImmediately

\n

Customer notifiedIf cancelled

\n

\n\n

\n

Offline queue

\n

Photos and PODs captured without signal are held in the phone's own storage and uploaded automatically when the connection returns. Purged 24 hours after successful upload.

\n

Queued items0

\n

Storage used0 KB

\n

Last sync—

\n

\n \n \n

\n

\n Solves · hardcopy POD · driver returns paper to office · Import scans and emails\n

ePOD Capture

\n

Signature, photo of the DO, piece count and an automatic timestamp — captured at the door. Try signing in the box. A single dot will not be accepted.

\n

\n\n

\n

Stop 7 of 14UAF-26-0812-0131

\n

TVS SCS

\n

93 Tuas Bay Drive · Collection

\n

Pieces received — despatched as 2

\n

Carton

\n

Bag

\n

Pallet

\n

\n \n

\n

Customer signature

\n

\n \n \n \n

\n

\n\n

\n

Captured automatically

\n

Job IDUAF-26-0812-0131

\n

MAWB618-52056583

\n

Completed at—

\n

Location stampNot captured

\n

Accuracy—

\n

DriverYeo Poh Huat

\n

CargohandKumar

\n

TruckYR2880Y

\n

SignatureNot captured

\n

DO photoNot captured

\n

Sent to customerPending

\n

Capture rules

\n

The photo is taken inside the app, never through the phone's camera app — otherwise the customer's signed delivery order lands in the driver's personal gallery and syncs to their private cloud.

\n

Documents are downscaled to 2400 px on the long edge in greyscale for OCR legibility; general photos to 1600 px in colour. The location stamp is a single reading at signature, not continuous tracking.

\n

\n Solves · control tower blind between despatch and return\n

Live Map — Control Tower

\n

Each truck has its own colour, carried through to its route line and its stop markers. Outsourced vehicles share one grey colour because UAF does not control them.

\n

\n \n \n

\n

\n\n

\n

Vehicles

\n

Selected

\n

Click any stop or truck on the map.

\n

Attention

\n

\n Schematic view — stops and routes are plotted from real coordinates, but the island outline is\n stylised and there is no basemap. Nothing here loads from the internet, so it renders the same on a\n locked-down laptop, behind a VPN, or offline. A OneMap basemap is an enhancement for production, not\n a dependency for the demo. Vehicle positions are last known, not a live feed.\n

\n

\n\n

\n

What \"live\" honestly means

\n

A web app cannot track a phone in the background. The moment a driver locks the screen or opens WhatsApp, position updates stop. So the map shows the last known position and how long ago it was reported, never a fake moving dot.

\n

Option 2, named in the proposal as the upgrade: a telematics unit in each truck at roughly $150 plus subscription. Always on, independent of the driver's phone, and it tracks the vehicle rather than the person — which is also the better privacy position.

\n

\n Solves · customers phoning Ops, Ops phoning drivers\n

Customer Tracking Link

\n

What the customer sees from a tokenised link with no login. The link expires once the job closes.

\n

\n \n

\n\n

\n

Union Air Freight618-52056583

\n

Out for delivery

\n

4 stops away

\n

\n\n

\n

Privacy by design

\n

Login requiredNo — tokenised link

\n

Link lifetimeExpires on completion

\n

Driver name shownNever

\n

Driver phone shownNever

\n

Other customers visibleNever

\n

Map visibleOnly when next

\n

Before thatStop count only

\n

Why the map stays hidden until they are next

\n

Showing a live vehicle position to every customer all day exposes the driver's whole route and working pattern to people outside the company. Stop count answers the real question — \"roughly when?\" — without that. The map appears only for the customer actually being served next, which is the same pattern the consumer couriers use.

\n

\n Solves · no operational data · no OT evidence · unknown utilisation\n

Operations — Wed 12 Aug 2026

\n

Figures derive from the board and the driver taps. Assign a job on the Planning Board and the counts here move.

\n

\n\n

\n

Truck utilisation — stops per truck

\n

\n Completed\n In progress\n Idle capacity\n

\n

\n\n

\n

Driver & cargohand hours

\n

From job timestamps. Today \"YEO/KUMAR\" is one string — nobody's individual hours can be calculated.

\n

\n \n \n

Person	Role	Truck	Stops	Hours	OT

\n

\n\n

\n

Internal vs outsourced — 2026 to date

\n

Outsourced volume: 259 jobs in January to 419 in July, up 62%. None of those jobs currently carry a driver, time, status or POD.

\n

\n\n

\n

Missing POD

\n

Ages automatically. Every one is an outsourced job — the DO never came back.

\n

\n \n \n \n \n \n \n \n \n

Job	Vendor	Consignee	Age	Status
UAF-26-0812-0203	AKS	NINJA · NJV	6h	Chasing
UAF-26-0812-0207	AKS	ECMS · J&T	6h	Chasing
UAF-26-0811-0188	AKS	NINJA · Shopee	1d	Overdue
UAF-26-0811-0191	VTQ	Redwood · Sungei Kadut	1d	Overdue
UAF-26-0808-0142	AKS	NINJA · AMK	4d	Escalate

\n

\n Solves · trucks assigned while in the workshop · planned distance mistaken for actual\n

Fleet

\n

A truck taken off the road disappears from the Planning Board immediately. Distance comes from the odometer, not from the route the planner drew.

\n

\n\n

\n \n \n \n

Truck	Type	Payload	Status	Odo start	Odo end	Actual km	Planned km	Variance	Action

\n

\n\n

\n

Why odometer, not GPS

\n

GPS-derived distance over-reads badly — position jitter while a truck sits at a loading bay adds phantom kilometres all day. Two odometer readings are simpler, more accurate, and match what fuel and servicing are billed against. GPS breadcrumbs are still useful for the shape of the route, which is what the Live Map draws.

\n

The variance column is a KPI in its own right: a consistently large gap between planned and actual means either the plan is unrealistic or the route is not being followed. Both are worth knowing.

\n

\n Solves · \"sometimes multiple mawb to the same delivery location are combined??\"\n

Vendor Billing Check

\n

Rate cards currently live as free text in a spreadsheet Notes tab. Held as data, the system prices every outsourced job and flags what does not match the invoice.

\n

\n \n

\n\n

\n

Jobs invoiced190August to date

\n

Flagged4Needs Finance review

\n

Consolidation risk63MAWBs on multiple rows, 2026

\n

Vendor concentration80%AKS share of outsourced

\n

\n\n

\n \n \n \n \n \n \n \n \n \n \n \n \n \n

Date	MAWB	Consignee	Vendor	Basis	Expected	Invoiced	Check
13 Aug	618-52059184	Vinum · Jalan Kilang Timor	Element	3 plts $160 + 45 x $25	$1,285	$1,285	Match
13 Aug	618-52059184	Vinum · same address	Element	Billed as separate trip	$0	$160	Same MAWB, same drop
13 Aug	618-52059184	Vinum · same address	Element	Billed as separate trip	$0	$160	Same MAWB, same drop
13 Aug	618-52059184	SWV · Fishery Port	Element	Additional pickup $80	$80	$80	Match
13 Aug	160-12524842	Premium Global · Clementi Loop	Element	First 3 plts	$160	$160	Match
12 Aug	618-54817873	Zuellig · Changi North Way	Shinyuu	14' $200 + clearance	$380	$380	Match
12 Aug	074-47037163	Woodlands Sunny · Senoko	Shinyuu	14' $200	$200	$280	24' rate on 40 kg
11 Aug	176-62560433	Zuellig · Changi North Way	Shinyuu	14' $200	$200	$200	Match
12 Aug	018-92819031	Ben Line · Jurong Port Rd	Hiap Lian	No rate card on file	—	$340	Unrated vendor

\n

\n\n

\n

The one feature with a hard dollar return

\n

MAWB 618-52059184 appears on four rows for 13 August — three to the same consignee at the same address. In 2026 to date, 63 of 242 reefer MAWBs appear on more than one row, one spanning thirteen. Nobody currently knows whether vendors bill those as one trip or as many. This screen answers that every month, automatically.

\n

\n Solves · management has no visibility · no evidence for the make-or-buy decision\n

Reports

\n

Scheduled by default — a weekly operations pack every Monday 07:00 and a monthly management pack on the 1st, both emailed as Excel and PDF. The buttons are for when someone wants it now.

\n

\n\n

\n

The decision this system exists to inform

\n

Outsourced volume grew 62% in six months. The question the board is actually facing is whether to buy a seventh truck or keep paying vendors — and today there is no figure that answers it, because internal jobs carry no cost and outsourced jobs carry no operational record.

\n

\n \n \n \n \n \n \n \n \n

Lane	Jobs Aug	Internal cost/job	Vendor rate/job	Gap	Read
West — Tuas / Jurong	148	$168	$245	-$77	Keep internal
East — Changi / Loyang	96	$142	$190	-$48	Keep internal
North — Woodlands / AMK	71	$203	$188	+$15	Outsource
Central — Pandan / PP	114	$155	$205	-$50	Keep internal
Reefer — all quadrants	66	$312	$268	+$44	Outsource — one reefer truck only

\n

Illustrative figures. Real values need truck capacities, fuel, and the driver hours this system will start capturing — which is exactly the point.

\n

\n\n

\n

Solving the sponsor's five goals first

\n

Every report here traces to one of the five goals in the briefing deck: office productivity, operational data capture, live job and ePOD status, customer status updates, and driver and cargohand tagging. Anything beyond those five is deliberately marked as later.

\n

' + r[0] + '

Job Inbox

New transport job

Why this screen matters

Planning Board — Wed 12 Aug 2026

The quadrant method, kept — and Clarke-Wright behind it

Trip TRP-26-0812-05 — West run

Optimised against the quadrant baseline

Interleaving — the real backhaul gain

Load Plan — YR2880Y

Vehicle profile

Truck bed — load in this order

What this is and is not

Driver App

Report exception

Offline queue

ePOD Capture

Captured automatically

Capture rules

Live Map — Control Tower

Vehicles

Selected

Attention

What \"live\" honestly means

Customer Tracking Link

Privacy by design

Why the map stays hidden until they are next

Operations — Wed 12 Aug 2026

Truck utilisation — stops per truck

Driver & cargohand hours

Internal vs outsourced — 2026 to date

Missing POD

Fleet

Why odometer, not GPS

Vendor Billing Check

The one feature with a hard dollar return

Reports

The decision this system exists to inform

Solving the sponsor's five goals first

History · main.tsx