AFS RN InstallGuide 2003.4.0

Landmark
Active Field Surveillance

Release2003.4.0.0
Release Notes and Installation Guide
Landmark/Asia Pacific
11th Floor Menara Tan & Tan
207 Jalan Tun Razak
50400 Kuala Lumpur
Malaysia
Tel: 011-60-3-2164-1121
Fax: 011-60-3-2164-1135
Help Desk: 011-61-8-9481-4488
Email: apsupport@lgc.com
Landmark/EAME
Hill Park South
Springfield Drive
Leatherhead, Surrey GU22 7NL
England
Tel: 011-44 (0) 1372 868-600
Fax: 011-44 (0) 1372 868-601
Help Desk: 011-44 (0) 1372-868686
Email: eame_helpdesk@lgc.com
Landmark/The Americas
Building 1, Suite 200, 2101 CityWest
Houston, TX 77042
P.O. Box 42806, Houston, TX 77242
U.S.A.
Tel: 713-839-2000
Help Desk: 713-839-2200
Fax: 713-839-2169
Email: support@lgc.com
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Whats in Release2003.4.0.0. . . . . . . . . . . . . . . . . . .
Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Conventions Used in this Guide . . . . . . . . . . . . . . . 21
Prerequisites for AFS Installation . . . . . . . . . . . . . 22
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing Hummingbird Exceed 7.0 . . . . . . . . . . . . 23
Installing Oracle or SQL Server . . . . . . . . . . . . . . . 24
Install AFS Product Suite . . . . . . . . . . . . . . . . . . . . . 24
R2003.4.0.0 Release Notes
Page 1 of 91
July 2002
Landmark
Install DESKTOP-VIP . . . . . . . . . . . . . . . . . . . . . . . . . 45
Pre-Database Creation Procedures . . . . . . . . . . . . 46
AFS Database Creation . . . . . . . . . . . . . . . . . . . . . . . 50
Post Database Creation Procedures . . . . . . . . . . . 58
Configure ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configure Oracle Service Name . . . . . . . . . . . . . . . 68
Citrix Metaframe XP Setup . . . . . . . . . . . . . . . . . . . . 71
Install LAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Known Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Appendix A: Contacting Support . . . . . . . . . . . . . . 86
Page 2 of 91
July 2002
Landmark
Introduction
Welcome to Landmark's Active Field Surveillance (AFS) synchronous release, Release2003.4.0.0.
AFS is centered around two workflows. To learn more, refer to the following sections:
Active Field Surveillance Workflows on page 4

Citrix Ready Applications on page 6
Release2003 marked the beginning of a new release strategy for Landmark, the foundation
release. The foundation release provides a basis for subsequent theme releases. In
Release2003.4.0.0 the production and economic data management products are grouped together
to create a theme release around Active Field Surveillance.
As with any complex, full-features software product, Release2003.4.0.0 contains some defects. An
abbreviated list of Known Problems is provided on page 84. For a complete list of defects, refer to
individual product release notes.
Release 2003.4.0.0 is a reliable, flexible enhancement to the Landmark family of products.
We welcome input on any of the Landmark products and thank you for helping make
Release2003.4.0.0 a success. For Support contact information, refer to Appendix A, page 86.
Page 3 of 91
July 2002
Landmark
Active Field Surveillance Workflows

Release2003.4.0.0 is a theme release focusing on two Active Field Surveillance Workflows. The
two workflows, Squeezing the Sponge and Dynamic Reservoir Management, revolve around
TOW/cs as a data management tool.
Squeezing the Sponge
In the first workflow, Squeezing the Sponge, production data from TOW/cs is used to identify
wells in DSS where current production is significantly below target production. This subset of
wells is analyzed further to identify potential solutions. Based on this analysis, one of the following
options is recommended:
workover
adjust equipment
recondition/recompletion
shut-in (TA)
plug and abandon (PA)
In addition to identifying problems, Squeezing the Sponge enables you to find and prioritize
opportunities by leveraging historical production data. The diagram below illustrates the general
process flow.
Wellbore Data
Workover Histories
Determine
Target
Production
DIMS
ARIES/DSS
OpenWorks
Surveillance
Collect
TOW/cs
Data
Collect
SCADA
Data
Zone Data
Logs
Layers
Reservoir Parameters
DSS
Determine
Actual
Actual
Production
ProductionData
Mechanical
Options
Reservoir
TOW/cs
Economics
Management
Presentation
ARIES
Page 4 of 91
July 2002
Landmark
Dynamic Reservoir Management

In the second workflow, Dynamic Reservoir Management, a newly acquired field is analyzed using
DSS and Desktop - VIP to determine why its decline is significantly steeper than that predicted by
reservoir simulation. Possible reasons for this discrepancy include previously misunderstood fluid
contacts and discontinuous permeabilities.
After examining analog data, reservoir simulations and infrastructure investigations are used to
create a development scenario in Desktop - VIP. Finally, economics are run in ARIES and a
business decision is made based on the results.
Compare
Forecasted vs.
Actual Production
DSS
Reservoir Modeling
history matching, predictions
VIP
Investigate Infrastructure
wells, resources
VIP/DSS
Development
Scenario
VIP
Project
Economics
(NPV)
ARIES
Not Economic
Delay
Move-on
Re-evaluate
Economic
Management
Presentation
Implement
Project
Evaluate
Project
Dynamic Reservoir Management allows you to increase the value and life of your newly acquired
asset using horizontal drilling.
Page 5 of 91
July 2002
Landmark
Whats in Release2003.4.0.0
Release2003.4.0.0 includes most of the production and economics PC Products from Landmark
Graphics integrated product suite. Specifically, Release2003.4.0.0 includes the following
applications:
ARIES
DSS
TOW/cs
Desktop-VIP, DIMS, and OpenWorks are also used in the AFS workflows, but they are not
covered in the AFS release notes. For more information on Desktop-VIP, DIMS, and OpenWorks,
refer to the latest version of individual product release notes.
Highlights of this release include:
Citrix-ready applications page 6.

New Integration Features on page 7.
New Point Product Features on page 11.
Citrix Ready Applications

Release2003.4.0.0 was tested with Citrix Metaframe XP. Individual applications should function
correctly in a Citrix environment. For Citrix Metaframe XP configuration information, refer to the
section on Citrix Metaframe XP Setup, page 68.
Page 6 of 91
July 2002
Landmark
New Integration Features

Dallas has a number of overall integration and installation improvements, as well as productspecific enhancements. The top integration enhancements include:
Common installation for all AFS products - ARIES and TOW/cs integration scripts are now
included on the installation CD.
Appropriate TOW/cs tables are automatically mapped using the DSS Project Creation Wizard.
Addition of a utility to synchronize TOW/cs and ARIES wells in Release2003.4.0.0 databases.
Less modification of flat files (ASCII), so that the same file may be used for import and export
between AFS products.
Well Groups are now recognized across the AFS product suite.
Implementation of DEX (data exchange) to bring wellbore data and workover histories from
DIMS into TOW/cs.
Support of common Third Party Products.
For a complete list of new features in each product, refer to individual product release notes.
Installation and Configuration
A common install was created for Release2003.4.0.0. This installation walks you through the
installation of ARIES, DSS, TOW/cs, and VIP. The database configuration process was also
improved for Release2003.4.0.0. The database creation utility leads you through the process of
either creating a script (Oracle) or attaching pre-defined databases (SQL Server). At the end of the
installation and configuration process, ARIES, TOW/cs, and DSS will be able to share data using
a common TOW/cs database.
Project Creation Wizard
The DSS Project Creation Wizard allows you to create an AFS workflow enabled project. If you
select an AFS project, the following TOW/cs tables are automatically visible in DSS:
Mapped Tables
VC_COMPLETION_RF (CompMaster)
CD_GROUP (Group Master)
CD_GROUP_MEMBER (ConfigMaster)
Linked Tables
VC_ARIES_WC_MM *
VC_ARIES_WC_DD *
AC_VIPDATA
Mapped Views
<VCV_PDM_DAILY_PROD>
<VCV_PDM_MONTHLY_PROD>
Page 7 of 91
July 2002
Landmark
<VCV_WELLBORE_RF>
Mapped Tables are visible because DSS automatically aligns the table with one of its own Master
Tables. Linked Tables allow you to view and edit data in a table, but the information in the table is
not directly aligned with a DSS Master Table. Mapped Views allow you to look at data in a table.
They do not allow you to write to a table.
Join Types
The following columns are added as default join types:
PROPNUM = PID
BORE_NAME = PID
WELL = PID
GROUP_SID = PID
GROUP_TYPE = PTYPE
MEMBER_SID = CHILD_PID
MEMBER_TYPE = CHILD_PTYPE
PROD_DT - DATE
DIMS Integration
In addition to integrating with TOW/cs, you also have the option to integrate with DIMS. When
you integrate with DIMS, the following views are created automatically:
<VCV_AFS_WORKOVERS>
<V_AFS_SURVEY>
<V_AFS_DOWNHOLEEQ>
<V_AFS_ZONES>
DIMS Views
DIMS Views are only compatible with DIMS 2003.0.1. They will not work
with other versions of DIMS.
Page 8 of 91
July 2002
Landmark
Well Synchronization Utility

