1 of 100

Innova Drilling & Intervention

Introduction to Innova Documentation

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.

Updates

Click on the link below to see the latest updates we have added to the Innova Document Portal:

Structure

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.

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.

Promotional Info & Software Overview

Feature Updates

An introduction to the latest updates that have been added to the Innova product range.

Well Seeker Pro - BGGM Error Estimate Integration

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:

[email protected]
US: +1 713-893-4435
UK: +44 (0) 7711411079

Alternatively visit our website: www.innova-drilling.com

Well Seeker Pro - Superior QC Integration

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:

[email protected]
US: +1 713-893-4435
UK: +44 (0) 7711411079

Alternatively visit our website:

Innova App & Portal - Feature Update

For more information on our app and portal, or any of our other products, please contact:

[email protected]
US: +1 713-893-4435
UK: +44 (0) 7711411079

Alternatively visit our website:

Promotional Info

Innova App & Web Portal

For more information on our new app or any of our other products, please contact:

[email protected]
US: +1 713-893-4435
UK: +44 (0) 7711411079

Alternatively visit our website: www.innova-drilling.com

Generic Documents

Innova Generic Documents

A selection of generic documents which are relevant to both Well Seeker and Innova Engineering

License Renewal

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)
Send it to
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 [email protected] for support

Installing Updates

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 [email protected] for support.

Quick Start Guides

Well Seeker X Guides

A selection of quick start guides for Well Seeker X

Well Seeker X: Backing up a WS Db

1.0 - Introduction

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.

2.0 – Backing up a Database

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.

2.1 – Backing up the current database

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.

2.2 – Backing up additional databases

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.

3.0 – Selecting a backup database

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.

4.0 - Important Points to Note

4.1 - Back Up Location

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.

4.2 - Uninstalling Well Seeker

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.

4.3 – mdb / ldb Files

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.

Questions relating to any of the above can be sent to

Well Seeker X: Changing Datum Elevations

1.0 - Introduction

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.

2.0 – Depth Reference

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
1. Note: The TVD Subsea values will remain unchanged if the GL to MSL value is the same for both datums.
2. 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
1. Note: The TVD Subsea values in this case will change.
2. 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.

3.0 – Example

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.

Well Seeker X: Adding an IPM

Introduction

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.

Method 1 - If the user has an IPM file

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.

Method 2 - If the user does not have an IPM file

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.

Well Seeker X: Local Login Guide

1.0 – Introduction

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.

2.0 – Setup – Innova Web Portal

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.

2.1 – Creating Roles for Local Database Users

This section requires the user to be familiar with the Innova Web Portal User Management feature. For details on this see the 19.0 - User Management section of the Web Portal Manual.

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.

2.2 – Create Users and Assign a Role

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.

For details of creating a new user see the 19.1.1 - Adding a New User section of the Web Portal Manual.

2.3 – Enabling the Local Login Feature

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.

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 Data Synchronization Feature Update document.

3.0 – Well Seeker X Local Login Process

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.

Well Seeker X: Survey Correction Integration Guide

1.0 - Introduction

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.

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 .

2.0 - Description

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.

Click on Get Wells to open the Well Selection dialog. Depending on your provider, the Well Selection dialog will look slightly different.

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.

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.
1. Note: This will overwrite any existing data in the sheet.
2. 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.

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.

3.0 - Superior QC Only features

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.

3.1 – 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.

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.

3.2 - 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.

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.

Plan v Actual Wall Plot Guide

Introduction

Innova have implemented a new wall plot templating feature in the Innova Portal. This feature allows an organization’s server administrator to create standardised wall plot designs that users in the field can utilize.

It also allows the administrator to create a Plan v Actual wall plot, which users in the office and the field can download and print with a single click. This document guides the user through the process of setting up a Plan v Actual wall plot template in the Portal, and how end users can utilize it.

Setup – Innova Portal

Before the Plan v Actual plot can be used, it needs to be set up in your organization’s Innova Portal. In order to do this, your role must have add/edit/create permissions, and have access to the Wall Plot Composer product feature. To set up the Plan v Actual, follow the below steps:

Log into the Innova Portal. In the Wells List page, select one of your wells by clicking on its name.

In the side menu on the left, expand the Well Views submenu and select Wall Plot Composer.

Use the Wall Plot Composer tools to construct the Plan v Actual plot to your specifications.

Users should take note of a useful feature that is an important part of a working Plan v Actual plot – the Lock to End feature. To activate it, double click on a plan or section view chart to open the Properties dialog for that chart. Navigate to the Scales tab and toggle on Lock to End. Then click on Apply to save your changes. With this option active, when you load the wall plot the chart will automatically zoom in on the latest survey.

Note that this feature is also available in Well Seeker X. It can be found in the Chart Properties dialog for a chart, when using the Wall Plot Composer:

Click on Save Layout As in the Wall Plot Composer toolbar to save your wall plot for later. Enter a name for the wall plot in the Template Name field, and then click on Save.

Click on Save As Template to add the wall plot to the list of available templates. Enter a name for the template in the Template Name field, and then click on Save.

Open the burger menu by clicking on the icon in the top left of the page. Expand the Database Admin Tools submenu and select Wall Plot Templates.

The Wall Plot Templates page contains a list of all available templates for your organization. Assign a template to one or more operators by clicking in the Default for Operators cell and selecting them from the dropdown.

Operations – Innova Portal

Now that a Plan v Actual template has been created and assigned to an operator, it can be used to quickly generate a Plan V Actual wall plot in PDF format. To do so, follow these steps:

Use the side menu to navigate back to the Wells List page.

Find a well that you wish to print the Plan v Actual plot for. You can use the search bar at the top of the table, or the filter feature at the top of each column.

Click on the icon on the left hand side of the well and select Plan v Actual. After a few moments, it will generate a PDF format wall plot, which you can then open or save depending on your browser settings.

If the well was under an operator that has a template assigned to it, the PDF will use that template. If not, it will use a generic PvA template.

Operations – Well Seeker X

Users at the rig site can also make use of the templates to quickly generate a Plan v Actual plot during drilling operations, using Well Seeker X. In order to do this, there are two requirements:

The user must have a license that is registered to their organization.
They must have a working internet connection.

Once those requirements are in place, you can create a Plan v Actual plot by following these steps:

Open a survey or actual wellbore.

Select the Home ribbon and navigate to the WPC icon in the Wall Plots section. Click on the arrow below the WPC icon and select Print to PDF. Well Seeker will contact your organization’s server, and if a template has been assigned to the operator of the current well, it will generate a PDF format plan v actual wall plot using that template. If no template is detected for the operator, it will use a generic design.
1. Note there is no requirement to open the WPC to achieve this.

Alternatively, the user can load a template into the Wall Plot Composer in Well Seeker X, allowing them to edit it before printing. To do so, follow these steps:

Open a survey or actual wellbore.

Select the Home ribbon and click on the WPC icon in the Wall Plots section, to open the Wall Plot Composer.

In the Wall Plot Composer window, click on the arrow below the Open icon select Open Template.

Well Seeker will contact your organizations server and retrieve a list of all Wall Plot templates that have been created for your organization.
Select the desired template from the list and click on Open. Well Seeker will download the template to the Wall Plot Composer.

You can then edit and print the template as if it were a normal wall plot. Click on Save As to save the template as a .wpc file on your computer, which you can then open at any time.

Well Seeker Pro Guides

A selection of quick start guides for Well Seeker Pro

Installation Guide

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.

Adding an IPM How To Guide

Introduction

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.

Method 1 - If the user has an IPM file

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.

Method 2 - If the user does not have an IPM file

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.

Backing Up A Well Seeker Database

A guide to backing up a Well Seeker Pro local Database.

1.0 - Introduction

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.

2.0 – Backing up the Database

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.

2.1 – Backing up the current database

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.

2.2 – Backing up additional databases

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.

3.0 – Selecting a backup database

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.

4.0 - Important Points to Note

4.1 - Back Up Location

4.2 - Uninstalling Well Seeker

4.3 – mdb / ldb Files

Questions relating to any of the above can be sent to

Changing Datum Elevation

A guide to changing datum elevation in an existing plan or survey.

1.0 - Introduction

2.0 – Depth Reference

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.

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
1. Note: The TVD Subsea values will remain unchanged if the GL to MSL value is the same for both datums.
2. 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
1. Note: The TVD Subsea values in this case will change.
2. 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.

3.0 – Example

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.

Compass Export Files & Db Naming Conventions

A guide to maintaining proper naming conventions to avoid conflicts when importing compass export files.

1.0 – Introduction

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

2.0 - Importing 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.

2.1 – 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.

2.2 – Recommended Settings

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.

3.0 – Well Seeker Setup File

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

Compass IPM Issues

A guide to some issues associated with ipm files taken from Compass.

1.0 - Introduction

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.

2.0 - Vector and Tie-On Issue

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.

3.0 – Duplicate Error Terms

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.

4.0 – Error Term Reference

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.

5.0 – drfr MWD Term

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.

Downlink Control User Guide

1.0 - Introduction

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.

2.0 – Security

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.

2.1 – Local Network Security

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.

2.2 – Remote Access Security

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.

3.0 – Downlink Control

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

Inclination Only IPM Guidelines

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:

1) Inclination-Only Models

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

2) Changing IPM File Name

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.

3) Inclination-Only Survey Behavior

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.

4) Inclination-Only Sensitivity to Zero Inclination Surveys

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.

5) Prior Versions of Well Seeker Pro

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.

Innova Remote Client Setup Guide

1.0 - Introduction

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.

2.0 – Security

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

3.0 – Innova Remote Client Installation

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

4.0 – Innova Remote Client Setup

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

Survey Correction Integration Guide

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

1.0 - Introduction

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.

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 Well Seeker Pro How to Guide.

2.0 - Description

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.

4. Click on Get Wells to open the Well Selection dialog. Depending on your provider, the Well Selection dialog will look slightly different.

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.

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.

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.

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.

3.0 - Superior QC Only features

3.1 – Auto-Get Well

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.

3.2 - Check Well Data

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.

Innova Engineering Guides

A selection of quick start guides for Innova Engineering

Installation Guide

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.

Apparent WOB Chart

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.

APPARENT WOB SNAPSHOT CHART

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.

Casing Wear Prediction

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

Drill Pipe Fatigue Plot

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)

Hole Cleaning Guide

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.

Annular Velocity Profile Plot

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 (Cuttings Carrying Index) Plot

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.

Cuttings % Plot

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.

Minimum Flow Rate Plot

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.

Remote Database Guides

A selection of guides for setting up and maintaining a remote cloud-based database using Amazon AWS or Microsoft Azure.

Oasis Integration Guide

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:

Innova in any Language - Web Browser Translation Guide

Background

As Innova Drilling and Intervention products continues to be adopted by teams around the world, we’re seeing growing interest from users whose first language is not English. While our documentation is currently written in English, we want to make sure that everyone has the tools they need to understand and use it effectively—regardless of language.

