One record per physical site: plant, distribution centre, office, store or lab, with its codes in every system and its calendar, address and roles.
Today a plant is a four-character code in SAP, an inventory organisation in Oracle, a location in Workday and a site in ServiceNow, and a new site is created four times.
With Lima the sites are read where they live, matched on geocode and address (standardised) and site name and country (fuzzy), assembled field by field and published as one golden record per real plant, with every source key underneath. Stock, orders, production and headcount at the site, and every system's code for it 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.
Two site records with the same geocode and a different role are one site with two roles, and the rules keep them together.
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 |
|---|---|
| Legal | company code → plant |
| Operational | region → cluster → site |
| Supply network | source site → destination site 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 | time zone is a valid IANA name country matches the address |
| Row | an active manufacturing site has a factory calendar a closing site has a closing date and a successor for open stock a site with a sales role has a sales organisation |
| Business | every open order names an active site one site per company code per address capacity by region equals the sum of its sites |
| Transactions in the bed | Read from |
|---|---|
| Stock by site | SAP MARD; Oracle on-hand |
| Orders by site | sales and purchase orders |
| Production | production orders |
| Headcount | HR |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens stock, orders, production and headcount at the site, and every system's code for it.
Site facts readable by all; codes and lifecycle editable by the operations data owner; addresses verified before publication. The twelve layers apply on every door; see security.
POST /api/v1/golden/site/lookup
{
"name": "Böblingen",
"country": "DE",
"role": "manufacturing"
}200 OK
{
"golden_id": "S-0114",
"confidence": 0.98,
"xref": {
"sap_plant": "1210",
"oracle_inv_org": "BOB1",
"workday": "LOC-338"
},
"calendar": "DE-BW",
"status": "active"
}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.
Plant read from T001W · T001K.
Open the SAP S/4HANA page →Inventory organisation read from INV_ORG_PARAMETERS · HR_ALL_ORGANIZATION_UNITS (REST: inventoryOrganizations).
Open the Oracle Fusion Cloud page →Location read from cmn_location. 2 objects, the keys in ServiceNow fields, the write path and the prerequisites.
Open the ServiceNow page →Location read from Get_Locations. 2 objects, the keys in Workday fields, the write path and the prerequisites.
Open the Workday page →Site read from CONFORMED.SITE. 2 objects, the keys in Snowflake fields, the write path and the prerequisites.
Open the Snowflake page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A logistics group with 214 sites in five systems found 31 sites created twice and 6 closed sites still receiving orders. The golden site list became the reference for every new system rollout.
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; 2 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Industrial manufacturing, Consumer goods, Logistics and 3PL, 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.