Status of the National Petroleum Data Repository DISKOS

1. Status of the National Petroleum Data Repository DISKOS Kjell Reidar Knudsen Norwegian Petroleum Directorate National Data Repository Meeting no 5 September 2004

2. National Data Repository Concept (Norway) Reference data Catalogue NPD Outsourced NDR-2 NDR-1 Core samples Fluid samples archive DISKOS Professional digital databases Physical storage/warehouses

3. English Fact page www.npd.no

5. NPD Fact pages - Well data • Core photos from selected wells have now been published on the NPD's fact pages. The photos of core samples taken during drilling provide important information on the seabed rocks. • WDSS (Well Data Summary Sheets) for selected released wells have now been published on the NPD's fact pages. • These contain a summary of data: • As well as general information and technical data, WDSS also contain well history, well testing results, geological interpretations of formation tops and geochemistry for the well. In addition, WDSS provide an overview of at what depths and intervals the NPD has cuttings and drilling cores from a given well.

6. National Data Repository Concept (Norway) Reference data Catalogue NPD Outsourced EW NDR-2 NDR-1 Core samples Fluid samples archive Professional digital databases Physical storage/warehouses EW = Environment Web

7. A joint database for emmission to air and discharges to sea for the Norwegian petroleum activity Co-operation between OLF, NPD og NPC ”EW-database ” National Data Repository Meeting no 5 September 2004

8. and a shared work process collaboration tool A joint database for emmissions to air and discharge to sea from Norwegian petroleum activity Co-operation between OLF, NPD og NPC ”EW-database ” all operating oil companies in Norway National Data Repository Meeting no 5 September 2004

9. EW - Objective Improve quality Basis for useful analysis Less workload

10. A central shared database public NPD E W OLF NPC

12. Reporting requirements • Field status • Discharge from drilling • Discharge of oily water • Use and discharge of chemicals • Chemicals evaluation • Use and discharge of environmentally toxic compounds • Emissions to air • Acute pollution • Waste