To support this, we’ve created this guide to show you how to use the translation features in Google Chrome and Microsoft Edge, two of the most widely used browsers. Both browsers include built-in translation tools that allow you to instantly translate our documentation and any other web page into your preferred language.

1.0 - Microsoft Edge Built-in Translation

1.1 - Automatically Translate a Page

When user visits any Innova Documentation page, Edge may offer to translate it automatically if the default language in the user’s system is not English.

Open the webpage you want to translate.
A pop-up banner may appear at the top of the page, offering to translate it.
Choose your preferred language from the drop-down.
Click ‘Translate’.

💡Tip: You can select ‘Always translate from [language]’ to automate this for the future.

1.2 - Manually Translate a Page

If no prompt appears, the user can trigger the translation manually:

Click on the Translate icon in the address bar, next to the star/bookmark icon.
In the pop-up menu, choose the target language.
Click ‘Translate’.

Right-click anywhere in the page
Select ‘Translate to [language]’,in the context menu

User can revert the translation at any time by clicking on the translate icon again and selecting ‘Show original’.

1.3 - Translation Settings

To customize when and how translations appear:

Go to Settings in Edge (three-dot menu > Settings).
Click on Languages.
Enable or disable “Offer to translate pages that aren’t in a language I read.”

2.0 - Google Chrome Built-in Translation

2.1 - Automatically Translate a Page

When user visits any Innova Documentation page, Chrome may offer to translate it automatically if the default language in the user’s system is not English.

Open the Webpage you want to translate.
A pop-up banner may appear at the top of the page, offering to translate it.
Click in the desired language (usually auto-selected).

💡 Tip: Clicking on the 3 dots icon will open the options to choose always translate this language, never translate it or choose another language.

2.2 - Manually Translate a Page

If the prompt doesn’t appear user have 3 options:

First Option
- Right-click anywhere on the page.
- Select ‘Translate to [Your Language]’ from the context menu.

Second Option
- Click in the Translate icon in the address bar (if visible).
- Click in the auto selected language.

Third Option
- Click in the 3 dots icon on the right top corner of the browser
- Select ‘Translate’ from the menu

User can revert the translation at any time by clicking on the translate icon again and selecting ‘English’.

2.3 - Translation Settings

To customize when and how translations appear:

Open Chrome Settings (three-dot menu > Settings).
Go to Languages.
Expand the section to “Language”.
Change the settings on ‘Google Translate’ grid under.

3.0 - Translate Any Web Page

It is important to mention that, these built-in browser tools are not only for Innova Documentation page, but can be used to translate any web page, including and .

4.0 - Conclusion

While this guide covers Chrome and Edge, it's worth noting that other modern browsers offer similar translation functionalities. If you're using a different browser, you can likely find a translation feature that works in much the same way.

We encourage all users, especially those in multilingual teams or regions, to leverage these browser tools for an enhanced, seamless experience with our documentation.

For further assistance, please contact support.

Innova ICP API Guides

A selection of guides that cover the configuration of Innova ICP API functionality with other software and services.

Registering an OAuth App on Okta

Covers registration and configuration of an OAuth App on the Okta identity management platform.

Introduction

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!

Procedure

Go to and log in to your account.

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.

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.

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.

Additional setup to enable Multi Factor Authentication (MFA) logins

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

Note for Innova Admins

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

Manuals

Well Seeker Pro Manual

The full Well Seeker Pro maunal.

1.0 - System Requirements

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.

4.0 - Getting Started

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.

6.0 - Main Menu

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.

6.2 – Edit Menu

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.

Well Seeker X: MWD Reporting Guide

Introduction

Well Seeker X improves the workflow for recording MWD information at the rig site, and adds a number of new features. This document is a guide to setting up and using the MWD reporting in Well Seeker X. By following this guide, users in the office and in the field can understand how to get the most from these features.

Office Pre-Job Steps

The Probe Catalog is an organization level record of the exact probe measurements that are uniform to the specific probes available to your organization, which is stored on your organization’s server database. It is usually the responsibility of your organization’s MWD Coordinator / Manager to maintain the MWD Probe Catalog.

Note: If you have a corporate license, you will only be able to access the Probe Catalog dialog when logged into your organization’s server database. If you attempt to access the Probe Catalog from a local database, you will receive the below error message:

When the DD or MWD Engineer at the rig site use the Data Fetch to pull well data into their local database, the Probe Catalog is also retrieved. The MWD Engineer can then use the probe data contained in it to construct the MWD probe string for their BHA. Using this method streamlines the MWD Engineer’s inputs, avoids potential errors by reducing manual entry, and allows your organization to maintain quality control.

Additionally, the Admin can also create MWD probe templates. These are pre-made, commonly used, MWD strings using the probes entered into the Catalog. The MWD Engineer at the rig site can then use these templates to build their probe strings at the click of a button, saving time and further reducing the need for manual entry.

Probe Catalog

The Probe Catalog should be populated on your organization’s server database. In order to do this, you will need login credentials and edit/create permissions. Follow the steps below to set up the Probe Catalog:

Log into your organization’s server database by clicking on the Server icon in the Home ribbon.

Once connected to the server, open the Tools ribbon click on MWD Probes in the Catalogs section.

Enter the probes owned by your organisation into the catalog.

Description: Enter a descriptive name for the probe.

System: Probes can be grouped into ‘systems’, which can then be filtered when picking probes to add into an MWD config.

Type: Select a probe type from the dropdown box.

Length: The length of the probe. This is always in inches.

Sensor 1 Type: If there is an L/MWD sensor in the probe, select it’s type from the dropdown box. If there is no sensor in the probe, select ‘none’.

Sensor 1 Distance from Bottom: If you selected a sensor type for any given probe, you can then enter the distance of the sensor from the bottom of the probe. The bottom is the end of the probe pointing towards the bit. This distance is always entered in inches.

Sensor 2 Type: If there is a second L/MWD sensor in the probe, select it’s type from the dropdown box.

Sensor 2 Distance from Bottom: The distance of the second sensor from the bottom of the probe.

Max number: The maximum number of this probe that can be included in a MWD config.

Required: If this is checked then at least one of this probe must be included in a MWD config.

Always on top: If this option is checked, this probe will automatically always be placed at the top of the probe string when added into an MWD Config.

Always on bottom: If this option is checked, this probe will automatically always be placed at the bottom of the probe string when added into a MWD Config.

An important point to note when adding a Pulser. If the transmitter is bottom mounted (i.e. a UBHO setup where the transmitter is the part of the probe string that is closest to the bit) the user should leave the Sensor 1 Type field as None.

If the pulser is top mounted (the transmitter is the farthest part of the probe string from the bit) the user should set the Senser 1 Type to Top Mounted Pulser Ref. In the Sensor 1 Distance from Bottom field, enter the distance from the bottom of the transmitter to the mounting point on the transmitter, where it is mounted to the drill collar. The program will place the probes inside the collars so that the mounting point lines up with the point defined by the “UBHO Pin to Set Screw (SS)” distance. See Appendix C for a more detailed breakdown of the top mounted configuration.

Click on Apply and then Close to save your changes and close the Probe Catalog.

MWD Probe Templates

MWD probe templates are created and stored on your organization's server database, and are pulled down at the same time as the Probe Catalog when the field engineers do a data fetch. Follow the below steps to set up a probe template.

The MWD Probe Templates dialog can be opened from within the Probe Catalog dialog by clicking on the Templates button in the bottom left corner.

Click on Add to create a new template. Enter a name for the template then click on Save.

The Catalog section contains the probes entered into the Probe Catalog. The dropdown box at the top can filter the list based on the system they were assigned to.

Use the Add and Remove buttons to add probes from the catalog to the template. Use the Move Up and Move Down buttons to re-arrange the order. Click on Save to save your changes.
1. Note: If a probe has the always on top or bottom cell checked then you will not be able to move this using the Move Up / Down buttons.
2. Note: Bit direction is down in the template, meaning that the bottom of the template should be the probe closest to the bit.

Field Pre-Run Steps

The following steps should be taken by the field personnel (i.e. the MWD Engineer) at the rig site while setting up the first BHA run. Subsequent BHA runs will need to repeat Step 3 onwards:

The engineers at the rig site should use the Data Fetch to retrieve the well from the server. Using this method will also pull down the MWD Probe Catalog and templates to the rig site computer.

This step is optional, but will make entering data easier in the following steps. Enter the details of the UBHO collars, non-magnetic drill collars, MWD probes and MWD surface system into the Inventory dialog. For the collars you should enter as much information as you can, but the MWD probes and surface system only need their Type and Serial Number entered. One of the collars, usually the UBHO sub, should have the type MWD/LWD.

Build your BHA in the Drill String Editor. In order to use the MWD Config, the BHA must include one component with the MWD/LWD type. In order to calculate the carrier length and insertion gear results in the MWD Config, you should also include the non-magnetic drill collars.
1. Note: In order to use the MWD Config, the MWD/LWD component must contain the word “UBHO” somewhere in its description.

In the MWD section of the menu ribbon, click on MWD Config. This will not be available to select unless you have an M/LWD component in the string.

In the MWD Config dialog, construct the M/LWD probe string that is being used in this BHA. If you have templates available, you can select one from the dropdown box in the Probe Config section to automatically populate the string.

If no templates are available, you will need to build the string manually. Use the Add and Remove buttons to add probes from the Catalog to the probe string. Use the Move Up and Move Down buttons to re-arrange the order.
1. Note: If a probe has the always on top or bottom cell checked then you will not be able to move this using the Move Up / Down buttons.
2. Note: Bit direction is down in the template, meaning that the bottom of the template should be the probe closest to the bit.

For each probe added to the probe string, enter a serial number and a version number. If you entered the details of the probes into the Inventory dialog, then the serial numbers will be available in dropdown boxes.

In the BHA section, fill in additional details for the probe string. Fields highlighted in green are editable.

Probe Length: The total length of the probes in the Probe Config section. This is automatically calculated and is displayed in the selected length unit.
Carrier Length: The length of the component above the MWD/LWD component, if the string is using a bottom mounted transmitter. If the string is using a top mounted transmitter, it will show the length of the component below the MWD/LWD component.
UBHO Pin to Set Screw: If the string is using a bottom mounted transmitter, this is the distance between the UBHO pin end and the set screw. The software assumes that the end of the last probe is sitting on the set screw. If the string is using a top mounted transmitter, this is the distance between the UBHO pin end and the anchor point on the transmitter.
UBHO Box to Set Screw: The difference between the pin to set screw value and the length of the UBHO / Transmitter Sub.
Bit to UBHO: The distance between the bit and the pin end of the UBHO.
Insertion gear: The distance between the top of the probe string and the end of the carrier component, and represents how much space you have left in your carrier. If this is a negative number, it means the probe string is sticking out of the end of the carrier. Refer to Appendix B to see how this value is calculated.

