Background

Historically Well Seeker Pro and Innova Engineering patch updates have been implemented manually, with the user copying the patch .exe file into the Well Seeker Pro or Innova Engineering install folder. This manual process can still be carried out, but Innova have now added the option to check for updates and then download and install the patch update within the software user interface should the user desire to do so. This is to make it easier for a company to ensure that all their users are running the same version of Well Seeker Pro and/or Innova Engineering.

This function only works for patch updates. It does not cover installer updates.

Well Seeker Pro

From version 2.2.0.4 onwards the Check for Update option in the help menu has been adjusted so that it carries out a check on Innova’s patch updates and will inform the user if their version is up to date, or if there is a newer version available via a message window.

If Well Seeker Pro is up to date, then no further action is required.

If a patch update is available, then the user will be informed of the new version number available and there will be an additional reminder in the bottom right of the UI.

In order to update to the latest version, select Help > About Well Seeker.

The user then has two options, Download or, Download/Install.

Selecting Download will download the latest patch update to the PCs Downloads folder, for the user to add to the install folder at a time that suits them.

Selecting the Download/Install option will download the latest patch update, close Well Seeker and then reopen Well Seeker Pro with the update carried out. Well Seeker will now be updated to the latest version.

Well Seeker Pro automatically checks for available updates when the program starts. This can be disabled by unchecking the Auto Update Check option in the help menu. This will also disable the reminder in the bottom right of the UI.

The users selection is saved in the local setup file. Companies who do not wish to have the updates display automatically can create and distribute a setup file that has this option unchecked. Users will still be able to manually check for new updates.

Innova Engineering

From version 2.6.0.6 onwards, Innova Engineering will automatically check (by default) for updates every time it is opened. If an update is available, then the below dialog will appear.

As long as the user is running the program in administrator mode, then all they need to do is select Yes, and the update will be downloaded and installed. Engineering will close and reopen and the new version will be ready to use. If they do not wish to update at that time, selecting No will close the dialog and the user can continue to use the current version they have installed.

This option can be disabled by unchecking the Auto Check for Updates option in the help menu. When selected, the update dialog will never pop up, even if a new update is available. Users will still be able to manually check for new updates.

To manually check for an update, the Check for Update option in the help menu has been adjusted so that it carries out a check on Innova’s patch updates and will inform the user if their version of Innova Engineering is up to date, or if there is a newer version available via a message window.

If a new Innova Engineering patch is available, the user can install it using one of two options available in the Help menu,

Selecting Download Updates will download the latest patch update to the PCs Downloads folder, for the user to add to the install folder at a time that suits them.

Selecting the Download and Install Updates option will download the latest patch update, close Innova Engineering and then reopen the program with the update carried out. Engineering will now be updated to the latest version.

Description

In Well Seeker Pro version 2.2.1.26 or earlier, anti-collision scans against inclination-only wells were giving incorrect results in certain scenarios. The issue occurred when the reference well and the offset well were close together, and there was a long course length between survey stations in the inclination-only well.

Solution

Innova have a released an updated version – v2.2.1.27 – which addresses this issue.

Implementation

Users should update to Well Seeker Pro version 2.2.1.27 at the earliest convenience. To update, follow these steps:

1. Follow this link to access the download page on the Innova Drilling website.

2. Click on the download button to download the zipped installer for version 2.2.1.27 and save it somewhere on your computer.

3. Unzip the installer file (Well-Seeker-PRO-v2.2.1.27.exe) from the .zip file.

4. In your current Well Seeker installation, backup your database by going to File >> Backup Database. Save your backup in a secure location. Then close Well Seeker.

5. Uninstall your current version of Well Seeker using the “Add or Remove Programs” feature in the Windows control panel.

6. Install the new version by running the installer file, Well-Seeker-PRO-v2.2.1.27.exe.

7. Open Well Seeker via the desktop shortcut. If Well Seeker opens the splash screen and then immediately closes, follow the steps in the following guide to address this.

Introduction

With the release of Well Seeker Pro Version 2.2.1.3, Innova introduced the Data Synchronization feature, with a further logic enhancement in Version 2.2.1.25.

Designed to supersede the Real Time Data Exchange, this feature automatically synchronizes the field personnel’s local database with their organization’s remote server database, automatically sending drilling data updates both to and from the server.

