Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
A selection of generic documents which are relevant to both Well Seeker and Innova Engineering
Loading...
Loading...
Loading...
A selection of quick start guides for Well Seeker X
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
A selection of quick start guides for Innova Engineering
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Thank you for visiting Innova's documentation resource page. From here you will have access to all of the various resources available including our video guides and online training.
You can return to our homepage at any time via the below link.
Click on the link below to see the latest updates we have added to the Innova Document Portal:
To aid navigation, our resources have been split into 6 main sections. Select any of the below tabs for a short description and link to the relevant pages.
This page lists the latest updates to the Innova Documentation Portal. Click on the page title to follow the link to the updated page.
24/04/2025
Well Seeker X Guides
08/04/2025
Technical Notes
08/04/2025
Well Seeker X Guides
08/04/2025
Well Seeker X Guides
08/04/2025
Well Seeker X Guides
02/04/2025
Well Seeker X Guides
01/04/2025
Well Seeker X Guides
28/03/2025
Well Seeker X - Guides
28/03/2025
Well Seeker X - Guides
28/03/2025
Well Seeker X - Guides
07/03/2025
Well Seeker X - Guides
26/02/2024
Technical Notes
18/02/2024
Technical Notes
13/12/2024
Technical Notes
13/12/2024
App & Portal - Guides
26/11/2024
Release Notes
26/11/2024
Technical Notes
20/11/2024
Technical Notes
20/11/2024
App & Portal - Guides
12/11/2024
Technical Notes
06/11/2024
Technical Notes
10/10/2024
Technical Notes
10/10/2024
Technical Notes
03/10/2024
Well Seeker - Guides
11/09/2024
Well Seeker - Guides
11/09/2024
Technical Notes
06/09/2024
Technical Notes
02/09/2024
Technical Notes
20/08/2024
Technical Notes
19/08/2024
Technical Notes
26/07/2024
Technical Notes
17/07/2024
Technical Notes
28/06/2024
Technical Notes
27/06/2024
Release Notes
27/06/2024
Release Notes
17/06/2024
Technical Notes
13/05/2024
App & Portal - Guides
22/04/2024
Technical Notes
15/04/2024
Well Seeker - Manual
25/03/2024
Well Seeker - Guides
19/03/2024
Technical Notes
06/03/2024
Release Notes
28/02/2024
Technical Notes
02/02/2024
Well Seeker - Guides
01/02/2024
Well Seeker - Guides
26/01/2024
Well Seeker - Guides
19/01/2024
Technical Notes
12/01/2024
App & Portal - Guides
27/11/2023
Technical Notes
24/11/2023
Technical Notes
16/11/2023
Technical Notes
19/10/2023
App & Portal - Guides
06/09/2023
Well Seeker - How To Videos
04/09/2023
Technical Notes
04/09/2023
Technical Notes
30/08/2023
Web Portal - How To Videos
21/08/2023
App & Portal - Manual
21/08/2023
App & Portal - Guides
08/08/2023
Well Seeker - Guides
31/07/2023
Technical Notes
26/07/2023
Well Seeker - Manual
19/07/2023
Well Seeker - Manual
29/06/2023
Well Seeker - Guides
26/06/2023
Well Seeker - How To Videos
05/06/2023
Well Seeker - How To Videos
04/06/2023
Web Portal - How To Videos
30/05/2023
Well Seeker - Guides
29/05/2023
Technical Notes
26/05/2023
Well Seeker - Guides
25/05/2023
App & Portal - Guides
25/05/2023
Innova Engineering - How To Videos
17/05/2023
Web Portal - How To Videos
12/05/2023
Innova Engineering - Guides
09/05/2023
Well Seeker - Guides
01/05/2023
Feature Updates
01/05/2023
Feature Updates
01/05/2023
Feature Updates
A selection of generic documents which are relevant to both Well Seeker Pro and Innova Engineering
A selection of quick start guides which focus on specific areas of the software. This section groups the documents together based on the program they are associated with.
The full manual for both Well Seeker Pro and Innova Engineering.
The most up to date release notes for both programs. These documents detail the various changes implemented between revisions.
This section contains links to all of Innova's video resources.
The How to Videos are bite size clips ranging from 2 to 12 minutes long and each cover a specific feature within the software.
The online training videos are are much longer and cover the various topics in more depth.
Technical notes are short documents that aim to make users aware of certain features in Well Seeker Pro, or solutions to particular technical issues that cannot be fixed with a patch.
Introducing the new BGGM Error Estimate Integration in Well Seeker Pro
For more information on our new integration, or any of our other products, please contact:
sales@innova-drilling.com
US: +1 713-893-4435
UK: +44 (0) 7711411079
Alternatively visit our website:
An introduction to the latest updates that have been added to the Innova product range.
Introducing the new Superior QC Integration in Well Seeker Pro
For more information on our new integration, or any of our other products, please contact:
sales@innova-drilling.com
US: +1 713-893-4435
UK: +44 (0) 7711411079
When you first download the software, it comes with a 2-day trial license. After the 2 days have passed the license will expire, and the next time you attempt to open the software you will see the warning box displayed below Left. This box will be displayed any time you try to open the software without a valid license. When you select OK the "Computer Code" box will appear.
The Computer Code can also be accessed at any time when in the program, by selecting Help – License Info
To request a license extension/renewal, follow the instructions below:
Highlight the code which is displayed in the "Computer Code" box
Press Ctrl + C (this will copy the code to your clipboard)
Paste the code into an email or word document (Ctrl + V)
You will need to clearly specify which program you need a license for, either Well Seeker Pro, Innova Engineering or BOTH, as each program requires a separate license.
Innova will then send out a new license in the form of a LICENSE.txt file. Once you have received this, follow the instructions below:
For Well Seeker Pro:
Place the LICENSE.txt file in the Well Seeker Pro folder (most common directory path detailed below)
C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO
Same directory as Well Seeker.exe
If a LICENSE.txt file already exists in this folder, make a copy before you replace it. This can then be used as a temporary backup in case there are any issues with the new file.
For Innova Engineering:
Place the LICENSE.txt file in the Innova Engineering folder (most common directory path detailed below)
C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering
Same directory as Innova engineering.exe
If a LICENSE.txt file already exists in this folder, make a copy before you replace it. This can then be used as a temporary backup in case there are any issues with the new file.
If you experience any issues during this process, please contact sales@innova-drilling.com for support
When first installed on a new computer, Well Seeker PRO or Innova Engineering will give the user access to the full capabilities of each individual program via a 2 day evaluation license which is incorporated within the respective install file.
Well Seeker Pro and Innova Engineering each require their own separate license file.
Software licenses are computer specific. In order to generate a license, the user must provide Innova with their unique computer code, which is generated within the software itself.
If the initial 2 day evaluation license has not expired, and the user still has access to the program, then the computer code can be found as follows: Open either Well Seeker Pro or Innova Engineering and select Help - License info. This will open the License Details dialog.
Alternatively, if the user has Microsoft outlook, they can select E-Mail Code when in Well Seeker or Send Mail when in Innova Engineering. A populated email, like the one below will open automatically in Outlook. Additionally, input the user details, and any other information that may be relevant, prior to sending the email.
Alternatively, if the user has Microsoft outlook, they can select E-Mail Code when in Well Seeker or Send Mail when in Innova Engineering. A populated email will open automatically in Outlook. Additionally, input the user details, and any other information that may be relevant, prior to sending the email.
A new license will then be sent to the user via email and can be installed onto the computer in one of two ways, which are detailed in the next section.
There are 2 ways in which a new license can be added to Well Seeker Pro or Innova Engineering. These are both detailed below.
The user will receive an email from Innova containing a license text file for each of the respective software programs for a specific computer. To add the license file(s) follow the below instructions for the relevant software:
Place the license(s) on your desktop
One License is for Well Seeker Pro (WS_LICENSE.txt)
One License is for Innova Engineering (ENG_LICENSE.txt)
Ensure both programs are closed and add the relevant license file to the corresponding folder below, overwriting any other license text files that may already be present in the folder.
C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO
C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering
Once these files have been added, the user can reopen and run the software.
The second method for license addition is that Innova send a licence key, which the user pastes directly into the cell below, which is displayed when the trial license period has expired:
Once the code is pasted into the correct cell click ENTER CODE and then click OK.
If it becomes necessary to deactivate a license (to transfer an existing license to another machine for example), navigate to Help > License Info. This will open the License Details dialog. Click on the deactivate license button in the license info dialog. This process is carried out separately for Well Seeker Pro and Innova Engineering.
IMPORTANT NOTE: Once you select the Deactivate button and select OK in the following message window, you will no longer be able to access the Well Seeker Pro software on this computer, until a new valid license has been successfully installed.
Close and then reopen the software.
If you’ve successfully deactivated the license, the following window will be displayed:
If the user forgets to make a note of the Deactivation code, then Well Seeker Pro also writes a backup text file into the default file location on the user’s computer, which contains the deactivation code. This can be found in the file directory as shown below (WS - Deactivation Code):
For more information on our app and portal, or any of our other products, please contact:
sales@innova-drilling.com
US: +1 713-893-4435
UK: +44 (0) 7711411079
For more information on our new app or any of our other products, please contact:
sales@innova-drilling.com
US: +1 713-893-4435
UK: +44 (0) 7711411079
Alternatively visit our website:
Send it to
After this period has expired, if required, an extended evaluation license or the purchase of a license can be organised for each software package by contacting .
The user should highlight and copy the computer code and then paste it into an email and send it to . Note, that the computer code will be the same for both programs.
If your trial copy of Well Seeker PRO or Innova Engineering has expired, or your license is invalid, the computer code will be displayed on the start-up screen. The code can be copied to the clipboard by highlighting the code and pressing Ctrl + C. This can then be pasted into an email and sent to .
Once deactivated, copy the deactivation code and send this in an email (along with the computer code) to . Once received, a member of the Innova team will confirm deactivation.
If the user has any issues carrying out any of the detailed processes, please contact Innova for support at either of the following email addresses: or support@innova-drilling.com
Alternatively visit our website:
Alternatively visit our website:
Well Seeker X is available in two versions, 64 and 32 bit.
As a 64-bit program, Well Seeker X can access significantly more of your computers random access memory (RAM). This improves performance, allowing the program to perform memory intensive tasks faster and handle larger data sets.
In order to be able to run the Well Seeker X 64 bit version the PC must fulfil the below criteria:
64 bit operating system (OS)
To check the PCs OS version, right click on the Start Menu icon in your Windows task bar and select System. In the Device Specifications section, it will display in the System Type field what bit version of OS is installed.
64 bit Microsoft Office / 365
If Microsoft Office / 365 is installed on the user’s machine, and the user wishes to use the 64-bit version of Well Seeker X, then Microsoft Office / 365 must also be 64-bit. To check the PCs Microsoft Office / 365 version, open any Office program, e.g., MS Excel or Word. Select File > Account > About XXX, where XXX is the name of the software.
If either of these conditions are not met, then the user should install the 32-bit version of Well Seeker X.
Well Seeker X can be supplied as a zipped installation file which must be unzipped before use. Right click on the file and select “Extract All….” from the context menu.
Select a location which you wish to extract the files to and click “Extract”. The installation files will be extracted to the selected location in a folder called “Well Seeker X”
Once the files have been extracted, open the Well Seeker X folder and double click on the “Well Seeker X vx.x.x.exe” file to begin the installation process.
Select the location which you wish to install Well Seeker X. The default location is “C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x64)\”. If you wish to change the location the program is installed to click on the “…” button.
If you have read the terms and conditions and want to proceed without reading it again, click on the checkbox to agree with the licenses terms and conditions and click on “Install” to proceed.
If you wish to read the terms, click on “Licenses terms and conditions”, this will display the below screen. This information can also be printed for future reference by selecting the printer icon. Once read, select the “Accept” and “Install” button to begin installation.
The installer checks the computer for some prerequisite software, which is required for Well Seeker X to operate correctly. If any of these software items are missing from the computer, then the installer will go through the steps of installing them before installing Well Seeker X.
If the Microsoft ODBC Driver 17 for SQL Server is missing then the below figure will display. Select “Next”.
Read the Microsoft ODBC Driver 17 for SQL Server license terms. Select “I accept the terms in the license agreement”. Select “Next”.
In the Microsoft ODBC Driver 17 for SQL Server feature selection section, select “Next”.
In the Microsoft ODBC Driver 17 for SQL Server ready to install section, select “Install” and “Finish” when this installation is completed.
If the correct version of Visual C++ Redistributable for Visual Studio 2015-2022 is missing the bellow figure will display x64, x84 or both installations one after another. Click on the checkbox to agree with the license terms and conditions and select “Install” and “Close” once the installation is complete.
If another version of Visual C++ Redistributable for Visual Studio 2015-2022 is already present on the PC then the below window may appear. Select “Repair” and “Close” once the update is complete.
Once prerequisite software are installed, if the copy of Well Seeker X is genuine the user will be presented with a dialog showing the verified publisher as “Innova Drilling and Intervention Ltd”. If not the software is not genuine and should not be used.
Click “Yes” to continue the installation.
Once the installation is complete the final dialog will display “Well Seeker X (64) has been successfully installed”. Select “Finish” to close the dialog.
A Well Seeker X shortcut icon will have been added to the desktop and an entry for “Well Seeker X” will be in the start menu.
Finally, restart the PC to ensure that the Visual C++ Redistributable for Visual Studio 2015-2022 is fully functional, prior to opening Well Seeker X.
If after installation, the user experiences any issues opening Well Seeker X, consult the technical note.
Well Seeker X comes with a number of new and improved features compared to Well Seeker Pro. It also has a new user interface which may be unfamiliar for users accustomed to Well Seeker Pro. This document is designed to be a guide for users who are already familiar with Well Seeker Pro, and help them during the transition to Well Seeker X.
Unlike Well Seeker Pro, which is only available as a 32-bit program, Well Seeker X is available in both 32-bit and 64-bit versions. As a 64-bit program, Well Seeker X can access significantly more of your computers random access memory (RAM). This improves performance, allowing the program to perform memory intensive tasks faster and handle larger data sets.
For information regarding 64 bit version compatibility see Section 3.1.
The old method of accessing features using nested dropdown menus has been replaced with menu ribbons. Ribbons provide a much more user friendly way of accessing functions by displaying them directly on the screen in organized tabs, making it easier to perform actions, or change settings quickly without having to navigate through multiple nested menus.
You will find menu ribbons in the main Well Seeker window and in major dialog windows, such as the Daily Reports and Drill String Editor dialogs. The ribbons contain all of the functions previously contained in the dropdown menus, along with some new features.
To free up space for the main user interface, the ribbons can be shrunk by toggling on Simplified Mode in the top right corner of the Well Seeker X window.
The ribbon options can also be searched using the Search option in the top right of the main user interface.
The Database Tree has been renamed the Object Explorer and has a number of improved features.
Levels in the tree now have an Active Well Indicator, represented by a green number, which indicates how many currently active wells are contained under each level. Additionally, the database can be searched by entering a well or plan name in the search bar at the top of the tree.
Innova have made it easier to access Reporting and other dialogs such as the casing and lithologies – the user can now access these dialogs from the menu ribbon when at actual well or plan level. In addition to this, the criteria for option selection is now less strict. For example, in Well Seeker Pro, the user could only open the Cost Codes dialog in the main UI when the Well level was selected in the Object Explorer. In Well Seeker X the user can open the Cost Codes dialog when the Well level, or any of its child items are selected in the Object Explorer, i.e., Well, Actual Well, Survey, Plan or Planned Wellbore. This makes it simpler for new users to be able to select relevant options.
The quick access toolbar at the top of the main user interface gives the user customizable quick access to commonly used options.
The status bar at the bottom of the page is now interactive. The user can now click on the items in the status bar to:
Change unit sets.
Open current database location.
Start/Stop screen captures.
Open the real time data exchange.
Download IPMs.
View Data Sync status and toggle between online and offline modes
View WITS/WITSML status
View notifications.
Well Seeker X now has a dark mode. To toggle between light and dark modes, use the Style dropdown box, which you can find in the very top right corner of the Well Seeker X window.
In Well Seeker X, survey, plan and plot tabs can be detached completely from the Well Seeker window. Simply left-click on a tab and drag the tab outside the window. Drag the tab back into the Well Seeker window to restore it. This feature makes user customizable screen layouts even more achievable.
All Daily Reporting related dialogs have been reworked to improve performance, simplify the UI and reduce the need for double entry of data. Users familiar with the daily reporting system will notice that a number of features have been rearranged, or removed entirely. This section details the key changes to the Daily Reports system.
Job data has been removed from the Daily Reports window into it’s own independent dialog. This dialog can be accessed by selecting the Actual Well level, or below, in the Object Explorer and selecting the Job Data button from the Home ribbon in the main Well Seeker interface.
Data entered into this dialog applies to all daily reports. Other dialogs also source data from the Job Data – for example the Drill String Editor uses the rig name entered here.
The Well Status, DD Coordinator and MWD Coordinator settings have also been moved from the Daily Reports window to the Job Data dialog. This allows the user to set these values without needing to create a daily report.
A number of changes have been made to the way the Daily Reports window interacts with the Slide Sheet, to reduce user workload and remove double data entry.
The Get DDR from slide sheet and Get Params buttons have been removed. Instead, whenever the slide sheet is saved, the drilling activity is uploaded to Daily Reports. The daily activity section in the Daily Reports window will automatically populate with rotating and sliding activity, and the activity descriptions will be updated using the drilling parameters from the slide sheet. Activities uploaded from the Slide Sheet cannot be edited in the Daily Reports window.
24 hour & BHA run drilling parameters, drilling and circulating hours, etc. are all calculated from the slide sheet and stored in the background. To streamline the user interface, only fields that require user entry remain in the Daily Data section and the Mud Data section.
The Data Validation menu has been removed from the Daily Reports window in Well Seeker X. Instead, the program will scan the daily activities in real time. If any discrepancies are found, they will be highlighted in red to alert the user.
Additionally, in the Home ribbon there is a new Data Validation section that logs any errors found, along with a description. The user can use the controls to quickly navigate to each error
In addition to the key changes detailed above, the following minor changes have been made to simplify the UI and streamline data entry.
You can now rearrange the columns in the Daily Activity section in the same way that you can for survey tables, plan tables and the slide sheet. Simply left click and drag on the column header to move a column.
The toggle for using dropdowns for rig names & personnel has been removed. If any names have been entered into the Rig Names and Personnel Names tables (located in the Admin ribbon in the main interface) then dropdowns will automatically be enabled in the Daily Reports.
The Assembly Type and MWD Type selections have been moved to the Daily Data section.
Each day now has it’s own Personnel dialog. When a new day is created, the previous day’s personnel will be copied over. Field Supervisor and Drilling Supervisor have been removed.
Company Man’s Report options have been removed.
Date changes and report number changes will now not take affect until the user selects save. The user will be warned about duplicate dates when a date is selected, and will be warned about duplicate report numbers when clicking on Save.
Users familiar with Well Seeker Pro will notice that some fields that could be manually altered, such as the Date In/Out and the Depth In/Out, have been removed. This data is now automatically retrieved whenever Daily Reports are saved.
The major change to the Drill String Editor is to the Performance Report. The dialog has been greatly simplified to reduce the need for double entry of data and has been split into two separate dialogs – one for motor related data, and another for MWD data. These two dialogs can be accessed via the Drilling and MWD options in the Run Data section of the menu ribbon.
All drill string related reports, including performance reports, are now printed from the Drill String Editor using the Print BHA Excel and Print BHA PDF options in the menu ribbon. Additionally, some new tools relating to M/LWD have been added to the menu ribbon. These are referred to as the MWD Toolkit and are covered in the next chapter.
The Performance Report dialog has been greatly simplified in comparison to Well Seeker Pro. The user no longer has the option to manually enter drilling parameters or pull parameters from the Daily Reports. Instead, this information is automatically updated when the Slide Sheet is saved.
As a result, the dialog has been reduced to only the information that is still required to be manually entered: some additional run information, the reason for POOH and failure information. Additionally, the MWD run data has been split off and given it’s own dialog.
If running a rental job, data can be input within the Rental Data dialog, negating the requirement to fill in the daily reports for such jobs. Toggle on the Is Rental option to indicate that the job is a rental job and enter the relevant run details. When this option is toggled on, the data entered here will ignore any data from the daily activity section of the daily reports.
Well Seeker X adds three new MWD related tools to the Drill String Editor. In addition, the way that MWD surface system data is entered for performance reports has been updated. These tools can be found on the menu ribbon in the Drill String Editor.
The MWD Probe Config tool allows the user to define the probe arrangement within the MWD/LWD tool. Well Seeker X will then combine this information with the BHA details to calculate the sensor offsets.
The Probe Config requires data to be present in the Probe Catalog, as it uses this to populate the options for selection. The Probe Catalog is an organization level record of the exact probe measurements that are uniform to specific probes, which is stored on the organizations server. This catalog can be accessed from the menu ribbon and will automatically pull to the local database when using Well Seeker X with an internet connection.
The user can then use the MWD Probe Config tool to arrange the desired probes in whatever order they wish. The program will calculate the sensor offsets, and when the user clicks Apply, the offsets will be automatically added to the MWD/LWD component properties.
The MWD surface system has been separated from the motor performance report and given it’s own dialog. Items entered here are applied to all BHAs for the well, so that the user does not need to enter their information multiple times. If surface system components have been entered into the Inventory, they will be available here as dropdowns. If not, their serial numbers can be entered manually.
The Non-Mag Spacing Calculator from Innova Engineering has been added to Well Seeker X. This feature allows the user to predict the amount of non-magnetic material required above and below the directional sensor to keep interference from the drill string within an acceptable tolerance for uncorrected magnetic surveys. It can also evaluate whether the BHA meets these requirements.
To run the calculator, the user requires a completed BHA that contains an MWD/LWD component with directional sensor offset entered into the component details and magnetics data present within the Actual Well Properties. The user manually inputs the estimated Depth In and Out for the run and the maximum acceptable azimuth error. The calculation can be toggled between using the actual wellbore, or the principal plan for the well. Pole strength values are automatically assigned based upon the BHA components present, but these can be manually overwritten by toggling off the Auto slider and editing the pole strength values.
The Pressure Drop Calculator can be used to calculate the pressure drop across positive pulse transmitters / pulsers or restrictors. The user should select either POPPET or RESTRICTOR from the Type column, and then enter the relevant parameters to calculate the pressure drop.
If there is a MWD/LWD type component in the string, the user can check the Selected checkbox and when they save and close the dialog, the poppet, orifice and pulse width values will be added to the MWD component properties.
Well Seeker X is available in two versions, 64 and 32 bit. In order to be able to run the Well Seeker X 64 bit version the PC must fulfil the below criteria:
64 bit operating system (OS)
To check the PCs OS version, right click on the Start Menu icon in your Windows task bar and select System. In the Device Specifications section, it will display in the System Type field what bit version of OS is installed.
64 bit Microsoft Office / 365
If Microsoft Office / 365 is installed on the user’s machine, and the user wishes to use the 64-bit version of Well Seeker X, then Microsoft Office / 365 must also be 64-bit. To check the PCs Microsoft Office / 365 version, open any Office program, e.g., MS Excel or Word. Select File > Account > About XXX, where XXX is the name of the software.
If either of these conditions are not met, then the user should install the 32-bit version of Well Seeker X.
Only Well Seeker Pro or Well Seeker X can function on a PC at any one time. In order to use one, the other must first be uninstalled.
The below steps detail how the user can upgrade their installation of Well Seeker Pro to Well Seeker X:
Uninstall Well Seeker Pro using the “Programs and Features” feature in the Windows control panel.
Run the compatible Well Seeker X installer, available for download from the Innova Website. Follow the instructions on screen to install any required pre-requisite software. Once installation is complete, you will see the new Well Seeker icon on your desktop and in the Start Menu.
This section details some common issues that prevent Well Seeker X from installing or running, and how to resolve them.
Users should be aware that the version of Well Seeker X used to create a database will affect it’s compatibility with other versions of Well Seeker X and Well Seeker Pro.
The 64-bit version of Well Seeker X is able to open any database, whether it was created using 64-bit Well Seeker X, 32-bit Well Seeker X or Well Seeker Pro. However, 32-bit Well Seeker X and Well Seeker Pro cannot open databases that were created in the 64-bit version of Well Seeker X.
The following document will help to guide the user through the process of changing the depth reference (elevation) in Well Seeker for an existing plan or survey, which has an elevation already assigned.
In Well Seeker, the depth reference is entered at Well Level via the Well Properties dialog. This dialog is accessed via the database tree, by right clicking on the Well level and selecting Properties.
The user can then enter their depth reference data into the Depth Reference section, highlighted in red below. Multiple depth references can be entered at Well Level.
Once the user has entered their depth reference information at Well Level, they can then select the relevant depth reference for any plan or survey under that well. This is done by right clicking on the Actual Well or Plan level and selecting Properties. This will open the Actual Wellbore/Plan Properties Dialog. The user can then select the desired depth reference from the dropdown menu in the Depth Reference section, highlighted in red below.
If the Plan/Actual Well already has a datum referenced, then changing the depth reference in the Actual Wellbore/Plan Properties Dialog will prompt the following warning:
The user has three options:
Change TVD’s: Picking this option will change the MD and TVD values of the survey/plan points to reflect the new depth reference
Note: The TVD Subsea values will remain unchanged if the GL to MSL value is the same for both datums.
This option is usually selected when you have an existing well that was drilled with one rig and you are now planning to perform additional work with a different rig. In this situation the user wants to see the survey or plan depths adjusted to reflect the new datum.
Preserve TVD’s: Picking this option will preserve the MD and TVD values of the survey/plan
Note: The TVD Subsea values in this case will change.
This option is usually selected when a plan or survey has mistakenly been referenced to the wrong datum, and the user wants to assign a new datum, but not adjust the MD and TVD values.
Cancel: The change of depth reference is cancelled, and no changes are made to the survey/plan points.
Note: The user will also get this warning if they edit the value of a depth reference that is currently being referenced by a survey or plan.
In this example, we have a simple set of surveys, referenced to the below left RTE (RTE Plan) @ 100Usft AMSL.
We are then given a new RTE (below left RTE Actual) to reference @ 101Usft AMSL. When we select this new depth reference, the below right warning appears.
If we choose to Change TVD’s the surveys will change to the below:
The MD and TVD values have increased by 1Usft
The TVDss values have remained the same, except for the tie-on line
This would be desirable if you are side-tracking this well with a rig that has a RTE 1ft greater than the original rig.
If we choose to Preserve TVD’s the surveys will change to the below:
The MD and TVD values have remained the same
The TVDss values have changed by 1ft
This would be desirable if you discover that you have the wrong RTE referenced and want to reference the correct RTE without adjusting the survey depths.
A guide to installing updates in Well Seeker Pro and Innova Engineering
Occasionally there may be the requirement to update your software. This could be due to the addition of new features or it could be to deal with any bugs that have been discovered and fixed. Updating your software is an easy process which is detailed in the instructions below.
To begin with, ensure that the relevant program is closed.
You will receive an update file via email
Well Seeker.xxx (for Well Seeker)
Innova Engineering.xxx (for Engineering)
Save the file to either a designated folder somewhere in your C drive, or the desktop.
Go to the file and change the file extension from .xxx to .exe
Firstly, make sure that the file extensions are visible (if they are go to step 4).
In Windows 10, go to File Explorer and in the View Tab, select File Name Extensions
For older versions of windows, go to My Computer, in the Tools menu click Folder Options and select the View Tab. In the Advanced Settings box, click to clear the hide extensions for known file types check box.
Right click the file and select rename. Change the now visible file extension.
You will see the warning box displayed below. Select Yes.
This is important, because if the file extension is not changed, then the file will not work.
For Well Seeker Pro:
Place the Well Seeker.exe file in the Well Seeker Pro folder (most common directory path detailed below)
C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO
There will already be a file of the same name in this folder. Overwrite this file with the new one
Before overwriting, make a copy of this file (save it to a different folder) which can then be used as a temporary backup in case there are any issues with the new file.
For Innova Engineering:
Place the Innova Engineering.exe file in the Innova Engineering folder (most common directory path detailed below)
C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering
There will already be a file of the same name in this folder. Overwrite this file with the new one
Before overwriting, make a copy of this file (save it to a different folder) which can then be used as a temporary backup in case there are any issues with the new file.
You have now installed the latest update and can open and run the programs as usual.
If you experience any issues during this process please contact sales@innova-drilling.com for support.
Well Seeker X comes pre-installed with the latest generic surveying error model tool codes issued by the ISCWSA. However, on occasion the user may want to add their own custom tool codes to the software. Usually this is to model the survey performance of a specific tool.
Most surveying tool manufacturers issue their tool codes as IPM (Instrument Performance Model) files with the “*.IPM” file format. If the user has received an IPM file they can follow the instructions in Method 1 below to add it to Well Seeker X. If the user does not have the IPM file but has the details of the tool code, they can enter them manually into Well Seeker X by following the instructions in Method 2.
Open Well Seeker X. Select the Settings tab and select Open in the Setup File section. This will open the Well Seeker Roaming folder in a new window.
Open the IPM folder.
Close Well Seeker X.
Paste your IPM file into the IPM folder.
Open Well Seeker X.
Your new IPM will now be available to select from the dropdown menus in the Survey Properties window and the Plan Properties window.
Open Well Seeker. Select the Tools tab and select Survey Tools from the IPM Files section.
Click the Add new IPM button.
Enter a suitable file name and hit save.
Search for the new name in the Search field, select the relevant option in the Survey Tools table and then click on the Edit button.
If required, you can enter a new name for the survey tool in the Survey Tool Name box, and a description in the Description box. Enter the relevant co-efficients into the table. As you enter a row into the table, the software will create a fresh row underneath so that you can continue. When you are finished, click on the Save button.
Your new IPM will be available to select from the dropdown menus in the Survey Properties window and the Plan Properties window.
The purpose of this document is to take the user through some of the steps required to set up the program and get to the stage where they can create a plan and survey.
This document assumes that Well Seeker X has already been installed (see Manual for Install guide) and this is the first time the program has been opened.
When you first open Well Seeker X, the screen will be configured as below.
The layout of the ribbons can be changed to simplified mode, by selecting the toggle button in the top right corner of the screen. Simplified mode hides the text in and compresses the area taken up by the ribbon.
The user can also toggle the style between Light / Dark Modes.
The Object Explorer and Notifications panes can be toggled on/off by selecting the relevant option in the Settings tab.
The Object Explorer and Notifications panes also have an auto-hide option that allows them to be hidden, and only visible when the relevant side pane is hovered over with the mouse.
The size of the text in the grids can be adjusted by selecting an option from the dropdown menu of the AB cell in the Grids section of the Settings Ribbon.
The local database is the .mdb file that Well Seeker X is directed to access information from. It is vitally important that the user is aware of the location of and backs up their database file regularly to another storage device. If this is done correctly then the user will always have a backup in the event of an unforeseen event such as a computer hard drive failure, that would have otherwise resulted in the loss of the database file and all the input data. The local database can be quickly backed up by going to Home > Backup Database.
The first thing to do when creating a new database is to select where you want to store the database on your computer. Ideally you want to put it somewhere where it will not need to be moved.
Create a folder somewhere in the C: drive and name it appropriately.
Go to Home > New.
The window below will appear.
Navigate to the desired location where you will save the new database and enter your database name in the File Name: box and click Save.
The new database will now have been created as a .mdb file at your chosen destination.
Go to Home > Select, browse to and select the database you have just created.
You have now created a new database and your screen should look like above, note that the database you have selected will be displayed at the bottom of the screen as highlighted by the red box.
To back up your database file go to Home > Backup. This will open a dialog box where you can choose a suitable location and name for the backup.
It is very straightforward to switch between databases, making it easy to maintain multiple databases depending on the user's needs.
Go to Home - Select.
Go to the location of the database you would like to use.
Select the database and select Open.
The new database will now be selected and can be used.
The following section details the steps to follow in order to create a new well.
The first thing to do is to make sure that you have the correct units selected.
This will open the Unit Sets dialog box
Well Seeker comes as standard with 5 unit sets (API, CAD, ND, SI & US), which are all editable.
There is also the option to create a new unit set using the Create new button. To edit a new unit set, click on Edit button. This will allow the user to access the unit drop down menus to change the parameters to the desired units.
Depth: Current units for measured depth and TVD. Options are Feet, US Feet and Meters.
Diameter: This defines the units used to display Casing OD and ID as well as hole size. Options are mm and inches.
Dogleg: The current units DLS, BR and TR are displayed in. Options are Deg/100ft (or 30m), Deg/30ft (or 10m), Deg/10ft (or 3m), or user defined. If user defined is selected, the parameter column becomes active and the units value becomes degrees per unit length based on the parameter entered.
Flow Rate: Current units for flow rate. User can choose between LPM and GPM.
Pressure: Current units for Pressure. User can choose between psi, bar, Kpa or Km/cm2
Volume: Current units for Volume. User can choose between BBLS and m3
Mud: Current units for Mud Weight. User can choose between PPG, SG, psi/ft3, lbs/ft3 and Km/cm3
Weight: Current units for Weight. User can choose between klbs, Tons and kdaN
Unit Weight: Current units for Unit Weight. User can choose between lb/ft and kg/m
Torque: Current units for Torque. User can choose between kftlb and kNm
Temperature: Current units for Temperature. User can choose between degC and degF.
Cost: Current units for Cost. User can choose between $, EUR and GBP.
Jets: Current units for Jet size. User can choose between in2 and mm2.
Magnetics: Current units for Magnetics. User can choose between Geolink/Tensor, SSP/SUCOP (ut), nt, nt (no XY), uT (XY Inversion) or EVO/Applied.
Accelerometer: Current units for Accelerometer. User can choose between G, mG, G Invert Z Axis or mG Invert Z Axis.
Whatever is selected here will be applied to the whole database. It can be changed at any point, but the units are set for the whole database and not individual operators or wells.
It is possible to create an instant plan or survey in Well Seeker. This can allow the user quick access to the planning tools without having to go through the process of filling in all the different levels of data to get there. For this kind of requirement, surface locations, elevations etc are of no concern and Well Seeker uses generic values at all the levels.
To create an instant plan or survey, right click on the database and select New Instant Plan or New Instant Survey.
Right click on the database and select Insert New Operator.
The Operator Properties dialog will now appear.
The Operator level is where the user sets up the company anti-collision policy, and it is very important to ensure this is done correctly.
This is also the level where the primary and secondary logos are added. These logos are then available to be included on generated reports.
Right click on the Operator and select Insert New Field.
The Field Properties dialog will now appear.
The following data is input at this level:
Mapping Grid or Coordinate Reference System (CRS). If the required CRS is not available a new one can be added (see the Adding a New Coordinate Reference System section).
Local Coordinate system:
Well Centred - Local coordinates for all plans & surveys will be referenced to the well location making all local coordinates 0.00N & 0.00E at surface.
Facility Centred - Local coordinates for all plans & Surveys will be referenced to the facility location meaning local coordinates at surface will vary between wells.
Apply Scale Factor: If this option is selected, the scale factor defined in the CRS will be used to calculate map co-ordinates from local co-ordinates. This is the ratio between measured distances on the map compared to measured distances on the ground as a result of distortion of linear scale associated with mapping a spherical surface (the earth) onto a plane. Note that this option does not affect the local coordinates, only the map coordinates (Northing and Easting’s).
Show Map: This extends the existing dialog to include a Google Maps section. This will show the location of the positional data entered and can be toggled between map and satellite view using the Satellite checkbox. The map can also be zoomed in and out using the mouse scroll wheel and – + keys. This map location will only be accurate if the CRS selected uses WGS 84, as this is what Google Maps utilises.
Show Field Ref Point on Report: When selected, the field reference point coordinates will be included in the Field data box of any report generated. Default is off.
Field Reference Point: This is the reference location used for the field.
Input: Select the coordinates used to enter the Field Reference Point. Either Latitude & Longitude or Grid Easting & Northing.
Grid Convergence is not editable as it is based on the CRS selected and the Field Reference Point entered.
System Vertical Datum: This is the datum which all TVDs below field level will be referenced to. This is usually either mean sea level “MSL”, lowest astronomical tide “LAT” or some other user specified value. If a value other than MSL is selected from the combo box, the elevation above or below MSL must be entered. A positive value indicates that the datum is above mean sea level and a negative value indicates it is below it.
Once the required inputs have been completed, click Apply then Close on the bottom right of the window. To access the Field Properties again at any time, right click at the Field level and select properties.
Right click on the Field and select Insert New Facility
The Facility Properties dialog will now appear
The following data is input at this level:
Azimuth North Reference: Grid or True.
A slot template can be created by Clicking on the Templates button (see Creating a Slot Template section for more detailed instructions)
Lease /Hard Lines: The user can select to have lease / hard lines show at all levels within the Targets dialog. On will pre-select the lease / hard lines to be displayed from Field to Actual / Plan levels. Off will pre-select the lease / hard lines to be displayed from Field to Facility level only.
Show Map: This extends the existing dialog to include a Google Maps section. This will show the location of the positional data entered and can be toggled between map and satellite view using the Satellite checkbox. The map can also be zoomed in and out using the mouse scroll wheel and – + keys. This map location will only be accurate if the CRS selected uses WGS 84, as this is what Google Maps utilises.
Facility Reference Point: This is the reference location used for the facility. For an offshore platform, this is usually platform centre and for an onshore facility, this is usually the centre of the site. This location will provide the Local Coordinates of 0.00N & 0.00E if Facility Centred Local Coordinate System was selected in the level above
Input: Facility Reference Point Select the units used to enter the Facility Reference Point. Either Latitude & Longitude or Grid Easting & Northing.
Grid Convergence is not editable as it is based on the CRS selected and the Facility Reference Point entered.
Facility Location Uncertainty: The uncertainty of the facility location to 1 sigma. If unknown, leave as 0.
Slot Radius: Radius of the slot.
Rig Directions: Area to input directions to the rig site for the rig crew to follow.
Once the required inputs have been completed, click Apply then Close on the bottom right of the window. To access the Facility Properties again at any time, right click at the Facility level and select properties.
Right click on the Facility and select Insert New Well
The Well Properties dialog will now appear
The following data is input at this level:
Location Uncertainty: The uncertainty of the Wellhead location to 1 sigma. If unknown, leave as 0.
Wellhead Location:
Slot: This allows the user to select any of the slots created in the template editor and the location will be automatically input based on this selection
Offset from Facility: This is the local Coordinates which allows the user to enter the distances at surface between the facility location and the wellhead location
Map: Input location as Grid Easting & Northing
Geographic: Input location as Latitude & Longitude
Depth Reference: Allows the user to input the relevant elevations. Default is for an onshore well with Ground Level to MSL, however If “offshore” is selected, the user can enter the well head elevation above MSL. If “subsea” is selected, the elevation below MSL can be entered. This is the distance between the top of the well head and MSL. By checking the Default box, the selected elevation will be automatically assigned to any new plans or surveys created.
Show Map: This extends the existing dialog to include a Google Maps section. This will show the location of the positional data entered and can be toggled between map and satellite view using the Satellite checkbox. The map can also be zoomed in and out using the mouse scroll wheel and – + keys. This map location will only be accurate if the CRS selected uses WGS 84, as this is what Google Maps utilises.
Once the required inputs have been completed, click Apply then Close on the bottom right of the window. To access the Well Properties again at any time, right click at the well level and select properties.
Right click on the Well and select Insert Planned Well.
The Plan Properties dialog will now appear.
The following data is input at this level:
Set as Principal Plan: Selecting a plan as the principal sets it apart from the other plans as the most important one, and it also tells Well Seeker to use it as the reference plan when the user is in a survey file under the same well. When inputting surveys, Well Seeker will display details telling the user how far away, Toolface, X & Y offset etc the survey is from the principal plan.
Complete: Selecting a plan as Complete will allow it to be filterable within the select offsets dialog.
Tolerance Circles: Tolerance circles are for visual reference only. The radius of the inner and outer tolerance circles can be added here. These can be displayed in a plan or spider plot by selecting their inclusion in the chart properties dialog. The default colours for the inner and outer tolerance circles can be adjusted in the Chart Defaults > Tolerance Circle menu.
Survey Tools: The Survey tool editor can be accessed from here by clicking on the Survey Tools button located beside the Apply button.
Vertical Section: The VS azimuth and the local origin of the VS.
Depth Reference: This will be the selected default (from Well Level), but can be changed by selecting options from the drop down list.
Magnetics: Magnetic data can be generated here by selecting the model and the date. If the relevant model is not available, user defined details can be added. Several lines can be added to the magnetics table; however, only the data which is checked as Active will be used by the program.
Tie-On / Sidetrack Details: If plan is to be tied on to another well or plan, check the Plan is tied to box and the user will be able to select the plan or survey that will act as the mother bore as well as determining the Tie on / ST depth. By then selecting Create Sidetrack, the Survey program will be populated with the relevant details from the mother bore. The Error Starts selection of ST Point or Surface will determine where the ellipse of uncertainty calculations will begin, when compared to the tied to well/plan for anti-collision scans.
Export Geomag Data: Exports the geomagnetics data as a document. Select the line in the Magnetics section that you want to export the geomagnetics data for. Then select the report format as PDF or Excel from the drop down menu, before selecting Export to generate the report.
Survey Program: This is where you create the survey program and assign the relevant error models to the plan. At this stage, because there is no plan yet this will remain incomplete (to be completed once a plan has been created). Error model can be assigned at this point by selecting from the drop down menu below IPM. However, if the plan is a sidetrack, then the details of the survey program from surface to ST depth can be entered. This will be done automatically when completing the Sidetrack details section.
Tie-on: Allows the user to select where the plan is tied on. This can be from surface, a user defined point where the tie-on line can be manually typed in by the user or from an existing survey or a plan. This will be automatically populated when the Tie-On / Sidetrack Details section is completed.
Force Colour: Selecting this option and choosing a colour will ensure that this plan will always be displayed in this colour in all of the plots. This supersedes any colour options for this plan in the Chart Properties dialog.
Once the required inputs have been completed, select Apply then close
To access the Plan Properties again at any time, right click at the Plan level and select properties
The object explorer should now look similar to the one below. In order to open the plan, the user must double click the Plan level of the database tree, and the plan window will open in the right hand pane. The plan can then be entered manually using MD, INC and AZI, or the Planning Tools at the bottom of the screen. Once a plan has been created click Save. For more details on the Planning Tools, see Appendix A.
When you select save for the first time, and again any time the plan is changed, the user is asked "Do you wish to add this plan to survey program". Select Yes. This will automatically update the survey program.
To check & edit the survey program, or assign an error model, open the Plan Properties. Left clicking on the Plan/survey column will reveal a drop-down menu with the available options. An appropriate error model can be selected from the drop-down list in the IPM column.
Click Apply and then close to save this selection.
To view the plan listed every 30m (100ft), double click on the Planned Wellbore level of the database tree and it will open this in the right-hand window. This is the definitive plan listing which is used in charts and anti-collision / distance calculations
When you have a plan selected, it is possible to choose what data you would like to be displayed by going to Settings > Show / Hide Columns.
Or by searching in the ribbon search bar in the top right corner
The user can choose which columns to be displayed. It is worth noting that the following columns will only be displayed for a survey (not a plan) even though they are selected, and will only be populated if one of the plans is selected as Principal:
Up Down
Left Right
Distance to Plan
Closure Azimuth - can always be displayed in a survey regardless of whether there is a principal plan selected.
Closure Distance - can always be displayed in a survey regardless of whether there is a principal plan selected.
TFO+Azi
TFO Highside
Slide Seen Only displays if slide sheet data exists for the interval in question
Slide Remain Only displays if slide sheet data exists for the interval in question
Motor Yield Only displays if slide sheet data exists for the interval in question
BR to Land
The Targets properties box can be accessed from field level down by right clicking on the required level (Field, Facility, Well, Plan or Actual Well) and selecting Targets.
Click on Add Target and the Target Properties section will become editable for the new target.
Target name, target center coordinates and display colour and line style can be selected.
If supplied with an azimuth and a horizontal displacement, target coordinates can be calculated by adding these values and selecting calculate. All target centre coordinates will be populated.
Drillers target can be calculated by selecting the desired confidence level (95% is the default) and selecting Create Drillers Target:
You will then be prompted to select the relevant plan before the calculation is done.
If the planned well path does not pass through the target, the calculation will not be carried out.
The size of the drillers target is affected by the Survey tool which is assigned to the plan - The more accurate the tool, the larger the drillers target.
Target shape, size and orientation can be selected by clicking on the desired tab at the centre right of the dialog.
The level that a target is created on will be displayed in the filter section. A target created at the Field level will only be seen at that level. A target created at plan level can be seen at all levels.
To see a target created at field level at plan level:
Open the target properties box at plan level - you will not be able to see the target.
Click on the Filter drop down menu and select Field.
You will now be able to choose which levels the target will be visible on. Just check the required box and click Save.
Lease lines and hard lines can be created by adding a target and selecting Polygon. The lease / hard line coordinates can then be entered in the same way as a polygon target. Once complete, the user should check the “Is a Lease Line” or “Is a Hard Line” box.
It is important to understand that once this has been checked, Well Seeker will see this as a lease line and not a target. The next time the user opens the target box, the lease / hard line will no longer be visible. To see the lease / hard lines, the user can select the “Show Lease Lines” option in the filter. This filter will hide the targets and display only the lease lines.
NOTE, that both targets and lease / hard lines will be available to plot and can be manipulated in a similar way in the chart properties dialog in the plots.
Casings can only be added at Actual Well and Plan level:
Right click on either and select Casing, and the casing details will appear.
The user can now fill in the required information.
Lithology details can only be added at Actual Well and Plan level:
Right click on either and select Lithologies, and the Lithologies box will appear.
The user can now fill in the required information.
Annotations can only be added at Actual Well and Plan level:
Right click on either and select Annotations, and the Annotations details will appear.
The user can now fill in the required information.
Right click on the Well and select Insert new actual well.
The Actual Wellbore Properties box will now appear.
The initial set up of the Actual Wellbore is the same as for a plan. Refer to Creating a New Well Plan Section.
Once the required inputs have been completed, click Apply then Close.
To access the Actual wellbore Properties again at any time, right click at the Actual Well level and select properties.
Right click on the Actual Well and select Insert new survey
The Survey Properties box will now appear
The user can select the appropriate Survey tool and select a tie-on.
Once the required inputs have been completed, click Apply then Close.
To access the Survey Properties again at any time, right click on the survey and select properties.
To enter the survey and add survey stations, double click on the survey you wish to add to, and the survey grid will open in the right-hand pane.
Once the survey has been entered, select Save
A prompt will appear which asks, "Do you wish to add this survey to the survey program?". Select Yes.
Once a survey has been created and saved, the next step is to go back to the Actual Wellbore Properties and check the Survey program. Clicking on the Survey column will reveal a drop down menu with the available options. Any surveys which have been created below the Actual Wellbore will be available to select. Since a survey tool has already been assigned to each individual survey the IPM column will be automatically populated.
Click Apply and then Close to save this selection.
Once a survey has been added to the survey program, if new survey stations are added to the survey, on saving, Well Seeker will again prompt the user Do you wish to add new surveys to the survey program? Selecting yes will update the survey program Depth To column to include the latest surveys.
The Actual Wellbore is where the user can view the survey program listing.
Double clicking on the Actual Wellbore displays an un-editable definitive listing which contains all the surveys assigned within the survey program. This listing is used in charts and anti-collision calculations
It is possible to import a Compass .xml file into Well Seeker. This file is an export file from Compass which contains details of plans, surveys, targets, error models etc. When this file is imported, all the information will be used to create the relevant wells within Well Seeker.
To import a Compass .xml file, select Home > Import EDM. This will then open a screen which will allow the user to navigate to the relevant file and select it.
Once selected, Well Seeker will begin the import process. The time taken for this process will vary based on the size of the import.
Compass Import Settings: This option opens the compass import settings dialog, where the user can select the appropriate settings they desire when importing data from a Compass EDM file.
Targets and Lease Lines: Allows the user to either include or omit targets and lease lines when importing. The user can also choose if imported lease lines are automatically assigned to their appropriate wells.
Surveys Tools: When checked, Well Seeker will import any survey tools associated with the relevant plans and surveys. If unchecked no survey tools will be imported. Note, that if survey tools are not imported, and any of the imported plans and surveys reference a survey tool which is not available on the imported computer, then Well Seeker will use the default error model selected by the user.
Well Plans: This option allows the user to import ALL plans which are contained within a Compass Export file. If this option is not selected, then Well Seeker will only pull in the plans which are selected as PRINCIPAL in the export file. Default is ON.
At Facility level, it is possible to add a slot template. When in the Facility Properties window, select Templates, and the Template Editor window will open.
Properties: Select Create New to create a new template:
Select Template: This will populate automatically once the Name box has been completed and the template has been saved.
Name: Add the relevant name.
Slot Prefix: This will appear in front of all slot names.
Template Centre Relative to facility: This is only available when Rectangle or Circle is selected in Geometry. Allows the user to offset the centre of the template relative to the facility location entered in the Facility Properties window.
Geometry: Select from Rectangle, Circle or Single Slot. Single slot allows the user to create a slot template that is not a predefined shape and is made up of individually entered slots.
Rectangle: Contains available options related to the Rectangle Geometry and will only be editable when the Rectangle option is selected.
Circle: Contains available options related to the Circle Geometry and will only be editable when the Circle option is selected.
Convert to Single Slots: This option allows the user to convert rectangle and circle templates into single slots. This action is not reversible once it is selected.
Display slot names: Displays the names of the slots on the plan view on the right.
Slots: This is where the slot Name and local coordinates are input. The local coordinates are generated automatically for the Rectangle and Circle Geometry and are fully editable for the Single Slot option.
When a slot template has been created select apply to save
When more than one template has been created, the relevant template can be selected from the Select Template drop down menu at the top of the screen.
You may find yourself in a situation where you are required to do planning referencing a CRS which is not available in Well Seeker. In this situation the information relating to the CRS should be requested from the client and can then be used to create a new CRS in Well Seeker.
The below screen shot is an example of the type of information which will be supplied by the client.
The following instructions detail how to use this information to create a new CRS.
Open the Geomagnetic Calculator by selecting Tools > Geomag Calculator.
Click on the "Mapping Grid" button at the top left of the dialog.
Select Add at the top left of the Mapping Grid.
Select the New CRS in the CRS list and click on Edit at the top left and now you have a blank template which you can start adding information to.
Parameters in RED below are important and affect the output - Care should be taken to enter the data correctly
Name: This can be anything you want as it has no impact on any of the calculations. In Well Seeker, the naming convention is the System / and then the Map Projection, and it is recommended that this convention is followed. For this example, the name would therefore be Polska 1992 / Transverse Mercator (Gauss-Kruger) Zone 3
Area of use: Description of which part of the earth this CRS references and has no effect on any of the calculations. For this example all we know is it is in Poland.
Datum: This is just text and does not directly affect any calculations. For this example it is WGS1984.
System: This is just text and does not directly affect any calculations. Polska 1992
Ellipsoid: This is important and you have to choose from a drop down list of 38 options. In this example you would choose WGS 84
Semi Major Axis (m): This is the Equatorial Radius of the Ellipsoid and is automatically populated based on the ellipsoid selected.
Semi Major Axis (UOM): This is the equatorial radius of the ellipsoid in the units of measure which the CRS is using and is automatically populated based on the ellipsoid selected.
Units of Measure: This is a drop-down menu option and you can choose from 7 options. For this example, it would be metre
Inverse Flattening: This is the inverse Flattening of the Ellipsoid and is automatically populated based on the ellipsoid selected.
Map Projection: This is just text and does not directly affect any calculations - Transverse Mercator (Gauss-Kruger) Zone 3
Projection Type: This is a drop-down menu and you can choose from 4 options – TM, 1SP (Standard Parallel), 2SP or STEREO. In this example, choose TM.
False Easting: 500000.00 m.
False Northing: -5300000.00 m.
Latitude of Origin: This should be input as a decimal - 0.0000 deg.
Longitude of Origin: This should be input as a decimal - 19.0000 deg.
Scale Factor: Ratio between measured distance on the map and on the ground - 0.99930 deg.
1st Standard Parallel: This information will be required if you select 1 SP or 2 SP from the Projection Type Drop down menu - Not applicable here
2nd Standard Parallel: This information will be required if you select 2 SP from the Projection Type Drop down menu - Not applicable here
The Screen shot below is what your new CRS should look like based on the information detailed above:
Select Save CRS and your new CRS will be available to select from the mapping grid dropdown menu.
Once wellbore or plan data has been input, it can be viewed in charts. All charts are a graphical representation of a reference data set. Which data set the chart is referenced to depends upon the actual wellbore, survey, plan or planned wellbore that is currently open and selected by the user when the plot is opened.
With the desired reference data table open and selected, click the required chart icon from the Home toolbar.
The charts can be zoomed using the mouse scroll wheel and panned by holding down the left mouse button and moving. Right clicking anywhere on the chart opens a context menu, with plot dependent options.
A chart can be copied to an image file by simply selecting the Chart Image icon in the bottom of the main UI.
As well as the reference data the charts can also display offset well data. In order to select which wells, surveys or plans are classed as offset well data the user must use the Select Offsets dialog icon in the Home toolbar.
When in a chart, to select an offset survey or plan, click on the Offset Selector. This will open the select offsets box and allow the user to select the relevant offsets.
Once these have been selected and the dialog box has been closed, the user can then display the offsets on the plot by selecting the Show Offsets icon.
Once a plot is open the user can then open the Chart Properties by selecting Chart Properties or by double clicking in the chart in question.
This is where most of the chart functionality is located, and allows the user to add labels, change colours and customise the plot.
To adjust the chart zoom, all the user need to do is select the plot and scroll the mouse wheel.
Any time the user Zooms in, the Chart Grid section in the Chart Properties updates to match. In the below, the plot was zoomed to show the point of interest. The chart scales are greyed out but match the plot. The plot was then manipulated using the chart scales option to fine tune the output.
Grid Lines can be added and manipulated from the Chart Properties. The user can also select the distance between major and minor tick marks on the plot. When a chart is first opened, the boxes are greyed out and empty. To manually select these values the user needs to check the boxes, and they will then be able to adjust the line spacing as required. The grid line colour can also be selected from here.
It is possible to select plot defaults, which will be applied each time a plot is opened. These default selections are available in the main UI on Home > Chart Defaults.
The selected defaults apply to the individual charts as well as the charts created in the WPC.
In addition to the individual Plan View, Section View and 3D View plots, Well Seeker X also has a Wall Plot Composer (WPC), where different plots, images and data tables can be displayed and then output together.
As with the individual plots, the WPC option only becomes available when the user is in a plan, survey, planned wellbore or actual wellbore.
The first thing to do after clicking on WPC is to ensure that the page is setup as required. The default page layout will be A4 Portrait view. To change this, click on Page Setup. The user can then choose sizes ranging from A0 to A7 or User Defined.
The user can then start to build the wall plot by inserting the desired Charts and Tables. This can be done by clicking on Charts and Table from the top menu or by right clicking anywhere on the plot.
In the Home option at the top left of the WPC screen, the user can select to Save or Open an existing wall plot composer template. These templates are saved as .wpc files and allow the user to save the template they are working on and come back to it at a later date.
When a table is inserted into the WPC, it will be a fixed size. Like the plots, manipulating the border changes the size of the table or logo. If the table or logo has been stretched out of shape, it will auto adjust to its standard ratio.
The toolbar Layout tools allow the user to line up the edges of items in the wall plot for neater presentation. The available options are left, right, top and bottom alignment. Click on one item, press CTRL, click on the second item, and select one of the alignment tools in the Home > Layout menu. The first object will move so that its edge lines up with the last selected object. Multi-select of objects can be achieved by holding down shift and selecting the items.
It is possible to adjust the screen zoom. This option allows the user to zoom in, to look more closely at a particular section of the plot, or to zoom out to look at the whole plot. This feature can be accessed via Home > Zoom menu.
The user can also hold CTRL and scroll the mouse wheel to zoom in and out.
When viewing a plan, the well planning tools will be displayed at the bottom of the window.
Selecting one of the seven planning tools displayed will activate other options to configure the chosen tool. Once all options have been entered, click on the calculate button to add it to the well plan. Below is a description of each available planning tool:
The adjust planning method is a simple tool that will draw a curve with the minimum dogleg required to reach the desired inclination, azimuth and distance from the current point. The exception to this is the INC, AZI, DLS option – In this case the planning tool will calculate the build/turn values required to reach the desired inclination and azimuth while keeping to the desired dogleg.
MD, INC, AZI: Enter a MD, an INC and AZI in the text boxes in the parameters section.
CL, INC, AZI: Enter a CL, an INC and AZI in the text boxes in the parameters section.
INC, AZI, TVD: Enter an INC, an AZI and a TVD in the text boxes in the parameters section.
INC, AZI, DLS: Enter an INC, an AZI and a DLS in the text boxes in the parameters section.
The build / turn planning method is a 3D planning tool in which consecutive surveys have a constant build / turn rate between them. The well path produced by this method is effectively describing a trajectory travelling around a cylinder.
MD / CL: Enter an MD or CL, build rate and a turn rate and click on the “Calculate” button.
INC: Enter a build rate and a turn rate and an INC and click on the “Calculate” button.
AZI: Enter a build rate and a turn rate and an AZI and click on the “Calculate” button.
TVD: Enter a build rate and a turn rate and a TVD and click on the “Calculate” button.
The dogleg tool face method is a 3D planning tool where build rates and turn rates will vary between survey stations depending on the dogleg and tool face setting requested.
MD / CL: Enter an MD / CL, DLS and TFO and click on the “Calculate” button.
INC: Enter a DLS, TFO and an INC and click on the “Calculate” button. The trajectory will be calculated until the required INC is reached. If the INC selected cannot be reached, an error will be displayed.
AZI: Enter a DLS, TFO and an AZI and click on the “Calculate” button. The trajectory will be calculated until the required AZI is reached. If the required AZI cannot be reached, an error will be displayed.
TVD: Enter a DLS, TFO and a TVD and click on the “Calculate” button. If the TVD cannot be reached, an error will be displayed.
TANGENT: There are two methods available for the tangent option:
Tangent – HC (Hold Curve): The HC option draws a tangent section then a curve to hit the target
Tangent – CH (Curve Hold): The Curve Hold draws a curve to line up on the target then a tangent to hit the target
The Curve Hold method allows a larger number of targets to be reached. A NS, EW and TVD value must be entered. This can be done manually or by selecting an existing target. Lastly the DLS of the curve must be selected. If the target cannot be reached with the parameters specified, an error will be displayed. Usually increasing the DLS allows the target to be reached or changing the method from hold curve to curve hold.
POINT: Enter a NS, EW and TVD; this can also be done by selecting an existing target from the drop-down menu. The well trajectory will be turned using the minimum possible dogleg to reach the point. This method describes a constant curve to the target. If the required point is on an existing plan, this can be achieved by selecting plan from the target details section, choosing the relevant plan from the drop-down menu and selecting the appropriate MD. This MD relates to the point on the offset plan and Well Seeker will automatically populate the NS, EW and TVD based on this selected point.
The Hold function causes the trajectory to travel in a straight line at the current inclination & azimuth until at reaches the specified distance or depth:
CL: Enter a CL (Closure Length) and click on the “Calculate” button.
MD: Enter an MD and click on the “Calculate” button.
TVD: Enter a TVD and click on the “Calculate” button.
VS: Enter a Vertical Section and click on the “Calculate” button
The optimum align function is a powerful tool for lining up on targets at specified inclinations and azimuths. It is particularly useful if multiple targets are to be hit. The trajectory produced is usually a 3D S-shape profile, which can be defined either by specifying two curve sections and a hold or by using two curves. If “Curve Hold Curve” is used, the doglegs for both the curve sections must be specified. For a “Curve-Curve” method, only the dogleg for one of the curves must be entered. If “Balanced” is selected, Well Seeker X will attempt to create a profile using the same dogleg for both curves.
When selecting a point to hit, the user can choose any available targets from the drop-down menu or enter the N/S, E/W and TVD values manually using the user defined option. Then select the appropriate optimum align parameters and required dogleg, and enter the desired inc and azi and click on the “Calculate” button
If there are 2 targets and the user requires the plan to “line up” the first target with the second, the second target can be selected from the line up drop-down menu. Well Seeker will calculate the tangent inc and azi between the 2 targets and automatically enter these values into the relevant boxes.
It is also possible to line up on an existing plan. When Plan is selected, the user can choose the relevant plan from the drop-down menu and the relevant MD on the plan that they would like to hit. The coordinates and TVD of the point on the plan will be automatically entered and the inc and azi will mirror that particular point on the well plan.
If the optimum align method cannot reach the desired inc and azi at the target point, an error message will be displayed. Usually increasing the doglegs will allow the target to be reached.
If the user has multiple targets to hit, then one way to achieve this is by clicking on “Thread” function in the target details section. No planning method needs to be selected to open the Thread targets dialog; however, the feature utilises the Optimum Align functions when generating plans. Targets are available to select via a drop down menu at the top of the dialog, and the planning method options are selected at the bottom of the dialog.
The 2D well planning tools are designed to allow a well from surface to be planned with a single click. The 2D planning tools have multiple build /drop rates but only one horizontal plane (azimuth). There are two options available: S-Well and Slant Well. The S-Well profile can either be a standard S where the inclination is dropped back to vertical at the target, or a modified S where a specified inclination greater than zero is reached at the target. The slant well has a constant build up rate and a specified kick off point to reach the target.
To use this method, the KOP must be entered (the inclination will be vertical to this point), the DLS of the initial build (BUR 1) and then the drop rate (BUR 2).
The user then has two additional options to choose from, final inclination (Fin Inc) and final hold length (Fin Hold). The user can choose to select none, one or both of these options via the checkbox to the right of the corresponding cell. The final details required are the target NS, EW and TVD. These can be entered manually or by selecting a target from the drop-down menu. If the target cannot be reached with the specified parameters, a warning message will be displayed.
No Checkboxes selected: When the user does not select either the Final Inclination or Final Hold options, the drop section of the plan will stop at the selected target at an inclination of 0° (if this is possible). This will be referenced in the Method Column of the plan as SWELL_OPT1.
Final Inclination Only: When the user enters only the final inclination, the drop section of the plan will stop at the selected target at the desired inclination (if this is possible). This will be referenced in the Method Column of the plan as SWELL_OPT2.
Final Hold Only: When the user enters only the final Hold, the plan will hit the target at 0° inclination (if possible) and will have lined up at the given hold distance entered prior to hitting the target. In the below example, the plan has lined up at 0° inclination 100m MD before hitting the target. This will be referenced in the Method Column of the plan as SWELL_OPT3.
Final Inclination & Hold: When the user enters both values, the plan will hit the target at the desired inclination (if possible) and will also include a hold section prior to hitting the target. In the below example, the plan has lined up at 5° inclination 100m MD before hitting the target. This will be referenced in the Method Column of the plan as SWELL_OPT4.
To use this method, the KOP must be entered (the inclination will be vertical to this point) and the DLS of the build (BUR 1). The final details required are the target NS, EW and TVD. These can be entered manually or by selecting a target from the drop-down menu. If the target cannot be reached with the specified parameters, an error message will be displayed.
You can navigate to the file location of your database by opening in the Open Database Location icon in the bottom of the screen.
Click on the Units icon located in the bar at the bottom left of the screen or type ‘unit’ in the Search bar at the top right of the screen:
A selection of quick start guides for Well Seeker Pro
Well Seeker X includes an integrated feature that allows the user to download corrected surveys from four survey correction providers – Superior QC, H&P Survey Management, RoundLAB and HLB Max Survey. This document is a guide to setting up and using the integration.
Open the survey that you want to sync with the survey correction service. When the corrected surveys are downloaded they will overwrite what is currently in the survey sheet, so if you have multiple tabs open, make sure you are viewing the correct one.
Select Integrations in the ribbon menu and select MSA in the Survey Correction section.
This will open the Survey Correction Provider Settings window.
Note that MSA option will be greyed out if a survey is not open.
Select your survey correction provider from the dropdown box in the Provider field, then enter the username and password provided by the survey correction provider into the Username and Password fields.
In the Select column click on the checkbox that corresponds to the desired well and then click on Update. The Sel Well Name and Sel Operator fields in the Survey Correction Provider Settings window will update.
Note: This will overwrite any existing data in the sheet.
Note: If the tie-on line for the survey is deeper than the surveys available, selecting yes will not do anything i.e. no surveys will be pulled into Well Seeker.
You can also set Well Seeker to automatically check for and sync new surveys. Change the Auto Update field from ‘NO’ to ‘YES’ and set the update rate in minutes in the Update Rate field. In order for the automatic sync to work, the survey sheet must remain open, but the Survey Correction Provider Settings window can be closed.
Some features of the Survey Correction Integration are only available when Superior QC is selected as the provider. These features are optional and are not required to perform the basic survey retrieval function.
To enter the API number in Well Seeker, select the relevant actual well in the object explorer and select Home >> Job Data.
In the Job Data window, fill in the API# field. Make sure this matches exactly with the API number entered in Superior QC. Click on Apply. Note, that if the API number is entered but does not match, then the user will still have the option to manually select the desired well.
In Well Seeker the Latitude and Longitude co-ordinates of the well are set in Well Properties dialog for the well. Grid Convergence is automatically calculated using the well location and the mapping grid selected in the Field Properties Dialog.
Total Field, Dip and Declination are set in the Actual Well Properties dialog. These dialogs can all be accessed by right clicking on the object explorer at the relevant level and selecting Properties.
While a well is being drilled, it is often necessary to project ahead of the most recent survey for the purposes of anti-collision, or to see what is required to get back on plan. The following document is a guide to the Project Ahead and Multi Nudge tools within Well Seeker X.
The Project Ahead tool can be found on the ribbon menu Home>Project Ahead Bit Projection at the top of the screen.
Or searching for the name in the top right corner:
It is important to note that this option is only available when the user is in a Survey. If the user is in a Plan, or the Actual Wellbore, this option will be greyed out and they will be unable to select it.
When in a survey, select the Project Ahead option. This will open the Project Ahead Box.
Note, that Line 1 at the top of the box will be populated with the last survey point. The projection will be made from this point.
The user can now select from the same Planning Tools which are available when creating a well plan, with the exception of the S-Well and Slant-Well tools, as these can only be plotted from surface.
Once the relevant planning tool has been selected and the values entered, the projection is calculated by selecting Calculate.
The projection can then be added to the survey by selecting Append and removed from the survey by selecting Remove.
Two of the more relevant projection options are discussed below.
The Trend Over tool is only available in the Project Ahead dialog and is not displayed in the planning tools when in a well plan. This function allows the user to apply the build and turn trends seen in the previous surveys to the projection.
To select the Trend Over function, the user must select Adjust and then either MD or CL. This function will remain greyed out until these options have been selected.
Select the Measured Depth (MD) or Course Length (CL) of the projection and the number of surveys to model the trend over, then hit the calculate button. The projection will appear in line 2, directly below the last survey in the Project Ahead box.
The tool works by averaging out the Build and Turn rates based on the number of surveys selected.
In the below example, 1 survey has been selected, so the projection just uses the build and turn rate calculated for the last survey.
In the below example, 3 surveys have been selected, so the projection calculates the average build and turn rate values over the last 3 surveys.
Average Build Rate= = 0.08°/100USft Average Turn Rate= = -0.71°/100USft
Using the Optimum Align function, it is possible for the user to project back onto a plan.
Select Optimum Align
In the target details section, select Plan - all the plans below the Well will be available to select from the drop-down menu – Select the relevant plan
In the By MD box, input the Measured Depth on the plan that you want to line up on. On entering the depth, the NS, EW, TVD, Inc and Azi will be automatically populated with the values that correspond to this depth
Select the relevant Optimum Align Parameters
Hit Calculate
NOTE, that once the projection has been calculated, the measured depth in almost all cases will not match the depth entered in the By MD box.
The Multi Nudge Projection tool allows the user to quickly project ahead using additional features which are not available in the standard Project Ahead section of Well Seeker. More importantly, it allows an unlimited number of projection lines to be included.
As with the Project Ahead tool, it is important to note that the Multi Nudge Projection tool is only available when the user is in a Survey. If the user is in a Plan, or the Actual Wellbore, this option will be greyed out and they will be unable to select it.
When in a survey, this tool can be selected from the ribbon menu Home > Multi Nudge Bit Projection or by searching in the top right of the screen.
When the tool first opens, the Tie-On line will be populated with the last survey in the listing. At this point the user can then select from 1 of 6 projection Methods.
The Multi Nudge Projection box can be left open while the user is adding new surveys, and the tie-on line can be updated by selecting the Update Tie On button. Note, that the surveys do not need to be saved for this to happen.
If the box is closed and then reopened, it will automatically tie onto the last survey point. The projection setup will remain populated with whatever setup the user had selected previously, even when the program has been closed and reopened. To remove the input projections, the user can delete the lines one at a time or select Reset to remove all projections.
Projections can be added to the survey by selecting Append to Survey and can be removed by selecting Remove from Survey. The Multi Nudge Projection window can remain open while using other Well Seeker functions, but all projections must be removed from the survey before new survey stations can be entered.
If the user has a slide sheet currently open, Get from Slide Sheet will pull the slide sheet entries in as projections.
Note: If the user has not input the motor yield for their slides in the slide sheet, the motor yield and the DLS will default to 15 in the Multi Nudge Projection.
The five projection methods are described below.
This option allows the user to select Course Length (CL), Dogleg (DLS) and Toolface Orientation (TFO) to calculate the projection. This method assumes a 100% slide. Motor Yield will be automatically populated with the same value input in the DLS column.
This option allows the user to select Course Length (CL), Slide Percentage (%) and Toolface Orientation (TFO) to calculate the projection. The user is also required to add the Motor Yield, as the projected dogleg is calculated based on the slide (%) and the Motor Yield.
In the example above, the slide (%) is 50% and the motor yield is 5°/30m, which results in a 2.5°/30m DLS.
This option allows the user to select Course Length (CL), Slide Distance (Dist) and Toolface Orientation (TFO) to calculate the projection. The user is also required to add the Motor Yield, as the projected dogleg is calculated based on the slide (Dist) and the Motor Yield.
In the above example, the Slide Distance is 4m (Course Length is 10m) and the motor yield is 5°/30m, which results in a 2.0°/30m DLS.
This option allows the user to select Inclination (Inc), Azimuth (Azi) and Dogleg (DLS) to calculate the projection. This method assumes a 100% slide. Motor Yield will be automatically populated with the same value input in the DLS column.
This option allows the user to select Course Length (CL). The inclination and azimuth from the tie-on line will be held for the selected distance.
This option allows the user to select Measured Depth (MD). The inclination and azimuth from the tie-on line will be held for the selected depth.
The user can set up the Multi Nudge Projection with as many lines as required.
This section of the Multi Nudge Projection allows the user to project to a landing point and is most useful when landing out a horizontal lateral and functions in a similar way to the Dogleg Toolface - Point planning method.
Note that this section will only work if a principal plan for the well has been assigned. To set a plan as a principal plan, right-click on the plan in the database tree and select Properties. In the Properties window check the Set as principal plan checkbox next to the well name.
The Bit row displays the deepest survey station in the currently opened survey sheet. As this is the most recent survey, to accurately use this projection tool, the user should make a projection to the bit to get the true bit position. To do this the user should make a projection in the top window and append it to the to the survey, as displayed in the image below. The Bit row will update automatically when the projection is added. If for any reason this does not happen, the Update Bit Position button can be used to force an update.
When a MD is entered in the Target row, Well Seeker looks for this MD on the Principal Plan and then populates the rest of the cells in the row with the values from the plan. The Landing Data tool then automatically calculates the constant Tool Face and DLS required to reach that point on the principal plan from the bit position shown in the Bit row.
In the below example, the MD of the curve landing point (15984.76 USft MD) has been entered and the TVD, NS and EW coordinates in the projection match the plan at this depth. The Tool Face and DLS columns show the Tool Face and DLS required to reach this landing point from the current bit position. Note that the plan is open here for demonstration purposes. It does not need to be open for the Landing Data window to work.
The Select Critical Point drop down box can be used to quickly select plan points from the principal plan as the landing target. If the principal plan is changed while the Multi Nudge Projection is opened, the list of plan points can be updated using the Update button.
The user can also enter a target using the Find Landing button. This button will automatically pick the plan point from the principal plan that has the highest inclination. If multiple plan points share the highest inclination, the Find Landing button will pick the shallowest.
The Append to Survey button will add the Target row to the survey list as a projection, while the Remove from survey will delete it. Projections from both the Multi-Nudge section and the Landing Data section can be present on the survey list at the same time.
The landing data calculation should automatically update whenever new input data is added; however, if for any reason this does not happen, it can be updated manually using the Calculate button.
Selecting the Adjust TVD checkbox allows the user to change the TVD of the point selected in the above. The MD stays unchanged as this is what the program is using to determine the local coordinates of the landing point.
Note in the below example how the NS and EW local coordinates are still the same as the landing point line, but because the TVD has been shifted deeper the DLS, Tool Face and Inc have changed. The program is still aiming for a specific point here, only with an adjusted TVD.
This option is only available when Adjust TVD is selected.
This allows the user to enter an Inc, Azi and TVD to project to. The main difference with this selection compared to the previous options is that the user is not projecting to a specific point i.e. the local coordinates are not fixed.
In the example below, the Inc, Azi and TVD are entered for the planned curve landing point. Note that the MD, NS and EW landing points are no longer the same as the landing point in the plan. This setup simply tells the user what dogleg is required to land out at horizontal for a given TVD. When new surveys are added, the bit line updates automatically and so does the landing point line.
NOTE: When you first open this dialogue, there is no requirement to enter a MD. It is possible to just select Adjust TVD and Adjust Inc / Azi and input the values. There is no need to add a MD unless you specifically want to hit an exact point.
The TVD Projection feature can be activated by clicking on the check box in the top right of the Landing Data window. This feature displays two new Target rows that are offset by a user specified TVD from the main Target row.
In the example below, TVD Projection 1 has been set as -10, so its target is the same as the Target row but 10 USft TVD shallower. TVD Projection 2 has been set as 10, so its target is 10 USft TVD deeper.
The TVD projection feature can be used in tandem with the Adjust TVD and the Adjust Inc/Azi functions. TVD projections are for reference only and cannot be appended to the survey list.
After selecting any Critical Point in the dropdown or hitting the calculate button in the Landing data section, a DLS to Land chart is displayed with a visual representation of the Dogleg Severity to Land. This chart will be presented by default in the units previously selected.
A right-click in the chart area will display a context menu with options to edit the chart visualization,. These changes will return to default mode once the Multi Nudge Projection is closed and opened again.
Introduction
Innova regularly releases updates for the Well Seeker X software. These new releases may include new feature updates or they may address bugs which have been discovered.
Innova have three different methods of distributing updates to end users:
Via the inbuilt auto-update feature in Well Seeker X.
Distributing an updated Well Seeker.exe executable for users to implement manually.
Distributing an updated installer file.
This document provides a guide for adding updates using these three methods. If, after following the instructions below, you still require assistance with an update, you can contact Innova Support at support@innova-drilling.com.
Note that using this method to install an update will cause Well Seeker to close and restart. If the user is updating in the field, it is recommended to delay updating until there is a convenient break in operations.
If Innova has made an update available for your organization, the next time you open Well Seeker X you should receive the below notification in the bottom right corner of the window:
Click on OK to close the notification, or click on Install to install the update. Well Seeker will download the update, then close and restart to implement it.
The update will also appear in the Notifications pane. This can be opened by clicking on the bell icon in the very bottom right corner of the Well Seeker X window.
If you missed the notification or chose not to install the update immediately, you can check for an update and download it at any time by following the below steps:
Backup your database by going to the Home ribbon and selecting Backup. Save your backup in a secure location.
Go to the Help ribbon and click on Check in the Software Update section.
If your version of Well Seeker is up to date, you will receive the following message:
If an update is available, you will be given the option to download and install it. If you select Yes, Well Seeker will download the update, then close and restart to implement it.
After using the Check option, you can also download and/or install the update via the Info button.
In the dialog that opens, you have three options:
a. Click on OK to close the dialog without downloading the update.
b. Click on Download to download the update to your PC. This allows you to manually apply the update at a later date. To do so, follow the instructions in the next chapter, Manually Applying an Updated Well Seeker.exe.
c. Click on Download/Install. Well Seeker will download the update, then close and restart to implement it.
Wait for Well Seeker to restart, then return to the Help ribbon and click on the Info button again. The dialog should display your new version number.
The auto-update feature described in the previous chapter downloads and applies an updated Well Seeker.exe executable file to the user’s PC. However, there are circumstances when this is not feasible. For example, you may wish to test an update before allowing Innova to distribute it to all users in your organization.
In these circumstances, Innova can send an updated Well Seeker.exe file directly, which you can then apply manually. To so, follow the below steps:
Double check whether you are using the 64-bit or 32-bit version of Well Seeker X. You can do this by going to the Help ribbon and clicking on Info.
Backup your database by clicking the Backup button in the Home ribbon. Save your backup in a secure location. Then close Well Seeker.
Receive the updated Well Seeker.exe file from Innova. This will usually be provided as a zipped folder via email. Check that the version number in the name of the zip file matches the version you have installed. This is what you checked in Step 1. If the update is for a 64-bit version, the file name will contain x64. If it is for a 32-bit, the file name will contain x86.
Unzip Well Seeker.exe from the zip file that you downloaded in the step above.
Copy and paste the unzipped Well Seeker.exe into your Well Seeker install directory, replacing the file that is already there. The default install directory address will depend on the version you are using:
For the 64-bit version: C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x64)
For the 32-bit version: C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x86)
Re-open Well Seeker X, go back to the Help ribbon and click Info. This should display the new version number.
Occasionally, Innova may release a significant feature update for Well Seeker X, that requires the software to be uninstalled and then reinstalled with the new version. This section will guide the user through the steps required to do this..
If you are using Well Seeker in the field, it is recommended that you wait until there is a convenient break in drilling operations before attempting to uninstall/reinstall Well Seeker.
Double check whether you are using the 64-bit or 32-bit version of Well Seeker X. You can do this by going to the Help ribbon and clicking on Info.
Backup your database by clicking the Backup button in the Home ribbon. Save your backup in a secure location. Then close Well Seeker.
Open the control panel and then open Programs and Features.
Uninstall Well Seeker X.
Download the zipped installer file. There are two ways to receive this file:
We will send it to you directly, usually via email.
Unzip the installer file from the zipped folder.
Re-open Well Seeker X, go back to the Help ribbon and click Info. The version number should display the new version.
When Well Seeker X is installed for the first time, part of the install is a database which can be found in the following location.
When the program is opened for the first time, this is the database which Well Seeker will access. The database being accessed is referenced in the bottom left corner of the Well Seeker screen.
Well seeker database files have a .mdb file extension, and the user can easily create and switch between databases using the Home > New and Home > Select in the Database ribbon menu.
It is very important that the user regularly backs up their databases to ensure they always have a copy in case something happens to their computer or in case there is some other issue.
The current database is defined as the database which is currently being accessed when you open Well Seeker X. This database is backed up as follows:
Open Well Seeker
Select Home > Backup
Choose an appropriate location to save the database and select an appropriate name. For example, Master Db.mdb or Master Db (Date).mdb etc.
Note: When backing up a database, it is recommended that you do NOT overwrite an existing backup, but instead create a completely new backup. That way if anything goes wrong with the process you will not lose he original backup.
It is not uncommon for a user to have multiple databases which they frequently switch between. It is very easy to back up a database without even opening Well Seeker, even if it is the current database. As an alternative method to the one described in section 2.1, any database can be backed up as follows:
Locate the database to be backed up. This will be a .mdb file.
Copy the .mdb database file and save it in the required backup location.
At this point the user can rename the database if necessary (but this is not required). For example, Well_Seeker_DB.mdb could be renamed Well_Seeker_DB (Date).mdb, or it could be completely renamed. This is just for reference and has no effect on the database itself.
When necessary a backup database can be accessed when in Well Seeker by selecting Home > Select in the Database ribbon menu.
The user should then navigate to and select the relevant back up.
The backup location should NOT be in the Programs (x86) folder. Rather it should be in a documents folder on the computer C drive, or ideally somewhere that is backed up regularly i.e. a shared drive etc. The user’s desktop should also be avoided as files on the desktop are easy to delete by mistake.
When a new version of the software becomes available, the user needs to remove the existing version (via the add/remove programs feature in Windows) before they can install the new version. This uninstall process removes all the files which initially came with the install. This INCLUDES the original Well_Seeker_DB.mdb database. Although Innova recommends that users create their own database when they first start using the software some users prefer to work in the default. In this situation it is ESSENTIAL that the user backs this database up before they uninstall the software as this database will be DELETED during the uninstall process.
Well seeker database files have a .mdb file extension. When a database is being accessed by Well Seeker an additional .ldb file is temporarily created. This is a very small file which, disappears when the database is not being accessed i.e. Well Seeker is using a different database, or when Well Seeker is closed.
When backing up the current database following Section 2.2 instructions, the user should be careful not to copy the .ldb file instead of the .mdb as this does not contain any data. To avoid making this mistake, it is safer to ensure that the .ldb file is not present, and Well Seeker being closed ensures this.
Historically, users could access Well Seeker without logging in, except when using a server database. The Innova Web Portal now includes options that allow organizations to enable local database user access for their version of Well Seeker X. When the Local Login feature is enabled, all users must provide valid credentials to access the software and its full suite of internet-dependent tools and features. Without login credentials, users will be unable to access any part of the software.
In addition to safeguarding access to Well Seeker X behind a login, the organization can also enable/disable:
Server database access
Real time data exchange dialog access
Remote data fetch dialog access
Data sync pull feature
Data sync push feature
When using the local login feature, Well Seeker X will also honor the well / operator access assigned to the user and role. Most notably this impacts the remote data fetch dialog, where the local user will now be limited to what wells they can access based on their permissions setup.
The below guide details the setup of this feature within the Innova Web Portal and highlights the impact this has on the Well Seeker X users within the organization.
In order to setup and maintain the Local Login feature for an organization, a user with Admin permissions and access to the User Management feature is required.
Once the Local Login feature is enabled, all users in the organization will be required to enter valid login credentials the next time they open Well Seeker X. Therefore, it is advised to setup all user credentials in the User Management system and issue these credentials to the users, prior to enabling the Local Login feature.
The following Well Seeker only features can now be assigned to a role. These features will only take effect if the Local Login feature is turned on:
Disable Data Exchange: Selecting this option will prevent a Well Seeker X user being able to open the Real Time Data Exchange dialog. When attempting to open the dialog the user will receive the below warning.
Disable Data Fetch: Selecting this option will prevent a Well Seeker X user being able to open the Remote Data Fetch dialog. When attempting to open the dialog the user will receive the below warning.
Disable Data Sync Pull: Selecting this option will allow the user to push data from the local database to the server database, but will prevent data automatically pulling from the server database to the local database via the data sync feature. The data sync status will appear as below when the data sync is in online mode.
Disable Data Sync Push: Selecting this option will allow data to pull from the server database to the local database, but will prevent the user automatically pushing data from the local database to the server database via the data sync feature. The data sync status will appear as below when the data sync is in online mode.
Disable Server Access: Selecting this option will prevent a Well Seeker X user from opening the Server Login dialog. When attempting to open the dialog the user will receive the below warning.
Below are two field user and one office support staff role setup suggestions; however, these are not exhaustive and organizations may adjust these as required. The two field roles allow users within an organization to either continue using the Real Time Data Exchange, or use the Data Sync method of data transmission between local and server databases. It also provides the tools for a phased transition from one data transmission method to the other, by assigning different users to different roles as required.
Field Engineer WSX Data Sync Off
Allows user access to the standard Real Time Data Exchange and Remote Data Fetch dialogs, whilst restricting access to the Server Login dialog and disabling the Data Sync push and pull features.
Field Engineer WSX Data Sync On
Allows user access to the Remote Data Fetch dialog and enabling the Data Sync push and pull features, whilst restricting access to the Real Time Data Exchange and Server Login dialogs.
Office Support Personnel WSX Data Sync Pull On Push Off
Allows user access to the Remote Data Fetch and Server Login dialogs and enables the Data Sync pull feature, whilst disabling the Data Sync push feature and restricting access to the Real Time Data Exchange dialog. This allows local database updates from the server, but with no ability to push data back to the server when QCing / troubleshooting data. If any data changes are required, the user can then log on to the server database and make them.
Existing users may have access to various features based upon their current login credentials. However, all local only database users (e.g., field personnel) still require to have a user created for them and a role assigned.
Once all users have login credentials assigned the Local Login feature can be enabled.
To enable the Local Login feature select the Main Menu > Database Admin Tools > Well Seeker Settings.
Select the check box for Local login required and select Apply.
Upon next opening Well Seeker X, all users will now be prompted for login credentials.
To turn off the Local Login feature, simply uncheck the check box for Local login required and select Apply.
If the Local Login feature has been enabled the following will be true.
Well Seeker X will open and immediately require valid login credentials
If valid login credentials are entered, the user can continue to use Well Seeker X with the feature permissions assigned to their user’s role
Once a user has been authenticated, no login dialog will be shown when logging on to the server database. However, if the Disable Server Access feature is enabled, the user will not be able to logon to the server database.
If invalid login credentials are entered, the below warning will display. When the user selects OK, Well Seeker X will close.
As has always been the case, when no internet connection is available, Well Seeker X will not require a local user login, but none of the internet dependant features will be available either e.g., remote data fetch, data sync, etc.
Innova provides an industry leading integrated drilling software solution for well planning and engineering applications.
Both programs are very quick and easy to install, and the user does not require any more than basic computer skills to achieve this.
Recommended system requirements are as follows
Intel i5 processor or equivalent.
4 GB of RAM.
500MB of hard disk space.
Microsoft Windows 64-bit (x64) version 10 or better.
Microsoft Excel 2007 or later.
Windows XP, Windows 7.0 and Mac OS are NOT supported.
Recommended screen resolution: 1920 x 1080.
Both Well Seeker Pro and Innova Engineering programs use computer specific licencing. Once the software has been installed on a computer, a code is generated which is unique to that machine. This is then used to generate a license which when added to the relevant folder, activates the license, and gives the user access to the program.
Server based, remote access and local license options are all supported.
Innova Well-Seeker Pro is a high performance well planning and survey management package designed for use by Operators, Well Engineering Companies and Directional Drilling Contractors. The software integrates high performance 2D & 3D graphics with a powerful database engine that allows the user to easily store and visualize their well trajectories as well as perform complex well planning and anti-collision calculations. Innova Well Seeker Pro offers exceptional performance with all the features expected of an industry leading well planning package, including Integrated Reporting, AFE Design, Asset Management, Well Analytics and RT anti-collision features.
Full range of easy to use 2D & 3D well planning methods including:
Dogleg Tool Face
Build and Turn
Optimum Align using Curve-Hold-Curve or Curve-Curve
Line up on Target at specified inc / azi,
One click S-Well and Slant Well construction
Supports multiple target geometries including:
Simple 2D circular and Elliptical
Point & Rectangular
Complex 3D multi point Polygonal
Lease Lines and Hard Lines
Create Drillers Targets based on error models, well trajectory & required confidence
Supports advanced well planning for all applications, from simple vertical exploration wells to complex multi-laterals
Perform anti-collision scans using industry leading proximity detection algorithms
Calculate ellipse of uncertainty (EOU) using full range of ISCWSA MWD and Gyro error models
Error outputs and Centre to Centre distances validated against ISCWSA standard well paths to < 0.1% error
Anti-collision scans can be run interactively during planning and drilling phases on multiple actual wells / plans
User defined warning criteria and alerts can be set to notify of potential collision risk
Casing and hole diameters can be included in separation factor calculation in order increase accuracy. Especially important for top hole drilling with large diameter surface casing.
Ability to create custom Instrument Performance Models (IPM)
Error output sigma level can be selected by the user
Real Time AC feature allows monitoring of multiple offset wells and distance to lease lines
Anti-collision tools such as travelling cylinder view and ladder plot update in real time as additional surveys are entered
Advanced anti-collision visualisation tools available including Ladder Plot, Separation Factor Plot and Travelling Cylinder Plot
Built on a powerful database engine which allows storage and navigation for an unlimited number of actual wells and plans
Easy navigation of database through familiar tree view
Import and export of data allows easy transfer of wells and plans from office locations to the field
Both local and SQL Server databases available
Local databases can be easily set up to provide real time data exchange with the master SQL Server database, allowing surveys, daily reports, BHA’s etc to be updated on the master database in real time from the field.
Local databases can perform a remote data fetch allowing them to pull plans and offset data directly from the master SQL Server database. This permits the field engineers to quickly build a database with all the relevant data.
Fully customisable, advanced and powerful 3D plotting capability
Plan View (Top Down) Plot
Section View (Side On) Plot
3D Plot
Fly down well 3D chart feature
Visualise closest approach to all offset wells and principal plan
Spider Plot with interactive TVD slice control
Azimuth Comparison Plot (Azimuth vs MD)
Inclination Comparison Plot (Inclination vs MD)
Dogleg Comparison Plot (Dogleg vs MD)
Live View Plot
Print directly to multiple image formats including PDF / jpg / bmp / png.
Copy directly to clipboard allowing images to be quickly added to Word, Excel & PowerPoint documents
Wall Plot Composer (WPC) allows the user to create customisable wall plots which can include data tables.
Pre-defined plot sizes range from A0 to A7 with a user defined option also available.
Visualise formation top and target depths
Customisable outputs in both 2D and 3D charts
Update and model geological target corridor based on RT updates
Provides clear visual updates to DD of drilling corridor
Quickly create offset plans based on real time geosteering updates
Includes World Magnetic Model (WMM) and International Geomagnetic Reference Field (IGRF) model as standard
Supports British Geological Survey Global Geomagnetic Model (BGGM)*
*available only to full BGGM license holders
Supports NOAA High Definition Geomagnetic Model (HDGM)**
**available only to full HDGM license holders
Supports MagVAR High Definition Geomagnetic Model (mvHD)***
***available only to full mvHD license holders
Integration with BBGM Hypercube IFR
Integration with BGGM Error Estimates
User defined reports include:
Standard Survey reports
Geographic Survey reports
Anti-Collision reports
Ellipse of uncertainty (EOU) reports
Exports to fully customisable PDF and Excel reports
Wall Plot Composer
Includes the ability to import Compass Export files, including batch import, where multiple export files can be pulled in simultaneously.
Quickly populate customer and Supplier addresses and details from dropdown lists
Print quotation including a cover letter and any relevant notes
Cost Codes included in the bids can be quickly and easily copied to well level where they can then be selected in the Daily Reporting feature
Bids are approved by users with the relevant user permissions
Bids can be Archived by users with the relevant user permissions
Integrated within Innova’s Well Seeker Pro are advanced custom reporting features including:
Daily Reports
Slide Sheets
Ability to populate Daily Reports directly from the slide sheet
Ability to auto populate slide sheets via received WITS data
Daily Cost Reports
Well Cost Reports
Cost Tracking
Tool Inventory
Tool Utilisation Reports
Personnel Utilisation Reports
Tool and Personnel Tracking
Shipping Tickets
Pipe Tally
BHA Reports
Motor and MWD Performance Reports
Motor and MWD Failure Reports
End of Well Reports
Company Man Report
KPI Tracking
Well statistics provides a detailed overview of the well data including well phases and BHA’s
Click of a button morning report package, directly opens outlook email complete with excel morning report and copy of current database as attachments and email body populated with a synopsis of daily operations
Generate and output detailed reports at the click of a button
Excel and PDF output
Easily create and output custom reports and charts
Powerful search tool to find and compare wells across the entire database. Multiple search criteria options available including Date Range, Radius from a given well, Formation, Assembly type, Failures, State, Directional Company, Hole Size, Rig and LIH etc
Plot all selected wells together on google maps. Surface locations, Plans, Surveys and Lease Lines can all be displayed.
Motor, MWD and Section KPI Reports
Revenue Report
Rig Days Report
Personnel Utilisation Report
Well Ranking Report
Compare KPI metrics between multiple wells and well phases:
Slide & Rotation Footage
Depth Vs Time
Failure Analysis
Directional Cost per Foot
Well Cost per Foot
BHA Details
Detailed Cost Breakdown
Wells by Formation, Directional Company, Motor Make, Bit Make
ROP & Footage by Formation, Directional Company, Motor Make, Bit Make, Hole Size
Activity & Phase Comparison
Wells by Rig
ROP & Footage by Rig
Parameter Comparison
Well / Section Performance
Average Interval Cost per Quarter
Driller Performance
Footage Per Day by Operator and Rig
BHA Reason Pulled Summary
The Authorization for Expenditure (AFE) Designer is a powerful well plan costing tool which includes the following features:
Build detailed AFE for any well plan from mobilisation to demobilisation.
Probabilistic & Deterministic approach
Calculate costs for P10, P50, P90 scenarios.
Standardised cost codes.
Factor in associated risks and assign probabilities.
Export KPI charts:
Time Probability Density Function
Cost Probability Density Function
Time Cumulative Density Function
Cost Cumulative Density Function
Depth vs Time
Cost vs Time
Time Interval
Time Cumulative
Cost Interval
Cost Cumulative
Generate full reports with detailed timeline and cost breakdown:
Event Model
Detailed Event Breakdown with costs
Cost Model
Time vs Depth
Time vs Cost
Time Histogram
Cost Histogram
Full report containing all the above reports and all KPI charts.
Supports WITS, WITSML and Wireless WITS connectivity
WITS data can be pushed back from the field to the remote server database, where it can be viewed by anyone with the relevant login credentials
Slide sheets can be automatically populated based on the data received via the WITS feed.
Remote data fetch allows the user to pull wells into a local database, directly from an SQL server database
Real Time Data Exchange allows field data to be updated on the SQL server database in real time.
DD Dashboard, which provides an interface containing tools a directional driller can utilize while drilling a well either locally on the rig or remotely from an RTOC. It updates automatically while using the WITS feed and contains the following:
Rig Gauges
A Tool Face Rose which displays Toolface, Effective Toolface, Bit Projection and various other information based on the selected mode
Real Time Anti-collision for bit projection
Last 4 surveys along with the Slide Seen and Motor Yield for each one
Projections including projection to bit and advisory projection
Real time 3D plot
Drilling parameters charts populated from the WITS data feed
Choose between 4 modes: Vertical, Nudge, Curve & Lateral which provide the user with slide and rotary recommendations based on the data entered in the settings menu.
Slide Analysis
Connection Analysis
Activity Dashboard
Shows a summary with up to date data for all selected wells including, depth vs time chart, revenue tracking, inventory etc
Print job board report which includes Active Wells, Upcoming and Standby Wells, daily and monthly revenue and summary of wells by operator, state, and coordinator
Logistics Dashboard
Provides an overview of all tools in the local inventories within the database giving full oversight of all equipment
View all tools in all locations via google maps
Various filter options to quickly find the relevant items
Rigs Online Dashboard
Shows a list of all current jobs where data is being sent from the field to the server database and displays the time since last update
AC Dashboard
Displays a summary of all open RTAC dialogs
At the click of a button the user can open the surveys and RTAC dialogs for all active wells in the database
Tool Orders Dashboard
Create, update and maintain oversight of all the tool requirements for upcoming and existing jobs
Managed directly from the SQL server database
Rig site local database users can create tool orders and push these back to the server for approval
Incident Dashboard
Shows a summary of all recent BHA failures
Allows user to quickly access BHA and well data for selected incidents
Merge Solutions: Cost and asset tracking via integration with Merge’s OASIS software
ZerdaLab: AI-powered automated bit dull grading, integrated into the Innova Web Portal and App
Superior QC: Survey correction integration. Pull corrected surveys directly from the Superior QC server into Well Seeker
RoundLab: Survey correction integration. Pull corrected surveys directly from the RoundLab server into Well Seeker
MagVar: Survey correction integration. Pull corrected surveys directly from the MagVar server into Well Seeker
NOV: RSS Downlink integration, where downlink commands can be sent directly from Well Seeker to NOV, on compatible NOV rigs
ROGII: Geosteering integration
British Geological Survey: Integration with BGGM Hypercube IFR and BGGM Error Estimates
Can be viewed on any internet enabled device with no additional software required
Login to the web portal from anywhere in the world via an internet browser
Filter and view all well data contained in the SQL database
Customizable drilling dashboard and well details
Full oversight of all equipment location and condition via the Logistics Dashboard
View well analytics and KPIs for all wells on the SQL server database
Monitor drilling in real time and view EDR logs
Remotely monitor multiple wells on a single screen
Perform database admin and maintenance
Manage (add / edit / delete) all levels of the database tree
View and edit reporting data
Integrated hydraulics and T&D with engineering dashboard
Access and manage Tool Orders
Manage user access and permissions to SQL server database
Available on Apple IOS and Android
View live well updates and drilling data directly on your smart phone or tablet
Real time remote performance optimization
Edit all reporting data directly from your phone or tablet
View well analytics and KPIs for all wells on the SQL server database
EDR logs display WITS data
Full oversight of all equipment location and condition via the Logistics section
Access and manage Tool Orders
Manage (add / edit / delete) all levels of the database tree
Perform database admin and maintenance
Built in chat feature
Provide clients access to view activity updates
Roles section allows admins to provide user permissions and access as required
Server based licensing
Supports data import / export from 3rd party software platforms
Ability to import COMPASS XML export files at the click of a button
Directional Difficulty Index (DDI) calculator
Automatic updates
One-click license request and download
Copy & Paste - Very quick and easy to add large surveys to the software - copy and paste directly from excel or txt files
Export files can be generated quickly at any level on the database tree
Quick and easy to create and switch between new databases
Well-Seeker Pro is a full featured well planning package providing an all in one solution that significantly raises the standard for well planning software.
When combined with the Innova Engineering package, Well-Seeker Pro provides both operators and service providers with a complete software solution for advanced well planning and engineering.
The Innova Portal and smartphone App allows users to access their data and monitor activities in real time from any device.
Innova Engineering is an advanced well engineering software solution combining the power of multiple packages into one application. Incorporating Hydraulics, Torque and Drag, SAG Correction, BHA Analysis, BHA magnetic Interference Calculator, Survey Correction & QC, Casing Standoff and Centralizer Placement, Cementing Design and Jar Placement modules, Innova Engineering provides a comprehensive engineering package to plan and drill your well successfully.
Innova Engineering was developed by engineers for engineers to provide the premier engineering software package for the oil and gas industry. With exceptional functionality and an intuitive yet powerful interface, Innova Engineering delivers an innovative and integrated solution for Operators and Service Providers alike.
Simple to use interface
Extremely fast calculations. Results for complex BHAs at multiple flow rates / friction factors are calculated in seconds
Copy and paste data from Well Seeker, Excel, Notepad or any other file type directly into Innova Engineering
Easy to interpret graphical and numeric outputs available for all calculation modules
Create professional, user customized reports in both PDF and Excel formats for all outputs
Detailed Summary Reports for each module
Fully customisable charts complete with screen reader to allow quick interpretation of generated data
Overlay data collected from the wellsite against the modelled outputs for quick and easy comparison
Supports modelling of complex drilling assemblies with multiple hole opener / under reamer combinations as well as casing / liner runs
Complete support for complex 3D directional wells
Import / Export BHA assemblies
Editable Fluids Library & Components Catalogue
Latest soft string model with stiffness correction factor
Model Viscous Drag, additional side force due to buckling & Contact Surface Correction
Conservative (Unloading) & Standard (Loading) Helical Buckling Models
Calculate T&D for multiple rig operations simultaneously Tripping In / Out, Rotating On / Off Bottom, Sliding and Reaming
Ability to model for both pumps on and pumps off and account for string differential pressure
Calculate Sinusoidal and Helical buckling limits
Full support for casing, liner, tubing & drilling assemblies
Full support for complex 3D directional wells
Friction factor sensitivity analysis for unlimited number of friction factors, or single calculation
Models casing flotation / drill string fill
Friction reduction devices (Non-rotating drill pipe protectors) can be modelled
Calculates expected pipe stretch and torque induced pipe twist
Elemental (snapshot) view available for all calculations
Calculate side forces & casing wear for all operations
Drill string fatigue prediction
Real time data can be modelled & displayed alongside the calculated data in order to back calculate real time friction factor
Actual and apparent WOB and overpull calculations, visualize how much overpull / WOB is experienced at the bit for a given value seen at surface. Useful for determine trip / overpull margins and for setting packers & liner hangers
Casing Standoff & Centralizer Spacing Calculation. Use to optimise standoff and achieve proper zonal isolation
Ability to model expandable liners including max pull, pull at cone, expected expansion hookload as well as outer & inner string running loads
Ability to model different materials such as Aluminium, Titanium as well as steel
Model the effect of casing centralisers / stabilisers
Ability to model Air Drilling
Option to select the fluid level in the wellbore.
Support for multiple hydraulic models:
Bingham Plastic
Power Law
Herschel Bulkley
Robertson Stiff
Calculated Outputs:
Standpipe Pressures
ECD: cuttings loaded and clean hole
Surge and Swab
Complete set of hole cleaning outputs:
Annular Velocity Profile
Cuttings Carrying Index (CCI)
Cuttings %
Minimum Flowrate required for good hole cleaning (sensitivity analysis for ROP)
Options for single calculation or sensitivity analysis for unlimited number of flowrates and tripping speeds simultaneously
Full support for riser-less / dual gradient drilling
Split flow modelling for complex BHAs with multiple hole openers / under reamers / circulating subs
Incorporate data gathered at the well site into the hydraulics model and overlay the real-world data and the theoretical hydraulics model
Enter multiple pore pressures & fracture gradients and plot against modelled data
Surge and swab calculations can be calculated for any reference:
Bit
Casing Shoe
Bottom Hole
Any User Defined depth
Surge and swab model can also include the effects of pipe acceleration, gel strength, coil tubing operations such as continuous tripping and continuous circulation
Model the effect of stabilisers and casing centralisers
Quick bit hydraulics calculator, determine bit pressure losses and impact force without having to setup a complete project
Pump Pressure Safety Factor: Option to allow the user to increase the SPP by a specified percentage.
Ability to model air drilling
Ability to apply a back pressure for MPD operations
Ability to include additional riser boost flow rate
Correct raw MWD surveys for Z axis magnetic interference with latest short collar correction (SCC) algorithm
QC raw MWD surveys for G total, B total and SCC with user definable limits
Well path magnetic interference analysis, calculate the expected error in azimuth for a given amount of non mag spacing. Fully supports intermediate steel above and below the MWD sensor or both
Multi Station Analysis (MSA) can be used to calculate an optimal bias and scale factor for XYZ magnetometers and accelerometers
No need to enter a separate BHA for magnetic interference or SAG correction. All calculations can be done from one BHA which greatly simplifies data entry.
Option to include inclination weighting on least squares fit (LSQ) calculation
Optimise the non mag spacing requirements and determine the best survey correction method for a give well trajectory / BHA.
Full support for the following Survey Calculation Methods:
Minimum Curvature
Radius of Curvature
Tangential
Balanced Tangential
Supports survey interpolation for both MD and TVD, results can be exported to text or Excel
Produce fully customisable plots for both section and plan views and overlay well plan and actual surveys on one chart
QC raw MWD surveys for G total, B total and magnetic dip with user definable limits
Survey SAG correction algorithm, to correct survey inclinations for BHA deflections
Can model bent motors and rotary steerable systems
Rotary BHA modelling to aid in build / walk rate predictions (equilibrium rate)
Predicted build / walk Rate for Sliding based on motor bend, hole size and Bit Formation Index
Predicated build / walk rates for both push and point the bit rotary steerable systems
Take into account bit aggressiveness and bit type (PDC, rollercone)
Vibration analysis calculates Critical RPM
BHA magnetic Interference Calculator Module
Well path magnetic interference analysis; calculate the expected error in azimuth for a given amount of non-mag spacing. Fully supports intermediate steel above and below the MWD sensor or both
Calculate non-magnetic spacing requirements and azimuth error for any well trajectory and BHA configuration
Model rigid and bow spring centralizers
Automatically optimize centralizer placement based on a desired standoff value
Calculate deflection at centralisers and mid joint
Ability to model bow spring running and restoring forces
Model the additional side force created by the compression of bow spring centralizers
One click standoff summary report, including tabulated results accompanied by standoff, side forces and hookload charts.
Calculates neutral point road map which shows WOB to avoid at every depth along the well path
Calculates pump open force
Model the impact / impulse of all types of jars, accelerators & intensifiers
Optimize the hammer length / jar type to maximize impulse / impact
Calculates weight above and below jar when vertical in air and mud
Calculates weight above and below jar at bottom hole location in air and mud
Cementing Schematic Animation gives a visual representation of the well geometry, string, and fluids at any given stage in the cement job
Calculate annular pressure, equivalent circulating density and pump pressure during cementing operations
User definable Pumping Schedule
Ability to model calculations with inner string
Select from Bingham, Power Law, Herschel Bulkley or Robertson Stiff Hydraulics Models
Calculate capacities and displacements
Calculate Top Down, Bottoms up and Full Circulation times.
Determine kick tolerance and perform sensitivity analysis to show how the kick tolerance changes throughout the section and the effect of mud weight changes
Calculate MASP, MAASP to determine surface pressure control equipment requirements
Quickly determine required kill mud weight and pumping schedule to kill the well
A guide to creating a sidetrack in Well Seeker Pro.
The purpose of this document is to help guide the user through the steps required to create a sidetrack.
Depending on the requirements, it is possible to create 3 different types of sidetrack within Well Seeker:
A plan which sidetracks another plan
A plan which sidetracks a survey
A survey which sidetracks another survey
NOTE: It is not possible to create a survey which sidetracks a plan.
The steps required to create the sidetrack are the same, regardless of which of the above 3 options are required.
This document will detail the steps required to create a sidetrack under 2 different conditions:
When the sidetrack and the motherbore both have the same depth reference
When the sidetrack and the motherbore have different depth references
In order to create a sidetrack, the user must first enter a well which will act as the motherbore. The motherbore can be either a plan or a survey. For the purposes of this guide, it will be assumed that the motherbore has already been created in Well Seeker.
Any well plan or survey which is entered in Well Seeker requires a depth reference to be assigned to it. In most cases this will consist of:
A Ground Level Elevation above a System - Usually MSL
A Datum above a System – Usually RTE or RKB above Mean Sea Level
When planning a sidetrack, it is important to know what the depth reference of the motherbore is and what the depth reference of the sidetrack is. There are 2 possible situations which the user may encounter.
The first situation is where the depth reference for the motherbore and sidetrack are the same. This is usually experienced when the sidetrack is drilled with the same rig, as the variable is the RTE above ground level, since ground level elevation is unlikely to change.
The second situation is where the depth reference for the motherbore and sidetrack are different. This is usually experienced when the sidetrack is drilled with a different rig, where the RTE above ground level is different when compared to the motherbore.
The following two sections detail the steps required to deal with these two situations.
This section will cover the creation of a sidetrack using the same depth reference as the mother bore.
Firstly, the user needs to open the well properties and ensure that the Motherbore Depth Reference is checked as Default. In this situation it is likely that other than the Default datum on line 1, the motherbore depth reference will be the only other option. Once selected, hit Apply and then Close.
In the Database Tree, right-click on the well containing the motherbore and select one of the following options:
Insert new actual well if the sidetrack is a survey.
Insert planned well if the sidetrack is a plan.
The Plan Properties/Actual Wellbore Properties dialog will appear. Fill in the Properties, Vertical Section and Magnetics Sections as normal
If the motherbore depth reference was correctly selected as default, then this should be referenced in the Depth Reference section. If it was not correctly selected as default, something else will be referenced here and the user will need to select the correct reference from the drop down menu.
If the user needs to do this, a warning box will appear. Choose the option Preserve TVD’s.
In the Sidetrack Details section, check the Plan is a sidetrack checkbox.
Select the mother bore from the Parent Well/Plan drop-down box and enter the sidetrack depth in the Sidetrack Depth box. Note that the depth must be within the range of the motherbore i.e. a motherbore with a TD of 1000m MD can’t be sidetracked at 1010m MD etc. Then click on the Create sidetrack box.
As soon as create sidetrack has been selected, the below warning will appear. This is warning that proceeding will reset the survey program in the plan or actual wellbore properties. This is not an issue as this section will currently be blank anyway. Select Yes.
The Survey Program and Tie-On sections will automatically update based on the sidetrack depth entered. The survey program will now mirror the survey program of the motherbore down to the sidetrack point, and the tie-on section will show the details of the tie-on line. Click on Apply and then Close to close the Plan Properties/Actual Wellbore Properties.
At this stage the process differs, depending on whether the user is creating a planned or actual sidetrack.
When the sidetrack is a plan, all the user needs to do is open the plan by double right clicking on the plan level. This will open the plan and the tie-on line in row 1 will mirror the sidetrack depth entered in the plan properties dialog.
The user can now build their sidetrack plan as per their planning requirements.
When the sidetrack is an actual wellbore, the first thing the user needs to do after selecting the ST depth and closing the Actual Wellbore properties (Section 3.0) is to create a new survey. The actual wellbore will already contain the motherbore surveys from surface to the ST depth, but in order to enter the ST surveys, the user must first create a new survey.
To do this the user should right click on the actual wellbore and select Insert New Survey.
In the survey Properties Dialog, select From Survey in the tie-on section and from the drop-down section, select the survey that you want to sidetrack. Note that when the appropriate survey has been selected the MD cell will be populated with the deepest survey station for the selected survey. If required, the user can then manually overwrite this value with the appropriate ST depth.
The user can then select the appropriate Survey Instrument from the drop-down menu and select Apply and then Close.
The user can now double right click on the newly created survey. This will open the survey and the tie-on line in row 1 will mirror the tie-on depth entered in the survey properties dialog.
The user can now enter the appropriate surveys as they are received.
This section will cover the creation of a sidetrack which has a different depth reference to the mother bore. This can happen, for example, when a well has been drilled a long time ago and then returned to for side tracking with a different rig.
In the Database Tree, right-click on the well containing the motherbore. Select Properties to open the Well Properties dialog.
In the Depth Reference section, create a new depth reference in the line below the motherbore reference. Give your depth reference a name in the Datum Name column. In the Elev above system column, enter the depth reference height of the sidetrack. Enter the name of the rig used to drill the sidetrack (if available) in the Rig column. Enter the ground level elevation in the Ground Elevation to MSL box. At this stage it is important to check that the Air Gap has been calculated correctly. If this value is not correct, then an error has been made entering the data and this needs to be addressed.
In the above you can see that the RTE above ground level for Rig 2 is 5m greater than Rig 1. Once the user is happy the new elevation has been entered correctly it is important to then select the new ST datum as the Default. Selecting the new ST datum as default at this stage will save a lot of unnecessary steps during the rest of the process which can lead to mistakes being made, so this is an important selection to make. Click on Apply and then Close to close the Well Properties dialog.
In the Database Tree, right-click on the well containing the motherbore and select one of the following options:
Insert new actual well if the sidetrack is a survey. Note, you can only sidetrack an existing survey with this option. If the motherbore is a plan, then this can only be sidetracked by another plan.
Insert planned well if the sidetrack is a plan.
The Plan Properties/Actual Wellbore Properties dialog will appear. Fill in the Properties, Vertical Section and Magnetics Sections as normal. Check to make sure the depth reference is correct. If the new ST datum was selected as default in the Well Properties dialog, then this should be correct.
In the Sidetrack Details section, check the Plan (or well) is a sidetrack checkbox.
Select the mother bore from the Parent Well/Plan drop-down box. This is now the point where the user should select the appropriate sidetrack depth. The sidetrack depth entered in the cell will be referenced to the Depth Datum selected in the plan properties dialog, which may differ from the motherbore. In the situation where the datum selected is different from the motherbore, the user needs to be very careful at this point to ensure they enter the correct depth.
Referencing the below diagram, if the user needs to sidetrack the motherbore at 1000m MD, then they should enter the sidetrack depth as 1005m MD.
Note that the depth must be within the range of the motherbore i.e. a motherbore with a TD of 1000m MD can’t be sidetracked at 1010m MD etc. Then click on the Create sidetrack box.
As soon as create sidetrack has been selected, the below warning will appear. This is warning that proceeding will reset the survey program in the plan or actual wellbore properties. This is not an issue as this section will currently be blank anyway. Select Yes.
The Survey Program and Tie-On sections will automatically update based on the sidetrack depth entered. The survey program will now mirror the survey program of the motherbore down to the sidetrack point, and the tie-on section will show the details of the tie-on line. Click on Apply and then Close to close the Plan Properties/Actual Wellbore Properties.
At this stage the process differs, depending on whether the user is creating a planned or actual sidetrack. For instruction regarding this process, refer to Section 3.1 - Planned Sidetrack and 3.2 - Actual Wellbore Sidetrack.
As soon as the user has setup a planned or actual sidetrack the first thing they should do is check that the sidetrack point has been chosen correctly. One way to double check this is to compare the ST tie-on line with the interpolated sidetrack point on the motherbore.
In the below screen shot, the motherbore plan is on the left and the interpolate window shows the interpolated sidetrack point on the motherbore at 1000m MD. To the right is the sidetrack tie-on line. It is expected that the MD and TVD will be different when comparing these, but if the inclination, azimuth, NS, EW and TVDss are the same, then the ST depth has been chosen correctly. If these values do not tie in, then the user should double check the sidetrack depth selected and adjust appropriately.
A guide to the Project Ahead Function within Well Seeker Pro.
The Project Ahead tool can be found on the Toolbar at the top of the screen.
It is important to note that this option is only available when the user is in a Survey. If the user is in a Plan, or the Actual Wellbore, this option will be greyed out and they will be unable to select it.
When in a survey, select the Project Ahead option. This will open the Project Ahead Box.
Note, that Line 1 at the top of the box will be populated with the last survey point. The projection will be made from this point.
The user can now select from the same Planning Tools which are available when creating a well plan, with the exception of the S-Well and Slant-Well tools, as these can only be plotted from surface.
Once the relevant planning tool has been selected and the values entered, the projection is calculated by selecting Calculate.
The projection can then be added to the survey by selecting Add to Survey and removed from the survey by selecting Remove From Survey.
Two of the more relevant projection options are discussed below.
The Trend Over tool is only available in the Project Ahead dialog and is not displayed in the planning tools when in a well plan. This function allows the user to apply the build and turn trends seen in the previous surveys to the projection.
To select the Trend Over function, the user must select Adjust and then either MD or CL. This function will remain greyed out until these options have been selected.
Select the Measured Depth (MD) or Course Length (CL) of the projection and the number of surveys to model the trend over, then hit the calculate button. The projection will appear in line 2, directly below the last survey in the Project Ahead box.
The tool works by averaging out the Build and Turn rates based on the number of surveys selected.
In the below example, 1 survey has been selected, so the projection just uses the build and turn rate calculated for the last survey.
In the below example, 3 surveys have been selected, so the projection calculates the average build and turn rate values over the last 3 surveys.
Using the Optimum Align function, it is possible for the user to project back onto a plan.
Select Optimum Align
In the target details section, select Plan - all the plans below the Well will be available to select from the drop-down menu – Select the relevant plan
In the By box, input the Measured Depth on the plan that you want to line up on. On entering the depth, the NS, EW, TVD, Inc and Azi will be automatically populated with the values that correspond to this depth
Select the relevant Optimum Align Parameters
Hit Calculate
NOTE, that once the projection has been calculated, the measured depth in almost all cases will not match the depth entered in the By box.
The Multi Nudge Projection tool allows the user to quickly project ahead using additional features which are not available in the standard Project Ahead section of Well Seeker. More importantly, it allows an unlimited number of projection lines to be included.
As with the Project Ahead tool, it is important to note that the Multi Nudge Projection tool is only available when the user is in a Survey. If the user is in a Plan, or the Actual Wellbore, this option will be greyed out and they will be unable to select it.
When in a survey, this tool can be selected from the toolbar or by selecting Tools – Multi Project from the menu bar at the top of the screen.
When the tool first opens, the Tie-On line will be populated with the last survey in the listing. At this point the user can then select from 1 of 5 projection Methods.
The Multi Nudge Projection box can be left open while the user is adding new surveys, and the tie-on line can be updated by selecting the Update Tie On button. Note, that the surveys do not need to be saved for this to happen.
If the box is closed and then reopened, it will automatically tie onto the last survey point. The projection setup will remain populated with whatever setup the user had selected previously, even when the program has been closed and reopened. To remove the input projections, the user can delete the lines one at a time or select Reset to remove all projections.
Projections can be added to the survey by selecting Append to Survey and can be removed by selecting Remove from Survey. The Multi Nudge Projection window can remain open while using other Well Seeker functions, but all projections must be removed from the survey before new survey stations can be entered.
If the user has a slide sheet currently open, Get from Slide Sheet will pull the slide sheet entries in as projections. Note: If the user has not input the motor yield for their slides in the slide sheet, the motor yield and the DLS will default to 15 in the Multi Nudge Projection.
The five projection methods are described below:
This option allows the user to select Course Length (CL), Dogleg (DLS) and Toolface Orientation (TFO) to calculate the projection. This method assumes a 100% slide. Motor Yield will be automatically populated with the same value input in the DLS column.
This option allows the user to select Course Length (CL), Slide Percentage (%) and Toolface Orientation (TFO) to calculate the projection. The user is also required to add the Motor Yield, as the projected dogleg is calculated based on the slide (%) and the Motor Yield.
In the example above, the slide (%) is 50% and the motor yield is 5°/30m, which results in a 2.5°/30m DLS.
This option allows the user to select Course Length (CL), Slide Distance (Dist) and Toolface Orientation (TFO) to calculate the projection. The user is also required to add the Motor Yield, as the projected dogleg is calculated based on the slide (Dist) and the Motor Yield.
In the above example, the Slide Distance is 4m (Course Length is 10m) and the motor yield is 5°/30m, which results in a 2.0°/30m DLS.
This option allows the user to select Inclination (Inc), Azimuth (Azi) and Dogleg (DLS) to calculate the projection. This method assumes a 100% slide. Motor Yield will be automatically populated with the same value input in the DLS column.
This option allows the user to select Course Length (CL). The inclination and azimuth from the tie-on line will be held for the selected distance.
The user can set up the Multi Nudge Projection with as many lines as required.
This section of the Multi Nudge Projection allows the user to project to a landing point and is most useful when landing out a horizontal lateral and functions in a similar way to the Dogleg Toolface - Point planning method.
Note that this section will only work if a principal plan for the well has been assigned. To set a plan as a principal plan, right-click on the plan in the database tree and select Properties. In the Properties window check the Set as principal plan checkbox next to the well name.
The Bit row displays the deepest survey station in the currently opened survey sheet. As this is the most recent survey, to accurately use this projection tool, the user should make a projection to the bit to get the true bit position. To do this the user should make a projection in the top window and append it to the to the survey, as displayed in the image below. The Bit row will update automatically when the projection is added. If for any reason this does not happen, the Update Bit Position button can be used to force an update.
When a MD is entered in the Target row, Well Seeker looks for this MD on the Principal Plan and then populates the rest of the cells in the row with the values from the plan. The Landing Data tool then automatically calculates the constant Tool Face and DLS required to reach that point on the principal plan from the bit position shown in the Bit row.
In the below example, the MD of the curve landing point (7751.18 USft MD) has been entered and the TVD, NS and EW coordinates in the projection match the plan at this depth. The Tool Face and DLS columns show the Tool Face and DLS required to reach this landing point from the current bit position. Note that the plan is open here for demonstration purposes. It does not need to be open for the Landing Data window to work.
The Select Critical Point drop down box can be used to quickly select plan points from the principal plan as the landing target. If the principal plan is changed while the Multi Nudge Projection is opened, the list of plan points can be updated using the Update button.
The user can also enter a target using the Find Landing button. This button will automatically pick the plan point from the principal plan that has the highest inclination. If multiple plan points share the highest inclination, the Find Landing button will pick the shallowest.
The Append to Survey button will add the Target row to the survey list as a projection, while the Remove from survey will delete it. Projections from both the Multi-Nudge section and the Landing Data section can be present on the survey list at the same time.
The landing data calculation should automatically update whenever new input data is added; however, if for any reason this does not happen, it can be updated manually using the Calculate button.
Selecting the Adjust TVD checkbox allows the user to change the TVD of the point selected in the above. The MD stays unchanged as this is what the program is using to determine the local coordinates of the landing point.
Note in the below example how the NS and EW local coordinates are still the same as the landing point line, but because the TVD has been shifted deeper the DLS, Tool Face and Inc have changed. The program is still aiming for a specific point here, only with an adjusted TVD.
This option is only available when Adjust TVD is selected.
This allows the user to enter an Inc, Azi and TVD to project to. The main difference with this selection compared to the previous options is that the user is not projecting to a specific point i.e. the local coordinates are not fixed.
In the example below, the Inc, Azi and TVD are entered for the planned curve landing point. Note that the MD, NS and EW landing points are no longer the same as the landing point in the plan. This setup simply tells the user what dogleg is required to land out at horizontal for a given TVD. When new surveys are added, the bit line updates automatically and so does the landing point line.
NOTE: When you first open this dialogue, there is no requirement to enter a MD. It is possible to just select Adjust TVD and Adjust Inc / Azi and input the values. There is no need to add a MD unless you specifically want to hit an exact point.
The TVD Projection feature can be activated by clicking on the check box in the top right of the Landing Data window. This feature displays two new Target rows that are offset by a user specified TVD from the main Target row.
In the example below, TVD Projection 1 has been set as -10, so its target is the same as the Target row but 10 USft TVD shallower. TVD Projection 2 has been set as 10, so its target is 10 USft TVD deeper.
The TVD projection feature can be used in tandem with the Adjust TVD and the Adjust Inc/Azi functions. TVD projections are for reference only and cannot be appended to the survey list.
The document is split into the following sections:
Office - Pre-Job Steps
Rig Site – Pre-Job Steps
Rig Site – WITS Setup
Rig Site- Drilling Operations
Office – Monitoring Drilling Operations
Rig Site – End Of Well Steps
Office – Post-Job Steps
These steps describe how to set up a job on your company’s remote server database, so that it is ready for the rig crew to download when they arrive at the rig site.
1. Log on to the SQL server field database.
If you are using a corporate license, your login window may be simplified (right) and will require you to only enter your username and password. Otherwise, you will require additional login credentials for your SQL server database (left).
2. Review your default activity, phase and cost codes. Click on the Tools menu and select Code Defaults.
3. Use the Code Defaults window to review the default activity, phase and cost codes for the server database. These codes will be applied to any new operator and actual well that is created, either manually or when imported using a Compass EDM file. When you are satisfied with your default codes, click on the Save icon and then close the window. Note that you will be able to tweak the codes for your well later.
Steps four, five and six assume that you will set up your well by importing a well plan from Compass. If you have built your well and/or well plan in Well Seeker, skip to step seven.
4. Review your Compass import settings.
5. Select Import Compass EDM file.
7. Make sure that your principal well plan has been correctly designated. Right click on the well plan and select Properties.
8. In the Plan Properties window, check the Set as Principal Plan checkbox and click Apply, then Close.
9. Right click at well level and select Insert new actual well.
11. Right click at actual well level and select Insert new survey.
12. Input and check survey name, tie on details and survey instrument/IPM. After checking your inputs, click on Apply and then Close.
13. Double click on the newly created survey to open the survey table. Click on the Save icon. When the program asks Do you wish to add this survey to the survey program? Click Yes. Then close the survey table.
14. Double click on the actual wellbore to open the actual wellbore table. Click on the Select Offsets icon in the toolbar, or open the Tools menu and select Offset Selector.
15. In the Select Offsets window, select all relevant offset wells. If you need to select offset well plans, you will need to make them visible by activation them in the Filters section. Once you have selected the desired offsets, click on Apply and then Close.
16. Right click on the actual well and select Reporting >> Drill String Editor.
17. In the Drill String Editor window click on the Add New BHA icon in the toolbar. In the newly crated BHA, input the BHA description and BHA number. Click on the Save icon and then close the window.
18. Open the Tools menu and select Personnel Names and Details.
19. In the Personnel Details window, ensure that the DD Coordinator, MWD Coordinator, DDs and MWD Engineers for the upcoming job are present in the list. Other personnel are optional. Once you are satisfied, click on the Apply button and then Close.
20. Open the Tools menu and select Rig Names.
21. In the Rig Names window, ensure that the rig being used in the upcoming job is present in the list. Once you are satisfied, click on the Apply button and then Close.
22. Open the Tools menu and select Shipping Addresses.
23. In the Addresses window, list contains any relevant addresses for the upcoming job. For example, the address of the rig and the workshop that tools will be shipped to/from. This will aid the field personnel when they come to create shipping tickets. Once you are satisfied, click on the Apply button and then Close.
24. Right click on the actual well and select Reporting >> Daily Reporting.
25. In the Daily Reports window, click on the Activity Codes icon on the toolbar. In the Activity Codes window, verify the activity codes are correct. Any changes to the codes here will only apply to the current operator and do not affect the default codes. You can reset to the default codes by clicking on the blue arrow icon in the toolbar. Once you are satisfied, click on the Save icon and close the window.
26. Click on the Phase Codes icon on the toolbar. In the Phase Codes window, verify the phases codes are correct. Any changes to the codes here will only apply to the current operator and do not affect the default codes. You can reset to the default codes by clicking on the blue arrow icon in the toolbar. Once you are satisfied, click on the Save icon and close the window.
27. Click on the Cost Codes icon on the toolbar. In the Cost Codes window, verify the cost codes are correct. Any changes to the codes here will only apply to the current well and do not affect the default codes. You can reset to the default codes by clicking on the blue arrow icon in the toolbar. Once you are satisfied, click on Apply and Close.
28. In the Daily Reports window, set the Well Status as Upcoming. Select the DD Coordinator and the MWD Coordinator from the dropdown menus. If they are not available, go back to step 18 and update the Personnel Details. Click on the Save button and then close the window.
29. Right click on the actual well and select External Files. Here you can add any file that you want the rig to have when they start the job. Click on the folder icon to select the desired file. You have the option to assign a category to the file if you wish using the drop down box. Click on the Add button to add the selected file to the well. Once you have added all of the desired files, click on the Close button.
These steps detail how the rig crew can download the job data from the remote server, and get the software ready to record drilling activity.
1. Open Well Seeker.
2. If you use a single database to store all of your wells, select it by opening the File menu and click on Select Database. If not, create a new blank database by opening the File menu and click on Create New Database. After you have created your new database, you will need to select it using Select Database.
3. You can confirm your currently selected database by checking the path displayed on the status bat at the bottom of your Well Seeker window.
4. Use the Remote Data Fetch tool to pull down your job from the server database. Open the Tools menu and select Remote Data Fetch.
5. In the Data Fetch window, enter the details for your company’s ICDS IP Address and Port. If you have a corporate license, these details may be automatically entered. If not, you will need to get them from your company administrator. After entering your details, click on the Connect button.
6. Find your job in the list of wells on the server database. You can use the search box and the filter drop down boxes at the top of the window to narrow down the list.
7. Make sure that Pull Offset Wells and Pull Principal Plan have been turned ON in the options section the bottom right corner of the window.
8. Select the actual well for your job from the list by clicking on the circle, then click on the Fetch Data button. When the download is complete, the message box should display the message Data Fetch Complete! You can now close the window.
9. Right click on the actual well and select External Files. Here you can view any files that were attached to the job. You can also put any signed tickets here during the job.
10. Right click on the well plan and select Properties. Check that all of the information is correct, and then click on Close.
11. Double click on the well plan to open it. Check that the well plan matches what well planning sent in their report.
12. The office will have made an actual well for you. Right click on the actual well and select properties. Check that all of the information is correct, and then click on Close.
13. Right click on the actual well and select Reporting >> Tool Inventory.
14. Fill in the inventory with your tools that you have on location. When you are finished, click on the Save button and then close the window.
15. Right click on the actual well and select Reporting >> Drill String Editor.
16. You should find that the office personnel have already created the first BHA. Start filling in the components for the BHA, starting from the bit. For each component, start by selecting the component type from the Component column. Then right click on the row and select Insert from Inventory. This will allow you to pick one of the components that you recorded in the Tool Inventory. Alternatively, select Insert from Catalogue. This will allow you to insert components from a list of generic tools.
17. After inserting a component, fill in its Component Properties on the right.
18. Repeat the process for each component until the BHA is complete. You can also fill in the Rig, MWD #, Mud Weight and target Formation if you wish. Click on the Save icon and then close the window.
19. Right click on the actual well and select Reporting >> Daily Reporting.
20. Click on the Add Daily Report icon in the toolbar to create your first day.
21. Click on the Well Data & Personnel icon in the toolbar.
22. Fill in the Well Data & Personnel with the information that you have, but make sure to fill in the Job #, Rig, State, County and the Day/Night DDs and MWD Engineers.
The Rig and Personnel fields should be selectable using drop down boxes. If not, go back to the Daily Reports window, open the Report Options menu and make sure that Use dropdown list for personnel/rig is toggled on.
After entering the information, click on Apply.
23. If you wish to add pump information, you can add it by clicking on the Pump Data icon in the main toolbar. After entering the pump data, click on Apply.
24. Click on the Daily Costs icon in the main toolbar. Enter the charges for the using the dropdown menu in the Description column. Enter the quantity and select an associated BHA, if applicable. After entering the charges, click on Apply.
25. Open the Reporting Options and select Set Default Activity Code / Description. This option sets the activity and comment that will be used to fill in time gaps when the Get DDR from Run Sheet button is pressed. Usually this will be survey and connection time, so pick an activity that represents that.
If it is company policy to count survey and connection time as circulating time, choose an activity code starting with 5 such as 5A: Circulate. If not, choose a different code such as 10D: Survey & Connection. If in doubt, check with your coordinator.
26. Set the Well Status to Active.
27. You can now start recording your daily activities. Remember to save regularly by clicking on the Save icon in the main toolbar.
The Daily Reports window does not need to be closed in order for you to work in other parts of Well Seeker. It can be minimized or moved to another screen.
28. All rigs should send data back to the server database. This can be done in the background using the Real Time Data Exchange. In the Daily Reports window, click on the Real Time Data Exchange icon in the main toolbar. If you are in the main Well Seeker interface, open the Tools menu and select Real Time Data Exchange.
29. In the Data Exchange dialog, use the dropdown boxes in the Select Well section to choose the current job.
30. In the ICDS Server section enter the details for your company’s ICDS IP and Port. If you have a corporate license, these details may be automatically entered. If not, you will need to get them from your company administrator.
31. In the Select Data section, select the data that you wish to push back to the server. At a minimum, select Surveys and Daily Reports. For other selections, discuss with your coordinator.
32. In the Data Transfer section, set the update rate. This sets the time between pushes to the server. For this example, we will use 30 minutes. Click on the Start button to begin running the data exchange.
33. You can now close the Data Exchange window. It will keep running in the background. You can view the status of the data exchange in the bottom right hand corner of the main Well Seeker window.
This section only applies if you are using a WITS feed from the rig to automatically fill in your slide sheet. If you are recording your slide sheet manually, you can skip to the next section.
1. In the main Well Seeker interface, open the Tools menu and select WITS mappings. Coordinate with the rig to make sure that the RECORD_ID and FIELD_ID match with the incoming WITS data. When you have finished, click on Apply.
2. The rest of the WITS options are found in the slide sheet. In the database tree, double click on the survey for the job to open it. Then right click on the survey in the database tree and select Reporting >> Slide Sheet.
3. In the slide sheet window, click on the Serial / TCP WITS Comms icon in the toolbar to open the WITS Comms window. Choose your WITS settings depending on the method of input:
a. If you are using a serial cable, select your comm port in the Serial WITS Settings section.
b. If you are using an ethernet cable, select your input type, port and IP address in the Ethernet WITS settings.
4. Click on Start Reading. You should see data coming through in the WITS Data Stream section.
5. You should also send data back to the server. The IP and Port boxes on the right hand side of the window define which server you are uploading to, and are set by the IP and Port set in your Real Time Data Exchange window. Toggle on the Send Data To Server option. If the upload is successful, you will see the message Update completed with no critical errors.
6. Minimize the WITS Comms window. Do not close it.
7. Click on the Rig States icon in the Slide Sheet main toolbar. In the Rig States window, the incoming WITS values are displayed in the Current WITS Data section. Adjust the settings in the Thresholds section so that the WITS data is translated into the correct rig state in the Current Rig State section.
8. Minimize the Rig States window. Do not close it.
9. In the slide sheet window, make sure that the correct BHA is selected in the drop down box. Click on the green Auto Populate Slide Sheet icon in the toolbar. You will see the message Live rig states running appear and you will no longer be able to edit the slide sheet. Instead it will automatically populate using the incoming WITS data. To stop recording, click on the red Stop Populating Slide Sheet icon in the toolbar. Remember to save regularly using the save icon in the toolbar.
10. Minimize the slide sheet, do not close it while recording WITS data. You will be able to work in the Daily Reports and main Well Seeker windows with the slide sheet minimized in the background.
The steps below detail some of the tools available to the rig crew during drilling operations, as well as recommended procedures for filling in and performing quality control on your reporting data.
1. Fill in your daily reporting activities until you are on bottom and drilling. From this point, begin recording your slide sheet and surveys. Drilling activities can be automatically transferred from the slide sheet to the daily report using the Get DDR from Run Sheet button, as detailed in Step 9, below.
2. When viewing a survey sheet, the Up/Down, Left/Right and (Centre-to-Centre) Dist columns can be used to monitor how closely you are following the principal plan. If these columns are not available, they can be activated using the Survey Column Show Hide option in the View menu.
3. If the wrong plan is set as the principal, it can be changed using the Set as principal plan option in the Plan Properties window.
4. Plots can be viewed when a survey or plan is open. Click on any of the plot icons on the toolbar, or select them from the Plots menu.
5. When viewing a plot, offset wells/plans can be toggled on or off by clicking on the Toggle Offsets icon on the toolbar. The selected offsets can be edited by clicking on the Offset Selector icon on the toolbar or in the Tools menu.
6. Projections can be added to a survey using the Multi-Project and Project Ahead tools. Multi-project allows you to add multiple, simple projections, while Project Ahead utilises the same planning tools as the well plan. Both of these windows can be left open while working in other parts of the software. Access them using the icons in the toolbar or in Tools >> Projection Tools.
7. The Real Time Anti-Collision (RT AC) dialog can be accessed when viewing a survey. Open it by clicking on the icon in the toolbar or by selecting Tools >> Dashboards >> RT AC Warnings. The RTAC will display the anti-collision results for all selected offsets, the principal plan and any lease lines/hard lines.
8. The Directional Drilling (DD) Dashboard collects data from multiple sources within Well Seeker and displays them in one interface, allowing the Directional Driller or a RTOC to monitor drilling operations from a single screen. It is accessed via the Slide Sheet. In the Slide Sheet window, click on the DD Dashboard icon in the toolbar.
The DD Dashboard will then open. It can be left open while working in other parts of the software. Multiple DD dashboards can be opened at the same time, but this can be taxing on your computer’s CPU and memory.
Real time gauges showing various drilling parameters. Requires WITS data from the rig.
Toolface rose displaying details of the last slide.
Real time anti-collision.
Recent surveys with automatic bit projection.
3D plot showing principal plan and bit projection.
Drilling parameters plot and current rig state. Requires WITS data from the rig.
9. During drilling, click on the Get DDR from Run Sheet button in the Daily Reports window to automatically fill in your drilling activities using the data recorded in the Slide Sheet. Any gaps in drilling activity will be filled in with the default activity code that you set in the Report Options menu.
10. Click on the Get Params button to automatically update your run and 24hr parameters using the data recorded in your slide sheet. Update mud properties and Well Data & Personnel with any changes. Remember to fill in the Daily Costs for each day.
11. At the end of each day, it is recommended to QC your report. Open the Data Validation menu and select Check activity against slide sheet. If the drilling activities in your report do not match with the slide sheet, you will get an error message. You should also check the following:
a. The depth at the start of the day is correct.
b. All activity codes are correct.
c. If a BHA has been picked up or lay down, it has a 6O or 6P activity assigned. If no BHA is in the hole, the BHA field should be blank.
d. Every activity has a phase assigned to it.
12. It is also recommended that you backup your database at least once a day. In the main Well Seeker interface, open the File menu and select Backup Database. This will let you save a backup copy of your database.
13. Print your Daily Report by going to File >> Print DDR or File >> Print PDF Reports >> Print DDR. You can configure what is included in the DDR by opening the Report Options menu and using the Daily Report and Additional Daily Report Options submenus.
14. You can create a morning report by going to File >> Create Morning Report Package. This morning report is treated like an End Of Well Report and is configured in the EOWR submenu in Report Options. The package contains the following:
a. A copy of the database.
b. An Excel format EOWR up to the current day.
c. An email template containing a summary of the current status of the well.
15. At the end of a run you should fill out the performance report for the BHA. Open the Drill String Editor, select the current BHA and click on the Performance Report icon in the toolbar.
16. In the Performance Report, click on the Get Data From DDR. This will automatically fill in the parameters section using data recorded in the Daily Reports.
17. Click on Get MWD Surface System. This will pull all of the surface system serial numbers from the Tool Inventory, allowing you to select them using dropdown boxes in the MWD section.
18. Make sure a Reason for POOH has been selected. Make any general comments on the run in the Additional Comments and MWD Comments section.
19. If there was a tool failure, record it by clicking the Motor Failed, MWD Failed or RSS Failed check boxes. If a different tool caused the failure, just click the Failed checkbox in the top right. This will activate the Failure section allowing you to record details of the failure. Make sure to click the Trip For Failure or LIH (Lost in Hole) checkboxes if these apply.
20. Save and then close the Performance Report.
21. Save your BHA and then create the BHA for the next run by clicking on the Add New BHA icon. You can also click on Copy BHA, which will create a new BHA and copy over all of the components from the current BHA. Give the new BHA a name and BHA #. Once you have finished filling in the new BHA, you can Save and then close the Drill String Editor.
The following steps introduce the tools that can be used to monitor the job from the office. These tools require the field engineers to be pushing data from the rig site using the Real Time Data Exchange. Some also require the WITS feed from the rig to be pushed to the server.
1. Log into the remote server database.
2. Open the Tools menu and select the Dashboards submenu. These dashboards can be used to provide information for multiple wells at the same time.
3. The Anti-Collision (AC) Dashboard allows you to monitor the anti-collision status of multiple wells at the same time. Open the File menu and select Open RT AC For Active Wells. A window will appear displaying all wells that are currently set to active in the daily reports. Select the ones you want to monitor using the Select column. You can also change the offset settings of the wells by toggling Update Offset Selection on.
4. Click on the OK button and Well Seeker will open the Real Time AC dialog for the selected wells. The AC Dashboard will also populate with two lines for each selected well. One will show the offset well with the lowest C2C distance to the selected well. The other will show the offset with the lowest SF to the select well. If any anti-collision limits are breached, the lines will be highlighted in red.
5. The Rigs Online Dashboard displays all of the rigs that are currently pushing data to the server using the real time data exchange. The Time Since Update column displays the time in hours and minutes since the last update from the rig. Opening the File menu and selecting Show WITS Connections will cause the list to also display wells that are pushing WITS data to the server.
6. The Logistics Dashboard searches all the well inventories in the database and displays all tools which are listed in these inventories. Note that if the On Location box is not checked, the tool will not show up in this dialog. The list van be filtered using the dropdown boxes and search bar.
7. The Activity Dashboard displays an overview of all ongoing jobs in the server database – that is any job with the daily reporting status set as Active, Standby, Upcoming or TD. The list of wells at the bottom of the window can be filtered using the dropdown boxes. Selecting a well from the list will display information for that specific well.
8. The Incident Dashboard displays all BHA failures that have occurred in the last 12 months. This is logged using the Motor Failed, MWD Failed or RSS Failed checkboxes in the performance report. Selecting a well from the list at the bottom will display the BHA assembly of the well.
9. The Directional Drilling (DD) Dashboard collects data from multiple sources within Well Seeker and displays them in one interface, allowing the Directional Driller or a RTOC to monitor drilling operations from a single screen.
It is accessed via the Slide Sheet. Open one of the surveys for the well you wish to view. Then right click on the survey in the database tree and select Reporting >> Slide Sheet.
In the Slide Sheet window, click on the DD Dashboard icon in the toolbar.
The DD Dashboard will then open. It can be left open while working in other parts of the software. Multiple DD dashboards can be opened at the same time, but this can be taxing on your computer’s CPU and memory.
Real time gauges showing various drilling parameters. Requires WITS data from the rig.
Toolface rose displaying details of the last slide.
Real time anti-collision.
Recent surveys with automatic bit projection.
3D plot showing principal plan and bit projection.
Drilling parameters plot and current rig state. Requires WITS data from the rig.
Once drilling operations have finished, follow the below steps to QA & QC your reporting data and close out the well.
1. Finish recording activities and parameters for the last day. Make sure that the last BHA has a 6P: Lay Down BHA activity assigned. Save and then close the Daily Reports window.
2. Save and close your slide sheet.
3. Save your surveys. Open the Actual Well Properties and check that the survey program is updated down to TD.
4. Once you have finished prepping your tools for backload, right click on the actual well and select Reporting >> Tool Inventory. In the Tool Inventory, mark tools that are ready for backload by clicking in the Ready for Backload column. When you are finished, click Save and close the window.
5. Right click on the actual well and select Reporting >> Shipping Ticket.
6. Create a new ticket by clicking on the New icon in the toolbar. In the Shipping From section, select the rig address from the dropdown box. In the Shipping To section, select the destination address. If these addresses are not available in the dropdown boxes, you can fill them in manually.
7. Add a comment and then select the tools that you want added to the ticket by clicking in the Select column. If you marked tools as Ready for Backload in the Tool Inventory, you can quickly select them by clicking the Mark Tools ready for Backload button.
8. Save your shipping ticket and then Print it. Once your tools have been shipped, you can click on the Ship Tools button to automatically mark your tools as off location in the Tool Inventory.
10. Right click on the actual well and select Reporting >> Daily Activity Editor. Check for the following:
a. Time Gaps – The start time of every activity should match with the end time of the previous activity. The editor will highlight any gaps in red.
b. Depth Gaps - The start depth of every activity should match with the end depth of the previous activity. The editor will highlight any gaps in red.
c. BHAs – Every BHA should have exactly one 6O: Pick Up and one 6P: Lay Down activity. Every row should have the BHA selected while it is in the hole. When no BHA is in the hole, the BHA cell should be blank.
d. Phases – Every row should have a phase selected.
Once you have completed these checks, click on Apply and Close.
11. Right click on the actual well and select Reporting >> Daily Reporting.
12. In the Daily Reports window, open the Data Validation menu and select Check activity against slide sheet all reports. Well Seeker will generate and open a text file that details all of the places where the drilling activities in the slide sheet do not match up with the daily activities in the daily reports.
Use the text file as a guide, and alter either the daily reports or the slide sheet until all errors have been dealt with. When you are finished, click on the Save icon in the toolbar.
13. Open the Data Validation menu again and select Zero RPM for all slides on slide sheet. This sets the RPM parameter on all slides in the slide sheet to 0, as this is supposed to represent surface RPM. Click on the Save icon in the toolbar again, and then minimize the Daily Reports window.
14. In the database tree, double click on one of the surveys for the job to open it. Then right click on the survey in the database tree and select Reporting >> Slide Sheet. For each slide sheet in the well, check through your drilling parameters to make sure that there have been no typos or mistakes.
A common mistake is that the drilling parameters get entered with the wrong units. If you are not sure what units you are supposed to be using, open the Tools menu in the main interface and select Unit Sets. The units in this dialog are the units used in the slide sheet.
When you have finished with each slide sheet, save your changes by clicking on the Save icon in the toolbar. When you have finished with every slide sheet, close the slide sheet window.
15. Go back to the Daily Reports window, open the Data Validation menu and select Update Activity Description from slide sheet all reports. This will take the drilling parameters that you have just checked in your slide sheets, and use them to update the descriptions for your drilling and sliding activities in your Daily Report.
16. Open the Data Validation menu and select Get drilling params from slide sheet all reports. This will take the drilling parameters that you have just checked in your slide sheets, and use them to update the 24hr and run parameters in in your Daily Report.
Click on Save in the toolbar and then minimize the Daily Reports window.
17. Once you have finished QC’ing the Daily Report, you should make sure that all of your BHA performance reports are filled in. Right click on the actual well and select Reporting >> Drill String Editor, then open the Performance Report by clicking on the icon in the toolbar.
18. For each performance report check that:
a. Parameters have been filled in. If not, you can click on the Get Data from DDR button in the toolbar. This will automatically update the drilling parameters in the performance report.
b. A reason for POOH has been selected.
c. If the BHA had a failure, make sure that this has been recorded.
19. You can now print your End of Well Report. In the Daily Reports window, open the Report Options menu and open the EOWR sub-menu. Toggle the options there on or off to set whether or not they are included in the EOWR.
20. In the Daily Reports window, open the File menu and select Print EOWR. This will print your EOWR in Excel format. If you want to print in PDF format, select File >> Print PDF Reports >> Print EOWR.
21. Set the well status to EOW Ready or EOW Sent. Click on Save and then close the Daily Reports window.
22. Right click on the actual well in the database tree and select External Files. Add any relevant documents, such as the EOWR and the shipping ticket.
23. Open the File menu and select SQL Server Databases. Make sure the Push External Files is toggled ON.
24. Push the last update to the server. Open the Tools menu and select Real Time Data Exchange. Force a push by clicking on Manual Push. Wait for the message box to say File Transmission Successful and External Files Transmission Complete. You can then stop the data exchange by clicking on the Stop button and closing the window.
1. Verify that the bottom line of the actual wellbore and actual well properties match with the well planner’s details.
2. Right click on the actual well and select Reporting >> Daily Activity Editor. Check for the following:
a. Time Gaps – The start time of every activity should match with the end time of the previous activity. The editor will highlight any gaps in red.
b. Depth Gaps - The start depth of every activity should match with the end depth of the previous activity. The editor will highlight any gaps in red.
c. BHAs – Every BHA should have exactly one 6O: Pick Up and one 6P: Lay Down activity. Every row should have the BHA selected while it is in the hole. When no BHA is in the hole, the BHA cell should be blank.
d. Phases – Every row should have a phase selected.
Once you have completed these checks, click on Apply and Close.
3. Right click on the actual well and select Reporting >> Daily Reporting.
4. In the Daily Reports window, open the Data Validation menu and select Check activity against slide sheet all reports. Well Seeker will generate and open a text file that details all of the places where the drilling activities in the slide sheet do not match up with the daily activities in the daily reports.
Use the text file as a guide, and alter either the daily reports or the slide sheet until all errors have been dealt with. When you are finished, click on the Save icon in the toolbar.
5. Open the Data Validation menu again and select Zero RPM for all slides on slide sheet. This sets the RPM parameter on all slides in the slide sheet, as this is supposed to represent surface RPM. Click on the Save icon in the toolbar again, and then minimize the Daily Reports window.
6. In the database tree, double click on one of the surveys for the job to open it. Then right click on the survey in the database tree and select Reporting >> Slide Sheet. For each slide sheet in the well, check through your drilling parameters to make sure that there have been no typos or mistakes.
A common mistake is that the drilling parameters get entered with the wrong units. If you are not sure what units you are supposed to be using, open the Tools menu in the main interface and select Unit Sets. The units in this dialog are the units used in the slide sheet.
When you have finished with each slide sheet, save your changes by clicking on the Save icon in the toolbar. When you have finished with every slide sheet, close the slide sheet window.
7. Go back to the Daily Reports window, open the Data Validation menu and select Update Activity Description from slide sheet all reports. This will take the drilling parameters that you have just checked in your slide sheets, and use them to update the descriptions for your drilling and sliding activities in your Daily Report.
8. Open the Data Validation menu and select Get drilling params from slide sheet all reports. This will take the drilling parameters that you have just checked in your slide sheets, and use them to update the 24hr and run parameters in in your Daily Report.
Click on Save in the toolbar and then minimize the Daily Reports window.
9. Once you have finished QC’ing the Daily Report, you should make sure that all of your BHA performance reports are filled in. Right click on the actual well and select Reporting >> Drill String Editor, then open the Performance Report by clicking on the icon in the toolbar.
10. For each performance report check that:
a. Parameters have been filled in. If not, you can click on the Get Data from DDR button in the toolbar. This will automatically update the drilling parameters in the performance report.
b. A reason for POOH has been selected.
c. If the BHA had a failure, make sure that this has been recorded.
11. After all data QC has been completed, open the Daily Reporting for the well and changed the well status to Verified.
12. If you have a clean master database, you can now transfer the well, using your company’s preferred method. After doing so, change the well status to Transferred.
A step by step guide to installing Well Seeker Pro
Well Seeker PRO can be supplied as a zipped installation file which must be unzipped before use. Right click on the file and select “Extract All….” From the context menu.
Select a location which you wish to extract the files to and click “Extract”. The installation files will be extracted to the selected location in a folder called “Well Seeker PRO”
Once the files have been extracted, open the Well Seeker Pro folder and double click on the “Well Seeker PRO vx.x.x.exe” file to begin the installation process.
The installer checks the computer for some prerequisite software, which is required for Well Seeker Pro to operate correctly. If any of these software items are missing from the computer, then the installer will go through the steps of installing them before installing Well Seeker Pro. To proceed with the installation of the prerequisite software select “Next”.
If the Microsoft Edge Update (Microsoft Edge webview2 run time) is missing, then the below figure will display. Select “Next”.
If Visual C++ Redistributable for Visual Studio 2015-2022 is missing then the below figure will display. Select “Next”.
If a version of Visual C++ Redistributable for Visual Studio 2015-2022 is already present on the PC then the below window may appear. Select “Repair”.
Once installed select “Close”. If you select “Restart” at this stage the Well Seeker installation will be aborted.
If the Microsoft ODBC Driver 17 for SQL Server is missing then the below figure will display. Select “Next”.
Read the Microsoft ODBC Driver 17 for SQL Server license terms. Select “I accept the terms in the license agreement”. Select “Next”.
In the Microsoft ODBC Driver 17 for SQL Server feature selection section, select “Next”.
In the Microsoft ODBC Driver 17 for SQL Server ready to install section, select “Install”.
Select the location which you wish to install Well Seeker Pro. The default location is “C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO\”. If you wish to change the location the program is installed to click on the “…” button.
Click on “License terms and conditions”. This will display the below screen.
Read the terms and conditions. This information can also be printed for future reference by selecting the printer icon. Once read, select the “Accept and Install” button to begin installation.
If the copy of Well Seeker Pro is genuine the user will be presented with a dialog showing the verified publisher as “Innova Drilling & Intervention”. If not the software is not genuine and should not be used. Click “Yes” to continue the installation.
Once the installation is complete the final dialog will display “Well Seeker PRO has been successfully installed”. Select “Finish” to close the dialog. An icon will have been added to the desktop and an entry for “Well Seeker PRO” will be in the start menu.
Finally, restart the PC to ensure that the Visual C++ Redistributable for Visual Studio 2015-2022 is fully functional, prior to opening Well Seeker Pro.
A guide to adding a new Coordinate Reference System within Well Seeker Pro.
There is a possibility you may find yourself in a situation where you are required to do planning referencing a CRS which is not available in Well Seeker. In this situation the information relating to the CRS should be requested from the client and can then be used to create a new CRS in Well Seeker.
The below screen shot is an example of the type of information which will be supplied by the client.
The following instructions detail how to use this information to create a new CRS.
1. From the Tools menu, open the Geomagnetic Calculator.
2. Click on the "Mapping Grid" button at the top left of the window.
3. Click on the Add New CRS in the toolbar to add a blank CRS to the list named ‘New CRS’.
4. Select ‘New CRS’ and click on Edit CRS in the toolbar. You will now be able to add information to your new CRS.
Parameters highlighted in GREEN are required and affect the output - Care should be taken to enter the data correctly:
Name: This can be anything you want as it has no impact on any of the calculations. In Well Seeker, the naming convention is the System / and then the Map Projection, and it is recommended that this convention is followed. For this example, the name would therefore be Polska 1992 / Transverse Mercator (Gauss-Kruger) Zone 3.
Area of use: Description of which part of the earth this CRS references and has no effect on any of the calculations. For this example, all we know is it is in Poland.
Datum: This is just text and does not directly affect any calculations. For this example, it is WGS1984.
System: This is just text and does not directly affect any calculations. Polska 1992.
Ellipsoid: The name of the Ellipsoid. This does not have any effect on the output. In this example you would choose WGS 1984.
Semi Major Axis (m): This is the Equatorial Radius of the Ellipsoid in metres and is required for the CRS to work. In this example it should be 6378137.
Semi Major Axis (UOM): This is the equatorial radius of the ellipsoid in the units of measure which the CRS is using and is optional. In this example it should be 6378137 again.
Units of Measure: This is a drop-down menu option, and you can choose from 7 options. For this example, it would be metre.
Inverse Flattening: Also called ‘1/f’, this is the inverse Flattening of the Ellipsoid and is required for the CRS to work. For this example, it should be 298.257224.
Map Projection: This is just text and does not directly affect any calculations - Transverse Mercator (Gauss-Kruger) Zone 3.
Projection Type: This is a drop-down menu, and you can choose from 4 options – TM, 1SP (Standard Parallel), 2SP or STEREO.
False Easting: 500000.00 m.
False Northing: -5300000.00 m.
Latitude of Origin: This should be input as a decimal - 0.0000 deg (See Point to Note Below).
Longitude of Origin: This should be input as a decimal - 19.0000 deg (See Point to Note Below).
Scale Factor: Ratio between measured distance on the map and on the ground - 0.99930 deg.
1st Standard Parallel: This information will be required if you select 1 SP or 2 SP from the Projection Type Drop down menu - Not applicable here - (See Point to Note Below).
2nd Standard Parallel: This information will be required if you select 2 SP from the Projection Type Drop down menu - Not applicable here - (See Point to Note Below).
5. The screen shot below is what your new CRS should look like based on the example information detailed above. Click on the Save icon in the toolbar to add your new CRS to the list and make it available to select from the mapping grid dropdown menu.
When adding Latitude & Longitude of Origin, and the 1st and 2nd Standard Parallel values, these are input as decimals. The below screen shot is from a CRS which requires all of these inputs. You can see that the numbers are provided in both decimal and degrees, minutes and seconds. To accurately input these values into a new CRS, the 4 decimal places displayed is not enough. This means that you will have to convert the degrees, minutes and seconds into decimal (so that you can see the additional decimal places) and input the numbers to 13dp.
The screen shot below shows a simple way to do this in excel. The formulae column shows the formulae used in the decimal column. You will note that to 4 decimal places the numbers match those above.
You can now add these numbers to the relevant CRS input.
After creating a new CRS, it is recommended that you check it for errors by comparing it against a location from an external source. This source must:
Use the same CRS as the one you just created.
Provide a location, such as the location of a wellhead, in both grid northing/grid easting AND latitude/longitude.
In Well Seeker, open the Tools menu and select Geomag Calculator. In the geomagnetic calculator, select your newly created CRS in the projection details section. Enter the grid northing and grid easting of the location, and Well Seeker will automatically generate the latitude and longitude.
If the latitude and longitude generated in Well Seeker match with the latitude and longitude in the external source, then the CRS are the same.
A guide to backing up a Well Seeker Pro local Database.
When Well Seeker Pro is installed for the first time, part of the install is a database which can be found in the following location.
When the program is opened for the first time, this is the database which Well Seeker will access. The database being accessed is referenced in the bottom right corner of the Well Seeker screen.
Well seeker database files have a .mdb file extension, and the user can easily create and switch between databases using the File – Create New Database and File – Select Database features in the top menu.
It is very important that the user regularly backs up their databases to ensure they always have a copy in case something happens to their computer or in case there is some other issue.
The current database is defined as the database which is currently being accessed when you open Well Seeker. This database is backed up as follows:
Open Well Seeker
Select File – Backup Database
Choose an appropriate location to save the database and select an appropriate name. For example, Master Db.mdb or Master Db (Date).mdb etc.
Locate the database to be backed up. This will be a .mdb file.
Copy the .mdb database file and save it in the required backup location.
At this point the user can rename the database if necessary (but this is not required). For example, Well_Seeker_DB.mdb could be renamed Well_Seeker_DB (Date).mdb, or it could be completely renamed. This is just for reference and has no effect on the database itself.
When necessary a backup database can be accessed when in Well Seeker by selecting File – Select Database. The user should then Navigate to and select the relevant back up.
The backup location should NOT be in the Programs (x86) folder. Rather it should be in a documents folder on the computer C drive, or ideally somewhere that is backed up regularly i.e. a shared drive etc. The user’s desktop should also be avoided as files on the desktop are easy to delete by mistake.
When a new version of the software becomes available, the user needs to remove the existing version (via the add/remove programs feature in Windows) before they can install the new version. This uninstall process removes all the files which initially came with the install. This INCLUDES the original Well_Seeker_DB.mdb database. Although Innova recommends that users create their own database when they first start using the software some users prefer to work in the default. In this situation it is ESSENTIAL that the user backs this database up before they uninstall the software as this database will be DELETED during the uninstall process.
Well seeker database files have a .mdb file extension. When a database is being accessed by Well Seeker an additional .ldb file is temporarily created. This is a very small file which, disappears when the database is not being accessed i.e. Well Seeker is using a different database, or when Well Seeker is closed.
When backing up the current database following Section 2.2 instructions, the user should be careful not to copy the .ldb file instead of the .mdb as this does not contain any data. To avoid making this mistake, it is safer to ensure that the .ldb file is not present, and Well Seeker being closed ensures this.
A guide to some issues associated with ipm files taken from Compass.
The Well Seeker Install includes a range of Instrument Performance Models (IPM) which have been created in line with the most up to date ISCWSA guidelines. In addition to these IPM files, Well Seeker is also able to utilize IPM files taken from Compass. These IPM files can be added manually, or they can be pulled in automatically as part of the Compass import process.
Care should be taken when assigning imported Compass IPM files. If assigned IPM files are giving unexpected results, then the user should check the below points.
In the IPM Co-efficients, there is a Vector and Tie-On entry for each row. An entry of “n” means that the associated error term is used as an intermediate calculation step in the error model calculation.
One of the issues seen with imported IPM files is that the tie-on column is marked as “n”, but the vector column is not. This can be seen in the below left screen shot, which is incorrect and incompatible with the ISCWSA standards.
If experiencing issues, check that any terms marked as “n” in the tie-on column are also marked as “n” in the vector column. The below right screen shot is correct.
The first column of the IPM file contains the name of the error term and the second contains the vector. Well Seeker (and the ISCWSA) requires the error term name to be unique for a given vector. If there are duplicate names with the same vector, the IPM can give unexpected results.
As an example, in the below left, the cgsys terms are duplicated as they all have the same name and vector. To address this issue, these terms must be renamed so they are unique (below right) and any other terms which use them must also be renamed. Note, in the below right that the vector was also changed from “a” to “n”, in line with the Vector Tie-On issue detailed above.
For some error terms, the weighting function may reference another error term in the formula. In the below, the term cgransq3 uses the term stiltavg.
In a situation like the above, any term which is referenced in the weighting function of another term, must come above it in the error file. The above example is correct, but if the stiltavg term was below the cgransq3 term, you would get unexpected results.
Some MWD IPM files have two values entered for the term drfr. These two entries have different numbers (usually 2.2 and 0.35) in the “Value” column. The term with the magnitude 0.35 is correct and the other term must be deleted.
This guide introduces the user to Well Seeker Pro from the point they first open the software after installation.
The purpose of this document is to take the user through some of the steps required to set up the program and get to the stage where they can create a plan and survey.
This document assumes that Well Seeker Pro has already been installed (see Manual for Install guide) and this is the first time the program has been opened.
When you first open Well Seeker, the screen will be configured as below.
The layout of the screen can be adjusted by going to View - Toolbars and Docking Windows:
The user can then choose what to display. For the rest of this document, the Output and Properties windows will be unselected.
The database is the .mdb file that Well Seeker Pro is directed to access information from. It is vitally important that the user is aware of the location of and backs up their database file regularly to another storage device. If this is done correctly then the user will always have a backup in the event of an unforeseen event such as a computer hard drive failure, that would have otherwise resulted in the loss of the database file and all the input data. The database can be quickly backed up by going to File > Backup Database.
The first thing to do when creating a new database is to select where you want to store the database on your computer. Ideally you want to put it somewhere where it will not need to be moved.
Create a folder somewhere in the C: drive and name it appropriately.
Go to File > Create New Database.
The box below will appear.
Navigate to the desired location where you will save the new database and enter your database name in the File Name: box and click Save.
The new database will now have been created as a .mdb file at your chosen destination.
Go to File > Select Database, browse to and select the database you have just created.
You have now created a new database and your screen should look like above, note that the database you have selected will be displayed at the bottom of the screen as highlighted by the red box.
You can navigate to the file location of your database by opening the Help menu and selecting Open database location. To backup your database file open the File menu and select Backup Database. This will open a dialog box where you can choose a suitable location and name for the backup.
It is very straightforward to switch between databases, making it easy to maintain multiple databases depending on the user's needs.
Go to File - Select Database.
Go to the location of the database you would like to use.
Select the database and hit open.
The new database will now be selected and can be used.
The following section details the steps to follow in order to create a new well.
The first thing to do is to make sure that you have the correct units selected.
Click on the Units icon located in the bar at the top of the screen or open the Tools menu and select Unit Sets.
This will open the Unit Sets dialog box
Well Seeker comes as standard with 5 unit sets (API, CAD, ND, SI & US), which are all editable.
There is also the option to create a new unit set using the Create new button. To edit a new unit set, click the Edit button. This will allow the user to access the unit drop down menus to change the parameters to the desired units.
Depth: Current units for measured depth and TVD. Options are Feet, US Feet and Meters.
Local: Current units for NS, EW and centre to centre distances. Options are Feet, US Feet and Meters.
Geographic: Defines what units the map co-ordinates are displayed in. Options are CRS Default (the unit set defined by the selected CRS), Feet, US Feet and Meters.
Diameter: This defines the units used to display Casing OD and ID as well as hole size. Options are mm and inches.
Dogleg: The current units DLS, BR and TR are displayed in. Options are Deg/100ft (or 30m), Deg/30ft (or 10m) or user defined. If user defined is selected, the parameter column becomes active and the units value becomes degrees per unit length based on the parameter entered.
Survey Calculation Method: This defines which calculation method is used for calculating survey parameters throughout Well Seeker PRO. Options are Minimum Curvature, Radius of Curvature, Tangential and Balanced Tangential. It should be noted that if a method other than minimum curvature is selected the Well Planning tools will not work.
Flow Rate: Current units for flow rate. User can choose between LPM and GPM.
Pressure: Current units for Pressure. User can choose between Bar and psi
Volume: Current units for Volume. User can choose between BBLS and m3
Mud: Current units for Mud Weight. User can choose between PPG, SG, psi/ft3 and lbs/ft3
Weight: Current units for Weight. User can choose between klbs and Tons
Torque: Current units for Torque. User can choose between kftlb and kNm
Temperature: Current units for Temperature. User can choose between degC and degF.
Cost: Current units for Cost. User can choose between $, EUR and GBP.
Jets: Current units for Jet size. User can choose between in2 and mm2.
Whatever is selected here will be applied to the whole database. It can be changed at any point, but the units are set for the whole database and not individual operators or wells.
Special care must be taken at this point because the survey calculation method affects the way the plans and surveys are generated. It is very unlikely that anything other than Minimum Curvature will ever be selected.
It is possible to create an instant plan or survey in Well Seeker. This can allow the user quick access to the planning tools without having to go through the process of filling in all the different levels of data to get there. For this kind of requirement, surface locations, elevations etc are of no concern and Well Seeker uses generic values at all the levels.
To create an instant plan or survey, right click on the database and select New Instant Plan or New Instant Survey.
Right click on the database and select Insert New Operator.
The Operator Properties box will now appear.
The Operator level is where the user sets up the company anti-collision policy, and it is very important to ensure this is done correctly.
This is also the level where the primary and secondary logos are added. These logos are then available to be included on generated reports.
Right click on the Operator and select Insert New Field.
The Field Properties box will now appear.
The following data is input at this level:
Mapping Grid or Coordinate Reference System (CRS). If the required CRS is not available a new one can be added (see the Adding a New Coordinate Reference System section).
Azimuth North Reference: Grid or True.
Local Coordinate system:
Well Centred - Local coordinates for all plans & surveys will be referenced to the well location making all local coordinates 0.00N & 0.00E at surface.
Facility Centred - Local coordinates for all plans & Surveys will be referenced to the facility location meaning local coordinates at surface will vary between wells.
Apply Scale Factor: If this option is selected, the scale factor defined in the CRS will be used to calculate map co-ordinates from local co-ordinates. This is the ratio between measured distances on the map compared to measured distances on the ground as a result of distortion of linear scale associated with mapping a spherical surface (the earth) onto a plane. Note that this option does not affect the local coordinates, only the map coordinates (Northing and Easting’s).
Show Map: This extends the existing dialog to include a Google Maps section. This will show the location of the positional data entered and can be toggled between map and satellite view using the Satellite checkbox. The map can also be zoomed in and out using the – and + buttons. This map location will only be accurate if the CRS selected uses WGS 84, as this is what Google Maps utilises.
Show Field Ref Point on Report: When selected, the field reference point coordinates will be included in the Field data box of any report generated. Default is off.
Field Reference Point: This is the reference location used for the field.
Input: Select the coordinates used to enter the Field Reference Point. Either Latitude & Longitude or Grid Easting & Northing.
Grid Convergence is not editable as it is based on the CRS selected and the Field Reference Point entered.
System Vertical Datum: This is the datum which all TVDs below field level will be referenced to. This is usually either mean sea level “MSL”, lowest astronomical tide “LAT” or some other user specified value. If a value other than MSL is selected from the combo box, the elevation above or below MSL must be entered. A positive value indicates that the datum is above mean sea level and a negative value indicates it is below it.
Once the required inputs have been completed, click Apply then Close on the bottom right of the window. To access the Field Properties again at any time, right click at the Field level and select properties
Right click on the Field and select Insert New Facility
The Facility Properties box will now appear
The following data is input at this level:
A slot template can be created by Clicking on the Templates button (see Creating a Slot Template section for more detailed instructions)
Lease /Hard Lines: The user can select to have lease / hard lines show at all levels within the Targets dialog. On will pre-select the lease / hard lines to be displayed from Field to Actual / Plan levels. Off will pre-select the lease / hard lines to be displayed from Field to Facility level only.
Show Map: This extends the existing dialog to include a Google Maps section. This will show the location of the positional data entered and can be toggled between map and satellite view using the Satellite checkbox. The map can also be zoomed in and out using the – and + buttons. This map location will only be accurate if the CRS selected uses WGS 84, as this is what Google Maps utilises.
Facility Reference Point: This is the reference location used for the facility. For an offshore platform, this is usually platform centre and for an onshore facility, this is usually the centre of the site. This location will provide the Local Coordinates of 0.00N & 0.00E if Facility Centred Local Coordinate System was selected in the level above
Input: Facility Reference Point Select the units used to enter the Facility Reference Point. Either Latitude & Longitude or Grid Easting & Northing.
Grid Convergence is not editable as it is based on the CRS selected and the Facility Reference Point entered.
Facility Location Uncertainty: The uncertainty of the facility location to 1 sigma. If unknown, leave as 0.
Once the required inputs have been completed, click Apply then Close on the bottom right of the window. To access the Facility Properties again at any time, right click at the Facility level and select properties.
Right click on the Facility and select Insert New Well
The Well Properties box will now appear
The following data is input at this level:
Location Uncertainty: The uncertainty of the Wellhead location to 1 sigma. If unknown, leave as 0.
Wellhead Location:
Slot: This allows the user to select any of the slots created in the template editor and the location will be automatically input based on this selection
Offset from Facility: This is the local Coordinates which allows the user to enter the distances at surface between the facility location and the wellhead location
Map: Input location as Grid Easting & Northing
Geographic: Input location as Latitude & Longitude
Depth Reference: Allows the user to input the relevant elevations. Default is for an onshore well with Ground Level to MSL, however If “offshore” is selected, the user can enter the well head elevation above MSL. If “subsea” is selected, the elevation below MSL can be entered. This is the distance between the top of the well head and MSL. By checking the Default box, the selected elevation will be automatically assigned to any new plans or surveys created.
Show Map: This extends the existing dialog to include a Google Maps section. This will show the location of the positional data entered and can be toggled between map and satellite view using the Satellite checkbox. The map can also be zoomed in and out using the – and + buttons. This map location will only be accurate if the CRS selected uses WGS 84, as this is what Google Maps utilises.
Once the required inputs have been completed, click Apply then Close on the bottom right of the window. To access the Well Properties again at any time, right click at the well level and select properties.
Right click on the Well and select Insert Planned Well
The Plan Properties box will now appear
The following data is input at this level:
Set as Principal Plan: Selecting a plan as the principal sets it apart from the other plans as the most important one, and it also tells Well Seeker to use it as the reference plan when the user is in a survey file under the same well. When inputting surveys, Well Seeker will display details telling the user how far away, Toolface, X & Y offset etc the survey is from the principal plan.
Tolerance Circles: Tolerance circles are for visual reference only. The radius of the inner and outer tolerance circles can be added here. These can be displayed in a plan or spider plot by selecting their inclusion in the chart properties dialog. The default colours for the inner and outer tolerance circles can be adjust in the Plots>Chart Defaults menu.
Survey Tools: The Survey tool editor can be accessed from here by clicking on the Survey Tools button located beside the Apply button.
Vertical Section: The VS azimuth and the local origin of the VS.
Depth Reference: This will be the selected default (from Well Level), but can be changed by selecting options from the drop down list.
Magnetics: Magnetic data can be generated here by selecting the model and the date. If the relevant model is not available, user defined details can be added. Several lines can be added to the magnetics table; however, only the data which is checked as Active will be used by the program.
Survey Program: This is where you create the survey program and assign the relevant error models to the plan. At this stage, because there is no plan yet this will remain incomplete (to be completed once a plan has been created). Error model can be assigned at this point by selecting from the drop down menu below IPM. However, if the plan is a sidetrack, then the details of the survey program from surface to ST depth can be entered. This will be done automatically when completing the Sidetrack details section.
Sidetrack Details: If plan is a ST, check the Plan is a sidetrack box and the user will be able to select the plan or survey that will act as the motherbore as well as determining the ST depth. By then selecting Create Sidetrack, the Survey program will be populated with the relevant details from the motherbore.
Tie-on: Allows the user to select where the plan is tied on. This can be from surface, a user defined point where the tie-on line can be manually typed in by the user or from an existing survey or a plan. This will be automatically populated when the Sidetrack Details section is completed.
Export Geomag Data: Exports the geomagnetics data as a document. Select the line in the Magnetics section that you want to export the geomagnetics data for. Then select the report format as PDF or Excel from the drop down menu, before selecting Export to generate the report.
Force Colour: Selecting this option and choosing a colour will ensure that this plan will always be displayed in this colour in all of the plots. This supersedes any colour options for this plan in the Chart Properties dialog.
Once the required inputs have been completed, hit apply then close
To access the Plan Properties again at any time, right click at the Plan level and select properties
The database tree should now look similar to the one below. In order to open the plan, the user must double click the Plan level of the database tree, and the plan window will open in the right hand screen. The plan can then be entered manually using MD, Inc and Azi, or the Planning Tools at the bottom of the screen. Once a plan has been created click Save. For more details on the Planning Tools, see Appendix A.
When you hit save for the first time, and again any time the plan is changed, the user is asked "Do you wish to add this plan to survey program". Select Yes. This will automatically update the survey program.
To check & edit the survey program, or assign an error model, open the Plan Properties. Left clicking on the Plan/survey column will reveal a drop-down menu with the available options. An appropriate error model can be selected from the drop-down list in the IPM column.
Click Apply and then close to save this selection.
To view the plan listed every 30m (100ft), double click on the Planned Wellbore level of the database tree and it will open this in the right-hand window.
When you have a plan selected, it is possible to choose what data you would like to be displayed by going to:
View - Show / Hide Columns
The user can choose which columns to be displayed. It is worth noting that the following columns will only be displayed for a survey (not a plan) even though they are selected, and will only be populated if one of the plans is selected as Principal:
Distance to Plan
TFO+Azi
TFO Highside
TC X&TC Y.
Up Down & Left Right
Closure Azimuth - can always be displayed in a survey regardless of whether there is a principal plan selected. It will not display in a plan.
The Targets properties box can be accessed from field level down by right clicking on the required level (Field, Facility, Well, Plan or Actual Well) and selecting Targets.
Select Create New and the Target Properties section will become editable.
Target shape, size and orientation can be selected by clicking on the desired tab at the centre right of the screen as seen highlighted by the red box in the above image.
If supplied with an azimuth and a horizontal displacement, target coordinates can be calculated by adding these values and selecting calculate. All target centre coordinates will be populated.
Drillers target can be calculated by selecting the desired confidence level (95% is the default) and selecting Create Drillers Target:
You will then be prompted to select the relevant plan before the calculation is done.
If the planned well path does not pass through the target, the calculation will not be carried out.
The size of the drillers target is affected by the Survey tool which is assigned to the plan - The more accurate the tool, the larger the drillers target.
The level that a target is created on will be displayed in the filter section. A target created at the Field level will only be seen at that level. A target created at plan level can be seen at all levels.
To see a target created at field level at plan level:
Open the target properties box at plan level - you will not be able to see the target.
Click on the Filter drop down menu and select Field.
You will now be able to choose which levels the target will be visible on. Just check the required box and click Save.
Lease lines and hard lines can be created by adding a target and selecting Polygon. The lease / hard line coordinates can then be entered in the same way as a polygon target. Once complete, the user should check the “Is a Lease Line” or “Is a Hard Line” box.
It is important to understand that once this has been checked, Well Seeker will see this as a lease line and not a target. The next time the user opens the target box, the lease / hard line will no longer be visible. To see the lease / hard lines, the user can select the “Show Lease Lines” option below the filter. This filter will hide the targets and display only the lease lines.
NOTE: Both targets and lease / hard lines will be available to plot and can be manipulated in a similar way in the chart properties dialog in the plots.
Casings can only be added at Actual Well and Plan level:
Right click on either and select Casing, and the casing details will appear.
The user can now fill in the required information.
Lithology details can only be added at Actual Well and Plan level:
Right click on either and select Lithologies, and the Lithologies box will appear.
The user can now fill in the required information.
Annotations can only be added at Actual Well and Plan level:
Right click on either and select Annotations, and the Annotations details will appear.
The user can now fill in the required information.
Right click on the Well and select Insert new actual well.
The Actual Wellbore Properties box will now appear.
The initial set up of the Actual Wellbore is the same as for a plan. Refer to Creating a New Well Plan Section.
Once the required inputs have been completed, click Apply then Close.
To access the Actual wellbore Properties again at any time, right click at the Actual Well level and select properties.
Right click on the Actual Well and select Insert new survey
The Survey Properties box will now appear
The user can select the appropriate Survey tool and select a tie-on.
Once the required inputs have been completed, click Apply then Close.
To access the Survey Properties again at any time, right click on the survey and select properties.
To enter the survey and add survey stations, double click on the survey you wish to add to, and the survey will open in the right-hand window.
A prompt will appear which asks, "Do you wish to add this survey to the survey program?". Select Yes.
Once a survey has been created and saved, the next step is to go back to the Actual Wellbore Properties and check the Survey program. Clicking on the Survey column will reveal a drop down menu with the available options. Any surveys which have been created below the Actual Wellbore will be available to select. Since a survey tool has already been assigned to each individual survey the IPM column will be automatically populated.
Click Apply and then Close to save this selection.
Once a survey has been added to the survey program, if new survey stations are added to the survey, on saving, Well Seeker will again prompt the user Do you wish to add new surveys to the survey program? Selecting yes will update the survey program Depth To column to include the latest surveys.
The Actual Wellbore is where the user can view the survey program listing.
Double clicking on the Actual Wellbore displays an un-editable listing which contains all the surveys assigned to the survey program
It is possible to import a Compass .xml file into Well Seeker. This file is an export file from Compass which contains details of plans, surveys, targets, error models etc. When this file is imported, all the information will be used to create the relevant wells within Well Seeker.
To import a Compass .xml file, select File > Import Compass EDM File. This will then open a screen which will allow the user to navigate to the relevant file and select it.
Once selected, Well Seeker will begin the import process. The time taken for this process will vary based on the size of the import.
Compass Import Settings: This option opens the compass import settings dialog, where the user can select the appropriate settings they desire when importing data from a Compass EDM file.
Targets and Lease Lines: Allows the user to either include or omit targets and lease lines when importing. The user can also choose if imported lease lines are automatically assigned to their appropriate wells.
Surveys Tools: When checked, Well Seeker will import any survey tools associated with the relevant plans and surveys. If unchecked no survey tools will be imported. Note, that if survey tools are not imported, and any of the imported plans and surveys reference a survey tool which is not available on the imported computer, then Well Seeker will use the default error model selected by the user.
Naming Conventions: Gives the user 3 options relating to the way Well Seeker names the imported data in the database tree. If all boxes in this section are unchecked, the data will just be pulled in as it is in the Compass export file.
Note: Well Seeker requires all items in the database tree (except for surveys) to have unique names, whilst Compass does not. Importing two items from Compass with the same name will cause a conflict in Well Seeker. For this reason, Innova recommend that these Naming Conventions should be turned on by default.
Append Operator Name to Field: Adds the relevant Operator name to the end of every Field name in the database.
Append Field Name to Facility: Adds the relevant Field name to the end of every Facility name in the database.
Append Facility Name to Well: Adds the relevant Facility name to the end of every Well name in the database.
Well Plans: This option allows the user to import ALL plans which are contained within a Compass Export file. If this option is not selected, then Well Seeker will only pull in the plans which are selected as PRINCIPAL in the export file. Default is ON.
At Facility level, it is possible to add a slot template. When in the Facility Properties window, select Templates, and the Template Editor window will pop up.
Properties: Select Create New to create a new template:
Select Template: This will populate automatically once the Name box has been completed and the template has been saved.
Name: Add the relevant name.
Slot Prefix: This will appear in front of all slot names.
Template Centre Relative to facility: This is only available when Rectangle or Circle is selected in Geometry. Allows the user to offset the centre of the template relative to the facility location entered in the Facility Properties window.
Geometry: Select from Rectangle, Circle or Single Slot. Single slot allows the user to create a slot template that is not a predefined shape and is made up of individually entered slots.
Rectangle: Contains available options related to the Rectangle Geometry and will only be editable when the Rectangle option is selected.
Circle: Contains available options related to the Circle Geometry and will only be editable when the Circle option is selected.
Convert to Single Slots: This option allows the user to convert rectangle and circle templates into single slots. This action is not reversible once it is selected.
Display slot names: Displays the names of the slots on the plan view on the right.
Slots: This is where the slot Name and local coordinates are input. The local coordinates are generated automatically for the Rectangle and Circle Geometry and are fully editable for the Single Slot option.
When a slot template has been created select apply to save
When more than one template has been created, the relevant template can be selected from the Select Template drop down menu at the top of the screen.
You may find yourself in a situation where you are required to do planning referencing a CRS which is not available in Well Seeker. In this situation the information relating to the CRS should be requested from the client and can then be used to create a new CRS in Well Seeker.
The below screen shot is an example of the type of information which will be supplied by the client.
The following instructions detail how to use this information to create a new CRS.
Open the Geomagnetic Calculator by clicking on the icon on the toolbar or go Tools > Geomag Calculator.
Click on the "Mapping Grid" button at the top left of the box.
Select Add CRS at the bottom left of the Mapping Grid.
You will now have a blank template which you can start adding information to.
Parameters in RED below are important and affect the output - Care should be taken to enter the data correctly
Name: This can be anything you want as it has no impact on any of the calculations. In Well Seeker, the naming convention is the System / and then the Map Projection, and it is recommended that this convention is followed. For this example, the name would therefore be Polska 1992 / Transverse Mercator (Gauss-Kruger) Zone 3
Area of use: Description of which part of the earth this CRS references and has no effect on any of the calculations. For this example all we know is it is in Poland.
Datum: This is just text and does not directly affect any calculations. For this example it is WGS1984.
System: This is just text and does not directly affect any calculations. Polska 1992
Ellipsoid: This is an important one and you have to choose from a drop down list of 38 options. In this example you would choose WGS 84
Semi Major Axis (m): This is the Equatorial Radius of the Ellipsoid and is automatically populated based on the ellipsoid selected.
Semi Major Axis (UOM): This is the equatorial radius of the ellipsoid in the units of measure which the CRS is using and is automatically populated based on the ellipsoid selected.
Units of Measure: This is a drop-down menu option and you can choose from 7 options. For this example, it would be metre
1/f: This is the inverse Flattening of the Ellipsoid and is automatically populated based on the ellipsoid selected.
Map Projection: This is just text and does not directly affect any calculations - Transverse Mercator (Gauss-Kruger) Zone 3
Projection Type: This is a drop-down menu and you can choose from 4 options – TM, 1SP (Standard Parallel), 2SP or STEREO. In this example, choose TM.
False Easting: 500000.00 m.
False Northing: -5300000.00 m.
Latitude of Origin: This should be input as a decimal - 0.0000 deg.
Longitude of Origin: This should be input as a decimal - 19.0000 deg.
Scale Factor: Ratio between measured distance on the map and on the ground - 0.99930 deg.
1st Standard Parallel: This information will be required if you select 1 SP or 2 SP from the Projection Type Drop down menu - Not applicable here
2nd Standard Parallel: This information will be required if you select 2 SP from the Projection Type Drop down menu - Not applicable here
The Screen shot below is what your new CRS should look like based on the information detailed above:
Select Save CRS and your new CRS will be available to select from the mapping grid dropdown menu.
In addition to the individual Plan View, Section View and 3D View plots, Well Seeker also has a Wall Plot Composer (WPC), where different plots along with data tables can be displayed and then output together.
As with the individual plots, the WPC option only becomes available when the user is in a plan, survey, planned wellbore or actual wellbore.
The first thing to do in the WPC is to ensure that the page is setup as required. The default page layout will be A4 Portrait view. To change this, select File > Page Setup. The user can then choose sizes ranging from A0 to A7 or User Defined.
The user can then start to build the wall plot by inserting the desired Charts and Tables. This can be done by selecting Insert from the top menu or by right clicking anywhere on the plot.
Certain Charts and Tables can also be inserted from the tool bar along the top of the screen.
The offset selector in the WPC works in the same way as it does on the main Well Seeker menu. It is however completely independent, which means that offset wells selected in the main menu will have to be reselected when in the WPC.
Once a plot has been inserted into the WPC, the user can then open the Chart Properties by selecting a chart and either using the menu, Tools > Chart Properties, or the Chart Properties icon. This is where most of the chart functionality is located, and allows the user to add labels, change colours and customise the plot.
Once a plot has been inserted the user can then manipulate the size of the plot and position it appropriately on the screen. Dragging the plot to increase or decrease its size affects the scale. Once the user is happy with the size of the plot and its position, they can then select the appropriate scale and zoom in if required. Once the scale has been fixed the physical size of the chart will also be fixed and the user will no longer be able to grab the corners and drag to manipulate the chart size.
To zoom in, all the user needs to do is Left click and drag across the relevant portion of the plot. This will change the max and min axis values along with the scale. To Undo a zoom, right click on the plot and select Undo Zoom from the list of options, or alternatively press the z key.
Any time the plot box size is changed, or the user Zooms in, the Chart Grid section in the Chart Properties updates to match. In the below left, the plot was zoomed to show the point of interest. The chart scales are greyed out but match the plot. The plot was then manipulated (below right) using the chart scales option to fine tune the output.
It is important to note that any selection made in the Chart Grid section will be overwritten if the user changes the physical size of the plot or zooms in or out. When the user goes back into the Chart Properties after doing either of these things, the check boxes will have been unchecked and the greyed-out values will represent what is currently being seen on the plot.
Grid Lines can be added and manipulated from the Chart Properties. The user can also select the distance between major and minor tick marks on the plot. When a chart is first opened, the default is Auto and the boxes are greyed out and empty. To manually select these values the user needs to uncheck the Auto box, and they will then be able to adjust the line spacing as required. The grid line colour can also be selected from here.
In the File option at the top left of the WPC screen, the user can select to Save or Open an existing wall plot composer template. These templates are saved as .wpc files and allow the user to save the template they are working on and come back to it at a later date.
When a table is inserted into the WPC, it will be a fixed size. Like the plots, manipulating the border changes the size of the table. If the table has been stretched out of shape then the Reset Table Aspect Ratio button can be selected from the toolbar. This will keep the width of the table as the user set and alters the height of the table to set the table to the correct aspect ratio.
The Logo size can also be manipulated in the same way. However, the logo aspect ratio is reset using the Reset Logo Aspect Ratio button
The initial logo input will be the primary logo selected at Operator Properties in the database tree. Once input this image can then be changed to any image, so long as the image is a .bmp file. Insert the logo, then right click on the logo and select Select Image. The user can then select any .bmp file for inclusion in the wall plot.
The last four options on the toolbar are the alignment tools, which allow the user to line up the edges of items in the wall plot for neater presentation. The available options are left, right, top and bottom alignment. Select an item, click on one of the alignment tools and then click on another item. The first item will move so that its edge lines up with the second item.
It is possible to adjust the screen zoom. This option allows the user to zoom in, to look more closely at a particular section of the plot, or to zoom out to look at the whole plot. This feature can be accessed via the View menu.
This option is also available on the quick access toolbar along the top of the WPC screen.
It is possible to select plot defaults, which will be applied each time a plot is opened. These default selections are available on the main Well Seeker interface when a plan, survey or actual wellbore is open.
Select Plots from the toolbar along the top of the screen and the Chart Defaults options are available in the list. The selected defaults apply to the individual plots as well as the plots created in the WPC.
When viewing a plan, the well planning tools will be displayed at the bottom of the window.
Selecting one of the seven planning tools displayed will activate other options to configure the chosen tool. Once all options have been entered, click on the calculate button to add it to the well plan. Below is a description of each available planning tool:
The adjust planning method is a simple tool that will draw a curve with the minimum dogleg required to reach the desired inclination, azimuth and distance from the current point. The exception to this is the INC, AZI, DLS option – In this case the planning tool will calculate the build/turn values required to reach the desired inclination and azimuth while keeping to the desired dogleg.
MD, INC, AZI: Enter a MD, an INC and AZI in the text boxes in the parameters section.
CL, INC, AZI: Enter a CL, an INC and AZI in the text boxes in the parameters section.
INC, AZI, TVD: Enter an INC, an AZI and a TVD in the text boxes in the parameters section.
INC, AZI, DLS: Enter an INC, an AZI and a DLS in the text boxes in the parameters section.
The build / turn planning method is a 3D planning tool in which consecutive surveys have a constant build / turn rate between them. The well path produced by this method is effectively describing a trajectory travelling around a cylinder.
MD / CL: Enter an MD or CL, build rate and a turn rate and click on the “Calculate” button.
INC: Enter a build rate and a turn rate and an INC and click on the “Calculate” button.
AZI: Enter a build rate and a turn rate and an AZI and click on the “Calculate” button.
TVD: Enter a build rate and a turn rate and a TVD and click on the “Calculate” button.
The dogleg tool face method is a 3D planning tool where build rates and turn rates will vary between survey stations depending on the dogleg and tool face setting requested.
MD / CL: Enter an MD / CL, DLS and TFO and click on the “Calculate” button.
INC: Enter a DLS, TFO and an INC and click on the “Calculate” button. The trajectory will be calculated until the required INC is reached. If the INC selected cannot be reached, an error will be displayed.
AZI: Enter a DLS, TFO and an AZI and click on the “Calculate” button. The trajectory will be calculated until the required AZI is reached. If the required AZI cannot be reached, an error will be displayed.
TVD: Enter a DLS, TFO and a TVD and click on the “Calculate” button. If the TVD cannot be reached, an error will be displayed.
TANGENT: There are two methods available for the tangent option:
Tangent – HC (Hold Curve): The HC option draws a tangent section then a curve to hit the target
Tangent – CH (Curve Hold): The Curve Hold draws a curve to line up on the target then a tangent to hit the target
The Curve Hold method allows a larger number of targets to be reached. A NS, EW and TVD value must be entered. This can be done manually or by selecting an existing target. Lastly the DLS of the curve must be selected. If the target cannot be reached with the parameters specified, an error will be displayed. Usually increasing the DLS allows the target to be reached or changing the method from hold curve to curve hold.
POINT: Enter a NS, EW and TVD; this can also be done by selecting an existing target from the drop-down menu. The well trajectory will be turned using the minimum possible dogleg to reach the point. This method describes a constant curve to the target. If the required point is on an existing plan, this can be achieved by selecting plan from the target details section, choosing the relevant plan from the drop-down menu and selecting the appropriate MD. This MD relates to the point on the offset plan and Well Seeker will automatically populate the NS, EW and TVD based on this selected point.
The Hold function causes the trajectory to travel in a straight line at the current inclination & azimuth until at reaches the specified distance or depth:
CL: Enter a CL (Closure Length) and click on the “Calculate” button.
MD: Enter an MD and click on the “Calculate” button.
TVD: Enter a TVD and click on the “Calculate” button.
VS: Enter a Vertical Section and click on the “Calculate” button
The optimum align function is a powerful tool for lining up on targets at specified inclinations and azimuths. It is particularly useful if multiple targets are to be hit. The trajectory produced is usually a 3D S-shape profile, which can be defined either by specifying two curve sections and a hold or by using two curves. If “Curve Hold Curve” is used, the doglegs for both the curve sections must be specified. For a “Curve-Curve” method, only the dogleg for one of the curves must be entered. If “Balanced” is selected, Well Seeker PRO will attempt to create a profile using the same dogleg for both curves.
When selecting a point to hit, the user can choose any available targets from the drop-down menu or enter the N/S, E/W and TVD values manually using the user defined option. Then select the appropriate optimum align parameters and required dogleg, and enter the desired inc and azi and click on the “Calculate” button
If there are 2 targets and the user requires the plan to “line up” the first target with the second, the second target can be selected from the line up drop-down menu. Well Seeker will calculate the tangent inc and azi between the 2 targets and automatically enter these values into the relevant boxes.
It is also possible to line up on an existing plan. When Plan is selected, the user can choose the relevant plan from the drop-down menu and the relevant MD on the plan that they would like to hit. The coordinates and TVD of the point on the plan will be automatically entered and the inc and azi will mirror that particular point on the well plan.
If the optimum align method cannot reach the desired inc and azi at the target point, an error message will be displayed. Usually increasing the doglegs will allow the target to be reached.
If the user has multiple targets to hit, then one way to achieve this is by selecting the “Thread” function in the target details section. No planning method needs to be selected to open the Thread targets dialog; however, the feature utilises the Optimum Align functions when generating plans. Targets are available to select via a drop down menu at the top of the dialog, and the planning method options are selected at the bottom of the dialog.
The 2D well planning tools are designed to allow a well from surface to be planned with a single click. The 2D planning tools have multiple build /drop rates but only one horizontal plane (azimuth). There are two options available: S-Well and Slant Well. The S-Well profile can either be a standard S where the inclination is dropped back to vertical at the target, or a modified S where a specified inclination greater than zero is reached at the target. The slant well has a constant build up rate and a specified kick off point to reach the target.
To use this method, the KOP must be entered (the inclination will be vertical to this point), the DLS of the initial build (BUR 1) and then the drop rate (BUR 2).
The user then has two additional options to choose from, final inclination (Fin Inc) and final hold length (Fin Hold). The user can choose to select none, one or both of these options via the checkbox to the right of the corresponding cell. The final details required are the target NS, EW and TVD. These can be entered manually or by selecting a target from the drop-down menu. If the target cannot be reached with the specified parameters, a warning message will be displayed.
No Checkboxes selected: When the user does not select either the Final Inclination or Final Hold options, the drop section of the plan will stop at the selected target at an inclination of 0° (if this is possible). This will be referenced in the Method Column of the plan as SWELL_OPT1.
Final Inclination Only: When the user enters only the final inclination, the drop section of the plan will stop at the selected target at the desired inclination (if this is possible). This will be referenced in the Method Column of the plan as SWELL_OPT2.
Final Hold Only: When the user enters only the final Hold, the plan will hit the target at 0° inclination (if possible) and will have lined up at the given hold distance entered prior to hitting the target. In the below example, the plan has lined up at 0° inclination 100m MD before hitting the target. This will be referenced in the Method Column of the plan as SWELL_OPT3.
Final Inclination & Hold: When the user enters both values, the plan will hit the target at the desired inclination (if possible) and will also include a hold section prior to hitting the target. In the below example, the plan has lined up at 5° inclination 100m MD before hitting the target. This will be referenced in the Method Column of the plan as SWELL_OPT4.
To use this method, the KOP must be entered (the inclination will be vertical to this point) and the DLS of the build (BUR 1). The final details required are the target NS, EW and TVD. These can be entered manually or by selecting a target from the drop-down menu. If the target cannot be reached with the specified parameters, an error message will be displayed.
For this feature to work, the user requires a stable internet connection and an actual well and survey already set up in the Well Seeker object explorer. For detailed steps regarding how to achieve this, refer to the .
Click on Get Wells to open the Well Selection dialog. Depending on your provider, the Well Selection dialog will look slightly different.
Click on Sync Surveys to check if any new surveys are available from your selected provider. If there are, the user will be given the option to update the survey list in Well Seeker. Click on Yes to update your survey sheet.
Click on Save to save your settings, and then click on the X in the top right of the window to close. To close without saving your settings, click on Cancel.
If the user has an API number for the well entered in the Daily Reporting section of Well Seeker, when the Get Wells button is clicked, Well Seeker will look up the API number on the Superior QC server and automatically select the correct well.
Clicking on Check Well Data will compare the latitude, longitude, magnetic field strength, dip, declination and grid convergence values stored on the Superior QC server, with the values referenced in Well Seeker. If they do not match, a warning box similar to the image below will appear.
If we have publicly released the new version, . If downloading from this page, make sure to download the version that matches with the your version that you checked in Step 1.
Run the installer file to install the new version of Well Seeker X. Follow the instructions provided by the install wizard. For more information on the install process, view this page:
Some users may experience an issue where Well Seeker X initially launches, but then immediately shuts down after displaying the splash screen pictured below. If this happens, refer to the following to resolve the issue. If the issue persists after following the instructions in the technical note, contact
Questions relating to any of the above can be sent to
This section requires the user to be familiar with the Innova Web Portal User Management feature. For details on this see the section of the Web Portal Manual.
For details of creating a new user see the section of the Web Portal Manual.
Note, for any of the Role level Data Sync settings to function, data sync must be set up correctly within the Well Seeker Settings dialog. For details on data sync setup see the document.
The following document details the recommended procedures to follow in Well Seeker Pro from pre-job, through to post-job. These procedures are designed to aid office and field personnel by providing a structured, repeatable workflow for them to follow. For a more detailed breakdown of each of the features mentioned in this guide, refer to the .
6. Select the correct Compass export file to import that includes final well plan and any offset wells not already included in the database. You may notice that your database tree contains slightly different names when imported into Well Seeker, compared to the original Compass file. This is because Well Seeker requires names in the database tree to be unique, whereas Compass does not. Well Seeker will modify names to avoid conflicts. For more information on the logic behind this process, visit this page:
10. In the Actual Wellbore Properties window that appears, input and check the actual well name, vertical section, magnetics and depth reference details. If your well is a sidetrack, refer to for a guide to tying your well onto its mother bore. After checking your inputs, click on Apply and then Close.
If you do not see any circles to select your well in the list,
The DD dashboard contains the following sections. For a detailed breakdown of these sections, refer to the :
The DD dashboard contains the following sections. For a detailed breakdown of these sections, refer to the :
9. Steps 10 - 18 detail how to perform a QA & QC check on the daily reporting in the well. Follow on the below steps. Before starting, it is recommended to back up your database by opening the File menu and selecting Backup Database.
After the rig has pushed their last update to the server, follow the below steps to QA & QC the data and verify that the well is finished. The rig may have already performed some of these steps during their End of Well procedure. Follow on quality control for the reporting data.
It is not uncommon for a user to have multiple databases which they frequently switch between. It is very easy to back up a database without even opening Well Seeker, even if it is the current database. As an alternative method to the one described in , any database can be backed up as follows:
Questions relating to any of the above can be sent to
Once the survey has been entered, hit Save
When in a chart, to select an offset survey or plan, click on the Offset Selector. This will open the select offsets box and allow the user to select the relevant plan or survey.
Once these have been selected and the dialog box has been closed, the user can then display the offsets on the plot by selecting the Offsets On / Off button.
This document answers frequently asked questions relating to Innova’s Well Planning and Engineering software.
Q1: I am getting an error message when I try to install the software?
Q2: Can I import a Compass Export file into Well Seeker Pro?
A: Yes. Simply open the Well Seeker Pro database that you wish to import the Compass Export file in to and select File > Import Compass EDM file. You can change the importing parameters by selecting File > Compass Import Settings.
Q3: I have been sent a hotfix; how do I install it?
A: If you encounter a bug with the program you will be sent a hotfix email. Normally this email will contain a link that will let you download the hotfix in the form of a .exe file.
Occasionally the hotfix will be sent as an attachment to the email. In this case the file extension will be changed to ensure that the receiving server does not strip the attached file from the email. For the hotfix to work, the recipient must change the file extension back to .exe by right-clicking on the file in windows explorer and selecting rename.
Once you have downloaded the hotfix .exe file, place it in the correct folder to activate it:
For Well Seeker Pro place the file in C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO
For Engineering update place the file in C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering
Windows will ask if you want to replace the existing file in the folder. Select yes.
Q4: My new license does not work
A: The license files for Well Seeker Pro and Innova Engineering are named WS_LICENSE.TXT and ENG_LICENSE.TXT respectively. The code within these files is different. If you get the licenses mixed up and placed in the incorrect folder, they will not work.
WS_LICENSE.TXT is placed in C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO.
ENG_LICENSE.TXT is placed in C:\Program Files (x86)\Innova Drilling and Intervention \Innova Engineering.
Only one license.txt file should be placed in the above folders at any one time. If you are renewing an old license, please delete the old license.txt file and replace with the new license.txt file. You must also ensure that the file name is not changed. If the file has been renamed, even if it is in the correct folder, it will not work.
Q5.0: I am trying to add my new license to the relevant folder, but I am being told I can’t add it here because I don’t have administrative rights.
A: If you are working on a company computer it is quite possible that you do not have the required permission to add files to this directory. Check with your IT department, who will be able to give you access.
Q5.1: I do have administrative rights on my computer, but I am still being told I can’t add the license file
A: Most computers will not let the user add files to this directory directly from an email, even if the user has administrative rights. The best way to avoid this is to save the license file to the desktop and add it to the folder from there. If this does not work restart your computer and try again. If none of these things work contact support.
Q6.0: My error outputs are not matching those from Compass
A: To compare generated errors, the set up in both programs must be identical. The following points detail where potential differences may lie.
Do you have the same Magnetic data assigned to each program (Dip / Btotal / Dec)?
Is the Wellbore set up in exactly the same way – Is the plan the same, or are the surveys entered in exactly the same way?
Do you have the same error models assigned over the same range?
Are the error models used in each program identical? It is worth noting that the ipm files used in Well Seeker are compatible with Compass.
If the answer to all of the above points are yes, and the errors are still not tying in, then the easiest thing to do is supply Innova with a Compass Diagnostic file, which will contain ALL of the information required to investigate the issue. Instructions regarding where to find this file are detailed below.
To generate a Compass Diagnostic File, follow the below instructions:
When in Compass, open the Survey tools box and check the “Diagnostics” box
Open the relevant well, and then run an error ellipse report – Don’t worry about the report, you can just close it once it has been generated.
Make sure that your computer is set up to show hidden files – If you don’t know how to do this, it differs between operating systems, so best to google the required steps.
Go to the C drive and search for .txt files. This will take a while. Once the search is over, list the results with the newest at the top. The top file, should be the file you require and you can see the location based on the search.
The generated file will be named se1.txt – Every time you create a new file, the number will increase by one.
Q7: I imported a new Coordinate Reference System (CRS) into Well Seeker and it worked as expected. I then created a new Database, and I can’t find the new CRS.
A: When you import or create a new CRS, it gets added to the database you currently have selected and will stay within this specific database. It is however only within this one database, and if you create a new database or switch to a different database (that has not had the CRS added previously) the new CRS will not be there as an option to select. The CRS will have to be imported to be able to use it.
If a new CRS is created, you can send this to Innova and it will be added to the Master CRS file, which when installed will mean any NEW databases created will contain this CRS. NOTE, adding the new Master CRS file only affects NEW databases. For Old databases, the CRS will need to be added manually by importing it.
Q8: When creating a pdf Wall Plot from the wall plot composer, the quality is not as good as I was expecting.?
A: When creating a pdf from the WPC, ensure that the print properties of the pdf writer are set to the optimal values. Ensure that the paper size is set correctly (most will have A4 portrait as default, so will need to be adjusted if printing an A0 plot) and make sure that the output resolution is set as 600dpi.
Q9: I have just tried to open the software and have been given the following Error message?
Q10: I have just added a new update to Well Seeker and when I open the program, it can’t find my database.
A: Occasionally an update may cause Well Seeker to forget the location of the last database accessed. The database will remain unaffected, and all the user needs to do is point Well Seeker to the database location. This can easily be done by opening Well Seeker and selecting File – Select Database. Navigate to the database location and select the relevant database .mdb file. The original install database is located in the following folder: C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO; however the user can select any database they know the location of.
Q11: Where is the best place to find out information on the specifics of the software?
A: The software has detailed help files within them, which can be access via Help > Help. This will open an intuitive and informative help file, where most information can be found. Additionally, selecting Help – Open Documentation Folder, will open a folder containing all the various manuals and guides. The software manuals and guides can also be downloaded from our documentation webpage:
Q12: I have created a new database in the “C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO” folder. When searching to selecting the database through Well Seeker, I can see it in this folder, but if I physically open this folder I do not see my database?
A: It is not recommended to save a new database in this location, however if the user does save their new database to this folder, the actual physical location of the database is C:\Users\Select the appropriate user\AppData\Local\VirtualStore\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO
Q13: I have imported a Compass export file and I can’t find my targets.
A: During the import process all targets are imported and stored at Field level. To assign the relevant target to Plan level, open the targets dialogue at Actual / Plan level, and then select Field from the dropdown under the Filter. This will take you to the targets at Field level, and the relevant targets can be selected by selecting the Actual / Plan check box.
Q14: I have imported a Compass export file which contained some new ipm files. Although I am able to select and use the new ipm files within Well Seeker, they do not appear to be in the “C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO\IPM” folder.
A: These new ipm files will be located in the following location: C:\Users\ Select the appropriate user \AppData\Local\VirtualStore\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO\IPM
Q15: When I open Well Seeker, it displays the Splash Screen (pictured below) but the program then closes.
A: This issue is caused by a corrupted setup file. To solve the issue, do the following:
Navigate to the Well Seeker Pro roaming folder. By default, the address is C:\Users\YOUR USERNAME\AppData\Roaming\Well Seeker Pro. You will need to enable Hidden Items in the Windows Explorer view menu to see the AppData folder.
Delete the file setupWS.ini.
Open Well Seeker Pro. Well Seeker will generate a new setup file.
NOTE: This will reset your Well Seeker program settings to their factory defaults.
Q16: Does Well Seeker support local database files (.mdb) located on a server i.e. OneDrive, Sharepoint etc?
A: This is not supported. Local database files should be physically stored on the computer in use.
Q17: When installing Well Seeker I get an error message saying that I am missing the MFreadWrite.dll and MFplay.dll files.
A: This error is due to the user not having the Windows Media Feature Pack installed. In most cases, this is because the user is running an ‘N’ or ‘NK’ edition of windows, which does not include the Windows Media Feature Pack as standard.
To check your edition and version of Windows, do the following:
Windows 10:
Select the Start or Windows button (usually in the lower-left corner of your computer screen).
Select Settings.
Select System and then select About. The resulting screen shows the Edition and Version of Windows.
Windows 8 or Windows 8.1:
Option 1: From the desktop
Swipe in from the upper-right corner of the screen while viewing the desktop to open the menu, and then touch Settings.
Select PC Info. Under Windows edition, the Windows version is shown.
Option 2: From the Start Screen
While on the Start screen, type computer.
Right-click the computer icon. If using touch, press and hold on computer icon.
Click or tap Properties. Under Windows edition, the Windows version is shown.
Windows 7
Click the Start or Windows button (usually in the lower-left corner of your computer screen).
Right-click Computer and choose Properties from the menu. The resulting screen shows the Windows version.
If your edition of Windows ends in an ‘N’ or ‘NK’ you will need to download and manually install the Media Feature Pack which can be download from the following Microsoft support page:
NOTE: Microsoft support for Windows 7 was discontinued in January 2020 and the download link for Windows 7 has been removed from the above page.
Q18: The database tree is missing from the main Well Seeker screen and I am unable to access any of the tree data.
A: The first place to check is the View Menu – Toolbars and Docking Windows. Check to see if the Well Seeker Database Tree option is checked.
This option needs to be checked for the database tree to display. If this option is checked and the tree is still not showing on the main user interface, then follow the below instructions:
Close Well Seeker
Open Notepad
Select File - Save and save a blank .txt file to the desktop called resetLayout.txt
Note, the file must be named exactly as above with a capital L
Paste this resetLayout.txt into the following folder: C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO
Open Well Seeker. You should see the window and toolbars have all been reset to the way they were on first install, and the database tree should now be visible at the left of the screen.
Delete the resetLayout.txt file once the reset has been completed, otherwise the users Window and toolbar selection will be reset each time Well Seeker is opened.
Details the different ways the user can configure Well Seeker Pro to handle Inclination-Only MWD error models
Well Seeker Version 2.2.1.5 and later has changed the way that Well Seeker Pro manages Inclination-Only instrument performance models (IPMs). The following guidelines clarify how the user should configure Well Seeker for use with Inclination-Only IPMs:
Well Seeker will recognise a survey tool as Inclination-Only if it has the following wording in the name of their IPM file. These names are not case sensitive, but anything other than the below will not be recognised as inclination only:
INC_ONLY
INC-ONLY
Inclination Only
Inclination-Only
Inclination_Only
IPM file names can be edited by opening the Survey Tool Editor (Tools >> Survey Tool Editor) and selecting the Open IPM Folder option in the toolbar. This will open a Windows folder where the file names can be edited.
If a survey has been assigned an Inclination-Only survey tool, the following behavior will occur:
The inclination values in the survey will be used to calculate the Ellipse of Uncertainty (EOU) in the error model.
The well will be treated as if it were completely vertical. No azimuth or inclination values will be used to calculate North/South, East/West, Vertical Section, Dogleg, Build Rate or Turn Rate i.e. they will all be zero.
However, the TVD and TVD Subsea values will be calculated using the inclination values. A constant azimuth value is assumed for the purpose of the calculation.
If an Inclination-Only survey is tied onto a non-Inclination-Only only survey, or vice versa, the non-Inclination-Only surveys will plot as normal but all Inclination-Only surveys will plot as vertical.
It should be noted that when using an inclination only IPM, the difference in the calculated error ellipse for a portion of a well with a zero degree inclination, when compared to a portion of a well with a positive inclination (0.01 degrees or greater) can be very large. This is caused in a large part by the misalignment term XYM1 in the inclination only models that has a very large magnitude and is based upon the sine of the inclination.
When inputting surveys for a well that is using an inclination only IPM, ensure that the surveys are input as per the inclination only survey results. Inputting an inclination of zero, where in reality it is not, will have a huge impact on the calculated error ellipse.
Note that in versions prior to 2.2.1.5, the user had the option to toggle Inclination-Only behaviour on and off in the Survey Tool editor. This option has been removed, and Inclination-Only behaviour is now always on. If the user wishes to stop Inclination-Only behaviour in a survey, they must switch to a non-Inclination-Only survey tool, or rename their Inclination-Only IPM in a way which does not correspond with the naming convention described earlier in this document.
A guide to maintaining proper naming conventions to avoid conflicts when importing compass export files.
When populating the database tree in Well Seeker it is important to understand that at every Level from Operator down, the user must enter UNIQUE naming conventions.
For example, in the below, we have 2 operators, and the field under the first operator is called Eddy County, NM (NAD 83 – NME). As a result, we cannot name the field under Operator 2 the same, even if it is in Eddy County as well. There MUST be some difference in the naming.
This is not an issue when manually entering data into the database tree, as Well Seeker will not allow the user to type a name that already exists. They will get the bellow warning.
Things can however become complicated when pulling in Compass Export Files
Compass does not require unique naming conventions in the database tree. As a result, depending on the naming convention used in Compass, the user may end up in a situation where they are importing data which is not unique at each level in the database tree. This can lead to a conflict and data being overwritten.
The best way to avoid this potential issue is within the Naming Conventions section of the Compass Import Settings.
The Compass Import Settings are accessed via the File menu in the main Well Seeker interface (File - Compass Import Settings).
Targets and Lease Lines: Allows the user to either include or omit targets and lease lines when importing.
Coordinates: When checked, Well Seeker will use the Latitude and Longitude values referenced in the Compass export file for the wellhead. When unchecked, Well Seeker will use the Northing and Easting values.
Surveys Tools: When checked, Well Seeker will import any survey tools associated with the relevant plans and surveys. If unchecked no survey tools will be imported. Note, that if survey tools are not imported, and any of the imported plans and surveys reference a survey tool which is not available on the imported computer, then Well Seeker will use the default error model selected by the user.
Naming Conventions: Gives the user 3 options relating to the way Well Seeker names the imported data in the database tree. If all boxes in this section are unchecked, the data will just be pulled in as it is in the Compass export file.
Append Operator Name to Field: Adds the relevant Operator name to the end of every Field name in the database.
Append Field Name to Facility: Adds the relevant Field name to the end of every Facility name in the database.
Append Facility Name to Well: Adds the relevant Facility name to the end of every Well name in the database.
Well Plans: This option allows the user to import ALL plans which are contained within a Compass Export file. If this option is not selected, then Well Seeker will only pull in the plans which are selected as PRINCIPAL in the export file. Default is ON.
To avoid any conflicts and naming issues, it is recommended that when the Well Planner or Coordinator imports a Compass export file into Well Seeker, they have ALL 3 of the Naming Convention options selected, as below.
Below left is an example of a well pulled in with none of the above options selected, while below right is the same export file with all 3 options selected during import.
With these naming conventions selected during the import process, it is very unlikely that there will be a conflict. This simple step will keep everything consistent when transferring data from Compass to Well Seeker and avoid the well planner having to make any adjustments to the existing Compass naming conventions.
A setup file saves each individual users preferred settings, which are loaded each time the software is opened. The Compass Import Settings are among the settings which are included in this setup file.
To ensure consistency across the company, it is recommended that once the desired Compass Import Settings are agreed, a setup file containing these settings should be distributed to the relevant personnel. This can be done as follows:
Open Well Seeker and setup the Compass Import Settings as required.
Go to File – Export Setup File
Distribute to the required personnel
They can then import by selecting File – Import Setup File
Well Seeker Pro now has the integrated functionality to remotely send and monitor downlinks on a specified rig, utilizing the rig’s control system. Currently Well Seeker Pro can communicate with NOV’s DrillLink software and downlink by either the mud pumps, or top drive on rigs utilizing the Amphion and Cyberbase rig control systems. This document is intended to guide the user through the process of setting up Well Seeker Pro, so that it can communicate with DrillLink and send downlinks from either the rig site, or a remote location.
Security of the rig control system is of the utmost importance, as such this section will deal specifically with the security in place when using the Downlink Control system within Well Seeker Pro.
If the Well Seeker Pro laptop is present at the rig site then the security concerns are minimized hugely.
The user will need to physically connect the laptop to the rig network
The user requires the IP address and Port for the DrillLink device, or the hardware that is forwarding commands to DrillLink, whichever is applicable. These are required to be input in the Downlink Control dialog, before any communication can be made with DrillLink
The Downlink Control functionality is a license enabled feature, meaning that only users with a valid license for the feature will be able to use it
The driller at the rig site will have ultimate control as to whether the DrillLink system allows remote access or not, utilizing an override switch in the DrillLink console on the rig floor
The below system diagram depicts how Well Seeker Pro interacts with DrillLink to send downlinks from the rig site.
If the Well Seeker Pro laptop is not at the rig site then the security risks are innately higher, as this requires a way for an external source to access the rig network. These risks are negated in the following ways:
Well Seeker Pro communication from a remote location is handled solely by the Innova Remote Client. This application will only deal with communication from Well Seeker Pro via the secure ICP API (Innova Cloud Portal API)
All communication between Well Seeker Pro and the Innova Remote Client use TSL encryption (Transport Layer Security)
Access to the Innova Remote Client requires a Username and Password for successfully communication to be established. These credentials can only be supplied by Innova
Each rig will be specified by a randomly generated unique code (GUUID) from Innova, which must be known to communicate with the Innova Remote Client for a specific rig. This can only be handled when using Well Seeker Pro software
The Downlink Control functionality is a license enabled feature, meaning that only users with a valid license for the feature will be able to use it
The driller at the rig site will have ultimate control as to whether the DrillLink system allows remote access or not, utilizing an override switch in the DrillLink console on the rig floor
The below system diagram depicts how Well Seeker Pro interacts with DrillLink to send downlinks from a remote location.
The below steps lead the user through setting up and using the Downlink Control functionality and assume that the user has already created an actual well, survey and a BHA populated with data.
1. Open the survey for the well that you are drilling
2. Open the slide sheet dialog
3. Select the Send downlink icon from the toolbar, or select Tools > Send Downlink. This will open the Downlink Control dialog
4. In the Drill Link section, select the Connection as either Local connection, or Remote connection. For local connections go to step 5. For remote connections go to step 6.
5. Input the IP Address and Port for the DrillLink device, or the hardware that is forwarding commands to DrillLink, whichever is applicable. These will be acquired from the rig. The port will always be 8080. Proceed to step 8
6. Input the Username and Password credentials for the ICP API. These can be acquired from Innova, or your company focal point.
7. If using a remote connection select Get rigs. This will populate the rig listing and display the rig name and online status. Check the Select cell for the required rig. The Online status must read Yes in order to send a downlink
8. If not already connected select Connect. If successful the Connection cell will change from Disconnected to Connected
9. In order to be able to send a downlink the Switch cell must contain Enabled. If this contains Disabled then the driller at the rig must enable remote access on their DrillLink display. This gives the driller at the rig ultimate control over whether remote access to the DrillLink system for downlinking purposes is granted or not
10. Select from the dropdown list which channel corresponds to which pump and the top drive. If unsure of the channel mapping, verify with the rig. Ensure that all channels that will be used are checked as Active and that any top drive channel has RPM CH selected
11. In the Downlink Setup section, select the Tool Type from the drop down list
12. Select the Software Ver. from the drop down list if applicable
13. Depending upon the tool type and software version selection, the Rotary DL check box may, or may not be selectable. If un-selectable / unchecked then the downlink will be transmitted using the mud pumps, if selected it will be transmitted using the top drive
14. Select the Tool Mode / Tool Map from the drop down list. The naming convention changes based upon the Tool Type selection
15. Select the desired Downlink from the drop down list
16. Select the desired percentage reduction of the pump strokes, or top drive rpm from the drop down list
17. Select Preview. This will load the Downlink Sequence and the Downlink Parameters portions of the Downlink Control dialog with the relevant data for the downlink
18. Select Send to start the downlink sequence. The progress of the downlink will display on the Downlink Sequence chart at the bottom of the dialog. If WITS data is being imported to Well Seeker Pro, the blue trace will display the WITS flow or rpm values in real time
19. Leave the sequence to complete, or the downlink sequence can be aborted at any time by selecting the Abort option
20. The user can carry out further downlinks, or if finished with the downlinking for the time being, select Disconnect and close the Downlink Control dialog
Well Seeker Pro now has the integrated functionality to remotely send and monitor downlinks on a specified rig, utilizing the rig’s control system. Currently Well Seeker Pro can communicate with NOV’s DrillLink software and downlink by either the mud pumps, or top drive on rigs utilizing the Amphion and Cyberbase rig control systems. This document is intended to guide the user through the process of installing and setting up the Innova Remote Client application on a device on the rig network, so that it can communicate with both DrillLink and Well Seeker Pro installed on a remote PC, to facilitate the downlink functionality. The Innova remote client is only required if the Well Seeker Pro PC is outside the rig network.
The below system diagram depicts how Well Seeker Pro interacts with DrillLink to send downlinks from a remote location and the role the Innova Remote Client plays in that communication.
If the Well Seeker Pro laptop is not at the rig site then the security risks are innate security risks, as this requires a way for an external source to access the rig network. These risks are negated in the following ways:
Well Seeker Pro communication from a remote location is handled solely by the Innova Remote Client. This application will only deal with communication from Well Seeker Pro via the secure ICP API (Innova Cloud Portal API)
All communication between Well Seeker Pro and the Innova Remote Client use TSL encryption (Transport Layer Security)
Access to the Innova Remote Client requires a Username and Password for successful communication to be established. These credentials can only be supplied by Innova
Each rig will be specified by a randomly generated unique code (GUUID) from Innova, which must be known to communicate with the Innova Remote Client for a specific rig. This can only be handled when using Well Seeker Pro software
The Downlink Control functionality is a license enabled feature, meaning that only users with a valid license for the feature will be able to use it
The driller at the rig site will have ultimate control as to whether the DrillLink system allows remote access or not, utilizing an override switch in the DrillLink console on the rig floor
The below steps lead the user through installing the Innova Remote Client application on to a device that is on the rig network and will be able to communicate with the DrillLink device.
1. Save the install file provided by Innova on to the desktop of the chosen device. This device should be connected to the rig network
2. Open the install file by double left clicking on it
3. Check the I agree to the License terms and conditions cell and then select INSTALL. The user can view the license terms and conditions by selecting the blue phrase License terms and conditions
4. The installation will complete. Select Finish
5. A shortcut for the application will have been created on the device desktop
Once installation is completed the Innova Remote Client must be setup so that it can communicate with both Well Seeker Pro, via the ICP API and DrillLink. The below steps will guide the user through this process.
1. Open the Innova Remote Client via the shortcut on the device desktop
2. In the ICP Configuration section input the Username and Password credentials supplied by Innova. This allows the Innova Remote Client to communicate with Well Seeker Pro via the ICP API
3. Input the Rig GUUID supplied by Innova. This is a security feature that ensures that the rig can only be communicated with by a validated user and not be confused with any other rigs
4. If not already the case, set the Environment to Production. This can be selected in the Environment menu and selecting Production
5. Enter the DrillLink Configuration IP Address and Port. This is the IP for the device that DrillLink is installed on, or relays information to DrillLink. The port is always 8080
6. The DrillLink Controls section displays the status of connection between the Innova Remote Client and DrillLink. The user can use the Connect and Disconnect options to ensure that the correct settings have been input and that a successful connection has been established, denoted by the Connected cell displaying Connected. During downlinking operations the connect, disconnect and abort functions will be controlled by the end user within Well Seeker Pro’s Downlink Control dialog.
7. The current inputs can be saved to a file. To do this select File > Save config
8. To load previous inputs saved to a file select File > Load config. Select the relevant config file and select Open
9. The setup process is now complete
A guide to adding HDGM, mvHD and BGGM geomagnetic models into Well Seeker Pro.
The Well Seeker install includes the latest IGRF and WMM geomagnetic models as standard. In addition to these, the software is also compatible with the following geomagnetic models:
HDGM (NOAA – National Oceanic and Atmospheric Administration)
mvHD (MagVAR)
BGGM (BGS - British Geological Survey)
This document details the steps required to add these geomagnetic models to Well Seeker, as they do not come with the initial install.
This section describes how to incorporate the NOAA HDGM geomagnetic model into Well Seeker.
The following file is required and will be provided by NOAA upon purchasing a license.
hdgm20xx.dll: This is the only file required and the xx in the file name will represent the year e.g. hdgm2020.dll, hdgm2021.dll etc.
The user must now follow the below steps to correctly add the file:
Place the .dll file in the C:\Program Files(x86)\Innova Drilling and Intervention\Well Seeker PRO\Magnetics directory
Open Well Seeker.
You should now be able to select HDGM model in either the Geomag Calculator Tool or in the Magnetics section of the plan/wellbore properties dialog.
This section describes how to incorporate MagVAR’s mvHD geomagnetic model into Well Seeker.
The following is a list of files which are required, ALL of which will be supplied by MagVAR.
MagVarGlobalPlugIn.DLL: Make sure you have the correct 64- or 32-bit version dependent on your computers operating system. Current version is 2.0
A *.mvgm file: This is the magnetic model file which contains the magnetic field parameters for a 12-month period
Hardware Key: This is a string of alpha numeric characters which is unique for each customer who has purchased the magnetic model
The user must now follow the below steps to correctly add the files:
Place the .DLL file and the .mvgm files in the C:\Program Files(x86)\Innova Drilling and Intervention\Well Seeker PRO\Magnetics directory
On the desktop, create a file called mvhdHardwareKey.txt (a standard text file)
Open the text file and copy and paste the hardware key into it
Save the file and close
Add this file to the same directory as the other 2 files
Open Well Seeker
You should now be able to select mvHD model in either the Geomag Calculator Tool or in the Magnetics section of the plan/wellbore properties dialog.
This section describes how to incorporate the BGGM geomagnetic model into Well Seeker.
The method used depends on whether the user has purchased a single or multiuser license.
When the user buys a single user license of BGGM, they will receive a standalone version of the software to run the calculations. If they want to have the BGGM model available to select from within Well Seeker, they need to enable the BGGM Web Service from their machine. This option is available in Well Seeker from v2.0.0.016 onwards. To do this the user should follow the below instructions:
Firstly, the user must have purchased a valid single user license from BGS.
Open Well Seeker and go to Help > License Info. In the License Details dialog, the computers MAC address will be displayed.
BGS will authenticate the MAC address and send a password.
Create a blank text file and name it bggmWebService2023.dat
Note: The name of this file should be adjusted each year, based on the model. For example, if the user purchases the 2025 model the file should be called bggmWebService2025.dat etc.
Innova can provide this if necessary.
Open this file with Notepad and paste the password received from BGS into it
Save and close.
Copy the bggmWebService2020.dat file into the Well Seeker magnetics folder: C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO\Magnetics
Open Well Seeker.
You should now be able to select bggmWebService2020.dat in either the Geomag Calculator Tool or in the Magnetics section of the plan/wellbore properties dialog.
When the user buys a multiuser license, BGS will send a bggm20xx.dat file which needs to be put in the magnetics folder: C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO\Magnetics
The xx in the file name will represent the year e.g. bggm2020.dat, bggm2021.dat etc.
With both files in the magnetics folder, the user will now be able to select bggm20xx.dat in either the Geomag Calculator Tool or in the Magnetics section of the plan/wellbore properties.
Once the new geomagnetic model has been added to Well Seeker, there are 2 places within the program where the user can select this to view the relevant output. These are detailed below.
The Geomagnetic calculator is accessed via the Tools menu in the main user interface.
This will open the below dialog. From here, the user can select the relevant Coordinate Reference System, enter the required surface location, and then generate the magnetics results based on the desired geomagnetic model.
As can be seen from the below dialog, the geomag model is available to select from a dropdown menu. If the user’s new model is not available in this menu, then the model has not been installed correctly and the user should repeat the installation process.
If the user would like to set the new geomagnetic model as their default, this can be done via the Magnetics results section of the Geomagnetic Calculator dialog. Simply select the desired default from the dropdown list and then select Set As Default. The user can check this has worked correctly by closing and reopening the Geomagnetic Calculator. The default will be automatically populated in the Model cell.
The plan and actual wellbore properties dialogs are accessed by right clicking on a plan or actual wellbore in the database tree and selecting Properties. In the Magnetics section the user will be able to select the required geomagnetic model from the dropdown list.
Note that row 1 is uneditable and will always contain the default model, but new rows can be added and selected as Active where appropriate.
A guide to integration with the Oasis ERP software by Merge Solutions, using Well Seeker Pro and the Innova Web Portal.
The Oasis integration within the Innova software allows the user to pull cost and inventory data from Oasis. This information can then be utilized in the daily reporting features, where daily costs and tool hours are recorded, and once complete, this data can be transferred back to Oasis.
The purpose of this document is to introduce the user to the Oasis integration in the Web Portal and Well Seeker Pro, and detail some of the steps required to correctly setup and use these features.
To use the Oasis integration within Well Seeker, the user requires the relevant license. The license features can be checked in Well Seeker by selecting Help – License Info, which will open the below License Details dialog.
The daily reporting module within the Innova database is where most of the Oasis integration data can be found. As a result, the user will need to ensure they have a database structure in place that includes at least one actual well, as this is the level in the database tree that the daily reporting is associated. Note, that this will NOT work in a plan, only in an actual well.
When using the Oasis integration within the Innova software there are two suggested workflow options detailed below.
Server workflow: The job is setup in Oasis, office personnel are then able to pull and synchronize Oasis data into the Web Portal, before the field user pulls down all the data via the Remote Data Fetch tool into a local Well Seeker Pro database. Data is automatically pushed back to Oasis.
The benefits of this workflow are:
Oasis login credentials are only input once in the Web Portal and are not required to be distributed to field personnel
Office personnel can ensure the correct data is pulled into the Web Portal
Data is pushed back to Oasis at a pre-defined time increment, requiring no additional steps from the field user for this to work
Local PC workflow: The job is setup in Oasis, the field user pulls down the well data from the Innova server, via the Remote Data Fetch tool, into a local Well Seeker Pro database and then has to synchronize the job number, cost code and tool data with Oasis. Data is manually pushed back to Oasis by the field user
The benefits of this workflow are:
This is the original workflow that many users are familiar with.
The negatives of this workflow are:
The Oasis credentials need to be distributed to all field personnel to input into each individual install of Well Seeker Pro
The field user is required to manually push the cost and tool data back to Oasis, for this data to then be available within Oasis
The following section will take the user through the server work flow, step by step.
Oasis credentials are input in the Web Portal only once
The job number in Oasis is synchronized with the desired well in the server database via the Wells List page in the Web Portal
The Cost Codes are pulled from Oasis via the Web Portal
The Tools are pulled from Oasis via the Web Portal
DD uses the Remote Data Fetch feature in Well Seeker Pro to pull the well data from the server database to their local PC
Turn on the Real Time Data Exchange to push data from local PC back to the Innova Server
When operations begin, complete the daily cost table for each daily report every day
Create the first BHA in the drill string editor and insert the relevant tools from the inventory. Repeat the process for each subsequent BHA as required throughout the job
When appropriate, reference the BHA’s in the daily activity table in the daily reports and ensure the performance report is updated for each BHA at the end of every run
The Well Seeker cost and tool hour data is automatically pulled to the Oasis server at a predefined time interval. This interval can’t be adjusted by the user.
To allow communication between the Web Portal and Oasis, the user needs to have the following Oasis login credentials, which are provided by Merge Solutions NOT Innova:
URL
Username
Password
To add these details to the Web Portal, the user should select the burger menu at the top left of the screen, then Database Admin Tools > Third Party Apps. Note that this option is only visible and editable for users with the admin permission enabled.
At the bottom of the page select OASIS from the Application cell dropdown list and enter the Oasis username and password. A new row with this data will be created at the top of the page. The organization cell will be populated automatically based on the organization the users login credentials are associated with. The user will need to enter the relevant URL at this point.
These credentials only need to be added once for the entire organization.
To allow Oasis and Innova to transfer data between their databases they require a common Job Number for each well. These job numbers must be identical in both programs otherwise none of the transfer functionality will work. The Job Number for each well is entered directly on the Wells List page in the Portal. This can be entered either manually or it can be pulled (synchronised) directly from the Oasis server. The advantage of pulling the job number from Oasis is that the values in both systems will be identical with no potential for data entry errors.
The Oasis Job Data dialog lists all the available jobs in Oasis. The user can use the search bar at the top or can select any of the column headers to sort or filter the data to find the relevant well. Once the relevant well has been found, the user should select the checkbox on the left. Once this has been selected a new option becomes available at the bottom of the dialog called UPDATE JOB INFO. Selecting this will update the Job# and Rig cells in the Wells List page of the Portal.
Note, if the incorrect job number is synchronized at this stage, any data transfer between Oasis and Innova will be for the incorrect job.
Select the well from the Wells List page and then select the Daily Reports option from the menu on the left of the screen. For the integration to function correctly, there must be at least 1 daily report available in this section. This report does NOT need to contain any data.
Select the pencil menu from the bottom right of the screen and select the Add New Report option. Select the relevant date and select submit.
The new report will be created in the table, and the user can then move onto the next step.
Note: If there are no daily reports in this table, when the user tries to import cost and tool data, they will receive the below error message. If this happens, follow the above steps to add a daily report and try to import the data again.
Select the relevant well from the Wells List and then select the Costs page. Select the Cost Codes tab from the far right of the page.
Within the Cost Codes tab, right click to open the context menu and select Get Oasis cost codes.
The Oasis Costs dialog will open. Select the desired Quote and then the desired cost items from that quote. All items can be selected using the top left check box. When selection is complete select IMPORT COST CODES. Note, the user can sort the quotes in this dialog using the columns or the search bar.
Select the relevant well from the Wells List and then select the Inventory page. Select the pencil icon and then Get Oasis Tools.
Select the tools you want to import and select IMPORT TOOLS.
The job number, cost code and tool data have now been synchronized between the Oasis server and the Innova server database. This data is now ready to be pulled down to a local user for use at the rig site.
The Real Time Data Exchange is a tool that is used to update the Innova server database with the latest well data from the local PC. It is essential with this workflow to ensure that the Real Time Data Exchange is pushing data back to the Innova server database throughout the duration of the well, as the data that will be pulled back to Oasis is not pulled from the local PC, but is pulled from the Innova server database. To run the Real Time Data Exchange, open the Daily Report dialog for the relevant well and select Tools > RT Data Exchange, or select the toolbar icon. This will automatically start the Real Time Data Exchange for the selected well.
The daily cost dialog is accessed from within Well Seeker Pro’s daily reporting interface by selecting View – Daily Costs.
Each daily report has its own separate daily cost table associated with it, allowing the user to easily keep track of daily and well total costs. Costs are selected by clicking on the description cell and choosing the appropriate option from the drop-down menu. The available options in the drop-down menu are taken directly from the cost codes table which was populated with the Oasis data.
Once a cost is chosen, the user can then enter the quantity and the total will update. Throughout the job, there will be daily cost data associated with each daily report and this will be pulled back to Oasis.
With the tools now entered in the inventory, the user can add any of these to a BHA. This is an important step in the process as BHAs have run sheets associated with them and are selected in the daily activity section of the daily reports, which is how the associated job run data (hours, depths, dates, drilling parameters etc) is linked to each BHA and by default their individual components.
The drill string editor is accessed by right clicking at Actual Well level and selecting Reporting – Drill String Editor.
Components can be added to the drill string from the inventory by selecting the relevant component type from the dropdown menu and then right clicking on that row and selecting Insert from Inventory. The user can then choose the appropriate tool and select Insert. Note that the tools displayed in the insert from inventory table will only be of the type selected in the drill string editor.
For example, in the below the component in the drill string is a sub, therefore the user will only be given the option to insert tools from the inventory that are referenced as subs, so care should be taken to ensure that each component in the inventory has the component type correctly referenced.
Once the BHA has been completed and all the necessary tools inserted from the inventory, the BHA can then be selected where appropriate in the daily reports. By doing this, as the section is drilled, all the associated data will be linked to the BHA. At the end of the run, this data can then be pulled into the performance report.
The performance report can be accessed via the drill string editor dialog, by selecting Performance Report – Edit Data.
When data is pushed back to Oasis for any given BHA, the performance report is where the data comes from, so it is important that this is updated correctly. Once a BHA has been laid down, and the user is happy the daily report and slide sheet have been completed correctly, they should go to the performance report and select Tools – Get Data from DDR. This will update the performance report with the relevant data which will be pulled to Oasis.
To transfer the cost and tool hour information from Well Seeker Pro to Oasis requires no user actions on the Well Seeker Pro side. This data is pulled from the Innova server database via the Innova API to the Oasis database at a predefined time interval.
It is however important to keep the Well Seeker server updated as much as possible to ensure that any time Oasis updates, it is pulling the most up to date information. As mentioned earlier in the document, this is achieved by setting up and utilizing the Real Time Data Exchange where possible.
The following section will take the user through the local PC workflow, step by step.
Oasis credentials are input in to Well Seeker Pro on each local PC
The job number in Oasis is synchronized with the desired well in the database via Well Seeker
Import the cost details from Oasis into the Cost Codes table in Well Seeker
Import the relevant tools from Oasis into the Well Seeker Inventory
When operations begin, complete the daily cost table for each daily report every day
Create the first BHA in the drill string editor and insert the relevant tools from the inventory. Repeat the process for each subsequent BHA as required throughout the job
When appropriate, reference the BHA’s in the daily activity table in the daily reports and ensure the performance report is updated for each BHA at the end of every run
At the end of the job:
Export the cost data back to Oasis
Export the tool data for all BHA’s back to Oasis
To allow communication between Well Seeker Pro and Oasis, the user needs to have the following Oasis login credentials, which are provided by Merge Solutions NOT Innova:
URL
Username
Password
To add these details, into Well Seeker Pro, the user should selecting File – SQL Server Databases – Oasis Credentials, which opens the Oasis Credentials dialog.
Once entered the user should select apply and close. The user will only need to enter these details once per PC, and they will then be saved within Well Seeker.
To allow Oasis and Innova to transfer data between their databases they require a common Job Number for each well. These job numbers must be identical in both programs otherwise none of the transfer functionality will work. The Job Number for each well can be entered directly in the Well Data and Personnel dialog in Well Seeker. This can be entered either manually or it can be pulled directly from the Oasis server. The advantage of pulling the job number from Oasis is that the values in both systems will be identical with no potential for data entry errors.
To synchronize the job number between Oasis and Well Seeker for a specific well, the user must right click at the Actual Well level and select Reporting > Daily Reporting > Well Data > Well Data and Personnel > Get from Oasis.
In the Oasis Jobs dialog select the relevant job checkbox and select OK. Selecting this will update the Job# and Rig cells in the Well Data and Personnel dialog.
In the Well Data and Personnel dialog, select Apply, and select Save in the Daily Report dialog.
Note, if the user fails to enter a job number at this stage, the Oasis Jobs dialog will open for the user to select the relevant job every time they pull costs codes, or tools and push costs, or tool hours data.
This section will detail how to pull in cost details from Oasis quotes, how to use this data within Well Seeker and how to push this data back to Oasis.
The cost details from Oasis quotes are pulled into Well Seeker via the cost codes dialog. This dialog is accessed by right clicking at the Actual Well level and selecting Reporting > Daily Reporting > Tools > Cost codes. Note that the Cost Codes can also be accessed at Well Level in the database tree. If accessed at Well Level, the “Import from Oasis” option will not be available. To access this feature, the Cost Codes MUST be accessed via the Daily Reporting dialog.
The cost codes entered here are available to select from a dropdown menu in the daily cost dialog within the daily reporting. These cost codes can be imported directly from Oasis by selecting the Import from Oasis button.
This will open the Oasis bids dialog, where all bids associated with the selected job will be listed. Note, if the Oasis credentials have been input incorrectly, then the user will get an error message and the Oasis jobs dialog will not open. The user will need to make the relevant adjustments to the entered credentials before they retry.
The user can then select the check box for the required bid and select ok. This will populate the table with all the costs associated with the selected bid in Oasis.
The daily cost dialog is accessed from within the daily reporting interface by selecting View – Daily Costs.
Each daily report has its own separate daily cost table associated with it, allowing the user to easily keep track of daily and well total costs. Costs are selected by clicking on the description cell and choosing the appropriate option from the drop-down menu. The available options in the drop-down menu are taken directly from the cost codes table.
Once a cost is chosen, the user can then enter the quantity and the total will update. At the end of a job, there will be daily cost data associated with each daily report and this can then be pushed back to Oasis.
At any point in the job, the cost data can be exported to Oasis from within the daily reporting interface by selecting File – Export cost data to Oasis.
If successful, the below message will appear on the screen.
This section will detail how to pull in tool details from Oasis, how to include these tools in BHA’s within Well Seeker and how to push job run data associated with each tool back to Oasis.
Tools from Oasis are pulled into Well Seeker via the Inventory dialog. This dialog is accessed by right clicking at Actual Well level and selecting Reporting – Tool Inventory.
The inventory is where all tools on location for any given job are detailed. The inventory can be filled in manually, or tools can be imported directly from Oasis by selecting File – Import from Oasis. It is important to note that for the Oasis integration to work correctly, tools MUST be imported and NOT manually entered.
Additional data is associated with the imported tools that is not visible in the inventory table but is required when pushing data back to Oasis. If this is missing because the tools have been manually entered, then the data will not push back to Oasis.
Once Import from Oasis has been selected, what happens next depends on what has been entered into the job number cell in the Well Data and Personnel dialog.
If the user has correctly synced the job number and it matches a job number on the Oasis server then the Select Tools dialog will open, where all the tools in Oasis associated with the selected job will be listed (below left). If a job number has been entered but has not been correctly synced, then a warning message will be displayed saying the job number could not be found. Finally, if no job number has been entered at all, The Oasis Jobs dialog (below right) will open. The user will then need to select their job before they can access the select tools dialog.
From the Select Tools dialog, the user can select some or all of the available tools by selecting the appropriate receive tool check box. Once the tools have been selected the user must then enter their name in the received by cell and then select receive selected. Note, the tools will NOT pull into Well Seeker unless a name has been entered in the received by box.
With the tools now entered in the inventory, the user can add any of these to a BHA. This is an important step in the process as BHAs have run sheets associated with them and are selected in the daily activity section of the daily reports, which is how the associated job run data (hours, depths, dates, drilling parameters etc) is linked to each BHA and by default their individual components.
The drill string editor is accessed by right clicking at Actual Well level and selecting Reporting – Drill String Editor.
Components can be added to the drill string from the inventory by selecting the relevant component type from the dropdown menu and then right clicking on that row and selecting Insert from Inventory. The user can then choose the appropriate tool and select Insert. Note that the tools displayed in the insert from inventory table will only be of the type selected in the drill string editor.
For example, in the below the component in the drill string is a sub, therefore the user will only be given the option to insert tools from the inventory that are referenced as subs, so care should be taken to ensure that each component in the inventory has the component type correctly referenced.
Once the BHA has been completed and all the necessary tools inserted from the inventory, the BHA can then be selected where appropriate in the daily reports. By doing this, as the section is drilled, all the associated data will be linked to the BHA. At the end of the run, this data can then be pulled into the performance report.
The performance report can be accessed via the drill string editor dialog, by selecting Performance Report – Edit Data.
When data is pushed back to Oasis for any given BHA, the performance report is where the data comes from, so it is important that this is updated correctly. Once a BHA has been laid down, and the user is happy the daily report and slide sheet have been completed correctly, they should go to the performance report and select Tools – Get Data from DDR. This will update the performance report with the relevant data which can now be pushed to Oasis.
Once a BHA is out of hole and has been laid down, the user can push the data associated with this back to Oasis. This is done from the drill string editor by selecting Import / Export – Export current BHA to Oasis. It is also possible to push all BHA’s back at one time by selecting Export all BHA’s to Oasis.
Note: The data can be pushed back to Oasis either from the local field database, or from the server database. When pushing from the server database it is important to make sure this is up to date with the latest data from the field, which is most often achieved by using the Real Time Data Exchange.
Once the data has been successfully sent, the below message will appear on the screen.
Within Well Seeker, it is possible to transfer tools from one well to another via the inventory dialog, by selecting Transfer Tools. The user can then select the job to transfer the tools to, what tools they wish to transfer and the transfer date.
If the user has Oasis Credentials entered, then the below dialog will appear, asking if the user wishes to transfer the tools in Oasis. If no Oasis credentials have been entered, then this dialog will not appear and the tools will only be transferred within Well Seeker.
Selecting Yes, allows the user to select the current job the tools are associated with in Oasis and then the well they wish the tools to be transferred to. Once complete, the tools will then be transferred within both Well Seeker and Oasis.
An alternative to the above would be to transfer the tools directly in Oasis and then import them into the Well Seeker inventory for the new well.
Well Seeker Pro comes pre-installed with the latest generic surveying error model tool codes issued by the ISCWSA. However, on occasion the user may want to add their own custom tool codes to the software. Usually this is to model the survey performance of a specific tool.
Most surveying tool manufacturers issue their tool codes as IPM (Instrument Performance Model) files with the “*.IPM” file format. If the user has received an IPM file they can follow the instructions in Method 1 below to add it to Well Seeker Pro. If the user does not have the IPM file but has the details of the tool code, they can enter them manually into Well Seeker by following the instructions in Method 2.
1. Open Well Seeker Pro. Open the Help menu and select Open Setup File Folder. This will open a new window.
2. Open the IPM folder.
3. Close Well Seeker Pro.
4. Paste your IPM file into the IPM folder.
5. Open Well Seeker Pro.
6. Your new IPM will be available to select from the dropdown menus in the Survey Properties window and the Plan Properties window.
1. Open Well Seeker. Open the Tools menu and select Survey Tool Editor.
2. Click the Create New button.
3. Enter a suitable file name and hit save.
4. Select the new name from the File Name dropdown menu and then click on the Edit button.
5. Enter a name for the survey tool in the Survey Tool Name box, and a description in the Description box. Enter the relevant co-efficients into the table in the Co-Efficients section. As you enter a row into the table, the software will create a fresh row underneath so that you can continue. When you are finished, click on the Apply button.
6. Your new IPM will be available to select from the dropdown menus in the Survey Properties window and the Plan Properties window.
A guide to changing datum elevation in an existing plan or survey.
The following document will help to guide the user through the process of changing the depth reference (elevation) in Well Seeker for an existing plan or survey, which has an elevation already assigned.
In Well Seeker, the depth reference is entered at Well Level via the Well Properties dialog. This dialog is accessed via the database tree, by right clicking on the Well level and selecting Properties.
The user can then enter their depth reference data into the Depth Reference section, highlighted in red below. Multiple depth references can be entered at Well Level.
Once the user has entered their depth reference information at Well Level, they can then select the relevant depth reference for any plan or survey under that well. This is done by right clicking on the Actual Well or Plan level and selecting Properties. This will open the Actual Wellbore/Plan Properties Dialog. The user can then select the desired depth reference from the dropdown menu in the Depth Reference section, highlighted in red below.
If the Plan/Actual Well already has a datum referenced, then changing the depth reference in the Actual Wellbore/Plan Properties Dialog will prompt the following warning:
The user has three options:
Change TVD’s: Picking this option will change the MD and TVD values of the survey/plan points to reflect the new depth reference
Note: The TVD Subsea values will remain unchanged if the GL to MSL value is the same for both datums.
This option is usually selected when you have an existing well that was drilled with one rig and you are now planning to perform additional work with a different rig. In this situation the user wants to see the survey or plan depths adjusted to reflect the new datum.
Preserve TVD’s: Picking this option will preserve the MD and TVD values of the survey/plan
Note: The TVD Subsea values in this case will change.
This option is usually selected when a plan or survey has mistakenly been referenced to the wrong datum, and the user wants to assign a new datum, but not adjust the MD and TVD values.
Cancel: The change of depth reference is cancelled, and no changes are made to the survey/plan points.
Note: The user will also get this warning if they edit the value of a depth reference that is currently being referenced by a survey or plan.
In this example, we have a simple set of surveys, referenced to the below left RTE (RTE Plan) @ 100Usft AMSL.
We are then given a new RTE (below left RTE Actual) to reference @ 101Usft AMSL. When we select this new depth reference, the below right warning appears.
If we choose to Change TVD’s the surveys will change to the below:
The MD and TVD values have increased by 1Usft
The TVDss values have remained the same, except for the tie-on line
This would be desirable if you are side-tracking this well with a rig that has a RTE 1ft greater than the original rig.
If we choose to Preserve TVD’s the surveys will change to the below:
The MD and TVD values have remained the same
The TVDss values have changed by 1ft
This would be desirable if you discover that you have the wrong RTE referenced and want to reference the correct RTE without adjusting the survey depths.
Innova’s Well Seeker Remote Client is a stand-alone program which can be utilized at the rig site to send WITS data back to the companies SQL server database via the ICDS (Innova Central Database Server). This data can then be viewed and used by anyone in the company with the appropriate access to the database, providing the user with all the data required to carry out remote operations from anywhere in the world.
This document describes the Well Seeker Remote Client and details the steps required to correctly utilise its functionality.
The below steps lead the user through the Well Seeker Remote Client installation process.
Save the install file (Well Seeker Remote Client - vX.X.X.X.exe) provided by Innova onto the desktop of the chosen device.
Open the install file by double left clicking on it
Check the I agree to the License terms and conditions cell and then select INSTALL. The user can view the license terms and conditions by selecting the blue phrase License terms and conditions
Once the installation is complete. Select Finish
A “Well Seeker Remote Client” folder will have been created in the following location on the computer:
C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker Remote Client
This folder will contain the following files:
wellSeekerClient.exe
PEGRP32G.DLL
vsflex8u.ocx
To open the Well Seeker Client, the user should double left click on the wellSeekerClient.exe file. This will open the program and the user will see the main user interface as show below.
File Menu
Save Config: Saves the current configuration. When this option is selected, the saved configuration will be what loads each time the program is opened.
Save Config As: Saves the current configuration as a .ini file which can be selected again at any time to load the users desired setup
Load Config: Loads an existing config .ini file, which pulls in all the users saved settings
Exit: Closes the program
WITS Mapping Menu
Reset to Defaults: Resets the WITS Mapping table to the default values
Help Menu
About: Opens a dialog which shows which version of the program is being used
This section allows the user to map the WITS inputs to ensure that the data is being received on the correct channels. WITS mapping should be standard, but this information can be obtained from the EDR provider.
RID: The Record ID, which comes from the WITS zero standards
FID: The Field ID, which comes from the WITS zero standards
Mnemonic: The Internal Mnemonic is what Well Seeker uses to map the WITS data it is receiving. For example, a WITS ID of 0110 is mapped to Hole MD (WITS zero standards), which is something that will make more sense to the user
If necessary, the user can add a new line to the table by selecting an existing line and pressing the spacebar. This inserts a line above the selected line.
This section allows the user to configure the thresholds used for determining the current Rig states. The rig states will operate when the WITS Reader is running.
The below is a guide to initial threshold values, which can be adjusted and fine-tuned as you start to receive data:
RPM: Initially, set this as the oscillating RPM when sliding; however, this is something that will likely need to be adjusted based on operating parameters.
Pump Pressure: 300psi.
Flow Rate: 50gpm.
HKLD: Set at block weight + 20, or something similar.
On Bottom Delta: 0.5ft.
WOB Threshold: 2k or 1T.
RPM Buffer Size: This is the number of rpm values which WS will remember in the rpm buffer. Well Seeker uses this to identifying when the assembly is rotating. 9 or 10 is usually a good starting value here.
The Rig States logic is what Well Seeker uses to determine what is currently happening in the well e.g. Rotating, Sliding, Tripping, Circulating etc. The thresholds will determine at what level certain rig states will be classified. Rig states logic is defined below:
RPM < RPM Threshold then Sliding = True
Pump Press < Pump Press Threshold then pumps off = TRUE
HKLD < HKLD Threshold then In Slips = TRUE
Pumps Off = TRUE and In Slips = TRUE then Connection
Hole Depth – Bit Depth < On Btm Delta, then On Bottom = TRUE
RPM threshold should be 50% of current rotating speed
Based on the WITS values being received, the threshold values and the above rig states logic, the Rig State cell will populate with the resulting rig state conclusions.
The WITS Data section will populate with the latest WITS values as they are received. The WITS mapping must be correct, otherwise the values will either not show in the table or will populate in the wrong cell.
This section is where the user chooses the type of WITS connection and starts reading the available data.
WITS Status: Show if WITS is being received.
With NO WITS being received the cell will be red and say Not Reading
When receiving WITS, the cell will be green and will say Reading WITS. The message will include whether the received wits is serial or UDP.
WITS Reader Window: When WITS data is being received, the user will see characters fill this window
Comm Port: This dropdown menu shows the list of available Comms ports for the user to select. Unless the user has a serial box to USB box connected to the computer, they are unlikely to have any comm ports available on this list.
UDP PORT: This option should be selected if receiving UDP WITS, which will be received via an ethernet cable. This is where the user enters the relevant UDP Port. This input will only be available when the checkbox to the left of the UDP Port text is selected.
TCP IP Address: This is where the user enters the relevant TCP IP Address. This input will only be available when the checkbox to the left of the TCP IP Address text is selected. When selected, the UDP Port cell will also become available to populate.
Pause Messages: This option pauses the live messages allowing the user to easily scroll through the list of messages without it constantly updating. This does not stop the messages being received, it only pauses the view. Once unselected, all messages which were received during the paused interval will appear.
Send Handshake: Leave checked, unless receiving WITS from Noralis.
Start Reading: Starts reading the available WITS data.
Stop Reading: Stops reading the available WITS data.
The ICDS data transfer section is where the user can enter the appropriate details to connect to the ICDS and select the relevant well which the WITS data will be associated with in the database.
ICDS Data Transfer Window: This window displays all available Actual Wells in the SQL server database which have daily reports associated with them. The user can then choose the appropriate well from the list. When the data is then sent, it will be associated with the selected well in the SQL database.
Get Well List: Selecting this option will populate the ICDS Window with all available wells from the SQL Server database.
Select Well: Once the user has selected the required well in the ICDS Window, choosing this option will populate the Selected Well cell.
Start Sending: Starts sending the WITS data to the SQL server database
Stop Sending: Stops sending the WITS data to the SQL server database
Selected Well: Shows the well which the WITS data will be associated with on the SQL server database
ICDS IP Address: The IP address for the relevant ICDS
ICDS Port: The port number for the relevant ICDS. This is usually 42000
ICDS Password: The password for the relevant ICDS.
ICDS Status: Shows the user if the WITS data is being sent or not.
To run the Well Seeker Remote Client correctly, the following inputs / Information are required:
ICDS IP Address
ICDS Port
ICDS Password
The Actual Well or Job Number, which needs to be selected in the ICDS Data Transfer Window
For the Rig States to operate, the below, correctly mapped WITS Inputs are required via either serial, UDP or TCP connection
The following section details the steps required to run the Well Seeker Client.
Ensure the computer has a WITS connection
Ensure the WITS Mapping matches that of the data being received
Select the relevant Comm or UDP Port
Check the Send handshake checkbox, unless receiving WITS via Noralis
Select Start Reading and ensure the WITS reader window is populating with the incoming WITS data
The WITS Status should be green and show the type of WITS connection being used
Check the Rig States Threshold values are setup as required
Enter the ICDS
IP Address
Port
Password
Select Get Well List
The ICDS Data Transfer Window should populate with the available wells
Select the required well from the table and hit the Select Well button
Ensure the correct well name has populated the Selected Well cell
Select Start Sending
The ICDS Status cell should turn green and it should say Sending Data along with the current time
If the above steps have been followed and all data has been entered correctly, then the WITS data will now be sent to the server database via the ICDS and will be available to all users.
Introduces the user to the Rig States dialog, which is used in tandem with WITS to automatically populate the slide sheet.
During drilling operations, Well Seeker Pro has the ability to receive a WITS or WITSML feed from the rig site and use this data to automatically populate the Directional Driller’s slide sheet. To do this, Well Seeker Pro must use the WITS data to deduce the current operation on the rig – drilling, sliding, connection and so on – otherwise known as the rig state.
Well Seeker receives drilling parameters from the WITS/WITSML feed and compares them against user-defined thresholds. Depending on whether the incoming values are above or below the threshold, Well Seeker can infer what activity is currently happening on the rig. For example, if the string RPM is below the RPM threshold it can be inferred that the string is not rotating etc. Well Seeker then combines all of these parameters to deduce the current rig state.
The user can control this process by defining the drilling parameter thresholds in the Rig States Dialog. The purpose of this document is to introduce the user to the Rig States dialog in Well Seeker Pro, and detail the steps required to correctly setup and use it.
To auto-populate the slide sheet, the following channels need to be received from the WITS/WITSML feed:
Weight on Bit
RPM
Total GPM
Bit Depth
Hole Depth
Hookload
Block Position
Standpipe Pressure
ROP (Optional – for recording parameters only)
Torque (Optional – for recording parameters only)
In addition, if the user wants to receive survey and toolface data, the following channels are required:
Magnetic Toolface
Gravity Toolface
Survey Measured Depth
Survey Inclination
Survey Azimuth
The Rig States dialog can be configured before or after setting up the WITS/WITSML feed. To do this, follow the below instructions:
Configure the rig parameter Thresholds.
The threshold value acts as a switching point. Any value below the threshold is effectively off, while any value recorded above the threshold is on. It should be set low enough that there is a clear demarcation between each activity, but not to zero. This will stop erroneous WITS values from accidentally changing the activity.
RPM: If the incoming RPM value is below the threshold, the pipe is considered to be not rotating. If it is above, it is rotating. When drilling, this is used to decide if the string is sliding or rotary drilling.
Pump Pressure: If the incoming standpipe pressure value is above the threshold value, then the pumps are considered on. If it is below the threshold, the pumps are off.
Flow Rate: This threshold is obsolete and can safely be ignored.
Hookload (HKLD) Threshold: If the incoming hookload value is lower than the threshold, the string is considered in slips. If it is above, then it is out of slips.
On Bottom Delta: The program calculates the difference between the Bit Depth and the total Hole Depth. If this value is smaller than the On Bottom Delta, then the bit is considered on bottom. If it is larger, then the bit is off bottom.
Weight On Bit (WOB) Threshold: The incoming weight on bit value must be above this threshold before the program acknowledges that WOB is being deliberately applied by the driller.
If necessary, configure the RPM buffer. RPM values from the WITS/WITSML feed can fluctuate, so in addition to the RPM Threshold, the Rig States dialog also uses the RPM Buffer to determine if you are rotating or sliding.
The RPM buffer size sets how many of the most recent RPM values to keep in the buffer, and the RPM Buffer Threshold sets how many values in the buffer need to be above the RPM threshold before Well Seeker considers the string to be rotating.
As an example, with an RPM Buffer Size of 9 and an RPM Buffer Threshold of 3 the below would be true.
If there are 3 or fewer values in the RPM buffer that are > RPM Threshold then you are sliding.
If there are 4 or more values in the RPM buffer that are > RPM threshold then you are rotating.
In most cases, these values can be left as the default.
Once the thresholds have been set up, minimize the Rig States dialog. Do not close it.
Once both the Rig States and the WITS/WITSML feed have been set up, you can click on the green Auto Populate Slide Sheet button on the toolbar to start automatically recording rotate and slide activity, as well as drilling parameters.
The message “Live Rig States Running” will appear below the toolbar. You will NOT be able to manually edit the slide sheet while the slide sheet is auto-populating. To pause recording, click on the red Stop Auto Populating Slide Sheet button on the toolbar. This will allow you to edit the slide sheet again.
The thresholds can be changed while the slide sheet is auto-populating. If you feel that the slide and rotate activity is not being accurately captured, try adjusting some of the thresholds.
While receiving WITS data, the Rig States dialogue can be used to view the incoming drilling parameter data and the rig state inferred from that data. These will display regardless of whether auto-populate is turned on or off.
The Current WITS Data and Drilling Params sections display the data values taken from the WITS feed. They will display the most recently received values.
In the Current Rig State section, Well Seeker takes the values from the Current WITS Data and Drilling Params sections, and compares them to the user defined threshold values to deduce the activities displayed:
On Bottom Delta >> On/Off Bottom
Pump Pressure >> Pumps On/Off
Hookload Threshold >> In/Out of Slips
These activities are combined with the direction of the travelling block to deduce the RigState output. The slide sheet can only record rotating or sliding activity, but the RigState output can deduce other activities, such as reaming in/out, tripping in/out and connection. See the Troubleshooting section below for the full list of activities.
If the WITS feed is also sending toolface data, this will be displayed in the Sliding TF section.
The Timers section displays the last time a Pumps On, In Slips, Off Bottom or Survey event was recorded. The Duration column records how long the event lasted.
If the slide sheet is not auto-populating in the way you would expect, follow the below steps to troubleshoot the issue:
Check the Current WITS Data and Drilling Params sections. As a minimum, the following channels need to be received from the WITS/WITSML feed for the Rig States dialog to function:
Weight on Bit
RPM
Total GPM
Bit Depth
Hole Depth
Hookload
Block Position
Standpipe Pressure
If all channels are not receiving data, this could indicate that the WITS feed is not being received at all. Make sure that the WITS or WITSML reader is reading. If it is, check that the message box is showing incoming messages. If not, there may be an issue with your connection.
Check the physical connection between your computer and the rig WITS system. If you are using serial WITS, note that you should be using a null modem cable and not a regular serial cable.
Observe the Current Rig State section while rig activity is happening. If the activities being displayed in the section do not match with the activities on the rig, this can indicate that your thresholds have not been set properly.
Each state displayed in the RigState field corresponds to a specific combination of threshold values and travelling block direction. The combination required for each is displayed in the table below.
If a cell is filled in GREEN then the value is above the threshold. If it is filled in RED then it is below the threshold. Cells filled in grey can be either above or below.
If the combination of thresholds and block speed does not match with one of the rig states listed here, the displayed rig state will be UNKOWN.
If having worked through all of the trouble shooting steps detailed above, you are still having issues, you can contact Innova support for assistance. When contacting Innova, to allow us to provide the most efficient support, please follow the below steps:
Create a debugging file: In the main Well Seeker window, open the Help menu and select Create Debugging File. This will create a .zip file containing a copy of the current database, a copy of your setup file and a txt document containing system information.
Clearly state the name of the well and Operator you are working in.
Create a log file: In the Slide Sheet window, open the Tools menu and toggle on Enable Error Logging. This will create a log file that captures incoming rig parameter data and logs any errors. Start reading with the WITS feed and open the Rig States dialog, and let them run for some time to collect some data in the log file. This should ideally be done whilst performing the next step.
Record a screen capture of your Slide Sheet and Rig States dialog: In the main Well Seeker window, open the Help Menu and select Start Screen Capture. This will begin recording a video of your screen. Note that it does not record any audio. Display your slide sheet and Rig States dialog on your screen, similar to the screenshot below, and begin auto-populating your slide sheet. Try to capture the issue occurring. When you are ready to stop recording, go back to the Help menu and select Stop Screen Capture.
Open the Help menu again and select Open Setup File Folder. In this folder, open the Debug folder. The log file rigStateLog.txt and the screen capture screenCapture.mp4 are located here.
Include a detailed description of your issue.
Innova support will get in contact with you to provide assistance.
A step-by-step guide to using the Solo Cloud feature in Well Seeker Pro version 2.2.0.4 onwards.
From version 2.2.0.4 onwards, Well Seeker Pro includes an integrated geosteering update feature which automatically creates new plans using updated geosteering data from ROGII’s Solo Cloud. This utilizes Well Seeker’s existing Create Offset Plan tool, combined with input data automatically pulled from Solo Cloud. In combination this negates the requirement for user input, speeds up the geosteering update workflow and eliminates a source of human error.
Additionally, this feature can pull the formation top data (topsets) from Solo Cloud and overwrite Well Seeker’s Lithology table data.
This document will guide the user through the specifics of the setup and operation of this feature.
Open any survey table under the well of interest.
Select Tools > Solo Cloud.
Check and then expand the relevant Organization, Well and Actual Well item in the Object Explorer. As you select items in the Object Explorer, the Settings dialog will update accordingly.
Chose the Auto Update setting. Select YES or NO.
YES: When a new starred Target Line is added to the Solo Cloud database, or an existing starred line is changed in some way, the Well Seeker user will receive a pop up message within the Well Seeker interface, informing the user of the existence of the new target line and offering the user the choice of creating a new plan within Well Seeker. If the user selects to create a new plan, the plan will be automatically generated in Well Seeker and selected as the principal plan. This new plan will also be pushed to Solo Cloud. If the user chooses not to create a new well plan, nothing will change. If the user selects YES, set the frequency of updates in minutes using the Update Rate (mins) field.
NO: The user picks the target line and creates an offset plan manually from the Solo Cloud dialog.
In the Back to Plan Transition field choose either STEP or SMOOTH. When the user creates a new offset plan in Well Seeker, it will be pushed back to Solo Cloud. This setting decides if the transition between the old plan and the new will be a step change, or a smooth transition. If SMOOTH is chosen, set the dogleg severity in the Back to Plan DLS field. Note that the smooth transition will only be displayed in Solo Cloud (below right). In Well Seeker, the transition is displayed as a step regardless of what is chosen here.
Check and expand the Target Lines level and select the relevant target line. Target lines that are currently Starred within Solo Cloud will display with a green T icon next to them. This is to indicate the most recent target line. The Object Info section will display the target line data when selected.
Select the Create offset plan icon. The offset plan will then be automatically created and will be accessible in the Well Seeker database. Close the Solo Cloud dialog. Note that when Auto Update is selected, the user will only need to manually create the first target line, after that a dialog will pop up on the screen any time a change in target line is detected.
When added to the database tree, the name of the offset plan will contain the name of the target line, the date and time it was added to Well Seeker, and whether it is using a STEP or SMOOTH transition (even when named smooth, it will always be stepped in Well Seeker).
The new offset plan will be automatically pushed to Solo Cloud and set as the principal plan in Well Seeker.
How the user should then proceed depends on whether they chose YES or NO for the Auto Update setting in step 5:
Selecting YES:
If a new target line is created and starred, or the current starred target line is changed in any way (including target thickness) in Solo Cloud, the Well Seeker Pro user will receive a popup message, describing the new target. If the user clicks on Ignore, no change will be made in Well Seeker. If they click on Accept, a new offset plan will be created in the database tree, and will be set as the principal plan for the well. It will also be automatically selected as an offset well so if a chart is open it will show up immediately.
Selecting NO:
The user will not automatically receive an update if any changes are made in the Solo Cloud database. They should periodically re-open the Solo Cloud dialog to check if any updates have been added to their project.
If a change has been made, the user should repeat steps 7 and 8 to create a new offset plan in their Well Seeker database tree.
Note: Well Seeker creates a new plan for EVERY target line change detected, even if this is just a change in an existing target line e.g. thickness. This is important because it is handled differently in Star Steer. This is discussed in more detail in the next section.
Whenever the user accepts a new target line in Well Seeker, either through the auto-update feature or manually using the Solo Cloud dialog, it always results in a new plan being created in the Well Seeker database tree. At the same time, Well Seeker transmits the plan back to Solo Cloud and the StarSteer software.
However, this does not necessarily result in a new plan being created in the StarSteer interface. In StarSteer, each target line can only have one plan from Well Seeker associated with it. If a plan already exists for a target line, it will be overwritten by the new plan transmitted from Well Seeker. The date and time in the name of the plan will change to show when the update was received.
For example, the StarSteer user has two target lines for a well. Target Line 1 is currently starred and the user creates an offset plan from this. Below left is Well Seeker and right is Star Steer.
They then make a change to Target Line 1, and this change is sent to Well Seeker. The Well Seeker user accepts the target line change, which creates a new plan in Well Seeker (below left) and sends this back to Star Steer. Because Target Line 1 already has a plan associated with it in Star Steer, the plan is overwritten and the name is updated (below right).
The StarSteer user than changes the starred target line to Target Line 2, which does not currently have a plan assigned to it. This change is sent to the Well Seeker user, who accepts the change, and a new plan is transmitted back. Because Target Line 2 currently has no plan, a brand new plan is created in StarSteer.
Follow section 2, steps 1 to 4.
Select Topsets and then the desired Topset group. Note that the check boxes will NOT be selectable. Only the text can be selected. The Object Info section will update with the relevant formation top data.
Select the Pull Tops icon. Select Yes to the overwrite existing lithologies message. Close the Solo Cloud dialog. The Lithologies table for the current actual wellbore will have been overwritten with the Solo Cloud Topsets data.
A step-by-step guide to using Well Seeker Pro's survey correction feature, that allows the software to sync surveys with external correction providers
Well Seeker Pro version 2.2.0.4 or later includes an integrated feature that allows the user to download corrected surveys from three survey correction providers – Superior QC, H&P Survey Management and RoundLAB. This document is a guide to setting up and using the integration.
1. Open the survey that you want to sync with the survey correction service. When the corrected surveys are downloaded they will overwrite what is currently in the survey sheet, so if you have multiple tabs open, make sure you are viewing the correct one.
2. Open the Tools menu and select Svy Correction Provider Settings. Note that this option will not show in the menu unless a survey is open. This will open the Survey Correction Provider Settings window.
3. Select your provider from the dropdown box in the Provider field, then enter your username and password into the Username and Password fields.
5. In the Select column click on the checkbox that corresponds to the desired well and then click on Update. The Sel Well Name and Sel Operator fields in the Survey Correction Provider Settings window will update.
Note: This will overwrite any existing data in the sheet.
Note: If the tie-on line for the survey is deeper than the surveys available, selecting yes will not do anything i.e. no surveys will be pulled into Well Seeker.
7. You can also set Well Seeker to automatically check for and sync new surveys. Change the Auto Update field from ‘NO’ to ‘YES’ and set the update rate in minutes in the Update Rate field. In order for the automatic sync to work, the survey sheet must remain open, but the Survey Correction Provider Settings window can be closed.
Some features of the Survey Correction Integration are only available when Superior QC is selected as the provider. These features are optional and are not required to perform the basic survey retrieval function.
To enter the API number in Well Seeker, right click on the relevant actual well in the database tree and select Reporting >> Daily Reporting.
In the Daily Reports window, make sure you have at least one daily report created, and then click on the Well Data & Personnel icon in the toolbar. In the Well Data & Personnel window, fill in the API Job # field. Make sure this matches exactly with the API number entered in Superior QC. Click on Apply, and then save in the Daily Reports window. Note, that if the API number is entered but does not match, then the user will still have the option to manually select the desired well.
In Well Seeker the Latitude and Longitude co-ordinates of the well are set in Well Properties dialog for the well. Grid Convergence is automatically calculated using the well location and the mapping grid selected in the Field Properties Dialog.
Total Field, Dip and Declination are set in the Actual Well Properties dialog. These dialogs can all be accessed by right clicking on the database tree at the relevant level and selecting Properties.
A guide to printing a wall plot to pdf via the Wall Plot Composer.
In most cases, printing a wall plot from the Wall Plot Composer (WPC) dialog within Well Seeker Pro is a simple process. However, a small number of cases have been noted when printing to an A1 or A0 size PDF, particularly from a device with high-resolution display settings, that the resulting PDF document does not accurately represent the image created within the WPC dialog.
This issue is independent of the ‘Page Setup’ settings within WPC and is solely related to the ‘PDF Page Size’ option in the PDF printer properties. So regardless of what size of plot is created within the wall plot composer (A0 to A7 or user defined), the user may only see an issue if they try to print to A1 or A0 size. It should be noted that in general, to get the best possible output, the user should print to the same paper size as selected in the page setup i.e. if an A4 plot is created, print it as an A4 PDF etc.
This is not a problem with Well Seeker Pro, but a common issue with multiple different PDF printing software applications and their interaction with a wide range of chart creation software.
The aim of this document is to give the user a simple solution to this potentially time-consuming problem.
When in the WPC dialog, in order to print the WPC design to PDF the user selects ‘File > Print’. The below, or similar, dialog will appear, allowing the user to select one of a number of potential PDF printers. The options available from the drop-down menu, depends on the pdf software the user has installed on their machine.
When the user selects ‘Properties’ the adjoining dialog, or similar, will appear, allowing the user to adjust the PDF print settings. In this example the settings will be left as default and the page size as A4.
The PDF is created when the user selects ‘OK’ in the Print dialog. The below images show the resulting PDF matches the WPC design.
In most instances the generated output matches the WPC layout; however, a few users with high resolution display settings may encounter the below issue when printing an A0/A1 plot to PDF.
When in the WPC dialog, in order to print the WPC design to PDF the user selects ‘File > Print’. The below, or similar, dialog will appear, allowing the user to select one of a number of potential PDF printers. When the user selects ‘Properties’ the adjoining dialog or similar will appear allowing the user to adjust the PDF print settings. In this example the settings will be left as default with the exception of the page size, which will be changed to A0.
The PDF is created when the user selects ‘OK’ in the Print dialog. The below images show the resulting PDF matches the WPC design in most respects, but the Y axis grid lines in the section view plot are not printed correctly.
If you encounter this issue it can be overcome by REDUCING the Print Quality DPI setting, without impacting the perceived image quality. This process will differ between PDF printer software, but the below example is for one such software.
To change the print quality DPI setting, when in the WPC dialog, the user selects ‘File > Print’. The below, or similar, dialog will appear, allowing the user to select one of a number of potential PDF printer options. When the user selects ‘Properties’ the adjoining dialog or similar will appear allowing the user to adjust the PDF print settings. In this example the settings will be left as default with the exception of the page size, which will be changed to A0.
The user then selects the ‘Paper/Quality’ tab, and then selects ‘Advanced’, shown below.
This will open the below, or similar, dialog where the user should DECREASE the ‘Print Quality’ to 600dpi.
Once this option has been selected and the printing process has been completed the resulting PDF should represent the image in the WPC dialog, without any graphical flaws in the X or Y axis gridlines of a chart.
A guide to the toolbars available within Well Seeker Pro.
Well Seeker Pro comes pre-installed with three toolbars:
A Well Seeker Toolbar which contains the main functions of Well Seeker
A Reporting Toolbar, which contains functions relating to the Drill String and Daily Reporting editors.
A Field Toolbar, which contains functions that Directional Drillers commonly use during drilling operations.
This document provides a guide to customizing the Well Seeker and Reporting toolbars.
It is possible to hide or display both toolbars based on the user’s personal preference. The selection made is remembered by Well Seeker and the selected toolbars will be displayed each time the software is opened. The user can show or hide the toolbars by following the below steps:
1 - Open the View menu from the Menu Bar and select the Toolbars and Docking Windows menu item.
2 - Select the Well Seeker Toolbar, Reporting Toolbar or Field Toolbar item to toggle the respective toolbars on/off.
When first installed, the toolbar contains all the available options, which for some users may be too many buttons. It is possible to remove any unwanted icons by following the below step:
Hold down the ALT key and then left-click the mouse key and drag the desired icon away from the toolbar. Releasing the mouse key will then cause the icon to disappear.
If an icon is removed by mistake, or if the user decides to add back in previously removed icons, this can be achieved by following the below steps:
1 - Open the View menu from the Menu Bar and select the Toolbars and Docking Windows menu item.
2 - Select the Customize menu item to open the Customize dialog. Select the Commands tab.
3 - The user can then search for the desired icon by selecting the various categories on the left-hand side of the dialog. The icons relating to the selected category will be displayed in the Commands box on the right-hand side of the dialog.
4 - Once the desired icon has been identified, it can be added to the toolbar by dragging and dropping it onto the toolbar.
The toolbar can be reset back to its default setting, as per first install as follows:
1 - Open the View menu from the Menu Bar and select the Toolbars and Docking Windows menu item.
2 - Select the Customize menu item to open the Customize dialog. Select the Toolbars tab.
3 - Select your desired toolbar and click on the Reset button. Alternatively click on the Reset All button to reset all the toolbars.
A guide to creating Certified Survey Reports in the Well Seeker daily reporting dialog.
After drilling a well in Texas or North Dakota, there is a requirement to send a certified survey report to the relevant government department. Well Seeker Pro allows the user to quickly print a set of certified surveys along with the accompanying report which is setup with the correct formatting.
The feature is accessed through the Daily Reports dialog. To print the certified surveys open the File menu, select Print PDF Reports and then select Print Certified Surveys.
To print the certification reports open the File menu and select Print PDF Reports. Select Print Certification Report – Texas or Print Certification Report – ND.
The certified surveys and certification reports are populated using data located in various parts of the Well Seeker Pro database. The sections below explain where each element is sourced.
The top of every page in the report contains the company’s logo and address.
Logo – Set using the Secondary Logo option in the Operator Properties, accessed via the Database Tree.
Company Address and Details – Your company’s details in the top right are set by opening the Help menu in the main Well Seeker interface and selecting Company Details.
After the recipient address the report contains some general information for the well:
Operator – Populated from the Name field in the Operator Properties, accessed via the Database Tree.
Well Name – Populated from the Name field in the Actual Well Properties, accessed via the Database Tree.
The following elements of the report are populated from the Well Data & Personnel dialog. In the Daily Reports window, open the Well Data menu and select Well Data & Personnel.
Permit Number – Permit Num.
Survey – Permit Survey.
Abstract – Permit Abstract.
Field – Target Formation.
County & State – Selected from the dropdown boxes in the State/County section.
API Number – API Job #.
Company Name - Open the Help menu in the main Well Seeker interface and select Company Details. The source for this element is the Company Name field.
Operator Number – Also in the Company Details dialog. The source for this element is the Survey Operator # field.
Name of Surveyor – In the Daily Reports window, open the Well Data menu and select Well Data & Personnel. The name of the surveyor is taken from the Day MWD Engineer field.
Drainhole Number – If the well starts at surface it will be described as ‘Original Wellbore’. If it is a sidetrack it will be described as a ‘sidetracked wellbore’.
Surveyed Depths – The shallowest and deepest value of each separate survey included in the survey program. It does not include the tie-on survey or the last survey. The program assumes the last survey is a projection.
Dates Performed – The date of the first and last daily report in the Daily Reports dialog. This will be the same for each line
Type of Survey – Populated based on the Survey Tool selected in the Survey Properties dialog. Gyro type surveys are not included in the list.
MWD Operations Manager - Open the Help menu in the main Well Seeker interface and select Company Details. The source for this element is the MWD Ops Manager field.
Job Number – Job # field in the Well Data & Personnel section.
Survey Type – Populated using the Survey Tool selected in the Survey Properties dialog. Gyro type surveys are not included in the list.
Operating Company – Populated using the Name field in the Operator Properties, accessed via the Database Tree.
Well Name and Number – Populated using the Name field in the Actual Well Properties, accessed via the Database Tree.
Drainhole Number – If the well starts at surface it will be described as ‘Original Wellbore’. If it is a sidetrack it will be described as a ‘sidetracked wellbore’.
Location – Selected from the dropdown boxes in the State/County section in the Well Data & Personnel section.
API Number – API Job # field in the Well Data & Personnel section.
Tie In Depth – The tie-in of the first survey of the well, set in the Survey Properties in the database tree.
Surveyed Depths – The first and penultimate survey in the actual wellbore of the well.
Projected TD Survey – Final survey in the actual wellbore of the well.
Dates Performed – The dates of the first and last daily report in the Daily Reports dialog.
Company Name - Open the Help menu in the main Well Seeker interface and select Company Details. The source for this element is the Company Name field.
Magnetic Variation Services LLC – This is standard text for this report and cannot be changed.
MWD Surveyor Name – In the Daily Reports window, open the Well Data menu and select Well Data & Personnel. The name of the surveyor is taken from the Day MWD Engineer field.
MWD Operations Manager – Open the Help menu in the main Well Seeker interface and select Company Details. The source for this element is the MWD Ops Manager field.
Signature – Intentionally left blank.
Date – The date the report was generated.
Email - Also in the Company Details dialog. The source for this element is the Ops Manager Email field.
The Certified Survey Listing is a survey report that has each of its constituent survey runs split up into their own individual reports, to comply with local government reporting requirements. The survey program, accessible via the Actual Wellbore Properties, is what determines which reports are included.
To print the certified surveys open the File menu, select Print PDF Reports and then select Print Certified Surveys.
Each report comes with its own cover page.
The cover page contains the Operator, Field, Well, Actual Well and Survey names. These are taken from the Database Tree in the main Well Seeker user interface.
It also contains the API Number, which is set in the API Job # field in the Well Data & Personnel section, in the Daily Reports interface.
Above each survey listing are a number of header boxes:
The Field header is populated using data from the Field Properties dialog, accessed via the Database Tree.
The Well header is populated using data from the Well Properties dialog, accessed via the Database Tree.
The Wellbore and Survey Program headers are populated using data from the Field Properties dialog, accessed via the Database Tree.
Provides details regarding the WITS setup and functionality within Well Seeker Pro, and how this can be utilised within the program for remote directional drilling operations.
The following document provides details regarding the WITS setup and functionality within Well Seeker Pro, and how this can be utilised within the program for remote directional drilling operations.
WITS is a standardised format by which wellsite information is transferred e.g. bit depth, hole depth, rpm average etc.
There are 3 types of WITS connection:
WITSML: WITS data transferred to an online server. Costs more, as such rarely used.
UDP WITS: WITS data transferred via a local network, usually an ethernet cable. Less commonly used.
WITS Serial: WITS data transferred via a serial cable.
The WITS data will be taken from the rigs EDR (Electronic Drilling Recorder) system, which will be provided by a company like PASON / TOTCO /NORALIS etc.
Serial WITS uses a seral cable to transfer the data from the EDR (Electronic Data Reader) to WS. The EDR will have a serial port, but it is unlikely that the receiving laptop will have a serial port as these are not very common now in modern computers. As a result, a USB to Serial connection is usually used. This allows the USB end to be plugged into the laptop.
Where DD and MWD computers need a feed, but only one serial cable from the EDR (PASON / TOTCO) is installed, a serial splitter cable can be used
The user will usually require USB to serial RS232 Adapter (which is a box with a USB wire coming out and a serial port) and a null modem cable. The null modem cable is a serial cable which will plug into the EDR serial port and then into the serial port on the adapter. It is important that it is a null modem cable and not a regular serial cable.
UDP & TCP WITS are transmitted via an ethernet (network) cable. The user just plugs in the ethernet cable, finds out which port the data is being sent on and then enters the port number into the WITS data reader. TCP WITS also requires and IP Address.
The following section describes the recommended steps to follow and settings to select when setting up a WITS feed in Well Seeker.
Open the WITS Mapping Dialog via the Tools Menu on the main Well Seeker interface: Tools – WITS Mapping:
Check the WITS mapping prior to setting up the WITS connection. The WITS mapping should be standard but can be obtained from the PASON / TOTCO provider.
Well Seeker’s default Record and Field ID come from WITS zero standard.
WITS will be sent from the rigs PASON / TOTCO system to the Well Seeker Pro computer.
The record ID and field ID must match the settings that PASON / TOTCO is outputting:
For example, PASON / TOTCO is outputting the bit measured depth on record ID 01, field ID 08. We must have the WITS mapping set to the same for bit md, or the computer will not know what the data is, or how to handle it.
Note PASON / TOTCO often outputs the hookload average and WOB average values on the hookload max and WOB max channels. Be aware of this and prepare to change the WITS mapping as required.
Hookload MAX is what is used when populating the PU/SO/ROT weights in the slide sheet.
There is no standard mapping for RAW survey values BX BY BZ, so this is something which will need to be double checked.
Once the user is happy with the setup, hit apply and close.
Open a survey and then open the slide sheet dialog.
Note, the slide sheet option is not available unless you are in a survey.
Select the WITS Survey Options: Settings – WITS Survey Options:
Survey Type: Select the format which the surveys are being received via the WITS feed:
Inc and Azi – Calculated Values.
GxGyGzBxByBz – RAW Values.
Magnetic Units: Only relevant if receiving raw survey data.
Accelerometer Units: Only relevant if receiving raw survey data.
Survey QC Limits: Only relevant if receiving raw survey data and applying Short Collar Correction (SCC).
Auto Send Survey Email: Select this if you require an email update to be automatically sent to the current distribution list defined in the survey email update template. No dialog or outlook window will appear.
Auto Accept Surveys: When a WITS survey is detected at a depth deeper than the last entered survey, it will automatically be accepted and added to the survey listing without prompting the user. Recommend that this is NOT selected.
Use Bit Depth as Survey Depth: If a new WITS survey is detected this option forces the survey depth to be set as the current bit depth.
Include Bit Projection in Survey Email: Allows the user to either include or omit a projection to bit in the survey update email template available from the Tools menu.
Attach Survey Listing to Email: Allows the user to either include or omit the survey listing in the survey update email template available from the Tools menu.
Check for WITS Surveys: When selected Well Seeker will check for and display any WITS Surveys which are received. When unselected, WITS surveys will be ignored.
Via the slide sheet dialog, select the Rig States Option: Tools – Rig States:
Rig States allows the user to configure the thresholds for real time state detection.
Rig States will operate when:
The WITS Data Reader is running (and receiving data), and
The Auto Populate Slide Sheet Option is selected from the Settings Menu.
The below is a guide to initial threshold values, which can be adjusted and fine-tuned as you start to receive data:
RPM: Initially, set this as the oscillating RPM when sliding; however, this is something that will likely need to be adjusted based on operating parameters.
Pump Pressure: 300psi.
Flow Rate: 50gpm.
HKLD: Set at block weight + 20, or something similar.
On Bottom Delta: 0.5ft.
WOB Threshold: 2k or 1T.
The Rig States logic is what Well Seeker uses to determine what is currently happening in the well e.g. Rotating, Sliding, Tripping, Circulating etc. The thresholds will determine at what level certain rig states will be classified. Rig states logic is defined below:
Is the Bit on Bottom?
Is (Bit MD – Hole MD) < On bottom threshold
If on bottom, are you drilling?
Pump Pressure > Threshold
WOB > Threshold
Hookload > Threshold
On bottom recorded when all 3 of the above are recorded = TRUE
If Drilling = TRUE, the logic is as follows
If 10% of the values in the RPM buffer are < Rotating threshold then Sliding
If 10% of the values in the RPM buffer are > Rotating threshold then Rotating
You can also see the current WITS data values received and the resulting rig state conclusions.
Via the slide sheet dialog, open the WITS Data reader: Tools – WITS Data Reader:
If you have a serial box to USB box connected, then you may be able to select a Com port from the drop-down menu.
UDP and TCP WITS will come in over an ethernet cable.
To start reading UDP WITS click on the UDP WITS check box and type in the port.
To start reading TCP WITS click on the TCP WITS check box and type in the port and IP Address.
Leave the Baud Rate as 9600, unless specified by the personnel transmitting the WITS data from the rig.
Start Reading: Will start the software looking for incoming WITS data. If any is found it will be displayed in the WITS Feed Stream.
Stop Reading: Stops looking for WITS data.
If you want to clear all the WITS data in the database click Clear WITS Data. You may want to do this if you have WITS data from a previous well or the database size is getting too big.
Pause Messages: Pauses the messages in the WITS Data Stream. WITS data will continue to be received in the background.
Save Svy and TF Data: This will save the Survey and Toolface data to the database. You need this selected if you want to calculate slide grade and view the slide analysis data.
Note that the slide sheet will populate without this option checked; however, if you want the data saved you must have these selected.
Send Data to Server: Will send the latest WITS data directly to the server database every 1 seconds if checked. Used for unmanned or small crew jobs.
Note, for this option to work, the user must also have entered the ICDS Server IP address, ICDS Server Port number and the Well that they are sending data for in the Real Time Data Exchange dialog, otherwise the data will not be directed to the ICDS.
Send Data Handshake: Leave checked, unless receiving WITS from Noralis.
To utilize all the features available within WS, to allow the slide sheets to be automatically populated, and to receive surveys and tool faces, as a minimum, the following channels need to be received.
There are several features within Well Seeker which can be utilized for remote DD operations. These are detailed below:
DD Dashboard:
Shows the live Toolfaces.
Effective Toolface.
Slide Grade which is effectively calculated from the above 2 points. This is displayed on the slide sheet and not in this dialog.
Last 4 calculated motor yields.
Live Bit projection based on the data entered in the slide sheet and DD Dashboard settings.
3D plot.
WITS Input traces e.g. RPM, SPP, Block height etc.
RT AC.
Rig Gauges.
AC Dashboard.
Rigs Online Dashboard.
For the above features to operate to their full capability, a local WITS input is required, which then needs to be sent on to the ICDS.
In the future we will have the ability to access the remote DD screen via a mobile phone or web browser to allow people to log in to see how the well is progressing.
To receive the WITS data on a remote computer, there needs to be a computer at the rig site with the following setup.
Rig site computer with:
Well Seeker Pro installed.
Principal well plan input.
Actual well with current survey and BHA input.
WITS equipment:
USB to Serial connection.
Serial Splitter.
Null Modem Cable.
WITS/WITSML feed to the rig site computer including:
ICDS IP address and Port number details.
These are required for the Real Time Data Exchange and the Data Fetch features within Well Seeker.
Stable internet connection.
Once there is WITS data streaming to the local rig computer, there are now two potential options for how we update the remote server database:
Well Seeker Pro is setup to send WITS data to the remote server database directly, every 1 second. The remote user can then utilise the WITS data to auto populate the slide sheets and perform all the required DD operations via their remote computer.
Local Rig Database User
Open the Real Time Data Exchange, fill in ICDS server IP and Port number details and select the current well.
Check the Send Data to Server box in the WITS Reader dialog. Start reading. WITS data is now being sent to the ICDS and on to the remote server database.
For this setup, the user does NOT need to Start the data exchange.
Remote Server Database User
Monitor incoming WITS feeds via the Rigs Online Dashboard and selecting File - Show WITS Connections.
Set the Rig States Thresholds in the rig states dialog.
Select the Auto Populate Slide Sheet radio button in the slide sheet toolbar. The WITS data populates the slide sheet and surveys.
The DD Dashboard will automatically update with real time projection to bit, anti-collision for the projection to bit, 3D plot and drilling parameters chart.
Data from the slide sheet can be used to one click populate the daily activity section of the daily reports (Get DDR from Run Sheet).
Based upon daily reporting data, KPIs and data analytics can be utilised in real time.
Well Seeker Pro is set up to auto populate the slide sheet on the local computer and then sends updates via the Real Time Data Exchange dialog to the remote server database, up to every 1 minute, or when manually pushed. DD operations are therefore performed locally at the rig site. This way remote users will have constant access to up to date data. WITS data can also be pushed back to the ICDS every second to allow the remote user to utilise the rig gauges and WITS traces.
Local Rig Database User
Opens the Real Time Data Exchange, fills in ICDS server IP and Port number details, selects the current well and either starts a data transfer by automatic update rate, or by a manual push
Check the Send Data to Server box in the WITS Reader dialog. Start reading. WITS data is now being sent to the ICDS and on to the remote server database.
Set the Rig States Thresholds in the rig states dialog.
Select the Auto Populate Slide Sheet radio button on the slide sheet toolbar. The WITS data populates the slide sheet and surveys.
The DD Dashboard will automatically update with real time projection to bit, anti-collision for the projection to bit, 3D plot and drilling parameters chart.
Data from the slide sheet can be used to one click populate the daily activity section of the daily reports (Get DDR from Run Sheet).
Remote Server Database User
Monitoring incoming data exchanges via the Rigs Online Dashboard. Each time the rig transfers data (surveys, slide sheets, daily reports etc) via the Real Time Data Exchange, the remote server database is updated with the same data as the local rig database for the given well.
Monitor incoming WITS data via the rig gauges or the WITS traces in the DD Dashboard.
Based upon daily reporting data, KPIs and data analytics can be utilised in real time.
This can be accessed via the main Well Seeker interface by selecting Tools – Real Time Data Exchange.
The real time data exchange is where the local rig database user inputs the following:
ICDS Server IP address.
ICDS Server Port number.
The Well that they are sending data for.
If these are not filled in, the WITS data will not be directed to the remote server database.
When running the operation remotely, you DO NOT need to start the data exchange.
When running the operation locally, you need to start the data exchange at a given update rate or select Manual Push every time you wish to push data from the local rig database to the remote server database:
Select the relevant survey and open the slide sheet. Tools > Slide Sheet.
Within the slide sheet select Tools > WITS Data Reader.
Check the Send Data to Server cell. This will send the latest WITS data to the ICDS and on to the server database every 1 seconds if checked.
This should be set up for BOTH local and remote operations.
For both local and remote operations, once the appropriate WITS feed is being received and transmitted, the user then needs to select to auto populate the slide sheet:
Settings – Auto Populate Slide Sheet.
Settings – Auto Populate Parameters.
The slide sheet will now begin to automatically populate as the data is received.
While this option is enabled, the user will NOT be able to manually add or adjust anything on the slide sheet.
If it is necessary to adjust the slide sheet for any reason, this can be done by temporarily turning off the auto populate option, making the appropriate adjustment and then turning it back on again.
The DD Dashboard is accessed via the Slide Sheet and provides an interface containing tools a directional driller can utilize while drilling a well either locally on the rig or remotely from an RTOC.
The DD Dashboard will automatically update based upon the following data:
The survey Record.
Real Time WITS data being received.
Slide sheet being set to auto populate.
The DD Dashboard contains the following information:
A Tool Face Rose which displays:
GTF & MTF values received via WITS.
Effective Toolface, calculated from the above inputs.
Bit Projection which is calculated based on the data entered into the slide sheet.
Target window for Vertical (Circle) and Lateral (Rectangle) modes.
Offset Wells.
Real Time Anti-collision for bit projection which displays C-C distance and Separation Factor and the relevant warnings against the following:
Principal Plan.
Offset Wells.
Lease Lines.
Last 4 surveys along with the Slide Seen and Motor Yield for each one
Projections:
Projection to Bit which is automatically updated based on data entered into the slide sheet. When auto populate slide sheet is selected, this is updated in real time.
Landing Projection, which is calculated when Curve Mode is activated.
Two additional Projections, which are calculated when Vertical and Lateral Modes are activated.
Real time 3D plot showing:
Actual surveys with appended projection to bit.
Principal Plan.
Offset Wells.
Lease Lines.
Surveys points.
Slide and Rotary Intervals.
Drilling parameters charts populated from the WITS data feed plot:
RPM.
Pump Pressure.
WOB.
Block Position.
Flow.
Hookload.
ROP.
Torque.
Differential Pressure.
Within the DD Dashboard, the user can select from 4 different modes, which are accessed and selected via the settings menu:
No Mode
No additional features activated.
Vertical Mode
Red Tolerance Circle is drawn on the rose bud (diameter can be set in the settings).
2 Projections are added (in addition to the bit projection) and will show on the rosebud and 3d view. Distances can be adjusted in settings.
Rotary walk and build can be set in the settings. Inc Rotary in Proj option must be selected for these to do anything.
If rotary is not included the additional projections will straight line and the rotary sections in the bit projection will also straight line.
A tool face back to plan will be displayed in the top left hand corner along with a slide distance to achieve the Max DLS (this value is set in the settings) the slide length is based on the stand length (also in settings).
Nudge Mode
This mode does not currently do anything.
Curve Mode
No tolerance box or circle is displayed.
A new projection is calculated to the TVD INC AZI specified in the landing target section of the dashboard settings.
The user can use the drop-down list or the find landing button in the settings dialog to quickly find / adjust the landing target.
The DLS to land will show in the top left along with the required tool face and slide distance (based on the motor yield and stand length curve in the settings).
The last Motor yield will also show at the bottom. If this is within 90% of the DLS to land it will be red, if it is within 75% it will be orange otherwise green.
Lateral mode
The same as Vertical mode except that it draws a rectangle as the tolerance box rather than a circle (lateral up/down/left/right tolerance can be set in the settings).
Well Seeker Pro’s reporting package allows the input, collection and analysis of drilling data. However, when an organization does not have a user at the drilling site to input all of the reporting information, such as a tool rental job, it has historically been difficult to keep a record of the run data for the tools used. Using end of run data provided by the renter, there is now a feature available that allows the user to input this condensed data into Well Seeker, which can then be viewed in the Well Analytics Motor and MWD KPI reports. This option is detailed below
Drill String Editor dialog - Input relevant BHAs
Daily Report dialog - Select correct Report Options
Well Data & Personnel dialog - Input relevant job details
Daily Report dialog - Input a row in the Daily Activity section for each relevant BHA
Drill String Editor dialog - Input relevant tools and run details
Performance Report dialog - Input relevant run details
These run details will now be visible within the Analytics Motor and MWD KPI reports, without having had to input all of the daily reports activity data covering the runs in question. The following section will provide more details regarding each of the steps in the above sequence.
Description
BHA #
Get Slide Rotate Hours from Activity
Auto Update Motor Report Params
Auto Update BHA Hours on save
If the user has any of these options selected, when the user selects save in the specific well’s Daily Reports dialog, it will overwrite any run data that has been entered in the Drill String Editor and Performance Report dialogs for that specific well.
Open the Well Data & Personnel dialog from within the Daily Reports dialog, by selecting Well Data > Well Data and Personnel. Input the data as follows:
Job #
API Job #
Rig
Target Formation
Any other relevant information
Select Apply
Add a row for each BHA that you want to include in the Daily Activity section. Input the data as follows:
End Time > Start Time. The actually end time is not important and is not used in the run data
Select the relevant BHA in the BHA column
Select the relevant Phase to associate with the BHA
Select an Activity. It does not matter what activity code is selected
In the Description cell enter Motor Rental Job
MWD # if relevant
Depth In
Depth Out
Date In
Date Out
Formation if known
Comments as required
Add a Drill Bit component. This must be added. Input the Drilling Hours and Circ Hours for the run within the Component Properties for the bit
Add a Motor component. This must be added, even if a motor was not run. Input any relevant data in to the Component Properties section
Add any other rental components. Input any relevant data in to the Component Properties section
Once the above processes have been carried out the user can view the relevant run data within the Well Analytics Motor and MWD KPI reports
A guide to the Analytics module in Well Seeker Pro
The purpose of this document is to introduce the user to the Well Analytics module features within Well Seeker Pro. It has been assumed that the user has already installed Well Seeker Pro, has a valid license that gives them access to the Well Analytics features and has a database structure in place ranging from Operator to Actual Well level.
The Well Analytics tool allows the user to search through their database and select wells based on various search criteria. The user can then plot these wells on google maps in the Maps tab or compare them using several KPI metrics. This tool is most powerful when combined with the Reporting license feature.
On the left of the Well Analytics window is the database tree. This tree contains every actual well and well plan in the database. Clicking on the check box beside each well enables them to be included in the Map and KPI tab. The user can select these wells manually or using the filtering tools in the Search tab.
The workflow for the Well Analytics tool follows the sequence below:
Activate one or more search fields in the Search Tab by clicking on the checkbox beside each one.
For each field, pick an option from the drop-down box.
Click on the Search button. Any wells that match the search criteria will be displayed in the Wells section at the bottom of the window. The user can also check the Ignore Offsets option. This filters out any wells without daily reporting data.
When the user is happy with the search results, they can click on the Select Wells button to select them in the database tree. The user can manually add or remove wells by clicking on them in the database tree.
Wells selected in the database tree can then be displayed in the Map tab, used to generate KPI charts in the KPI Tab or used to generate reports in the KPI Reports menu.
Details for the tabs and menus are shown in the following sections:
The search tab contains several options which can be used to quickly filter through the data in the database tree to find the relevant information. Each field must be activated using the checkbox to its right.
Operator: Allows the user to filter their search for a given operator.
Date Range: Allows the user to filter their search based on start and end dates. The start and end dates which Well Seeker searches for are the ones associated with the daily reports for each individual well.
Distance from Well: Enter a decimal latitude and longitude into the Lat and Long boxes, and then a radius into the Dist box. Well Seeker will include any wells in the database which are the radius entered. The user can also select a well from the dropdown boxes – this will populate the Lat and Long boxes with the surface location of the selected well.
Drilling Parameters: Allows the user to search for wells that contain the entered drilling parameter. Currently only RPM is available.
Formation: Allows the user to filter their search for wells that are targeting a selected formation. The formation which Well Seeker searches for is the one entered in the Well Data & Personnel dialog in the daily report.
Assembly Type: Allows the user to filter their search for wells with the selected BHA type. Options available from the drop-down menu are Motor, RSS and Rotary. A BHA is defined as a Motor or RSS BHA if there is a motor or RSS present for the BHA in the Drill String Editor. A BHA can then be assigned to a well in the Daily Activity section of the Daily Report.
Failure: Allows the user to filter their search for wells which had a BHA failure. The failure type can be MWD, Motor or Any. Whether or not a BHA failed is defined in the Performance.
State: Allows the user to filter their search for wells in the selected US state. The state is assigned in the Well Data & Personnel dialog in the daily report.
Job Number: Filter the search using job number. The job number is assigned in the Well Data & Personnel dialog in the daily report.
Directional Company: Filter the search using the directional company. The directional company is assigned in the Well Data & Personnel dialog in the daily report.
Well Status: Filter the search using the well status. The well status is assigned on the main userinterface in the Daily Reports window.
Rig: Filter the search using the rig used to drill the well. The rig for a well is defined by the selection in the Well Data & Personnel dialog in the daily report.
Motor SN: Filter the search for a particular mud motor serial number. The mud motor serial number is defined by the SN of the motor in the Drill String Editor.
County: Filter the search using the county. The county that a well is in is defined by the selection in the Well Data & Personnel dialog in the daily report.
Motor Make: Filter the search using the motor make. The motor make is taken from the motor component details in the Drill String Editor.
Bit Make: Filter the search using the bit make. The bit make is taken from the motor component details in the Drill String Editor.
LIH (Lost in Hole): Allows the user to filter their search for failures that resulted in a BHA being lost in hole. For a BHA to be flagged as LIH, the LIH checkbox must be checked in the Failure Information section of the Performance Report.
Hole Size: Allows the user to filter their search for wells that drilled a section with the selected hole size. The hole size is set by the OD of the bit in the Drill String Editor.
Motor Config: Allows the user to search by the selected motor lobes and stages. These are set in the Component Properties section for the motor in the Drill String Editor.
Serial Number: Allows the user to search for wells containing tools with the matching serial number. The serial number is set in the Component Properties section for any tool in the Drill String Editor. Serial numbers entered in the Tool Inventory do not count.
Incidents/Failures: Searches for wells that have the Failed option checked in the Performance Report in the Drill String Editor. If CLOSED is selected in the drop-down box, then the results will only show wells where the Closed option has been checked in the Performance Report. If OPEN is selected then the results will only show wells where the Closed option has NOT been checked.
Chargeback: Searches for wells that have any text entered in the Chargeback section in the Performance Report in the Drill String Editor.
Once the desired filters have been selected, the user can then choose from one of the following options:
Search: Any well that matches all the filters will appear in the Wells section below.
Clear Results: Clears all wells from the Wells section.
Reset Filters: Clears all search filters.
Select Wells: All wells currently in the Wells section, and set as included, will be selected in the Database Tree, allowing them to be used in the Maps and KPI tab.
Deselect Wells: Clears the selections made in the Database Tree.
Check All: Toggles the Include column on for all wells in the Wells section. Wells with Include toggled off will not be selected when the Select Wells button is clicked.
Uncheck all: Toggles the Include column off for all wells in the Wells section. Wells with Include toggled off will not be selected when the Select Wells button is clicked.
Open Job: Selecting a well in the Wells section and then clicking Open Job will close the Analytics window and open the well in the main database tree.
Map Options:
Well Paths: Displays the well path of selected wells on the map tab. Note that this will always show the surveys but will only show the plans if the Show planned well paths option is selected as well.
Lease Lines: If any of the selected wells have lease lines associated with them, selecting this option will display them on the map.
Well Names: Displays the well names of selected wells on the map. Note, the names will display at the wellhead.
Planned wells: Displays the well paths of selected plans on the map, so long as Show well paths on map is selected.
Database QC Report
Clicking on the Print button in the Database QC Report section will generate an Excel spreadsheet that contains statistics for all wells selected in the Database Tree. The QC report contains the following information:
The Map tab displays the selected wells on Google Maps. Surveys are displayed in Blue and Well Plans are displayed in Green. Note that Google Maps references the WGS 84 Mercator projection, so any wells referenced to a CRS which does not use this projection, may be offset slightly on the map.
How the wells are displayed on the map can be customised using options found on the Search tab (see previous section).
The KPI tab allows the user to quickly generate a variety of KPI charts for the selected wells. The data used to generate these charts is taken from the daily reports and BHA’s associated with each of these wells.
Generate KPI: Generates all the KPI charts for the selected wells.
Export: Creates an excel document containing the data used to generate the currently selected chart
White Chart: Changes the background of the charts from black to white.
Sanitised: Instantly sanitises the names displayed along the X axis of the charts.
Short Names: Shortens names in the X axis be removing the rig name.
Sort Data: Sorts the data in the chart so that the smallest value is on the left and the largest on the right.
Select KPI: This dropdown menu allows the user to select from the following list of KPI charts:
Phase: When in the appropriate KPI chart, the user can select to either view the Well data or any one of the available Phases from this dropdown menu.
Motor KPI: Once a search has been completed this button may be selected. Creates an excel motor KPI report, containing statistics for all motors used in the filtered wells that appear in the Wells section.
Motor KPI Summary: Once a search has been completed this button may be selected. Creates an excel motor KPI report for the filtered wells that appear in the Wells section. This is like the Motor KPI report but instead of listing individual motors is summarises them by manufacturer, size and state.
MWD KPI: Once a search has been completed this button may be selected. Creates an excel MWD KPI report, containing statistics for all MWD tools used in the filtered wells that appear in the Wells section.
Section KPI: Once a search has been completed this button may be selected. Creates an excel report containing statistics for each drilling phase in the filtered wells that appear in the Wells section.
Revenue Report: Only functions when a Date Range filter has been applied in the Search tab. This report lists every job running on each day inside the date range, along with the total revenue and number of rigs for each day.
Rig Days Report: Only functions when a Date Range filter has been applied in the Search tab. This report lists every job running on each day inside the date range, along with the number of rigs, the 30-day average rigs and the 10-day average rigs for each day.
Personnel Report: Only functions when a Date Range filter has been applied in the Search tab. Creates an excel personnel report for all wells within the date range. This lists all personnel in the database and shows the days that they worked within the set date range.
Rig Days Chart: Displays a chart generated using data from the Rig Days Report.
Revenue Chart: Displays a chart generated using data from the Revenue Report.
Well Ranking: Generates a Well Ranking report from the filtered wells that appear in the Wells section. This report shows which out of the selected wells performed the best in several different categories, as well as an overall score between 0 and 1 based on the performance of each well over all categories.
Well Ranking Weights: Allows the user to set how much each category affects the overall score of a well in the Well Ranking report. The user should enter a value between 0 and 1 in the Weight column. The user can also exclude a category from affecting the overall score entirely by unchecking the checkbox in the Included column.
Drill Records: This option is only available when connected to a remote server database. Opens the Drilling Records dialog, which allows the user to create a report containing rankings of the wells that have performed best in selected KPIs.
The user should choose the report format (Excel or PDF) from the Report Type drop-down. The number in the # Results box sets how many results are in each ranking – for example a value of 5 will mean each ranking lists the top 5 wells.
The user should select the KPIs that they want to create rankings for in the KPI column. Currently there are four KPIs to choose from – fastest section, fastest ROP, longest section, and max footage per day. The user can optionally limit each ranking to a single phase and/or hole size if they wish, by choosing a value from the dropdowns in the Phase and Hole Size columns.
Checking the Inc Non Drlg Hrs checkbox will factor non-drilling hours into the rankings. The Active column can be toggled off to disable a ranking and remove it from the report.
Once the user is happy with their setup, they can generate the report by clicking on the Create button.
Get well list from search grid: If this option is toggled on, reports generated from the KPI Reports Menu will be populated with wells in the Wells section. If it is toggled off, the reports will be populated by the wells that have been selected in the Database Tree.
The context menu is available in every plot by right clicking anywhere on the plot. This allows the user to change certain aspects of the plot based on their requirements. The contents of the menu will vary depending upon the chart selected.
Viewing Style – Allows the user to select the desired Chart style
Border Style – Allows the user to select the desired Border style of the chart
Font Size – Allows the user to select the desired font size, which will affect all fonts on the chart including title and axis labels. Large, Medium or Small
Show Legend – Allows the user to toggle the chart legend on and off
Legend Style – Allows the user to select the Legend style. There are 6 options, including Hide Legend
Numeric Precision – Allows the user to select the number of decimal places the numbers in the plots are referenced to. Zero to 3 d.p
Plotting Method – Allows the user to select the way the line is plotted: Point, Line, Bar, Points + Line, Spline Area
Data Shadows – Allows the user to select between off, shadow and 3D
Gradient Styles – Allows the user to select the gradient graphic on a pie chart
Data Labels as – Allows the user to select the labels as a percentage or as the actual value
Group Percentages – User can select the percentage threshold below which a segment in a pie chart will be grouped as other
Grid Options – Allows the user to change the grid options in the chart
Graph and/or Table – Allows the user to view the chart only, table only or both at the same time
Point Label Orientation – Allows the user to select the orientation of the X axis series labels
Include Data Labels – Allows the user to add data labels to the chart
Mark Data Points – Adds the data points relating to the data labels
Undo Zoom – Resets the zoom on the chart. Pressing the Z button has the same effect
Customization Dialog – Opens a dialog that allows the user to chart titles, axis min and max values, fonts, line colour and styles
Maximise – Maximises the chart to fill the screen. Escape button exits this view
Export Dialog – Allows the user to Export the chart using multiple image formats: EMF, WMF, BMP, JPG and PNG. The user has 3 options:
Clipboard: exports directly to clipboard, allowing images to be quickly added to word, excel & PowerPoint documents
File: Creates an image file of the chart which can be used on its own or imported into any suitable document
Printer: Sends the chart to the printer
The user can also choose the relevant Width, Pixels and DPI to use for the export. For Clipboard and File options, Pixels is the only available selection. When Printer is selected, the Millimeters, Inches and Points options become available to select.
X Axis on Top – Moves the labelled X axis from the bottom to the top
Y Axis on Top – Moves the labelled Y axis from the left to the right
Additional X Axis – Adds an additional labelled X axis
Additional Y axis – Adds an additional labelled Y axis
Print current chart Excel/PDF: Prints the last viewed KPI chart as an image in an Excel or PDF document.
Print all charts Excel/PDF: Export all KPI charts as images in a single Excel or PDF document,
Export all chart data: Exports all KPI charts as data tables in an Excel document.
Exit: Close the Well Analytics window.
Expand All: Expands the Database Tree to show every well in the database.
Collapse All: Collapses the Database Tree so that no wells are visible.
Hide Tree: Removes the Database Tree section from the Analytics window so that the user can view the map and the KPI charts easier. Click on Hide Tree again to bring the Database Tree back.
Select Wells: All wells currently in the Wells section, and set as included, will be selected in the Database Tree, allowing them to be used in the Maps and KPI tab.
Deselect Wells: Clears the selections made in the Database Tree.
Search: Any well that matches all the filters will appear in the Wells section.
Clear Results: Clears all wells from the Wells section.
Reset Filters: Clears all search filters.
Remove Flat Time at Start: Removes any time when there is no change in depth at the start of the Depth V Days KPI chart. The Generate KPI button needs to be clicked before any changes are applied.
Remove all flat time: Removes any time when there is no change in depth at any point in the Depth V Days KPI chart. The Generate KPI button needs to be clicked before any changes are applied.
A: Please make sure that you have administrator rights for the PC that you are installing to. For a step by step guide for software installation please see the documents IDI06-011C - Well Seeker PRO - Installation Guide and IDI06-010C - Engineering - Installation Guide. Both can be downloaded from our website at the following location: . In the unlikely event that you are still experiencing issues installing the software please contact us at .
Once you have located this file, send it to , along with your current database and an explanation of the issue you are having.
A: This error is related to windows updates which have not installed properly and may not be isolated to just Innova’s software. The only way to address this is to remove the program via the Add / Remove programs tool and then reinstall. The latest install files can be downloaded from Innova’s website . Removing and reinstalling the program should only take around 10 minutes to do.
If the issue is not resolved, please contact Innova support at .
Firstly, the user must have purchased a valid license from NOAA. Innova do not supply these licenses and the user must contact NOAA directly () to organize this.
Firstly, the user must have purchased a valid license from MagVAR. Innova do not supply these licenses and the user must contact MagVAR directly () to organize this.
Firstly, the user must have purchased a valid license from BGS. Innova do not supply these licenses and the user must contact BGS directly () to organize this.
Click Email MAC Address and send the mail along with the relevant BGGM license details to BGS ()
A second file called bggm32_v3_8.dll is also required in the magnetics folder. This file is provided by Innova. Once the user has purchased the multiuser license from BGS, they should contact Innova () to receive the second file.
This document assumes that Well Seeker Pro has already been installed (), and that the user is familiar with the daily reporting features ().
If the Oasis Integration check box is empty, then the user will not be able to access these features and should contact to organise a new license. Note, that as the Oasis integration is part of the daily reporting module, the user will also require this license to be turned on as well.
In order to synchronize a well’s Job Number and Rig details between Oasis and Well Seeker Pro, navigate to the Wells List page, right click on the well of interest and select Get Oasis job info.
The remote data fetch is a tool used by the field user to pull a copy of a specific well and it’s offset data from the Innova server database to their local PC. Pull down the required well on to the local PC. For more details on the Remote Data Fetch function see the following .
Note that the Rig States dialog requires an incoming WITS or WITSML feed to function properly. For details on setting up a WITS/WITSML feed, see the following guide: .
In the Slide Sheet window, open the Rig States dialog by clicking on the icon in the toolbar, or by going to Tools > Rig States.
If a channel is not receiving data, it will display a null value of -9999.25. If one or more channels are displaying this value, it could indicate that the WITS channels have not been mapped correctly. Consult with the rig and change the WITS mapping by going to Tools >> WITS Mapping. For more detailed information on WITS mapping, refer to the following guide: .
Attach the debugging file, log file and screen capture file to an email, and send it to .
For this feature to work, the user requires a stable internet connection and an Actual Well / Survey setup in the Well Seeker database tree. For detailed steps regarding how to achieve this, refer to the .
The Solo Cloud dialog will open. In the Object Explorer section, your organization name should display below Solo Cloud. If it does not, confirm that the ICDS Server IP and Port values in the Real Time Data Exchange dialog are correct. Input valid Username and Password credentials for the relevant Solo Cloud server, then click on the Connect button in the toolbar. These credentials should be obtained from your Solo Cloud provider. Once entered the Username and Password will be saved and used for all surveys present below the Actual Well.
For this feature to work, the user requires a stable internet connection and an actual well and survey already set up in the Well Seeker database tree. For detailed steps regarding how to achieve this, refer to the .
4. Click on Get Wells to open the Well Selection dialog. Depending on your provider, the Well Selection dialog will look slightly different.
6. Click on Sync Surveys to check if any new surveys are available from your selected provider. If there are, the user will be given the option to update the survey list in Well Seeker. Click on Yes to update your survey sheet.
8. Click on Save to save your settings, and then click on the X in the top right of the window to close. To close without saving your settings, click on Cancel.
If the user has an API number for the well entered in the Daily Reporting section of Well Seeker, when the Get Wells button is clicked, Well Seeker will look up the API number on the Superior QC server and automatically select the correct well.
Clicking on Check Well Data will compare the latitude, longitude, magnetic field strength, dip, declination and grid convergence values stored on the Superior QC server, with the values referenced in Well Seeker. If they do not match, a warning box similar to the image below will appear.
For this feature to work, the user is required to have a relevant actual well already set up in the Well Seeker database tree. For detailed steps regarding how to achieve this, refer to the .
Open the Drill String Editor dialog, by selecting the relevant actual wellbore in the database tree and either right clicking, Reporting > Drill String Editor, or selecting the Drill String Editor icon from the toolbar . Add a BHA by selecting File > Add New, or the green add icon from the toolbar . Input the data as follows:
Repeat this process for each BHA to be included in the well, ensuring that each BHA is saved by selecting the save icon .
Close the Drill String Editor dialog by selecting File > Exit, or the close icon .
Open the Daily Reports dialog, by selecting the relevant actual wellbore in the database tree and either right clicking, Reporting > Daily Reporting, or selecting the Daily Reporting icon from the toolbar . From the Daily Report dialog, select Report Options. Ensure that the below options are unchecked:
At this stage you can also select the relevant Well Status to improve filtering these wells when using the analytics tools. Select the Save icon .
Add a new daily report by selecting the File > Add Daily Report, or the green add icon from the toolbar .
Select the Save icon
Close the Daily Reports dialog by selecting File > Exit, or the close icon .
Open the Drill String Editor dialog, by selecting the relevant actual wellbore in the database tree and either right clicking, Reporting > Drill String Editor, or selecting the Drill String Editor icon from the toolbar . For each BHA, input the data as follows:
Repeat this process for each BHA, ensuring that each BHA is saved by selecting the save icon .
Open the Performance dialog from within the Drill String Editor dialog, by selecting Performance Report > Edit Data, or selecting the Performance Report icon from the toolbar . For each BHA, input any relevant run data. Repeat this process for each BHA to be included in the well, ensuring that each BHA is saved by selecting the save icon .
WOB
STANDPIPE PRESSURE
RPM
MAGNETIC TF
TOTAL GPM
GRAVITY TF
BIT DEPTH
SURVEY MD
HOLE DEPTH
SURVEY INC
HOOKLOAD
SURVEY AZI
Block Position
Torque (Optional)
ROP (Optional)
WOB
STANDPIPE PRESSURE
RPM
MAGNETIC TF
TOTAL GPM
GRAVITY TF
BIT DEPTH
SURVEY MD
HOLE DEPTH
SURVEY INC
HOOKLOAD
SURVEY AZI
Block Position
Torque (Optional)
ROP (Optional)
Operator
Field
Facility
Well
Actual / Planned Well Name
CRS / Map Grid
Well Latitude (Decimal)
Well Longitude (Decimal)
Well Latitude (DD MM SS)
Well Longitude (DD MM SS)
Well Grid North
Well Grid East
BHL (Bottom Hole Location) Latitude (Decimal)
BHL Longitude (Decimal)
BHL Latitude (DD MM SS)
BHL Longitude (DD MM SS)BHL Grid North
BHL Grid East
BHL TVD
Depth Datum
Datum Elevation
System Datum
System Datum Elevation
North Reference
Local Co-ordinate Reference
Vertical Section Azimuth
Slide & Rotation Footage
Depth V Time
Failure Analysis
Directional Cost Per Foot
Well Cost Per Foot
BHA Details
Detailed Cost Breakdown
Wells by Formation
Activity Comparison
Wells by Rig
Parameter Comparison
Average Interval Cost by Quarter
Footage per Day by Operator
Wells by Directional Company
Wells by Motor Make
Wells by Bit Make
ROP & Footage by Formation
ROP & Footage by Directional Company
ROP & Footage by Motor Make
ROP & Footage by Bit Make
ROP & Footage by Hole Size
Phase Comparison
ROP & Footage by Rig
Well / Section Performance
Driller Performance
Footage per Day by Rig
A selection of guides for setting up and maintaining a remote cloud-based database using Amazon AWS or Microsoft Azure.
A selection of guides for using the features in the Innova Mobile App and Web Portal
A selection of guides that cover the configuration of Innova ICP API functionality with other software and services.
The full Well Seeker Pro maunal.
IMPORTANT NOTICE: PLEASE READ CAREFULLY BEFORE INSTALLING THE SOFTWARE: This licence agreement (Licence) is a legal agreement between you (Licensee or you) and Innova Drilling and Intervention Limited of Union Plaza, 1 Union Wynd, Aberdeen, AB10 1DQ (Licensor, we or us) for the software (being one or more of Well Seeker PRO or Innova Engineering) (Software) which you have selected to either trial or purchase , which includes computer software, the data supplied with it, the associated media, and electronic documentation comprising the Installation Guide, the details of the Software available from the Licensor’s website and the PDF user manual provided with the download of the Software (Documentation).
THIS SOFTWARE REQUIRES (1) A COMPUTER WITH A MINIMUM OF 2Gb RAM AND 500MB HARD DRIVE, (2) MICROSOFT WINDOWS 7, 8 OR 10 OPERATING SYSTEM AND (3) MICROSOFT EXCEL.
BY CLICKING ON THE "AGREE" BUTTON BELOW YOU AGREE TO THE TERMS OF THIS LICENCE WHICH WILL BIND YOU AND YOUR EMPLOYEES. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENCE, WE ARE UNWILLING TO LICENSE THE SOFTWARE TO YOU AND YOU MUST DISCONTINUE INSTALLATION OF THE SOFTWARE NOW BY CLICKING ON THE "I DO NOT AGREE" BUTTON BELOW. IN THIS CASE YOU MUST RETURN THE MEDIUM ON WHICH THE SOFTWARE IS STORED AND ALL ACCOMPANYING DOCUMENTATION TO US WITHIN 30 DAYS OF PURCHASE. IF YOU DO THIS YOUR LICENCE FEE WILL BE REFUNDED.
1. GRANT AND SCOPE OF LICENCE
1.1 In consideration of payment of an annual licence fee (except where the Software is downloaded on a trial basis), the Licensor hereby grants to you a non-exclusive, non-transferable licence to use the Software and the Documentation on the terms of this Licence. If you do not renew your licence fee in one year, your licence will come to an end one year from the date of download of the Software and your licence to use the Software will automatically come to an end. If you have selected the option to trial the Software, your licence to trial the Software is subject to the terms of this Licence and your licence to use the Software will come to an end thirty days from the date of download of the Software. You may only use the Software under a trial period once.
1.2 You may:
(a) install and use the Software for your internal business purposes only on one physical CPU;
(b) transfer the Software from one computer to another provided it is used on only one computer at any one time;
(c) receive and use any free supplementary critical software code or update of the Software incorporating "patches" and corrections of critical errors as may be provided by the Licensor from time to time; and
(d) use any Documentation in support of the use permitted under condition 1.1 as is reasonably necessary for its lawful use.
2. LICENSEE'S UNDERTAKINGS
2.1 Except as expressly set out in this Licence or as permitted by any local law, you undertake:
(a) not to copy the Software or Documentation except where such copying is incidental to normal use of the Software or where it is necessary for the purpose of back-up or operational security;
(b) not to rent, lease, sub-license, loan, translate, merge, adapt, vary or modify the Software or Documentation;
(c) not to make alterations to, or modifications of, the whole or any part of the Software nor permit the Software or any part of it to be combined with, or become incorporated in, any other programs;
(d) not to disassemble, de-compile, reverse engineer or create derivative works based on the whole or any part of the Software nor attempt to do any such things except to the extent that (by virtue of section 296A of the Copyright, Designs and Patents Act 1988) such actions cannot be prohibited because they are essential for the purpose of achieving inter-operability of the Software with another software program, and provided that the information obtained by you during such activities:
(i) is used only for the purpose of achieving inter-operability of the Software with another software program;
(ii) is not disclosed or communicated without the Licensor's prior written consent to any third party to whom it is not necessary to disclose or communicate it; and
(iii) is not used to create any software which is substantially similar to the Software;
(e) to keep all copies of the Software secure and to maintain accurate and up-to-date records of the number and locations of all copies of the Software;
(f) to supervise and control use of the Software and ensure that the Software is used by your employees and representatives in accordance with the terms of this Licence;
(g) to include the copyright notice of the Licensor on all entire and partial copies of the Software in any form;
(h) not to provide, or otherwise make available, the Software in any form, in whole or in part (including, but not limited to, program listings, object and source program listings, object code and source code) to any person other than your employees without prior written consent from the Licensor;
(i) not to use the Software via any communications network or by means of remote access.
2.2 You must permit the Licensor and his representatives, at all reasonable times and on reasonable advance notice, to inspect and have access to any premises, and to the computer equipment located there, at which the Software or the Documentation is being kept or used, and any records kept pursuant to this Licence, for the purpose of ensuring that you are complying with the terms of this Licence.
2.3 You confirm and warrant that you will not use or permit the use of the Software (whether through permission or act of omission) in any way which would breach (directly or indirectly) EU restrictive measures, including but not limited to financial and economic sanctions or the same as implemented by European Union member states.
2.4 You confirm and warrant that you will not use or permit the use of the Software (whether through permission or act of omission) in any way which would breach (directly or indirectly) U.S. restrictive measures, including but not limited to financial and economic sanctions or the same as implemented by the United States of America.
2.5 You shall indemnify us against any losses, liabilities, penalties, damages, costs, claims and expenses (including but not limited to legal fees and investigation expenses) incurred by, or awarded against, us as a result of any breach of the warranties set out in condition 2.3 or 2.4 by you or your associated persons, any person working for you or any third party retained by you.
3. SUPPORT
The Licensor's technical support staff will endeavour to answer by telephone any queries which you may have regarding the use or application of the Software. For telephone support please contact the support email support@innova-drilling.com between the hours of 09:00 and 17:00 Monday – Friday.
4. INTELLECTUAL PROPERTY RIGHTS
4.1 You acknowledge that all intellectual property rights in the Software and the Documentation throughout the world belong to the Licensor, that rights in the Software are licensed (not sold) to you, and that you have no rights in, or to, the Software or the Documentation other than the right to use them in accordance with the terms of this Licence.
4.2 You acknowledge that you have no right to have access to the Software in source code form or in unlocked coding or with comments.
5. WARRANTY
5.1 The Licensor warrants that:
(a) the medium on which the Software is stored and distributed is (at the time it is supplied), and will be for the period of 90 days after that time (Warranty Period), free from defects in design, material and workmanship under normal use. If a defect in the medium occurs during the Warranty Period, the Licensor will replace it free of charge if you return it to the Licensor with proof of purchase and (so far as you are able) a documented example of such defect or error;
(b) always subject to condition 5.2 and 5.3, during the Warranty Period, the Software will, when properly used, perform substantially in accordance with the functions described in the Documentation (provided that the Software is properly used on the computer and with the operating system for which it was designed as referred to in the accompanying documentation), and the Documentation correctly describes the operation of the Software in all material respects; and
(c) it has tested the Software for viruses using commercially available virus-checking software, consistent with current industry practice.
5.2 YOU ACKNOWLEDGE THAT THE SOFTWARE HAS NOT BEEN DEVELOPED TO MEET YOUR INDIVIDUAL REQUIREMENTS AND THAT IT IS THEREFORE YOUR RESPONSIBILITY TO ENSURE THAT THE FACILITIES AND FUNCTIONS OF THE SOFTWARE AS DESCRIBED IN THE DOCUMENTATION MEET YOUR REQUIREMENTS.
5.3 YOU ACKNOWLEDGE THAT THE SOFTWARE MAY NOT BE FREE OF BUGS OR ERRORS AND YOU AGREE THAT THE EXISTENCE OF ERRORS SHALL NOT CONSTITUTE A BREACH OF THIS LICENCE. WE DO NOT WARRANT THAT THE CONTENT OF THE SOFTWARE IS ACCURATE, CURRENT OR ERROR-FREE AND WE EXPRESSLY DISCLAIM ANY WARRANTY OR REPRESENTATION AS TO THE ACCURACY OF THE CONTENT OF THE SOFTWARE AND DUE TO THE NATURE OF THE SOFTWARE, YOU AGREE AND ACKNOWLEDGE THAT YOU WILL VERIFY ANY RESULTS OBTAINIED FROM YOUR USE OF THE SOFTWARE.
5.4 If, within the Warranty Period, you notify the Licensor in writing of any defect or fault in the Software in consequence of which it fails to perform substantially in accordance with the Documentation, and such defect or fault does not result from you having amended the Software or used it in contravention of the terms of this Licence, the Licensor will, at its sole option, repair or replace the Software, provided that you make available all information that may be necessary to assist the Licensor in resolving the defect or fault, including sufficient information to enable the Licensor to recreate the defect or fault.
6. LICENSOR'S LIABILITY
6.1 This condition sets out the entire liability of the parties (including any liability for the acts or omissions of their respective employees, agents and subcontractors) to each other in respect of:
(a) any breach of this Licence however arising;
(b) any use made or resale of the Software or the Documentation by you, or of any product or service incorporating any of the Software or the Documentation; and
(c) any representation, statement or tortious act or omission (including negligence) arising under or in connection with this Licence.
This condition is always subject to the warranties set out at condition 5 above.
6.2 Nothing in this Licence shall limit or exclude the liability of either party for:
(a) death or personal injury resulting from negligence; or
(b) fraud or fraudulent misrepresentation; or
(c) breach of the terms implied by section 12 of the Sale of Goods Act 1979; or
(d) breach of section 2 of the Consumer Protection Act 1987; or
(e) the deliberate default or wilful misconduct of that party, its employees, agents or subcontractors.
6.3 Without prejudice to conditions 2.4 and 6.2, neither party shall under any circumstances whatever be liable to the other, whether in contract, delict (including negligence) or restitution, or for breach of statutory duty or misrepresentation, or otherwise, for any:
(a) loss of income;
(b) loss of business profits or contracts;
(c) business interruption;
(d) loss of the use of money or anticipated savings;
(e) loss of information;
(f) loss of opportunity, goodwill or reputation;
(g) loss or deferral of production;
(h) loss of product;
(i) loss of, damage to or corruption of data; or
(j) any indirect or consequential loss or damage of any kind howsoever arising and whether caused by tort (including negligence), breach of contract or otherwise;
provided that this condition 6.3 shall not prevent claims for loss of or damage to your tangible property that fall within the terms of condition 5 or any other claims for direct financial loss that are not excluded by any of categories (a) to (j) inclusive of this condition 6.3.
6.4 Subject to condition 6.2 and condition 6.3, the Licensor's maximum aggregate liability under or in connection with this Licence, whether in contract, delict (including negligence) or otherwise, shall in all circumstances be limited to the annual licence fee paid.
6.5 Subject to condition 6.2 and condition 6.3, the Licensor's liability for infringement of third party intellectual property rights shall be limited to breaches of rights subsisting in the UK.
6.6 This Licence sets out the full extent of the Licensor's obligations and liabilities in respect of the supply of the Software and Documentation. In particular, there are no conditions, warranties, representations or other terms, express or implied, that are binding on the Licensor except as specifically stated in this Licence. Any condition, warranty, representation or other term concerning the supply of the Software and Documentation which might otherwise be implied into, or incorporated in, this Licence, or any collateral contract, whether by statute, common law or otherwise, is hereby excluded to the fullest extent permitted by law.
7. TERMINATION
7.1 The Licensor may terminate this Licence immediately by written notice to you if:
(a) you fail to pay the any Licence fees due;
(b) you commit a material or persistent breach of this Licence which you fail to remedy (if remediable) within 14 days after the service on you of written notice requiring you to do so; or
(c) a petition for a bankruptcy order to be made against you has been presented to the court; or
(d) the Licensee (where it is a company) becomes insolvent or unable to pay its debts (within the meaning of section 123 of the Insolvency Act 1986), enters into liquidation, whether voluntary or compulsory (other than for reasons of bona fide amalgamation or reconstruction), passes a resolution for its winding-up, has a receiver or administrator manager, trustee, liquidator or similar officer appointed over the whole or any part of its assets, makes any composition or arrangement with its creditors or takes or suffers any similar action in consequence of its debt.
7.2 Upon termination for any reason:
(a) all rights granted to you under this Licence shall cease;
(b) you must cease all activities authorised by this Licence;
(c) you must immediately pay to the Licensor any sums due to the Licensor under this Licence; and
(d) you must immediately delete or remove the Software from all computer equipment in your possession and immediately destroy or return to the Licensor (at the Licensor's option) all copies of the Software then in your possession, custody or control and, in the case of destruction, certify to the Licensor that you have done so.
8. TRANSFER OF RIGHTS AND OBLIGATIONS
8.1 This Licence is binding on you and us and on our respective successors and assigns.
8.2 You may not transfer, assign, charge or otherwise dispose of this Licence, or any of your rights or obligations arising under it, without our prior written consent.
8.3 The Licensor may transfer, assign, charge, sub-contract or otherwise dispose of this Licence, or any of his rights or obligations arising under it, at any time during the term of the Licence..
9. NOTICES
All notices given by you to the Licensor must be given to Innova Drilling and Intervention Ltd at Union Plaza (6th Floor), 1 Union Wynd, Aberdeen, Scotland, AB10 1DQ. The Licensor may give notice to you at either the e-mail or postal address you provided to it when purchasing the Software. Notice will be deemed received and properly served 24 hours after an e-mail is sent, or three days after the date of posting of any letter. In proving the service of any notice, it will be sufficient to prove, in the case of a letter, that such letter was properly addressed, stamped and placed in the post and, in the case of an e-mail, that such e-mail was sent to the specified e-mail address of the addressee.
10. EVENTS OUTSIDE THE LICENSOR'S CONTROL
10.1 The Licensor will not be liable or responsible for any failure to perform, or delay in performance of, any of his obligations under this Licence that is caused by an event outside his reasonable control (Force Majeure Event).
10.2 A Force Majeure Event includes any act, event, non-happening, omission or accident beyond our reasonable control and includes in particular (without limitation) the following:
(a) strikes, lock-outs or other industrial action;
(b) civil commotion, riot, invasion, terrorist attack or threat of terrorist attack, war (whether declared or not) or threat or preparation for war;
(c) fire, explosion, storm, flood, earthquake, subsidence, epidemic or other natural disaster;
(d) impossibility of the use of railways, shipping, aircraft, motor transport or other means of public or private transport;
(e) impossibility of the use of public or private telecommunications networks;
(f) the acts, decrees, legislation, regulations or restrictions of any government.
10.3 The Licensor's performance under this Licence is deemed to be suspended for the period that the Force Majeure Event continues, and he will have an extension of time for performance for the duration of that period. We will use our reasonable endeavours to bring the Force Majeure Event to a close or to find a solution by which our obligations under this Licence may be performed despite the Force Majeure Event.
11. WAIVER
11.1 If the Licensor fails, at any time during the term of this Licence, to insist on strict performance of any of your obligations under this Licence, or if the Licensor fails to exercise any of the rights or remedies to which he is entitled under this Licence, this shall not constitute a waiver of such rights or remedies and shall not relieve you from compliance with such obligations.
11.2 A waiver by the Licensor of any default shall not constitute a waiver of any subsequent default.
11.3 No waiver by the Licensor of any of these terms and conditions shall be effective unless it is expressly stated to be a waiver and is communicated to you in writing.
12. SEVERABILITY
If any of the terms of this Licence are determined by any competent authority to be invalid, unlawful or unenforceable to any extent, such term, condition or provision will to that extent be severed from the remaining terms, conditions and provisions which will continue to be valid to the fullest extent permitted by law.
13. ENTIRE AGREEMENT
13.1 This Licence and any document expressly referred to in it constitute the whole agreement between us and supersedes any previous arrangement, understanding or agreement between us, relating to the licensing of the Software and Documentation.
13.2 We each acknowledge that, in entering into this Licence (and the documents referred to in it), neither of us relies on any statement, representation, assurance or warranty (Representation) of any person (whether a party to this Licence or not) other than as expressly set out in this Licence or those documents.
13.3 Each of us agrees that the only rights and remedies available to us arising out of or in connection with a Representation shall be for breach of contract as provided in this Licence.
13.4 Nothing in this clause shall limit or exclude any liability for fraud.
14. LAW AND JURISDICTION
This Licence, its subject matter or its formation (including non-contractual disputes or claims) shall be governed by and construed in accordance with Scots law and submitted to the non-exclusive jurisdiction of the Scottish courts.
Well Seeker PRO recommended system requirements:
Intel i5 processor or equivalent.
4 GB of RAM.
500MB of hard disk space.
Microsoft Windows 64-bit (x64) version 10 or better.
Microsoft Excel 2007 or later.
Windows XP, Windows 7.0 and Mac OS are NOT supported.
Recommended screen resolution: 1920 x 1080.
Well Seeker Web client is compatible with the following browsers:
Desktop browser: Microsoft Edge, Google Chrome, or Firefox.
Mobile operating system: iOS or Android.
Recommended remote server setup:
Compatible with Amazon Web Services (AWS) and Microsoft Azure cloud-based servers.
Engine type: Microsoft SQL Server version 2017 14.00.2049.1.v1 or newer.
Engine Edition: SQL Server Express Edition.
DB Instance size: Minimum 2 vCPUs and 4 GB RAM.
Minimum storage: 100 GB.
Server management software e.g. Microsoft SQL Server Management Studio.
Ubuntu based ICDS Instance e.g. Amazon EC2.
Innova Well-Seeker Pro is a high performance well planning and survey management package designed for use by Operators, Well Engineering Companies and Directional Drilling Contractors. The software integrates high performance 2D & 3D graphics with a powerful database engine that allows the user to easily store and visualize their well trajectories as well as perform complex well planning and anti-collision calculations. Innova Well Seeker Pro offers exceptional performance with all the features expected of an industry leading well planning package.
Directional Well Planning Module:
Full range of easy-to-use 2D & 3D well planning methods including:
Dogleg Tool Face
Build and Turn
Optimum Align using Curve-Hold-Curve or Curve-Curve
Line up on Target at specified inc / azi,
One click S-Well and Slant Well construction
Supports multiple target geometries including:
Simple 2D circular and Elliptical
Point & Rectangular
Complex 3D multi point Polygonal
Lease Lines and Hard Lines
Create Drillers Targets based on error models, well trajectory & required confidence.
Supports advanced well planning for all applications, from simple vertical exploration wells to complex multi-laterals.
Anti-Collision Module:
Perform anti-collision scans using industry leading proximity detection algorithms.
Calculate ellipse of uncertainty (EOU) using full range of ISCWSA MWD and Gyro error models.
Error outputs and Centre to Centre distances validated against ISCWSA standard well paths to < 0.1% error.
Anti-collision scans can be run interactively during planning and drilling phases on multiple actual wells / plans.
User defined warning criteria and alerts can be set to notify of potential collision risk.
Casing and hole diameters can be included in separation factor calculation in order increase accuracy. Especially important for top hole drilling with large diameter surface casing.
Ability to create custom Instrument Performance Models (IPM).
Error output sigma level can be selected by the user.
Real Time AC feature allows monitoring of multiple offset wells and distance to lease lines
Anti-collision tools such as travelling cylinder view and ladder plot update in real time as additional surveys are entered.
Advanced anti-collision visualisation tools available including:
Ladder Plot
Separation Factor Plot
Travelling Cylinder Plot
Powerful database:
Built on a powerful database engine which allows storage and navigation for an unlimited number of actual wells and plans.
Easy navigation of database through familiar tree view.
Import and export of data allows easy transfer of wells and plans from office locations to the field.
Both local and SQL Server databases available.
Local databases can be easily set up to provide real time data exchange with the master SQL Server database, allowing surveys, daily reports, BHA’s etc to be updated on the master database in real time from the field.
Local databases can perform a remote data fetch allowing them to pull plans and offset data directly from the master SQL Server database. This permits the field engineers to quickly build a database with all the relevant data.
Wellbore Visualization:
Fully customisable, advanced, and powerful 3D plotting capability:
Plan View (Top Down) Plot
Section View (Side On) Plot
3D Plot
Fly down well 3D chart feature
Visualise closest approach to all offset wells and principal plan
Spider Plot with interactive TVD slice control
Azimuth Comparison Plot (Azimuth vs MD)
Inclination Comparison Plot (Inclination vs MD)
Dogleg Comparison Plot (Dogleg vs MD)
Live View Plot
Print directly to multiple image formats including PDF / jpg / bmp / png.
Copy directly to clipboard allowing images to be quickly added to Word, Excel & PowerPoint documents.
Wall Plot Composer (WPC) allows the user to create customisable wall plots which can include data tables.
Pre-defined plot sizes range from A0 to A7 with a user defined option also available.
Integrated Geosteering Functionality
Visualise formation top and target depths.
Customisable outputs in both 2D and 3D charts.
Update and model geological target corridor based on RT updates.
Provides clear visual updates to DD of drilling corridor.
Quickly create offset plans based on real time geosteering updates.
Geomagnetic Modelling
Includes World Magnetic Model (WMM) and International Geomagnetic Reference Field (IGRF) model as standard.
Supports British Geological Survey Global Geomagnetic Model (BGGM)*
*available only to full BGGM license holders
Supports NOAA High Definition Geomagnetic Model (HDGM)**
**available only to full HDGM license holders
Supports MagVAR High Definition Geomagnetic Model (mvHD)***
***available only to full mvHD license holders
Standard Reporting Features
User defined reports include:
Standard Survey reports
Geographic Survey reports
Anti-Collision reports
Ellipse of uncertainty (EOU) reports
Exports to fully customisable PDF and Excel reports.
Wall Plot Composer.
Import Compass Export Files
Includes the ability to import Compass Export files, including batch import, where multiple export files can be pulled in simultaneously.
Bid Sheets
Quickly populate customer and Supplier addresses and details from dropdown lists.
Print quotation including a cover letter and any relevant notes.
Cost Codes included in the bids can be quickly and easily copied to well level where they can then be selected in the Daily Reporting feature.
Bids are approved by users with the relevant user permissions.
Bids can be Archived by users with the relevant user permissions.
Integrated Daily Reporting Features
Integrated within Innova’s Well Seeker Pro are advanced custom reporting features including:
Daily Reports
Slide Sheets
Ability to populate Daily Reports directly from the slide sheet.
Ability to auto populate slide sheets via received WITS data.
Daily Cost Reports
Well Cost Reports
Cost Tracking
Tool Inventory
Tool Utilisation Reports
Personnel Utilisation Reports
Tool and Personnel Tracking
Shipping Tickets
Pipe Tally
BHA Reports
Motor and MWD Performance Reports
Motor and MWD Failure Reports
End of Well Reports
Company Man Report
KPI Tracking
Well statistics provides a detailed overview of the well data including well phases and BHA’s.
Click of a button morning report package, directly opens outlook email complete with excel morning report and copy of current database as attachments and email body populated with a synopsis of daily operations.
Generate and output detailed reports at the click of a button.
Excel and PDF output.
Easily create and output custom reports and charts.
Database Analytics Tool
Powerful search tool to find and compare wells across the entire database. Multiple search criteria options available including Date Range, Radius from a given well, Formation, Assembly type, Failures, State, Directional Company, Hole Size, Rig and LIH etc.
Plot all selected wells together on google maps. Surface locations, Plans, Surveys and Lease Lines can all be displayed.
Motor, MWD and Section KPI Reports.
Revenue Report.
Rig Days Report.
Personnel Utilisation Report.
Well Ranking Report.
Compare KPI metrics between multiple wells and well phases:
Slide & Rotation Footage
Depth Vs Time
Failure Analysis
Directional Cost per Foot
Well Cost per Foot
BHA Details
Detailed Cost Breakdown
Wells by Formation, Directional Company, Motor Make, Bit Make
ROP & Footage by Formation, Directional Company, Motor Make, Bit Make, Hole Size
Activity & Phase Comparison
Wells by Rig
ROP & Footage by Rig
Parameter Comparison
Well / Section Performance
Average Interval Cost per Quarter
Driller Performance
Well AFE Designer
The Authorization for Expenditure (AFE) Designer is a powerful well plan costing tool which includes the following features:
Build detailed AFE for any well plan from mobilisation to demobilisation.
Probabilistic & Deterministic approach.
Calculate costs for P10, P50, P90 scenarios.
Standardised cost codes.
Factor in associated risks and assign probabilities.
Export KPI charts:
Time Probability Density Function
Cost Probability Density Function
Time Cumulative Density Function
Cost Cumulative Density Function
Depth vs Time
Cost vs Time
Time Interval
Time Cumulative
Cost Interval
Cost Cumulative
Generate full reports with detailed timeline and cost breakdown:
Event Model
Detailed Event Breakdown with costs
Cost Model
Time vs Depth
Time vs Cost
Time Histogram
Cost Histogram
Full report containing all the above reports and all KPI charts
WITS & Remote Directional Drilling
Supports WITS & WITSML connectivity.
WITS data can be pushed back from the field to the remote server database, where it can be viewed by anyone with the relevant login credentials.
Slide sheets can be automatically populated based on the data received via the WITS feed.
Remote data fetch allows the user to pull wells into a local database, directly from an SQL server database.
Real Time Data Exchange allows field data to be updated on the SQL server database in real time.
DD Dashboard, which provides an interface containing tools a directional driller can utilize while drilling a well either locally on the rig or remotely from an RTOC. It updates automatically while using the WITS feed and contains the following:
Rig Gauges.
A Tool Face Rose which displays Toolface, Effective Toolface, Bit Projection and various other information based on the selected mode.
Real Time Anti-collision for bit projection.
Last 4 surveys along with the Slide Seen and Motor Yield for each one.
Projections including projection to bit and advisory projection.
Real time 3D plot.
Drilling parameters charts populated from the WITS data feed.
Choose between 4 modes: Vertical, Nudge, Curve & Lateral which provide the user with slide and rotary recommendations based on the data entered in the settings menu.
Slide Analysis.
Connection Analysis.
Dashboards
Activity Dashboard
Shows a summary with up-to-date data for all selected wells including, depth vs time chart, revenue tracking, inventory etc.
Print job board report which includes Active Wells, Upcoming and Standby Wells, daily and monthly revenue and summary of wells by operator, state, and coordinator.
Logistics Dashboard
Provides an overview of all tools in the local inventories within the database giving full oversight of all equipment.
View all tools in all locations via google maps.
Various filter options to quickly find the relevant items.
Rigs Online Dashboard
Shows a list of all current jobs where data is being sent from the field to the server database and displays the time since last update.
AC Dashboard
Displays a summary of all open RTAC dialogs.
At the click of a button the user can open the surveys and RTAC dialogs for all active wells in the database.
Innova Web Portal
Login to the web portal from anywhere in the world via an internet browser.
Filter and view all well data contained in the SQL database.
Can be viewed on any internet enabled device with no additional software required.
Additional Features
Server based licensing
Supports data import / export from 3rd party software platforms.
Ability to import COMPASS XML export files at the click of a button.
Directional Difficulty Index (DDI) calculator.
Motor Yield Calculator.
Motor and MWD Forecasting.
Additional UI Features
Copy & Paste - Very quick and easy to add large surveys to the software - copy and paste directly from excel or txt files.
Export files can be generated quickly at any level on the database tree.
Quick and easy to create and switch between new databases.
A guide to the Casing Standoff output within Innova Engineering's Torque & Drag Module.
This document will deal with the Casing Standoff calculation within Innova Engineering's Torque & Drag Module and will detail the steps required to run this calculation.
The casing standoff calculation uses the data input by the user and calculates either:
The casing standoff based upon a given centralizer spacing entered by the user, or
The required centraliser spacing to achieve the users desired standoff. Based upon the minimum step value selected by the user the optimum centraliser spacing will also be calculated.
In order to run the casing standoff calculation, a Torque and Drag calculation needs to be run. For T&D setup, refer to the Torque & Drag Quick Start Guide.
Over and above the standard Torque & Drag inputs, the following inputs are required.
In the Tools Menu select - Standoff Optimisation Parameters
Desired Standoff: This is the standoff which will be calculated when Optimise Standoff is selected in the Torque and Drag section of the Engineering Parameters tab on the main user interface
Min Step Value: The minimum step value between one optimum spacing and the next. Engineering looks at the Required Spacing values which provide the desired standoff, and groups similar values (which land within the step range) together to provide a single Optimum Spacing output for each of these points. This is basically a smoothing parameter. Larger step values encompass more of the optimum spacing values providing more of a smoothing effect.
Max Spacing: The spacing value above which no centralisers will be recommended. This affects the Centralizer Spacing Summary in the Standoff Summary Report.
In the above charts the yellow line represents the Optimum Spacing and the pink line is the Required Spacing (achieves the Desired Standoff exactly). These examples show the difference in the Optimum Spacing when different minimum step values (5 and 100) are entered.
In the Options Menu, select Torque and Drag Model. If running bow spring centralizers, the user can select the option to Include Bow Spring Force within the torque and drag calculation. Note that if a bow spring force has been entered in the casing component details, this will be included in the casing standoff calculation regardless of what is selected here.
In the Drill String, Well Geometry & Fluids Tab, for each casing selected, in the component details, the user has the following centralizer inputs available:
Centralizer Spacing: The distance between Centralizers. If centralisers are only run across a certain interval, then the casing should be entered as separate sections in the string. NOTE: this value is ignored when Optimised Standoff is selected. This is a required input for the casing standoff calculation when Optimise Standoff is not selected.
Centralizer OD: The Outside Diameter of the Centralizer. For bowspring centralisers the OD input may be larger than the ID of the hole This is a required input for the casing standoff calculation.
Centralizer Length: The length of the centralizer blade which contacts the wellbore. This input is not used in the standoff calculation but is used for hydraulics.
Centralizer Blade Width: The width of the individual centralizer blades. This input is not used in the standoff calculation but is used for hydraulics.
Centralizer Blade Count: The number of blades on the stabilizer. This is not used in the standoff calculation but is used for hydraulics.
Bowspring Restoring Force: The Force exerted by a centralizer against the casing to keep it away from the wellbore wall. This input is used in the standoff calculation to determine how much the bow spring centralizer has deformed for a given side force. The centralizer will never compress more than the body OD. The higher the side force the more deformation of the centralizer. If nothing is entered for the restoring force it is assumed that the centralizer is rigid. In the scenario where the include bow spring force option is selected and the running force cell is left empty, this value will be used for the running force in the T&D calculation of the PU, SO and reaming values.
Centralizer body OD: The OD of the body of the centralizer. This is not used in the standoff calculation but is used for hydraulics. It is also used to calculate percentage compression of a bow spring stabiliser, which can affect the T&D results.
Running Force: The maximum force required to insert a centralizer into a specified wellbore diameter. This input is not used in the standoff calculation but is used for T&D. If entered, this value will supersede the bowspring restoring force in the T&D calculation. The running force will be applied to the pickup, slack-off and reaming values and will increase / decrease with the well bore size. Running force is not applied to the T&D calculation until the compression of the centralizer is greater than 50% and will gradually increase as the compression increases from 50% to 100%.
Centralizer Type: The user can manually enter the centralizer type and make / model here. This is not used in any calculations.
Running Force Restrict. ID: The restriction ID that 100% of the running force will be utilised in T&D calculation. When no value is entered here, the program will apply the running force to the T&D calculations based on the the amount of compression experienced by the bowspring centralizer at any given point in the wellbore. The more the centralizer is compressed, the higher the percentage of the running force which is applied. If the user enters a value here, the program will apply the maximum running force over any part of the wellbore where the ID is the same or less regardless of the compression.For example, Running Force = 2.1klbs, Running Force Restrict. ID = 8”. Any points in the well geometry that this component passes through with an ID less than or equal to 8” will have 2.1klbs of running force applied to the T&D calculation. Any part of the wellbore where the ID is greater than the value entered here will just be treated in the usual way.
In the Engineering Parameters tab the user can choose:
Optimise Standoff: This will override the centralizer spacing selected in casing component details, and output the spacing required to achieve the desired standoff
Point to Note: Optimised Standoff and Desired Standoff (in the Standoff Optimisation Parameters dialog) are linked. When the user changes the value in either of these boxes, it auto updates in the other.
In order to generate the Casing Stand Off output, the user must run a Torque & Drag calculation. To do this, select either the icon displayed below (low and high resolution icons), or select Calculate - Torque and Drag.
Once the calculation has been run, the Stand Off summary report can be viewed by selecting the TAD Results Menu and then Standoff Summary from the available options. This report can be saved as a pdf.
The Casing Standoff Chart is available by selecting the TAD Results Menu - Snapshot Charts - Casing Standoff.
The report can also be generated by selecting "File" - "Print Reports” or selecting the icon on the toolbar.
The three report options for Casing Stand Off can be found on the T&D tab at the bottom right:
Standoff Summary: This is the Report
Standoff Chart: A graphical representation of the results
Standoff Data: Base data used to generate the plots.
The report can be generated either as excel or pdf.
The standoff summary report is generated at the click of a button and contains the following:
Centralizer spacing summary
Drill string summary
Centralizer stand-off results
Standoff chart
Side forces / centralizer forces chart
Hookload chart
The casing standoff chart is a snapshot chart which provides outputs for each point in the string from surface to the calculated depth.
If Optimise Standoff has NOT been selected when the torque and drag calculation is run, the standoff chart will look like the above.
Inc: Inclination
Cent OD: Centralizer Outside Diameter
Deflection Mid Joint: Deflection of the casing between 2 centralizers.
Deflection Centralizer: Deflection of casing at the centralizer.
Standoff Mid Joint: This is calculated as follows (1 – (Deflection Mid Joint / ((Hole ID – Casing OD)/2))) * 100. It is effectively the percentage deflection from well bore centre. If the casing is centralised perfectly the standoff is 100%
Standoff Centralizer: The Percentage Standoff at the Centralizer. This is calculated as follows (1 – (Deflection Centralizer / ((Hole ID – Casing OD)/2))) * 100.
Cent Spacing: The centralizer spacing as entered by the user in the component details section of the drill string editor (This line will NOT be present if Optimise Standoff is selected in the Torque and Drag section of the Engineering Parameters tab on the main user interface).
Restoring Force: The restoring force of the bow spring centralizer which has been entered in the component details section of the drill string tab.
Running Force: The running force of the bow spring centralizer which has been entered in the component details section of the drill string tab.
Side Force: The side force exerted on the casing.
If Optimise Standoff has been selected (in the above this has been set at 60%), when the torque and drag calculation is run, the standoff chart will have the addition of an Optimum Spacing line, and the Centralizer Spacing line becomes the Recommended Spacing line.
Rec Spacing: Recommended Spacing, calculated based on the Optimise standoff value (This line will NOT be present if Optimise Standoff is not selected)
Opt Spacing: This is the optimum spacing which applies the maximum step value to the Recommended Spacing (This line will NOT be present if Optimise Standoff is not selected).
All the other lines described in Section 5.1.1 - Without Optimised Standoff, are also available to be displayed in this chart if required.
A guide to the Torque & Drag module within Innova Engineering.
This document will deal with the Torque & Drag module within Innova Engineering and will detail the steps required to run these calculations.
In the options menu, there are selections that affect the way the torque and drag calculation is run and these should be double checked.
Units: Ensure that all units are correctly selected, based on requirements. Note: If air drilling is being modelled, SFCM must be selected as the Flow units to activate air drilling mode.
Include Tool Joints: Select whether the OD and ID of the tool joint is included in the calculations. Default is Yes.
Include Stabilizers / Centralizers: Enables or disables drill string stabilisers or casing centralisers. Default is Yes.
Include Drilling Data in Calculation: Determines if data entered in the Drilling Data tab is used in the hydraulics and torque and drag calculations. If yes is selected the mud weight, mud rheology, ROP and RPM are used at the depths specified in the calculations. This option is useful for comparing field data to modelled data. By default, this option is set to Yes.
Torque & Drag Model: Select the T&D setup you would like to run.
o Viscous Drag: Refers to the drag caused by pulling the string through the mud. This only affects pick-up weights. Default is No.
o Buckling Friction: The additional friction added if the pipe is helically buckled and being pushed through the well. Only applies to slack-off weights. Default is No.
o Contact Surface Correction: Additional friction applied based on the surface area of the tubular touching the well bore i.e. casing has more friction because more surface area. Default is No.
o Calculate Casing Wear: If No is selected, there will be no output in the Casing Wear Plot. Default is Yes.
o Buckling Lines: User can select between Sliding & Rotary. This selection determines which buckling lines are displayed on the Tension On & Off Bottom Snapshot Charts. Default is Sliding.
o Buckling Model: Determines the way the Helical Buckling limit is calculated.
Conservative (Unloading Model): Sinusoidal limit x 1.4. This is the default.
Standard (Loading Model): Sinusoidal limit x 2.1
o Include Friction Reduction Subs: Friction reduction inputs are available in the DP & HWDP component details. This option determines whether these inputs are used in the calculation. Default is Yes.
o Include Overpull In Stretch Calcs: Stretch calculations will take into consideration the overpull entered in the Engineering Parameters tab. Default is No.
o Outer String Properties: Required input for Liner Expansion calculations.
o Step Interval: Determines the interval between calculated points. Default is 10 i.e. outputs are generated every 10 meters or feet. This will be apparent when viewing the data tables.
o Air Drilling Options: To be used when the section is air drilled. User enters the expected standpipe pressure here for the given flow rate. This will calculate the additional string weight caused by drilling on air. Note: If air drilling is being modelled this must be selected.
o Fluid Level: This option allows the user to select the fluid level in the wellbore. The depth entered is Measured Depth, and the program will assume no fluid from surface to this depth. Over this range, there will be no buoyancy factor considered, therefore the hookload will increase as a result.
Pipe Tensile Yield Limits: Allows the user to enter a pipe size and yield limit into the grid. This can then be displayed on any of the charts via the add additional series button. This input does not affect any calculation. It is instead a reference which can be added to the required charts.
To run Torque & Drag, the following inputs are required.
Drill string, Well Geometry & Fluids Tab
Drill String: Input the assembly as accurately as possible including the drill pipe to surface (note, for the last component e.g. DP to surface, the user does not have to input the exact length as the program will do this automatically based on the calculation depth. Inputting a value of 10 is fine). Note that once you have selected the component type it is possible to right click on the line and select "select from Library", which will open the components library.
Input the dimensions of the drill sting components into the Drill String grid:
Description: A description of the component entered, this is only used in the generation of reports and plays no part in any of the calculations.
OD: The outer diameter of the component in inches.
ID: The inside diameter of the component in inches.
TJ OD: If the component has a tool joint (such as drill pipe) enter the OD in inches into this column. If the “Include TJ in calculations” menu option is turned off this column will be disabled.
TJ ID: If the component has a tool joint (such as drill pipe) enter the ID in inches into this column. If the “Include TJ in calculations” menu option is turned off this column will be disabled.
Weight: This is the weight per unit length of the component, this is either calculated automatically based on the OD / ID of the component or can be entered manually by the user if the “Auto Calculate Weight” option is turned off. This is used for torque and drag calculations as well as SAG calculations.
Length: The length of the component in the system units.
Component: Select the component type from the drop-down list. The type of component that is selected will determine the properties displayed in the lower components grid.
Bit TFA: The bit TFA is required to calculate the pressure drop below the bit, which is used in the buoyancy calculations and in the buckling calculations. This is selected in the component grid section when the bit is selected.
Well Geometry: Input casing, liner and open hole details including depths and ID's. For Open hole, the ID is the OD of the bit.
Mud Weight: This is required for buoyancy and viscous drag calculations
Surveys Tab
Survey Selection: T&D calculations can be run against surveys and well plans. Data can be input as measured depth, inclination and azimuth in both Actual Surveys or Well Plan Surveys and the program will generate the rest of the numbers using whichever survey calculation method you have selected (Minimum Curvature Default). T&D cannot be run against surveys input the RAW surveys section. Either enter the plan or surveys manually, import them or copy and paste the data directly into the cells.
Tortuosity: For portions of a plan which are vertical, it is possible to add tortuosity, to better simulate down hole conditions as a drilled well will never be exactly vertical.
The Engineering Parameters Tab is where the user can select the parameters they want to run the Torque & Drag calculation.
Survey Selection: The user can select either Well Plan Surveys or Actual Surveys. There is also an option to select Composite Listing, which splices the actual surveys into the well plan surveys to create a composite listing.
Flow rate: If manual flow increment is selected, the first flow rate entered will be used in the T&D calculation. If the manual flow increment is not selected, the flow rate entered in line 3 will be used.
Calc Depth – This is the depth the calculation will stop at and the depth the snapshot graphs and tables will display.
RPM – Rotational speed of the drill string, used to calculate reaming torques and hook loads.
Pipe speed – The speed the pipe is moving up and down in depth units / min. Used to calculate reaming hook loads and torques. It is also used to calculate the viscous drag if selected.
WOB Rotate – The weight on bit while on bottom rotary drilling. Used for creating the Apparent WOB & Apparent WOB Snapshot Charts.
WOB Slide – The weight on bit while on bottom slide drilling. If the check box is not selected, this will auto populate with the value in the WOB cell.
Overpull: The overpull applied to the assembly when pulling out of hole. Used for creating the Apparent Overpull & Apparent Overpull Snapshot Charts.
Block weight – The weight of the travelling block.
Block PU – if the weight of the travelling block is different to the block weight while picking up enter it here, click the check box to enable.
Block SO - if the weight of the travelling block is different to the block weight while slacking off enter it here, click the check box to enable.
Optimise Standoff: Used in the casing standoff calculation. This will override the centralizer spacing selected in casing component details and output the spacing required to achieve the desired standoff.
Est Bit Torque – The estimated torque generated by the bit, this is calculated from the WOB and the bit OD (taken from the drill string), however it can be over-ridden with a user defined value by clicking the check box.
Side force units – Specifies the unit length of the calculated side force. It should be noted that if you are using side force to predict casing wear, the default units should be over ridden to side force / per tool joint (e.g. 30ft or 10m).
Casing Wear Factor – Casing wear factor, defined as the ratio of friction factor to specific energy, E-10psi-1. The table below should be used as guide for casing wear factor selection. Default is set to 1.
ROP – The rate of penetration in feet or meters / hour. The ROP is used to calculate the casing wear. This is done by taking the depth of the last casing or liner and subtracting it from the calculation depth. This value is then divided by the ROP to give the time period over which casing wear is calculated.
Friction factor grid – The friction factors for cased hole and open hole. By default, the enable manual increment box is disabled. Enter a friction factor for the cased hole and open hole in the middle cells of each column and values above and below will automatically be calculated (±25% &±50%) in order to perform a sensitivity analysis. If you wish to override this feature, click the check box and enter as many friction factors as required. This can also be used to perform a single friction factor calculation.
Once the user has completed all the required inputs the calculation can be run. To do this, select either the icon displayed below, or select Calculate - Torque and Drag. This will calculate all the torque and drag and the torque and drag snapshot data.
Additionally, the option is available to only calculate the torque and drag snapshot data. To do this, select either the icon displayed below, or select Calculate – Torque and Drag Snapshot. This option reduces the calculation time; however, will not calculate the full standard torque and drag data.
Once the calculation has been run, the Torque and Drag summary report can be viewed by selecting the icon from the toolbar at the top of the screen. This contains an overview of the main values associated with the calculation and can be saved as a pdf.
If required, a more detailed report can be generated by selecting "File" - "Print Reports” or selecting the icon on the toolbar (highlighted below). The required data can be selected, and a report can be generated either as excel of pdf. Note that when excel is selected the chart selection will be greyed out as these can only be output as pdf.
Some of the torque and drag results are available to view by selecting the toolbars along the top. This is a quick way to access some of the more commonly used plots.
All the torque and Drag plots and data are available to view by selecting the TAD results at the top of the screen. The Data options mirror the charts and display the numerical data used to generate the charts.
Survey Data: Only available to select when on the survey tab. This gives a breakdown of the survey data every 10 meters or feet and includes any tortuosity which has been applied.
Stress Data: Gives the user access to the stress data associated with different operations i.e. Rotating off bottom, Sliding etc. Charts for this data can be generated directly from here.
TAD Summary: This option prints a report that includes a Torque & Drag Summary Report, Drillers Hookload Chart and Drillers Torque Chart.
Standoff Summary: This option prints a report that includes a Centralizer spacing summary, Drill String summary, Centralizer Stand-off results, Standoff chart, Side Forces / Centralizer Forces chart and Hookload chart.
The drilling charts represent the calculated (theoretical) values that the driller would expect to see on his gauges as the well is being drilled. Therefore, at each depth, the numbers displayed on the charts and the drilling data tables can be directly compared with values recorded from the drillers gauges as the well is being drilled.
This chart displays the calculated hookload values for tripping in, Rotating Off Bottom and tripping out. It also includes the Reaming In and Out hookloads.
For each operation, there will be a line represented for each set of friction factors entered in the Engineering Parameters tab, apart from the Rotating off Bottom line, of which there will only ever be one.
The minimum weight to helically buckle (Trip In) will also be displayed on this chart. Any tripping in line which crosses this limit will start to experience buckling in the string. At this point it may be difficult to effectively transfer weight down hole and the string may need to be rotated in order to get to bottom. From the chart, you can tell the string depth and hookload when the buckling will occur, but you will not be able to determine where in the string the buckling is occurring.
This chart displays the On and Off Bottom torques. For each operation, there will be a line represented for each set of friction factors entered in the Engineering Parameters tab.
The Reaming Hookload Chart displays the PU & SO weights seen at surface for any given depth in the section, based on a specific string RPM and pipe speed. If either rpm or pipe speed is modelled as zero, the reaming Hookloads will match the drillers Hookloads. A Reaming PU and SO line will be displayed for each set of friction factors which have been modelled.
The Reaming Torque Chart displays the PU & SO torques seen at surface for any given depth in the section, based on a specific string RPM and pipe speed. With a pipe speed of zero, both of these lines will mirror the off bottom torque line in the Drillers Torque Chart. PU & SO Torque lines will be displayed for each set of friction factors which have been modelled.
The Pipe Stretch Chart displays the calculated amount of pipe stretch expected while picking up for any given depth in the section. There will be a line displayed for each friction factor which has been modelled.
This chart displays the number of completed revolutions that the rotary table must be turned in order to turn the bit. A line will be represented for each of the friction factors entered in the Engineering Parameters tab.
This chart displays the apparent weight on bit (WOB) required at any given depth to achieve a user defined Actual WOB. The actual WOB value used is the WOB value entered in the torque and drag section of the Engineering Parameters tab.
To read the chart the user should select the measured depth of interest and note the apparent WOB for each of the friction factors at that depth. These are the WOB values the user will need to register at surface in order to achieve the desired actual WOB down hole at the bit. Note that if no WOB value is entered in the torque and drag section of the Engineering Parameters tab, then this will model as a vertical line.
This chart displays the apparent Overpull (OP) required at any given depth to achieve a user defined Actual OP. The actual OP value used is the OP value entered in the torque and drag section of the Engineering Parameters tab.
To read the chart the user should select the measured depth of interest and note the apparent OP for each of the friction factors at that depth. These are the OP values the user will need to register at surface in order to achieve the desired actual OP down hole at the bit. Note that if no overpull value is entered in the torque and drag section of the Engineering Parameters tab, then this will model as a vertical line.
The snapshot charts represent the theoretically calculated values that you would expect at each point in an assembly when the assembly is at a given depth. For example, when looking at the torque snapshot chart, it will display the torque at each point in the string (for a given depth) from the bit all the way to surface. The surface values will match those of the drilling charts at the depth in question.
This chart displays the effective tension at all points in the string when the string is at a specific depth. This depth is displayed at the top of the chart and is the calc depth entered in the torque and drag section of the Engineering Parameters tab.
The chart displays the following lines:
Rotating off Bottom
Sinusoidal Buckling – Any load line which crosses this buckling line will be representative of Sinusoidal buckling. The depth at which the line crosses will also represent the component in the string which is experiencing the buckling.
Helical Buckling – Any load line which crosses this buckling line will be representative of Helical buckling. The depth at which the line crosses will also represent the component in the string which is experiencing the buckling.
PU – A Pickup line will be represented for each of the entered friction factors.
SO – A Slack Off line will be represented for each of the entered friction factors.
Tensile Limit – The tensile limit will be displayed based on the tensile limits entered in the component details section for each individual component.
String Tension with Overpull – This line is generated based on the overpull entered in the torque and drag section of the Engineering Parameters tab.
This chart displays the effective tension at all points in the string when the string is at a specific depth with a specific WOB. The depth and WOB are displayed at the top of the chart with these values having been entered in the torque and drag section of the Engineering Parameters tab.
The chart displays the following lines:
Rotating off Bottom
Sinusoidal Buckling – Any load line which crosses this buckling line will be representative of Sinusoidal buckling. The depth at which the line crosses will also represent the component in the string which is experiencing the buckling.
Helical Buckling – Any load line which crosses this buckling line will be representative of Helical buckling. The depth at which the line crosses will also represent the component in the string which is experiencing the buckling.
PU – A Pickup line will be represented for each of the entered friction factors.
Sliding – A Sliding line will be represented for each of the entered friction factors.
Tensile Limit – The tensile limit will be displayed based on the tensile limits entered in the component details section for each individual component.
This chart displays the torque at all points in the string when the string is at a specific depth. This depth is displayed at the top of the chart and is the calc depth entered in the torque and drag section of the Engineering Parameters tab. For each operation, there will be a line represented for each set of friction factors entered.
This chart displays the side force at all points in the string when the string is at a specific depth. This depth is displayed at the top of the chart and is the calc depth entered in the torque and drag section of the Engineering Parameters tab.
The chart displays the rotating side force along with the pickup and slack off side forces for each set of friction factors entered.
This chart plots the actual WOB against the apparent WOB when the string is at a specific depth. This depth is displayed at the top of the chart and is the calc depth entered in the torque and drag section of the Engineering Parameters tab.
To use this chart, the user should select the actual WOB they require downhole, and the corresponding apparent WOB is the weight that will be required at surface to achieve this.
This chart plots the actual overpull against the apparent overpull when the string is at a specific depth. This depth is displayed at the top of the chart and is the calc depth entered in the torque and drag section of the Engineering Parameters tab.
To use this chart, the user should select the actual overpull they require downhole, and the corresponding apparent overpull is the overpull that will be required at surface to achieve this.
This chart shows the predicted cumulative wear at each point in the casing when the assembly is at a specific depth. This depth is displayed at the top of the chart and is the calc depth entered in the torque and drag section of the Engineering Parameters tab.
The casing wear is expressed as depth in ether inches or mm depending on what units are selected for Diameter. The depth of wear indicates depth of the groove which will be worn into the side of the casing over a period of time.
Casing Wear Rotating: This is the predicted wear on the casing when the string has 0 ROP. This calculation uses the rotating side force.
Casing Wear SO: This is the predicted casing wear calculated using the reaming slack off. This calculation uses the slack off side force.
Drill string fatigue will only occur while rotating and only while rotating over a dogleg. The more tension within the pipe the more likely it is to get fatigued. There is a critical value of dogleg where fatigue failure becomes an issue.
The Drill Pipe Fatigue Chart is a snapshot chart which displays the actual dogleg and the critical dogleg at every point in the string for a given depth. If the actual dogleg is greater than the critical dogleg, then fatigue failure is a potential issue.
The critical dogleg curve is generated based on the free rotating weight of the drilling assembly. One point to note is that back reaming will increase the tension and therefore reduce the critical rotating dogleg; however, this has not been included in the chart because back reaming operations do not generally last too long.
This chart shows the Internal and External pressure at each point in the string for a given flowrate, when the assembly is at a specific depth. This depth is displayed at the top of the chart and is the calc depth entered in the torque and drag section of the Engineering Parameters tab.
In the flow rate section, if manual flow increment is selected, the first flow rate entered will be used for generating the outputs for this chart. If the automatic range is selected, the flow rate entered in line 3 will be used.
A guide to the Hydraulics module within Innova Engineering.
This document will deal with the Hydraulics module within Innova Engineering and will detail the steps required to run these calculations.
Units: It is important to ensure that the correct Units are selected before you do anything else as changing units after the data has been input can lead to mistakes. Note: If air drilling is being modelled, SFCM must be selected as the Flow units to activate air drilling mode.
Note: If the unit for Flow is selected as SFCM in the Units Menu, Engineering will assume that air drilling is being modelled. In this case the calculation will ignore Mud Weight, PV, YP and Mud Rheology, and instead assume the properties of air as the drilling fluid.
Hydraulics Model Options should then be checked from the Options menu. These mostly relate to the surge and swab calculations.
Surge and Swab is calculated by breaking down the measured depth into sections of a given length (Stand Length), where 30m / 100ft is the default. The program then does a lumped surge and swab calculation over this course length, where the pipe accelerates from 0 to the desired trip speed and then decelerating back to zero.
The acceleration and deceleration phases are calculated based on the trip speeds entered in the Engineering Parameters tab; the higher the trip speed the larger the acceleration effect. The generated outputs in the plot and data table, are the maximum surge or minimum swab values calculated over this interval.
Below is a description of each option:
Surge and Swab Parameters:
Mud Compressibility: A compressibility factor for the mud in 1/psi. Default for most oil-based fluids is 3 x 10-6.
10m Gel Strength: 10-minute gel strength, used to calculate the additional surge pressure required to break down the gels. Default is 12.
Stand Length: Length of the stand used in the calculations. Default is 30m / 100ft.
SnS - Include Pipe Acceleration: This option allows the user to include or exclude pipe acceleration. When this is included, the calculation will use an acceleration and deceleration phase for each stand length. When it is not included, the trip speed will be used for the whole stand with no acceleration or deceleration phase. Default is Off.
SnS - Include Gel Strength Pressure Loss: Include the additional pressure required to break down the gels. This is normally a relatively small value. Default is Off.
SnS – Continuous Circulation: Used to model coiled tubing. Assumes circulation while tripping, this means that swab affects will be less and surge effects will be more depending on flow rate. The first flow rate in the flow grid of the Engineering Parameters tab is used to determine the annular velocity generated by the circulating fluid. Default is Off.
SnS – Limit Acceleration Effects: This option limits the additional surge pressures due to acceleration to a maximum of 2 x the current max surge pressure. This stops very large (artificial) equivalent mud weights being generated when very shallow. Default is On
SnS – Continuous Tripping: This option assumes continuous tripping, and as a result will only calculate one acceleration phase (on the first stand length) and one deceleration phase (on the last stand length). This option is best used to model coiled tubing. Default is Off.
SnS – Use Bit TFA for Open Ended Calcs: This option allows the user to use the bit TFA when running open ended surge and swab calculations. This will only work for assemblies which have a bit and a TFA entered. When this selection is off, the program uses the internal diameter of the last component. Default is Off.
Pump Pressure Safety Factor: This option allows the user to increase the SPP by a specified percentage. Pipe Pressure Loss, Annular Pressure Loss and SPP values are all adjusted to reflect the input Safety Factor.
MPD Data: This option allows the user to enter a back pressure for Managed Pressure Drilling.
MPD Setup. The MPD Back Pressure is added as a fixed value to all of the SPP calculation totals and will also be reflected in the ECDs.
EMW Calculator: The user inputs the desired EMW increase at a specific TVD and the required back pressure to be applied is calculated. The user can then enter this value in the MPD setup.
Riser Boost Rate: The boost flow rate across the riser is entered here. This additional flow in the riser annulus affects the annular pressure loss, annular velocity, hole cleaning and ECDs in the riser only. This in change in the riser values affects the SPP, annular pressure loss, hole cleaning and ECDs for the section. This is only applicable in wells where the Well Geometry includes a ‘Riser’. If the well geometry does not include a riser, any value entered here will have no effect on the calculated outputs.
In order to run Hydraulics, the following inputs are required.
Drill String, Well Geometry & Fluids Tab
Drill String: Input the assembly as accurately as possible including the drill pipe to surface (note, for the last component e.g. DP to surface, the user does not have to input the exact length as the program will do this automatically based on the calculation depth. Inputting a value of 10 is fine). Note that once you have selected the component type it is possible to right click on the line and select "select from Library", which will open the components library.
Input the dimensions of the drill sting components into the Drill String grid:
Description: A description of the component entered, this is only used in the generation of reports and plays no part in any of the calculations.
OD: The outer diameter of the component in inches.
ID: The inside diameter of the component in inches.
TJ OD: If the component has a tool joint (such as drill pipe) enter the OD in inches into this column. If the “Include TJ in calculations” menu option is turned off this column will be disabled.
TJ ID: If the component has a tool joint (such as drill pipe) enter the ID in inches into this column. If the “Include TJ in calculations” menu option is turned off this column will be disabled.
Length: The length of the component in the system units.
Component: Select the component type from the drop-down list. The type of component that is selected will determine the properties displayed in the lower components grid.
Bit TFA: This is selected in the component details section when the bit is selected. The user can select a fixed TFA or can input multiple nozzles and sizes and a TFA will be generated based on this selection.
Motor Pressure Drop: This is selected in the component details section when the motor is selected.
MWD Pressure Drop: This is selected in the component details section when the MWD is selected.
Well Geometry: Input casing, liner and open hole details including depths and ID's. For Open hole, the ID is the OD of the bit.
Mud weight: Mud density used in all hydraulics calculations
PV: Mud plastic viscosity only used if Bingham Plastic hydraulics model is selected
YP: Mud yield point only used if Bingham Plastic hydraulics model is selected
Mud Rheology: The Fann dial readings of the drilling fluid, required for all hydraulics models except Bingham plastic.
Surveys Tab
Survey Selection: Hydraulics calculations can be run against surveys and well plans. Data can be input as measured depth, inclination and azimuth in both Actual Surveys or Well Plan Surveys and the program will generate the rest of the numbers using whichever survey calculation method you have selected (Minimum Curvature Default). Hydraulics cannot be run against surveys input the RAW surveys section. Either enter the plan or surveys manually, import them or copy and paste the data directly into the cells.
Engineering Parameters Tab
This is where the user can select the parameters they want, to run the Hydraulics calculation.
Hydraulics Model –four models are included as standard
Bingham Plastic
Power Law
Herschel Bulkley
Robertson Stiff
Bingham plastic uses PV and YP and mud weight, all other models use the fann readings and mud weight.
Surge / Swab – Specifies if the surge and swab calculation to be carried out is open or close ended. If modelling for a casing or liner assembly and close ended is used, the pressure loss through the float / shoe is taken into account.
Surge / Swab Reference – This is the reference point for the surge / swab calculation, select some common references from the combo box such as bit, shoe and bottom hole or click on the check box to enable a user defined depth.
User defined depth – Only active if the enable check box has been ticked, this will disable the surge / swab reference combo above and the surge and swab reference depth can be entered in the edit box.
ROP – Rate of penetration, this is used to calculate the cuttings loaded ECD’s and other hole cleaning parameters.
RPM – The rotational speed of the drill string. Additional pressure will be added based on the RPM.
ECD Adj – ECD adjustment is manual adjustment to all the ECD curves in order to better match the model with MWD PWD data.
SW Den – Sea water density, which is used for riserless drilling calculations
Surface Pressure Losses – The pressure loss through the surface equipment. This value is added to the total standpipe pressure calculated by the model.
must
Flow rate: This grid allows the flow rates for the hydraulics model to be entered. By default, the manual flow increment box is unchecked, and the user enters a flow rate in the middle cell of the grid. The software then automatically calculates flow rates above and below this base rate (±25% & 50%) with which to perform a sensitivity analysis. If you wish to override the automatic values generated, click the enable manual flow increment check box. This will leave the user with a single line and once filled a new line will be added. An unlimited number of flowrates can be entered.
Survey Selection: The user can select either Well Plan Surveys or Actual Surveys. There is also an option to select Composite Listing, which splices the actual surveys into the well plan surveys to create a composite listing.
Tripping Speed: This grid allows the tripping speeds for the hydraulics model to be entered. By default, the manual tripping increment box is unchecked, and the user enters a tripping speed in the middle cell of the grid. The software then automatically calculates tripping speeds above and below this base rate (±25% & 50%) with which to perform a sensitivity analysis. If you wish to override the automatic values generated, click the enable manual trip increment check box. This will leave the user with a single line and once filled a new line will be added. An unlimited number of trip speeds can be entered but the first trip speed entered will be used for the reports. The tripping speed is used in Surge Swab calculations.
Once the user has completed all the required inputs the calculation can be run. To do this, select either the icon displayed below, or select Calculate - Hydraulics
Once a calculation has been run, the hydraulics results section of the Engineering Parameters tab will be populated with the results. The results displayed are for the flow selected at the top right of this section. This flow is a drop-down menu which will contain the same flows input during the setup, so if only one flow was used, there will be only one available here. The depth can also be adjusted by clicking on the arrows to the right of the depth and it will scroll in 30m / 100ft intervals and display the results based on the depth and flow selected.
Note that whatever results are displayed in this section (based on the flow and depth selected), will be output in the summary report.
Once the calculation has been run, the Hydraulics Summary Report can be viewed by selecting the icon from the toolbar at the top of the screen. This contains an overview of the main values associated with the calculation and can be saved as a pdf.
If required, a more detailed report can be generated by selecting "File" - "Print Reports” or selecting the icon on the toolbar (highlighted above). The required data can be selected, and a report can be generated either as excel of pdf. Note that when excel is selected the chart selection will be greyed out as these can only be output as pdf.
Some of the Hydraulics results are available to view by selecting the toolbars along the top. This is a quick way to access some of the more commonly used plots.
All the Hydraulics plots and data are available to view by selecting the Hydraulics results at the top of the screen. The Data options display the numerical data used to generate the charts. Note that there is no option to view the data for the Annular Velocity Profile, CCI and Cuttings % Charts.
The hydraulics charts give a graphical representation of the theoretical values you would expect to see as the well is being drilled. Therefore, at each depth, the numbers displayed on the charts and the data tables can be directly compared with values recorded from the SPP gauge and down hole tools, as the well is being drilled.
This chart displays the standpipe pressure (SPP) expected at surface when the assembly is at any given depth. There will be a line displayed for each of the flowrates entered in the hydraulics section of the Engineering Tab. If pump liner data has been added to the pump data dialog in the tools menu, then this can also be represented on the chart via the add series dialog.
This chart displays the following lines for each of the flowrates entered in the hydraulics section of the Engineering Tab:
Clean ECD: The ECD at the end of the string, for any given depth, based on a cutting’s free annulus.
Dirty ECD: The ECD at the end of the string, for any given depth, based on a cutting’s loaded annulus. The volume of cuttings in the annulus is calculated based on the ROP entered in the hydraulics section of the Engineering Tab. If the ROP is entered as zero then the clean and dirty ECD lines will lie on top of each other.
ECD Snapshot: The ECD snapshot line shows the expected ECD at each point in the annulus when the string is at a given depth. This depth relates to the deepest depth represented on the chart. This line is generated based on a cuttings free annulus, which means that the last point for both the Clean ECD line and the ECD Snapshot line will be the same.
A line representing the Mud Weight is also displayed on the chart.
This chart displays the surge and swab lines for each of the tripping speeds entered in the hydraulics section of the Engineering Tab.
The Y axis corresponds to the bit depth (bottom of the assembly being run) regardless of what has been selected as the reference point. The results, however, display the calculated values at the reference point based on the bit position. So if for example you have the reference point selected as the bottom of the hole, when you look at the chart, it will be displaying the surge and swab pressures at the bottom of the hole, when the bit is at any given depth.
The reference point is selected in the hydraulics section of the Engineering Tab and is displayed at the top of the chart.
Innova Engineering Hydraulics Module contains 4 (snapshot) hole cleaning charts. A basic explanation is given below. For a more detailed explanation of these, see Innova's "Hole Cleaning Guide".
Flow rate is the dominant factor in cuttings removal while drilling directional wells. An increase in flow rate will result in more efficient cuttings removal under all conditions. However, how high a flow rate can be increased may be limited by:
• The maximum allowed ECD
• The susceptibility of the open hole section to hydraulic erosion
• The availability of rig hydraulic power
This is a snapshot chart and shows the Annular Velocity at all different points in the wellbore when the assembly is at a given depth for the various flow rates.
CCI (Cutting Carrying Index) is a measure of how clean a vertical (0-35° inc) well is.
• 0.5 or less and hole cleaning is poor & problems may be seen
• Greater than or equal to 1.0 indicates good hole cleaning
Annular Velocity and Mud weight (along with PV & YP values) are used in this calculation. The higher the annular velocity, the higher the CCI.
For sections of the wellbore where the inclination is greater than 35°, hole cleaning should be evaluated using the Cuttings % Chart.
This is a snapshot chart and shows the CCI at all different points in the wellbore when the assembly is at a given depth for the various flow rates.
The Cuttings % plot represents the percentage of the annulus which is taken up with cuttings. Anything above 5% should be considered a problem.
Unlike the CCI plot, this measure of hole cleaning is not limited by inclination and can be used for any well profile. This calculation is also affected by ROP and RPM. Increased ROP, increases the cuttings %.
This is a snapshot chart and shows the Cuttings % at all different points in the wellbore when the assembly is at a given depth for a given ROP at various different flow rates.
The minimum flow rate plot is a snapshot chart which shows the minimum flow required to keep the hole clean at all points in the wellbore for a range of ROPs at a certain depth.
The ROP value selected in the hydraulics setup (e.g. 10m/hr) will be used as the lowest ROP and 4 additional ROP values will be displayed which are automatically generated by the program and are pre-set percentages of the original (125%, 150%, 200% & 250%). These percentages are built into the program and are not adjustable by the user.
To interpret the plot, the user needs to find the largest flow rate for any one ROP and that will be the minimum flow that is required at that depth to keep the hole clean. This can be done by using the Screen Reader or the data table.
A guide to the Casing Wear chart within Innova Engineering.
Once a T&D calculation has been run, you can check the predicted casing wear:
TAD Results - Snapshot Charts - Casing Wear (for the plot)
TAD Results - Snapshot Data - Casing Wear (for the Data Table)
The casing wear is expressed as depth in ether inches or mm depending on what units are selected for Diameter. The depth of wear indicates depth of the groove which will be worn in to the side of the casing over a period of time.
This is calculated based on:
Side force (calculated)
ROP (Engineering Parameters tab - Torque and Drag section)
Length of the open hole section (Drill string, Well Geometry & Fluids tab - Well Geometry Section)
rpm (Engineering Parameters tab - Torque and Drag section)
Casing wear factor (Engineering Parameters tab - Torque and Drag section)
Casing Wear Factor – Casing wear factor, is defined as the ratio of friction factor to specific energy, E-10psi-1. The table below should be used as guide for casing wear factor selection.
This is a snapshot chart, which shows the predicted cumulative wear at each point in the casing when the assembly is at 11,820ft MD.
Casing Wear Rotating: This is the predicted wear on the casing when the string has 0 ROP
Casing Wear SO: This is the predicted casing wear calculated using the reaming slack off
A guide to the Apparent WOB Chart within Innova Engineering
Once a T&D calculation has been run, you can check the Apparent WOB Chart:
TAD Results - Drilling Charts - Apparent WOB (for the plot)
TAD Results - Drilling Data - Apparent WOB (for the Data Table)
This plot shows the Apparent WOB (Sliding) you need to see at surface (at each depth) in order to Actually have 15klbs WOB.
For example, in the above chart. @ 600ft MD with CH 0.25 OH 0.30 FF's, you would require 36.5klbs Apparent WOB (as seen on the drillers screen) to Actually have 30klbs WOB.
Once a T&D calculation has been run, you can check the Apparent WOB Snapshot Chart:
TAD Results - Snapshot Charts - Casing Wear (for the plot)
TAD Results - Snapshot Data - Casing Wear (for the Data Table)
This snapshot plot shows the Apparent WOB (Sliding) you will see at surface (for any one specific depth, which is displayed in the chart title) vs the Actual WOB.
For example, in the above chart. @ 11,820ft MD with CH 0.10 OH 0.15 FF's, with 35klbs Apparent WOB (as seen on the drillers screen) you would expect to have an Actual WOB of 30klbs.
A guide to the cementing module within Innova Engineering.
This document describes the cementing module within Innova Engineering and details the steps required to correctly utilise its functionality.
This document describes the cementing module within Innova Engineering and details the steps required to correctly utilise its functionality.
Units: Ensure that all units are correctly selected, based on requirements.
Options Menu – Cementing: The default flow rate in the Cementing tab is barrels per minute (bbls/min). This option allows the user to “Use flow units as pump rate”, which means the flow rate used in the cementing tab will match whatever the user has selected as the flow units from the units menu. This is useful when using the cementing section to simulate pumping pills etc.
To utilise the cementing modules functionality, the following inputs are required.
Drill String: Required inputs are component, description, OD, ID, TJ OD, TJ ID and length. Input the assembly as accurately as possible including the drill pipe to surface (note, for the last component e.g. DP to surface, the user does not have to input the exact length as the program will do this automatically based on the calculation depth. Inputting a nominal value of 10 is fine). Note that once a component type has been selected from the dropdown menu, it is possible to right click on the line and choose "select from Library", which will open the components library. The user can then select the appropriate component and select the option to insert it directly into the drill string grid.
Bit / Float TFA: If a float or bit has been included in the assembly, then it is important to enter the relevant TFA as this is required to calculate the pressure drop across this component, which is used in the pump pressure calculation. This is entered in the bit, casing or liner component details section.
Well Geometry: Input casing, liner, riser and open hole details including depths and ID's. For open hole, the ID is the same as the OD. Note that the user should only enter the well geometry which is relevant for the section in question and should not enter the entire casing string here.
Fluid Properties: Input mud weight, PV and YP. These inputs relate to the fluid in the wellbore prior to starting the cement job.
Survey Selection: Cementing calculations will be run using plan or survey data entered in the Survey Tab on the main user interface.
If there are well plan surveys and no actual surveys, the program will automatically use the well plan.
If there are actual surveys and no well plan surveys, the program will automatically use the actual.
If there are both well plan and actual surveys the program will use whatever is deeper.
Data is input as measured depth, inclination and azimuth in both the Actual Surveys and Well Plan sections, and the program will generate the rest of the numbers using whichever survey calculation method has been selected (Minimum Curvature Default). Cementing calculations are not run against surveys input in the RAW surveys table. The user can either enter the plan or surveys manually, import them or copy and paste the data directly into the cells.
This section displays the various volumes, capacities and displacements of the drill string and the annulus.
The top of this section details the different capacities of the drill string components. These components are taken directly from the drill string entered in the drill string tab, and the capacities are automatically calculated based on the dimensions (OD & ID) associated with these components. The annular capacities are detailed for the components, based on each of the lines entered in the Well Geometry section of the drill string tab. NOTE: A String Depth MUST be entered for this section to display correctly.
The middle part of this section shows the various capacities, volumes and displacements for the well. NOTE: A String Depth MUST be entered for this section to display correctly.
The lower part of this section is the most important as the inputs here affect the entire cementing calculations.
String Depth: Depth of the string when performing the cement job. The calculation will not run without a value entered here.
Displacement Type: Select Open Ended or Close Ended. This affects the Displacement and Total Displacement calculated values.
Flow Rate: Flow rate of cement job. This is used to calculate the Top Down, Bottoms Up and Full Circulation values. This input is not required to run the cementing calculation, as the pump rate for this is entered in the pumping schedule section.
Pump Output: Volume pumped per stroke. Pump efficiency should be factored into this input i.e. if the book output is 0.1bbl/stroke and the pump is 95% efficient, then output should be entered as 0.095bbl/stroke. This input is essential as it is required for calculating the number of strokes in the Pumping Schedule section.
Stroke Rate: This cell auto calculates based on the values entered for flow rate and pump output.
Hydraulics Model: Select from Bingham, Power Law, Herschel Bulkley or Robertson Stiff. This affects the calculated Annular Pressure, Pump Pressure and ECD values in the Cementing Results dialog.
This section allows the user to quickly calculate the volumes required for the cementing operation.
Row 1 should contain the first fluid to be pumped and the user can enter the required top, and the bottom will be automatically populated. The top and bottom depths of the fluid represent where they will be in the Annulus at the end of the cementing operations. The user can then enter as many additional lines as required. It should be noted that the bottom depth of the fluid in the last row will always be equal to the String Depth value input in the Volumes section.
The user can also enter the desired excess and the volume column will update automatically to reflect this excess percentage.
Once the Cement Volumes and Cement Job Calculation sections have been input, the user can select Create, which will populate the Pumping Schedule table, with the description and calculated volumes from the Cement Volumes section. Note that this also considers the data input in the Cement Job Calculation section. It is also possible to complete this section manually. In order for the schematic to be represented correctly in the results dialog, excess volume should not be included in this section.
If the Include Spacer box is checked and then Create is selected, row one of the table will be created for a spacer, but the volume cell will need to be populated manually by the user. If the user has included a spacer in the cement volumes section, then the include spacer box should not be checked.
The Use Rheometer Readings check box toggles the Pumping Schedule table between PV, YP and 600 – 3 rpm dial reading inputs.
The user should fill in the Description, Volume, Wt, Pump Rate, and rheology values for each row. These inputs affect the calculated Annular Pressure, Pump Pressure and ECD values in the Cementing Results dialog.
For conventional cement jobs the user should enter the Shoe – Float Distance. The shoe track capacity will be automatically calculated.
If cementing with a stinger, the user should check the Cementing with inner string box and enter the Description, OD, ID and Length of the stinger string. The capacity and total capacity of the inner string will be automatically calculated.
Once the cementing tab has been completed, selecting Calculate, opens the Cementing Results Dialog.
It is suggested that data is input in the following order to increase input efficiency. This is, however, just a guide and the user can enter the data in whatever sequence they wish.
Ensure units are correctly selected, including the cementing flow units in the Options menu.
Input data in the Drill String table. Input the component, description, OD, ID, length and TJ OD / ID if applicable (Drill String, Well Geometry & Fluids Tab).
Input any relevant TFA details in the Component details table (Drill String, Well Geometry & Fluids Tab).
Input the Well Geometry (Drill String, Well Geometry & Fluids Tab).
Input the drilling Fluid Properties (Drill String, Well Geometry & Fluids Tab).
Input the survey data into the Well Plan or Actual Surveys table (Surveys Tab).
Input the String Depth (Cementing Tab).
Select the Displacement Type (Cementing Tab).
Input the Flow Rate (optional) (Cementing Tab).
Input the Pump Output (Cementing Tab).
Select the Hydraulics Model (Cementing Tab).
Input the Description, Top and Excess % for each fluid in the Cement Volumes table (Cementing Tab).
Input the Shoe – Float Distance (Cementing Tab).
Add cementing inner string Description, OD, ID and Length if applicable (Cementing Tab).
If a spacer is being included and was not added in the cement volumes section check the Include Spacer checkbox (Cementing Tab).
Select the Create button in the Pumping Schedule section (Cementing Tab).
Input the Weight (Wt), Pump Rate, fluid rheology and spacer volume (if applicable) data (Cementing Tab).
Select the Calculate button to run the cementing calculation and open the Cementing Results dialog (Cementing Tab).
Once the user has entered all the required inputs, the user selects Calculate from the Cement Job Calculation section. This runs the cementing calculation and opens the cementing results dialog.
The Cementing Results dialog displays all the information and results relevant to the cementing module. By utilising the scroll bar at the bottom of the dialog the user can view the three charts at different stages of the cement job.
This is a visual representation of the well geometry, string and fluids at a given stage in the cement job, dictated by the position selected on the scroll bar. The values used to generate this schematic (MD, component OD & ID’s and well geometry OD & ID’s) are taken from the values entered in the Drill String, Well Geometry and Fluids Tab. The fluid labels can be toggled on or off by selecting Chart Options and checking or unchecking Show Schematic Fluid Labels.
Changes in well geometry are marked by a label and dashed line.
Areas out with the fluid flow path are white.
Sea water is dark blue
Drilling mud is brown.
Spacer is light blue.
Lead cement is dark grey.
Tail cement is light grey.
Displacement fluid is a variable colour.
The Pumping Schedule chart depicts:
The annular pressure at the string depth entered in the volumes section
The equivalent circulating density (ECD) at the string depth entered in the volumes section
The pump pressure at surface at a given stage in the cement job
The Flow Rate
All the above outputs are dictated by the position selected on the scroll bar.
The X-axis can be toggled to display either Elapsed Time or Strokes by selecting Chart Options and checking or unchecking X Axis – Strokes.
The position of the slider on the scroll bar dictates the stage of the cement job depicted on the Cementing Schematic, Pumping Scheldule and ECD Snapshot. The user can click the play button for the slider to commence movement at a specific speed. This speed can be adjusted using the + and – keys to speed up and slow down the slider progression respectively. The user can then select the pause button to stop the slider at any point. The slider can also be manually dragged to any point in the scroll bar by the user.
The ECD Snapshot chart depicts the equivalent circulating density and the annular velocity, across all depths from surface to the string depth, at a given stage in the cement job, dictated by the position selected on the scroll bar.
The right-hand side of the chart shows the flow regime across all depths from surface to the string depth, at a given stage in the cement job, dictated by the position selected on the scroll bar. Red is Laminar Flow and Green is Turbulent.
Additionally, markers display the respective depths of the top of the various fluids in the annulus and any changes in the well geometry.
Within the Cementing Results dialog, the user can output the following via the file menu:
PDF Cementing Report
Excel Cementing Report
Export Data
The user selects File > Print PDF Report. This generates a report which can be saved to pdf format.
The report includes all the relevant data used in the cementing calculation and the charts displayed within the Cementing Results dialog, as they appeared when the report was created.
The user selects File > Print Excel Report. This generates a report which can be saved to excel format.
The report includes all the relevant data used in the cementing calculation and the charts displayed within the Cementing Results dialog, as they appeared when the report was created. These charts are allocated their own sheet within the excel document.
This option allows the user to export the data used to generate the Pumping Schedule and ECD Snapshot Charts.
The context menu is available in every plot by right clicking anywhere on the plot. This allows the user to change certain aspects of the plot based on their requirements.
Viewing Style – Allows the user to select the desired Chart style.
Border Style – Allows the user to select the desired Border style of the chart.
Font Size – Allows the user to select the desired font size, which will affect all fonts on the chart including title and axis labels. Large, Medium or Small.
Plotting Method – Allows the user to select the way the line is plotted: Point, Line, Bar, Points + Line, Spline Area.
Data Shadows – Allows the user to select between off, shadow and 3D.
Grid Options – Allows the user to change the grid options in the chart.
Mark Data Points – Adds the data points relating to the data labels
Undo Zoom – Resets the zoom on the chart. Pressing the Z button has the same effect.
Maximise – Maximises the chart to fill the screen. Escape button exits this view.
Customization Dialog – Opens a dialog with more user definable chart options.
Export Dialogue – Allows the user to Export the chart using multiple image formats: EMF, WMF, BMP, JPG and PNG. The user has 3 options:
Clipboard: exports directly to clipboard, allowing images to be quickly added to word, excel & PowerPoint documents
File: Creates an image file of the chart which can be used on its own or imported into any suitable document
Printer: Sends the chart to the printer
The user can also choose the relevant Width, Pixels and DPI to use for the export. For Clipboard and File options, Pixels is the only available selection. When Printer is selected, the Millimetres, Inches and Points options become available to select.
A step by step guide to installing Innova Engineering.
Innova engineering can be supplied as a zipped installation file which must be unzipped before use. Right click on the file and select “Extract All….” From the context menu.
Select a location which you wish to extract the files to and click “Extract”. The installation files will be extracted to the selected location in a folder called “Innova Engineering”
Once the files have been extracted, open the Innova Engineering folder and double click on the “Innova Engineering vx.x.x.exe” file to begin the installation process.
Select the location which you wish to install Innova Engineering. The default location is “C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering”. If you wish to change the location the program is installed to click on the “…” button.
Click on “License terms and conditions”. This will display the below screen.
Read the terms and conditions. This information can also be printed for future reference by selecting the printer icon. Once read, select the “Accept and Install” button to begin installation.
If the copy of Innova Engineering is genuine the user will be presented with a dialog showing the verified publisher as “Innova Drilling & Intervention”. If not the software is not genuine and should not be used. Click “Yes” to continue the installation.
Once the installation is complete the final dialog will display “Innova Engineering has been successfully installed”. Select “Finish” to close the dialog. An icon will have been added to the desktop and an entry for “Innova Engineering” will be in the start menu.
A guide to the drill pipe fatigue plot within Innova Engineering
Drill string fatigue will only occur while rotating and only while rotating over a dogleg. The more tension within the pipe the more likely it is to get fatigued. There is a critical value of dogleg where fatigue failure becomes an issue.
The Drill Pipe Fatigue Chart, is a snapshot chart which displays the actual dogleg and the critical dogleg at every point in the string for a given depth. If the actual dogleg is greater than the critical dogleg then fatigue failure is a potential issue.
The critical dogleg curve is generated based on the free rotating weight of the drilling assembly. One point to note is that back reaming will increase the tension and therefore reduce the critical rotating dogleg; however, this has not been included in the chart because back reaming operations do not generally last too long.
Once a T&D calculation has been run, you can check the Drill Pipe Fatigue Chart:
TAD Results - Snapshot Charts - Drill Pipe Fatigue (for the plot)
TAD Results - Snapshot Data - Drill Pipe Fatigue (for the Data Table)
A guide to the hole cleaning charts within the Innova Engineering hydraulics module.
In the Hydraulics Module of Innova's Engineering software, there are 4 plots dedicated to hole cleaning. This document is a guide to these plots and how to interpret the results.
Once a hydraulics calculation has been run, you can check the hole cleaning charts by going to: Hydraulics Results - Hole Cleaning.
Flow rate is the dominant factor in cuttings removal while drilling directional wells. An increase in flow rate will result in more efficient cuttings removal under all conditions. However, how high a flow rate can be increased may be limited by:
The maximum allowed ECD
The susceptibility of the open hole section to hydraulic erosion
The availability of rig hydraulic power
This is a snapshot chart and shows the Annular Velocity at all different points in the wellbore when the assembly is at a given depth for various different flow rates.
CCI (Cutting Carrying Index) is a measure of how clean a vertical (0-35° inc) well is.
0.5 or less and hole cleaning is poor & problems may be seen
Greater than or equal to 1.0 indicates good hole cleaning
Annular Velocity and Mud weight (along with PV & YP values) are used in this calculation. The higher the annular velocity, the higher the CCI.
For sections of the wellbore where the inclination is greater than 35°, hole cleaning should be evaluated using the Cuttings % Plot.
This is a snapshot chart and shows the CCI at all different points in the wellbore when the assembly is at a given depth for various different flow rates.
The Cuttings % plot represents the percentage of the annulus which is taken up with cuttings. Anything above 5% should be considered a problem.
Unlike the CCI plot, this measure of hole cleaning is not limited by inclination and can be used for any well profile. This calculation is also affected by ROP. Increased ROP, increases the cuttings %.
This is a snapshot chart and shows the Cuttings % at all different points in the wellbore when the assembly is at a given depth for a given ROP at various different flow rates.
The minimum flow rate plot is a snapshot chart which shows the minimum flow required to keep the hole clean at all points in the wellbore for a range of ROPs at a certain depth.
The ROP value selected in the hydraulics setup (in this example 10m/hr) will be used as the lowest ROP and 4 additional ROP values will be displayed which are automatically generated by the program and are pre set percentages of the original (125%, 150%, 200% & 250%). These percentages are built into the program and are not adjustable by the user.
To interpret the plot, you need to find the largest flow rate for any one ROP and that will be the minimum flow that is required at that depth to keep the hole clean. This can be done by using the Screen Reader or the data table.
In the plot above, for an ROP of 12.5m/hr @ 1006m MD, the minimum flow rate required to keep the hole clean would be ~1,512 lpm.
A guide to the SAG survey correction module in Innova Engineering
SAG occurs when a BHA bends under its own weight when positioned between two points of stabilisation. The degree of bending is affected by the hole size, stabiliser size, distance between points of stabilisation, and tubular OD & ID. SAG causes MWD sensor misalignment in relation to the borehole, and accounts for up to 80% of wellbore TVD position uncertainty.
The purpose of this document is to guide the user through the setup, calculation and the interpretation of the results of the SAG module in Innova Engineering.
Before inputting data, the user should configure the relevant options in the Units menu and the Options menu:
Units: Ensure that all of the units are correctly selected, based on your inputs.
Options – Include Motor Bend in BHA Analysis: This lets you toggle whether the program factors in the bend angle in your motor into the SAG calculation. See Section 7.2 for additional considerations when using this option.
Options – SAG Calculation Precision: This will let you set the number of decimal places that the SAG results will be calculated to. Default is 3.
In order to run SAG, the user is required to enter data into the Drill String, Well Geometry and Fluids Tab and the Surveys Tab.
In order to run SAG, the following parts of the Drill String, Well Geometry and Fluids Tab require data entered:
Well Geometry: The wellbore geometry tells the program the size of hole that the assembly is in.
Mud Weight: The mud weight is used to calculate the buoyancy of the drill string.
Drill string – All components: Enter your drill string into the Drill String section. This does not need to include any more than ~30m (100ft) of assembly beyond the last point of stabilisation. Beyond this point the remainder of the drill string will be lying on the low side of the hole and is not considered in the calculation. All components entered into the main Drill String table must have a component type, length, OD and ID. This includes items that don’t normally come with an ID, such as the motor or the bit.
Drill String – Stabilizers: As well as the above requirements, stabilizers require the following information entered into their component properties:
Stab OD: The outside diameter of the stabilizer.
Stab Blade Length: The length of the stabilizer blade that will be in contact with the side of the hole – Watch your units, this will be in inches or mm, depending on your diameter unit.
Stab Distance from Bottom: The distance from the Pin end shoulder to the bottom of the stab blade
Note: There is also space to enter stabilizer information into the component details for RSS, MWD/LWD, Motor, Turbine and Reamer component types. If you have stabilizer sleeves on any of these items in your BHA, don’t forget to enter the details for them as well.
Drill String – Motor Bend: If you have a motor in your BHA, you can enter the motor bend angle in the component details section. This is only required if you have the Include Motor Bend in BHA Analysis option toggled on.
In order to run SAG, the following parts of the Surveys Tab require data entered:
Survey Offset: The distance between the cutting surface of the bit and the MWD inclination sensor.
Select the type of SAG calculation that you want to run from the drop down box in the Survey Connections section. Users have a choice of Single, Inclination Range or Surveys. Single and Inclination Range are configured in the Survey Corrections section.
Selecting Single allows the user to calculate a SAG correction based on a single inclination:
Inc: Inclination that the user requires SAG results for.
DLS: Dogleg (°/30m or °/100ft depending on units selected). The program will use the dogleg to simulate hole curvature which affects the results. Zero represents a tangent.
TF: The Toolface of the motor bend during the survey. If the Include Motor Bend in BHA Analysis option toggled is toggled off, this will have no effect.
Selecting Inc Range allows the user to calculate SAG over a range of inclinations:
Inc Start: Initial Inclination.
Inc Stop: Final Inclination.
Inc Step: Step change in inclination between the initial and final. A step change of 2.5° will calculate SAG every 2.5° between the selected range.
DLS: Dogleg (°/30m or °/100ft depending on units selected). The program will use the dogleg to simulate hole curvature which affects the results. Zero represents a tangent.
TF: The Toolface of the motor bend during the survey. If the Include Motor Bend in BHA Analysis option toggled is toggled off, this will have no effect.
Selecting Surveys allows the user to calculate SAG on Actual Surveys, Well Plan Points or RAW Surveys, depending on what is selected. As well as the offset, the toolface of the motor is the only value in the Survey Corrections section that effects this calculation type. If the Include Motor Bend in BHA Analysis option toggled is toggled off, the TF will have no effect.
Select your survey type from the drop down box in the Survey Selection section, and then enter your surveys into the table. SAG can be run on Raw Surveys, Actual Surveys or Well Plan points. Whichever is selected in the Surveys tab when the calculation is run will be used.
Actual Surveys and Well Plan requires you to enter surveys using Measured Depth, Inclination and Azimuth. Raw Surveys require Measured Depth, raw Accelerometer Values (G) and raw Magnetometer Values (H). Make sure that you are using the correct units for your accelerometers and magnetometers.
To run the calculation, open the Calculate menu and select BHA Analysis and SAG Correction. The calculation will run and the results window will appear. You may also receive a warning. The most common warnings are:
WOB greater than zero, SAG correction value may be incorrect: The WOB parameter entered into the Engineering Parameters tab has an effect on the SAG result. Depending on your circumstances this may not be an error, but as surveys are usually taken when the bit is off bottom, the program will warn you if a value other than zero is entered.
No stabilizers: You have not entered any information in the component details for stabilizers, or components with stabilizer sleeves.
BHA tangential point found before sensor for 1 or more surveys: The tangential point is the point above the last stabilizer where the assembly touches the side of the hole. Anything above this point will be lying against the side of the hole and will therefore not be subjected to SAG. It is important to note that the tangential point changes depending on the curvature of the hole, and in some instances when running the calculation there will be some stations that will require correction and others that will not. Engineering runs through all of these calculations and assigns a 0° correction to those that do not. If you think you are getting this message in error, it is usually because you have set your survey offset too far back from the last stabilizer.
The following outputs are displayed in the SAG Results window:
Deflected Shape: Shows how far the BHA is from the centre line of the well bore. The X-Axis shows the distance from the bit along the BHA. The Y-Axis shows the deflection. The blue dot represents the sensor position. Note that the displayed plot always represents the final survey station.
BHA Slope: Shows the angle of the BHA with respect to the centre line of the well bore. The X-Axis shows the distance from the bit along the BHA. The Y-Axis shows the slope. The blue dot represents the sensor position, and the slope at this position is the error that is being corrected by the SAG correction. The displayed plot always represents the final station.
Below the charts is the results table, which contains the following information:
MD: Measured Depth of each survey station.
Inc (Org): The original uncorrected inclination of the survey.
Inc (Corr): The SAG corrected inclination.
Sag (Corr): The SAG correction to be applied to the uncorrected inclination to get the corrected inclination. Note that SAG correction is always added.
After running the calculation, the SAG column will be populated in the Survey tab and in the MSA window. Select SAG corrected Inc from the Inclination to Use drop down to use the corrected inclination when calculating the TVD, NS, EW and VS values.
A SAG report can be created with the following steps:
Close the results window. In the main Engineering interface, open the File menu and select Print Reports.
Configure your format and other options in the Options section.
Select the BHA Analysis and SAG type to create a SAG report. You can customize the report using the below options:
Before running the SAG calculation there are a couple of things to consider:
From 0-3° inclination the potential correction will likely be invalid due to the difficulty with finding the point at which the top of the BHA contacts the wellbore, this is due to the hole not having a defined highside.
Due to this, most companies have a policy that SAG should not be applied until the inclination is >3°. However, >5° is also acceptable in certain circumstances.
This consideration applies when using the Surveys calculation type.
If the motor bend is not being modelled in Engineering (Bend angle is 0° in the motor component details, or Include Motor Bend in BHA Analysis is turned off) then it is possible to SAG correct all required survey stations in one go. If however, the motor bend is being modelled, then each station has to be SAG corrected individually, assigning the relevant Toolface for each survey. This is more labour intensive and therefore more susceptible to errors.
When the bend is not being modelled, the addition of new stations has no effect on previous corrections. This is not the case when modelling the bend. When a new survey station is added and the correction run, the program runs the correction against all of the previous stations using the assigned toolface. Since every station will likely have been measured on a different toolface, it is possible that the program may change some of the previous corrections based on the new toolface. For this reason it is important to carefully note the correction at each new station as it is calculated, and understand why you may see a difference when looking at earlier corrections.
It is recommended that you try toggling the option on/off and comparing results. If there is a negligible difference, it may be simpler to leave the option off.
A guide to Innova's QAQC, Short Collar Correction (SCC) and Multi Station Analysis modules within Innova Engineering.
The following document is a guide to Innova's QAQC, Short Collar Correction (SCC) and Multi Station Analysis modules within Innova Engineering.
The purpose of this document is to guide a new user through the layout, setup, calculation and outputs for these modules.
This module takes raw data from the MWD accelerometer (GX, GY & GZ) and magnetometer (HX, HY & HZ) and checks the generated outputs against the local geomagnetic data to ensure that the survey falls within accepted tolerances.
In order to run the QAQC check, the following inputs are required.
RAW Survey Data section of the Surveys tab
Latitude: Required to calculate the SCC Delta Azi in the Magnetic Spacing Calculator
HL Ref – Reference magnetic field
Dip Ref – Reference magnetic dip angle
TAC – Total Applied Correction - Automatically calculated based on North Reference selected
Grid convergence – Angle between True North & Grid North from True North
Declination – Magnetic declination - Angle between True North & Magnetic North from True North
North reference – The north reference the surveys are referenced to. Either True or Grid.
This data is generally obtained from the well planning department who generate the data using programs like IGRF, BGGM & HDGM.
Magnetic Units associated with HX, HY & HZ.
Geolink / Tensor (mv), SSP / SUCOP (uT), nT, nT no XY inversion, EVO / Applied Physics or Vertex
Accelerometer Units: Associated with GX, GY & GZ.
G or mG. The option to Invert Z Axis can be checked or unchecked irrespective of the accelerometer unit choice
Raw data from the MWD tool (GX, GY, GZ, HX, HY & HZ) + Measured Depth
It is important that the correct QC limits are set. These values are the ± limits used to compare the measured values against the calculated values. If these limits are not accurate it is possible that surveys may pass, which should not pass and conversely surveys may fail, when they should pass.
The QC default limits set in Engineer are industry standard. It is however possible to change these if required. You can do this as follows:
In the Surveys tab, select Raw Surveys from the Survey Selection drop down.
Select Options from the top toolbar and then Raw Survey QC Limits.
Note, that you can only access these values when you have Raw Surveys selected.
Individual limits can now be changed as required.
Note, that any changes made to these limits will only be valid for each specific project. When creating a new project, limits will be the default values until changed.
Ensure that the correct units have been selected, fill in the RAW Surveys Tab data (HL, Dip etc) and ensure that you have the correct RAW survey QC limits assigned.
Ensure that you have the correct survey calculation method selected: Options - Survey Calculation Method. The default is Minimum Curvature and is very unlikely to be anything other than this.
Select Raw surveys from the survey selection drop down menu.
You can now enter your raw MWD data on a survey by survey basis, or if you are retrospectively checking an existing survey you can add the whole thing in one go
You can copy and paste the data, or
Go to File - Import Survey - you can then select the file you want to import
Note that in the drop down file type menu, there is an option that says Navigator SCC .txt. This should be used when importing Navigator export files (Navigator export files also contain the Geomag data; therefore, once imported ensure the Geomag data that has been pulled in is correct)
The generated HL, GT and Dip values are compared to the reference data in the RAW surveys Tab and any of the generated values out with the selected QC limits will be highlighted in RED. For a survey station to pass the QAQC procedure, they must fall within the QC limits and therefore not be highlighted.
Any surveys which have been highlighted should be rejected and retaken, unless it is possible to use the Short Collar Correction (SCC) algorithm to correct them to within the accepted limits.
The values in the SCC column's will be generated regardless of whether a survey passes QAQC or not, and should therefore be disregarded, unless of course you are using the correction.
Short Collar Correction (SCC) corrects for magnetic interference in the Z axis. It should be noted that for the short collar correction algorithm to work correctly the Z axis must be aligned with the hole direction i.e. the Z axis points along hole. If this is not the case the short collar correction algorithm will not work. All major MWD companies with the exception of Schlumberger have the Z axis aligned with the along hole direction.
Firstly, you need to ensure that the following data has been added to Engineering.
Proposed BHA with the relevant components marked as non-magnetic
Well Plan, in the Surveys Tab under Well Plan Surveys
Raw Survey Data section and Sensor offset in the Survey Corrections section
You can now calculate the well path magnetics: Calculate - Wellpath Magnetic Interference
A window will now appear with the results and will look like the screen shot below.
Results
Azimuth: The azimuth displayed is referenced to Magnetic North and will therefore look different when compared to the azimuth that was entered in the plan (which could be referenced to Grid or True North). The correction applied to the input azimuth is automatic and is based on the Geomagnetic data that you have entered in the Raw Survey Data Section.
Delta Bz: The expected error between the Theoretical Bz and the Measured Bz (from MWD) for raw, uncorrected surveys.
Delta Azimuth: The expected error in the raw uncorrected azimuth reading, <0.5 degrees is considered acceptable
Delta Dip: The expected error between the calculated dip (from the geo-mag data) and the actual measured value (from MWD). This will be highlighted in red if the value is greater than the tolerance entered in the QC Limits dialog.
Delta HL: The expected error between the calculated magnetic field strength (from the geo-mag data) and the actual measured value (from MWD). This will be highlighted in red if the value is greater than the tolerance entered in the QC Limits dialog.
Theoretical Bz: The theoretical magnetic field strength expected in the Z axis with no interference.
SCC Delta Azi: The expected error in the SCC corrected azimuth, <0.5 degrees is considered acceptable. This is affected by the Latitude entered in the Raw Survey Data section.
The P1 and P2 pole strength values are automatically selected based on the component type and size above and below the non mag components in the string. These can be overridden by the user if necessary, by checking the override pole box at the bottom right of the dialog and alternative values can then be entered by the user. Once entered, the user must select recalculate.
The whole output can be saved to pdf by selecting File – Export to PDF.
The data table can be exported to Excel by selecting File - Export.
These results can be used to make an informed decision as to whether there is a requirement to run the SCC algorithm, add additional non-mag or do nothing. Company policy will dictate what error values are considered acceptable.
When it is deemed necessary to run SCC, careful consideration should be given to the planned well path, as there are defined limitations to the SCC which must be adhered to. Failure to follow these guidelines could result in surveys passing correction which should not. The SCC limits are listed in the table below.
Note 1 – If possible, SCC should NOT be used and the BHA should be correctly spaced with non-magnetic tubulars as required.
Note 2 – SCC must NOT be used if the well path is known to be within these parameters. Again, the BHA should be correctly spaced with non-magnetic tubulars as required.
If the above parameters are encountered, then the SCC algorithm will not function correctly and erratic corrected data will be seen. It is therefore necessary to discuss beforehand with the Directional Driller/Company Representative as to an agreeable plan of action if the above criteria are expected to be encountered during the drilling that particular borehole.
If the planned wellbore falls out with the above limitations, SCC should NOT be used, and you should ensure that the BHA has the correct non-mag spacing.
When running the SCC, raw survey data is added in the same way as you do for the QAQC.
As with the QAQC, any numbers which are out of spec are highlighted red and should not be used. However, there are 3 columns (Azi SCC, HL SCC & Dip SCC) which contain corrected values, and as long as all 3 of these columns are not red, the Azi SCC value can be used instead of the calculated azimuth.
If even one of these 3 cells are red, the corrected azimuth should not be used, and the survey should be retaken.
Multi Station Analysis is a technique which can be used to calculate Magnetometer biases in the X, Y & Z axis. This is achieved by examining the measured and theoretical values at each sensor over multiple stations to find corrections which minimise the errors. These corrections are then applied to all the raw values to produce corrected surveys.
This section will assume that the user has input all data required to run SCC, as these steps must be complete before MSA can be calculated. In the Surveys tab on the main screen, select the MSA radio button located at the bottom right of the screen, this will open the Multi Station Analysis dialog.
All the RAW surveys populated on the main screen can be found here – Note that these inputs are NOT editable on this page.
The HL Ref box located at the top left of the screen will contain the value entered on the main surveys tab. This can however be changed on this screen if a more accurate value is supplied e.g. from an IFR model
MSA Parameters: The user can select the required Bias and SF start, stop and Step values. If the LSQ fit does not show a good curve with a minimum found these values can be adjusted to extend the range of the calculation. Changing the step size can speed up / slow down the calculation but a smaller step size can increase the accuracy.
Values in Use: The user can choose which values to use for the calculation:
Bz: Choose between SCC or raw. This determines which Bz value is used in the MSA calculation. If there is a large amount of interference in the Z axis, select the SCC option as the Z axis interference from the drill string must be removed before the MSA calculation can be run. If, however the BHA is correctly spaced or the assembly is run in the SCC no-go zones, then the raw value should be used.
Azimuth: This selection determines which azimuth is used in the survey calculation and only affects TVD, NS, EW, DLS etc
Inclination: This selection determines which inclination is used in the survey calculation and only affects TVD, NS, EW, DLS etc
Apply Gt Weighting: Surveys at a higher inclination are given more weighting in the calculation than surveys at lower inclinations. This is because they have more of an effect on azimuth. Ticking this box defines if the weighting is applied.
Override Correction: When this box is ticked the user can manually edit the Bias X, Y, Z and Scale X, Y, Z values.
To run the MSA calculation, select the “Calculate MSA” radio button. The MSA columns will populate with the relevant corrected values. As with the SCC results, anything out of spec will be highlighted in red.
At the left-hand side of the screen, if required the user can deselect any survey station which is out of spec. Once the relevant surveys have been deselected it is possible to rerun the calculation. The lines which have been deselected will have blank cells in the MSA columns, and this station will not be included in the calculation.
The MSA report and output charts are separate from the QAQC and SCC reports.
Once a calculation has been run, if required the user can generate a report. This can be done by either selecting the Report icon or by going to File - Print Reports.
Select the Surveys tab and select raw surveys. It is possible to create the report as PDF or Excel. Then select File - Print.
The MSA reports are accessed directly from the MSA window and are NOT available from the Print Reports section. Once MSA has been calculated the user can select File – Print Report.
This generates a PDF report which includes the MSA results, Magnetics, Pseudo Bias & SF values and a listing of the corrected surveys. Note that any stations which were deselected will not appear in this listing.
The user can also export the main MSA data table, as displayed on the main MSA interface. This can be exported as a .txt or Excel file. To export this data, select File – Export.
In addition to the reports, the View menu contains QA/QC and other tools to evaluate the data.
The LSQ Data table shows the data from the least squares fit
The Azimuth Comparison chart, provides the user with a visual representation of the Uncorrected azimuth against the SCC corrected azimuth and the MSA azimuth.
The HL comparison chart gives the user a visual representation of the reference HL against the measured (uncorrected) HL and the SCC & MSA corrected HL values. The chart also includes the tolerance lines which make it very easy to quickly identify any points which are out with the QC parameters
The Dip comparison chart gives the user a visual representation of the reference Dip against the measured (uncorrected) Dip and the SCC & MSA corrected Dip values. The chart also includes the tolerance lines which make it very easy to quickly identify any points which are out with the QC parameters
The BH BV Scatter Plot shows the horizontal and vertical components of the sensor readings plotted against the QC values. Ideally, they should all reside within the limits
The LQS Chart shows the least squares fit. If a V shape curve is seen the minimum has been found and the calculation is a success. If any one of the charts does not show a “minimum found” the calculation must be re-run.
This Chart plots the difference in the RAW and MSA corrected azimuths against the HSTF recorded when the survey was taken. This chart gives a good visual representation of the number of surveys taken in each quadrant. For best results, an even spread is ideal, but it is essential that there are at least some survey points in each quadrant.
The Delta Azi Plot shows the difference in azimuth between the MSA and RAW azimuth and the SCC and RAW azimuth.
The Delta Dip Plot shows the difference in the dip between the MSA and RAW dip and the SCC and RAW dip.
The Delta HL Plot shows the difference in the HL between the MSA and RAW dip and the SCC and RAW dip.
This plot shows the difference between the corrected and uncorrected surveys in the plan view.
This plot shows the difference between the corrected and uncorrected surveys in the section view.
The GT Plot shows the measured GT values against the value entered in the magnetics section.
Selecting this option, displays labels on the BH BV Scatter plot.
Allows the user to select which plots to include in the reports.
A guide to integration with the Oasis ERP software by Merge Solutions, using Well Seeker Pro and the Innova Web Portal.
The Oasis integration within the Innova software allows the user to pull cost and inventory data from Oasis. This information can then be utilized in the daily reporting features, where daily costs and tool hours are recorded, and once complete, this data can be transferred back to Oasis.
The Oasis integration guide for both Well Seeker and the Innova Web Portal is contained under the Well Seeker Pro Guides section. To view it, follow the below link:
Guides a company administrator through creating a user on the Web Portal or Mobile App that is restricted to specific operators, products or features.
Your organization may wish to give third parties permissions based access to your server database data, so that they can view progress on drilling projects etc., via the Innova Web Portal or the Innova Mobile App. To do this in a way that keeps your data secure and that respects the confidentiality of other clients, third party levels of access must be controlled.
The User Management section of the Web Portal contains options that allow you to customize the level of access for users viewing your organization’s data. Users can have their access customized in the following ways:
Their permission to create new data, and edit or delete existing data. Removing all permissions turns the user into a ‘view only’ user, who can view data but not edit it.
Their access can be restricted so that they can only view data for specific operators or wells.
Their access to Products & Features within the Web Portal and Mobile App can be restricted.
There are 2 different ways a third party user can be given access to a database:
The first way is to create a new user within your organization and assign the appropriate role to this user. In this situation, everything about this user is controlled by you as a company administrator.
The second way is to provide access to a user who already has login credentials for a different company. For example, an Operator may already have their own server database, where they have logins for all the appropriate members of their team. In this situation, it is possible to provide access to your companies database to one or all of these users. When doing this, the admin will assign an appropriate role and can restrict access to wells and features, but overall management of this user is controlled by their own admin.
This document will guide an admin through the process of adding a user in both of the above scenarios.
User access is controlled through the creation and assignment of roles. A role is a set of user permissions that can be applied to multiple users. Follow the below steps to create a customized view only role that can then be applied to any user in your organization, and also any user from outside your organization:
In the main menu, scroll to the bottom and click on User Management, then click on Roles.
This will open the User Roles page.
Create a new role by filling in the fields at the bottom of the page. Once you have filled in all three fields, the new role will be automatically added to the list. Double click on each field to edit it:
In the Organization field, choose your company from the dropdown. There will only be one option available here.
Enter a name for the new role in the Name field.
Give your role a brief description in the Description field.
Turn the new role into a view only role by toggling OFF the Admin, Edit, Delete, Create and Approve permissions. Users that are assigned a view only role will be able to view data in the portal but not make any changes to it.
Restrict the operators that the new role can access by checking ON the operator(s) that you want to grant access to, while leaving the others toggled OFF. In this example, we are allowing the role to only view data related to the operator ‘Black Oil & Gold, LCC’. Click on Apply to save your settings. Note: Leaving all operators checked OFF will allow the role to access ALL operators.
Choose which features the new role will have access to in the Web Portal and Mobile App by checking the checkboxes in their respective columns. Toggling on features in the Third Party column will allow users with the role to make API requests to the Innova API.
If you allow access to any features in a column, you must also check the Base feature at the top of each column.
Note: The only feature available for Well Seeker is the Base feature. Toggling this option off will prevent the user from logging into your organization’s server database via Well Seeker. This is recommended if you are setting up a viewer only user, as the permissions defined in step 4 do not apply to Well Seeker. Access to other features in Well Seeker are controlled by the user’s license and cannot be restricted via Roles. The assigned operator access will apply when the user logs into your organization’s remote server database via Well Seeker.
Click on the Apply button in the Products and Features window to save your settings. Setup of the view only and operator restricted role is now complete. The next step is to assign the role to a user.
Now that the customized view only role has been created, it needs to be applied to a user.
In the main menu, scroll to the bottom and click on User Management, then click on Users.
This will open the Users page.
Double click in the Role column for the existing user. From the dropdown menu, select the restricted role that you created. This is why it is important to name your roles appropriately, as this list may have quite a number of options available to choose from.
When the user next logs into the Web Portal or App, they will now be restricted to the operators and features permitted by their Role. They will also not have permission to make any changes to the data in the database.
In the main menu, scroll to the bottom and click on User Management, then click on Users.
This will open the Users page.
Create a new user by filling in the fields at the bottom of the page. Double click on each field to edit it:
In the Organization field, choose your company from the dropdown. There will only be one option here.
Enter an email address for the new user in the Username field. The username must be a valid email address.
In the Password field, enter a temporary password. This must contain at least one uppercase letter, lowercase letter, number and symbol.
In the RoleID field, select the restricted role that you created from the dropdown list.
In the UnitPrefs field, select the default unit set for the new user. They can change this themselves after they log in.
Before the new user creation can complete, you must toggle the Password Reset Required option on. This will force the new user to create their own password when they first log into the Web Portal. Once all of the required fields have been filled in, the new user will automatically be added to the list of users for your organization.
When the user logs into the Web Portal or App, they will now be restricted to the operators and features permitted by their Role. They will also not have permission to make any changes to the data in the database.
Once a user has been assigned a role in the Users page, they can be granted access to additional operators beyond those defined by their role. They can also be restricted to specific wells, if required. To do so, follow the below steps:
Toggle ON operators that you want the user to be able to access. Click on Apply to save your changes. The chosen operators will be added to the permitted operators granted by the user’s role. In this example, the user’s role grants access to Black Oil & Gold, LLC, but this specific user has also been granted access to Venture E&P and Gold Resources.
Click on Apply to save your changes.
This will display a list of all wells contained under the operators that the user can access. The list can be filtered by typing in the search bar at the top of the list.
By default, the wells will all be toggled OFF. When this is the case, the user has access to ALL wells under the operators permitted by their role.
To restrict access for the user, toggle the wells you want them to be able to access ON. The user will now only be able to access wells that have been toggled on, and will not be able to access any wells that are toggled off.
Click on Apply to save your changes.
The Database Access page allows the you to grant users from other organizations access to your organization's server database, using the Innova Web Portal. To grant a user access to your organization's server database, follow these instructions:
In the main menu, scroll to the bottom and click on User Management, then click on Database Access.
Enter a valid username from another organization into the UserName field at the bottom of the page. Note, that if the email address used here is not being used within another Organizations user management, then this process will not work.
Alternatively, you can grant access to all users registered under another organization by entering the organization's name. For example, typing Innova would grant access to all users in the Innova organization. This option removes the requirement to add lots of individual usernames, and ensures any new users are granted access automatically. Contact Innova directly to find out the correct nomenclature for any required organization.
In the Organization field, select the organization that you want to grant the user access to. In most cases, you will only have your own organisation as an option here.
In the RoleId field, choose the role that you wish to grant the user when they are viewing your organization.
Each row in the expanded section displays the following:
Organisation: The organisation that the user has been granted access to.
Role: The role the user has when accessing the organisation.
Access Granted By: The name of the admin in your organisation that gave the user access.
Access Granted Date: The date this user was granted access.
Once a user has been granted access to your organization’s server data, they will able to view wells from both their organization and yours on their Wells List page, when logged into the Web Portal.
A guide to the jar placement module within Innova Engineering.
This document describes the jar placement module within Innova Engineering and details the steps required to correctly utilise its functionality.
This document describes the jar placement module within Innova Engineering and details the steps required to correctly utilise its functionality.
Units: Ensure that all of the units are correctly selected, based on requirements.
It is suggested that data is input in the following order to increase input efficiency. This is however, just a guide and the user can deviate from this sequence should they wish.
Input data in the Drill String table.
Input data in the Components Details table for each component.
Input the Well Geometry
Input the Mud Weight
Input the survey data into the Well Plan or Actual Surveys table.
Input the Flow Rate
Input the Calc Depth in the Torque and Drag section
Input WOB Rotate
Input Block Weight
Input Overpull if applicable
Select Tools > Jar Placement
To utilise the jar placement functionality, the following inputs are required.
Drill string, Well Geometry & Fluids Tab
Drill String: Input the assembly as accurately as possible including the drill pipe to surface (note, for the last component e.g. DP to surface, the user does not have to input the exact length as the program will do this automatically based on the calculation depth. Inputting a nominal value of 10 is fine). Note that once a component type has been selected, it is possible to right click on the line and choose "select from Library", which will open the components library. The user can then select the appropriate component and insert it directly into the drill string grid.
Bit TFA: The bit TFA is required to calculate the pressure drop at the bit, which is used in the pump open force calculation. This is entered in the bit component details section.
Mandrel Area: The mandrel area of the jar. Sometimes referred to as the pump open area. Used when calculating the pump open force. This needs to be input in the jar component details section.
Stroke Length: The Free Stroke length of the jar. The stroke length of the jar controls the amount of time it takes for the hammer to hit the anvil, the longer the stroke the more time the hammer has to accelerate. Typical stroke lengths vary between 7 – 12”. It should be noted that the stroke length reported by the manufacturers is usually the total stroke length and should be halved for the purposes of this calculation. This needs to be input in the jar (and accelerator if included) component details section.
Well Geometry: Input casing, liner, riser and open hole details including depths and ID's. For open hole, the ID is the OD of the bit. Note that the user should only enter the well geometry which is relevant for the section in question and should not enter the entire casing string here. The open hole MD value entered here, is the value used for Hole Depth in the jar placement dialog, which dictates the deepest bit measured depth used in the neutral point results.
Mud Weight: This is required for calculating the buoyancy factor.
Surveys Tab
Survey Selection: Jar placement calculations will be run using plan or survey data entered in the Well Plan table. In the absence of data in the Well Plan table, data from the Actual Surveys table will be used. Data can be input as measured depth, inclination and azimuth in both the Actual Surveys and Well Plan sections, and the program will generate the rest of the numbers using whichever survey calculation method has been selected (Minimum Curvature Default). Jar placement cannot be run against surveys input in the RAW surveys table. Either enter the plan or surveys manually, import them or copy and paste the data directly into the cells.
Engineering Parameters Tab
Flow rate: If manual flow increment is selected, the first flow rate entered will be used in the calculation. If the automatic range is selected, the flow rate entered in line 3 will be used. The flow rate is used in the Pump Open Force calculation.
Torque and Drag Calc Depth: The value input here will dictate the bit measured depth used in the Jarring Results table.
WOB Rotate: The value input here will display in the WOB cell in the Jar Placement dialogs Drilling Data section. This is used in the neutral point calculation.
Block Weight: Block weight entered here will be added to the values in the HKLD Fire column in the Jarring Results section.
Overpull: If no overpull is specified the jarring results will be calculated for an overpull up to 500 klbs (250 Tons). If an overpull is specified the jarring results will be calculated up to the overpull value x 2
Once the user has entered all the required inputs, the jar placement calculations are carried out automatically when the user opens the Jar Placement dialog via Tools > Jar Placement or selecting the icon from the toolbar.
The Jar Placement dialog displays all the information and results relevant to the jar placement module.
Non-editable display of the drill string entered in the Drill String section of the main UI. Jars are highlighted in green and accelerators in orange.
Non-editable display of the jar and accelerator component details entered in the Drill String section of the main UI. Only Stroke and Mandrel Area affect the jar placement results. All other cells are for reference only.
Stroke: This is the free stroke length and is used in the impact and impulse calculations.
Mandrel Area: Is used in the pump open force calculation.
Non-editable display of drilling data used in the jar placement calculations.
Hole Depth: Value taken from the deepest MD entered in the Well Geometry section of the main UI. Dictates the deepest depth that the neutral point calculation is run.
Mud Weight: Value from the Fluid Properties, Mud Weight cell. Used in the buoyancy factor calculation.
Buoyancy Factor: Calculated using the below formula.
BF = 1 – (MW/k)
Where BF is buoyancy factor, MW is mud weight and k is a (mud weight unit dependant) constant. Buoyancy factor is used in the neutral point and jarring results calculations.
Flow Rate: Value from the Engineering Parameters tab. If manual flow increment is selected, the first flow rate entered will be used in the calculation. If the automatic range is selected, the flow rate entered in line 3 will be used. Used in the pump open force calculation.
WOB: Value from Torque and Drag sections WOB Rotate cell. Used in the neutral point calculation.
Hole Size: Value from Well Geometry, Open Hole, ID cell. Used in the Jar Size Check and Jarring Results calculations.
Inclination at Bit: Interpolated inclination from the survey listing at the Hole Depth. Used in the Weight Below Jar BHL (Air)/(Mud) calculation.
Non-editable display of calculated data.
Jar Size Check: A pass or fail check based upon the jar size and the hole size. This is to confirm that the correct OD jar has been chosen for the given hole size. Note that a Fail in this cell has NO effect on the jarring calculations, which will be run regardless. All this cell does is highlights to the user if the size of the jar selected is suitable for the hole size based on a checklist which can be fully edited by the user. This is a warning and no more.
Jar is in: TENSION or COMPRESSION. Based upon the input data, this cell shows whether the jar is currently in tension or compression.
Weight Below Jar Vertical (Air): The weight below the jar in a vertical well in the absence of a drilling fluid. Calculated by the sum of the component weights (input in the Drill String section of the main UI) beneath the jar.
Weight Below Jar Vertical (Mud): The weight below the jar in a vertical well, taking in to account the buoyancy effect of the drilling fluid. Calculated by multiplying the Weight Below Jar Vertical (Air) by the buoyancy factor.
Weight Below Jar BHL (Air): The weight below the jar at the bottom hole location (the bit depth) in the absence of a drilling fluid. Calculated by multiplying the Weight Below Jar Vertical (Air) by the cosine of the Inclination at Bit.
Weight Below Jar BHL (Mud): The weight below the jar at the bottom hole location (the bit depth), taking in to account the buoyancy effect of the drilling fluid. Calculated by multiplying the Weight Below Jar Vertical (Mud) by the cosine of the Inclination at Bit.
Pump Open Force: The force generated by the flow of drilling fluid through the BHA that acts to open the jar. Calculated by the bit pressure loss multiplied by the Mandrel Area.
Neutral Point: The MD of the point in the drill string that transitions from compression to tension based upon the input data. This is directly affected by the WOB.
Jar to Bit: The distance from the top of the jar to the face of the bit.
Accelerator to Bit: The distance from the top of the accelerator to the face of the bit.
The pump open force chart displays the pump open force versus the flow rate. The green vertical line depicts the currently selected flow rate.
For details on adjusting the chart settings see Appendix A – Context Menu.
The neutral point chart is a neutral point road map, which shows the WOB to avoid at every depth along the well path. The centre of the red area represents the neutral point. The red section represents a ±5% safety margin, and the orange area represents a ±10% safety margin. This gives the personnel on the job a WOB range to avoid for any given MD along the entire well path. Note that the 5% and 10% margins are the default values, but these can be changed based on user requirements via the settings menu.
For details on adjusting the chart settings see Appendix A – Context Menu.
The jarring up chart displays the calculated jarring up impulse and impact at the jar, versus hook load.
For details on adjusting the chart settings see Appendix A – Context Menu.
The jarring down chart displays the calculated jarring down impulse and impact at the jar, versus hook load. The area shaded in red indicates the hook load range in which the string is modelled as being helically buckled. The buckling will occur at some point in the drill string above the jar and simply indicates that it may not be possible to transmit the required weight to cock / fire the jar. This range is indicated in the jarring results table by lines highlighted in Orange.
For details on adjusting the chart settings see Appendix A – Context Menu.
The jarring results table showing the results of the jarring calculations. These results are the source of the data that is plotted in the Jarring Up and Jarring Down charts. Note, that in the jarring down section of the results table, any lines which are highlighted in orange, indicate the hook load range in which the string is modelled as being helically buckled. The buckling will occur at some point in the drill string above the jar and simply indicates that it may not be possible to transmit the required weight to cock / fire the jar. This range is represented in the jarring down chart by the red shaded area.
HKLD @ Fire: The surface hook load used to fire the jar This takes in to account the string weight and pick up forces which need to be overcome before the jar starts to have overpull applied. The calculation assumes CHFF 0.15 and OHFF 0.25.
OP @ Surf: The overpull registered at surface for a given hook load.
OP @ Jar: The overpull at the jar for a given hook load. This takes in to account the effects of drag.
Wt @ Surf: The weight registered at surface for a given hook load.
Wt @ Jar: The weight at the jar for a given hook load. This takes in to account the effects of drag.
Impact @ Jar: The impact at the jar resulting from the jar firing when the associated hook load is registered at surface. Calculated utilising the length of the drill collars above the jar, the stroke length of the jar, the overpull/weight applied and the drag in the hole.
Impulse @ Jar: The impulse at the jar resulting from the jar firing when the associated hook load is registered at surface. Calculated as the integral of impact force with respect to time.
Impact @ SP: The impact at the stuck point (the bit) resulting from the jar firing when the associated hook load is registered at surface. Calculated utilising the length of the drill collars above the jar, the stroke length of the jar, the overpull/weight applied, the drag in the hole and the distance between the jar and the stuck point.
Impulse @ SP: The impulse at the stuck point (the bit) resulting from the jar firing when the associated hook load is registered at surface. Calculated as the integral of impact force with respect to time.
Within the Jar Placement dialog, the user can output the following via the File Menu:
Jar placement report
The jarring results table data
Any of the charts present.
The user selects File > Print Report. This generates a report which can be saved to pdf format.
The report includes all the data and charts displayed within the Jar Placement dialog.
Exports the data in the Jarring Results table in a .txt file format.
Additionally, the user can export any of the charts individually using the right click context menu and selecting Export Dialog. For more information on exporting charts see Appendix A – Context Menu.
The settings Menu gives the user access to the Jar Placement Settings dialog.
The Jar Placement Settings dialog is where the user can adjust the jar check size and neutral point chart safety factors.
Jar Check Size: The user can enter the jar sizes and the relevant minimum and maximum hole sizes the jars are suitable to be run in. This information will be displayed on the main Jar Placement dialog in the jar checklist section. These sizes will also be used by the program for the Jar Size Check, where the user will be informed if the jar they have entered into the drill string is suitable, based on the hole size selected.
Neutral Point Safety Factors: The safety factors entered here are represented on the neutral point chart on the main Jar Placement dialog.
Safety factor 1 is represented by the red highlighted area
Safety factor 2 is the orange area displayed on either side of the neutral point line.
The default values are 5% and 10% respectively but can be changed here, as per the user’s requirements.
Impulse/Impact Charts X Axis Hookload: When checked, the X axis of the Jarring Up and Down charts will represent the Hookload at surface. If unchecked, the X axis will represent the relevant Overpull (Jarring Up) and Slack Off (Jarring Down) values.
The context menu is available in every plot by right clicking anywhere on the plot. This allows the user to change certain aspects of the plot based on their requirements. It should be noted that almost all of the functions available in this menu, are also available in the Chart Properties.
Viewing Style – Allows the user to select the desired Chart style.
Border Style – Allows the user to select the desired Border style of the chart.
Font Size – Allows the user to select the desired font size, which will affect all fonts on the chart including title and axis labels. Large, Medium or Small.
Plotting Method – Allows the user to select the way the line is plotted: Point, Line, Bar, Points + Line, Spline Area.
Data Shadows – Allows the user to select between off, shadow and 3D.
Grid Options – Allows the user to change the grid options in the chart.
Mark Data Points – Adds the data points relating to the data labels
Undo Zoom – Resets the zoom on the chart. Pressing the Z button has the same effect.
Maximise – Maximises the chart to fill the screen. Escape button exits this view.
Customization Dialog – Opens a dialog with more user definable chart options.
Export Dialogue – Allows the user to Export the chart using multiple image formats: EMF, WMF, BMP, JPG and PNG. The user has 3 options:
Clipboard: exports directly to clipboard, allowing images to be quickly added to word, excel & PowerPoint documents
File: Creates an image file of the chart which can be used on its own or imported into any suitable document
Printer: Sends the chart to the printer
The user can also choose the relevant Width, Pixels and DPI to use for the export. For Clipboard and File options, Pixels is the only available selection. When Printer is selected, the Millimeters, Inches and Points options become available to select.
This document teaches the user to use the ZerdaLab AI-based automatic bit grading system, integrated into the Innova Web Portal and phone App.
Manually grading drill bits is a subjective process, as it relies on individual expertise and experience of the assessors, as well as the assessment conditions, all of which can vary considerably.
Innova has teamed up with ZerdaLab to provide an AI-based grading system within our Web Portal and App, which implements an objective, consistent and unbiased methodology wherever it is employed across the company.
This document will guide the user through the specifics of the setup and operation of this feature.
This integration is only available via the Innova Web Portal and Mobile App. The user therefore requires the following to be able to access this feature:
Server Database Access: The portal and app operate with a server database, therefore access to a server database is required. This feature does not work with a local database.
Login Credentials: The user must have login credentials that give them access to the portal and app. In addition this access must include user permissions that allow them to add as a minimum. Read only permissions will not allow the user to access this feature.
Stable Internet Connection: This feature requires the user to upload images to the server database using either their phone, tablet or computer, which will require an internet connection
The grading is accessed directly via the Drill String Page, and the user requires the following setup:
The database tree needs to be populated down to Actual Well Level
There needs to be at least one BHA available
The BHA needs to have a minimum of a Bit entered
Please note that this feature will only work for PDC bits. Tri cone bits must be dull graded manually in the conventional way.
For the automated bit grading to operate optimally, follow these rules:
Upload one image of each blade and one image of the face of the bit. Do not upload multiple images of the same blade.
The image of each blade must show all cutters on the blade and clearly show the face of each cutter.
All images should be well lit and clear, without any blurring.
The image below shows examples of good pictures to upload. Note, it is useful, but not required, to label the blades as this helps to ensure each one is photographed, with no duplicates.
The following section details the required steps to grade a bit using the automated feature in the Innova Web Portal.
From the Wells List page, search for the desired well and then select it from the list
Access the Drill String page, via the left hand menu. If there are no BHA’s here, then one must be added before you can proceed to the next step. The BHA must also include a bit.
Select the 4 squares beside the appropriate BHA and select the BHA images option
Images can now be uploaded. This can be done individually by selecting the picture icon to the right of each image, or by choosing Select Multiple from the bottom of the dialog.
Images can also be deleted individually or all at the same time via this dialog.
Once an image has been uploaded, a new option will become available at the top right of the picture where the user can identify the picture as a drill bit.
This is important as this dialog is for any relevant BHA pictures and is not exclusively for drill bits.
Once a minimum of 4 pictures have been identified as drill bits, click on Grade Bit at the bottom of the dialog to run the ZerdaLab bit grading feature. Depending on the number of blades, you may require more than 4 oictures to accurately grade the bit.
Wait for the Portal to contact the ZerdaLab server. After a minute or so, the Bit Grade dialog should appear with the results.
The user can then edit the results if they wish.
The Bearing grade will default to Not Applicable.
The output cannot provide the Gauge or Reason POOH results. The user must enter these manually.
Once the user is happy with the bit grade, they should click Accept to save the results.
The results will be saved to the Grade Out property for the bit belonging to the selected BHA.
The following section details the required steps to grade a bit using the automated feature in the Innova Phone App.
Login to the App using valid login credentials.
Select the desired well from the Wells page by tapping on its name in the list.
Access the Drill Strings page by tapping on the BHA option at the bottom of the screen.
Images can now be uploaded.
This is important as this dialog is for any relevant BHA pictures and is not exclusively for drill bits.
Wait for the App to contact the ZerdaLab server. After a minute or so, the Bit Grade dialog should appear with the results.
The user can then edit the results if they wish.
The Bearing grade will default to Not Applicable.
The Output cannot provide the Gauge or Reason POOH results. The user must enter these manually.
Once the user is happy with the bit grade, they should tap Submit to save the results.
The results will be saved to the Grade Out property for the bit belonging to the selected BHA. To view the bit grading, return to the Drill Strings page and tap on the desired BHA to view its components.
Tap on the Drill Bit component in the list.
Scroll down to the Grade Out field. The bit grading can be edited by tapping on it.
A guide to setting up and running the Electronic Data Reader (EDR) in the Innova Web Portal.
The Data Acquisition and EDR features within the Innova Web Portal allows the user to capture, store, view and manage EDR (Electronic Drilling Recorder) data in real time, or historically.
The purpose of this document is to introduce the user to the Data Acquisition and EDR features in the Web Portal, and detail some of the steps required to correctly setup and use these features.
To use the Data Acquistion and EDR features within the Web Portal, the organization requires the Data Acq and Real time features to be enabled respectively. Additionally, in order to interact with any of the data acquisition features the user requires Admin permissions. It should be noted that to view data in the EDR page, no special users permissions are required.
The user will need to ensure they have a database structure in place that includes at least one actual well, as this is the level in the database tree that the EDR data is associated. Note, that this will not work in a plan, only in an actual well.
The following section will take the user through the data acquisition work flow, step by step.
The data store is an SQL server database that the EDR data is written to and stored in. The majority of companies will not require to add a data store, as they will use Innova’s own data store by default.
However, if a company does want to store data in their own data store, they can. To allow the Data Acquisition system access to store and retrieve EDR data to a company’s own data store, the user needs to input the following SQL Server database credentials for the relevant data store:
Name (generic name given by the user to the store)
Server (IP/URL)
Port
Username
Password
Database Name
To add these details to the Web Portal, the user should select the burger menu at the top left of the screen, then Data Acquisition > Data stores. The user can add the details at the bottom of the page next to the green plus icon. Once added the details will appear in the main list at the top of the page.
The user can test that the connection details are valid by selecting the four square icon and Test connection. If successful, the user will get the below message. If unsuccessful, the details should be checked and adjusted accordingly.
The data source can be one of the below options:
Well Seeker Pro
WITS/WITSML connection to Well Seeker and Send Data to Server
Well Seeker Client
WITS connection to Well Seeker Client and Send Data to Server
WITSML
Can be pulled directly into the server
Can be pulled into a local Well Seeker Database and pushed to the server
If the data source is to be either Well Seeker or the Well Seeker Client see the above links for documents covering the setup. If the data source is WITSML, then the user requires to input the WITSML server credentials, followed by the configuration. To add the WITSML server credentials to the Web Portal, the user should select the burger menu at the top left of the screen, then Data Acquisition > WITSML Servers. The user can add the below details at the bottom of the page next to the green plus icon. Once added the details will appear in the main list at the top of the page.
Name (generic name given by the user to the WITSML server)
Server (IP/URL)
Username
Password
Version (Select from the dropdown list)
The user can test that the connection details are valid by selecting the four square icon and Test connection.
Data Configurations is where a user selects a well to associate EDR data with and adjusts any required configuration settings for a real time EDR data connection if required.
To add a well to the list, the user should select the burger menu at the top left of the screen, then Data Acquisition > Data Configurations.
The user can add a well by selecting from the ActualWell dialog at the bottom of the page next to the green plus icon. Once selected the below dialog will open, allowing the user to search for and select any actual well in the database. Only actual wells that are not already present in the Data Configuration page listing will be visible. Once the check box for the desired well has been ticked, select the green plus icon and the well will appear in the main list as a new row.
When EDR data is received live, or uploaded at a later date, it is possible to assign a relevant Rig State to each line of the data. The Rig State defines the operation being carried out at the time e.g. rotating, sliding, circulating etc. In order for rig state data to be inferred based upon the EDR data, the user must first select the rig state thresholds for the well. Select the four square icon for the relevant well and select Rig state thresholds.
Note that if the Dynamic Thresholds option is checked in the Data Configurations page, the portal will automatically adjust the hookload and RPM thresholds to better fit the captured data.
If EDR data is to be captured in real time then the below options need to be configured correctly:
Update Rate(s) (user defined with a minimum value of 1)
Data Source (Select from dropdown menu from Well Seeker, Well Seeker Client and WITSML)
Data Store (If a new data store was added then select from the dropdown, otherwise leave as Default which will save to Innova’s database)
WITSML Server (Select from the dropdown if a WITSML server was added): Note, this is only available to select if WITSML has been selected as the Data Source
If WITSML has been selected as the Data Source, the WITSML settings need to be configured. Select the four square icon to the left of the relevant well in the table and select WITSML Config.
In the expanded WITSML Config options, select the correct well, wellbore and track for the well in the tree on the left, and select the desired log type. In the Mnemonics section in the top right, assign the correct WITSML Mnemonic to the EDR parameters you wish to record. All other fields in the WITSML Config options are there for user information purposes and cannot be edited.
Select the four square icon for the relevant well and select Start reading. The Status will change to RUNNING. The data acquisition system will now save EDR data to the data store, and the rig states will be defined and recorded as the data is received.
Once there is no longer any requirement to capture WITS data, the user should select Stop Reading.
Note: The data acquisition system will automatically stop logging for any wells that have data that is static for a period of 48 hours. If this occurs, The reader can be started again at any time if required by the user.
If EDR data is to be uploaded via a file e.g. a Pason/Totco export csv file, either at points during the well, or after the well is completed, then the user does not need to change any of the below configuration settings.
Select the four square icon for the relevant well and select Upload file.
The Import Data dialog will open. Select SELECT FILES and navigate to the desired file to import.
Once the file has loaded the column and row data will display as below. At the top left of the dialog, select the check box if the data being imported is referenced to UTC (Coordinated Universal Time) and select the Import Mode from the options of overwrite and fill.
The first row of the .csv file is assumed to be a header row and will display in the top of the table. The row below this (the second row) will be blank, allowing the user to Map the data via dropdown options. This is a critical step, as it identifies the data in each of the columns and ensures they are correctly assigned during the import process. Once completed, select IMPORT.
At this point the Status cell will read “import in progress”. Depending on the volume of data being imported, and the internet connection, this may take a while to complete. Once successful, the user will receive the pop up message, File Uploaded. Close the dialog by selecting CLOSE. The status of the file upload can be monitored on the File History page (Burger menu > Data Acquisition > File History).
The user who initiated the file upload will also receive an email notification when the data upload has completed.
Once a well is completed and all the required data has been stored in the data acquisition system the user has options regarding what to do with that data.
The user can export a copy of the EDR data for the well to a .csv file by selecting Export raw data. The user will receive a message notifying them that the export has been queued. The user will be able to monitor the export process on the File History page. Note that for large amounts of data, this can take some time. Once the export has completed, they will receive an email containing a link allowing them to download the .csv file, similar to the screenshot below. The file will also be available for download at any time via the File History page.
The user can reprocess the rig state data based upon the current rig states threshold values by selecting Re-Process Data. By selecting this option, each line of data will be reevaluated based on the current rig states threshold and an appropriate rig state will be assigned. In most circumstances, the user would use this after uploading historic EDR data via the Upload File function. However, it can also be used after capturing live EDR data, to regenerate the rig state values based on the currently selected Rig State Threshold values.
Clear Data is an Innova Admin feature only.
In order to keep the well list in the Data Configuration page manageable, the user can Delete & Archive the data. This removes the well from the list in the data configuration page and makes it no longer viewable in the EDR page. The data is downloaded and stored as a .csv file on Innova’s cloud storage system. The status of the archiving process can be monitored on the File History page. Note that for large amounts of data, this this can take some time. Once archiving is complete, the user will receive an email where they can download the data, as if they had exported it. The data can also be viewed, downloaded and restored at any time via the File History page.
The File History page keeps a record of all EDR data files that have been uploaded, re-processed, exported, archived and restored. The File History page can be accessed by selecting the burger menu at the top left of the screen, then Data Acquisition > File History.
In the File History table, the Wellname field shows the well that the data belongs to, and the Status field shows the task that was performed to generate the record. Clicking on the > icon to the left of each record will display a more detailed breakdown of the task, with time stamps.
Users can search for specific records using the search bat at the top of the page.
Clicking on the four square icon to the left of each record displays some additional options. Note, these will only be available if the row status is either Archive complete or Export ready:
The Download File option allows the user to download the EDR data as a .csv file. This csv file, if required, can be used with the Upload File function in the Data Configuration page.
The Restore Archive option will restore the well and its data to the Data Configuration page and make the data visible in the EDR page again. This option allows the user to retrieve data that was archived using the Delete & Archive function in the Data Configuration page.
Archive data can be deleted using the Delete Archive option. Note that this is permanent, and any data deleted from the File History page in this way cannot be retrieved.
The EDR page is where a well’s data, which is stored in the data acquisition system, can be viewed.
To access the EDR page select the burger menu at the top left of the screen, then Well Views > EDR.
The data stored in the data acquisition system for the currently selected well will be displayed. The user can change the referenced well via the well selection option at the top right of the page.
The EDR page display is broken down into sections:
Mini-map
Depth time activity bar
Charts
Side tabs
Additional options
The mini map displays the entire wells data set as time vs hole depth, time versus bit depth and time vs activity (colour coded bands). There is also a overlay that displays which section of the well data is current visible within the y-axis and charts sections. The overlay can be resized by dragging the top and bottom overlay edges to the desired time span and then the overlay can be moved by selecting the overlay centre and dragging to the desired location on the mini-map. This is a fast, effective way of being able to view a desired data range.
The depth time activity bar, displays data relating to the currently selected chart section.
At the top left of the bar next to the chart legends, is tool tip data related to where the user is hovering the mouse cursor on the charts area, including hole depth, rig state inferred activity, date and time. The remainder of the bar displays the y-axis time date increments and the rig states inferred activity coloured areas.
The charts section consists of a user definable number of tracks and each track displays a user definable number and selection of curves. Below is the default layout and configuration.
Tracks are the columns that curves can be displayed upon. Users can select to have as many or as few tracks as desired, but will realistically be limited by display dimensions.
To add a track, right click on a track main area and select Add Track. The new blank track will be inserted to the left of the track in question. Tracks can also be deleted in this manner.
The Add Curve option is also available from the right click context menu. Details of how to edit curve settings once added are included in the next subsection.
In addition to using the mini-map functions, the user can scroll up and down the data using the mouse wheel and zoom in and out using the mouse wheel whilst the Ctrl button is depressed.
Curves are the individual lines that are plotted on the tracks and represent one of a number of predefined mnemonics that are saved in the data acquisition system.
To add or delete a curve right click on a curve legend and select the corresponding option.
To edit an existing curve, double left click on a curve legend and the below dialog will open.
The user can select the curve data type by selecting the CURVE NAME and selecting from a dropdown list. Colour is selected by either inputting the colour code, or selecting the colour tile and manually selecting the desired colour. Minimum and maximum display range can also be selected for a curve here.
An existing curve can also be dragged and dropped from one track to another, by holding down the left mouse button on a curve legend and dragging it to the curve legend area of another track and releasing the left mouse button.
Side tabs allow additional dialogs to be displayed or hidden based on the users requirements. Below details the current side tabs.
Displays a schematic of the current well. Conductor, casing and liner dimensions and measured depth data displayed is from the actual well Casing table. Open hole data is from the survey or slide sheet data, whichever is greater.
Displays directional drilling related data for real time drilling operations overview.
In the bottom right of the EDR page the user can hover over the pencil icon to display additional options.
Reset Curves gives the user the option to manually reset the curve data layout on the page to the default settings.
Export to excel produces an xlsx report that shows all of the raw tabulated data currently displayed within the tracks on the page over the same date/time range.
Covers registration and configuration of an OAuth App on Microsoft Azure Portal
It is possible to register an OAuth app for the Microsoft Graph API from the . This document covers the steps required to register an app on the Azure Active Directory and configure permissions for it.
Input all data as per this document. Naming conventions are critical for this function to work successfully!
2. Click on the icon in the top left of the page to open the side menu.
3. In the side menu, select Azure Active Directory.
4. In the Azure Active Directory window, click on App Registrations and then select New Registration.
5. In the Register an Application screen, enter the following information:
Name: ICPAPI
Supported Account Types: Accounts in this organizational directory only
Under the Redirect URL (optional section) enter the following:
Select a Platform: Web
Sign-On URL: Not required
Then click on the Register button at the bottom of the page.
6. On the newly created Overview page for the app take a copy of the Application (client) ID and the Directory (tenant) ID. Hover over each code and select the Copy to Clipboard option when it appears. Save these IDs in a secure location.
7. Create a new Client Secret: On the left of the page click on Certificates & Secrets. Then click on Client Secrets and New Client Secret.
8. In the window that opens on the right, enter the following:
Name (description): ICPAPI_Handshake
Expires: Choose an expiry date that suits you.
Click Add- A new Client Secret will be generated for you. This will be the only time you will see the Client Secret Value, so you better copy it to a secured location otherwise you won't be able to retrieve it again! Click on the Copy to Clipboard icon to the right of the Client Secret Value to copy it.
Note: These steps require the user to have admin permissions in their organisation’s Azure Portal.
If the user has navigated away from the App Overview page, they can return to it by clicking on the icon in the top left of the page to open the side menu. Then select Azure Active Directory. In the Azure Active Directory select App registrations from the menu on the left and then select ICPAPI from the list.
1. From the App Overview page, select API Permissions and then Add a Permission.
2. In the window that opens on the right, click on Microsoft Graph.
3. Click on Delegated Permissions. To select a permission, search for it in the search bar and then click on the check box to the left of its name. Select these two permissions:
User.Read.All
Application.Read.All
Click on the Add Permissions button to add the selected permissions.
4. In the API Permissions window, click on Grant admin consent for Innova Drilling & Intervention.
5. In the menu on the left, click on Expose an API and then Add a Scope
6. In the window that opens on the right, click on Save and Continue.
7. On the next page enter the following information and then click on Add Scope:
Scope name: allow_user
Who can consent: Admins and users
The display name and description entries are optional. Enter a name/description that you want admins and users to see when the consent to the scope later.
State: Enabled.
8. In the menu on the left click on API Permissions and then Add a permission.
9. In the window that opens on the right, select My APIs and then click on your App/API.
10. Select the scope you just created by ticking the check box next to it, and then click on Add Permissions.
If your organization wishes to have MFA logins turned on for the Innova Web Portal, Mobile App and Well Seeker Pro server database logins, then they must first follow the below steps within Azure Active Directory. In addition to these steps, the system admin will require to turn on MFA for the organization, or for individual users within Azure Active Directory. For that process the user should refer to Azure Active Directory documentation.
1. Once logged on to Azure Active Directory select Home > App registration > ICPAPI > Authentication.
2. Use the call back URI for the single page web app. In the Single-page application section add the below URIs by selecting Add URI.
https://www.icpwebportal.com
https://icpwebportal.com
https://eu.icpwebportal.com
3. In the Mobile and desktop applications section ensure that the URI below is available, if not add it. Check the selection box to select it.
https://login.microsoftonline.com/common/oauth2/nativeclient
4. In the Mobile and desktop applications section add the below URI.
com.icds-innova-dan://auth
5. Scroll down to the Implicit grant and hybrid flows section. This is to turn on access tokens for authorization endpoint. Select the check boxes for the Access tokens and ID tokens options.
6. Select the Expose an API section.
7. Select Add a scope and input the below details and then select Add scope.
Scope Name: icpapi_read
Who can consent: Admins and users
Admin consent display name: Read icp api
User consent display name: icpapi read
State: Enabled
A guide to setting up multi-factor authentication for your organization's users in the Web Portal interface.
Multi-factor authentication (MFA) is a commonly used method of online security. It requires a user to firstly input their username and password and secondly input a code generated by a third party app on a device the user has previously designated. This means in order to access a user’s account they must have a username, password and their authentication device available, which increases the security of the account.
MFA can now be enabled for use when logging onto the Innova Web Portal and the Innova Phone App. Additionally, if your Well Seeker Pro server database is hosted within Innova’s infrastructure, MFA can be enabled for use when logging onto a Well Seeker Pro server database.
This document will guide the user through the various use cases, which differ slightly based upon the organization’s user management system (Innova, Okta or Azure AD).
MFA is turned off by default. It is up to an organization’s admins to turn on MFA for their existing users, if they desire to use this security feature. This is done via the User Management page in the Innova Portal.
To access the User Management page, log in to the Innova Web Portal, using credentials that have the Admin permission enabled. Open the main menu and select User Management and then Users.
MFA settings are managed on a user by user basis. Before changing any settings, check the Auth Type column.
MFA Enabled: Click the button in the MFA Enabled column to toggle MFA on for that user. The user can then follow the steps in Section 3 below to set up MFA on their secondary device. The button will display green when MFA is enabled for the user.
API User: Toggling the API User function on prevents a user from using MFA, and ensures that they can log in using their username and password only. It also prevents the MFA Enabled option from being toggled on. If MFA was previously enabled for the user, it will automatically be deactivated. The button will display green when API user is enabled.
If MFA has not been enabled then the user will login as usual.
If MFA has been enabled, one of two scenarios will occur:
1. This is the first time a user is logging in after MFA has been enabled, or the MFA authenticator has been reset:
a. The user must register an MFA device. This must be done via the login page for the Innova Web Portal. It cannot be done in the App or Well Seeker.
b. The user inputs their username and password
c. The below screen will appear (for Okta and Azure AD organization users, a similar app specific version will appear)
d. Open an authenticator application on a chosen device, and scan the QR code (see the relevant authenticator app’s documentation for details on how to do this). A row named Innova Drilling & Intervention will be added in to the authenticator app in question, which will generate a six digit code at a pre-determined time interval. Input this six digit code into the six cells displayed below and select SUBMIT MFA
e. If correct the user will be logged in
If a user attempts to login to the Innova Phone App or Well Seeker Pro before registering an MFA device, they will receive a warning message.
2. An MFA device has already been registered:
a. The user inputs their username and password
b. The below screen will appear (for Okta and Azure AD organization users, a similar app specific version will appear)
c. Open the authenticator application on the registered device. Input the six digit code from the row Innova Drilling & Intervention into the six cells displayed below and select SUBMIT MFA.
d. If correct the user will be logged in
The above process will also occur in a comparable order when logging into the Innova Phone App. Where an organizations Well Seeker Pro server database is hosted within Innova’s infrastructure, this will also occur when logging onto the server database in Well Seeker Pro.
Guides the user through the steps necessary to create an SQL server database and ICDS (Innova Central Database Server) web server via the Microsoft Azure cloud-based platform.
The purpose of this document is to guide the user through the steps necessary to create an SQL server database and ICDS (Innova Central Database Server) web server via the Microsoft Azure cloud-based platform. The system diagram below details how the SQL server database and ICDS Web Server fit in to the structure of data flow within Well Seeker Pro.
This is a guide only and where necessary a company may deviate from the specific settings of the Azure account, SQL database and virtual machine to align with their financial and IT requirements.
Before you start, to save time, there are some programs which should be downloaded and installed, as access to these will be required at various points throughout the document.
You will also require credit card details while setting up the Azure account, so have these to hand.
These programs and the relevant links are detailed below.
Download the 32-bit MSI.
During installation, select the Commander interface style.
Installation of SQL Management Studio can take a while, which is normal and expected.
Throughout the setup process, the user will be required to enter numerous different login details and passwords. All of these will be unique to the user. The below table lists the various details the user will be required to supply, along with a blank cell, where they can keep track of these details during the process. It is recommended that this table is completed as the user follows the steps keeping all details in one place for easy reference during and after the setup has been completed.
1. If you already have a Microsoft Azure account, ignore this section and go directly to section 5
3. Click “Try Azure for free”
4. Click “Start for free”
5. A suitable email address should be used, and the password should be very secure
a. Note, it is necessary to add payment details to allow Microsoft to verify your identity and if the “Azure Free Tier Limits” are exceeded your card will be charged.
b. You then need to confirm your identity via phone so are asked to enter your phone number for text or voice call verification
c. Once the user has successfully signed up they will be sent a welcome email by Azure, within which there is a link “Go to the portal”. Select this link and it will open the portal, where you can access the Azure account settings and functionality.
6. As this is the first time logging in, the user must enter their email and password. The Email address and Password required here are the ones entered while creating the Azure account
This guide does not cover user setup and login credentials within the Azure account. If required this should be looked in to by the users IT department based upon company IT security guidelines.
It is now time to create your database on Azure. The following section will guide you through database creation steps and the relevant server firewall rules which need to be added to allow the ICDS to communicate with the database.
7. Click on Home page and select SQL databases
8. Select Create SQL database
9. Select subscription as Free Trial
10. Under resource group, select Create new, and name the group appropriately
11. Enter an appropriate database name.
12. Under Server select Create new. Input a server name, admin login name and password (note these two as they will be used later). Select a location for the server that is geographically as close to the office location as possible, as this will directly affect lag time when communication with the server.
13. Select No for the elastic pool option.
14. Under Compute + Storage select Configure database. Select 10 DTUs and 250GB database max size. Select Apply. (This is a user choice and will directly affect the monthly cost of the Azure services)
15. Select Next : Networking >.Select Public endpoint. Select No regarding Azure services access and Yes to add current client IP address (this allows the current computer that you are using access through the firewall). Select Next : Additional settings >
16. For Use existing data select None. For Collation select SQL_Latin1_General_CP1_CI_AS. For Enable advanced data security select Not now. Select Next : Tags >
17. Add tag names for reference if desired
18. Select Review + create.
19. Select Create. The SQL Database will now be created and you will be taken back to the Azure Portal Home Page.
20. On the home page select your newly created SQL database, by clicking on its name
21. Once on the SQL database page select Show database connection strings and then select the JDBC tab.
User Name
DB Name
Endpoint
Take note of the endpoint, database name (what you chose to call it during setup) and user name (that was used when creating the Azure account). The port number will be 1433 by default.
Now that the database has been created in Azure, you need to connect to it remotely, to finalise the setup. This involves using Well Seeker Pro and SSMS.
22. Open Well Seeker
23. Go to File - SQL server databases - connect to remote database
24. Enter the relevant information to connect:
a. Database IP/URL: Enter the database Endpoint here
b. Database Name: Database name as created in the previous section
c. Port: 1433
d. DB Username: Server admin login
e. DB Password: Server password
f. WS Username: Master Database Username (first time use is not pre-defined)
g. WS Password: Master Database Username (first time use is not pre-defined)
25. Click connect
h. It’s likely it will say the Db schema is out of date. Select yes to update
i. It will say there are no admins and ask if you want to make this user an admin. Select yes
26. On first connecting, Well Seeker will create all the relevant tables in the SQL database
27. You can now close Well Seeker
28. Open SQL Server Management studio
j. Server Type: Database Engine
k. Server Name: This is the Endpoint followed by a comma, followed by the Port number.
l. The Login and Password for the database are the server admin login and password
29. In the Object Explorer Tree, navigate to the tables folder under your database
30. Scroll down till you get to the DB_SETTINGS table
31. Right click on the table and select Edit Top 200 Rows
32. Insert a single record in to the table: ./icdsFileDir/
This sets the field IMAGE_PATH for the remote Db, which is where any logos and attached files will be stored.
A virtual machine instance is a virtual server in Azure’s Compute Cloud for running applications on the Azure infrastructure. Azure is a comprehensive, evolving cloud computing platform; virtual machine is a service that allows business subscribers to run application programs in the computing environment. This is where the ICDS will be installed.
33. Click on the home page, select Virtual machines
34. Select Add and Virtual Machine
35. In the Basics section.
a. Select your subscription and the same resource group used for the SQL database.
b. Name the virtual machine accordingly.
c. Select a location for the virtual machine that is geographically as close to the office location as possible, as this will directly affect lag time when communication with the virtual machine.
d. Select the desired availability options.
e. Select the Ubuntu Server 18.04 LTS – Gen1 image.
f. Select No for Azure Spot instance
g. Select required size. Standard B1s is recommended. This can be changed based upon requirement
h. Authentication type as SSH public key
i. Set a suitable user name for the virtual machine. Take note of this name as you will require it later
j. SSH public key source, select Generate new key pair
k. Set a suitable key pair name
l. Public inbound ports, select Allow selected ports
m. Select inbound ports, select SSH (22)
n. Select Next : Disks >
36. In the Disks section
a. OS disk type, select Standard SSD
b. Encryption type, select Default
c. Select Next : Networking >.
37. In the Networking section
a. Virtual network, select new default option
b. Subnet, select new default option
c. Public IP, select new default option
d. NIC network security group, select Advanced
e. Configure network security group, select new Create new
i. Add temporary rules inbound and outbound that allow all IP addresses on all Ports to pass through the fire wall. This is only for the setup phase and can be adjusted when the setup and testing is complete
ii. Take note of the network security group name, as you will require this later
f. Accelerated networking, select Off
g. Load balancing, select No
h. Select Next : Management >
38. In the Management section
a. Enable basic plan for free, select Yes
b. Boot diagnostics, select Enabled with managed storage account
c. OS guest diagnostics, select Off
d. System assigned managed identity, select Off
e. Login with AAD credentials, select Off
f. Enable auto-shutdown, select Off
g. Enable backup, select On
h. Recovery Services vault, select new default option
i. Backup policy, select new default option
j. Select Next : Advanced >
39. In the Advanced section
a. Leave all as default and select Next : Tags >
40. The user can add tags if desired
a. Select Next : Review + create >
41. Select Create
42. The below window will pop up. Select Download private key and create resource
43. This will create a .pem file. Store this .pem file in a safe location, as it is critical for a later stage.
44. Wait while the virtual machine is deployed
45. Once it is deployed, go to the Home page, select All resources and select the virtual machine. Take note of the public IP address, as you will require this later.
Now that the virtual machine and a virtual network has been created, the user must update the SQL server security rules, to allow communication between:
The ICDS (located on the virtual machine) and the SQL database
Well Seeker and the SQL database
SQL Server Management Studio and the SQL database
The admins PC and the virtual machine when using WinSCP and PuTTY
46. In the Portal, select Home then All Resources. Select the resource with Type SQL server
47. Select Show firewall settings
48. At the bottom of the page select Add existing virtual network
49. Give the rule a suitable name and select the virtual network (-vnet) from the dropdown list, that was created during the setup of the virtual machine (there should only be one)
The SQL server now has security rules that only allow the SQL database to communicate with any other device on your virtual network i.e., the virtual machine and any IP addresses or ranges that we have specified during the SQL database setup, on port 1433.
50. Open puTTYgen.
51. Select load and select the PEM file (you will have to change the file type filter to all files (*.*)
52. Click OK to the notice.
53. Click save private key, it is ok not to use a passphrase. Again, keep this file in a safe place as it is very important.
54. Close puTTYgen.
55. Open win SCP.
56. Select protocol as SFTP.
57. Enter the virtual machines public IP address in the hostname.
58. Username is the virtual machine username created during the virtual machine setup
59. Password is blank
60. Port is 22
61. Click on advanced -> SSH -> Authentication and select the browse option to the right of the private key input cell and select the private key that was created with puTTY gen. Select OK.
62. Click login and click yes to the security notice.
63. You will now have the below, where you have created a drag and drop file explorer interface to the virtual machine. If you do not see the virtual machine username folder on the right, its likely because you are already in it. Just select the only folder showing and it should then display the virtual machine username folder.
64. Download the ICDS files via the link provided by Innova.
65. Remove the .linux extension from the icdsServer.linux file.
66. Drag this Linux executable icdsServer file to the virtual machine username folder below right.
67. You will get the below left popup. Select OK and you get the below right.
68. Open the attached config .JSON in a text editor e.g. Notepad
a) CompanyID: Type Company Name (this will be supplied by Innova and must be written in EXACTLY the same way as its supplied). Make sure Company Name is inside double quotes
b) Port: Usually enter the port field as 42000 (no quotes) – this is the port which will be entered into the Well Seeker RT Data exchange for communication with the ICDS
c) devmode: Leave as false (no quotes)
d) sqluser: Set to the SQL Server master username used to access the database. Make sure this is inside double quotes
e) sqlpass: Set to the SQL Server master password used to access the database. Make sure this is inside double quotes
f) sqlsvr: Set to the SQL database Endpoint. Make sure this is inside double quotes.
g) sqldbname: Set to the name of the database you wish the ICDS to connect to. This is the database name that you see when logged in to SQL server Management Studio. Make sure this is inside double quotes
h) sqlport: Set to the port used to connect to the SQL server database (no quotes), usually this is 41433
i) externalPath: Specifies where external files are stored. Input useDatabase (stores files on the virtual machine)
j) sqldbnamewits: If a user is pushing and storing WITs data to a database separate to the Well Seeker database, insert the name of the database here. Make sure this is inside double quotes. If this function is not used then leave a the doubles quotes empty
k) transferWits: If pushing WITs data to a second database then enter true, if not enter false
l) allowActivePush: If false is entered then a computer can push data back to a server database regardless of the well status. If true is entered then a computer can push data back to a server database only when the well status is Upcoming, Active or Standby. The well status is selected in the Daily Reports dialog
m) awsAccessKeyID: This refers to an AWS feature. Leave blank
n) awsSecretKey: : This refers to an AWS feature. Leave blank
o) awsRegion: : This refers to an AWS feature. Leave blank
p) s3Bucket: This refers to an AWS feature. Leave blank
q) Leave all other fields as they are
69. Once completed, drag the config.JSON file to the same directory as the icdsServer file
70. In the same sub directory as the icdsServer executable is located, create a directory called icdsFileDir.
a. To do this, right click under the icdsServer file and select New – Directory.
b. Your folder should now look like the below
c. This folder is where the logos and external files added to the remote database will be saved.
71. Close WinSCP. You will get the below. Selected No, so that the workspace is saved.
72. Open puTTY
73. In the Host Name Cell: Type virtual machine username@virtual machine public IP , both of which we took note of earlier. Add this information to the login details section of this document.
a. Select the port as 22 and name the session in the saved sessions box.
74. Then click on Connection - SSH – Auth.
75. Click Browse and select the ppk file created earlier.
76. Click open.
77. Click Yes to the security alert message. You then get the below.
a. There are a set of commands which need to be entered into Putty. At the end of each line there is a copy button which copies the code. If you then right click on the bottom line in the putty interface, it pastes the code in for you.
b. Hit enter and then move onto the next code.
c. Your putty interface should look like the below right by the end.
79. Enter the following into the command line to install PM2: npm install pm2 -g
d. You should get the below after entering this.
e. PM2 is just a program which allows you to run a file as a service i.e. if it crashes or the computer restarts it will restart the program automatically.
80. Check pm2 is running by typing pm2 ls
f. You should get below after entering this.
81. Update node. Type the following command: nvm install 4.4.5 check version number from node.js website
a. You should get the below after entering this.
b. Node.js is a java script library for linux which is required to run the program PM2.
82. Type: sudo apt-get update
a. You should get the below after entering this.
b. At this point close and reopen putty. If you do not do this, when you get to the point where you type a pm2 command, putty will tell you it is not recognised. Not sure why this happens, but it is a consistent error. Closing and reopening puTTY allows you to proceed without any issues.
83. You now need to change the file permissions using the following “Change Mode” command: chmod 777 icdsServer
a. This makes the file readable, writable, and executable by everyone.
b. If you do not do this step, then in the next step you will likely get an errored message like the one below.
84. Now setup default instance using config file: pm2 start icdsServer
c. You should get the below.
d. Note that the “icdsServer” is the name of the linux file which was placed in the virtual machine via WinSPC. If you have changed the name for any reason, then you will need to adjust the command by replacing “icdsServer” with whatever the name of the file you added is.
85. Save the current pm2 settings so it starts correctly after a server restart: pm2 save
The following is a list of useful commands which can be used in puTTY and relate to pm2. These may be helpful if there are any issues / errors when starting the pm2 application.
86. Stop any current pm2 icds processes: pm2 stop icdsServer
87. Delete old pm2 config params: pm2 delete icdsServer
88. Kill any pm2 process which is running: pm2 kill
89. View list of pm2 running apps: pm2 ls
90. View logs: pm2 logs
Well permissions have been put in place to give the admin control over what computers can pull what wells via the remote data fetch functionality from the SQL server database, if required. This might be the case when a company employs consultant rig personnel, who they do not want to have access to their historical well data. In order to access and setup well permissions follow the below steps:
91. Log on to the SQL server database via Well Seeker Pro
92. Once connected, select Tools > Well Permissions. This will open the Well Permissions dialog. Note that only Well Seeker users with Admin permissions can access the Well Permissions dialog
93. Well Permissions can be set to two states:
a. Enable Individual Well Permissions disabled. To select this option uncheck the Enable Individual Well Permissions check box. This allows any company computer with Well Seeker installed on and a user who has the virtual machine IP address and port number details to pull any and all well data from the SQL server database via the Remote Data Fetch dialog
b. Enable Individual Well Permissions enabled. To select this option check the Enable Individual Well Permissions check box. When this is selected no computers are able to pull down well data via the Remote Data Fetch dialog, even if the user has a company computer with Well Seeker installed and the user has the virtual machine IP address and port number details. Only computers entered in the table will be able to pull down a specified well or job number, when the active check box is selected.
The Computer Name for a computer can be found by right clicking on This PC and selecting Properties. Depending on the windows version the user has, the computer name will come under one of a number of different titles. These details will need to be updated on a well by well basis in order to allow the rig personnel access to the required wells
With the ICDS Server now running it is important to test if this is working correctly. This can be done as follows:
94. Open the RT data exchange in WS and push an operator to the remote Db.
95. Create a new Db and then do a remote data fetch to pull in the well you have just added to the remote Db.
96. Open the RT data exchange and connect to the well you have added on the remote Db. Add some new data to the local Db and ensure that it pulls into the remote Db correctly.
97. Add a new plan to the remote Db and check to see if you receive the relevant notification in the messages window.
98. Add a couple of logos and external files to the remote database to ensure that these save correctly.
a. NOTE: For the logos and external files to work correctly, the user must have the Push External Files option selected in Well Seeker
Now that everything has been setup and tested, the final step is to adjust the network security rules of the virtual machine to make them more secure. If there is an issue connecting after this stage, you can then be sure that the issue is related to the setup of these rules and not any of the other previous steps.
The below settings are a suggestion, which should be adjusted where required by the user’s IT department.
The virtual machine has inbound and outbound communications from/to:
WS - data fetch and exchange
WinSCP and PuTTY (during setup and troubleshooting)
SQL database
When creating a network security rules, the 2 main pieces of information required are the Port and the IP address. Set the virtual machine Incoming and Outgoing Security rules as displayed in the below sub-section:
99. Select the All Resources page
100. Select the Network security group
101. Under settings select Inbound security rules
102. By default the network security group will have three rules in place, which cannot be deleted or edited. These allow all virtual network comms, all azure load balancer comms and deny all other comms coming in to the virtual network.
103. During setup of the virtual machines network we added in a rule that allowed all inbound comms via any port from source to any destination. This allowed us to test the setup without interference from the security settings. Now that setup has been tested successfully we require to put in place tighter security settings, that only allow through the required comms from the Well Seeker Data Fetch and Data Exchange functions and the SQL database. As the SQL database is on the virtual network, the AllowVnetInBound rule covers these comms.
104. Select Add. Input a rule for port 22, used for WinSCP comms to the virtual machine
Public IP of WinSCP / PuTTY user
105. Select Add. Input a second rule for port 42000, used for Well Seeker Pro’s Remote Data Exchange and Data Fetch utilities
106. Your inbound rules should now resemble the below
Public IP of WinSCP user
107. Select the All Resources page
108. Select the Network security group
109. Under settings select Outbound security rules
110. By default the network security group will have three rules in place, which cannot be deleted or edited. These allow all virtual network comms, all internet comms and deny all other comms coming in to the virtual network.
111. During setup of the virtual machines network we added in a rule that allowed all outbound comms via any port from source to any destination. This allowed us to test the setup without interference from the security settings. Now that setup has been tested successfully we require to put in place tighter security settings, that only allow through the required comms from the Well Seeker Data Fetch and Data Exchange functions and the SQL database. As the SQL database is on the virtual network, the AllowVnetOutBound rule covers these comms.
112. Select Add. Input a rule for port 22, used for WinSCP comms to the virtual machine
Public IP of WinSCP / PuTTY user
113. Select Add. Input a second rule for any port, used for Well Seeker Pro’s Remote Data Exchange and Data Fetch utilities
114. Select Add. Add a third rule that denies outbound internet traffic, which has a larger priority value than the previous two rules
115. Your outbound rules should now resemble the below
Public IP of WinSCP user
There may be times when a user is experiencing issues with logging in to the SQL server database via SSMS or Well Seeker, or where the external files / data push and pull functions are not working. The below sections will guide the user through some problem solving steps that will help isolate and solve the issue in question.
If the user receives an error message and cannot log in to the SQL database via SSMS then follow the below steps:
1. Check the user’s computer has internet connectivity
2. Check the Server type is Database Engine
3. Check the Server name is the SQL database endpoint, immediately followed by a comma, then a space and then the SQL database port number, which is usually 41433. For example:
a. SQL database Endpoint = exampleendpoint
b. SQL database Port = 41433
c. Server name entered = exampleendpoint, 41433
4. Check the authentication type is SQL Server Authentication
5. Check the Login entered is the SQL database Username the user created when setting up the SQL database
6. Check the Password is the SQL database password the user created when setting up the SQL database
7. If the above checks still haven’t fixed the problem the remaining potential cause is the SQL database security settings. Log on to the Azure account, select the SQL database in question and review the security settings.
Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser
If the user receives an error message and cannot log in to the SQL server database via Well Seeker Pro then follow the below steps:
1. Check the user’s computer has internet connectivity
2. Check the Database IP / URL is the SQL database endpoint
3. Check the Database Name is the name of the SQL server database as it appears when viewed in SSMS
4. Check the Port is the port number of the SQL database, usually 41433
5. Check the DB Username is the SQL database Username the user created when setting up the SQL database. If the user has since created an additional user in SSMS, this user name can also be used, as long as they have the clearance to access the database entered in Database Name cell
6. Check the DB Password is the SQL database password the user created when setting up the SQL database. If the user has since created an additional user in SSMS, this user password can also be used, as long as they have the clearance to access the database entered in Database Name cell
7. Check the WS Username is correct. Each WS username has been created in the User Permissions dialog by a user with administrator permissions.
If the administrator cannot log on to the SQL server database via Well Seeker then they can log on to the SQL database via SSMS and look in the dbo.USER_PERMISSIONS table to see if the WS username exists
8. Check the WS Password is correct. If the user has forgotten their password then the admin can delete the users password from the User Permissions dialog. The next time the user logs in they will be asked to enter a new password
9. If the above checks still haven’t fixed the problem the remaining potential cause is the SQL database security settings. Log on to the Azure account, select the SQL database in question and review the security settings.
Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser
The Real Time Data Exchange is design to give a user the ability to push data for a specific well from their Well Seeker database, back to the SQL server database. The Remote Data Fetch is designed to give a user the ability to pull data for specific wells from the SQL server database to their Well Seeker database. In order to achieve this there are many things that have to be set up correctly
For both the Real Time Data Exchange and the Remote Data Fetch:
Correct IP and port number input in Data Exchange / Data Fetch dialog. These are the IP of the virtual machine and the port number specified in the .json file on the virtual machine
Correct credentials entered in the .json file on the virtual machine. See 10.1 – ICDS files, step 68 for details
The ICDS server has to be running without error on the virtual machine. See 11.0 – PuTTY for details
The virtual machine security settings have to be correct within the Azure account. See 14.2 virtual machine for details
The SQL database security settings have to be correct within the Azure account. See 14.1 SQL database for details
For the Real Time Data Exchange only:
Correct well selected in the Data Exchange dialog. This well must already exist on the server data base
If the .json file on the virtual machine has allowActivePush as false then a computer can push data back to a server database regardless of the well status. If true is entered then a computer can push data back to a server database only when the well status is Upcoming, Active or Standby. The well status is selected in the Daily Reports dialog. See 10.1 – ICDS files, step 68 for details
For the Remote Data Fetch only:
If the Well Permissions dialog on the SQL server database has Enable Individual Well Permissions selected, then only wells included in the Well Permissions table will be able to fetch specific wells. In the case that the user does not have permission to download well data, the user will be able to connect to the SQL server database and see the database tree, but there will be no structures below facility level to select, as below.
See 12.0 – Well Permissions for details
External files for the SQL database are stored on the virtual machine and rely upon a similar data transmission method as the real time data exchange and remote data fetch functions. If you are experiencing issues saving or accessing external files and logos, either from the SQL database, or when the data has been pulled down to a local database, follow the below steps:
1. Ensure the real time data exchange and remote data fetch functions are working correctly. See 15.3 – Real Time Data Exchange / Remote Data Fetch for details. If they are then it rules out a number of potential causes for the issue. If both these functions are working, but you are still experiencing issues with the external files functions then proceed to the next step
2. Ensure that during the database creation the step was followed that created the external files image path in the dbo.DB_SETTINGS table. See 6.2 - SQL Server Management studio (SSMS), step 32 for details
3. Ensure that the option Push External Files is selected on all computers trying to use the functionality
A guide to the Engineering page in the Innova Web Portal
The Engineering Dashboard is a feature in the Innova Web Portal that allows the user to run torque & drag, BHA analysis, well control and hydraulics calculations against the wells stored on any relevant server database.
This document will guide the user through setting up an engineering case for their well, running the calculation and viewing the results. The user should follow the below chapters in order.
Before using the Engineering Dashboard, make sure that the correct well has been selected. The currently selected well is displayed in the top left of the portal.
Select a well by clicking on its name in the Wells List page. Or by clicking on the Select Well option in the top right corner. Note that only actual wells can be selected, and that the desired well must have a status assigned before it can be seen or selected in the Wells List or the Select Well option.
The units used for inputs and outputs in the Engineering Dashboard are governed by the user’s currently selected Unit Set. Unit sets can be changed by opening the User Profile Menu in the top right of the page and then selecting Change Units.
Once a well has been selected, the Engineering Dashboard is then available to select from the Well Views section located down the left hand side of the portal. If the Engineering Dashboard is not showing in the list the user should check with their system admin to make sure this feature is enabled in the role they have assigned.
Inputs for the Engineering model are entered in the Input Parameters section on the left and the Input Tables section at the bottom of the page Engineering Dashboard page.
Before entering any inputs, the user should first create or select an Engineering case in the Case Details section. Once a case has been created or selected, all the input options will then be available to populate.
Different Engineering setups for each well are stored in the Innova Portal as cases. This could be cases for different BHA configurations, different hole sections, casing runs etc. Before any inputs are entered, a case needs to be created or selected in the Selected Case field.
Active: Toggling this on marks the currently selected case as the active case. Each time the Engineering Dashboard is opened for a given well, it will default to the active case; however, the user can still select and edit other cases which are not active.
Calculation Depth: This is the depth at which the calculation will be run and the depth at which snap shot calculations will be performed. This depth must be within the range of the principle plan or surveys for the well.
After the case has been set up, the user can begin entering parameters into each of the sections below the Case Details. Note that initially when no cases have been created, none of these input parameters will be displayed. At least one case has to be created before these options appear in the list.
Depending on the results that interest you, not all of the input parameters are necessary to fill in.
ROP: Rate of penetration. This is used to calculate the cuttings loaded (Dirty) ECD’s and other hole cleaning parameters.
RPM: The rotational speed of the drill string at surface. Affects standpipe pressure results, reaming hookloads and reaming torques.
WOB: The weight on bit while rotary drilling.
WOB – Slide: The weight on bit when sliding.
The inputs available in this section depend on the hydraulics model selected in the Hydraulics section (2.2.3 – Hydraulics). If Bingham Plastic is selected, only the Mud Weight, PV, and YP will be available to enter. If any other model is selected, the Mud Rheology fields will also be available.
Description: Enter a descriptive name for the drilling fluid used in the case.
Mud Weight: The density of the drilling mud.
PV: Mud plastic viscosity. Only used if Bingham plastic hydraulics model is selected.
YP: Mud yield point. Only used if Bingham Plastic hydraulics model is selected.
Mud Rheology: The Fann dial readings of the drilling fluid (600, 300, 200, 100, 6, 3) are used for all hydraulics models except Bingham Plastic.
Model: Choose between Bingham Plastic, Power Law, Herschel Bulkley or Robertson Stiff. Bingham plastic uses PV, YP and mud weight, while all other models use Mud Rheology and Mud Weight.
Surface Pressure Loss: The pressure loss through the surface equipment. This value is added to the total standpipe pressure calculated by the model.
Surge & Swab Type: Specifies if the surge and swab calculation to be carried out is Open or Closed Ended.
Surge & Swab Ref: The location in the wellbore where the surge / swab results will be calculated. Select from the drop down box:
Bit – Bit depth.
Shoe – Uses the shoe depth of the deepest casing, taken from the Wellbore table.
Bottom Hole – Uses the deepest survey in the Surveys table.
User Defined – Enables the Reference Depth field where the user can enter a custom reference point.
Continuous Circulation: Used to model coiled tubing. Assumes circulation while tripping, this means that swab effects will be less and surge effects will be more depending on flow rate. The first flow rate in the Flow Rates table is used to determine the annular velocity generated by the circulating fluid.
Continuous Tripping: This option assumes continuous tripping, and as a result will only calculate one acceleration phase (on the first stand length) and one deceleration phase (on the last stand length). This option is best used to model coiled tubing.
Include Gels: Include the additional pressure required to break down the gels. This is normally fairly small.
Include Pipe Acceleration: This option allows the user to include or exclude pipe acceleration. When this is included, the calculation will use an acceleration and deceleration phase for each stand length. When it is not included, the Trip Speeds table will be used for the whole stand with no acceleration or deceleration phase.
Limit Acceleration: This option limits the additional surge pressures due to acceleration to a maximum of 2x the current max surge pressure. This stops very large (artificial) equivalent mud weights being generated when very shallow.
Use bit TFA: This option allows the user to use the bit TFA when running open ended surge and swab calculations. This will only work for assemblies which have a bit and a TFA entered. When this selection is off, the Engineering Dashboard uses the internal diameter of the last component.
Min EMW: Sets the minimum acceptable effective mud weight limit for the Tripping Speeds chart.
Max EMW: Sets the maximum acceptable effective mud weight limit for the Tripping Speeds chart.
Include Stabilizers: When this option is toggled off, the Dashboard will not consider stabilizer blades or casing centralisers when calculating hydraulics.
ECD Adjustment: An optional manual adjustment to all the ECD curves to better match the model with MWD PWD data.
SPP Safety Factor: Enter a percentage value here to increase the stand pipe pressure by the specified amount. Pipe Pressure Loss, Annular Pressure Loss and SPP values are all adjusted to reflect this input.
Interval: Determines the interval between calculated points. For example, a step interval of 10 generates a data point every 10 meters, or feet, measured depth.
Auto Bit Torque: When toggled on, the torque generated by the bit is calculated automatically using the bit OD and the WOB. Toggle off to enter a user defined value.
Block Weight: The weight of the rig travelling block.
Overpull: The overpull applied to the assembly when pulling out of hole.
Reaming Speed: The pipe speed up/down when reaming in and out. Used to calculate reaming hook loads and torques. It is also used to calculate the viscous drag if enabled in the section below.
Casing Wear Factor: Defined as the ratio of friction factor to specific energy (units E-10psi-1), the casing wear factor is used to quantify the effects of pipe/casing material and drilling fluid on casing wear. The table below should be used as a guide for casing wear factor selection.
Viscous Drag: Toggle on to take into consideration the drag caused by pulling the string through the mud. This only affects the PU and SO weights.
Side Force Units: Specifies the unit length of the calculated side force. If you are using side force to predict casing wear, this should be set to the length of a tool joint (i.e. 30ft or 10m).
In some situations, it may be necessary to add tortuosity to better simulate real life conditions.
Apply Tortuosity: Toggle this on to add some extra tortuosity to the wellbore. Makes other tortuosity options in the section available.
Depth Range: If this is toggled off, tortuosity will be added to all surveys in the table. If toggled on, the user can define the depth range where tortuosity is applied by entering a Start Depth and an End Depth.
Method: Choose whether the tortuosity is applied in the form of a sinusoidal wave or randomly.
Period: The length of one cycle of tortuosity. Cycles of tortuosity are repeated down the length of the depth range. Only available when Sinusoidal is selected as the method.
This section applies to the calculation for the Kick Tolerance results chart.
LOT / FIT: The leak off or formation integrity test pressure.
Gas Gradient: The expected pressure gradient of the influx fluid.
Kick Intensity: The value of the kick above the pore pressure.
Safety Margin: The safety margin in pressure units.
Pit Gain: The expected pit gain before the well is shut in.
Currently the Casing Standoff module is not available. These inputs will have no effect on the calculation results.
At the bottom of the page, below the results charts, are the Input Tables. These tables must be filled in to run the torque & drag and hydraulics calculations for the Engineering model. The exception to this is the Kick Tolerance Limits table, which is only required for the Kick Tolerance result.
Enter the pump flow rates that will be used for the hydraulics modelling. The torque and drag modelling also requires one flow rate to be entered. If multiple flow rates are entered, the torque and drag calculation will use the FIRST value in the list.
Enter the pipe tripping speeds that will be used for the hydraulics modelling. The torque and drag modelling also requires one trip speed to be entered. If multiple trip speeds are entered, the torque and drag calculation will use the first value in the list.
Enter the friction factors that will be for the torque and drag modelling. Each friction factor has a value for cased hole and a value for open hole.
Enter the kick tolerance limits for the case. By default the values in the table will be the same as the image below. The names of the first three warnings levels cannot be changed. New warning levels can be added, and given any appropriate name, but these will be coloured green on the Kick Tolerance results chart.
This section allows the user to define the well construction. Before entering data, make sure a Wellbore has been selected or created in the Case Details section. Multiple wellbores can be saved to the same case, allowing the user to quickly switch between well configurations. The values shown here reflect the wellbore selected in the Case Details Section.
Note that the user should not enter all of the planned casings here. The user should only enter casings which affect the annular space for the relevant section they are modelling. For example, if drilling an 8.5” section which has 9 5/8” casing back to surface, the user would not enter the details of the 13 3/8” casing as this has been isolated by the 9 5/8” casing and does not affect the annulus for this section.
The section type is selected from the drop down in the Comp Type column and the depth is entered in the MD column. The ID of the section is entered in the ID column, and the OD is entered in the OD column. When Open Hole is selected, the OD cell will automatically populate with the same value entered in the ID cell.
A list of the hole section types can be found below:
Open Hole: This must always be the last item in the list
Casing: Casing can be positioned below a riser, open water, or an air gap but must be above a liner or open hole. Multiple casing sections can be added to represent a tapered casing string.
Liner: Must be positioned below casing and above open hole
Air Gap: If drilling in open water without a riser, this must be the first item entered and the next item must be open water.
Open Water: If drilling in open water without a riser, this must be below air gap and must be the second item.
Riser: If drilling with a riser, this must be the first item entered.
The BHA chosen in the Case Details section will be displayed in the Drill String table for the well.
The drill string can be edited in the same way as in the Drill String page. The Tool Inventory and Component Catalogue can be opened by clicking on their names to the right. Left click and drag items into the string to insert them.
Note: Any changes made in this table will also affect the drill string saved in the Drill String page for the well. BHA’s can also be created from scratch in this section if required.
In this table, the surveys from the Surveys page in the portal will be displayed.
In the planning stages of a well, where there is a principle plan but no surveys, this section will be blank, with only the tie-on line from surface. When a calculation is run, it will see that there are no surveys available and default to use the principle plan instead. Note that in this situation, if none of the plans are selected as principle, then the calculation will not run.
During the drilling phase, when there are surveys displaying in this section, the calculation will always use the surveys as default. If the calculation depth exceeds the depth of the deepest survey, then the calculation will use a composite listing of the surveys, down to their deepest point, and then tie the plan on from there to the calculation depth.
Note: Any changes made in this table will also affect the surveys saved in the Surveys page for the well.
Once the user has entered all of the relevant data into the Input Parameters and Input Tables sections, they can now run the Engineering case and generate results.
Results charts can be selected in the Results Menu to the left of the chart area, and are split into four categories – Hydraulics, Torque & Drag, Well Control, and BHA Analysis. Click on a category in the Results menu to expand it and reveal the individual results charts for that category. The 5th category, Casing Standoff, is currently not accessible.
When viewing a chart, any warnings or errors for that chart will appear at the top of the Results Menu. A warning represents an issue with the inputs for the engineering case that could be affecting the results of the current chart. An error represents an issue with the inputs that is preventing the calculation from generating a result. For more details, hover over the warnings or errors icon.
On any chart, use the mouse scroll wheel to zoom in and out of the chart. Left click and drag to move the viewing area of the chart around. Hover over a line on the chart to read the X and Y axis values at that point. Left clicking any series in the legend will toggle the visibility of a series off /on from the chart.
This menu contains the Calculate function, which the user must click to run the model for their case. It also contains functions that allow the user to customize the charts, display additional drilling data, or export the model results. The functions that are available will vary depending on the chart currently being viewed.
The Chart Controls menu contains the following functions:
Export as Image: In addition to the export options in the Chart Controls menu, the user can also export the current chart as an image. To do so, right click on the chart and select Save image as to save the chart to an image file. Alternatively, select Copy image to copy the chart to the clipboard.
Expand the Hydraulics section to access the Hydraulics results charts.
This chart displays the standpipe pressure (SPP) expected at surface when the bit is at the depth specified on the Y-Axis. There will be a line displayed for each of the flow rates entered in the Flow Rates input table. Slide sheet and EDR on/off bottom pressure data can be overlayed on this chart.
This chart displays the following lines for each of the flowrates entered in the Flow Rates input table:
Clean ECD: The ECD at the end of the string, when the bit is at the depth specified on the Y-Axis, based on a cuttings-free annulus.
Dirty ECD: The ECD at the end of the string, when the bit is at the depth specified on the Y-Axis, based on a cuttings-loaded annulus. The volume of cuttings in the annulus is calculated based on the ROP entered in the Drilling Parameters section. If the ROP is entered as zero then the clean and dirty ECD lines will lie on top of each other.
Mud Weight The Mud Weight entered in the Mud section.
The ECD snapshot chart shows the expected ECD at each point in the annulus when the bit is at the Calculation Depth specified in the Case Details section. This line is generated based on a cuttings free annulus, which means that the last points for both the ECD chart and the ECD Snapshot will be the same.
The chart displays a line for each of the flow rates entered in the Flow Rates input table. Additionally the Mud Weight entered in the Mud section will also be displayed.
This chart displays the surge and swab lines for each of the tripping speeds entered in the Trip Speeds table.
The Y axis corresponds to the bit depth regardless of what has been selected as the Surge & Swab Reference in the Hydraulics section. The results, however, display the calculated values at the surge & swab reference based on the bit position. So if for example you have the reference point selected as the bottom of the hole, when you look at the chart, it will be displaying the surge and swab pressures at the bottom of the hole, when the bit is at any given depth.
This chart shows the maximum speed that you can trip in and out of the well, without causing surge & swab effects that would push the effective mud weight (EMW) beyond limits specified by the user. The Y-Axis shows the measured depth, while the X-Axis displays the tripping in/out speed.
The minimum and maximum allowed EMW are set in the Input Parameters under the Advanced – Surge & Swab section.
The minimum flow rate plot is a snapshot chart which shows the minimum flow required to keep the hole clean at all points in the wellbore for a range of ROPs at a certain depth. The ROP value in the Drilling Parameters section will be used as the lowest ROP and 4 additional ROP values that are 125%, 150%, 200% & 250% larger will be automatically generated.
To interpret the plot, the user needs to find the largest flow rate for any one ROP and that will be the minimum flow that is required at that depth to keep the hole clean. This can be done by hovering the mouse pointers over the desired line.
Expand the Torque & Drag section to access the Torque & Drag results charts.
This chart displays the calculated hookload values for slack-off (tripping in), rotating off bottom and pickup (tripping out). For slack-off and pickup, there will be a line represented for each set of friction factors entered in the Friction Factors table. The Y-Axis denotes the bit position.
The minimum weight to helically buckle (tripping in) will also be displayed on this chart. Any tripping in line which crosses this limit will start to experience buckling in the string. At this point it may be difficult to effectively transfer weight down hole and the string may need to be rotated in order to get to bottom. From the chart, you can tell the string depth and hookload where the buckling will occur, but you will not be able to determine where in the string the buckling is occurring. To determine this, consult the on and off bottom tension snapshot charts. Slide sheet and EDR pick up, slack off and rotating off bottom data can be overlayed on this chart.
The Calculated Friction Factors chart combines the data entered by the user for the case with recorded WITS and slide sheet data, to try and back-calculate friction factors for the well bore.
The chart will generate two lines based on the Pick Up hookloads and Slack Off hookloads recorded in the slide sheet. This requires drilling parameter data to be recorded in the Slide Sheet page for the well. It will also generate four lines based on WITS data recorded when Picking Up, Slacking Off, Tripping In and Tripping Out. This requires WITS data for the well to be stored in the Data Acquisition section and the operation is automatically determined via the rig states. If the stored drilling parameter or WITS data is updated, the charts must be refreshed by clicking on the Refresh Drilling Parameters button beside the Calculate button.
This chart displays the on and off bottom torques. For each operation, there will be a line represented for each set of friction factors entered in the Friction Factors table. The Y-Axis denotes the bit position. Slide sheet and EDR on bottom torque data can be overlayed on this chart.
This chart is a snapshot chart, meaning that the bit depth stays at the calculation depth specified in the Case Details section. The Y-Axis value denotes the position in the drill string, while the X-Axis value shows the tension in the string at that point. The chart displays the following lines:
Rotating on Bottom: Rotating with the WOB from the Drilling Parameters section applied.
Sliding: A Sliding line will be represented for each of the entered friction factors.
Sinusoidal Buckling: If the Rotating or Sliding lines cross this threshold, the string will experience sinusoidal buckling at that point. The further the line drops below the threshold, the more severe the buckling during the activity in question.
Helical Buckling: If the Rotating or Sliding lines cross this threshold, the string will experience helical buckling at that point. The further the line drops below the threshold, the more severe the buckling during the activity in question.
This chart is a snapshot chart, meaning that the bit depth stays at the calculation depth specified in the Case Details section. The Y-Axis value denotes the position in the drill string, while the X-Axis value shows the tension in the string at that point. The chart displays the following lines:
The chart displays the following lines:
Rotating off Bottom: Rotating off bottom with no WOB applied.
Pick-up (PU): A Pickup line will be represented for each of the entered in the Friction Factors table.
Slack-of (SO): A Slack Off line will be represented for each of the entered in the Friction Factors table.
Sinusoidal Buckling: If the Rotating or Sliding lines cross this threshold, the string will experience sinusoidal buckling at that point. The further the line drops below the threshold, the more severe the buckling during the activity in question.
Helical Buckling: If the Rotating or Sliding lines cross this threshold, the string will experience helical buckling at that point. The further the line drops below the threshold, the more severe the buckling during the activity in question.
This chart is a snapshot chart, meaning that the bit depth stays at the calculation depth specified in the Case Details section. The Y-Axis value denotes the position in the drill string, while the X-Axis value shows the side force in the string at that point.
The chart displays the rotating side force along with the pickup and slack off side forces for each set of friction factors entered in the Friction Factors table.
This chart displays the apparent weight on bit (WOB) required at any given depth to achieve the actual WOB entered in the Drilling Parameters section.
To read the chart the user should select the measured depth of interest and note the apparent WOB for each of the friction factors at that depth. These are the WOB values the driller will need to see at surface in order to achieve the desired actual WOB down hole at the bit.
This chart displays the number of completed revolutions that the rotary table must be turned in order to turn the bit. A line will be represented for each of the friction factors entered in the Friction Factors table. The Y-Axis denotes the bit position.
This chart displays the amount of pipe elongation the user would see when picking up, for each of the friction factors entered in the Friction Factors table. The Y-Axis denotes the bit position.
The Well Control section currently contains one results chart – the Kick Tolerance chart.
Displays the kick tolerance for the well, based on the inputs in the Well Control section, when the bit is at the depth specified on the Y-Axis.
The blue lines represent the kick tolerance for an influx, while the red lines represent the swab kick tolerance. For each there is a line for the mud weight as well as lines for ±0.5 MW units and ±1 MW units.
In the Kick Tolerance Limits input table, the user can enter the warning levels for different amounts of kick tolerance. Under the Chart Controls menu, toggle on Shade Limits to display these warning levels as regions on the chart.
Expand the BHA Analysis section to access the BHA Analysis results charts. Note that as this calculation uses finite element analysis (FEA), it will take longer to calculate than the torque and drag and hydraulics, and this is expected.
The 2D Line Charts page contains several charts that model the bending moment, deflection, rotation, contact force, shear, axial deflection, torsion, tension and torque in the BHA.
The X-Axis for every chart represents the distance along the BHA from the bit, while the Y-Axis represents the magnitude of each output being modelled.
A magenta line indicates the maximum value on each chart. Hover over a point on each chart to see more information, including the BHA component that is present at that point.
The charts in the 2D Contour Plots model the same outputs as the 2D line charts. However, in every chart the Y-Axis shows the OD of the BHA components. The shape of each chart shows the high side deflection of the BHA.
For each chart, the chart is coloured to represent the magnitude of the output being modelled. Refer to the key beside each chart, or hover over a point on each chart to see the exact output value, including the BHA component that is present at that point.
The 3D Chart result visualises the BHA in a 3D space while displaying results from the 2D Contour Plots results.
The chart is centred on the work sight circle. Use the up and down arrow keys on your keyboard to move the work sight up and down the drill string. The overlay in the top left will display the BHA analysis output values for that point. The chart can be rotated by left-clicking and dragging the mouse, and can be zoomed in and out using the mouse scroll wheel. The size of the BHA on the chart represents the OD of each component, while the shape of the BHA represents the high side deflection at each point.
Beneath the chart are a number of options that can be toggled:
Wellbore: Toggles the display of the wellbore.
Overlay: Toggle this option off to hide the text overlay in the top left.
Contact Force: When toggled on, the chart will display vector arrows that show the direction and magnitude of the contact force between the BHA and the wellbore.
Vertical Scale: Toggles the Z-Axis of the chart, representing TVD.
Colour by Bending Moment: When toggled on, the colour of the BHA represents the magnitude of the total bending moment output. When toggled off, it represents the shear load output.
Worksight: Toggling this off will hide the work sight circle.
This chart predicts the build/drop rate of the BHA at a range of inclination values, against a range of either WOB or motor bend values specified by the user. The red lines represent sliding activity and the blue lines represent rotating activity. The X-Axis displays the inclination of the wellbore, while the Y-Axis displays the predicted build rate. Hover over a point on a line to see the predicted build/drop rate at the specified inclination.
When viewing this chart, additional options become available in the BHA BUR Params tab that appears in the Input Tables section below the chart. Note that if any changes are made, the user must select the Calculate function to re-run the model.
Variable: Select the input parameter that will be varied. Users have a choice between WOB or motor bend.
Star/End WOB: If WOB is selected in the Variable option above, enter the range of WOB values that will be modelled.
Start/End Motor Bend: If motor bend is selected in the Variable option above, enter the range of motor bend values that will be modelled.
Start/End Inc: Enter the range of inclination values that will be modelled.
Rotating: Unselecting this option will move the rotating lines from the chart.
This chart shows the predicted BHA modes that the driller should avoid. A BHA mode is a combination of WOB/INC and RPM that cause lateral vibration in the drill string which coincides with the strings natural frequencies. This can cause excessive vibration in the string.
When viewing this chart, additional options become available in the BHA RPM Params tab that appears in the Input Tables section below the chart. Note that if any changes are made, the user must select the Calculate function to re-run the model.
Variable: Select the input parameter that will be varied. Users have a choice between WOB or Inclination. When WOB is chosen, the model will be run at the inclination of the wellbore at the Calculation Depth. If Inclination is chosen, the model will run at the WOB set in the Input Parameters section. The Y-Axis label will change to show the chosen parameter.
Start/End WOB: If WOB is selected in the Variable option above, enter the range of WOB values that will be modelled.
Start/End Inc: If Inclination is selected in the Variable option above, enter the range of inclination values that will be modelled.
The BHA Mode Shapes chart is used in conjunction with the BHA Critical RPM chart. It displays the magnitude of each BHA mode identified in the Critical RPM chart, as well as the location of the vibration in the string. The Y-Axis displays the magnitude of the vibration, expressed as displacement from the centre line of the string. The X-Axis displays the position of the vibration in the string, expressed as distance from the bit.
Note that modes with a relatively large magnitude can distort the scale of the chart. To view a mode with a smaller magnitude, it can be useful to hide other modes by clicking on them in the legend.
Covers registration and configuration of an OAuth App on the Okta identity management platform.
The Innova API can be integrated into Okta, allowing Innova logins to be managed through your organization’s single sign-on system. This document covers the steps required to register an app on Okta and configure permissions for it.
Input all data as per this document. Naming conventions are critical for this function to work successfully!
2. Click on Admin in the top right of the window to access the Admin Dashboard.
3. On the side menu to the left, click on Applications to expand the Applications sub-menu, then click on Applications again to open the Applications window. In the Applications window click on Create App Integration.
4. On the Create a New App Integration page, select the sign-in method as OIDC – OpenID Connect and the Application type as Native Application. Then click on Next.
5. On the New Native App Integration screen in the General Settings section, enter the App Integration Name as ‘icpApi’. Toggle on Refresh Token and Resource Owner Password.
In the Assignments section, the Controlled Access setting should be set according to your organisation’s policy. All other settings in the New Native App Integration window can be left as their defaults. Click Save.
6. On the next screen, named ‘icpApi’ in this case, click on the Edit button in the Client Credentials section.
Change the Client Authentication setting to Client secret, then click Save.
8. Scroll back up to the top of the screen and click on Sign On.
9. In the Sign On screen, scroll down to the User Authentication section and click on Edit.
Change the Authentication Policy to Password Only and then click on Save.
10. Scroll back up to the top of the screen and click on Okta API Scopes.
11. Click on Grant next to the Okta.apps.read scope to grant consent.
12. Scroll back up to the top of the screen and click on Okta API Scopes.
13. Click on Assign and then Assign to People.
14. Assign the relevant users by clicking on the Assign button beside each user, then click Done.
If your organization wishes to have MFA logins turned on for the Innova Web Portal, Mobile App and Well Seeker Pro server database logins, then they must first follow the below steps within Okta. In addition to these steps, the system admin will require to turn on MFA for the organization, or for individual users within Okta. For that process the user should refer to Okta documentation.
Navigate to the icpApi application General Settings page. Change the grant types to the below.
Add the below to the call backs
Within the Innova infrastructure the following information provided by the client is input in to the following cells in the Organizations tab:
Client ID: Input in to CLIENT ID
Client Secret: Input in to CLIENT SECRET
Domain: Input in to TENANT (DIRECTORY) ID
In the DOMAIN NAME cell, input the end of the company email address, e.g., @innova-drilling.com
A guide to managing an AWS account, including additions and changes relating to Well Seeker Pro.
Once a user has set up their AWS account, an RDS and an EC2, they then require to manage that account. As time goes on the software is updated, company personnel change, and the way the user uses the software may change. This document is intended to give the admin in charge of managing the AWS account a guide as to how to manage certain additions and changes relating to Well Seeker Pro.
The system diagram below details how the AWS SQL Server Database and EC2 fit in to the structure of data flow within Well Seeker Pro.
Before you start, to save time, there are some programs which should be downloaded and installed, as access to these will be required at various points throughout the document.
These programs and the relevant links are detailed below.
Download the 32-bit MSI
During installation, select the Commander interface style
Installation of SQL Management Studio can take a while, which is normal and expected.
In addition to installing the above programs on your computer, install the Google Authenticator App on a suitable mobile phone.
There are several reasons a company may require an additional database, the most likely is so they can have a “Dirty” database which the field engineers populate remotely via the Real Time Data Exchange, and a “Clean” database where only QAQC’d data is stored. Another popular reason would be to allow a third party to access server data without them having access to the company’s master database.
An additional database is created using SQL Server Management Studio:
1. Open SQL Server Management studio. Login as using the below information
a. Server Type: Database Engine
b. Server Name: This is the Endpoint followed by a comma, followed by the Port number
c. The Login and Password for the database are the same as when the database was created
2. Right click on the databases folder and click create new database
3. Give the database a name and click add then click ok
a. It is important to take a note of the database name, exactly as it has been entered, as this is case sensitive and will be required to access the Db via Well Seeker
4. You should now see the database in the tree. If you do not see the database you have just created, hit refresh and it should appear
5. When you expand the database and open the tables tree item you will see there is nothing there
6. You need to connect to the database with Well Seeker to create the tables and set the database up. Well Seeker does this automatically on the first connection to the database
7. Until you create a new user, you will need to login with the same details used for your primary database
a. NOTE: You need to make sure the Database Name is the name of the new database you have just created
8. Click connect:
a. It is likely it will say the Db schema is out of date. Select yes to update
b. It will say there are no admins and ask if you want to make this user an admin. Select yes
9. On first connecting, Well Seeker will create all the relevant tables in the SQL database
10. You can now close Well Seeker
11. Open the server database in SQL Server management studio.
12. In the Object Explorer Tree, navigate to the tables folder under your database.
13. Scroll down till you get to the dbo.DB_SETTINGS table.
14. Right click on the table and select Edit Top 200 Rows.
15. Insert a single record in to the table: ./icdsFileDir/
a. This sets the field IMAGE_PATH for the remote Db, which is where any logos and attached files will be stored.
With a new (additional) SQL server database created it may be necessary for the user to set up an ICDS server for this database to allow data exchange between it and other databases. The following section details the steps required to achieve this.
1. Open WinSCP and login. See Appendix A – Login To WinSCP for details
2. You will now have the below, where you have created a drag and drop file explorer interface to the AWS EC2. If you do not see the Ubuntu folder on the right, its likely because you are already in it. Just select the only folder showing and it should then display the ubuntu folder
Note: If you have been using the original database prior to setting this second database up, and have been performing data fetch operations, you may find there are a lot of zipped folders named “Pull Files” now present in the window, where there were previously none. This is expected
3. Create a new directory called icdsServer2
1. Take a copy of the 2 files (icdsServer and configICDS.JSON) which are currently in the drop file explorer interface
2. Take the configICDS.JSON and do the following:
a. Open this file in a text editor e.g. Notepad
b. Change the sqldbname to the name of the new database created in section 3.0
c. Change the Port to 42001. This is ESSENTIAL as this is the port which will be entered into the Well Seeker RT Data exchange for communication with this ICDS. 42000 is already being used so it must therefore be different
d. Keep the rest of the information the same INCLUDING the name of the file. For more details see Appendix C – configICDS.json
3. Once completed, drag both files into the new icdsServer2 folder
4. Right click on the icdsServer file and select Properties. Then ensure all the below permissions are checked
a. Note: If these are not all checked, you may receive an error message when starting the pm2 in the next section
5. In the same folder as the above two files create a new folder called icdsFileDir
6. Close WinSCP
1. Open PuTTY. See Appendix B – Login to PuTTY, for instructions on how to login to the PuTTY interface
2. Check pm2 is running by typing pm2 ls. This should display as below, showing the icdsServer as being online
3. Type pwd, which will show the current location you are in. This should be /home/ubuntu
4. You now need to change the location by typing cd /home/ubuntu/icdsServer2
5. Now start the new instance: pm2 start icdsServer –-name icdsServer2
6. Within pm2 the new ICDS is now referred to as icdsServer2, which differentiates it from the original ICDS that was already running on the EC2
7. You should now see the below where BOTH icdsServer files are Online
8. Type pm2 ls to check the icdsServer2 still has a status of online
9. Save the current pm2 settings so it starts correctly after a server restart: pm2 save
10. Close Putty
With the addition of the new ICDS Server, which is using a new port (42001), this port needs to be added to the AWS incoming and outgoing security rules in the EC2. Failure to do this will result in a connection error, and the user will not be able to use the data fetch and transfer features. Add the below rule to both the incoming and outgoing EC2 Security rules.
1. Additional Rule:
a. Type: Custom TCP
b. Port: 42001
c. All public IP addresses to be allowed
i. The reason to allow all public IP addresses is because it is difficult to know the relevant public IP addresses for each rig computer which is out with the company’s network. Setting a range here could mean some rig computers are unable to communicate with the ICDS
ii. For larger companies who have the relevant IT structure, they may want to set an IP range for computers in their network. This is more secure
iii. If a company does select an IP range, and we end up having to provide support, they may need to add our IP addresses in as a rule otherwise we will not be able to access
2. The Inbound and Outbound security rules in the EC2 should now look like the below
The original master user which was created with the RDS has access to all parts of the RDS and has full admin control. Supplying login details like this to everyone in the company is not ideal. To get round this, you can create a new login, which will have more restricted access.
An additional Login is created using SQL Server Management Studio.
1. Open SQL Server Management studio and go to the tree on the left and under Security right click on logins and select New Login
a. In the Login Properties dialog, select SQL Server Authentication and enter a login name and password. Choose something sensible here, like the name of the company and Guest after e.g. InnovaGuest
b. Select Enforce Password Policy, but leave the other password options unchecked
c. Select the default database from the dropdown
i. Select the new database here
d. Keep a note of these new login details:
i. Login: InnovaGuest
ii. P/W: InnovaGuest
2. Select Server Roles on the left-hand side of the dialog, and check Public
3. Select User Mapping on the left-hand side of the dialog:
a. In the top section, you will see the available databases. Check ONLY the database you want the user to have access to
i. You will see the new username populate in the cell to the right of the database name
b. In the bottom section, check public and db_owner
4. Select Securables on the left-hand side of the dialog. This section will be empty but will populate after the login has been created
5. Select OK at the bottom of the dialog and this will create the new login
6. Right click on the new login and select properties. Then go to Securables
a. This time the section will be populated
b. Connect SQL is already checked with the Grantor being rdsa
c. In the row above, there is another Connect SQL option. Check the Grant box for this and then OK.
WS users are designated to give each user individual login credentials and controlled user permissions when they access the server database via Well Seeker Pro. The below steps will outline how to add WS users and explain the permissions options.
1. Open Well Seeker Pro
2. Select File > SQL Server Databases > Connect to remote database
3. Fill in the login credentials and select Connect
4. Once you have connected to the remote database select Tools > User Permissions. This will open the User Permissions dialog
5. To add a new WS user select Add User. This will add a new blank row to the table. Input the new users username
6. Leave the Password cell blank. This will be populated after the new user logs on for the first time and has chosen their password. If at any time a user has forgotten their password, the admin can delete the information in the password cell and the next time the user logs in they will be asked to create a password like a first time login
7. Check the relevant permissions boxes for the WS user. Below is a description of each permission:
a. Create New Items – The user will be able to add new data to the database
b. Delete Items – The user will be able to delete existing data from the database
c. Edit Items – The user will able to edit existing data from the database
d. Administrator – An administrator can add, remove and edit user permission details
e. Approver – An approver can approve bid sheets
8. Once the user permissions have been set select Apply. The dialog will automatically close
9. If you wish to remove a user, select the relevant row and select Delete User
As with Well Seeker Pro, the ICDS is updated periodically with improvements and additional functionality. As such, the ICDS may require to updated in order to gain access to this functionality. The below steps outline how to update the ICDS executable to the latest version.
1. Open WinSCP and login to the EC2. See Appendix A – Login To WinSCP for details
2. You will now have the below, where you have created a drag and drop file explorer interface to the AWS EC2. In the right hand panel you should now see the default folder on the EC2 / virtual machine that contains the current icdsServer executable file. On the left panel is your local PC
3. Download the ICDS files via the link provided by Innova
4. Remove the .linux extension from the icdsServer.linux file
5. Delete the existing icdsServer file from the EC2 (right hand panel)
6. Drag the new Linux executable icdsServer file from the local PC (left hand panel) to the EC2 / virtual machine folder(right hand panel)
7. You will get the below left popup. Select OK and you get the below right
8. Right click on the icdsServer file and select Properties. Then ensure all the below permissions are checked
a. Note: If these are not all checked, you may receive an error message when you restart the pm2
9. If required update the .json file. See Appendix C – configICDS.json for details
10. Close WinSCP. You will get the below. Selected No, so that the workspace is saved
11. Open and login to PuTTY. See Appendix B – Login to PuTTY for details
12. Restart the ICDS server. See Appendix D – Restarting the ICDS Server for details
Within AWS, there is the potential to restore an RDS to the condition it was in at a previous timestamp. The AWS account administrator is in control of the settings that determine if and when these restore points are created in the AWS account.
The purpose of this section is to guide the user through a couple of scenarios where restoring to a previous database condition may be useful and some suggested steps to carry out the restore:
Database restoration required to completely replace the existing version of the SQL database
Database restore required for a particular data table, or small number of data tables within the SQL database
The below steps are required to be carried out, regardless of the level of restoration that is required to be undertaken.
1. Log on to the AWS account where the SQL database is hosted
2. Navigate to the RDS > Databases page
3. Select the database that requires restoring
4. Select the Maintenance & backups tab and scroll to the bottom section called Snapshots
5. Select the snapshot that you want to restore to by selecting the checkbox and the selecting Restore
6. When restoring a snapshot, you do not overwrite your existing database. The restored information will be created as an additional database. In the DB Instance Class cell select the same instance class as your existing database
7. In the DB Instance Identifier cell, input the name you want to call the restore point database. This is the name it will have when viewed in the AWS console. If left blank then a random name will be generated
8. In the Public accessibility section select Yes. Very important to select this, as the restored database will effectively be useless if you don’t. Double check this before restoring the database, as selecting some options reverts this back to No
9. In the Availability zone section select the zone your current database is in
10. In the VPC security groups section select the security group that your current database has selected
11. Leave the rest of the options as default, double check point 8 and then select Restore DB Instance
12. AWS will now create the restore point database and will have a status of Creating until the database is ready. This process will take varying amounts of time depending upon the size of the database that is being restored
13. Once the status of the database has changed from Creating to Available the user can move on to the next step.
14. All of the restored database login credentials should be the same as your original database instance, with the exception of the endpoint/url. From the Databases table select the restored database
15. Take a note of the endpoint details in the Endpoint & port section of the Connectivity & security tab
16. If your original database is irreparable and it is required to use the restored database going forward then see section 8.1. If the majority of the original database is correct and only a small portion of the original database requires restoring, then see section 8.2
If the original database is such that it is best to abandon it and use the restore point database going forward, then follow the below steps.
1. The new restored database, the users must input the new endpoint in the Connect to remote database dialog within Well Seeker Pro, overwriting the previously used endpoint. All other details should remain the same. This process will need to be completed on each computer logging in to the restored database
2. In order to have computers pushing and pulling data from the restored database via the Real Time Data Exchange and Remote Data Fetch dialogs, the admin must update the endpoint in the .json file on the EC2. In order to do this:
a. Log on to the EC2 using WinSCP. See Appendix A – Login To WinSCP for details
b. Locate the configICDS.json file and open in a text editor
c. Edit the endpoint in the configICDS.json file. See Appendix C – configICDS.json for details. Save the change and close the file
d. Close WinSCP
e. In order for the changes in the .json file to take effect, the ICDS server needs to be restarted. Restart the ICDS server. See Appendix D – Restarting the ICDS Server for details
3. Logging in to the restored database via SQL server management studio will require the new endpoint to be included in place of the old database endpoint
If only a small portion of the database needs to be replaced i.e. a few data tables, then it may be easier to replace the problematic data in the original database with good data from the restored database. This has the benefit of not having to get all of the users to change their endpoint login details and the admin would not be required to update the EC2 .json file either.
1. Take note of the names of the database tables that contain data that needs to be replaced with the restored data
2. Open SQL Server Management Studio. In the login window input the new endpoint followed by , 41433 with 41433 being the RDS port number. All other login details remain the same as the original database. Select Connect
3. This will open the restored RDS. Navigate within SQL Server Management Studio and open a required table in the required database, by right clicking on the table in the tree and selecting Select Top 1000 Rows
4. If there are more than 1000 rows of data in the table that the user wants to export, the user can increase the command line to display a greater number of rows in the table. The user then selects Execute to run the command, which will update the table display with the inputted number of rows, or all of the rows in the data table, if that number is smaller than the input number. In the below example the command will allow the user to see the top 9000 rows in the selected table
5. Select the top left cell in the data table, right click and select Copy with Headers
6. Open a blank excel document and paste in the copied data. In excel select File > Save As and save the document as a .csv file
7. Repeat this process for all required database tables
8. When importing this data to the original database the data is added to the existing table, it does not overwrite it. With this in mind, edit the data in the .csv file to include only the data that you plan on adding to the original database
9. Log out of the restored database in SQL Server Management Studio
10. Log in to the original database using SQL Server Management Studio
11. Right click on the required database and select Tasks > Import Flat File…
12. Select Next
13. Browse to the saved file and select. NOTE, this process is going to create a NEW table in your database. It does not pull the data into an existing table. You will be asked to enter a table name. Choose something suitable so it is easy to find. Also make sure it is not the same as an existing table. Then hit Next
14. Preview the data. Have a check and select Next
15. The user will proceed to the modify columns section. Be careful here as the data types are decided automatically by the program. Well Seeker has what’s called nvarchars opposed to Floats. If anywhere you see Float, change this to nvarchar. You will see that there are several options here which differ with a number at the end e.g. nvarchar(1), nvarchar(100) etc. Select the same nvarchar number as the one above and below in the table
16. Select Next and then Finish. Once the results section indicates Operation Complete select Close
17. Navigate through the tree within the original database. The user will see there is now a new table with all the imported data. It will be named whatever was entered in step 12
18. From the toolbar select New Query
19. The user can now edit and use the following query to insert all the data from the new table into the required table in the database:
insert into [PhilEuroDb1].dbo.DAILY_ACTIVITY select * from [PhilEuroDb1].dbo.restoredData
In the above, the command is inserting data into the DAILY_ACTIVITY table in the PhilEuroDb1 database from the restoredData table, which is also in the PhilEuroDb1 database. If the table containing the restored data is in a different database, then just enter the appropriate database name
20. From the toolbar select Execute
21. The Messages section will update to show the query was executed successfully
This data will not overwrite the information in the table it is writing to, but rather just add to the data that is currently there. As a result, if the user is restoring some specific data, opposed to the whole table, which has maybe been wiped, then you take the data from the restore to excel, delete all the info the user doesn’t need, leaving only the specific info to be restored, and then follow the instructions as normal. This ensures that the data that’s added to the table is only what is needed
22. Repeat this process for each table that requires data to be imported to
23. Once completed, delete your backup tables. The process is now complete
A good guide to SQL commands can be found at the below web link
When storing WITS data to a databases tables, the database size becomes large very quickly, which can affect the performance of the database. It is advised that if a user wishes to save WITS data to a server database that they do so on a second database to avoid this issue. Below are outlined steps to achieve this:
1. Ensure a second server database has been set up. See section 3.0 – Adding a New Database for details
2. Open and login to WinSCP. See Appendix A – Login To WinSCP for details
3. Open and edit the configICDS.json file, specifically the sqldbnamewits and transferWits inputs. See Appendix C – configICDS.json for more details
4. Save and close the .json file
5. Close WinSCP
6. Restart the ICDS server to utilise the new details entering in the .json file. See Appendix D – Restarting the ICDS Server
7. Any WITS data pushed back to the server will now also be stored in the CURWITS_DATA table in the second database every 5 seconds
If you have historically had issues where field personnel push data from an old well in their local database, there is the potential that they could overwrite QCed or finalised data on the server. To avoid this there is the option to only allow data to be pushed to wells that have a status of Active, Upcoming, or Standby. This obviously requires the well status to be updated accordingly by the appropriate users for it to be successful. This option is facilitated by an input in the configICDS.json file located on the EC2. See below steps to enable this option:
1. Open and login to WinSCP. See Appendix A – Login To WinSCP for details
2. Open and edit the configICDS.json file, specifically the allowActivePush input. See Appendix C – configICDS.json for more details
3. Save and close the .json file
4. Close WinSCP
5. Restart the ICDS server to utilise the new details entering in the .json file. See Appendix D – Restarting the ICDS Server
The SQL server database at any one time has a fixed database schema, or structure. This structure will be the same for all users using the same version of Well Seeker Pro. When a user logs on to the server database, Well Seeker Pro runs a check to see if the users current version of Well Seeker Pro matches the database structure of the server database. If it does not then it will ask the user if they wish to update the database schema. If the user selects yes, then the server database structure is updated to match the version of Well Seeker Pro.
Potential issues can arise (error messages) when a company does not roll out a new version update of Well Seeker Pro correctly and multiple users are running different versions of the software at the same time and accessing the server database.
In order to prevent this issue during a Well Seeker Pro roll out the database admin can lock the version / structure of the server database, so that the users cannot change the structure upon logging in to the server. Once the roll out was completed the database admin can then unlock the version / structure and it can be update to the latest version. See below for the steps involved.
1. Open SQL Server Management studio and log on to the RDS in question
2. Right click on the database in question and select New Query
3. Input INSERT INTO DATABASE_INFO (UPDATE_NUM, UPDATE_VERSION) VALUES (‘999’, ‘-999.25’)
4. Select Execute
5. The database version is now locked until the below steps are followed
6. Right click on the database in question and select New Query
7. Input DELETE FROM DATABASE_INFO WHERE UPDATE_NUM = ‘999’
8. Select Execute
9. The database version can now be updated as usual
Security rules may be required to be updated after the initial setup, for example if IP public addresses of users changes. Separate security rules apply for the RDS and EC2 and will need to be edited separately.
Below are some recommended settings. The RDS database has communications with:
The ICDS (located on the EC2 Instance)
Well Seeker / SQL Server Management Studio
When creating a security rule, the 2 main pieces of information required are the Port and the IP address. Set the RDS Incoming and Outgoing Security rules as detailed below:
1. Rule one:
a. Type: Custom TCP
b. Port: 41433
c. All public IP addresses that require access to the RDS via either Well Seeker or SQL Server Management Studio
i. For larger companies who have the relevant IT structure, they may want to set an IP range for computers in their network. This is more secure
ii. If there are just a few IP addresses to be added, the smaller companies can find each Public IP by accessing the web browser on each computer and typing “ip4.me” into the address bar at the top of the page
iii. If a company does select an IP range, and we end up having to provide support, they may need to add our IP addresses in as a rule otherwise we will not be able to access
iv. End the IP addresses with /32
2. Rule Two:
a. Type: Custom TCP
b. Port: 41433
c. Security group assigned to the EC2 instance
The EC2 instance has inbound communications from:
WS - data fetch and exchange
RDS database
WinSCP and PuTTY
When creating a security rule, the 2 main pieces of information required are the Port and the IP address. Set the EC2 Incoming and Outgoing Security rules as displayed below:
1. Rule One (This should already be present when you open the rules dialog):
a. Type: SSH
b. Port: 22
c. Only public IP addresses of admins who will be using WinSCP or Putty to access the EC2
2. Rule Two:
a. Type: Custom TCP
b. Port: 42000 or whichever port is used for push and pull traffic
c. All public IP addresses to be allowed
i. The reason to allow all public IP addresses is because it is difficult to know the relevant public IP addresses for each rig computer which is out with the company’s network. Setting a range here could mean some rig computers are unable to communicate with the ICDS
ii. For larger companies who have the relevant IT structure, they may want to set an IP range for computers in their network. This is more secure
iii. If a company does select an IP range, and we end up having to provide support, they may need to add our IP addresses in as a rule otherwise we will not be able to access
3. Rule Three:
a. Type: Custom TCP
b. Port: 41433
c. Select the security group assigned to the RDS
This function is intended to allow a user to upload an existing local database (.mdb file), or a selection of its data tables to the server. This is useful when a user has migrated all of their data from historical wells in to a local database format.
This should only be used at the very start of a server database’s existence, as the upload will overwrite all data in any selected tables of the server database.
1. Log on to the server database within Well Seeker
2. Select File > SQL Server Databases > Access To SQL Server Transfer
3. Select the local database file to be uploaded to the server and select Open
4. A message window will allow the user to upload all tables, or select which to upload. If the user selects Yes then proceed to step 6, if No then continue from step 5
5. If the user selects No then the Select Data dialog opens. Select the Import box of each table that the user wishes to import. When the user has completed their selection select OK
6. The next message window reminds the user that any existing data on the server database tables will be overwritten by the data that is being uploaded. Select Yes
7. Depending on the size of the transfer and the latency to the server the upload can take a wide range of time. E.g. for larger database migrations of ~1GB the upload can take up to 10 hours. During this time do not close Well Seeker or turn off your PC. An internet connection is required throughout. Once completed the below message will appear
A server database brings many benefits, but one down side is that it will always be slower in operation than a local database. The reasons for this are purely time and distance related. For Well Seeker to carry out a programmed action on a local database, the process is carried out within the user’s computer, a physically short distance, with minimal system interrupts. When the same action is carried out on a server database the process has to be transmitted from the user’s computer, to the server and back. Depending on the server set up this results in varied increased latency times and as such Well Seeker will appear to run slower, particularly for very data intensivee tasks. The steps below will help identify the network latency and if possible suggest ways of improving it.
1. Login to the server database using Well Seeker Pro
2. Select Tools > Real Time Data Exchange. The Data Exchange dialog will open
3. Select the Network Latency button. A window will open displaying the average round trip time for 10 queries to the server database
4. For an AWS database, anywhere between 20-40ms is a very good latency. No further actions are required
5. If the latency is greater than this, especially if >100ms then Well Seeker will appear to operate slowly for certain actions and attempts should be made to improve this
6. Log on to the AWS account, select the RDS and check which region it is in (found in the top right of the AWS account screen). This is where the RDS is hosted by AWS and latency is directly affected by geographically how far this is away from the user’s computer. If AWS offer a location to host the RDS that is closer to the majority of the users locations, then a new RDS should be created in the closer location to reduce latency
7. On the same screen also check the RDS Class. If the class is db.t2.micro then upgrading to a more powerful version may improve latency
8. A computer’s or company’s network firewall settings can also have an impact on latency ( it runs checks on communication to and from the computer, which add time to the operation). As a result, changes in firewall settings may reduce latency
Well permissions have been put in place to give the admin control over what computers can pull what wells via the remote data fetch functionality from the SQL server database, if required. This might be the case when a company employs consultant rig personnel, who they do not want to have access to their historical well data. In order to access and setup well permissions follow the below steps:
1. Log on to the SQL server database via Well Seeker Pro
2. Once connected, select Tools > Well Permissions. This will open the Well Permissions dialog. Note that only Well Seeker users with Admin permissions can access the Well Permissions dialog
3. Well Permissions can be set to two states:
a. Enable Individual Well Permissions disabled. To select this option uncheck the Enable Individual Well Permissions check box. This allows any company computer with Well Seeker installed on and a user who has the EC2 IP address and port number details to pull any and all well data from the SQL server database via the Remote Data Fetch dialog
b. Enable Individual Well Permissions enabled. To select this option check the Enable Individual Well Permissions check box. When this is selected no computers are able to pull down well data via the Remote Data Fetch dialog, even if the user has a company computer with Well Seeker installed and the user has the EC2 IP address and port number details. Only computers entered in the table will be able to pull down a specified well or job number, when the active check box is selected.
The Computer Name for a computer can be found by right clicking on This PC and selecting Properties. Depending on the windows version the user has, the computer name will come under one of a number of different titles. These details will need to be updated on a well by well basis in order to allow the rig personnel access to the required wells
During the RDS and EC2 setup process, the user sets any external files to be stored in a folder on the EC2. If you are using AWS for your storage then Amazon offer a storage device called an S3. The S3 is much cheaper per GB of storage than an EC2. It also makes all files available to any service or person that can access the S3. The S3 does not require the use of Putty and can also be accessed through the Innova Web Portal. This gives many advantages to using an S3 for storing external files.
Follow the below steps:
1. Create an S3 bucket in the users AWS account. This guide doesn’t cover the setup of an AWS S3. For more information see the below web address:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html
2. Create an IAM User with access to the S3 service. Keep a note of the AWS access key and AWS secret key
3. Update the configICDS.json file below fields. See Appendix C – configICDS.json for details
a. externalPath input useS3. This specifies using the S3 as the storage service
b. awsAccessKeyID Input the AWS Access Key ID of the IAM user
c. awsSecretKey Input the AWS secret key for the IAM user
d. awsRegion Input the region where the AWS service is hosted eg “us-east-2” or “us-west-2”
e. s3Bucket Input the name of the S3 bucket which was created to store the Well Seeker external files
4. If the ICDS server executable is less than version 1.9.4 then this will need to be updated. See 7.0 – Updating the ICDS executable version for details
5. If not already done so in the above step, restart the ICDS server. See Appendix D – Restarting the ICDS Server for details
6. With the above steps followed, the ICDS will use the S3 to store and retrieve files
Use the below method if the physical data on the EC2 has been corrupted, but the network and security settings of the EC2 are still functioning correctly.
The files stored on the EC2 are not automatically backed up like the RDS, so the user must first create manual snapshots of the EC2’s storage device (volume). When required the volume snapshot can be restored, so the data on the EC2 is the same as when the snapshot was created. Be aware that having a snapshot stored will be an AWS chargeable extra.
This process does not deal with restoring the EC2 network and security group settings, only the data stored on the EC2.
1. User logs on to their AWS console
2. In Services select EC2
3. Select Instances (running)
4. Select the relevant EC2 instance and select the Storage tab. Take a note of the Volume ID. Think of the volume as the virtual hard drive of your virtual machine and is therefore where all of your files and folders are stored on your EC2. This is what you want to backup
5. Under Elastic Block Store select Volumes
6. Select the volume that the EC2 is using. Select Actions and Create Snapshot
7. Enter a Description and select Create Snapshot
8. Once created, the snapshot of the volume will be located under Snapshots
9. Select Instances (running)
10. Select the relevant EC2 instance and select the Storage tab
11. Select Replace root volume
12. Select the desired snapshot from the dropdown menu and select Create replacement task
13. Once the replacement has been completed the files and folders stored on the EC2 will have been restored to the state they were in when the snapshot was created
14. After changing the volumes the ICDS Server will need to be started again. Log on to PuTTY and start the ICDS Server. See Appendix D – Restarting the ICDS Server
There may be times when a user is experiencing issues with logging in to the SQL server database via SSMS or Well Seeker, or where the external files / data push and pull functions are not working. The below sections will guide the user through some problem solving steps that will help isolate and solve the issue in question.
If the user receives an error message and cannot log in to the RDS via SSMS then follow the below steps:
1. Check the user’s computer has internet connectivity
2. Check the Server type is Database Engine
3. Check the Server name is the RDS endpoint, immediately followed by a comma, then a space and then the RDS port number, which is usually 41433. For example:
a. RDS Endpoint = exampleendpoint
b. RDS Port = 41433
c. Server name entered = exampleendpoint, 41433
4. Check the authentication type is SQL Server Authentication
5. Check the Login entered is the RDS Username the user created when setting up the RDS
6. Check the Password is the RDS password the user created when setting up the RDS
7. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 12.1 RDS for more details.
Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser
If the user receives an error message and cannot log in to the SQL server database via Well Seeker Pro then follow the below steps:
1. Check the user’s computer has internet connectivity
2. Check the Database IP / URL is the RDS endpoint
3. Check the Database Name is the name of the SQL server database as it appears when viewed in SSMS. This should not be confused with the name of the RDS when viewed in the AWS account
4. Check the Port is the port number of the RDS, usually 41433
5. Check the DB Username is the RDS Username the user created when setting up the RDS. If the user has since created an additional user in SSMS, this user name can also be used, as long as they have the clearance to access the database entered in Database Name cell
6. Check the DB Password is the RDS password the user created when setting up the RDS. If the user has since created an additional user in SSMS, this user password can also be used, as long as they have the clearance to access the database entered in Database Name cell
7. Check the WS Username is correct. Each WS username has been created in the User Permissions dialog by a user with administrator permissions.
If the administrator cannot log on to the SQL server database via Well Seeker then they can log on to the RDS via SSMS and look in the dbo.USER_PERMISSIONS table to see if the WS username exists
8. Check the WS Password is correct. If the user has forgotten their password then the admin can delete the users password from the User Permissions dialog. The next time the user logs in they will be asked to enter a new password
9. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 12.1 RDS for more details.
Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser
The Real Time Data Exchange is design to give a user the ability to push data for a specific well from their Well Seeker database, back to the SQL server database. The Remote Data Fetch is designed to give a user the ability to pull data for specific wells from the SQL server database to their Well Seeker database. In order to achieve this there are many things that have to be set up correctly
For both the Real Time Data Exchange and the Remote Data Fetch:
Correct IP and port number input in Data Exchange / Data Fetch dialog. These are the IP of the EC2 and the port number specified in the .json file on the EC2
Correct credentials entered in the .json file on the EC2. See Appendix C – configICDS.json for details
The ICDS server has to be running without error on the EC2. See Appendix D – Restarting the ICDS Server
The EC2 security settings have to be correct within the AWS account. See 12.2 – EC2 for details
The RDS security settings have to be correct within the AWS account. See 12.1 – RDS for details
For the Real Time Data Exchange only:
Correct well selected in the Data Exchange dialog. This well must already exist on the server data base
If the .json file on the EC2 has allowActivePush as false then a computer can push data back to a server database regardless of the well status. If true is entered then a computer can push data back to a server database only when the well status is Upcoming, Active or Standby. The well status is selected in the Daily Reports dialog. See 10.0 – Only Push Data to Active Wells for details
For the Remote Data Fetch only:
If the Well Permissions dialog on the SQL server database has Enable Individual Well Permissions selected, then only wells included in the Well Permissions table will be able to fetch specific wells. In the case that the user does not have permission to download well data, the user will be able to connect to the SQL server database and see the database tree, but there will be no structures below facility level to select, as below.
See 15.0 – Well Permissions for further details
External files for the SQL server database are stored on the EC2, or an S3 and rely upon a similar data transmission method as the real time data exchange and remote data fetch functions. If you are experiencing issues saving or accessing external files and logos, either from the SQL server database, or when the data has been pulled down to a local database, follow the below steps:
1. Ensure the real time data exchange and remote data fetch functions are working correctly. See 16.3 – Real Time Data Exchange / Remote Data Fetch for details. If they are then it rules out a number of potential causes for the issue. If both these functions are working, but you are still experiencing issues with the external files functions then proceed to the next step
2. Ensure that during the database creation the step was followed that created the external files image path in the dbo.DB_SETTINGS table
3. Ensure that the option Push External Files is selected on all computers trying to use the functionality
4. If using an S3 to store external files, ensure that the .json file on the EC2 has been filled in correctly. See Appendix C – configICDS.json for details
5. If any changes were made in step 4, ensure that the ICDS server is restarted. See Appendix D – Restarting the ICDS Server for details
1. Open WinSCP. If you have a saved session select it, login and continue. If not follow the below steps
2. Select protocol as SFTP.
3. Enter the EC2 ipv4 address in the hostname.
4. Username is ubuntu
5. Password is blank
6. Port is 22
7. Click on advanced -> SSH -> Authentication and select the browse option to the right of the private key input cell and select the .ppk file you have saved. Select OK.
8. Click login and click yes to the security notice.
9. You will now have the below, where you have created a drag and drop file explorer interface to the AWS EC2. If you do not see the Ubuntu folder on the right, its likely because you are already in it. Just select the only folder showing and it should then display the ubuntu folder.
Note: If you have been using the original database prior to setting this second database up, and have been performing data fetch operations, you may find there are a lot of zipped folders named “Pull Files” now present in the window, where there were previously none. This is expected.
1. Open PuTTY
2. In the Host Name Cell: Type ubuntu@ then the EC2 ipv4 public IP we took note of earlier. Add this information to the login details section of this document.
a. Select the port as 22 and name the session in the saved sessions box.
3. Then click on Connection - SSH – Auth.
4. Click Browse and select the ppk file you have saved
5. Click Open
The .configICDS.json file is stored on the EC2. The user requires to log on to the EC2 using WinSCP to access and edit the .json file. See Appendix A – Login To WinSCP for details. The .json file stores all of the details that the ICDS requires to remotely push and pull data from and to the server database. It is critical that these details are input correctly, otherwise the data push and pull functions will not work. Below are details of each item in the file.
1. CompanyID: Type Company Name (this will be supplied by Innova and must be written in EXACTLY the same way as its supplied). Make sure Company Name is inside double quotes
2. Port: Usually enter the port field as 42000 (no quotes) – this is the port which will be entered into the Well Seeker RT Data exchange for communication with the ICDS
3. devmode: Leave as false (no quotes)
4. sqluser: Set to the SQL Server master username used to access the database. Make sure this is inside double quotes
5. sqlpass: Set to the SQL Server master password used to access the database. Make sure this is inside double quotes
6. sqlsvr: Set to the SQL Server RDS database Endpoint. Make sure this is inside double quotes.
7. sqldbname: Set to the name of the database you wish the ICDS to connect to. This is the database name that you see when logged in to SQL server Management Studio. Make sure this is inside double quotes
8. sqlport: Set to the port used to connect to the SQL server database (no quotes), usually this is 41433
9. externalPath: Specifies where external files are stored. Input either useDatabase (stores files on the EC2) or useS3 (stores files on an S3)
10. sqldbnamewits: If a user is pushing and storing WITs data to a database separate to the Well Seeker database, insert the name of the database here. Make sure this is inside double quotes. If this function is not used then leave a the doubles quotes empty
11. transferWits: If pushing WITs data to a second database then enter true, if not enter false
12. allowActivePush: If true is entered then a computer can push data back to a server database regardless of the well status. If false is entered then a computer can push data back to a server database only when the well status is Upcoming, Active or Standby. The well status is selected in the Daily Reports dialog
13. awsAccessKeyID: If storing external files on an s3, input the AWS Access Key ID of the IAM user. If not leave blank
14. awsSecretKey: : If storing external files on an s3, input the AWS secret key for the IAM user. If not leave blank
15. awsRegion: : If storing external files on an s3, input the region where the AWS service is hosted eg “us-east-2” or “us-west-2”. If not leave blank
16. s3Bucket: If storing external files on an s3, input the name of the S3 bucket which was created to store the Well Seeker external files. If not leave blank
17. Leave all other fields as they are
1. In order for the changes in a .json file to take effect, the ICDS server needs to be restarted. Open and login to PuTTY. See Appendix B – Login to PuTTY for details
2. Check pm2 is running by typing pm2 ls This should display as below, showing the icdsServer as being online
3. Stop the ICDS server. Type: pm2 stop icdsServer
4. Now start the ICDS server. Type: pm2 start icdsServer
5. You should get the below. Note that the “icdsServer” is the name of the linux file which was placed in the EC2 instance via WinSPC. If you have changed the name for any reason, then you will need to adjust the command by replacing “icdsServer” with whatever the name of the file you added is.
6. Check there are no errors. Type: pm2 ls This will display the icdsServer as being online. If it reads errored then the process has not worked correctly and will need to troubleshot
7. If the ICDS server is online then save the current pm2 settings so it starts correctly after a server restart: pm2 save
8. Close Putty
The following is a list of useful commands which can be used in PuTTY and relate to pm2. These may be helpful if there are any issues / errors when starting the pm2 application.
1. Stop any current pm2 icds processes: pm2 stop icdsServer
2. Delete old pm2 config params: pm2 delete icdsServer
3. Kill any pm2 process which is running: pm2 kill
4. View list of pm2 running apps: pm2 ls
5. Save pm2 settings: pm2 save
6. View logs: pm2 logs
The menu bar across the top of the main Well Seeker PRO user interface allows the user access to all Well Seeker PRO functions. A lot of the functions are also duplicated in the available toolbars.
Use the navigation tree on the left to view the page for each menu.
Guides the user through the steps necessary to create an SQL server database and ICDS (Innova Central Database Server) web server via the Amazon Web Services (AWS) cloud-based platform.
The purpose of this document is to guide the user through the steps necessary to create an SQL server database and ICDS (Innova Central Database Server) web server via the Amazon Web Services (AWS) cloud-based platform. The system diagram below details how the SQL server database and ICDS Web Server fit in to the structure of data flow within Well Seeker Pro.
Before you start, to save time, there are some programs which should be downloaded and installed, as access to these will be required at various points throughout the document.
You will also require credit card details while setting up the AWS account, so have these to hand.
These programs and the relevant links are detailed below.
Download the 32-bit MSI.
During installation, select the Commander interface style.
Installation of SQL Management Studio can take a while, which is normal and expected.
In addition to installing the above programs on your computer, install the Google Authenticator App on a suitable mobile phone.
Throughout the setup process, the user will be required to enter numerous different login details and passwords. All of these will be unique to the user. The below table lists the various details the user will be required to supply, along with a blank cell, where they can keep track of these details during the process. It is recommended that this table is completed as the user follows the steps keeping all details in one place for easy reference during and after the setup has been completed.
2. Click “Create an AWS account” in the top-right corner.
3. A suitable email address should be used, and the password should be very secure.
a. Note, it is necessary to add payment details to allow Amazon to verify your identity and if the “AWS Free Tier Limits” are exceeded your card will be charged.
b. You then need to confirm your identity via phone so are asked to enter your phone number for text or voice call verification.
4. The user then needs to select the relevant plan. Smaller companies can select the basic plan, while larger companies may prefer to select the Business Plan. For the purposes of this guide the Free - Basic Plan was selected. Once selected, the user will be taken to the below right page.
5. Once an AWS account has been created, the user can then sign into the AWS Management Console.
6. As this is the first time logging in, the user must select to sign in as a Root User. The Email address and Password required here are the ones entered while creating the AWS account.
7. Once the user has signed into the AWS Management Console, click on Services at the top left of the console and go to IAM (Under Security, Identity & Compliance).
8. Click on activate MFA on your root account.
a. This takes you to the below screen, where you select Multi-Factor authentication (MFA) and then Activate MFA.
9. With Virtual MFA device selected, click continue. You will see the below window.
10. Go to your phone and open the Google Authenticator App, which you should have already installed.
11. Click on show QR code and scan this with the app on your phone.
12. Enter the 1st MFA code, wait and enter the 2nd then click assign MFA.
a. The app keeps generating codes every 30 seconds. You need to enter 2 consecutive codes. If successful, you get the below.
b. Note, with this set up, every time you try to log into the AWS management console, you will need your password, and then it will ask you to enter the MFA code. You will therefore need to open this app again and enter the code which you see every time you log in.
13. Go back to the IAM dashboard. This option is available on the top left of the screen, just above access management.
The AWS website states the following:
This section will guide the user through the steps required to set up an IAM user.
14. Click on create individual IAM users and select Manage Users. You will get the below.
15. Click Add User.
a. Enter a Username and access type.
i. Selected BOTH Programmatic Access and AWS Management Console Access.
b. With AWS Management console access selected you are then prompted for some password info. Select Custom Password, create a password and remove the Require Password reset option.
c. Take a note of your IAM Username and Password.
d. Select Next: Permissions.
16. Create a group
a. Group name must have no spaces. This opens the below right dialog.
b. Enter the Group Name and select the following policy:
i. AdministratorAccess
c. Select Create Group at the bottom right.
17. This then takes you to the below window. Make sure that the check box beside the group name is checked. Take a note of the Group Name. Select Next: Tags.
18. This then takes you to the below window. Select Next: Review.
19. This then takes you to the below window. Select Create User.
20. This then takes you to the below window. Select Close.
21. In the below, click on the username and this opens the User Summary.
a. Select the Security Credentials Tab and select Manage beside “Assigned MFA Device”.
22. Assign Virtual MFA Device. Do this for each user. This will open a similar screen like before, where you need to scan a code in the Google Authenticator App.
a. In the app, press the little white plus symbol and scan the barcode.
b. You will now have 2 sets of codes generating. One for the Root account and one for the User.
23. Once this is done, select Users at the top left of the window and you will see below where the MFA is showing as Virtual.
24. Go back to the IAM dashboard.
25. You now need to Create a password policy by selecting:
a. “Apply an IAM password policy” – “Manage Password Policy” – “Set password Policy”.
b. This is now the user’s choice, but as minimum it is suggested to select “Require at least one upper Case and one number, plus min 6 characters”.
c. Hit save changes.
26. With the above now in place, when logging into the AWS Management Console, if the user wishes to, they can select to sign in as an IAM User (instead of Root User). When selected, the user will be asked for the Account ID (12 digits) or Account Alias.
a. Enter the username and on the next page, the Account Id will be populated. Take a note of this.
b. Note: When prompted to enter the MFA code, remember to enter the code associated with the user account, and not the root account.
It is now time to create your database on the AWS. The following section will guide you through database creation steps and the relevant security rules which need to be added to allow the ICDS (Innova Central Database Server) to communicate with the database.
27. Click on Services and under Database select RDS (Relational Database Service).
28. Before you proceed, you must select the relevant region you want the Db to be created in. This option is available from the top right of the screen, to the right of your account details in the navigation bar.
29. Select - Create Database. Note, below the Create Database button, it will tell you where the Db instance will launch. Make sure this is as expected. If not, you may need to repeat the previous step.
30. Step 1: Create Database:
a. Choose Standard Create as the database creation method.
31. Step 2: Engine Options:
a. Choose Microsoft SQL server as the engine type and then SQL Server Express Edition for the edition. Notice that the express edition is eligible for the RDS free Usage tier.
b. Set the version to SQL Server 2017 14.00.3049.1.v1.
32. Step 3: Templates:
a. Select Dev/Test as the template.
33. Step 4: Settings:
a. Db Instance Identifier: Enter the name you want to use for your RDS database name.
b. Master Username: Enter a master username of your choice.
c. Master Password: Enter a master password of your choice.
d. Take a note of your chosen DB Instance Identifier, Username and Password.
34. Step 5: DB Instance Size:
a. Choose db.t2.medium (2 vCPU, 4 GiB RAM) as the DB instance class.
35. Step 6: Storage:
a. Storage Type: General Purpose (SSD).
b. Allocated Storage: 100 GiB.
c. Storage Autoscaling: Leave as the default, Enable storage autoscaling.
d. Maximum Storage Threshold: 1000 GiB.
36. Step 7: Connectivity:
a. Virtual private cloud (VPC): Choose the default VPC.
b. Click on Additional connectivity configuration to enable the following options:
c. Subnet Group: Choose the default subnet group.
d. Public Access: Choose Yes.
e. VPC Security Group: Select Create New and give it a suitable name such as “RDS Security Group.” Note - Once the DB Instance is launched you will have to wait 10-15 mins for the security group to be created.
f. Availability Zone: Choose No preference
g. Database port: Ensure that the port is changed from the default 1433 to 41433.
37. Step 7: Microsoft SQL Server Windows Authentication and Additional Configuration:
a. Leave Microsoft SQL Server Windows Authentication turned off.
b. Click on Additional Configuration to enable extra options.
38. Step 8: Database Options:
a. DB parameter group: Pick default.sqlserver-ex-14.0.
b. Option group: Pick default:sqlserver-ex-14-00.
c. Time zone: Choose your local time zone.
d. Collation: Leave blank.
39. Step 9: Backup:
a. Turn on Enable automatic backups.
b. Set the Backup retention period to 7 days.
c. Set the Backup window to No preference.
d. Turn off Copy tags to snapshots.
40. Step 10: Other Options:
a. Performance Insights: Turn off.
b. Monitoring: Turn off.
c. Log Exports: Turn off.
d. Maintenance: Turn on Enable auto minor version upgrade and set the Maintenance window to no preference.
e. Deletion protection: Turn on.
41. Select Create Database and you will get the below left screen. Below right is what you will see if you select “View DB Instance Details.”
a. Note: Depending on the region you have selected, the database can take a while to create. Sometimes over 30 mins.
42. Select Services – RDS.
43. Select Databases.
44. Click on the Db identifier for the Db that you are interested in.
45. At the top of the Connectivity and Security Tab, you will see the Endpoint and Port displayed. Take a note of these as they are required later in the setup process.
46. At the right-hand side of the Connectivity and Security Tab, you will see the VPC Security Group. Select this and then select the details tab.
a. Take a note of the Security Group Name and ID, as you will need to assign these when setting up the final security rules.
Now that the database has been created, the user must create some security rules, to allow communication between
The ICDS (located on the EC2 Instance) and the RDS database.
Well Seeker and the RDS database.
SQL Server Management Studio and the RDS database.
47. Select Services – RDS.
48. Select Databases.
49. Click on the Db identifier for the Db that you are interested in.
50. Scroll down till you see the security group rules section. There is an inbound and outbound and both need to be adjusted. This is so that there is no restriction to the computers which can connect i.e. any IP address can connect.
a. This is done so the user can test connectivity, but eventually, the IT department will need to put something in place here to make it more secure. Further details regarding this are provided in Section 15.
51. Select one of the security groups (inbound or Outbound) and the user will be taken to the below, which will open in a separate tab in the browser.
52. Select the inbound Rules Tab and edit the rules to mirror the below and select Save Rules.
a. 0.0.0.0/0 effectively means traffic from ALL IP addresses are allowed.
53. Now, select the outbound rules tab and edit this in the same way.
Now that the database has been created in AWS, the user needs to connect to it remotely, to finalise the setup. This involves using SSMS and Well Seeker Pro.
54. Open SQL Server Management studio.
a. Server Type: Database Engine.
b. Server Name: This is the Endpoint followed by a comma, followed by the Port number.
i. The Endpoint and the Port can be found in the AWS console by selecting Services – RDS and then selecting the database. It is displayed in the Connectivity and Security Tab.
c. The Login and Password for the database are the same as when the database was created in the AWS Console.
55. Right click on the databases folder and select create new database.
56. Give the database a name and select add then ok.
a. It is important to take a note of the database name, exactly as it has been entered, as this is case sensitive and will be required to access the Db via Well Seeker.
57. Once the Database has been created, close SSMS.
58. Open Well Seeker.
59. Go to File - SQL server databases - connect to remote database.
60. Enter the relevant information to connect:
a. Database IP/URL: Enter the Endpoint here.
b. Database Name: Database name as created in the previous section.
c. Port: 41433
d. DB Username: Master RDS Database Username.
e. DB Password: Master RDS Database Password.
f. WS Username: Master RDS Database Username (Must use this the first time).
g. WS Password: Master RDS Database Username (Must use this the first time).
61. Click connect
a. It is likely it will say the Db schema is out of date. Select yes to update.
b. It will say there are no admins and ask if you want to make this user an admin. Select yes.
62. On first connecting, Well Seeker will create all the relevant tables in the SQL database.
63. You can now close Well Seeker.
64. Open the server database in SQL Server management studio.
65. In the Object Explorer Tree, navigate to the tables folder under your database.
66. Scroll down till you get to the dbo.DB_SETTINGS table.
67. Right click on the table and select Edit Top 200 Rows.
68. Insert a single record in to the table: ./icdsFileDir/
a. This sets the field IMAGE_PATH for the remote Db, which is where any logos and attached files will be stored.
An EC2 instance is a virtual server in Amazon’s Elastic Compute Cloud (EC2) for running applications on the Amazon Web Services (AWS) infrastructure. AWS is a comprehensive, evolving cloud computing platform; EC2 is a service that allows business subscribers to run application programs in the computing environment. This is where the ICDS (Innova Central Database Server) will be installed.
69. Click on services and under Compute, select EC2.
70. IMPORTANT – You now need to select the region you want the instance to launch in. To do this, select the drop down in the toolbar at the top right of the screen. Select the closest region to your operations to reduce lag.
71. Click on Launch Instance – select the latest Ubuntu server – 64-bit (x86).
72. Select the Free Tier Eligible option shown below.
a. Select Review and Launch.
73. Select Edit security groups and change the name to something suitable e.g. “EC2 Security Group.”
74. Select Launch.
75. Select to Create a new key pair and enter a key pair name.
76. Download the Key Pair. This will be a .PEM file.
b. Keep this file in a safe place as it is VERY IMPORTANT.
77. Once downloaded, select Launch Instances.
78. You will now get the below.
c. An optional step here is to set up the Billing alerts to warn when the usage is approaching or exceeding the free tier.
d. Select View Instances.
Now that the EC2 instance has been created, the user must create some security rules, to allow communication between:
The ICDS (located on the EC2 Instance) and WS (data fetch and exchange).
The ICDS (located on the EC2 Instance) and the RDS database.
The EC2 and the admin’s PCs, for use of WinSCP and PuTTY software.
79. In the AWS Console, select Services – EC2.
80. Select Running Instances and select the instance that you just created.
81. Take note of the EC2 Public IPv4 Address.
82. Select the Security Tab and select the security group.
83. Take a note of the Security Group Name and ID, which can be found at the top of the screen, as you will need to assign these when setting up the final security rules.
84. Select Inbound Rules and select to Edit inbound rules. There will already be an SSH rule for port 22. Add a new rule as below, where All traffic is allowed. Select Save Rules.
a. This is done so the user can test connectivity, but the clients IT will need to put something in place here to make it more secure. Further details regarding this are provided in Section 15.
85. Open puTTYgen.
86. Select load and select the PEM file (you will have to change the file type filter to all files (*.*)
87. Click OK to the notice.
88. Click save private key, it is ok not to use a passphrase. Again, keep this file in a safe place as it is very important.
89. Close puTTYgen.
90. Open win SCP.
91. Select protocol as SFTP.
92. Enter the EC2 ipv4 address in the hostname.
93. Username is ubuntu
94. Password is blank
95. Port is 22
96. Click on advanced -> SSH -> Authentication and select the browse option to the right of the private key input cell and select the private key that was created with puTTY gen. Select OK.
97. Click login and click yes to the security notice.
98. You will now have the below, where you have created a drag and drop file explorer interface to the AWS EC2. If you do not see the Ubuntu folder on the right, its likely because you are already in it. Just select the only folder showing and it should then display the ubuntu folder.
99. Download the ICDS files via the link provided by Innova.
100. Remove the .linux extension from the icdsServer.linux file.
101. Drag this Linux executable icdsServer file to the ubuntu EC2 folder below right.
102. You will get the below left popup. Select OK and you get the below right.
103. Open the attached configICDS.json in a text editor e.g. Notepad
a) CompanyID: Type Company Name (this will be supplied by Innova and must be written in EXACTLY the same way as its supplied). Make sure Company Name is inside double quotes
b) Port: Usually enter the port field as 42000 (no quotes) – this is the port which will be entered into the Well Seeker RT Data exchange for communication with the ICDS
c) devmode: Leave as false (no quotes)
d) sqluser: Set to the SQL Server master username used to access the database. Make sure this is inside double quotes
e) sqlpass: Set to the SQL Server master password used to access the database. Make sure this is inside double quotes
f) sqlsvr: Set to the SQL Server RDS database Endpoint. Make sure this is inside double quotes.
g) sqldbname: Set to the name of the database you wish the ICDS to connect to. This is the database name that you see when logged in to SQL server Management Studio. Make sure this is inside double quotes
h) sqlport: Set to the port used to connect to the SQL server database (no quotes), usually this is 41433
i) externalPath: Specifies where external files are stored. Input either useDatabase (stores files on the EC2) or useS3 (stores files on an S3)
j) sqldbnamewits: If a user is pushing and storing WITs data to a database separate to the Well Seeker database, insert the name of the database here. Make sure this is inside double quotes. If this function is not used then leave a the doubles quotes empty
k) transferWits: If pushing WITs data to a second database then enter true, if not enter false
l) allowActivePush: If true is entered then a computer can push data back to a server database regardless of the well status. If false is entered then a computer can push data back to a server database only when the well status is Upcoming, Active or Standby. The well status is selected in the Daily Reports dialog
m) awsAccessKeyID: If storing external files on an s3, input the AWS Access Key ID of the IAM user. If not leave blank
n) awsSecretKey: : If storing external files on an s3, input the AWS secret key for the IAM user. If not leave blank
o) awsRegion: : If storing external files on an s3, input the region where the AWS service is hosted eg “us-east-2” or “us-west-2”. If not leave blank
p) s3Bucket: If storing external files on an s3, input the name of the S3 bucket which was created to store the Well Seeker external files. If not leave blank
q) Leave all other fields as they are
104. Once completed, drag the config.JSON file to the same directory as the icdsServer file
105. In the same sub directory as the icdsServer executable is located, create a directory called icdsFileDir.
a. To do this, right click under the icdsServer file and select New – Directory.
b. Your folder should now look like the below
c. This folder is where the logos and external files added to the remote database will be saved.
106. Close WinSCP. You will get the below. Selected No, so that the workspace is saved.
107. Open PuTTY
108. In the Host Name Cell: Type ubuntu@ then the EC2 ipv4 public IP we took note of earlier. Add this information to the login details section of this document.
a. Select the port as 22 and name the session in the saved sessions box.
109. Then click on Connection - SSH – Auth.
110. Click Browse and select the ppk file created earlier.
111. Click open.
112. Click Yes to the security alert message. You then get the below.
a. There are a set of commands which need to be entered into Putty. At the end of each line there is a copy button which copies the code. If you then right click on the bottom line in the putty interface, it pastes the code in for you.
b. Hit enter and then move onto the next code.
c. Your putty interface should look like the below right by the end.
114. Enter the following into the command line to install PM2: npm install pm2 -g
d. You should get the below after entering this.
e. PM2 is just a program which allows you to run a file as a service i.e. if it crashes or the computer restarts it will restart the program automatically.
115. Check pm2 is running by typing pm2 ls
f. You should get below after entering this.
116. Update node. Type the following command: nvm install 4.4.5 check version number from node.js website
c. You should get the below after entering this.
d. Node.js is a java script library for linux which is required to run the program PM2.
117. Type: sudo apt-get update
a. You should get the below after entering this.
b. At this point close and reopen putty. If you do not do this, when you get to the point where you type a pm2 command, putty will tell you it is not recognised. Not sure why this happens, but it is a consistent error. Closing and reopening puTTY allows you to proceed without any issues.
118. You now need to change the file permissions using the following “Change Mode” command: chmod 777 icdsServer
b. This makes the file readable, writable, and executable by everyone.
c. If you do not do this step, then in the next step you will likely get an errored message like the one below.
119. Now setup default instance using config file: pm2 start icdsServer
d. You should get the below.
e. Note that the “icdsServer” is the name of the linux file which was placed in the EC2 instance via WinSPC. If you have changed the name for any reason, then you will need to adjust the command by replacing “icdsServer” with whatever the name of the file you added is.
120. Enter pm2 ls again. You should see the icdsServer status as online still. If the status is errored then something is wrong with the setup
121. Save the current pm2 settings so it starts correctly after a server restart: pm2 save
The following is a list of useful commands which can be used in puTTY and relate to pm2. These may be helpful if there are any issues / errors when starting the pm2 application.
122. Stop any current pm2 icds processes: pm2 stop icdsServer
123. Delete old pm2 config params: pm2 delete icdsServer
124. Kill any pm2 process which is running: pm2 kill
125. View list of pm2 running apps: pm2 ls
126. View logs: pm2 logs
Well permissions have been put in place to give the admin control over what computers can pull what wells via the remote data fetch functionality from the SQL server database, if required. This might be the case when a company employs consultant rig personnel, who they do not want to have access to their historical well data. In order to access and setup well permissions follow the below steps:
127. Log on to the SQL server database via Well Seeker Pro
128. Once connected, select Tools > Well Permissions. This will open the Well Permissions dialog. Note that only Well Seeker users with Admin permissions can access the Well Permissions dialog
129. Well Permissions can be set to two states:
a. Enable Individual Well Permissions disabled. To select this option uncheck the Enable Individual Well Permissions check box. This allows any company computer with Well Seeker installed on and a user who has the EC2 IP address and port number details to pull any and all well data from the SQL server database via the Remote Data Fetch dialog
b. Enable Individual Well Permissions enabled. To select this option check the Enable Individual Well Permissions check box. When this is selected no computers are able to pull down well data via the Remote Data Fetch dialog, even if the user has a company computer with Well Seeker installed and the user has the EC2 IP address and port number details. Only computers entered in the table will be able to pull down a specified well or job number, when the active check box is selected.
The Computer Name for a computer can be found by right clicking on This PC and selecting Properties. Depending on the windows version the user has, the computer name will come under one of a number of different titles. These details will need to be updated on a well by well basis in order to allow the rig personnel access to the required wells
With the ICDS server now running it is important to test if this is working correctly. This can be done as follows:
130. Open the RT data exchange in WS and push an operator to the remote Db.
131. Create a new Db and then do a remote data fetch to pull in the well you have just added to the remote Db.
132. Open the RT data exchange and connect to the well you have added on the remote Db. Add some new data to the local Db and ensure that it pulls into the remote Db correctly.
133. Add a new plan to the remote Db and check to see if you receive the relevant notification in the messages window.
134. Add a couple of logos and external files to the remote database to ensure that these save correctly.
a. NOTE: For the logos and external files to work correctly, the user must have the Push External Files option selected in Well Seeker
Now that everything has been setup and tested, the final step is to adjust the security rules to make them more secure. If there is an issue connecting after this stage, you can then be sure that the issue is related to the setup of these rules and not any of the other previous steps.
Below are some recommended settings. The RDS database has communications with:
The ICDS (located on the EC2 Instance).
Well Seeker / SQL Server Management Studio.
When creating a security rule, the 2 main pieces of information required are the Port and the IP address. Set the RDS Incoming and Outgoing Security rules as detailed below:
1. Rule one:
a. Type: Custom TCP
b. Port: 41433
c. All public IP addresses that require access to the RDS via either Well Seeker or SQL Server Management Studio.
i. For larger companies who have the relevant IT structure, they may want to set an IP range for computers in their network. This is more secure.
ii. If there are just a few IP addresses to be added, the smaller companies can find each Public IP by accessing the web browser on each computer and typing “ip4.me” into the address bar at the top of the page.
iii. If a company does select an IP range, and we end up having to provide support, they may need to add our IP addresses in as a rule otherwise we will not be able to access.
iv. End the IP addresses with /32.
2. Rule Two:
a. Type: Custom TCP
b. Port: 41433
c. Security group assigned to the EC2 instance.
The EC2 instance has inbound communications from:
WS - data fetch and exchange.
RDS database.
WinSCP and PuTTY
When creating a security rule, the 2 main pieces of information required are the Port and the IP address. Set the EC2 Incoming and Outgoing Security rules as displayed below:
1. Rule One (This should already be present when you open the rules dialog):
a. Type: SSH
b. Port: 22
c. Only public IP addresses of admins who will be using WinSCP or Putty to access the EC2.
2. Rule Two:
a. Type: Custom TCP
b. Port: 42000
c. All public IP addresses to be allowed.
i. The reason to allow all public IP addresses is because it is difficult to know the relevant public IP addresses for each rig computer which is out with the company’s network. Setting a range here could mean some rig computers are unable to communicate with the ICDS.
ii. For larger companies who have the relevant IT structure, they may want to set an IP range for computers in their network. This is more secure.
iii. If a company does select an IP range, and we end up having to provide support, they may need to add our IP addresses in as a rule otherwise we will not be able to access.
3. Rule Three:
a. Type: Custom TCP
b. Port: 41433
c. Select the security group assigned to the RDS.
There may be times when a user is experiencing issues with logging in to the SQL server database via SSMS or Well Seeker, or where the external files / data push and pull functions are not working. The below sections will guide the user through some problem solving steps that will help isolate and solve the issue in question.
If the user receives an error message and cannot log in to the RDS via SSMS then follow the below steps:
1. Check the user’s computer has internet connectivity
2. Check the Server type is Database Engine
3. Check the Server name is the RDS endpoint, immediately followed by a comma, then a space and then the RDS port number, which is usually 41433. For example:
a. RDS Endpoint = exampleendpoint
b. RDS Port = 41433
c. Server name entered = exampleendpoint, 41433
4. Check the authentication type is SQL Server Authentication
5. Check the Login entered is the RDS Username the user created when setting up the RDS
6. Check the Password is the RDS password the user created when setting up the RDS
7. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 16.1 RDS for more details.
Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser
If the user receives an error message and cannot log in to the SQL server database via Well Seeker Pro then follow the below steps:
1. Check the user’s computer has internet connectivity
2. Check the Database IP / URL is the RDS endpoint
3. Check the Database Name is the name of the SQL server database as it appears when viewed in SSMS. This should not be confused with the name of the RDS when viewed in the AWS account
4. Check the Port is the port number of the RDS, usually 41433
5. Check the DB Username is the RDS Username the user created when setting up the RDS. If the user has since created an additional user in SSMS, this user name can also be used, as long as they have the clearance to access the database entered in Database Name cell
6. Check the DB Password is the RDS password the user created when setting up the RDS. If the user has since created an additional user in SSMS, this user password can also be used, as long as they have the clearance to access the database entered in Database Name cell
7. Check the WS Username is correct. Each WS username has been created in the User Permissions dialog by a user with administrator permissions.
If the administrator cannot log on to the SQL server database via Well Seeker then they can log on to the RDS via SSMS and look in the dbo.USER_PERMISSIONS table to see if the WS username exists
8. Check the WS Password is correct. If the user has forgotten their password then the admin can delete the users password from the User Permissions dialog. The next time the user logs in they will be asked to enter a new password
9. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 16.1 RDS for more details.
Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser
The Real Time Data Exchange is design to give a user the ability to push data for a specific well from their Well Seeker database, back to the SQL server database. The Remote Data Fetch is designed to give a user the ability to pull data for specific wells from the SQL server database to their Well Seeker database. In order to achieve this there are many things that have to be set up correctly
For both the Real Time Data Exchange and the Remote Data Fetch:
Correct IP and port number input in Data Exchange / Data Fetch dialog. These are the IP of the EC2 and the port number specified in the .json file on the EC2
Correct credentials entered in the .json file on the EC2. See 12.1 – ICDS files, step 103 for details
The ICDS server has to be running without error on the EC2. See 13.0 – PuTTY for details
The EC2 security settings have to be correct within the AWS account. See 16.2 EC2 for details
The RDS security settings have to be correct within the AWS account. See 16.1 RDS for details
For the Real Time Data Exchange only:
Correct well selected in the Data Exchange dialog. This well must already exist on the server data base
If the .json file on the EC2 has allowActivePush as false then a computer can push data back to a server database regardless of the well status. If true is entered then a computer can push data back to a server database only when the well status is Upcoming, Active or Standby. The well status is selected in the Daily Reports dialog. See 12.1 – ICDS files, step 103 for details
For the Remote Data Fetch only:
If the Well Permissions dialog on the SQL server database has Enable Individual Well Permissions selected, then only wells included in the Well Permissions table will be able to fetch specific wells. In the case that the user does not have permission to download well data, the user will be able to connect to the SQL server database and see the database tree, but there will be no structures below facility level to select, as below.
See 14.0 – Well Permissions for details
External files for the SQL server database are stored on the EC2 and rely upon a similar data transmission method as the real time data exchange and remote data fetch functions. If you are experiencing issues saving or accessing external files and logos, either from the SQL server database, or when the data has been pulled down to a local database, follow the below steps:
1. Ensure the real time data exchange and remote data fetch functions are working correctly. See 16.3 – Real Time Data Exchange / Remote Data Fetch for details. If they are then it rules out a number of potential causes for the issue. If both these functions are working, but you are still experiencing issues with the external files functions then proceed to the next step
2. Ensure that during the database creation the step was followed that created the external files image path in the dbo.DB_SETTINGS table. See 14.0 – Well Permissions, step 68 for details
3. Ensure that the option Push External Files is selected on all computers trying to use the functionality
Well Seeker Pro can be downloaded from the Innova Drilling & Intervention website in an unzipped format. However, if Well Seeker Pro is supplied via email, it will be attached as a zipped installation file, which must be unzipped before use. Right click on the file and select “Extract All….” From the context menu.
Select a location which you wish to extract the files to and click “Extract”. The installation files will be extracted to the selected location in a folder called “Well Seeker PRO”.
Once the Installation file has been extracted, open the Well Seeker PRO folder and double click on the “Well Seeker PRO vx.x.x.xxx.exe” file to begin the installation process.
The next screen will allow you to select the location in which you wish to install Well Seeker PRO. The default location is “C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO”. If you wish to change the location the program is installed to click on the “…” button. Before continuing you must tick the “I agree to the License terms and conditions” checkbox. You can read the License terms and conditions by clicking on the blue highlighted text (See Figure 4 below). One you are ready click the “INSTALL” button to begin the installation.
At this point, you may be asked “Do you want to allow this app to make changes to your device?”. Click “Yes” to continue the installation.
During the installation process, the Well Seeker PRO installer may also install one or more pieces of prerequisite software. If this happens follow the instructions in the setup wizard for each software. Once all prerequisite software has been installed the Well Seeker PRO installtion will resume. All prerequisite software is created by Microsoft and poses no risk to your computer. Some software may require you to restart your computer. In this case, allow the Well Seeker PRO to finish and then restart your computer before running Well Seeker PRO for the first time.
With the installation complete Well Seeker Pro will display the message “Well Seeker PRO has been successfully installed.” Click on the “Finish” button to close the installer.
Once the installation is complete an icon will have been added to the desktop and an entry for “Well Seeker PRO” will be in the start menu.
The Well Seeker PRO user interface is split into four main sections. All sections of the user interface can be dragged and resized, so the user can customize how the interface looks.
The properties window allows the user to quickly see common properties for the currently selected tree item and all parent items. It also displays the current unit set information.
The Well Seeker PRO status bar located at the bottom of the main user interface also provides the user with information as to the programs current operation, unit sets and location of the Database currently selected.
On the right-hand side of the status bar the status and current activity of the Real Time Data Exchange is displayed. See Section 6.4.15 – Real Time Data Exchange for more information on the Real Time Data Exchange.
Well Seeker Pro comes pre-installed with three toolbars which are displayed at the top of the main user interface.
The Well Seeker Toolbar contains the main functions of Well Seeker
The Reporting Toolbar contains functions relating to the Drill String and Daily Reporting editors.
The Field Toolbar contains functions that Directional Drillers commonly use during drilling operations.
The following table contains a list of all the icons available across the 3 toolbars.
It is possible to hide or display the toolbars based on the user’s personal preference. The selection made is remembered by Well Seeker and the selected toolbars will be displayed each time the software is opened. For more information regarding this see section 6.3 – View Menu.
When first installed, the toolbar contains all the available options, which for some users may be too many buttons. It is possible to remove any unwanted icons by holding down the ALT key and then left-clicking the mouse key on the desired icon and dragging it away from the toolbar. Releasing the mouse key will then cause the icon to disappear.
If an icon is removed by mistake, or if the user decides to add in previously removed icons, this can be achieved as follows
Open the View menu from the Menu Bar and select the Toolbars and Docking Windows menu item.
Select the Customize menu item to open the Customize dialog. Select the Commands tab.
The user can then search for the desired icon by selecting the various categories on the left-hand side of the dialog. The icons relating to the selected category will be displayed in the Commands box on the right-hand side of the dialog.
Once the desired icon has been identified, it can be added to the toolbar by dragging and dropping it onto the toolbar.
The toolbar can be reset back to its default setting, as per first install as follows:
Open the View menu from the Menu Bar and select the Toolbars and Docking Windows menu item.
Select the Customize menu item to open the Customize dialog. Select the Toolbars tab.
Select your desired toolbar and click on the Reset button. Alternatively click on the Reset All button to reset all the toolbars.
As of version 2.0.6.12, Well Seeker Pro now contains the Tool Orders functionality. Tool Orders is a licensed feature that is designed to give an organization the means by which to create, update and maintain oversight of all the tool requirements for upcoming and existing jobs. The Tool Orders will be managed from the server database, but local database users at the rig site can also create tool orders and push these back to the server for approval, should the requirement for more tools occur during an ongoing job.
The way in which Tool Orders can be accessed and used differs between the server and local database. The remainder of the document will guide the user through the specifics of the setup on the server and any subsequent utilization from a local database.
The below steps assume that the user already has a Well Seeker Pro SQL server database:
1. Log on to the SQL server database
2. Select Tools > Dashboards > Tool Orders Dashboard
4. Input details for each of the tool order detail types in the Select menu option dropdown list. This will form the basis of what tool configurations the user can specifically ask for when using the Tool Orders dialog. This can be edited at a later date if required. When the user has filled in all of the relevant options, select Apply and then close the dialog.
6. Fill in the relevant details in the Tool Orders table:
If the tool order is for a job that has no daily reporting data yet, i.e. an upcoming job, then the user would input the Operator, Job # and Well information and leave the Hole Size, State, County, Rig, Mud Type, Mud Weight, Min Temp and Max Temp inputs blank.
If the tool order is for an existing job which has daily reporting data input within the database, the user would enter the Job # only and the rest of the cells will populate based upon the daily reporting data.
Update the Date Needed cell. This defaults to the date the tool order was created.
Input any additional information in the remaining cells.
7. Fill in the relevant details in the Order Details table. Some cells will be manually input, others will be selectable from the dropdown menu, the choices of which the user has set up previously. More than one row for multiple tools may be input in this section.
8. The Tool Order has been completed. By default the tool order status is Draft. This should be changed to Submitted when the details are finalized. The status can be updated sequentially as the tool order is In Progress, Shipped and Complete.
9. At any stage a tool order can be printed or attached to an email. Firstly select the tool order from the Tool Order table. In the Order Details table, check the Print cell for any row that you wish to be included in the printed report.
11. A tool orders status can be updated from the Status dropdown menu as the tool order progresses through its work cycle.
The below steps assume that the user already has a Well Seeker Pro local database, populated with an actual wellbore:
3. When the dialog opens it checks the IP and Port values entered in the Real Time Data Exchange dialog. If these are correct, then the dropdown menu options for the Order Details cells will be populated from the information on the server database.
4. Create the tool order and order details as you would on the server database. Any tool orders created on the local database will automatically be given the status of Request from rig.
Note: To perform the steps in this guide, you must be logged into the Web Portal as a user that has Admin permission and access to the User Management feature. To check your available features and permissions, click on the icon in the top right of any page and select Profile.
Click on the icon in the top left to open the main menu.
Click on the icon to the left of the new role and select Operator Access.
Click on the icon to the left of the new role again and select Products & Features.
Click on the icon in the top left of the page to open the main menu.
Click on the icon in the top left to open the main menu.
In the Users page click on the icon to the left of the user, and select Operator Access.
In the Users page, click on the icon to the left of the user, and select Well Access.
Click on the icon in the top left to open the main menu.
If the user is successfully added, a row will be added to the table displaying their username and their source organisation to the page. Click on the icon to expand the user, displaying the organisation(s) that they have access to.
Delete: Clicking on the dustbin icon will revoke the user’s access to the organization.
For other pages, they can switch between their organization and yours by clicking on the icon in the top right of every page.
Login to the using valid login credentials
Scroll to the desired BHA and tap the BHA Images icon beside its name. If there are no BHA’s here, then one must be added before you can proceed to the next step. The BHA must also include a bit.
Upload individual images from your phone gallery by tapping the icon.
Tap the button at the bottom of the dialog to upload multiple pictures at once from your phone gallery.
Tap the icon to upload an image using your phone camera.
Images can be deleted by tapping the icon beside each image.
The button at the bottom will delete all images.
Tap the icon beside each image to identify the picture as a drill bit.
Once a minimum of 4 pictures have been identified as drill bits, tap the button at the bottom of the dialog to run the ZerdaLab bit grading feature.
Follow this link for a guide:
Follow this link for a guide:
Input the desired threshold values. See following video guide for an explanation of rig state thresholds:
1. Go to the Microsoft Azure Portal home page at .
If the Auth Type column displays a icon or a icon, then your organization’s user credentials are managed using Azure AD or Okta, respectively. In this case, the password and MFA management functions in the Innova Portal will have no effect.
If the Auth Type column displays a icon, then user credentials are managed in the Innova Portal and the admin will be able to use the below functions to control the user’s MFA status:
Reset MFA Device: Click on the icon to the left of the User Name column and then select Reset MFA device from the menu that appears. Once selected a second dialog will open requiring user confirmation of this action. Select YES to continue, or NO to cancel the process. Once reset, the user will need to setup a new authenticator the next time they login to the Portal, app or Well Seeker.
2. Go to
78. Follow the instructions on the following link to install node on the virtual machine:
The Input Parameters and Input Tables can be hidden by clicking on the to the top right of each section. This provides more space to view the results charts.
A new case can be created by clicking on the icon, or deleted by clicking on the icon. If the user has created multiple cases, double left clicking on the case name will display the list for the user to choose from. Click on the icon to rename the selected case. After a case has been created / selected, the other inputs can be entered.
BHA: Select the drill string that will be used for this case. BHA’s created in the Drill String page for the well will be available here. Once selected, the components for the drill string will populate the Drill String table in the Input Tables section. A new blank string can be created by clicking on the icon, or deleted by clicking on the icon. Click on the icon to rename the selected string. Double left clicking on the BHA name provides a list of available BHA’s for the user to choose from.
Wellbore: This section is where the user can create and select the casing and open hole details that make up the wellbore. A new wellbore can be created by clicking on the icon, or deleted by clicking on the icon. Click on the icon to rename the currently loaded wellbore. Once a wellbore has been created, the details that define the Wellbore e.g. Comp type, OD and ID, are entered in the Input Tables section.
Clicking on the icon beside Select Case or BHA allows the user to copy an existing case or BHA from another well into the currently selected well.
The dialog will display wells that have engineering cases/BHAs set up. Click on the to expand each operator and well, or use the search bar at the top of the dialog. Select the desired case/BHA by clicking in the check box to the left of each one, and then select Import.
Enter new rows into a table by filling in the information for the new row in the area at the bottom of the page, next to the symbol. When all of the information for the new row is entered, it will automatically be added to the table.
Rows in each table can be deleted by clicking on the symbol.
Click on the icon beside each component to display its component properties. The Engineering Dashboard only displays component properties that are relevant to the Engineering Dashboard calculations. To access any properties relevant to daily reporting, the user should go to the drill string section of the portal.
To do so, hover over the icon at the bottom right of each results chart to reveal the Chart Controls menu. Then select the Calculate function to model the case and populate the results charts. If any changes are made to the inputs, the calculate button will need to be clicked again to re-run the calculations.
Hover over the icon at the bottom right of each results chart to reveal the Chart Controls menu.
Calculate: After entering input data, the user must click on this option to run the calculations. This will populate the results charts. If any changes are made to the inputs, the calculate button will need to be clicked again to re-run the case.
Refresh Drilling Parameters: This is used in conjunction with the Show Slide Sheet Parameters and Show WITS Data options. If any Slide Sheet or WITS data associated with the current well is updated, the user will need to click the Refresh Drilling Parameters button to update the charts.
Casing Symbols: Adds lines to represent the casing shoe depths on the charts. These depths are taken from the Wellbore input table.
Show Legend: Toggles the display of the chart legend to the right of each chart.
Shade Buckling: Only available in the Drillers Hook Loads chart or the On/Off Bottom Tension Snapshot charts. This will shade the area to the left of the buckling lines on these charts
Shade Limits: Only available when viewing the Kick Tolerance chart. This will apply a block of colour to the areas covered by each kick tolerance limit. These limits are defined in the Kick Tolerance Limits input table.
Show Slide Sheet Parameters: Toggle on to display drilling parameter data recorded in the Slide Sheet page on the chart. If the data in the Slide Sheet page is updated, the charts must be refreshed by clicking on the Refresh Drilling Parameters button beside the Calculate button.
Show WITS Data: Toggle on display WITS data on the chart. Requires WITS data for the well to be stored in the Data Acquisition section. If the stored WITS data is updated, the charts must be refreshed by clicking on the Refresh Drilling Parameters button beside the Calculate button.
Select BHAs: Only relevant if Show Slide Sheet Parameters is toggled on. Allows the user to choose which BHA(s) have their slide sheet data displayed on the chart. The user can toggle on multiple BHAs at the same time.
Select WITS Depth Range: Only relevant if Show WITS Data is toggled on. Allows the user to restrict the WITS data to only be displayed in the selected measured depth range.
PDF Settings: Opens the PDF Print Settings dialog. This dialog allows the user to customize which results are printed when they print one of the full PDF format reports using the PDF option.
Export XLSX: Exports the data points used to plot the currently opened results chart to an Excel format file.
Export PDF: Prints a full results report in PDF format. There are four reports available – Hydraulics, Torque and Drag, Well Control and BHA Analysis. The chart that the user currently has open dictates which report is printed. For example, if you are viewing a Pump Pressure chart then it will print a Hydraulics report. Each report will contain all relevant inputs for that section. The results that are printed can be customized using the PDF Print Settings option.
Go to and log in to your account.
7. Take a note of the Client ID, Client Secret and Domain. The Client ID and Client Secret can be copied to clipboard by clicking on the symbol to the right of each item. The Domain is your sign-in URL that you used to log in (e.g., mycompany.okta.com). Provide these three pieces of information to Innova.
1. Go to
“We strongly recommend that you do not use the root user for your everyday tasks, even the administrative ones. Instead, adhere to the . Then securely lock away the root user credentials and use them to perform only a few account and service management tasks.”
113. Follow the instructions on the following link to install node on the EC2 instance:
3. The Tool Orders dialog will open. Prior to the first use of the Tool Orders it is recommended that the user input all the of the available tool order options that users will be able to select when creating a tool order in future. Select either Tools > Edit drop down menus or the icon from the toolbar.
5. To add a new Tool Order select Tools > Create new tool order or select the icon from the toolbar. This will create a new row in the Tool Orders table.
10. Any tool orders with the status of Request from rig are a tool order that has been pushed from a local database to the server database. A user on the server can the approve this request for tools by selecting the tool order in question and selecting Tools > Approve order, or select the icon on the toolbar. This will change the status from Request from rig to Submitted.
1. Select the actual wellbore that the user requires and open the Tool Inventory, by selecting either the icon from the toolbar, or right clicking on the actual wellbore in question and selecting Reporting > Tool Inventory.
2. In the Tool Inventory dialog select the icon. This will open the Tool Orders dialog.
5. To send this tool order request back to the server database, select the icon, or select Tools > Send order to server. The tool order can then be approved by the administrators from the server database and acted upon.
This menu is only available if a survey or plan is open in the Survey / Chart viewer area. It is also available by right clicking anywhere in the Survey / Chart Viewer when a survey or plan is selected.
Undo: Reverses the last action that you performed in the Survey / Chart viewer.
Redo: Reverses the last Undo action that was performed in the Survey / Chart viewer.
Copy: Copy the selected grid rows to the clip board.
Paste: Paste survey data from the clip board to the grid. Only MD INC and AZI data will be pasted; all other data will be discarded.
Delete: Delete the currently selected row if a full row is selected or delete the contents of the currently selected cell / cells.
Insert Row: Insert a row below the current selection.
The plots menu allows the user to bring up a plot for the currently selected plan / survey.
Plan View – Top down plot showing a bird’s eye view of the well / wells
Section View – A slice at the reference well’s vertical section azimuth
3D View – A 3D representation of all wells
Travelling Cylinder Plot – A specialised polar plot used for anti-collision; requires at least one offset well to be selected.
Separation Factor – Shows separation factor vs measured depth; requires at least one offset well to be selected.
Ladder Plot – Shows the centre-to-centre distance vs measured depth; requires at least one offset well to be selected.
Spider Plot – Similar to a plan view except “TVD slices” can be produced whereby only the current well bore sections which have a TVD greater than or equal to the current value are displayed. This plot is used to help with anti-collision. Using the “+” and “-“ keys changes the current TVD slice. This can also be done from the chart properties menu.
Azimuth Comparison – Show azimuth vs measured depth.
Inclination Comparison – – Show inclination vs measured depth.
Dogleg Comparison - – Show dogleg vs measured depth.
Turn On Error Ellipses– Turns On / Off the error ellipses in whichever chart is currently displayed.
Chart Properties– Brings up the chart properties dialog which allows the user to customize chart settings. See section 6.7 - Chart Properties for more details
Screen Reader – Allows the user to turn the screen reader on and off. The screen reader is not available in 3D plots.
The screen reader will display the co-ordinates of the current mouse position in the top left-hand corner of the chart. If the user clicks on the chart area, a red line will be drawn from the point which was clicked to the current mouse position. The distance between the current mouse position and the point at which the mouse was clicked will be displayed in the distance box of the screen reader, as will the angle (azimuth) between the 2 points. Turning the screen reader off will remove the red measuring line.
Reset Zoom – Reset the chart view to default zoom levels
Chart Defaults – Allows the user to select from a range of default chart options
Default Chart Style – Allows the user to change the default style for all chart types
Default Grid options – Allows the user to set up the default options for the chart grids, such as grid lines, tick marks and grid line styles.
Default Series Style – Allows the user to set the default line style for the chart series.
Default Border Style – The default style for the chart border.
Default Minor Grid Line Colour – Default Colour for Minor gridlines.
Default Major Grid Line Colour – Default Colour for Major gridlines.
Show Offsets On Open – Toggles whether offsets are shown by default when a chart is created.
Show Targets On Open – Toggles whether targets are shown by default when a chart is created.
Tick Marks - Sets the default scale of major and minor ticks on the x- and y-axis.
Show Casing On Open – Toggles whether casing symbols are shown by default when a chart is created.
Casing Symbol – Allows the user to select whether to display the Casing Symbols as casing symbols or Dots.
Chart Font Sizes – Allows the user to set the default font size value for various chart elements:
Default Chart Label Size – The default size of chart labels. This affects all labels within the charts including but not limited to the well name, target name, casing name, annotations etc.
Default Grid Number Size – The default size of grid number and axis number sizes.
Default Axis Label Size – The default size for axis titles.
Default Font Size - Default size for all chart fonts, including axis labels and title.
Show Legend – Allows the user to select the position of the legend on the chart. Default setting is hidden.
Geo Steering Zone Settings – Allows the user to set the colours for the Target, Top Target and Bottom Target geo steering zones, which can be represented on the Section and 3D plots. User can also select a check box to use these options as default.
Tolerance Circle Settings – Allows the user to set the colour and line style for Inner and Outer Tolerance Circles. User can also select a check box to use these options as default.
3D Plot Defaults – Allows the user to set the default options for various 3D chart elements.
3D Plot Centre at Top of Well – When user selects centre on survey in the 3D plot the plot will centre on the top of the well when this option is checked, or at the bottom of the well when this option is unchecked.
Survey Spheres – Select the default size of the Survey Spheres
Fly Down Well Spheres Select the default size of the Fly Down Well Spheres.
Line Thickness – Select the default line thickness. 0.1 - 0.2 is recommended.
Work Sight Settings – User selects the default settings for the work sight in the 3D plot.
Show Rig – Select whether a rig graphic is displayed above the wellhead of the reference well or not by default.
Show Critical Point Targets – Displays plan critical points with a target radius disc by default.
Critical Point Target Radius – User sets the default radius of the critical point target disc.
Show Lease Line Curtain – Select whether to display a lease line as a vertical curtain or a line by default.
Projection Settings – Allows the user to set the colour for Bit projections. User can also select a check box to use these options as default.
Lease / Hard Line Settings – Allows the user to select the colour and line style of lease and hard lines. User can also select a check box to use these options as default.
Show Lithology Lines on Open – Shows Lithology Lines on the Section view and 3D plot when they are first opened. Default is OFF.
Show Principal Plan on SF Plot – Allows the user to select whether to show the Principal plan associated with a survey when in the Separation Factor plot. Default is OFF. This means that when in a survey, if the principal plan is selected as one of the offsets, it will not be displayed on the SF plot. It will display on all other plots.
Show axis scales – Toggles axis scales on/off by default.
Show Plan Points On Open – Allows the user to Toggles the plan points on or off as a default.
Show Well Names – Toggles whether well names are shown by default when a chart is opened.
Show Tether Lines - Toggles whether tether lines are shown by default when a chart is opened.
Only Show Principal Plan – If this option is toggled on, plots will not display any wells other than the reference well and the principal plan for that well, if one has been assigned.
Survey Line Colours – The default colour surveys will be displayed with on charts.
Actual Line Colours – The default colour Actual Wellbores will be displayed with on charts.
Plan Line Colours – The default colour plans will be displayed with on charts.
Principal Plan Line Colours – The default colour principal plans will be displayed with on charts.
X and Z Plane Colour – The default colour of the X and Z plane colours of the 3d chart
Y Plane Colour - The default colour of the Y plane colours of the 3d chart.
The reports menu allows access to the Report Manager, where PDF and Excel reports can be generated. It will only be available if the user is currently viewing a survey, plan or plot in the main user interface.
When special character sets are being entered into the program e.g. Cyrillic characters for well names etc, the user can select the relevant character set from here, which will allow these characters to be used when generating reports.
The user should select their desired report type – Error Ellipse, Anti-Collision or Survey. This will open the Report Manager where they can configure their report.
Note: Well Seeker will remember the settings from the last report printed, with the exception of the following settings: Include Details, SF Plot, Ladder Plot, Whole Path and Save Report. Reports will display the logos selected in the Operator Properties for the well in the Database Tree.
At the top of the Report Manager window is the Select Report Type section. Here the user should select one of the pre-set templates and then customize them to their liking using the options in the lower section. The user can use the drop down box in the bottom right of this section to switch between the three report types. The report type defines the options available in the Report Columns and the Report Options sections.
The user can create a new report template by clicking on the New Survey Report, New AC Report or New Error Report buttons, depending on the report type they need. Templates can be deleted by clicking on the Delete button. After configuring the report in the report manager, the settings can be saved to the currently selected template by clicking on the Apply button.
The Output section allows the user to choose the format of their report. The available formats are PDF, Excel 2003 or 2007, and tab delimited text file. The Font Size option allows the user to set the size of text in the results table, but only in PDF format reports.
The Report Columns table allows the user to select the columns displayed in the main results table of each report. Columns can be turned on or off by clicking the Enabled check box. Columns can be re-arranged using the Move Up and Move Down buttons. The Report Options table allows the user to enable or disable other features of the report.
The available options in these tables depends on the type of report selected - Error Ellipse, Anti-Collision or Survey. See the sections below for details on each report type.
The Interpolate section allows the user to apply some interpolation to their survey or plan listing. The AC Reports Plots section allows the user to add two relevant plots to their AC report.
Interval: When this option is toggled on, instead of listing the survey/plan stations the report will show an interpolated listing. The interval sets the distance in MD between each interpolated station.
Depth From/To: Allows the user to only display stations within a specific depth range in the report. This can be used without interpolation.
Include Final Station: The final survey/plan station will be included in the interpolated listing.
Include Stations: All survey/plan stations will be included in the interpolated listing.
Whole Path: If the well/survey being printed does not start from surface – for example it is a survey tied on to a shallower section, or it is a sidetrack – then toggling this option will add the sections above it to the report, all the way up to surface.
Only Interpolate Plans: If the trajectory being printed is made up of both a plan and actual surveys, then the user can toggle this option so that the interpolation settings only apply to the plan. The actual surveys will display normally with no interpolation.
SF Plot/Ladder Plot: The options allow the user to add a Separation Factor and Ladder plot to the end of their report. These are only available in an Anti-Collision report, and the well/plan being printed must have offsets assigned.
The sections in the bottom right of the Reports Manager give the user some additional options for formatting and printing their reports.
Colours: The Background and Inset Background options allow the user to set the colour scheme of PDF format reports. The Excel Report option sets the colour scheme of Excel format reports. The Defaults button will reset the colour schemes back to the defaults displayed above.
Page Setup: Allows the user to choose between portrait or landscape orientation when creating PDF or Excel format reports.
Include Details: Toggling this on will display the company details on the front page of the PDF format report. The company details can be edited by opening the Help menu in the main interface and selecting Company Details.
Save Report: Toggling this on will prompt the user to save the report to a file location. If this option is not selected, the report will be generated and previewed but not saved when the Create button is pressed. The report can be saved by clicking the save button in either the PDF viewer or Excel depending on which report type is generated.
Create: After setting up their report, the user should click on the Create button to print it.
Cancel: Close the Report Manager.
Batch Print: Opens the Batch Print window. This feature allows the user to save multiple reports at once. All reports will use the options selected in the Report Manager.
The user should select the wells they want to print from the database tree. The type of wells/plans displayed in the tree can be changed using the Filters section. The user should select a location to save the reports using the Select Folder box. When the Print button is clicked, a report for each selected well/plan will be created and saved.
Error Ellipse report column options include: MD, Inc, Azi, Mag H, Bias H, Mag L, Bias L, Mag V, Bias V, Mag Bias, Semi Major, Semi Minor, Azi, Survey Tool.
It should be noted that Well Seeker will only generate an AC Report if the user has at least one offset well selected. If no offset wells are selected, then the user will receive a warning.
AC Report column options include: Ref MD, Ref TVD, Off MD, Off TVD, Ref Semi Maj, Off Semi Maj, TFO, Off NS, Off EW, Ref OD, Off OD, C2C, Ellipse Separation, Min Separation, Bias, SF, Warnings.
When creating an anti-collision report the SF Plot and Ladder Plot options at the bottom of the report manager become available. These options allow the user to add a Separation Factor plot and a Ladder Plot to the report.
Survey Report column options include: MD, Inc, Azi, TVD, NS, EW, VS, DLS, BR, TR, TFO, CL, TVDSS, Grid N, Grid E, LAT, LONG, Closure Azi, Up Down, Left Right, Dist.
The view menu allows the user to customize how the Well Seeker PRO interface looks and which elements to display.
Toolbars and Docking Windows: This menu allows the user to show or hide various elements of the Well Seeker PRO main user interface. If there is a tick next to the item, it means it is currently being displayed. If an element has been closed it can be re-opened from this menu. The customize option displays a dialog which allows the user to customize the look and feel of the overall interface.
Decimal Places: Allows the user to select the number of decimal places the plan and surveys are referenced to. User can select between 1 and 10 decimal places.
Font Size: This option relates to the size of the font in the Survey / Chart window. The user can choose between Small, Medium, Large and Extra Large.
Lat Long Display Options: This option allows the user to select how latitude and longitude are displayed in the Survey Viewer. The user can select either Degrees, Minutes and Seconds or Decimal Degrees. Any active surveys must be closed and re-opened before the change can come into effect.
Survey Column Show Hide: This option is only available if a plan or survey is open in the Survey / Chart viewer area. This allows the user to customize the columns which appear in the survey / plan grids. Click on the checkmark in the Visible column to toggle that column on/off when viewing a survey or a plan. Click ‘Apply’ to save changes and ‘Cancel’ to exit without saving changes.
The “Method” and “Target” columns are only applicable when in a plan.
The “TC X” “TC Y” “TFO Highside” “TFO + Azi”, “Distance to Plan”, “Up Down”, “Left Right”, “Closure Azimuth” & “BR to Land” columns are only available when in a survey.
Use Direct 3D: Toggles whether Well Seeker uses DirectX drivers to render 3D charts and effects. If the user is experiencing issues while viewing 3D charts, toggling this option off may resolve them. However, display quality and functionality are reduced in 3D charts when Direct 3D is toggled off.
Color Palette Selection: Sets the color palette for some charts, such as the KPI charts produced in Daily Reporting or Well Analytics.
PDF Report Font Size: Changes the font size for PDF format reports. Default size is 12.
The tools menu allows the user access to various Well Seeker PRO functions, some of which are only accessible when a survey or plan view is visible. Additionally, some functions are only accessible when logged into a remote database.
The unit sets dialog can be accessed either from the “Tools -> Unit Sets” menu or by the unit sets icon on the main tool bar. The currently loaded unit set is displayed in the status bar as well as in the properties window.
The unit set defines the units which Well Seeker PRO uses to display data. US Feet is the default unit set when Well Seeker is first installed. A unit set is a specifically formatted text file which is stored in the Well Seeker PRO install directory under the unit sets folder. Unit set files can be copied from computer to computer and if they are placed in the unit sets folder will become visible to Well Seeker PRO. By default, Well Seeker PRO comes with four unit set files: API, SI, ND, US and Canadian. When a unit set is selected, it applies to the entire database.
A unit sets file contains fifteen parameters. The first 6 parameters directly relate to the planning, survey and anti-collision portions of the program. The rest of the parameters all relate to the daily reporting and engineering sections:
Depth: Current units for measured depth and TVD. Options are Feet, US Feet and Meters.
Local: Current units for NS, EW and centre to centre distances. Options are Feet, US Feet and Meters.
Geographic: Defines what units the map co-ordinates are displayed in. Options are CRS Default (the unit set defined by the selected CRS), Feet, US Feet and Meters.
Diameter: This defines the units used to display Casing OD and ID as well as hole size. Options are mm and inches.
Dogleg: The current units DLS, BR and TR are displayed in. Options are Deg/100ft (or 30m), Deg/30ft (or 10m) or user defined. If user defined is selected, the parameter column becomes active and the units value becomes degrees per unit length based on the parameter entered.
Survey Calculation Method: This defines which calculation method is used for calculating survey parameters throughout Well Seeker PRO. Options are Minimum Curvature, Radius of Curvature, Tangential and Balanced Tangential. It should be noted that if a method other than minimum curvature is selected the Well Planning tools will not work.
Flow Rate: Current units for flow rate. User can choose between LPM and GPM.
Pressure: Current units for Pressure. User can choose between Bar and psi
Volume: Current units for Volume. User can choose between BBLS and m3
Mud: Current units for Mud Weight. User can choose between PPG, SG, psi/ft3 and lbs/ft3
Weight: Current units for Weight. User can choose between klbs and Tons
Torque: Current units for Torque. User can choose between kftlb and kNm
Temperature: Current units for Temperature. User can choose between degC and degF.
Cost: Current units for Cost. User can choose between $, EUR and GBP.
Jets: Current units for Jet size. User can choose between in2 and mm2.
A new unit set file can be created by clicking the “create new” button and can be edited by clicking the “Edit” button. To save changes, including changing the unit set currently selected, click the “Apply” button.
The geo mag calculator is a standalone tool that performs the following functions:
Convert latitude and longitude to map co-ordinates and vice versa.
Calculate and print magnetic data based on the co-ordinates entered.
Set the default magnetic model used in Ellipse of Uncertainty (EOU) calculations.
Convert between NAD83 and NAD27 co-ordinates.
In order to use the Geomagnetic Calculator a co-ordinate reference system (CRS), also known as a mapping grid, must be selected from the drop-down menu at the top of the dialog. The “Scale factor” box will then display the scale factor of the selected CRS. Clicking on the Mapping Grid button will open the CRS Editor. See section 8.3.1 – CRS Editor.
Co-ordinates can be entered either as a latitude & longitude or as a map co-ordinate. This is defined by selecting the “Grid North / East” or “Lat / Long” radio button. The grid convergence is displayed in the edit box marked “grid convergence”. This value will be applied when converting between grid north and true north.
Once a CRS has been selected and co-ordinates have been entered, the user can display the location on a map using the Show Map button. Note that this map is generated using Google Maps, which will likely not be using the same CRS as the one selected by the user. This means that the location plotted on the map will not be completely accurate.
Magnetics data can be calculated for the co-ordinates entered by selecting a date and entering an altitude in the “location data” section.
It should be noted that the date selected must be within range of the geo-magnetic model selected or an error will be displayed.
To select the geomagnetic model, open the drop-down menu next to the model edit box and all the models which are currently in the install directory “Magnetics” folder will be displayed.
Well Seeker PRO comes as standard with the IGRF and WMM magnetic models, however it also supports HDGM, BGGM and mvHD magnetic models. To use BGGM, copy the BGGMXXXX.dat file into the magnetics directory and make sure there is a copy of bggm32_v3_8.dll in the magnetics directory. For HDGM models simply paste the hdgmxxxx.dll into the magnetics directory.
If the Geo Mag converter dialog is open and a new model is added to the magnetics folder, the dialog will have to be closed and reopened before Well Seeker PRO can see it.
It should be noted that world magnetic model .COF files must start with “WMM” as the first three letters of the filename, IGRF files must start with “IGRF”, BGGM must start with “BGG” and HDGM must start with “HDGM”.
Once the date and model have been selected, the magnetic data will be displayed. The user can export their magnetic data to either PDF or Excel format using the Print button. The Set as Default button will set the selected magnetic model as the default model when creating a new Actual or Planned Well.
The NAD83 / NAD27 Conversion section can be used to convert map co-ordinates & latitude/longitudes plotted on a NAD83 Datum CRS to their equivalent in a NAD27 Datum CRS, and vice versa. Note: An internet connection is required for this function to work.
To perform a conversion, the user should select a CRS in the Projection details that uses a NAD83 or NAD27 Datum. Then enter their co-ordinates into the Location data section and click on the Convert button. The converted nothing, easting, latitude, and longitude results will then be displayed in the results boxes. If there is an error with the conversion, then a message will be displayed in the “Errors” box.
The survey tool editor is used to create, view and edit Well Seeker PRO .ipm (Instrument Performance Model) files, which are used to calculate Ellipse of Uncertainty (EOU).
The available IPMs are listed on the left of the window and can be filtered using the Search box at the top of the list. The default IPM is highlighted in green. Clicking on an IPM in the list will select it and display its error terms in the main window.
IPMs can be manipulated using the toolbar at the top of the window:
Save IPM: Saves any changes made to the currently selected IPM.
Add new IPM: Creates a new blank IPM.
Delete IPM: Deletes the currently selected IPM.
Edit IPM: Allows the currently selected IPM to be edited. Any changes made should be saved using the Save IPM option.
Open IPM folder: Opens the IPM folder on the user’s computer where the .ipm files are stored. Error models can be added to Well Seeker PRO by putting the .ipm file in to the IPM folder in the Well Seeker PRO install directory. Anything in the file with a # preceding it will be ignored by Well Seeker PRO.
Select IPM: Only available if the Survey Tool Editor is accessed from the plan properties dialog of a Well Plan, or the Survey Properties dialog of a survey. Clicking on this option will set the currently selected IPM as the error model for the plan.
When an IPM is selected its error terms are displayed in the main window. Well Seeker PRO uses the ISCWSA mathematical framework for all EOU calculations, and each line in the .ipm file contains a coefficient which has 8 properties.
Name: The name used to identify the coefficient, it should be noted that as per the ISCWSA framework, certain error terms are singular in vertical hole. Well Seeker PRO accounts for these terms, however they must be named correctly in order for it to do this. The terms which are singular should be named as follows: abx, abix, aby, abiy, mxy3, mxy4, abxy_ti2, abixy_ti2, xym3, xym4, cna.
Vector: The vector defines which direction the error term applies; possible options are:
a – Azimuth
i - Inclination
l – Lateral (equivalent to 1/sin(Inc))
b – Bias term
e – Depth
f - Depth Bias
n – Intermediate calculation term
m – Wolfe and DeWardt misalignment term
Tie – On: Describes what type the error source is and how it is summed together.
s – Systematic, correlated within a survey file
r – random, never correlated
g – Global, correlated between survey files, and wells
b – bias, correlated within a survey file
n – intermediate calculation step
m – Wolfe and DeWardt misalignment term
Unit: The units used for 1 sigma value of the error term
- No units
d – Degrees
m – Meters
im – Inverse Meters
nt – Nano Teslas
dnt – Degree Nano Teslas
Value: The value of the error term at 1 sigma (1 standard deviation)
Weighting Function: This is the mathematical formula used to describe the error term using generalised variables. The formula is parsed much like in MS Excel and uses all normal operators such as * / () ^. The variables which are supported in Well Seeker PRO are:
Inc – Inclination
Azi – Azimuth referenced to whatever is defined at field level
Tfo – Tool Face
Mtot – Total magnetic Field
Dip – Dip Angle
Gtot – Total gravity
Erot – Earths horizontal rotation speed in rads/s
Tmd – Total measured depth
Tvd – True vertical depth
Azt – Azimuth referenced to True North
Azm – Azimuth referenced to magnetic north
Lat – Latitude
Din – Delta Inc
Smd – Delta Measured Depth
Min Inc: Minimum inclination for the weighting function to be evaluated, generally only used for gyro models.
Max Inc – Maximum inclination at which the weighing function to be evaluated, generally only used for gyro models.
Above the main window is some extra information and options.
Survey tool name: The name of the currently selected IPM.
Description: The user can add a more detailed description of the selected IPM if they wish.
Default IPM: Displays the name of the current Default Survey Tool/IPM.
Create diagnostic file: Toggling this check box, will produce a diagnostic file every time the error model is run and be placed in the Debug folder in the Well Seeker PRO install directory. It should be noted that this option will vastly increase the calculation time required for anti-collision scans and error ellipse reports.
Default survey tool: Toggling this check box sets the currently selected IPM as the default IPM. Its name will be displayed in the Default IPM box above and will be highlighted in green in the list. If a survey or plan has no IPM specified, or Well Seeker cannot find the file for the specified IPM, it will use the default IPM. This is “ZERO_ERROR.ipm” by default.
Inclination Only wells display vertical: Toggling this checkbox defines how Well Seeker handles surveys with an inclination only IPM assigned. Well Seeker will recognise an IPM as inclination-only if it has any of the following names. These names are not case sensitive:
INC_ONLY
INC-ONLY
Inclination Only
Inclination-Only
Inclination_Only
If ‘Inclination Only wells display vertical’ is turned on and an Inclination-Only IPM has been recognized, the following will happen:
The inclination values in the survey will be used to calculate the Ellipse of Uncertainty (EOU) in the error model.
The well will be plotted and assumed to be completely vertical. No azimuth or inclination values will be used to calculate position data.
If an Inclination-Only survey is found with a non-Inclination-Only tool tied on below it the whole well will display as vertical. This including the non-Inclination-Only section.
If an Inclination-Only survey is found below a non-Inclination-Only only tool, the portion of the well above the Inclination-Only tool will plot as normal but all Inclination-Only surveys and anything below them will plot as vertical.
Turning OFF ‘Inclination Only wells display vertical’ will stop all the above behaviour and Inclination-Only wells will plot using the inclination and azimuth data provided in the survey grid.
The default value for the ‘Inclination Only wells display vertical’ option is ON, so by default any Inclination-Only surveys will be treated as above. This value is saved within the setup file, so if the user turns this option OFF, Well Seeker will remember this choice.
The interpolate dialog is available if there is an active survey or plan view open, and it allows the user to interpolate the survey listing for both MD, inclination and TVD.
Type the desired value into either the MD, Inc or TVD cell in the grid and the line will be populated with the interpolated values. Should the value entered be out of range, then -999 will be displayed in all cells. The results can be exported to either a text file or Excel file by clicking the Export Data button in the toolbar.
Show interpolated listing: When selected, the greyed-out buttons along the top of the dialog become available to manipulate. The user then has the option to enter the following data:
Interval: The required interval which the plan or survey will be interpolated e.g. 100 will generate an interpolated line every 100ft or m.
Start Depth: The start depth of the interpolation
End Depth: The end depth of the interpolation
Include Stations: Includes the plan lines or survey stations in the interpolated listing
Include Final Station: Includes the final station in the interpolated listing
Bit Projection Only: If a projection has been added to a survey listing via either the Project Ahead or Multi Project tools, then the user can select this option to interpolate the projection only.
Calculate: Generates the interpolated listing
The Create Target button in the toolbar can be used to create a point target from an interpolated position. The user should select the row number of the listing they would like to turn into a target and then click on the ‘Create Target’ button. Enter a name in the dialog box and click OK. The target will be created and assigned to the Actual Well/Plan for the active survey/plan, and can be edited in the Targets window.
The anti-collision settings dialog allows the user to specify the details used when creating anti-collision reports and generating travelling cylinder, separation factor or ladder plots.
The Interpolate section only affects the Travelling Cylinder, Ladder and Separation Factor Plots. If the “interval” check is selected, the reference well will be interpolated at the interval specified, and AC scans against offsets will be performed at these interpolated points. The “depth from” check box allows the user to specify a depth range to scan. The “include final station” and “include stations” options define whether actual survey stations are included in the interpolation and whether a final station is included at the end.
The Limit Anti-Collision Results section allows the user to define maximum values at which AC results will be displayed. It should be noted that these settings are global and do not change regardless of which well / wells are being scanned against and as such they should be checked before performing any anti-collision scan so that potential collisions are not missed.
Any selections made here will be saved and applied to any AC scans run while the program is open. When the program is closed, upon reopening, these selections will be reset.
The AC results section of this dialog allows the user to select the following (note that these 2 options are defaults and once selected these will be remembered by the program and will NOT reset when the program is closed and reopened):
Sort AC Summary: User can choose from the following: No sort, C-C, ES and SF. This determines the way the AC summary in the AC report is displayed. Choosing C-C, ES or SF will order the summary with the smallest relevant value at the top and the largest at the bottom. No sort will keep the summary for each offset well together. See figures below.
Default TC: Choose the default Traveling Cylinder Plot reference. User can choose between North and High Side.
The Directional Difficulty Index, (DDI), provides a first pass evaluation of the relative difficulty expected when drilling a directional well.
DDI is one of the metrics by which directional drilling performance can be measured. By plotting the planned DDI against the actual DDI, the separation between the two can be used as a metric for directional drilling performance. The smaller the difference the better the directional drilling performance, (it should be noted this is not applicable to wells which are modified while drilling or wells that are geo-steered).
The DDI has also proved useful in other areas of planning. It allows various proposed well paths targeting the same reserves to be ranked in terms of their directional complexity. This is particularly useful in mature assets where a number of candidate wells may be available as side tracking options. By ranking these options, unsuitable host wells may be eliminated. It also ensures that the most cost-effective option from a directional drilling viewpoint is known. This can then be weighed against other influencing factors allowing the most suitable host well to be selected.
For more details relating to this feature refer to IADC/SPE 59196 (The Directional Difficulty Index - A New Approach to Performance Benchmarking)
The offset selector is available if an active survey or plan view is open. It allows the user to select any offset wells which are to be displayed in any of the plots or used in anti-collision scans. Only wells referenced to the same CRS are available to select here.
The offset selector dialog displays a tree which will represent all the selectable wells. This is represented in the same way as the database structure on the main user interface. The Expand and Collapse buttons at the bottom of the dialog affect the offset selector tree and allow the user to quickly access all the surveys and plans without expanding each level individually.
The filter at the bottom of the dialog allows the user to select the following filter options:
Include Surveys: The Actual Wellbore is always available to select; however, this option also allows the user to select individual surveys below the actual wellbore level.
Include Non-Principal Plans: When this option is selected the user can choose to offset any non-principal plans. This option is turned on as a default.
Include Plans: When this option is selected the user can choose to offset any principal plans. This option is turned on as a default.
If any of the filters are removed, the user can click on the Update button to automatically deselect any applicable surveys or plans.
Global Scan is another filtering method which allows the user to select a radius from the reference well surface location. Any offset wells within this radius will be automatically selected when the user clicks Select.
In addition to the individual Plan View, Section View and 3D View plots, Well Seeker also has a Wall Plot Composer (WPC), where different plots along with data tables can be displayed together.
As with the individual plots, the WPC option only becomes available when the user is in a plan, survey, planned wellbore or actual wellbore.
Once open, the user can build the wall plot by inserting the desired Charts and Tables. This can be done via the Insert menu at the top of the page, or by right clicking anywhere on the plot. Certain Charts and Tables can also be inserted from the tool bar along the top of the screen. Once inserted, a chart or table can be moved around the page by clicking and dragging.
See below for a definition of each item on the toolbar:
In the File option at the top left of the WPC screen, the user can select to Save or Open an existing wall plot composer template. These templates are saved as .wpc files and allow the user to save the template they are working on and come back to it later.
When a chart is inserted into the WPC, its size can be manipulated by clicking on it and then dragging the outer edges. Manipulating the chart size changes the scale along with the minimum and maximum X & Y Axis values. This is reflected in the Chart Properties Dialog.
If the user selects to fix the scale, by checking the Fixed Scale box, they will no longer be able to manually manipulate the physical size of the chart. It will be fixed and can only be changed by unchecking the Fixed Scale option.
When dealing with an inserted table, the size and shape of the table can be manipulated by clicking and dragging the outer edge. Once the user is happy with the relative size and position of the table, they can select the Reset Table Aspect Ratio option from the top tool bar, which will adjust the selected table to give it a balanced aspect ratio.
Once a wall plot has been populated, it is possible to move charts and tables forward and back on the page in relation to each other. This allows the user to manipulate the layout to ensure smaller items are kept visible at the front while larger items are pushed to the back. This is achieved by right clicking on any chart or table when in the WPC and selecting either “Bring to Front” or “Send to Back” from the context menu.
For more details regarding the Context Menu, see Section 6.8 – Context Menu.
New: Creates a new WPC project.
Open: Opens an existing WPC project.
Save: Saves the WPC project the user is currently working in.
Save As: Save as function for saving the current WPC project.
Print: Opens the print dialog, where the user can send the current WPC project to a printer or can save the plot as a pdf.
Page Setup: allows the user to select the desired page size and layout. Nine predefined sizes are available from the drop-down menu, including user defined.
Exit: Closes the WPC
New Chart: Allows the user to insert any one of 10 available charts.
New Table: Allows the user to insert any one of 18 available tables.
Insert North Reference: Inserts the North reference data.
Insert Logo: Inserts the primary logo assigned at operator level.
Insert Text Box: Inserts a box in which custom text can be entered. Text can be edited by right clicking on the box and selecting Enter Text, and the background colour can be edited by right clicking and selecting Select Background Colour. Text box aspect ratios can be reset using the Reset Table Aspect Ratio option from the top tool bar.
Chart Properties: Once a plot has been inserted into the WPC, the user can then open the Chart Properties, which is where most of the chart functionality is located, and allows the user to add labels, change colours and customise the plot. The chart properties dialog is available to all plots and is described in more detail in section 6.6 – Plots Menu.
Offset Selector: The offset selector in the WPC works in the same way as it does on the main Well Seeker menu. It is however completely independent, which means that offset wells selected in the main menu will have to be reselected when in the WPC.
Offsets On/Off: When in a plot, this option turns the offset plans and surveys on and off.
Error Ellipses On/Off: When in a plot, this option turns the error ellipses on and off.
Chart Titles On / Off: When in a plot, this option turns the chart title on and off.
Select Image: When a logo has been inserted, the user can click on it and choose select image. This allows the user to select any .bmp image to be used in place of the logo. This option will be greyed out unless the user has a logo selected.
Reset Chart: When the user selects any chart in the WPC, they can then select this option and it will reset the chart to how it appeared originally when it was first inserted.
Object Border On/Off: This allows the user to add a border around any individual chart. The user must select the relevant chart before they select this option.
Select Table Data: When a data table is inserted in the WPC and selected, choosing this option opens the select data dialog. This allows the user to select which data they want to show on the table. Note that the data included in the tables is fixed. The user can choose which of this data they want to display, but they are not able to choose any different data not initially displayed in the table. Note that this dialog can also be accessed by double left clicking on a table.
Chart Properties Default: This option allows the user to select default settings for any charts that are inserted into the WPC. The user can create several different defaults and switch between these when pulling in different charts.
Show Gridlines: Shows gridlines on the main WPC page.
Show Ruler: Displays a ruler at the top and left of the screen.
Show Ruler Numbers: Includes numbers on the ruler.
Show Margins: Shows the margins on the main WPC page.
Show Page Border: Adds a border to the outside edges of the page.
Reset Logo Aspect Ratio – Resizes the selected logo to give it a balanced aspect ratio.
Reset Table Aspect Ratio: Adjusts the selected table to give it a balanced aspect ratio.
Zoom: Gives the user various options for zooming in and out of the WPC.
Align Left: Select a chart/table, select Align Left and then click on another chart/table. The selected chart/table will align itself so that the left side of both items is aligned.
Align Right: Select a chart/table, select Align Right and then click on another chart/table. The selected chart/table will align itself so that the right side of both items is aligned.
Align Top: Select a chart/table, select Align Top and then click on another chart/table. The selected chart/table will align itself so that the top of both items is aligned.
Align Bottom: Select a chart/table, select Align Bottom and then click on another chart/table. The selected chart/table will align itself so that the bottom of both items is aligned.
Opens the Slide Sheet. For more information see section 13.10 – Slide Sheet. This option is only available when a survey is open in the main interface.
The Projection Tools submenu contains a number of tools that allow the user to project ahead of the currently active survey sheet.
The Multi Nudge Projection tool allows the user to quickly project ahead using additional features which are not available in the standard Project Ahead section of Well Seeker. More importantly, it allows an unlimited number of projection lines to be included.
As with the Project Ahead tool, it is important to note that the Multi Nudge Projection tool is only available when the user is in a Survey. If the user is in a Plan, or the Actual Wellbore, this option will be greyed out and they will be unable to select it.
When the tool first opens, the tie-On line will be populated with the last survey in the listing. If there are any projections already in the survey table, they will be ignored. At this point the user can then select from 1 of 5 projection Methods, which are described in more detail below.
The Multi Nudge Projection box can be left open while the user is adding new surveys, and the tie-on line can be updated by selecting the Update Tie On button. Note, that the surveys do not need to be saved for this to happen.
If the box is closed and then reopened, it will automatically tie onto the last survey point. The projection setup will remain populated with whatever setup the user had selected previously, even when the program has been closed and reopened. To remove the input projections, the user can delete the lines one at a time or select Remove from Survey, which will remove all of the Multi Nudge Projection and Landing Data projections from the survey table.
Projections can be added to the survey by selecting Append to Survey.
CL/DLS/TFO - This option allows the user to select Course Length (CL), Dogleg (DLS) and Toolface Orientation (TFO) to calculate the projection. This method assumes a 100% slide. Motor Yield will be automatically populated with the same value input in the DLS column.
CL/Slide (%)/TFO - This option allows the user to select Course Length (CL), Slide Percentage (%) and Toolface Orientation (TFO) to calculate the projection. The user is also required to add the Motor Yield, as the projected dogleg is calculated based on the slide (%) and the Motor Yield.
CL/Slide (Dist)/TFO - This option allows the user to select Course Length (CL), Slide Distance (Dist) and Toolface Orientation (TFO) to calculate the projection. The user is also required to add the Motor Yield, as the projected dogleg is calculated based on the slide (Dist) and the Motor Yield.
INC/AZI/DLS - This option allows the user to select Inclination (Inc), Azimuth (Azi) and Dogleg (DLS) to calculate the projection. This method assumes a 100% slide. Motor Yield will be automatically populated with the same value input in the DLS column.
Hold CL - This option allows the user to select Course Length (CL). The inclination and azimuth from the tie-on line will be held for the selected distance.
The user can set up the Multi Nudge Projection with as many lines as required.
Landing Data: This section of the Multi Nudge Projection allows the user to project to a landing point and is most useful when landing out a horizontal lateral and functions in a similar way to the Dogleg Toolface Point planning method. The position of the bit in the Bit row is populated from the last projection in the Multi Nudge section above. Data in the survey table is ignored.
Entering a Landing Point MD
The MD entered relates to the MD on the principal plan. In the below example, the survey is on the left and the corresponding principal plan is on the right. The Multi Nudge dialog is open at the front.
The MD of the curve landing point (7127.21USft MD) has been entered and the TVD, NS and EW coordinates in the projection match the plan at this depth. The program is effectively calculating a constant dogleg and toolface from the Bit line to this EXACT point. The final landing point can be automatically populated by selecting the Find Landing radio button.
In some cases, it may be important to land out exactly at the same point as the plan. If this is the case, then this is the most suitable option.
It is worth noting that the plan is open here for demonstration purposes. It does not need to be open for this to work.
Adjust TVD
Selecting the adjust TVD, allows the user to change the TVD of the point selected in the above. The MD stays unchanged as this is what the program is using to determine the local coordinates of the landing point.
Note in the above how the locals are still the same in the landing point line, but because the TVD has been shifted deeper, the DLS and the inc have changed. The program is still aiming for a specific point here, only with an adjusted TVD.
Adjust Inc / Azi
This option is only available when Adjust TVD is selected. This allows the user to enter an inc, azi and TVD to project to. The main difference with this selection compared to the previous options is that the user is not projecting to a specific point i.e., the local coordinates are not fixed.
In the above, the inc, azi and TVD are entered for the planned curve landing point. This setup tells the user what dogleg is required to land out at horizontal for a given TVD. When new surveys are added, the bit line updates automatically and so does the landing point line.
NOTE: When this dialog is first opened, there is no requirement to enter a MD. It is possible to just select Adjust TVD and Adjust inc / azi and input the values. There is no need to add a MD unless the user specifically wants to hit an exact point.
When the user clicks on Append to Survey in the Landing Data section, it will add both the landing projection and any projections from the Multi Nudge section above to the survey listing.
The project ahead dialog is only available when the user is in a Survey. If the user is in a Plan, or the Actual Wellbore, this option will be greyed out and will not be available to select. It provides access to a range of Well Seeker PRO directional planning tools to allow the user to project ahead from the last survey point.
One additional tool which is only available in the Project Ahead box and is not displayed in the planning tools when in a well plan is the Trend Over tool. This function allows the user to apply the build and turn trends seen in the previous surveys to the projection.
To select the Trend Over function, the user must select Adjust and then either MD or CL. This function will remain greyed out until these options have been selected. The tool works by averaging out the Build and Turn rates based on the number of surveys selected.
The projection tools always use the last survey on the active survey grid as the starting point for any projection. Any time a new survey is added, this will be automatically updated in the project ahead dialog. The planning tools are described in more detail in the planning section of this manual.
It should be noted that any projections appended to a survey file cannot be edited in the grid and must be deleted before any new surveys can be added to the survey file. Projections can be deleted manually via the survey dialog once the projection dialog has been closed or can be removed by selecting “Remove from Survey”.
If Stack Projections is checked on, then Add to survey will not overwrite any previously added projections and the projection will be added to the survey list as a new line. If it is turned off then “Add to survey” will overwrite any projections that were previously added to the survey.
Refer to the “Well Seeker PRO - Project Ahead Guide” for more details on this feature.
The Dashboards submenu contains tools designed to help the user monitor the wells in their database. It contains the Real Time Anti-Collision warnings tool if accessed whilst a survey or plan is open.
The Real Time Anti-Collision tool allows the user to monitor the proximity of offset wells in real time while drilling and will alert the user if the selected anti-collision warning levels are breached. It can also be used to monitor the deviation of the wellbore from its well plan and alert the user if the trajectory of the well strays beyond a specified distance from the plan. Finally, it can be used to monitor the distance between the well and the edge of the lease.
The Real Time Anti-Collision Tool can only be run when viewing a survey. Each offset well needs to be created in Well Seeker as a planned well, actual well or survey list, and then selected using the Offset Selector tool. The Offset selector tool can be found in the Tools Menu or on the main toolbar. These offset wells must have an error model assigned to allow calculation of Separation Factors.
The well plan referenced in the RT AC dialog is whichever plan is selected as the Principal Plan for that well. To set a plan as the principal plan, right-click on the well plan at the plan level and select ‘properties.’ In the Plan Properties window check the ‘Set as principal plan’ checkbox. Any lease lines that are assigned to the well in the Targets window will also be included in the results.
Warning Levels: Allows the user to specify the relevant warning levels. If one of these thresholds is violated, then the offending result will be highlighted in red and an error message will appear in the warnings column.
Sorting: Allows the user to sort the Anti-Collision Results. Three options are available: None, C2C and SF.
Point of Interest: This section displays the last survey in the survey listing. All results in the anti-collision results window are referenced to this point. This point is updated automatically when a new survey or projection is added to the survey listing.
Anti-Collision Results: This section lists the principal plan, offset wells and lease lines, along with their centre to centre (C2C) distance from the point of interest. If the Calculate Separation Factor checkbox is ticked the results section will also show the Ellipse Separation (ES), Reference Ellipse semi-major radius, Offset Ellipse semi-major radius, Separation Factor (SF), High Side Gravity Toolface (TFO HS) and North Referenced Magnetic Toolface (TFO NORTH). The toolfaces displayed are the toolfaces from the reference well point of interest to the closest point of the offset well in question.
File Menu:
Open RT AC Email: Allows the user to generate an anti-collision update email, which can be configured using settings in the Options menu. The email body contains the last recorded survey and/or bit projection, along with its anti-collision output for the principal plan, offset wells and lease lines. The email will also have a full Survey Report and Anti-Collision Report attached.
Note that these reports use the template that is at the top of the list in the Survey Reports Manager and the Anti-Collision Reports Manager. The user should rename the template that they want to use so that it is first alphabetically. See section 6.5 – Reports Menu for more information on the reports manager.
Exit: Closes the RT AC window.
Options Menu:
Open Email: If this option is toggled on, selecting Open RT AC Email in the File menu will generate an email in Microsoft Outlook, with the Survey Report and Anti-Collision Report attached. If toggled off, selecting Open RT AC Email in the File menu will open an html file in the user’s default browser containing the email body.
Bit Projection on Last Line: Signifies that the last line in the survey tab of the reference well is a bit projection instead of a proper survey. If toggled on, the RT AC Email will list the second to last survey as the final survey, and the last survey as a bit projection.
Include Survey Report: Allows the user to select the format of the Survey Report attached to the RT AC Email. The user can choose between Excel, PDF or Text.
Include Anti-Collision Report: Allows the user to select the format of the Anti-Collision Report attached to the RT AC Email. The user can choose between Excel or PDF.
Straight Line Projections: Allows the user to add one or more projections to the Survey Information section of the RT AC Email. Projections will use the inclination and azimuth of the last line in the survey tab of the reference well.
The Activity Dashboard allows the user to monitor the status of all wells (aka ‘jobs’) in the current database, as well as the status of personnel. It is populated using Reporting Data. See Section 13.0 – Reporting for more information. The Activity Dashboard can be left open or minimized whilst working in other sections of Well Seeker.
When first opened the Activity Dashboard will display the Summary page. This page can be returned to at any time by opening the View menu and selecting Show Summary. The page is split into three charts:
Job Summary by Customer (left) – Displays the number of wells in the database for each operator and their status. The status of a well is set in the latest Daily Report for that well. See Section 13.4.7.1 – DDR Report Selection for information on setting the status.
Job Summary by Coordinator (top right) – Displays the number of wells, along with their status, that have been assigned to each DD Coordinator in the database. The user can change this chart to show the wells assigned to each MWD Coordinator by opening the View menu and selecting Filter by MWD Coordinator. The coordinators are set in the latest Daily Report for that well. See Section 13.4.7.1 – DDR Report Selectionfor information on setting the coordinators.
Job Summary by State (bottom right) – Displays the number of wells, and their status, in each US state. The state that a well is drilling in is defined in the Well Data and Personnel section of the latest Daily Report for that well. See Section 13.4.8 – Well Data & Personnel for information on setting the state.
Below the Summary charts is the Jobs Grid. This is a list of all wells in the database that can be filtered using the dropdown boxes at the top of the grid. Well information for these filters is defined in the Well Data and Personnel section of the latest Daily Report for that well, except for the Operator, which is defined in the Database Tree.
Selecting a well in the Jobs Grid will cause the Summary page to change to the Well Details for that well. When viewing the Summary page, the details for the last well selected can be opened by opening the View menu and selecting Show Well Details.
The Well Details page is split into four charts:
Days vs Depth (top left): Displays the Days vs Depth KPI chart from the Daily Report. This chart is constructed from the daily activities section of the daily report. The colour of the chart can be altered by opening the View menu and selecting Colour by Phase, Colour by BHA or Colour by Activity.
Well Information (bottom left): Displays some general well information from the Daily Report and surveys.
Revenue Tracking (top right): Displays the daily revenue of the selected well. This chart is generated using the daily costs in the Daily Report. See Section 13.4.10 – Daily Costs for more information.
Inventory (bottom right): Displays the number of different types of equipment in the well inventory. This chart is generated using the Tool Inventory. See Section 13.6 – Tool Inventory for more information.
All charts can be customised and exported by right clicking on them to open the Context Menu. See Section 6.8 – Context Menu for more information. In addition to the charts and the jobs grid, there are also some menu items at the top of the screen:
File Menu:
Print Job Board: Prints an Excel document that lists all active, upcoming and on standby wells. Also summarises the revenue and daily revenue for any current wells. The date range for the revenue and daily revenue can be changed in the Revenue Forecast menu.
Print Motor Overview: Prints an Excel document that contains a summary of the number of motors that are currently at each well. For each well there is also a breakdown of the motors on stie by serial number, description, size and status.
Open Selected Well in Tree: Opens the currently selected well in the Database Tree.
Exit: Closes the Activity Dashboard.
View Menu:
Show Summary: Forces the charts to display the summary charts.
Show Well Details: Forces the charts to display the well details of the last well selected.
Show Grid: Toggles the jobs grid on/off.
Show Charts: Toggles the charts on/off.
Colour by Phase/BHA/Activity: Changes the colour and legend of the Depth vs Time chart.
Filter by MWD Coordinator: Toggling this option on changes the Job Summary by Coordinator chart to split jobs by MWD Coordinator instead of Directional Coordinator.
Refresh Data: If any changes are made to the database while the Activity Dashboard is open, the user can use the Refresh Data menu item to apply them to the Dashboard.
Revenue Forecast Menu:
Calendar Month/Last 30 Days/60 Days/90 Days: Changes the date range for the revenue and daily revenue pages in the Jobs Board Report.
The Logistics Dashboard searches all the well inventories in the database and displays all tools which are listed in these inventories. Note that if the On Location box is not checked, the tool will not show up in this dialog.
The filter allows the user to quickly search the available inventory based on Well Status, Tool Type, Tool Status, State and County.
The interactive map at the top left of the dialog displays whatever tools are listed in the table at the bottom of the dialog. Left clicking on any pin in the map will open a window, listing the tools at that location. The window will detail the following for each tool: Serial Number, Description, Tool Type and Status.
The chart at the top right of the dialog shows the number of tools in the inventory at each rig in the database and splits them up by tool type. The chart can be customised and exported by right clicking to open the Context Menu. See Section 6.8 – Context Menu for more information.
The Reset Map button will reset the map to the default position if it has been moved or zoomed in. The Logistics Dashboard can be left open whilst working on other parts of the database. If any changes are made to the database, the user can click the Refresh Data button to update the table.
This option shows the user which wells are currently performing real time data exchange with the SQL server database.
The dialog will only populate when:
The user is accessing an SQL remote database.
At least one additional computer is setup to perform real time data exchange.
If opened while accessing a local database, the dialog will be blank.
In addition to the table, the File Menu is available with the following options:
Show WITS Connections: Any wells that are sending WITS data via the Send Data to Server option in WITS Reader will also be displayed on the Rigs Online Dashboard. If this option is toggled off only wells sent via the Real Time Data Exchange will show up. See section 13.10.7 – Serial/TCP WITS Data Reader for more information on the WITS Reader.
Print Daily Summary: Prints a PDF report that includes the Rigs Online table, as well as the 24hr Summary and 24hr Lookahead for each well.
Exit: Closes the Activity Dashboard.
In Well Seeker, it is possible to have multiple RT AC dialogs open at the same time. In a real-time operations center for example, one user may be monitoring multiple different rigs at any one time. In these situations, the AC Dashboard is designed to help the user monitor these wells as follows:
Two lines will be displayed in the dashboard for each RT AC dialog which is open.
One line will show the details of the offset well with the lowest Centre to Centre distance.
One line will show the details of the offset well with the lowest SF, so long as “Calculate Separation Factor” is turned on in the RT AC dialog.
If any of these values trigger a warning, based on the individual warning levels selected in each RT AC dialog, then the line will be highlighted in red.
Any item which is not an Offset i.e. it does not say offset in the first column of the RT AC dialog, like the principal well plan and targets, will be ignored.
The user can configure the visible columns shown in the AC Dashboard using the Show Hide menu. Additionally, in the File menu, the user has access to the Open RT AC for Active Wells option:
The Open RT AC for Active Wells option allows the user to open multiple RT AC dialogs simultaneously from the AC Dashboard. The Select Wells window will display all wells that are currently set to active in their Daily Report. See Section 13.4.7.1 – DDR Report Selection, for more information on setting the status of a well. The user can toggle wells on or off using the Select column and then click on the Ok button. This will open an RT AC dialog for each selected well.
The user can also check the Update Offset Selection option which unlocks the other options in the Offset Well Selection. Activating these options and then selecting Ok will override the offset selection for the selected wells.
Include Non-Principal Plans: Any plans that are under the same well for each selected actual well in the list will be added to the RT AC offsets for those wells.
Include Principal Plans: Adds the principal plan for each selected well to their RT AC offsets.
Include Actual Wellbore: User should enter a distance in the “Distance from well” box. Any actual wellbores within this distance from the selected wells will be added to their RT AC offsets.
Opens the Tool Orders dialog. The Tool Order dialog allows the user to create tool requests for upcoming jobs and monitor the status of the order to ensure all required tools are ready when the job starts. For more information on the Tool Order dialog, see section 13.21 – Tool Orders.
The Tool Orders dialog is only accessible from the Tools > Dashboards submenu when logged into a remote server. When in a local database, the user can access the Tool Orders dialog via the Tool Inventory window (see section 13.6 – Tool Inventory).
The Incident Dashboard is only accessible from the Tools > Dashboards submenu when logged into a remote server. The dashboard allows the user to review all BHA failures that have occurred over the previous twelve months.
The top half of the window is split into three charts. All of these charts show incidents that have occurred over the last twelve months:
Incident Overview – Displays the total number of BHA failures and the months that they occurred, coloured by the type of tool that failed. BHAs that have had the Motor Failed, MWD Failed or RSS Failed boxes checked in their respect performance reports will be marked on this chart. The month on which they are marked is set by the Date Out date in the performance report. The chart also displays the number of open and closed failure investigations. A BHA is marked as closed if the Closed checkbox in the Failure Information section of the performance report is checked.
Motor Vendor – Displays the total number of motor failures and the months that they occurred, coloured by the motor make. The motor make is set by the Make field in the component properties of the motor in the Drill String Editor.
MWD Type – Displays the total number of MWD failures and the months that they occurred, coloured by the MWD type. The MWD type is set by the MWD Type drop-down box in the main Daily Reports window.
The bottom half of the window contains the incidents grid. This is a list of all BHAs that have had the Motor Failed, MWD Failed or RSS Failed boxes checked in their respect performance reports. The list contains all such BHAs in the database, and is not restricted to occurrences within the last twelve months like the charts. The list can be filtered using the drop-down boxes and the Job # search box at the top of the grid.
Selecting a well in the grid will replace the Incident Overview chart with a listing of the components in the BHA. The user can then use the Open Selected Well in Tree command in the File menu to open the well or return the Incident Overview chart by selecting Show Summary in the View menu.
The admin tools submenu contains tools that can aid the user in managing both local and remote databases.
The database tree search dialog allows the user to quickly search the database to find the relevant well they are looking for.
Search / Select Job Number: Allows the user to search the database using the assigned job number. The job number can be found in the Well Data & Personnel section of the Daily Report. Job number can be entered manually or selected from the drop-down list which will display all the available job numbers in the database.
Select Actual Well: Allows the user to search the database using the actual well name. Well Name can be entered manually or selected from the drop-down list which will display all the available well names in the database.
Date Range: Allows the user to search for wells that have daily reports falling within the chosen date range.
Search Job Status: Allows the user to search the database using the assigned Job Status. The job Status can be found at the top right of the main dialog in the Daily Report. Job Status can only be selected from the drop-down list which has options: N/A, Active, Standby, TD & Complete. The user can also search the assigned DD or MWD Coordinator by checking the Coordinator checkbox and selecting from the second dropdown list. The coordinators are set in the Well Data & Personnel section of the Daily Report.
Search Results Table: Once a search parameter has been entered and search has been selected, any results will populate in the search results table. The user can then select the desired line in the table and hit select. This will close the search dialog and expand the relevant Operator in the database tree, down to the well level.
Search Rig Name: Allows the user to search the database by rig name. The user can enter a rig name into the search box or select from the dropdown list. Rig names are set in the Well Data & Personnel section of the Daily Report.
Select: Clicking on a row and then clicking on the Select button will open the selected well in the Database Tree.
Export Cost Data: Exports the total daily cost data for all currently found wells to an Excel document.
The Clean Database tool will fix any errors in the database due to missing records and data corruption. When run, this tool will do the following:
Check to see if child tables associated with plans / actuals and surveys exist and remove any orphaned tables not associated with any wells.
Checks and removes duplicate records.
Checks and removes daily report records no longer associated with any wells.
Checks that a survey program references wells / surveys which still exist.
Checks and adds in a default depth datum for all wells.
Checks the depth datum for a plan / actual exists and is assigned.
Checks to see if any Instrument Performance Models (IPM’s) which are referenced exist in the IPM folder.
Note, that it is important to back up the database before this tool is run, as some of the changes made are not reversible. The below warning message will be displayed any time the user chooses to run this tool.
This tool allows the user to check if there are any ‘space’ characters at the start or end of any names in the Database Tree. Upon opening the tool, the grid will be populated with any names with spaces at the start or end. The Level column informs the user where in the database tree each name has been found. If there are many names found, the Search box can be used to filter out all but the desired name.
If the user checks the checkbox in the Repair column beside a name and clicks OK, Well Seeker will remove the spaces from the names in the database tree. The user can use the Check All and Un-check All buttons to check or uncheck the whole of the Repair column.
This tool works in a similar way to the Check Names for Whitespace tool. It checks for any duplicated names in the Database Tree and displays them in a list. The Level column tells the user where in the Database Tree the duplicated name can be found. The Parent column displays the name of the level above the duplicated item. If there are many names found, the Search box can be used to filter out all but the desired name.
If the user checks the checkbox in the Repair column beside a name and clicks OK, Well Seeker will fix the duplicated names in the database tree. The user can use the Check All and Un-check All buttons to check or uncheck the whole of the Repair column.
The User Permissions tool allows the user to view and edit the permissions for the users of the currently connected remote SQL database and can only be accessed when connected to a remote SQL database.
The following permissions are available:
Create New Items: User can create new items in the database.
Delete Items: User can delete items in the database.
Edit Items: User can edit items that other users have created.
Administrator: The user can change the permissions of other users.
Approver: User has permission to approve and archive bid sheets. See section 13.15 – Create Bid Sheet.
See Section 6.1.5 – SQL Server Databases for more information on SQL remote server databases.
When a remote database is first created, only its creator will have a username login assigned. New users can be created using the Add User button and removed using the Delete User button. Click on the Username field to edit an existing user’s login name.
The first time a user logs in to the remote database, the WS password that they enter will be saved as the password for any future logins. If a user forgets their password, another user with administrator permission can reset their password by clicking on the Password field.
This feature is only available to Innova Drilling & Intervention staff.
This feature is only available to Innova Drilling & Intervention staff.
Selecting this menu item will round the measured depths of the currently opened survey to the nearest whole number.
Code Defaults allows the user to set the defaults for Activity, Phase and Cost Codes for the whole database. Once these have been set, any new actual well which is created will contain these defaults.
The user can switch between Activity, Phase and Cost Codes using the drop-down box. Any changes they make should be saved by clicking on the save icon at the top of the window.
The user can modify these codes for individual operators and wells if required. See Section 13.0 – Reporting for more information on Activity, Phase and Cost Codes.
The Real Time data exchange tool allows the user to automatically upload updates for a given well to a remote database. After configuration, the exchange can be left running and will automatically ‘push’ regular updates for a well back to their organization’s remote server database.
The Select Well section displays all of the actual wells in the user’s local database, along with the Operator, Rig, Job # and Status of each well.
The list can be filtered by typing in the Search box at the top. Select the well that you wish to push back to the server by clicking the Select checkbox in that well’s row.
The well that you wish to push must also exist on your organization’s server database, with the exact same name at every level in the database tree. You may only push one well at a time. The well status MUST be set to Active, Upcoming or Standby on your organization’s server database, or the server will reject the push.
The Select Data section allows the user to configure what data is sent when the well is pushed.
Daily Reports: Survey data is always sent when the well is pushed, but you can check the Daily Reports option to send daily reporting data as well. This includes inventory, drill string, motor reports, slide sheets and geo-steering.
Push Principal Plan: If the local user has created a new principal plan for the selected actual well, then they can check the Push Principal Plan option. This will cause the data exchange to push the new principle plan to the server. Note that if the user modifies the existing principal plan, then this will not update on the server. It has to be a new principle plan.
Check for new Plans: If this option is checked then every time data is pushed up to the server, Well Seeker will also check if any new plans have been created for the selected well on the server. If so, you will receive a popup notification and message in the Messages section.
To push updates to the correct server database, the Data Exchange needs the credentials of your organization’s ICDS server. Well Seeker should automatically fill in these details based on your license, but if no credentials are detected, these boxes will be manually editable.
The data transfer section allows the user to define how often the Data Exchange should push up to the server database. Enter the time interval between each push in the Update rate box, and then click on Start to begin the data exchange. The Real Time Data Exchange window can now be minimized and you can continue working. The Data Exchange will push your data up to the server automatically, every time the update rate is reached. In the bottom left of the main Well Seeker interface, an indicator will show the status of the Data Exchange.
You can force a push at any time, even if the exchange has not started, by clicking on the Manual Push button. Click on the Stop button to stop the exchange.
The Messages section can be used to monitor the status of the Data Exchange when it is running. It will record every time data is pushed, as well as any errors that are preventing data transmission. If Check for new Plans is turned on, this is where details of the new plans are displayed. The Clear button will clear all messages.
The Real Time Data Exchange dialog also has the following miscellaneous functions:
Check network latency will ping your organization’s server and return the average round trip time in milliseconds. This can be used to troubleshoot network problems
Check for new plans functions in the same way as the Check For New Plans option, but can be used at any time without having to wait for the next data transfer.
Sync Rig/Personnel Names will pull the Rig Names table and Personnel Names & Details table down from the server. Note that this will overwrite anything that is in those tables in your local database.
The Remote Data Fetch tool allows the user to import well and plan data from a remote database without needing login credentials for the server. Its primary purpose is to allow field personnel to quickly retrieve all the required information on a well before they start drilling. The Remote Data Fetch tool allows them to do this without needing to log in to their organisation’s remote server database, which could represent a risk from a security and data management perspective.
The Data Fetch window is split into three main sections, which are described below:
To use the Data Fetch tool, the user requires the URL and port number for their organisation’s ICDS server, which they should enter into the ICDS Server and Port boxes, respectively. This information should be provided to the user by their organisation. An IP address is also acceptable instead of a URL. Depending on how the user’s organisation has set up user management, these credentials may be automatically filled in and not editable.
After entering the ICDS Server and Port, the user can test their connection to the server by clicking the Test Con button. The server will send back a response in the Message Box above. Whenever the user clicks on the Test Con, Connect or Fetch Data buttons, the Message Box will display a response from the server. If there are any errors during the connection or fetch process, they will be displayed here.
After entering the ICDS Server and Port, the user can click on the Connect button. This will populate the Well List section with the wells that are present on their organisation’s remote server database. Once the user has selected the wells they wish to download, and they have adjusted their download settings in the Data Fetch Options section, they can download them to their local database by clicking on the Fetch Data button. The message box will detail the progress of the download. If the download is successful, the message box will display “Data fetch complete!” and the selected wells will appear in the user’s local database tree. Note that if the wells already exist in the user’s local database, they will be overwritten by the downloaded wells.
When the user clicks on the Connect button, the Well List section will populate with the wells that are stored in the organisation’s remote server database.
By default, only wells with the status Upcoming, Active, Standby and TD are displayed and selectable. The user can view plans, principal plans and wells with other statuses by selecting the appropriate setting in the Data Fetch Options section.
At the top of the window is the Filters section. Dropdown boxes allow the user to filter the well list by operator, well status, job number and rig. The search box allows the user to filter the list by any string they want, such as well name, county, or state.
The user can select the wells they wish to download by clicking on the circle to the right of each well. Depending on the settings they have selected in the Data Fetch Options section, offsets and principal plans for the selected wells may also be downloaded when the user clicks the Fetch Data button.
The Data Fetch Options section allows the user to adjust what wells are displayed in the Wells List and what gets downloaded along with the selected wells when the user clicks the Fetch Data button.
Show all wells: By default, only wells with the status Upcoming, Active, Standby and TD are displayed and selectable. Toggling on Show all wells will display all wells regardless of their status and allows them to be selected for download.
Show plans: By default, well plans are not displayed. Toggling on Show plans will display all non-principal well plans and allows them to be selected for download.
Show principal plans: By default, well plans are not displayed. Toggling on Show principal plans will display all principal well plans and allows them to be selected for download.
Pull offset wells: When this option is toggled on, any wells that are downloaded will also download their offsets, if they have any.
Pull principal plan: When this option is toggled on, any wells that are downloaded will also download their principal well plan, if one is available.
Set transferred status: When this option is toggled on, any wells that are downloaded will have their status changed on the server to ‘transferred’. This is a useful way to indicate to the server database manager that a data fetch has been performed.
Opens the Contact List dialog, where the user can enter any relevant contact details.
The Personnel Details window can be used to keep a list of all personnel involved with wells in the database. These personnel will then be accessed quickly when adding personnel to other Well Seeker features such as Daily Reports and Analytics.
The user should enter the name of each member of personnel into the Name column and then select their position from the dropdown box in the Position column. The Email, Phone and Personnel ID columns are optional. The checkboxes in the Active column can be toggled on/off to show/hide personnel from other Well Seeker features.
At the top of the window the user can filter the list by typing in the Search box, which searches all fields in the table. The dropdown boxes can be used to filter by the Position and Employment fields.
The Personnel Utilization tool can be used to generate a personnel utilization report. This report will mark on a calendar each day that the selected personnel member(s) have worked as well as the rig(s) that they worked on.
The user should select a date range in the Date Range section and choose which personnel to include from the list. The Check All and Un-check All buttons can be used to quickly include or exclude all personnel. The personnel list is populated by names that have been entered into the Well Data & Personnel section in a Daily Report. See Section 13.4.8 – Well Data & Personnel for more information.
The report can also be filtered by coordinator and personnel type by clicking on the check boxes in the top right of the window. These dropdown boxes will be populated according to the information entered into the Personnel Details tool. The user can also filter the list using the Search box in the top right corner.
The Rig Names window allows the user to create a list of rig names that can then be used in the Daily Reporting and Database Tree Search tools. Un-checking the Active checkbox next to each rig name will hide that rig from any dropdown list.
Wits data comes in with a time stamp and an ID and is then translated into the appropriate parameter based on the Well Seeker WITS mapping.
When selected, this will open the WITS Mapping dialog, as displayed below.
Port Number: This is not currently used for anything
Internal Mnemonic: The Internal Mnemonic is what Well Seeker uses to map the WITS data it is receiving. For example, a WITS ID of 0110 is mapped to Hole MD (WITS zero standards), which is something that will make more sense to the user. The internal mnemonic is displayed when you double click on one of the Real Time Gauges (see section 13.11.1.1 – Real Time Gauges) in the DD Dashboard, and the user can choose which mnemonic to display.
Table Name: The table ID in the Well Seeker Database which the parameter is written to.
It is important to note that currently, there is NO standard mapping for RAW survey values BX BY BZ, and as a result, it is likely that the channels used will vary from company to company. The user should therefore be aware of this and adjust the mapping accordingly once the relevant channels have been determined.
Here the user can enter the addresses of any company or location that are being shipped to/from over the course of a project. These addresses can then be used in the Daily Reporting package to generate a shipping ticket or a bid sheet. The addresses entered in the Shipping Address tool are applied to every operator in the database, so these addresses are available to select for any well within the database.
The Logos submenu allows the user to set a default for the primary and secondary logos, that are normally set in the Operator Properties window.
Allows the user to select a default primary logo. Once selected, when the user creates a new Operator, the selected logo will automatically populate as the primary logo in the Operator Properties. Well Seeker accepts bmp, png and jpg format images as logos.
Allows the user to select a default secondary logo. Once selected, when the user creates a new Operator, the selected logo will automatically populate as the secondary logo in the Operator Properties. Well Seeker accepts bmp, png and jpg format images as logos.
Removes the currently set primary logo.
Removes the currently set secondary logo.
The IPM File Management tools allows an organisation with a Well Seeker Pro server database to store and manage a list of IPM files on their server. This list of IPMs can then be pulled down to any PC with the correct company Well Seeker Pro credentials, overwriting all existing IPM files used by Well Seeker Pro on that PC. This ensures that well planning have control over the IPM files used within their organization and gives the field the tools to always be in line with the well planner’s IPM structure.
The server administrator should upload the desired IPMs using the Upload IPM Folder command. Well Seeker running on a local computer can then connect to the server to check if the local user’s IPMs are up to date.
With a stable internet connection, Well Seeker connects to the server database every 30 minutes to perform the check. The IP Address and Port Number entered in the ICDS section of the RT Data Exchange (section 6.4.15 – Real Time Data Exchange) dialog is what determines which remote database Well Seeker performs the check on. Well Seeker checks the upload date for each of the IPM’s on the server database and takes the most recent date. It then checks the created date for all the IPM’s on the local computer and takes the most recent date.
If the upload date is newer than the created date an orange warning displays in the status bar at the bottom right-hand side of the main user interface:
The user can then update their IPMs using the Pull IPM Files from Server option.
The user must be logged on to their company main Well Seeker Pro server database, with a Well Seeker login that has the Administrator user permission enabled. This option first deletes any existing IPMs on the server database and then uploads all of the IPM files on the local PC they are currently using from the following pathway C:\Users\[Username]\AppData\Roaming\Well Seeker Pro\IPM, to the server database.
The user must be logged on to their company main Well Seeker Pro server database. Opens a dialog where the current list of IPMs on the server can be viewed, including the file name, the user that uploaded the IPM file and the upload date.
This option can be selected when accessing either a local or server database. When selected, all existing IPMs on the computer are moved to a new folder in the IPM directory called Old, and the IPMs from the server are then all downloaded to the IPM directory (C:\Users\[Username]\AppData\Roaming\Well Seeker Pro\IPM) on the local PC.
The user must be logged on to their company main Well Seeker Pro server database, with a Well Seeker login that has the Administrator user permission enabled. This option deletes all the IPMs from the server.
The Asset Search option allows the user to search all inventories in the database tree for a specific drill string component. The user should enter the serial number of the component and select its type in the Asset Details section and then click on Search. The user can also limit the search to a specific date range by checking the checkbox in the Date Range section before clicking Search.
Results of the search are shown in the three Data sections. The Well Data section will display wells that contain the selected asset in their Inventory. The Run Data section will show wells where the asset has been used in the Drill String Editor as part of a BHA. The Summary Data section displays a summary of the above two sections. For more information in the Inventory and the Drill String Editor, see Section 13.0 – Reporting.
Well Seeker Pro is integrated with a number of third party survey correction providers – Superior QC, H&P Survey Management and RoundLab, allowing the user to contact their servers and download corrected surveys.
The Survey Correction Provider Settings dialog can only be accessed when viewing a survey table. When a corrected survey listing is retrieved from a third party provider, it will be placed in the currently open survey table. Note that all existing surveys in the table will be overwritten.
After opening the dialog, the user should select the provider from the dropdown box in the Provider field, then enter the username and password into the Username and Password fields. The username and password are supplied by the third party survey provider.
In the Select column click on the checkbox that corresponds to the desired well and then click on Update. The Sel Well Name and Sel Operator fields in the Survey Correction Provider Settings window will update.
Note: This will overwrite any existing data in the sheet.
Note: If the tie-on line for the survey is deeper than the surveys available, selecting yes will not do anything i.e. no surveys will be pulled into Well Seeker.
You can also set Well Seeker to automatically check for and sync new surveys. Change the Auto Update field from ‘NO’ to ‘YES’ and set the update rate in minutes in the Update Rate field. In order for the automatic sync to work, the survey sheet must remain open, but the Survey Correction Provider Settings window can be closed.
Some features of the Survey Correction Integration are only available when Superior QC is selected as the provider. These features are optional and are not required to perform the basic survey retrieval function.
To enter the API number in Well Seeker, right click on the relevant actual well in the database tree and select Reporting >> Daily Reporting.
In the Daily Reports window, make sure you have at least one daily report created, and then click on the Well Data & Personnel icon in the toolbar. In the Well Data & Personnel window, fill in the API Job # field. Make sure this matches exactly with the API number entered in Superior QC. Click on Apply, and then save in the Daily Reports window. Note, that if the API number is entered but does not match, then the user will still have the option to manually select the desired well.
In Well Seeker the Latitude and Longitude co-ordinates of the well are set in Well Properties dialog for the well. Grid Convergence is automatically calculated using the well location and the mapping grid selected in the Field Properties Dialog.
Total Field, Dip and Declination are set in the Actual Well Properties dialog. These dialogs can all be accessed by right clicking on the database tree at the relevant level and selecting Properties.
Creates a new blank Well Seeker PRO database. It should be noted that spaces and other symbols should not be used in the filename and that the user must have write permissions for the file location selected. Unless Well Seeker PRO is running with administrator privileges it will not by default have write access to the C:\ location or “program files”
Select the database for Well Seeker PRO to use. This will also be the database which Well Seeker PRO will attempt to connect to the next time the program is opened.
This option refreshes the database tree and useful when accessing an SQL database as it will update the tree with any changes made by other users who are accessing the database at the same time.
Allows the user to select a database from a list of the 10 most recently selected databases.
The User can access Well Seeker’s remote database and SQL server functions here.
This option opens the below dialog, which allows the user to connect to a remote database.
The user should enter their login credentials provided by their server administrator into the appropriate sections. The checkboxes beside Database IP/URL, Database Name and Port hide the entered information. Passwords are hidden by default but can be displayed by clicking on the Show Passwords button. Click on the Save Passwords button to save entered passwords between logins. The Clear button will delete all entered information. Login credentials entered in this window are saved in Setup.ini file. See section 6.1.15 - Export Setup File for more information on the setup file.
Depending on how the user’s organisation has set up their user management section, the Connect to Remote Database login may look like the above, instead. In this case the user does not need to enter any credentials for their company’s database – these are selected automatically. The user simply needs to enter the username and password they use for the Innova Web Portal, provided to them by their administrator.
When logged into a remote server database, this option can be used to update the server table schema to match with the user’s current version of Well Seeker. When used, Well Seeker will display a message similar to the one below, comparing the user’s version of Well Seeker with the remote server’s.
Well Seeker will then update all the relevant tables to the remote server to bring it up to date with the user’s version of Well Seeker. Please note that this can sometimes cause issues for users that try to connect to the remote database using old versions of Well Seeker.
This function can be used to select a new external files directory for the ICDS server. The user should select a folder on their local computer. The folder will then be copied to the ICDS server and will be used as the directory for storing external files from that point on. Any files inside the folder on the local computer will also be copied to the ICDS server.
When this option is toggled on, the Real Time Data Exchange will upload external files when it pushes data to the remote server.
This function links the database to an Oasis ERP database, which then allows the user to import/export data from the Cost Codes, Tool Inventory, Daily Reporting and Drill String sections of the Reporting module. The user should enter the URL, username, and password provided by the Oasis database admin.
Save the currently open survey or plan to the database and update any associated survey programs. This option is only available if a survey or plan is selected in the “Survey / Chart Viewer” area.
Allows the user to import survey data into the selected survey. This option is only available if a survey is selected in the “Survey / Chart Viewer” area. This option is NOT available when in a plan. When the option is clicked the user will be promoted to select a survey file.
Select a survey file from the dialog box and select its file type from the filter drop down menu. Supported file types are tab delimited text, space delimited text, comma delimited text, Excel 2003 files and Excel 2007 files. The file type must be selected correctly based on the file you are trying to import, or the file will not open properly. The survey file can contain column headers and must contain the measured depth in a column, inclinations in a column and azimuths in a column. The columns do not have to be in any order and the file can contain other data columns. Once selected the following dialog will be displayed.
A preview of the survey file will be displayed in the main grid with the row numbers down the left-hand side of the lower grid. Select the start row and the end row of the surveys you wish to import and select which column is which from the combo boxes in the upper grid. MD INC and AZI must be selected and if the column is not to be imported select NA from the combo box.
Once happy with the selection, click the import button and the surveys will be imported.
This option is only available if a survey or plan is selected in the “Survey / Chart Viewer” area. Selecting this option will bring up the survey export dialog which allows the currently active survey / plan to be exported either as a text or an Excel file.
If text file is selected from the drop-down menu, the delimiter can be selected from the radio buttons to the right of the dialog. If the results are to be interpolated, click the ‘Interval’ check box and enter the interval required. Clicking the ‘Depth From’ check box allows the user to specify a depth range to export. Clicking the ‘Include Stations’ check box will include all survey/plan stations as well as interpolated points. Clicking the ‘Include Final Station’ will include only the final survey/plan point. If a plan or survey fie is selected, the ‘Export Whole Path’ option becomes available. This exports the current survey / plan as well as any surveys or plans which the current view is tied to.
When selected, the Autosave feature will automatically save any plan or survey which has not been saved for 30 minutes e.g. if the user enters a survey and then leaves their machine without saving, after 30 minutes, Well Seeker will automatically save the survey. Default is ON.
This option allows the user to create a backup copy of the currently selected database. This is effectively a “save as” feature, allowing the user to choose a suitable location and name for the backup.
This option allows Compass .xml files to be imported into Well Seeker. Select the desired file in the Open File dialog window and click on ‘Open’. Well Seeker will import targets, lease lines, survey error models and well plans according to the settings chosen in section 6.1.13 – Compass EDM Import Options.
Well Seeker Pro requires all items in the same database tree level to have a unique name, whilst Compass does not. To avoid conflicts Well Seeker will modify names at the field, facility, well and actual/plan level when importing a Compass EDM. The logic that the software uses is described below:
Operator: Well Seeker will use the name of the operator stored in the EDM.
Field: Well Seeker will append the name of the operator to the end of the field name stored in the EDM.
Facility: The facility will use the name of the facility stored in the EDM and will not append the field name to it.
Well: The well may or may not have the facility name appended to the end of it, depending on the logic shown in the flow chart below:
Actual Well and Plan: Actual wells and plans will always have the name of the well appended to them as a prefix.
This submenu contains additional settings and options for importing Compass EDM files.
This option opens the compass import settings dialog, where the user can select the appropriate settings that they desire when importing data from a Compass EDM file.
Targets and Lease Lines: Allows the user to either include or omit targets and lease lines when importing. The user can also choose to assign lease lines to their associated wells. If not, the user must assign them manually in the Targets window.
Surveys Tools: When checked, Well Seeker will import any survey tools associated with the relevant plans and surveys. If unchecked no survey tools will be imported. Note, that if survey tools are not imported, and any of the imported plans and surveys reference a survey tool which is not available on the imported computer, then Well Seeker will use the default error model selected by the user.
Well Plans: This option allows the user to import ALL plans which are contained within a Compass Export file. If this option is not selected, then Well Seeker will only pull in the plans which are selected as PRINCIPAL in the export file. Default is ON.
This option functions the same as Import Compass EDM file above, but also sets the status of all imported wells to ‘upcoming’ in the Daily Reporting window. See Section 13.4– Daily Reporting for more information.
This option functions the same as Import Compass EDM file above but allows the user to import the Compass data under an existing operator in the user’s Well Seeker database, instead of the operator contained in the EDM. After selecting this option, a dialog will appear allowing the user to select the operator they wish to import the Compass data into. After that an Open File dialog will appear allowing the user to select the desired EDM file.
This option functions the same as the Import Compass EDM File option above but allows the user to select multiple Compass .xml files to import at the same time. Note that depending on the number and size of the Compass files being imported, the import process can take a long time to complete.
Exports the users Setup.ini file. This file contains all the Well Seeker settings which the user has on their computer including Chart Defaults, Colum Selections, Font Size etc. The only thing this file does not contain is the unit set the user is referencing at the time of export. The exported file does not need to be named ‘setup.ini’, the user can give it any name for easier identification later. The exported file also contains the Toolbar Layout. Users importing an exported setup file will be asked if they also want to import toolbar information.
Allows the user to import a Setup.ini file. This will allow the user to instantly set up a new computer with the same settings being used on another machine. This import will not change the units the user had selected before the import and it will also not affect the database which they are working in. i.e., it will not cause them to switch databases. The user will also be asked if they want to import Toolbar Layout information. The user can import any .ini file. If Well Seeker does not recognize it as a valid setup file, it will give a warning message. Note that setup files exported from obsolete versions of Well Seeker may not be recognised by the latest version.
Resets the setup file back to its original install settings.
Exports the user’s configuration of the toolbars at the top of the main user interface as a .ini file. See Section 5.1 - Toolbars for more information on Toolbars. Note that the Toolbar Layout is also included in a Setup File export, so exporting the Toolbar Layout is not required if the user is exporting their Setup File at the same time.
Allows the user to import a .ini file containing Toolbar Layout information. This will allow the user to instantly set up a new computer with the same toolbars being used on another machine. The user can import any .ini file. If Well Seeker does not recognize it as a valid toolbar export, it will give a warning message.
Resets the setup file back to its original install settings.
This option is primarily for users who are accessing an SQL database which is receiving data from several rigs. When selected, the database is refreshed every 1 minute to ensure that all new surveys pushed from the rig are updated on the user’s screen and incorporated in the real time Anti-collision dialog.
This option closes Well Seeker.
The chart properties dialog allows the user to turn on depth labels by clicking the “Depth Labels” check box and labels will be displayed at the interval specified by the “label interval” edit box. “Start Depth” and “Stop Depth” can also be selected here, where only labels within this depth range are displayed.
Inclinations and azimuths can also be displayed by clicking the inclinations and azimuths check boxes, and these will be displayed alongside the depth labels at the same frequency. These labels can be added independently of the depth labels. It should be noted that if a large number of wells are displayed; turning on depth labels can drastically reduce chart zooming and scrolling performance.
This section allows the user to turn on various chart annotations, such as well names, lithology’s, annotations, casing symbols and plan sections. Plan Sections can only be displayed if the reference well is a plan and annotations, lithology’s, casing symbols and plan sections can only be displayed in section, plan, 3D and spider plots. If lithology lines are selected horizontal lines will be drawn across the plot at the depths of the lithology change. Lithology’s can only be displayed on section plots. Lithology Planes can only be displayed on 3D plots. Lease Line Intersections will display an annotation if a well crosses a lease line. They require a lease line to be set as a target for the reference well.
The warnings annotations if selected will show the warning levels defined at operator level on the separation factor plot. These are on by default in the separation factor plot.
This section allows the user to control properties which affect all chart labels. The style of the label can be changed to bold or italics and the default size of the label can be set here too. If the allow labels to be zoomed box is checked when the user zooms a plot the label size will increase accordingly. If not, the label size will remain fixed regardless of zoom level.
Tether lines can also be attached to labels if the check box is selected. If this is done, when a label is dragged a tether line will be drawn to indicate its original position.
These options are only available in the section and 3D plots and allow the user to add the Geo Steering data to the plots. User can select to add one or all the following zones: Top Target, Target and Bottom Target
This section allows the user to select the font size of the chart labels, axis labels and grid numbers.
The TVD slice section is only applicable to spider plots and allows the user to specify a TVD range which will be displayed on the spider plot.
By default, labels are coloured the same as the well they are associated with, this can be overridden by selecting the check boxes in the label colour section. Overriding the colours will make all labels of that type the same colour.
If the current plot is a plan view or a spider plot, this section allows the user to display a symbol for the wellhead location and allows any templates to be displayed. The slot names on the templates can also be displayed by clicking the slot names option.
Inner and Outer Tolerance circles can also be displayed by selecting the check boxes in this section.
This section allows the user to determine the frequency at which error ellipses are draw. Error colour and line style can also be selected to match the series style in this section.
This option can severely reduce scrolling and zooming performance if a large number of wells are being displayed.
This section allows the user to define if labels are displayed on offset wells or just the reference well. Check the appropriate check box for the label type.
This section allows the user to override the default line colour for various well types.
When selected, the “Randomize offset colours” option overrides all default well colours and all offset wells are displayed with a different, randomly generated colour.
If the current plot is a travelling cylinder, this section allows the user to change the reference of the travelling cylinder plot from highside to true north. The default reference can be selected in the Anti-Collision Settings, which is accessed via the Tools menu.
If the user has opened a Travelling Cylinder plot from a plan, any offset surveys which are associated with the same Well will not display errors when the user selects to show these.
In the above example if the user opens the New Plan and offsets the current survey and the offset survey, when in the TC plot, if they select to display errors, NO errors will be displayed on the Current Survey because it is associated with the same well (Ref Well) as the plan which is being referenced. The offset survey will show errors as it is associated with a different well.
Selecting “Show Errors on Ref Well” from this section of the chart properties, allows the user to override this and display the errors on Current survey if they require.
It is worth noting here that if the user opens a TC plot from the Current survey and offsets the New Plan, even though the new plan is associated with the same well, the errors will display. The program behaves differently depending on whether a survey or plan is the reference for the TC plot.
This section allows the user to select the colour of the Major and Minor gridlines, and the background colour of the plot.
The X, Y and Z plane colours can also be changed here for the 3D plot.
The colour of the text in the plot axis can be changed here via the “Text” option.
This section allows the user to manipulate the X and Y Axis Minimum and Maximum values and fix the chart scale. The axis scale can be added or omitted from the relevant charts by checking or unchecking the “Show Scales” box.
The axis scale units are scale/inch as default but can be changed to scale/cm by checking this box.
In order to display wells correctly, Well Seeker attempts to preserve the aspect ratio of a plot, so it does not appear distorted i.e. X & Y axis scales are kept the same. This can however lead to plots not filling the entire screen. De-selecting the preserve aspect ratio option means that when zooming in on a plot, Well Seeker does not maintain the 1:1 ratio for the axis scales. This can produce wells which look distorted and it is not recommended to disable this option.
Chart grid lines can be manually overridden by unchecking the “auto” check box. This allows the user to manually enter the distance between major and minor grid lines.
When a chart is first opened, it will display the reference well. Sometimes, if there are several targets and the well does not hit these targets e.g. when planning a well, the user wants to initially understand where all the targets are before they attempt to hit them, the targets may fall out with the maximum and minimum values on the chart, and as a result they are not showing. In this situation, the user can select Auto Max Min Scale to Include Targets, and this will automatically adjust the chart axis scale on opening to include the targets.
The colour and line style of individual plans and surveys can be changed by selecting the series from the drop-down menu (or by selecting the plan or survey directly from the box) and then selecting the colour and line style from the drop-down menus. This can also be done by right clicking the chart and using the customization dialog. Note that the customization dialog option is disabled in the Wall Plot Composer. Also note that changing a series style will have no effect if the Force Color option has been select for the plan/actual wellbore properties level, it will remain the forced colour. If the Only Show Principal Plan option is toggled on, plots will not display any wells other than the reference well and the principal plan for that well, if one has been assigned.
This section allows the user to select which grid lines are displayed. X & Y Major and Minor grid lines can be displayed independently of each other. The “Thick Major Gridline” option, displays the major grid lines more boldly than the minor, making them stand out more.
This section allows the user to select the Chart Style. There are 13 different styles to choose from which includes a “No Style” option. Border style is selected from here also. There are five options: Shadow, Thin Line, No Border, Insert and Thick Line.
If required a Legend can be added to any of the plots, and the drop-down in this section gives the user six options: Hide, Top, Bottom, Left, Right and Inside Axis.
This section allows the user to display targets, drilling targets, target names and it also allows the user to determine individual targets colour and line style. It is also possible to hide targets so that they are not displayed on a particular plot. This is achieved by unchecking the “Visible” box associated with any specific target.
Lease Lines and Hard Lines are also displayed in this section and are identified by the check in the Lease and Hard Lines cell.
This section allows the user to toggle Bit Projections on and off. The user can also select the colour of the projection.
This section allows the user to change the size of Survey Spheres and Fly Down Spheres in 3D Charts, adjust Worksight settings, select the rig graphic on or off and adjust the Critical Point Target settings. These options are only available to edit in the Chart Properties for 3D plots.
Allows the user to switch between currently open surveys, plans and charts.
The context menu is available in every plot by right clicking anywhere on the plot. This allows the user to change certain aspects of the plot based on their requirements. The contents of the menu will vary dependent upon the chart selected.
Viewing Style – Allows the user to select the desired Chart style.
Border Style – Allows the user to select the desired Border style of the chart.
Font Size – Allows the user to select the desired font size, which will affect all fonts on the chart including title and axis labels. Large, Medium or Small.
Show Legend – Allows the user to toggle the chart legend on and off.
Legend Style – Allows the user to select the Legend style. There are 6 options, including Hide Legend.
Numeric Precision – Allows the user to select the number of decimal places the numbers in the plots are referenced to. Zero to 3 d.p.
Plotting Method – Allows the user to select the way the line is plotted: Point, Line, Bar, Points + Line, Spline Area.
Data Shadows – Allows the user to select between off, shadow and 3D.
Gradient Styles – Allows the user to select the gradient graphic on a pie chart.
Data Labels as – Allows the user to select the labels as a percentage or as the actual value.
Group Percentages – User can select the percentage threshold below which a segment in a pie chart will be grouped as other.
Grid Options – Allows the user to change the grid options in the chart.
Graph and/or Table – Allows the user to view the chart only, table only or both at the same time.
Point Label Orientation – Allows the user to select the orientation of the X axis series labels.
Include Data Labels – Allows the user to add data labels to the chart.
Mark Data Points – Adds the data points relating to the data labels.
Undo Zoom – Resets the zoom on the chart. Pressing the Z button has the same effect.
Customization Dialog – Opens a dialog that allows the user to chart titles, axis min and max values, fonts, line colour and styles.
Maximise – Maximises the chart to fill the screen. Escape button exits this view.
Export Dialog – Allows the user to Export the chart using multiple image formats: EMF, WMF, BMP, JPG and PNG. The user has 3 options:
Clipboard: exports directly to clipboard, allowing images to be quickly added to word, excel & PowerPoint documents
File: Creates an image file of the chart which can be used on its own or imported into any suitable document
Printer: Sends the chart to the printer
The user can also choose the relevant Width, Pixels and DPI to use for the export. For Clipboard and File options, Pixels is the only available selection. When Printer is selected, the Millimeters, Inches and Points options become available to select.
X Axis on Top – Moves the labelled X axis from the bottom to the top.
Y Axis on Top – Moves the labelled Y axis from the left to the right.
Additional X Axis – Adds an additional labelled X axis.
Additional Y axis – Adds an additional labelled Y axis.
The following context menu items are only available in a 3D chart. For more information on the 3D chart and how to use these items, see Section 12.3 - 3D Chart:
Rotation Animation – Toggle this option on to make the 3D chart rotate automatically around the z-axis, for display purposes.
Rotation Increment – Changes the speed and direction of the rotation animation.
Center on survey – Changes the view to a ‘fly down sphere’ centered on the deepest survey in the reference well. The keyboard arrow keys can be used to change the survey well that the fly down sphere is referencing.
Fly down well – Causes the fly down sphere to automatically move from the top of the well down to the bottom.
Show closest approach – Measures the distance between the fly down sphere and the nearest point on the chosen reference well.
Orientate to North – Orientates the 3D chart so that north on the chart is pointing straight up with reference to the screen.
North Ref Distances – When toggled off, the show closest approach option will display distances with reference to the highside of the reference well. When toggled on, distances will be measured with reference to north.
Go to bottom of well – When center on survey is turned on, this will cause the fly down sphere to go to the deepest survey in the well.
Go to top of well - When center on survey is turned on, this will cause the fly down sphere to go to the shallowest survey in the well.
Record ID: Comes from the .
Field ID: Comes from the .
Click on Get Wells to open the Well Selection dialog. Depending on the selected provider, the Well Selection dialog will look slightly different.
Click on Sync Surveys to check if any new surveys are available from the selected provider. If there are, the user will be given the option to update the survey list in Well Seeker. Click on Yes to update your survey sheet.
Click on Save to save your settings, and then click on the X in the top right of the window to close. To close without saving your settings, click on Cancel.
Auto Get Well: If the user has an API number for the well entered in the Daily Reporting section of Well Seeker, when the Get Wells button is clicked, Well Seeker will look up the API number on the Superior QC server and automatically select the correct well.
Check Well Data: Clicking on Check Well Data will compare the latitude, longitude, magnetic field strength, dip, declination and grid convergence values stored on the Superior QC server, with the values referenced in Well Seeker. If they do not match, a warning box similar to the image below will appear.