Common Conceptual Object Model CCOM Dr Avin Mathew

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

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

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

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.

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

UUIDs xxxx-xxxx-xxxxxxxx 36 characters (32 hexidecimal, 4 hypens) 550 e 8400 -e 29 b-41 d 4 -a 716 -446655440000 6

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

UN/CEFACT CCT 8

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

Basic Data and Metadata Entity + + + GUID: UUID [0. . 1] IDIn. Info. Source: cct: IDType [0. . 1] Registration. Info. Source: ccom: Info. Source [0. . 1] Tag: cct: Text. Type [0. . 1] Name: cct: Text. Type [0. . 1] Created: ccom: UTCDate. Time [0. . 1] Creator: ccom: Agent [0. . 1] Last. Edited: ccom: UTCDate. Time [0. . 1] Last. Editor: ccom: Agent [0. . 1] Last. Updated. Info. Source: ccom: Info. Source [0. . 1] Status: cct: Code. Type [0. . 1] 10

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

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

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

Types and Taxonomies • A Type designates a subtype/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, AC - Motor, DC 14

Types 15

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

Data Sheets 17

Data Sheets Attribute. Type Measure 18

Asset Install/Remove 19

Breakdown Structures 20

Mesh Networks/Topologies 21

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

Measurement Locations and Regions 23

Geospatial Tracking 24

CCOM and Use Cases 25

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

Registry-Related CCOM BODs BOD type Verbs Asset. Definition Get/Show/Sync Model. Definition Get/Show/Sync Measurement. Location. Definition Get/Show/Sync Segment. Definition Get/Show/Sync Engineering. Diagram Sync Segment. Hierarchy Sync Current. Asset. Install. On. Segment Get/Show Current. Segment. Where. Asset. Installed Get/Show Asset. Install Sync Asset. Remove Sync 27

Open. O&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)

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

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