One record per physical asset: identity, location, ownership, technical structure and the maintenance and IT records that refer to it.
Today an asset is an equipment number in SAP, a fixed asset in finance, a configuration item in ServiceNow and a serial number on a label, and the four disagree on where it is.
With Lima the assets are read where they live, matched on serial number and manufacturer and asset tag, assembled field by field and published as one golden record per real equipment, with every source key underneath. Work orders, tickets, depreciation lines and readings for the asset, and its place in the technical structure 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.
Serial numbers are strong keys within a manufacturer; asset tags are strong within a company; the two are reconciled with the fixed-asset register.
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 |
|---|---|
| Technical | plant → functional location → equipment → sub-equipment |
| Financial | asset class → fixed asset |
| IT | service → configuration item |
| Geography | region → site → building |
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 | serial number is unique per manufacturer warranty end is after installation date |
| Row | an installed asset has a functional location a retired asset has no open work orders an IT asset has an owner and a support group |
| Business | the count of in-service assets per site matches the fixed-asset register or carries an explained difference no asset appears at two sites on the same date warranty claims are raised only for assets within warranty |
| Transactions in the bed | Read from |
|---|---|
| Work orders and notifications | SAP AUFK · QMEL; maintenance systems |
| Incidents and changes | ServiceNow |
| Depreciation | finance |
| Sensor readings | IoT feeds |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens work orders, tickets, depreciation lines and readings for the asset, and its place in the technical structure.
Acquisition cost visible to finance; location and status to operations; serials and models to everyone who maintains. The twelve layers apply on every door; see security.
POST /api/v1/golden/asset/lookup
{
"manufacturer": "KLA",
"serial": "KLA-2911-0047"
}200 OK
{
"golden_id": "A-70211",
"confidence": 0.99,
"site": "Austin fab 2",
"status": "in service",
"warranty_until": "2027-03-31",
"open_work_orders": 1
}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.
Equipment read from EQUI · EQKT · EQUZ.
Open the SAP S/4HANA page →Maintainable asset read from CSE_ASSETS_B (REST: installedBaseAssets).
Open the Oracle Fusion Cloud page →Asset read from alm_asset · alm_hardware.
Open the ServiceNow page →Asset read from CONFORMED.ASSET. 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 $100B semiconductor company keeps product warranty maintenance on Lima across 80 GB of new data a day; the equipment record ties each claim to the serial, the site and the service history in one view.
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; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.
High-tech and semiconductor, Industrial manufacturing, Telecom, Logistics and 3PL. 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.