September 2008 1 MIMOSA Open System Architecture for Enterprise Application Integration (OSA-EAI)...

September 2008 1

MIMOSA Open System Architecture for

Enterprise Application Integration (OSA-EAI) Primer

MIMOSA Open System Architecture for

Enterprise Application Integration (OSA-EAI) Primer

September 2008

Ken BeverMIMOSA CTO/Technical Director

[email protected]

Principal Consultant, Assetricity LLC AMRDEC Software Engineering Directorate

[email protected]

513-276-4105

September 2008 2

Goals of TrainingGoals 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

September 2008 3

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

September 2008 4



►Extremely complex, constantly moving assets of various types





September 2008 5



►Extremely complex, constantly moving assets of various types





September 2008 6

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 PlantCapability 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)?



How Can I Feed Asset Capability Data Into My Production Optimization, Planning & Scheduling Systems?

September 2008 7

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

Configuration

Management Data



Production Optimization, Planning & Scheduling

September 2008 8









time]

Serialized Asset


Configuration

Management Data


How Best to Integrate the 100+ Systems?How Best to Integrate the 100+ Systems?

September 2008 9









time]

Serialized Asset


Configuration

Management Data


Serialized Asset Registry

& Lifecycle Configuration Management

Data

How Best to Integrate the 100+ Systems?How Best to Integrate the 100+ Systems?

Proprietary MiddlewareData Bridge

September 2008 10









time]

Serialized Asset


Configuration

Management Data


Teach Them To Speak the OpenO&M Languages! Teach Them To Speak the OpenO&M Languages!

ISO 15926ISO 15926

F O U N D A T I O N

September 2008 11

MIMOSA OSA-EAI DesignMIMOSA OSA-EAI Design

COMPUTER-DRIVENAPPLICATIONS

WORK FLOW PROCESSES

PEOPLE-DRIVENAPPLICATIONS

APPLICATION DATA & EVENTS

OSA-EAI Information Architecture

AUTOMATION DATA & EVENTS

September 2008 12



WORK FLOW PROCESSES





September 2008 13



WORK FLOW PROCESSES





September 2008 14



WORK FLOW PROCESSES


MIMOSA Common Relational Information Schema (CRIS)



September 2008 15



WORK FLOW PROCESSES



MIMOSA Data Access Web Services (Tech-XML / Tech-CDE) &MIMOSA Data Access Messaging (Tech-Message)



September 2008 16



WORK FLOW PROCESSES



MIMOSA Data Access Web Services (Tech-XML / Tech-CDE) &MIMOSA Data Access Messaging (Tech-Message)



September 2008 17

Integration Platform

Suncor View -- A Coordinated Approach to Suncor View -- A Coordinated Approach to Full Integration within the EnterpriseFull 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 Mes

sage

Tra

nspo

rt

Data

Data

Data

Data

Data

Data

Data

DataFinancialHRProductionDocumentsProceduresPlanningEHSMaintenanceSupply

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”

Bas

icA

dmin

Adv

ance

d

Environmental Monitoring System Data

September 2008 18

What is an OpenO&M Information Model?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 19

Why Use an OpenO&M Information Model?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

September 2008 20

Why Use an OpenO&M Model?Why Use an OpenO&M Model?

Most Current Applications Are Designed to Work Closely-Coupled to a Supplier-Specific Proprietary Database

Application A

Application ATransactional Data

ProprietaryData Model

September 2008 21


Software Engineering Best Practice Dictates A Separation of the Application from the Required Data it Needs

Application A



September 2008 22


World Class Enterprises Are Now Designing an Enterprise-owned Information Model Abstraction Layer Which Hides Proprietary Data Models

Application A


OpenO&M Information Model &OpenO&M Information Service Bus

OpenO&MModel & Bus


September 2008 23


This Allows Many New Applications to be Built With Just Knowledge of the Enterprise Information Model

Application A

Application A Transactional Data


OpenO&MModel & Bus


Application B Application C

September 2008 24

OpenO&M Information StrategyOpenO&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



OpenO&MModel & Bus

Application B Application C



OpenO&M Information

Model

September 2008 25

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

MIM

OS

A O

SA

-EA

I S

erv

ices

B2B GatewayProvisioning Framework

MIM

OS

A O

SA

-EA

I S

erv

ices

Subscriber Applications

PublisherApplication

Publishes “system of record” change events

Store-and-Forward Caching

Receives eventsTech-Message Header with Tech-CDE, Tech-

Doc, or Tech-XML Body

“System of record” events


“System of record” events“System of record” events

MIMOSA Tech-Message Support for “Fire-and-Forget” Pub/Sub PatternMIMOSA Tech-Message Support for “Fire-and-Forget” Pub/Sub Pattern

September 2008 26

Application A

Application B

Application C

Application D

Application E

Application F

Secure Message Bus

P

P

P

P

P

P

P P

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 ExampleMIMOSA Tech-Message Support for “Fire-and-Forget” Pub/Sub Example

September 2008 27



Topic Registry Management

System Service Management

Security


Message Routing


MIM

OS

A O

SA

-EA

I S

erv

ices


MIM

OS

A O

SA

-EA

I S

erv

ices

Subscriber Applications


PublisherApplication

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



Delivered to Subscriber A

Delivered to Subscriber C

MIMOSA Tech-Message Support for “Sync” Pub/Sub Pattern

MIMOSA Tech-Message Support for “Sync” Pub/Sub Pattern

September 2008 28



System Service Maagement

Security


Message Routing


MIM

OS

A O

SA

-EA

I S

erv

ices


MIM

OS

A O

SA

-EA

I S

erv

ices

Receiver of Push

Application


Sender of Push

Application

Requests MIMOSA CRIS-formatted Information

with a-priori Knowledge of Name of Target Receiver

Application

Results of Push


Pushed Data

Responds to Push in an Appropriate Way

Pushed Data

Results of Push

MIMOSA Tech-Message Support for Targeted “Push” Pattern

MIMOSA Tech-Message Support for Targeted “Push” Pattern

September 2008 29




Security


Message Routing


MIM

OS

A O

SA

-EA

I S

erv

ices


MIM

OS

A O

SA

-EA

I S

erv

ices

Query Server Application

Query Client Application

Responds to QueriesRequests MIMOSA CRIS-

formatted Information with a-priori Knowledge of

Name of Target Server Application


Query Results

Query

Query Results

Query

MIMOSA Tech-Message Support for Targeted “Pull” Pattern

