1. Final Report on Harmonization of MFI & MDR Hajime Horiuchi hori@tiu.ac.jp May. 2011 SC32WG2 N 1533 OpenForum 2011 & SC32WG2 Meeting, May 2011, Kona, Hawaii

2. Company Logo Overview of the Study The study project on the harmonization of MDR & MFI was initiated at the Jeju meeting (2009.06) and it was extended one more year at the Kunming meeting(2010.06) This is the final report on the study. Some recommendations were made. However, it is premature to develop documents as the Reference model or the Framework for both MFI & MDR

3. Company Logo History of MDR &MFI 19972000 20052010 MDR 1,2,3,4,5,6 MDR ed.2 1,2,3,4,5,6 MFI 2,4 MFI 5 MFI6 MFI7 MDR 3-ed.3 20944 MFI 1 MFI3-ed2 MFI8 TR MFI project started (2003.05) ED2 MFI3 SC14 SC21 WG3 MFI 10,11 JTC1 SC32 Formulated NWI

4. Company Logo Current MFI Structure ISO/IEC 19763-1 : Metamodel framework for interoperation Part-1: Reference model Part-2: Core model  Part-3: Metamodel for ontology registration Part-4: Metamodel for model mapping  Part-5: Metamodel for process model registration Part-6: Registration Procedure Part-7: Metamodel for service registration Part-8: Metamodel for Role & goal registration Part-9: On demand model selection (TR) Part-10: Core model and basic mapping Part-11: Advanced model mapping

5. Company Logo Current Status Basic attribute Data Elements (E1) IRDS (SC14) (SC21WG3) MDR-3 MDR-3 (E3) MFI-1 MFI-2&4 MFI-3(E1) (2003) MFI-3 (E2) MFI-6 MFI-7 MFI-8 MDR-1 (MDR-1(E2)) MFI-9 MFI-10 MFI-5 1997 (MFI-1(E2)) MDR-6(E2) MDR-2MDR-6MDR-4MDR-5 XXX-X : WD XXX-X : Published XXX-X : CD (E2) XXX-X : Expected MDR MFI

6. Company Logo MFI structure at the beginning MFI-2 MFI-3MFI-4 MFI-1 Core model Ontology registration Model mapping registration Reference model AS of May 2003 ISO/IEC 19763 : Metamodel framework for Interoperability (MFI)

7. Company Logo Current Part Relationship in MFI Administered Item Part-3Part-5 Part-7 Part-1 Part-8 Part-6 Part-9(TR)Part-11 Part-10 Registration Procedure Reference Model Ontology Business ProcessWeb service Role & GoalAdvance Mapping Core & Basic Mapping ODMS

8. Company Logo Concept Modeling Constructs Modeling Facility M3 Level M2 level M1 level M0 level Core Model MFI Values Common Data Element Object Patterns Metamodel Model Real World inherit refer Govern use Metamodel MOF Metameta model Original Idea of MFI

9. Company Logo Original Motivation of ISO/IEC19763(MFI) standards 9 Heterogeneous Registries Registry Interoperation Registry ROR ManufacturingLogisticRetails Registry ROR: Registry of Registry SC32 Seoul 020506 4 PDES/STEP Registry Manufacturing ebXML Registry UDDI Component Registry GCI Registry EAN Registry CPFR Registry RosettaNet Registry Business Negotiation Vender Catalog Shipper Catalog Business Category Shipping Customer Support Consumer Profile CALS Production Planning & Procurement System Development 11179 Registry

10. Company Logo BuyerSellerBuyerSeller Industry Domain AIndustry Domain B Registry Metamodel Registry Metamodel Metamodel Registry MMF Core Model MMF for Model Mapping Register Meta Model Frameworks Refer describe Mapping Business describe Register Expected Solution by MFI (2003)

11. Company Logo So Many different Views to Metamodel Framework !!

12. Company Logo Early Registration Concept (MMF 2005)

13. Company Logo Model Registration Concept (1) Model Metamodel (UML) Common Metamodel Model Metamodel (ER) Register Collect well-known metamodels Register individual models with normative administrative information Benefit: Make model mapping make easy MFI Registry Model Repository order Cust Collection & Register Target Model Metamodel (UML) orderr Cust

