Presentation is loading. Please wait.

Presentation is loading. Please wait.

September 2008 1 MIMOSA Open System Architecture for Enterprise Application Integration (OSA-EAI) Primer September 2008 Ken Bever MIMOSA CTO/Technical.

Similar presentations


Presentation on theme: "September 2008 1 MIMOSA Open System Architecture for Enterprise Application Integration (OSA-EAI) Primer September 2008 Ken Bever MIMOSA CTO/Technical."— Presentation transcript:

1 September MIMOSA Open System Architecture for Enterprise Application Integration (OSA-EAI) Primer September 2008 Ken Bever MIMOSA CTO/Technical Director Principal Consultant, Assetricity LLC AMRDEC Software Engineering Directorate

2 September Goals of Training ►Fundamental understanding of the breadth and depth of the MIMOSA specifications ►Provide sample database and tools for further exploration/study ►Target audience: –Technical Program Managers –Software/System Integrators –Software Developers

3 September Oil&Gas Industry Asset Management Data Integration Challenges ►Extremely complex platforms with many components ►Overwhelming data volumes ►Multiple data “languages” –Multiple formats of data from a variety of systems –Vendors promote their proprietary data standard as the optimal for a specific application

4 September Oil&Gas Industry Asset Management Data Integration Challenges ►Extremely complex, constantly moving assets of various types ►Overwhelming data volumes ►Multiple data “languages” –Multiple formats of data from a variety of systems –Vendors promote their proprietary data standard as the optimal for a specific application

5 September Oil&Gas Industry Asset Management Data Integration Challenges ►Extremely complex, constantly moving assets of various types ►Overwhelming data volumes ►Multiple data “languages” –Multiple formats of data from a variety of systems –Vendors promote their proprietary data standard as the optimal for a specific application

6 September How Can I Access My Engineering Design Information and RCM Study Data? How Can My Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Provide Timely and Relevant Data and Events to all Other Enterprise Systems? What Data About Current and Future Plant Capability Does My ERP System Need? (KPIs, Order Management, Supply Chain, Financial, Materiel, Logistics, HR) How Can I Change My Maintenance Systems into “Condition-based” and Access Necessary Maintenance Data – Past, Present, and Future? (people, parts, plans, tools, and time) How Can I Access My Physical Plant Configuration and Installed Equipment Registry Components (Past & Present)? Oil&Gas Industry Asset Management Data Integration Challenges How Can I Feed Asset Capability Data Into My Production Optimization, Planning & Scheduling Systems?

7 September EPC & OEM Engineering Product Design Data & Reliability Study Data Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] Serialized Asset Registry & Lifecycle Configuratio n Management Data Oil&Gas Industry Asset Management Data Integration Challenges Production Optimization, Planning & Scheduling

8 September EPC & OEM Engineering Product Design Data & Reliability Study Data Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] Serialized Asset Registry & Lifecycle Configuratio n Management Data Production Optimization, Planning & Scheduling How Best to Integrate the 100+ Systems?

9 September EPC & OEM Engineering Product Design Data & Reliability Study Data Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] Serialized Asset Registry & Lifecycle Configuratio n Management Data Production Optimization, Planning & Scheduling Serialized Asset Registry & Lifecycle Configuration Management Data How Best to Integrate the 100+ Systems? Proprietary Middleware Data Bridge

10 September EPC & OEM Engineering Product Design Data & Reliability Study Data Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] Serialized Asset Registry & Lifecycle Configuratio n Management Data Production Optimization, Planning & Scheduling Teach Them To Speak the OpenO&M Languages! ISO 15926

11 September MIMOSA OSA-EAI Design COMPUTER-DRIVEN APPLICATIONS WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS APPLICATION DATA & EVENTS OSA-EAI Information Architecture AUTOMATION DATA & EVENTS

12 September MIMOSA OSA-EAI Design COMPUTER-DRIVEN APPLICATIONS WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS APPLICATION DATA & EVENTS OSA-EAI Information Architecture AUTOMATION DATA & EVENTS

13 September MIMOSA OSA-EAI Design COMPUTER-DRIVEN APPLICATIONS WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS APPLICATION DATA & EVENTS OSA-EAI Information Architecture AUTOMATION DATA & EVENTS

14 September MIMOSA OSA-EAI Design COMPUTER-DRIVEN APPLICATIONS WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS MIMOSA Common Relational Information Schema (CRIS) APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS

15 September MIMOSA OSA-EAI Design COMPUTER-DRIVEN APPLICATIONS WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS MIMOSA Common Relational Information Schema (CRIS) MIMOSA Data Access Web Services (Tech-XML / Tech-CDE) & MIMOSA Data Access Messaging (Tech-Message) APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS

16 September MIMOSA OSA-EAI Design COMPUTER-DRIVEN APPLICATIONS WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS MIMOSA Common Relational Information Schema (CRIS) MIMOSA Data Access Web Services (Tech-XML / Tech-CDE) & MIMOSA Data Access Messaging (Tech-Message) APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS

17 September Integration Platform Suncor View -- A Coordinated Approach to Full Integration within the Enterprise Document Management Engineering CAD/CAE Systems Process Modeling Systems Planning and Dispatch Systems Lab Information Management Reconciliation System Maintenance System Historian System Data Index Message Transport Data Message Transportation Message Routing & Brokering Data Mapping & Transformation Pre-packaged Adaptors/ Connectors Workflow Process-modeling & optimization Integration Administration Encryption, Audit, Security Adapter Development Kit Analysis Tools Spreadsheets “Portals” Basic Admin Advanced Environmental Monitoring System Data

18 September What is an OpenO&M Information Model? ►Representation of the information objects required for the business based on defined set of OpenO&M standards ►Contains the things of importance in an organization and how they relate to one another ►Provides a basis for physical database design but does not mandate a particular data storage format. The physical design of a database involves deep use of particular database management technology. Information Model Physical Data Model

19 September Why Use an OpenO&M Information Model? ►Helps common understanding of business requirements ►Provides foundation for designing databases and bulk binary datastores, and data warehouses ►Facilitates data re-use and sharing ►Decreases development and maintenance time and cost ►Focuses on information requirements independent of technology and changing processes ►Decreases system development time and cost ►Becomes a template for the enterprise ►Facilitates data re-use and sharing ►Faster ROI ►Gathers metadata ►Fosters seamless communication between applications ►Focuses communication for data analysis and project team members ►Establishes a consistent naming scheme

20 September Why Use an OpenO&M Model? Most Current Applications Are Designed to Work Closely-Coupled to a Supplier- Specific Proprietary Database Application A Transactional Data Proprietary Data Model

21 September Why Use an OpenO&M Model? Software Engineering Best Practice Dictates A Separation of the Application from the Required Data it Needs Application A Transactional Data Proprietary Data Model

22 September Why Use an OpenO&M Model? World Class Enterprises Are Now Designing an Enterprise-owned Information Model Abstraction Layer Which Hides Proprietary Data Models Application A Transactional Data OpenO&M Information Model & OpenO&M Information Service Bus OpenO&M Model & Bus Proprietary Data Model

23 September Why Use an OpenO&M Model? This Allows Many New Applications to be Built With Just Knowledge of the Enterprise Information Model Application A Transactional Data OpenO&M Information Model & OpenO&M Information Service Bus OpenO&M Model & Bus Proprietary Data Model Application B Application C

24 September OpenO&M Information Strategy Application Supplier A Has the Option to Keep Proprietary Data Model or Evolve to Natively Use OpenO&M Information Model For Some/All Data Application A Transactional Data OpenO&M Information Model & OpenO&M Information Service Bus OpenO&M Model & Bus Application B Application C Application A Transactional Data Proprietary Data Model OpenO&M Information Model

25 September Tech-Message On-Ramp/Off-Ramp Services Proprietary ESB / MOM / SOA Engines Topic Registry Management System Service Management Security ESB / MOM / SOA Core Engine Message Routing Exception Management MIMOSA OSA-EAI Services B2B Gateway Provisioning Framework MIMOSA OSA-EAI Services Subscriber Applications Publisher Application Publishes “system of record” change events Store-and-Forward Caching Receives events Tech-Message Header with Tech-CDE, Tech-Doc, or Tech-XML Body “System of record” events MIMOSA Tech-Message Support for “Fire-and-Forget” Pub/Sub Pattern

26 September Application A Application B Application C Application D Application E Application F Secure Message Bus P P P P P P PP P Published Message from Application A which Applications D & E have Subscribed To Receive P Published Message from Application F which Applications B & C have Subscribed To Receive MIMOSA Tech-Message Support for “Fire-and-Forget” Pub/Sub Example