The Well Synchronization Tool allows you to correlate wells created in ARIES, DIMS, and TOW/
cs. The tool allows you to map wells to or from TOW/cs and DIMS and from TOW/cs to ARIES
using an AFS integrated database. The Well Synchronization Utility is accessed from Start >
Programs > Landmark AFS > Utilities > Well Sync Utility.
In order to evaluate a drilling prospect, a well is created in ARIES or DIMS. Once the well is drilled
and goes on production, this same well shows up in TOW/cs. The TOW/cs well is a duplicate of
the first well, but does not contain the information from that well. Until now, there was no simple
method of synchronizing these two wells. The new Well Synchronization Tool allows you to map
the well information from one product to another. In addition, it allows you to filter wells based on
certain criteria.
During TOW/cs to ARIES synchronizations, new records are created with a TOW ID in userspecified ARIES tables within the TOW/cs database. New records are created in the ARIES
portion of the VC_COMPLETION_RF table that match the information from ARIES. Data must
be populated in both the TOW/cs tables and the ARIES tables prior to synchronization.
Existing records in the tables are not deleted. If you wish to delete information, you must do so
manually using an SQL command. During the TOW/cs to ARIES synchronization process,
information from the TOW/cs VC_COMPLETION_RF table, including TOW/cs ID, is written to
the following ARIES tables:
MP (Monthly production)
DP (Daily Production)
EC (Economic input)
EZ (Econ Summary)
OL (Econ Oneline Output)
DT (Econ Detail Output)
EM (Econ Monthly Output)
OW (Economic Ownership)
During TOW/cs to DIMS and DIMS to TOW/cs synchronizations, manually mapped well names
in the specified database are replaced with new well names.
Import/Export Formats
An AFS ASCII import/export file format was created for Release2003.4.0.0. This format allows
you to move data easily between AFS applications. This standardized AFS format can be used to
import data into DSS and ARIES. The format is also available with Desktop-VIP for
Release2003.4. The format is not available in TOW/cs.
Page 9 of 91
July 2002
Landmark
Common Well Groups

When pulling well data from TOW/cs into DSS and ARIES, it is often necessary to group the data
into more manageable assemblages. The subset of wells you are interested in may be connected by
workover type, reservoir, or some other similarity.
With Release2003.4.0.0, all well groups are created in a TOW/cs table, which is read by DSS and
ARIES. The TOW/cs CD_GROUP table is automatically mapped to the DSS Group Master table
by the Project Creation Wizard. The TOW/cs CD_GROUP_MEMBER table is automatically
mapped to the DSS ConfigMaster table. Groups are created in the same manner, but are now
accessible to both DSS and ARIES.
DEX
DEX, the Data Exchange Utility, allows you to share data across applications. With DEX, you
control which pertinent business objects are loaded. Pertinent objects are objects that directly effect
calculation results within an application, and they are usually a part of the applications processing.
DEX was implemented in Active Field Surveillance to move data from DIMS to TOW/cs. The
following types of data are moved from DIMS to TOW/cs:
Platform (VC_PLATFORM table)

Formation (VC_FORMATION table)
Field (VC_FIELD table)
Location (VC_LOCATION table)
Business Associate (VC_BA table and VC_BA_TYPE table)
Well Bore (VC_WELLBORE table)
Well Completion (VC_WELLCOMP table)
Well Completion Status (VC_COMP_STATUS table)
Page 10 of 91
July 2002
Landmark
Resolved PDEN_ID/Propnum Conflicts

DSS uses PDEN_ID as a unique constraint when linking with ARIES. Formerly, when a new well
was created in ARIES, PDEN_ID was set to zero. After creation of the first well, PDEN_ID was
no longer a unique constraint. For Release2003.4.0.0, ARIES has new property rules for creating
wells. When a new well is created in ARIES, the Data Source is set to ARIES and the PdenType
is set to ARE (ARIES Entity) or ARG (ARIES Group). This only applies to creation of new wells
and is not applicable to imported data.
New Point Product Features

The most important new point product features are described below. For a complete list of
individual product updates, refer the R2003.4.0.0 Release Notes for ARIES, DSS, and TOW/cs.
ARIES Reserve Management Suite (RMS)
The Reserve Management Suite is designed to track your reserve changes on a property basis.
Using RMS, you can define several booking proposals using economic and/or volumetric
calculations. After making your proposals, you can compare them to each other and to the previous
booked reserves prior to selecting one of the other proposals for booking. Once you select a
proposal, you can either book your properties separately or use the Mass Booking function to book
a group of properties.
ARIES RMS allows you to
Create several proposals for each property and reserve category.

Compare your proposals with each other or with the previously booked volumes.
Reconcile your reserves between two booking dates or two booking proposals. If the dates
between the two are different, RMS adjusts the data to a defined date, then calculates the
difference in reserves.
In order to correctly calculate the difference in reserves, you must correlate the names used for
production volumes in the Monthly Production Table, for monthly economic forecast data
stored in the Economic Monthly table, and for the name used for booking. RMS provides a
cross reference table to correlate this information.
Show the calculations between one booking date and the next prior to booking the reserves.
Show the changes in booked volumes on either a major phase or BOE basis for either gross or
net reserves.
Display an audit trail that shows how the reserves for a property changed for each booking
period.
Define your own revision codes.
Page 11 of 91
July 2002
Landmark
TOW/cs Zone Level Allocation (ZLA)

The Zone Level Allocation module adds the functionality required to allocate commingled string
production to the originating zones.
The Zone Level Allocation module offers the ability to:
Tie completion zones to commingled well strings on a date/time effective basis.

Tie completion zones to multiple commingled well strings at different times (i.e.; there may be
two or more strings in one well bore and it is possible that one zone could be produced through
more than one string over time).
Sum all allocation percentages for each product to 100%.
Modify previous allocation percentages and update historical production data. Reallocations
will not be necessary because string production has not changed.
To increase or decrease the number of zones associated with a string.
Integrate the reporting of commingled zone production with reporting for single zone
completions.
Page 12 of 91
July 2002
Landmark
Before You Install

Before installing Release2003.4.0.0, you should review these release notes entirely. The release
notes give you necessary information about:
the applications in Release2003.4.0.0
the hardware and operating systems on which you can run Release2003.4.0.0
product dependencies and unique product requirements
These release notes also give you information about product and workflow issues that surfaced
during the testing of Release2003.4.0.0. The installation information provided in this guide refers
to a greenfield installation. A greenfield installation is defined as an implementation where
none of the products in the AFS Suite are currently installed. In this case, all products are installed
and configured at one time. For instances other than greenfield, refer to individual product
release notes and user guides.
This section of the release notes contains information you need to know about the following topics:
Contents of the Release2003.4.0.0 CDs on page 14
System Requirements page 14
Product Dependencies on page 19
Page 13 of 91
July 2002
Landmark
Contents of the Release2003.4.0.0 CDs

Release2003.4.0.0 contains 5 volumes. The AFS CDs are as follows:
Release CDs (Box 2)
Volume 1: OpenBooksTM
Volume 2: Adobe Acrobat
Volume 3: LAM
Volume 15: Active Field Surveillance Installation (ARIES, DSS, TOW/cs)
Volume 17: Desktop - VIP
System Requirements
Release2003.4.0.0 was developed to run on the same hardware and operating systems as Oracle 8.
The following sections list specific requirements.
Hardware and Space Requirements
The platforms used during the certification of Release2003.4.0.0 are listed below. These
configurations include the installation of all Active Field Surveillance products (TOW/cs, ARIES,
and DSS). For information on individual product space requirements, refer to the Space
Requirements for Individual Applications section on page 16.
Servers
Recommended
Minimum
Windows 2000 Professional Server
Windows 2000 Professional Workstation
Pentium III
Pentium III
256 MB RAM or greater
VGA Color Monitor
VGA Color Monitor
106 key Windows ready integrated keyboard
MS-compatible mouse or pointing device
TCP/IP-based network connection 100Mbps
TCP/IP-based network connection minimum

10Mbps
2-4 GB or better SCSI disk space
2 GB SCSI disk space
1.44 MB, 3.5 Floppy Drive
CD-ROM drive
CD-ROM drive
Page 14 of 91
July 2002
Landmark
Clients
Recommended
Minimum
Windows XP, SR1
Windows 2000 Professional Workstation, SP2
800 MHz Pentium III processor
300 MHz Pentium II processor
VGA Color Monitor
VGA Color Monitor
TCP/IP-based network connection minimum

10Mbps
3 GB or better SCSI disk space
1.5 GB SCSI disk space
CD-ROM drive
CD-ROM drive
OpenWorks Servers
Recommended
Minimum
800 MHz Intel Pentium processor
2GB RAM or greater
VGA Color Monitor
VGA Color Monitor
101 AT-style Windows ready integrated keyboard
CD-ROM drive
CD-ROM drive
Page 15 of 91
July 2002
Landmark
OpenWorks Clients
Recommended
Minimum
Windows 2000 Professional
500 MHz Intel Pentium processor
512 MB RAM
VGA Color Monitor
VGA Color Monitor
CD-ROM drive
CD-ROM drive
Space Requirements for Individual Applications

You must have access to a CD-ROM drive to install Release2003.4.0.0 applications. Sufficient
disk space is also required. The following table lists the space requirements for each application.
For information on Desktop-VIP requirements, refer to the most recent version of the Desktop-VIP
Release Notes.
Size (in Megabytes)
Application
Minimum
Recommended
ARIES
50MB
500MB
DSS
200MB
500MB
TOW/cs
500MB
800MB
Total
750 MB
1.8 GB
Database Space Requirements

The disk space information provided above refers only to the space required
for the applications. It does NOT refer to database space requirements.
Page 16 of 91
July 2002
Landmark
Screen Resolution and Color Depth Requirements

Landmark recommends a screen resolution of 1280x1024 for Active Field Surveillance
applications. A minimum screen resolution of 1024x768 is required.
Landmark recommends 24-bit color. A minimum color depth of 16-bit is required.
Operating System and Third Party Upgrades
To better support new hardware platforms, improve performance, and increase stability, Landmark
has upgraded the operating systems and third party applications used to build our software. The
following table describes the operating systems (OS) and third party software upgrades supported
for ARIES, DSS, and TOW/cs versions in Release2003.4.0.0
Product/Package
Adobe Acrobat Reader
Windows 2000
Windows 2000
SP2
5.05
Windows XP
Windows XP
SR1
5.05
ComponentOne - Chart (Olectra)
7.0
7.0
ComponentOne - TrueDBGrid Pro
7.0b
7.0b
Crystal Reports
8.5
8.5
Data Dynamics - ActiveBar PRO
1.0.6.5
1.0.6.5
Desaware- SpyWorks
6.1 Pro
6.1 Pro
FarPoint - Spread
7.0 (Desktop - VIP 2003)

