Route cost analyser
the engagement
client data — not shown
heard
"I am asked to cut transport cost and I cannot tell you what a single delivery costs me."
real problem
Cost sat in carrier invoices, activity in the telematics feed, and nothing joined them. Per-route profitability did not exist as a number anyone could produce.
system built
An invoice-to-telematics matching pipeline, a cost model at drop level including waiting time and failed deliveries, and a route review that ranks the twenty worst routes each month with the driver of the cost named.
what broke
Invoice line items matched routes only 71% of the time at first. The unmatched remainder is reported openly rather than allocated by assumption.
the open rebuild
same architecture · public data
dataset
NYC TLC trip records + public fuel and toll tariffs
what the rebuild covers
Matching pipeline and drop-level cost model. The monthly review view is a notebook only.
artifacts
NotebookCodeDatasetWrite-upDemo