27 September Tech-Message On-Ramp/Off-Ramp Services Proprietary ESB / MOM / SOA Engines Topic Registry Management System Service Management Security ESB / MOM / SOA Core Engine Message Routing Exception Management MIMOSA OSA-EAI Services B2B Gateway Provisioning Framework MIMOSA OSA-EAI Services Subscriber Applications “System of record” events Publisher Application Tech-Message Header with Tech-CDE or Tech-XML Body “System of record” events Store-and-Forward Caching Delivered to Subscriber B Delivered to Subscriber C Delivered to Subscriber A Delivered to Subscriber B “System of record” events Delivered to Subscriber A Delivered to Subscriber C MIMOSA Tech-Message Support for “Sync” Pub/Sub Pattern

28 September Tech-Message On-Ramp/Off-Ramp Services Proprietary ESB / MOM / SOA Engines System Service Maagement Security ESB / MOM / SOA Core Engine Message Routing Exception Management MIMOSA OSA-EAI Services B2B Gateway Provisioning Framework MIMOSA OSA-EAI Services Receiver of Push Application Store-and-Forward Caching Sender of Push Application Requests MIMOSA CRIS- formatted Information with a-priori Knowledge of Name of Target Receiver Application Results of Push Tech-Message Header with Tech-CDE or Tech-XML Body Pushed Data Responds to Push in an Appropriate Way Pushed Data Results of Push MIMOSA Tech-Message Support for Targeted “Push” Pattern

29 September Tech-Message On-Ramp/Off-Ramp Services Proprietary ESB / MOM / SOA Engines System Service Maagement Security ESB / MOM / SOA Core Engine Message Routing Exception Management MIMOSA OSA-EAI Services B2B Gateway Provisioning Framework MIMOSA OSA-EAI Services Query Server Application Query Client Application Responds to Queries Requests MIMOSA CRIS- formatted Information with a-priori Knowledge of Name of Target Server Application Store-and-Forward Caching Query Results Query Query Results Query MIMOSA Tech-Message Support for Targeted “Pull” Pattern

30 September Tech-Message On-Ramp/Off-Ramp Services Proprietary ESB / MOM / SOA Engines System Service Maagement Security ESB / MOM / SOA Core Engine Message Routing Exception Management MIMOSA OSA-EAI Services B2B Gateway Provisioning Framework MIMOSA OSA-EAI Services Query Client Application Requests MIMOSA CRIS- formatted Information without a-priori Knowledge of Server Applications Store-and-Forward Caching Tech-Message Header with Tech-CDE or Tech-XML Body Query Results Query Query Server Applications Query “System of record” events Query Results MIMOSA Tech-Message Support for Untargeted “Scatter/Gather” Pattern

31 September Tech-Message Bus OnRamp & OffRamp Computer A OpenO&M Information Service Bus Tech-Message Bus OnRamp & OffRamp Vendor App Computer B Tech-Message Bus OnRamp & OffRamp Tech-Message Bus OnRamp & OffRamp Vendor App MIMOSA Tech-Message Services for an OpenO&M Information Service Bus

32 September MIMOSA’s Two Open Standards Tightly Coupled Systems Loosely Coupled Systems INFORMATION SYSTEMS MIMOSA OSA-EAI Information Architecture Standard EMBEDDED SYSTEMS MIMOSA OSA-CBM Processing Architecture Standard At Platform Diagnostics Portable Diagnostic Tools Maintenance Logistics EAM, CMMS Copyright 2007 MIMOSA

33 September ISO Standard Published standard for open software specifications which will allow machine condition monitoring data and information to be processed, communicated and displayed by various software packages without platform-specific, vendor-specific, or hardware-specific protocols ISO Parts 1 and 2 provide an informative Annexes which provides a reference to the open, vendor-neutral, XML-based consensus standards which are compliant with the architecture as described MIMOSA’s OSA-EAI and OSA-CBM Specifications are currently the only ones listed as compliant in this Annex

34 September OSA-EAI Based Upon 5-Layer ISO Open Information Architecture Requirements Conceptual Information Model Implementation Data Model Reference Data Library Semantic Definitions Data Document Definitions ISO Open Information Architecture Requirements

35 September OSA-EAI Based Upon 5-Layer ISO Open Information Architecture Requirements Common Conceptual Object Model (CCOM) Common Relational Information Schema (CRIS) CRIS Reference Data Library Terminology Dictionary Tech-Doc & Tech-CDE XML Document Schema OSA-EAI Information Architecture

36 September MIMOSA OSA-EAI Specification ►ISO compliant information architecture ►Built upon a Common Conceptual Object Model (CCOM) ►Converted into Relational Implementation Model called the Common Relational Information Model (CRIS) that can be implemented ►Specifications packaged for interoperability of: –Registry information for model nameplate information / asset registries / maint. breakdowns / resources (parts/tools/consumables) –Reliability information –Condition event data –Condition measurement data Scalar data Dynamic data (vibration / sound) Test data Sample data Binary data –Diagnostic / prognostic / health assessment information –Work management information ►Designed to transfer archived data which is normally stored in a database ►No middleware required

37 September MIMOSA OSA-EAI Interfaces ►MIMOSA Open System Architecture for Enterprise Application Integration (OSA-EAI) Core Technology –Built upon a Common Conceptual Object Model (CCOM) –Converted into an Relational Implementation Model called the Common Relational Information Model (CRIS) –Specifications packaged for Interoperability of: Model Nameplate Information / Asset Registries / Maint. Breakdowns Work Management Systems Diagnostic / Health Assessment Systems Process Data Historian Systems Dynamic Vibration / Sound Data Condition Monitoring Systems Lab Information Management Systems Test and Measurement Systems Binary / Thermography Condition Monitoring Systems Reliability Database Systems –Designed to Transfer Archived Data Which Is Normally Stored in a Database –No Middleware Required Copyright 2007 MIMOSA

38 September MIMOSA OSA-EAI Interfaces ►MIMOSA OSA-EAI Interfaces –Tech-Doc Interfaces defines CRIS XML documents of any size to use over any transport protocol –Tech-CDE (Compound Document Exchange) defines aggregate CRIS database queries and inserts/updates with Client/Server XML interfaces –Tech-XML Interfaces define discrete CRIS Client/Server XML transactions –Tech-File Export specification details the requirements for an application which will be exporting its data in Tech-Doc form –Tech-CDE-Services specification details the requirements for client/server Web applications which are runningTech-CDE transactions over SOAP transport protocol –Tech-XML-Web specification details the requirements for client/server Web applications which are running Tech-XML transactions over HTTP transport protocol –Tech-XML-Services specification details the requirements for client/server Web applications which are running Tech-XML transactions over SOAP transport protocol Copyright 2007 MIMOSA

39 September Open Maintenance Management Open Reliability Management Open Condition Management Open Object Registry Management MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI) Copyright 2007 MIMOSA

40 September Open Object Registry Management OSA-EAI Open Object Registry Management Meta-Data, Registry, & Current/Historical Configuration for: Enterprises Sites Functional Segments Segment Hierarchies & Named Relationships (Networks) Databases & Mapping Info OEM Model & Nameplate Specs Physical Assets with Segment Installation Agents Resources ( Parts/Consummables/Tools/Labour)

41 September MIMOSA OSA-EAI Specification ►ISO compliant information architecture ►Built upon a Common Conceptual Object Model (CCOM) ►Converted into Relational Implementation Model called the Common Relational Information Model (CRIS) that can be implemented ►Specifications packaged for interoperability of: –Registry information for model nameplate information / asset registries / maint. breakdowns / resources (parts/tools/consumables) –Reliability information –Condition event data –Condition measurement data Scalar data Dynamic data (vibration / sound) Test data Sample data Binary data –Diagnostic / prognostic / health assessment information –Work management information ►Designed to transfer archived data which is normally stored in a database ►No middleware required

42 September Understanding UML Class Diagrams Class ►The core element of the class diagram is the class. In an object oriented system, classes are used to represent entities within the system; entities that often relate to real world objects. ►The Contact class to the right is an example of a simple class that stores location information. ►Classes are divided into three sections: –Top: The name, package and stereotype are shown in the upper section of the class. –Center: The center section contains the attributes of –Bottom: In the lower section are the operations that can be performed on the class.