7.1 (Desktop - VIP 2003.4)
3.0
3.0
FarPoint - TabPro
3.1.1.0
3.1.1.0
FLEXlm
7.2e
7.2e
Infragistic - UltraToolBars
4.0
4.0
Inner Media - DynaZIP
4.0.0
4.0.0
INT
3.4
3.4
Internet Explorer
6.0
6.0
JET
4 SP6
4 SP6
List Collection - LC3 Tree
3.0
3.0
Mabry - Internet FTP Control
5.0.0.12
5.0.0.12
MDAC
2.7
2.7
Microsoft Office 2000
SP2
--
Microsoft Office XP
--
SR1
MS Access
Access 2000 SR2
Access XP SR1
MS MSDE
2.0 SP2
2.0 SP2
MS SQL Server
7.0 SP3/2000 SR2
--
Nutcracker
4.2a
4.2a
OpenGL
1.2
1.2
Oracle Client
8.1.7
9i
Certified OS
Exceed/Exceed 3D
Page 17 of 91
July 2002
Landmark
Oracle Server
8.1.6
--
PaTENT MPI Dev Kit
4.0.15
4.0.15
PaTENT MPI Runtime
4.0.15
4.0.15
Rogue Wave
6.0.4
6.0.4
SDI
5.3
N/A
Sheridan - Active ThreeD Plus
3.0.1.10
3.0.1.10
Sheridan - Active Toolbars
1.0.0.35
1.0.0.35
Sheridan - Active ListBar
1.0.0.24
1.0.0.24
Sheridan - Active TreeView
1.0.2.8
1.0.2.8
Sheridan - Data Widgets
3.1.2.15
3.1.2.15
Sheridan - Calendar Widgets
1.0.8.2
1.0.8.2
SoftTree - Softel vdm (Tree Control)
2.5
2.5
Software FX - Chart FX
3.0.35.0
3.0.35.0
Stingray - Objective Grid PRO
8.11
8.11
Stingray - Objective Grid Standard
6.0
6.0
Stingray - Objective Toolkit PRO
7.11
7.11
Stingray - Objective Toolkit Standard
6.0
6.0
TCL Library
8.2.3
8.2.3
Desktop-VIP
Desktop - VIP is not certifying as a part of the AFS release. It will release
separately in the third quarter of 2002. Exceed and Exceed 3D are only
required if running Desktop - VIP.
Operating Systems
The following operating systems and corresponding environments are certified by Landmark for
use with Release2003.4.0.0 on all platforms, regardless of whether the system is a client or a server.
Windows Server
Windows 2000 Server with Service Pack 2 (SP2)
Windows Client
Windows 2000 Professional with Service Pack 2 (SP2)
XP Client
Windows XP with Service Release 1 (SR1)
Page 18 of 91
July 2002
Landmark
Product Dependencies
Several of the applications found in Release2003.4.0.0 have dependencies on the order of
installation. The notes below outline phases of the installation process and specific requirements
encountered with subsequent application installations.
1. Upgrade the Operating System
2. Install Adobe Acrobat Reader, Exceed and Exceed 3D.
3. Install AFS product suite
Select Install Type (Local, Client, or Server)
Select Products
Select Server Location (Client Installation only)
Select Program Group
Review Summary Information
Finish Installation
4. Install Oracle or SQL Server Instance
5. Pre Database Creation Procedures
6. Create the Database
7. Post Database Creation Procedures
8. Configure ODBC
9. Configure Oracle Service Names (Oracle only)
10. Install LAM
Page 19 of 91
July 2002
Landmark
Installation
This part of the document describes the installation and configuration of ARIES, DSS, TOW/cs,
and Desktop-VIP, with the purpose of performing Active Field Surveillance. Active Field
Surveillance is defined here by two workflows, Squeezing the Sponge and Dynamic Reservoir
Management. For configurations other than the one here, refer to individual product release notes.
The Active Field Surveillance installation consists of:
Active Field Surveillance (AFS) Pre-Installation instructions
AFS Installation
Pre Database Configuration Procedures
Database Configuration
Post Database Creation Procedures
Workflows may be performed using an Oracle or Microsoft SQL Server database. The installation
and configuration of this database is covered in this document.
Page 20 of 91
July 2002
Landmark
Conventions Used in this Guide

Throughout the installation section, certain conventions are used in explaining how to install the
products for Active Field Surveillance. As a reference, a list is provided below:
Menu Options
Menu options and pushbutton names are

printed in boldface, for example, Next.
Type: red fault
Text that you are required to key in is printed

in a different typeface (Courier). Type
exactly what you see.
Type: project name A different typeface (Courier) in italics

indicates that you are to supply information.
At this instruction, for example, you would
type the name of your project.
Click on
Move the cursor to the option or object

specified and quickly press and release the
mouse button. Unless otherwise specified,
Button 1 is meant.
Highlight
In a selection box, move the cursor to the

filename you want to use and press Button 1
to select it.
Select
Move the cursor to the option or object you

want to select and click on it.
Double-click
Press Button 1 twice rapidly without moving

the mouse. The first press highlights the
option or object beneath the cursor; the
second press is equivalent to clicking on the
OK button to accept the selection.
Menu > Path
Bolded words separated by arrows indicate

the order in which you are to select menu
items. For example: Select File > Open
means you are to select File, then Open from
the menu.
Page 21 of 91
July 2002
Landmark
Prerequisites for AFS Installation

You must have the following CDs to install Active Field Surveillance:
AFS Common Install CDs
Desktop-VIP Installation CD
LAM Install CD
Adobe Acrobat CD
Previously Installed Products
This list of CDs assumes that Oracle or SQL Server are already installed
either locally or on a server. If they are not, you will need these CDs also.
Desktop - VIP
If installing Desktop - VIP, it is also necessary that Exceed and Exceed3D
be installed. For more information on Desktop - VIP installation, refer to the
individual product release notes.
The following Installation Guides are suggested when installing Active Field Surveillance:
LAM 2003.0 Guide
LAM 2003.0 - Windows
Desktop-VIP 2003 Release Notes or Desktop-VIP 2003.4 Release Notes
TOW/cs 2003.4.0.0 Release Notes and Installation Guide
DSS 2003.4.0.0 Installation Guide
ARIES 2003.4.0.0 Installation Guide

OpenBooks
All of the release notes and installation guides can be found on the
OpenBooks CD, Volume 1 in Box 2.
Page 22 of 91
July 2002
Landmark
System Requirements
Refer to the Before You Install section of these Release Notes on page 13 for complete list of
Hardware and Software Requirements. Active Field Surveillance must be installed on Windows
2000 or a combination of Windows 2000 and Windows XP.
Installing Hummingbird Exceed 7.0

Desktop - VIP Release2003 was certified by our testing department using ExceedTM 7.0 and
Exceed 3DTM 7.0. Exceed enables the remote display of UNIX products such as VIP on the
Windows 2000 or Windows XP desktop.
To learn more about remote display and Exceed, see the HummingbirdTM website:
www.hummingbird.com. Refer to the Desktop-VIP 2003.0.0 or the Desktop-VIP 2003.4 Release
Notes for information on installing and configuring Exceed.
Note
The configuration documented in the Desktop-VIP Installation Guide is the
only supported and tested configuration of Exceed.
Exceed 7.1 and Exceed 3D 7.1

Exceed 7.1 and Exceed 3D 7.1 should be used for Desktop - VIP
Release2003.4. At the time of this release, Desktop - VIP
Release 2003 is the available version.
Page 23 of 91
July 2002
Landmark
Installing Oracle or SQL Server

You must have an installation of Oracle or SQL Server in order to complete the Active Field
Surveillance full installation. The AFS Workflows require Oracle 8.1.6 Server and Oracle 8.1.7
Client on Windows 2000. Oracle 9i is required for Windows XP. Installation instructions for
installing Oracle appear in the OpenWorks 2003 Installation Notes for Windows (part of the
OpenWorks System Administration set of manuals). Please read the entire Installing Oracle
manual before attempting this install.
Note
Digital versions of the most recent documents (including the Installation
Guide and Release Notes) are on the OpenBooks CD.
Install AFS Product Suite

All Release2003.4.0.0 products may be installed from the AFS Common Install CD. Please consult
the individual point products release notes for any unique product installation requirements.
Important
Individual product release notes are located on the OpenBooks CD.
Warning
The user interface for Desktop-VIP must be installed and run from the
Windows 2000 platform. To run the Desktop-VIP reservoir simulator on a
UNIX platform, special post-installation steps must be taken. Please consult
the Desktop-VIP Release Notes for detailed installation instructions.
The install program provides two setup options:
Direct install from the CD
Install from a network-staging area.
After initial installation and setup of TOW/cs and its components, the selected database must be
installed and populated with data. For further information on installing and operating TOW/cs,
refer to TOW/cs 2003.4.0.0 Release Notes.
Page 24 of 91
July 2002
Landmark
Begin the Installation

Landmarks new AFS Common Install provides a consistent GUI-based interface for installing
ARIES, DSS, and TOW/cs on CD-ROM. After you specify the programs to be installed and the
directories in which to install them, the program provides a graphical status display of the
installations progress.
1. Disable your virus checking software.
2. Insert AFS CD 1 into the CD-ROM drive. The installation program runs in auto-startup mode.
If it does not, manually run setup.exe from the CD.
Page 25 of 91
July 2002
Landmark
3. Click Continue. The Volume 15 Installation Screen appears.
4. Click Install. The Active Field Surveillance splash screen and installation progress bar
appear.
Page 26 of 91
July 2002
Landmark
5. If your screen resolution is set to 800X600 or below, you will receive the following warning:
Clicking No will cancel the installation. If you wish to continue the installation with the
current screen resolution, click Yes.
6. A warning appears indicating that you need to disable your virus checker. Disable your virus
protection software and continue. Click OK.
Internet Explorer 6.0

You must have Internet Explorer 6.0 to install AFS. Refer to page 17 for a
complete list of supported third party products.
Previous AFS versions of ARIES, DSS, and TOW/cs

