LogisticHubA common knowledgebase for tracking information for the offshore supply chain

Dr. Thore LangelandManager Integrated Operations Norwegian Oil and GasEmail address: tla@norog.noMobile: +47-9095 1756

Agenda

1. RFID in Norwegian Oil and Gas

2. Guideline No. 112 “Deployment of RFID in oil and gas industry” Overview - 9 parts Part 4 Unique identification number Part 2 Architecture and Integration

3. LogisticHub   Logistics in the offshore industry Automatic identification and data capture (AIDC) Requirements specification

4. Summing up

2

RFID in Norwegian Oil and Gas

- how did it start?

3

RFID in Norwegian Oil and Gas

YESYES NoNo

RFID

OIL & GAS RFID

Oil &Gas

1. The RFID solutions should be adapted to oil and gas industry and not to the RFID world

Enterprise Service Bus

Services integration

Communication and Information Security

Enterprise Service Bus

Services integration

Communication and Information Security

DCS, PLC &Historians

RotatingEquipmentMonitoring

FacilityMonitoringand MES

EngineeringSystems

Maintenance& AssetManagement

Equipment andProcessDocumentation

DCS, PLC &HistoriansDCS, PLC &Historians

RotatingEquipmentMonitoring

RotatingEquipmentMonitoring

FacilityMonitoringand MES

FacilityMonitoringand MES

EngineeringSystemsEngineeringSystems

Maintenance& AssetManagement

Maintenance& AssetManagement

Equipment andProcessDocumentation

Equipment andProcessDocumentation

PROCESS CONTROLDOMAIN

ENTERPRISEDOMAIN

NEWUPSTREAM

APPLICATIONS

EXISTINGAPPLICATIONS

&INFORMATIONREPOSITORIES

Drilling and Completion

Reservoir and Production

Management

Operations and Maintenance

Enterprise’Drilling and Completion

Reservoir and Production

Management

Operations and Maintenance

Enterprise’

Oil & Gas

Ontology

2. The RFID solutions should be adapted to Norwegian OIL and Gas’ Reference IT architecture for Integrated Operations Generation 2

https://www.posccaesar.org/svn/pub/LogisticHub/

Two initial requirements in 2007:

4

Norwegian Oil and Gas’ Information Strategy

Vendor

Vendor

Smarter data

Field data Health, safety,

environment Seismic Drilling &

Completion Reservoir &

production Operations &

maintenance Logistics Transportation

Common XML schemas

Smarter solutions

Operator

Web portalsWeb services

Semantic Web Infrastructure for web services Oil & Gas Ontology1)

(Based on ISO 15926)

An efficient pipeline for real-time data transferal and analysis

1)Ontology = A hierarchical data structure containing concepts, relationships, properties and rules for a specific domain

66

An Oil and Gas Ontology based on ISO 15926

Ontology activities initiated by Norwegian Oil and Gas:Business integrated planning

• Range 5+ yearsHSSE

• Yearly environment reporting (EnvironmentalWeb)

Drilling • Daily drilling report• Drill pipes (operation and

maintenance)

Supply chain• EqHub – standard

equipment• LogisticHub – CCU tracking

Production• Daily production report• Monthly production report• Production optimization

Operations and maintenance• Based on Purdue Enterprise

Reference Architecture (PERA)

http://www.posccaesar.com/ 7

8

E&P Information Management Association (EPIM) EqHub – quality standard equipment

information (standardized according to ISO 15926)

EPIM ReportingHub (ERH) – standardized drilling and production reports (ISO 15926 compliant RDF triplestore)

EPIM LogisticHub ????

8

EPIM is the instrument for the operators on the NCS to secure efficient information sharing among all relevant stakeholders by providing cost effective and user friendly common digital solutions based on international standards.

Services today:License2Share (L2S) – is a collaboration tool, a repository for all licensees on the NCS containing all documents shared in a license with the partners and authorities, and has more than 6 000 users

EnvironmentWeb (EW) – yearly reports of emissions and discharges from operators to authorities (ISO 15926 compliant)

Norwegian Oil and Gas

Guideline No. 112 “Deployment of RFID in oil and gas industry”

http://www.norskoljeoggass.no/no/Publikasjoner/Retningslinjer/Integrerte-operasjonerIntegrated-operations/112/

Dr. Ovidiu Vermesan SINTEF

Part 1-9, 2007/9

Dr. Tore R. Christiansen PCA

Dr. Geir ØvsttunDNV

Revised Part 4, 2011 Revised Part 2, 2012

9

Guideline No. 112 Deployment of RFID in oil and gas

Deployment of RFID in oil and gas for the domains:

Personnel Containers Drill strings Fixed and mobile

equipment

The guideline is based onISO standards.

The Guideline No. 112 is available at: http://www.norskoljeoggass.no/no/Publikasjoner/

Retningslinjer/Integrerte-operasjonerIntegrated-operations/112/