14. Company Logo Model Registration Concept, Today Model Metamodel (UML) Common Metamodel Model Metamodel (ER) Registering Investigate and define common abstracted modeling contracts as Metamodel Register individual models with normative administrative information MFI Registry Model Repository order Cust abstraction Target Model

15. Company Logo Common Metamodel MFI Registry Administered_Ite m Registry entryIdentification Naming Registration Authority Model representation Following Common Metamodel Model Registration Concept (2) order Cust Target model Order: Cust:

16. Company Logo Registrar, Registration Authority, Stewardship Expanding of register targets 16 Data Element Target ObjectObject Constructs DEC, CD, VD Model Compnents Concept Ontology components Service Components Codes Terminology Model Ontology/ Concept System Service References Identification Designation Scheme Classification Scheme Administered Item Outer Registry Role & Goal

17. Company Logo Service Registry Information Semantic Registry DD/DS Metadata Registry Market Requirements Sharing of knowledge Sharing of Methodology Sharing of Data Sharing of Software Discover & Casting Web Service ROR Cross Domain Interoperation Cloud Interoperation

18. Company Logo Diversity of the needs to MFI MFI Model Sharing (Level1, Level2) Semantic Interoperation Software Components Sharing Cloud Computing Registry Interoperation Model Mapping & Transformation Service Discovery & Sharing

19. Company Logo Evolution of MDR & MFI (1) 19 Common Administration Information Metadata Registration Model Registration “Common Facility” for both MDR & MFI ISO/IEC11179 Edition 2 MOF (ISO/IEC19502) ISO/IEC11179 Edition 1 Data Elements SC14 IRDS (ISO/IEC 10728) MOF (OMG) ISO/IEC19763 ISO/IEC11179 Edition 3

20. Company Logo Possible Integration Registration Procedure, Administer Item, Basic Types, Naming, Identification, Registry Summery Models Ontology Services Role & Goal Data Elements Concept MDR(11179) MFI (19763)

21. Company Logo Recommendation Recommendations

22. Company Logo RECOMMENDATION 1 Define “Common Facility” for both MDR & MFI Recommendation-1

23. Company Logo MDR/MFI Registration Common Core Package 23 Namespace Registry Authority Registrar Administered_Item Stewardship_Record Submission_Record Registration _Record Registration Identification Designation & Definition MDR/MFI Registration Core Package Contact Date-and Time Individual Language_Id Organization Phone_Number Postal_address Registration A_ID Basic Registry profile From ISO/IEC 11179 ED3 ISO/IEC 11179-3 Ed3 use

24. Company Logo Recommendation 2 MFI-6 (Registry summery ) should be integrated in MDR-6 (Registration Procedure). MFI-6 should be with drawn (Japan NB position). Title of ISO/IEC11179-6 could be “MDR/MFI registration procedure”.

25. Company Logo MDR/MFI-6 package (Registration) 25 Namespace Registry Authority Registrar Administered_Item Stewardship_Record Submission_Record Registration _Record Registration Identification Designation & Definition > MDR/MFI Registration Core Package Contact Date-and Time Individual Language_Id Organization Phone_Number Postal_address Registration A_ID Basic MFI Registration Process Registry Profile Lifecycle Process (Service) Registration of Model (Service) Registration of Ontology (S) Registration of Service (S) Registration of Goal & Role (S) Registry Common Process MDR/MFI -6

26. Company Logo ROR Collection of RS(Registry Summery) RS is a simple artifact that describes own registry to enable registry discovery Model Registry RS Ontology Registry RS Model Registry RS ROR

27. Company Logo Metamodel for Registry Summery

28. Company Logo Where RORs were located Find Service Establish collaboration Use Service (Interchange ) ROR Model registry Ontology registry Metadata registry Model registry Metadata registry Metadata registry ROR Within a organization Within a industry Ontology registry

29. Company Logo Recommendation 3 Initiate a project to develop a common reference model or framework that defines overall architecture of both MDR & MFI Expected MDR-1 and MFI-1 should be integrated

30. Company Logo Recomendation Basic attribute Data Elements (E1) IRDS (SC14) (SC21WG3) MDR-3 MDR-3 (E3) MFI-1 MFI-2&4 MFI-3(E1) (2003) MFI-3 (E2) MFI-6 MFI-7 MFI-8 MDR-1 MDR-1(E3) MFI-9 MFI-10 MFI-5 1997 MFI-1(E2) MDR-6(E2) MDR-2MDR-6MDR-4MDR-5 XXX-X : WD XXX-X : Published XXX-X : CD (E2) To be initiated

