Skip to main content

EAM and CMMS Optimization

What is master data management in facilities maintenance?

It is the governance that keeps asset, location and work data consistent as the system is used. Without it a clean go-live degrades on its own within a few quarters, because every site invents its own naming and the portfolio stops being comparable.

On this page

Master data management is the set of rules that decide what a thing is called, where it sits in the hierarchy, and who is allowed to change either. In a facilities program that means asset naming, location structure, work types, and criticality, settled once and held across every site in the portfolio.

It is the least visible part of a maintenance program and the first one to fail quietly.

How a clean system degrades on its own

Nothing dramatic happens. A site opens, or a vendor changes, or a crew inherits equipment the register did not anticipate, and somebody names it the most sensible way they can think of. That name is reasonable. It is also different from the name the site next door chose for the same class of equipment.

Within two quarters one asset class carries five names across three sites. Every record is individually correct.

What that costs at the portfolio level

Portfolio reporting then compares things that are not comparable. A roll-up of pump failures across fifteen sites is only a number if the fifteen sites agree on what a pump is, and once they do not, the roll-up quietly becomes an estimate.

The damage is not that the number is wrong. It is that nobody can tell how wrong, so nobody makes a decision on it, and a reporting layer that took a year to build stops being used for anything except proving activity.

Why it is settled before the screens

The hierarchy, the naming, the work types and the criticality model get agreed for the whole portfolio before a single screen is configured. Every configuration decision after that point either follows the model or breaks reporting later, and the breakage shows up two years downstream, well after the person who made the call has moved on.

This is the step most implementations compress, because it produces no visible software and it is the hardest part of the project to sell as progress.

What the governance actually is

It is not a document. It is a named owner, a rule for what happens when the building changes, and an audit that runs whether or not anyone is worried.

This is how a mission-critical plant treats its equipment list: verified rather than believed, with the verification itself audited. That is the shape this takes. A change to the building becomes a change to the data, with an owner, every time.

In practice

What the governance covers

Four decisions, made once for the portfolio rather than per site. Each one is cheap to settle up front and expensive to unwind later.

  • Asset hierarchy and namingOne structure and one naming convention across every site, so a roll-up compares equipment that is actually the same.
  • Location structureWhere a thing sits, expressed the same way in every building, because a work order that cannot be located is a work order somebody guesses at.
  • Work types and criticalityThe consequence rank that sets both the interval and the priority, agreed before anything is configured against it.
  • An owner and an auditA named person, a rule for what happens when the building changes, and a check that runs whether or not anyone suspects drift.
Still your question

Ask it about your own building.

A general answer is a starting point. If the question is about the site you run, it needs the site in front of it, and you will get a person who runs facilities rather than a form.