International Association of Data Quality Managers Using ISO

  • Slides: 29
Download presentation
International Association of Data Quality Managers Using ISO 8000 to get the data you

International Association of Data Quality Managers Using ISO 8000 to get the data you need Peter Benson Executive Director ECCMA All ERP applications run better on ISO 8000 quality data! Copyright © 2011 by ECCMA All rights reserved Slide 1

Data is the New Reality! Slide 2

Data is the New Reality! Slide 2

Motivation for ISO 22745 and ISO 8000 Controlling costs requires better asset, product, component

Motivation for ISO 22745 and ISO 8000 Controlling costs requires better asset, product, component and process visibility. This is achieved through faster, better and lower cost access to authoritative characteristic data. Slide 3

Motivation for ISO 22745 and ISO 8000 Controlling costs requires better asset, product, component

Motivation for ISO 22745 and ISO 8000 Controlling costs requires better asset, product, component and process visibility. This is achieved through faster, better and lower cost access to authoritative characteristic data. Slide 4

Motivation for ISO 22745 and ISO 8000 “From a logistics information perspective… an F-15

Motivation for ISO 22745 and ISO 8000 “From a logistics information perspective… an F-15 is just 171, 000 parts flying in very close formation. ” Cataloging and Standardization Act, Public Law 82 -436 as codified by United States Code, Title 10, Chapter 145 – Cataloging and Standardization Sec. 2451. (a) The Secretary of Defense shall develop a single catalog system and related program of standardizing supplies for the Department of Defense. (b) In cataloging, the Secretary shall name, describe, classify, and number each item recurrently used, bought, stocked, or distributed by the Department of Defense, so that only one distinctive combination of letters or numerals, or both, identifies the same item throughout the Department of Defense. Only one identification may be used for each item for all supply functions from purchase to final disposal in the field or other area. Slide 5

A Commercial Example of the Application of ISO 8000 Common ERP Descriptions 52368965412 –

A Commercial Example of the Application of ISO 8000 Common ERP Descriptions 52368965412 – Tire Bridgestone 435/95 R 25 56329845 – Tyre BS 435/R 25 Standard Purpose E 3 2 Star Radial 125435 – Bridge Stone 25 inch 435/95 965123465 – Tyre Bridgestone Part Number 12345 Standardised Long Description: Tire: Pneumatic, Vehicular: Service Type for Which Designed: Loader Tire Rim Nominal Diameter: 25' Tire Width: 445 mm Aspect Ratio: 0. 95 Tire Ply Arrangement: Radial Ply Rating: 2* Tire & Rim Association Number: E 3 Tread Material: Standard Tire Air Retention Method: Tubeless Tire Load Index and Speed Symbol: NA Tread Pattern: VHB TKPH Rating: 80 Standardised Short Description: Tire Pneumatic: Loader 25‘ 445 mm 0. 95 2* Slide 6

International Organization for Standardization (ISO) • 156 National standard organization members (one per country)

International Organization for Standardization (ISO) • 156 National standard organization members (one per country) (AFNOR, ANSI, BSI CNIS, DIN, GOST, SABS, SASO ………. ) • Central Secretariat in Geneva – 150 staff • 192 Technical Committees – 3 000 Technical bodies – 50 000 domain experts* (*you can become an ISO expert ) • ISO TC 184 Automation systems and integration Standardization in the field of automation systems and their integration for design, sourcing, manufacturing and delivery, support, maintenance and disposal of products and their associated services. Areas of standardization include information systems, robotics for fixed and mobile robots in industrial and specific non-industrial environments, automation and control software and integration technologies. ISO TC 184 SC 4: ISO 8000 data quality - ISO 22745 exchange of quality data Slide 7

ISO Standards Development Process New Work Item (NWI) Ballot simple majority and at least

ISO Standards Development Process New Work Item (NWI) Ballot simple majority and at least 5 countries supporting Committee Draft (CD) Ballot 2/3 majority Draft International Standard (DIS) Ballot 2/3 majority Final Draft International Standards (FDIS)Ballot 2/3 majority International Standard (IS) A two year (minimum) process designed to ensure international consensus Slide 8

What do standards do and how do they do it What do standards do?

What do standards do and how do they do it What do standards do? Standards make interoperability possible, they allow us all to benefit from economies of scale, they set minimum expectations (safety for example). How? : Standards are specifications – by claiming compliance with a standard you are publicly announcing that you meet the requirements of the standard. ISO Standards contain: Definition of terms • If a term is not defined in a standard, the Oxford English dictionary (OED) definition applies. A term may be defined in another ISO standard, in which case it will be referenced. • New definitions are called “normative” definitions, they are an integral part of the standard. Normative text • If you claim compliance you are stating that you have implemented these clauses. Informative text • This is helpful information, you do not have to agree with it or apply it. Slide 9

ISO 8000 Quality Data that meets requirements Data that is Portable Slide 10

