# 7.0 - Object Explorer

The Object Explorer allows the user to navigate through and manipulate the Well Seeker X database. All wells and plans stored in the database will be displayed in the Object Explorer. The database is organised into a tree structure with multiple branching levels. For a breakdown of each level, see [**Section 6.0 - Well Seeker X Database Structure**](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure)**.**

An item in the Object Explorer can be expanded or collapsed by clicking on the triangle icon to the left of each item. Alternatively, the user can right click on an item and select ‘Expand all’ and ‘Collapse all’. The tree state is saved when the program is closed to help aid navigation, however if the program exits unexpectedly the tree will not be saved.

The Object Explorer can be searched by typing in the **Search Database** box at the top of the tree. It can be minimized by clicking on the pin icon in the top right.

Items in the tree have a green number beside them which indicates how many active wells are contained in that branch. This feature can be toggled on and off using the **Active Well Badge** option in the **Settings** ribbon.

If a survey, plan, or wellbore is double left clicked, it will be opened as a new tab in the main viewing area. A maximum of 20 plans & 20 surveys tabs can be open at any one time.

![Figure 63: Object Explorer](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/oY8D1aXEMEaAn5MMMiF7/Unknown%20image)

Database functions can be performed either by using the toolbar at the top of the Object Explorer, or using the context menu. This can be accessed by right clicking on an existing level in the Object Explorer.

Some of these functions are only available when a particular level of the tree is selected, or when a plan/survey is open in the main viewing area. If a function is unavailable, it will be greyed out.

![Figure 64: Database viewer toolbar](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/QKXLWHVrPuS6DgOnYPnc/Unknown%20image)

![Figure 65: Database viewer menu](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/MMFgWYEDlpvJMEv2oG3p/Unknown%20image)

### 7.1 - Insert New Level

Depending on which level you select when you right click, this function will insert a new operator, facility, well, actual well, plan or survey below the currently selected level. It will also automatically open the properties dialog for the new level. The properties dialog for an existing level can be opened by right clicking and selecting **Properties** from the context menu.

### 7.2 - Create Sidetrack

Only available at actual well level. The create sidetrack dialog gives the user a quick way to create a new actual well that is sidetracked from the currently selected actual well. For a full guide to creating a sidetrack, see this page: [Well Seeker X: Sidetrack Guide](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-sidetrack-guide)

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/QYoN9y6z22ZccxHbDKSO/Unknown%20image" alt=""><figcaption><p><strong>Figure 66: Create Sidetrack</strong></p></figcaption></figure>

**Sidetrack Depth:** The measured depth (MD) at which the sidetrack begins. This depth must fall within the existing range of the motherbore. For example, if the total depth of the motherbore is 1000m MD, you cannot create a sidetrack at 1010m MD.

**Sidetrack #:** A numeric identifier used to auto-generate the name of the new sidetrack well. The final well name will be based on the motherbore's name, with the sidetrack number appended.

**Transfer Reports:** A drop-down menu with options **Yes** or **No**.

If **Yes** is selected, all reporting data from the motherbore (including reports, information, and notes) will be transferred to the new sidetrack. If the motherbore well is currently marked as Active, the new sidetrack will inherit the Active Well badge, and the motherbore will be marked as Complete.

If **No** is selected the sidetrack will be created without transferring any reporting or status data.

After filling in the required fields, click on the **Create** button and the following actions are performed automatically:

* A **new actual well** is created, with the same depth reference, magnetics, vertical section and offsets settings as the parent well.
* The new well is marked as a **sidetrack**, and its **parent well** is linked.
* A tie-on survey is created at the specified sidetrack depth, and the survey program is copied from the motherbore down to the sidetrack point.
* If reports were transferred, the reporting context (including active/completed status) is updated accordingly.

### 7.3 - Tie-On Plan

Only available at actual well or plan level. The tie-on plan dialog gives the user a quick way to create a new planned well that is sidetracked from the currently selected plan or actual well. For a full guide to creating a sidetrack, see this page: [Well Seeker X: Sidetrack Guide](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-sidetrack-guide)

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/zyzPZyPcglI7FlVkHrju/Unknown%20image" alt=""><figcaption><p><strong>Figure 67: Tie-On Plan</strong></p></figcaption></figure>

