V2.2.3 Release

Upgrade Announcement

POSC has released an update to Version 2.2. The update is labeled V2.2.3, and was released August 24, 1999. Instructions for performing the update are contained in the Instructions for Update section.

The release consists of the following parts:

1. Minor additions and changes to reference data.
2. Additions to activity_class to make present activity_class and activity_class_classification values consistent with the methods of the WIME activity classes.
3. Facility_class values to handle well and wellbore status and purpose. The values for completions are also rationalized.
4. Recommended data model changes for adding a distance measure between two sets, and for adding the ability to model compound coordinate transformations.

Not included in this release are:

1. Incorporation of gravity and magnetics into Epicentre.
2. Incorporation of well log service classes.
3. Scripts to add attributes in topological_relationship to indicate distance from.
4. Scripts to modify coordinate_transformation to allow compound transformations.

The changes will be explained further below. These have been available for review.

Release Process

Previous upgrades have included the following:

• EntityLoader files formed for the logical data model.
• SQL files to upgrade the tables, where a data model change was made. These files work only where the area being changed had the standard extension.
• Summary of changes document.
• More detailed list of all new and changed reference values.
• Incremental express description of data model changes.
• New html files to replace the existing files that were released on the v2.2 CD.
• The set of RefLoadLevelOne load file tables (tarred and zipped).

Based on comments received on this process, no change is being made to the set of documents being released.

List of Changes

As with previous updates, the changes as presently developed are listed as general changes and specific changes. See the Description of Changes since v2.2.2 for general changes and the Epicentre Standard Values Specific Changes list for specific changes.

Change: Incorporation of gravity and magnetics.

The model was extended to include gravity and magnetics as part of a special project. It is the intent of POSC to include this extension in the standard data model. Comments have been received regarding the addition to gravity and magnetics. See the Gravity and Magnetic Comments page.

This change will be considered a recommended extension. It is not to be considered a part of the Epicentre data model, but it is considered to be the POSC recommendation for extending the data model. Since this extension has been incorporated in at least one location, it is felt that it will be interoperable. The extension will be made available to those wanting it by contacting help@posc.org.

Change: Facility_values for well status, etc.

The Department of Trade and Industry (DTI) has been working extensively with industry to develop a useful list of well, wellbore, and completion status values. A summary of the recommended changes has been produced, and has been available for comment. See the Facility class values document for a summary. The document was placed before the membership and comments on these values were received before the August release.

Change: WIME inclusions.

See the WIME into Epicentre page for a discussion of the additions of WIME classes to Epicentre v2.2.2, and plans for v2.2.3 and further.

This release will add a classification system to all POSC activity class instances. Also included are new standard instances of Activity class classification that reflect the WIME activity type hierarchy.

Change: Handle well log service classes

The version 2.2.2 upgrade included a list of well log service classes for comments. In order to include these, it will be necessary to extend the data model. However, this extension will only be applied if it is useful to do so. Please view the Proposed Well Log Service Classes, and send comments on the class values to bobbitt@posc.org or purdy@posc.org.

Change: Add distance values for sets

Several (regulatory) reporting requirements have indicated a need to specify a minimum and/or maximum distance between sets. It has been proposed to add additional attributes to topological_relationship to carry this information. Below is the incremental express for the recommended extension (see the Incremental Express Web Pages for more information about incremental express):

alter entity topological_relationship;
  add minimum_distance: optional ndt_length
  (*The approximate minimum distance between the primary and 
      the secondary object. Let A be the primary and B the secondary 
      object. Define d(y,A) = min (x in A) d(x,y), for every y in B. 
      The minimum_distance (A,B) = min (y in B) [d(y,A)]. For sets that
      are not disjoint, this value is zero.*);
  add maximum_distance: optional ndt_length
  (*The approximate maximum distance from the secondary object, 
      B, to the primary object, A is max (y in B) [d(y,A)], where d(y,A)
      is as defined for minimum_distance. This should not be used for
      sets that are not disjoint.*);
end_entity;

The change will be included as a recommended extension. No scripts will be delivered to implement the change, and the change will not be considered to be part of the Epicentre data model. This is considered to be a workaround, and may appear differently in later major releases of Epicentre.

Change: Include compound coordinate transformations

Some coordinate transformations are more easily handled by giving them as several simple transformations rather than as a single transformation. Others must be given that way. In order to accommodate the former and to allow the latter, a compound coordinate transformation is being introduced, which is a list of simple coordinate transformations.

Since there are several ramifications to discuss, the proposed change and comments are given in the Compound Coordinate Transformations document.

The change will be included as a recommended extension. No scripts will be delivered to implement the change, and the change will not be considered to be part of the Epicentre data model. The extension is to be considered a workaround to maintain upward compatibility. It will appear differently in later versions of Epicentre. See the discussion in the Compound Coordinate Transformations document for details.

Business Purpose

The topics included in the release are intended for the following purposes:

• Expand the coverage of Epicentre to include gravity and magnetics.
• Expand on the WIME activity classes in the Epicentre model.
• Allow the description of well log services in Epicentre. Allow a well log trace to be tied to the service that produced it, so that more details about its acquisition are known.
• Give standard values and standard practices for specifying well, wellbore, and completion statuses. This also includes standard values in addition to statuses.
• Allow minimum and maximum distance to be given for a field, well, or some other object of interest to another land area.
• Allow additional coordinate transformations that are widely used to be stored in Epicentre.

To utilize this release, there are two sets of .tar.Z files that should be downloaded via FTP:

• Get Version 2.2.3 Update - 76KB
  The file v223upgrade.tar.Z consists of EntityLoader and psql files that can be run to upgrade the existing 2.2.2 database. On a UNIX system the files can be expanded by running

  uncompress -c v223upgrade.tar.Z | tar xvf -
  

  Once the files are expanded, the README file can be opened to get detailed instructions to perform the upgrade.
   
• Get Version 2.2.3 HTML Documentation
  Unix compressed tar file (217KB), Windows zip file - (107KB)
  The Epicentre Version 2.2 CD contains .html files that document the reference data values and logical dictionary. New V2.2.3 .html files are included in the compressed tar file html.tar.Z. On a UNIX system the files can be expanded and loaded as follows: (assume the .tar file is in /tmp).

  # the directory below is the one with 'DataModel','DataAccess', etc.
  cd <documentation root directory>
  uncompress -c /tmp/html.tar.Z | tar xvf -
  #optional:
  /bin/rm /tmp/html.tar.Z
  

  Note that this is not a full set of html files, but only the html files that have changes in going from v2.2.2 to v2.2.3. In order to get the full set of changes, you must also install the updated html files from the previous upgrades.
   
• Get complete set of Version 2.2.3 RefLoadLevelOne files. - 1275KB
  These files are not necessary to perform the upgrade. However, they are being made available to those who want a complete set of v2.2.3 data files. The files are in compressed tar format as refLoadLevelOne.tar.Z. They are uncompressed and untarred as are the other files.

Please send all comments to John Bobbitt, the update manager, at bobbitt@posc.org

Last modified: 24 August 99. Send questions and comments to webmaster@posc.org

© Copyright 1994-1999 POSC. All rights reserved.