
OpenSpirit® LoadIT™ WITSML 2009
Release Notes
June, 2009
Introduction to OpenSpirit LoadIT WITSML 2009
The OpenSpirit LoadIT WITSML 2009
(LoadIT WITSML) is the first release of the OpenSpirit plug-in application that
facilitates the flow of real-time well data information from the Drilling and
Completions industry directly to the oil and service companies and other
regulatory agencies. It utilizes the petroleum industry data standard format
Well-site Information Transfer Standard Markup Language (WITSML), to augment
the drilling and completions decision-making process between real-time data
producers and data consumers.
Real-time data from the rig to a
data store in initiated and maintained by the creation of LoadIT “data feeds”
that define the WITSML source and the destination wellbore. Multiple
source-destination data feeds can be created to enable users to load log curves
and trajectories.
OpenSpirit LoadIT WITSML 2009 Distribution
LoadIT WITSML software can be downloaded from the OpenSpirit Website www.openspirit.com , under the heading ‘Support’ and then ‘Downloads’. Click on the ‘OpenSpirit
LoadIT WITSML 2009’ link to download and install the software on your PC, after
installation and configuration of the accompanying mandatory ‘OpenSpirit 3.1.3’
software. The OpenSpirit 3.1.3 software is also available under ‘Downloads’.
Certified Operating Systems
LoadIT WITSML software application is certified on Windows XP (32 bit).
License
The LoadIT WITSML application
uses two license features, namely a Client (OspLoadITFeed) and Server
(OspLoadITServer) feature. OspLoadITFeed is only checked out when a data feed
is running. The license is checked in when the data feed is stopped.
Minimum System Requirements
The minimum system requirements for a successful LoadIT WITSML application installation are:
- Microsoft Windows XP Professional SP3(32-bit)
- Intel Pentium processor – 2.4 GHz or greater
- Minimum 2 GB of RAM
- Microsoft .NET Framework Version 3.0
- Microsoft Windows XP - Regional and Language Options set to English (United States)
Known Issues
The following are the most significant issues known at the time of the release of LoadIT WITSML 2009:
- Matching Channels in OpenSpirit window displays
System.Windows.Controls.ComboBoxItem: New Version in the Action
column.
Details: During the creation of the LoadIT 2009 Data Feed, between a
WITSML Source and a destination wellbore, it is not uncommon to see two version
of the same log curve, say GR (Version 1) and GR (Version 2) in a selected
wellbore. To accommodate this, LoadIT will display the Matching Channels in
OpenSpirit window (namely Step 7 of 10), with the Action for GR (Version 1)
defaulted to ‘Skip’ and GR (Version 2) to ‘New Version’. If the user selects
the Action drop down menu for GR (Version 2) and toggles to ‘New Version’ again
the attribute will display System.Windows.Controls.ComboBoxItem: New Version,
instead of ‘New Version’.
Workaround: Simple engage the drop down menu and select ‘New Version’ again.
- Get the error message Error creating Feed.
Could not convert from remote values(s) when creating a Data Feed.
Details: If the ‘Regional and Language Options’ (in Control Panel)
for the Windows XP software is set to something other than ‘English (United States)’,
LoadIT 2009 will display a message stating ‘Error creating Feed. Could not
convert from remote values(s)’.
Workaround: Change the Regional and Language Options’ (in
Control Panel) to ‘English (United States)’. You may need to reboot the PC for
the change to take effect.
- Get the error, Osprey connection cannot
be initialized in silent mode without connection, source, and mapping
information when starting a Data Feed.
Details: In LoadIT 2009, the creation of the Data Feed is a wizard based process requiring the
selection of many different options and components. Bypassing or circumventing
a component will result in an incomplete Data Feed creation. Specifically, if
one attempts to bypass the selection of the WITSML source component in Osprey,
it will result in the creation of a Data Feed without a source. Attempts to start
this feed will display the message, “Osprey connection cannot be initialized in
silent mode without connection, source, and mapping information”.
Workaround: The user can either delete the incomplete Data
Feed or create another Data Feed and use the "Copy from existing" option.
- Regional setting on the PC must be set to English (United States).
- Deviation Surveys – LoadIT will load
the deviation survey from the WITSML source. It is highly recommended that the
service company providing the deviation survey begin from the surface (i.e.
Measured Depth, MD = 0). This will ensure that a complete well trajectory is
loaded into the destination project.
- Data Feed – When using LoadIT to
populate the destination wellbore with deviation and/or log curve data, it is
imperative that no other application, including OpenSpirit (using Copy Manager,
etc.), is transferring or loading any related data such as 2D or 3D seismic,
well picks, etc. into the same project data store. If it becomes necessary to
transfer/load any additional related data, the data feed must be stopped and
the restarted when the data transfer/load is completed.
- Data Feed – When creating a data feed,
it may be required to select multiple log curve channels along with the deviation
survey. If this selection is large (i.e. about 30 - 40 log channels), the LoadIT
server will give preference to the loading the log curves first and then the
deviation survey.
- Data Feed Matching – When creating a
data feed, it may be required to edit the Mapped Curve Kind and the Mapped
Unit column (Step 6 of 10) values of selected channels. Note that for the
deviation survey, only the Mapped Unit can be edited and not the Mapped
Curve Kind. Specifically, in the GeoFrame data store, when creating a new
deviation survey it is always named using the convention,
‘wds_<wellbore_name>’.
- When launching the Open existing feed button (or File > Open) from the LoadIT Client GUI or selecting the Copy from existing when creating a Data Feed, we get a “Could not communicate with server” error. This is due to a stale or corrupt .odb file.
Workaround: Close the LoadIT Client and Server and delete the $LOADIT_HOME/Server/AppData/LoadIT.odb file and then restart the LoadIT Client (and Server).
Technical Support
Please refer to the following resources for OpenSpirit information:
OpenSpirit LoadIT WITSML 2009 is designated with U.S. Department of Commerce
Export Control Classification Number 5D002.b.1