Matching Water Maintenance Jobs Recorded Under Old Site Names
Match water maintenance jobs to current asset records using controlled site aliases, component clues and reviewed exceptions instead of name-only joins.
How can a municipality link old maintenance jobs to assets after site names change?
Build a reviewed alias table connecting historical site names to stable location identifiers, then match each job to the appropriate asset or component using its supporting details. Keep ambiguous jobs unresolved until someone checks them. A shared site name is not sufficient evidence to assign every maintenance cost to one asset.
A maintenance system uses an informal pump station nickname while the asset register uses a formal project name. An integration joins neither, or joins the wrong installation with a similar name. A small translation layer can recover useful history without rewriting the source work orders.
Create an alias table with context
Extract unmatched site names from a defined maintenance period. Ask operations staff to associate them with current site identifiers, noting former names, abbreviations and effective dates. Include geographic or facility context where names repeat. Record who reviewed each mapping and which evidence supports it.
Treat an alias as a relationship, not a universal text replacement. A former site may have been split into two installations, or the same nickname may describe an entire precinct. Mark those cases as one-to-many or unresolved. Do not let a spreadsheet lookup choose the first plausible destination simply because it returns a result.
Use component clues before allocating jobs
Read the work order's equipment number, serial, description and attachment references. A job recorded against a station might concern a pump, building, fence or shared electrical installation. Link it at the level the evidence supports. If the component cannot be identified, retain the station-level association and flag the limitation.
Separate document linkage from cost allocation. A job spanning several assets may need finance or engineering input before costs are distributed. Do not copy the entire invoice value to every linked asset. Keep the original job and amount intact while recording any reviewed allocation as a distinct derived record.
Test the mapping before broad use
Apply the alias table to a sample that includes duplicate names, renamed sites and jobs near a change date. Ask operations staff to inspect matches and rejected cases. Measure confirmed matches and unresolved records separately; a high automatic match rate is not useful if it conceals incorrect asset histories.
Version the accepted mapping and preserve the source names in imported records. When an alias changes, assess whether earlier imports need correction rather than silently changing their meaning. Give the table a maintenance owner so the next site rename does not recreate the same backlog in a different reporting period.
Practical Example
Illustrative example: Old jobs refer to North Pump, but the current system contains North Station A and North Station B. A name-only match would allocate everything to A. Reviewing work-order equipment numbers links most jobs correctly and leaves three without enough detail. Those remain station-area exceptions until operations can supply evidence.
Action Checklist
- 1.Extract unmatched names from a bounded maintenance period and preserve the source text.
- 2.Review aliases with operations staff using location context and effective dates.
- 3.Match jobs to components only where identifiers or supporting details justify it.
- 4.Keep multi-asset cost allocation separate from document matching.
- 5.Test difficult cases, version the accepted mappings and assign an update owner.
Improve maintenance-to-register matching with Asset Management Software.
