READI JIPWeb page analytics March 4th

2020

READI –REquirement Asset Digital lifecycle Information

Background

Strategy for the Norwegian oil and gas industry – realization of Konkraft recommendations

Digital transformation of business processes for field development and operation

We need a comon digital language and framework which enable efficient flow of information between disciplines and work processes

READI JIP- digital transformation of business processes

READI ObjectiveThe READI JIP project will facilitate the oil and gas industry to be transformed from inefficient and cost-driven working methods to the digitized world where requirements and documentation are accessible and processed by machines.

The background

Owners/operators, EPCI contractors and Suppliers spend a massive amount of expert manhours to specify, interpret, implement, and verify design and technical documentation vs. requirements, yet repeatedly resulting in significant quality deviations in project execution and operation

Our Solution

READI will establish a machine readable format for requirements specification and validation which require a shared standard for Design Data Model (Digital Twin) formulation. This enables computer-aided assurance of requirements’ consistency as well as the conformance of technical and LCI to Requirements, thereby reducing manhour cost, time duration, and eliminating quality deviations, giving large operational benefits.

UNLIKE current situation, with requirements written in free text and design and LCI is delivered as drawings and documents where it limits use in a digital twin, our product will improve automatic data sharing between systems and enable automation of key business processes with accuracy at a minimal cost and time expenditure.

Change is needed to enhanced safety, reduce cost, improved quality and reduce failures

Strengthen the competitive edge of the O&G industry

Position the Norwegian O&G industry as a global leader applying digital technology

Efficient exchange of information between appropriate IT platforms- and systems – enhance interoperability

Automation of work processes in engineering, procurement and operation

NCS = the Norwegian Continental Shelf.O&G = Oil & Gas

KonKraft: “Norwegian cluster should take a leading global position in development and use of digitalized solutions”

AIBEL MMD3: 5% cost reduction for bulk material ordered

amounts to > NOK 150 mill for a large project

6

Business cases points to significant benefits with digitalised requirements and documentation in E&P projects.

High level estimate for Norwegian Continental Shelf 1)

– broad implementation:

• Annual spending 2): NOK 72 billion• Annual savings from 3): up to 5 %• Annual savings from : NOK 4 billion

• Precise requirements and digital control of documentation

• Re-use of concepts and products• More effective and improved quality in

engineering and procurement work processes• Reduction of variants and avoiding duplication

1)Work lead by Equinor 2) Input from Rystad Energy 3) Input from Aibel

Cost savings and enhanced safety due to:

Management of requirements and information is lost along the asset’s life cycle

• Lack of precision• Requirements are to a large extent unprecise and give room for different

interpretations resulting in higher prices to compensate for increased delivery risks

• High complexity• Difficult to understand for which context the requirements are relevant and

applicable• There are lots of examples of contradictory and irrelevant requirements in

projects• To a large extent there exist divergent company specific requirement• Relations between requirements are complex, and hard for human beings

to understand

• Lack of automation• Standards/requirements are analogue and not accessible by computers• Verification of requirements is mainly done manually

• Lack of interoperability• Software solutions supporting requirements- and information management

processes are proprietary• Information sharing and exchange between different systems are costly

• Standardization is time consuming• Updating of standards requires update of entire standard documents. This

is time-consuming resulting in outdated requirements.

8 |

Our seamless value chain are broken proprietary solutions and unstructured information

Exploration Development Operation and maintenance

Marketing and sales

9 |

Cost savings by a common digital language are huge

Some digitalization examples?

How has the job changed?What are the enabling methods and tools?Which competency was required?

Digitalization changes work processes and creates new business opportunities

Ambitions and goals

13

READI value propositionThe journey from paper based to machine readable standards

The open industry platform READI translates diverse company practises into shared digital LCI and technical requirements, and helps the industry to improve safety, cut costs and increase efficiency in business critical processes through automation.

READI – governance of digital requirements in the oil and gas industry

Paper based standards Application for business process improvements

READI – Common industry vocabulary and digitalization method for machine readable requirements

