OpenO&M and POSC Caesar wit IBM

OpenO&M and POSC Caesar wit IBM

Using Asset Management Standards and the Open Industrial Interoperability Ecosystem (OIIE) to enable Critical Infrastructure Management on a Cross Sector Basis Alan T. Johnston, MIMOSA Markus Stumptner, UniSA and Co-CTO MIMOSA @ Asset Institute Standardization Workshop November 8, 2018 Asset Institute 2018 Asset Management Standardization for Critical Infrastructure Management: Workshop Outline Part A Introduction: What is MIMOSA and Workshop Leaders Understanding Critical Infrastructure: What is Critical Infrastructure?-Alan Critical Infrastructure Scope From US PPD 21- 2013 Interdependent and Heterogenous Nature of Critical Infrastructure Need for Public and Private Sector coordination with shared responsibilities for Risk Management Cooperation with US NIST and US DOE Public Sector includes Federal, State and Local Governments (National and Multi-Lateral) Private Sector includes all private owner/operators in sectors of critical infrastructure and their key suppliers Key Interrelated Problems Proposed Solution Model, Monitor and Manage the Processes, Systems and Components Supplier-Neutral industrial Digital Ecosystem Open Industrial Interoperability Ecosystem (OIIE) OIIE Oil and Gas Interoperability (OGI) Pilot Greenfield versus Brownfield (and the need for infrastructure and information remediation)

Asset Institute 2018 Asset Management Standardization for Critical Infrastructure Management: Workshop Outline Part B Group Background and Ecosystem Projects New Open Industrial Interoperability Ecosystem (OIIE) Use Cases-Markus Standard OIIE Use Case Architecture RFI/RFI Response for both Greenfield and Brownfield Asset Model Information Industry Standard Datasheet Definition (ISDDs)- Major Developments- Markus ISDD Build Process ISDD Mapping ISDD Use and Re-Use Major Breakthrough in Instrumentation ISDDs Top 100 Now Achievable by Q2 2019 Working with Land O Lakes, NIST and Open Applications Group (OAGi) Markus Industrial Internet of Things (IIOT) and other Sensor Data New CBM Use Case Contextualization based on MIMOSA CCOM and the OIIE CCOM and Breakdown Structure Asset Institute 2018 Asset Management Standardization for Critical Infrastructure

Management: Workshop Outline Part C Initiation of the next phase of the OIIE/Oil and Gas Interoperability (OGI) Pilot Alan Shared Piloting environment for OOs, EPCs and OEMs working with many software suppliers Next phase Includes 7 key OIIE Use Cases spanning CAPEX and OPEX (RFI through CBM) Engineering models developed by EPCs, as in a real project Validates all parts of OIIE, providing R&D Testbed for Digitalization and Interoperability Collaboration with other Industry Associations, ISO and IEC - Alan Q&A Asset Institute 2018 MIMOSA Organizational Summary MIMOSA is a 501 (c) 6 mutual benefit association formed in 1997 to develop supplier-neutral standards enabling complex industrial assets, systems and associated processes to be modeled, monitored and managed, wherever they may be operated. Early funding: Office of Naval Research for Dual Use Technology (Industry and Military/Aerospace) Focus on Asset Intensive industries (often process industries and their suppliers) Members include Owner/Operators, OEMs and major industrial Software Suppliers MIMOSA identifies and/or develops fit for purpose IM and IT standards to enable good practices (defined by other groups) to be deployed in a supplier-neutral manner. MIMOSAs recent focus: Industry Digital Business Transformation Based on the Digital Ecosystem paradigm Open Industrial Interoperability Ecosystem (OIIE): A supplier neutral ecosystem specification Adaptable, Repeatable, Scalable & Sustainable: decreasing costs & risks across the asset life-cycle Oil and Gas Interoperability Pilot (OGI Pilot): OIIE instance with Oil and Gas asset classes Enabling cross-sector Critical Infrastructure Management MIMOSA 2018

What is Critical Infrastructure Critical infrastructure (or critical national infrastructure (CNI) in the UK) is a term used by governments to describe assets that are essential for the functioning of a society and economy the infrastructure. Wikipedia Government led efforts have addressed key aspects of Security (physical and cyber) and Resilience (usually focused on disaster and emergency preparedness). A key aspect of Critical Infrastructure is that it is Highly Interdependent. MIMOSA 2018 Critical Infrastructure Sectors From US PPD 21-2013 Chemical Commercial facilities Communications Critical manufacturing Dams Defense industrial base Emergency services Energy Financial services (including insurance) Food and agriculture Government facilities Healthcare and public health Information technology Nuclear reactors, materials, and waste Transportation systems Water and wastewater systems

Critical Infrastructure Management Critical Infrastructure Management Process Business Process Models Systems Models Industrial Process Models MIMOSA 2018 IIOT Sensors Components Models Trusted Systems $ Risk Models Critical Infrastructure Management Process Public/Private Cross-Sector Energy, Wastewa ter Multiple Sectors Manage ment, Transport , IT Enterpris Enterprises e1 (Energy)

Plant/Platform/Facility Plant 1 Plant 2 Enterpris e2 (Agricult ure, Chemical s) Facility 1 Facility 2 Enterprise/Area/Unit Risk Models Risk Models Risk Models Risk Models Business Process Models Business Process Models Business Process Models Business Process Models

Components Models Components Models Components Models Components Models Systems Models Systems Models Systems Models Systems Models Industrial Process Models Industrial Process Models Industrial Process Models Industrial Process Models MIMOSA 2018 Critical Infrastructure Interdependencies-1 IEEE Journal- Dec 2001 Identifying, Understanding, and Analyzing Critical Infrastructure Interdependencies Steven M. Rinaldi James P. Peerenboom

Terrence K. Kelly MIMOSA 2018 Critical Infrastructure Interdependencies-1a IEEE Journal- Dec 2001 Identifying, Understanding, and Analyzing Critical Infrastructure Interdependencies Steven M. Rinaldi James P. Peerenboom Terrence K. Kelly MIMOSA 2018 Critical Infrastructure Interdependencies-2 NIST Special Publication 1190 Community Resilience Planning Guide For Buildings and Infrastructure Systems Volume II October 2015 MIMOSA 2018 Critical Infrastructure Interdependencies-3 State Energy Resilience Framework Global Security Sciences Division December 2016 J. Philips, M. Finster, J. Pillon, F. Petit and J. Trail MIMOSA 2018

