ISO 8000: what the international standard for master data quality is

The same bolt created three different ways in the same ERP. One description in uppercase, another in lowercase, a third with the unit of measure swapped. The buyer can't find the item, inventory gets duplicated, and nobody knows which of the three records is the right one.

ISO 8000 is the international standard that says what has to be true for data to be considered quality data. It's not a consultant's opinion or a generic project checklist. It's an ISO standard, maintained by the technical committee that handles industrial data, and it goes straight at what I discuss every day with people in purchasing, maintenance and IT: the material master, supplier master, customer master and service master.

What ISO 8000 is

ISO 8000 defines quality data as portable data that meets stated requirements. Two concepts make all the difference here.

Portability means the data is formatted in a known, agreed-upon syntax, designed to be exchanged between different companies without losing meaning. A supplier sends the technical datasheet for a bearing and the customer's system understands it without someone reclassifying everything by hand.

Stated requirements means there is a specification behind the record. For each type of item, someone has defined which attributes are mandatory, in what format, with what unit of measure. Without that specification, data quality becomes a synonym for "looks organized," which is very different from being auditable.

The standard was born in 2002 and its first parts were approved in 2009, within the ISO/TC 184/SC 4 committee, the same one that handles industrial data. The inspiration comes from NATO's supply codification system, designed so that parts and materials could be identified without ambiguity across different countries and armies. Swap the military context for the industrial one and it's exactly the problem I live with in the master data of MRO materials, spare parts and maintenance items.

How ISO 8000 works in practice

The standard is split into parts, and each one tackles a specific piece of the bad data problem.

Part 8000-1 gives the overview and 8000-8 covers concepts and quality measurement. Part 8000-120 deals with provenance, that is, where the data came from and who answers for it. Part 8000-130 covers accuracy. Part 8000-140 covers completeness. Part 8000-110 defines the syntax and encoding so that a data specification is followed to the letter.

There's one part I consider decisive for anyone working with the material master: 8000-115, which covers quality identifiers, the so-called SmartPrefixes. In the record, it's a prefix that links a part's part number to the corresponding technical specification, cataloged in an open dictionary. Instead of each company inventing its own code for "2-inch ball valve," there's a common reference that is searchable and auditable.

Translated to the desk of a master data analyst: without ISO 8000, the material is described the way whoever typed it understood it that day. With the standard applied, the description follows a specification, carries the origin of the data and can be checked against an external source. It's the difference between trusting because the record looks right and trusting because you can prove it.

Who uses ISO 8000 and who is responsible for it

Inside the company, master data quality is not just an IT matter. Purchasing feels it when a poorly built material or supplier master leads to emergency buying and duplicate items in inventory. Maintenance feels it when poorly classified equipment delays the search for the right part in a warehouse with thousands of items. Quality and compliance feel it when data provenance and accuracy become evidence requested in an audit.

The role most closely tied to the standard, in companies that have already organized this, is the data steward, the person responsible for the quality of a specific data domain. This is the professional who helps define the specification for a type of material, makes sure the record follows the agreed syntax, and answers when someone asks where a given value came from. In a large company, this also lands on the agenda of the data governance committee, which decides which specifications apply across the whole organization, from the raw material master to the industrial asset master.

What tools support ISO 8000

The standard defines the benchmark. The ones who apply it day to day are MDM platforms and data dictionaries. ECCMA, the association that takes part in building ISO 8000, maintains an open technical dictionary used as a reference for a good part of the specifications described in the standard.

On the master data management platform side, SAP MDG, Informatica, Stibo Systems, Reltio, Semarchy, Profisee and Ataccama offer standardization, enrichment and validation features that help bring the company's data closer to ISO 8000 requirements, mainly in the dimensions of completeness, accuracy and provenance. No tool alone delivers compliance with the standard. It delivers structure. Whoever decides the specification and makes sure it is followed, record after record, is the governance process behind the tool.

How to learn about data quality and ISO 8000

For those who want to study the topic seriously, ECCMA offers the Master Data Quality Manager certification, the MDQM, aimed specifically at people who work with master data specification and quality.

Beyond that, the most traditional path is still DAMA-DMBOK and the CDMP certification, which cover data quality within a broader body of knowledge, alongside governance, modeling and architecture. I recommend the two as complementary. DAMA gives you the whole map of data management, and the ISO 8000 track goes deeper specifically into what has to be true for a record to be considered quality data. As I discuss in the book "Master Data Management: Fundamentos e Aplicações" (book in Portuguese), published by Editora Brasport, this is one of the points where master data theory and practice meet the most.

Career opportunities

Master data quality has become a recognized function within the data field, with salaries that already pass R$ 10,000 for a senior analyst and climb quite a bit for those who take the data steward or data quality manager seat. Companies that export, deal with international suppliers or need to prove compliance in an audit value even more someone who understands a formal standard like ISO 8000, because that professional knows how to turn "our data is right" into something that can be demonstrated with specification, provenance and evidence.

Main questions about ISO 8000

Is ISO 8000 mandatory? No. It's a voluntary standard. A company adopts it because it wants to reduce record errors, improve integration between systems or meet the requirement of a customer or partner that already works with the standard.

Is ISO 8000 the same thing as MDM? MDM is the discipline and practice of managing master data, with process, people and technology. ISO 8000 is the standard that defines what counts as quality within that practice. You can do MDM without following the standard to the letter, but without the same level of assurance.

Do I need specific software to follow ISO 8000? Not necessarily. You can apply the principles of the standard with a well-defined process and disciplined record maintenance. An MDM platform helps a lot, but what guarantees compliance is the specification and the governance behind it.

What's the difference between accuracy and completeness in the standard? Accuracy means the data is correct, matching reality. Completeness means the data is whole, with all mandatory fields filled in. A record can be complete and still wrong, and it can be correct and incomplete. ISO 8000 treats the two as separate dimensions, with their own parts for each.

Is it worth pursuing ISO 8000 certification? It depends on the sector and on what your business partners require. For a company that already organizes its records with a serious process, pursuing compliance formalizes what's already practiced and becomes a commercial argument. For those who haven't yet sorted out the basics of governance, the path is to start by organizing the records before aiming for certification.

MDM Academy

It's for people who live this master data routine, day after day, that we created MDM Academy, 4MDG's master data governance school. There we bring together content on master data, data quality, SAP, LGPD (Brazil's General Data Protection Law) and data careers, designed for people who work with master records every day and want to understand the theory without losing touch with what really happens inside the company.

If you want to go beyond the article, you can check out MDM Academy or join Data Club, our community of master data and governance professionals who share real experience about what works and what doesn't in the material, supplier and customer master.

Conclusion

After almost thirty years working with master data, SAP and big-company data, I learned that data quality is not a feeling. It's something you measure, specify and prove. ISO 8000 formalizes exactly that. It turns "our data is good" into a set of requirements you can audit, part by part, supplier by supplier.

At your company, does the material master hold up to an audit of provenance and completeness, or does it only look organized on the outside?