EXIT

Overview of Steps Required for Depth Conversion

Version 8.6

January 2011

EXIT

Trademarks and Copyright This manual was produced by Seismic Micro-Technology, Inc

Version 8.6

Date: January 2011

VelPAK software and documentation was designed and developed by Equipoise Software Ltd. on behalf of Seismic Micro-Technology.

The “Galleon” sample data is made courtesy of Shell based on the condition that no Party makes any warranties or representations with respect to the accuracy or completeness of any Data, and no Party shall have any liability to any other Party resulting from the use of the data, all risk relating thereto being on the Party using the data.The following trademarks may appear in this manual.The KINGDOM™ software and all of its components, 2dPAK®, 3dPAK®, 2d/3dPAK®, AVOPAK®, EarthPAK®, LoadPAK®, ModPAK®, PAKnotes®, SynPAK®, Tunnel L+®, Tunnel O®, VelPAK®, VuPAK®, KINGDOM Colored Inversion™, The KINGDOM Company®, KINGDOM Data Management™, KINGDOM DM Catalog Builder™, KINGDOM Illuminator™, KINGDOM Seeker™, are trademarks or registered trademarks of Seismic Micro-Technology, Inc. (SMT).Certain software programs incorporated in KINGDOM are proprietary products copyrighted © 1993 – 2011 by Seismic Micro-Technology, Inc. All rights reserved. Portions of data loading are copyrighted by Blue Marble Geographics. VuPAK and VelPAK include OpenInventor™ and VolumeViz™ from the Mercury Computer Systems Incorporated. ModPAK includes SHAPES® from XOX Corporation. Tunnel L+ includes OpenWorks® and SeisWorks® Development Kit from the Landmark Graphics Corporation. Tunnel O includes OpenSpirit® FrameWork from the OpenSpirit Corporation.

Seismic Micro-Technology, Inc. 8584 Katy Freeway, Suite 400

Houston, Texas 77024 U.S.A.

Tel: (713) 464-6188 Fax: (713) 464-6440

Internet Address: www.seismicmicro.com E-Mail Address: smt@seismicmicro.com

Marketing: sales@seismicmicro.com Tech Support: support@seismicmicro.com

www.equipoise.co.uk Equipoise Software Ltd, 3a Rathbone Square, 28 Tanfield Road, Croydon, Surrey, CR0 1BT. U.K.

iii

Portions of KINGDOM bitmap graphics are based on GD library by Boutell.Com, Inc. Further information about the company can be found at www.boutell.com. PAKnotes TIFF support is based in part on libtiff. Rock Solid Attributes™ is a trademark of RDSP I, L.P. Solid Attributes™ contains confidential, proprietary, and trade secret information of RDSP I, L.P. This unpublished work by RDSP I, L.P. is ii protected by the laws of the United States and other countries. Additionally, if publication occurs, the following notice shall apply: Copyright ©RDSP I, L.P., All Rights reserved. Microsoft is a registered trademark of Microsoft Corporation. Windows 2000, XP, and XP x64 operating systems, MS-DOS and SQL Server are trademarks of Microsoft Corporation. Oracle® Databases are registered trademarks of Oracle Corporation. OpenWorks, SeisWorks, Interpret 2000 and Interpret 2003 are registered trademarks of Landmark Graphics Corporation. SMT incorporates BMC® AppSight™ Black Box Technology in its software. BMC Software, BMC Software logos and all other BMC Software product and service names are registered trademarks or trademarks of BMC Software Inc. © 2007 BMC Software, Inc. All rights reserved. All other trademarks are the property of their respective holders. ©2011 Seismic Micro-Technology, Inc. All Rights Reserved Worldwide KINGDOM and this manual are both copyrighted and intended for use by a single user or a single computer whose model is authorized by Seismic Micro-Technology, Inc. You are entitled to electronically transcribe KINGDOM CD-Rom to the hard disk of an authorized computer so long as KINGDOM and related software packages are operated on only one computer at a time. You are further entitled to electronically transcribe the CD to other CD(s) for archival storage only. Physical duplication of the KINGDOM software and SENTINEL is expressly forbidden. No portion of KINGDOM software may be incorporated into any other program. No other usage or transcription in any form is allowed without the express written permission of Seismic Micro-Technology, Inc. No portion of this manual may be reproduced, transmitted, transcribed or stored on any information retrieval system, or translated into any foreign language or any computer language in any form and by any means whatsoever without the express written permission of Seismic Micro-Technology, Inc.This document contains confidential