**Tie on depth:** The measured depth at which the sidetrack begins. This depth must fall within the existing range of the motherbore or plan.

**Name:** A name to be used to auto-generate the name of the new tie on plan. The final plan name will be based on the motherbore's/plan name, with the name input appended.

After filling in the required fields, click on ‘Create’ button and the following actions are performed automatically:

* New plan created with the same depth reference, magnetics, vertical section and offsets settings as the parent well/plan.
* A **tie-on line** referencing the selected depth and well.
* The **survey program** up to that point is copied into the new plan.
* The **parent-child link** is established between the original and the new plan.

### 7.4 - Cut/Copy/Paste/Delete

Items in the Object Explorer can be moved, copied or removed using these functions. Note that there are some restrictions – for example actual wells cannot be cut and can only be copied/pasted under their already existing well.

**Cut**: Cut the selected tree item and copy to the clipboard.

**Copy**: Copy the selected item to the clip board.

**Paste**: Paste cut / copied items to the current tree item.

**Delete**: Delete the currently selected tree item. Note that surveys must be removed from their parent actual well’s survey program before they can be deleted.

### 7.5 - NADCON Conversion

This option is only available at field level. If the co-ordinate reference system (CRS) for the field is NAD83 or NAD27, NADCON conversion can be used to convert between the two. Surface co-ordinates for items in the field will be altered so that they occupy the same location but in the new CRS. When user select this option, a dialog will show to confirm the change.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/qXWdATiddJNoE5wfowwu/Unknown%20image)

### 7.6 - Casing

Only available at actual well or planned well level. Allows the user to enter casing and wellbore OD details for the well/plan. If casings are set as included in the anti-collision rules in the Operator Properties dialog, the inputs entered here will also be used in anti-collision calculations.

![Figure 68: Casing Details Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/rnuEeRO1BxQUMzG9Uh8g/Unknown%20image)

The only fields which are required are MD or TVD, Type and OD. The MD or TVD is interpolated (based on the input) from the actual wellbore so if this has not yet been created then the generated depth will not be calculated.

When pasting data into the casing dialog it will by default use the TVD value. Casing Type is selected from a drop-down menu which has 4 options: Conductor, Casing, Liner and Open Hole.

To delete an entry, select the row by clicking on it’s row number and pressing delete key on your keyboard.

![Figure 69: Casing Delete Confirmation](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OeFO9La7IZUXRODZkZM3/Unknown%20image)

### 7.7 - Targets

Available from field level down to actual well/planned level. The Targets dialog allows the user to create and manage targets and lease lines, which can then be navigated to as part of a plan, plotted on charts and used in anti-collision. For more information on the Targets dialog follow the below link:

{% content-ref url="7.0-object-explorer/7.7-targets" %}
[7.7-targets](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/7.0-object-explorer/7.7-targets)
{% endcontent-ref %}

### 7.8 - Annotations

This displays the dialog for user defined annotations. The user can enter a MD or TVD and the corresponding depth field will populate i.e., enter a MD and the TVD cell will automatically populate with the relevant value which Well Seeker interpolates from the plan or survey. If the depth entered does not exist, then the annotation will not be displayed.

![Figure 84: Annotations Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/NQebsunDIjzAqBTXlGem/Unknown%20image)

If the user is entering annotations for a plan, the **Import Critical Points** button will be available. Clicking this button will pull the plan points of the plan into the table as annotations.

### 7.9 - Lithologies

Allows the user to enter the formation tops depths. These are entered as a MD, TVD or TVDSS and can only be displayed on the section view and 3D plot. The user can also enter the Dip Angle, which will change the angle of the lithology lines in the plots.

![Figure 85: Lithologies Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/6JAP313u1qtaQKJpxFHt/Unknown%20image)

### 7.10 - Reporting

This option is available to select from all database tree levels; however, the sub-menu option availability is dependent upon the selection level in the database tree. For a detailed description of the Reporting menu and all the sub-menu items, see the below link:

![Figure 137: Reporting sub menu](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/DH8MYY6ABitzndSAIS8t/Unknown%20image)

### 7.11 - Properties

Displays the properties dialog for the current tree selection. For more details on the individual properties, see **section** **6.0 - Well Seeker X Database Structure.**

### 7.12 - Rename

Rename the currently selected item in the object explorer. Symbols including # $ £ / \[ ] @ cannot not be used for naming database items. Note that all items in the object explorer must have a unique name, except for surveys.

### 7.13 - Import / Export

Opens a sub-menu with more refined options.

![Figure 86: Import / Export Menu](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/saTg2tpATV1ypAJvCdei/Unknown%20image)

**Export**: Export the currently selected tree item and all children to an export file.

**Export with offsets:** Only available at actual well and plan level. Export the currently selected tree item and all its offsets to an export file.

**Export Multi Well**: Gives the user the option to select which facilities, wells, actual wells and planned wells are to be included in the export from a given field.

**Import**: Import a Well Seeker X transfer file into the current database. If the files to be imported contain any database tree item with the same name as an existing item, Well Seeker X uses an internal logic process to automatically decide how the conflict is handled.

In all standard cases where a name match is found between the export file and the database, the outcome is the database data is overwritten with the data from the export file. The only exception to this is when a duplicate name is encountered under a different parent item in the database tree.

The way in which duplicate child items, under different parent items in the database tree are handled is described below:

![Figure 87: Naming convention logic when importing a Well Seeker export file](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/KsxsB8gm2inFpPdbZgFL/Unknown%20image)

The tables below show examples of a simple Well Seeker export file imported into Well Seeker X using the new process, including a scenario where duplicate level items are dealt with.

**Export and Database naming matches:**

![Figure 88: Outcome when naming matches.](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/gFzVh39aRyW3kY5CQYxn/Unknown%20image)

**Export and Database naming mismatch, resulting in duplicate level resolution logic:**

![Figure 89: Outcome when naming mismatch occurs](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/FTCfndlIEHjGDNUrehAu/Unknown%20image)

A message dialog appears after the import process has completed, informing the user if any duplicate level items have been resolved.

![Figure 90: Naming mismatch alert.](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/PsQ3e8dvicoD5AtC8rz2/Unknown%20image)

WellSeekerLog.txt file is also updated in the debug folder. This contains the same information that is displayed in the message dialog above, and provides a reference for the user once the dialog has been closed. The debug folder file path is: *C:\Users\USERNAME\AppData\Roaming\Well Seeker Pro\Debug.*

**Import – No Reporting:** Functions the same as Import, but does not import any of the reporting data contained in the export file. This will allow users to pull in trajectory data, such as plan updates from the office, without concern about overwriting reporting data.

### 7.14 - New Instant Plan

Only available from database level, this allows the user to create an instant plan and all the levels above it with default values.

![Figure 91: Create New Instant Plan](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/FSinWacicE6uQrTJIn7f/Unknown%20image)

### 7.15 - New Instant Survey

Only available from database level, this allows the user to create an instant survey and all the levels above it with default values.

![Figure 92: Create New Instant Survey](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/fQN7iQrtdAw4r87Xj9E5/Unknown%20image)

### 7.16 - Create Offset Plan

This option is primarily used for Geo-steering adjustments in lateral sections of the well bore and is only available for planned wellbores. It allows the user to create a plan from a user defined measured depth with a user defined TVD and dip angle. The TVD reference can also be selected here as zero Vertical Section.

![Figure 93: Create Offset Plan Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/LYvi5iDJoqfyL5T0gT3y/Unknown%20image)

Whenever a Geo-Steering report is received it will specify a new target TVD and dip angle. The user should enter the current bit depth into the MD box (this will calculate an interpolated point on the selected plan). The user can then enter either the TVD Change (+ve value is deeper, -ve value is shallower) or the New Target TVD from the geo steering report. When one is entered, the other calculates automatically. Finally, the new Dip Angle can be entered.

![Figure 94: New Offset Plan](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/wemzSY9TVq28XnUOoZhq/Unknown%20image)