The rest of the inputs in this section do not have any effect on the sensor offsets, but can appear in reports:

Pulser type: Enter a description for the pulser type (e.g. positive pulse).
Helix type: The helix material.
MWD collar type: Choose from either Slick or Flex.
Telemetry Type: Choose from either MP (Mud Pulse), EM, Dual or Wired Pipe
Fin Size: Enter a size for the probe centralizing fins.
Stickup: Enter a stickup length for the MWD.
Gamma Correction: Enter the amount of gamma correction, if applicable.
Retrievable: Select whether the probe string is retrievable or not.

The Sensor Offsets section displays the sensor offsets. The sensors displayed here depend on the types of probes selected in the Probe Config section. The offset values are calculated using the probe length and sensor distance from bottom values entered in the probe catalog, along with the lengths entered in the Drill String Editor for the specific BHA.

Refer to Appendix A to see how these values are calculated for a standard UBHO configuration, and Appendix C for a top mounted configuration.

When you are finished, click on the Apply button to save your changes, and then Close to close the dialog. The sensor offset values will be sent to the MWD/LWD component in your drill string.

In the MWD section of the menu ribbon, click on Surface System.

In the MWD Surface System dialog, enter the serial numbers of each piece of the surface system, click on Apply to save your changes, and then Close to close the dialog. If you entered details for the surface system equipment into the Inventory dialog, the serial numbers will be available as dropdowns. Note that the data entered here will be applied to all BHAs on the well, not just the currently selected BHA so you generally only need to enter this data once.

Click on the Save icon in the menu ribbon to save your data.

Field Steps During Drilling

The following steps should be taken by the MWD engineer at the start of, and during the BHA drilling run:

After picking up your tools, return to the Drill String Editor and click on MWD in the Run Data section of the menu ribbon.

In the MWD Run Data dialog enter the pre-run test results in the Test section, the battery plugin time in the Batteries section, and any other details in the Setup section. Click on Apply and then Close.

During drilling there is some information that the MWD can fill each day, in the Daily Data section of the Daily Reports – MWD Comments, MWD Type, MWD pulse height on btm and MWD pulse height off btm.

Field End of Run Steps

Once the BHA run is complete, the MWD engineer should perform the following steps:

Return to the Drill String Editor and click on MWD in the Run Data section of the menu ribbon.

Fill in the post-job test results in the Tests section MWD Run Data dialog, and enter the battery plug out time in the Batteries section.

Enter any relevant comments in the Run Summary section.

If there has been an MWD incident during the run, record it by checking the MWD Incident box. Select the probe type in the Incident Type dropdown and the specific component in the Component dropdown. Enter any relevant comments in the Incident Information and Shop Findings boxes.

Click on Apply to save your changes and the Close the dialog.
You can now print a MWD Performance Report from the options in the menu ribbon.

Calculators

In addition to the features mentioned in the sections above, Well Seeker X includes two additional MWD tools – the Non-Magnetic Spacing Calculator and the Pressure Drop Calculator. These calculators can be accessed from the menu ribbon in the Drill String Editor.

Non-Magnetic Spacing Calculator

The Non-Mag Spacing Calculator from Innova Engineering has been updated and 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 calculation, the following inputs are required:

A completed BHA in the Drill String Editor. This BHA must include:
- An MWD/LWD component, with the directional sensor offset entered into the component properties.
- The non-mag checkbox checked for all non-magnetic components.
- Lengths and OD values entered for every component.
Geomagnetic values entered and marked as active in the Magnetics section of the Actual Wellbore Properties dialog for the well.
The Co-ordinate Reference System selected in the Filed Properties dialog.
Select Grid or True for the north reference in the Facility Properties dialog.
Enter a well location in the Well Properties dialog.
A survey or principal plan covering the desired depth interval.

In the Settings section, enter the depth interval of the BHA run in the Depth In/Out fields. If you wish to use your principal plan instead of your surveys, toggle the Use Wellplan option. In the Max Azi Error field, set your maximum acceptable error in the raw azimuth measurements. The default is 0.5.

The Pole Strengths section displays the pole strength in mWb of the components below (P1) and above (P2) the non-magnetic collars. This is based on their component type and OD. You can manually override these values by toggling the Auto option off.

For each survey/plan station, the table displays the following results.

MD: The measured depth of the survey/plan station.

INC: The inclination of the survey/plan station.

AZI (GRID/MAG): The azimuth of the survey/plan station, referenced to grid north and magnetic north, respectively.

AZI Err: The estimated error in the azimuth readings due to axial magnetic interference from the steel components in the BHA. This column will be colour coded depending on the Max Azi Error limit that you set. Green means the error is below the acceptable limit, orange means it violates the limit by a small margin, and red means it violates the limit by a large margin.

Dip/BTotal Err: The estimated error in the dip and field strength measured by the directional sensor, due to axial magnetic interference.

Req NM Above/Below: An estimation of the length of non-magnetic collars that would be needed above/below the directional sensor, in order to reduce axial magnetic interference enough to get the Azi Error below the Max Azi Error limit.

If any station violates the Max Azi Error limit, the calculator will conclude that there is not enough non-magnetic spacing. It will also report the largest Req NM Above/Below value, and compare it to the actual lengths of non-magnetic collars in the BHA.

The user can save their changes by clicking on the Save icon, and print their results using the Print icon.

Pressure Drop Calculator

The pressure drop calculator can be used to estimate the pressure drop across the transmitter.

Selected: Select a row and then click on apply. The inputs and results from the selected row will be added to the component properties of the MWD/LWD component.

Type: Choose either Poppet or Restrictor. This will affect the input and output columns available.

Orifice ID: Poppet only. Select the size of the orifice in inches from the dropdown.

Poppet OD: Poppet only. Select the size of the poppet in inches from the dropdown.

Restrictor Size: Restrictor only. Enter the restrictor size in 32nds of an inch – the same as a bit jet.

Flow Rate: Enter the estimated drilling fluid flow rate during the BHA run.

Mud Weight: Enter the mud weight for the BHA run.

Depth: Poppet only. Enter a measured depth value. This is used to calculate the surface amplitude result.

Pulse Width: Poppet only. Enter the pulse time in seconds.

Pressure Drop: The calculated pressure drop across the poppet/restrictor based on the above inputs.

Surface Amplitude: Poppet only. The estimated amplitude of the pulse when it reaches surface. Requires a value entered into the Depth field.

Error: If any required inputs are missing or have invalid values, an error message will appear in this column.

Appendix A: Sensor Offset in Bottom Mounted Configuration

The below MWD config is an example of a standard probe configuration using a UBHO collar with a NMDC carrier above it.

The BHA for this example would look something like this:

The equation for finding the sensor offset in this configuration is as follows:

The above equation has the following assumptions:

The UBHO Pin to SS measurement assumes that the lower end/helix probe is sitting on the set screw with no overlap.
The Sensor distance from bottom value for the sensor probe is measured from the end of the probe pointing towards the bit, to the sensor on the probe.

The diagram below illustrates the sensor offset calculation.

Appendix B: Insertion Gear Calculation

The insertion gear value represents how much space is left in the Carrier collar, in a standard MWD config. If the Insertion Gear value is negative, this means that your probe string is sticking out of the end of the carrier. The equation for the insertion gear calculation is as follows:

Where the UBHO Pin to SS measurement assumes that the lower end/helix probe is sitting on the set screw with no overlap.

The diagram below illustrates the insertion gear calculation.

Appendix C: Sensor Offset in Top Mounted Configuration

The below MWD config is an example of probe configuration using a top mounted pulser in a transmitter/pulser/gap sub, with a NMDC carrier below it. This configuration is activated by inserting a pulser that has Top Mount Pulser Ref selected in the Sensor Type column in the Probe Catalog.

The BHA for this example would look something like this:

In this configuration, the equation for finding the sensor offset is as follows:

The terminology used in the MWD Config dialog does not change, but when in a top mounted configuration, the following parts of the equation have different definitions:

UBHO = Although in reality the sub that the pulser is mounted in may have a different name, it is still referred to as the “UBHO” in the MWD Config.

Bit to UBHO = Bit to the Pulser Sub/Gap Sub. This collar is still referred to as the UBHO in the MWD Config dialog.

UBHO Pin to SS = Pulser Sub pin end to the mounting point on the Pulser Sub.

Sensor dist from bottom = The distance from the bottom of the pulser to the anchor point. The software will position the probe string inside the collars so that the anchor point on the pulser, and the mounting point on the pulser sub will line up. This is measured from the end of the pulser pointing towards the bit.

The diagram below illustrates the sensor offset calculation for a top mounted config:

Well Analytics How to Guide

A guide to the Analytics module in Well Seeker Pro

1.0 – Well Analytics Introduction

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:

1.1 - Search Tab

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:

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

1.2 - Map Tab

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).

1.3 - KPI (Key Performance Index) Tab

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:

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

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.

1.4 - KPI Reports 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.

Appendix A– Context Menu

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

Appendix B – Analytics Toolbar and Menus

B.1 – Well Analytics Toolbar

B.2 – Well Analytics File Menu

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.

B.3 – Well Analytics Database Tree Menu

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.

B.4 - Well Analytics Search Database Menu

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.

B.5 - Well Analytics Depth V Days Menu

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.

Torque & Drag Quick Start Guide

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.

1.1 - Setup

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.

1.2 - Required Inputs

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.

1.3 - Running the 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.

1.4 - Output

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.

1.5 - Drilling Charts

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.

1.5.1 - Drillers Hookload Chart

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.

1.5.2 - Drillers Torque Chart

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.

1.5.3 - Reaming Hookloads Chart

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.

1.5.4 - Reaming Torque Chart

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.

1.5.6 - Pipe Stretch Chart

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.

1.5.7 - Pipe Twist Chart

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.

1.5.8 - Apparent WOB Chart

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.

1.5.9 - Apparent OP Chart

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.

1.6 - Snapshot Charts

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.

1.6.1 - Tension Off Bottom SS Chart

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.

1.6.2 - Tension On Bottom SS Chart

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.

1.6.3 - Torque SS Chart

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.

1.6.4 – Side force SS Chart

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.

1.6.5 - Apparent WOB SS Chart

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.

1.6.6 - Apparent OP SS Chart

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.

1.6.7 - Casing Wear SS Chart

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.

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.

1.6.8 - Drill Pipe Fatigue SS Chart

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.

1.6.9 – Pressure Data SS Chart

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.

Oasis Integration Guide

A guide to integration with the Oasis ERP software by Merge Solutions, using Well Seeker Pro and the Innova Web Portal.

1.0 - Introduction

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.

This document assumes that Well Seeker Pro has already been installed (Installation Guide), and that the user is familiar with the daily reporting features (Daily Reporting).

2.0 - License

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.

If the Oasis Integration check box is empty, then the user will not be able to access these features and should contact [email protected] 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.

