Back to Blog
Blog

How do you map document identities when two systems use different site and location hierarchies?

How do you map document identities when two systems use different site and location hierarchies?

Mapping document identities across different hierarchies is a common problem, since one system might organize by site, area and unit while another uses…

Mapping document identities across different hierarchies is a common problem, since one system might organize by site, area and unit while another uses a completely different structure or naming, which makes it hard to match documents and equipment across systems. A document control system might file procedures under a plant code and building, while the CMMS uses functional locations and the engineering system uses its own area numbering inherited from the original construction contractor.

Without a reliable mapping between the two structures, integrations either fail outright or quietly link the wrong things. A procedure meant for a pump in one unit could be attached to equipment with a similar name somewhere else, or documents simply fail to appear where people expect them, and once users see a wrong link they stop trusting the integration and go back to searching each system by hand.

The practical approach is to build a mapping table between the two hierarchies, starting with the most important locations and expanding over time, and to use stable identifiers like equipment tags wherever possible. Tags tend to survive reorganizations and system migrations far better than location names, which change when units are merged or renamed, so anchoring the mapping on tags and treating location as a secondary match reduces how often it breaks.

The table itself should have a clear owner and a simple process for updating it when either hierarchy changes, since a mapping that was accurate at go live will slowly decay as new equipment is added and areas are reorganized. Records that cannot be matched automatically should land in a review list for someone who knows the site, rather than being matched on a best guess that nobody checks.

It is slow work at the start, but once done it makes every later integration much easier. The same mapping can support procedures, inspections, permits and reporting, and many teams find that building it exposes duplicate or obsolete locations in their own systems, so the effort usually improves data quality beyond the integration that prompted it.