LogisticHub
A common knowledgebase for tracking
information for the offshore supply chain
Dr. Thore Langeland
Manager Integrated Operations
Norwegian Oil and Gas
Email address: tla@norog.no
Mobile: +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
Two initial requirements in 2007:
OIL & GAS
RFID
YES
1. The RFID solutions should
be adapted to oil and gas
industry and not to the RFID
world
2. The RFID solutions should be
adapted to Norwegian OIL and
Gas’ Reference IT architecture
for Integrated Operations
Generation 2
Oil &Gas
RFID
Reservoir and
Production
Management
Drilling and
Completion
No
Operations and
Maintenance
Enterprise’
NEW
UPSTREAM
APPLICATIONS
Enterprise Service Bus
DCS, PLC &
Historians
Services integration
Oil & Gas
Communication and Information Security
Ontology
Rotating
Equipment
Monitoring
Facility
Monitoring
and MES
Engineering
Systems
Maintenance
& Asset
Management
https://www.posccaesar.org/svn/pub/LogisticHub/
PROCESS CONTROL
DOMAIN
Equipment and
Process
Documentation
EXISTING
APPLICATIONS
&
INFORMATION
REPOSITORIES
ENTERPRISE
DOMAIN
4
Norwegian Oil and Gas’ Information Strategy
An efficient pipeline for
real-time data transferal
and analysis
Smarter solutions
Vendor
Field data







Health, safety,
environment
Seismic
Drilling &
Completion
Reservoir &
production
Operations &
maintenance
Logistics
Transportation
Web portals
Web services
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
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
•
6
Based on Purdue Enterprise
Reference Architecture (PERA)
6
http://www.posccaesar.com/
7
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.

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 ????
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)
8
8
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/
Part 1-9, 2007/9
Dr. Ovidiu Vermesan
SINTEF
Revised Part 4, 2011
Dr. Geir Øvsttun
DNV
Revised Part 2, 2012
Dr. Tore R. Christiansen
PCA
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 on
ISO standards.
The Guideline No. 112 is available at:
http://www.norskoljeoggass.no/no/Publikasjoner/Retningslinjer/In
tegrerte-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
The Purdue Enterprise Reference Architecture (PERA)
13
Guideline No. 112, Part 2 Architecture and Integration
Reference data and ontologies
LogisticHub
Common knowledgebase
of
tracking information
for
the Norwegian offshore industry
1
5
Logistics in the offshore industry
1
6
Logistics on the NCS – An overview 2012





Suppliers of products
and services
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

Rig suppliers

Service companies

O&M contractors

Transport suppliers
Tracking using RFID?
Cargo & Passenger

Supply ships
 Cargo Carrying Units
• Equipment

Helicopter
 People (POB)
 Equipment

Tanker
 Oil
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
The supply chain as seen from the operator
18
A LogisticHub may provide information to all
operators and suppliers
The CCU:





LogisticHub
?
CCU
Transport
owner
Supplier
Who
What
Where
When
Why
+ documents / info.
?
?
Transport
Supply base/Operator
CCU back to the owner
Transport
Installation
19
Automatic Identification and Data Capture
(AIDC)
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)
Unloading (Accepting)
Unpacking (Receiving)
Packing (Picking)
Staging_outbound (Lorry)
Loading
Departing
21
Tracking CCU at supply base
The CCU returning from offshore
The CCU going offshore
22
Automatic Identification and Data Capture (AIDC) technology
Cargo
Carrying
Unit (CCU)
Onshore
Gate/
Portable
RFID reader
& antenna
RFID Tag
Identec Solutions
2-WAY Main Cabinet
10dB Yagi antenna
Onshore
Forklift
truck
RFID reader
& antenna
Identec Solutions
D EN i-PORT M350
2 v1.11 F
Laird, S8655P
Garmin GPS 16 17
Identec Solutions
i-Q350X FL
Onshore
cranes
Tracking package
available similar to
the forklift truck
Server/client and
software package
per site
PC LXE VX9
Identec Solutions
Forklift truck package
RFID reader
& antenna
Identec Solutions
Handheld
RFID reader
Identec Solutions
i-Roc 62x
Offshore
Gate/
Portable
Identec Solutions
Scalable up to
Offshore
cranes
Tracking package
available
Identec Solutions
Price dependent on
the offshore crane
~ NOK ?????
Identec Solutions
GA – Main Cabinet
Model
Arial Oy Av2091
Handheld
RFID reader
Identec Solutions
Atex approved and
available in 2013
~ NOK ????
23
Forklift truck plays an important role at onshore locations
But how to achieve AIDC?
24
LogisticHub Requirements Specifications
ReportingHub – A schematic overview
Master data
NPD Fact
Pages
Regularly updating
of master data
GS1
GLN
Register
PCA
RDS
The Brønnøysund Registers
CCU Owners
XML schemas
(response)
XML schemas
XML schema
(query)
Owner
ID
Type
Certificate
Hirer
Period
NORSOK
Z015 Units
Norwegian
Oil & Gas
sealed CCU
Dangerous
CCU
Appl.
Appl.
Updating
Event
Updating
Event
Updating
Event
Updating
Event
RFID
Reader
RFID
Reader
RFID
Reader
RFID
Reader
RFID Tag
Event
Ordinary
CCU
Appl.
Appl.
CCU
Owner
location
RFID Tag
Event
Supplier
location
RFID Tag
Event
Transport
positions
Supply Chain
RFID Tag
Event
Supply
base
location
Appl.
Updating
Event
RFID
Reader
RFID Tag
Event
Operator
locations
Appl.
Updating
Event
RFID
Reader
RFID Tag
Event
Rig owner
location
26
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
LogisticHub will communicate with probably 300+ organizations
30
Data flow in LogisticHub
13. RH website
User
11. Sending
10. Transforming
to XML file and
validating
12. Regular statistical reporting
9. Generating
RDF report
Response
7. Storing as RDF triples
8. Querying reporting
User
1. Receiving
XML file
2. Validating
3. Decision
6. Storing as XML file
5. New event data
Query
Resend
Correct
Receive
Brønnøysund Register
GS1 GLN Register
NPD Fact Pages
PCA RDS
4. Returning with
error message
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
Phase I of LogisticHub project has focus on the following business
process events:
 Arriving
 Inspecting
 Unloading
 Internal_moving
 (Packing)
 Loading
 Departing
33
Arriving
Query
Response
tag_id
tag_id
org_no
org_no
GLN_location/NPDID_location
GLN_location/NPDID_location
arriving
arriving
date_time
date_time
34
Inspecting
Query
tag_id
org_no
GLN_location/NPDID_location
inspecting
date_time
loc_lat
loc_long
Response
tag_id
org_no
GLN_location/NPDID_location
inspecting
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)
35
Loading
Query
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
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
36
LogisticHub’s conceptual and generic data model
Conceptual data model
Generic data model
37
LogisticHub’s event model
38
Guideline No. 112, Part 2 Architecture and Integration
The semantic technology stack
ISO 15926
39
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
LogisticHub’s master data and standard ontologies
ISO 15926
Part 2
ISO 15926
Part 8
NPD Fact Pages
Convert to ISO 15926
Part 8 (RDF)
RDL
Concepts
&
relationship
ISO 15926
Part 7
Standardized
classification
Brønnøysund Reg.
Convert to ISO 15926
Part 8 (RDF)
GS1 GLN
Convert to ISO 15926
Part 8 (RDF)
41
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