- Data that can be checked by computers
- Data that meets the requirement of the user
- Data that can be exchanged freely between organisations and systems
MRO Insyte is there to help you through the ISO 8000 journey.
The following is an extract from the technical specification of the standard (introduction to ISO/TS 8000-110:2008(E) ) that is designed to give an indication of the key requirements for implementation. It is not the complete standard, and any users wishing to adopt the standard should purchase the standards directly from ISO or their local ISO agent.
Data quality – Part 110: Master data:
Exchange of characteristic data: Syntax, semantic encoding, and conformance to data specification
ISO 8000-110:2009 specifies requirements that can be checked by computer for the exchange, between organizations and systems, of master data that consists of characteristic data. The focus of ISO 8000-110:2009 is on requirements that can be checked by computer.
- Each master data message shall contain in its header a reference to the formal syntax or syntaxes to which the master data message complies. The reference shall be in the form of an unambiguous identifier for the specific version of the formal syntax that was used to encode the master data message. Each formal syntax shall be available to all interested parties. If the master data is offered to the public, all the formal syntax shall be publicly available. Each formal syntax should be available at a reasonable cost.
- NOTE 1 Referencing more than one formal syntax is useful when one standard restricts the capability of the syntax defined in another standard while remaining compatible with the latter. In this case, users of both standards may decode the same master data message.
- NOTE 2 It is not required that a formal syntax be free of charge.
- NOTE 3 This does not preclude encryption.
- NOTE 4 Examples of publicly-available formal syntaxes are given in Table 2.
- It shall be possible to check, automatically, using software tools, that a master data message complies with the formal syntax.
- NOTE 5 From a practical standpoint, this means that the formal syntax needs to be a computer language, not a natural language.
- EXAMPLE A reference to the English language as the syntax would not satisfy this requirement.
Table 2 — Examples of publicly-available formal syntaxes
|ISO 9735||Electronic data interchange for administration, commerce and transport (EDIFACT) — Application level syntax rules|
|ISO 13584-25||Industrial automation systems and integration — Parts library — Part 25: Logical resource: Logical model of supplier library with aggregate values and explicit content|
|ISO 13584-35||Industrial automation systems and integration — Parts library — Part 35: Implementation resources: Spreadsheet interface for parts library|
|ISO/TS 22745-40||Industrial automation systems and integration — Open technical dictionaries and their application to master data — Part 40: Master data representation|
8 Semantic encoding
8.1 General requirements
8.1.1 Level 1 requirements
Semantic encoding is the technique of replacing natural language terms in a message with references to data dictionary entries. Each reference shall be in the form of a unambiguous identifier.
Each property value shall include or reference all data necessary to unambiguously define its meaning. Each reference shall be to a data dictionary entry contained in a data dictionary.
9 Conformance to data specification
Each master data message shall contain in its header a reference to the data specification or specifications to which the master data message complies. Each reference shall be in the form of an unambiguous identifier for the specific version of the data specification that was used to encode the master data message. All referenced data specifications shall be available to all interested parties. If the master data is offered to the public, then all referenced data specifications shall be publicly available. The data specifications should be available at a reasonable cost.
|NRICSC identification guide for machine bolts||ISO/TS 22745-30|
|FIIG A003B||item identification guide for bolts and screws||DoD 4100.39-M Volume 3|
|ISO 13584-501 dictionary||reference dictionary for measuring instruments||ISO 13584-25|
|ISO 13584-511||reference dictionary for fasteners||ISO 13584-25|
Technical Specification ISO/TS 8000-120:2009(E)
First edition 2009-08-01 Data quality — Part 120:
Master data: Exchange of characteristic data: Provenance
5 Fundamental concepts and assumptions
The Oxford English Dictionary defines provenance as:*
- the fact of coming from some particular source or quarter; origin, or derivation;
- the history or pedigree of a work of art, manuscript, rare book, etc.; concretely a record of the ultimate derivation and passage of an item through its various owners.
In this part of ISO 8000, the term “data provenance” corresponds to the first part of the second definition above: “history or pedigree of a property value”; the term “provenance record” corresponds to the second half of second definition above: “record of the ultimate derivation and passage of a property value through its various custodians”.
* The OED’s first citation of the use of the word “provenance” in English is from 1785. However, the word traces back to the earlier French word “provenance”.
Data Provenance is the history or pedigree of a property value.
Provenance Record is the record of the ultimate derivation and passage of a property value through its various custodians.