10

Core elements of RFID deployment

Global Unique Identification (GUID): ISO/IEC 15459

11

Guideline No. 112, Part 2 Architecture and Integration

12

Guideline No. 112, Part 2 Architecture and Integration

13

The Purdue Enterprise Reference Architecture (PERA)

Guideline No. 112, Part 2 Architecture and Integration

Reference data and ontologies

LogisticHub

Common knowledgebase of

tracking information for

the Norwegian offshore industry

15

Logistics in the offshore industry

16

Logistics on the NCS – An overview 2012

Cargo & PassengerSupply ships

Cargo Carrying Units• Equipment

Helicopter People (POB) Equipment

Tanker Oil

Licensees 500+ Active Production Licensees 80+ Fields in production 10+ Active Transport Licensees

37 Operators 12 operators with production 1 operator of pipelines 6 operators with PDO (no prod.) 18 operators with only exploration

Suppliers of products and services

Rig suppliers

Service companies

O&M contractors

Transport suppliers

Offshore supply bases Kirkenesbase, KirkenesPolarbase, HammerfestNorbase, HarstadHelgelandsbase, SannessjøenVestbase, KristiansundKistiandsundbase, KristiansundFjordbase, FlorøMongstadbase, LindåsCoast Center Base, SotraStordbase, StordNorsea base, Tananger, SOLANorsea base, Dusavika, Stavanger

Tracking using RFID?

The supply chain as seen from the operator

18

A LogisticHub may provide information to alloperators and suppliers

Supplier InstallationTransportCCU owner TransportTransport

CCU back to the owner

LogisticHub

???

Supply base/Operator

19

The CCU:

WhoWhatWhereWhenWhy

+ documents / info.

Automatic Identification and Data Capture (AIDC)

A typical layout of a supply baseA supply base is typically divided into zones where different business process events takes place :Arriving (with lorry)Inspecting HoldingUnloading (Accepting)Unpacking (Receiving)Packing (Picking)Staging_outbound (ISPS)Loading DepartingArriving (with ship)Unloading (Accepting)Unpacking (Receiving)Packing (Picking)Staging_outbound (Lorry)Loading Departing 21

Tracking CCU at supply base

22

The CCU going offshoreThe CCU returning from offshore

23

Identec Solutionsi-Q350X FL

RFID Tag

HandheldRFID reader

Identec Solutionsi-Roc 62x

Cargo Carrying

Unit (CCU)

OnshoreGate/

Portable

Onshore Forklift

truckOnshorecranes

Offshorecranes

OffshoreGate/

Portable

RFID reader& antenna

Identec Solutions GA – Main Cabinet Model Arial Oy Av2091

Identec Solutions 2-WAY Main Cabinet 10dB Yagi antenna

RFID reader& antenna Tracking package

available

Identec Solutions Price dependent on the offshore crane~ NOK ?????

Identec Solutions Atex approved andavailable in 2013~ NOK ????

HandheldRFID reader

Identec Solutions D EN i-PORT M350

2 v1.11 FLaird, S8655P

RFID reader& antenna

Garmin GPS 16 17

PC LXE VX9

Identec SolutionsForklift truck package

Tracking package available similar tothe forklift truck

Identec Solutions

Identec Solutions Scalable up to

Server/client andsoftware package

per site

Automatic Identification and Data Capture (AIDC) technology

Forklift truck plays an important role at onshore locations

24But how to achieve AIDC?

LogisticHub Requirements Specifications

ReportingHub – A schematic overview

NPD Fact Pages

PCARDS

The Brønnøy-sund Registers

GS1GLN Register

Master dataRegularly updatingof master data

OwnerIDTypeCertificateHirerPeriod

CCU Owners

XML schemas

XM

L sc

hem

a(q

uer

y)

CCU Owner

location

Appl.

RFID TagEvent

RFIDReader

UpdatingEvent

XML schemas(response)

Docum

enta

tion

acce

ssib

le

Supply Chain

Supplybase

location 26

Rig ownerlocation

Transportpositions

Appl.

RFIDReader

RFID TagEvent

UpdatingEvent

Supplierlocation

Appl.

UpdatingEvent

RFID TagEvent

RFIDReader

Operatorlocations

Appl.

RFID TagEvent

RFIDReader

UpdatingEvent

Master data – how to get and maintain them

CCU owners sites Only at supply bases?

Operators’ offshore sites Platforms Drilling rigs Accommodation rigs Other?

Operators’ onshore sites Only at supply bases?

Supply bases Managing all activity offshore?

Suppliers sites More simple AIDC technology

must be available

27

LogisticHub’s potential users

28

Access to LogisticHub CCU owner has access to all events generated by

her/his CCUs where there are change of custody (loading/unloading) and events of the CCU on the way to her/his custody (loading and departing previous site)

The hirer has access to all events generated by her/his hired CCUs

