Domain catalogue Supply chain

Carriers and transport lanes

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.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSnowflakelakehouseDatabrickslakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN CARRIERS AND TRANSPORT LANESCarriers and transport lanesone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the carriers and transport lanes record comes from, how it is assembled, and who reads it. Other systems have their own page.
3 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
2
match keys
catalogue
2
hierarchies the record sits in
catalogue
2
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

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.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Carrierlegal entity (golden supplier), SCAC or code, services, contacts
wins: transport system
Lanefrom site or region, to site or region, mode, service level, valid dates
wins: transport and planning
Times and ratestransit time, cut-off, rate basis, currency
wins: transport contracts
Performanceon-time rate, damage rate, used in rules
wins: derived from shipments
How records match

The keys, in order

carrier codefrom + to + mode + service level

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.

Where it sits

2 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Networkregion → site → lanes
Carriercarrier → 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.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columntransit time is between 0 and 90 days
mode is in the code list
Rowan active lane names two active sites or regions
a lane with a rate has a currency and a basis
Businessevery planned lane in the planning tool exists here
a carrier whose on-time rate falls under 90% for two months opens a review
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Shipmentstransport system, carrier events
Freight invoicesAP
on-time by lanecost per shipmentlanes with no carriertransit time vs actual

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.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Transport edits; planners read; rates visible to procurement and finance. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/lane/lookup
{
  "from": "S-0114",
  "to": "S-0207",
  "mode": "road"
}
response
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.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

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.

illustrative scenario · Carriers and transport lanes
Terms on this page

LaneA route between two points with a mode and a service level.
SCACA standard code identifying a carrier.
Cut-offThe latest time an order can be received to ship the same day.
Golden recordThe one record for a real carriers, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

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.

How long to the first golden view?

One working day for the first two sources; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Logistics and 3PL, Consumer goods, Industrial manufacturing, High-tech and semiconductor. The industry pages show the domains each starts with.

See your first domain built on your data

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.