MIMOSA CTO/Technical Director

MIMOSA CTO/Technical Director kbever@mimosa.org
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 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Provide sample database and tools for further exploration/study
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 Goals of Class MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Extremely Complex, Constantly Moving Assets of Various Types MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Overwhelming Data Volumes MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Multiple Data “Languages” MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Feed Asset Capability Data Into My Production Optimization, Planning & Scheduling Systems? 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 Engineering Design Information and RCM Study Data? How Can I Access My Physical Plant Configuration and Installed Equipment Registry Components (Past & Present)? How Best to Integrate the 100+ Systems 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? MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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

How Best to Integrate the 100+ Systems?
Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Production Optimization, Planning & Scheduling Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] EPC & OEM Engineering Product Design Data & Reliability Study Data Serialized Asset Registry & Lifecycle Configuration Management Data Choice #1: Build Point-to-Point Proprietary Data Bridge Connections Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

How Best to Integrate the 100+ Systems?
Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Production Optimization, Planning & Scheduling Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] EPC & OEM Engineering Product Design Data & Reliability Study Data Proprietary Middleware Data Bridge Serialized Asset Registry & Lifecycle Configuration Management Data Serialized Asset Registry & Lifecycle Configuration Management Data Choice #2: Build Point-to-Proprietary Middleware Data Bridge Connections Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Teach Them To Speak the OpenO&M Languages!
Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Production Optimization, Planning & Scheduling Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] EPC & OEM Engineering Product Design Data & Reliability Study Data ISO 15926 Serialized Asset Registry & Lifecycle Configuration Management Data Choice #3: Require All Systems Communicate In an Open, Unambiguous Data Language Rather than using proprietary, point-to-point interfaces to integrate the large number of potential application platforms and their associated technical applications with each other, compliance with MIMOSA open system specifications provide a standards-based abstraction and integration layer. Applications can leverage the standards with a wide range of Technical Applications providing integration between the true real-time platform control environment and the transaction processing ERP environment. Adoption of Non-proprietary, Open Standards such will enable cost effective transition management for many different technical applications as they change over time. MIMOSA’s Open System Architecture for Condition Based Maintenance (OSA-CBM) is on-platform. Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS
MIMOSA OSA-EAI Design OSA-EAI Information Architecture WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS COMPUTER-DRIVEN APPLICATIONS APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS OSA-EAI Based Upon 5-Layer ISO Open Information Architecture Requirements MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS
MIMOSA OSA-EAI Design OSA-EAI Information Architecture WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS COMPUTER-DRIVEN APPLICATIONS OSA-EAI Based Upon 5-Layer ISO Open Information Architecture Requirements APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA OSA-EAI Design WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS
COMPUTER-DRIVEN APPLICATIONS OSA-EAI Based Upon 5-Layer ISO Open Information Architecture Requirements MIMOSA Common Relational Information Schema (CRIS) APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA OSA-EAI Design WORK FLOW PROCESSES PEOPLE-DRIVEN APPLICATIONS
COMPUTER-DRIVEN APPLICATIONS MIMOSA Data Access Web Services (Tech-XML / Tech-CDE) & MIMOSA Data Access Messaging (Tech-Message) OSA-EAI Based Upon 5-Layer ISO Open Information Architecture Requirements MIMOSA Common Relational Information Schema (CRIS) APPLICATION DATA & EVENTS AUTOMATION DATA & EVENTS MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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

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 September 2008

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 Faster ROI Gathers metadata Fosters seamless communication between applications Focuses communication for data analysis and project team members Establishes a consistent naming scheme September 2008

Why Use an OpenO&M Model?
Most Current Applications Are Designed to Work Closely-Coupled to a Supplier-Specific Proprietary Database Application A Proprietary Data Model Application A Transactional Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Software Engineering Best Practice Dictates A Separation of the Application from the Required Data it Needs Application A Proprietary Data Model Application A Transactional Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

World Class Enterprises Are Now Designing an Enterprise-owned Information Model Abstraction Layer Which Hides Proprietary Data Models Application A OpenO&M Model & Bus OpenO&M Information Model & OpenO&M Information Service Bus Proprietary Data Model Application A Transactional Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

This Allows Many New Applications to be Built With Just Knowledge of the Enterprise Information Model Application A Application B Application C OpenO&M Model & Bus OpenO&M Information Model & OpenO&M Information Service Bus Proprietary Data Model Application A Transactional Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Application B Application C OpenO&M Model & Bus OpenO&M Information Model & OpenO&M Information Service Bus OpenO&M Information Model Proprietary Data Model Application A Transactional Data Application A Transactional Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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