When the Create button is clicked a new well plan will be created. The new plan will include the Offset TVD and Dip angle in the name. This plan will mirror the original plan down to the MD selected as the start point.

![Figure 95: Create Offset Plan Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/5OiIs03IE8VmFDSvXr10/Unknown%20image)

From the start point, the new plan will then drop (or build) instantly to the new required TVD. It should be noted that this tool is not intended to output a polished well plan; rather, its purpose is to quickly adjust the current well plan to reflect the drilling requirements / changes supplied by the geologist. The Directional Driller then has a new updated plan to follow and can bring the wellbore back to plan.

### 7.17 - Geo-Steering Updates

This option is only accessible from the Actual Wellbore level. The Geo-Steering Updates tool allows the user to plot a geo-steering window on the section view and 3D plots. The data entered here would be supplied by the geologist.

![Figure 96: Geo Steering Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/4CqHDTZqnyvwbyMJrZHX/Unknown%20image)

Follow this procedure to populate the table:

1. Enter the **MD** of each geo-steering reference point as supplied by the Geologist. Well Seeker will take this MD and interpolate the survey to find the corresponding Vertical Section. Well Seeker will use the VS azimuth defined in the Actual Wellbore Properties dialog.
2. Enter the **Target TVD** of each reference point. This is the depth of the centre of the geo-steering zone.
3. Define the thickness of each geosteering section by entering a value in the **Top Target TVD**and **Bottom Target TVD**, or by entering a value in the **Thickness Top** and **Thickness Bottom** fields. When one is filled in, the software will automatically calculate the other.
4. The user can also enter a **Dip Angle**, however this is just for reference. When plotting on the charts, the software will use the difference between the TVD values to draw the dip lines. The exception to this is the last dip value, which is used to project to the vertical section TD of the principal plan.

![Figure 97: Section View Plot with Geo Steering Data](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/46a9mjpbWTZYkxBf5HYh/Unknown%20image)

In the above plot, the black Vertical lines represent the different lines entered in the Geo-Steering Dialog. If the first line in the geo-steering dialog has a vertical section which is greater than the vertical section of the landing point in the principal plan, then Well Seeker will automatically add an additional line to represent this point. If the vertical section of the first line in the dialog is less than or equal to the vertical section of the landing point in the principal plan, then this line will not be added.

Geo-steering data can be added to the plot from the Chart Properties ribbon menu or the Chart Properties dialog.

![Figure 98: Chart Properties Ribbon Menu](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/zbnsg55Zm4Kuc6PpcGJn/Unknown%20image)

![Figure 99: Chart Properties Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/QhVtq8vlxxVu2J0oAYyk/Unknown%20image)

It is worth noting that if there is no data entered in the Geo Steering Updates dialog, WS will still represent the target zones on the plot if these are turned on. The data used for this comes from the TVD and dip angle at the start of the lateral in the principle plan. Thickness will be 20 as default for all thickness options.

### 7.18 - Expand/Collapse All

These options will expand or collapse the selected level and all levels below it.

### 7.19 - External Files

Only available at the Actual Well level. The External Files dialog allows the user to attach additional files and images to the database and associated with the selected actual well. These files will then be included when the user exports the well or uploads it to the server using the Real Time Data Exchange. External files added on the server will also be download when a local database downloads the well using the Data Fetch feature.

This dialog can also be opened via the Drill String Editor window, however when opened this way the user will only be able to view files that have been associated with that specific BHA.

![Figure 100: External Files](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/Jg7g24px6oXSg0F7yk3z/Unknown%20image)

Files can be added by clicking on a folder and then clicking on the **Add Files** button at the top. They can also be added by dragging and dropping into the zone at the bottom, or dragging and dropping directly onto the desired folder. Once the file has been added, it can be moved to another folder by left clicking on the file icon and dragging to the desired folder. Note that the folders do not have a specific function, they are just to help with categorizing your files.

Left click on a file to view a preview at the bottom of the dialog. Right click on the file to access a context menu where the user can open the file, delete it, copy it or open the file location on their PC. If the file is an image, clicking on it will display a **Rotate** button at the top of the dialog, allowing the user to rotate the image.