The operator has access to all events generated by CCUs in her/his custody and events of the CCU on the way to her/his custody (loading and departing previous site)

The supply base owner has access to all events generated by CCUs in her/his custody and events of the CCU on the way to her/his custody (loading and departing previous site)

29

30

LogisticHub will communicate with probably 300+ organizations

Data flow in LogisticHub

3. Decision

User

Query

1. Receiving XML file

2. Validating

4. Returning with error message

ResendCorrectReceiv

e

Brønnøysund RegisterGS1 GLN RegisterNPD Fact PagesPCA RDS

7. Storing as RDF triples

5. New event data

6. Storing as XML file

9. Generating RDF report

12. Regular statistical reporting

11. Sending 10. Transforming to XML file and validating

User

Response

13. RH website

8. Querying reporting

31

Tracking of a CCU in the supply chain

The communication between LogisticHub and the users of this service defines:

Who - organization creating the event

What - the CCU (& content phase II)

Where - location of the CCU

When - timestamp yyyy.mm.dd.hh.mm.ss

Why - to some degree the business reason

32

A typical sequence of events at a supplier location

Arriving

Inspecting

Unloading

Internal_moving

(Packing)

Loading

Departing

33

Phase I of LogisticHub project has focus on the following business process events:

Arriving

34

Response

tag_id

org_no

GLN_location/NPDID_location

arriving

date_time

Query

tag_id

org_no

GLN_location/NPDID_location

arriving

date_time

Inspecting

35

Responsetag_idorg_noGLN_location/NPDID_locationinspectingdate_timeweighttemploc_latloc_longdangerous_goodsdoc_dangerous_goodsccu_classccu_sub_subclassccu_owner_prod_typeccu_owner_idccu_manufacture_datepayloadtaramax_gross_weightlengthwithheighttag_installation_datebattery_statuscertificate_numbercertificate_exp_datecertificate_docCCU_docsuppl_securitytrans_security 1)

Query

tag_idorg_noGLN_location/NPDID_locationinspectingdate_timeloc_latloc_long

Loading

36

Response 1tag_idorg_noGLN_location/NPDID_locationloadingdate_timeweighttemploc_latloc_longtrans_org_noTrans_GLN_legalns_org_nons_GLN_location/NPDID_locationexp_arriv_timefinal_destination

Query

tag_idorg_noGLN_location/NPDID_locationloadingdate_timeweighttemploc_latloc_longtrans_org_noTrans_GLN_legalns_org_nons_GLN_location/NPDID_locationexp_arriv_timefinal_destination

LogisticHub’s conceptual and generic data model

37

Conceptual data model Generic data model

LogisticHub’s event model

38

Guideline No. 112, Part 2 Architecture and Integration

39

The semantic technology stack ISO 15926

LogisticHub as RDF store (triplestore) - Advantages

Easy to merge data and/or add new data

Put meaning to data so they can be used outside the context

Can do reasoning

Can build one knowledgebase at a time and query all of them as one database

Easy to transfer data between databases, without loss of information

41

RDL

Concepts&

relationship

ISO 15926Part 2

ISO 15926Part 8

ISO 15926Part 7

Standardizedclassification

NPD Fact Pages

Convert to ISO 15926 Part 8 (RDF)

Brønnøysund Reg.

Convert to ISO 15926 Part 8 (RDF)

GS1 GLN

Convert to ISO 15926 Part 8 (RDF)

LogisticHub’s master data and standard ontologies

Reports/statistics and queries

Reports Daily Monthly Yearly

Content Movement / Lifting Onhold Damaged Onshore/Offshore North Sea Norwegian Sea Barents Sea

Queries Queries related business process events Find the CCU’s last movement and location Number of CCUs on location and where they are

42

LogisticHub – Costs and benefits

Costs RFID tags on CCUS

AIDC technology on sites/locations

Interconnecting internal software

Benefits Improved work processes

Improved document management

Not leaving CCUs behind at supply base

Deliver CCUs to the right place first time

Improved management of hired equipment

Improved management of the CCUs

Reduced time for searching

Sharing of information improves interfaces and planning

Improve control of in- and out freight goods

Might be used as an operation system and as archive 43

Possible schedule LogisticHub

Request For Information (RFI) 07.11.12 -20.12.12

Recommendation of the RFI sent to EPIM 21.12.12

Business case for LogisticHub to be approved by EPIM’s Board and General Assembly

RFP process initiated in early spring 2013?

LogisticHub available for testing in late fall 2013?

44

Summing up LogisticHub LogisticHub – a RDF triplestore

that communicate with the users through a Web service based on query and response (XML schemas)

Master data – automatic updates

CCU owners provides information about the CCUs before sent to the hirer

The hirer has to supply necessary documentation

The users have to installed tracking solutions at their sites

6 different types users - CCU owner, supplier, transporter, supply base, rig owner and operator 45