Critical Infrastructure Interdependencies-4 Incorporating Prioritization in Critical Infrastructure Security and Resilience Programs Homeland Security Affairs 13, Article 7 (https://www.hsaj.org/articles/14091) October 2017 Duane Verner, Frederic Petit, and Kibaek Kim MIMOSA 2018 Critical Infrastructure Interdependencies-5 NSW Critical Infrastructure Resilience Strategy Partner, Prepare, Provide NSW Department of Justice | Office of Emergency Management 2018 MIMOSA 2018 The Critical 5 The Critical Five was established in 2012 to enhance information sharing and work on issues of mutual interest between Australia, Canada, New Zealand, the United Kingdom and the United States. One of the first efforts was to understand how each country addresses critical infrastructure as a basis for clearly articulating and communicating a common message on the value, meaning, and importance of critical infrastructure. Forging a Common Understanding of Critical Infrastructure published March 2014.

The Role of Critical Infrastructure in National Prosperity published October 2015 MIMOSA 2018 Australia, Japan and United States Trilateral Partnership Announced July 31, 2018 Australia: Minister for Foreign Affairs-The Hon Julie Bishop MP Japan: Japanese Bank for International Cooperation United States: United States Overseas Private Investment Corporation (OPIC) Indo-Pacific region Cooperation on Investment to: 1. 2. 3. 4. Build infrastructure Address development challenges Increase connectivity Promote economic growth MIMOSA 2018 MIMOSA 2018 Interrelated Problems Critical Infrastructure Management is inherently Cross-Sector and has mostly been focused on Security (physical and cyber) and Disaster Mitigation, while discussing Resilience Due to the interdependent nature of Critical Infrastructure, the consequences of failure of the key sector activities may be broad reaching and catastrophic (no matter the cause of the failure). Major capital projects are routinely experiencing 25-50 percent cost

overruns Current Process for life-cycle management of Asset Information is highly fragmented and inefficient Methods for modeling, monitoring and managing Processes, Systems and Components (Assets) are fragmented, even within a single industry sector MIMOSA 2018 The Proposed Solution We propose a standardized approach to Model, Monitor and Manage the associated Processes, Systems, Components and Risks Use Supplier-neutral Standards for Digitalization and Interoperability Cooperation with Public and Private Sectors and Academia Cooperation with NIST and DOE, results flow to ISO When done as an integrated part of industrial life-cycle asset management Helps lower costs and risks in both CAPEX and OPEX Provides a basis for Cross-Sector Critical Infrastructure Management Provides the basis for a Supplier-Neutral industrial digital ecosystem specification Open Industrial Interoperability Ecosystem (OIIE)-MIMOSA Branded, Supplier-Neutral Oil and Gas Interoperability (OGI) Pilot Interoperability R&D Proving Grounds Gate Keeper for ISO 18101 (ISO OGI TS) MIMOSA 2018 ERP P to B Stack: Automation system s: apa s e C c ro ons

p ss rati e Primary business process: si n O p e u b in y ar inta d on Ma c Se and ish l b a t Es Level R4 y li it b Level R3 Operations Level R2 Level R1 Level R0 MIMOSA 2018

Full Asset Life-cycle Management Completion, Commission and Startup Continuous Improvement Feedback Loops Product Design Product MFG Device/Equip Manufacturing Process Engineer Simulate Engineer Procure Construct Design Platform Integrator Capital Project Operate & Maintain (O&M) Owner/Operators Product Model/Product=Component/Systems(Packages)/System of Systems/Plant/Facility/Platform Life-Cycles Derived from ISO TC 184 Manufacturing Asset Management Integration Task Force Final Report MIMOSA 2018

End of Life Standard OIIE/OGI Use Cases Cross Project Activities Capital Projects Complete/ Commission/ Startup Operate/ Maintain Decommission/ Dispose Sustained Life-cycle Digital Asset Management Opportunistic Handover of Structured Digital Assets OIIE Use Case 1: Information handovers to O&M OIIE Use Case 2: Recurring Engineering Updates to O & M OIIE Use Case 3: Field Changes to Plant/Facility engineering OIIE Use Case 4: Enterprise Product Data Library management (tied to ISDDs) OIIE Use Case 5: Asset Installation/Removal Updates OIIE Use Case 6: Preventive Maintenance Triggering OIIE Use Case 7: Condition Based Maintenance Triggering OIIE Use Case 8: Early Warning Notifications Yellow Use Cases in Phase 3 Sub-Phase 1 OIIE Use Case 9: Incident Management/Accountability

OIIE Use Case 10: Automated Provisioning of O & M systems OIIE Use Case 11: Enterprise RDL Management OIIE Use Case 12: RFI and RFI Response (Models Meeting Requirements and Model Information, Green and Brown Field) OIIE Use Case 13: Lockout/Tagout MIMOSA 2018 Digital Ecosystem-Why? Wikipedia: The concept of Digital Business Ecosystem was put forward in 2002 by a group of European researchers and practitioners, including Francesco Nachira, Paolo Dini and Andrea Nicolai, who applied the general notion of digital ecosystems to model the process of adoption and development of ICT-based products and services in competitive, highly fragmented markets like the European one. More recently, the term has been shortened to Digital Ecosystem MIMOSA 2018 Ecosystems and Interoperability Supplier-specific Interoperability Lego Enterprise Resource Planning (ERP) Apple Ecosystem Open Source Linux Android Standards-based Interoperability Intermodal Transport Internet Industrial Internet of Things (IIOT) Open Industrial Interoperability Ecosystem (OIIE) Embraces COTS & Open Source MIMOSA 2018

Supplier Neutral Industrial Digital Ecosystem Digital Ecosystem Concept Specialized For Process Industries Major suppliers of IT Infrastructure and Industrial Applications and Systems all want their ecosystem to be THE Ecosystem. MIMOSA 2018 Engineering , Procurement and Construction IT Networks M od e Inf l an or d I m ns ati ta on nce Enterprise Business Systems EPC Firms s es nts si n e Bu irem qu cs Re Do s, s

ag ent ,T ID rem P& ui D, eq PF & R OEMs Manufacturers Fu nc ti T Re ec ona qu hn l a ire ica nd m l en ts OIIE Inter-Enterprise Systems Connectivity and Services Architecture Enabling Industry 4.0 Owner/Operators Enterprise Business Systems IT Networks Manufactured Asset Data Automation (Make/Model Information, Serial #) and Control

IT Networks Operations & Maintenance Data (Monitoring, Diagnostics Prognostics) Automation and Control OIIE Intra-Enterprise Systems Connectivity and Services Architecture Enterprise Business Systems OIIE Administration Planning Engineering Design Construction Management Operations Operations Risk Management Management Maintenance Management IEC 62264 Messaging Service Model /OpenO&M Information Service Bus Model Standard, Cloud Friendly Enterprise Solutions Architecture For Digital Business Ecosystems Trusted

Systems Automation and Control HSE and Operation Monitoring Prognostic & Health Management Inter-Enterprise Connections Automation Control Bus Connectivity Legend IIoT Connections (Constrained) IIOT Device Device Device Trusted IT/OT connections ISBM Web Services (Constrained) Shared Information and Semantic Context

Enterprise Reference Data Libraries IIoT Device Metadata MIMOSA 2018 Sensor/ Transducer Industry Reference Data Libraries IIoT Device Metadata (ISO 15926, OTD, CDD) Contextualization for Open Industrial Interoperability Ecosystem using MIMOSA CCOM 4.x, ISA, OAGi, ISO and IEC Standards Process Engineering-(CCOM Segment Networks)- PFDs Work Processes followed for CAPEX and OPEX (Intra and Inter-Enterprise) Production Process to be supported by Plant/Platform/Facility Functional/Systems Engineering-(CCOM Segment Networks)- P&IDs , other schema System of Systems Systems (Functional Packages) Functional Locations (P&ID Tag) Components Sensors Models - (CCOM Model) Used for MFG Model and Package Model Serialized Equipment & Devices-(CCOM Assets installed in CCOM Functional Locations) Multiple Breakdown Structures as Needed- Taxonomic views of same CCOM objects Enterprise Breakdown Enterprise/Area/Unit (ISA 95/88) Maintenance Breakdown Structure - (eg ISO 14224) ISDDs - Property Sets for ALL Functional Locations, Equipment and Devices IIOT- Data captured by Sensors is Contextualized by ALL of Above MIMOSA 2018 OIIE OGI Pilot Next Phase (s)

Objective- Drive Industry Digital Business Transformation Reach agreed industry digitalization inflection point by 2020 Aligned with CII/Fiatech, IOGP and NIST Priorities 3 Sub-phases 5 months each 1st sub-phase Validate ISDD Process, Add 50+ISDDs, Core OIIE Use Cases covering asset life-cycle Sub-phases 2 and 3 add AWP, 2 JIP 33 Packages, More OIIE Use Cases, ISDDs and suppliers, add target unit(s) Sub-Phase 1 - Priority Use Cases covering key parts of life-cycle, using ISDDs for properties RFI/RFI Response (Greenfield) Main source of information for Model Selection Install Assets on Functional Locations (Greenfield Capital Project) CBM Information Capture and Triggering (2 Device Classes with ISDDs, Instrument and Drive/Motor) Remove and Replace Use Case RFI/RFI Response (Brownfield) Core for Information Remediation Use Existing Debutanizer Tower Engineering Dataset (Originally provided by Worley Parsons) and Add To It Focus on Condenser Unit which includes the instrument and equipment classes with existing ISDDs MIMOSA 2018 Debutanizer Tower P&IDs Worley Parsons MIMOSA 2018 OIIE OGI Pilot Sub-Phase 1 Activities 1-4 (October 2018 February 2019) Procure E P C MIMOSA 2018 O E

M OIIE OGI Pilot Sub-Phase 1 Activities 5-8 (October 2018 February 2019) MIMOSA 2018 Section End MIMOSA 2018 Digital Ecosystems and the OIIE Markus Stumptner Advanced Computing Research Centre AI and Software Engineering Group AI and Software Engineering Group About 20 members AI + Software Engineering + Data Management Major topics Reasoning about system behaviour Information and knowledge management in distributed ecosystems Projects in the Ecosystem Space OT/IT Interoperability Digital Information Energy Australia Gateway OGI Pilot Genetic Data Curation SOA for Future Combat Systems Automated Modelling for Combat Simulation Ecosystems Integrated Law Enforcement Federated Data Platform Activities in the OIIE Space

New Use Case for RFI/RFI Response in Greenfield and Brownfield Industry Standard Datasheet Definitions (ISDDs) Project ISDD Build ISDD Management and Mapping ISDD Use and Reuse Teaming with Land O'Lakes, OAGi and NIST CBM Use Case (Use of JSON and ISO 13374) Use Case 12: Request for Information and Response in Greenfield and Brownfield (RFI/RFI Response) MIMOSA 2018 Use Case 12 RFI/RFI Response in Greenfield EPC Functional Requirements (RFI) OEM Models Meeting Requirements (RFI Response) RFI/RFI Response in Brownfield Information Remediation Serial No, Requirements, Known Properties (RFI) O/O OEM Matching Model(s) (RFI Response) MIMOSA 2018 User Stories for Use Case 12 in Greenfield

MIMOSA 2018 Story M100: Start Unit Functional Requirements 1.We need to build a light ends unit to remove butane from our incoming crude supply Client Business Person Functional Requirements Debutanizer PFD and P&ID Client Engineer 2.a How Much Capacity Do We Need? b. What will the incoming crude spec be? A MIMOSA 2018 Story M101: Model Selection 1. We need to buy equipment and instruments meeting or exceeding functional requirements taken from PFD and P&IDs for the new Debutanizer Tower.

2. Send me the Requirements from those documents and I will check with our preferred suppliers. Requirements (RFI) 3.P2M Dialog Client Engineering Person A Requirements Debutanizer PFD and P&ID Client Purchasing B MIMOSA 2018 Models Meeting Requirements (RFI Response) Instrument or Equipment Supplier Portals

User Story for Use Case 12 in Brownfield Information Remediation MIMOSA 2018 Story M102: Make/Model Match-up 1. We have a large number of 2. I will send RFIs requesting instruments in our Debutanizer Tower, but we do not know the Models or many of the Properties. Manufacturer to send us their corresponding Models and the properties for those models 3. RFIs Maintenance and Reliability Manager Asset Information Manager MIMOSA 2018 4. RFI Responses Equipment and

Instrument OEM Industry Standard Datasheet Definition (ISDD) MIMOSA 2018 Industry Standard Datasheet Definition (ISDD) Capture existing Industry Standard Datasheets (ISDs) as machine interpretable business objects that are then fully re-usable, mappable and extensible. Provide standard XML exchange schema for exchanging datasheet oriented information Mappable to existing OEM and O/O Datasheets Capture high-value properties from existing, high-value ISDs published by credible industry associations including API, ASME, IEC, ISA, ISO, NORSOK and PIP. Support Assets full life-cycle information management Data sheets are not used just for procurement Improves ability to procure, install, commission, operate and maintain assets with reduced effort, cost and schedule MIMOSA 2018 Data Sheets Functional Segments can be associated with data sheets to specify functional requirements Models can be associated with data sheets to specify characteristics of equipment of that model Equipment Assets can be associated with data sheets to specify characteristics of that equipment Segment and Asset Types can have data sheet templates (AttributeSetDefinitions) to support class libraries Data Sheet Engineering-Specific Requirements

Data Sheet Asset-Specific Properties Data Sheet Make/Model-Specific Properties has has has Functional Segment 11PMP01 Equipment Asset 810001 instance of MIMOSA 2018 Model ZDNMM3581 Industry Standard Data Sheets (ISDs) Currently have identified 263 source ISDs in common use Most commonly identified ISD publishers are listed below API 15 (+20 ISO equivalents) ASME 2 (+1 ISO equivalent) IEC 10 ISA 166

ISO 28 NORSOK 31 PIP 11 MIMOSA 2018 Condenser Unit of Debutanizer Tower P&ID Equipment class ISD API 660 Shell and Tube Heat Exchanger Data-sheet Instrument class ISD ISA 20T2221 RTD/Thermocouple Temperature Transmitter or Switch Revision 1 Data-sheet MIMOSA 2018 Industry Standard Datasheet Example (ISA Rev 0) Temperature Transmitter ISA 20T2221 Device Specifications ISA 20T1001 Operating Parameters Datasheet Datasheet Picklist MIMOSA 2018 Picklist Industry Standard Datasheet Example (ISA Rev 1) Temperature Transmitter

ISA 20T2221 Operating Parameters + Device Specifications Datasheet + Picklist Datasheet + Picklist MIMOSA 2018 ISDD Phases Build Map Publish ISO 15926 PCA RDL Energistics Unit of Measure MIMOSA CCOM Reference Data ISA 20 Picklists USPI CFIHOS RDL IEC Common Data Dictionary ECCMA Open Technical Dictionary MIMOSA Website MIMOSA 2018 Use XML Excel JSON (Work-in-progress) Building ISDDs

MIMOSA 2018 Current ISDD Build Process Applies to ISDs from all sources ISA (Rev 0, Rev 1), API, IEC.. Degree of automation differs based on the complexity/consistency of the datasheet ISA highly automatable, API much more difficult Manual QA review identifies issues with extracted properties and issues/ambiguities in source datasheets XMLprimary CCOM format Excel Spreadsheetfor Human Readability JSONfor IoT, light-weight data exchange Estimated ISDD Build Process Efforts Estimated level of effort per class for ISA and API ISDs ISA-Build ISDDs - 3.5 Hours/Class API-Build ISDDs - 3, 7 or 10 Days/Class/Sub-Class Estimated level of effort per class to convert CFIHOS classes 2 Hours/class assuming CFIHOS logically correct and consistent Automated conversion with manual QC review MIMOSA 2018 Current ISDD Status MIMOSA 2018 ISDD ISA 20T2221 Datasheet Equipment Type Temperature Transmitter

Attribute Set Definition Attribute Set Definition 20T2221 Device Specifications 20T1001 Operating Parameters Attribute Group Definition RESPONSIBLE ORGANIZATIONS Attribute Group Definition PROTECTIVE SHEATH AND FITTING ISA 20T2221 Picklist Attribute Definition Housing Type (Line 12) Attribute Type Housing Type Enumeration Housing Type Enumeration Items Extruder bolt High pressure Attribute Definition Pad/Collar Type (Line 13) Attribute Type Pad/Collar Type MIMOSA 2018

ISDD Instance Equipment Type ISA 20T2221 Datasheet Temperature Transmitter Attribute Set 20T2221 Device Specifications Attribute Set 20T1001 Operating Parameters Attribute Group RESPONSIBLE ORGANIZATIONS Attribute Group PROTECTIVE SHEATH AND FITTING ISA 20T2221 Picklist Attribute Housing Type = high pressure Attribute Pad/Collar Type = 1x1 flat parallel Attribute Fitting conn nominal size = in Attribute Attribute Type Housing Type

Enumeration Housing Type Enumeration Items Extruder bolt High pressure Mounting fitting type = compression . MIMOSA 2018 ISDD Definition ISDD Instance AttributeSet and Attribute in an ISDD Definition will have their type set to their respective AttributeSetType and AttributeType. AttributeSet, AttributeGroup and Attribute in an ISDD instance will refer to its definition in the ISDD definition. MIMOSA 2018 Temperature Transmitter

20T2221 Device Specifications 20T2221 Device Specifications PROTECTIVE SHEATH AND FITTING RESPONSIBLE ORGANIZATIONS PROTECTIVE SHEATH AND FITTING RESPONSIBLE ORGANIZATIONS Housing Type (Line 12) Pad/Collar Type (Line 13) Housing Type = high pressure Pad/Collar Type = 1x1 flat parallel Housing Type Pad/Collar Type MIMOSA 2018 Conformance Testing using ISDD CONFORMANCE ASSESSMENT DATA SHEET DEFINITION (ISDD) Property Reqd DATA SHEET (ISD) Property Value

MAX OPERATING TEMPERATURE Y MAX OPERATING TEMPERATURE 140 C MAX OPERATING PRESSURE Y MAX OPERATING PRESSURE MECHANICAL SEAL DIAMETER Y SHAFT MATERIAL N MIMOSA 2018 13 bar Mapping ISDDs

MIMOSA 2018 Supplier Mapping ISDDs suction _pres Shared Reference Data Library map 27507681-2369-4c38-967e-05ca7959c4bc Owner/Operator map Suction Pres . SUCTION PRESSURE shared UUID Shared Reference Datareceives Library Equipment Type Temperature Transmitter Data Sheet Definition sends 27507681-2369-4c38-967e-05ca7959c4bc Temperature Device

Attribute Set Definition 20T2221 Device Specifications mapping Attribute Group Definition RESPONSIBLE ORGANIZATIONS Organisation Metadata (Property Class) Attribute Group Definition PROTECTIVE SHEATH AND FITTING Attribute Definition Sheath and Fitting Data (Property Class) Housing Type Attribute Type Housing Type Enumeration Housing Type Enumeration Items Extruder bolt High pressure SUCTION PRESSURE (Equipment Type)

Temp. Device Housing (Property Type) Temp. Device Housing Values (Picklist) Extruder Bolt Housing High Pressure Bolt Housing MIMOSA 2018 Mappings defined and queried based on MIMOSA CIR specification. Supports terminological mappings and resolution within an OIIE Modified CIR spec to enable ISO 22745 conformance. Vendor/Supplier-to-ISDD Mapping Process E.g. Yokogawa EJX110A Differential Pressure Transmitter Relevant Properties, Picklist Values, UoMs, etc., for the model Similar to building an ISDD 1. Select Model Specification/ Datasheet 2. Create CCOM

Representation 4. Map Model Information to ISDD Properties 3. Identify Relevant ISDDs Map the model Properties, Picklist values, etc. to those of the identified ISDDs in the CCOM representation E.g. ISA 20P2301 Differential Pressure Device Specifications MIMOSA 2018 1. Select a Model Specification The EJX110A Differential Pressure Transmitter specification defines a type of differential pressure transmitter, where any physical device of this type is in a particular configuration as described by model specification suffix code. Only when a particular configuration or model variant is selected do all of the properties defined by the

specification have concrete values. MIMOSA 2018 2. Create CCOM Representation Attribute Set Definition EJX110A General Specifications Model Equipment Type Yokogawa - EJX110A Diff. Pressure Transmitter Attribute Group Definition MODEL AND SUFFIX CODES Attribute Definition Output signal [Level 1] Attribute Type Output Signal Enumeration Output Signal Enumeration Items 4 to 20 mA DC, w/ digital (BRAIN) [-D] Digital, FOUNDATION protocol Attribute Definition Measurement span (capsule) [level 2]

[-F] Attribute Type Measurement span Enumeration Measurement span Enumeration Items Attribute Group Definition OPTIONAL CODES MIMOSA 2018 0.1 to 5kPA (0.4 to 20 inH2O) [F] 0.1 to 10kPa (0.4 to 40 inH2O) [L] 3. Identify Relevant ISDDs Equipment Type Diff. Pressure Transmitter 20P2301 Device Specifications Attribute Set Definition 20P2301 Device Specifications Datasheet Attribute Group Definition Picklist TRANSMITTER

Attribute Definition Attribute Type Output signal type (Line 35) Output signal type Enumeration Output signal type Attribute Definition Min diff pressure span (Line 28) Attribute Type Min diff pressure span Enumeration Min diff pressure span Enumeration Items 0.4 MIMOSA 2018 Enumeration Items analog current digital multi-variable 4. Map Model Information to ISDD Properties Model Attribute Set Definition EJX110A General Specifications

Equipment Type Yokogawa - EJX110A Diff. Pressure Transmitter Attribute Group Definition MODEL AND SUFFIX CODES Attribute Definition Output signal [Level 1] Attribute Type Output Signal Enumeration Output Signal Enumeration Items 4 to 20 mA DC, w/ digital (BRAIN) [-D] Digital, FOUNDATION protocol Attribute Definition Measurement span (capsule) [level 2] [-F] Attribute Type Measurement span Enumeration Measurement span

Enumeration Items Attribute Group Definition OPTIONAL CODES 0.1 to 5kPA (0.4 to 20 inH2O) [F] 0.1 to 10kPa (0.4 to 40 inH2O) [L] MIMOSA 2018 Publishing ISDDs MIMOSA 2018 Publishing ISDDs Downloadable from MIMOSA website as a set of ZIP archives. Each (version of an) ISDD will have its own archive containing the following four files: 1. Load file in Excel format - provides a simplified view for aiding understanding. 2. CCOM XML - the normative data. 3. CCOM data in Excel format - non-normative, considered as documentation to aid understanding. 4. Reverse engineered single column datasheet in Excel - produced from the ISDD load file, similar to the original datasheet. Additional CCOM XML files containing reference data shared across ISDDs will also be provided, for example, a CCOM XML file for ISA-based property types will be provided. All ISA-based ISDDs will reference this file. Due to copyright and licensing, original ISDs will not be made available MIMOSA 2018 Using ISDDs Re-visiting User Stories for RFI/RFI response Show-casing the use of ISDDs MIMOSA 2018

Story M001:OIIE Configuration ISDD Selection 2. We need API 610 Centrifugal Pump, ISA 20C1001 (Control Valve, OP), 1. What datasheets (ISDDs) do we need in our OIIE instance? Client Ecosystem Admin 3. ISDD selection MIMOSA Reference OIIE Instance (InteropRegister and ISBM @ mimosa.org) Client Engineer?? (May be EPC) ISDD Defns. 4. Provisioning of local system with ISDD definitions MIMOSA 2018 Client OIIE System Story M002:OIIE Configuration ISDD Customisation

1. What non-standard properties do we need in the datasheets? 4. Do we need to restrict the export of any datasheet properties? Client Ecosystem Admin 6. Property restriction config dialog 3. ISDD extension dialog Client OIIE System ISDD defns. Extended ISDD definitions MIMOSA 2018 2. We need properties X, Y, Z for the Centrifugal Pump Client Engineer?? (May be EPC)

Client Business Manager?? 5. Properties A, B, C should only be shared with partners. Story M100:Start Unit Functional Requirements ISDD Instances 1.We need to build a light ends unit to remove butane from our incoming crude supply Client Business Person 2.a How Much Capacity Do We Need? b. What will the incoming crude spec be? Functional Requirements Debutanizer PFD and P&ID Client Engineer

(May be EPC) A MIMOSA 2018 Story M101:Model Selection 1. We need to buy equipment and instruments meeting or exceeding functional requirements taken from PFD and P&IDs for the new Debutanizer Tower. 2. Send me the Requirements from those documents and I will check with our preferred suppliers. Requirements Instrument or Equipment Supplier Portals 3.P2M Dialog Client Engineering Person A Requirements Debutanizer PFD and P&ID Models Meeting Requirements ISDD Instances

Client Purchasing (May be EPC) for Models ISDD defns. for Models B ISDD Instances Functional places MIMOSA 2018 OIIE/OGI Standardized Use Case Structure Actors Triggers Process Workflows Scenarios User Stories User Stories High-level Pictographic Depict 1 or more Use Cases, Scenarios, and/or Events Actors, Systems, Exchanges, Data MIMOSA 2018 Use Case 12: RFI/RFI Response in Brownfield Information Remediation

Scenario: RFI for Possible Models of an Asset Scenario: RFI Standard Model Properties Event 1: Process Model Request For Asset Event 3: Get Model Datasheets Event 2: Acknowledge Model Request For Asset Event 4: Show Standard Datasheets MIMOSA 2018 Use Case 12: Brownfield Information Remediation Scenario: RFI for Possible Models of an Asset Scenario: RFI Standard Model Properties Event 1: Process Model Request For Asset Event 3: Get Model Datasheets

Event 2: Acknowledge Model Request For Asset Event 4: Show Standard Datasheets Simplified Schema of ISDD CCOM XSLT ISDD Simplified Schema of ISDD instance CCOM ISDD Instance CCOM instance XSLT CCOM Simplified ISDD Instance

.. . .. ..

.. CCOM BODs Conceptual Approach Example BOD Noun Process Model Request For Asset Agent Owner/Operator Model ModelRequest Request(Request (RequestFor ForInformation) Information) from type *Request For Information Respond By = 2018-06-06 From FromAgent Agent(Agent: (Agent:Owner/Operator) Owner/Operator)

Request Type Model Request for Asset From FromAgent Agent(Agent: (Agent:Owner/Operator) Owner/Operator) about Asset Serial No. = XYZ0001 has Attribute Set has installed asset Respond RespondBy By(2018-06-06) (2018-06-06) Attribute Group Asset Asset(Asset: (Asset:with

withS/N S/NXYZ0001) XYZ0001) has Serial SerialNumber Number(XYZ0001) (XYZ0001) Attribute Model Spec. No. = Asset Installation Event Installed At: 2017-06-06 Functional FunctionalLocation Location(Segment: (Segment:Functional FunctionalLocation LocationTS001) TS001) installed location Segment Functional Location TS001 has Attribute Set ISDD Instance

has Asset AssetInstallation InstallationDate Date(2017-06-06) (2017-06-06) Attribute Group Functional FunctionalRequirements Requirements(Attribute (AttributeSet: Set:ISDD ISDDInstance) Instance) has Attribute Temp. Max. = 90o Group Group(Attribute (AttributeGroup) Group) Attribute Temp. Min. = 15o o Attribute Attribute(Attribute:

(Attribute:Temp. Temp.Min. Min.==-15 -15o)) o Attribute Attribute(Attribute: (Attribute:Temp. Temp.Max. Max.==90 90o)) MIMOSA 2018 BOD: ProcessModelRequestForAsset Application Area Data Area Brownfield Information Remediation Business Object Document Scenario: RFI for Possible Models of an Asset Scenario: RFI Standard Model Properties Event 1: Process Model Request For Asset Event 3: Get Model Datasheets Event 2: Acknowledge Model Request For Asset

Event 4: Show Standard Datasheets Verb: Process Noun: ModelRequestForAsset MIMOSA CCOM Entity (e.g. Asset, Functional Location) ISDD ISDD Instance Instance ISDD ISDD Instance Instance (Functional (Functional Requirements) Requirements (Model (Model Information) Information) ) Simplified ISDD Instance XML (Model Information)

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 83641788-187f-4be1-96bf-c1bfe517f94f 78807960-cf6a-4524-94bd-b06d0cc1405d RTD Assembly-T1 Example O/O 1002468 extruder bolt 1x1 flat parallel 1/8 inch NF thd MIMOSA 2018 BOD: ProcessModelRequestForAsset Application Area Data Area Verb: Process Brownfield Information Remediation With Multiple Devices Scenario: RFI for Possible Models of an Asset Scenario: RFI Standard Model Properties

Event 1: Process Model Request For Asset Event 3: Get Model Datasheets Event 2: Acknowledge Model Request For Asset Event 4: Show Standard Datasheets Noun: ModelRequestForAsset MIMOSA CCOM Entity: Pressure Transmitter ISDD ISDD Instance (Operating Instance Parameters) ISDD ISDD Instance (Device Instance Specifications) ISA 20P2201 Operating Parameters ISA 20P1001 Device Specifications

MIMOSA CCOM Entity: Temperature Transmitter ISDD ISDD Instance (Operating Instance Parameters) ISDD ISDD Instance (Device Instance Specifications) ISA 20T2201 Operating Parameters MIMOSA 2018 ISA 20T1001 Device Specifications How do Owner/Operators and Suppliers use ISDDs? Use ISDD as-is Extend ISDDs (for custom properties) Re-use ISDDs (for common properties) Restrict ISDDs MIMOSA 2018 Extending an ISDD MIMOSA 2018

ISDDs Support Extensions Industry Standard DSD Extensions through single inheritance Allow common properties to be grouped together at an equipment super class Thus changes at a super class ISDD are also reflected in sub class ISDD Reduces work for ISDD authoring (as long as a suitable equipment taxonomy is in place) Standard property 1 Industry Standard DSD Standard property 1 Standard property 2 parent Standard property 2 parent O/O Extended DSD Custom property 1 Custom property 2 O/O Extended DSD Custom property 1 Custom property 2 Owner/Operator Extensions

parent Project Extended DSD Custom property 3 Custom property 4 Project Extensions Re-using ISDDs MIMOSA 2018 ISDDs Support Re-use (CCOM 4.1 onwards) Reuse of Attribute (Set/Group) Definitions across many different entity types More flexible reuse than single inheritance parent relationship Ability to reuse multiple attribute sets Reduce duplication of Attribute (Set/Group) Definitions Copy of includes parent Extended Metadata includes OEM Metadata

for Device (Type) Cannot modify Temp. Trans. Properties for Temperature Transmitter for OEM Model XJC Temp. Trans. parent XJC Properties group OEM Metadata Aim to avoid this type of duplication. Pressure Transmitter ISDD Path Forward Use ISDDs to define the property sets associated with all Functional

Locations, Models and Uniquely Identified Assets Allow new ISDD versions to be applied to existing Sites, Areas and Units under an MoC process Use ISDDs for packages ISDD Team will develop, publish and maintain most important ISDDs develop and publish associated documentation for each ISDD it publishes. develop and publish requirements documentation develop associated validation process, using OIIE/OGI Pilot testbed Future candidate ISDDs can then be built by anyone and submitted as candidates for validation and publication by MIMOSA MIMOSA 2018 ISDD Build and Use Plan for 2018/2019 Numbers of Properties on ISDs All properties needed for digitalization ISA- 150-350 API- 100-900* 75 ISA Rev 1 Sheets OIIE/OGI Pilot Sub-Phase 1 CFIHOS Limited number of properties based on current industry use practices ISA Rev 1 Sheets can now be converted to ISDDs through mostly automatic processing.

A +5 +25 ISA Rev 1 Sheets +15 O t OIIE/OGI Pilot h Sub-Phase 2 e r O t h e r I S D D S I S D D S B

MIMOSA 2018 C D +ISDDs based on CFIHOS Classes Business-Driven Work Arounds Will work with members and industry to prioritize Sets B and D and work around strategy for all remaining classes. Package ISDDs: The Bigger Picture Complex Unit Equipment Packages Devices & Equipment Pumping Package Standardised ISDD Group for Package MIMOSA 2018 ISDDs for Devices & Equipment Business Object Document for Packages

BOD: ProcessModelRequestforPackage ProcessModelRequestFor Package Application Area Use Case: Make-Model Match-Up (Package) Data Area Verb: Process Noun: ModelRequestForPackage MIMOSA CCOM Entity: VF AC Drive Package ISDD Instance ISDD Instances Entity: Controller ISDD Instances Entity: Centrifugal Pump

ISDD Instances MIMOSA 2018 Scenario: RFI for Possible Models for Package Scenario: RFI Standard Model Properties Event 1: Process Model Request For Package Event 3: Get Model Datasheets Event 2: Acknowledge Model Request For Package Event 4: Show Standard Datasheets Use case for Make-Model Match-Up Scenarios for individual devices, equipment and packages. Scenario for retrieving model datasheets is reused across use cases. BOD for packages ensures the request is treated as a whole

Use Cases 7 & 14: Condition Based Maintenance & IIoT MIMOSA 2018 Open Industrial Interoperability Ecosystem Use Cases for Condition Based Maintenance Currently, three use cases related to CBM: Use Case 5: Asset Installation/Removal Updates Use Case 7: Condition Based Maintenance Triggering Use Case 14: Condition Based Maintenance Information Collection Collectively describe the: collection of measurement data: Scenarios 29, 30, 31, 32 generation of diagnostics, prognostics, and advisories: Scenarios 14 creation of a work order to repair/replace the equipment: Scenarios 15, 16 replacement of the equipment that will/has fail(ed): Scenarios 10, 11 Assume other use cases (handover/provisioning) as prerequisites that set up the context in which CBM operates Context maintained on event-driven basis (Configuration Change) MIMOSA 2018 Contextualization for Open Industrial Interoperability Ecosystem using MIMOSA CCOM 4.x, ISA, OAGi, ISO and IEC Standards Process Engineering (CCOM Segment Networks) PFDs Work Processes followed for CAPEX and OPEX (Intra and Inter-Enterprise) Production Process to be supported by Plant/Platform/Facility Functional/Systems Engineering (CCOM Segment Networks) P&IDs , other schema System of Systems Systems (Functional Packages) Functional Locations (P&ID Tag)

Components Sensors Models (CCOM Model) Used for MFG Model and Package Model Serialized Equipment & Devices (CCOM Assets installed in CCOM Functional Locations) Multiple Breakdown Structures as Needed Taxonomic views of same CCOM objects Enterprise Breakdown Enterprise/Area/Unit (ISA 95/88) Maintenance Breakdown Structure (eg ISO 14224) ISDDs (Standardized) Property Sets for ALL Functional Locations, Equipment and Devices IIOT Data captured by Sensors is Contextualized by ALL of Above MIMOSA 2018 ExampleSegments and Asset Configuration Organization UniSA Farm Co. Site Mawson Lakes Breakdown Structure Primary Segment Holding Tank T-001 AssetSegmentEvent Install 8 Jan 2018 Asset

Tank Serial # TXZ-738 Model Tank TXZ Series Segment Pasteurizer P-001 AssetSegmentEvent Install 30 Jan 2018 Asset Pasteurizer Serial # PZR-3246 Model Pasteurizer PZR 5000 Segment Holding Tank T-002 AssetSegmentEvent Asset Tank Serial # TYA-234 Remove 10 Jan 2018 AssetSegmentEvent

Install 12 Jan 2018 MIMOSA 2018 Asset Tank Serial # TYA-637 Manufacturer Parts and Associated Manufacturer UniSA Parts Services Model Tank TYA ExampleComponents & Measurement Locations Asset Pasteurizer Serial # PZR-3246 Asset Tank Serial # MT-456 Asset Pump Serial # PF332 Asset Tube

Asset Temp. Sensor Serial # TS-999 Model Pasteurizer PZR 5000 Transducer Measurement Location Temp. Loc. 1 AssetSegmentEvent AssetSegmentEvent AssetSegmentEvent AssetSegmentEvent Install 1 Jan 2018 Install 1 Jan 2018 Install 1 Jan 2018 Install 1 Jan 2018 Segment

Feed Tank T1 Segment Feed Pump P2 Segment Product In Tube PIT 3 Segment Temperature Sensor TS-1 Segment Temperature Sensor TS-2 Breakdown Structure Primary MIMOSA 2018 Supports both Assetand Segment-based MeasurementLocations Measurement Location Temp. Loc. 1 ExampleMesh Networks Model Pasteurizer PZR 5000

from Segment T1 Outlet parent Segment Feed Tank T1 Segment Connection to Segment Mesh Segment P2 Inlet parent Segment Feed Pump P2 PZR Connections from And similar at the Asset level Segment P2 Outlet parent Segment

PIT 3 Inlet parent Segment Connection to MIMOSA 2018 Segment Product In Tube PIT 3 OIIE Systems and Scenarios Landscape SDAIR MIMOSA 2018 Registry of digital asset data for contextualisation. Condition Based Maintenance and IIoT Device Manufacturer Supplying Remote Diagnostic/Prognostic/Advisory Support Owner/Operator Internally may have some or none of Intra-Enterprise ISBM these systems.

ERP SDAIR Automation and Control May be same physical instance as the intraenterprise ISBM HSE and Operation Monitoring Automated System Bus Prognostic & Health Management Inter-Enterprise via ISBM Maintenance Management System Operational Risk Management System HSE and Operation Monitoring Prognostic & Health Management Device

Device Sensor/ Transducer Support for different protocols as required by industry. IIoT Device IIoT Device MIMOSA 2018 IIoT Device Supports remote queries for measurement data and publishes advisories via ISBM. User Stories for CBM Use Cases MIMOSA 2018 CBM According to ISO 13374 Machine condition assessment data processing & information flow blocks.

Sensor / Transducer / Manual Entry DATA ACQUISITION (DA) External Systems, Data Archiving, & Block Configuration DATA MANIPULATION (DM) STATE DETECTION (SD) HEALTH ASSESSMENT (HA) PROGNOSTICS ASSESSMENT (PA) ADVISORY GENERATION (AG) MIMOSA 2018 Technical Displays & Information Presentation Story M200: Condition Information Collection (Trusted) 1. Condition Information Device/Instrument Operational Risk Management (ORM) System B

Equipment XXX 2b. Condition Information Sensor/Instrument 2a. Measurements Condition Monitoring System (CMS) * CMS could be running autonomously or responding to human requests MIMOSA 2018 Story M201a: Condition Information Collection (IIoT) Authorization A1. I need to obtain entry to the Trusted Systems to send my data to ORM* Maintenance Engineer OIIE Authentication (through ISBM) A2. Request Access OIIE Authorization B2. Request Access A3. Authorization Granted OIIE Authorization

Equipment XXX Sensor/Instrument B3. Authorization Granted B1. I need to obtain entry to the Trusted Systems to send my data to ORM* MIMOSA 2018 * Operational Risk Management System Story M201b: Condition Information Collection (IIoT) 1. I need to check the condition of equipment XXX Maintenance Engineer 3a. Vibration measurements 4a. Condition Information (Assigned by Human) Operational Risk Management System B OIIE Authorization 4b. Condition Information (Assigned by CMS) 2. Take vibration measurements (Triggered by Human)

OIIE Authorization Equipment XXX Sensor/Instrument 3b. Measurements Condition Monitoring System * Condition Monitoring System could be MIMOSA 2018 running autonomously or responding to human requests Story M202: CBM Diagnostic/Prognostic/Advisory Generation 1. I have detected an incipient failure of equipment XXX B Operational Risk Management System 2. Lodge Request for Work for equipment XXX Maintenance Management System 3a. Generate Work Request Work Request YYY

3b. Confirm request with Work Request C MIMOSA 2018 Story M203: Plan Corrective Maintenance (Remove/Replace) 1. I need to schedule the maintenance of equipment XXX according to Work Request YYY before it fails. C Work Request YYY 4. I need to keep track of the Work Order so I know when it is time to shut down the machine and when it is complete. Operational Risk Management System Maintenance Planner 2. Generate and schedule Work Order 3. Notify ORM of Work Order ZZZ Maintenance Management System Work Order ZZZ

D MIMOSA 2018 Story M204: Maintenance & Status Updates D 1. I need to perform maintenance on equipment XXX according to Work Order ZZZ Work Order ZZZ 2. Record Removal* Maintenance Technician 6. The work looks complete. I will sign off on it and close the Work Order ZZZ. 4. Record Installation* Work Status Removed 5. Publish update Work Status Installed 7. Publish update 6. Close work order ZZZ

Work Status Closed E * Asset Remove and Asset Install Events (dis-)establish relationship between Assets and Functional Locations Maintenance Management System (MMS) 3. Publish update Maintenance Supervisor 3, 5. Work order ZZZ Status Updates MIMOSA 2018 Story M205: Work Order Closed 1. I have detected that Work Order ZZZ is complete. (Either by querying MMS or through notifications) Operational Risk Management System 2. Notify that equipment XXX is ready to come back online 0. Notification or query. Maintenance

Management System Work Status Closed E Work Order ZZZ MIMOSA 2018 Control System CCOM ContextualisationMaintained by SDAIR Asset Debutanizer Serial # DZR-3246 Each identified by Also to system Each object object uniquely uniquely identifiedAsset by aa UUID. UUID.Asset Also refer refer back back to the the

system of of record. record. Asset Asset Transducer Tower Serial # T-456 Pipe Section Condenser Serial # CF332 Temp. Sensor Serial # TS-999 Model Debutanizer DZR 5000 Measurement Location Temp. Loc. 1 AssetSegmentEvent Install 1 Jan 2018 AssetSegmentEvent Install 1 Jan 2018 AssetSegmentEvent Install

1 Jan 2018 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 10oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 AssetSegmentEvent Install 1 Jan 2018 Supports both Assetand Segment-based MeasurementLocations Segment Debutanizer Tower T100 Segment Debutanizer Feed Segment Condenser C200 Segment Temperature Sensor TS-1

Segment Temperature Sensor TS-2 Breakdown Structure Primary MIMOSA 2018 AttributeSet Custom Measurement Data Measurement Location Temp. Loc. 2 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 4oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 CCOM ContextualisationConfiguration Change Remove/Replace Asset

Debutanizer Serial # DZR-3246 Asset Tower Serial # T-456 Model Debutanizer DZR 5000 Asset Pipe Section Asset Pipe Section Asset Condenser Serial # CF332 Asset Temp. Sensor Serial # TS-999 Transducer Measurement Location Temp. Loc. 1 AssetSegmentEvent Install 1 Jan 2018 Segment Debutanizer

Tower T100 AssetSegmentEvent Install AssetSegmentEvent AssetSegmentEvent 1 Jan 2018 Remove Install 2 Jan 2018 3 Jan 2018 Segment Debutanizer Feed AssetSegmentEvent Install 1 Jan 2018 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 10oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00

AssetSegmentEvent Install 1 Jan 2018 Supports both Assetand Segment-based MeasurementLocations Segment Condenser C200 Segment Temperature Sensor TS-1 Segment Temperature Sensor TS-2 Breakdown Structure Primary MIMOSA 2018 AttributeSet Custom Measurement Data Measurement Location Temp. Loc. 2 Measurement Measurement Measurement Recorded at: Measurement

Recorded at: Recorded at: 2018-06-01:01:00 4oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 Message Exchanges MIMOSA 2018 (Web Service) Information Service Bus Model Information Service Bus Model is the centre of messaging in the OIIE Purpose: to facilitate interoperability by providing a standardized set of web services for the sending/receiving of messages via a busleads to application and supplier agnostic ecosystem administration Supports publish/subscribe and request/response modalities Includes Notification web services: avoids polling the bus for messages OpenO&M ws-ISBM specification v1.0 based on SOAP web services Current SOAP API already RESTful: each request includes all information required RESTful architectures are technically protocol and data format agnostic Revised specification, v1.1, will support plain HTTP/JSON REST interface To be proven in the upcoming stage of the OGI pilot MQTT or AMQP MIMOSA 2018 ws-ISBM REST APIResources ISBM is payload data agnostic Resources are NOT payload data types such as MeasurementLocation Resources in the ISBM include: Channels

Security Tokens Sessions Messages Revision 1.2 will consider configurable mappings for payload-based interfaces There are several potential challenges in developing such a mapping MIMOSA 2018 ws-ISBM Channel Management Service Service Operation SOAP Interface RESTful Interface Create Channel HTTP method: POST URL: /ChannelManagement Data: Specified in HTTP body HTTP method: POST URL: /channels Data: Specified in HTTP body Add Security Tokens HTTP method: POST URL: /ChannelManagement Data: Specified in HTTP body HTTP method: POST URL: /channels/{channel-id}/security-tokens

Token data is specified in HTTP body Remove Security Tokens HTTP method: POST URL: /ChannelManagement Data: Specified in HTTP body HTTP method: DELETE URL: /channels/{channel-id}/security-tokens/{token-id} Data: Specified in URL Delete Channel HTTP method: POST URL: /ChannelManagement Data: Specified in HTTP body HTTP method: DELETE URL: /channels/{channel-id} Data: Specified in URL Get Channel HTTP method: POST URL: /ChannelManagement Data: Specified in HTTP body HTTP method: GET URL: /channels/{channel-id} Data: Specified in URL Get Channels HTTP method: POST

URL: /ChannelManagement Data: N/A HTTP method: GET URL: /channels Data: N/A MIMOSA 2018 ws-ISBM Consumer Request Service Service Operation SOAP Interface RESTful Interface Open Consumer Request Session HTTP method: POST URL: /OpenConsumerRequestSession Data: Specified in HTTP body HTTP method: POST Post Request HTTP method: POST URL: /PostRequest Data: Specified in HTTP body HTTP method: POST URL: /sessions/{session-id}/requests?topic={string}[&expiry={duration}] Data: Message specified in HTTP body, filters in URL

Expire Request HTTP method: POST URL: /ExpireRequest Data: Specified in HTTP body HTTP method: DELETE URL: /sessions/{session-id}/requests/{message-id} Data: Specified in URL Read Response HTTP method: POST URL: /ReadResponse Data: Specified in HTTP body HTTP method: GET URL: /sessions/{session-id}/responses?requestMessageId={string} Data: Specified in URL Remove Response HTTP method: POST URL: /RemoveResponse Data: Specified in HTTP body HTTP method: DELETE URL: /sessions/{session-id}/responses/{response-message-id} Data: Specified in URL Close Consumer Request Session HTTP method: POST URL: /CloseConsumerRequestSession

Data: Specified in HTTP body HTTP method: DELETE URL: /sessions/{session-id} Data: Specified in URL URL: /channels/{channel-id}/consumer-request-sessions[?listenerUrl={URL}] Data: Specified in URL (channel-id, optional listenerUrl) MIMOSA 2018 ws-ISBM Provider Request Service Service Operation SOAP Interface RESTful Interface Open Provider Request Session HTTP method: POST URL: /OpenProviderRequestSession Data: Specified in HTTP body HTTP method: POST URL: /channels/{channel-id}/provider-request-sessions Data: Session config specified in HTTP body (topics[1..*], listener-url[?], XPathExpression[0..1], XPathNamespace[*]) Read Request HTTP method: POST URL: /ReadRequest

Data: Specified in HTTP body HTTP method: GET URL: /sessions/{session-id}/request Data: Specified in URL Remove Request HTTP method: POST URL: /RemoveRequest Data: Specified in HTTP body HTTP method: DELETE URL: /sessions/{session-id}/request Data: Specified in URL Post Response HTTP method: POST URL: /PostResponse Data: Specified in HTTP body HTTP method: POST URL: /sessions/{session-id}/responses?requestMessageId={string} Data: Message specified in HTTP body, filters in URL Close Provider Request Session HTTP method: POST URL: /CloseProviderRequestSession Data: Specified in HTTP body HTTP method: DELETE URL: /sessions/{session-id}

Data: Specified in URL MIMOSA 2018 OIIE Use Case Message Requirements Response messages must include contextual parameters to support: Redistribution Load balancing Archival Analytics Standardized application level status (errors, etc.) Through appropriate CCOM reference data Extensible application level status: Different providers/systems may have their own error codes that need to be describable, exchangeable, and interpretable Through vendor reference data, for example MIMOSA 2018 OIIE Use Case Message Structure Utilise the BOD architecture Fulfils most requirements out-of-the-box Extensibility allows support for the rest Supported Verbs Get, Show, Sync, Confirm Specify additional header properties in the Application Area as required For example, Show including the original filters from the Get message. User Area is preferred for meta-data, rather than modifying the Data Area

Business Object Document Application Area Data Area Verb Noun MIMOSA CCOM Payload Example Publish Configuration Change (Remove): Scenario 10 Asset Debutanizer Serial # DZR-3246 POST: POST: /sessions/{session-id}/publications?topic={topic-name} /sessions/{session-id}/publications?topic={topic-name} Asset Asset Asset SyncAssetSegmentEvents SyncAssetSegmentEvents Transducer Asset Tower Condenser Temp. Sensor Model Debutanizer DZR 5000 Breakdown Structure

Primary Pipe Section Serial # T-456 Serial # CF332 Serial # TS-999 "dataArea": { "sync": {}, "dataArea": { "sync": {}, Measurement Location "assetSegmentEvents": "assetSegmentEvents": [[ {{ Temp. Loc. 1 "assetSegmentEvent": "assetSegmentEvent": [[ {{ "@@type": "AssetSegmentEvent", "@@type": "AssetSegmentEvent", "UUID": "UUID": "3a79dbc5-4801-8fd7-8645-2de5faef4780", "3a79dbc5-4801-8fd7-8645-2de5faef4780", AssetSegmentEvent AssetSegmentEvent AssetSegmentEvent "ShortName": "Flow S/N on "ShortName": "Flow Meter Meter AssetSegmentEvent S/N TS-189 TS-189 Removed

Removed on FM-8", FM-8", Install "Created": "2018-10-01T03:28:20Z", Install Install Install "Created": "2018-10-01T03:28:20Z", 1 Jan 2018"Start": "2018-10-01T03:40:20Z", 1 Jan 2018 1 Jan 2018 1 Jan 2018 "Start": "2018-10-01T03:40:20Z", "End": "End": "2018-10-01T03:28:40Z", "2018-10-01T03:28:40Z", Supports both Asset"InfoSource": "InfoSource": {{ "UUID": "UUID": "19a137cf-a70d-2888-343a-bc1158bf7f9f" "19a137cf-a70d-2888-343a-bc1158bf7f9f" }, }, and Segment-based "EventType": { "EventType": { MeasurementLocations "UUID": "UUID": "3a45e126-b234-42a0-b3b1-07c29522d02d", "3a45e126-b234-42a0-b3b1-07c29522d02d", "ShortName": "ShortName": "Removal "Removal of of Asset Asset on on Segment",

Segment", Segment "InfoSource": { "UUID": "cf3f3a8a-1e42-4f15-9288-9cf2241e163d" Segment }} "InfoSource": Segment{ "UUID": "cf3f3a8a-1e42-4f15-9288-9cf2241e163d" Segment Debutanizer Temperature }, }, Debutanizer Feed Condenser C200 Tower T100 Sensor TS-1 "Asset": "Asset": {{ "UUID": "35e17dde-6e82-4591-50a3-f553b6185292", "UUID": "35e17dde-6e82-4591-50a3-f553b6185292", "ShortName": "ShortName": "Flow "Flow Meter Meter FM-189" FM-189" Segment }, Measurement Location }, Temperature Temp. Loc. 2 "Segment": "Segment": {{ Sensor TS-2 "UUID":

"UUID": "ec5a2f64-1c3a-34ef-766d-eb69ba865d59", "ec5a2f64-1c3a-34ef-766d-eb69ba865d59", "ShortName": "ShortName": "Flow "Flow Meter Meter FM-8" FM-8" }} }} ]] }} ]] }} MIMOSA 2018 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 10oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 AttributeSet Custom Measurement Data Measurement Measurement Measurement Recorded at: Measurement Recorded at:

Recorded at: 2018-06-01:01:00 4oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 Example Query for Context/Configuration: Scenario 11 Asset Debutanizer Serial # DZR-3246 POST: POST: /sessions/{session-id}/requests?topic={topic-name} /sessions/{session-id}/requests?topic={topic-name} Asset Asset Asset GetAssetSegmentEvents GetAssetSegmentEvents Transducer Asset Tower Condenser Temp. Sensor Serial # T-456 Pipe Section Serial # CF332 Model Debutanizer DZR 5000

Serial # TS-999 Measurement Location Temp. Loc. 1 {{ Breakdown Structure Primary }} AssetSegmentEvent AssetSegmentEvent AssetSegmentEvent AssetSegmentEvent Install Install Install Install "@@type": "@releaseID": "9.0", "@versionID": "1.0", "@@type": "GetAssetSegmentEvents", "@releaseID": "9.0", "@versionID": "1.0", 1 Jan 2018"GetAssetSegmentEvents", 1 Jan 2018

1 Jan 2018 1 Jan 2018 "applicationArea": "applicationArea": {{ "sender": "sender": {{ Supports both Asset"logicalId": "logicalId": "466aa22b-ffce-4ea0-acf4-587e372d7ba5" "466aa22b-ffce-4ea0-acf4-587e372d7ba5" and Segment-based }, }, MeasurementLocations "creationDateTime": "creationDateTime": "2018-10-22T08:34:15Z", "2018-10-22T08:34:15Z", "bodID": "bodID": "0e4bd242-77b6-476c-9105-c63fc078b595" Segment "0e4bd242-77b6-476c-9105-c63fc078b595" Segment Segment Segment }, }, Debutanizer Temperature Debutanizer Feed Condenser C200 "dataArea": "dataArea": Tower T100 {{ Sensor TS-1 "get":

"get": {}, {}, "assetSegmentEventsCriteria": "assetSegmentEventsCriteria": [[ {{ Segment Measurement Location "segmentUuid": }} Temperature "segmentUuid": {{ "value": "value": "ec5a2f64-1c3a-34ef-766d-eb69ba865d59" "ec5a2f64-1c3a-34ef-766d-eb69ba865d59" Temp. Loc. 2 }} Sensor TS-2 ]] }} MIMOSA 2018 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 10oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00