43 September Understanding UML Class Diagrams Generalization ►The generalization link is used between two classes to show that a class incorporates all of the attributes and operations of another, but adds to them in some way. ►In the diagram to the right, we again see our Contact class, only now with two child classes. We can say that Client and Company inherit, generalize or extend Contact. In each of Client and Company all of the attributes in Contact (address, city, etc.) exist, but with more information added. In the above situation Contact is said to be the superclass of Client and Company.

44 September Understanding UML Class Diagrams Associations ►Classes can also contain references to each other. The Company class below has two attributes that reference the Client class. ►The first association (the top one) represents the old contactPerson attribute. There is one contact person in a single Company. The multiplicity of the association is one to one meaning that for every Company there is one and only one contactPerson and for each contactPerson there is one Company. In the bottom association there are zero or many employees for each company. Multiplicities can be anything you specify. Some examples: 0 = zero 1 = one 1..* = one to many * or 0..* = zero to many ►The arrows at the end of the associations represent their navigability. In the above examples, the Company references Clients, but the Client class does not have any knowledge of the Company. You can set the navigability on either, neither or both ends of your associations. If there is no navigability shown then the navigability is unspecified.

45 September Understanding UML Class Diagrams Composition ►The example below shows an aggregation association and a composition association. ►The composition association is represented by the solid diamond. It is said that ProductGroup is composed of Products. This means that if a ProductGroup is destroyed, the Products within the group are destroyed as well. ►The aggregation association is represented by the hollow diamond. PurchaseOrder is an aggregate of Products. If a PurchaseOrder is destroyed, the Products still exist. ►If you have trouble remembering the difference between composition and aggregation, just think of the first 4 letters of the alphabet A through D. Aggregation means you can keep Building with the child classes if the parent class is destroyed. Composition means you must Destroy all the child classes if the parent class is destroyed.

46 September Open Object Registry Management OSA-EAI Open Object Registry Management Meta-Data, Registry, & Current/Historical Configuration for: Enterprises Sites Functional Segments Segment Hierarchies & Named Relationships (Networks) Databases & Mapping Info OEM Model & Nameplate Specs Physical Assets with Segment Installation Agents Resources ( Parts/Consummables/Tools/Labour)

47 September OSA-EAI Open Object Registry Management ►Enterprise – the corporate level of an organization, or the top organizational structure of a non-profit or military body. Each Enterprise is associated with exactly one Enterprise Type. An enterprise uniquely registers/births Sites and may control one or more Sites (which could have formerly been controlled by other enterprises). In order for multiple enterprises to exchange MIMOSA information, every Enterprise must request and utilize its unique, unchanging MIMOSA-assigned Enterprise Unique Integration Code (Enterprise- UIC) ►Enterprise Type – a kind of Enterprise, ex. "Corporation" ►Enterprise Unique Integration Code (Enterprise-UIC) – the MIMOSA- assigned unique identifier of an Enterprise. A globally-unique, non- negative, non-repeating integer assigned to an Enterprise through MIMOSA's Enterprise Unique Integration Code Registry Service.

48 September OSA-EAI Open Object Registry Management ►Enterprise Unique Integration Code (UIC) –The OSA-EAI Enterprise UIC is a 4-byte, non-negative integer assigned by MIMOSA for OpenO&M. Normally, MIMOSA will issue one enterprise GUID per corporation/organization. For some organizations, multiple enterprise GUIDs may be requested. –MIMOSA will also assign the enterprise with a globally-unique, alpha-numeric user_tag_id value. This can be used in conjunction with the USER_TAG_IDENT column in the site table to form a globally unique text string –A representative from the registration authority for an organization should the OpenO&M Enterprise Registrar at with the name of the organization, requested USER_TAG_IDENT point of contact name, title, phone number, and address –The OpenO&M Enterprise Registrar will then assign the enterprise GUID and enterprise USER_TAG_IDENT and return this non- negative integer and associated 8-byte string to the point of contact. –MIMOSA is the enterprise with a Enterprise UIC of 0 and user_tag_ident value of “MIMOSA”.

49 September OSA-EAI Open Object Registry Management

50 September OSA-EAI Open Object Registry Management

51 September OSA-EAI Open Object Registry Management

52 September OSA-EAI Open Object Registry Management ►Site – an enterprise-defined object (manufacturing plant, facility, platform, fleet object). Each Site is associated with exactly one Site Type. Sites uniquely register/birth Segments, Assets, Agents, Databases, and Measurement Locations. For facility applications, the “Site” can normally represents either the “as-designed” model of a building or the “as-built” building. For industrial and manufacturing applications, this entity normally represents the “as-designed” model of a physical plant or the “as-built” tangible plant. For fleet applications, this entity normally represents the “as-designed” model of a “mobile platform” (truck, vehicle, aircraft or tank) or the “as-built” tangible platform. Each Enterprise uniquely assigns every Site its unique, unchanging Site Unique Integration Code (Site-UIC). ►Site Type – a kind of Site, such as a "Facility" or "Fleet object" ►Site/Site Type Child Structure – a taxonomy of Site Type classifications which have a "super-class" (ex. "Facility") which may be sub-divided into "sub-classes" (ex, "Facility, Office Building", "Facility, Manufacturing Plant", etc.) ►Site Template – a logical Site which can be utilized as a prototype for physical Site instances.

53 September OSA-EAI Open Object Registry Management ►Site Unique Integration Code (Site-UIC) – the Enterprise-assigned unique identifier of a Site. Because of multiple methodologies for site/plant/platform identification in different industries and in various computer systems, a Site will often need to be associated with many identifiers relevant to the Site because they are the site's "unique key" for various databases. These identifiers may change as a Site is sold, transferred, or its role changes in relationship to multiple other Sites or Enterprises. Because of this requirement, MIMOSA-compliant systems require that a Site be permanently assigned one and only one Site Unique Integration Code which is composed of the birth Enterprise Unique Integration Code concatenated with a site-unique, non-negative integer (in CRIS, the "site_id") which should never change throughout the lifetime of the Site. This Site Unique Integration Code (Enterprise Unique Integration Code + "site_id") normally does not have any external end-user meaning, but is the vital link for all MIMOSA-compliant systems to properly integrate and associate information to the correct Site. The identical Site Unique Integration Code must remain permanently-unique for the life-time of the Site, even though it will most likely have additional temporarily-unique identifier tags assigned to the Site by various systems.

54 September OSA-EAI Open Object Registry Management

55 September OSA-EAI Open Object Registry Management ►Birth a Site for each platform life- cycle engineering design office which will be generating design databases with functional segments over the life of a model of a platform ►Birth a Site for each “end-item” platform where as-built/as- maintained configuration needs to be tracked over time

56 September OSA-EAI Open Object Registry Management ►Database (Data Archive / Site Database) – a repository of MIMOSA data or information at a Site. A Database is associated with exactly one Site. A Site uniquely assigns a Database Unique Integration Code (Database-UIC) to new Databases ("births" Databases). Among other information, customer and supplier Databases identify reference "type" data pertinent enterprise-wide, site-wide, supplier product-wide, or applicable to this site only. MIMOSA publishes Databases with reference data of international or enterprise-to-enterprise applicability (see CRIS Reference Data Library). The reference "type" data includes Enterprise Types, Asset Types, Segment Types, Agent Types, Manufacturers, Measurement Location Types, and Segment/Asset Event Types ►Database Unique Integration Code (Database-UIC) – the Site-assigned unique identifier of a MIMOSA-compliant Database. MIMOSA-compliant systems require that a Database be permanently assigned one and only one Database Unique Integration Code which is composed of the birth Site Unique Integration Code (in CRIS, the "db_site") concatenated with a site- unique, non-negative integer (in CRIS, the "db_id") which should never change throughout the lifetime of the Asset. This Database Unique Integration Code (Site Unique Integration Code + "db_id") normally does not have any external end-user meaning, but is the vital link for all MIMOSA-compliant systems to properly integrate and associate information to the correct Database. The identical Database Unique Integration Code must remain permanently-unique for the life-time of the Site, even though it will most likely have additional temporarily-unique identifier tags assigned to the Database by various systems.

57 September OSA-EAI Open Object Registry Management

58 September Best Practice Use of Database in Fleet Applications ►Birth a Database for each platform life-cycle engineering design office which will be generating design meta-data over the life of a model of a platform ►Birth a Database for each “end- item” platform where information will be locally cached/stored