MIMOSA Tech-Message Support for “Fire-and-Forget” Pub/Sub Example
Application D Application A P P P Application E Application B P Secure Message Bus P P P Application F Application C 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 September 2008

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

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

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

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

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

MIMOSA’s Two Open Standards
INFORMATION SYSTEMS EMBEDDED SYSTEMS MIMOSA OSA-CBM Processing Architecture Standard MIMOSA OSA-EAI Information Architecture Standard At Platform Diagnostics Portable Diagnostic Tools Maintenance Logistics EAM, CMMS MIMOSA’s Two Open Standards MIMOSA's Open Systems Architecture for Condition-Based Maintenance (OSA-CBM) specification is an ISO compliant on-board condition monitoring and diagnostic (CM&D) processing architecture specification. MIMOSA's Open Systems Architecture for Enterprise Application Integration (OSA-EAI) ) is compliant as a CM&D information architecture specification with ISO and facilitates the integration of CM&D information into enterprise systems Tightly Coupled Systems Loosely Coupled Systems MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008 Copyright 2007 MIMOSA

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 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Based Upon 5-Layer ISO 13374-2 Open Information Architecture Requirements
Data Document Definitions Reference Data Library Implementation Data Model Conceptual Information Model Semantic Definitions OSA-EAI Based Upon 5-Layer ISO Open Information Architecture Requirements MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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

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 MIMOSA OSA-EAI Specification MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008 Copyright 2007 MIMOSA

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 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008 Copyright 2007 MIMOSA

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

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) OSA-EAI Open Object Registry Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 MIMOSA OSA-EAI Specification MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Understanding UML Class Diagrams
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. Understanding UML Class Diagrams MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. Understanding UML Class Diagrams MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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: = 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. Understanding UML Class Diagrams MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. Understanding UML Class Diagrams MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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) OSA-EAI Open Object Registry Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Enterprise Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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”. OSA-EAI Enterprise Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Enterprise Object in OSA-EAI Common Conceptual Object Model (CCOM) MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Sample of MIMOSA-Maintained OSA-EAI Enterprise Entries MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Site Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Site Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Site Object in OSA-EAI Common Conceptual Object Model (CCOM) MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Best Practice Use of Site in Fleet Applications MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Database Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Site Object in OSA-EAI Common Conceptual Object Model (CCOM) MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Best Practice Use of Database in Fleet Applications MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Model and Manufacturer Objects MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Model and Manufacturer Objects in OSA-EAI Common Conceptual Object Model (CCOM) MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Best Practice Use of Model in Fleet Applications MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 OSA-EAI Segment Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 OSA-EAI Segment Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Segment Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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) Best Practice Use of Segment in Fleet Applications MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 OSA-EAI Asset Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Asset Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Segment Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Best Practice Use of Asset in Fleet Applications MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Difference Between an Asset and Segment MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Difference Between an Asset and Segment MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. OSA-EAI Agent Object MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. Mandatory Use of Unique Integration Codes for OSA-EAI Compliance MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Example of the “As-Designed” Physical Area Decomposition Segment Network for Missile Model A-405 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Example of the “As-Designed” Functional Decomposition Segment Network for Missile Model A-405 Note: Blue highlighted segments are included in both network hierarchies MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Example of the “As-Built” Functional Decomposition Segment Network for Missile Asset Model A-405 S/N: F Note: Dark green segments are “leaf” segments where serialized assets can be installed MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Example of an Install & Removal of Motor Asset S/N: 4324 into Rocket Motor Segment Motor P/N AB-C800 S/N: 4324 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

CRIS Representation of Object Registry Common Relational Information Schema (CRIS) Common Conceptual Object Model (CCOM) Terminology Dictionary CRIS Representation of Object Registry MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA Interface Types MIMOSA Data Categ. Type MIMOSA Support Type MIMOSA Functionality Type MIMOSA Access Type Enterprise Enterprise Type Row Status Type Database MIMOSA Interfaces Site Type Site Segment Child Segment Asset On Segment Asset Model Segment Type Asset Type CRIS Representation of Object Registry Manu- facturer Site Database 1 to many(*) relationship MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

