ISO 8000-100:2016
(Main)Data quality — Part 100: Master data: Exchange of characteristic data: Overview
Data quality — Part 100: Master data: Exchange of characteristic data: Overview
ISO 8000-100:2016 contains an overview of the master data quality series of parts of ISO 8000, which addresses master data quality. The following are within the scope of the master data quality series of parts of ISO 8000: · master data-specific aspects of quality management systems; · master data quality metrics. The approach of the master data quality series of parts of ISO 8000 is to address data quality: · from the bottom up, i.e. from the smallest meaningful element, the property value; · at the interface of master data management systems, not within the systems. The master data quality series of parts of ISO 8000 contains requirements that can be checked by computer for the exchange, between organizations and systems, of master data that consists of characteristic data. These parts address the quality of property values that are exchanged within master data messages. ISO 8000-100:2016 describes fundamentals of master data quality and specifies requirements on both data and organizations to enable master data quality. The following are within the scope of ISO 8000-100:2016: · specification of the scope of the master data quality series of parts of ISO 8000; · introduction to master data; · description of the data architecture; · overview of the content of the other parts of the series. The following are outside the scope of ISO 8000-100:2016: · aspects of data quality that apply to all data regardless of whether they are master data; · aspects of data quality that apply to data that are not master data.
Qualité des données — Partie 100: Données permanentes: Échange des données caractéristiques: Aperçu général
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 8000-100
First edition
Data quality —
Part 100:
Master data: Exchange of
characteristic data: Overview
Qualité des données —
Partie 100: Données permanentes: Échange des données
caractéristiques: Aperçu général
PROOF/ÉPREUVE
Reference number
©
ISO 2016
© ISO 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – All rights reserved
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviated terms . 2
5 Master data . 2
6 Data architecture for master data . 4
7 High-level data model . 5
7.1 General . 5
7.2 Diagram . 6
7.3 Entities . 6
7.3.1 data_dictionary . 6
7.3.2 data_dictionary_entry . 7
7.3.3 data_record . 7
7.3.4 data_set . 7
7.3.5 data_object . 7
7.3.6 data_object_accuracy_event. 8
7.3.7 data_object_completeness_event . 8
7.3.8 data_object_provenance_event . 8
7.3.9 property_value_assignment . 8
8 Overview of the master data quality series of parts of ISO 8000 . 9
Annex A (normative) Document identification .11
Annex B (informative) Categories of items .12
Bibliography .14
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO’s adherence to the World Trade Organization (WTO) principles in the
Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.
The committee responsible for this document is Technical Committee ISO/TC 184, Automation systems
and integration, Subcommittee SC 4, Industrial data.
This first edition of ISO 8000-100 cancels and replaces ISO/TS 8000-100:2009, which has been
technically revised.
ISO 8000 is organized as a series of parts, each published separately. The structure of ISO 8000 is
described in ISO/TS 8000-1.
Each part of ISO 8000 is a member of one of the following series: general data quality, master data
quality, transactional data quality, and product data quality. This part of ISO 8000 is a member of the
master data quality series.
A list of all parts in the ISO 8000 series can be found on the ISO website.
iv PROOF/ÉPREUVE © ISO 2016 – All rights reserved
Introduction
The ability to create, collect, store, maintain, transfer, process and present data to support business
processes in a timely and cost effective manner requires both an understanding of the characteristics
of the data that determine its quality, and an ability to measure, manage and report on data quality.
ISO 8000 defines characteristics that can be tested by any organization in the data supply chain to
objectively determine conformance of the data to ISO 8000.
ISO 8000 provides frameworks for improving data quality for specific kinds of data. The frameworks
can be used independently or in conjunction with quality management systems.
ISO 8000 covers industrial data quality characteristics throughout the product life cycle from
conception to disposal. ISO 8000 addresses specific kinds of data including, but not limited to, master
data, transaction data, and product data.
The master data quality series of parts of ISO 8000 addresses the quality of master data. This part of
ISO 8000 is an introduction to the series. It contains an introduction to master data, a data architecture,
a high-level data model, and an overview of the remaining parts of the series.
Annex A contains an identifier that unambiguously identifies this part of ISO 8000 in an open
information system.
Annex B describes different categories of items and their identifiers.
INTERNATIONAL STANDARD ISO 8000-100:2016(E)
Data quality —
Part 100:
Master data: Exchange of characteristic data: Overview
1 Scope
This part of ISO 8000 contains an overview of the master data quality series of parts of ISO 8000, which
addresses master data quality.
The following are within the scope of the master data quality series of parts of ISO 8000:
— master data-specific aspects of quality management systems;
— master data quality metrics.
The approach of the master data quality series of parts of ISO 8000 is to address data quality:
— from the bottom up, i.e. from the smallest meaningful element, the property value;
— at the interface of master data management systems, not within the systems.
The master data quality series of parts of ISO 8000 contains requirements that can be checked by
computer for the exchange, between organizations and systems, of master data that consists of
characteristic data. These parts address the quality of property values that are exchanged within
master data messages.
This part of ISO 8000 describes fundamentals of master data quality and specifies requirements on
both data and organizations to enable master data quality.
The following are within the scope of this part of ISO 8000:
— specification of the scope of the master data quality series of parts of ISO 8000;
— introduction to master data;
— description of the data architecture;
— overview of the content of the other parts of the series.
The following are outside the scope of this part of ISO 8000:
— aspects of data quality that apply to all data regardless of whether they are master data;
— aspects of data quality that apply to data that are not master data.
EXAMPLE Transaction data are not considered to be master data.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 8000-2, Data quality — Part 2: Vocabulary
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 8000-2 apply.
4 Abbreviated terms
MDR master data record
UML Unified Modeling Language
5 Master data
Within an organization, master data is used to identify and describe things that are significant to the
organization.
NOTE 1 In cataloguing applications, master data are used to describe things called “items”.
Figure 1 depicts a taxonomy of data, showing where master data fits.
NOTE 2 Figure 1 is not intended to be a complete taxonomy of data; it is only intended to show the context of
master data.
Figure 1 — Taxonomy of data (for master data)
Master data is typically referenced in business transactions through an identifier. The identifier is
commonly a reference both to the thing itself and to a master data record (MDR) that describes the
thing. The MDR is commonly held in a central repository.
EXAMPLE 1 It is common for the central repository of MDRs for an organization to be the organization’s
enterprise resource planning (ERP) or master data management (MDM) system.
NOTE 3 What is logically a single MDR can be represented by several physical records in a software system.
EXAMPLE 2 In a relational database implementation, a master data record could consist of rows from several
different tables.
NOTE 4 A MDR that describes something can be identified via a reference using its identifier. Something can
be described by characteristic data, represented by property values. Additionally, something can be described by
descriptive strings or definitions.
2 PROOF/ÉPREUVE © ISO 2016 – All rights reserved
Identifying references are designed to be used as references to master data held by others.
EXAMPLE 3 A corporate tax identifier, an individual’s national insurance number, and a part number assigned
by a manufacturer to an item of production are all examples of identifying references.
In order for an identifying reference to be meaningful, it shall be associated with a system of
identification.
EXAMPLE 4 The organization that issued the identifier can be specified by the metadata, as is common in tax
identifiers, but a part number is meaningless if the manufacturer that issued it is not known.
A description can be computer interpretable characteristic data,
...
INTERNATIONAL ISO
STANDARD 8000-100
First edition
2016-10-01
Data quality —
Part 100:
Master data: Exchange of
characteristic data: Overview
Qualité des données —
Partie 100: Données permanentes: Échange des données
caractéristiques: Aperçu général
Reference number
©
ISO 2016
© ISO 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – All rights reserved
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviated terms . 2
5 Master data . 2
6 Data architecture for master data . 4
7 High-level data model . 5
7.1 General . 5
7.2 Diagram . 6
7.3 Entities . 6
7.3.1 data_dictionary . 6
7.3.2 data_dictionary_entry . 7
7.3.3 data_record . 7
7.3.4 data_set . 7
7.3.5 data_object . 7
7.3.6 data_object_accuracy_event. 8
7.3.7 data_object_completeness_event . 8
7.3.8 data_object_provenance_event . 8
7.3.9 property_value_assignment . 8
8 Overview of the master data quality series of parts of ISO 8000 . 9
Annex A (normative) Document identification .11
Annex B (informative) Categories of items .12
Bibliography .14
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO’s adherence to the World Trade Organization (WTO) principles in the
Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.
The committee responsible for this document is Technical Committee ISO/TC 184, Automation systems
and integration, Subcommittee SC 4, Industrial data.
This first edition of ISO 8000-100 cancels and replaces ISO/TS 8000-100:2009, which has been
technically revised.
ISO 8000 is organized as a series of parts, each published separately. The structure of ISO 8000 is
described in ISO/TS 8000-1.
Each part of ISO 8000 is a member of one of the following series: general data quality, master data
quality, transactional data quality, and product data quality. This part of ISO 8000 is a member of the
master data quality series.
A list of all parts in the ISO 8000 series can be found on the ISO website.
iv © ISO 2016 – All rights reserved
Introduction
The ability to create, collect, store, maintain, transfer, process and present data to support business
processes in a timely and cost effective manner requires both an understanding of the characteristics
of the data that determine its quality, and an ability to measure, manage and report on data quality.
ISO 8000 defines characteristics that can be tested by any organization in the data supply chain to
objectively determine conformance of the data to ISO 8000.
ISO 8000 provides frameworks for improving data quality for specific kinds of data. The frameworks
can be used independently or in conjunction with quality management systems.
ISO 8000 covers industrial data quality characteristics throughout the product life cycle from
conception to disposal. ISO 8000 addresses specific kinds of data including, but not limited to, master
data, transaction data, and product data.
The master data quality series of parts of ISO 8000 addresses the quality of master data. This part of
ISO 8000 is an introduction to the series. It contains an introduction to master data, a data architecture,
a high-level data model, and an overview of the remaining parts of the series.
Annex A contains an identifier that unambiguously identifies this part of ISO 8000 in an open
information system.
Annex B describes different categories of items and their identifiers.
INTERNATIONAL STANDARD ISO 8000-100:2016(E)
Data quality —
Part 100:
Master data: Exchange of characteristic data: Overview
1 Scope
This part of ISO 8000 contains an overview of the master data quality series of parts of ISO 8000, which
addresses master data quality.
The following are within the scope of the master data quality series of parts of ISO 8000:
— master data-specific aspects of quality management systems;
— master data quality metrics.
The approach of the master data quality series of parts of ISO 8000 is to address data quality:
— from the bottom up, i.e. from the smallest meaningful element, the property value;
— at the interface of master data management systems, not within the systems.
The master data quality series of parts of ISO 8000 contains requirements that can be checked by
computer for the exchange, between organizations and systems, of master data that consists of
characteristic data. These parts address the quality of property values that are exchanged within
master data messages.
This part of ISO 8000 describes fundamentals of master data quality and specifies requirements on
both data and organizations to enable master data quality.
The following are within the scope of this part of ISO 8000:
— specification of the scope of the master data quality series of parts of ISO 8000;
— introduction to master data;
— description of the data architecture;
— overview of the content of the other parts of the series.
The following are outside the scope of this part of ISO 8000:
— aspects of data quality that apply to all data regardless of whether they are master data;
— aspects of data quality that apply to data that are not master data.
EXAMPLE Transaction data are not considered to be master data.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 8000-2, Data quality — Part 2: Vocabulary
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 8000-2 apply.
4 Abbreviated terms
MDR master data record
UML Unified Modeling Language
5 Master data
Within an organization, master data is used to identify and describe things that are significant to the
organization.
NOTE 1 In cataloguing applications, master data are used to describe things called “items”.
Figure 1 depicts a taxonomy of data, showing where master data fits.
NOTE 2 Figure 1 is not intended to be a complete taxonomy of data; it is only intended to show the context of
master data.
Figure 1 — Taxonomy of data (for master data)
Master data is typically referenced in business transactions through an identifier. The identifier is
commonly a reference both to the thing itself and to a master data record (MDR) that describes the
thing. The MDR is commonly held in a central repository.
EXAMPLE 1 It is common for the central repository of MDRs for an organization to be the organization’s
enterprise resource planning (ERP) or master data management (MDM) system.
NOTE 3 What is logically a single MDR can be represented by several physical records in a software system.
EXAMPLE 2 In a relational database implementation, a master data record could consist of rows from several
different tables.
NOTE 4 A MDR that describes something can be identified via a reference using its identifier. Something can
be described by characteristic data, represented by property values. Additionally, something can be described by
descriptive strings or definitions.
2 © ISO 2016 – All rights reserved
Identifying references are designed to be used as references to master data held by others.
EXAMPLE 3 A corporate tax identifier, an individual’s national insurance number, and a part number assigned
by a manufacturer to an item of production are all examples of identifying references.
In order for an identifying reference to be meaningful, it shall be associated with a system of
identification.
EXAMPLE 4 The organization that issued the identifier can be specified by the metadata, as is common in tax
identifiers, but a part number is meaningless if the manufacturer that issued it is not known.
A description can be computer interpretable characteristic data, which is typically represented as
property values, or human reada
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.