Geophysics SIG Work Meetings Houston, 12 March 2009 Web Conference, 26 March 2009

Energistics Meeting Policies Intellectual Property –Participation indicates agreement to abide –Do not disclose confidential Disclosures are deemed public –Contributions are made with grant of rights to use, modify, etc. Competitive Information –Do not disclose pricing, costs, sales, plans, schedules, etc. Or your participation may be terminated –If you are uncomfortable regarding such legal matters, leave the meeting and report your concerns.

Meeting Agenda Welcome and Introductions Meeting Objectives Highlights of the 2008 Study ONGC Presentation Topics for Discussion: –Best practice elaborations –Input to or promotional activities for SEG TSC –Specifications definition –RESQML coordination activities –OGP (Positioning and Survey) Initiative Refinement of practical suggestions; discussion of next steps Adjourn

Welcome and Introductions Welcome and Logistics Introductions –Please state Your name and company Your current role and responsibilities Your reasons and expectations for participating today

Meeting Objectives To begin to identify: –work practice improvement opportunities that can be promoted by the SIG –collaboration opportunities that can be taken forward by the SIG To agree on several high value collaborative activities for the SIG

Energistics Board of Directors Management & Staff Advisory Council Membership Other SIGs Membership and SIGs RESQML SIG WITSML SIG PRODML SIG Participants Energistics Standards: WITSML, PRODML, etc. SIGs are standards user communities

Industry Services SIG Energistics Subject Areas Reservoir Engineering Expl Geology PetrophysicsPetroleum Engineering Drilling Engineering Production Geology Production Engineering Facilities Engineering Production OperationsGeophysics Drilling Operations Completion & Workover Asset Management Reservoir Engineering Expl Geology PetrophysicsPetroleum Engineering Drilling Engineering Production Geology Production Engineering Facilities Engineering Production Operations Geophysics Drilling Operations Completion & Workover SIG Geophysics SIG SIG Geology SIG Asset/Data Management SIG eRegulatory SIG 7

Geophysics SIG Headlines –Formal assessment study of work practice improvement opportunities published –A member review meeting (October) Plans –SEG relationship strengthening –RESQML relationship Interpretation models –Presence in India –Identify viable activities for the SIG Member meetings (March 12, …) Recruiting participation –Collaboration site GeophSIG Geophysics

Best Practice Recommendations Principles –Life cycle data procedures –Data ownership responsibilities –Sufficient resources to manage data –Use industry standards Work Practice Improvement Opportunities –Geodetics and CRS –Service and data acquisition agreements –Data compression –Survey and line names –SEG-Y rev1, SEG-D rev 3, SEG-Y/SEG-D alignment –Integrate position and trace data –Improve logs and reports –Improve trade data evaluations

Highlights of the 2008 Study Identifies typical delays in Acquisition, Processing, Interpretation (API) and Data Management life cycle Identifies opportunities for improved use of existing and rapid uptake of imminent SEG standards –Recognizes need for greater standardization to enable geophysics role in Integrated Operations Recognizes need for collaboration with SEG and OGP Outlines guidelines for improved work practices

Geophysical ActivityNumber of Opportunities Cumulative average delays (days) Acquisition2632 Positioning1419 Processing116 Interpretation48 Data Management1218 Total – all activities6783 Energistics Study on Delays

ONGC Presentation – Dr J.V.S.S.N. Murthy

Topics for Discussion Geophysical Best practices elaborated Input to or promotional activities for SEG TSC Specifications definition RESQML coordination activities

Geophysical Best practices elaborated Guiding Principles Enabling Work Practice Improvements Routine Work Practice Improvements

Guiding Principles Define Life Cycle Data Procedures Define Ownership Responsibilities Assign Sufficient Data Resources Use Available Data Standards