CRIS Representation of Object Registry 1 to many(*) relationship
MIMOSA Interface Types MIMOSA Data Categ. Type MIMOSA Support Type MIMOSA Functionality Type MIMOSA Access Type Enterprise Enterprise Type Asset Readiness Type Purchase Condition Type Row Status Type Database MIMOSA Interfaces Site Type Site Asset Owner History Model Child Segment Child Asset Child Segment Asset On Segment Asset Model Segment Numeric Data Type Segment Numeric Data Asset Numeric Data Asset Numeric Data Type Model Numeric Data Segment Character Data Type Segment Character Data Asset Character Data Asset Character Data Type Model Character Data Segment BLOB Data Asset BLOB Data Model BLOB Data BLOB Data Type BLOB Content Type Segment Type Asset Type Manu- facturer CRIS Representation of Object Registry Site Database 1 to many(*) relationship Agent Agent Type Reference Unit Type Engineering Unit Type Engineering Unit Enumerated MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

CRIS Meta-Data Reference Data Library CRIS Reference Data Library Common Relational Information Schema (CRIS) Common Conceptual Object Model (CCOM) Terminology Dictionary CRIS Meta-Data Reference Data Library MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 CRIS Meta-Data Reference Data Library MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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” 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 CRIS Meta-Data Reference Data Library MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA Information Manager Use Case #1 Example: M1A2 SEP MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 Review of OSA-EAI Open Object Registry Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Open Reliability Management
MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008 Copyright 2007 MIMOSA

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 OSA-EAI Open Reliability Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008 Copyright 2007 MIMOSA

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 OSA-EAI Open Reliability Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Failure Modes and Effects Analysis (FMEA) The FMEA method is a tool for identifying and evaluating the function failure modes of a system as well as how to detect and monitor for each of the failure modes. The process starts by describing the function of each component or sub-system (model or model segment). This analysis will be conducted for only the components and sub-systems determined to be the top platform degraders. The next step is to list the failure modes (hypothetical events) that prevent the implementation of that function. For this analysis, only the dominant and critical failure modes will be listed. The symptoms and effects (hypothetical events) of each failure mode are also listed through the FMEA process. An example of the general FMEA format from a military ground vehicle is shown. MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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 OSA-EAI Open Reliability Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Open Condition Management

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 OSA-EAI Open Condition Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008 Copyright 2007 MIMOSA

Condition Monitoring Core Objects: MeasurementLocation & MeasurementEvent MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Dynamic Data Model MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Binary Large Object (BLOB) Data Model MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Sample Data Model MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Test Data Model MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

CRIS Condition Management Example: USS Nimitz MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. MIMOSA Information Manager Use Case #3 Example: M1A2 SEP MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA Information Manager Use Case #3 Example: M1A2 SEP MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Open Maintenance Management

MIMOSA Open Maintenance Management
OSA-EAI Open Maintenance Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

OSA-EAI Open Capability Forecast Management

OSA-EAI Open Capability Forecast Management
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 OSA-EAI Open Capability Forecast Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008 Copyright 2007 MIMOSA

Open Maintenance Management Open Reliability Management Open Object Registry Management OSA-EAI Open Condition Management MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI) Architecture
Tech-CDE-Services For SOAP Tech-CDE Clients & Servers Tech-XML-Web For HTTP Tech-XML Clients & Servers Tech-XML-Services For SOAP Tech-XML Clients & Servers Compliant SOA Application Definitions Tech-Doc Producer& Consumer XML Stream or File Tech-CDE Client & Server XML Stream or XML File Tech-XML Client & Server XML Stream or XML File Compliant Application Service Definitions Tech-Doc CRIS XML Document Schema Tech-CDE Aggregate CRIS XML Transaction Client & Server Schema Tech-XML Atomic CRIS XML Transaction Client & Server Schema XML Content Definition CRIS Reference Data Library MetaData Taxonomy Common Relational Information Schema (CRIS) Implementation Model OSA-EAI Common Conceptual Object Model (CCOM) Conceptual Model OSA-EAI Terminology Dictionary Semantic Definitions 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) Technology Types [Tech-] REL (RCM/FMECA/Model Reliability Information) TRACK (Physical Asset GeoSpatial Tracking Information) MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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

MIMOSA Specification Development Process Flowchart
OSA-EAI MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

MIMOSA Specification Release History
OSA-EAI Beta Version, Members-only Release Final Version, Production Release MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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

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