This process is automatic and designed for maximum ease of use, with virtually no setup required at the rig site. It allows for multiple personnel, for example the DD and the MWD engineers, to work on the same well from different computers.

This technical note details the setup and use of the feature.

Basic Rules

Local Push

When a user on a local database saves data in a given dialog, that specific data is pushed to the server database. For example, if the user is in the Drill String Editor accessing BHA 7 and they select save, only the data for BHA 7 will be pushed to the server.

Local Pull

When a user on a local database opens a dialog, all data associated with that dialog will be pulled down from the server, ONLY if the data on local database is older than the data on the server database. E.g., Open Drill String Editor. A save time stamp check is carried out between the local database and server database Drill String Editor data. If the local database data is older than the server database data then all of the Drill String Editor data will be pulled down from the server database for the whole well. If the local data is newer then nothing will happen.

Controls

The above rules only apply when:

1. The organization has opted to have the Data Sync feature turned on.

2. The local PC has an internet connection that can communicate with the Innova infrastructure.

3. The local PC has the relevant organization’s valid Well Seeker license present

4. The local PC has the Data Sync feature in online mode. The Data Sync feature is in online mode by default when Well Seeker is opened, but can be manually toggled to offline mode if required.

5. The relevant well has an allowed Well Status selected.

Setup

Innova Administrator

Before it can be used, the Data Synchronization feature must be activated and configured for your organization. This is not an option available to company admins, but is instead setup by Innova on your organization’s behalf.

The following customization options are available:

Locking Dialogs: Any or all of the following dialogs can be locked: Cost Codes, Activity Codes, Phase Codes, Shipping Addresses, MWD Probe Catalog, Rig Names, Personnel Names & Details, and the Real Time Data Exchange. When a dialog is locked, the local Well Seeker user will not be able to access or edit it. Instead, they will get the below message. Any changes to these dialogs would need to be done on the server database, either via the Web portal or Well Seeker, by someone with the relevant permissions.

Push Principal Plan: If this option is checked, any changes to the existing principal plan made on the local user’s database will be pushed up to the server database. If a different plan is assigned as the principal plan, this will also be updated on the server. If a new plan on the local database is created and designated as the principal plan, this new principal plan will be pushed up to the server. Note that to initiate these pushes, the actual well associated with the principal plan must be pushed by either selecting 'Apply' in the Actual Well Properties or by saving a survey.

Check for New Plans: : If this option is checked, the local user’s computer will check the server every five minutes to see if there are any new plans associated with the well. The well status must be set to Active and the user must have the survey or actual wellbore open for that well. If any new plans are detected, the local user will receive a popup notification, giving them the opportunity to Pull Plans. If Pull Plans is selected, the plans will be added to the database tree. If Ok is selected, the dialog will close, but will appear again the next time the check is carried out.

Allowed Well Status: Select the well status, as set in the Daily Reports dialog, that can be pushed/pulled using the data sync. If a well has a status that is not selected here, it will not sync. This can be used to prevent accidental syncing of wells that have been completed and certified. Typically Active, Standby and Upcoming are the well status options assigned here.

Whether data can be pushed or pulled depends on the status of the well in question on both the server and the local user’s database. The table below illustrates how the combination of both statuses effects the rules:

Note: If the local user changes the well status in their Daily Reports dialog, this change will get pushed to the server, so long as the current status of the well on the server is an allowed status. It is possible to change the well on the server to a non-allowed status using this method, meaning that no further pushes from the local will be accepted. The local user can use this rule to ‘close out’ the well at the end of a job.

Tables to Sync: The specific data tables/dialogs that are synced can be customized, based on each companies requirements. The following tables are available to select:

Data Sync Rules

Once the data sync has been set up, any well on the local user’s database will begin syncing with the equivalent well on the organization’s server database, provided the wells have the exact same database tree structure and the relevant Well Status assigned, based on the companies setup. Note, this means that a name change at any level in the database tree will break the link and prevent synchronization. If required, database tree name changes MUST be made both on the local and the server databases.