3.0 – Database Tree - Actual Well

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.

4.0 – Workflow Options

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

5.0 – Server Workflow

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.

5.1 – Web Portal Oasis Credentials

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.

5.2 – Web Portal Synchronize Job Data

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.

In order to synchronize a well’s Job Number and Rig details between Oasis and Well Seeker Pro, navigate to the Web Portal Wells List page, right click on the well of interest and select Get Oasis job info.

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.

5.3 – Web Portal Create a Daily Report

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.

5.4 – Web Portal Import Oasis Quote Costs

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.

5.5 – Web Portal Import Oasis Tools

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.

5.6 – Remote Data Fetch Well Data

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 link.

5.7 – Real Time Data Exchange

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.

5.8 – Daily Cost

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.

5.9 – Drill String Editor

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.

5.10 – 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.

5.11 – Data Transferred to Oasis Automatically

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.

6.0 – Local PC Workflow

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:
1. Export the cost data back to Oasis
2. Export the tool data for all BHA’s back to Oasis

6.1 – Well Seeker Pro Oasis Credentials

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.

6.2 – Well Seeker Synchronize Job Data

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.

6.3 – Oasis Quotes

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.

6.3.1 – Cost Codes

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.

6.3.2 – Daily Cost

The daily cost dialog is accessed from within the daily reporting interface by selecting View – Daily Costs.

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.

6.3.3 – Exporting Costs from Well Seeker 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.

6.4 – Oasis Tools

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.

6.4.1 – Inventory

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.

6.4.2 – Drill String Editor

The drill string editor is accessed by right clicking at Actual Well level and selecting Reporting – Drill String Editor.

6.4.3 – Performance Report

The performance report can be accessed via the drill string editor dialog, by selecting Performance Report – Edit Data.

6.4.4 – Pushing Tool data back 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.

7.0 – Additional Functions

7.1 – Transferring Tools Between Wells

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.

Web Portal Engineering Quick Start Guide

A guide to the Engineering page in the Innova Web Portal

1.0 - Introduction

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.

2.0 - Inputs

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.

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.

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.

2.1 - Case Details

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.

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.

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.

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.

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.

2.1.1 – Copying a Case or BHA from another well

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.

2.2 - Input Parameters

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.

2.2.1 - Drilling Parameters

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.

2.2.2 - Mud

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.

2.2.3 - Hydraulics

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.

2.2.4 - Advanced – Surge & Swab

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.

2.2.5 - Advanced – Hydraulics

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.

2.2.6 - Torque & Drag

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.

2.2.7 - Advanced – Torque & Drag

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).

2.2.8 - Tortuosity

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.

2.2.9 - Well Control

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.

2.2.10 – Casing Standoff

Currently the Casing Standoff module is not available. These inputs will have no effect on the calculation results.

2.3 - Input Tables

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 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.

2.3.1 - Flow Rates

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.

2.3.2 - Trip Speeds

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.

2.3.3 - Friction Factors

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.

2.3.4 - Kick Tolerance Limits

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.

2.3.5 - Wellbore

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.

2.3.6 - Drill String

The BHA chosen in the Case Details section will be displayed in the Drill String table for the well.

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.

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.

2.3.7 - Surveys

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.

3.0 – Results

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.

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.

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.

3.1 – Chart Controls Menu

Hover over the icon at the bottom right of each results chart to reveal the Chart Controls menu.

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:

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.

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.

3.2 – Hydraulics

Expand the Hydraulics section to access the Hydraulics results charts.

3.2.1 - Pump Pressure

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.

3.2.2 - ECD

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.

3.2.3 - ECD Snapshot

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.

3.2.4 - Surge & Swab

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.

3.2.5 – Tripping Speeds

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.

3.2.6 - Minimum Flow for Hole Cleaning

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.

3.3 – Torque & Drag

Expand the Torque & Drag section to access the Torque & Drag results charts.

3.3.1 - Drillers Hookloads

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.

3.3.2 – Calculated Friction Factors

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.

3.3.3 - Drillers Torques

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.

3.3.4 - On Bottom Tension Snapshot

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.

3.3.5 - Off Bottom Tension Snapshot

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.

3.3.6 - Side Force

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.

3.3.7 - Apparent WOB

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.

3.3.8 - Pipe Twist

3.3.9 - Pipe Stretch

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.

3.4 – Well Control

The Well Control section currently contains one results chart – the Kick Tolerance chart.

3.4.1 - Kick Tolerance

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.

3.5 – BHA Analysis

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.

3.5.1 – 2D Line Charts

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.

3.5.2 – 2D Contour Plots

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.

3.5.3 – 3D Charts

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.

3.5.4 – BHA Directional Tendency

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.

3.5.5 – BHA Critical RPM

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.

3.5.6 – BHA Mode Shapes

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.

WITS Setup & Remote Directional Drilling

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.

1.0 - Introduction

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.

2.0 – WITS

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.

2.1 - Serial WITS

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.

2.2 - UDP & TCP WITS

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.

3.0 – WITS Setup

The following section describes the recommended steps to follow and settings to select when setting up a WITS feed in Well Seeker.

3.1 – WITS Mapping

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.

3.2 – WITS Survey Options

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.

3.3– Rig States Settings

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.

3.3.1 – Rig States Logic

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?
1. Is (Bit MD – Hole MD) < On bottom threshold
If on bottom, are you drilling?
1. Pump Pressure > Threshold
2. WOB > Threshold
3. Hookload > Threshold
4. On bottom recorded when all 3 of the above are recorded = TRUE
If Drilling = TRUE, the logic is as follows
1. If 10% of the values in the RPM buffer are < Rotating threshold then Sliding
2. 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.

3.4 – WITS Data Reader

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.

3.5 – Required WITS Inputs

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.

STANDPIPE PRESSURE

MAGNETIC TF

TOTAL GPM

GRAVITY TF

BIT DEPTH

SURVEY MD

HOLE DEPTH

SURVEY INC

HOOKLOAD

SURVEY AZI

Block Position

Torque (Optional)

ROP (Optional)

4.0 – Remote DD Operations

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.

4.1 - Initial Rig Site Setup

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:

STANDPIPE PRESSURE

MAGNETIC TF

TOTAL GPM

GRAVITY TF

BIT DEPTH

SURVEY MD

HOLE DEPTH

SURVEY INC

HOOKLOAD

SURVEY AZI

Block Position

Torque (Optional)

ROP (Optional)

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.

4.2 - Transmitting Data to the Remote Server Database

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:

4.2.1 – Running the Operation Remotely

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

- 1. Open the Real Time Data Exchange, fill in ICDS server IP and Port number details and select the current well.
  2. 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.
  3. For this setup, the user does NOT need to Start the data exchange.

Remote Server Database User

- 1. Monitor incoming WITS feeds via the Rigs Online Dashboard and selecting File - Show WITS Connections.
  2. Set the Rig States Thresholds in the rig states dialog.
  3. Select the Auto Populate Slide Sheet radio button in the slide sheet toolbar. The WITS data populates the slide sheet and surveys.
  4. 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.
  5. 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).
  6. Based upon daily reporting data, KPIs and data analytics can be utilised in real time.

4.2.2 – Running the Operation Locally

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.

4.3 – Real Time Data Exchange

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:

4.4 – WITS Transfer

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.

4.5 – Auto Populate Slide Sheet

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.

5.0 – DD Dashboard

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.

5.1 - Settings

Within the DD Dashboard, the user can select from 4 different modes, which are accessed and selected via the settings menu:

No Mode
1. No additional features activated.
Vertical Mode
1. Red Tolerance Circle is drawn on the rose bud (diameter can be set in the settings).
2. 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.
3. Rotary walk and build can be set in the settings. Inc Rotary in Proj option must be selected for these to do anything.
4. If rotary is not included the additional projections will straight line and the rotary sections in the bit projection will also straight line.
5. 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
1. This mode does not currently do anything.
Curve Mode
1. No tolerance box or circle is displayed.
2. A new projection is calculated to the TVD INC AZI specified in the landing target section of the dashboard settings.
3. The user can use the drop-down list or the find landing button in the settings dialog to quickly find / adjust the landing target.
4. 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).
5. 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
1. 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).

Innova Technical Specification

1.0 – Introduction

Innova provides an industry leading integrated drilling software solution for well planning and engineering applications.

2.0 - Computer Requirements

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.

3.0 - Licensing

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.

4.0 – Innova Well Seeker Pro

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.

4.1 - Comprehensive Well Path Planning

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

4.2 - Anti-Collision Tools

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

4.3 - 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.

4.4 - 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.

4.5 - 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

4.6 - 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

Integration with BBGM Hypercube IFR
Integration with BGGM Error Estimates

4.7 - 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

4.8 - Import Compass Export Files

Includes the ability to import Compass Export files, including batch import, where multiple export files can be pulled in simultaneously.

4.9 – 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

4.10 - 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

4.11 - 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
- Footage Per Day by Operator and Rig
- BHA Reason Pulled Summary

4.12 - 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.

4.13 – WITS & Remote Directional Drilling

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

4.14 - 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
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

4.15 - Third Party Services Integration

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

4.16 – Innova Web Portal

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

4.17 – Innova App

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

4.18 - 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
Automatic updates
One-click license request and download

4.19 - 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

4.20 – Well Seeker Pro Capability Summary Table

4.21 - Benefits

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.

5.0 - Innova Engineering

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.

5.1 - Main features

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

5.2 - Torque and Drag Module

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.

5.3 - Hydraulics Module

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

5.4 – Survey Correction Module

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

5.5 - SAG Correction & BHA Analysis

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

5.6 – Magnetic Interference Calculator Module

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

5.7 – Casing Standoff & Centralizer Spacing Module

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.

5.8 - Jar Placement Module

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

5.9 – Cementing Design

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.

5.10 – Well Control

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

5.11 – Innova Engineering Capability Summary Table

Creating an Azure Database

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.

1.0 - Introduction

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.

2.0 - Getting Started

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.

2.1 - PuTTY

https://www.chiark.greenend.org.uk/~sgtatham/putty/
Download the 32-bit MSI.

2.2 - WINSCP

https://winscp.net/eng/download.php
During installation, select the Commander interface style.

2.3 - SQL server management studio (SSMS)

https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017
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.

4.0 - Create a Microsoft Azure Account

1. If you already have a Microsoft Azure account, ignore this section and go directly to section 5

2. Go to www.azure.microsoft.com

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

5.0 – Create an SQL Database

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.

6.0 - Connect to the Database

6.1 – Well Seeker Pro

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

6.2 - SQL Server Management studio (SSMS)

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.

7.0 – Create a Virtual Machine

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.

8.0 – Update SQL Server Firewall and Virtual Network Settings

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.

9.0 – puTTYgen

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.

10.0 - WinSPC

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.

10.1 – ICDS files

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.

11.0 – puTTY

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.

