Asset data that arrives in someone else’s structure
The engine maps contractor deliveries, maintenance data and master data into your model by meaning, holds anything uncertain for a person, and keeps systems aligned as they change.
The sector
Operators run engineering registers, maintenance systems, document management and master data systems for assets that stay in service for decades. Much of the data in them comes from contractors, suppliers and previous owners.
The problem
Every handover arrives in the contractor’s own structure and has to be mapped into the operator’s model before it can be used. From the day of handover, the engineering register and the maintenance system start to drift apart, and master data is staged for loading largely by hand.
How we fix it
| Where it breaks | What the engine does | |
|---|---|---|
| Contractor handover | Tag registers, equipment lists and documentation arrive in each contractor’s structure. Standards such as CFIHOS help, but every handover is still mapped. | Incoming data is classified by what it means and mapped to your structure, with a confidence score on every mapping. |
| Engineering and maintenance | The register and the maintenance system drift apart from the day of handover. | When either one changes, the mapping between them is re-interpreted, not rebuilt. |
| Master data staging | Data has to be cleaned, deduplicated and structured before it can be loaded, mostly by hand. | Duplicates are found, records are classified and scored, and anything uncertain is held for a person instead of being loaded. |
| Asset transactions | When a field or a licence changes hands, the buyer inherits years of data in the seller’s structure. | The seller’s data is mapped into your model as a migration, with a fixed end point and a clear test of whether it arrived correctly. |
What your architect will ask
- Does it understand CFIHOS or ISO 15926?
- It works from what the data contains, whatever standard it was meant to follow. How well it handles a particular contractor’s delivery is something to test on that delivery.
- What happens to poor-quality data?
- It is scored. Records the engine cannot classify with confidence are held for a person, so nothing low-confidence reaches the target without someone seeing it.
- Where does it run?
- Wherever you run your other enterprise systems: private cloud or on-premise. It has no connection to us, to any model provider or to any other third party.
Where we would start
With the next contractor handover or asset transaction, run as a data migration. It has a fixed end point and a clear test: does the data arrive in your model correctly.
Bring us one of your integrations
We will run it against your systems in a working session and show you what the engine does with it.
Book a demo