aesop data practice portal sample build · Caldera Logistics 30 30 / 100 · Critical

Data lineage

Where every number comes from

Four source systems, eight tables, the reports they feed — auto-mapped from Caldera Logistics's warehouse. Not one relationship is enforced; the estate hangs on naming convention. Click below to watch the on-time number split into the two definitions fighting underneath it.

system → table inferred (0 enforced keys) Ops 94.1% Finance 87.7%
Source systems Tables Reports & dashboards TMS Billing / ERP WMS CRM Power BI SharePoint Excel shipments 5,416 rows orders 5,000 rows invoices 4,695 rows shipment_events 10,613 rows exceptions 157 rows carriers 12 rows customers 60 rows facilities 8 rows credit_amount Ops OTD Dashboard 94.1% OTD Finance OTD Pack 87.7% OTD Board OTD Pack computes OTD Carrier Scorecard computes OTD Exec KPI Scorecard computes OTD
On-Time Delivery, traced on the same data — two answers
94.1%
Operations
4,895 / 5,203
6.4
pt gap
87.7%
Finance
4,116 / 4,695
The fork is one field — credit_amount. Ops ignores it; Finance subtracts it. Same data, 6.4 points.