If ARIES, DSS, or TOW/cs already exist on the machine, the installation
provides information on what products are installed. You are prompted to
Modify, Repair, or Remove these programs. Landmark suggests that you
remove previous versions of these products before installing the AFS
Product Suite.
Page 27 of 91
July 2002
Landmark
7. If you have pre-AFS versions of ARIES or TOW/cs, you must remove them before installing
AFS. It is possible to install DSS with pre-AFS versions of DSS.
If previous versions exist on your machine, you are prompted with the following message.
Click OK.
You are prompted to remove each of the products. Select Yes. The product is removed from
your machine. Click OK to finish.
If you do not remove the products, the installation will continue. However, if you attempt
to install pre-AFS versions of TOW/cs and/or ARIES, the installation will abort.
8. The Welcome screen appears. Click Next.
Page 28 of 91
July 2002
Landmark
9. The Customer Information screen appears. Verify or change the information and click Next.
10. Select the Install Type (Client, Local, or Server). The remainder of the installation process
will vary, depending on the Install Type you select. Read the information below and follow the
instructions for either Local, Client, or Server (on the following pages).
Server Installation
The Server Installation installs components for the network server. These components include
executables (.exe) and dynamic link libraries (.dll). In a Server Installation, no changes are made
to the Windows System Directory and no applications may be run from the Server at the end of the
installation. A client installation installs additional components that allow the applications to run.
In the Landmark AFS server installation, only DSS and ARIES can be installed. TOW/cs and
Desktop - VIP require a local installation.
Client Installation
In a networked environment utilizing server components, the client installation installs the
necessary components for applications to run. These components include system files, database
files and shortcuts to the executable. The Client installation should occur after the Server
installation. Applications are run on the client machine, but executables are located on the server.
In the Landmark AFS Client Installation, you must supply the server location for AFS applications.
Only DSS and ARIES can be installed using the client installation. TOW/cs and Desktop - VIP
require a local installation.
Local Installation
The Local Installation installs all components. This is often referred to as a standalone system
because all programs run locally. All Landmark AFS products can be installed locally.
Page 29 of 91
July 2002
Landmark
Local Installation
1. In this installation, use the Local configuration click Next.
2. Choose the appropriate destination for Active Field Surveillance applications. Click Next.
Page 30 of 91
July 2002
Landmark
Select Products to Install

Because you selected the Local option (above), you have the option to install TOW/cs, ARIES,
and/or DSS.
3. When the Select Components dialog appears, ARIES, DSS, and TOW/cs are already checked.
Select all of the components. Click Next.
If you have pre-AFS versions of ARIES or TOW/cs and you select these products for
installation, a message appears indicating that the installation will abort. At this point you must
restart the installation and remove pre-AFS versions of the products you wish to install.
Unselected ARIES Components

RMS and Decision Suite are purchased separately from the standard ARIES
set of components, so they are not automatically checked when you select
ARIES. To select RMS and Decision Suite you must expand the ARIES set
of components and select them individually.
In addition, OpenWorks and Canadian Economic Version files are not
automatically checked. If you wish to select these components, you must
expand the components list in ARIES and select them.
Page 31 of 91
July 2002
Landmark
Desktop-VIP Installation
In order to install Desktop-VIP, you need a separate installation CD. If you
select Desktop-VIP from the Select Components list, be prepared to insert
the Desktop - VIP CD at the end of the AFS Installation.
MDSE
MSDE should be selected if you wish to install the reporter database for
TOW/cs.
OpenWorks Files
ARIES allows you to install OpenWorks files. If you set up ARIES with
OpenWorks, some ARIES functionality is replaced by OpenWorks and no
longer available from ARIES. For more information, refer to the ARIES
Release Notes.
Page 32 of 91
July 2002
Landmark
Install Products
The AFS installation wizard uses default values to install DSS. Follow the instructions below to
install the TOW/cs and ARIES portions of AFS on the current computer.
4. The TOW/cs Shared Reports select language version screen appears. Select the appropriate
language and click Next.
5. The Select Office Directory dialog appears. Point to the location of your Microsoft Office
installation and click Next.
Page 33 of 91
July 2002
Landmark
6. The Select Program Folder screen appears. Click Next.
7. The Start Copying Files screen appears.Click Next.

8. The Setup Status screen appears. Setup begins installing the components and supporting files
required to complete the installation process. As TOW/cs and its components are being
installed, the bar graph indicator will begin to cycle, confirming that installation is
proceeding.
9. A message appears indicating that MDAC is installed with TOW/cs.
Page 34 of 91
July 2002
Landmark
10. Next, a message appears indicating that MSDE is being installed.

MSDE and SQL Server
MSDE cannot be installed if an installation of Microsoft SQL Server exists
on the machine.
11. A reminder about installing Adobe Acrobat appears. Click OK.
12. Information about installing Desktop-VIP appears. If you wish to install Desktop - VIP, select
Yes to continue. To continue the Desktop - VIP installation, refer to page 45.
13. You must reboot your computer before attempting to use Active Field Surveillance.
Page 35 of 91
July 2002
Landmark
Server Installation
1. In this installation, use the Server configuration click Next.
Server Location
Your server location must be shared with other users in order to function
properly. To share, right click on the folder and select Properties. Select the
Sharing tab and toggle ON Share this folder.
Page 36 of 91
July 2002
Landmark

Because you selected the Server option (above), you have the option to install ARIES and/or DSS.
When the Select Components dialog appears, select the components you wish to install and
click OK. In this example, all options are selected. If you do not select all products, you will
not see all of the screens in the Install section.
If you have pre-AFS versions of ARIES and you select ARIES for installation, a message
appears indicating that the installation will abort. At this point you must restart the installation
and remove pre-AFS versions of the products of ARIES.
Page 37 of 91
July 2002
Landmark
Unselected ARIES Components

RMS and Decision Suite are purchased separately from the standard ARIES
set of components, so they are not automatically checked when you select
ARIES. To select RMS and Decision Suite you must expand the ARIES set
of components and select them individually.
In addition, OpenWorks and Canadian Economic Version files are not
automatically checked. If you wish to select these components, you must
expand the components list in ARIES and select them.
TOW/cs, MSDE, and Desktop - VIP

TOW/cs, MSDE, and Desktop - VIP are not available under the Server or
Client options. To install TOW/cs, MSDE, and/or Desktop - VIP, you must
select the Local option.
OpenWorks Files
Release Notes.
AFS Utilities
DEX and Well Sync Tool Utilities are only available in Local and Client
installations.
Page 38 of 91
July 2002
Landmark
Install Products
The AFS installation wizard uses default values to install ARIES, DSS, and TOW/cs. Follow the
instructions below to install AFS on the current computer.

required to complete the installation process. As the AFS components are being installed, the
bar graph indicator will begin to cycle, confirming that installation is proceeding.
Page 39 of 91
July 2002
Landmark
Client Installation
1. In this installation, use the Client configuration click Next.
Page 40 of 91
July 2002
Landmark

Because you selected the Client option (above), you have the option to install ARIES and/or DSS.
3. When the Select Components dialog appears, select the components you wish to install and
click OK. The screens below reflect the selection of all products. If you do not select all
products, you will not see all of the screens in the Install section.
If you have pre-AFS versions of ARIES and you select ARIES for installation, a message
appears indicating that the installation will abort. At this point you must restart the installation
and remove pre-AFS versions of ARIES.
RMS and Decision Suite

RMS and Decision Suite, part of the ARIES set of components, are not
automatically checked when you select ARIES. To select RMS and
Decision Suite you must expand the ARIES set of components and select
them individually.
Page 41 of 91
July 2002
Landmark
TOW/cs, MSDE, and Desktop - VIP

TOW/cs, MSDE, and Desktop - VIP are not available under the Server or
Client options. To install TOW/cs, MSDE, and/or Desktop - VIP, you must
select the Local option.
OpenWorks Files
Release Notes.
Page 42 of 91
July 2002
Landmark
Install Products
The AFS installation wizard uses default values to install ARIES and DSS. Follow the instructions
below to install AFS on the current computer.
4. The Landmark AFS Server Location screen appears. Select the location of the server and click
Next. Remember, the server you select must be shared.
Page 43 of 91
July 2002
Landmark
required to complete the installation process. As the AFS components are being installed, the
bar graph indicator will begin to cycle, confirming that installation is proceeding.
Page 44 of 91
July 2002
Landmark
Install DESKTOP-VIP
1. Desktop - VIP is only available if you selected the Local option. To load Desktop - VIP you
must be logged in as administrator. Log off of the machine and logon as administrator.
2. Insert the DESKTOP-VIP CD into the CD-ROM drive. Click OK to install.
3. Refer the Desktop-VIP 2003 or the Desktop-VIP 2003.4 Release Notes for complete
instructions on installing Desktop-VIP.
Desktop-VIP Release Notes and Installation Guide
The latest version of the Desktop-VIP Release Notes and Installation Guide
is found on the OpenBooks CD (Volume 1 in Box 2).
Desktop-VIP on Windows XP
Desktop - VIP is not available on Windows XP. For a complete list of
compatible operating systems, refer to the Desktop - VIP release notes and
installation guide.
Page 45 of 91
July 2002
Landmark
Pre-Database Creation Procedures

It necessary to follow the steps below before installing the database. The databases may be Oracle
or SQL Server, but all must be maintained on Windows 2000. Instructions for setup on Oracle and
SQL Server are outlined below.
Set Up TOW/cs on an Oracle Instance

This section describes the process for creating an Oracle TOW/cs database. Oracle installation
should be done by your companys database administrator, or by Landmarks Solutions Delivery
Organization. The following specific information is detailed within this section.
Determining tablespace and table creation
Loading initial data and converted data into TOW/cs
Before You Begin

Before you begin creating the Oracle data, you must know the following:
Instance Name (Sid or Server Name)
Login Name (SYS) and password (DBA)
Oracle home directory [ORANT]
Oracle DBF directory [/Database/Sid]
The following diagram describes the installation process of the TOW/cs Oracle database.
Install
AFS
Create Oracle
Instance
Create
Tablespaces
Create
Tables
Page 46 of 91
July 2002
Landmark
Install Oracle
If you do not have Oracle installed, install it at this time.
Create new tablespaces
After installing Oracle, you create tablespace(s). If you installed both ARIES and TOW/cs, you
must run two scripts. If you installed only one of the applications, you only need to run one of the
scripts. The TOW/cs script is located in the Products\AFS\Install\DB\TOWcs\Oracle\tablespaces
directory on the AFS CD. The ARIES script is located in the
Products\AFS\Install\DB\ARIES\Oracle\tablespaces directory on the AFS CD.
1. Run TOWSPC.SQL if you installed TOW/cs.
2. Run ARIESPC.SQL if you installed ARIES.
Page 47 of 91
July 2002
Landmark
Setup TOW/cs on SQL Server