59 September OSA-EAI Open Object Registry Management ►Manufacturer/Maker – the organization which designs Models of Assets and "Makes" Assets. Databases assign each Manufacturer entry with a unique, unchanging Manufacturer Unique Integration Code (Manufacturer-UIC). ►Model (Make-Model / Manufacturer Product / Manufacturer Part) – identifies a class or sub-class ("model revision" or "lot") of a Manufacturer's products as defined by a manufacturer, of which only one instance can be associated with a specific Asset. Each Model is associated with exactly one Asset Type. A Model can be associated with a top-level Segment which can then be referenced any many Networks which can define the as-designed functional segment structure. ►Model Child Structure – a taxonomy of a manufacturer's product Model "class" (ex. AH-64) which has revision "releases" (ex. "AH- 64A" ) and/or may be sub-divided into "lots" (ex, "AH-64A Lot 1") which vary in some way from the "parent" Model.

60 September OSA-EAI Open Object Registry Management

61 September OSA-EAI Open Object Registry Management

62 September OSA-EAI Open Object Registry Management ►An OEM life-cycle engineering design office database should birth the Model and Model Child relationships. ►Store model-specific specification data and nameplate data in ModelNumericData, ModelCharacterData, and ModelBLOBData

63 September OSA-EAI Open Object Registry Management ►Segment (Functional Area Entity / Breakdown Structure Entity) –Associated with a Model – as-designed functional area or breakdown structure entity for a Model. Each Model-associated Segment is associated with exactly one Segment Type. These segments would normally appear on the engineering drawings of the model. The Segment can be decomposed into one or more Segment Child Structures, which are child Segment functional locations inside the parent Segment. The Segment can have multiple Segment Network Structures defined. A Model-associated Segment can have as-designed Measurement Locations. –Associated with an Asset – as-built/as-maintained functional area or breakdown structure entity for a serialized Asset. Each Asset-associated Segment is associated with exactly one Segment Type. These segments might initially be identical to the Model's Segments, but may be changed to be unique for this particular Asset. The Segment can be decomposed into one or more Segment Child Structures, which are child Segment functional locations inside the parent Segment. The Segment can have multiple Segment Network Structures defined. An Asset- associated Segment can have as-built/as-monitored Measurement Locations. An Asset- associated Segment can have serialized Asset component parts installed over time, tracked by Asset Utilization History. ►Segment Child Structure – Dependent decomposition of Segments into multiple sub- segments (child segments) to form a single breakdown structure. Only recommended in fleet applications such as paper forms where there is only 1 Segment composition structure

64 September OSA-EAI Open Object Registry Management ►Segment Type – a kind of Segment (ex. "Rotor") which has an associated unchanging, unique Segment Type Unique Integration Code which can be referenced universally and used in Segment Type Child Structures ►Segment Type Child Structure – a taxonomy of Segment Type classifications which have a "super-class" (ex. "Rotor") which may be sub-divided into "sub-classes" (ex, "Rotor, Front" and "Rotor, Tail") ►Segment Unique Integration Code (Segment-UIC)– the Site-assigned unique identifier of a Segment. Because of multiple methodologies for functional location identification in various computer systems, a Segment will often need to be associated with many identifiers relevant to the Segment because they are the segment's "unique key" for various databases. Because of this requirement, MIMOSA-compliant systems require that a Segment be permanently assigned one and only one Segment Unique Integration Code which is composed of the associated Site Unique Integration Code (in CRIS, the "segment_site") concatenated with a site-unique, non-negative integer (in CRIS, the "segment_id") which should never change throughout the lifetime of the Segment. This Segment Unique Integration Code (Site Unique Integration Code + "segment_id") normally does not have any external end-user meaning, but is the vital link for all MIMOSA-compliant systems to properly integrate and associate information to the correct Segment. The identical Segment Unique Integration Code must remain permanently-unique for the life-time of the Segment, even though it will most likely have additional temporarily-unique user identifier tags assigned to the Segment

65 September OSA-EAI Open Object Registry Management ►Network - the unique identification of a Segment Network Structure and/or an Asset Network Structure for a given database ►Model’s Segment Network Structure - defines connectivity relationships between segments, and allows segments to be associated in ordered input-output flow chains (i.e., process flowcharts) or sequenced parent-child relationships. These networks are useful for associating segments into Breakdown Structures useful for maintenance, system engineering, operations, logistics, diagnostic/prognostic systems, etc. A Segment can be specified in an unlimited number of Networks.

66 September OSA-EAI Open Object Registry Management

67 September OSA-EAI Open Object Registry Management

68 September OSA-EAI Open Object Registry Management

69 September OSA-EAI Open Object Registry Management ►Birth a segment which represents the entire model and associate it with the Model ►Create segments for each functional grouping area in a platform including LRU locations, and software/firmware locations ►Create Measurement Locations associated with each segment where monitoring will occur ►Store model-specific specification data and nameplate data in ModelNumericData, ModelCharacterData, and ModelBLOBData ►Create a Network with SegmentNetworkConnect entities for each model configuration and associate it with a Model using ModelValidNetworkHistory (which tracks changes to the configuration of the Model over time)

70 September OSA-EAI Open Object Registry Management ►Asset – a physical, non-intelligent instantiated object. An Asset may be an entire facility, an entire functioning system (such as an CH-47 Tail Number XYZ helicopter), or a component piece of equipment, such as a specific instance of a bearing. Each Asset is associated with exactly one Asset Type. An Asset can be associated with a top-level Segment which defines its internal as-built/as-maintained functional segment structure. A component Asset may be installed on/at a Segment over a period of time (asset tracking). An Asset can be monitored via Measurement Locations, be associated with work, and may be composed of one or more Asset Child Structures. When first referenced in a MIMOSA-compliant system, an origination Site permanently assigns an Asset an Asset Unique Integration Code. ►Asset Child Structure – a breakdown of assets into sub-asset components (child assets), to form serialized component part breakdown trees ►Asset Network Structure - connectivity relationships between assets, and allows assets to be associated in ordered input-output flow chains (i.e, process flowcharts) or sequenced parent-child relationships ►Asset Type – a kind of Asset or Model (ex. "Motor, AC") which has an associated unchanging, unique Asset Type Unique Integration Code which can be referenced universally and used in Asset Type Child Structures

71 September OSA-EAI Open Object Registry Management ►Asset Type Child Structure – a taxonomy of Asset Type classifications which have a "super-class" (ex. "Pump") sub-divided into its "sub-classes" (ex. "Pump, Centrifigual" and "Pump, Axial") ►Asset Unique Integration Code (Asset-UIC) – the Site-assigned unique identifier of an Asset. Because of multiple methodologies for serialized asset/component tracking identification in different industries and in various computer systems, an Asset will often need to be associated with many identifiers relevant to the Asset because they are the asset's "unique key" for various databases. These identifiers may change as an Asset is sold, leased, or refurbished and moves throughout multiple Sites or Enterprises. Because of this requirement, MIMOSA-compliant systems require that an Asset be permanently assigned one and only one Asset Unique Integration Code which is composed of the birth Site Unique Integration Code (in CRIS, the "asset_org_site") concatenated with a site-unique, non-negative integer (in CRIS, the "asset_id") which should never change throughout the lifetime of the Asset. This Asset Unique Integration Code (Site Unique Integration Code + "asset_id") normally does not have any external end-user meaning, but is the vital link for all MIMOSA-compliant systems to properly integrate and associate information to the correct Asset. The identical Asset Unique Integration Code must remain permanently-unique for the life-time of the Asset, even though it will most likely have additional temporarily-unique identifier tags assigned to the Asset by various systems.

72 September OSA-EAI Open Object Registry Management ►Network - the unique identification of a Segment Network Structure and/or an Asset Network Structure for a given database ►Asset’s Segment Network Structure – Specific for an asset, defines connectivity relationships between segments, and allows segments to be associated in ordered input- output flow chains (i.e., process flowcharts) or sequenced parent-child relationships. These networks are useful for associating segments into Breakdown Structures useful for maintenance, system engineering, operations, logistics, diagnostic/prognostic systems, etc. A Segment can be specified in an unlimited number of Networks.

73 September OSA-EAI Open Object Registry Management

74 September OSA-EAI Open Object Registry Management

75 September OSA-EAI Open Object Registry Management

76 September OSA-EAI Open Object Registry Management ►OEM should birth the Asset with its Asset-UIC and associate it with the proper Model. If the OEM does not assign, then must be birthed at first organization receiving the part. ►For platform Assets, create a Site and replicate all the Segments from the previously-created Model networks, including a top-level Segment equivalent to the entire platform. Create a link to this Segment from the Site and and the Asset. ►For platform Assets, create Networks with SegmentNetworkConnect entities from previously created Model networks for each asset configuration and associate it with an Asset using AssetValidNetworkHistory (which tracks changes to the configuration of the Asset over time) ►Store Asset-specific specification data and nameplate data in AssetNumericData, AssetCharacterData, and AssetBLOBData