78. Follow the instructions on the following link to install node on the virtual machine: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-up-node-on-ec2-instance.html

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

11.1 - Useful puTTY Commands

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

12.0 – Well Permissions

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

13.0 – Testing ICDS Server Connection

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

14.0 – Setting up Final Network Security Rules

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:

14.1 – Virtual Machine Inbound Security Rules

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

14.2 – Virtual Machine Outbound Security Rules

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

15.0 – Troubleshooting Connectivity Issues

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.

15.3 – Real Time Data Exchange / Remote Data Fetch

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

15.4 – External Files Not Saving

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

Well Seeker X: How To Guide

1.0 - Getting Started

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.

1.1 - Display

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.

2.0 - Creating a new local database

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.

You can navigate to the file location of your database by opening in the Open Database Location icon in the bottom of the screen.

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.

3.0 - Switching between Databases

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.

4.0 - Creating a new Well

The following section details the steps to follow in order to create a new well.

4.1 - Unit Selection

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 bottom left of the screen or type ‘unit’ in the Search bar at the top right of the screen:

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/cm²
Volume: Current units for Volume. User can choose between BBLS and m³
Mud: Current units for Mud Weight. User can choose between PPG, SG, psi/ft³, lbs/ft³and Km/cm³
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 in² and mm².
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.

4.2 - New Instant Plan / Survey

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.

4.3 - New Operator

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.

4.4 - New Field

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.

4.5 - New Facility

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.

4.6 - New Well

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.

5.0 - Creating a new Well Plan

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

5.1 - Show / Hide Columns

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

5.2 - Creating a Target

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.

5.3 - Adding a Lease Line or Hard Line

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.

5.4 - Adding Casing Details

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.

5.5 - Adding Lithology Details

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.

5.6 - Adding Annotations

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.

6.0 - Creating a new Actual Survey

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.

6.1 - Adding a New Survey

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.

6.2 - Actual Wellbore

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

7.0 – Importing a Compass Export File

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.

8.0 - Creating a Slot Template

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.

9.0 - Adding a New Coordinate Reference System (CRS)

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.

10.0 – Charts

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.

10.1 - Offset Selector

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.

10.2 - Chart Properties

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.

10.3 - Chart Zoom and Chart Scales

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.

10.4 - Grid Lines

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.

10.5 – Plot Defaults

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.

11.0 – Wall Plot Composer

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.

11.1 - Saving a WPC Template

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.

11.2 - Table Text and Logo Size

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.

11.3 – Alignment

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.

11.4 - Screen Zoom

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.

Appendix A – Well Planning Tools

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:

A.1 – Adjust

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.

A.2 - Build / Turn

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.

A.3 -Dogleg Tool Face

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.

A.4 – Hold

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

A.5 – Optimum Align

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.

A.6 – 2D Planning

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.

S-Well

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.

Slant Well

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.

Recommended Job Startup Procedure

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 Well Seeker Manual.

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

Office -Pre-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.

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: EDM Import Function Update

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.

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 this page for a guide to tying your well onto its mother bore. After checking your inputs, click on Apply and then Close.

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.

Rig Site – Pre-Job Steps

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.

If you do not see any circles to select your well in the list, refer to this technical note.

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.

Rig Site – WITS Setup

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.

Rig Site – Drilling Operations

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.

The DD dashboard contains the following sections. For a detailed breakdown of these sections, refer to the Well Seeker Manual:

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.

Office – Monitoring Drilling Operations

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 contains the following sections. For a detailed breakdown of these sections, refer to the Well Seeker Manual:

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.

Rig Site – End Of Well Steps

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.

9. Steps 10 - 18 detail how to perform a QA & QC check on the daily reporting in the well. Follow this link for an in depth video guide on the below steps. Before starting, it is recommended to back up your database by opening the File menu and selecting Backup Database.

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.

Office – Post-Job Steps

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 this link for an in depth video guide on quality control for the reporting data.

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.

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.

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.

How To Guide

This guide introduces the user to Well Seeker Pro from the point they first open the software after installation.

1.0 - Getting Started

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.

1.1 - Display

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.

2.0 - Creating a new database

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.

3.0 - Switching between Databases

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.

4.0 - Creating a new Well

The following section details the steps to follow in order to create a new well.

4.1 - Unit Selection

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.

4.2 - New Instant Plan / Survey

To create an instant plan or survey, right click on the database and select New Instant Plan or New Instant Survey.

4.3 - New Operator

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.

4.4 - New Field

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.

4.5 - New Facility

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.

4.6 - New Well

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.

5.0 - Creating a new Well Plan

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.

5.1 - Show / Hide Columns

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

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.

5.2 - Creating a Target

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.

5.3 - Adding a Lease Line or Hard Line

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.

5.4 - Adding Casing Details

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.

5.5 - Adding Lithology Details

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.

5.6 - Adding Annotations

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.

6.0 - Creating a new Actual Survey

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.

6.1 - Adding a New Survey

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.

Once the survey has been entered, hit 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.

6.2 - Actual Wellbore

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

7.0 – Importing a Compass Export File

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.

8.0 - Creating a Slot Template

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.

9.0 - Adding a New Coordinate Reference System (CRS)

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.

10.0 - Wall Plot Composer

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.

10.1 - 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.

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.

10.2 - Chart Properties

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.

10.3 - Chart Zoom and Chart Scales

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.

10.4 - Grid Lines

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.

10.5 - Saving a WPC Template

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.

10.6 - Table Text and Logo Size

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.

10.7 – Alignment

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.

10.8 - Screen Zoom

This option is also available on the quick access toolbar along the top of the WPC screen.

10.9 – Plot Defaults

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.

Appendix A – Well Planning Tools

When viewing a plan, the well planning tools will be displayed at the bottom of the window.

A.1 – Adjust

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.

A.2 - Build / Turn

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.

A.3 -Dogleg Tool Face

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.

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

A.4 – Hold

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

A.5 – Optimum Align

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.

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.

A.6 – 2D Planning

S-Well

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).

Slant Well

Well Seeker X: Job Startup Procedure

1.0 - Introduction

The following document details the recommended procedures to follow in Well Seeker X 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.

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

2.0 - Office -Pre-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.

2.1 – Company Setup

The data detailed in this section is relevant to all items in your server database. You will enter this data once, and only revisit these dialogs when an update is required. When the DD/MWD Engineers in the field download data from the server, the information entered in this section will be included, and will be available for them as they begin to fill in their daily reports.

Before entering any data in Well Seeker X, check that you are using the correct unit set by clicking on the Select button in the Settings ribbon.

Select your unit set using the dropdown box at the top of the dialog, and confirm by clicking on Apply.

Log onto the SQL server database by clicking on the Server button in the Home ribbon.

Once you have logged in, select the Admin ribbon and select Personnel Names.

In the Personnel Details window, update the list of commonly used field personnel. 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. These names will then be available to select from a dropdown list in the Daily Reporting.

In the Admin ribbon, select Rig Names.

In the Rig Names window, update the list of rigs that your organization operates on. Ensure that as a minimum, the rig being used in the upcoming job is present in the list and is selected as Active. Once you are satisfied, click on the Apply button and then Close. These rig names will then be available to select from a dropdown list in the Daily Reporting.

Open the Home ribbon and select Addresses.

In the Addresses window, enter any relevant addresses. 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 as they will be available via a dropdown menu. Once you are satisfied, click on the Apply button and then Close.

Select the Tools ribbon and then click on MWD Probes to open the Probe Catalog. Enter the details of the M/LWD probe types used by your organization.

Select the Templates option within the Probe Catalog to open the MWD Probe Templates dialog. Where appropriate, Add any templates, name them appropriately and save. This data will allow the MWD Engineer in the field to select commonly used probe configurations and automatically calculate sensor offsets.

2.2 – Phase & Activity Codes

Phase and Activity codes are a very important part of the Daily Reporting package, and are selected at Operator level in the Object Explorer. While not recommended, this means that if required, it is possible to utilize different phase and Activity codes across different Operators. This data should only be entered once per operator.

This section assumes that at least one operator exists in the Object Explorer tree. If the relevant Operator is not displayed in the tree, please refer to section 2.3.

If you are not already logged into your server database, do so by clicking on the Server button in the Home ribbon, and then log in with your username and password.

Click on the operator, or any level in the object explorer under the operator, and then select Codes in the Home ribbon. From the dropdown box, select Activity Codes.

In the Activity Codes window, verify the activity codes are correct. Any changes to the codes here will apply to all wells under the current operator. Once you are satisfied, click on the Save icon and close the window.

NOTE: It is best practice to use the same Activity Codes and Phase Codes for every operator in your organisation’s server database. This will make KPI analysis easier. Refer to the following video for more information regarding this: Choosing Phase and Activity Codes

Click on the operator, or any level in the object explorer under the operator, and then select Codes in the Home ribbon. From the dropdown box, select Phase Codes.

In the Phase Codes window, verify the phase codes are correct. Any changes to the codes here will apply to all wells under the current operator. Once you are satisfied, click on the Save icon and close the window.

2.3 – Creating the Well Plan

While everything in the Object Explorer can be created and entered manually by the user, it is also possible to import Compass EDM files, which will automatically populate all levels of the tree. This section details both the Compass Import process and the process of creating everything from scratch.

2.3.1 – Importing from Compass

When creating a Compass export for an upcoming well, it is recommended that in addition to the plan, the well planner also includes all offset wells, and a blank survey for the well which is going to be drilled. Including this blank survey ensures that everything is setup correctly by the well planner and means that all the DD needs to do is start entering the surveys as they are taken.

Review your Compass import settings.

Select Import Compass EDM file.

Select the correct Compass export file to import. You may notice that your object explorer contains slightly different names when imported into Well Seeker, compared to the original Compass file. This is because Well Seeker requires names in the object explorer 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: EDM Import Function Update
If the Operator already existed in the database, check that the well plan and offsets have correctly imported into the existing operator. If they did not, this is because the operator name in the Well Seeker database and the operator name in the import file are not exactly the same.
Make sure that your principal well plan has been correctly designated. Right click on the well plan and select Properties.

In the Plan Properties window, check the Set as Principal Plan checkbox and click Apply, then Close.

2.3.2 – Creating from Scratch

This section details the steps required to create a well plan when there is no existing data in the database. If an Operator, Field, Facility or Well Already exists, then the user can skip to the relevant part of this section.

Right clicking on Well Seeker Database in the Object Explorer section and select Insert New Operator.

In the Operator Properties window, enter the operator name and select a logo. You can also set up the anti-collision rules. These rules will apply to all wells stored under this operator. Click Apply and the close.
Right click on the operator and select Insert New Field.
In the Field Properties window, input the field name, select the co-ordinate reference system, and enter a reference location for the field. You can also change the system vertical datum, but note that this defines where 0 TVD subsea is, so should almost always be left as MSL. After checking your inputs, click on Apply and then Close.