MIMOSA Tech-Message Support for Targeted “Pull” Pattern

September 2008 30




Security


Message Routing


MIM

OS

A O

SA

-EA

I S

erv

ices


MIM

OS

A O

SA

-EA

I S

erv

ices

Query Client Application

Requests MIMOSA CRIS-formatted Information

without a-priori Knowledge of Server

Applications



Query Results

Query

Query Server Applications

Query

Query


Query Results

Query Results

Query Results

MIMOSA Tech-Message Support for Untargeted “Scatter/Gather” PatternMIMOSA Tech-Message Support for Untargeted “Scatter/Gather” Pattern

September 2008 31

Tech-Message BusOnRamp & OffRamp

Computer A

OpenO&M Information Service Bus


Vendor App

Computer B



Vendor App

MIMOSA Tech-Message Services for an OpenO&M Information Service Bus

MIMOSA Tech-Message Services for an OpenO&M Information Service Bus

September 2008 32

MIMOSA’s Two Open Standards MIMOSA’s Two Open Standards

Tightly Coupled Systems

Loosely Coupled Systems

INF

OR

MA

TIO

N

SY

ST

EM

S

MIMOSAOSA-EAI

Information Architecture

Standard

EM

BE

DD

ED

S

YS

TE

MS

MIMOSA OSA-CBM Processing

ArchitectureStandard

At Platform Diagnostics

Portable Diagnostic

Tools

Maintenance Logistics

EAM, CMMS

Copyright 2007 MIMOSA

September 2008 33

ISO 13374 StandardISO 13374 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 13374 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

September 2008 34

OSA-EAI Based Upon 5-Layer ISO 13374-2 Open Information Architecture Requirements


Conceptual Information Model

Implementation Data Model

Reference Data Library

Semantic Definitions

Data Document Definitions

ISO 13374-2 Open Information Architecture Requirements

September 2008 35



Common Conceptual Object Model (CCOM)

Common Relational Information Schema (CRIS)

CRIS Reference Data Library

Terminology Dictionary

Tech-Doc & Tech-CDE XML Document Schema


September 2008 36

MIMOSA OSA-EAI SpecificationMIMOSA OSA-EAI Specification

► ISO 13374 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

September 2008 37

MIMOSA OSA-EAI InterfacesMIMOSA 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


September 2008 38

MIMOSA OSA-EAI InterfacesMIMOSA 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


September 2008 39

Open Maintenance Management

Open Reliability

Management

Open Condition

Management

OpenObject

RegistryManagement

MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI)



September 2008 40

OpenObject

RegistryManagement

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)

September 2008 41

MIMOSA OSA-EAI SpecificationMIMOSA OSA-EAI Specification

► ISO 13374 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

September 2008 42

Understanding UML Class DiagramsUnderstanding 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.

September 2008 43


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.

September 2008 44


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 = zero1 = one1..* = 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.

September 2008 45


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.

September 2008 46

OpenObject

RegistryManagement



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)

September 2008 47



► 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.

September 2008 48



►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 e-mail the OpenO&M Enterprise Registrar at [email protected] with the name of the organization, requested USER_TAG_IDENT point of contact name, title, phone number, and e-mail 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”.

September 2008 49



+enterpriseUIC : long(idl)+userID : string(idl)

Enterprise

+enTypeID : long(idl)+userID : string(idl)

EnterpriseType

*

+Classified as

1

September 2008 50



Enterprise NameEnterprise User Tag

Identifier

Enterprise Type (sole prop, partnership, for-

profit corp., not-for-profit, governmental organization)

Enterprise-UIC

Enterprise-UIC (Hex format)

Allied-Signal Inc. For-profit corp. 1066 0000042AAmerican Institute of Architects AIA Not-for-Profit 1046 00000416BAE Systems Information For-profit corp. 1070 0000042EBoeing BA For-profit corp. 1001 000003E9Building Owners & Managers Association BOMA Not-for-Profit 1047 00000417

Construction Specifications Institute CSI Not-for-Profit 1048 00000418Construction Users Roundtable CURT Not-for-Profit 1049 00000419FIATECH FIATECH Not-for-Profit 1045 00000415General Dynamics Land Systems Inc. For-profit corp. 1071 0000042FGeneral Electric Company For-profit corp. 1068 0000042CHoneywell HON For-profit corp. 1031 00000407Hydraulic Institute HI Not-for-Profit 1051 0000041BInternational Alliance for Interoperability IAI Not-for-Profit 1044 00000414International Facilities Management Association IFMA Not-for-Profit 1050 0000041ALockheed Martin Corp. For-profit corp. 1067 0000042BMIMOSA MIMOSA Non-profit 0 00000000Northrop Grumman Systems Corp. For-profit corp. 1069 0000042DOpen Geospatial Consortium OGC Not-for-Profit 1043 00000413Open Standards Consortium for Real Estate OSCRE Not-for-Profit 1042 00000412Penn State University PSU Not-for-Profit corp. 1063 00000427SAIC SAIC For-profit corp. 1065 00000429SAP AG SAP For-profit corp. 1038 0000040E

September 2008 51



Enterprise NameEnterprise User Tag

Identifier

Enterprise Type (sole prop, partnership, for-

profit corp., not-for-profit, governmental organization)

Enterprise-UIC

Enterprise-UIC (Hex format)

U.S. Government USGOV Governmental org. 1014 000003F6United States Army Corps of Engineers USACE Governmental org. 1041 00000411United States Coast Guard USCG Governmental org. 1039 0000040FUnited States Department of Defense USDOD Governmental org. 1015 000003F7

United States Department of the Air Force USAF Governmental org. 1016 000003F8United States Department of the Army USARMY Governmental org. 1017 000003F9United States Department of the Army, Aviation and Missile Command AMCOM Governmental org. 1053 0000041DUnited States Department of the Army, Communications and Electronics Command CECOM Governmental org. 1054 0000041E

United States Department of the Army, Tank Automotive Command TACOM Governmental org. 1062 00000426United States Department of the Navy USNAVY Governmental org. 1018 000003FAUnited States General Services Administration USGSA Governmental org. 1040 00000410United States Marine Corps (USMC) USMC Governmental org. 1019 000003FBUnited States National Guard USNG Governmental org. 1020 000003FCUS Army LOGSA LOGSA Governmental org. 1072 00000430Westar Aerospace & Defense Group WESTAR For-profit corp. 1055 0000041F

September 2008 52



► 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.

September 2008 53



► 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.

September 2008 54



