Seismic Data

Definition Update
October 2019
Doug Gregory, Chevron
 Seismic Data Definition and Modeling Purpose

Provide data definition for R2 Seismic:

» Schema and definition for seismic data types
– Master data
– Reference data and controlled values
– Work product/component metadata
» Workflow design target and use cases
» File Format targets
» Index schema additions
» Impact on APIs 2
Copyright © The Open Group 2019
 Object Scope for Seismic R2
Object R2 Deferred Notes
Survey Geometry Surface geometries (stress Borehole, Microseismic, SWD, hi-res/ 2D not expected to be fully evolved
on 3D) uav/ shallow/ geotechnical, 4D, 4C.
Data Lifecycle Interpretation Acquisition, Processing R2 will require minimum field and processing info
to support datasets and interpretation
Support Data Technical documentation Agreements, contract terms Includes OB notes.
(e.g. processing reports)
Traces Poststack. Stretch Workflow – form substacks, track lineage
Stretch goal – prestack. to inputs
Geometry Data Navigation, Bin grid Navigation likely to fall out

Faults and Fault and Horizon Picks Surfaces and Earth Model are separate What representations are in R2?
Horizons (point sets)
Velocity Time-to-depth Checkshot, stack/ migration models Non-borehole models probably included

Provenance Lineage Process History Minimal process history already present in R2

Ownership As needed to support Documention of no-permit zones Topic includes licensed vs. proprietary.
entitlements Entitlements within single dataset out of scope.
GIS mappables Boundary shapes What are the sources?

Copyright © The Open Group 2019

 Seismic MVP2 Workflow
» Ingest 3D survey
» Merge bin geometry (P6/11)
» Transcode SEGY to OpenVDS
» View slices of volume in 2D
» Search by map and metadata
» Extract seismic amplitudes
– Convert well path to time and to seismic volume’s CRS, extract and interpolate amplitudes
along wellbore between two seismic horizons
– Extract slab of amplitudes between two seismic horizons.
» Pass extracted amplitudes to (external?) ML platform
» Return predicted result and catalog to universe
» Export/deliver trace volume as Petrel ZGY, SEGY Rev 1
» Export/deliver some interpretation data type(s) to RESQML
4
Copyright © The Open Group 2019
 Work done
» Defined Project virtual master data concept, realized as
– Seismic Acquisition Project
– Seismic Processing Project
– Seismic Interpretation Project
» Updated SDU objects as made available
– Seismic Processing Activity WP
– Seismic Trace Data WPC
– Velocity Modeling WPC
– Alias Name
» Paused to review and understand OpenDES
– Reference architecture
– Seismic model
– OSDU friction points
» Agreed to Volve for test data
5
Copyright © The Open Group 2019
 Work to do this year
» Translate subcommittee structural decisions from face-to-face into seismic
schema. Issues include:
– Role of Project, Activity, Work Product
– Preferred expression of relationships
– Reformulation of abstract references
– Design principles for calculated properties, repeating properties, and additional index
schema properties
– Addition of data validation and data quality attributes
» Merge OpenDES seismic types into existing data types
– Review proposed changes to already-reviewed types
– Incorporate desired elements into new data types
» Consider additional proposals and achieve consensus on all updated data
types
» API impact of schema changes
6
Copyright © The Open Group 2019
 Work to do in 1Q20 for R2
» Achieve consensus on index schema additions
» Identify controlled reference data types and supply
recommended reference values
– Establish namespace standard for identifiers
» Finalize changes due to entitlements design
» Finalize changes due to subscription service design
» Write usage documentation

7
Copyright © The Open Group 2019