Right click on the field and select Insert New Facility.

In the Facility Properties window, input the facility name, select the north reference, and enter a location for the facility. After checking your inputs, click on Apply and then Close.
Right click on the facility and select Insert New Well.
In the Well Properties window, input the well name, the wellhead surface location, and set up the depth reference. After checking your inputs, click on Apply and then Close.
Right click on the well and select Insert Planned Well.

In the Plan Properties window, input the plan name, vertical section, magnetics and depth reference details. If your plan is a sidetrack, refer to our Sidetrack Guide for tying your well onto its mother bore. Lastly, designate the plan as the principal plan for the well by checking the Set as principal plan checkbox. After checking your inputs, click on Apply and then Close.
In the Object Explorer, double click on the Well Plan level to open it. Use the planning tools to create your well plan, then click on Save in the Home ribbon.
Right click on the well plan and select properties. In the Plan Properties window, assign a survey error model using the IPM column in the Survey Program Section. Click on Apply and then Close.

2.4 – Creating the Actual Well

After creating the principal plan for the job, you should set up the actual well for the directional driller. If the plan has been imported via a Compass EDM, it is highly recommended that an Actual Well is included as it will remove the requirement to create this manually in Well Seeker.

Right click at well level and select Insert new actual well.
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 our Sidetrack Guide for tying your well onto its mother bore. After checking your inputs, click on Apply and then Close.
Right click at actual well level and select Insert new survey.
Input and check survey name, tie on details and select survey instrument/IPM. After checking your inputs, click on Apply and then Close.
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.
Now click on the Select Offsets icon in the Home ribbon.
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 activating them in the Filters section. Once you have selected the desired offsets, click on Apply and then Close.
1. Note: If you have a plan in your database which is not showing in the below tree, it may be because the plan has been selected as Complete in the Plan Properties. Uncheck this option to see the plan if required.
2. This is an important step because when the field engineers pull this well from the server, they can choose to also pull the offset wells. Correctly selecting the offset wells at this stage, ensures they will pull all the required offsets when the job starts.
Click on an item in the object explorer at Well level or below. In the Home ribbon, select Codes. From the dropdown box, select Cost Codes.
In the Cost Codes window, enter the cost codes for the well. Once you are satisfied, click on Apply and Close.
1. NOTE: These Cost Codes will feed the Daily Costs, which means the field engineer will choose these options from a drop down menu and will not need to enter them manually each day.
Click on an item in the object explorer at actual well level or below, and then click on the Job Data button in the Home ribbon.
In the Well Details 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 2.1 Company Setup and update the Personnel Details. Select the Rig from the dropdown menu. If the desired rig is not available, go back to 2.1 Company Setup and update the Rig Names. Fill in any other required fields, in particular the Job# and API# if known. Click on the Apply button and then close the window.

NOTE: The Well Status must be set to Upcoming, Standby or Active in the server database, or the field engineers will not be able to push updates during rig operations to the server.

Click on the actual well in the object explorer, and then click on the Daily Reports button in the Home ribbon.
Select the Settings ribbon and select Default Activity. This option sets the activity and comment that will be used to fill in time gaps when the Slide Sheet sends updates to the Daily Report. Usually this will be survey and connection time, so pick an activity that represents that.

Right click on the actual well and select External Files.

In the External Files dialog, 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.

3.0 - Rig Site – Pre-Job Steps

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.

Open Well Seeker.
If you use a single database to store all of your wells, select it by opening the Home ribbon and click on Select. If not, create a new blank database by opening the Home menu and click on New. After you have created your new database, you will need to select it using Select.
You can confirm your currently selected database by checking the path displayed on the status bar at the bottom of your Well Seeker window.
Use the Remote Data Fetch tool to pull down your job from the server database. Open the Home ribbon and select Fetch in the Data Exchange section.
In the Data Fetch window, the ICDS Server and Port should already be filled with your companies details. If not, you are likely using the incorrect license, and should contact your company administrator. Click on the Connect button.
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.
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.
Select the actual well for your job from the list by clicking on the checkbox, then click on the Fetch Data button. When the download is complete, the message box should display the message Data Fetch Complete! Your object explorer should now be populated with the relevant wells and you can now close the window.
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.
Right click on the well plan and select Properties. Check that all of the information is correct, and then click on Close.
Double Left click on the well plan to open it. Check that the well plan matches the well planning report.
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.
Click on the actual well in the object explorer, and then click on the Inventory button in the Home ribbon.
Fill in the inventory with the tools that you have on location. When you are finished, click on the Save button and then close the window.
Click on the actual well in the object explorer, and then click on the Drill String button in the Home ribbon.
In the Drill String Editor window click on the Add New BHA icon in the toolbar. In the newly created BHA, input the BHA description and BHA number. MWD number, mud weight and target formation can also be entered if you have that information.

At least one BHA component must be entered before the BHA can be saved.

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, you can manually fill in the component details or select Insert from Catalogue. This will allow you to insert components from a list of generic tools, which can then be edited as required.
After inserting a component, fill in the necessary Component Properties on the right.
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 required.
Click on the Surface System icon to open the MWD Surface System dialog. Enter the serial numbers for your surface system components. If you recorded your surface system items in the Inventory, they will be available here as dropdowns. If not, you will need to enter them manually. When you are finished, click Apply and then close.
Click on the MWD Probe Config icon to open the MWD Config dialog. Use the controls to build the probe config using items in the catalog section, or select from the probe config dropdown menu to select a probe configuration. The automatically calculated sensor offsets will display in the Sensor Offsets section. When you click on the Apply button, the sensor serial numbers and sensor offsets will be added to the component properties of the MWD/LWD component.
1. Note: If the probe catalog has not been set up on your organization’s remote server you will not be able to use this dialog, and must manually enter the MWD sensor information into the MWD/LWD component properties.
Click on the Save icon and then close the Drill String window.
Click on the actual well in the object explorer, and then click on the Job Data button in the Home ribbon.
Confirm the data filled in here by the office. Make sure that the Job # and Rig fields have been filled in. Other fields are optional. Set the Well Status to Active. Then click on Apply and close.
Click on the actual well in the object explorer, and then click on the Daily Reports button in the Home ribbon.

Click on the Add button in the Home ribbon to create your first day, or if it already exists, adjust the date using the date selector.
Click on the Personnel icon in the home ribbon.
Select the personnel working at the rig site, and enter their time on/off. At a minimum, select the Day/Night DDs and MWD Engineers. After entering the information, click on Apply and then close.
If you wish to add pump information, you can add it by clicking on the Pumps button in the Home ribbon. After entering the pump data, click on Apply.
Click on the Costs button in the Home ribbon. Enter the charges for the day using the dropdown menu in the Description column. Enter the quantity and if applicable, select an associated BHA. If the SN Dropdown option is checked, the SN cell will provide a dropdown list with the SN of all tools in the inventory. After entering the charges, click on Apply.
Open the Settings ribbon and select Default Activity. Double check that the office have set the correct default activity code. 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.
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.

3.1 – Set Up Data Exchange

All rigs should send data back to the server database. Well Seeker X has two methods of transmitting data from the rig back to the server database – Data Sync and the Real Time Data Exchange. If your organisation has set up the Data Sync, you should use that method. Otherwise, use the Real Time Data Exchange.

3.1.1 – Data Sync

If your organisation has set up the Data Sync, there is minimal setup required at the rig. For the data sync, the following needs to be in place at the rig site:

You must be using a license that is registered to your organization. For most users this will already be the case.
You must have an active internet connection.
The well that you want to sync must have exactly the same object explorer naming structure on both the local computer and your organization’s remote server database. This includes Operator, Field, Facility, Well and Actual well name. If you used the Data Fetch to pull the well information from the server then this will be the case.

Once these three criteria are met, the local database will automatically start to sync with the server database whenever you click on save or apply in a dialog. The status of the Data Sync is displayed in the bottom right corner of the main interface:

The Data Sync can be temporary disabled by toggling the Offline option in the Home ribbon:

For a more detailed explanation of the Data Sync, see the following tech note: Data Synchronization Feature Update | Innova Drilling & Intervention

3.1.2 – Real Time Data Exchange

Unlike the Data Sync, the Real Time Data Exchange must be manually set up and started by the DD/MWD at the rig site.

In the Daily Reports window, click on the Data Exchange icon in the Home ribbon.

If you are in the main Well Seeker interface, click on the Push button in the Home ribbon.

In the Data Exchange dialog, select the current job by checking the checkbox in the Select column. If your well is not showing in the list, go back to Step 24 in section 3.0 and set the well status to Active.
In the ICDS Server section the ICDS Server Address and Port should already be filled with your companies details. If not, you are likely using the incorrect license, and should contact your company administrator.
In the Select Data section, select the data that you wish to push back to the server. At a minimum, select Daily Reports. Survey data is always pushed. For other selections, discuss with your coordinator.
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.
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.

3.2 – WITS Setup

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.

In the main Well Seeker interface, open the Settings ribbon and select WITS under the Mapping section. Make sure that the RECORD_ID and FIELD_ID match with the incoming WITS data. When you have finished, click on Apply. Note: If you are using SoloBox or RigSense at the rig site you can skip this step.

The rest of the WITS options are found in the slide sheet. In the object explorer, double click on the survey for the job to open it. Then click on Slide Sheet in the Home ribbon.
In the slide sheet window, open the Serial/TCP WITS dialog by clicking on Serial/TCP in the WITS section of the Home ribbon.
Choose your WITS settings depending on the method of input:
1. If you are using a serial cable, select your comm port in the Serial WITS Settings section.
2. If you are using an ethernet cable, select your input type, port and IP address in the Ethernet WITS settings.
3. If you are using SoloBox or RigSense at the rig site to receive your WITS data, toggle the respective checkbox in the Options section. This will automatically configure your WITS settings and mappings for you.
Click on Start Reading. You should see data coming through in the WITS Data Stream section. Use the WITS Status section to monitor the health of the WITS feed.
It is also possible to send data back to the server. In the Server Data Sync section , the IP and Port should already be filled with your companies details. If not, you are likely using the incorrect license, and should contact your company administrator. Check the Send Data box to begin pushing data back to the server. The WITS Status section will indicate if the last push to the server was successful.
Minimize the WITS Comms window. Do NOT close it, as this will stop the incoming WITS data.
In the Rig States section of the ribbon, click on the Settings button to open the Rig States configuration dialog.
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. Refer to the Rig States Guide for more details information.

You can also set Auto Thresholds to YES. This will cause Well Seeker to dynamically adjust the hookload and RPM values based on incoming data. Note that the hookload will only be adjusted down, based on connection data.

Minimize the Rig States window. Do NOT close it.
In the slide sheet window, make sure that the correct BHA is selected in the drop down box. Click on the green Start icon in the Rig States section of the ribbon. 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 icon in the Rig States section of the ribbon. Remember to Save regularly using the save icon.
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.