READI JIP Industry applications

Company specific requirements

Updated and common requirements in a digital format

READI JIP- digital transformation of business processes

READI ObjectiveThe READI JIP project will facilitate the oil and gas industry to be transformed from inefficient and cost-driven working methods to the digitized world where requirements and documentation are accessible and processed by machines.

The background

Owners/operators, EPCI contractors and Suppliers spend a massive amount of expert manhours to specify, interpret, implement, and verify design and technical documentation vs. requirements, yet repeatedly resulting in significant quality deviations in project execution and operation

Our Solution

READI will establish a machine readable format for requirements specification and validation which require a shared standard for Design Data Model (Digital Twin) formulation. This enables computer-aided assurance of requirements’ consistency as well as the conformance of technical and LCI to Requirements, thereby reducing manhour cost, time duration, and eliminating quality deviations, giving large operational benefits.

UNLIKE current situation, with requirements written in free text and design and LCI is delivered as drawings and documents where it limits use in a digital twin, our product will improve automatic data sharing between systems and enable automation of key business processes with accuracy at a minimal cost and time expenditure.

In a world where READI never was…

Human language format is imprecise and inconsistent, allowing for contradictory information, preventing automated verification

The vision READI is pointing towards

Ontology is about semantics and formalism that enables computers to reason and analyze the Requirements data and Design data

17

The ambition: Significant cost saving through common digital requirements and automated verification

Transformation

RequirementDevelopment

Stakeholders needs and

expectations

Requirements

Tran

sfor

mat

ionVerification

confirmation, through the provision of objective evidence that specified requirements have been fulfilled.

Is the set of Requirements consistent?

ASSET MODEL

As-builtBaseline 1 Baseline 2 Baseline n

Is the system built right accordingto the Requirements?

Plans and deliverables

19

READI scope and main deliverables

Scope:• Z-001: Documentation for Operation (DFO) • Z-CR-002: Component Identification System• Z-DP-002: Coding System• Z-003: Technical Information Flow Requirements • Z-018: Supplier’s documentation of equipment CR = Common Requirements

DP= Design Principles

Transform LCI requirements to machine readable format

Agree common LCI requirements

Establish methodology and tools to enable automated reasoning

Establish framework and governance model for future management of digital

NORSOK requirements

20

The READI JIP is executed in phases

Phase 1: Building the platform for digitalisation at a larger scale –Proof of Concept based on concrete pilots; valves (general) and subsea system

Initiation Phase 1 Phase 2 Phase 3

Phase 2: Common DFO* requirements Complete methodology and platform for digitalisation of requirementsInternational collaboration

*Documents For Operation

Phase 3: Digitalisation of DFO and Supplier documentation requirements

Extensive use case for practical application of shared digital requirements

October 2019 2021June 2018

Some achievements Phase 1

Captured and structured more than 3100 documentation requirements for subsea and valves according to READI methodology.

Demonstrated that a >50% reduction in number of documentation requirements in DNV GL RP-O101 is achievable by application of the READI methodology .

Demonstrated automatic consistency checks of requirements by use of the READI methodology and tools. The tool also recommends how to resolve inconsistencies.

Established core methodology and working tool enabling creation and automatic processing of digital requirements..

Use case: Digitalisation of DNV GL RP O-101 and STI (valves)

○ Transformation of RP O-101 to digital format completed, including of building the ontologies (triplets) – only quality check remains

○ Decided to use RP O-101 as pilot case for demonstration of “proof of concept”

○ The decision to use IEC 81346 as reference standard for system/component classification delayed the process, but important inorder to meet overall ambitions related to automation and improved interoperability between current management/enterprise systems used by the industry.

ISO/IEC 81346

IEC 61355SCD

DNV GL RP O-101

Z-018/STIValves

• Definition and mapping of system/component classes supporting >3000 requirements

• The classes are defined according the principles in IEC 81346-Part 1/2

• Available at Excel format in READI Tool

• Definition and mapping of document classes supporting >3000 requirements

