Asset master data: the equipment master record that underpins industrial maintenance
Asset master data: what it is, how to organize the equipment master record in SAP PM, and why it decides industrial maintenance.
Asset master data is the record that describes each physical piece of equipment in an industrial plant, uniquely and completely, so that maintenance, engineering, and operations can plan, execute, and pay for what actually exists on the plant floor.
It sounds like a technical IT concept. In practice it's a machine downtime problem.
I once saw a plant that had the same compressor registered three times in SAP, once for each overhaul it went through. Each overhaul, a different technician, a different tag, a different functional location. When the reliability team went to pull that compressor's failure history to decide whether to replace it or overhaul it again, it found three fragmented histories, none complete. A decision that should have taken an afternoon took two weeks.
That is poorly maintained asset master data costing money and the time of good people.
What asset master data is
Asset master data is the information that uniquely identifies each piece of equipment, machine, vehicle, or facility the company owns and needs to maintain. Equipment tag, manufacturer, model, serial number, installation date, functional location, criticality to the operation, linked maintenance plan, and intervention history. All of that is asset master data.
The difference from the material master is simple to explain and hard to remember day to day. A material is what the company buys, stocks, and consumes, like spare parts, oil, screws. An asset is the physical good the company owns, installs, and maintains over years, like the compressor, the conveyor, the truck fleet, the transformer. The same part can be a material in the warehouse and become a component of an asset once it is installed. The office chair, for example, is a product for whoever manufactures it and an asset for whoever does the fixed-asset inventory. The same reasoning applies, on a larger scale, to an entire production line.
In SAP projects, this record lives in the PM module, Plant Maintenance, within what the market calls EAM, Enterprise Asset Management. That is where the equipment, the functional location, the maintenance order, and the history sit. And it is exactly where master data mess shows up first, because everyone touches this record under pressure, in the middle of a plant shutdown, with no time to do it right.
How it works in practice
The heart of the asset master is two objects that complement each other. The functional location describes the functional place within the plant, for example filling line 2, regardless of which machine is installed there today. The equipment is the physical asset that occupies that location, with its own serial number and history. When the machine is replaced, the functional location keeps existing and receives the new equipment. If this structure isn't respected, the failure history is lost with every machine swap, exactly as in the compressor case.
On top of those two objects, the company hangs the preventive maintenance plan, the list of linked spare parts, the asset's criticality to the operation, and the availability indicators. If the asset master is wrong, the preventive maintenance order is opened on the wrong equipment, the reserved part is not the part actually installed, and the technician arrives at the machine without the right part in hand.
Criticality is another point that almost always ends up half-baked. Every company says it classifies assets by criticality, but in practice half the fleet shows up as critical because nobody wanted to take on the responsibility of saying it isn't. That destroys planning, because the PCM (maintenance planning and control) cannot prioritize what can really stop production.
Who uses it and who is responsible
The asset master is not exclusively owned by anyone, and that is where the governance problem lives. Maintenance engineering registers the equipment at installation. Maintenance planning and control, the PCM, uses that record every day to schedule orders. Operations reports failures and stoppages linked to the asset. Reliability engineering uses the history to decide whether to replace, overhaul, or scrap. Finance uses the same asset for depreciation and fixed-asset control. And procurement uses the linked parts list to buy spare parts.
With so many people touching the same record, without a formal data owner, the record gets corrupted little by little. My recommendation in projects is always the same: define an asset data steward, usually someone from maintenance engineering, responsible for approving the creation and change of equipment. Without an owner, the asset master becomes no man's land.
Which tools support the asset master
Most Brazilian companies with a relevant industrial base use SAP PM as the system of record for equipment and maintenance orders, often inside S/4HANA. Outside the SAP universe, IBM Maximo and Infor EAM are the most common references in large plants, mining, oil and gas, and energy.
These systems store the data, but they don't on their own guarantee that it is correct, complete, and duplicate-free. That is where the governance and master data quality layer comes in, with tools such as SAP Master Data Governance, Informatica, Stibo Systems, Reltio, Semarchy, Profisee, and Ataccama, which help standardize record creation, apply approval rules, and identify duplicate or misclassified equipment before the error reaches the maintenance order. None of these tools replaces the work of defining, together with engineering, what a complete asset master record is for that specific plant.
How to learn about asset master data
Anyone already working in industrial maintenance is halfway there, because they understand the physical process behind the data. What is usually missing is the view of governance, of data modeling, and of how this record connects with procurement, finance, and IT.
The most direct path is to study in depth the maintenance module of the system the company uses, whether SAP PM, Maximo, or another, understanding thoroughly the structure of functional location and equipment. In parallel, it is worth building a solid foundation in master data governance and management, which is a larger body of knowledge than any specific system. DAMA's CDMP certification, with its different levels, is the most widely recognized international reference for those who want to prove mastery of the data management field as a whole, including master and reference data.
As I discuss in the book Master Data Management: Fundamentos e Aplicações (book in Portuguese), published by Editora Brasport, asset data follows the same principles as any master data domain, uniqueness, completeness, integrity, and governance, only applied to a physical object you can touch with your hand.
Opportunities in the field
Heavy industry, mining, oil and gas, energy, pulp and paper, and capital goods are investing heavily in reliability and predictive maintenance, and none of those initiatives works without a reliable asset master behind it. That opens room for professionals who can move between the world of maintenance engineering and the world of data.
The most common roles on this track are asset master data analyst, maintenance planner with a data focus, reliability engineer, SAP PM functional consultant, and industrial asset data steward. It is an area with fewer people competing than the generic data market, because it requires understanding the industrial process and not just databases.
Main questions about asset master data
What differentiates asset master data from material master data? A material is what the company buys, stocks, and consumes. An asset is the physical good the company installs, maintains, and depreciates over time, like a machine or a vehicle.
Which system holds the asset master at most Brazilian companies? SAP PM, the Plant Maintenance module, is the most common at mid-sized and large companies that use SAP. Outside that universe, IBM Maximo and Infor EAM show up frequently.
Who should own the equipment master record? Ideally a formally appointed data steward, usually from maintenance or reliability engineering, responsible for approving the creation and change of each record.
Is asset master data related to predictive maintenance and Industry 4.0? Directly related. Sensors and artificial intelligence applied to maintenance only generate reliable predictions if the asset history and the functional location structure are correct. A good sensor on top of a poor master record only speeds up a wrong decision.
Is it worth having a governance tool just for assets? It depends on the size of the fleet and the criticality of the operation. Companies with thousands of pieces of equipment and continuous operation, where downtime is expensive, normally justify investing in a dedicated governance layer, in addition to the maintenance system itself.
MDM Academy
MDM Academy is 4MDG's governance and master data school, created to train the kind of professional the Brazilian market still has too few of, someone who understands business process, systems, and data at the same time. The courses range from the fundamentals of governance and data quality to specific tracks on material, supplier, customer master data and, increasingly, domains such as assets and maintenance.
If you work in maintenance, engineering, or master data and feel there is a missing bridge between the physical world of equipment and the world of data governance, it's worth getting to know MDM Academy or joining the Data Club, where we discuss these problems with people who live them every day.
Conclusion
Asset master data is not an IT topic. It is a topic for whoever decides whether the machine stops or doesn't. Every time I see a company investing heavily in sensors, artificial intelligence, and predictive maintenance without first fixing the equipment master record that supports all of it, I think the same thing: they are building a beautiful building on top of a cracked foundation.
The asset master doesn't need to be perfect to start generating value. It needs to be unique, complete, and have an owner. The rest adjusts over time, as long as someone takes responsibility for looking after it.
Want to become a data governance specialist? Talk to our specialists now and get to know MDM Academy
I want to be a student