31. Company Logo Recommended MDR/MFI Registration Core Package MFI-10 MFI-3(E2) MFI-5 MFI-7 MDR/MFI- 1 MFI-8 MDR/MFI- 6 MFI-9(TR) MDR/MFI Common Facility Registry Architecture SOA Architecture MDR- 3(E3) OntologyProcessService Role & Goal Registry Core

32. Company Logo Goal of Harmonization Model Registry Service Registry Role & Goal Registry Metadata Registry Ontology Registry Process Model Registry MDR-3 Ed3 MDR/MFI Registration Procedure MFI-10 MFI-3MFI-5 MFI-7MFI-8 MFI-9: On Demand Selection (TR) TR Part-1 ISO/IE C 24706 ISO/IE C 20944 ISO/IE C 24707 ISO/IEC 20943 (TR) MDR/MFI Reference Model ROR Registries RS

33. Company Logo the Architecture Establish an architectural framework to be referred in the future standardization activities in the ISO/IEC SC32. The architecture should provide a structural view of related standards, showing an information sharing infrastructure where each standard to be located, in order to increase the high level and smooth sharing of data, information and models through the registrations in the coming new paradigm such as the Cloud computing or the Grid computing. The exchanging of data, information and models should be supposed to be done through the Web services.

34. Company Logo Architecture Issues

35. Company Logo New MFI Structure New Architecture for Registry Interoperation

36. Company Logo Registry Architecture Types 36 Domain Specialty Diversity of Stakeholder SOS ProcessContents SOA/SaaS limited Alliance High (Narrow) ROR Cross Industries Metadata Dependent (Non Structural) Model Dependent (Structural) Low (Generic) High Target of the Standardizations System of Systems Registry Of Registries Cross Homes 10 2 10 8

37. Company Logo Registry to Support Engineering 37 Domain Specialty Diversity of Stakeholder SOS SOA/SaaS limited Alliance High (Narrow) ROR Cross Industries Metadata Dependent (Non Structural) Model Dependent (Structural) Low (Generic) High System of Systems Registry Of Registries Cross Homes 10 2 10 8 Registry to support Engineering

38. Company Logo Registry for Discovery 38 Domain Specialty Diversity of Stakeholder SOS SOA/SaaS limited Alliance High (Narrow) ROR Cross Industries Metadata Dependent (Non Structural) Model Dependent (Structural) Low (Generic) High System of Systems Cross Homes 10 2 10 8 Registry for Discovering

39. Company Logo System Engineering Architecture SOSE IEEE1471 SysML(Profile) MARTE AUTOSAR SPEM QoS Functional Security 39 IEEE1471

40. Company Logo Required Architecture Industrial Requirements New Architecture for Registry Interoperation StakeholdersTechnologies Security/ Dependability Problems to be solved SOA, Cloud Computing Inter Enterprises Collaboration

41. Company Logo Needs for Architecture Service UDDI MD Registry MD Registry MD Registry MD Registry Metadata Registry MFI Registry MFI Registry MFI Registry ROR UDDI Data SemanticsModel & Information Semantics Customized collection of registry summery Service Process Cloud

42. Company Logo Registry Service Integration Architecture 2009/6/1842 User Catalogue Information Service Interface Specification Metadata used by Service RaaS Registry Service Platform (J-SaaS) Service Platform (SFDC) S1S1 S2S2 S4S4 S3S3 Reference ROR Service Registry Service enjoy Service lookup ★ :Components to be standardized ★ ★ ★ ★ ★ Service Integrator Service Platform ★ S n : Service Registry Service Federation Service Profile Specification in the Registry Interface Specification between Service Integrator and Platform Interface Specification between Service Registry and Service Integrator

43. Company Logo Actions to be needed Common facility should be used in the next edition of each part or parts in the WD stage of both MDR & MFI. Integrate MFI-6 (Registry summary) into MFI-6 (MFI-6 should be withdrawn) MDR-1 & MFI-1 Integration project should be initiated

44. Company Logo Time line Extension of the harmonization study period for one year. WD MFI-1 ED2 should be submitted to the next interim meeting (Authorization should be done at the next SC32 meeting ) In the future, both MDR/MFI should be merged to one series of standard, (ex. ISO/IEC 11179)

45. Company Logo THANK YOU