The user can assign a file to any BHA that has been created for the actual well by clicking in the **BHA#** column on the right. This will make the file available if the External Files dialog is opened from the Drill String Editor.

If the file is missing from the organisation’s server database, or from the user’s local PC, a exclamation mark **(!)** will be displayed beside the file.

### 7.20 - Push to Server

Only available at actual well level. Selecting this option performs a manual push for the actual well, using the Real Time Data Exchange. When selected, the user will receive the message “Data push initiated”. If there are any issues with the data push, the user will receive a notification. For more information on the Real Time Data Exchange, refer to **section 9.4.15 - Real Time Data Exchange.**

### 7.21 - ISCWSA Diagnostic

Only available at survey level or planned wellbore level. This option exports an excel format diagnostic for the selected survey or planned wellbore. The diagnostic file contains a survey listing where the error ellipse calculation at each station is broken down into it’s constituent terms, depending on the survey error model selected. The file is commonly used for troubleshooting issues with anti-collision results. For more information, refer to this tech note: [**Troubleshooting Differences in Anti-Collision Results | Innova Drilling & Intervention**](https://docs.innova-drilling.com/introduction/technical-notes/low-priority/troubleshooting-differences-in-anti-collision-results)

### 7.22 - Data Sync Diagnostic

Only accessible at actual well level. The Data Sync Diagnostic tools helps the user to troubleshoot data sync and real time data exchange transmission issues.

![Figure 101: Data Sync Diagnostic](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/ja2yowlKG96QVdGCa4qq/Unknown%20image)

The Data Sync Diagnostic dialog displays all of the checks that must pass for the Data Synchronisation feature to function correctly. Each check will be marked as either OK or NOT OK. If any of the checks are marked as NOT OK, use the definitions listed below to troubleshoot the problem. Note that if any changes are made, the diagnostic must be closed and re-opened to refresh the results:

**Internet Connection:** Checks if your computer is connected to the internet. If this is marked NOT OK, consult with the rig site internet provider. **Note:** If Well Seeker X is being blocked by a firewall / anti-virus software, this check can still register as OK, but all checks below it will show NOT OK.

**Data Sync Active:** Checks if your organisation is using the Data Synchronisation feature. If this is marked NOT OK, you must use the Real Time Data Exchange to push data back to the server. If you think this is in error, contact your system admin.

**Data Sync Online:** Checks if the Data Synchronisation feature is enabled on the user’s computer. If this is marked as NOT OK, check if the **Offline** option has been toggled on in the Home ribbon, or in the toolbar at the bottom of the main user interface:

![Figure 102: Toggling data sync status](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/bcT98tnIsT2BXB8yrTcP/Unknown%20image)

**Role Allows Push:** Only applies if **Local Login** has been activated for your organisation, requiring the user to log in when they open Well Seeker X. This factor checks if your user has permission to use the Data Synchronisation feature. If this is marked NOT OK, you may still have permission to use the Real Time Data Exchange. Contact your co-ordinator to clarify your user permissions.

**ICDS Online:** Checks your organisation's ICDS server is online and functioning. The ICDS server facilitates communication between the server database and rig site computers. In the event of an outage, the ICDS server should restart automatically. If this check remains NOT OK for some time, notify your system admin, who may need to contact Innova Support.

**Well on Server:** Data sync is only possible if the actual well is present on both the server database and the user’s local database. The actual well, and all levels above it in the database tree, must have **exactly** the same names in both databases. This includes case sensitivity. **Note:** A common issue is that a blank space has been left at the start or end of a name.

**Well Status on Server:** Checks if the actual well on your organisation’s server database has a status that permits data push/pull. If this is marked NOT OK, someone with edit permissions must log into the server database and change the well status. By default, data push/pull requires a status of either **Active**, **Standby**, **Upcoming** or **TD**, but this can vary depending on your organisation’s policy.

**Local Well Status:** Checks if the actual well in the user’s local database has a status that permits data push/pull. If this is marked NOT OK, access the Job Data dialog in the Home ribbon and check the Well Status field. By default, data push/pull requires a status of either **Active**, **Standby**, **Upcoming** or **TD**, but this can vary depending on your company’s policy.