Enabling Work Practice Improvements Geodetic and Projected Coordinate Reference Systems Service and Acquisition Agreement Templates Data Compression Techniques Survey and Line Names SEG-D revision 3, SEG-Y revision 1 SEG-Y / SEG-D Alignment SEG SPS / SEG-D Alignment Data Management Data Management –General Metadata for data management and auditing Note: Underlined subjects were high priority on March 12 th.

Routine Work Practice Improvements Position and Trace Data Integration EPSG Geodetic and Projected Coordinate Reference System List Use Observer’s Log Use Position Data and Survey Report Use Processor’s Log Use Acquisition Agreement Template Use Trade Data Evaluation SPS Land 3-D Survey QC

Collaboration with SEG Possible inputs or promotional activities –Units of Measure in SEG-D Rev 3 –Usage guidelines for SEG-D Rev 3 ? –Promotion of SEG-Y Rev 1, SEG-D Rev 3 ? –Requirements for SEG-Y / SEG-D alignment ? –Other??

Specifications definition Content standard for Observer’s Log Content standard for Survey Report (ref OGP) Content standard for Processing Log Exchange standard for Velocity Data –Proposal in hand –Will re-use Energistics XML assets (content and architecture)

Velocity Function Outline Schema velocityFunctionSet documentInformation seismicSurvey surveyKind (e.g. 2D or 3D) seismicWaveKind indexKind indexUnit coordinateReferenceSystem velocityFunction velocityFunctionID (Choice of (2-D seismic, 3-D seismic, well)) positionTuple seismicDatum (to be clarified) listOf(velocityKind, velocityUnit) VelocityTupleSet indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName indexValue, listOf(velocityValue), reflectorID, horizonName velocityFunction......

Velocity Function - Issues Is there value in using the same XML schema for velocities from wells as from seismic? Who will add to the list of velocity types (average, rms, interval, etc.? Is there ever a need to mingle velocities for different wave types in one data set? What is the meaning of seismicDatum, or Datum Time? Is the seismicDatum always a time, never a depth? (What about in well data?) Do we need to handle anisotropy? Now or later? What are the detailed requirements for this? The method (algorithm, interpolation technique, manual) by which the velocity function was created should be captured. (Doug Gregory, Chevron, raised at SIG meeting Houston 12 March 2009) Others?

Velocity Function – Enumerated Lists indexKind: –one-way-time, two-way-time, depth, measured depth surveyKind: –well check-shot, VSP, uphole, 2-D seismic, 3-D seismic... velocityKind: –average, rms, interval, stacking, migration... seismicWaveKind: –P, S, SH, SV...

RESQML coordination activities RESQML is the successor to the RESCUE C++ libraries for exchange between Geological (static) and Reservoir Simulation (dynamic) models –RESQML will be compliant with other Energistics ML’s Geophysical Interpretations produce structural and property models which provide horizon, fault and other data into Geological and Reservoir models –There is a requirement that the data and meta-data of the geological objects should be consistently represented at both levels –Process history and audit data are also needed

OGP (Survey & Positioning) Initiative Oil and Gas Producers Association –Have custodianship of former UKOOA and SEG seismic position data formats and of EPSG Geodetic Dataset –New Initiative proposes to modernise P1 (post-processing) position data exchange formats P2 (pre-processing) position data exchange formats P6 seismic binning standard P7 (post-processing, archive) deviated well path data –Requirements Questionnaire gathering user requirements: results to be presented in April –Plan to complete revisions by end 2009 –SEG D revision 3 will reference ‘current’ PN formats

Practicalities Refine suggestions Recommendations from March 12 Meeting –General metadata for data management and auditing –Agreement templates by work practice profile –Standard dataset names and identifiers –Processor Log work practice improvements –Velocity function specifications –Coordination with RESQML SIG Next steps –Web conference on March 26 at 09:00 Houston, 14:00 UK, 15:00 Europe, 19:30 India –Refinement of proposed collaborative activities into timelines and calls for participation.

Adjourn Questions? Thank You! More Information from: Alan Doniger Paul Maton