1. Joint MIMOSA/Fiatech Industry Standard Datasheet Definitions Workshop Houston, Texas August 4-5, 2015

2. Industry Standard Datasheet Definitions (ISDD) Workshop Objectives
Establish mutual understanding of Business Problem and Proposed Solution
Review and agree on project scope
Review and agree on project methodology
Review and agree on project deliverables
Agree on preliminary project phasing
Initiate POC Phase of Project
Agree on POC Deliverables and Schedule
Establish Participation and Sponsorship

3. ISDD Project Overview Business Problem and Background Purpose
Proposed Deliverables
Scope and Phases

4. Business Problem
It is “intuitively obvious” that most asset intensive organizations are managing life-cycle asset information in a sub-optimal manner
Critical Infrastructure Management requirements are different from basic e-Commerce (consequences of failure, risk management)
Large amounts of asset related data which will be used and re-used are handed over and managed as unstructured, non-machine interpretable documents
Asset data is manually transcribed multiple times during the capital project, handover and O&M phases of capital facilities
Asset data and systems are “integrated” using methods that are fragile and inflexible
Asset data is trapped in many organizational silos and proprietary products

5. ISDD Project Background
OGI Pilot Required Deliverables
2D P&ID Schema
Breakdown Structures
Tags (Functional Location and Asset)
Properties (as Datasheets) – Not easy for anyone to provide
Documents – Structures Exist in MIMOSA CCOM
Gap analysis
Discussions about ISDD were started at Semantic Days 2013
Joint Fiatech/MIMOSA/PCA RDL Improvement Workshops
BP POC – Presented at 2015 Fiatech Technology Showcase

6. BP POC as Presented at Fiatech Technology Showcase 04/15/2015

7. Proposed Solution
In order to leverage information to gain value we must
Make the costs and risks obvious (Business Value Model)
Provide a rational alternative (The ISDDs)
Which is easy to understand, adopt and use
Where the investment costs can be shared and recovered quickly
Which is based on existing specifications and standards as well as known methods
Which is available as standards which can be shared by the industry

8. Automation and Control Systems
Critical Intersection for a Supplier Neutral Ecosystem Enabling Multi-domain Systems Interoperability
Enterprise Business Systems
Big Data and Analytics
Supplier Neutral
Open Specifications
LIFE CYCLE ENGINEERING
Systems
Automation and Control Systems
At the infrastructure level, most of the problems are common in upstream, downstream and midstream as well as on a cross industry basis.
ISDDs Provide Basis
For Datasheet Oriented
Information Exchange

9. The Role of Standards in Sustainable Enterprise Solutions
Standards help rationalize chaos into widely accepted good practices
NGO Standards Organizations such as ISO and IEC
Industry Standards Organizations – API, ISA, OPC, MIMOSA, PCA, USPI
Practice Standards – Focus on what should be done
Such as PAS 55 and ISO define good asset management practices to be followed
CFIHOS - Working to define good handover practices
Individual IT/IM Oriented Standards – Focus on IT/IM aspects of how
Such as ISO 15926, OPC, ISA 95/88, ISO and MIMOSA
Enable SoS to properly support good practices defined in Practice Standards

10. WG 6 – Oil and Gas Interoperability
There are multiple standards from multiple committees and industry standards groups being incorporated into the OGI Pilot and the OGI TS. This slide shows some of the ones tied closely to ISO.

11. OGI Pilot Business Use Cases Roadmap - Part 1
Enterprise Standards and
Project Execution Template
for all projects
Enterprise Capital Project Data Management Standards
Plan / Program / Contract
Engineer / Design
Procure
Fabricate / Construct
Complete / Commission / Startup
Operate / Maintain
Decommission
/ Dispose
Continuous Handover (Structured Digital Assets, Tags, Docs)
Establishing an Environment for Lifecycle System of Systems Interoperability
Sustained Lifecycle Digital Asset Management
OGI Use Case 1: Capital project handovers to O&M
OGI Use Case 4: Enterprise Product Data Library Management
OGI Use Case 10: Automated provisioning of O&M systems
OGI Use Case 11: Enterprise Reference Data Library (RDL) Management
Levy contractual requirements
on suppliers at start of
specific projects
USPI CFIHOS Collaboration

12. Standardized Use Case Structure
Background
Scope
Preconditions
Successful End Condition
Actors
Triggers
Process Workflow
Scenarios
Scenario
Actors
Data Content
Data Formats
Reference Data
Information Service Bus Configuration

13. Pre-populate datasheets from previous phases (e.g. design basis)
Develop project specific engineering terminology and map to industry RDLs
Send completed datasheets to vendors with provision for their reply; receive, load, verify and compare vendor offerings
Select project specific templates from ISDDs for structured data entry by engineers
Matchup requirements against product datasheets from equipment suppliers
Plan / Program / Contract
Engineer / Design
Procure
Fabricate / Construct
Complete / Commission / Start-up
Operate / Maintain
Decommission / Dispose
Handover machine-interpretable datasheets for immediate loading into engineering master data system to compare against the physical asset and configuring O&M systems
Determine project % completeness by analyzing filled in datasheet properties required by equipment type for each phase
Pre-populate datasheets from previous phases (e.g. design basis)
as engineers choose equipment to design