+enterpriseUIC : long(idl)+userID : string(idl)

Enterprise

+siteID : long(idl)+userID : string(idl)+templateYN : boolean(idl)

Site

1

+Controls*

+stTypeID : long(idl)+userID : string(idl)+mobile_YN : boolean(idl)

SiteType

*

+Classified as

1

*

* +enTypeID : long(idl)+userID : string(idl)

EnterpriseType

*

+Classified as

1

1

+Registers*

September 2008 55



►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

September 2008 56

OSA-EAI Open Object Registry ManagementOSA-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.

September 2008 57




Site (Enterprise Registration Entity)

+databaseID : long(idl)+userID : string(idl)

Database

1

+Registers*

September 2008 58

Best Practice Use of Database in Fleet Applications

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

September 2008 59



► 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.

September 2008 60

1

+R

egis

ters

*




+manufID : long(idl)+userID : string(idl)

Manufacturer


Database

1

+Registers*

*+Maintains0..1

*

-Manufactured by

1

*

+Has Child Model(s)*

-modelID : long(idl)-userID : string(idl)-prodFamily : string(idl)-prodFamilyMember : string(idl)-prodFamilyMemberRev : string(idl)-partNumber : string(idl)

Model

*

+Maintains0..1

+asTypeID : long(idl)+userID : string(idl)

AssetType*+Belongs to Class

1

September 2008 61

OSA-EAI Open Object Registry ManagementOSA-EAI Open Object Registry ManagementModel

+value : string(idl)

ModelCharacterData

1

-Is Topic Of*

+astCharDataTypeID : long(idl)+userID : string(idl)

AssetCharacterDataType

-Type of

1

*

+refUnitTypeID : long(idl)+userID : string(idl)

ReferenceUnitType

-Default type of 0..1

*

+engUnitTypeID : long(idl)-userID : string(idl)

EngineeringUnitType1

-References

*

-With units of

1

*

Database

1

-Maintains*

1

-Maintains *

+value : double(idl)

ModelNumericData

1

-Is Topic Of*

+astNumDataTypeID : long(idl)+userID : string(idl)

AssetNumericDataType

-Type of

1*

-Default type of

0..1

*

1

-Maintains*

+value : object(idl)+name : string(idl)

ModelBlobData

1

-Is Topic Of

*

+blobDataTypeID : long(idl)+userID : string(idl)

BlobDataType

-Binary type of

1*

+blobContentTypeID : long(idl)+userID : string(idl)

BlobContentType

-Content type of

1

*

-With units of

1

*

1

-Maintains

*

1

-Maintains*

1

-Maintains *

September 2008 62



►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

September 2008 63



► 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

September 2008 64



► 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

September 2008 65



► 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.

September 2008 66




+segmentID : long(idl)+userID : string(idl)

Segment

+sgTypeID : long(idl)+userID : string(idl)

SegmentType


Database

1

+Registers*

1+Maintains *

*

+Composed of*

*

+Classified as

1

*

+Has Child Type(s)*

0..1 *

*

+Maintains 0..1

+Functionally Equivalent To

0..1

0..1

Model

September 2008 67


Model

Network

+utcFrom+utcTo

AssetModelHistory

**

+utcFrom+utcTo

AssetValidNetworkHistory

*

*

Asset

Segment

Segment*

+Classified as1

-From* *

-To *

-orderingSeq : long(idl)

SegmentNetworkConnect

*

+Classified as

1

+netConnTypeID : long(idl)+userID : string(idl)

NetworkConnectionType

MIMOSA Entries:

Primary Backup

+netTypeID : long(idl)+userID : string(idl)

NetworkType

September 2008 68


Segment


SegmentCharacterData

1

+Is Topic Of*

+sgCharDataTypeID : long(idl)+userID : string(idl)

SegmentCharacterDataType

+Type of

1*


ReferenceUnitType

+Default type of 0..1

*



+References

*

+With units of

1

*

Database

1

+Maintains*

1+Maintains *


SegmentNumericData

1

+Is Topic Of*

+sgNumDataTypeID : long(idl)+userID : string(idl)

SegmentNumericDataType

+Type of

1*

+Default type of

0..1

*

1

+Registers*


SegmentBlobData

1

+Is Topic Of*


BlobDataType

+Binary type of

1*


BlobContentType

+Content type of

1

*

+With units of

1

*

1+Registers

*

1

+Maintains

*

1

+Maintains *

1

+Maintains

*

+csTypeID : long(idl)+userID : string(idl)+minValue : long(idl)+maxValue : long(idl)

CriticalityScaleType

0..1*

September 2008 69



► 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)

September 2008 70



► 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

September 2008 71



► 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.

September 2008 72



► 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.

September 2008 73


+assetID : long(idl)+userID : string(idl)

Asset

+asTypeID : long(idl)+userID : string(idl)

AssetType

+manufID : long(idl)+userID : string(idl)

Manufacturer


Database

1

+Registers*

*

+Model of

0..1

1

+Maintains *

*

+Composed of*

*

+Maintains

0..1

*

+Classified as1 *

+Belongs to Class1

+Functionally Equivalent To

0..1 0..1

*

+Manufactured By0..1

ModelSegment

Site

September 2008 74


Model

Network

+utcFrom+utcTo

AssetModelHistory

**

+utcFrom+utcTo

AssetValidNetworkHistory

*

*

Asset

Segment

Segment*

+Classified as1

-From* *

-To *

-orderingSeq : long(idl)

SegmentNetworkConnect

*

+Classified as

1

+netConnTypeID : long(idl)+userID : string(idl)

NetworkConnectionType

MIMOSA Entries:

Primary Backup

+netTypeID : long(idl)+userID : string(idl)

NetworkType

Segment

+utcInstalled+utcRemoved

AssetUtilizationHistory

* *

September 2008 75

OSA-EAI Open Object Registry ManagementOSA-EAI Open Object Registry ManagementAsset


AssetCharacterData

1

-Is Topic Of*

+asCharDataTypeID : long(idl)+userID : string(idl)

AssetCharacterDataType

-Classified as

1

*


ReferenceUnitType

-Default type of 0..1

*



-References

*

-With units of

1

*

Database

1

-Maintains*

1

-Maintains *


AssetNumericData

1

-Is Topic Of*

+asNumDataTypeID : long(idl)+userID : string(idl)

AssetNumericDataType

-Classified as

1*

-Default type of

0..1

*

1

-Maintains*


AssetBlobData

1

-Is Topic Of*


BlobDataType

-Binary type of