The following diagram describes the steps necessary to install TOW/cs on SQL Server.
Install
AFS
Install SQL
Server
Configure
SQL Server
Create
Database
Copy AFS
Database
Prior to installing TOW/cs, you must create and setup the TOW/cs database. To install the TOW/
cs database environment for Microsoft SQL Server, the following tasks must be completed and are
covered in this section:
Install SQL Server. This step is usually done by the on-site DBA.
Configure Server. TOW/cs will not work without changing the default configuration of nested
triggers.
Install SQL Server Client, TOW/cs and setup ODBC.

Installing Microsoft SQL Server TOW/cs Database
TOW/cs requires installation of Microsoft SQL Server on the server and clients. This installation
is usually done by the Clients DBA. If you have not installed SQL Server, please do so now.
Configure Server
The following changes to the server configuration options are required by TOW/cs. Landmark
recommends that TOW/cs be installed on its own database server to prevent possible conflicts with
other databases.
1. Start SQL Server Enterprise Manager (from server or client machine).
2. Select server and log in (as system administrator).
Page 48 of 91
July 2002
Landmark
3. Highlight the server and select Tools > SQL Server Configuration Properties.
4. The SQL Server Properties form appears. Click the Server Settings tab.
5. Uncheck the default for Allow triggers to be fired which fire other triggers (nested triggers)
box.
6. Click Apply.
Changes
For changes to take effect, stop SQL Server and restart.
Setup ARIES on Oracle

The setup for running ARIES on Oracle requires that an Oracle instance be installed. If you setup
TOW/cs on Oracle, this process is complete. If not, you must install and configure your Oracle
instance at this time. For information on installation and configuration of Oracle, refer to page 46.
If your Oracle setup is complete, you are ready to create your database. Proceed to AFS Database
Configuration on page 50.
Setup ARIES on SQL Server

The setup for running ARIES on SQL Server requires that SQL Server be installed. If you setup
TOW/cs on SQL Server, this process is complete. If not, you must install SQL Server at this time.
For more information on installation and configuration of SQL Server, refer to page 49. If your
SQL Server setup is complete, you are ready to create your database. Proceed to AFS Database
Configuration on page 50.
Page 49 of 91
July 2002
Landmark
AFS Database Creation

Release2003.4.0.0 facilitates database creation with the db_create.exe utility. This utility does one
of two things:
For Oracle, db_create creates a master script which runs a series of scripts that create the
database. For information on manually creating the database, refer to the
\Products\AFS\Install\DB\readme.txt
For SQL Server, db_create attaches a starter database to the existing instance of SQL Server.
You may run the database creation utility locally, or from a remote machine. If you run the utility
remotely, you must have access to the executable and to database files.
1. To create the database, navigate to \Products\AFS\Install\DB on the AFS CD and double-click
db_create.exe.
2. Select Oracle or SQL Server and click Start. The rest of database creation depends upon the
option you select. Follow the instructions on the following pages for Oracle Database
Creation (page 51) or SQL Server Database Creation (page 55).
Page 50 of 91
July 2002
Landmark
Oracle Database Creation

1. A message appears indicating that the utility will create a master script that is needed to build
the database. Click Yes.
2. Select product database you wish to install. The script created depends on your selection. For
the AFS workflows, select TOW/cs with ARIES Integration. Press Continue.
Database Creation from a Location other than the CD

If you are running the database creation from a location other than the CD,
you must indicate where the TOW/cs Database Directory
(Products\AFS\Install) is located. Another dialog appears asking you to
Browse to the location of this directory, which must be mapped.
Page 51 of 91
July 2002
Landmark
3. The Select directory to create script in dialog appears. The script, CreateDB.SQL, and all log
files created by the script are placed in this directory. Select the target directory for database
files and click OK.
Creating the CreateDB.SQL File on a Server

If you wish to create the CreateDB.SQL file on a server, you must use a
mapped drive to navigate to the location.
4. You are prompted to create an ADMIN schema. If a schema owner does NOT already exist,
select Yes.
Existing Schemas
If you have an existing schema that you wish to use, select No when you are
asked to create an ADMIN schema. You are prompted to enter the name of
the existing schema.
Page 52 of 91
July 2002
Landmark
5. You are prompted for an admin username. The user is created with a default password that
matches the username.
Changing the Password

The password may be changed in one of two ways:
- Change the password by editing the master script. Run the script.
- Run the script and then issue the alter user command.
6. The script is created. Click OK.
Additional Script Information

The script you create runs existing scripts found on the installation CD. You
should familiarize yourself with the script before running it. For additional
information, refer to the script itself.
7. The original Database Schema Creation Wizard appears. If you wish to create another
database, click Start. If you wish to close the dialog, click Close.
8. Open a command prompt. Navigate to the location of the script and execute it.
Page 53 of 91
July 2002
Landmark
Running the Script from Locations Other than the Server/

Multiple Oracle databases
1. If you are running the script from a location other than the server or if
you have multiple Oracle databases on one machine, you will need to
change the connection string. The script should include the instance
name if you are not running it from the server.
Example:
connect towadmin/towadmin
should be changed to
connect towadmin/towadmin@instancename
2.
In addition, you need to update the location of log files within the
script. To manually change the location of log files, edit the script with
a text editor. Log files exist at each instance in the script where
something is created.
Page 54 of 91
July 2002
Landmark
SQL Server Database Creation

1. A message appears indicating that the utility will attach a starter database to an instance of
SQL Server. Click Yes to continue.
Database Creation from a Location other than the CD

If you are running the database creation from a location other than the CD,
you must indicate where the database (.mdf) files are located. Another
dialog appears asking you to Browse to the location of this directory.
2. The Select database target directory dialog appears. Indicate the directory location for the
SQL Server starter database (.mdf and .ldf files). The location will vary depending on the type
of database you wish to install. You have 5 options:
ARIES only - Products\AFS\Install\DB\Aries\SQLServer\DB\ariesdb.mdf

ARIES and RMS - Products\AFS\Install\DB\Aries\SQLServer\DB\ariesrms.mdf
TOW/cs only - Products\AFS\Install\DB\TOWcs\SQLServer\DB\TOWDB.MDF
TOW/cs with ARIES Products\AFS\Install\DB\TOWcs\SQLServer\DB\TOWAriesDB.mdf
TOW/cs with ARIES and RMS Products\AFS\Install\DB\TOWcs\SQLServer\DB\TOWAriesRMS.MDF
Page 55 of 91
July 2002
Landmark
Select the database location and click OK.
Copying the Database on a Remote Machine

If you wish to copy the database to a remote machine, you must use a
mapped drive to navigate to the location. In addition, the remote location
must be running the SQL Server Engine. If the machine is not running a
SQL Server Engine, the database is copied to the specified directory but
cannot be attached properly. For instructions on manually attaching the
database, refer to the Readme.txt file in the Products\AFS\Install DB
directory.
3. You are prompted to enter a database name. Accept the default or enter the desired name of
your database. Click OK.
Installing the Database on a Remote Machine

The database creation utility recognizes that your database is not located on
a local drive. In this event, you must also enter the full path to the database
and the name of the SQL Server instance.
Page 56 of 91
July 2002
Landmark
4. Database files are copied from the install CD to the location you specified in Step2. You are
prompted to enter the SQL Server system administration password. Enter the password
and click OK.
This allows the utility to attach the database to the SQL Server Enterprise Manager.
SA Password
If you choose not to enter the SA password at this time, the database is still
copied to the specified directory. You can attach the database at a later time
using SQL attach commands and the Query Analyzer. For more information
on these commands, refer to the Readme.txt file in the
Products\AFS\Install\DB directory.
Page 57 of 91
July 2002
Landmark
Post Database Creation Procedures

The following are post-installation steps for ARIES and TOW/cs.
Post-TOW/cs Database Configuration

Create Additional Users/Roles
The Database Creation utility will create the database owner, if you select this option. The utility
also creates three roles for TOW/cs: TOW_ADMIN (administrative privileges), VCR_INQUIRY
(SELECT privileges only), VCR_UPDATE (INSERT, DELETE, SELECT, and UPDATE
privileges). If you need other users/roles, you must create them manually. For information on
adding users and roles, refer to the Welcome to TOW/cs chapter of any TOW/cs User Guide.
Configure TOW/cs Options
1. From the TOW/cs group, double-click on the Utilities icon to start the application.
2. Select Tools > Options. The System Options dialog appears. This dialog contains several
important pointers used by TOW/cs.
3. Verify that the correct log file and message files have been selected under Error Message
Level. Use the drop-down arrow to select the correct level.
Page 58 of 91
July 2002
Landmark
Post ARIES Database Configuration

Populate User Tables in ARIES
User Tables for the ARIES database were created by the installation scripts using a set of standard
items. The database columns can be tailored to your needs by your dba. No values were populated
for any of these items. To populate these tables, use one of the following options:
Manually create properties and fill in the items you want using the table editor. For more
information on using the table editor, refer to ARIES on-line help.
Use IHS, Accumap, or other commercial data vendor import routines to create new properties
and bring in the associated data values.
Use the ARIES Data Transporter to transport data values from an existing ARIES database into
the new database. For more information on the Data Transporter, refer to ARIES online help.
Create Additional Users/Roles
The Database Creation utility will create the database owner, if you select this option. The utility
also creates one role for ARIES: ARIESROLE (administrative privileges). If you need other
users/roles, you must create them manually. For information on adding users and roles, refer to the
ARIES Conversion Utility chapter of the ARIES User Guide.
Modify ARIES Reporting Database
You must use the AFS ARIES Reporting Database in order for ARIES to function properly in an
AFS environment. The Database (AFSREP32.mdb) is located in the
Products\AFS\Install\UnsupportedTools\Aries directory. First, copy the file to your
Landmark\AFS\ARIES\DB directory.
Next, modify the Aries Reports ODBC Connection so that it points to the AFSREPORT.mdb file.
Page 59 of 91
July 2002
Landmark
Changing the Aries Reports ODBC Connection