4.0 - Rig Site – Drilling Operations

The steps below detail some of the tools available to the DD and MWD Engineers during drilling operations, as well as recommended procedures for filling in and performing quality control on your reporting data.

In the Daily Report dialog, 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 will be automatically transferred from the slide sheet to the daily report whenever the slide sheet is saved, as detailed in Step 9, below.
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 displayed in the survey grid, they can be activated using the Show/Hide option in the Settings menu.
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.
Plots can be viewed when a survey or plan is open. Open a plot by clicking on its icon in the Charts section of the Home ribbon.
When viewing a plot, offset wells/plans can be toggled on or off by clicking on the Show Offsets icon on the Home ribbon. The selected offsets can be edited by clicking on the Select Offsets icon just above the Show Offsets button.
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 similar planning tools as the well plan. Both of these windows can be left open while working in other parts of the software. Access them in the Bit Projection section of the Home ribbon.
The Real Time Anti-Collision (RT AC) dialog can be accessed when viewing a survey. Open it by clicking on the Real Time button in the Home ribbon. The RTAC will display the anti-collision results for all selected offsets, the principal plan and any lease lines/hard lines.
The Directional Drilling (DD) Dashboard collects data from multiple sources within Well Seeker and displays them in one interface, allowing the Directional Driller or an RTOC to monitor drilling operations from a single screen. It is accessed via the Slide Sheet dialog by clicking on the DD Dashboard icon in the Tools section of the ribbon.

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 with different configurations, but this can be taxing on your computer’s CPU and memory.

The DD dashboard contains the following sections. For a detailed breakdown of these sections, refer to the Well Seeker Manual:

Toolface rose displaying details of the current 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.
Drilling recommendations

Whenever you click on Save in the Slide Sheet, the program will automatically push drilling activity recorded in the Slide Sheet to the relevant day in the Daily Report. NOTE: Drilling activities populated via the slide sheet cannot be edited in the Daily Report; if you need to make changes you must do so in the Slide Sheet and click on Save to update the DDR.

Any gaps in drilling activity will be filled in with the default activity code, but can still be edited if required. This default can be set by clicking on the Default Activity icon in the Settings ribbon in the Daily Report window.

Fill in the Daily Data and Mud Data sections on the right hand side of each Daily Reports window. Update the Personnel dialog with any changes.
Click on the Costs icon in the Home ribbon in the Daily Reports window to open the Daily Costs dialog. Enter the relevant cost data for the day, and click on Apply to save your changes.
At the end of each day, it is recommended to QC your Daily Report. Daily activities will be highlighted in red if:
1. The start time of an activity does not match the end time of the previous activity.
2. The start depth of an activity does not match the end depth of the previous activity.
3. The user changes BHA without a 6O/6P activity.
4. There is more than 1 6O/6P activity for any single BHA
5. A phase or BHA has been chosen that does not match the phase or BHA of the activities above and below it.
6. Any code 8 or 26 are selected. These represent NPT and will flag red, even though there is no error.

The top right corner of the Daily Reports window contains the Data Validation section. The #Errors field displays the number of errors found on the current day. The Prev and Next options can be used to quickly scroll through errors, and Desc field gives a description of the currently selected error.

In addition, you should check:

g. The depth at the start of the day is correct.

f. All activity codes are correct.

i. The first activity for a BHA should be 6O and the last should be 6P. If no BHA is in the hole, the BHA field should be blank.

j. Every activity has a phase assigned to it.

It is also recommended that you backup your database at least once a day. In the main Well Seeker interface, open the Home ribbon and select Backup in the Database section. This will let you save a backup copy of your database. It is recommended that you never overwrite an existing backup when you do this. Always create a new backup file.

In the Daily Reports window, print your Daily Report in either Excel or Pdf format by clicking on the Print DDR buttons in the Home ribbon.

You can configure what is included in the DDR by opening the DDR Options ribbon and toggling the options in the Options section. Other reports can be added to the DDR as attachments in the Additional Reports section.

You can create a morning report by clicking on the arrow below the EOWR option and selecting Morning Report Package. The package contains the following:

a. A copy of the database. This is optional and if not required can be omitted via the settings tab in the ribbon.

b. An Excel format EOWR up to the current day.

c. An email template containing a summary of the current status of the well.

The morning report is treated like an EOWR. Its contents can be configured using the options in the EOWR Options ribbon.

At the end of a run you should fill out the Run Data for the BHA. Open the Drill String Editor, select the current BHA and click on the Drilling icon in the Run Data section of the ribbon.
Choose the reason for POOH in the Reason dropdown. Make any general comments on the run in the Comments section, and fill in the Run Data section if necessary.
If there was a tool failure, check the Failed check box. This will activate the other sections where you can record details of the failure. In the Incident Type section select the BHA Component that caused the failure. If the component was a motor, MWD or RSS, check the relevant checkbox as well. Check the Trip for Failure or LIH (Lost in Hole) boxes if necessary. In the comments boxes below, enter relevant details of the failure, and any NPT the failure caused.
Click on Apply and then close the Drilling Data dialog.
If MWD was present in the string, click on the MWD icon in the Run Data section of the ribbon.
In the MWD Run Data window, fill in the Run Information, Tests and Setup sections. If there was an incident with the MWD, check the MWD Incident checkbox. This will enable you to enter details in the other sections. Click Apply to save your changes and then close.
Save your BHA and then create the BHA for the next run by clicking on the Add BHA icon. If required, you can also click on Duplicate 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.

5.0 - Office – Monitoring Drilling Operations

For monitoring drilling operations from the office, the best option is to use the Innova Portal. The tools introduced in the steps below require the rig site to be pushing data using the Real Time Data Exchange or Data Sync. The EDR also requires the WITS feed from the rig to be pushed to the server.

Open your internet browser and navigate to one of the below websites based on your servers geographic location:
1. USA: www.icpwebportal.com.
2. Europe: https://eu.icpwebportal.com/
3. UAE: https://uae.icpwebportal.com/
Log in with your username and password.

The Wells List page displays all of the wells in your server database. Filter the Status column to Active to display only the wells currently being drilled. The Wells List page displays some drilling information for each well. If the field is pushing survey/reporting data to the server via the data exchange or data sync, the last time an update was sent is listed in the DEX column. If the field is forwarding WITS data from the rig to the survey, the last time the server received an update is listed in the WITS column.
In the Wells List page, click on your desired well in the Well column to select it. The name of the selected well will appear at the top of the screen, and your browser will move to the Well Details page. Now you can expand the Well Views option on the sidebar menu, which will give you access to detailed information on the well.

The following steps describe some of the more useful Well View pages.

The Daily Reports page allows you to view the daily reports for the well. The bottom half of the page displays a summary for each day, showing drilling progress, cost overview and activity overview. Clicking on the > icon to the left of a day will expand it to display the daily activities in detail. The top half of the page displays the Depth v Days, Phase Footage, Phase Hours and Phase ROP charts. Hover over the left or right hand sides of the charts to display the < and > icons that allow you to cycle between each one.

Click on the icon beside a day to print the report for that day, or click on the icon in the bottom right to print all days in one report.

The Surveys page allows you to view the currently recorded surveys for the well. The top half of the page displays the 3D plot, section and plan view charts for the well. Hover over the left or right hand sides of the charts to display the < and > icons that allow you to cycle between each one. Hover over the icon to change chart settings.
On the Surveys page, click on the Real Time AC tab to the right of the survey listing to display the real time anti-collision results for the well. This will automatically update every time data is pushed from the rig site.
The Drill String page contains details of every BHA created for the well. Clicking on the > icon to the left of each will expand it to display its components. Click on the icon beside a BHA to print a BHA or performance report.
The EDR (Electronic Data Reader) page allows you to view drilling parameters from the rig site in real time. It also uses the drilling parameters to create a record of the rig state.

The EDR requires the rig site to be sending WITS data to your organisation’s server database. It also requires a data store to be set up for the well in the Portal. When the DD/MWD first start sending data, the Portal will do this automatically. For a more detailed guide on setting up the data store and configuring the EDR, see the following guide: Web Portal Data Acquisition and EDR Guide | Innova Drilling & Intervention

The Anti-Collision Dashboard is accessed from the left hand menu and displays all active wells in the database. This allows the user to monitor company wide anticollision in one dashboard. This dashboard is updated in real time any time new data is pushed from the field.

6.0 - Rig Site – End Of Well Steps

Once drilling operations have finished, follow the below steps to QA & QC your reporting data and close out the well.

Finish recording daily data, mud data, personnel and costs 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.
Save and close your slide sheet.
Save your surveys. Open the Actual Well Properties and check that the survey program is updated down to TD.
Once you have finished prepping your tools for backload, click on the actual well or below in the object explorer, and then click on the Inventory button in the Home ribbon.

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.

Click on the actual well or below in the object explorer, and then click on the Shipping Ticket button in the Home ribbon.
Create a new ticket by clicking on the Add 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.
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 Select Ready for Backload button.
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.
Steps 10 - 13 detail how to perform a QA & QC check on the daily reporting in the well. Follow this link for an in depth video guide on the below steps. Before starting, it is recommended to back up your database via the Home Tab and selecting Backup in the Database section.
Right click on the actual well and select Reporting >> Daily Activity Editor. The Daily Activity Editor displays all activities for the job in one continuous table, making it easy to check for errors. Any errors that the software has detected will be highlighted in red and listed in the Validate section. You can scroll through the errors using the Prev and Next buttons.

Check for the following:

a. Time Gaps – The start time of every activity should match with the end time of the previous activity.

b. Depth Gaps - The start depth of every activity should match with the end depth of the previous activity.

d. Phases – Every row should have a phase selected.

Once you have completed these checks, click on Save and then close the window.

In the object explorer, double click on one of the surveys for the job to open it Then click on Slide Sheet in the Home ribbon.

For each slide sheet in the well, check through your drilling parameters to make sure that there have been no typos or mistakes.

Make sure the RPM is zero for all slide activities where there is no pipe oscillation.

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 Settings ribbon in the main interface and click Select in the 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.

Once you have finished QC’ing the Daily Report, you should make sure that all of your Run Data is filled in. Click on the actual well in the object explorer, and then click on the Drill String button in the Home ribbon.

Select a BHA and click on the Drilling icon in the Run Data section of the ribbon.

Check the Drilling Data dialog for every BHA in the well. For each BHA check that:

a. A reason for POOH has been selected.

b. Comments have been filled in.

c. If the BHA had a failure, make sure that this has been recorded.