When the sync downloads data from the server to the local user’s database, this is defined as a ‘pull’. This typically happens when the local user opens the relevant dialog. Note that the sync will never pull data that could effect the well trajectory on the local database. For example, changes made to surveys on the server will NOT be pulled down.

When the sync uploads from the field to the server, this is defined as a ‘push’. Typically the data is pushed as soon as the local user clicks on ‘Apply’ or ‘Save’ in the relevant dialog.

If you have a dialog open and data relevant to that dialog is synced, you will need to close and re-open the dialog to see it. In the Innova Portal, you will need to refresh the page.

The table below defines the specific rules for each dialog/table that can be synced:

Using the Data Sync Feature

Local Well Seeker User

The advantage of the Data Synchronization feature over the Real Time Data Exchange is that it requires minimal setup by the local user on the rig site. Small packets of data are updated to the server whenever the user selects saves or apply in a dialog. To activate the data sync, the local user needs the following in place:

1. They must be using a license that is registered to your organization. For most users this will already be the case.

2. They must have an active internet connection.

3. The well that they want to sync must have exactly the same database tree naming structure on both the local computer and your organization’s remote server database. This includes Operator, Field, Facility, Well and Actual well name.

The best way to ensure this is, at the start of the job, to use the Remote Data Fetch feature to pull the well down from the server. For information about the Remote Data Fetch, refer to the Well Seeker Pro manual.

Online / Offline Status

Once these three criteria are met, and as long as the data sync feature has been activated by Innova admin, the local database will automatically start to sync with the server database whenever a save/apply is made. At the bottom right corner of the Well Seeker Pro interface, there is a window indicating if the data sync is active. If the data sync has not been turned on by Innova, or there is no internet connection, then this cell will be greyed out with no text visible.

The local user can manually pause the data sync by selecting File >> SQL Server Databases >> Data Sync Offline. When the data sync is paused, the message Data Sync Offline will display in the bottom right corner of the Well Seeker window. This allows the user to make adjustments to local databases without these changes being reflected on the server, which can be useful when troubleshooting. Note that the data sync will resume if the user closes and re-opens Well Seeker i.e. the Data Sync Offline option does not save, and is therefore reset every time Well Seeker is closed and reopened.

What to do if local and server databases have not been connected for a long time?

In a scenario where the local and server data have not been in communication for a long time, such as the loss of internet connection at the rig location, then when communication can be reestablished the local user should use the Push to server option. The option is found in the right click context menu of an actual well in the object explorer. This will bulk update the server database with all of the well information from the local database, synchronizing both databases with the latest local database information.

How does the user know if the data sync worked?

The user will not receive any notification of data syncing, as this happens continuously and would become extremely obtrusive. However, if the data sync is online and subsequently fails, then the user is notified by a Windows notification.

Note: If any changes are made to the data sync setup on the server side by the Innova Administrator, local users must close and re-open Well Seeker before these changes are applied.

Working Example

The below example demonstrates how the DD and MWD Engineer can utilize the Data Synchronization feature, in the field, to work on the same well from two different computers, whilst keeping the well up to date on their organization’s server as well.

1. The DD and MWD Engineer arrive at the rig site. They each use the Remote Data Fetch to download the job from the server to their respective computers. This ensures that the well has the same database tree naming structure on both computers and on the server, enabling synchronization between all three.

1. The MWD Engineer fills in the Inventory, saves and closes the dialog. When they click on the ‘Save’ button, their changes will be pushed up to the server.

Note: It is best practice to ensure that the DD does not have the Inventory open on their computer when this happens, because if the DD clicks ‘Save’ after the MWD, the DD’s Inventory will push to the server and overwrite the MWD’s changes, so a level of communication is required between the DD and MWD engineers.

1. The DD opens the Inventory (or the Daily Report dialog) on their computer. This will cause Well Seeker to pull the updated Inventory down to the DD’s computer.

1. The DD can then use the newly downloaded components to build their BHA in the Drill String Editor. When they save their changes, these will be pushed up to the server. The DD should then close the Drill String Editor.

1. The MWD then opens the Drill String Editor (or the Daily Reports) on their computer, causing the new BHA to pull down from the server. They can then use the Drill String Editor to enter the sensor offsets for the MWD/LWD component, and select all the relevant serial numbers etc. When they click on the ‘Save’ button, their changes will be pushed up to the server.

