Before
Equipment was an equipment number in the ERP, a configuration item in the service tool and a serial on a label, and the three disagreed on where the tool was; warranty claims were checked against a spreadsheet.
A semiconductor company keeps its product warranty maintenance and a global control tower on Lima; the golden equipment record ties each claim to the serial, the site and the service history, across 80 GB of new data a day.
Equipment was an equipment number in the ERP, a configuration item in the service tool and a serial on a label, and the three disagreed on where the tool was; warranty claims were checked against a spreadsheet.
Golden equipment records matched on serial number and manufacturer, placed in the technical structure (site, functional location, equipment) and the financial structure; the warranty rule (claims only within warranty); drill-down from the asset to work orders, tickets and readings.
A claim opens on the golden asset with its service history beside it; the rule checks the warranty; the control tower pivots claims by model, site and month.
anonymised engagement
of new data processed on the estate.
anonymised engagementgolden equipment record per serial, in two structures.
anonymised engagementcontrol tower on the golden records.
anonymised engagementSlot for the customer's own words: supplied and approved by the reference contact before publication. The story above is written in Lima's voice from the engagement material; the customer's feedback goes here in theirs.
Match on serial and manufacturer, reconcile with the fixed-asset register, and put the service history on the asset page before the first claim rule.
Under NDA, with the account owner's approval, we arrange a conversation with a customer whose domains and systems resemble yours.
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.