Asset data management for records your service team can identify
A maintenance record, a location label and a supplier description may refer to the same machine. A custom equipment workflow can make those references usable while keeping genuinely separate assets apart.
How could equipment records be cleaned and checked for duplicates?
Agree what identifies one physical asset: manufacturer, serial number, site and equipment type may all matter. Normalize supported names and references, then review potential duplicates with maintenance owners. Repeated model numbers identify a product family, not necessarily the same machine.
Equipment identity needs more than a similar name
Names and technical fields
Define naming patterns, manufacturer labels, model codes and mandatory fields. Preserve original identifiers and do not infer technical ratings from similar equipment descriptions.
Location and hierarchy
Agree site, building and parent/child references. Check whether a record represents a whole machine, an assembly, a replaceable component or a service location before comparing it.
Duplicate review with owners
Use available serial numbers and location evidence to suggest candidates. Keep service history and operational status attached to their original records unless a supported, separately approved action says otherwise.
How it works
- 1
Choose records and owners
Select a site, equipment class or limited record range. Involve the team that can distinguish a duplicate asset from two machines of the same model.
- 2
Define identifiers and formats
Agree serial-number handling, manufacturer aliases, naming patterns and location mappings. Preserve significant leading zeros and characters.
- 3
Review proposed corrections
Compare field changes and candidate duplicates. Resolve missing identifiers or conflicting sites manually; do not treat absent evidence as a match.
- 4
Apply supported master-data updates
Publish approved fields and report outcomes. Any action affecting service records, maintenance scheduling or deactivation needs explicit provider checks and approval.
Same compressor model, two different machines
“Compressor AC-20” and “COMPRESSOR AC 20” could be the same model installed at two sites. A rule can standardize the model label while retaining separate assets. A repeated serial number can prompt review, but conflicting sites should remain visible.
Equipment processing is a custom project option. This example does not include condition monitoring, safety validation, maintenance rescheduling or merging service history.
Frequently asked questions
Which systems could supply asset records?
Is a matching serial number enough?
Can location labels be standardized?
Will service history be merged?
What should your data process do differently?
Use the Contact page to describe your systems, record types and the problem you want to solve. We will agree the scope, access and acceptance criteria before implementation.