1. LogisticHub
A common knowledgebase for tracking information for the offshore supply chain
Dr. Thore Langeland Manager Integrated Operations
Norwegian Oil and Gas address:
Mobile:

2. Agenda RFID in Norwegian Oil and Gas
Guideline No. 112 “Deployment of RFID in oil and gas industry”
Overview - 9 parts
Part 4 Unique identification number
Part 2 Architecture and Integration
LogisticHub  
Logistics in the offshore industry
Automatic identification and data capture (AIDC)
Requirements specification
Summing up

3. RFID in Norwegian Oil and Gas - how did it start?3

4. RFID in Norwegian Oil and Gas
Two initial requirements in 2007:
YES No
RFID
OIL & GAS
Oil &Gas
The RFID solutions should be adapted to oil and gas industry and not to the RFID world
The RFID solutions should be adapted to Norwegian OIL and Gas’ Reference IT architecture for Integrated Operations Generation 2

5. Norwegian Oil and Gas’ Information Strategy
An efficient pipeline for real-time data transferal and analysis
Smarter solutions
Vendor
Web portals
Web services
Field data
Health, safety, environment
Seismic
Drilling & Completion
Reservoir & production
Operations & maintenance
Logistics
Transportation
Operator
Common XML schemas
Vendor
Semantic Web
Infrastructure for web services
Oil & Gas Ontology1) (Based on ISO 15926)
Smarter data
1)Ontology = A hierarchical data structure containing concepts, relationships, properties and rules for a specific domain

6. An Oil and Gas Ontology based on ISO 15926
Ontology activities initiated by Norwegian Oil and Gas:
Business integrated planning
Range 5+ years
HSSE
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) 6 6

7. 7

8. E&P Information Management Association (EPIM)
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 users
EnvironmentWeb (EW) – yearly reports of emissions and discharges from operators to authorities (ISO compliant)
EqHub – quality standard equipment information (standardized according to ISO 15926)
EPIM ReportingHub (ERH) – standardized drilling and production reports (ISO compliant RDF triplestore)
EPIM LogisticHub ???? 8

9. Norwegian Oil and Gas Guideline No
Norwegian Oil and Gas Guideline No “Deployment of RFID in oil and gas industry”
Part 1-9, 2007/9
Revised Part 4, 2011
Revised Part 2, 2012
Dr. Ovidiu Vermesan
SINTEF
Dr. Geir Øvsttun
DNV
Dr. Tore R. Christiansen
PCA 9

10. Guideline No. 112 Deployment of RFID in oil and gas
and gas for the domains:
Personnel
Containers
Drill strings
Fixed and mobile equipment
The guideline is based on
ISO standards.
The Guideline No. 112 is available at: 10

11. Core elements of RFID deployment
Global Unique Identification (GUID):
ISO/IEC 15459 11

12. Guideline No. 112, Part 2 Architecture and Integration

13. Guideline No. 112, Part 2 Architecture and Integration
The Purdue Enterprise Reference Architecture (PERA) 13

14. Guideline No. 112, Part 2 Architecture and Integration
Reference data and ontologies

15. LogisticHub Common knowledgebase of tracking information for the Norwegian offshore industry
1515

16. Logistics in the offshore industry
1616

17. Logistics on the NCS – An overview 2012
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
Tracking using RFID?
Offshore supply bases
Kirkenesbase, Kirkenes
Polarbase, Hammerfest
Norbase, Harstad
Helgelandsbase, Sannessjøen
Vestbase, Kristiansund
Kistiandsundbase, Kristiansund
Fjordbase, Florø
Mongstadbase, Lindås
Coast Center Base, Sotra
Stordbase, Stord
Norsea base, Tananger, SOLA
Norsea base, Dusavika, Stavanger
Cargo & Passenger
Supply ships
Cargo Carrying Units
Equipment
Helicopter
People (POB)
Tanker
Oil

18. The supply chain as seen from the operator

19. A LogisticHub may provide information to all operators and suppliers
The CCU:
Who
What
Where
When
Why
+ documents / info.
LogisticHub ? ? ?
CCU
owner
Transport
Supplier
Transport
Supply base/Operator
Transport
Installation
CCU back to the owner

20. Automatic Identification and Data Capture (AIDC)

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

22. Tracking CCU at supply base
The CCU returning from offshore
The CCU going offshore

23. Forklift truck package
Automatic Identification and Data Capture (AIDC) technology
Cargo
Carrying
Unit (CCU)
Onshore
Gate/
Portable
Forklift
truck
cranes
Offshore
Identec Solutions
D EN i-PORT M350
2 v1.11 F
Laird, S8655P
RFID reader
& antenna
Garmin GPS 16 17
PC LXE VX9
Forklift truck package
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 similar to
the forklift truck
Identec Solutions
Tracking package
available
Identec Solutions
Price dependent on
the offshore crane
~ NOK ?????
Identec Solutions
i-Q350X FL
RFID Tag
Identec Solutions
Scalable up to
Server/client and
software package
per site
Identec Solutions
Atex approved and
available in 2013
~ NOK ????
Handheld
RFID reader
Handheld
RFID reader
Identec Solutions
i-Roc 62x