14. Energistics PRODML/WITSML
Open Industrial Interoperability Ecosystem Key Standard Information Models
ISO 15926
Reference data and capital project artefacts
MIMOSA CCOM
Lifecycle engineering configuration, condition, work and reliability management
OPC Classic/UA
Real-time and historical time series data, alarms and events
Energistics PRODML/WITSML
Production and well data
MESA B2MML
Production schedules, forecasts, demand
We’re using standard information models for the representation of data payloads and service inputs and outputs. So we’re not specifying the use of proprietary models and we’re only using formats that have been published by standards bodies. There are inevitably some applications that only have an output using a proprietary model, and in these cases we map those to a corresponding standard format and document the transformation rules. But ideally we’d like the owner/operators to collectively persuade vendors to adopt the standardized models.

15. Microsoft ESB (Terawe), IBM ISBM, Assetricity SimpleISBM AVEVA P&ID
Reference Environment
Execution Environment
AVEVA P&ID
ISO 15926
Proteus
Maintenance Management System
Bentley OpenPlant PowerPID
ISO 15926
Part 8 OWL
MIMOSA
CCOM
Intergraph SmartPlant P&ID
ISO 15926
Proteus
Rockwell PlantPAx
UniSA
Transform Engine
Assetricity IOM-OG Register
Aspen Basic Engineering
MIMOSA
CCOM
ISO 15926
Eng. XML
MIMOSA
CCOM
IBM IIC
Sharecat/ EqHub
Data Sheet information
Datasheet information
MIMOSA
CCOM
ISO 15926
Vendor XML
OPC UA
ISO Reference Data
OSIsoft PI
IEC 61360
ISO (API 610)
MIMOSA CCOM
ISA TR20
ISO 14224

16. ISDD Project Purpose
Provide a practical, standardized way to build, maintain, exchange and use datasheet related information, based on existing Industry Standard Datasheets.

17. ISDD Project Proposed Deliverables
Business Value Model
Activity based
Cover full asset life-cycle
In cooperation with Owner/Operators, Suppliers and Academia
Sets of Industry Standard Datasheet Definitions
Included Industry Standard Datasheets prioritized by industry
In collaboration with publishers of original Industry Standard Datasheets
Breadth and depth of properties determined by life-cycle requirements

18. ISDD Project Scope and Phases
Scope: Coverage of all high priority Industry Standard Datasheets, as determined by project sponsors
Phases
Each Phase is expected to last 3-4 months
Each phase will build and publish a set of ISDDs
We project a POC Phase plus 3 to 4 main phases
POC Phase
Business Value Model
Approximately 3 Prototypical ISDDs
Objective of preliminary progress report at Fiatech Leadership Forum –Sep 21-23

19. Industry Standard Data Sheets
Currently have identified 263 potential sources to start with
API
15 (+20 ISO equivalents)
ASME
2 (+1 ISO equivalent)
IEC 10
ISA
166
ISO 28
NORSOK 31
PIP 11

20. API 610 Centrifugal Pump Data Sheet Elements Needed by Category As Determined by Plant Maintenance, Operations and Reliability Engineers
Category Number of Elements
Category Number of Elements
Data Sheet Header 10
Pump Materials 4
Drive and Power Train 6
Pump Bearings 10
Liquid Characteristics 6
Base Plate Information 14
Service Conditions 6
Seal Plans 2
Notes on Pump Design 6
Heating and Cooling 8
Pump Performance 14
Manifold Piping 4
Pump Physical Orientation 22
Painting Spec’s 8
Pump Casing 2
Maintenance Prep. 4
Case Pressure Limits 6
Safety Limits 25
Rotor Information 3
Manufacturing Tests 10
Coupling Information 8
Welding PMI Inspections 25
Notes on Rotating Elements 6
As Built Field Tests 31
Red Operations
Green Maintenance
Total Data Sheet Elements needed per 240 per Pump out of approximately 600 in API 610

21. BUILD Process ISDD BUILD Discipline Engineers Information Engineers
EXISTING INDUSTRY STANDARD DATA SHEETS (ISD)
SUBJECT MATTER EXPERTS
API
BUILD
Process
</>
XML
CCOM
ASME
CCOM
ISA
IEC 61360
PIP
INDUSTRY STANDARD DATA SHEET DEFINITIONS (ISDD)
IEC CDD
PCA RDL
SV RDL
USPI RDL
INDUSTRY REFERENCE DATA LIBRARIES

22. An Industry Rosetta Stone
ISDD
USE
An Industry Rosetta Stone
INDUSTRY STANDARD DATA SHEETS
API
ASME
ISA
NORSOK
PIP
Map Elements
ISDDs
EPCs
Map Elements
Owner/
Operators
Map Elements
Capital
Equipment
Suppliers
IEC CDD
PCA RDL
SV RDL
USPI RDL
INDUSTRY REFERENCE DATA LIBRARIES

23. OIIE and OGI Pilot To Be Featured At Future Events
Close
OIIE and OGI Pilot To Be Featured At Future Events
Solutions 2.0 – August 3-7, 2015, Westin Galleria, Houston, TX
All OIIE and OGI Pilot Working Documents are available at
Alan T. Johnston
MIMOSA