Teach Them To Speak the OpenO&M Languages!
Enterprise HR, Financial, Materiel, Logistics, & Mission Capability Data Production Optimization, Planning & Scheduling Maintenance System Data P4T2 (problem, plan, people, parts, tools, and time] EPC & OEM Engineering Product Design Data & Reliability Study Data ISO 15926 Serialized Asset Registry & Lifecycle Configuration Management Data Choice #3: Require All Systems Communicate In an Open, Unambiguous Data Language Rather than using proprietary, point-to-point interfaces to integrate the large number of potential application platforms and their associated technical applications with each other, compliance with MIMOSA open system specifications provide a standards-based abstraction and integration layer. Applications can leverage the standards with a wide range of Technical Applications providing integration between the true real-time platform control environment and the transaction processing ERP environment. Adoption of Non-proprietary, Open Standards such will enable cost effective transition management for many different technical applications as they change over time. MIMOSA’s Open System Architecture for Condition Based Maintenance (OSA-CBM) is on-platform. Control Systems, Plant Data Historians & Plant Asset Health/Safety/Environmental Systems Data MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

End User/EPC Engineering Data Supported by ISO 15926
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 September 2008

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 September 2008

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 September 2008

OEM Model Reference Data Supported by ISO 15926
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 September 2008

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) September 2008

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 September 2008

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 September 2008

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 September 2008

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 September 2008

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

Mike Brooks – Chevron Vision
name services metadata model maps abstraction not proprietary interoperability MIMOSA OSA-EAI Standard for Fleets June 17, 2008 September 2008 156 September 2008 156

Mike Brooks – Chevron Vision
2 1 OpenO&M September 2008

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

Systems Requiring Interoperability
September 2008

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 September 2008

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

Oil & Gas/PetroChem Industry OpenO&M Interoperability Scenarios
RFQs & POs (OAGIS, CIDX) RFQs & POs (OAGIS, CIDX) ERM PORT ERP Enterprise Risk Management System, Enterprise Resource Planning System & Enterprise KPI/Event Portals Suppliers Customers RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX) Production Orders (OAGIS, CIDX, B2MML) Production Performance (B2MML) RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX) MES KPIs (B2MML) PDM Production Forecasting & Scheduling Systems MES “As-Designed” & “As-Built” Product/Part Data (ISO & MIMOSA) EOM REG Event-Oriented Message Bus OEM Product Data Mgmt. Systems OPM KPIs (MIMOSA & B2MML) Forecasted Demand (B2MML & PRODML) Asset Performance Prediction (B2MML & PRODML) Product/Part Engineering Change Advisories Detailed Prod. Performance (B2MML) Operational Performance Modeling & Optimization Systems OPM Detailed Prod. Schedules (B2MML) Planned Asset Unavailability Schedule (MIMOSA & B2MML) “As-Installed” & “As-Maintained” Master Data (MIMOSA & B2MML) EIS ORM KPIs (MIMOSA & B2MML) Significant Actual & Early Warning ORM Events (MIMOSA) Hist. Op. Data & Events (OPC UA-HDA) Maintenance Work Status, & Work History (MIMOSA) This figure shows the vision of how MIMOSA, ISA-95 and OPC could be used together to integrate maintenance and operational plans. The bottom of the figure shows different condition monitoring and inspection functions. Some done by automation systems, some manually and others by specialized equipment. For automation system based measurements OPC can be used to move the data to a control/SCADA system or a historian. For specialized measurement (perhaps like vibration) or manual asset inspections different systems are used – The MIMOSA interfaces are designed to pass this information between systems, OPC UA will be used as the “data pipe”. EAM and Asset Health/DSS systems will use the asset measurement and inspection data to predict failures, issue work orders, track maintenance work. The Asset Capability Forecasting and Asset Optimization DSS function uses the EAM and Asset Health DSS data to forecast & schedule maintenance work to optimize asset availability. In parallel ERP-MES-Control systems may use the ISA-95 standard to pass production schedules from the ERP level to the control system level and report on actual production back to the ERP level. In most cases today there is only a weak link between the production schedules/forecasts and the maintenance schedules/forecasts. OpenO&M’s vision is to use the ISA-95 and MIMOSA interfaces to permit this to become a more tightly coupled interface. This would permit production schedules to be based upon real-time, condition-monitoring based maintenance forecasts. Likewise maintenance schedules could be adjusted to reflect changes in production schedules to minimize downtime that might impact production. DCS HMI Control/SCADA, HMI, & Historians ORM Enterprise Asset Management Systems EAM Operational Risk Management Systems (EH&S, PSMS, AHMS, QMS) CBO Advisories (MIMOSA) CBM Advisories (MIMOSA) Plant/Process “As-Installed” & “As-Maintained” & Configuration Management Historians Network/Segment/Asset/Tag Registry Op. Work Status & Work History (MIMOSA) HIST Maint. KPIs (MIMOSA) Usage Readings (MIMOSA) Plant/Process Engineering As-Designed & As-Built Network/Segment/Tag Information, Config. Mgmt. Historians Full-resolution Condition Data & Events (MIMOSA) CBM/Calib. Schedule (MIMOSA) CBM/Calib. Work Completed (MIMOSA) Control Data (Fieldbus) Asset Removals & Installations (MIMOSA) Current Op. Data & Events (OPC UA DA/A&E) CMS Measurements, Events, Inspections, Calibrations, Conditions, Usage, and Sensed O&M Actions DEV 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) “As-Designed” & “As-Built” Plant/Process Engineering Data (ISO & MIMOSA) Plant/Process Engineering Change Advisories MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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