77 September OSA-EAI Open Object Registry Management ►Is it an Asset? –An object is an Asset if it meets one of these criteria: Could be depreciated in a financial system Could be tracked by serial number Could be transferred/sold and utilized/installed at a different Segment possibly associated with another Site at another Enterprise

78 September OSA-EAI Open Object Registry Management ►Is it a Segment? –A functional location where various Assets can be installed over time –Are associated with a Model of a component or a design of an entire process or platform

79 September OSA-EAI Open Object Registry Management ►Agent – a physical, intelligent instantiated object (person, group, organization, or intelligent agent software) which can perform work, make diagnoses, health assessments, etc. Each Agent is associated with exactly one Agent Type. When first referenced in a MIMOSA-compliant system, an origination Site permanently assigns an Agent an Agent Unique Integration Code (Agent-UIC). ►Agent Type – a kind of Agent, ex. "Person" or "Organization" ►Agent Unique Integration Code (Agent-UIC) – the Site-assigned unique identifier of an Agent. Because of multiple methodologies for agent identification in different industries and in various computer systems, an Agent will often need to be associated with many identifiers relevant to the Agent because they are the agent's "unique key" for various databases. These identifiers may change as an Agent has various roles for multiple Sites or Enterprises. Because of this requirement, MIMOSA-compliant systems require that an Agent be permanently assigned one and only one Agent Unique Integration Code which is composed of the birth Site Unique Integration Code (in CRIS, the "org_agent_site") concatenated with a site- unique, non-negative integer (in CRIS, the "agent_id") which should never change throughout the lifetime of the Agent. This Agent Unique Integration Code (Site Unique Integration Code + "agent_id") normally does not have any external end-user meaning, but is the vital link for all MIMOSA- compliant systems to properly integrate and associate information to the correct Agent. The identical Agent Unique Integration Code must remain for the life-time of the Agent, even though it will most likely have additional temporarily-unique identifier tags assigned to the Agent by various systems.

80 September OSA-EAI Open Object Registry Management ►In order to guarantee “plug-and-play” interoperable OSA-EAI systems, users and suppliers of OSA-EAI compliant systems must agree to abide by conventions regarding the assignment of Unique Integration Codes (UICs) which are used to guarantee correct identification of objects on every row on every CRIS XML document ►4 Registration Authorities: –Global Level: MIMOSA Provides enterprise UIC to corporations/organizations desiring OSA-EAI Interoperability and suppliers of MIMOSA-compliant systems –Enterprise Level: Enterprise Administrator Provides site UIC’s unique for the enterprise –Site Level : Site Administrator Provides segment UIC’s, agent UIC’s, database UIC’s, and measurement location UIC’s unique for site. –Database Level : Database Administrator Provides network, manufacturer, model, reference type, ordered list, and work management UIC’s unique to a specific database/data source.

81 September OSA-EAI Open Object Registry Management

82 September OSA-EAI Open Object Registry Management Note: Blue highlighted segments are included in both network hierarchies

83 September OSA-EAI Open Object Registry Management Note: Dark green segments are “leaf” segments where serialized assets can be installed

84 September OSA-EAI Open Object Registry Management Motor P/N AB-C800 S/N: 4324

85 September OSA-EAI Open Object Registry Management Motor P/N AB-C800 S/N: 9432

86 September OSA-EAI Open Object Registry Management Motor P/N AB-C800 S/N: 1254

87 September OSA-EAI Open Object Registry Management Common Conceptual Object Model (CCOM) Common Relational Information Schema (CRIS) Terminology Dictionary CRIS Representation of Object Registry

88 September AssetSegment Site Model Segment Type Site Database Asset Type Manu- facturer Row Status Type Segment Child Asset On Segment Database MIMOSA Interfaces MIMOSA Interface Types MIMOSA Data Categ. Type MIMOSA Support Type MIMOSA Functionality Type Enterprise Site Type Enterprise Type MIMOSA Access Type OSA-EAI Open Object Registry Management 1 to many(*) relationship

89 September Asset Numeric Data Asset Character Data Segment Numeric Data Segment Character Data Segment BLOB Data Asset BLOB Data Model Numeric Data Model Character Data Model BLOB Data Segment Type Site Database Asset Type Manu- facturer BLOB Content Type BLOB Data Type Agent Type Row Status Type Purchase Condition Type Asset Readiness Type Asset Child Model Child Asset Owner History 1 to many(*) relationship Reference Unit Type Engineering Unit Enumerated Engineering Unit Type Segment Numeric Data Type Segment Character Data Type Asset Numeric Data Type Asset Character Data Type Database MIMOSA Interfaces MIMOSA Interface Types MIMOSA Data Categ. Type MIMOSA Support Type MIMOSA Functionality Type AssetSegment Site Segment Child Asset On Segment Enterprise Type Site Type MIMOSA Access Type

90 September OSA-EAI Open Object Registry Management Common Conceptual Object Model (CCOM) Common Relational Information Schema (CRIS) Terminology Dictionary CRIS Meta-Data Reference Data Library CRIS Reference Data Library

91 September OSA-EAI Open Object Registry Management ►OSA-EAI MetaData Classification System Enables: –Extensible classification taxonomy system for asset types, segment types, OEM codes, model types, asset nameplate data, and all associated specification/cut-sheet data elements

92 September OSA-EAI Open Object Registry Management ► CRIS Meta-data Classification System –Asset Type Classification Codes Universal asset type taxonomy Allows standard querying of common asset types, i.e., “Bearing, Anti-friction, Roller ” Site Database-extensible –Segment Type Classification Codes Universal service segment type taxonomy Allows standard querying of segment type, i.e, “Rotor Tail Section” Site Database-extensible –OEM & Model Codes Facilitates standard manufacturer codes and model information –Segment / Asset / Model Nameplate Data Element Standard Codes Framework to allow open information transfer between all OEMs and end-users Standard Engineering Units Related to SI Reference Units

93 September OSA-EAI Open Object Registry Management

94 September OSA-EAI Open Object Registry Management

95 September OSA-EAI Open Object Registry Management

96 September OSA-EAI Open Object Registry Management

97 September OSA-EAI Open Object Registry Management ►Enables permanent & consistent identification of all systems, sub- assemblies and components ►Facilitates correlated tracking of life-cycle O&M information for: Service Segments – Functional areas of a platform or system with information tracked for the lifetime of the platform or system Assets – Cradle to grave serialized component information tracking with OEM and user-defined attributes with segment installation history tracking Models – OEM model component information tracking with OEM-defined attributes –Agent – An intelligent object (person, group, organization, or intelligent agent software) which makes various types of assessments and can be assigned work to be performed ►Supports all types of physical asset components, systems, platforms, and facilities ►Unlimited functional breakdowns of a model of a platform and a specific platform instance

98 September Open Reliability Management OSA-EAI Open Reliability Management Copyright 2007 MIMOSA

99 September Copyright 2007 MIMOSA OSA-EAI Open Reliability Management

100 September ►Provide a consistent information architecture for managing all physical asset reliability information in an open, distributed, multi-vendor, multi-system environment. ►Based on MIMOSA’s physical asset registry ►Enables continuous improvement throughout system, sub- assembly and component life-cycles ►Supports enterprise-wide, continuous RCM and FMECA analysis ►Enables enterprise-wide component tracking, including geo- spatial tracking ►Supports OEM model-specific problem reporting ►Provides information to support spare part optimization ►Incorporates root cause analysis information Copyright 2007 MIMOSA OSA-EAI Open Reliability Management

101 September OSA-EAI Open Reliability Management ► OSA-EAI Meta-data Classification System –Hypothetical Event Failure Classification Codes Facilities Pareto analysis of most common failure modes by asset type, by model, and by segment type enterprise-wide

102 September OSA-EAI Open Reliability Management

103 September OSA-EAI Open Reliability Management

104 September OSA-EAI Open Reliability Management

105 September OSA-EAI Open Reliability Management ► OSA-EAI Meta-data Classification System –Event Classification Codes –Measurement Location Type Classification Standard Codes Framework to allow open information transfer between all OEMs and end-users Standard Engineering Units Related to SI Reference Units

106 September OSA-EAI Open Condition Management Open Condition Management Copyright 2007 MIMOSA

107 September OSA-EAI Open Condition Management Copyright 2007 MIMOSA