ISO 8000 Quality Data that meets requirements Data that is Portable Slide 10

ISO data standards are the antidote to application “lock-in” Data quality analysis app User

ISO data standards are the antidote to application “lock-in” Data quality analysis app User Application Operating system Hardware ISO 22745 ISO 8000 Portable data Data de-dup app Data validation app Quality data is portable data; it is independent of the software application and accessible by any application Slide 11

ISO 8000 Referenced in a NATO Contract Please be advised that the change request

ISO 8000 Referenced in a NATO Contract Please be advised that the change request has been fully accepted by the IPET during the IPET 2010/02 meeting this week. We will now forward the change request to the MCG and other expert teams for their approval and inclusion in Issue 5. 0 of the S 2000 M. ASD 2000 M Chapter 1 B section 3. 1 will now have the following statement, once approved by the MCG and will be published Mar 2011: The Contractor shall supply identification and characteristic data in accordance with ISO 8000 -110: 2009 on any of the selected items covered in his contract. Following an initial codification request as specified in section 3. 2, the home NCB shall present a list of the required properties in accordance with the US Federal Item Identification Guides. ASD Specification 2000 M (S 2000 M) is a standard that specifies the information exchange requirements for most materiel management functions commonly performed in supporting international projects. S 2000 M is based on a business model agreed between military customers and industry suppliers. Slide 12

ISO 8000 Referenced in a Commercial Contract The contractor, sub-contractor or supplier shall, as

ISO 8000 Referenced in a Commercial Contract The contractor, sub-contractor or supplier shall, as and when requested to do so, supply technical data in electronic format on any of the items covered in this contract as follows: The data shall be ISO 8000 -110: 2009 compliant. • The data shall comply with registered ISO 22745 -30 compliant data requirements • The data shall be encoded using concept identifiers from an ISO 22745 compliant open technical dictionary that supports free resolution to concept definitions. • The data shall be provided in ISO 22745 -40 compliant Extensible Markup Language (xml). • Providing the data necessary for the safe and efficient operation of plant and equipment is an established legal requirement in most countries. • Creating ISO 8000 -110: 2009 compliant data does not require the payment of any license fees or the use of specialized software, it is within the technical ability of all suppliers regardless of their size. Slide 13

Automating the Data Supply Chain A data provider may not have all the data

Automating the Data Supply Chain A data provider may not have all the data requested so they in turn send a request through their supply chain using the same ISO 22745 standard exchanges Sub-Tier e. OTD-q-xml Sub (query) ISO 22745 -35 Data provider Data requester Sub-Tier e. OTD-r-xml e. OTD-i-xml (data requirements statement) ISO 22745 -30 e. OTD-r-xml (reply) ISO 22745 -40 Slide 14

Distributed Data Gathering Scenarios Internet Research e. OTD-q-xml Sn Data requester e. OTD-r-xml S

Distributed Data Gathering Scenarios Internet Research e. OTD-q-xml Sn Data requester e. OTD-r-xml S 1 System integrator S 2 Manufacturer S 3 Supplier S 4 Wholesaler S 5 Company that does manual internet research S 6 Company that does automated internet research S 7 Company that sells parts data Sn Company that provides data services Third Party Master Data Slide 15

ISO 8000 Family of Standards ISO 8000 Master Data General Principles Part 1 Introduction

ISO 8000 Family of Standards ISO 8000 Master Data General Principles Part 1 Introduction Part 2 Terminology Part 110 Part 100 introduction Syntax Semantic encoding Part 120 Provenance Part 130 Accuracy Transaction data Part 140 Completeness Meets requirements Slide 16

ISO 8000 -110 Syntax Master Data Part 110 Syntax There must be one! It

ISO 8000 -110 Syntax Master Data Part 110 Syntax There must be one! It must be referenced in the data and the reference must be resolvable to the syntax, if it is not freely available the data must be labeled ISO 8000 -110: 2009 fee based encoded. EDI (ISO 9735), eb. XML, SWIFT MT, SWIFT MX, ISO 20022, e. OTD-r-xml (ISO 22745) are all acceptable syntaxes. Slide 17

ISO 8000 -110 Semantic Encoding Master Data Part 110 Semantic encoding All metadata must

ISO 8000 -110 Semantic Encoding Master Data Part 110 Semantic encoding All metadata must be explicitly defined either in an external open dictionary or the definition must be contained in the data. if it is not freely available the data exchange must be labeled as ISO 8000 -110: 2009 fee based encoded. Any defined metadata is acceptable. This includes the field, headings or attributes that are “explicitly defined” in electronic forms, spreadsheets or database tables. Slide 18

The Need for Semantic Encoding Plane Slide 19

The Need for Semantic Encoding Plane Slide 19

The Need for Semantic Encoding Robot Slide 20

The Need for Semantic Encoding Robot Slide 20

Semantic Encoding e. OTD (ECCMA Open Technical Dictionary): a registry of terminology from many