13. Level of reporting • Wellbore level • Drilling- and well chemicals • Facility level (fixed or movable) • ”Rig chemicals” (thread grease and BOP/jetting--) • Waste, acute discharge, diesel • Chemicals ( production- export-… • Discharge to sea • Emission to air • Operator level • Total exploration wells • Field level • Discharge concents and estimated consumption/discharge of products • Total all facilities From operators

14. Work process

15. History • Januar 2002 SFT,OD og OLF wanted to develop a database on SOIL • Dec 2002 Request for information to software vendors • April 2003 Tender invitation • Juni 2003 Contract with Cap Gemini Ernst&Young • August 2003 Formal co-operation contract signed • November 2003 Testing of first delivery • January 2004 Database went live • March 2004 First reports loaded from all operators on NCS (2003 data) • August 2004 Historical data load started

16. National Data Repository Concept (Norway) Reference data Catalogue NPD Outsourced NDR-2 NDR-1 Core samples Fluid samples archive DISKOS Professional digital databases Physical storage/warehouses

17. DISKOS project milestones • Project started in 1992 • Operation started 1995 • Revised business model 2000 • Change of operator 2004

18. DISKOS basics • Mandatory to submit all new data to DISKOS (government reporting requirements) • Database contains both confidential and public data • What is public varies with time • Membership required to download data online • Non-members can get physical copies of public data • Members can buy ”additional services”

19. History - The Diskos Project • The Diskos Project requirements – specifications and application to tender were sent out in June 1993 • To establish a joint database for quality controlled geodata and to make this data available to users • An open solution able to interact with other solutions • Main focus on digital seismic data • POSC Data model (Epicentre) • UNIX-based client-server environment • GIS Gui (e.g. ArcInfo) • Water-tight security and use ”World Class” technology were specific demands. • The system must control ownership, entitlements (access rights) and trade transactions to each survey, line, line segment for original and reprocessed data

20. Issues...... • Technical • Number of involved companies • Work processes ( incl quality requirements) • Budget requirements • Software development • Projects ( incl loading of historic data ) • Cost split between members

21. Diskos Organisation • The key to success has been a climate of collaboration and mutual understanding • Different members: • The authorities • Major Oil Companies • Smaller Oil Companies • New Companies on the NCS • Diskos Work Groups has been a key to establishing good solutions • Challenge is to maintain a firm industry focus • Perception that Diskos now works and does not need the same level of commitment as before. This must be avoided!

22. Meet 3-4 times/yearAll companies represented Meet 7-8 times/yearThis group is elected by Diskos MC All members are entitled to participate in work groups Landmark and PetroData are also represented Project Manager NPD legal dept. NPD accounts

23. DATATYPES • Administrative data • License, block, quadrant, coastlines, national borders • Field, platform, pipeline, water depth • Well data • Position, name, category, etc • Well reports • Post stack seismic data • All processed 2D and 3D data, velocity data • Seismic navigation • Navigation shotpoint position • Production Data • Historical and future reporting • Log Data • Historical and future reporting Quality controlled data from NPD, every week From companies

24. Cultural DataA Cornerstone in the Solution • Registration of all licences • Operator status and Licence participants • Share of licence • Historical Licence Information • Well ID’s • Pipelines • Coastlines • Etc. • Cultural Data supplied by NPD to PetroData

25. Digital Reporting – Seismic Data • Processed seismic data in the following versions is to be reported: • Raw Stack • Raw Migration • Filtered Migration • The naming of seismic lines must be in accordance with guidelines (established by Diskos Seismic Work Group) • Velocity Data • Digital Navigation data • In accordance with ”Specifications and Information for Reporting Navigation Data to PetroData – see also NPD web site

26. Data to PetroBank • Example: Stages in the life of well data: Reporting to NPD complete ‘Public’ access Exclusive access Data acq. & proc. Time 0 - completion date 6 months Stage 2 Stage 0 Stage 1 24 months

27. DISKOS Status Sept 2004 • Users (Members and non-members) • Contract structure • Change of operator • Data volume

28. Diskos members 2004

29. Roles: NPDPetroData – Landmark - Schlumberger • NPD management of the Diskos Project • on behalf of Diskos Members • Landmark Graphics • Development of the PetroBank software in collaboration with PetroBank users world wideSOFTWARE • SINAS • Management of data on behalf of the Diskos Group using PetroBank technology OPERATIONS

30. DISKOS SOLUTION 3 ELEMENTS • SOIL network • High-speed secure closed networks • Lan2Lan connection Harstad • PetroBank Software • Multi-client petroleum data repository • Developed by Landmark • The Diskos Database • Central storage of company data • Run by PetroData since 1995 • By Schlumberger from 2004 Trondheim Bergen Oslo Stavanger

31. Diskos Tender Process 2002Operations of Diskos Database • Diskos by law had to go to tender – • Bound by Norwegian and European • New agreement in place 2004 • A time consuming and demanding process • Committment from the whole of Diskos in this work • An important exercise for Diskos • Operators are in a privilged position – monopoly issues • Tender process gives the Diskos group valuable insight into technological alternatives • The current business model and contractural structure will be evaluated and modified

32. Statistics – Data Storage • SINAS currently storage capacity • Oracle Database – ~ 150 GB • Netapp Disc storage systems – ~ Total 110 TB. • ~ 60 TB in use for post stack seismic, logs and other “small” data sets • StorageTek Tape robotics system - 1800 TB of storage capability • IBM 3592 Tape technology • Tivoli Storage Manager (TSM) used to manage Post Stack data.

33. Historical Well-Data Projects • Loading of scanned completion reports 1965-1999 • access according to entitlements • Loading of Scanned ”Public” reports from exploration and appraisal wells drilled 1965-1979. • Loading of well data from 1965 to 1993to transfer data from old media to PetroBank to eliminate old input media. • Loading of indexes for well reports and well logs, exploration and development wells 1965 to 1999

34. Lessons learnt in loading legacy data • Time consuming and costly process • A lot of manual work • QC of data input • Need to understand the data • Level of quality when scanning • Are all pages legible? • Are all pages included? • Colour vs black-and-white • Older tape formats • Difficult to read • Costly to covert – cost-benefit • Setting entitlements to data was a major task • Data transfer due to changes in licence ownership/participation

35. Transfer of operations Data definitions Robot clean up Bulk data transfer Agree on transfer method Verification Data Transfer from Petrodata to SINAS Acceptance Planning Diskos Petrodata SINAS Business as usual 1.1.2004 All Diskos members

36. DTP-Transfer Plan 2003

37. Transfer of operations – some experiences from Norway • Very demanding process • Can be problems with the previous operator • Takes focus away from ongoing issues • Takes a lot of time so the process must begin early • in Norway at end of 2002 for 2004 change over • Need a good spread of expertise • Technical (data), contractual (tenders, legal aspects), software • It is worth the effort! • Introduces/maintains competition • Step change in technology • Revise/improve business model • Improve/streamline workflows