OpenSpirit^® Ocean Petrel Application Adapter
Version 2010 - Release Notes

Release Date: June 30, 2010

The Ocean-Petrel Application Adapter from OpenSpirit (OPAA) provides seamless access to more than 12 OpenSpirit-enabled data stores, including GeoFrame®, Finder®, OpenWorks®, and KINGDOM^TM.

End users can access data across multi-vendor and cross-disciplinary data stores and applications in a single step, without the need to learn multiple user interfaces. Petrel users can now be liberated from the mundane and time-consuming task of searching for the right data to load into Petrel.

Overview

This release of the Ocean-Petrel Application Adapter contains all fixes from previous versions and service packs and can be installed as an update to any previous OPAA 2009 or as a stand alone install. OPAA 2010 must be run with OpenSpirit runtime version 3.2.1 or higher. It offers enhanced workflow possibilities and ease of use for both new and existing customers.

Release Highlights

• Compatible with both Petrel 2009.2 and Petrel 2010.1
• Supports sending/receiving GIS events that include all feature attributes (may be used in conjunction with OpenSpirit ArcGIS Extension 2010).
• Supports sending/receiving GIS events that include simple display attributes such as point size and color, line color and width, and polygon fill color and opacity (may be used in conjunction with OpenSpirit ArcGIS Extension 2010).
• Supports "classification" of petrel point and polygon objects as specified feature types and allows addition and editing of assicaiated attributes (requires user customization of XML file to define company GIS standards).
• Supports multiple object export in a single dialog.
• Supports importing to a selected, or hightlighted, folder in the Petrel tree.
• Implemented match and merge functionality on non-Petrel properties,
• Supports importing wells without their associated checkshots.
• Added a process to delete OpenSpirit data keys.
• Supports migration of OpenSpirit data keys for markers from previous Petrel versions.
• When used in conjunction with OpenSpirit v3.2.2 (due to be released late summer 2010) or higher, OPAA can be run in Import Only mode, in order to restrict write-back access to OpenSpirit data stores.

Notable Resolved Issues

• Exporting 2d seismic horizons into a target project that already contains portions of that horizon may invalidate the existing horizon set. To that end, we have disabled the export functionality of 2d seismic horizons in this release. Export of 2d seismic horizons into an empty target project functions as expected with OPAA 2009 SP2. (23748)
• Fixed a problem saving migrated keys after the project is closed. (23750)
• Fixed a problem requiring the default Petrel folders (Wells, Seismic, Well Tops 1) to exist in the tree prior to import (23224).
• Improved performance when opening Petrel projects with migrated markers (23751).
• Fixed a problem importing fault pointsets (23611).
• Fixed a performance problem )
• Fixed a problem when deleting seismic from Petrel (23522).
• Fixed a problem sending and receiving contours as GIS events (22919).
• Fixed a problem sending well bottom and surface locations as GIS events (23637).
• Fixed a problem sending and receiving objects with Z values as GIS events (22911).
• Fixed a problem supporting Schlumberger Well Known Text strings for coordinate systems (21973).
• Fixed a problem with invalid compression factors when exporting 3d volumes in Brick format (22422).
• Fixed a problem displaying correct survey name for 3d seismic horizons in the multiple export dialog (23165).
• Fixed a problem sending mixed polygon/polyline features as a GIS event (22917).
• Fixed a problem with match and merge after marker deletion (23547).
• Fixed a problem allowing refresh from external option on 2d horizons exsiting somewhere other than the default location in the Petrel tree (23119).
• Fixed a problem sending and receiving faults as GIS events (23126).

Certified Operating Systems and Prerequisites

• OpenSpirit Ocean Petrel Application Adapter functions on all Operating Systems that Petrel 2009.2 Sep 11, 2009 or Petrel 2010.1 Apr 24, 2010 functions on.
• Prerequisites that must be installed on the System running the OpenSpirit Ocean Petrel Application Adapter are
• Petrel 2009.2 Sep 11, 2009 or Petrel 2010.1 Apr 24, 2010
• OpenSpirit v3.2.1 or higher

Known Issues

The following are the most significant known issues at the time of the release of Version 2010.