1. Select Start > Settings > Control Panel.
2. Select Administrative Tools and Data Sources (ODBC).
3. When the ODBC Data Source Administration dialog appears, select Aries Reports and click
Configure. The ODBC Microsoft Access Setup dialog appears.
Page 60 of 91
July 2002
Landmark
4. Click Select. Choose the AFSREP32.mdb database and click OK.
5. Select OK in the ODBC Microsoft Access Setup dialog. Click OK in the ODBC Data Source
Administrator dialog.
DIMS Database Configuration

If you are using DIMS with AFS, you must do the following:
1. Create an AFS_VIEW role in the Oracle/SQL Server database.
Open the MS SQL Server Enterprise Manager

Highlight the database and select Roles.
Right-click and select Create New Role.
Type AFS_VIEWS as the role name and click OK.
The Add Role Members dialog appears. Give this role to each user who will be using the
views and click OK.
The AFS_VIEWS role should have the following privileges:
SELECT V_AFS_BOREMASTER
SELECT V_AFS_DOWNHOLEEQ
SELECT V_AFS_SURVEYS
SELECT V_AFS_WORKOVERS
SELECT V_AFS_ZONES
2. Run the AFS_DIMS_VIEWS.sql script on the DIMS database you are using.
DIMS
Only DIMS Release2003.0.1 can be used with Active Field Surveillance.
The AFS_DIMS_VIEWS.sql script is available on the DIMS 2003.0.1 CD.
Page 61 of 91
July 2002
Landmark
This script creates the following DIMS views:
V_AFS_BOREMASTER
V_AFS_DOWNHOLEEQ
V_AFS_SURVEYS
V_AFS_WORKOVERS
V_AFS_ZONES
Page 62 of 91
July 2002
Landmark
Configure ODBC
ODBC for Oracle
If you are using an Oracle database, you must connect to the database using either the Microsoft
ODBC or Oracle ODBC driver. Instructions for setting up the drivers are given below. You must
know the following to configure the ODBC:
Data Source Name
User Name
Server Location
Microsoft ODBC
1. For Windows 2000, choose Start > Settings > Control Panel > Administrative Tools and
double click Data Sources (ODBC).
2. Click Add, choose the Microsoft ODBC for Oracle and click Finish. The Microsoft ODBC
for Oracle Setup screen will be displayed.
3. Type in:
Data Source Nameanything that identifies the data source to you.
Descriptionan option for further identification.
User Namean option that identifies the user.
ServerThe TNS Service Name for the Oracle Server you want to access.
4. Click OK.
Page 63 of 91
July 2002
Landmark
Oracle ODBC
double click Data Sources (ODBC).
2. Click Add, choose the Oracle ODBC driver.
3. Click Finish. The Oracle 8 ODBC Driver Configuration screen is displayed.
4. Enter the following information in the dialog:

Data Source Namethe same as the Microsoft data source name with _batch added as the
suffix. (ex: ts8a_batch).
Descriptionan option for further description.
Service Namethe location of the Oracle database from which the ODBC driver will
retrieve data.
User IDan option that identifies the user.
Defaults
Defaults should be used in the lower portion of the screen.
Page 64 of 91
July 2002
Landmark
Oracle 9i
If you are using Windows XP, Oracle 9i should be used.
TOW/cs Batch
TOW/cs requires an additional ODBC connection for its Production
Accounting Module. This connection should be named tow_batch.
5. Click OK to finish the setup.
Page 65 of 91
July 2002
Landmark
ODBC for SQL Server

You must also create an ODBC connection if using SQL Server. The instructions for creating this
connection are outlined below. You need the following information to setup the ODBC connection
for SQL Server:
Data Source Name

SQL Server Name
double click Data Sources (ODBC)
2. Click Add. Select the SQL Server driver.
3. Enter the data source Name and the SQL Server name. Click Next.
Page 66 of 91
July 2002
Landmark
4. Configure settings as shown below.
5. Click Next. Select the default database and click Next.
6. Select Finish. The ODBC Connection for SQL Server is complete.
Page 67 of 91
July 2002
Landmark
Configure Oracle Service Name

If you are using Oracle, you must also configure a service name in your tnsnames.ora file. You will
need to know the following to configure the Service Name:
Service Name
Host Name
Username/Password
1. Select Start > Programs > Oracle - Oracle Home > Network Administration > Net 8
Configuration Assistant.
2. Select Local Net Service Name Configuration. Click Next.
3. Select Add and click Next.
Page 68 of 91
July 2002
Landmark
4. Select Oracle8i database or service and click Next.
Oracle 9i
If you are using Windows XP, Oracle 9i should be used.
5. Type the Service Name and click Next.
6. Select the appropriate protocol and click Next.

7. Type the Host Name and click Next.
Page 69 of 91
July 2002
Landmark
8. Select Yes, perform a test and click Next.
9. Enter the appropriate username/password and click OK. When the test is successful,
click Next.
10. Enter the Net Service Name (if different from the Service Name) and click.
11. Select No and click Next.
12. Select Next and Finish to close the Net 8 Configuration Assistant.
Page 70 of 91
July 2002
Landmark
Citrix Metaframe XP Setup

Release2003.4.0.0 is certified on Citrix Metaframe XP. All applications should function properly
if the following setup is performed.
Inside the Firewall Citrix Metaframe XP Setup

Release2003.4.0.0 applications are certified on Citix inside a firewall. The following configuration
is recommended:
Windows XP or Windows 2000 client
Windows 2000 FLEXlm license server

Scripts
For ARIES to function correctly, several Citrix Metaframe XP configuration scripts must be run.
These compatibility scripts set up the ARIES user environment. In order to avoid sharing/
overwriting problems, the scripts provide each user with an individual workspace while working
with ARIES.
Applying the Citrix Metaframe XP Compatibility Scripts
1. Create a directory to store the scripts (e.g. Citrix Batch).
2. Copy the script files to the directory (Acsr.exe, Regini.exe).
Contact Support for Scripts
Citrix Metaframe XP configuration scripts are not included on the AFS
CDs. Please contact your local support representative for scripts.
3. Create a subdirectory within the initial directory named template.

4. Copy the aries.key and ariesall.key files into the template directory. Aries.key and aries.all are
used in conjunction with the ascr.exe utility. These files insert the necessary registry entries
for ARIES to function properly in a multi-user Citrix Metaframe XP environment.
If AFS is not Installed on C:\Landmark
If your AFS applications are not installed on C:\Landmark, you need to edit
the scripts so that they point to the location of your installation.
Whenever ARIES is used in the Citrix Metaframe XP environment, it should be launched using the
scripts instead of the program executable. The first time ARIES is run in this manner, all
Page 71 of 91
July 2002
Landmark
directories, paths, and registry entries are created. If anything is moved, the path to the scripts must
be revised.
Page 72 of 91
July 2002
Landmark
Citrix Metaframe XP Setup for Landmarks Data and Application

Management Solution (Outside the Firewall)
Scripts
For ARIES to function correctly, several Citrix Metaframe XP configuration scripts must be run.
These compatibility scripts set up the ARIES user environment. In order to avoid sharing/
overwriting problems, the scripts provide each user with an individual workspace while working
with ARIES.
Applying the Citrix Metaframe XP Compatibility Scripts
1. Create a directory to store the scripts (e.g. Citrix Batch).
2. Copy the script files to the directory (Acsr.exe, Regini.exe).
Contact Support for Scripts
Citrix Metaframe XP configuration scripts are not included on the AFS
CDs. Please contact your local support representative for scripts.
3. Create a subdirectory within the initial directory named template.

4. Copy the aries.key and ariesall.key files into the template directory. Aries.key and aries.all are
used in conjunction with the ascr.exe utility. These files insert the necessary registry entries
for ARIES to function properly in a multi-user Citrix Metaframe XP environment.
If AFS is not Installed on C:\Landmark
If your AFS applications are not installed on C:\Landmark, you need to edit
the scripts so that they point to the location of your installation.
Whenever ARIES is used in the Citrix Metaframe XP environment, it should be launched using the
scripts instead of the program executable. The first time ARIES is run in this manner, all
directories, paths, and registry entries are created. If anything is moved, the path to the scripts must
be revised.
ICA Connections
Release2003.4.0.0 applications were certified on Landmarks Data and Application Management
Solution, a comprehensive data, information, and application hosting service for E&P enterprises.
ICA Connections can be generated individually, using Custom ICA Connections, or together,
using the Application Set Manager. To use the Application Set Manager all applications must be
published from the server. Refer to the sections below for setup of Custom ICA Connections and
the Application Set Manager.
Page 73 of 91
July 2002
Landmark
Custom ICA Connections

One way to setup the Citrix Metaframe XP connection is to add Custom ICA Connections for each
application. Follow the steps below to setup a Custom ICA Connection:
1. From your Citrix Program Neighborhood, select Custom ICA Connections > Add ICA
Connection.
2. Select Local Area Network and click Next.
3. Enter a description for the ICA Connection. Select TCP/IP as the Network Connection.
Toggle ON Published Application and browse to select the application you wish to use.
4. Select Server if the application is not published. If the application is already published, select
Published Application. If you need to identify the location of the server, the dialog below
appears. Enter the appropriate information and click OK.
Page 74 of 91
July 2002
Landmark
5. Click Next.
6. Select to View the application in a separate window or a remote desktop window. Click Next.
7. Use the Default Encryption level. Click Next.
8. Enter a username/password and domain for the connection. Click Next.
9. Set Window Colors to 256 Colors. Click Next.
10. Click Finish to complete the ICA Connection setup.
Page 75 of 91
July 2002
Landmark
Application Set Manager Connections

The Application Set Manager is another way to setup Citrix Metaframe XP Connections. To view
applications, they must first be published to a server.
1. From your Citrix Program Neighborhood, select Application Set Manager > Find New
Application Set.
2. Select the type of connection and click Next.
3. Enter a description for the new application set.