AttributeSet Custom Measurement Data Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 4oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 Example Query for Context/Configuration: Scenario 11 Asset Debutanizer Serial # DZR-3246 {{ "dataArea": GET: "dataArea": {{ "show": "show": {}, {}, GET: /sessions/{session-id}/responses?requestMessageId=0e4bd242--c63fc078b595 /sessions/{session-id}/responses?requestMessageId=0e4bd242--c63fc078b595 "assetSegmentEvents": "assetSegmentEvents": {{ "count": 2, "count":

2, Asset Asset Asset GetAssetSegmentEvents GetAssetSegmentEvents Transducer Asset[[ "assetSegmentEvent": "assetSegmentEvent": Tower Condenser Temp. Sensor Model Debutanizer DZR 5000 Breakdown Structure Primary Pipe Section Serial{{ # T-456 Serial # CF332 Serial # TS-999 "@@type": "AssetSegmentEvent", "@@type": "AssetSegmentEvent", "UUID": "UUID": "3a79dbc5-4801-8fd7-8645-2de5faef4780", "3a79dbc5-4801-8fd7-8645-2de5faef4780", Measurement Location "ShortName":

"ShortName": "Flow "Flow Meter Meter S/N S/N TS-189 TS-189 Removed Removed on on FM-8", FM-8", Temp. Loc. 1 "Created": "Created": "2018-10-01T03:28:20Z", "2018-10-01T03:28:20Z", "Start": "Start": "2018-10-01T03:40:20Z", "2018-10-01T03:40:20Z", "End": "End": "2018-10-01T03:28:40Z", "2018-10-01T03:28:40Z", AssetSegmentEvent AssetSegmentEvent AssetSegmentEvent AssetSegmentEvent "InfoSource": {{ "UUID": }, Install Install Install "InfoSource": Install "UUID": "19a137cf-a70d-2888-343a-bc1158bf7f9f" "19a137cf-a70d-2888-343a-bc1158bf7f9f" }, "EventType": { 1 Jan 2018

1 Jan 2018 1 Jan 2018 1 Jan 2018 "EventType": { "UUID": "UUID": "3a45e126-b234-42a0-b3b1-07c29522d02d", "3a45e126-b234-42a0-b3b1-07c29522d02d", "ShortName": Supports both Asset"ShortName": "Removal "Removal of of Asset Asset on on Segment", Segment", "InfoSource": }} and Segment-based "InfoSource": {{ "UUID": "UUID": "cf3f3a8a-1e42-4f15-9288-9cf2241e163d" "cf3f3a8a-1e42-4f15-9288-9cf2241e163d" }, MeasurementLocations }, "Asset": "Asset": {{ Segment "UUID": Segment "UUID": "35e17dde-6e82-4591-50a3-f553b6185292", "35e17dde-6e82-4591-50a3-f553b6185292",

Segment Segment "ShortName": "Flow Meter FM-189" Debutanizer Temperature "ShortName": "Flow Meter FM-189" Debutanizer Feed Condenser C200 }, Tower T100 Sensor TS-1 }, "Segment": { "Segment": { "UUID": "UUID": "ec5a2f64-1c3a-34ef-766d-eb69ba865d59", "ec5a2f64-1c3a-34ef-766d-eb69ba865d59", Segment "ShortName": "ShortName": "Flow "Flow Meter Meter FM-8" FM-8" Measurement Location Temperature }} Temp. Loc. 2 Sensor TS-2

}, }, {{ }} ]] }} }} }} MIMOSA 2018 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 10oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 AttributeSet Custom Measurement Data Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 4oC at:

2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 Push (Current) Condition/Operation Information: Scenarios 29/30 Asset Debutanizer Serial # DZR-3246 Asset Tower Serial # T-456 Asset Condenser Serial # CF332 Asset Pipe Section Asset Temp. Sensor Serial # TS-999 Model Debutanizer DZR 5000 Transducer Measurement Location Temp. Loc. 1 AssetSegmentEvent

Install 1 Jan 2018 AssetSegmentEvent Install 1 Jan 2018 AssetSegmentEvent Install 1 Jan 2018 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 10oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 AssetSegmentEvent Install 1 Jan 2018 Supports both Assetand Segment-based MeasurementLocations POST: POST: /sessions/{session-id}/publications?topic={topic-name} /sessions/{session-id}/publications?topic={topic-name}

SyncMeasurements [including MeasurementLocation context] SyncMeasurements [including MeasurementLocation context] Segment Segment Segment Segment Debutanizer Tower T100 Debutanizer Feed Condenser C200 GET: GET: /sessions/{session-id}/publication /sessions/{session-id}/publication SyncMeasurements SyncMeasurements Primary Breakdown Structure MIMOSA 2018 AttributeSet Custom Measurement Data Temperature

Sensor TS-1 Segment Temperature Sensor TS-2 Measurement Location Temp. Loc. 2 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 4oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 Get (Historical) Condition/Operation Information: Scenarios 31/32 POST: POST: /sessions/{session-id}/requests?topic={topic-name} /sessions/{session-id}/requests?topic={topic-name} GetMeasurementLocations[filtered GetMeasurementLocations[filtered by by Asset Asset UUID] UUID] Asset Debutanizer Serial # DZR-3246

