Projects Intelligent Data Sets Project 3

Projects

Intelligent Data Sets Project • 3 year project ending December 31 2008 with a total budget of 2. 7 mill USD – Funded by Research Council of Norway (NRC) and participants • Participants – – • Operator Solution Providers Consultants Associations Collaborating associations and projects – Accelerating Deployment of ISO 15926 (ADI) and FIATECH (US initiatives)

Intelligent Data Sets Project Objective • The objective of the project is to – Develop a methodology for mapping existing proprietary data representations to/from an ISO 15926 representation to support data exchange and integration using “Intelligent Data Sets” – This provides data separated from presentations, which again allows assembly of data in new formats targeted at new work processes – To study how this support new collaborative work processes within and between organizations is a research topic at the Ui. S. Many different, view dependant descriptions - business - company - phase (lifecycle) - application (DS/2 D/3 D) - etc One neutral, extendable description, supporting multiple views across phases and applications

Examples Of Inconsistent Representations

Daily Challenges For Data Sheet Mapping • • In order to resolve this, a neutral, system independent representation that can map to any proprietary representation is required. Need to recognise which representation is used by which proprietary representation NORSOK B 37 14 Conn. Size/Type Proc. : 1/4"-18 NPT (F) Representation 1, Context 1 SHARECAT Connection design. Size Thread pitch M 45, M 46, M 47 : : : Representation 2, Context 2 ANSI/ASME B 1. 20. 1 1/4 - 18 NPT-F NPT 1/4” 18 thr/in

Context Of Codes I

Context Of Codes II Local Name T 5: T 5 here: www. informativos. telecinco. es t 5. no-thobben på nett Sony tilbakekaller Cyber-shot DSC-T 5 Volvo T 5 Class Name T 5 APPARATUS IEC 60079 -0 IIC: International Institute for Conservation of Historic and Artistic Works IIC here: GROUP IIC APPARATUS IEC 60079 -0 IP 66: EEx ia: IP 66 APPARATUS IEC 60529 EX IA APPARATUS IEC 60079 -11 Class Name

IDS • • Intelligent Data Sets Support mapping and exchange between proprietary data sheet formats using 15926 templates and RDL/ontology development for Oil & Gas Template development – Generic basic templates – Assembly into molecular templates – Represent complex data sheets using templates • Template application – – Implement template definitions as instantiation scripts in (e. g. ) SWRL Rules generate rich 15926 structures for standardized storage Common representation of data supports exchange Validation and quality checks on data

ADI • Accelerating Deployment of ISO 15926 (ADI) – Bechtel – Bentley – Fluor Daniel • The ADI project defines 15926 Part 7: Templates – Implementation methods for the integration of distributed systems – Develops SW for the RDS/WIP “inbox” • POSC Caesar provides – Methodology for Part 7 template specification, using First-order logic – Initial set of template definitions – Validation of templates using automated reasoning • 15926 Part 2 in OWL format • Longhand template definitions expressed as SWRL rules – Hosting ADI software to access POSC Caesar Reference Data System (RDS)

ADI Sponsors • • • • Aramco Services Company Atomic Energy Canada Ltd AVEVA Barton Consulting Bechtel Corporation Bentley Systems COADE Conoco. Phillips Consolidated Contractors Company DNV Dow Chemical Du. Pont Fluor Corporation Georgia Institute of Technology • • • Hatch Intergraph KBR National Institute of Standards & Technology (NIST) Noumenon Consulting NRX Global Onto. Consult POSC Caesar Association Procter & Gamble Software Innovation USPI VTT

Lessons Learned From Developing ISO 15926 (I) • Need a neutral representation, independent of – Application – System – Lifecycle stage • An integration model – Conceptual model • Needed to be concerned with “what things are” as opposed to their representation – Need for semantics • How things are related – Need for a rich ontology

Lessons Learned From Developing ISO 15926 (II) • The obvious choice for us was set theory and first order logic (FOL) • Later we ran into the problem “What is information about a class member as opposed to information about the class itself? ” Led to the identification of the need for Second Order Classes • • • – – All specifications used in the industry are by nature about class membership Developing a specification is adding constraints, i. e. defining subclasses – The classes had to be dealt with as object – We have later discovered that we also have Third Order Classes – Will probably later need even higher level classes Note that this is observations discovered from industrial needs. We were introduced to OWL in 2003, and decided to test this to see if this was the way forward We ran into lengthy discussions of OWL Full vs. DL – The current state of development indicates both, Full to support lifecycle data, DL for reasoning. POSC Caesar, which is a Norwegian based industry association, and one of the organisations behind ISO 15926 has become W 3 C member, and is participating in the establishment of a W 3 C O&G Incubator Group.

Lessons Learned From Developing ISO 15926 (III) • • • Most systems used in the industry are “proprietary” systems and will probably be in use for a long time to come They all use their internal representations, and will continue to do so Systems can be interfaced, but at a considerable cost. Resource restrictions. They have to be interfaced to new systems whenever project participants change If an ontology is not interfaced to existing systems it will only be useful for new developments, systems etc. , not for use with existing systems Tool support to map between standardised and proprietary representations. Templates (ISO 15926 -7) and IDS tools are means to achieve this An ontology will never be completed, a system must be in place to handle extensions Capability to handle lifecycle data Reasoning over data quality Interfacing the ISO 15926 ontology to existing systems and setting up a system to handle extensions is what the IDS project is about

Integrated Operations in the High North Project Outline May 2008

Main Objectives • The primary objective of the project is to develop: § § § • A demonstrated reliable digital platform for Integrated Operation Generation 2 (IO G 2) in the High North IO G 2 pilots within drilling, R&P, O&M in the High North Decision Support for drilling, R&P, O&M IO G 2 for the High North shall facilitate operations in remote and hazardous conditions, the use of limited operational personnel and “zero footprint” solutions

Project Architecture – Technical view Business processes Digital platform Unmanned Improved Sub-ice Drilling rig production operation Risk management for reliable information & IT Activity 4 Semantic oil and gas platform and information assurance Activity 3 Networks, infrastructure and web services Activity 2 Autonomous and failsafe subsea control systems Activity 1 Activity 5 Activity 6 Activity 7

Semantic Oil & Gas Platform Objectives: • To extend and improve the content and quality of the ISO 15926 based oil and gas ontology • To develop a prototype information validation service

Semantic Oil & Gas Platform Main deliverables: 1. Ontology building methodology from the IDS project adapted to the addressed domains 2. Extended and improved Oil & Gas ontology with § § Oil & Gas production ontology including relevant parts of PRODML, Daily Production Report and Monthly Production Report ISO 10303 -239 Product Life Cycle Support (PLCS) Operation & Maintenance ontology including relevant parts of IBM’s RSM, ISA 95 and ISA 88 and ISO 13375/Mimosa Drilling ontology 3. A prototype information validation service based on semantic web technology, IDS-templates and the oil & gas ontology

Committed Participants and Funding • Committed to join: § Statoil. Hydro, Norwegian Defence, IBM, DNV, National Oilwell Varco, Invenia, Computas, Epsis, Tieto. Enator, FMC, SAS Institute, Kongsberg, PSA Centre of Integrated Operations, IRIS, NTNU, Ui. O, Ui. S, POSC Caesar, OLF, Abelia and FSi § Representing a total committed funding of 70 MNOK (RCN 17 MNOK) • Project will start as described with activity 2, 3, 4, 5 and 7 • Activities 1 and 6 will start as soon as funding is secured • Start-up 2008 -05 -01 - Duration 4 years • Target total budget 90 MNOK