1 / 45

LogisticHub

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. RFID in Norwegian Oil and Gas

nora
Download Presentation

LogisticHub

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LogisticHub A common knowledgebase for tracking information for the offshore supply chain Dr. Thore LangelandManager Integrated Operations Norwegian Oil and Gas Email address: tla@norog.no Mobile: +47-9095 1756

  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. OIL & GAS RFID YES No The RFID solutions should be adapted to oil and gas industry and not to the RFID world Oil &Gas RFID • 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: RFID in Norwegian Oil and Gas

  5. An efficient pipeline for real-time data transferal and analysis Smarter solutions Norwegian Oil and Gas’ Information Strategy 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

  7. 7 http://www.posccaesar.com/

  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 6 000 users • EnvironmentWeb (EW) – yearly reports of emissions and discharges from operators to authorities (ISO 15926 compliant) • 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

  9. Norwegian Oil and GasGuideline No. 112 “Deployment of RFID in oil and gas industry”http://www.norskoljeoggass.no/no/Publikasjoner/Retningslinjer/Integrerte-operasjonerIntegrated-operations/112/ Revised Part 2, 2012 Part 1-9, 2007/9 Revised Part 4, 2011 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 • 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/Integrerte-operasjonerIntegrated-operations/112/ 10

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

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

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

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

  15. LogisticHubCommon knowledgebase of tracking information for the Norwegian offshore industry 15

  16. Logistics in the offshore industry 16

  17. Suppliers of products and services • Rig suppliers • Service companies • O&M contractors • Transport suppliers • 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 Logistics on the NCS – An overview 2012 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 Tracking using RFID? Cargo & Passenger • Supply ships • Cargo Carrying Units • Equipment • Helicopter • People (POB) • Equipment • 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 Supplier Supply base/Operator Installation Transport Transport Transport 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) Unloading (Accepting) Unpacking (Receiving) Packing (Picking) Staging_outbound (Lorry) Loading Departing

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

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

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

  25. LogisticHub Requirements Specifications

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

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

  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 12. Regular statistical reporting User 10. Transforming to XML file and validating User 9. Generating RDF report 11. Sending Query 3. Decision Response 7. Storing as RDF triples 8. Querying reporting 6. Storing as XML file 1. Receiving XML file 2. Validating 5. New event data Brønnøysund Register GS1 GLN Register NPD Fact Pages PCA RDS Resend Correct Receive 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. Phase I of LogisticHub project has focus on the following business process events: A typical sequence of events at a supplier location • Arriving • Inspecting • Unloading • Internal_moving • (Packing) • Loading • Departing

  33. Arriving

  34. Inspecting

  35. Loading

  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 ISO 15926 The semantic technology stack 39

  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

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

  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

More Related