Repeat the process for the MWD run data. When you have finished checking the drilling and MWD run data for each BHA, Save and close the Drill String Editor.
You can now print your End of Well Report. In the Daily Reports window, open the EOWR Options ribbon. Toggle the checkboxes to choose which reports and charts are included in the EOWR.
In the Daily Reports window, return to the Home menu and click on the arrow below the EOWR button. Print the EOWR in your desired format by selecting Print EOWR Excel or Print EOWR pdf.
Right click on the actual well in the object explorer and select External Files. Add any relevant documents, such as the EOWR and the shipping ticket.
Click on the Job Data button in the Daily Reports Home ribbon. Set the well status to TD or whatever your company has designated the Well Status should be once the well has been TD’d and the data has been validated. Click on Apply and close. Save and then close the Daily Reports window.
If you are using Data Sync to send updates to the server, it will have sent the last update when you clicked on Apply in the previous step. However, if you are using the Real Time Data Exchange, you should manually push the last update to the server. In the main Well Seeker interface, click on the Push button in the Home ribbon.

Click 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.

NOTE: Pushing your data to the server after changing the status to TD will prevent you from pushing any further changes afterwards.

7.0 - Office – Post-Job Steps

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 should have already performed some of these steps during their End of Well procedure. Follow this link for an in depth video guide on quality control for the reporting data.

Verify that the bottom line of the actual wellbore matches with the well plan, and that the actual well survey program is complete.
Right click on the actual well and select Reporting >> Daily Activity Editor. The Daily Activity Editor displays all activities for the job in one continuous table, making it easy to check for errors. Any errors that the software has detected will be highlighted in red and listed in the Validate section. You can scroll through the errors using the Prev and Next buttons.

Check for the following:

a. Time Gaps – The start time of every activity should match with the end time of the previous activity.

b. Depth Gaps - The start depth of every activity should match with the end depth of the previous activity.

d.Phases – Every row should have a phase selected.

Once you have completed these checks, click on Save and then close the window.

In the object explorer, double click on one of the surveys for the job to open it Then click on Slide Sheet in the Home ribbon.

For each slide sheet in the well, check through your drilling parameters to make sure that there have been no typos or mistakes.

Make sure the RPM is zero for all slide activities where there is no pipe oscillation.

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.

Once you have finished QC’ing the Daily Report, , you should make sure that all of your BHA performance reports are filled in. Click on the actual well in the object explorer, and then click on the Drill String button in the Home ribbon.

Select a BHA and click on the Drilling icon in the Run Data section of the ribbon.

Check the Drilling Data dialog for every BHA in the well. For each BHA check that:

a. A reason for POOH has been selected.

b. Comments have been filled in.

c. If the BHA had a failure, make sure that this has been recorded.

Repeat the process for the MWD run data. When you have finished checking the drilling and MWD run data for each BHA, Save and close the Drill String Editor.
You can now print your End of Well Report. In the Daily Reports window, open the EOWR Options ribbon. Toggle the checkboxes to choose which reports and charts are included in the EOWR.
After all data QC has been completed, click on the Job Data button in the Daily Reports Home ribbon. Set the well status to Verified or Complete or whatever Well Status your company policy specifies at this point. Click on Apply and close. Save and then close the Daily Reports window.

Managing an AWS Database

A guide to managing an AWS account, including additions and changes relating to Well Seeker Pro.

1.0 - Introduction

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.

2.0 - Getting Started

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.

2.1 - PuTTY

https://www.chiark.greenend.org.uk/~sgtatham/putty/
Download the 32-bit MSI

2.2 - WINSCP

https://winscp.net/eng/download.php
During installation, select the Commander interface style

2.3 - SQL server management studio (SSMS)

https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017
Installation of SQL Management Studio can take a while, which is normal and expected.

2.4 - Google Authenticator App

In addition to installing the above programs on your computer, install the Google Authenticator App on a suitable mobile phone.

3.0 – Adding a New Database

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.

4.0 – Setting up an additional ICDS Server

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.

4.1 – WinSPC

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

4.2 – ICDS Server and .json Files

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

4.3 - PuTTY

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

4.4 – EC2 Security Rules

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.

6.0 – Creating Additional Well Seeker (WS) Users

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

7.0 – Updating the ICDS executable version

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

8.0 – Restoring an SQL database from a backup

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

8.1 – Complete Database Restoration Process

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

8.2 – Partial Database Restoration Process

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

SQL SELECT Statement (w3schools.com)

9.0 – Storing WITS data on a second database

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

10.0 – Only Push Data to Active Wells

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

11.0 – Lock the Database Version

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

12.0 – Editing AWS Security Rules

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.

12.1 – RDS

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

12.2 – EC2

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

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

13.0 – Uploading a Local Database to the Server

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

14.0 – Server Database Latency Optimization

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

15.0 – Well Permissions

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.

16.0 – Storing external files on an Amazon S3

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

17.0 – Backup and Restore an EC2’s Data

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.

17.1 – AWS Console – Create Volume Snapshot

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

17.2 – AWS Console – Restore the Volume Snapshot

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

18.0 – Troubleshooting Connectivity Issues

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.

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

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.

18.3 – Real Time Data Exchange / Remote Data Fetch

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

18.4 – External Files Not Saving

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.

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

Appendix C – configICDS.json

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

Appendix D – Restarting the ICDS Server

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

Appendix E – Useful PuTTY Commands

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

6.4 - Tools Menu

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.

6.4.1 – Unit Sets

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.

6.4.2 – Geo Mag Calculator

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.

6.4.3 – Survey Tool editor

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.

6.4.4 – Interpolate

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.

6.4.5 – Anti-Collision Settings

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.

6.4.6 – Directional Difficulty Index (DDI)

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)

6.4.7 – Offset Selector

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.

6.4.8 – Wall Plot Composer

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.

6.4.8.1 – File 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

6.4.8.2 – Insert Menu

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.

6.4.8.3 – WPC Tools Menu

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.

6.4.8.4 – WPC View Menu

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.

6.4.9 – Slide Sheet

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.

6.4.10 – Projection Tools

The Projection Tools submenu contains a number of tools that allow the user to project ahead of the currently active survey sheet.

6.4.10.1 – Multi Project

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.

6.4.10.2 – Project Ahead

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.

6.4.11 - Dashboards

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.

6.4.11.1 – RT Anti-Collision warnings

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.

6.4.11.2 – Activity Dashboard

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.

6.4.11.3 – Logistics Dashboard

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.

6.4.11.4 – Rigs Online Dashboard

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.

6.4.11.5 – AC 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.

6.4.11.6 – Tool Orders Dashboard

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).

6.4.11.7 – Incident Dashboard

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.

6.4.12 – Admin Tools

The admin tools submenu contains tools that can aid the user in managing both local and remote databases.

6.4.12.1 – Database Tree Search

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.

6.4.12.2 – Clean Database

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.

6.4.12.3 – Check Names for Whitespace

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.

6.4.12.4 – Check for Duplicate Names in Tree

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.

6.4.12.5 – User Permissions

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.

6.4.12.6 – ICP Organizations

This feature is only available to Innova Drilling & Intervention staff.

6.4.12.7 – ICP Users

This feature is only available to Innova Drilling & Intervention staff.

6.4.13 – Round Survey Depths

Selecting this menu item will round the measured depths of the currently opened survey to the nearest whole number.

6.4.14 –Code Defaults

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.

6.4.15 – Real Time Data Exchange

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.

6.4.16 – Remote Data Fetch

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:

6.4.16.1 - Controls and Message Box

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.

6.4.16.2 - Well List and Filters

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.

6.4.16.3 - Data Fetch Options

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.

6.4.17 – Contact List

Opens the Contact List dialog, where the user can enter any relevant contact details.

6.4.18 – Personnel Names and 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.

6.4.19 – Personnel Utilization

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.

6.4.20 – Rig Names

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.

6.4.21 – WITS Mapping

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

Record ID: Comes from the WITS zero standards.

Field ID: Comes from the WITS zero standards.

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.

6.4.22 – Shipping Addresses

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.

6.4.23 – Logos

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.

6.4.23.1 – Set Default Primary Logo

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.

6.4.23.2 – Set Default Secondary Logo

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.

6.4.23.3 – Clear default primary logo

Removes the currently set primary logo.

6.4.23.4 – Clear default secondary logo

Removes the currently set secondary logo.

6.4.24 – IPM File Management

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.

6.4.24.1 – Upload IPM Folder

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.

6.4.24.2 - View IPM files

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.

6.4.24.3 – Pull IPM Files from server

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.

6.4.24.4 – Delete IPMS from server

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.

6.4.25 – Asset Search

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.

6.4.26 – Survey Correction Provider Settings

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.

Click on Get Wells to open the Well Selection dialog. Depending on the selected provider, the Well Selection dialog will look slightly different.

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.

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.

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.

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.

To enter the API number in Well Seeker, right click on the relevant actual well in the database tree and select Reporting >> Daily Reporting.

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.

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.

Creating an AWS Database

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.

1.0 - Introduction

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.

2.0 - Getting Started

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.

2.1 - PuTTY

https://www.chiark.greenend.org.uk/~sgtatham/putty/
Download the 32-bit MSI.

2.2 - WINSCP

https://winscp.net/eng/download.php
During installation, select the Commander interface style.

2.3 - SQL server management studio (SSMS)

https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017
Installation of SQL Management Studio can take a while, which is normal and expected.

2.4 - Google Authenticator App

In addition to installing the above programs on your computer, install the Google Authenticator App on a suitable mobile phone.

4.0 - Create an AWS Account

1. Go to https://aws.amazon.com/

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.0 - AWS Management Console

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.

6.0 - Setting up Multi Factor Authentication (MFA)

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.

7.0 – Creating an IAM User

The AWS website states the following:

“We strongly recommend that you do not use the root user for your everyday tasks, even the administrative ones. Instead, adhere to the best practice of using the root user only to create your first IAM user. Then securely lock away the root user credentials and use them to perform only a few account and service management tasks.”

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.

8.0 – RDS (Relational Database Service)

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.

8.1 – Creating a 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.

8.2 – Create RDS 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.

9.0 – Connect to the Database

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.

9.1 - SQL Server Management studio (SSMS) -1

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.

9.2 – Well Seeker

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.

9.3 - SQL Server Management studio (SSMS) - 2

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.

10.0 – Amazon EC2 (Amazon Elastic Compute Cloud)

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.

10.1 – Creating an EC2 Instance

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.

10.2 – Creating EC2 Security Rules

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.

11.0 – puTTYgen

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.

12.0 - WinSPC

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.

12.1 – ICDS files

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.

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)

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.

13.0 – PuTTY

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.

113. Follow the instructions on the following link to install node on the EC2 instance: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-up-node-on-ec2-instance.html

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.

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

13.1 - Useful puTTY Commands

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

14.0 – Well Permissions

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.

15.0 – Testing icdsServer Connection

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

16.0 – Setting up Final Security Rules

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.

16.1 – RDS

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.

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.

16.2 – EC2

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.

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.

17.0 – Troubleshooting Connectivity Issues

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

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

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

17.3 – Real Time Data Exchange / Remote Data Fetch

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

17.4 – External Files Not Saving

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:

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