1

*


BlobContentType

-Content type of

1

*

-With units of

1

*

1

-Maintains

* 1

-Maintains*

1

-Maintains *

+purchCondTypeID : long(idl)+userID : string(idl)

PurchaseCondType

+asReadinessTypeID : long(idl)+userID : string(idl)

AssetReadinessType

*

-Current Readiness

0..1

*+Readiness When Purchased 0..1

*

+With Condition

0..1

1

-Maintains

*

1

-Maintains

*

Site

+gmtPurchased

AssetOwner

*

*+Owned By

September 2008 76



► 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

September 2008 77



►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

September 2008 78



►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

September 2008 79


► 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.

September 2008 80



► 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.

September 2008 81



Physical Area DecompositionSegment Network for Missile

Model A-405

Missile

Nose Cone Guidance Housing Missile Body

Guidance Electronics

Fixed Fins

Electronics Unit

Forward Battery Pack

Tail Unit

Sensor Unit Sensor AmpTail Unit Casing

Guidance Fins

Fin Control Unit

Rocket MotorRear Battery

Pack

MissileModel A-405

<<model>> <<segment>>

<<segment>> <<segment>> <<segment>> <<segment>>

<<segment>> <<segment>> <<segment>> <<segment>> <<segment>> <<segment>>

<<segment>> <<segment>> <<segment>><<segment>><<segment>>

Model A-405

September 2008 82



Missile

Structure Guidance Function Explosive Function

Guidance Electronics Function

Directional Control Function

Sensor FunctionProcessing

FunctionPower Function

Propulsion Function

Function Decomposition

Segment Network for Missile Model A-405

Rear Battery Pack


MissileModel A-400

<<segment>>


<<segment>> <<segment>>

<<segment>> <<segment>> <<segment>>

<<segment>> <<segment>>

Rocket Motor

<<segment>>

<<model>>

Note: Blue highlighted segments are included in both network hierarchies

September 2008 83



Physical Area Decomposition

Segment Network for Missile Model A-405 Serial Number

F9342312-33

Missile



Fixed Fins

Electronics Unit


Tail Unit


Guidance Fins

Fin Control Unit


Pack

MissileModel A-405

S/N: F9342312-33

<<asset>> <<segment>>



<<segment>> <<segment>> <<segment>><<segment>><<segment>>

Note: Dark green segments are “leaf” segments where serialized assets can be installed

September 2008 84





F9342312-33

Missile



Fixed Fins

Electronics Unit


Tail Unit


Guidance Fins

Fin Control Unit


Pack

MissileModel A-405

S/N: F9342312-33




<<segment>> <<segment>> <<segment>><<segment>><<segment>>Motor

P/N AB-C800S/N: 4324

September 2008 85





F9342312-33

Missile



Fixed Fins

Electronics Unit


Tail Unit


Guidance Fins

Fin Control Unit


Pack

MissileModel A-405

S/N: F9342312-33





P/N AB-C800S/N: 9432

September 2008 86





F9342312-33

Missile



Fixed Fins

Electronics Unit


Tail Unit


Guidance Fins

Fin Control Unit


Pack

MissileModel A-405

S/N: F9342312-33





P/N AB-C800S/N: 1254

September 2008 87






CRIS Representation of Object Registry

September 2008 88

AssetSegment

Site

Model

SegmentType

SiteDatabase

AssetType

Manu-facturer

RowStatus Type

SegmentChild

Asset OnSegment

DatabaseMIMOSAInterfaces

MIMOSAInterface

Types

MIMOSAData Categ.

Type

MIMOSASupport

Type

MIMOSAFunctionality

TypeEnterprise

SiteType

EnterpriseType

MIMOSAAccessType



1 to many(*) relationship

September 2008 89

AssetNumeric

Data

AssetCharacter

Data

SegmentNumeric

Data

SegmentCharacter

Data

SegmentBLOBData

AssetBLOBData

Model

ModelNumeric

Data

ModelCharacter

Data

ModelBLOBData

SegmentType

SiteDatabase

AssetType

Manu-facturer

BLOBContent

Type

BLOBDataType

AgentAgentType

RowStatus Type

PurchaseCondition

Type

AssetReadiness

Type

AssetChild

ModelChild

AssetOwnerHistory

1 to many(*) relationship ReferenceUnitType

EngineeringUnit

Enumerated

EngineeringUnitType

SegmentNumeric

Data Type

SegmentCharacterData Type

AssetNumeric

Data Type

AssetCharacterData Type

DatabaseMIMOSAInterfaces

MIMOSAInterface

Types

MIMOSAData Categ.

Type

MIMOSASupport

Type

MIMOSAFunctionality

Type

AssetSegment

Site

SegmentChild

Asset OnSegment

EnterpriseEnterprise

Type

SiteType

MIMOSAAccessType

September 2008 90






CRIS Meta-Data Reference Data Library

CRIS Reference Data Library

September 2008 91



►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

September 2008 92



►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

September 2008 93



September 2008 94



September 2008 95



September 2008 96



September 2008 97



► 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

September 2008 98

Open Reliability

Management

OSA-EAI Open Reliability ManagementOSA-EAI Open Reliability Management


September 2008 99

Failure Histories

Geo-Spatial Tracking

Component Tracking

Model Database

OEM Model

Reliability InfoRCM

Analysis Info

Root Cause

Analysis Info

Spare Part

Analysis Info

Open Physical

Asset Registry

Failure Histories


Component Tracking

Model Database

OEM Model

Reliability InfoRCM

Analysis Info

Root Cause

Analysis Info

Spare Part

Analysis Info

Open Physical

Asset Registry



September 2008 100

► 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



September 2008 101


►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

September 2008 102


September 2008 103


Model

1

+Is Topic Of

*

Database

1

+Maintains*

+mdHypEventGUID : long(idl)+userID : string(idl)+utcCreated : string(idl)+severityRank : string(idl)

ModelHypotheticalEvent

*

+Caused By *

Agent

0..1+Creates

*

ModelRecommendation

*

*

SegmentEvent

+Evidence

*

*

MeasurementEvent

+Evidence*

*

+mdHypEventNumDataGUID : long(idl)+userID : string(idl)

ModelHypotheticalEventNumData

1

*

+evNumDataTypeGUID : long(idl)+userID : string(idl)

EventNumericDataType

+Type of1

*

+With units of1

*

EngineeringUnitType

+ordering_seq : long(idl)+userID : string(idl)-description : string(idl)

ModelFunction

*