4. Select Server Location to identify the location. Enter the location of the server and click
Next.
Page 76 of 91
July 2002
Landmark
5. Accept or override the default display options. Click Next.
6. Click Finish to setup the application.
Page 77 of 91
July 2002
Landmark
Install LAM
Introduction
Licensing allows controlled use of Landmark applications in a networked environment. When you
license a Landmark application, you also purchase one or more licenses. The number of licenses
determines the number of users who can access the application simultaneously. The license system
should be transparent to the user and, once installed, require minimal configuration and
maintenance by the network administrator.
The License Application Manager (LAM) is based on GLOBEtrotter Softwares (http://
www.globetrotter.com) updated Flexible License Manager (FLEXlm) v7.2.e technology. The LAM
Server software must be installed and configured as part of the installation process as previous
FLEXlm server versions will not work with this release. This should be completed before installing
any point product.
A detailed guide for managing LAM on Windows appear in the LAM 2003.0 Guide. The LAM
Guide and the UNIX and Windows Release Notes are included on the OpenBooks CD. Please read
these documents before attempting the install.
Note
Before installing LAM Release2003 server, please uninstall all existing
previous versions of LAM servers.
FLEXlm is the Only Supported License Manager

If you are running older versions of ARIES, DSS, or TOW/cs that use
previous bitlock, Netsecur, or HASP methods, you must update your
existing licenses to FLEXlm for this release.
Every Release2003 application requires a Release2003 license to run. The process for obtaining
and installing a license is discussed in the next section.
Note
The Network License Administrator (NLA) is not available for
Release2003.0. The following files will not be supplied for Release2003.0:
nla nlacheck nlademo nlatrimlog nla.exe nlacheck.exe nlademo.exe
nlierrors.
Page 78 of 91
July 2002
Landmark
Obtaining a license to run the software

After installing any point product the following dialog box message will remind you to obtain a
proper license:
License Information Card
To streamline your software license request, contact the License Administration Team via
the World Wide Web at:
http://www3.lgc.com/LandmarkPortal/Landmark?PID=LicenseReqMain.html
If you do not have Internet access, call the Houston license center at 713-839-2110, option
6 or the UK license center at 44-1932-832100, option 6.
Please be prepared to provide the following:
Site No*_____________________________
Sales Order No.* _____________________________
Company Name_____________________________
Location______________________________
Requestor______________________________
Email Address______________________________
Phone______________________________
Hostid value ______________________________
Hostname (if applicable) _____________________________
OS and version_______________________________
Platform_______________________________
Model_______________________________
If you have any questions about these requirements, refer to your Landmark Installation
Notes or contact your local Landmark Support center at:
http://www3.lgc.com/LandmarkPortal/Landmark?PID=SupportHome.html
Page 79 of 91
July 2002
Landmark
You must have the hostid for your system in order to request a license. To obtain the hostid, enter
the following for Windows systems:
ipconfig /all (from a Command Prompt window)
Upon receiving the license request, a Landmark representative will generate and return your
license. The license will contain information such as product name, version, expiration date,
number of copies, encrypted key. For example, a license for five versions of ARIES would be
similar to below:
FEATURE ARIES licsrv 2003.000 10-jan-2002 5 AKEY42AAD7898675309F
VENDOR_STRING="Ewing Oil
Once you receive your license, you must add it your license.dat file (typically in the lam directory)
and restart the license manager. After the license manager has been restarted your newly installed
software will be able to run.
For more information on managing the LAM, refer to the LAM 2003 Guide, which is included on
the OpenBooks CD (Volume 1, Box 2).
Page 80 of 91
July 2002
Landmark
LAM Installation
Landmark's license system (LAM) is based on Globetrotter Software's FLEXlm licensing server
package. This document describes the procedures for installing, configuring, and managing the
license system to control the usage of Landmark applications in a standalone environment. For
additional information on installing LAM 2003, please refer to the following documents:
LAM 2003.0 Guide
LAM 2003.0 - Windows

