Carriers, service levels and lanes between sites and regions, with transit times and rates, kept as master data the planning and transport systems agree on.
Today lanes are in the transport system, transit times in the planning tool and carrier codes in the ERP, and a new distribution centre needs all three updated by hand.
With Lima the lanes are read where they live, matched on carrier code and from + to + mode + service level, assembled field by field and published as one golden record per real carriers, with every source key underneath. The shipments and invoices on a lane and the carrier's performance are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
Lanes are relationships between golden sites, so a merged or renamed site keeps its lanes.
Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Network | region → site → lanes |
| Carrier | carrier → services → lanes |
A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | transit time is between 0 and 90 days mode is in the code list |
| Row | an active lane names two active sites or regions a lane with a rate has a currency and a basis |
| Business | every planned lane in the planning tool exists here a carrier whose on-time rate falls under 90% for two months opens a review |
| Transactions in the bed | Read from |
|---|---|
| Shipments | transport system, carrier events |
| Freight invoices | AP |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the shipments and invoices on a lane and the carrier's performance.
Transport edits; planners read; rates visible to procurement and finance. The twelve layers apply on every door; see security.
POST /api/v1/golden/lane/lookup
{
"from": "S-0114",
"to": "S-0207",
"mode": "road"
}200 OK
{
"lane": "LN-3391",
"carrier": "L-01120",
"transit_days": 2,
"cut_off": "16:00",
"on_time_90d": 0.94
}The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Carrier read from LFA1 (partner role CR).
Open the SAP S/4HANA page →Carriers read from WSH_CARRIERS (REST: carriers).
Open the Oracle Fusion Cloud page →Carrier read from CONFORMED.CARRIER. 3 objects, the keys in Snowflake fields, the write path and the prerequisites.
Open the Snowflake page →Carrier read from silver.carrier. 3 objects, the keys in Databricks fields, the write path and the prerequisites.
Open the Databricks page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A 3PL governed 4,700 lanes across a transport system and two planning tools. The planning tool's transit times now come from the golden lanes, refreshed from actual shipments each month.
The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.
One working day for the first two sources; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Logistics and 3PL, Consumer goods, Industrial manufacturing, High-tech and semiconductor. The industry pages show the domains each starts with.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.