108 September ►Provides a consistent information architecture for managing all physical asset condition management information in an open, distributed, multi-vendor, multi-system environment. ►Based on MIMOSA’s physical asset registry ►Conforms to ISO standard for Machine Condition Monitoring & Diagnostics ►Manages sensor registry using a general measurement location with a measurement location type ►Manages meta-data, raw data, and computational data from a wide variety of technologies –Operational data monitoring –Vibration/sound dynamic data monitoring –Oil/fluid/air sample analysis –Thermographic image analysis –Binary large object (BLOB) data monitoring ►Supports intelligent agent diagnostic analysis, prognostic analysis, remaining useful life estimates, future failure mode probabilities Copyright 2007 MIMOSA OSA-EAI Open Condition Management

109 September OSA-EAI Open Condition Management Copyright 2007 MIMOSA

110 September OSA-EAI Open Condition Management

111 September OSA-EAI Open Condition Management

112 September OSA-EAI Open Condition Management Copyright 2006 MIMOSA

113 September OSA-EAI Open Condition Management

114 September OSA-EAI Open Condition Management

115 September OSA-EAI Open Condition Management

116 September OSA-EAI Open Condition Management

117 September OSA-EAI Open Condition Management

118 September OSA-EAI Open Condition Management

119 September OSA-EAI Open Condition Management

120 September OSA-EAI Open Condition Management

121 September OSA-EAI Open Condition Management

122 September OSA-EAI Open Condition Management

123 September OSA-EAI Open Condition Management

124 September Use Case #3 Example: Flow platform O&M data (20,000 points) from the field to national. There is a normal operation mode for the tank and then there is a diagnostic mode for the tank. If something goes wrong, then they use "diagnostic mode" where all the modules report out after performing bit/byte tests, SRU diagnostic tests, etc. OSA-EAI Open Condition Management

125 September OSA-EAI Open Condition Management

126 September OSA-EAI Open Condition Management

127 September OSA-EAI Open Condition Management

128 September OSA-EAI Open Condition Management

129 September OSA-EAI Open Condition Management

130 September OSA-EAI Open Condition Management

131 September OSA-EAI Open Maintenance Management Open Maintenance Management Copyright 2007 MIMOSA

132 September OSA-EAI Open Maintenance Management Copyright 2007 MIMOSA

133 September MIMOSA Open Maintenance Management

134 September MIMOSA Open Maintenance Management

135 September OSA-EAI Open Capability Forecast Management Copyright 2007 MIMOSA

136 September ►Provides a consistent information architecture for physical asset capability forecasting based on projected future operating profiles, quality constraints, and time constraints managing all physical asset capability forecasting information in an open, distributed, multi-vendor, multi-system environment. ►Supports operational forecast scheduling and what-if order/mission decision support ►Key enabling technology for the real-time enterprise along with raw material availability, personnel availability, and product storage capability forecasting assessment Copyright 2007 MIMOSA OSA-EAI Open Capability Forecast Management

137 September Open Maintenance Management Open Reliability Management Open Condition Management Open Object Registry Management MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI)

138 September MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI) Copyright 2007 MIMOSA

139 September MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI) Architecture OSA-EAI Common Conceptual Object Model (CCOM) Conceptual Model Common Relational Information Schema (CRIS) Implementation Model CRIS Reference Data Library MetaData Taxonomy OSA-EAI Terminology Dictionary Semantic Definitions XML Content Definition Compliant Application Service Definitions Tech-Doc Producer& Consumer XML Stream or File Tech-CDE Aggregate CRIS XML Transaction Client & Server Schema Tech-XML Atomic CRIS XML Transaction Client & Server Schema Tech-XML-Services For SOAP Tech-XML Clients & Servers Tech-XML-Web For HTTP Tech-XML Clients & Servers Tech-Doc CRIS XML Document Schema REG (Object Registry Management) WORK (O&M Agent Work Management) DIAG (Diagnostics / Prognostics / Health Assessment) TREND (Operational Scalar Data & Alarms) DYN (Dynamic Vibration/Sound Data & Alarms) TEST (Oil/Fluid/Gas/Solid Test Data & Alarms) BLOB (Binary Data/Thermography Data & Alarms) REL (RCM/FMECA/Model Reliability Information) TRACK (Physical Asset GeoSpatial Tracking Information) Technology Types [Tech-] Tech-CDE Client & Server XML Stream or XML File Tech-XML Client & Server XML Stream or XML File Compliant SOA Application Definitions Tech-CDE-Services For SOAP Tech-CDE Clients & Servers

140 September MIMOSA OSA-EAI V3.3 Release OSA-EAI Common Conceptual Object Model (CCOM) Conceptual Model Common Relational Information Schema (CRIS) Implementation Model CRIS Reference Data Library MetaData Taxonomy OSA-EAI Terminology Dictionary Semantic Definitions XML Content Definition Compliant Application Service Definitions Tech-Doc Producer & Consumer XML Stream or File Tech-CDE Aggregate CRIS XML Transaction Client & Server Schema Tech-XML Atomic CRIS XML Transaction Client & Server Schema Tech-Doc CRIS XML Document Schema Tech-CDE Client & Server XML Stream or XML File Tech-XML Client & Server XML Stream or XML File OpenO&M for Industry Use Cases OpenO&M for Industry Interoperability Scenarios Tech-Message Open On-Ramp & Off-Ramp Specification OpenO&M for Industry Tech-Doc and Tech-CDE Message Definitions with Relevant Tech-XML Messages OpenO&M for Industry CRIS Business Rules OpenO&M for Industry Data Element Dictionaries & Taxonomies Tech-CDE-Services SOAP Client & Server Tech-XML-Services SOAP Client & Server For Message Buses For Point-to-Point Web Services

141 September MIMOSA Specification Development Process Flowchart

142 September MIMOSA Specification Release History Beta Version, Members-only Release Final Version, Production Release

143 September OSA-EAI Distribution ►CCOM UML Model ►CRIS XML Relational Schema –XML ►CRIS Meta-Data Reference Database –XML –SQL Server –ORACLE ►TACOM Reference CRIS SQL Server Database ►Tech-CDE Server for SQL Server / ORACLE ►MIMOSA Information Manager Tech-CDE Client Software

144 September Services Oriented Architecture Major Classes of Data and Related Architecture Initial Focus Areas As-Designed Reference Data As-Fielded Instance Data As-Monitored & As-Maintained Event Data Ontology

145 September EPC & OEM Engineering Product Design Data & Reliability Study Data Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] Serialized Asset Registry & Lifecycle Configuratio n Management Data Production Optimization, Planning & Scheduling Teach Them To Speak the OpenO&M Languages! ISO 15926

146 September End User/EPC Engineering Data Supported by ISO Process/Platform Requirements Process/Platform Segment “Type” Definitions Process/Platform Segment “Attribute” Definitions Process/Platform As-Built Segment Information Segment Unique Identifier Segment Type + Attribute + Eng.Unit Data Process/Platform Segment-Segment Relationships (Lifecycle History) Hierarchical Breakdown Structures Process Networks System Networks Process/Platform Segment Diagrams (Lifecycle History) P&ID Diagram System Network Diagram Process Flow Diagram

147 September End User/EPC Engineering Data Supported by ISO Sensor Design Process/Platform Sensor “Type” Definitions Process/Platform Sensor “Attribute” Definitions Process/Platform As-Built Sensor Information Sensor Tag Unique Identifier Semi-static Attribute + Eng. Unit Data Pairs Process/Platform As-Built Segment-Sensor Relationship Spatial relationship of sensor to segment Sensor Networks Process/Platform Sensor Diagrams Sensor Network Diagram System Network Diagram

148 September End User/EPC Engineering Data Supported by ISO Engineered Maintenance Packages (“Solution Packages”) Process/Platform Segment Potential Faults Process/Platform Segment Pre-defined Maintenance Packages Parts Requirements Tools Requirements Personnel Requirements Time Requirements Process/Platform Segment – Solution Packages Relationship

149 September OEM Model Reference Data Supported by ISO Equipment OEM Model/Part Information Equipment “Type” Definitions Equipment “Attribute” Definitions As-Designed OEM Model/Part Information Model/Part Unique Identifier Model/Part + Attribute + Eng.Unit “Cut-Sheet” Data As-Designed Sensor Information Semi-static meta-data regarding Sensors built into design As-Designed OEM Model/Part Bill of Material (BOM) Breakdown Structure As-Designed OEM Model Diagrams BOM Diagram CAD Drawing