LAM 2003.0 Guide and LAM 2003.0 - Windows
The LAM 2003.0 Guide and LAM 2003.0 - Windows documents are
located on the OpenBooks CD (Box 2, Volume #1).
Version Compatibility
Release 2003.4.0.0 requires FLEXlm 7.2e. FLEXlm 7.2e server and license files incorporate new
security enhancements used by Release 2003.4.0.0. As a result, Release 2003.4.0.0 applications
will not work with earlier FLEXlm versions.
The LAM 2003.0 Server software must be installed and new license files must be obtained prior to
attempting to run any Release 2003.4.0.0 applications.
Installation Terminology - Client versus Server

Before you begin installing LAM, please note that there are two distinct components to the LAM
software: client and server.
LAM Client
If the machine will not be serving licenses to other machines, or if it is not a standalone system, it
is called a "Client."
The individual product installation processes automatically install the client version of the LAM
software and files on the system. It is highly unlikely that you will need to use any of the procedures
contained in the platform-specific chapters of the LAM installation and user guides.
LAM Server
If the machine will be serving licenses to other machines, or if it is a standalone system, it is
referred to as a "Server." Install LAM Server according to the platform-specific procedures
contained in the specified installation and user guides. For the purposes of this document, a
standalone system is assumed.
Page 81 of 91
July 2002
Landmark
Obtaining a Host Name and Physical Address

A license file must be obtained from Landmark Graphics Corporation before you can start the
license server and run the Landmark applications.You need a Host Name and Physical Address
when requesting a license file. To determine this information, follow the steps below.
1. Log on to the server machine as Administrator.
2. Enter the following command in a Command Prompt window:
ipconfig / all
3. If the machine has more than one Ethernet card or is a stand-alone system, enable the correct
card using the Hardware Manager.
4. Note the Host Name here: _________________________
5. Note the Physical Address here: _________________________ (On Windows 2000
systems, this is a 12 digit string; for example, 00-C0-3D-68-F9-2B.) Do not include the
hyphens; 00C03D68F92B would be the entry for the Physical Address above.
Page 82 of 91
July 2002
Landmark
Installing LAM Server

Before you proceed with the steps in this section, uninstall all previous versions of LAM Server
that have been installed on the machine. Failure to uninstall all previous versions of LAM Server
result in a duplicate FLEXlm service that replicates itself until it crashes Windows. See LAM
Server Uninstall on page 38 of the LAM 2003.0 Guide.
1. Log on to the server machine as administrator.
2. Put the appropriate Release 2003 CD in the CD-ROM drive. The installation will run in an
automatic startup mode; if is does not, use the following steps:
Select Start > Run. The Run dialog box opens.
In the Open text field, type <CD-ROM drive lettter>:\Setup.exe
Click OK.
The installation screen appears.
3. Click on Install Products.
4. When the installation screen changes, click on LAM Server. A Setup box appears briefly.
5. Select the destination for the install. Use the default location, <Drive
Letter>:\Landmark\LAM.
6. Place the license file obtained in the previous section, Obtaining a Server License File, in the
LAM 2003 destination folder, <Drive Letter>:\Landmark\LAM.
7. When prompted to reboot the machine, click Yes, Reboot Now, then click Finish.
8. Remove the CD from the CD-ROM drive.
If the license file is in place when the machine re-boots, the license server starts automatically. If
you do not have the license file when the machine re-boots, you have to start up the License Server
manually. For more information on starting the License Server manually, refer to the LAM 2003.0
Guide - Unix and Windows.
Page 83 of 91
July 2002
Landmark
Known Problems
This section describes problems that were noted during Release2003.4.0.0 testing. For a complete
list of known problems in each application, refer to the products release notes. If you have any
problems with the install, please contact your nearest support location (page 86).
Exceed Issues
The X server configuration settings outlined in the Desktop-VIP Installation Guide are for specific
graphics cards and drivers. For non-certified graphics cards, other settings may be more
performant.
XP Graphics Issue
Users of Windows XP may experience slower graphics. This is an operating system issue.
LAM/Citrix Issue
You must use the FLEXlm daemon to serve feature licenses in a Citrix or Terminal server
environment. FLEXlm bitlock licenses are not supported on Citrix.
LAM/Windows XP Issue
On Windows XP the LAM installation may occur in a directory other than the directory specified
during install. If this occurs, you must manually change the environment variables and registry
settings to reflect the actual location of LAM.
LAM on Local/Network Issue

LAM version 7.2e, the version used for the Active Field Surveillance release, does not work
properly in configurations with both local and network license servers. If a license is not available
on the local server, LAM will not rollover to the network server. If all licenses are combined, LAM
functions properly.
DSN Issues on Citrix

When logged into Citrix, System DSNs created on the local machine will not display because the
Citrix system environment overrides the local system environment. DSNs on the local machine
must be created as User DSNs. All DSNs created in the Citrix account should work correctly.
Page 84 of 91
July 2002
Landmark
DSS Issue on Citrix

The same DSS project cannot be opened on a local machine and on Citrix at the same time. One
project should only be used in one environment at a time.
TOW/cs on Landmarks Data and Application Management Solution

(Using Citrix Metaframe XP Outside the Firewall)
TOW/cs Regulatory EDI files are generally saved to a local hard drive. When using TOW/cs on
Landmarks Data and Application Management Solution, the Save dialog defaults to the Data and
Application Management server. You must type the drive letter of your local machine in the Save
dialog (in front of the file name), to save the files to your local machine.
DSS and DIMS Connections

To connect DSS and DIMS, you must use DIMS2003.0.1. Scripts to connect DSS and DIMS are
found on the DIMS2003.0.1 CD, scheduled for release in the fourth quarter of 2002.
ARIES on NT
None of the Release2003.4.0.0 products are certified on the NT operating system with
Release2003.4.0.0. ARIES will have an NT-certified release (Release2003.4.1.0) in the third
quarter of 2002. Contact your account representative for more information on this release.
Desktop-VIP and AFS

Initially, Release2003.4.0.0 will ship with Desktop-VIP Release2003. In the third quarter,
Desktop-VIP Release2003.4 will be available. This version contains the following:
AFS export/import formats
Export to the DEX (data exchange) utility
ARIES Data Transport and Import/Export Functionality

ARIES Data Transport does not function properly on AFS databases. Data Transport continues to
work properly for non-AFS databases.
In addition, ARIES Economic Import/Export does not function properly between AFS databases.
This functionality continues to be available for non-AFS databases.
Page 85 of 91
July 2002
Landmark
Appendix A: Contacting Support

Landmark operates a number of Technical Assistance Centers (TACs). Additional support is
provided through district support offices around the world. If problems cannot be resolved at the
district level, Landmarks escalation team is called to resolve your incidents quickly.
Support information is always available on the Landmark Graphics Support internet page.
Technical Assistance Centers

North America (Houston, Texas)
713-839-2200 or toll-free 1-877-HELP-LGC
7:30 am - 5:30 pm CST/CDT

Monday - Friday, excluding holidays
Fax: 713-839-2168
Email: support@lgc.com
South America (Houston, Texas)

713-839-3405
7 am - 5:00 pm Local Time

Fax: 713-839-3405
Email: soporte@lgc.com
United Kingdom (Leatherhead)

44-1372-868686

Fax: 44-1372 868601
Europe and Africa

44-1224-778500
24 hour support including weekends and holidays

**NOTE: 24 hour support is for DIMS only. WellPlan,
Compass, and Profile are supported business hours: 8
a.m. - 6 p.m. Local Time, Monday - Friday, excluding
holidays.
Telephone: +44-1224-778500
Email: pc-support-aberdeen@lgc.com
Middle East and North Africa

9712-676-1745
Fax: 9712-672-5924
Support Mobile Phone: 971-50-551-7273
Page 86 of 91
July 2002
Landmark
Asia Pacific International

61-8-9481-4488 or
toll-free 1-800-448-488
8:30 am - 5:30 pm Local Time

Monday-Friday, excluding holidays
Toll-Free Numbers:
10-800-6100-253 (China)
001-803-61284 (Indonesia)
00531-61-0021 (Japan)
1800-803-687 (Malaysia)
0800-400-555 (New Zealand)
1800-1611-0207 (Philippines)
00308-61-0046 (South Korea)
0080-61-1350 (Taiwan)
001-800-611-2784 (Thailand)
Bangladesh, Brunei, India, Pakistan, Vietnam

61-8-9481-4488
District Support Offices

Argentina (Buenos Aires)
54-11-481-25-888
9 am - 6 pm Local Time
Monday-Friday, excluding holidays
Fax: 54-11-481-29777
Australia
1800-448-488
Australia (Melbourne)
61-3-9820-2486

Fax: 61-3-9828-5365
Email: ozsupport@lgc.com
Australia (Perth)
61-8-9481-4488 or toll free 1800-448-488

Fax: 61-8-9481-1580
Email: ozsupport@lgc.com
Brazil (Rio de Janeiro)

55-21-220-9790 or 000-814-550-3785
Chile (LAO TAC, Houston, Texas)

800-201-898
7 am - 5 pm CST/CDT
Fax: 1-713-839-3405
Page 87 of 91
July 2002
Landmark
China
10-800-6100-253
Colombia (Bogota)
980-915-4743
57-1-317-6083 or 57-1-317-6756 or
57-1-317-6106 or 57-1-317-6150
Fax: 57-1-317-5670
Ecuador (Quito)- Halliburton Office

59-32-261-844
Fax: 59-32-261-835
Egypt (Cairo)
20-2-517-3095
(ask for Landmark Technical Support)

Local Business Days, excluding holidays
Fax: 20-2-353-2608
Email: drilling_support@lgc.com
India (New Delhi)

91-11-622-1885

(c/o Samit Enterprises)
Fax: 91-11-647-9246
Indonesia
001-803-61284
Indonesia (Balik Papan)

0542-76-3636
Indonesia (Jakarta)
62-21-526-5555 or
toll-free 001-803-61284

Fax: 62-21-526-6555
Japan
00531-61-0021
Malaysia
1800-803-687
Malaysia (Kuala Lumpur)

60-3-2164-1121 or toll free 1800-803-687

Fax: 603-2164-1135
Page 88 of 91
July 2002
Landmark
Mexico (LAO TAC, Houston, Texas)

001-888-438-1296
7 am - 5 pm CST/CDT
Fax: 1-713-839-3405
New Zealand
0800-400-555
Nigeria (Lagos)
234-1-262-0765
Fax: 234-1-262-0769
People's Republic of China (Beijing)

86-10-6465-4501 or toll free 10-800-6100-253

86-10-6465-4502 or 86-10-6465-4503
Email: bjsupport@lgc.com
Peru (Lima)- Halliburton Office

51-1-442-0699
Philippines
1800-1611-0207
Russia (Moscow)
7-095-755-8300
7 am - 5 pm CST/CDT
Fax: 7-095-755-8301
South Korea
00308-61-0046
Taiwan
0080-61-1650
Thailand
001-800-611-2784
Trinidad (LAO TAC, Houston, Texas)

1-888-438-1296
7 am - 5 pm CST/CDT
Fax: 1-713-839-3405
Page 89 of 91
July 2002
Landmark
United Arab Emirates (Abu Dhabi)

9712 676 1745
Fax. 9712 672 5924

Email: drilling_support@lgc.com
Support Mobile is 97150 551 72 73
8:30am - 5pm Local Time, Saturday-Wednesday,
excluding holidays
Out of office hours support provided for DIMS only,
call Support mobile number.
United Arab Emirates (Dubai)

+971-4-331-3142
Fax: 971-4-331-5837
Email: gulf_support@lgc.com
United Kingdom (Aberdeen)

44 (0)1224 778500
8:30am - 5pm Local Time, Monday-Friday, excluding

holidays
Fax. 44 (0)1224 778555
Email: pc-drilling-support@lgc.com
Out of office hours support provided for DIMS only,
call above number and request Oncall Support.
Venezuela (Caracas)
0-800-526-3627
Monday - Friday, excluding holidays Fax:58-2-9523845
Vietnam (Ho Chi Minh City)

84-8-910-1901
Fax: 84-8-910-1902
Helpful internet links are shown below.

Name
Website Address
Landmark Graphics home page
http://www.lgc.com
Landmark Graphics FTP Site
ftp://ftp.lgc.com
Oracle home page
http://www.oracle.com
FLEXlm license management software

home page
http://www.globetrotter.com/flexlm.htm
Microsoft SQL Server home page
http://www.microsoft.com/sql/default.asp
Adobe Acrobat Reader
http://www.adobe.com
Microsoft MSDE
http://www.microsoft.com/sql/default.asp
Page 90 of 91
July 2002
Landmark
Trademarks
Landmark, the Landmark logo, 3D Drill View, 3D Drill View KM, 3DVIEW, Active Field Surveillance, Active Reservoir
Surveillance, ARIES, Automate, BLITZ, BLITZPAK, CasingSeat, COMPASS, Contouring Assistant, DataStar, DBPlot, Decision
Suite, Decisionarium, DecisionDesktop, DecisionSpace, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam
Extreme, DepthTeam Interpreter, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW, DIMS, Discovery, Drillability Suite, DrillModel,
DrillVision, DSS, Dynamic Surveillance System, EarthCube, EdgeCa$h, eLandmark, EPM, e-workspace, FastTrack, FZAP!,
GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, GeoLink, GES, GESXplorer, GMAplus, GrandBasin, GRIDGENR,
I2 Enterprise, iDims, IsoMap, LandScape, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Make Great Decisions,
MathPack, Model Builder, MyLandmark, MyWorkspace, OpenBooks, OpenExplorer, OpenJournal, OpenSGM, OpenTutor,
OpenVision, OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView, Point Gridding Plus,
Pointing Dispatcher, PostStack, PostStack ESP, PRIZM, PROFILE, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM,
ProMAX MVA, ProMAX VSP, pStaX, QUICKDIF, RAVE, Real Freedom, Reservoir Framework Builder, RESev, ResMap, RMS,
SafeStart, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, SigmaView,
SpecDecomp, StrataMap, Stratamodel, StratAmp, StrataSim, StratWorks, StressCheck, STRUCT, SynTool, SystemStart, T2B,
TDQ, TERAS, Total Drilling Performance, TOW/cs, TOW/cs The Oilfield Workstation, Trend Form Gridding, Turbo Synthetics,
VIP, VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-POLYMER,
VIP-THERM, WavX, Web OpenWorks, Well Editor, Wellbase, Wellbore Planner, WELLCAT, WELLPLAN, WellXchange, wOW,
Xsection, ZAP!, Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark Graphics Corporation.
All other trademarks are the property of their respective owners.
Page 91 of 91
July 2002

AFS RN InstallGuide 2003.4.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AFS RN InstallGuide 2003.4.0

Uploaded by

Copyright:

Available Formats

Landmark

Active Field Surveillance

Active Field Surveillance

Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Active Field Surveillance

R2003.4.0.0 Release Notes

Active Field Surveillance

Active Field Surveillance Workflows on page 4

R2003.4.0.0 Release Notes

Active Field Surveillance

Active Field Surveillance Workflows

R2003.4.0.0 Release Notes

Active Field Surveillance

Dynamic Reservoir Management

R2003.4.0.0 Release Notes

Active Field Surveillance

Citrix-ready applications page 6.

Citrix Ready Applications

R2003.4.0.0 Release Notes

Active Field Surveillance

New Integration Features

R2003.4.0.0 Release Notes

Active Field Surveillance

R2003.4.0.0 Release Notes

Active Field Surveillance

Well Synchronization Utility

R2003.4.0.0 Release Notes

Active Field Surveillance

Common Well Groups

Platform (VC_PLATFORM table)

R2003.4.0.0 Release Notes

Active Field Surveillance

Resolved PDEN_ID/Propnum Conflicts

New Point Product Features

Create several proposals for each property and reserve category.

R2003.4.0.0 Release Notes

Active Field Surveillance

TOW/cs Zone Level Allocation (ZLA)

Tie completion zones to commingled well strings on a date/time effective basis.

R2003.4.0.0 Release Notes

Active Field Surveillance

Before You Install

the applications in Release2003.4.0.0

product dependencies and unique product requirements

Contents of the Release2003.4.0.0 CDs on page 14

System Requirements page 14

Product Dependencies on page 19

R2003.4.0.0 Release Notes

Active Field Surveillance

Contents of the Release2003.4.0.0 CDs

Windows 2000 Professional Server

Windows 2000 Professional Workstation

256 MB RAM or greater

256 MB RAM or greater

VGA Color Monitor

VGA Color Monitor

106 key Windows ready integrated keyboard

106 key Windows ready integrated keyboard

MS-compatible mouse or pointing device

MS-compatible mouse or pointing device

TCP/IP-based network connection 100Mbps

TCP/IP-based network connection minimum

2-4 GB or better SCSI disk space

2 GB SCSI disk space