Asset Tower Serial # T-456 Asset Pipe Section Asset Condenser Serial # CF332 Asset Temp. Sensor Serial # TS-999 Transducer Model GET: GET: /sessions/{session-id}/responses?requestMessageId={id} /sessions/{session-id}/responses?requestMessageId={id} Debutanizer DZR 5000 ShowMeasurementLocations ShowMeasurementLocations AssetSegmentEvent Install 1 Jan 2018 AssetSegmentEvent Install 1 Jan 2018 AssetSegmentEvent Install

1 Jan 2018 Measurement Location Temp. Loc. 1 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 10oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 AssetSegmentEvent Install 1 Jan 2018 Supports both Assetand Segment-based MeasurementLocations POST: POST: /sessions/{session-id}/requests?topic={topic-name} /sessions/{session-id}/requests?topic={topic-name} Segment Segment Segment Segment GetMeasurements[filtered by

MeasurementLocation UUID GetMeasurements[filtered by MeasurementLocation UUID & & date/time] date/time] Debutanizer Temperature Debutanizer Feed Condenser C200 Tower T100 AttributeSet Custom Measurement Data Sensor TS-1 Segment GET: GET: /sessions/{session-id}/responses?requestMessageId={id} /sessions/{session-id}/responses?requestMessageId={id} Temperature Sensor TS-2 Primary Could also be filtered ShowMeasurements ShowMeasurements Breakdown Structure by Asset or Segment.