*

0..1

+Originator*

1

+Is Topic Of

*

+Maintains

*

1

+Evidence

*

*

*

*

EventType

+Type of1

*

September 2008 104


Segment

1

+Is Topic Of

*

Database

1

+Maintains*

+sgHypEventGUID : long(idl)+userID : string(idl)+utcCreated : string(idl)+severityRank : string(idl)

SegmentlHypotheticalEvent

*

+Caused By *

Agent

0..1+Creates

*

SegmentlRecommendation

*

*

SegmentEvent

+Evidence

*

*

MeasurementEvent

+Evidence*

*

+sgHypEventNumDataGUID : long(idl)+userID : string(idl)

SegmentlHypotheticalEventNumData

1

*

+evNumDataTypeGUID : long(idl)+userID : string(idl)

EventNumericDataType

+Type of1

*

+With units of1

*

EngineeringUnitType

+ordering_seq : long(idl)+userID : string(idl)-description : string(idl)

SegmentFunction

*

*

0..1

+Originator*

1

+Is Topic Of

*

+Maintains

*

1

+Evidence

*

*

*

*

EventType

+Type of1

*

September 2008 105


►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

September 2008 106

OSA-EAI Open Condition ManagementOSA-EAI Open Condition Management

Open Condition

Management


September 2008 107

Open Physical

Asset Registry

Open Physical

Asset Registry



September 2008 108

► 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 13374 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



September 2008 109


Open Physical

Asset Registry

Open Physical

Asset Registry


September 2008 110


Segment Asset

+utcEventStart

SegmentEvent

+utcEventStart

AssetEvent

Database

1*

1*

+eventTypeID : long(idl)+userID : string(idl)

EventType

1

-Maintains *

*

1

*

+Classified as1

*

*

September 2008 111

Site

+mlocGUID : long(idl)+userID : string(idl)

MeasurementLocation

1

+names*

+utcEvent+dataQualityType : short(idl)

MeasurementEvent

Segment Asset

{OR} {OR}0..1

*

0..1

*

0..1

*

0..1

*

Transducer

Database

+trTypeGUID : long(idl)+userID : string(idl)

TransducerType

*

+Type of1

1+Maintains *

DataSource

+dsTypeGUID : long(idl)+userID : string(idl)

DataSourceType

*

+Type of1

1+Maintains *

+mlocTypeGUID : long(idl)+userID : string(idl)

MeasurementLocationType

1

+Maintains *

*

-Type of1

+trAxisDirTypeGUID : long(idl)+userID : string(idl)

TransducerAxisDirectionType

1

+Maintains *

+calcTypeGUID : long(idl)+userID : string(idl)

CalculationType

1

+Maintains *

*

0..1

*

*

*

0..1

*

0..1

1 +Generates*

*

0..1

*

*

*

0..1

*

0..1

*

0..1

SegmentRecommendation

SegmentEvent

*

*

*

*


September 2008 112



MeasurementEvent

-value : double(idl)

NumericMeasurement

1

+Produces*


ReferenceUnitType


EngineeringUnitType

*

+With Units Of1

*

+References1

-value : string(idl)

CharacterMeasurement

*

+With Units Of1

1

+Produces*

1

+References

*

-integerValue : long(idl)+userID : string(idl)

EnumeratedDataItems

September 2008 113

OSA-EAI Open Condition ManagementOSA-EAI Open Condition ManagementMeasurementEvent

-orderingSeq : unsigned long(idl)-frequencyOrOrder : char(idl)-minInHzOrOrder : double(idl)-maxInHzOrOrder : double(idl)-amplitude : double(idl)-angleInDegrees : double(idl)

AmplitudeVectorData

1

+Produces*

EngineeringUnitType

*

+With Units Of1

1

+Produces*

1

+Produces*

1

+Produces*

Database

1

+Maintains *

WindowType AverageType AverageSynchType AverageWeightTypePostScalingType

1

+Maintains *

1

+Maintains *

1

+Maintains *

1

+Maintains *

1

+Maintains *

*

+With Units Of1

*

+With Units Of1

*

+With Units Of1

*

1

*

1

*

1

*

1

*

1

*

1

SourceDetectorType

1

+Maintains *

*

+With Units Of1

*

1

*

1

*

1

-orderingSeq : unsigned long(idl)-frequencyOrOrder : char(idl)-minInHzOrOrder : double(idl)-maxInHzOrOrder : double(idl)-assocRPMInHz : double(idl)-numberOfAverages : long(idl)-averageOverlapPercentage : long(idl)-resolutionLines : long(idl)-dcLevel : long(idl)-complexYN : char(idl)-spectrumBinaryData : object(idl)

FastFourierTransformData

-orderingSeq : unsigned long(idl)-numberOfBands : long(idl)-centerInHz1Band : double(idl)-widthPctOrOctave : char(idl)-bandWidth : double(idl)-assocRPMInHz : double(idl)-numberOfAverages : long(idl)-averageOverlapPercentage : long(idl)-spectrumBinaryData : object(idl)

ConstantPercentageBandData

-orderingSeq : unsigned long(idl)-secondsOrRevs : char(idl)-offsetSecondsOrRevs : double(idl)-maxSecondsOrRevs : double(idl)-numberOfSamples : long(idl)-assocRPMInHz : double(idl)-numberOfAverages : long(idl)-averageOverlapPercentage : long(idl)-complexYN : char(idl)-waveformBinaryData : object(idl)

TimeWaveformData

*

1

*

1

*

1

*

1

*

1

*

1

September 2008 114


MeasurementEvent

1

+Produces*

Database

1+Maintains

*+mevBlobTypeID : long(idl)+userID : string(idl)

MeasEventBlobType

+imageBLOBData : object(idl)+name : string(idl)

SegmentBlobData


BlobDataType

+Binary type of

1

*

1

+Registers

*

+Type of Data

1*

September 2008 115

OSA-EAI Open Condition ManagementOSA-EAI Open Condition ManagementMeasurementEvent

-sampleOrderSequence : long(idl)-userID : string(idl)

Sample

1

+Produces*

Agent

*

+By

1

*

+child*


SampleCharacterData

+smCharDataTypeID : long(idl)+userID : string(idl)

SampleCharacterDataType

+Classified as

1

*

ReferenceUnitTypeEngineeringUnitType

1

+References

*

+With units of

1

*

Database

1

+Maintains*

1

+Maintains *


SampleNumericData

1

+Is Topic Of*

+smNumDataTypeID : long(idl)+userID : string(idl)