Semantic Encoding e. OTD (ECCMA Open Technical Dictionary): a registry of terminology from many sources where each concept is assigned a unique and permanent public domain identifier and where concept identifiers may be mapped to each other and ranked according to their use (ISO 22745). Slide 21

ECCMA Open Technical Dictionary (e. OTD) ISO 22745 Terminology SDO Terminology • Public domain

ECCMA Open Technical Dictionary (e. OTD) ISO 22745 Terminology SDO Terminology • Public domain concept identifiers • Free identifier resolution to underlying Terminology Industry Terminology • • • terminology (web services) Hyperlink to source standards Multilingual Multiple terms, definitions and images linked to single concept identifier Slide 22

ECCMA Open Technical Dictionary (e. OTD) Just as with music notation and engineering symbols,

ECCMA Open Technical Dictionary (e. OTD) Just as with music notation and engineering symbols, the e. OTD concept identifiers are simply used to communicate more accurately in a language independent environment. Music Engineering e. OTD A unique public domain identifier is assigned to a concept. 0161 -1#01 -089388#1 table 0161 -1#01 -086445#1 chair 0161 -1#02 -018635#1 weight 0161 -1#02 -005808#1 length 0161 -1#07 -277660#1 Monday 0161 -1#05 -001122#1 kilogram

Semantic Encoding Using ISO 22745 Class ID: 0161 -1#01 -014161#1 Property ID 0161 -1#02

Semantic Encoding Using ISO 22745 Class ID: 0161 -1#01 -014161#1 Property ID 0161 -1#02 -027375#1 0161 -1#02 -023822#1 0161 -1#02 -010200#1 0161 -1#02 -010196#1 0161 -1#02 -004968#1 0161 -1#02 -027376#1 0161 -1#02 -027378#1 Value 3225020037 1. 0 1. 450 1. 653 0. 591 10 0. 80 Measure ID 0161 -1#05 -000798#1 e. OTD Identifier Coded 0161 -1#08 -002569#1 Class Name: Bolt, Machine Property term PRODUCT NUMBER NOMINAL THREAD DIAMETER WIDTH ACROSS FLATS WIDTH ACROSS CORNERS HEAD HEIGHT COUNT PER PACK PRICE Value 3225020037 1. 0 1. 450 1. 653 0. 591 10 0. 80 Measure term INCHES e. OTD Identifiers Resolved US DOLLAR Bolt, Machine; Product Number: 3225020037; Nominal thread diameter: 1. 0 inches; Width across flats: 1. 450 inches; Width across corners: 1. 653 inches; Head height: 0. 591 inches; Count per pack: 10; Pack price: $0. 80 (M-Bolt; NTD 1. 0”; WAF 1. 45”; CPP 10) Rendered Slide 24

ISO 8000 -110 Meets Requirements Master Data Part 110 Meets requirements Requirements support a

ISO 8000 -110 Meets Requirements Master Data Part 110 Meets requirements Requirements support a business function, granting access to a computer, a website or a software program, simply asking for the data needed to deliver the right product or service, these are all data requirements. As long as the data meets the requirements it is considered quality data. Be careful what you ask for – data quality starts with the quality of the request for data Slide 25

Requirements Define Quality It is all about the requirements Quality data is data that

Requirements Define Quality It is all about the requirements Quality data is data that meets requirements nothing more – nothing less! Peter R. Benson Slide 26

What does a data requirement look like? The buyer, item manager or user as

What does a data requirement look like? The buyer, item manager or user as the data requestor defines their requirements for data: What is the item name and what characteristic data do I need? A data requirement statement is created as an e. OTD-i-xml identification guide, an XML file that conforms to ISO 22745 part 30 in which the item name is the class and the characteristic data is represented by property-value pairs What is the common name in the e. OTD ? : What data do you need to Bearing, Ball, Annular successfully accomplish a task? Data requirements are function specific, they change over time, from company to company and from function to function What do I need to know about this bearing in order to buy or manage it? This is a data requirement statement also known as an identification guide or a cataloguing template. Data requestor e. OTD-i-xml (data requirements statement) ISO 22745 -30 • • Inner Diameter Outer Diameter Width # Rows Sealing Method Load Rating Speed Rating Properties selected from the e. OTD BEARING, BALL, ANNULAR Slide 27

A Form is a Specification of a Data Requirement Slide 28

A Form is a Specification of a Data Requirement Slide 28

Bringing Your Master Data into Compliance with ISO 8000 1. 2. 3. 4. Document

Bringing Your Master Data into Compliance with ISO 8000 1. 2. 3. 4. Document your business language Map your business language to the e. OTD* Document your requirements for data* Create your Master Data Ontology* – Terminology – Data requirements – Class hierarchies 5. Measure the quality of your master data* (by comparing your data to your requirements for data) *there are low cost software tools that make this process very straight forward Slide 29