ISO TC184/SC4 Future architecture Rotterdam Progress on the Future SC4 Architecture PWI Friday 13 th November 2009

ISO TC184/SC4 Future architecture Rotterdam IDIOM - A proposal for a name I ndustrial D ata I ntegrated O ntologies and M odels

ISO TC184/SC4 Future architecture Rotterdam IDIOM workshop Overview of the IDIOM architecture Case studies –Interoperable Manufacturing Knowledge Sharing (IMKS) Formal validation of manufacturing data using Ontologies + Common Logic Agreement of summary and recommendations for future work –pilots, NWIs and SC4 Standing documents Wednesday 11 th November 2009

ISO TC184/SC4 Future architecture Rotterdam Major components

ISO TC184/SC4 Future architecture Rotterdam definitions of the concepts data model schemas data model schemas information flows process components process components process components ARM schemas analyse scope information flows AIM/MIM schemas analysis information requirements defines the data about the concepts needed to fulfil the information requirements data model schemas data model schemas implementation specification domain knowledgedomain knowledge in AAM mapping domain knowledge as reference data reference data Current ISO approach

ISO TC184/SC4 Future architecture Rotterdam reference data knowledge of the concepts reference data definitions of the concepts data model schemas data model schemas information flows process components process components process components definitions of the concepts analyse scope information flows data model schemas analysis information requirements defines the data about the concepts needed to fulfil the information requirements reference data data model schemas data model schemas implementation specification domain knowledge knowledge of the concepts (an ontology) A part of the IDIOM approach

ISO TC184/SC4 Future architecture Rotterdam Summary and recommendations for further work IDIOM objectives - why industry should spend the money –standards which are quicker and cheaper to develop and implement take advantage of new tools (especially from W3C) – already coming into SC4 tools which are already mainstream within some industry sectors –better re-use of standards greater semantic precision giving clarity on what to re-use and how links to other semantics repositories (e.g. UoMs) – using not harvesting –new capabilities tracing solutions to requirements and tracking data provenance automated design validation web enabled external views of product data repositories Structure of initial IDIOM project deliverables Technical work necessary to achieve deliverables Next steps beyond the PWI report

ISO TC184/SC4 Future architecture Rotterdam Summary and recommendations for further work IDIOM objectives - why industry should spend the money Structure of initial IDIOM project deliverables –IDIOM part 1 (so that the architecture can be used outside SC4) short like ISO IT framework describing the use of languages and technologies for industrial data an architecture for standardisation deliverables which span process models, dictionaries, ontologies, data models, and service models (c.f. AP structure) –SC4 standing document SC4 methodology – our processes for creating standardisation deliverables Technical work necessary to achieve deliverables Next steps beyond the PWI report

ISO TC184/SC4 Future architecture Rotterdam Summary and recommendations for further work IDIOM objectives - why industry should spend the money Structure of initial IDIOM project deliverables Technical work necessary to achieve deliverables –the reference data “big picture” natural language dictionary – thesaurus – catalogue – ontology interfaces between levels, representation of levels, interfaces with data models –what a mappings between an ontology and a data model actually says c.f. EXPRESS-X and mapping tables –ontologies and catalogues ontology for the entities in a catalogue model ontology for the instances of a catalogue model Next steps beyond the PWI report

ISO TC184/SC4 Future architecture Rotterdam Summary and recommendations for further work IDIOM objectives - why industry should spend the money Structure of initial IDIOM project deliverables Technical work necessary to achieve deliverables Next steps beyond the PWI report –letter ballot of PWI report –an IDIOM project – a permanent team work on “initial IDIOM project deliverables” – NWI + SC4 standing document –from IDIOM methodology to IDIOM content discussions with AP 242 team ontologies to provide external views of AP 209 edition 2 content OWL or CL representation of OntoML content program for exposure of core SC4 concepts –ISO (especially 41) – e.g. product –ISO and – e.g. key concepts in part ontologies –fundamental concepts in geometry (ISO and ISO ) –PSL, AP 233 SysML

ISO TC184/SC4 Future architecture Rotterdam Summary of the summary IDIOM objectives - why industry should spend the money –new technologies mean faster cheaper standardisation and implementation; better use of content developed elsewhere; better quality and new capabilities through greater semantic precision Structure of initial IDIOM project deliverables –IDIOM part 1 – how to use the new technologies (for us and for other standardisation communities); SC4 procedures Technical work necessary to achieve deliverables –road map on how to represent, manage and use reference data (dictionaries, thesauri, catalogues, ontologies) alongside data models Next steps beyond the PWI report –an IDIOM project to produce the initial deliverables –create IDIOM content, which means winning “customers” within SC4 and outside