Professional Documents
Culture Documents
OspreyConnect User Guide
OspreyConnect User Guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Evaluation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Installing Runtime License Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Obtaining the MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Adding a Floating License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Adding Node Lock License Through
Schlumberger Licensing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Checking the License Server Status Using the Command Prompt . . . . . . . . . . . . . . . . . . . . . 2-8
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Toolbar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Source Connection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Data Mapping and Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Loading and Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Saving Connection and Mapping Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Loading Connection and Mapping Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Connecting Through Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Connecting to Multiple Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Osprey Connect Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Contents v
IDEAL Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Streaming Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
WITSML API Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Loading a Static Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Writing an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Changing a Wellbore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Sanitizing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Code and Unit Sanitizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Code Sanitizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Unit Sanitizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Starting Transfer/Stopping Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Data Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Starting Indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Viewing Osprey Connect Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
In This Section
About Schlumberger is the leading oilfield services provider, trusted to deliver superior
Schlumberger results and improved E&P performance for oil and gas companies around the world.
Through our well site operations and in our research and engineering facilities, we
develop products, services and solutions that optimize customer performance in a
safe and environmentally sound manner.
Alert Statements The alerting statements are Notes, Cautions, and Warnings. These statements are
formatted in the following style:
• • • • • •
Note: Information that is incidental to the main text flow, or to an important
point or tip provided in addition to the previous statement or instruction.
• • • • • •
Caution: Advises of machine or data error that could occur should the user fail
to take or avoid a specified action.
• • • • • •
Warning: Requires immediate action by the user to prevent actual loss of data
or where an action is irreversible, or when physical damage to the
machine or devices is possible.
Contacting Schlumberger
Technical Support Schlumberger has sales and support offices around the world. For information on
contacting Schlumberger, please refer to the information below.
For Technical Support for SIS software: https://support.slb.com
In This Chapter
Introduction
After you install Osprey Connect (formely Real-Time Data Link or RTDL), you must
set up the license. You will be able to run the Osprey Connect application in
evaluation mode if you have not obtained a license, or if the system is unable to
verify the license. The evaluation mode is configured for 20 minutes, and has limits
set on available functionality.
• • • • • •
Note: You must have the Schlumberger provided Flexnet runtime environment
installed on your machine before you setup licenses for Osprey Connect.
Evaluation Mode
Osprey Connect 2008.1 is a licensed toolkit which works in evaluation mode if it fails
to locate valid licenses. The following are certain constraints on the toolkit usage in
evaluation mode:
• The session time is limited to 20 minutes and is indicated to the user by a splash
screen when the toolkit is first initialized, as illustrated below.
• In the evaluation mode, when the session limit of 20 minutes is reached, the
Osprey Connect instance is self destroyed after displaying the following splash
screen.
• The Osprey Connect user can retrieve only 20 minutes of historical time data and
1000 ft of historical depth data in evaluation mode.
• The user will not be able to set the starting index because the starting index
controls are disabled in evaluation mode.
Licensing
The following section will walk you through the setup of your license.
Installing Runtime As part of the Osprey Connect SDK installation, the self-extracting Schlumberger
License Runtime License installer (flex113Installer.exe) is copied to the Osprey Connect
Environment installation directory.
If you do not have the Schlumberger runtime license environment already installed
on your machine, invoke Windows Explorer and double-click the license installer.
Once the installation wizard appears, follow the instructions on the wizard to install
the runtime license environment.
Obtaining the MAC To set up a node lock, you need a MAC address (physical address). Refer to the
Address following steps on how to obtain your MAC address.
Adding a Floating You should have a floating license server already configured with valid Osprey
License Connect licenses.
• • • • • •
Note: Use the Schlumberger licensing utility (SLBLicensing.exe) to add a floating
license server.
2 Enter the name of the license server host in the port@host format, as shown in
the figure above.
• • • • • •
Note: In the example below, the floating license server is listening for license
requests at the (default) port 27000 on a machine named ro-ofs
Adding Node Lock Use the following steps to add the license through the Schlumberger Licensing
License Through server.
Schlumberger
Licensing Server
Checking the Use the following steps to add the license using the command prompt.
License Server
Status Using the
Command Prompt
In This Chapter
Introduction
Osprey Connect provides a common user interface for establishing a real-time
connection across a multitude of sources. The source connections are driven by
various components, which control and monitor the connection and transfer status.
In addition, Osprey Connect allows users to map specific channels to be handled by
the application and optionally save and load settings for future use.
User Interface
The following sections will briefly discuss the layout of Osprey Connect user
interface.
Title Bar The title bar displayed at the top of the window provides information about the
currently selected source and connection status.
Toolbar Menu The toolbar menu, located at the top of Osprey Connect user interface, consists of
six icons. The four icons on the left enable you to perform the following:
• Create a new connection
• Load a previously saved connection and mapping settings
• Save connection and mapping settings
• Sanitize incoming data
About and Help icons are also displayed on the right of the toolbar.
Table 3-1 provides an overview of all icons available in Osprey Connect user
interface:
Table 3-1 Osprey Connect Toolbar Commands
Icon Description
Clears mapping and connection information.
New Disconnects if connected.
Status Bar The status bar, located at the bottom of the window, provides status information
about Osprey Connect transfer state and actions occurring internally.
Source Connection The Source Connection window allows users to connect to a source to receive data.
Window This window is composed of three sections: the source selection list, the source
details box, and the source connection form.
The source selection list is located on the left side of the window, under the label
Select a Source. This section is used to select a source to connect to. The Source
Details box is located below the source selection list. This section provides a
detailed description of the currently selected source. The source connection form is
located to the right of the source selection list. This section is used to enter
information about the currently selected source. The form will vary from source to
source.
Fig. 3-1 Osprey Connect Source Connection Window
Data Mapping and The data mapping and selection window enables users to select the channels that
Selection Window they would like to receive.
The application is capable of specifying the type of data that it supports (e.g. Logs,
Surveys, Risks), and optionally the particular channels that it wishes to process (e.g.
‘Hookload’, ‘Bit Depth’).
Petrel, for example, only specifies the type of data that it supports, while other
applications specify both the type of data that they support and the specific
channels that they wish to process.
Mapping Channels The Data Requested by the Application grid enables you to map available data
Specifically Requested channels to the data requested by the underlying application. The Select from the
by the Application Available Data Items grid shows the compatible data channels available for mapping
to the requested data.
• • • • • •
Note: Applications which do not request specific channels (e.g. Petrel) will not
see this view. Instead, they will only see the Select Available Data view
described in “Selecting Additional or Available Data” on page 3-5.
Each requested data can map to at most one available data channel. Osprey
Connect will try to map requested data automatically to the most compatible
available data channel. If a requested data is mapped to an available data channel,
the will appear in the mapped column of the row for the requested data. If the
requested data is not mapped to an available data channel, the icon will appear
instead.
When a requested data is selected, the available data channels grid will update to
show only compatible available data channels. If an available data channel is
mapped to the currently selected requested data, the check box in the map column
of its row will be selected. If an available data channel is mapped to a requested
data other than the one selected, its background color will be light grey instead of
white.
• • • • • •
Note: Mapping an available data channel that is mapped to another requested
data will un-map the previous requested data.
The following table provides detailed information about the functionality available
from the right-click context menu of the requested data grid.
Table 3-2 Right-click Menu Commands
The following table provides detailed information about the functionality available
from the right-click context menu of the available channels grid.
Table 3-3 Right-click Menu Commands
Selecting Additional or The Additional Data Selection and the Available Data Selection windows allow you to
Available Data select from a complete list of available data channels. The real-time application has
the ability to filter this list of channels according to their needs. In either window,
the user selects the channels to be transferred by selecting the check box in the
selected column.
Using Filter Rows The row filter of a grid enables users to quickly find available data channels and
requested data that meet specified criteria. It has a yellow background and is
located just below the column headers on the available data channels grid and the
requested data grid. The user can enter information in each cell of the filter row to
filter out rows that don’t meet the criteria. To remove filter criteria, simply click the
icon that appears when hovering over a filter cell.
Fig. 3-4 Filter Row showing unit of FT
Saving Connection Use the following steps to save a connection and map settings.
and Mapping
Settings
Osprey Connect now supports the following sources that you can connect to:
• InterACT 5.8 (WITSML 1.3.1)
• InterACT Legacy (WITSML 1.2.0)
• • • • • •
Note: You must have a valid network connection to proceed. Osprey Connect
now supports IDEAL 12 and 13.
• • • • • •
Note: You must have a valid network connection and access to an InterACT
server before proceeding.
Downloading from 1 Select the Download option from the Osprey Connect main window.
InterACT
2 Enter the URL for the Server.
Loading from Disk Use the following steps to load from sisk.
Regulate Playback If the Regulate Playback Speed check box is selected, any files selected will be
Speed played back at a slower, regulated rate. By regulating the playback speed, you can
simulate a Real-Time job. You can specify the speed in the Playback data items
and every seconds fields. For example, by specifying 10 as the Playback data
items every 3 seconds, you can simulate ten sensors being read every ten seconds
at the wellsite.
WITSML API Use the following steps to connect to WITSML API sources.
Sources
1 Select a WITSML source from the Select a Source list of the main window.
• • • • • •
Note: Osprey Connect now supports these WITSML API sources:
InterAct 5.8 (WITSML 1.3.1), InterACT Legacy (WITSML 1.2.0), Baker
RigLink (WITSML 1.3.1.1), Baker RigLink (WITSML 1.2.0), Kongsberg
SiteCom (WITSML 1.3.1), Kongsberg SiteCom (WITSML 1.2.0), Sperry
InSite Anywhere (WITSML 1.2.0) and WellStorm (WITSML 1.3.1).
5 Navigate through the tree and select the Wellbore/Log or Section you wish to
connect to.
6 Click Connect to Log.
Writing an Object
Osprey Connect supports writing the following objects to wellbores on an
InterACT 5.8 WITSML API 1.3.1 server:
• Logs - time or depth indexed channels
• Trajectory Stations
• Risks
• Any other WITSML type
For detailed information on writing an object, refer to the Programmer’s Guide and
Reference.
Changing a Wellbore
Prior to the 2008.1 release, in order to change a wellbore you had to go back to the
Login window and connect to a server and then select a wellbore. In version 2008.1,
you can change to a new well or wellbore from the Channel selection window.
X To change a wellbore
1 Launch Osprey Connect.
2 Select a source.
3 Enter the Server URL.
4 Enter your credentials and click Select Wellbore.
5 Browse to a wellbore and click Connect to Wellbore.
The Channel selection window appears.
6 Click Select Source.
The Save Mapping Changes & Select Source dialog appears.
• If you select Yes, enter a File name and click Save. This will take you back
to select a wellbore.
• If you select No, this will directly take you to the Select Source window with
the current wellbore selected.
7 Select another wellbore within the current well or select another well, and click
Connect to Wellbore.
Sanitizing Data
The Sanitize Data functionality enables you to correct a mismatch in naming
standards for units and/or channel codes. If the source and the real-time application
differ in the way they refer to a given unit or channel-code a sanitizing record can be
defined to fix the mismatch on incoming data.
X To sanitize data
Code and Unit Sanitizing by both code and unit is used in the scenario where an individual
Sanitizing incoming channel has a different naming standard for both its code and unit than
what the real-time application expects. You can define a single record that would
correct the channel having the record’s code and unit.
1 Select Code & Unit Sanitizers from the drop-down list at the top of the
dialog.
2 Enter the mismatched Code.
3 Enter the mismatched Unit.
4 Enter the expected code in the Sanitized Code field.
5 Enter the expected unit in the Sanitized Unit field.
Code Sanitizing Sanitizing by code is used in the scenario where incoming time and depth channels
with the same code are spelled differently than the real-time application expects.
You can define a single record that would correct the code for all channels that
match the record’s code.
• • • • • •
Note: Code sanitizing will not occur if the channel is sanitized by a Code & Unit
sanitizing record.
1 Select Code Sanitizers from the drop-down list at the top of the dialog.
2 Enter the mismatched Code.
3 Enter the expected code in the Sanitized Code field.
Fig. 3-18 Entering Sanitize Code Record
Unit Sanitizing Sanitizing by unit is used in the scenario where incoming channels with the same
unit are spelled differently than the real-time application expects. The user can
define a single record that would correct the unit for all channels that match the
record’s unit.
• • • • • •
Note: Unit sanitizing will not occur if the channel is sanitized by a Code & Unit
sanitizing record.
1 Select Unit Sanitizers from the drop-down list at the top of the dialog.
2 Click in the Unit field and enter the mismatched unit.
3 Click in the Sanitized Unit field and enter the expected unit.
4 Click OK.
Sanitizing Limits You cannot change the sanitization information while transferring data. If you
click Sanitize Data from the menu while transferring data, the following
message dialog appears.
Fig. 3-20 Message Dialog
• • • • • •
Note: When restarted (without disconnecting), the data transfer continues from
the point at which it was stopped. If you wish to receive historical data
from the earliest or designated starting index, you must first disconnect
from the source.
Data Availability
When you launch a Osprey Connect instance and connect to a wellbore to request
data, Osprey Connect can either retrieve the data that you requested from the
server, or if the data is unavailable or the server cannot be contacted an error
message will appear, as illustrated in Figure 3-21.
Fig. 3-21 Error Retrieving Data
Starting Indexing
Osprey Connect now allows you to specify Global Time and Depth range for data
requests. The Depth will only appear if the application supports depth log data.
By default, the Starting Depth is set to Shallowest and Starting Time is set to
Earliest.
• • • • • •
Note: If you are a non-licensed user, you will not be able to set the Depth and
the Time, and instead the appliction will force a Historical Depth of 1,000
feet and a Historical Time of 20 minutes.
• • • • • •
Note: You will not be able to set the Depth and Time while the transfer is in
process. The corresponding fields will be disabled until the transfer is
complete.
6 Select the Starting Depth check box and enter a depth value.
7 Select the Starting Time check box and enter a date and time.
• • • • • •
Note: You can set a relative index value through the User Interface. This index
value will change to an absolute value when you start the transfer.
Osprey Connect now supports the application context, which allows you to set a
string through the API. For more details, refer to the Osprey Connect Programmer’s
Guide and Reference.
Once you set the string, it will appear next to the Application label (as illustrated in
Figure 3-24).
Fig. 3-24 API String
Once you click the link, the Osprey Connect Connection Information window
appears (Figure 3-26), listing information about the server where Osprey Connect is
currently connected to.
Fig. 3-26 OSprey Connect Connection Information