SampleNumericDataType

+Classified as

1*

1

+Maintains*

+With units of

1

*

1

+Maintains *

1

+Is Topic Of*

+remarkText : string(idl)

SampleRemark

1

+Is Topic Of1

September 2008 116


Sample

+orderingSeqID : long(idl)+userID : string(idl)-testGMT : char(idl)

Test

+Performed on a0..1

+Produces*

1

+Produces*

MaterielItem (Material Sampled / Tested)

MlocTestCompNumericAlarmRegion

TestCompAlarmAssociatedMlocNumRegion

*

*

0..1+Analyzed In

*

TestType

*

-Type of

1

MeasurementEvent

1*

+mlocID : long(idl)+userID : string(idl)

MeasurementLocation

1+Generates*

+orderingSeqID : long(idl)+userID : string(idl)-numValue : double(idl)-chrValue : string(idl)-BlobValue : object(idl)

TestComponent

1+Produces*

BlobContentType +Binary type of

0..1

*

EngineeringUnitType+With units of

1 *

MeasLocationType

*

-Type of

1

1

*

0..1 +Analyzed In

*

Transducer

DataSource

*

0..1

-ordering_seq

TestComponentAlarm

AlarmType

+Type of 1 *

+orderingSeqID : long(idl)-userID : string(idl)

TestComponentGroup Database1

+Maintains

*

-orderingSeqID : long(idl)

TestComponentInGroup

*

*

*

0..1

1

+Maintains

*

*

-Type of1

1

+Maintains*

TestComponentType

*

-Type of

1

1

+Maintains

*

1

+Maintains

*

-testCompGroupTypeID : long(idl)-userID : string(idl)

TestComponentGroupType

Agent+Performing

1

*

1+Produces

*

-ordering_seq

TestCompNumericAlarmRegion

+With units of1

*+Type of1

*

1

+Produces

*

+Type of1

*

TestCompAlarmAssociatedNumRegion

*

*

September 2008 117

OSA-EAI Open Condition Management

OSA-EAI Open Condition Management

September 2008 118


September 2008 119


September 2008 120


September 2008 121


September 2008 122


September 2008 123


September 2008 124

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.


September 2008 125


September 2008 126


September 2008 127


September 2008 128


September 2008 129


September 2008 130


September 2008 131

OSA-EAI Open Maintenance ManagementOSA-EAI Open Maintenance Management



September 2008 132

Open Physical

Asset Registry

MRO Tools

MRO Labor

MRO Materials

Work Order Tracking

Pre-Planned Work Packages

Reactive Main-

tenancePreventive

Main-tenance

Condition-Based Maint-enance

Calibration & Config.

Mgmt

Open Physical

Asset Registry

MRO Tools

MRO Labor

MRO Materials

Work Order Tracking


Reactive Main-

tenancePreventive

Main-tenance



Mgmt

OSA-EAI Open Maintenance ManagementOSA-EAI Open Maintenance Management


September 2008 133

MIMOSA Open Maintenance ManagementMIMOSA Open Maintenance Management

SegmentAsset

SegmentRecommendation

AssetRecommendation

AssetRequestForWork

SegmentRequestForWork

Database

Agent

OrderedList

OrderedListRequestForWork

-solPackID : long(idl)-userID : string(idl)

SolutionPackage

-workReqID : long(idl)-userID : string(idl)

WorkRequest

-workStepID : long(idl)-userID : string(idl)

WorkStep

-workOrderID : long(idl)-userID : string(idl)

WorkOrder

WorkRequestAudit

WorkStepAudit

WorkOrderAudit

1

*

*

-Is Assigned

0..1

*

+Is Assigned0..1

*

+Is Assigned

0..1

1

+Has Status History*

1

+Has Status History*

1

+H

as

Sta

tus

His

tory

*

*

*

*

*

WorkAuditType

1

+Maintains *

*1

*

1

*1

+By, To, & From 0..3

*

0..3

+By, To, & From

*

0..3

+By, To, & From

*

PriorityLevelType

*

1

*

1

*+Is Assigned0..1

*

+Is Assigned

0..1

*

+Is Assigned0..1

*

+Is Assigned0..1

1

+Maintains

*

1

+Maintains *

*

+Has Child*

+sequence : long(idl)+userID : string(idl)

SolutionPackageStep

0..1*

*+Originally From

1

11

*

+Derives From 0..1

*

+References 0..1

*

+References

0..1

*

+Followup From

0..1

1

*

Request

1

*

1

*

+By & From

0..2

* 0..1

*

+To 0..1

*

+To 0..1

*

+To 0..1

*

1

+M

ain

tain

s *

*

**

*

September 2008 134

MIMOSA Open Maintenance ManagementMIMOSA Open Maintenance Management

SegmentAsset

-gmtStarted-gmtCompleted-userID

SegmentCompletedWork


AssetCompletedWork

Database

OrderedList


OrderedListCompletedWork

1

*

1

*

WorkStep

*

0..1

*

0..1

*

0..1

1

*

WorkTaskType

1

+Maintains *

*

1

*

1

*

1

AssetUtilization

AssetUtilizationFromAsCompWork

* +utilized on

*

AssetUtilization

AssetUtilizationFromSgCompWork

* +utilized on

*

AssetUtilizationFromOLCompWork

* +utilized on

*

September 2008 135

OSA-EAI Open Capability Forecast ManagementOSA-EAI Open Capability Forecast Management


September 2008 136

►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 ManagementOSA-EAI Open Capability Forecast Management

September 2008 137


Open Reliability

Management

Open Condition

Management

OpenObject

RegistryManagement



September 2008 138

MIMOSA Open Systems Architecture for Enterprise Application Integration

(OSA-EAI)


Failure Histories


Component Tracking

Model Database

OEM Model

Reliability InfoRCM

Analysis Info

Root Cause

Analysis Info

Spare Part

Analysis Info

MRO Tools

MRO Labor

MRO Materials

Work Order Tracking


Reactive Main-

tenancePreventive

Main-tenance



Mgmt

Open Object

Registry Mgmt.

September 2008 139

MIMOSA Open Systems Architecture for Enterprise Application Integration (OSA-EAI) Architecture

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-DocProducer& Consumer

XML Stream or File

Tech-CDE AggregateCRIS XML Transaction Client & Server Schema

Tech-XML Atomic CRIS XML Transaction Client & Server Schema

Tech-XML-ServicesFor SOAP Tech-XML

Clients & Servers