MIMOSA 2018 Measurement Location Temp. Loc. 2 Measurement Measurement Measurement Recorded at: Measurement Recorded at: Recorded at: 2018-06-01:01:00 4oC at: 2018-06-01:01:00 2018-06-01:01:00 2018-06-01:01:00 Collaboration Update MIMOSA 2018 Solution: Open Standards Fill The Gaps Enterprise Business Systems Enterprise Resource Planning (ERP) O P E R A T I O N

S OpenO&M FOUNDATION Physical Asset Control Real-time Systems MIMOSA 2018 M A I N T E N A N C E OpenO&M Joint Working Group Current Activities ISBM Update in alignment with ISA 95/IEC 62264 MSM Version 1.0 being updated to Version 1.x OIIE Use Cases Provide Functional and Non-Functional Requirements OpenO&M Website

Channel Management Service API Message support for IIoT sensor data Process support (e.g., BPEL) Implementation Requirements Non-Functional Requirements Functional Requirements Performance Easy Administration Scalability Supplier Neutrality Reliability Security (e.g., ISA99) Intra-/Inter-Enterprise comm. MIMOSA 2018

Publish/Subscribe vs Request/ Response REST vs SOAP Support for XML and JSON OpenAPI MQTT Proper evaluation of requirements from IIoT perspective necessary Each requirement is evaluated against OIIE Use Cases Examples: XML vs JSON and OpenAPI OpenAPI XML vs JSON Large differences between XML Schema and JSON Schema definition Required for verification Challenges if support for both at the same time MIMOSA 2018 Proposal for JSON and XML