150 September End User Asset Instance Data Supported by MIMOSA OSA-EAI Equipment Instance “Serialized Asset” Information Equipment Instance “Type” Definitions (referenced to ISO 15926) Equipment Instance “Attribute” Definitions (referenced to ISO 15926) As-Built Equipment Instance Information Asset Unique Identifier Semi-Static Attribute + Eng.Unit “Cut-Sheet” Data Pairs (inherited from ISO model data) As-Built Equipment Instance Bill of Material (BOM) Breakdown Structure As-Built Asset Model Diagrams BOM Diagram (inherited from ISO model) CAD Drawing (inherited from ISO model)

151 September End User Asset Instance Data Supported by MIMOSA OSA-EAI Equipment Instance “Serialized Asset” Information (cont.) As-Maintained Equipment Instance Information As-Maintained Equipment Instance Bill of Material (BOM) Breakdown Structure As-Maintained Asset Model Diagrams BOM Diagram CAD Drawing

152 September End User Field Engineering Data Supported by OSA-EAI Process/Platform Field Engineering Modifications Process/Platform As-Modified Segment Information Segment Unique Identifier Semi-static Attribute + Eng.Unit Data Pairs Process/Platform Segment-Segment Relationships Hierarchical Breakdown Structure Updates Process Network Updates System Network Updates

153 September End User Asset Event Data Supported by MIMOSA OSA-EAI & OPC-UA/MIMOSA Asset and Segment “Event” Data (Current / Historical) Operating Events and Associated Data Usage Events (e.g., 1000 hours since last lube) Alarm Notification Events (e.g., turbine overspeed alarm) Operating Envelope Events (e.g., exceedances) Safety Events and Associated Data Environmental Events and Associated Data Maintenance Events and Associated Data Maintenance-notification Events (e.g., request for maintenance) Work Order Generation / State change Completed Work Asset Installed/Removed on Segment (Current & Historical) Hard Failure Events and Associated Data

154 September End User CBM Data Supported by MIMOSA OSA-EAI & OPC-UA/MIMOSA Data Acquisition (Current & Historical) Active Tag Sensor Database Registry with Connections to Segments/Assets and OPC UA Current/Historical Server Locations On-line Monitoring Scalar Data Dynamic Signal-processed Data Periodic Diagnostic Tests & Measurements Lab Information Sample Data Data Manipulation (Current & Historical) State Detection (Current & Historical) Health Assessment (Current & Historical) Prognostic Assessment (Current & Historical) Advisory Generation

155 September End User Production Reporting Data Supported by ProdML Production Level Reporting Production Scheduling

156 September June 17, Mike Brooks – Chevron Vision name services metadata model maps abstraction not proprietary interoperability

157 September OpenO&M Mike Brooks – Chevron Vision

158 September Integration Platform Suncor View -- A Coordinated Approach to Full Integration within the Enterprise Document Management Engineering CAD/CAE Systems Process Modeling Systems Planning and Dispatch Systems Lab Information Management Reconciliation System Maintenance System Historian System Data Index Message Transport Data Message Transportation Message Routing & Brokering Data Mapping & Transformation Pre-packaged Adaptors/ Connectors Workflow Process-modeling & optimization Integration Administration Encryption, Audit, Security Adapter Development Kit Analysis Tools Spreadsheets “Portals” Basic Admin Advanced Environmental Monitoring System Data

159 September Systems Requiring Interoperability

160 September System Systems Requiring Interoperability With Abbreviations ►AHM:Asset Health Management System ►CMS:Condition Monitoring System ►DCS:Distributed Control System ►DEV:Instrumentation & Control Device Monitoring System ►EAM:Enterprise Asset Management (Maintenance Management) System ►EH&S:Environmental, Health, and Safety Management System ►EIS:Engineering Information System (Plant/Process Engineering As-Designed & As-Built Network/Segment/Tag Information, Configuration Management Historian) ►EOM:Event-Oriented Message Bus ►ERM:Enterprise Risk Management System ►HIST:Process/Asset Data Historian System ►HMI:Human-Machine Interface (Operator Console) System ►MES:Manufacturing Execution System / Production Forecasting & Scheduling System ►OPM:Operational Performance Modeling & Optimization System ►ORM:Operational Risk Management System such as EH&S, PSM, AHM, QMS ►PDM:Product Data Management (As-Designed Product/Part Model Identification and Data Sheets, As-Built Asset identification and Data Sheets) ►PORT:Enterprise KPI/Event Portal ►PSM:Process Safety Management System ►QMS:Quality Management System ►REG:As-Installed & Maintained Plant/Process Nework/Segment/Asset/Tag Registry & Configuration Management Historian System

161 September Oil & Gas/PetroChem Industry OpenO&M Interoperability Scenarios (Complete View) NOTE: Arrows with Do Not Connect Directly to Another System Publish Information Which Can Be Subscribed to By Multiple Systems Open Standards Which Define Data Content for Information Exchange: OAGIS, CIDX ISO & MIMOSA B2MML B2MML & PRODML MIMOSA & B2MML MIMOSA OPC Fieldbus (Foundation, Profibus, etc.)

162 September Enterprise Risk Management System, Enterprise Resource Planning System & Enterprise KPI/Event Portals Oil & Gas/PetroChem Industry OpenO&M Interoperability Scenarios Production Forecasting & Scheduling Systems Operational Performance Modeling & Optimization Systems Enterprise Asset Management Systems CBM Advisories (MIMOSA) Control/SCADA, HMI, & Historians CBO Advisories (MIMOSA) Measurements, Events, Inspections, Calibrations, Conditions, Usage, and Sensed O&M Actions O&M Event Monitoring I&C Device Monitoring Portable Monitors (Off- & On-line) Online Surveillance Monitors Online Protection Monitors Online Transient Monitors Laboratory Information Management Systems (LIMS) Operational Risk Management Systems (EH&S, PSMS, AHMS, QMS) Event-Oriented Message Bus Production Performance (B2MML) Asset Performance Prediction (B2MML & PRODML) Full-resolution Condition Data & Events (MIMOSA) “As-Installed” & “As-Maintained” Master Data (MIMOSA & B2MML) Significant Actual & Early Warning ORM Events (MIMOSA) ORM KPIs (MIMOSA & B2MML) Maintenance Work Status, & Work History (MIMOSA) Production Orders (OAGIS, CIDX, B2MML) RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX) RFQs & POs (OAGIS, CIDX) Suppliers Customers Detailed Prod. Performance (B2MML) Detailed Prod. Schedules (B2MML) Plant/Process Engineering As-Designed & As-Built Network/Segment/Tag Information, Config. Mgmt. Historians Plant/Process “As-Installed” & “As-Maintained” Network/Segment/Asset/Tag Registry & Configuration Management Historians OEM Product Data Mgmt. Systems “As-Designed” & “As-Built” Product/Part Data (ISO & MIMOSA) Asset Removals & Installations (MIMOSA) EOM ORM EAM HIST DCS HMI CMS DEV REG OPM MES EIS PDM OPM KPIs (MIMOSA & B2MML) Forecasted Demand (B2MML & PRODML) Planned Asset Unavailability Schedule (MIMOSA & B2MML) MES KPIs (B2MML) “As-Designed” & “As-Built” Plant/Process Engineering Data (ISO & MIMOSA) Usage Readings (MIMOSA) CBM/Calib. Schedule (MIMOSA) CBM/Calib. Work Completed (MIMOSA) Maint. KPIs (MIMOSA) ERM PORT ERP Plant/Process Engineering Change Advisories Product/Part Engineering Change Advisories Hist. Op. Data & Events (OPC UA-HDA) Current Op. Data & Events (OPC UA DA/A&E) Op. Work Status & Work History (MIMOSA) Control Data (Fieldbus)

163 September Oil & Gas/PetroChem Industry OpenO&M Interoperability Top- Priority Scenarios As Determined By Top-Priority Use Cases NOTE: Arrows with Do Not Connect Directly to Another System Publish Information Which Can Be Subscribed to By Multiple Systems Open Standards Which Define Data Content for Information Exchange: OAGIS, CIDX ISO & MIMOSA B2MML B2MML & PRODML MIMOSA & B2MML MIMOSA OPC Fieldbus (Foundation, Profibus, etc.)

