1. Common Conceptual Object Model (CCOM) Dr. Avin Mathew Technical Director MIMOSA

2. CCOM is… An object-oriented, data exchange model for the operations and maintenance of complex machinery Released as part of the OSA-EAI Designed/documented as UML Implemented in XML Schema as CCOM-ML Employed in interoperability scenarios as CCOM BODs 2

3. OSA-EAI Based Upon 5-Layer ISO 13374-2 Open Information Architecture Requirements OSA-EAI V3.2.3 Information Architecture Common Conceptual Object Model (CCOM) UML Class Model CRIS Markup Language (CRIS-ML) Persistence Model in XML Schema CRIS-ML Reference Data Library Terminology Dictionary CRIS-ML Document XML Schema CCOM Markup Language (CCOM-ML) Object Model in XML Schema CCOM-ML Reference Data Library CRIS-ML Document Client/Server Transactions CRIS-ML Atomic Data Client/Server Transactions CCOM-ML ISBM Business Object Document Transactions (finalizing in 2012) Tech-CDE Document SOAP Client/Server Tech-XML Atomic Data SOAP Client/Server CCOM-ML ISBM Business Object Document Producer / Consumer Tech-Doc XML Document Producer / Consumer CCOM-ML Document XML Schema CCOM-ML XML Document Producer / Consumer CRIS UML Class Model

4. MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI) The MIMOSA Open Object Registry Is a Core O&M Interoperability Enabler for Asset Intensive Industries. It provides a full mesh network for maintaining interrelationships between people, processes and systems in a Services Oriented Architecture. Unlike traditional Master Data Management (MDM), it is designed to support the highly dynamic requirements of physical asset management such as configuration management.

5. Incorporation of Other Standards Use UUIDs (ISO 9834-8) 5

6. UUIDs xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 36 characters (32 hexidecimal, 4 hypens) 550e8400-e29b-41d4-a716-446655440000 6

7. Incorporation of Other Standards Use UUIDs (ISO 9834-8) Use UN/CEFACT XML Schema naming conventions Use UN/CEFACT Core Component Types (CCT) 7

8. UN/CEFACT CCT 8

9. Object Registry Management Metadata, Registry and Current/Historical Configuration for: –O&M Classes/Types and Taxonomies –Functional Segments, Breakdown Structures, Networks –OEM Model and Nameplate Specs –Physical Assets with Segment Installation –Measurement Locations and Regions –Geospatial Tracking 9

10. Basic Data and Metadata Entity + GUID: UUID [0..1] + IDInInfoSource: cct:IDType [0..1] + RegistrationInfoSource: ccom:InfoSource [0..1] + Tag: cct:TextType [0..1] + Name: cct:TextType [0..1] + Created: ccom:UTCDateTime [0..1] + Creator: ccom:Agent [0..1] + LastEdited: ccom:UTCDateTime [0..1] + LastEditor: ccom:Agent [0..1] + LastUpdatedInfoSource: ccom:InfoSource [0..1] + Status: cct:CodeType [0..1] + GUID: UUID [0..1] + IDInInfoSource: cct:IDType [0..1] + RegistrationInfoSource: ccom:InfoSource [0..1] + Tag: cct:TextType [0..1] + Name: cct:TextType [0..1] + Created: ccom:UTCDateTime [0..1] + Creator: ccom:Agent [0..1] + LastEdited: ccom:UTCDateTime [0..1] + LastEditor: ccom:Agent [0..1] + LastUpdatedInfoSource: ccom:InfoSource [0..1] + Status: cct:CodeType [0..1] 10

11. Functional Segments Identifies a functional area/location in an enterprise Could be an entire site or base maintainable unit 11

12. Models Identifies a class of a manufacturer’s products (make-model, manufacturer part) 12

13. Equipment Assets Tangible object that can be: –Depreciated in a financial system –Assigned a serial number –Transferred/sold and installed/utilized on a Functional Segments (possibly at another enterprise) Could be entire facility, platform (e.g. vehicle) or a component (e.g. bearing) 13

14. Types and Taxonomies A Type designates a sub- type/class for an object Taxonomies specify super and sub class relations between Types Can reference other reference data libraries (e.g. ISO 15926) and integrate discipline standards (e.g. ISO 14224, IEC 61360) Asset Type Taxonomy - Asset - Mechanical Device - Motor - Motor, AC - Motor, DC 14

15. Types 15

16. Data Sheets Functional Segments can be associated with data sheets to specify functional requirements Models can be associated with data sheets to specify characteristics of equipment of that model Equipment Assets can be associated with data sheets to specify characteristics of that equipment Segment and Asset Types can have data sheet templates to support class libraries 16

17. Data Sheets 17

18. Data Sheets 18 AttributeType Measure

19. Asset Install/Remove 19

20. Breakdown Structures 20

21. Mesh Networks/Topologies 21

22. PRODML Flow Model Example Network = Segment Mesh Unit = Segment (Production Header Segment Type) Port = Segment (Fluid Inlet Port Segment Type)Node = Segment Connection

23. Measurement Locations and Regions 23

24. Geospatial Tracking 24

25. CCOM and Use Cases 25

26. MIMOSA CCOM BODs Based on OAGIS BOD structure Message metadata, e.g. Message ID Timestamp Sender Signature How to interpret the Noun, e.g. Sync Get/Show Confirm 26

27. Registry-Related CCOM BODs BOD typeVerbs AssetDefinitionGet/Show/Sync ModelDefinitionGet/Show/Sync MeasurementLocationDefinitionGet/Show/Sync SegmentDefinitionGet/Show/Sync EngineeringDiagramSync SegmentHierarchySync CurrentAssetInstallOnSegmentGet/Show CurrentSegmentWhereAssetInstalledGet/Show AssetInstallSync AssetRemoveSync 27

28. OpenO&M ISBM Defines the minimum set of functions for a message service: –Messaging Patterns (pub/sub, request/response, async notifications) –Message Routing (channels, topics) –Message Content (XML) –Security (WS-Security tokens) –Services (WSDL)

29. BODs and ISBM Correlation between BOD type and ISBM messaging model: –Sync used with Publish/Subscribe –Get/Show used with Request/Response 29

30. Structural Digital Asset Interoperability Registry Support REG-STRUCTURE, REG-ASSET, REG-PRODUCT systems in OGI Use Cases Support OpenO&M ISBM for data communications Share data using MIMOSA CCOM BODs Support OpenO&M CIR for object identifier mapping