schema in an OpenAPI document (not yet accepted) Current OpenAPI refers to early JSON Schema version MIMOSA/OIIE Documentation Strategy MIMOSA 2018 Many related ISO and IEC Activities WG 6 MIMOSA 2018 ISO 18101-1 Concept Map Being Developed By ISO TC 184/WG 6 CD/DTS Ballot Completed (12 Yes Votes) Reference Environment Capital Project Execution Environment Interoperability Digital Transformation Supplier Neutral IEC 62264 MSM/OpenO&M ISBM Shared Semantic Context Digital Twin/Event/Time Series Data Sets

Validated Use Cases OGI Pilot Information and Data Quality ISO 8000 MIMOSA 2018 O&M Global Collaboration Asset Institute NIST (Smart Manufacturing Team for Industry 4.0) POSC Caesar, USPI MIMOSA 2018

Recently Viewed Presentations

  • Synthetic Chemical Experiment Chem is try ! Grignard

    Synthetic Chemical Experiment Chem is try ! Grignard

    Grignard Reaction 实验 1-苄基环戊醇的合成 实 验 原 理: 反应式: 化学教学实验中心 Chem is try ! 实 验 装 置 图: 化学教学实验中心 Chem is try ! 实 验 流 程: 化学教学实验中心 Chem is try ! Mg粉 无水乙醚 引发反应 微沸20min 反应 ...
  • Presentazione di PowerPoint - Emodnet Chemistry

    Presentazione di PowerPoint - Emodnet Chemistry

    OGS + ISPRA. EMODnet Chemistry 3 TWG meeting, 4-5 April 2017 . The request. START: ... Proposal was presented and discussed at the last EMODnet Chemistry 2 plenary meeting. EMODnet Chemistry 3 TWG meeting, 4-5 April 2017 . Which ....
  • The Pew Oceans Commission - Kenyon College

    The Pew Oceans Commission - Kenyon College

    Simple models integrate different parameters to estimate rates of productivity Model components (Field et al. Science 281:237-240) chlorophyll concentration water depth in photic zone fraction of water column where photosynthesis is light-saturated surface temperature average primary productivity in the oceans...
  • PowerPoint on Deviance Chapter 1: Introduction

    PowerPoint on Deviance Chapter 1: Introduction

    Left realism. Friday, 19 October 2018. Left Realist's Square of Crime. Left Realism takes us beyond the offender and shows concern for victim patterns and formal and informal factors. They argue that crime can only be understood in terms of...
  • Columbia Machine Core Grinding - Computer Action Team

    Columbia Machine Core Grinding - Computer Action Team

    Columbia Machine Inc. Based in Vancouver, Washington Est. 1937 World leader and innovator of concrete product equipment Complete systems Project Description Concrete Block Making Core Bar Assembly Current Process for Core Manufacturing Laser Cutting Forming Welding Grinding Design Requirements Safe...
  • Poetry

    Poetry

    * * * Learning Intentions In today's lesson, we will... Study a Carol Anne Duffy poem 'Havisham'. Talk about THEME. Identify and explain poetic techniques. 'Havisham' Th
  • Stats 244.3

    Stats 244.3

    Experimental Design Statistical Theory is interested in The design of the data collection procedures. ... Example Suppose we are collecting data on Blood Pressure Height Weight Age Suppose we are interested in how Blood Pressure is influenced by the following...
  • Florida's Bathymetry - University of Florida

    Florida's Bathymetry - University of Florida

    Ejection trajectories of grains blasted into the air by rainsplash The Raindrop CTSV Raindrop Size and Effects Rain Splash Experiments Measuring Net Downslope Rainsplash Transport Creep General term for slow, downslope mass movement of material in response to gravity on...