1 / 55

Abstract

dillan
Télécharger la présentation

Abstract

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Work is underway to explore the application of ISO 11179 to the Electronic Commerce Code Management Association (ECCMA) Open Technical Dictionary (eOTD). The eOTD will be registered under ISO 22745, a standard being developed within TC184/SC4 to define the requirements for Open Technical Dictionaries. The eOTD is a collection of terminology from consensus organizations designed to support a central, public domain dictionary of cataloging concepts used to create unambiguous, language independent descriptions of individuals, organizations, locations, goods, and services. The eOTD contains property names and definitions that are the key to creating unambiguous descriptions. Essentially, every person, organization, location, and all goods and services can be described using property-value pairs. These “data labels” are the properties that are defined in the eOTD. Good progress is being made on 22745 and the eOTD has evolved considerably, particularly as a vehicle for free open resolution of terminology and as a tool for terminology harmonization. The eOTD effort is working with 11179 as the metadata registry model and has been working with TC37 to refine some of the terminology representation. There are now some wide-scale implementations of the eOTD in the mining industry, NATO is promoting it as their bridge to industry, it is being incorporated into the DoD EMALL and Boeing is promoting it in the aerospace industry, so the eOTD is making steady progress. Abstract

  2. ISO TC184/SC4 ECCMA Open Technical Dictionary ISO 22745 Cataloguing module for ISO 10303 ISO 8000 Relationship to ISO/IEC 11179 Conclusions Outline

  3. ISO TC184/SC4

  4. Standardization in the field of industrial automation and integration concerning discrete part manufacturing and encompassing the application of multiple technologies, i.e. information systems, machines and equipment, and telecommunications. ISO TC184 Scope

  5. ISO/TS 8000, Catalogue management systems – Requirements ISO 10303, Industrial automation systems and integration – Product data representation and exchange ISO 13584, Industrial automation systems and integration – Parts library ISO 15531, Industrial automation systems and integration – Industrial manufacturing management data ISO/PAS 16739, Industry Foundation Classes, Release 2x, Platform Specification (IFC2x Platform ISO 15926, Industrial automation systems and integration – Integration of life-cycle data for process plants including oil and gas production facilities ISO 18629, Industrial automation systems and integration – Process specification language ISO 18876, Industrial automation systems and integration – Integration of industrial data for exchange, access and sharing ISO/PAS 20542, Industrial automation systems and integration – Product data representation and exchange – Reference model for systems engineering ISO/PAS 22720, ASAM Open Data Services 5.0 ISO/TS 22745, Industrial automation systems and integration – Open technical dictionary ISO/PAS 26183, SASIG Product data quality guidelines for the global automotive industry TC184/SC4 Standards

  6. Metamodel and Infrastructure ISO 10303-11 EXPRESS information modeling language ISO 10303-2x series: implementation methods for EXPRESS data, including metamodel of EXPRESS ISO 13584-26: model dictionary, CAD parts library, catalog ISO 15926-2: general integration model ISO 18876: guidelines for mapping and integration of models ISO 22745: dictionary, identification guide and catalog models TC184/SC4/N1977, guidelines for the development of mapping specifications Content ISO 10303-221: AP with standard reference data in 15926 format ISO 10303-233, 239: APs with standard reference data in OWL format ISO 13584-5xx series: standard dictionaries for mechanical components ISO 15926-4 Reference Data Library (RDL) for process industries Some SC4 Documentsof Interest to Metadata Researchers

  7. STEP • ISO 10303, "Standard for Exchange of Product Model Data" • Many different manufacturing fields • Application protocols (APs) • AP 209 Design Through Analysis of Composite and Metallic Structures • AP 210Electronic Printed Circuit Assembly, Design and Manufacturing • AP 218Ship Structures • AP 224Mechanical Product Definition for Process Planning • Using common metamodel (Integrated Resources [IR]) • The ultimate goal is for STEP to provide a means of describing product data through the life cycle of a product that is independent of any particular computer system

  8. STEP's goal is to represent all technical information about a product Product representation Process to make the product Material properties Process inputs (stock) Tolerances Assembly Maintenance … One of the new areas is Product Life Cycle Support (PLCS) Data not so much related to the manufacturing process, but related to the “maintaining-in-service-life” , usage and disposal processes AP 239 (directly stemming from the CALS initiative and NATO Product Data Model) STEP

  9. ECCMA Open Technical Dictionary

  10. The ECCMA Open Technical Dictionary (eOTD) is an open technical dictionary of cataloging concepts used to create unambiguous language independent descriptions of individuals, organizations, locations, goods and services.

  11. "The extraction, interpretation and validation of information in accordance with defined policies and procedures to satisfy a request for information." Building a representation that allows a potential user to easily find items that meet a given set of requirements The compilation and maintenance of primary information by systematically describing objects in the collection, and the arranging of this information into an object catalog record. [http://www.willpowerinfo.myby.co.uk/cidoc/guide/guideglo.htm] The systematic organization of information, data, or materials so that they can retrieved when the requester needs them. Cataloging follows rules and practices to enable users to understand the system... [http://home.earthlink.net/~ddstuhlman/defin1.htm] What is Cataloguing?

  12. Class Property Feature Representation Unit of Measure Qualifier of Measure Property Value Currency Concept Types

  13. Class bolt:machine bearing:plain:self-aligning Property thread series designator thread diameter Feature flange inner liner outer ring second hole Representation string decimal measure rational measure Unit of Measure degree radian kilogram newton per square millimeter Qualifier of Measure nominal minimum maximum Enumerated Property Value Monday Tuesday iron Currency US Dollar Euro Examples of Concepts

  14. Catalogue Data Machine Bolt; 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 Rendered • Property ID Value Measure ID • 0161-1-02-0468980161-1-07-014684 • 0161-1-02-0273753225020037 • 0161-1-02-0238221.00161-1-05-000798 • 0161-1-02-0102001.4500161-1-05-000798 • 0161-1-02-0101961.6530161-1-05-000798 • 0161-1-02-0049680.5910161-1-05-000798 • 0161-1-02-02737610 • 0161-1-02-027378 0.80 0161-1-08-000168 eOTD Coded Property term Value Measure termeOTD CLASS NAMEBOLT:MECHANICAL PRODUCT NUMBER 3225020037 NOMINAL THREAD DIAMETER 1.0INCHES WIDTH ACROSS FLATS 1.450INCHES WIDTH ACROSS CORNERS 1.653INCHES HEAD HEIGHT0.591INCHES COUNT PER PACK 10 PACK PRICE 0.80 US DOLLAR XML Identifiers Resolved eOTD

  15. Lower the cost and increase the quality of cataloging items of supply and production by facilitating cataloging at source Goal

  16. The eOTD development approach is driven by empirical analysis of millions of catalogue records, including NATO, mining industry and office supplies An important consideration is upward compatibility with existing government and commercial cataloguing systems Catalogue representation is extensional– intended to represent real items of supply and production Approach

  17. Cataloguing at source: The supplier creates and delivers eOTD-compatible cataloguing data along with product technical data STEP APs as the delivery mechanism for both product technical data and cataloguing data XML catalogue format available as well Data representation: The explicit representation of the catalogue data as property-value pairs using eOTD tags for concepts Key Ideas

  18. Terminology Terminology Terminology Terminology Terminology SDO Terminology eOTD Concept Registry (metadata registry) SDO Terminology SDO Terminology • Public domain concept identifiers • Free identifier resolution to underlying terminology (web services) • Hyperlink to source standards • Multilingual • Multiple terms, definitions and images linked to single concept identifier GSA-IAE Terminology

  19. Concepts identified by a globally unambiguous code Items described with codes for properties, property values, representations, qualifiers, etc., that are recognized by the receiver’s supply system All properties required by the receiver to describe an item based on the item class must be present Unambiguous Description

  20. Data Architecture Identification Scheme has conceptsidentified by is coded using concepts in Catalogue Dictionary conformsto theconstraints in constrains the use of Identification Guide

  21. Catalogue Catalogue eOTD Dictionary Dictionary Identification Guide Identification Guide Data Architecture Data Model (UML) Exchange Format (XML Schema)

  22. A concept may have multiple terms and definitions

  23. eOTD • The eOTD is meta-information: terminology used to describe individuals, organizations, locations, goods and services. • The ECCMA Stock Number Registry (ESNR) contains the product information itself.

  24. UML conceptual model definitionMarkup attribute contains XML markup XML exchange format Dictionary Model

  25. Constrains the use of the eOTD dictionary in catalogue data to meet the needs of a specific buyer or group of buyers Developed and maintained by buyers Registered with and validated by ECCMA Subsumes Item Identification Guides (IIGs) used within the NATO Codification System Identification Guide (IG)

  26. Identification Guide Dictionary Prescribed header Prescribed property Property-id = 04 Representation = 02 Prescribed property Property-id = 05 Representation = 01 ... ...

  27. Identification Guide Dictionary Prescribed header Prescribed property Property-id = 04 Representation = 02 Prescribed property Property-id = 05 Representation = 02 Prescribed property Property-id = 07 Representation = 01 Prescribed property Property-id = 08 Representation = 01 ... ... ...

  28. Globally Unique Identifier 0161-1 nn nnnnnn Concept Code Concept Type Code Organization identifier, compliant with ISO 6523, Information technology — Structure for the identification of organizations and organization parts

  29. An IG does not contain its own set of identifiers A catalogue references concept identifiers from the dictionary, not the IG An IG is not needed to decode a catalogue An IG is needed to create a catalogue that meets a buyer’s requirements Referencing

  30. ISO 22745

  31. Part 1: Overview Part 10: Dictionary representation Part 11: Guidelines for the formulation of cataloging terminology Part 13: Identification of concepts and terminology Part 14: Dictionary query interface Part 20: Procedures for the maintenance of an Open Technical Dictionary Part 30: Identification guide representation Part 40: Catalogue representation Part 50: Structure and operation of the Registration Authority Part 200: Implementation guide for incorporating cataloguing information into ISO 10303 product data Planned Parts

  32. Harmonization of terminology is outside the scope of ISO 22745 ISO 860 is referenced The eOTD will be a powerful tool to facilitate harmonization because of the large amount of terminology loaded, and its free and open access Maintenance processes are defined in 22745-20 to allow addition of terminology to a concept, merger of concepts, etc. Harmonization

  33. Common dictionary XML schema and Web services interfaces being developed Will be published as a separate standard – no number assigned yet Will be tailored within 22745 and 13584 Relationship Between ISO 22745and ISO 13584

  34. Cataloguing Model for ISO 10303

  35. Simple catalogue representation as property-value pairs with features Allows reference to external dictionary for class, property, feature, non-SI unit of measure, enumeration value Compatible with any dictionary of classes and properties (OTD, PLIB, Oil&Gas, etc.) 22745-200 will provide guidance for use of this module with ISO 22745 dictionaries Targeted for inclusion in AP 203 ed 2 DIS Simplified cataloguing module, 10303-1137

  36. Linking from STEP File to Dictionary STEP File Dictionary Class, Property, Feature, Representation, Unit of Measure, Qualifier of Measure, Property Value, or Currency Concept Entry term Concept Identifier term term definition definition definition Class, Property, Feature, Representation, Unit of Measure, Qualifier of Measure, Property Value, or Currency Concept Entry term Concept Identifier term term definition definition definition

  37. Catalogue Data property_id part_version property_value string value property_id property_value string value property_id property_value string value property_id property_value string value

  38. ISO 8000

  39. Data Quality Problems Due to Poor Data Quality Sources of Data Quality Problems • Extra time to reconcile data • Loss of credibility in a system • Extra costs • Customer dissatisfaction • Delay in deploying a new • system • Lost revenue • Compliance problems • Data entry by employees • Changes to root/source • systems • Data migration or conversion • projects • Mixed expectations by users • External data • System errors • Data entry by customers

  40. Background The value of information is dependent on, (1) its relevance (fit for the purpose), (2) its currency (timeliness), (3) its accuracy and (4) its accessibility (ease of use). This standard recognizes that there is a need to allow the intended recipient of information (typically a buyer) the ability to define their data requirements in terms of the standards to be used for data encoding (syntax and semantic encoding) and for defining completeness. This standard also recognizes that the provider of the information (typically a supplier) may wish to provide an assurance of accuracy (representations, certifications, and warranties) and that this can be validated (certified) by an independent third party. While compliance with encoding and completeness can be validated programmatically, assertions of grades of accuracy are covered by authoritative representations, certifications and warranties at the organizational level.

  41. Minimum encoding requirements Labeling: Each data element must be tagged using a globally unique identifier that can be resolved to its terminology through a free (anonymous) internet interface. Originating and cataloging organizations: The originating and cataloging organizations for each data element must be identified using globally unique identifiers that can be resolved to contact information through a free (anonymous) internet interface. Origination and cataloging date The origination and cataloging date of each data element must be specified. Fundamental Requirementsof ISO 8000

  42. Relationship between ISO 8000 and ISO 22745 • The labeling requirements of ISO 8000 should be amended to read: "each data element must be tagged using a globally unique identifier that can be resolved to its terminology through a free (anonymous) internet interface. An example of this would be ISO 22745-14 or any other terminology resolution standard”

  43. Relationship between ISO 8000 and ISO 22745 It is recommended the following wording be included: 1. ISO 8000 compliance requires that a standard data model is used for encoding. Examples of these include ISO 22745-10. ISO 13584-42/25, 15926-2, ISO 9735, ISO 15000. 2. ISO 8000 shall state that there be a clearly defined data requirement standard against which the data can be programmatically tested for compliance. Examples of this include ISO 22745-30 Identification Guide and ISO 13584-511 Fasteners or an UN/CEFACT IMPDEF message

  44. Information quality at the level of the organization Assessment of the level (grade) of information management capabilities Requirements of ISO 8000

  45. Relationship to ISO/IEC 11179

  46. ISO 22745-10 is intended to be compatible with ISO/IEC 11179-3 ISO 22745-11 implements ISO/IEC 11179-4 and -5 Links between Standards

  47. 22745 separates dictionary and IG, 11179 not clear Use of term "concept" Inheritance from Administered_Item In eOTD, Administered_Item is in a separate private schema, not part of the 22745 standard Standardized implementation methods (e.g., Web services, exchange file formats) Need standard resolution services Conformance requirements Aggregates, complex data types Issues

  48. Different sets of administered items Issues 11179 Classification_Scheme Conceptual_Domain Data_Element Data_Element_Concept Derivation_Rule Object_Class Property Value_Domain 22745 Class Property Feature Representation Unit of Measure Qualifier of Measure Property Value Currency

More Related