Topic:
How to maximize Data Management efficiency with the IESX database model.

Description:
How to best orgainise IESX data for maximum efficiency.

Solution:
Ideally, disks should be separated into two categories so that seismic data is
written to one set of disks and all other data is written to another set of
disks. Develop a naming convention for the DSLs so that the path/link indicates
the DSL type. For example:
/disk1/seis1/iesxroot
.
.
.
/disk1/seis8/iesxroot
/disk2/seis9/iesxroot
.
.
.
/disk2/seis16/iesxroot
/disk3/proj1/iesxroot
/disk3/proj2/iesxroot
/disk3/intp1/iesxroot
.
.
.
/disk3/intp5/iesxroot
/disk4/intp6/iesxroot

etc.

In the above example, disk1 and disk2 are dedicated to seismic data only and
disk3 and disk4 are for all other data.

It is usually beneficial to adopt a master project/working project model. In
this model master seismic projects contain the seismic and well data while the
master interpretation projects contain the final interpretations. Seismic master
projects should generally not exceed 20Gb-30Gb in size, therefore create several
for a particularly large area if necessary.  Also create separate 2D and 3D
master projects unless there is only a very small amount of 2D data.

Equally important, whenever a user needs to work in the project area, create
a new project, share into the seismic masters as needed and merge over from the
interpretation master(s) the horizon/fault data from which the user wishes to
begin. Move well information into the working project as required (IES DMS
Inventory Rebuild, Geoshare, load, etc).  When the user has completed the
interpretation work, determine what interpretation needs to be saved as 'final'
and merge it back to the interpretation master. Share/copy any derived
volumes to be saved back to the seismic master and then delete the working
project.






Last Modified on: 14-SEP-00