164 September Enterprise Risk Management System, Enterprise Resource Planning System & Enterprise KPI/Event Portals Production Forecasting & Scheduling Systems Operational Performance Modeling & Optimization Systems Enterprise Asset Management Systems CBM Advisories (MIMOSA) Control/SCADA, HMI, & Historians CBO Advisories (MIMOSA) Measurements, Events, Inspections, Calibrations, Conditions, Usage, and Sensed O&M Actions O&M Event Monitoring I&C Device Monitoring Portable Monitors (Off- & On-line) Online Surveillance Monitors Online Protection Monitors Online Transient Monitors Laboratory Information Management Systems (LIMS) Operational Risk Management Systems (EH&S, PSMS, AHMS, QMS) Event-Oriented Message Bus Production Performance (B2MML) Asset Performance Prediction (B2MML & PRODML) Full-resolution Condition Data & Events (MIMOSA) “As-Installed” & “As-Maintained” Master Data (MIMOSA & B2MML) Significant Actual & Early Warning ORM Events (MIMOSA) ORM Risk KPIs (MIMOSA & B2MML) Maintenance Work Status, & Work History (MIMOSA) Production Orders (OAGIS, CIDX, B2MML) Control Data (Fieldbus) RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX) RFQs & POs (OAGIS, CIDX) Detailed Prod. Performance (B2MML) Detailed Prod. Schedules (B2MML) Plant/Process Engineering As-Designed & As-Built Segment/Tag Information, Configuration Management Historians Plant/Process “As-Installed” & “As-Maintained” Segment/Asset/Tag Registry & Configuration Management Historians OEM Product Data Mgmt. Systems “As-Designed” & “As-Built” Product/Part Data (ISO & MIMOSA) Asset Removals & Installations (MIMOSA) EOM ERM PORT ERP ORM EAM HIST DCS HMI CMS DEV REG OPM MES EIS PDM OPM KPIs (MIMOSA & B2MML) Forecasted Demand (B2MML & PRODML) Planned Asset Unavailability Schedule (MIMOSA & B2MML) MES KPIs (B2MML) “As-Designed” & “As-Built” Plant/Process Engineering Data (ISO & MIMOSA) Usage Readings (MIMOSA) CBM/Calib. Schedule (MIMOSA) CBM/Calib. Work Completed (MIMOSA) Hist. Op. Data & Events (OPC UA-HDA) Op. Work Status & Work History (MIMOSA) Maint. KPIs (MIMOSA) 22 Current Op. Data & Events (OPC UA DA/A&E) Suppliers Customers Plant/Process Engineering Change Advisories 24 Product/Part Engineering Change Advisories Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-Priority Scenarios

165 September Pull Model Data Out of PDM to ERM, ERP, PORT, ORM, EAM, EIS, REG, CMS, HMI, HIST Synch Creation/Update of Model Data Out of PDM to ERM, ERP, ORM, EAM, EIS, REG, CMS, HIST Push Model Data Into PDM from ERM, ERP, PORT, ORM, EAM, EIS, REG, CMS, HMI, HIST Pull As-Designed Plant/Process Engineering Network/Segment/Tag Data Out of EIS to REG Synch Creation/Update of As-Designed Process Engineering Network/Segment/Tag Data Out of EIS to REG Push Asset Removal/Installation into REG from CMS Pull Registry Data Out of REG to ERM, ERP, PORT, ORM, EAM, HMI, HIST, OPM, MES, CMS Synch Creation/Update of Registry Data Out of REG to ERM, ERP, EIS, ORM, EAM, HIST, OPM, MES, CMS Push Registry Data Into REG from ERM, ERP, ORM, EAM, HMI, HIST, OPM, MES, CMS Pull Usage Readings Out of HIST to EAM, ORM Synch Creation/Update of Usage Readings Out of HIST to EAM, ORM Push CBM Advisories into EAM from ORM Pull Maintenance Work Status/Work History Out of EAM to ORM, HMI, OPM Synch Creation/Update of Maintenance Work Status/Work History Out of EAM to ORM, HMI, OPM Pull EAM KPIs Out of EAM to PORT, ORM, OPM Synch Creation/Update of EAM KPIs Out of EAM to PORT, ORM, OPM Pull ORM KPIs Out of ORM to ERM, PORT, OPM Synch Creation/Update of ORM KPIs Out of ORM to ERM, PORT, OPM Pull Significant ORM Events Out of ORM to ERM, PORT, OPM Synch Creation/Update of Significant ORM Events Out of ORM to ERM, PORT, OPM Pull OPM KPIs Out of OPM to ERM, PORT, MES Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-Priority Scenarios

166 September Synch Creation/Update of OPM KPIs Out of OPM to ERM, PORT, MES Synch Product/Part Engineering Change Advisories Out of PDM to ORM, REG Synch Plant/Process Change Advisories Out of EIS to ORM, REG (OPC UA) Pull Current Operating Data and Events Out of CMS to ORM, OPM, HMI, HIST (OPC UA) Synch Current Operating Data and Events Out of CMS to ORM, OPM, HMI, HIST (OPC UA) Pull Historical Operating Data and Events Out of HIST to ORM, OPM Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-Priority Scenarios

167 September Scenarios Activated by Use Cases

168 September Frequently Asked Questions Q: What version of MIMOSA OSA-EAI should the industry use today? A: Use the latest production release of specifications – Version 3.2. Q: Does MIMOSA OSA-EAI compliance require a specific physical database structure to be used? A: No. Compliance looks at the resulting XML data in a Web Service to ensure it is compliant with the CRIS XML Schema. Suppliers can choose to physically store their data in optimal ways based on a particular database as long as they can generate the appropriate XML in the end. Q: Does one need to use database replication to exchange MIMOSA OSA-EAI data? A: No. In fact, persistence of CRIS data is not even addressed by MIMOSA OSA-EAI, though MIMOSA publishes a meta-data dictionary in XML, ORACLE, and SQL-Server script formats. MIMOSA OSA-EAI defines a common information model “language” which is typically utilized in point-to-point Web Services or used as the information content format in an Information Service Bus. The use of OSA-EAI CRIS XML content in an Information Service Bus has been successfully implemented in the Oil & Gas industry, and is the direction the Oil & Gas industry is moving.

169 September Frequently Asked Questions Q: How does MIMOSA OSA-EAI ensure that data generated by one application does not use the same primary key that another application uses? A: MIMOSA OSA-EAI is a global, peer-to-peer, common information model, assuming a centralized registration authority/service for each enterprise. Each enterprise has control of the process to register its platform/logistic management offices, fleet assets, segments, sensors, networks, and data dictionaries/taxonomies. MIMOSA OSA-EAI only specifies the format of the resulting Unique Integration Codes (UICs), which are universally-unique surrogate primary keys [keys without meaning except for integration]. The use of surrogate primary keys is the best practice in software engineering, since any key with meaning to an end-user could possibly be changed (or entered incorrectly) and subsequently need to be changed--not possible of a primary key. In addition, some assets are keyed differently in different information systems. This drives the need for AMC to have a registration authority in order to provide the method for applications to obtain/derive these OSA-EAI Unique Integration Codes (UICs).

170 September Frequently Asked Questions Q: How does MIMOSA OSA-EAI implement different role-based “views” of a platform asset? A: MIMOSA OSA-EAI allows up to 4 billion different segment breakdown views of an asset (called “Networks”) to be defined and then assigned to a User profile (called “Agent_Roles”). Q: Can MIMOSA OSA-EAI work “out of the box” or does it normally need to be configured with business rules, data dictionaries and taxonomies? A: The latter. MIMOSA OSA-EAI is a “language” which allows you to define standard meta-data, data dictionary entries and taxonomies for a given domain. OSA-EAI has been used to monitor California highways and bridges, sensored stationary manufacturing processes, jet aircraft, and trucks. The entity names in OSA-EAI never change (such as “Asset”), only the meta-data entries (such as those in “Asset_Type”) and the data dictionaries (such as “Asset Character Data Type”) which contain the meta-data relevant for all Assets in a given domain.

171 September Bibliography ►Byrne, John A., “The Horizontal Corporation, It’s about Managing Across, Not Up and Down”, Newsweek, December 20, ►Cook, Melissa. Building Enterprise Information Architectures, Reengineering Information Systems, Prentice-Hall, ►Howard, Philip. Bloor Research, SOA and Information Services: The Information Service Bus, March ibm.com/industries/government/doc/content/bin/soa_informa tion_services.pdf 03.ibm.com/industries/government/doc/content/bin/soa_informa tion_services.pdf ►Hatami, Mehdi. DM Direct, SOA: Providing Enterprise-Wide Information Access, April ►Zachman, John A. “A Framework for Information Systems Architecture,” IBM Systems Journal 26, no. 3, 1987.


Download ppt "September 2008 1 MIMOSA Open System Architecture for Enterprise Application Integration (OSA-EAI) Primer September 2008 Ken Bever MIMOSA CTO/Technical."

Similar presentations


Ads by Google