• The classes are defined according the principles in IEC 61355

• Available at Excel format in READI Tool

Subsea RDL for products Subsea RDL for documents

• > 3000 requirements transformed to SCD format

• Available at Excel format in READI Tool

• Original requirements available at human readable format

Subsea RP requirements

23

Overall execution plan Phase 2 and 3

Harmonized Z-001 acc. Tag-doc structure Classification of Z-001 and Z-018 requirements acc. RDS-O&G+++

Development of 81346-O&G, classification of info and common attributes/properties

Update digitalisation method and tool according to RDS-O&G

Digitalization of Z-001 and Z-018 acc. To ISO 15926-14

Subsea Complete

Phase 2 Phase 3

Methodology and tools; working methods and digitalisation methods

Specification of framework governance of digital requirements

*Drilling equipment, Equipment units and Technical Safety (partly)

OPTIONAL: Completion of STI deliverables*

Completion of STI Subsea

Main deliverables are standards, technology, services, training, communication and international collaboration

Global Standard Organisations like:

Global Industry initiatives like:

25

READI has global ambitions – bringing the digital platform to the O&G community

IOGP, JIP33, CFIHOS and PCA

ISO, IEC, NORSOK, ASME and API• Common, machine intelligible requirements

• RDLs (Common vocabularies)

• Methods and tools based on W3C

26

Current Participants

Category Company

Operators

Equinor

ConocoPhillips

Aker BP

Lundin

Shell

Vår Energi (Eni)

EPC Contractors

TechnipFMC

Aibel

Aker Solution

Category Company

Equipment and system vendors

ABB

ComputasProenco

AuthoritiesPetroleum Safety Authority

Ministry of Petr. and Energy

Others

Standard NorgeDNV GL Sector Board Petroleum

Observers

NOROGPOSC Caesar AssociationNorsk Industri

Technical framework

GovernanceManage and maintain RDS and Reference Data Libraries (RDLs)

Host validation serviceREADI: Specify framework

W3C standardsOWL 2, semantics, ontologies, logical

reasoning, HTML 5,

ISO/IEC 81346Functional naming and breakdown structure (own part for Oil & Gas)

Upper ontology, ISO 15926Part 14: Oil & Gas OWL vocabulary

(relations)

READI Vision• Automated digital verification of requirements and design in the oil and gas industry • Used globally, based on international standards and open source technology• Standardized breakdown of assets and identification of components in all project life cycles and operation across

facilities.

READI framework

Industry

Norsok Z-Ti harmonization and digitalization

Z-001, Z-DP-002, Z-CR-002, Z-003 (replaced) , Z-018

Digitalization methodology and tools

Requirement syntax (SCD), READI tool suite, reference data architecture and

INCOSE guidelines

Digital design basisOLGA, Hysys, Unisim integration through common

vocabulary (-14)

Piping commodity codesISO15926-14, TR2000 etc.

Applications and use cases

Standard RDLs and vocabularies ISO 14224 – Maintenance and reliability

IEC 61355 – Document designationsISO 15926 Part 4: Reference Data Library (not reasonable)

IOGP JIP 33/36ISO15926-14, RDS, .

DeepStar

Information model

Curr

ent s

cope

Ong

oing

dia

logu

eRE

ADI a

mbi

tion

Other

Conceptual information model - main building blocks

READI Information model

Main purpose‒Provide a basis for further planning and prioritization project activities,

and by that secure that READI will deliver scope and valuable solutions‒Help PM in planning and managing project activities

‒ Improve understanding of content and relations between the various elements of the model‒Create trust and ensure that that end users needs and expectations are

met.

The activity has just started. A conceptual information model is expected to be presented medio January 2020.

READI contact informationProject manager: Erik Østby, DNV GL

E-mail: Erik.Ostby@dnvgl.com

Mobile: +47 906 74 106

www.readi.com

Steering Committee Chair: Steinar Mollan, Equinor

E-mail: stem@equinor.no

Mobile: +47 974 19 251