You are on page 1of 11

Auto Merge 2D Seismic Interpretation

© 2014 Schlumberger. All rights reserved.

An asterisk is used throughout this presentation to denote a mark of Schlumberger.


Other company, product, and service names are the properties of their respective
owners.
Introduction
Background
 While we perform a Information Management Project,
clean up process for seismic interpretation data is the most time consuming step.
 To enhance the speed of the data clean up, we suggest petrel work-flow for auto-
mergence
of 2D seismic interpretation.
 There is a case that same horizon interpretation is separated as difference interpretation
with same name. Merging all these horizon one by one manually is quite boring and
burdensome job.

Problem & Solution


 By using Petrel workflow, we are going to merge 2D seismic interpretation with same
name.
⁃ Firstly, convert each seismic to point data
⁃ Merge each point data with same name to one-set of point data
⁃ Convert merged point data to seismic horizon interpretation
Structure of Workflow

YES

NO
Petrel Workflow (1/3)

 Designate horizon interpretations to be merged


Petrel Workflow (2/3)

 Generate new folder to save intermediate product & convert each horizon interpretations
to point

 Release point data to the folder based on name


Petrel Workflow (3/3)

 After appending each point data set, convert them to seismic horizon interpretation
 Finalize the algorithm & eliminate intermediate product such as point data
How to Use
Step 1.
 Input the seismic horizon interpretation to the Reference list

Step 2.
 Designate the seismic survey to convert point data set

Step 3.
 Run the workflow & Quality check the result.
Result (1/2)
Seoul Horizon (1) Seoul Horizon (2)

Seoul Horizon (3) Seoul Horizon (1+2+3)


Result (2/2)
Advantage & Limitation

Advantage of suggested workflow


 We can enhance the speed of mergence process
which is one of the most burdensome job in data clean up.

 Well organize the interpretation data.

Limitations

 All interpretations to be merged should be set as same name before run the
workflow.

You might also like