1. The next time the DD opens the Daily Reports or the Drill String Editor, the MWD’s changes will be pulled down from the server. This process can be repeated for all dialogs during the job, allowing the Field Engineers to seamlessly keep their computers and the server up to date.

Logging Data Sync Events

Database Changes

The mechanism for defining which data is the most recent, and therefore which data updates another database, is determined by entries in the Database Changes log of both the local and server databases. When a save or update event occurs to a table, that event and timestamp is updated in the relevant database.

The Database Changes page allows an organization's administrator to track the most recent change to each well in their server database.

The table lists wells on the server database that have been edited. For each well, the date of the most recent update is listed in the Last Update column, and the user that made the change is listed in the Last Update By column. If the change was made by a user logged into the server database, via Well Seeker or the Portal, their username will be displayed here. If the change was made by a push from Well Seeker, using the Real Time Data Exchange or the Data Sync, the computer name and MAC address of the user’s computer will be displayed.

Data Sync Log

Well Seeker stores a log of all data sync events that have occurred on a specific PC. To access this select Help > Data sync error log and the log file will open.

Description

In Well Seeker Pro Version 2.2.1.11, the 3D view plot was updated to accommodate new chart features. After this update, in specific cases where there was an NAD27 to NAD83, or NAD83 to NAD27 conversion between the reference well and any of the offset wells, the Up/Dn, Left/Right and Dist values displayed in the 3D plot will have been incorrect.

All other aspects of Well Seeker Pro, such as the AC report and RTAC dialogs reported this number correctly.

Solution

A bug fix has been issued in Well Seeker Pro Version 2.2.1.13. All users currently using Well Seeker Pro versions 2.2.1.11 and 2.2.1.12 are strongly advised to update to version 2.2.1.13 as soon as possible.

Background

Some administrators expressed a desire to be able to assign role access to certain pages and features within the Web Portal and App, that were only available when the Admin feature was assigned to a role, but not allow that same role to have access to other Admin pages and features, e.g., have access to the Data QC feature, but not have access to the User Management feature.

As of 12th April 2024, we have tackled this request with an update to the user management Products & Features and User Permissions system.

Description

Roles are now simpler to define. All of the old base feature options have been moved into the products and features section. Any features that were previously locked behind the Admin user permission, have also been moved and are now selectable within the products & features section.

The only visible changes that a user will see are in the Roles & Profile pages. The Base Features option has been removed and the Products & Features selection interface has been updated to make selection of the larger number of products & features simple.

In the Roles section the Admin user permission no longer gives access to specific products and features. However, it is required to carry out any of the below actions within the Web Portal and App; so while a user may have access to some of the below features, they will not be able to use all/some of the actions within them, unless their role has Admin permissions enabled:

• Bulk Edit

• Delete Field

• Delete Operator

• Update / Delete Activity Code

• Update / Delete Phase Code

• Update Third Party app credentials

• Update Anti-Collision Dashboard settings

• Reset Component Catalog

• Component Catalog Create/Edit/Delete

Description

When attempting to open the 3D chart in Well Seeker the program crashes or becomes unresponsive. In some instances the user may also see the below message.

Cause

In most cases, the cause of this issue is the integrated Intel Iris Xe Graphics card. To check what graphics card is installed on your machine, follow the below instructions:

• Select Display Adapters from the list and this will show the available graphics cards

Solution

There are 2 possible solutions to this issue, both of which are detailed below:

Option-1

Upgrade the Graphics Drivers to the latest versions. Note, that this needs to be done directly via the Intel website, and not by using Windows, or the Windows update options.

The following link will take you directly to an Intel support page “How to Install an Intel® Graphics Driver in Windows® 10 & Windows 11” that details the steps required to do this.

Option-2

Adjust the Graphics Settings to grant graphics performance preference to Well Seeker. This should address the issue with the application being blocked by the graphics card.

• In Graphics settings, under Add an app select Browse.

• Navigate to the following folder: C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO

• Select Well Seeker.exe and select Add

• Well Seeker will now appear in the app list in the Graphics Settings.

• Select Well Seeker from the list and select Options

• Select High Performance from the Graphics Preference dialog and hit save

• You may need to restart your computer for the changes to take effect