ERM PORT PDM MES EOM REG OPM EIS DCS HMI ORM EAM HIST CMS DEV
Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-Priority Scenarios RFQs & POs (OAGIS, CIDX) RFQs & POs (OAGIS, CIDX) ERM PORT ERP Enterprise Risk Management System, Enterprise Resource Planning System & Enterprise KPI/Event Portals Suppliers Customers RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX) Production Orders (OAGIS, CIDX, B2MML) Production Performance (B2MML) RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX) MES KPIs (B2MML) PDM 1 “As-Designed” & “As-Built” Product/Part Data (ISO & MIMOSA) Production Forecasting & Scheduling Systems MES EOM 2 REG Event-Oriented Message Bus OEM Product Data Mgmt. Systems OPM KPIs (MIMOSA & B2MML) Forecasted Demand (B2MML & PRODML) Asset Performance Prediction (B2MML & PRODML) 3 21 22 Detailed Prod. Performance (B2MML) Operational Performance Modeling & Optimization Systems OPM Product/Part Engineering Change Advisories 23 7 Detailed Prod. Schedules (B2MML) Planned Asset Unavailability Schedule (MIMOSA & B2MML) 8 “As-Installed” & “As-Maintained” Master Data (MIMOSA & B2MML) EIS Hist. Op. Data & Events (OPC UA-HDA) ORM Risk KPIs (MIMOSA & B2MML) Significant Actual & Early Warning ORM Events (MIMOSA) 17 18 19 20 Maintenance Work Status, & Work History (MIMOSA) 27 DCS HMI Control/SCADA, HMI, & Historians ORM Enterprise Asset Management Systems EAM Operational Risk Management Systems (EH&S, PSMS, AHMS, QMS) 28 CBO Advisories (MIMOSA) CBM Advisories (MIMOSA) 9 Plant/Process “As-Installed” & “As-Maintained” & Configuration Management Historians Segment/Asset/Tag Registry 13 14 Op. Work Status & Work History (MIMOSA) 12 15 16 HIST 10 11 Maint. KPIs (MIMOSA) Usage Readings (MIMOSA) Plant/Process Engineering As-Designed & As-Built Segment/Tag Information, Configuration Management Historians 25 26 Full-resolution Condition Data & Events (MIMOSA) CBM/Calib. Schedule (MIMOSA) CBM/Calib. Work Completed (MIMOSA) Control Data (Fieldbus) Asset Removals & Installations (MIMOSA) Current Op. Data & Events (OPC UA DA/A&E) CMS Measurements, Events, Inspections, Calibrations, Conditions, Usage, and Sensed O&M Actions 6 DEV 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) “As-Designed” & “As-Built” Plant/Process Engineering Data (ISO & MIMOSA) 4 5 24 Plant/Process Engineering Change Advisories MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-Priority Scenarios
1 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 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-Priority Scenarios
22 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 23 24 25 26 27 28 MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

Scenarios Activated by Use Cases
MIMOSA OSA-EAI Standard for Fleets September 2008 September 2008

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. September 2008

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). September 2008

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. September 2008

Bibliography Byrne, John A., “The Horizontal Corporation, It’s about Managing Across, Not Up and Down”, Newsweek, December 20, 1993. Cook, Melissa. Building Enterprise Information Architectures, Reengineering Information Systems, Prentice-Hall, 1996. Howard, Philip. Bloor Research, SOA and Information Services: The Information Service Bus, March 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. September 2008

MIMOSA CTO/Technical Director

Similar presentations

Presentation on theme: "MIMOSA CTO/Technical Director"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

MIMOSA CTO/Technical Director

Similar presentations

Presentation on theme: "MIMOSA CTO/Technical Director"— Presentation transcript:

Similar presentations

About project

Feedback