Install guide

COL02 "Play Summary" N 2
COL03 "Stratigraphy" N 3
COL04 "Reservoir" N 4
COL05 "Source" N 5
COL06 "Seal" N 6
COL07 "Structure" N 7
COL08 "Timing" N 8
COL09 "Scout Info" N 9
COL10 "Other Comments" N 10
$OWHOME/WebApps/conf/seismic_keyfacts:
COL01 "Data Source" N 1
COL02 "Acquisition Info" N 2
COL03 "Processing Info" N 3
COL04 "Data Loading Info" N 4
COL05 "Related Seismic" N 5
COL06 "Other Comments" N 6
$OWHOME/WebApps/conf/survey_keyfacts:
COL01 "Interp Status" N 1
COL02 "Quad/Block" N 2
COL03 "Field" N 3
COL04 "Operator" N 4
COL05 "Asset" N 5
COL06 "Data Loading Info" N 6
COL07 "Data Availability" N 7
COL08 "Other Comments" N 8
Customizing the Comparison Module
The Comparison module allows users to compare well, field, lease and navigation headers
as well as details on well position logs, curves, picks and time-depth tables.
In addition to the above, users may compare counts for any well-related reference data
types. For example, do the wells have the same number of casing points in two different
projects? The default option caters for cores, tests, casing, tubing, completions,
perforation, liners, packers, dipmeters, shows, paleo and mud reports.
The list is customizable using the default file well_comparison.dat.default in
$OWHOME/WebApps/conf. To modify the defaults, copy this file to
well_comparison.dat and add tables as indicated by the syntax description. Note
that any tables added must contain a well_id field.
#
# If present, the well_comparison.dat file allows the specification of
# additional well data types for the comparison of data between 2 OpenWorks
# projects. Comparison will simply be on counts per well.
#
# format: TableName Label
#
well_core Cores
well_test Tests
casing Casing
tubing Tubing
well_completion Completions
well_perforation Perforations
liner Liners
packer Packers
dipmeter Dipmeters
intrp_drilg_show Shows
paleo Paleontology
mud_report "Mud Report"
WOW 5000.0.1.11 Release Notes Page 72 of 104 March 2014