Tech-XML-Web For HTTP Tech-XML Clients & Servers

Tech-Doc CRISXML 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-]Technology Types [Tech-]

Tech-CDE Client & Server

XML Stream or XML File

Tech-XMLClient & Server

XML Stream or XML File

Compliant SOA Application Definitions

Tech-CDE-ServicesFor SOAP Tech-CDE

Clients & Servers

September 2008 140

MIMOSA OSA-EAI V3.3 ReleaseMIMOSA OSA-EAI V3.3 Release

OSA-EAI Common Conceptual Object Model (CCOM) Conceptual Model

Common Relational Information Schema (CRIS)Implementation Model

CRIS Reference Data LibraryMetaData Taxonomy

OSA-EAI Terminology Dictionary Semantic Definitions

XML Content Definition

Compliant Application Service Definitions

Tech-Doc Producer& Consumer

XML Stream or File

Tech-CDE AggregateCRIS XML Transaction Client & Server Schema

Tech-XML Atomic CRIS XML Transaction Client & Server Schema

Tech-Doc CRISXML Document

Schema

Tech-CDE Client & Server XML Stream or XML File

Tech-XMLClient & Server XMLStream 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-ServicesSOAP Client & Server

Tech-XML-ServicesSOAP Client & Server

For Message Buses For Point-to-Point Web Services

September 2008 141

MIMOSA Specification Development Process Flowchart

MIMOSA Specification Development Process Flowchart

Step 1 – MIMOSA Member Organization Submits a New Work Proposal (NWP) to MIMOSA President for a New Standard

or Major Revision to a MIMOSA Specification

Step 3 – MIMOSA Technical Committee (TC) Reviews the NWP and Submits a NWP Technical Committee Analysis Report (TCAR) to MIMOSA Member

Organizations to Seek Commitments for Subject Matter Experts (SMEs)

Step 2 – MIMOSA President and MIMOSA CTO Review NWP for Technical and Business Fit For Organization and

Approve/Disapprove. If disapproved, MIMOSA Member Organization can

appeal to MIMOSA Board of Directors.

Step 4 – MIMOSA President and CTO Review the Technical Expert Volunteers

available for a Subcommittee and Approve/ Disapprove/Delay NWP. If

disapproved, submitting organization can appeal to the Board of Directors.

Step 5 – MIMOSA CTO Forms a Technical Subcommittee from MIMOSA Member

Organizations and Other Industry Expert Volunteers.

Step 6 – MIMOSA CTO Recommends a Subcommittee Chairperson to the

MIMOSA Board to Lead the Effort. Board votes to approve or reject the

recommendation.

Step 7 – Subcommittee develops a Draft Specification and Submits it to TC for TC-

defined Review Period. All MIMOSA members have access to the

specification during this review period.

Step 8 – TC members submit written comments using Specification Comment

Form (SCF) to Subcommittee

Step 9 – Subcommittee reviews and responds to comments, incorporating

changes as appropriate. The subcommittee chair has the ultimate

authority to approve or reject comments after taking into account all

subcommittee member comments.

Step 10 – Subcommittee submits production specification and

demonstration of trial implementations to TC for final review and approval

Step 11 – TC sets a time period for the production specification to be vetted and tested. After this period expires, then the

TC votes in a regularly scheduled meeting to approve the specification and

send to Board for final ratification

Step 12 – Board votes to ratify the specification

Step 13 – Specification and all associated compliance tools are posted on public Download area of MIMOSA Web Site

Step 14 (On-going) – TC Accepts Specification Comment Forms (SCF) on

published specification for revisions

A

A B

B C

C D

D

September 2008 142

MIMOSA Specification Release History

MIMOSA Specification Release History

Beta Version, Members-only Release

Final Version, Production Release

May-00 May-01 May-02 May-03 May-04 May-06 Dec-06 Jun-08OSA-EAI Terminology Dictionary V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Common Conceptual Object Model V0.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Common Relational Info. Schema V1.1 V2.0 V2.1 V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI CRIS Reference Data Library V1.1 V2.0 V2.1 V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Tech-Doc XML Schema V1.1 V2.0 V2.1 V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Tech-Doc Producer/Consumer Spec. V1.1 V2.0 V2.1 V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Tech-XML Client/Server Schema V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Tech-XML Client/Server App. Spec. V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Tech-XML-Web Application Spec. V2.2 V3.0a V3.0h V3.1 V3.2

OSA-EAI Tech-XML-Services Application Spec. V3.0h V3.1 V3.2

OSA-EAI Tech-CDE Client/Server Schema V3.1 V3.2

OSA-EAI Tech-CDE Client/Server App. Spec. V3.1 V3.2

OSA-EAI Tech-CDE-Services Client/Server V3.2

OSA-CBM Specifications V3.1 V3.2

September 2008 143

OSA-EAI Distribution 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

September 2008 144

Services Oriented Architecture

Major Classes of Data and Related ArchitectureInitial Focus Areas

Major Classes of Data and Related ArchitectureInitial Focus Areas

As-DesignedReference Data

As-FieldedInstance Data

As-Monitored & As-Maintained

Event DataOntology

September 2008 145









time]

Serialized Asset


Configuration

Management Data


Teach Them To Speak the OpenO&M Languages! Teach Them To Speak the OpenO&M Languages!

ISO 15926ISO 15926

F O U N D A T I O N

September 2008 146

End User/EPC Engineering DataSupported 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 147



• 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 148



• 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 149

OEM Model Reference DataSupported by ISO 15926

OEM Model Reference DataSupported 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 150

End User Asset Instance DataSupported by MIMOSA OSA-EAIEnd 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 15926 model data)

• As-Built Equipment Instance Bill of Material (BOM) Breakdown Structure

• As-Built Asset Model Diagrams• BOM Diagram (inherited from ISO 15926 model)• CAD Drawing (inherited from ISO 15926 model)

September 2008 151

End User Asset Instance DataSupported by MIMOSA OSA-EAIEnd 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 152

End User Field Engineering DataSupported by OSA-EAI

End User Field Engineering DataSupported 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 153

End User Asset Event DataSupported by MIMOSA OSA-EAI &

OPC-UA/MIMOSA

End User Asset Event DataSupported 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 154

End User CBM DataSupported by MIMOSA OSA-EAI &

OPC-UA/MIMOSA

End User CBM DataSupported 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 155

End User Production Reporting DataSupported by ProdML

End User Production Reporting DataSupported by ProdML

• Production Level Reporting

• Production Scheduling