24. Forklift truck plays an important role at onshore locations
But how to achieve AIDC?

25. LogisticHub Requirements Specifications

26. ReportingHub – A schematic overview
NPD Fact
Pages
PCA
RDS
The Brønnøy-
sund Registers
GS1
GLN
Register
Master data
Regularly updating
of master data
Owner ID
Type
Certificate
Hirer
Period
CCU Owners
XML schemas
XML schemas
(response)
Operator
locations
Appl.
RFID Tag
Event
RFID Reader
Updating
Dangerous
CCU
Ordinary
Norwegian Oil & Gas sealed CCU
NORSOK
Z015 Units
Documentation
accessible
Supply Chain
Supplier
location
Appl.
Updating
Event
RFID Tag
RFID Reader
Transport
positions
Appl.
RFID Reader
RFID Tag
Event
Updating
Appl.
RFID Reader
RFID Tag
Event
Updating
Supply
base
location
Appl.
RFID Reader
RFID Tag
Event
Updating
Rig owner
location
XML schema
(query)
CCU
Owner
location
Appl.
RFID Tag
Event
RFID Reader
Updating

27. 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
Supply bases
Managing all activity offshore?
Suppliers sites
More simple AIDC technology must be available

28. LogisticHub’s potential users

29. 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)

30. LogisticHub will communicate with probably 300+ organizations

31. Data flow in LogisticHub
13. RH website
12. Regular statistical reporting
11. Sending
10. Transforming
to XML file and
validating
User
Response
9. Generating
RDF report
7. Storing as RDF triples
5. New event data
6. Storing as XML file
8. Querying reporting
User
Query
1. Receiving
XML file
2. Validating
3. Decision
Brønnøysund Register
GS1 GLN Register
NPD Fact Pages
PCA RDS
4. Returning with
error message
Resend
Correct
Receive

32. 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

33. A typical sequence of events at a supplier location
Phase I of LogisticHub project has focus on the following business process events:
Arriving
Inspecting
Unloading
Internal_moving
(Packing)
Loading
Departing

34. Arriving Query Response tag_id tag_id org_no org_no
GLN_location/NPDID_location
arriving
date_time
Response
tag_id
org_no
GLN_location/NPDID_location
arriving
date_time

35. Inspecting Response Query tag_id org_no GLN_location/NPDID_location
date_time
weight
temp
loc_lat
loc_long
dangerous_goods
doc_dangerous_goods
ccu_class
ccu_sub_subclass
ccu_owner_prod_type
ccu_owner_id
ccu_manufacture_date
payload
tara
max_gross_weight
length
with
height
tag_installation_date
battery_status
certificate_number
certificate_exp_date
certificate_doc
CCU_doc
suppl_security
trans_security 1)
Query
tag_id
org_no
GLN_location/NPDID_location
inspecting
date_time
loc_lat
loc_long

36. Loading Response 1 Query tag_id org_no GLN_location/NPDID_location
date_time
weight
temp
loc_lat
loc_long
trans_org_no
Trans_GLN_legal
ns_org_no
ns_GLN_location/NPDID_location
exp_arriv_time
final_destination
Response 1
tag_id
org_no
GLN_location/NPDID_location
loading
date_time
weight
temp
loc_lat
loc_long
trans_org_no
Trans_GLN_legal
ns_org_no
ns_GLN_location/NPDID_location
exp_arriv_time
final_destination

37. LogisticHub’s conceptual and generic data model
Conceptual data model
Generic data model

38. LogisticHub’s event model

39. Guideline No. 112, Part 2 Architecture and Integration
The semantic technology stack
ISO 15926 39

40. 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
Fint om du også kan si noe om inn- og utgangsdata til triplestore i
figuren nedenfor eller i RFI-en.  Gjerne noe om fordeler og ulemper
med en slik løsning.
Early but mainstream
Put meaning to data so they can be used outside the context
Can build one knowledgebase at a time and query all of the as one database

41. LogisticHub’s master data and standard ontologies
ISO 15926
Part 2
ISO 15926
Part 8
NPD Fact Pages
Convert to ISO Part 8 (RDF)
ISO 15926
Part 7
RDL
Concepts
&
relationship
Brønnøysund Reg.
Convert to ISO Part 8 (RDF)
Standardized
classification
GS1 GLN
Convert to ISO Part 8 (RDF)

42. Reports/statistics and queries
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

43. LogisticHub – Costs and benefits
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

44. Possible schedule LogisticHub
Request For Information (RFI)
Recommendation of the RFI sent to EPIM
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?

45. 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