• Unable to migrate markers from OSP v2.9x to v3x due to improper key in source (Ocean Petrel Issue 979). Fixed with Petrel 2010 and OPAA 2010.
• OPAA depicts holes in GIS polygons as its own polygon. The polygon representing the hole does not appear as a hole to the user (Ocean/Petrel Issue 1046).
• LastModifiedDate (LMD) for a Petrel Marker not updated when modified (Ocean/Petrel Issue 568).
• OpenSpirit Properties not displayed in Settings for Horizons. OpenSpirit Properties are displayed in Settings for the associated Horizon Property (Ocean/Petrel Issue 828).
• Blank place-holder is created in the Petrel Input Tree when importing 3D Seismic Volumes.
• Does not support drilling targets.
• On export of seismic data, if the Petrel SRD does not match external project's SRD, a warning is issued to note difference; the export of the data is still performed.
• The Settings dialog for the Process OpenSpirit cursor tracking does not display. There are no settings for this process.
• NAD27 transformation methods listed twice in details dialog.
• Short_Time unit cannot be set to “s” (Ocean/Petrel Issue 1184).
• Unable to export WellType to Kingdom data store.
• Importing 3d Volumes into Petrel from a Kingdom8.4 data store yields wrong results. Traces appear replicated (issue resolved in Kingdom 8.5).
• Exporting CheckShots from Petrel to a Kingdom data store does not account for any difference in Velocity Datum (SMT Issue 27012).
• Only one well log curve version can be exported from Petrel to Kingdom8.4 because the Kingdom data connector does not support multiple log curve versions.
• When exporting to a Kingdom data connector from Petrel, no matter what interpreter is selected in the Export dialog, the data will always be associated with the Author used to run the Kingdom data connector.
• The horizon grid “Origin Name” field is not exported when performing an export to a Kingdom project.
• When upgrading Petrel projects from an older version to Petrel 2009.2 with the OpenSpirit Ocean Petrel Application Adapter (OPAA), the user is prompted to convert any existing keys upon connection to OpenSpirit. Keys are tags for data items, stored in Petrel, that point back to an OpenSpirit data connector. The process of conversion changes the old keys to keys appropriate for OPAA access and validation. Check shot keys are not converted or validated. Thus, when importing matching check shots with the OPAA, they will populate the Petrel project and appear as duplicates. Deleting the old check shots is a typical workaround.
• Duplicate points are discarded when importing fault polylines into Petrel. Petrel considers a point to be a duplicate if the X, Y, and Z values match any point on the fault, even points on different fault segments (Ocean Petrel Issue 1251).
• The “Skip” option must be selected when exporting log curves and well picks from Petrel to an OpenSpirit data source that does not support check shot creation.
• Accessing 3d seismic data via a live link in Petrel from a Kingdom project with an incorrect seismic path setting will cause Petrel to hang.
• The min/max sample values shown in the DataSelector may not match the min/max sample values shown in Petrel because the values in the DataSelector do not necessarily reflect the min/max values of the raw seismic data. The timeshift, phase rotation, and amplitude scale factor, which are all defined in the KingdomSuite Survey Management Mistie dialog, may have been applied.
• Kingdom8.4 data connectors return KB Elevation as Seismic Reference Datum (SRD).
• Kingdom data connectors do not support last modified date. As a result, Match and Merge timestamps comparisons cannot be established to indicate which data source has been updated most recently.
• Re-importing faults multiple times from a Kingdom data source occasionally produces a lost connection error in the Petrel message log. Shut down and restart the Kingdom data connector to reestablish the connection.
• Exporting faults to a target data store that contains matching parent objects, such as 2d lines or 3d surveys, causes the fault key to update, but not the parent (2d line or 3d survey). Thus there is a mismatch between parent and child sources after export. Caution should be used when exporting faults.
• Microsoft Windows Uniform Naming Convention sysntax is not supported when entering a configuration file custom location on installation.
• Cannot export 3d seismic horizons to an OpenWorks R5000 data store where the horizon name already exists (issue resolved in OpenSpirit v3.2.2).
• The OpenSpirit data key for non-primary Z 2d seismic horizon properties does not get updated upon export.
• A change in Petrel 2010 causes the directional survey calculation method to always falls back to linear (Ocean/Petrel Issue 1612).
• When deleting a well pick in Petrel 2010 an error is logged in the message dialog. The delete completes as expected.
• Issues migrating unrealized 2d lines from previous Petrel versions (Ocean/Petrel Issue 1636).
• OpenSpirit keys for markers are not honored after moving data using the Perel Reference Project Transfer tool. OpenSpirit has worked around this issue by populating a new column in the marker spreadsheet with the OpenSpirit key.
• If 2d lines were imported into Petrel 2009.x from an OpenWorks 2003.12 datastore configured in OpenSpirit 3.2.0 or higher, the shotpoint array is not accurate. To resolve this issue, reimport the 2d lines using OPAA 2010.
• If multiple 3d seismic horizon properties are imported into Petrel from the OpenSpirit Horizon Properties tab, including the primary Z property, the primary Z property loses its OpenSpirit datakey. To resolve this issue, either broadcast from the Horizon tab, or broadcast only the primary Z property from the Horizon Properties tab.
• When a 2d horizon is imported into a custom folder (not the OpenSpirit default), subsequent refresh of that horizon will place a duplicate 2d horizon in the OpenSpirit default Interpretation folder.
• Cannot install both 32 bit and 64 bit versions of OPAA on the same machine.
• When importing 2d horizon properties, the primary Z property is considered part of the geometry, and therefore is not listed as a property in the Petrel message log on import.

Technical Support

Please refer to the following resources for OpenSpirit information:

Web Support	www.openspirit.com/support
E-mail Support	support@openspirit.com

OpenSpirit Ocean Petrel Application Adapter is designated with U.S. Department of Commerce Export Control Classification Number 5D992.b.1