Misuse DisclaimerSeismic Micro-Technology, Inc. makes no representation or warranties of any kind with respect to this manual or The KINGDOM Software Package. Specifically, Seismic Micro-Technology, Inc. disclaims any implied or any other claimed warranties of merchantability or suitability for any particular purpose. Seismic Micro-Technology, Inc. reserves the right to modify. The KINGDOM Software Package and any of the associated user documentation at any time.

Acknowledgments Seismic Micro-Technology, Inc. wishes to gratefully acknowledge the contributions of the many amber software testers in preparing The KINGDOM Software. The enthusiastic Beta Testers, smoke testers, and the SMT Staff greatly appreciate their invaluable feedback and contributions.

iv

EXIT

How to Depth Convert in VelPAKThe most common method of depth conversion in VelPAK is via surfaces using the VelPAK workflow modules, but it is also possible for the user to manually depth convert surface data in the VelPAK project.

However before either manual or workflow Depth Conversion can take place the Layers in your project must be defined.

Note: Before any method of surface Depth Conversion that uses well data can take place you must assign the Layers in the Layer Definition Module.

The typical flow of work on the following page describes the two flows available.

For a tutorial on how to depth convert following Layer Definition using the Workflow method Go Here.

For a tutorial on how to depth convert following Layer Definition using a manual method Go Here.

Note: You can also run a layer cake depth conversion on Event Horizon Profile data within VelPAK that has been successfully snapped without needing to run a Layer Definition. Go Here for further details.

KINGDOM 8.6 1

Typical VelPAK Depth Conversion Flow

EXIT

Typical VelPAK Depth Conversion Flow Open your project or read

data in via the TKS link

Go into theWorkflow Module

Import your Stacking Velocities if you intend to use them

Assign the Layer Definitions

Press the RUN

button

Choose a pre-defined Workflow

Depth Conversion that suits

yourdata

Choose WORKFLOW

Method

ChooseMANUAL Method

Select the Depth Conversion method and parameters to use in the Depth Tab of the Surface

Module

Press the ACTIVATE

Check button

Decide what Depth Conversion method

Generate Curves, Grids etc. that will

be used in your Depth Conversion

For Each Surface

2 KINGDOM 8.6

Exporting Surfaces from VelPAK into TKS

EXIT

Exporting Surfaces from VelPAK into TKSAfter you have performed your depth conversion you can move surface grids from the VelPAK model into the project database (project tree).

Currently only surface grid data can be exported from VelPAK via the Link into the current TKS project.Please refer to Exporting TKS data from VelPAK for details.

Exporting the Velocity VolumeOnce a velocity model has been built, the velocity volume can be created and exported as SEG Y, please refer to the Exporting the Velocity Volume.

KINGDOM 8.6 3

Profile Depth Conversion

EXIT

Profile Depth Conversion

Once Event Horizon Profile data within VelPAK have been successfully snapped to form continuous layers, a layer cake depth conversion can be performed on the data, using either pre-stored methods or user-defined methods, utilizing Constants, Grids, Curves and a large number of standard formulae.

These would tend to be set up manually - not through the workflow system - and currently there are no pre-defined workflows set up for Profile depth conversion.

Depth Conversion methods within the Profile Module of VelPAK work solely on the TIME PRO-FILE data.

Depth conversion methods are set up under the Depth Parameters tab of the Profile module.

Note: All event horizons within your model need to have a valid depth Conversion method set up in order for the Profile Layer-Cake depth conversion to run successfully. Set up is done per event horizon; set up one event horizon in the Depth Dialog Parameters and then move to a new event horizon via the VelPAK Surface&Slot selector and set up a new set of Depth Conversion Parameters for that event horizon...and so on.

4 KINGDOM 8.6