September 2008 156June 17, 2008 156

Mike Brooks – Chevron VisionMike Brooks – Chevron Vision

• name services

• metadata

• model maps

• abstraction

• not proprietary

• interoperability

September 2008 157

12

OpenO&M

Mike Brooks – Chevron VisionMike Brooks – Chevron Vision

September 2008 158

Integration Platform

Suncor View -- A Coordinated Approach to Suncor View -- A Coordinated Approach to Full Integration within the EnterpriseFull 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 Mes

sage

Tra

nspo

rt

Data

Data

Data

Data

Data

Data

Data

DataFinancialHRProductionDocumentsProceduresPlanningEHSMaintenanceSupply

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”

Bas

icA

dmin

Adv

ance

d

Environmental Monitoring System Data

September 2008 159

Systems Requiring Interoperability

Systems Requiring Interoperability

September 2008 160

System Systems Requiring Interoperability With Abbreviations

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 161

Oil & Gas/PetroChem Industry OpenO&M Interoperability

Scenarios (Complete View)

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 15926 & MIMOSA

B2MML

B2MML & PRODML

MIMOSA & B2MML

MIMOSA

OPC

Fieldbus (Foundation, Profibus, etc.)

September 2008 162

Enterprise Risk Management System, Enterprise Resource Planning System &

Enterprise KPI/Event Portals

Oil & Gas/PetroChem Industry OpenO&M Interoperability Scenarios

Oil & Gas/PetroChem Industry OpenO&M Interoperability Scenarios

Production Forecasting & Scheduling Systems

Operational Performance Modeling & Optimization Systems

EnterpriseAsset

ManagementSystems

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)

OperationalRisk 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)

RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX)

RFQs & POs (OAGIS, CIDX)RFQs & POs (OAGIS, CIDX)

Su

pp

lier

sC

ustom

ers

Detailed Prod. Performance (B2MML)

Detailed Prod.

Schedules (B2MML)

Pla

nt/

Pro

cess

Engin

eeri

ng A

s-D

esi

gned &

As-

Built

N

etw

ork

/Segm

ent/

Tag Info

rmati

on,

Config.

Mgm

t. H

isto

rians

Pla

nt/P

roce

ss “As-In

stalle

d” &

“As-M

ain

tain

ed”

Netw

ork

/Segm

ent/A

sset/T

ag R

egistry

&

Configura

tion M

anagem

ent H

istoria

ns

OEM

Pro

duct

D

ata

Mgm

t.

Syst

em

s

“As-Designed” & “As-Built” Product/Part Data (ISO 15926 & MIMOSA)

Asset Removals & Installations

(MIMOSA)

EOM

ORM EAM

HIST

DCS HMI

CMSDEV

REG

OPM

MES

EIS

PDMOPM 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 15926 & MIMOSA)

Usage Readings (MIMOSA)

CBM/Calib.

Schedule (MIMOSA)

CBM/Calib. Work Completed (MIMOSA)

Maint. KPIs (MIMOSA)

ERM PORTERP

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)

September 2008 163

Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-

Priority Scenarios As Determined By Top-Priority Use Cases

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 15926 & MIMOSA

B2MML

B2MML & PRODML

MIMOSA & B2MML

MIMOSA

OPC

Fieldbus (Foundation, Profibus, etc.)

September 2008 164

Enterprise Risk Management System, Enterprise Resource Planning System &

Enterprise KPI/Event Portals

Production Forecasting & Scheduling Systems

Operational Performance Modeling & Optimization Systems

EnterpriseAsset

ManagementSystems

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)

OperationalRisk 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)

RFQ Cost/Delivery Schedule & PO Delivery Status (OAGIS, CIDX)

RFQs & POs (OAGIS, CIDX)RFQs & POs (OAGIS, CIDX)

Detailed Prod. Performance (B2MML)

Detailed Prod.

Schedules (B2MML)

Pla

nt/

Pro

cess

Engin

eeri

ng A

s-D

esi

gned &

As-

Built

Segm

ent/

Tag

Info

rmati

on,

Configura

tion

Managem

ent

His

tori

ans

Pla

nt/P

roce

ss “As-In

stalle

d” &

“As-M

ain

tain

ed”

Segm

ent/A

sset/T

ag R

egistry

&

Configura

tion M

anagem

ent H

istoria

ns

OEM

Pro

duct

D

ata

Mgm

t.

Syst

em

s

“As-Designed” & “As-Built” Product/Part Data (ISO 15926 & MIMOSA)

Asset Removals & Installations

(MIMOSA)

EOM

ERM PORTERP

ORM EAM

HIST

DCS HMI

CMSDEV

REG

OPM

MES

EIS

PDMOPM 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 15926 & 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)

1

2

3

4 5

6

7

8

9

10

21

2019

11

12

13 14

15 16

17 18

Maint. KPIs (MIMOSA)

22

Current Op. Data & Events (OPC UA

DA/A&E)

Su

pp

lier

sC

ustom

ers

Plant/Process Engineering Change Advisories24

Product/Part Engineering Change Advisories

23

25 26

27

28

Oil & Gas/PetroChem Industry OpenO&M Interoperability Top-Priority Scenarios


September 2008 165

1

2

3

4

5

6

7

8

9

10

21

20

19

11

12

13

14

15

17

18

16

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



September 2008 166

25

26

27

28

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

(OPC UA) Pull Historical Operating Data and Events Out of HIST to ORM, OPM

22

23

24



September 2008 167

Scenarios Activated by Use CasesScenarios Activated by Use Cases

1 2 3 4 5 6 7 8 9

1 •2 •3 •4 •5 •6 •7 •8 • •9 •

10 •11 •12 •13 •14 •15 •16 •17 •18 •19 • •20 • •21 •22 •23 •24 •25 • • • •26 • • • •27 • • • •28 • • • •

Use Cases

Sce

nar

ios

September 2008 168

Frequently Asked QuestionsFrequently 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 169


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 170


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 171

BibliographyBibliography

► 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 2006. http://www-03.ibm.com/industries/government/doc/content/bin/soa_information_services.pdf

► Hatami, Mehdi. DM Direct, SOA: Providing Enterprise-Wide Information Access, April 2007. http://www.dmreview.com/dmdirect/20070413/1080889-1.html

► Zachman, John A. “A Framework for Information Systems Architecture,” IBM Systems Journal 26, no. 3, 1987.

Date post:	15-Jan-2016
Category:	Documents
Upload:	trevin-dent
View:	214 times
Download:	0 times