One record per physical asset: identity, location, ownership, technical structure and the maintenance and IT records that refer to it.
Tables are read through the Table API and, for volume, exports; the rows stay in ServiceNow.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Asset | alm_asset · alm_hardware | sys_id · asset_tag · serial_number · model · location · assigned_to · install_status | live; polled or event-driven |
| Configuration item | cmdb_ci | sys_id · name · serial_number · model_id · support_group | live; polled or event-driven |
| Incidents and changes | incident · change_request | cmdb_ci · state · opened_at | live; polled or event-driven |
The first object above carries the strong keys; the standardised attributes come from the same rows. Serial numbers are strong keys within a manufacturer; asset tags are strong within a company; the two are reconciled with the fixed-asset register.
Writes go through the Table API or Import Sets with a coalesce field; each call returns the sys_id or the error, logged beside the change.
| Interface | Used for | Result |
|---|---|---|
Import Set with coalesce on serial_number; Table API for status | golden values approved for write-back: identity; location and ownership; technical | the id or error ServiceNow returns, stored beside the change |
Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.
ServiceNow roles and ACLs are mapped to Lima policies once.
Equipment and assets on
Other domains on ServiceNow
The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.
Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in ServiceNow.
Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.
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.