> This is part 1 of 5 of the full documentation (pages 1–100 of 405).
> The content is paginated: fetch every part to see all of it.
> Next part: https://docs.innova-drilling.com/introduction/llms-full.txt/1
> Page index: https://docs.innova-drilling.com/introduction/llms.txt

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
This site has an agentic ask interface you may use to query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.innova-drilling.com/introduction/index.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

---

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

{% hint style="info" %}
<https://www.innova-drilling.com/>
{% endhint %}

## Updates

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

{% content-ref url="/pages/oagHyGR6quVlUbDuKYpI" %}
[Documentation Updates](/introduction/master/documentation-updates)
{% endcontent-ref %}

## 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.&#x20;

{% tabs %}
{% tab title="Generic Documents" %}
A selection of generic documents which are relevant to both Well Seeker Pro and Innova Engineering

{% content-ref url="/pages/-MfcP-mxkaJm\_lRE9CNA" %}
[Innova Generic Documents](/introduction/generic-documents/innova-generic-documents)
{% endcontent-ref %}

{% endtab %}

{% tab title="Quick Start Guides" %}
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.

{% content-ref url="/pages/-Mf8MOKVOfvd08rDJcOh" %}
[Well Seeker Pro Guides](/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides)
{% endcontent-ref %}

{% content-ref url="/pages/-Mf7ULNcvbwtlhGaIFKz" %}
[Innova Engineering Guides](/introduction/innova-engineering-how-to-guides/innova-engineering-guides)
{% endcontent-ref %}

{% endtab %}

{% tab title="Manuals" %}
The full manual for both Well Seeker Pro and Innova Engineering.

{% content-ref url="/pages/-MfH85eQ2CUCMa-2r7j6" %}
[Well Seeker Pro Manual](/introduction/legacy-documentation/manuals/well-seeker-pro-1)
{% endcontent-ref %}

{% content-ref url="/pages/-MfH8aV2EuZy4fSrtYFa" %}
[Innova Engineering Manual](/introduction/innova-engineering-manual/innova-engineering)
{% endcontent-ref %}

{% endtab %}

{% tab title="Release Notes" %}
The most up to date release notes for both programs. These documents detail the various changes  implemented between revisions.

{% content-ref url="/pages/hHwOPCumBGLyPcm7zqWS" %}
[Well Seeker X Release Notes](/introduction/release-notes/well-seeker-x-release-notes)
{% endcontent-ref %}

{% content-ref url="/pages/-MfcOpZAt5jLUV3eolcS" %}
[Innova Engineering Release Notes](/introduction/release-notes/innova-engineering)
{% endcontent-ref %}

{% endtab %}

{% tab title="Video Guides" %}
This section contains links to all of Innova's video resources.&#x20;

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

{% content-ref url="/pages/-MfgVURMxUtMolvacUbR" %}
[How To Videos](/introduction/video-guides/how-to-videos)
{% endcontent-ref %}

{% content-ref url="/pages/-Mf8XFN\_Xt2WtS9RyMZQ" %}
[Innova Online Training](/introduction/video-guides/training-videos)
{% endcontent-ref %}

{% endtab %}

{% tab title="Tech Notes" %}
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.

{% content-ref url="/pages/-MiM4TjzsPZKGU9Rcvx-" %}
[High Priority](/introduction/technical-notes/well-seeker-pro-technical-notes)
{% endcontent-ref %}

{% content-ref url="/pages/-MiM\_6Jnr9KhEKzg1lEy" %}
[Medium Priority](/introduction/technical-notes/medium-priority)
{% endcontent-ref %}

{% content-ref url="/pages/-MiM\_K5AhLAyiBoiT2J2" %}
[Low Priority](/introduction/technical-notes/low-priority)
{% endcontent-ref %}

{% endtab %}
{% endtabs %}


# Documentation Updates

This page lists the latest updates to the Innova Documentation Portal. Click on the page title to follow the link to the updated page.

<table><thead><tr><th width="143">Date</th><th width="374">Page Title</th><th>Section</th></tr></thead><tbody><tr><td>15/10/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-alert-system">Innova Vantage - Alert System</a></td><td>Vantage Guides</td></tr><tr><td>02/10/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/data-bridge-importing-3rd-party-data">Data Bridge: Importing 3rd Party Data</a></td><td>Vantage Guides</td></tr><tr><td>02/10/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-insert-a-missing-daily-report">Well Seeker X - Insert a Missing Daily Report</a></td><td>Well Seeker X Guides</td></tr><tr><td>01/10/2026</td><td><a href="/introduction/technical-notes/low-priority/troubleshooting-differences-in-anti-collision-results">Troubleshooting Differences in Anti-Collision Results</a></td><td>Technical Notes</td></tr><tr><td>29/09/2026</td><td><a href="/introduction/release-notes/well-seeker-x-release-notes">Well Seeker X Release Notes</a></td><td>Release Notes</td></tr><tr><td>22/09/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-multi-leg-lateral-guide">Well Seeker X: Multi Leg Lateral Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>13/08/2026</td><td><a href="/introduction/release-notes/well-seeker-x-release-notes">Well Seeker X Release Notes</a></td><td>Release Notes</td></tr><tr><td>11/08/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-alert-system">Innova Vantage - Alert System</a></td><td>Vantage Guides</td></tr><tr><td>27/07/2026</td><td><a href="/introduction/technical-notes/low-priority/large-well-seeker-database">Large Well Seeker Database</a></td><td>Technical Notes</td></tr><tr><td>20/07/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-alert-system">Innova Vantage - Alert System</a></td><td>Vantage Guides</td></tr><tr><td>16/07/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-engineering-quick-start-guide">Innova Vantage - Engineering Quick Start Guide</a></td><td>Vantage Guides</td></tr><tr><td>16/07/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/innova-vantage-manual/7.0-well-views/6.12-engineering-dashboard">Innova Vantage - Engineering Dashboard</a></td><td>Innova Vantage Manual</td></tr><tr><td>06/07/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/providing-3rd-party-access-to-your-organizations-server-data#toc135722907">Providing 3rd Party Access to Your Organizations Server Data</a></td><td>Vantage Guides</td></tr><tr><td>01/07/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/8.0-menu-ribbons/8.2-home/8.2.2-database">Home > Database</a></td><td>Well Seeker X Manual</td></tr><tr><td>01/07/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/11.0-reporting/11.11-slide-sheet#id-11.11.1-slide-sheet-menu-ribbon">Slide Sheet Menu Ribbon</a></td><td>Well Seeker X Manual</td></tr><tr><td>23/06/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-alert-system">Innova Vantage - Alert System</a></td><td>Vantage Guides</td></tr><tr><td>23/06/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/8.0-menu-ribbons/8.9-chart-properties-ribbon">Chart Properties Ribbon</a></td><td>Well Seeker X Manual</td></tr><tr><td>23/06/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/11.0-reporting/11.6-drill-string-editor">Drill String Editor</a></td><td>Well Seeker X Manual</td></tr><tr><td>11/06/2026</td><td><a href="/introduction/release-notes/well-seeker-x-release-notes">Well Seeker X Release Notes</a></td><td>Release Notes</td></tr><tr><td>05/06/2026</td><td><a href="broken://pages/ymAJIL3KbvjPz4BThpSc">Innova Data Bridge: Importing Baker Hughes Data</a></td><td>Vantage Guides</td></tr><tr><td>05/06/2026</td><td><a href="broken://pages/xwNyhwVv6rfuHp3TCCsZ">Innova Data Bridge: Importing Schlumberger Data</a></td><td>Vantage Guides</td></tr><tr><td>05/06/2026</td><td><a href="broken://pages/oXD8YzaXT9UvcTiHYPuc">Innova Data Bridge: Importing Compass/ Halliburton Data</a></td><td>Vantage Guides</td></tr><tr><td>29/05/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-alert-system">Innova Vantage - Alert System</a></td><td>Vantage Guides</td></tr><tr><td>22/05/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-rogii-integration-guide">Well Seeker X: ROGII Integration Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>21/05/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/11.0-reporting/11.11-slide-sheet#id-11.11.1.5.4-survey-email">Slide Sheet </a></td><td>Well Seeker X Manual</td></tr><tr><td>21/05/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/8.0-menu-ribbons/8.2-home/8.2.8-survey-reports">Surveys Report</a></td><td>Well Seeker X Manual</td></tr><tr><td>18/05/2026</td><td><a href="broken://pages/ymAJIL3KbvjPz4BThpSc">Innova Data Bridge: Importing Baker Hughes Data</a></td><td>Vantage Guides</td></tr><tr><td>18/05/2026</td><td><a href="broken://pages/xwNyhwVv6rfuHp3TCCsZ">Innova Data Bridge: Importing Schlumberger Data</a></td><td>Vantage Guides</td></tr><tr><td>18/05/2026</td><td><a href="broken://pages/oXD8YzaXT9UvcTiHYPuc">Innova Data Bridge: Importing Compass Data</a></td><td>Vantage Guides</td></tr><tr><td>18/05/2026</td><td><a href="/introduction/innova-engineering-manual/well-seeker-x-manual/8.0-menu-ribbons/8.6-integrations/8.6.2-rogii">ROGII Integrations</a></td><td>Well Seeker X Manual</td></tr><tr><td>11/05/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-data-link-guides/vantage-data-link-guide">Vantage Data Link Guide</a></td><td>Vantage Data Link Guides</td></tr><tr><td>08/05/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-data-link-guides/vantage-data-link-installation-guide">Vantage Data Link: Installation Guide</a></td><td>Vantage Data Link Guides</td></tr><tr><td>08/05/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-project-ahead-guide">Well Seeker X: Project Ahead Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>08/05/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-job-startup-procedure">Well Seeker X: Job Startup Procedure</a></td><td>Well Seeker X Guides</td></tr><tr><td>08/05/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-backing-up-a-ws-db">Well Seeker X: Backing up a WS Db</a></td><td>Well Seeker X Guides</td></tr><tr><td>07/05/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.7-level-6-actual-well/6.7.1-actual-well-properties">WSX Manual - 6.7.1 - Actual Well Properties</a></td><td>Well Seeker X Manual</td></tr><tr><td>07/05/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well/6.6.1-plan-properties">WSX Manual - 6.6.1 - Plan Properties</a></td><td>Well Seeker X Manual</td></tr><tr><td>06/05/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-reporting-an-issue">Well Seeker X: Reporting an Issue</a></td><td>Well Seeker X Guides</td></tr><tr><td>05/05/2026</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-engineering-quick-start-guide">Innova Vantage - Engineering Quick Start Guide</a></td><td>Vantage How To Guides</td></tr><tr><td>01/05/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-manual/innova-vantage-manual/6.0-well-views/6.12-engineering-dashboard">Innova Vantage - Engineering Dashboard</a></td><td>Innova Vantage Manual</td></tr><tr><td>21/04/2026</td><td><a href="https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-rig-states-guide">Well Seeker X: Rig States Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>06/04/2026</td><td><a href="/introduction/video-guides/how-to-videos/well-seeker-x/wsx-intro-to-real-time-data-exchange">WSX - Intro to Real Time Data Exchange</a></td><td>Video Guides</td></tr><tr><td>06/04/2026</td><td><a href="/introduction/video-guides/how-to-videos/well-seeker-x/wsx-unit-sets">WSX - Units Guide</a></td><td>Video Guides</td></tr><tr><td>06/04/2026</td><td><a href="/introduction/video-guides/how-to-videos/well-seeker-x/wsx-introduction-to-object-explorer">WSX - Introduction to Object Explorer</a></td><td>Video Guides</td></tr><tr><td>06/04/2026</td><td><a href="/introduction/video-guides/how-to-videos/well-seeker-x/wsx-exporting-and-importing">WSX - Exporting and Importing</a></td><td>Video Guides</td></tr><tr><td>06/04/2026</td><td><a href="/introduction/video-guides/how-to-videos/well-seeker-x/wsx-proximity-plot">WSX - Proximity Plot</a></td><td>Video Guides</td></tr><tr><td>30/03/2026</td><td><a href="/introduction/technical-notes/low-priority/new-features-in-well-seeker-x-v3.0.5.5">New Features in Well Seeker X v3.0.5.5</a></td><td>Technical Notes</td></tr><tr><td>13/01/2025</td><td><a href="/introduction/video-guides/how-to-videos/innova-vantage/innova-vantage-introduction-to-ops-dashboards">Innova Vantage - Introduction to Ops Dashboards</a></td><td>Vantage How To Guides</td></tr><tr><td>8/12/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-wits-setup-guide">Well Seeker X: WITS Setup Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>16/10/2025</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/compass-edm-slot-exports-incorrect-surface-location"><mark style="color:red;">Compass EDM: Slot Exports Incorrect Surface Location</mark></a></td><td>Technical Notes</td></tr><tr><td>16/10/2025</td><td><a href="/introduction/technical-notes/low-priority/wsx-operating-system-not-configured-to-run-application">WSX: Operating System not Configured to Run Application</a></td><td>Technical Notes</td></tr><tr><td>16/10/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/bha-trend-analyzer-guide">Innova Vantage - BHA Trend Analyzer</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>16/10/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-data-insights-upgrade">Innova Vantage - Data Insights Upgrade</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>03/10/2025</td><td><a href="/introduction/promotional-info-and-software-overview/promotional-info/presentations">Innova Product Presentations</a></td><td>Promotional Info</td></tr><tr><td>02/10/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-reporting-an-issue">Well Seeker X: Reporting an Issue</a></td><td>Well Seeker X Guides</td></tr><tr><td>25/09/2025</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-x-tool-inventory-tracking-hours">Well Seeker X: Tool Inventory Tracking Hours</a></td><td>Technical Notes</td></tr><tr><td>25/09/2025</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-x-installation-internet-connection-error">Well Seeker X: Installation Internet Connection Error</a></td><td>Technical Notes</td></tr><tr><td>25/09/2025</td><td><a href="/introduction/technical-notes/low-priority/error-message-when-closing-well-seeker-x">Error Message when closing Well Seeker X</a></td><td>Technical Notes</td></tr><tr><td>24/09/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-data-sync-diagnostic-guide">Well Seeker X: Data Sync Diagnostic Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>15/09/2025</td><td><a href="/introduction/video-guides/how-to-videos/well-seeker-x/well-seeker-x-transition">Well Seeker X Transition</a></td><td>Video Guides</td></tr><tr><td>10/09/2025</td><td><a href="/introduction/release-notes/well-seeker-x-release-notes">Well Seeker X Release Notes</a></td><td>Release Notes</td></tr><tr><td>09/09/2025</td><td><a href="broken://pages/oXD8YzaXT9UvcTiHYPuc">Innova Data Bridge: Importing Compass Data</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>09/09/2025</td><td><a href="broken://pages/q9JZXtDXALuO5RDBAmhC">Troubleshooting Differences in Anti-Collision Results</a></td><td>Technical Notes</td></tr><tr><td>29/08/2025</td><td><a href="/introduction/getting-started/getting-started-with-well-seeker-x">Getting Started with Well Seeker X</a></td><td>Getting Started</td></tr><tr><td>29/08/2025</td><td><a href="/introduction/getting-started/getting-started-with-innova-engineering">Getting Started with Innova Engineering</a></td><td>Getting Started</td></tr><tr><td>29/08/2025</td><td><a href="/introduction/getting-started/getting-started-with-innova-vantage">Getting Started with Innova Vantage</a></td><td>Getting Started</td></tr><tr><td>28/08/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-alert-system">Innova Vantage - Alert System</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>22/08/2025</td><td><a href="broken://pages/ymAJIL3KbvjPz4BThpSc">Innova Data Bridge: Importing Baker Hughes Data</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>22/08/2025</td><td><a href="broken://pages/xwNyhwVv6rfuHp3TCCsZ">Innova Data Bridge: Importing Schlumberger Data</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>19/08/2025</td><td><a href="/introduction/generic-documents/innova-generic-documents/innova-privacy-policy">Innova Privacy Policy</a></td><td>Generic Documents</td></tr><tr><td>01/08/2025</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-x-u-zontal-well-plans-minimum-curvature-limitation">Well Seeker X: U-Zontal Well Plans - Minimum Curvature Limitation</a></td><td>Technical Notes</td></tr><tr><td>18/07/2025</td><td><a href="/introduction/generic-documents/innova-generic-documents/innova-software-licensing">Innova Software Licensing</a></td><td>Generic Documents</td></tr><tr><td>16/07/2025</td><td><a href="/introduction/release-notes/well-seeker-x-release-notes">Well Seeker X Release Notes</a></td><td>Release Notes</td></tr><tr><td>15/07/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-sidetrack-guide">Well Seeker X: Sidetrack Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>15/07/2025</td><td><a href="/introduction/release-notes/well-seeker-x-release-notes">Well Seeker X Release Notes</a></td><td>Release Notes</td></tr><tr><td>10/07/2025</td><td><a href="/introduction/promotional-info-and-software-overview/promotional-info/innova-technical-specification">Innova Technical Specification</a></td><td>Promotional Info</td></tr><tr><td>18/06/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-installation-guide">Well Seeker X: Installation Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>10/06/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-mwd-reporting-guide">Well Seeker X: MWD Reporting Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>05/06/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/plan-v-actual-wall-plot-guide">Plan v Actual Wall Plot Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>22/05/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/innova-in-any-language-web-browser-translation-guide">Web Browser Translation Guide</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>13/05/2025</td><td><a href="/introduction/technical-notes/low-priority/target-line-dip-angle-adjusted-for-azimuth-changes">Target Line Dip Angle Adjusted For Azimuth Changes</a></td><td>Technical Notes</td></tr><tr><td>07/05/2025</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-x-failure-to-open">Well Seeker X Failure to Open</a></td><td>Technical Notes</td></tr><tr><td>06/05/2025</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-x-displays-not-fully-visible">Well Seeker X: Displays Not Fully Visible</a></td><td>Technical Notes</td></tr><tr><td>05/05/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-job-startup-procedure">Well Seeker X: Job Startup Procedure</a></td><td>Well Seeker X Guides</td></tr><tr><td>05/05/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-sidetrack-guide">Well Seeker X: Sidetrack Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>24/04/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/updating-well-seeker-x">Updating Well Seeker X</a></td><td>Well Seeker X Guides</td></tr><tr><td>08/04/2025</td><td><a href="/introduction/technical-notes/low-priority/ws-new-outlook-email-automation-unavailable">Well Seeker - New Outlook Email Automation Unavailable</a></td><td>Technical Notes</td></tr><tr><td>08/04/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-project-ahead-guide">Well Seeker X: Project Ahead Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>08/04/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-survey-correction-integration-guide">Well Seeker X: Survey Correction Integration Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>08/04/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-how-to-guide">Well Seeker X: How to Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>02/04/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-local-login-guide">Well Seeker X: Local Login Guide</a></td><td>Well Seeker X Guides</td></tr><tr><td>01/04/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-adding-an-ipm">Well Seeker X: Adding an IPM</a></td><td>Well Seeker X Guides</td></tr><tr><td>28/03/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-changing-datum-elevations">Well Seeker X: A Guide to Changing Datum Elevations</a></td><td>Well Seeker X - Guides</td></tr><tr><td>28/03/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-backing-up-a-ws-db">Well Seeker X: Backing up a WS Db</a></td><td>Well Seeker X - Guides</td></tr><tr><td>28/03/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-installation-guide">Well Seeker X: Installation Guide</a></td><td>Well Seeker X - Guides</td></tr><tr><td>07/03/2025</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-transition-guide">Well Seeker X Transition Guide</a></td><td>Well Seeker X - Guides</td></tr><tr><td>26/02/2024</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/critical-update-for-anti-collision-in-inc-only-wells">Critical Update for Anti-Collision in Inc Only Wells</a></td><td>Technical Notes</td></tr><tr><td>18/02/2024</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/data-synchronization-feature-update">Data Synchronization Feature Update</a></td><td>Technical Notes</td></tr><tr><td>13/12/2024</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-x-failure-to-open">Well Seeker Pro - Failure to Open</a></td><td>Technical Notes</td></tr><tr><td>13/12/2024</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-engineering-quick-start-guide">Web Portal Engineering Quick Start Guide</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>26/11/2024</td><td><a href="/introduction/legacy-documentation/release-notes/release-notes">Well Seeker Pro release notes</a></td><td>Release Notes</td></tr><tr><td>26/11/2024</td><td><a href="/introduction/technical-notes/low-priority/wsp-charts-and-wpc-improvements">WSP - Charts &#x26; WPC Improvements</a></td><td>Technical Notes</td></tr><tr><td>20/11/2024</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/data-synchronization-feature-update">Data Synchronization Feature Update</a></td><td>Technical Notes</td></tr><tr><td>20/11/2024</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/providing-3rd-party-access-to-your-organizations-server-data">Providing 3rd Party Access to Your Organization's Server Data</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>12/11/2024</td><td><a href="https://docs.innova-drilling.com/introduction/technical-notes/well-seeker-pro-technical-notes/ws-3d-chart-c2c-distance-critical-update">WSP - 3D Chart C2C Distance Critical Update</a></td><td>Technical Notes</td></tr><tr><td>06/11/2024</td><td><a href="/introduction/technical-notes/low-priority/wsp-solo-cloud-target-lines-update">WSP - Solo Cloud Target Lines Update</a></td><td>Technical Notes</td></tr><tr><td>10/10/2024</td><td><a href="/introduction/technical-notes/low-priority/wsp-and-innova-portal-object-validation-feature">WSP &#x26; Portal - Object Validation Feature</a></td><td>Technical Notes</td></tr><tr><td>10/10/2024</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-pro-slide-sheet-update">WSP - Slide Sheet Update</a></td><td>Technical Notes</td></tr><tr><td>03/10/2024</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/installation-guide">Installation Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>11/09/2024</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/inclination-only-ipm-guidelines">Inclination Only IPM Guidelines</a></td><td>Well Seeker - Guides</td></tr><tr><td>11/09/2024</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/data-synchronization-feature-update">Data Synchronization Feature Update</a></td><td>Technical Notes</td></tr><tr><td>06/09/2024</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-x-failure-to-open">Well Seeker Pro - Failure to Open</a></td><td>Technical Notes</td></tr><tr><td>02/09/2024</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/data-synchronization-feature-update">Data Synchronization Feature Update</a></td><td>Technical Notes</td></tr><tr><td>20/08/2024</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-pro-slide-sheet-crash-in-v2.2.1.1">WSP - Slide Sheet Crash in v2.2.1.1</a></td><td>Technical Notes</td></tr><tr><td>19/08/2024</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-pro-real-time-data-exchange-update">WSP - Real Time Data Exchange Update</a></td><td>Technical Notes</td></tr><tr><td>26/07/2024</td><td><a href="/introduction/technical-notes/low-priority/sidetrack-reporting">Sidetrack Reporting</a></td><td>Technical Notes</td></tr><tr><td>17/07/2024</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-pro-compass-edm-erroneous-grid-convergence">WSP Compass EDM Erroneous Grid Convergence</a></td><td>Technical Notes</td></tr><tr><td>28/06/2024</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-pro-crs-updated-functionality">WSP CRS Updated Functionality</a></td><td>Technical Notes</td></tr><tr><td>27/06/2024</td><td><a href="/introduction/legacy-documentation/release-notes/release-notes">Well Seeker release notes</a></td><td>Release Notes</td></tr><tr><td>27/06/2024</td><td><a href="/introduction/release-notes/innova-engineering">Engineering release notes</a></td><td>Release Notes</td></tr><tr><td>17/06/2024</td><td><a href="/introduction/technical-notes/low-priority/excel-report-printing-error">Excel Report Printing Error</a></td><td>Technical Notes</td></tr><tr><td>13/05/2024</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/providing-3rd-party-access-to-your-organizations-server-data">Web Portal Viewer Only User Guide</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>22/04/2024</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/products-and-features-and-user-permissions-update">Products &#x26; Features and User Permissions Update</a></td><td>Technical Notes</td></tr><tr><td>15/04/2024</td><td><a href="/introduction/legacy-documentation/manuals/well-seeker-pro-1">Well Seeker - Manual</a></td><td>Well Seeker - Manual</td></tr><tr><td>25/03/2024</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/solo-cloud-integration-guide">Solo Cloud Integration Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>19/03/2024</td><td><a href="/introduction/technical-notes/low-priority/target-line-dip-angle-adjusted-for-azimuth-changes">Target Line Dip Angle Adjusted For Azimuth Changes</a></td><td>Technical Notes</td></tr><tr><td>06/03/2024</td><td><a href="/introduction/release-notes/well-seeker-x-release-notes">Release Notes</a></td><td>Release Notes</td></tr><tr><td>28/02/2024</td><td><a href="/introduction/technical-notes/low-priority/offset-selector-c2c-global-scan">Offset Selector - C2C Global Scan</a></td><td>Technical Notes</td></tr><tr><td>02/02/2024</td><td><a href="/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-rig-states-guide">WSP - Rig States Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>01/02/2024</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/geomag-model-installation-guide">Geomag Model Installation Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>26/01/2024</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/oasis-integration-guide">Oasis Integration in Innova</a></td><td>Well Seeker - Guides</td></tr><tr><td>19/01/2024</td><td><a href="/introduction/technical-notes/well-seeker-pro-technical-notes/check-for-update-function">Check For Update Function</a></td><td>Technical Notes</td></tr><tr><td>12/01/2024</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-data-acquisition-and-edr-guide">Web Portal Data Acquisition and EDR Guide</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>27/11/2023</td><td><a href="/introduction/technical-notes/low-priority/error-ellipses-at-sidetrack-depth-well-seeker-vs-compass-comparison">Error ellipse at sidetrack depth - WSP vs Compass comparison</a></td><td>Technical Notes</td></tr><tr><td>24/11/2023</td><td><a href="/introduction/technical-notes/low-priority/well-seeker-pro-change-to-ud-lr-logic-at-low-inclination">WSP - Change to UD LR logic at low inclination</a></td><td>Technical Notes</td></tr><tr><td>16/11/2023</td><td><a href="/introduction/technical-notes/low-priority/missing-mfc140u.dll-error">Missing MFC140U.DLL Error</a></td><td>Technical Notes</td></tr><tr><td>19/10/2023</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/automated-bit-grading-guide">Automated Bit Grading Guide</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>06/09/2023</td><td><a href="/introduction/legacy-documentation/how-to-videos/well-seeker-pro/untitled/targets">WSP - Targets</a></td><td>Well Seeker - How To Videos</td></tr><tr><td>04/09/2023</td><td><a href="/introduction/technical-notes/low-priority/force-layout-reset">WSP - Force Layout Reset</a></td><td>Technical Notes</td></tr><tr><td>04/09/2023</td><td><a href="/introduction/technical-notes/low-priority/third-party-survey-correction-integration">Third Part Survey Correction Integration</a></td><td>Technical Notes</td></tr><tr><td>30/08/2023</td><td><a href="https://docs.innova-drilling.com/introduction/video-guides/how-to-videos/web-portal/web-portal-bulk-edit">Web Portal - Bulk Edit</a></td><td>Web Portal - How To Videos</td></tr><tr><td>21/08/2023</td><td><a href="https://docs.innova-drilling.com/introduction/web-portal-manual/12.0-user-management">Web Portal Manual - User Management</a></td><td>App &#x26; Portal - Manual</td></tr><tr><td>21/08/2023</td><td><a href="https://docs.innova-drilling.com/introduction/app-and-portal-guides/web-portal-mfa-guide">Web Portal - MFA Guide</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>08/08/2023</td><td><a href="https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/certified-survey-reports-how-to-guide">WSP - Certified Surveys How To Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>31/07/2023</td><td><a href="https://docs.innova-drilling.com/introduction/technical-notes/low-priority/missing-sql-driver">Missing SQL Driver</a></td><td>Technical Notes</td></tr><tr><td>26/07/2023</td><td><a href="https://docs.innova-drilling.com/introduction/well-seeker-pro-1/13.0-reporting/13.11-directional-drilling-dashboard">Well Seeker - Manual</a></td><td>Well Seeker - Manual</td></tr><tr><td>19/07/2023</td><td><a href="https://docs.innova-drilling.com/introduction/well-seeker-pro-1/6.0-main-menu/6.1-file-menu">WSP Manual - File Menu</a></td><td>Well Seeker - Manual</td></tr><tr><td>29/06/2023</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/tool-rental-run-tracking-guide">Tool Rental Run Tracking Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>26/06/2023</td><td><a href="/introduction/generic-documents/innova-generic-documents/license-renewal">Well Seeker Pro Licensing</a></td><td>Well Seeker - How To Videos</td></tr><tr><td>05/06/2023</td><td><a href="/introduction/legacy-documentation/how-to-videos/well-seeker-pro/untitled/how-to-install-wsp">How to Install Well Seeker Pro</a></td><td>Well Seeker - How To Videos</td></tr><tr><td>04/06/2023</td><td><a href="/introduction/video-guides/how-to-videos/innova-vantage/innova-vantage-user-management">Web Portal User Management</a></td><td>Vantage - How To Videos</td></tr><tr><td>30/05/2023</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/survey-correction-integration-guide">Survey Correction Integration Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>29/05/2023</td><td><a href="/introduction/technical-notes/low-priority/force-layout-reset">Force Layout Reset</a></td><td>Technical Notes</td></tr><tr><td>26/05/2023</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/solo-cloud-integration-guide">Solo Cloud Integration Guide</a></td><td>Well Seeker - Guides</td></tr><tr><td>25/05/2023</td><td><a href="/introduction/innova-engineering-how-to-guides/vantage-guides/innova-vantage-mfa-guide">Web Portal MFA Guide</a></td><td>Vantage &#x26; Vision Guides</td></tr><tr><td>25/05/2023</td><td><a href="/introduction/video-guides/how-to-videos/innova-engineering-1/back-calculate-friction-factors">Back Calculate Friction Factors</a></td><td>Innova Engineering - How To Videos</td></tr><tr><td>17/05/2023</td><td><a href="/introduction/video-guides/how-to-videos/innova-vantage/innova-vantage-analytics">Web Portal Analytics</a></td><td>Vantage - How To Videos</td></tr><tr><td>12/05/2023</td><td><a href="/introduction/innova-engineering-how-to-guides/innova-engineering-guides/sag-quick-start-guide">SAG Quick Start Guide</a></td><td>Innova Engineering - Guides</td></tr><tr><td>09/05/2023</td><td><a href="/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/adding-a-new-crs">Adding a New CRS</a></td><td>Well Seeker - Guides</td></tr><tr><td>01/05/2023</td><td><a href="/introduction/legacy-documentation/feature-updates/well-seeker-pro-bggm-error-estimate-integration">WSP - BGGM Error Estimate Integration</a></td><td>Feature Updates</td></tr><tr><td>01/05/2023</td><td><a href="/introduction/legacy-documentation/feature-updates/well-seeker-pro-superior-qc-integration">WSP - Superior QC Integration</a></td><td>Feature Updates</td></tr><tr><td>01/05/2023</td><td>Vantage &#x26; Vision<a href="/introduction/promotional-info-and-software-overview/feature-updates/innova-vision-and-vantage-feature-update"> - Feature Update</a></td><td>Feature Updates</td></tr></tbody></table>


# Feature Updates

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


# Innova Vision & Vantage - Feature Update

{% embed url="<https://vimeo.com/684225875>" %}

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

* **<sales@innova-drilling.com>**
* **US: +1 713-893-4435**
* **UK: +44 (0) 7711411079**

Alternatively visit our website: [www.innova-drilling.com](https://www.innova-drilling.com/)


# Promotional Info


# Innova Vision & Vantage

{% embed url="<https://vimeo.com/595235145>" %}

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

* **<sales@innova-drilling.com>**
* **US: +1 713-893-4435**
* **UK: +44 (0) 7711411079**

Alternatively visit our website: [www.innova-drilling.com](https://www.innova-drilling.com/)


# Innova Technical Specification

## 1.0 – Software <a href="#toc201920610" id="toc201920610"></a>

Innova’s software ecosystem is a fully integrated digital drilling platform designed to support the full lifecycle of well planning, engineering, and reporting. Built with scalability, real-time connectivity, and user configurability at its core, the Innova suite empowers both field and office-based teams to collaborate seamlessly. The platform is comprised of three key components, Well Seeker X, Innova Engineering, and Innova Vantage & Innova Vision mobile app, each playing a critical role in delivering safe, efficient, and data-driven operations. Together, they provide a unified environment that supports everything from trajectory planning and anti-collision to torque and drag modelling, real-time analytics, and standardized operational reporting. The following sections provide a brief overview of the technical requirements and functionality of each component.

### 1.1 – Well Seeker X <a href="#toc194419361" id="toc194419361"></a>

Innova Well-Seeker X is a high performance well planning, survey management and reporting 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 X offers exceptional performance with all the features expected of an industry leading well planning package, including Integrated Reporting, Asset Management, Well Analytics and RT anti-collision features.

### 1.2 - Innova Engineering <a href="#toc194419380" id="toc194419380"></a>

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.

### 1.3 – Innova Vantage & Innova Vision <a href="#toc194419392" id="toc194419392"></a>

Innova Vantage is an online, cloud-based platform designed to provide users with access to an array of powerful solutions across the Innova platform. It provides a powerful collaborative ecosystem with centralized data storage.

Innova Vantage allows users, with the relevant permissions and credentials to access the organisations server database without the requirement to download and install any software. In addition to the features detailed in the Well Seeker X section, Vantage also has the following features.

#### 1.3.1 - User Management <a href="#toc194419393" id="toc194419393"></a>

* Comprehensive and robust user management system utilizing Auth0

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FV59mEwNK4QWaLbbumHAN%2F0.png?alt=media" alt="" width="563">

* Can accommodate Azure and Okta, allowing clients existing user management systems to work seamlessly with Innova’s
* Unlimited user definable Roles, ensures each company can tailor access to their specific needs
  * Admin, Create, Edit, Delete and Approve

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FF3hFfhyqbFDjRAxAKJvN%2F1.png?alt=media" alt="" width="563">

* Roles can restrict access to any given feature along with Operator level restrictions for accessing the database tree

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDUwV05uJWHRWi2et13RA%2F2.png?alt=media" alt="" width="563">

* At User level individual wells can be restricted
* Manage user access to Innova API via third party apps.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJ9yJ74bTfFcNdL0OqbgV%2F3.png?alt=media" alt="" width="530">

#### 1.3.2 - Data Management & Analytics <a href="#toc194419359" id="toc194419359"></a>

* Secure and Compliant Data Management with SOC2 Type II
* Flexible Hosting on Amazon AWS and Microsoft Azure
* Suite of database QC tools:
  * Bulk editor allows for one-click cleanup of data entry errors across the entire database

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgixDhCK6dXGQWPl92z7h%2F4.png?alt=media" alt="" width="375">

* Object Validation tool to impose data standards across all field computers and alerts users if they do not comply

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXURYa9x1QB1L4Tn6A24K%2F5.png?alt=media" alt="" width="563">

* Data QC tool paired with Object Validation allows co-ordinators to track wells with incomplete data.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhFpV0UgBWoi0y1A1mgfM%2F6.png?alt=media" alt="" width="563">

* Invoice QC to ensure consistency in client billing.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyA1guYYtluEal3DslUtd%2F7.png?alt=media" alt="" width="563">

* Audit Data and Database Changes tools allow co-ordinators to track changes to the organization’s server database.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwUCEBroCR4O4LnvkPqBg%2F8.png?alt=media)

* Two-way data synchronization allows co-ordinators to remotely QC and correct field data in real time during drilling operations
* Powerful data analytics dashboard allows the user to search and compare wells across the cloud server based database, with the following features:
  * Extensive search criteria including: date, hole size, failures, assembly type etc.
  * Comprehensive KPI Analytics including: depth vs days, motor performance, connection analysis and drilling parameters
  * Drilling performance metrics such as: ROP, weight on bit, RPM, hookload etc.
  * Output single KPI or full reports including customizable charts and data tables
  * Benchmark performance of multiple wells and KPI’s

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ff2NEg0SJW9uQSL1xvsal%2F9.png?alt=media" alt="" width="563">

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkdXvOHDdtn50vzQkCrNo%2F10.png?alt=media" alt="" width="563">

#### 1.3.4 - Computer Requirements <a href="#toc201920616" id="toc201920616"></a>

Both Well Seeker X and Innova Engineering 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.
* Minimum 4 GB of RAM.
* Minimum 500MB of hard disk space.
* 64-bit Computer
* 64-bit Microsoft Windows version 10 or better
* 64-bit - Microsoft Office
* <mark style="color:red;">Windows XP, Windows 7.0 and Mac OS are</mark> <mark style="color:red;"></mark><mark style="color:red;">**NOT**</mark> <mark style="color:red;"></mark><mark style="color:red;">supported</mark>
* Recommended screen resolution: 1920 x 1080.

#### 1.3.5 - Licensing <a href="#toc194419360" id="toc194419360"></a>

Both Well Seeker X and Innova Engineering programs use computer specific licensing. 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.

Enterprise, server based, remote access and local license options are all supported.

## 2.0 – Well Placement Solution <a href="#toc201920618" id="toc201920618"></a>

Innova’s Well Placement solution, built around the powerful Well Seeker X and Vantage platform, delivers a comprehensive, industry-aligned environment for accurate, efficient well path planning and collision risk management. Designed to meet the rigorous standards of ISCWSA and tailored for complex well geometries, our solution enables engineers to plan, visualize, and execute trajectories with precision and confidence. With real-time anti-collision functionality, integrated geosteering tools, and robust 3D visualization capabilities, Innova ensures safe well placement and optimal asset utilization across all operational regions.

The full suite of capabilities, including advanced planning methods, real-time collision avoidance, and integration with third-party geosteering tools, is detailed in the following section.

### 2.1 - Comprehensive Well Path Planning <a href="#toc194419362" id="toc194419362"></a>

* 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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fo6rxYogkZ6YzDyiATsLy%2F11.png?alt=media" alt="" width="563">

* Supports multiple target geometries including:
  * Simple 2D circular and Elliptical
  * Point & Rectangular
  * Complex 3D multi point Polygonal
  * Lease Lines and Hard Lines

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FiXJACxLvf5unpKy6rApx%2F12.png?alt=media" alt="" width="563">

* 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

### 2.2 - Anti-Collision Tools <a href="#toc201920620" id="toc201920620"></a>

* Perform anti-collision scans using industry leading proximity detection algorithms

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlvMMFvlBojwABzUg5gpW%2F13.png?alt=media)

* 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
* Scan for potential collisions using all error surfaces including Ellipsoid Scalar Expansion

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAJVtehqYOBrZt1mmcTal%2F14.png?alt=media" alt="" width="375">

* Anti-collision scans can be run interactively during planning and drilling phases on multiple actual wells / plans

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1MhvGTxVOaQYA8K1Hdqq%2F15.png?alt=media)

* User defined warning criteria and alerts can be set to notify of potential collision risk
* Implementation of latest anti-collision standards including WPTS Separation Rule and Maximum Allowable Separation Distance (MASD).

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlhK51WOf3yw5dvPMth0q%2F16.png?alt=media" alt="" width="479">

* Casing and hole diameters can be included in separation factor calculation in order to increase accuracy. Especially important for top hole drilling with large diameter surface casing.
* Ability to create custom Instrument Performance Models (IPM)

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZUALf01XKAZNaFKDF43V%2F17.png?alt=media" alt="" width="563">

* Error output sigma level can be selected by the user
* **Real Time AC** feature allows efficient monitoring of multiple offset wells and distance to lease lines

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F51BF9edmko4mnVpoyUfB%2F18.png?alt=media" alt="" width="563">

* Anti-collision tools such as travelling cylinder view and ladder plot update in real time as additional surveys are entered

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FziM0uNtiKEfjJ5Dy7U3W%2F19.png?alt=media" alt="" width="563">

* Advanced anti-collision visualization tools available including Ladder Plot, Separation Factor Plot and Travelling Cylinder Plot

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOHrXqmHMymtyRozIz0Nx%2F20.png?alt=media)

* Real-time Anti-Collision dashboard allows office personnel to remotely monitor the anti-collision status of all active wells on one screen. Create user defined alerts for separation factor, C2C, well plans and lease lines.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSimTjBPqOC1SWaB5KZxF%2Fimage.png?alt=media&amp;token=3f9ae368-42ed-405b-a52c-23e08edc0f5c" alt="" width="563"><figcaption></figcaption></figure>

* Manage your organization’s error models, allowing them be retrieved by field users operating Well Seeker X.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfNYwEEi136DcF2PmJWl1%2Fimage.png?alt=media&amp;token=0859f560-56af-4051-a7c3-4a6de1d28f61" alt=""><figcaption></figcaption></figure>

### 2.3 - Powerful Database <a href="#toc194419364" id="toc194419364"></a>

* 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 intuitive tree view

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLNiDoRcaWatr8z4lYcfh%2Fimage.png?alt=media&amp;token=9e038f78-4683-421a-bcd2-f207cbd1adde" alt="" width="222"><figcaption></figcaption></figure>

* 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 sync and 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5DCjH295AuHdAeb96KYN%2Fimage.png?alt=media&amp;token=926739f6-2977-4c1d-85cd-865610a1f845" alt="" width="563"><figcaption></figcaption></figure>

* 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 and easily build a database with all the relevant data.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjkP7ZtJBwtfybgRJfqqJ%2Fimage.png?alt=media&amp;token=d489f2e9-7c40-4ed3-a639-96f3e076be2a" alt="" width="563"><figcaption></figcaption></figure>

### 2.4 - Wellbore Visualization <a href="#toc201920622" id="toc201920622"></a>

* Fully customisable, advanced and powerful 3D plotting capability

  * Plan View (Top Down) Plot

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDEMAPHVmlPoidEsMBKha%2Fimage.png?alt=media&amp;token=607467fc-ed3a-4699-b1f6-c44f034ffab4" alt="" width="532"><figcaption></figcaption></figure>

  * Section View (Side On) Plot

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSsErm6dNTHVuOD1qOBeQ%2Fimage.png?alt=media&amp;token=aee5ebca-4041-42bc-9956-b32ce3aaff6c" alt="" width="532"><figcaption></figcaption></figure>

  * 3D Plot - Fly down well 3D chart feature. Visualise closest approach to all offset wells and principal plan

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeReodUzBquVylE4zRSo3%2Fimage.png?alt=media&amp;token=daf353ea-43e9-4992-abf3-beb5c786b21e" alt="" width="488"><figcaption></figcaption></figure>

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9JSbl0FOGrtl4z4uSnBv%2Fimage.png?alt=media&amp;token=0cb54db4-bf79-4b96-8da1-5c44c2a3e433" alt="" width="563"><figcaption></figcaption></figure>

  * Spider Plot with interactive TVD slice control

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrC912WHuDy3sxfde6SAH%2Fimage.png?alt=media&amp;token=e3d8253b-d891-4a20-a0e2-c2cee920c44a" alt="" width="532"><figcaption></figcaption></figure>

  * Azimuth Comparison Plot (Azimuth vs MD)

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKggUNEYtEBGwi9g0f71H%2Fimage.png?alt=media&amp;token=b9e8c716-d351-43ff-86fd-887ffd76a82a" alt="" width="443"><figcaption></figcaption></figure>

  * Inclination Comparison Plot (Inclination vs MD)

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FY1wgyom6994mck6hg2gj%2Fimage.png?alt=media&amp;token=73870377-96d5-4a69-9f4f-9efe70609843" alt="" width="443"><figcaption></figcaption></figure>

  * Dogleg Comparison Plot (Dogleg vs MD)

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FV1D2PzvMz9GLWOkeDM4p%2Fimage.png?alt=media&amp;token=2e6188ca-180e-439e-a115-840229af1925" alt="" width="443"><figcaption></figcaption></figure>
* 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, logos etc.

  * Pre-defined plot sizes range from A0 to A7 with a user defined option also available.
  * Print PvA plots directly from the main UI, without having to open the WPC
  * Master Plot Templates can be pulled directly from the server to the local machine

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCVcrUy2bWYfM3qQ1W5CB%2Fimage.png?alt=media&amp;token=a188fc57-20ad-4bf1-825c-92aa719259be" alt="" width="563"><figcaption></figcaption></figure>

### 2.5 - Integrated Geosteering Functionality <a href="#toc201920623" id="toc201920623"></a>

* Visualise formation top and target depths

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOztnKfcX6ooaQvDuxSKq%2Fimage.png?alt=media&amp;token=a11e2be1-78fe-430f-8236-5fdefc9eca3a" alt="" width="563"><figcaption></figcaption></figure>

* Customisable outputs in both 2D and 3D charts

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkDvlqPFGqf3rHdYM0o0A%2Fimage.png?alt=media&amp;token=dc79e0ba-b38a-4758-ba64-1daa1efccd93" alt="" width="463"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvShHWX7vREayZHCzBzTu%2Fimage.png?alt=media&amp;token=caf11a11-c44d-42b5-b8ff-77e9052b8ee2" alt="" width="563"><figcaption></figcaption></figure>

* Support for dip adjustments during geosteering turns
* Integration with ROGII Star Steer third party software.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4LcTCGd893HftNbd25ch%2Fimage.png?alt=media&amp;token=24c5691d-3280-45e2-891a-61eaa8345a9e" alt="" width="406"><figcaption></figcaption></figure>

### 2.6 - Geomagnetic Modelling <a href="#toc194419367" id="toc194419367"></a>

* 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

### 2.7 - Standard Reporting Features <a href="#toc201920625" id="toc201920625"></a>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtimQRRR2PaoKiAogYyPt%2Fimage.png?alt=media&amp;token=334a7f0e-521d-4780-bb2f-b7f6f1e987ea" alt="" width="563"><figcaption></figcaption></figure>

* Wall Plot Composer

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJwVya5Cx1W3G2q9WEOU1%2Fimage.png?alt=media&amp;token=06d821c1-69e3-4cde-926a-3ca90768b5c0" alt="" width="563"><figcaption></figcaption></figure>

### 2.8 - Import Compass Export Files <a href="#toc194419369" id="toc194419369"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6nvbYRQdByIJH8QW0NIz%2Fimage.png?alt=media&amp;token=82d7b5e2-e2da-4c69-a19a-db401b604427" alt=""><figcaption></figcaption></figure>

### 2.9 - Additional Features <a href="#toc194419376" id="toc194419376"></a>

* Data synchronization feature provides an automatic two-way data sync between the field and the server database, allowing the software to send updated plans from the office to the field and vice versa without requiring any input from the field or office personnel.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnJ4nEseP6kP9R8RgcjU6%2Fimage.png?alt=media&amp;token=574feb51-ad65-4682-a20e-0340ec227c66" alt="" width="436"><figcaption></figcaption></figure>

* Supports data import / export from 3rd party software platforms
* Directional Difficulty Index (DDI) calculator

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9a2QRywu9mvwUEOZ31nk%2Fimage.png?alt=media&amp;token=2298cc59-1254-4e68-a9dd-fd48f565a549" alt="" width="333"><figcaption></figcaption></figure>

* Automatic updates
* One-click license request and download

### 2.10 - Additional UI Features <a href="#toc194419377" id="toc194419377"></a>

* 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

## 3.0 - Well Engineering Solution <a href="#toc201920629" id="toc201920629"></a>

Innova Engineering offers a unified platform for critical well engineering calculations, empowering engineers to perform detailed torque and drag, hydraulics and survey correction simulations within a single, intuitive interface. Developed by drilling engineers for engineers, the solution prioritizes speed, accuracy, and transparency of results, supporting our clients need for configurable, verifiable outputs that align with internal engineering standards. From advanced modelling of complex BHAs to real-time comparison of actual versus simulated performance, Innova Engineering equips each user with the tools to optimize well design, execution, and safety outcomes.

A breakdown of the system’s core engineering modules and calculation tools, covering everything from hydraulics to survey correction, is provided below.

### 3.1 - Main features <a href="#toc194419381" id="toc194419381"></a>

* Simple to use interface

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWTP98hqeTuSWg0W2NRKR%2Fimage.png?alt=media&amp;token=ac04c900-38e9-4d5a-ae41-f3e99c4d5f41" alt="" width="563"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FADZB5ZvsguduPC7bweWK%2Fimage.png?alt=media&amp;token=15a90be7-73dd-4bd4-948d-9da889c4fa56" alt="" width="332"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDqFzixrdlixzlcLqjAC9%2Fimage.png?alt=media&amp;token=73a86792-2e8a-4a20-9c26-91a45dfce54e" alt="" width="332"><figcaption></figcaption></figure>

* Fully customisable charts complete with screen reader to allow quick interpretation of generated data

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDrBhfoFi7LR6JpKzFAGP%2Fimage.png?alt=media&amp;token=f30a8de2-952b-4c04-a58c-09b24dc6f4c0" alt=""><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhLHbwkAkFmcvbFedYO9x%2Fimage.png?alt=media&amp;token=86122fc5-42ef-4f0a-8ce5-5f4dd2e296f5" alt=""><figcaption></figcaption></figure>

### 3.2 - Torque and Drag Module <a href="#toc194419382" id="toc194419382"></a>

* Latest soft string model with stiffness correction factor
* Model **Viscous Drag**, **additional side force due to buckling** & **Contact Surface Correction**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fn6Wd3ZUb735uUJG6KiVN%2Fimage.png?alt=media&amp;token=8abe61a3-2759-47ad-bd35-8e7944bae7ed" alt="" width="563"><figcaption></figcaption></figure>

* **Conservative** (Unloading) & **Standard** (Loading) Helical Buckling Models

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4XNkQy8fl9apXGq5d0iq%2Fimage.png?alt=media&amp;token=47205a39-3777-4f00-817a-7fd383f91baa" alt="" width="457"><figcaption></figcaption></figure>

* Calculate T\&D for multiple rig operations simultaneously Tripping In / Out, Rotating On / Off Bottom, Sliding and Reaming

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPFNllWOxsGl1GmMOxWfj%2Fimage.png?alt=media&amp;token=29022a97-901c-44a9-b149-d7fd48e2a22a" alt="" width="563"><figcaption></figcaption></figure>

* Ability to model for both pumps on and pumps off and account for string differential pressure
* Calculate Sinusoidal and Helical buckling limits

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFIJYPTpCK0WOhrV1lGSi%2Fimage.png?alt=media&amp;token=9fa606e0-c01c-48e7-9010-da89ef1b3ca5" alt="" width="563"><figcaption></figcaption></figure>

* Full support for casing, liner, tubing & drilling assemblies

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FT8CQ8CYYVDLxrTpGpleJ%2Fimage.png?alt=media&amp;token=4cd19e37-660d-42b6-9f55-7917833caa47" alt="" width="563"><figcaption></figcaption></figure>

* Full support for complex 3D directional wells

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fa1Y5ICL4RKohPCqkABRT%2Fimage.png?alt=media&amp;token=47987dfd-327c-4784-b464-4e8508e4d1fa" alt="" width="563"><figcaption></figcaption></figure>

* Friction factor sensitivity analysis for unlimited number of friction factors, or single calculation

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjDd9l0JMaePTYm2ptxb5%2Fimage.png?alt=media&amp;token=dd12444c-37d1-44da-96ab-ebaf2010c404" alt="" width="217"><figcaption></figcaption></figure>

* Models casing flotation / drill string fill
* Friction reduction devices (Non-rotating drill pipe protectors) can be modelled
* BHA Analysis & Critical RPMs

  * 2D Line Charts

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLkEQo97FWB9lSN0ONv35%2Fimage.png?alt=media&amp;token=fc527443-2fb1-4070-b181-8087371b86b1" alt="" width="563"><figcaption></figcaption></figure>

  * 3D Charts

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fcw7Jo8Zpmzdq98AIYK2X%2Fimage.png?alt=media&amp;token=e4549ca8-9b4e-403e-8773-c7f43e18b692" alt="" width="563"><figcaption></figcaption></figure>

  * BHA Directional Tendency Chart

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3pqOevHffVewCVqoNYA9%2Fimage.png?alt=media&amp;token=899173d2-5cdf-4fdf-962e-c18ec87dfee5" alt="" width="563"><figcaption></figcaption></figure>

  * Vibration analysis calculates Critical RPMs

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fhz8tzaOFQfUoEJFOQzG7%2Fimage.png?alt=media&amp;token=62b28e3b-94bf-4a85-b22b-88c5da190144" alt="" width="563"><figcaption></figcaption></figure>
* Calculates expected pipe stretch and torque induced pipe twist

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnXJGGyW4yQlPg3HzhtyJ%2Fimage.png?alt=media&amp;token=8836b3d0-9cc5-472d-83db-673359b0af73" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwH6hQ68NDZnspi1cGcUy%2Fimage.png?alt=media&amp;token=0d7a1a15-7bfe-4ac5-b7ca-61d1e2bccba4" alt="" width="563"><figcaption></figcaption></figure>

* Elemental (snapshot) view available for all calculations

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTHUyKgRDvR0sbOweuYR1%2Fimage.png?alt=media&amp;token=2749fa91-59f1-4814-acc1-c6036276a9ec" alt="" width="514"><figcaption></figcaption></figure>

* Calculate side forces & casing wear for all operations

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fl8fsHt2y2HDz5M6CytzC%2Fimage.png?alt=media&amp;token=1be58164-36c9-4354-ab1f-c5f86d83da46" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBeLHTtADGrS1GcoOdnAr%2Fimage.png?alt=media&amp;token=f02496e3-ce39-4323-ae53-0c114451d5ad" alt="" width="563"><figcaption></figcaption></figure>

* Drill string fatigue prediction

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxsiFgH2LTXhgO9VnICPC%2Fimage.png?alt=media&amp;token=66bdc164-544b-4f9a-a9a6-bdbf66cfaf7f" alt="" width="560"><figcaption></figcaption></figure>

* Real time data can be modelled & displayed alongside the calculated data in order to back calculate real time friction factor

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fd523XYtk0EUzloDuquPU%2Fimage.png?alt=media&amp;token=2c5183ef-e643-41b7-a5db-7b7a790a0488" alt="" width="563"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmsR8h9tppZYOnxosD80B%2Fimage.png?alt=media&amp;token=707de286-39a8-4bbd-85c2-e0856d388093" alt="" width="542"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FA6yC3X0nhAY0zCGGOLQV%2Fimage.png?alt=media&amp;token=9522e741-d686-4e72-a07b-845b69772a17" alt="" width="509"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8yjxw0veKt2JopYpkFt3%2Fimage.png?alt=media&amp;token=7066212d-0af4-4d8c-bc6c-0ac35f466d50" alt="" width="483"><figcaption></figcaption></figure>

* Casing Standoff & Centralizer Spacing Calculation. Use to optimise standoff and achieve proper zonal isolation

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRbLOnc2s2UtLNMcGxS33%2Fimage.png?alt=media&amp;token=d5c01159-db66-4fc1-9ce4-d07bb6f0c045" alt="" width="552"><figcaption></figcaption></figure>

* Ability to model expandable liners including max pull, pull at cone, expected expansion hookload as well as outer & inner string running loads

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FiSrADISIKVET63c8FXAP%2Fimage.png?alt=media&amp;token=e200ef01-61a8-4d9f-b812-19e8d2ed734c" alt="" width="269"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrJZeBUrAPnzQMkE9XLMo%2Fimage.png?alt=media&amp;token=d923b135-e202-4613-b775-8912ce6b495c" alt="" width="563"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fe9MrOAH6ues6bheKJ34H%2Fimage.png?alt=media&amp;token=cb529128-1383-43fe-bc6f-64e2a4308bda" alt="" width="221"><figcaption></figcaption></figure>

* Option to select the fluid level in the wellbore.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxvFvC0AzoSyGn9SPjsBm%2Fimage.png?alt=media&amp;token=8db1cfe4-1d92-4c9e-bd39-afddb7abe80e" alt="" width="221"><figcaption></figcaption></figure>

### 3.3 - Hydraulics Module <a href="#toc194419383" id="toc194419383"></a>

* Support for multiple hydraulic models:
  * Bingham Plastic
  * Power Law
  * Herschel Bulkley
  * Robertson Stiff

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZWhMViDpqEKNNzhS7ubD%2Fimage.png?alt=media&amp;token=97e580bb-c51c-4e0b-bd69-4fddc488777c" alt="" width="402"><figcaption></figcaption></figure>

* Calculated Outputs:

  * Standpipe Pressures

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmP2cCs0TRnlOmrMB50Ub%2Fimage.png?alt=media&amp;token=73704a58-fef5-4042-a91d-017c05f6a513" alt="" width="563"><figcaption></figcaption></figure>

  * ECD: cuttings loaded and clean hole

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcIN5FTlZ2JM25q3qYGFj%2Fimage.png?alt=media&amp;token=a559f37a-d992-4611-8d4f-bf9bfadcc1e4" alt="" width="500"><figcaption></figcaption></figure>

  * Surge and Swab

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBDSVHxxeTIa4BtSR0MT5%2Fimage.png?alt=media&amp;token=915d5547-b5f6-48dc-8eb0-7fc7f3407d23" alt="" width="504"><figcaption></figcaption></figure>

* Complete set of hole cleaning outputs:

  * Annular Velocity Profile

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fd9GZ66p2MQ1DdO0Byisx%2Fimage.png?alt=media&amp;token=0e751184-2e4f-4bde-95ec-9fa747c30efc" alt="" width="533"><figcaption></figcaption></figure>

  * Cuttings Carrying Index (CCI)

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUHKyw61XvKOxmGnMifOs%2Fimage.png?alt=media&amp;token=c7989375-a658-4a9f-bf17-023bd33c95b4" alt="" width="488"><figcaption></figcaption></figure>

  * Cuttings %

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FR9lUmaAP6QSTg6ZG82Vy%2Fimage.png?alt=media&amp;token=f5f9be4c-f73c-46cf-80ca-3a9de84ba797" alt="" width="488"><figcaption></figcaption></figure>

  * Minimum Flowrate required for good hole cleaning (sensitivity analysis for ROP)

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3rFd4G97hz7Ye8OvtDPq%2Fimage.png?alt=media&amp;token=54914a77-1787-463e-a60f-278f67d06e81" alt="" width="500"><figcaption></figcaption></figure>

* Options for single calculation or sensitivity analysis for unlimited number of flowrates and tripping speeds simultaneously

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKYBR6Hp4KlDY8p0Xbg9V%2Fimage.png?alt=media&amp;token=916aa912-6f4c-4828-b3d1-9920c4e64cec" alt="" width="442"><figcaption></figcaption></figure>

* Full support for riser-less / dual gradient drilling

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFcUX3Wz7AYiZFVR6df4C%2Fimage.png?alt=media&amp;token=45c6572a-7ab9-441e-89e0-efc689ff84d5" alt="" width="398"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWlGYEAkBobiaDZIZva2c%2Fimage.png?alt=media&amp;token=51814774-9d4b-4687-8233-482658b78b79" alt="" width="563"><figcaption></figcaption></figure>

* Split flow modelling for complex BHAs with multiple hole openers / under reamers / circulating subs

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzD1SgthPHPUFiD1Rb2SZ%2Fimage.png?alt=media&amp;token=57f84387-5f0c-4a97-b0a9-1db6ebd74d83" alt="" width="563"><figcaption></figcaption></figure>

* Incorporate data gathered at the well site into the hydraulics model and overlay the real-world data and the theoretical hydraulics model

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FoH4Px1ur3tmumPOLML94%2Fimage.png?alt=media&amp;token=9d6659f3-5b41-47a8-a65d-5d5c31136d98" alt="" width="563"><figcaption></figcaption></figure>

* Enter multiple pore pressures & fracture gradients and plot against modelled data

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCAu1P1FE3tXKhhImz7T1%2Fimage.png?alt=media&amp;token=4a8ff131-31e3-403d-b54f-dc0de7127c98" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSqrpI34EVFcUmG9XNjBA%2Fimage.png?alt=media&amp;token=94431c94-5ae8-4a93-901d-8f9d1b6382c4" alt="" width="215"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjwdN1rxnokWJiYxirZAY%2Fimage.png?alt=media&amp;token=1b50cc9a-dc1d-4063-8779-8feb9a230909" alt="" width="243"><figcaption></figcaption></figure>

* Surge and swab calculations can be calculated for any reference:
  * Bit
  * Casing Shoe
  * Bottom Hole
  * Any User Defined depth

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FI5SbXipfkpzASwJ6yQFT%2Fimage.png?alt=media&amp;token=67cd3cf1-89a2-4b65-b888-7791b79d00e3" alt="" width="369"><figcaption></figcaption></figure>

* Surge and swab model can also include the effects of pipe acceleration, gel strength, coil tubing operations such as continuous tripping and continuous circulation

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUpmK6CgtcDGeZIjeYsYO%2Fimage.png?alt=media&amp;token=993d4dcf-8cfc-4236-baa8-f131ddddb765" alt="" width="422"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHJufBD29qmnRY1VCVsKh%2Fimage.png?alt=media&amp;token=59401951-0b67-4fb2-9024-33da185bdc93" alt="" width="434"><figcaption></figcaption></figure>

* Pump Pressure Safety Factor: Option to allow the user to increase the SPP by a specified percentage.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTCd0pp5oEacoxbjUB6LT%2Fimage.png?alt=media&amp;token=3abd54a3-46bb-492a-a783-52df9acb6365" alt=""><figcaption></figcaption></figure>

* Ability to model air drilling

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOBcB0KIWFYqe36v1TaXS%2Fimage.png?alt=media&amp;token=53c3f6e6-4e40-4eef-b495-a472d326dc2e" alt="" width="230"><figcaption></figcaption></figure>

* Ability to apply a back pressure for MPD operations

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0wAAQic8JV6jXfZiwjjw%2Fimage.png?alt=media&amp;token=d76e4be4-e093-48c8-b637-71fcd275cb7d" alt="" width="200"><figcaption></figcaption></figure>

* Ability to include additional riser boost flow rate

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbXnvE9viJGEIgcLoSZWs%2Fimage.png?alt=media&amp;token=b44d7e40-c7f3-4385-b73c-ea5dfd179ac6" alt="" width="250"><figcaption></figcaption></figure>

### 3.4 – Survey Correction Module <a href="#toc194419384" id="toc194419384"></a>

* Correct raw MWD surveys for Z axis magnetic interference with the latest short collar correction (SCC) algorithm

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fe6z1WGhQpqBfQqPf6fM8%2Fimage.png?alt=media&amp;token=b918cc03-6d65-4d67-8590-0c15238a16a8" alt=""><figcaption></figcaption></figure>

* QC raw MWD surveys for G total, B total and magnetic dip with user definable limits

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVyVhBwUxBEOLi1YHX9hO%2Fimage.png?alt=media&amp;token=2ed1d861-c0f4-4b88-bbd8-16c76b8aefaa" alt="" width="327"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfpOGNHV0AQumiYOT6VHp%2Fimage.png?alt=media&amp;token=e4142844-86a2-408f-84ee-1cdcfcb68d11" alt="" width="342"><figcaption></figcaption></figure>

* Multi Station Analysis (MSA) can be used to calculate an optimal bias and scale factor for XYZ magnetometers and accelerometers

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRFySFWHxzWqe1f9uB1KL%2Fimage.png?alt=media&amp;token=3429913d-0736-41b3-9bb2-310a69465a9d" alt="" width="448"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQgwdzwl9vtzpdEdsORjr%2Fimage.png?alt=media&amp;token=17eec9c8-01a1-4498-9744-ae19ca130053" alt=""><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4dpOlidsjAfwNsKO9OXM%2Fimage.png?alt=media&amp;token=fd9661fa-59cf-4654-9747-e84015872fbe" alt=""><figcaption></figcaption></figure>

* Supports survey interpolation for both MD and TVD, results can be exported to text or Excel

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7HHClHuF4rI6PBSjBcxH%2Fimage.png?alt=media&amp;token=47d01c8d-1326-4ef3-98f0-1e5b6e110cd1" alt="" width="563"><figcaption></figcaption></figure>

* Produce fully customisable plots for both section and plan views and overlay well plan and actual surveys on one chart

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhyJ6tg7JyFnx9r9CaOvU%2Fimage.png?alt=media&amp;token=2b4ac51c-eb2d-4a35-87ba-13579005e2bd" alt="" width="563"><figcaption></figcaption></figure>

### 3.5 - SAG Correction <a href="#toc194419385" id="toc194419385"></a>

* Survey SAG correction algorithm, to correct survey inclinations for BHA deflections

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fdg239TAHN8ydrnYQd1vs%2Fimage.png?alt=media&amp;token=85b360f7-f79d-42a0-a7dd-e51d1fbe228d" alt="" width="563"><figcaption></figcaption></figure>

### 3.6 – Magnetic Interference Calculator Module <a href="#toc194419386" id="toc194419386"></a>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F45QIF5vXiq6B3ArOL0g1%2Fimage.png?alt=media&amp;token=96ddf4dd-aa3e-4d16-b3ab-c36b32df7ac1" alt="" width="563"><figcaption></figcaption></figure>

### 3.7 – Casing Standoff & Centralizer Spacing Module <a href="#toc194419387" id="toc194419387"></a>

* Model rigid and bow spring centralizers
* Automatically optimize centralizer placement based on a desired standoff value

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtC57fbOOTzDjFkTgYJLH%2Fimage.png?alt=media&amp;token=c13bfeb5-beeb-49bc-935a-7472d8d6183a" alt="" width="563"><figcaption></figcaption></figure>

* Calculate deflection at centralisers and mid joint

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRiDOQwhAKU4rTue3FXsa%2Fimage.png?alt=media&amp;token=12dfed66-886e-452b-a155-4a4e207cd315" alt="" width="563"><figcaption></figcaption></figure>

* Ability to model bow spring running and restoring forces
* Model the additional side force created by the compression of bow spring centralizers

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fk0JIeab1zZsslrCYboyl%2Fimage.png?alt=media&amp;token=c3ef470e-d8bc-4ade-a568-19b4d0b8ae9e" alt="" width="560"><figcaption></figcaption></figure>

* One click standoff summary report, including tabulated results accompanied by standoff, side forces and hookload charts.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXmjkaK6yXbX7jf3bORGv%2Fimage.png?alt=media&amp;token=46af303d-3d38-4dfb-baa1-f825d6f1e783" alt="" width="548"><figcaption></figcaption></figure>

### 3.8 - Jar Placement Module <a href="#toc194419388" id="toc194419388"></a>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F07zCVm9s5UNtxvarzUn2%2Fimage.png?alt=media&amp;token=3dfcf52e-2478-475b-8d9f-d6b41e326ecc" alt="" width="551"><figcaption></figcaption></figure>

* Calculates neutral point road map which shows WOB to avoid at every depth along the well path

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnJNLZCO3WAQhmW5BhWR1%2Fimage.png?alt=media&amp;token=ebcb15df-f2e6-475e-abee-53b3a4a11dfa" alt="" width="415"><figcaption></figcaption></figure>

* Calculates pump open force

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFIHbgN5yOxorpx3BdOvv%2Fimage.png?alt=media&amp;token=be20ca4b-59b6-4c4c-a6cb-7999c3c53181" alt="" width="311"><figcaption></figcaption></figure>

* Model the impact / impulse of all types of jars, accelerators & intensifiers

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ftrm6u6CWFbObUg34zZAc%2Fimage.png?alt=media&amp;token=91af37a8-197d-4385-829c-0b4483b014cf" alt="" width="398"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvoC47lOTDc8Kv7pkqdna%2Fimage.png?alt=media&amp;token=f29bb383-8f24-4075-9350-131ba77590e5" alt="" width="398"><figcaption></figcaption></figure>

### 3.9 – Cementing Design <a href="#toc194419389" id="toc194419389"></a>

* Cementing Schematic Animation gives a visual representation of the well geometry, string, and fluids at any given stage in the cement job

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F50BY5oJkFkk4IzwQ8Rb0%2Fimage.png?alt=media&amp;token=4c924a5a-3107-45ff-b079-73a10bfd3ed8" alt="" width="563"><figcaption></figcaption></figure>

* Calculate annular pressure, equivalent circulating density and pump pressure during cementing operations

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjyYIsFrQECu4wec8AZp6%2Fimage.png?alt=media&amp;token=95158b4d-bb14-499d-b236-6587b2d252c8" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpowjfpGslbgvWiDUlnS7%2Fimage.png?alt=media&amp;token=7265f9b5-2e1e-4a38-b340-b7177ea3655d" alt="" width="249"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBhN1RDmPi8mdXKdugORC%2Fimage.png?alt=media&amp;token=4159466b-62a2-45b9-95c4-6a647b6c69f5" alt="" width="563"><figcaption></figcaption></figure>

### 3.10 – Well Control <a href="#toc194419390" id="toc194419390"></a>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTgADHAMA7UCcT3NiuU3p%2Fimage.png?alt=media&amp;token=965afb4c-3d2d-4a2e-b483-06b4e1adb5fb" alt="" width="563"><figcaption></figcaption></figure>

## 4.0 - Operational Reporting Solution <a href="#toc201920640" id="toc201920640"></a>

Innova’s integrated Operational Reporting system provides end-to-end visibility and control of drilling activities, seamlessly connecting field data with office oversight through Innova Vantage and Vision mobile app. Our platform facilitates real-time data exchange, automated reporting workflows, and deep analytics, ensuring consistent, high-quality reporting across global operations. Whether tracking costs, personnel, KPIs, or equipment logistics, Innova enables each company to standardize and streamline reporting processes while enhancing data quality and decision-making through a secure, cloud-based environment.

The following section outlines the core features and functionalities of our operational reporting solution, highlighting its real-time data capabilities, reporting tools, and analytics-driven insights.

### 4.1 - Integrated Daily Reporting Package <a href="#toc194419371" id="toc194419371"></a>

Integrated within the Innova platform are advanced daily reporting features including:

* Daily Reports

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNcKNDMCEXT2pSLOspEZ2%2Fimage.png?alt=media&amp;token=7ad58ce7-1768-4c29-a9a0-acc7862f70e9" alt="" width="563"><figcaption></figcaption></figure>

* Slide Sheets
  * Auto populate Daily Reports directly from the slide sheet
  * Auto populate slide sheets via received WITS data

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FB86wyReWIczErhZsrC6g%2Fimage.png?alt=media&amp;token=6e68340e-f7d2-46f3-9668-c0a110498d4d" alt=""><figcaption></figcaption></figure>

* Drill String Editor

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0kscJRVwDgmJtlsl80iS%2Fimage.png?alt=media&amp;token=0518d142-1a60-462e-9551-c37c27eb9722" alt=""><figcaption></figcaption></figure>

* Tool Inventory

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDMkTP1OL0M4uj9KrDUSU%2Fimage.png?alt=media&amp;token=4e488fca-9f85-4fe7-a8ab-66cdac296543" alt=""><figcaption></figcaption></figure>

* Tool and Personnel Tracking
* Cost Tracking (Daily and Well)
* Shipping Tickets

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIKUvOnXaRAQxJAyviILc%2Fimage.png?alt=media&amp;token=cec343b1-697a-4e45-919c-e044864885c4" alt="" width="331"><figcaption></figcaption></figure>

* Pipe Tally

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8x6X4Jy91iFiKJm7ryEF%2Fimage.png?alt=media&amp;token=3c7df18d-fa3c-4e1a-bd15-6c17851e3f57" alt="" width="302"><figcaption></figcaption></figure>

* Motor and MWD Performance Reports

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwTwLTulSZwh6zgV2dEl8%2Fimage.png?alt=media&amp;token=032d7b20-510c-4781-a39b-af7a71e950f4" alt="" width="563"><figcaption></figcaption></figure>

* Motor and MWD Failure Reports
* Non-Mag Spacing Report

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnYPDCslSkLwbVltREuR4%2Fimage.png?alt=media&amp;token=e068aaa9-1dd1-4391-81a0-6324fcbaa05f" alt="" width="563"><figcaption></figcaption></figure>

* MWD Pre Run Verification Report
* End of Well Reports
* KPI Tracking

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvMAorNwwm1eZyMETKwlI%2Fimage.png?alt=media&amp;token=0a0ea276-99d1-4619-8293-36f846e390a6" alt="" width="563"><figcaption></figcaption></figure>

* Well statistics provides a detailed overview of the well data including well phases and BHA’s

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzJCqPKB4wzDpm4cn0UJc%2Fimage.png?alt=media&amp;token=5f658477-9440-4a3c-a1a7-efb957b7c5d0" alt="" width="563"><figcaption></figcaption></figure>

* Generate and output detailed reports at the click of a button
* Excel and PDF output
* Easily create and output custom reports and charts
* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIW4BwgA0qGWlsLZQ8qUl%2Fimage.png?alt=media&amp;token=db2779c0-849b-4746-af30-375d6e0f7869" alt="" width="435"><figcaption></figcaption></figure>

* Large and customisable catalogue of drilling components, casing centralizers and stop collars, for use in drill string and casing string design.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fu3kPXJMewzjGlaa02LZT%2Fimage.png?alt=media&amp;token=54424032-2a69-4477-9800-9e6d6f758e22" alt=""><figcaption></figcaption></figure>

* Real time updates from the field using Data Exchange and Data Sync allow co-ordinators to view reporting data at will without needing to wait for morning reports.

### 4.2 - Database Analytics Tool <a href="#toc194419372" id="toc194419372"></a>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7fVatL7ETs6HVtBIEDwu%2Fimage.png?alt=media&amp;token=dab00c4f-04f5-46fd-a853-83fc2ac3d64e" alt="" width="563"><figcaption></figcaption></figure>

* Plot all selected wells together on google maps. Surface locations, Plan and Survey trajectories and Lease Lines can all be displayed.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fl9n50PovSbTKcpN4G6fj%2Fimage.png?alt=media&amp;token=4c716a36-4cda-40dc-8132-3adb5f019639" alt="" width="563"><figcaption></figcaption></figure>

* Motor, MWD and Section KPI Reports

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCE97pHvQvxplqwKY52yl%2Fimage.png?alt=media&amp;token=820e8518-e0b5-4504-9af3-b634014fd423" alt=""><figcaption></figcaption></figure>

* Revenue Report

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRrWEsdRgiowIF8Cq3ZCE%2Fimage.png?alt=media&amp;token=d877d914-6be5-4643-b0d2-401985aa4ee6" alt=""><figcaption></figcaption></figure>

* Rig Days Report

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F38E5EBwQEFcCo8LEiQWN%2Fimage.png?alt=media&amp;token=e98e172b-4b89-45ba-92f2-e1a4c8cf1b3d" alt="" width="563"><figcaption></figcaption></figure>

* Personnel Utilisation Report

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FltrAmDT2QhhXl3I5LPf7%2Fimage.png?alt=media&amp;token=7c9883a8-08f7-4923-a289-ab94141ab09a" alt=""><figcaption></figcaption></figure>

* Well Ranking Report

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fbn9gJKIcW7J00Mz3wXv2%2Fimage.png?alt=media&amp;token=1864cead-588f-452b-8547-7718ddde7435" alt=""><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FF7MPaLGPT7Wgaw0PUs4E%2Fimage.png?alt=media&amp;token=c59cfb27-94d7-4493-8cad-2096e84bfc7e" alt="" width="563"><figcaption></figcaption></figure>

* Connection Analysis screen to monitor connection speed at the rig site.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fiswtz2jWSb8hHRwNGEGW%2Fimage.png?alt=media&amp;token=95fe8463-92d2-463d-90dd-bdfa86712084" alt="" width="511"><figcaption></figcaption></figure>

### 4.3 - Operational Oversight <a href="#toc194419373" id="toc194419373"></a>

* Full operational oversight of all active, upcoming and standby wells company wide

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9zrZuXMLH69suGVQXbmU%2Fimage.png?alt=media&amp;token=37cfa044-da9d-4c55-87f8-1ad0b3fdb3d0" alt="" width="563"><figcaption></figcaption></figure>

* Automated top level KPI data for all wells at a glance including Footage drilled, drilling hours and ROP

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F09a6r31OSkC9Z9glKiZp%2Fimage.png?alt=media&amp;token=e5700d2f-2e43-417b-8a40-bb2bb4fd9444" alt=""><figcaption></figcaption></figure>

* Time since last data exchange from the field
* Time since last WITS data received

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpWqX62rECHoLayqeOJ5z%2Fimage.png?alt=media&amp;token=bbe0f9c9-a516-462d-bd07-2cedacfa8fff" alt="" width="563"><figcaption></figcaption></figure>

* Depth vs Days

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGswvCLALvxrk7Soubdlg%2Fimage.png?alt=media&amp;token=363218bf-15d3-4989-ae26-6d40bebed090" alt="" width="563"><figcaption></figcaption></figure>

* Track location and condition of equipment in the field via the Logistics Dashboard

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZTRB5cf0RcaoBv08KQGR%2Fimage.png?alt=media&amp;token=4944e717-2c6e-4fcf-9a42-b88d0f4f548a" alt="" width="563"><figcaption></figcaption></figure>

* Standardise daily reporting nomenclature across your organization, including activity codes, phase codes, cost codes, rig and personnel names, and shipping addresses

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnVCFR9rhLYUddrEG2WM6%2Fimage.png?alt=media&amp;token=cf880d59-7cea-4e8e-bbe8-a991f757ab6c" alt="" width="284"><figcaption></figcaption></figure>

* Manage your organization’s survey tool models and co-ordinate reference systems

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fr5ICFhk1txhMVoF9GVEP%2Fimage.png?alt=media&amp;token=e0773962-63cc-4f04-a59f-07819ce7dd1e" alt="" width="563"><figcaption></figcaption></figure>

* Manage tool orders for your organization

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyQNt5yuxkwkIF4ZvqNWq%2Fimage.png?alt=media&amp;token=6ce55acd-841b-400d-b6bc-08cfce57c601" alt="" width="563"><figcaption></figcaption></figure>

* Access and manage bids and invoices, convert accepted bids to well cost codes

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3gctzdDz46ov5VABf9yg%2Fimage.png?alt=media&amp;token=68d6e205-5aac-42b9-b7dd-94177117e0f0" alt="" width="563"><figcaption></figcaption></figure>

* Track tool failures using the Incident Dashboard

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3G9ash0jLcEgVdn2ZQ2W%2Fimage.png?alt=media&amp;token=a4970cba-071f-4b8f-92ce-21cbced65c10" alt="" width="563"><figcaption></figcaption></figure>

### 4.4 – WITS & Remote Directional Drilling <a href="#toc201920644" id="toc201920644"></a>

* Supports WITS, WITSML and Wireless WITS connectivity

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FarC9dqDBiGyLke7fvHIK%2Fimage.png?alt=media&amp;token=cb616111-23d4-47b9-a875-d77ec8c7ad76" alt="" width="444"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuMyRuQoF9JfGYKJIEKhe%2Fimage.png?alt=media&amp;token=8db64604-89cd-4a38-b7a0-4c270940aec7" alt="" width="449"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYVDZHjhHqQSi21H2Qvpx%2Fimage.png?alt=media&amp;token=631536bc-5145-439b-a004-c6bd1f8a24f0" alt="" width="315"><figcaption></figcaption></figure>

* Integration with ROGII SoloBox, Nabors RigSense and Digidrill with one-click mnemonic setup.
* 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
* Fully customizable Electronic Data Reader (EDR)

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8fJiFKf8X6uwEycqsQTJ%2Fimage.png?alt=media&amp;token=01bb4380-a1db-4f78-a054-aed6202aca8f" alt="" width="563"><figcaption></figcaption></figure>

* Automatic assignment of rig states to track rig activity
* Store and view historical data from previously drilled and offset wells

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2kh59nP18JSMRicaZSbl%2Fimage.png?alt=media&amp;token=da296994-cd3d-4416-9fd6-2fd173db6d21" alt=""><figcaption></figcaption></figure>

* Set up alarms for stuck pipe, wellbore washout, motor stalls, etc.
* Use Muli-Well Dashboard to monitor multiple wells simultaneously on one screen.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fs9lBKEDkZTBUGKwBBtdp%2Fimage.png?alt=media&amp;token=2e9e3ddc-3c84-4350-bca7-6bf0d1b1ba40" alt="" width="563"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnBnPUuSYomznxVcsI0aw%2Fimage.png?alt=media&amp;token=e5caeb82-e3df-4d34-b38d-b6ab71f8c234" alt=""><figcaption></figcaption></figure>

* Real Time Data Exchange and Data Sync functionality allows field data to be updated on the SQL server database in real time.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FB90qeJzzalVTC0VNhLwf%2Fimage.png?alt=media&amp;token=79f5f49d-edcc-4342-9cae-c920183b6636" alt="" width="511"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKxEH3XZfNsSX6G9HwLAa%2Fimage.png?alt=media&amp;token=06db630d-d445-4d2a-8792-5e09355ee2bd" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHGrG8KMh141We5uWjg91%2Fimage.png?alt=media&amp;token=4e3cb3fb-0faf-471e-bd38-2b12d6b75669" alt="" width="434"><figcaption></figcaption></figure>

* Slide Analysis
* Connection Analysis

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FK8unNbq1oERXUSiCjId7%2Fimage.png?alt=media&amp;token=0eb8c82d-a915-4eb1-be31-b8b104ee3bbe" alt="" width="386"><figcaption></figcaption></figure>

### 4.5 - Optimization <a href="#toc194419374" id="toc194419374"></a>

* BHA recommendation tool suggests BHA designs based on offset well data.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFAqdfKSEVFLniaLHFlqd%2Fimage.png?alt=media&amp;token=43f3e13b-7dc9-4d23-9824-5c6adca74b97" alt=""><figcaption></figcaption></figure>

* Parameters Roadmap collates offset data to advise the driller on optimal drilling parameters in real time.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxWvfgRV3wHwjpV7biZag%2Fimage.png?alt=media&amp;token=c2502c52-6d46-4682-afeb-2c56d28165a8" alt=""><figcaption></figcaption></figure>

### 4.6 - Dashboards <a href="#toc201920646" id="toc201920646"></a>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuWX8myRkRT2b0IRWogz3%2Fimage.png?alt=media&amp;token=91ebc831-732f-4c66-bb9b-1d391ad78e14" alt="" width="532"><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FA9XOQf1ZHIcYoQGSctwy%2Fimage.png?alt=media&amp;token=b82c718f-dd6e-416a-aa3b-ecbcd20c42bb" alt="" width="532"><figcaption></figcaption></figure>

* 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.7 – Bid Sheets <a href="#toc194419370" id="toc194419370"></a>

* Quickly populate customer and Supplier addresses and details from dropdown lists

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4a7QGVXOaJkVYz9WY31i%2Fimage.png?alt=media&amp;token=fa5d25a6-5936-40d5-98b5-86d7f5aafe68" alt="" width="563"><figcaption></figcaption></figure>

* Print quotation including a cover letter and any relevant notes

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQkOIwWa5tJ5NHOtpxsra%2Fimage.png?alt=media&amp;token=dddf6734-6f47-443a-8a8a-bab59a78cba0" alt="" width="492"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAmRuKZSp6RFtI42aiWGx%2Fimage.png?alt=media&amp;token=39d83918-0949-45a6-9c6c-f891f03eabdc" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2PmGF1otLnPJgmXeBocq%2Fimage.png?alt=media&amp;token=04f64e29-76e9-41b0-b64a-d82dfeff6cd4" alt=""><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRan3QIsluzghUG0dVy4s%2Fimage.png?alt=media&amp;token=61b0feef-6635-4809-9535-4cd8b9d89506" alt="" width="448"><figcaption></figcaption></figure>

* Bids are approved by users with the relevant user permissions
* Bids can be Archived by users with the relevant user permissions

### 4.8 – Third Party Services Integration <a href="#toc194419375" id="toc194419375"></a>

**Merge Solutions**: Cost and asset tracking via integration with Merge’s OASIS software

**SureShop**: Seamlessly import tools and inventories from SureShop and export tool runs from Well Seeker

**ZerdaLab**: AI-powered automated bit dull grading, integrated into Innova Vantage and Vision mobile app.

**Superior QC**: Survey correction integration. Pull corrected surveys directly from the Superior QC server into Well Seeker. Can also accommodate HIFI Nav surveys.

**RoundLab**: Survey correction integration. Pull corrected surveys directly from the RoundLab server into Well Seeker

**H\&P Survey Management**: Survey correction integration. Pull corrected surveys directly from the H\&P server into Well Seeker

**Halliburton Max Survey**: Survey correction integration. Pull corrected surveys directly from the Halliburton 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, SoloBox WITSML integration

**British Geological Survey:** Integration with BGGM Hypercube IFR and BGGM Error Estimates

**Peloton:** Synchronization with Peloton allows for seamless exchange of BHA and survey data with WellView users.

**Xcalibur Smart Mapping:** Integration with Xcalibur MagCUBE IFR.


# Presentations

Click on the links below to view our promotional presentations for our suite of Innova products.


# Innova Products Overview

{% embed url="<https://docs.google.com/presentation/d/e/2PACX-1vRHUPqEYT09is_mvIf5tyOLyfwACFWHLFN4FwGCG19VCRk44AmRjG_Sner53LqiDNkfVCAfBSb_GEdm/pub?delayms=30000&loop=false&start=false>" %}


# WELL SEEKER X

Use the controls in the bottom left to scroll through our WELL SEEKER X promotional presentation.

{% embed url="<https://docs.google.com/presentation/d/e/2PACX-1vTYyS1Fm0FloaMvUL8Tfr-X3dDRvaaj9wWKWL92hxzMdTZgDXNpvvnnFreBiWprMwxGwHlABFDa68g-/pub?delayms=30000&loop=false&start=false>" %}


# VANTAGE

Use the controls in the bottom left to scroll through our VANTAGE promotional presentation.

{% embed url="<https://docs.google.com/presentation/d/e/2PACX-1vQhRtIle8OSs99-D9vI-OBkQHRMe75nAdxsBmnZ98oqMbHbGjqFTH_6_cLh4T1roMRMvz0lmNDab1OL/pub?delayms=30000&loop=false&start=false>" %}


# NEXUS

Use the controls in the bottom left to scroll through our NEXUS promotional presentation.

{% embed url="<https://docs.google.com/presentation/d/e/2PACX-1vTVXFEbfCnn2ezXY7GiZCVZpeL41BUgT1kX0CAIawwJXomjMFlpxL5ovnBDghbdJqhHSlcowYnWUFNJ/pub?delayms=30000&loop=false&start=false>" %}


# Getting Started with Well Seeker X

Follow these steps to install Well Seeker X (WSX), access resources, and manage your license.

## **Download & Install**

* [**Software Installers**](https://www.innova-drilling.com/download/trial)**:** Download the latest installation files. Click on **Existing Users** to access the download links.
* [**Installation Guide**](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-installation-guide)**:** Step-by-step instructions, compatibility notes, and troubleshooting tips.
* [**Innova Documentation Portal**](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-how-to-guide)**:** Access manuals, quick start guides, and video tutorials.

## **License Information**

WSX includes a **2-day evaluation license** by default. To extend this evaluation or renew an existing license:

* Open WSX
* When the **License Expiration dialog** appears, select **Request License**.
  * If you already have a paid license, this dialog appears when less than **30 days** remain.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLuKr8eask1sMSM6LP1Ex%2F0.png?alt=media)

* Complete the form and add details in the **Comments** field (e.g., *extend evaluation*, *renew license*).

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSqe0LDC3UmDj5JoPQ50g%2F1.png?alt=media)

* Click **Submit**. You will receive:
  * A **confirmation email**, followed by
  * A **license email** from a no-reply address once your license is generated.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0b2KoxBE1oxraE9E95X8%2F2.png?alt=media)

* Check your **Junk Mail** folder if you don’t receive these emails.

## **Sample Database**

An optional sample database with pre-populated data is available.

To load the sample database:

1. Download the demo database from the link below.

{% file src="/files/3q4IOE31eWBH31NTSCGF" %}

2. Save the zip file somewhere on your PC and unzip the database.
3. Open **WSX** → **Home Tab** → **Select Database** → choose the unzipped file.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZWh9QPghV6klhyCPPVWK%2F3.png?alt=media)


# Getting Started with Innova Engineering

Follow these steps to install Innova Engineering, access resources, and manage your license.

## **Download & Install**

* [**Software Installers**](https://www.innova-drilling.com/download/trial)**:** Download the latest installation files. Click on **Existing Users** to access the download links.
* [**Installation Guide**](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/innova-engineering-guides/installation)**:** Step-by-step installation instructions.
* [**Innova Documentation Portal**](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/innova-engineering-guides)**:** Access manuals, quick start guides, and video tutorials.

## **License Information**

Innova Engineering includes a **2-day evaluation license** by default. To extend this evaluation or renew an existing license:

* Open Innova Engineering.
* When the **License Expiration** dialog appears, select **Request License**.
  * If you already have a paid license, this dialog appears when **less than 30 days remain**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2gVEgFgGmsVqKxZVl4RW%2F0.png?alt=media" alt="" width="497">

* Complete the form and add details in the **Comments** field (e.g., *extend evaluation*, *renew license*).

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGTdMoEOgKvDib8BWsfoQ%2F1.png?alt=media" alt="" width="350">

* Click **Submit**. You will receive:
  * A confirmation email, followed by
  * A license email from a no-reply address once your license is generated.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ff2fDGBY28vFaTu7Nc9M2%2F2.png?alt=media)

* Check your **Junk Mail** folder if you don’t receive these emails.

## **Example Projects**

Innova Engineering comes with pre-loaded example projects that you can explore to get familiar with the software.

To open them:

1. Launch Innova Engineering.
2. Select **File → Open → Example Projects folder**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FloxW6oms9nbhSOUIxXXT%2F3.png?alt=media)

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FaBl465om3YVc9Mfl673s%2F4.png?alt=media" alt="" width="563">


# Getting Started with Innova Vantage

## Introduction

Innova Vantage allows you to securely access your company’s server database from any internet-enabled device—no installation required. It provides real-time visibility of data, dashboards, and reports through a simple web interface.

Access is available for two types of users:

* **Existing Clients** – Users who work for a company that currently uses the Innova Suite of Software.
* **Trial Users** – Users who would like to trial Vantage.
* In both cases, your company email will become your **Username**.

## **Request Access**

* If you are an existing client, to get started you will need to provide your **company email address** to either your company admin or Innova support.
* If you are not an existing client, you can fill the form on [**Innova Website**](https://www.innova-drilling.com/download/trial) to request a free trial.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ffo0oCVU8okp3Gtm60s1f%2F0.png?alt=media)

## **Account Provisioning**

Once your email is received, you’ll be added to one of the following:

* **Your Company’s Database** – if your organization is an existing client.
* **Demo Database** – for trial access and exploration.

## **Login Instructions**

1. Navigate to the [**Innova Vantage login page**.](https://vantage.innova-drilling.com/)
   * If your organisation is based in the EU, [**use this page to log in**](https://vantageeu.innova-drilling.com/).
   * If your organisation is based in the Middle East, [**use this page to log in**](https://vantageuae.innova-drilling.com/)

![
](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdnXOt7nC12N5buZyn9Sm%2F1.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FH5uCRltQxOUBiUgVDprv%2F2.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5VgEliqBwQ9tqbKAdPBE%2F3.png?alt=media)

2. Enter your **Username** (your company email) and the temporary **password** provided via email.
3. **Change your password** on first login—follow the prompt.

## **User Roles & Permissions**

Depending on your requirements, you will be assigned one of the following roles:

* **Viewer** – Read-only access to projects and dashboards.
* **Editor** – Can modify data and upload new files.
* **Administrator** – Full control, including user management.

*If you need additional permissions, please contact Innova Support.*

## **Sample Data**

* The **Demo Database** includes a sample project **Cerberus 14 28 – 3H (LH)**
  * This includes complete daily reports, EDR data and an Engineering case.
* The Innova Vantage manual can be accessed from our [**documentation page**.](https://docs.innova-drilling.com/introduction/innova-engineering-manual/innova-vantage-manual)


# Innova Generic Documents

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


# Innova Privacy Policy

Last updated: January 09, 2025

This Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your information when You use the Service and tells You about Your privacy rights and how the law protects You.

We use Your Personal data to provide and improve the Service. By using the Service, You agree to the collection and use of information in accordance with this Privacy Policy.

## Interpretation and Definitions

### Interpretation

The words of which the initial letter is capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in singular or in plural.

### Definitions

For the purposes of this Privacy Policy:

**Account** means a unique account created for You to access our Service or parts of our Service.

**Affiliate** means an entity that controls, is controlled by or is under common control with a party, where "control" means ownership of 50% or more of the shares, equity interest or other securities entitled to vote for election of directors or other managing authority.

**Application** means the software program provided by the Company downloaded by You on any electronic device, named Innova App

**Business**, for the purpose of the CCPA (California Consumer Privacy Act), refers to the Company as the legal entity that collects Consumers' personal information and determines the purposes and means of the processing of Consumers' personal information, or on behalf of which such information is collected and that alone, or jointly with others, determines the purposes and means of the processing of consumers' personal information, that does business in the State of California.

**Company** (referred to as either "the Company", "We", "Us" or "Our" in this Agreement) refers to INNOVA DRILLING AND INTERVENTION LIMITED , Union Plaza (6th Floor), 1 Union Wynd, Aberdeen, AB10 1DQ.

For the purpose of the GDPR, the Company is the Data Controller.

**Consumer**, for the purpose of the CCPA (California Consumer Privacy Act), means a natural person who is a California resident. A resident, as defined in the law, includes (1) every individual who is in the USA for other than a temporary or

transitory purpose, and (2) every individual who is domiciled in the USA who is outside the USA for a temporary or transitory purpose.

**Cookies** are small files that are placed on Your computer, mobile device or any other device by a website, containing the details of Your browsing history on that website among its many uses.

**Country** refers to: United Kingdom

**Data Controller**, for the purposes of the GDPR (General Data Protection Regulation), refers to the Company as the legal person which alone or jointly with others determines the purposes and means of the processing of Personal Data.

**Device** means any device that can access the Service such as a computer, a cellphone or a digital tablet.

**Do Not Track** (DNT) is a concept that has been promoted by US regulatory authorities, in particular the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing internet users to control the tracking of their online activities across websites.

**Facebook Fan Page** is a public profile named Innova Drilling And Intervention specifically created by the Company on the Facebook social network, accessible from [www.facebook.com/InnovaDrillingandIntervention/](http://www.facebook.com/InnovaDrillingandIntervention/)

**Personal Data** is any information that relates to an identified or identifiable individual.

For the purposes for GDPR, Personal Data means any information relating to You such as a name, an identification number, location data, online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity.

For the purposes of the CCPA, Personal Data means any information that identifies, relates to, describes or is capable of being associated with, or could reasonably be linked, directly or indirectly, with You.

**Sale**, for the purpose of the CCPA (California Consumer Privacy Act), means selling, renting, releasing, disclosing, disseminating, making available, transferring, or otherwise communicating orally, in writing, or by electronic or other means, a Consumer's personal information to another business or a third party for monetary or other valuable consideration.

**Service** refers to the Application or the Website or both.

**Service Provider** means any natural or legal person who processes the data on behalf of the Company. It refers to third-party companies or individuals employed by the Company to facilitate the Service, to provide the Service on behalf of the Company, to perform services related to the Service or to assist the Company in analyzing how the Service is used. For the purpose of the GDPR, Service Providers are considered Data Processors.

**Usage Data** refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself (for example, the duration of a page visit).

**Website** refers to Innova Web Portal , accessible from <https://www.innova-drilling.com/>

**You** means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.

Under GDPR (General Data Protection Regulation), You can be referred to as the Data Subject or as the User as you are the individual using the Service.

## Collecting and Using Your Personal Data

### Types of Data Collected

#### Personal Data

While using Our Service, We may ask You to provide Us with certain personally identifiable information that can be used to contact or identify You. Personally identifiable information may include, but is not limited to:

* Email address
* First name and last name Phone number
* Address, State, Province, ZIP/Postal code, City
* Bank account information in order to pay for products and/or services within the Service
* Usage Data

When You pay for a product and/or a service via bank transfer, We may ask You to provide information to facilitate this transaction and to verify Your identity. Such information may include, without limitation:

* Date of birth
* Passport or National ID card
* Bank card statement
* Other information linking You to an address

#### Usage Data

Usage Data is collected automatically when using the Service.

Usage Data may include information such as Your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

When You access the Service by or through a mobile device, We may collect certain information automatically, including, but not limited to, the type of mobile device You use,

Your mobile device unique ID, the IP address of Your mobile device, Your mobile operating system, the type of mobile Internet browser You use, unique device identifiers and other diagnostic data.

We may also collect information that Your browser sends whenever You visit our Service or when You access the Service by or through a mobile device.

#### Information Collected while Using the Application

While using Our Application, in order to provide features of Our Application, We may collect, with Your prior permission:

* Information regarding your location
* Pictures and other information from your Device's camera and photo library

We use this information to provide features of Our Service, to improve and customize Our Service. The information may be uploaded to the Company's servers and/or a Service Provider's server or it may be simply stored on Your device.

You can enable or disable access to this information at any time, through Your Device settings.

#### Tracking Technologies and Cookies

We use Cookies and similar tracking technologies to track the activity on Our Service and store certain information. Tracking technologies used are beacons, tags, and scripts to collect and track information and to improve and analyze Our Service. The technologies We use may include:

* **Cookies or Browser Cookies.** A cookie is a small file placed on Your Device. You can instruct Your browser to refuse all Cookies or to indicate when a Cookie is being sent. However, if You do not accept Cookies, You may not be able to use some parts of our Service. Unless you have adjusted Your browser setting so that it will refuse Cookies, our Service may use Cookies.
* **Web Beacons.** Certain sections of our Service and our emails may contain small electronic files known as web beacons (also referred to as clear gifs, pixel tags, and single-pixel gifs) that permit the Company, for example, to count users who have visited those pages or opened an email and for other related website statistics (for example, recording the popularity of a certain section and verifying system and server integrity).

Cookies can be "Persistent" or "Session" Cookies. Persistent Cookies remain on Your personal computer or mobile device when You go offline, while Session Cookies are deleted as soon as You close Your web browser. You can learn more about cookies here: [All About Cookies by TermsFeed](https://www.termsfeed.com/blog/cookies/).

We use both Session and Persistent Cookies for the purposes set out below:

#### **Necessary / Essential Cookies**&#x20;

* **Type:** Session Cookies
* **Administered by:** Us
* **Purpose:** These Cookies are essential to provide You with services available through the Website and to enable You to use some of its features. They help to authenticate users and prevent fraudulent use of user accounts. Without these Cookies, the services that You have asked for cannot be provided, and We only use these Cookies to provide You with those services.

#### Cookies Policy / Notice Acceptance Cookies

* **Type:** Persistent Cookies&#x20;
* **Administered by:** Us
* **Purpose:** These Cookies identify if users have accepted the use of cookies on the Website.

#### **Functionality Cookies**&#x20;

* **Type:** Persistent Cookies&#x20;
* **Administered by:** Us
* **Purpose:** These Cookies allow us to remember choices You make when You use the Website, such as remembering your login details or language preference. The purpose of these Cookies is to provide You with a more personal experience and to avoid You having to re-enter your preferences every time You use the Website.

#### Granular Cookie Preferences

We use the following types of cookies:

* Essential Cookies: Required for website functionality.
* Performance Cookies: Track user interaction to improve site performance.
* Targeting Cookies: Used for advertising purposes.

#### Global Privacy Control (GPC) Signals:

We honor GPC signals, allowing you to automatically opt out of data sharing for targeting advertising.

For more information about the cookies we use and your choices regarding cookies, please visit our Cookies Policy or the Cookies section of our Privacy Policy.

### Use of Your Personal Data

The Company may use Personal Data for the following purposes:

**To provide and maintain our Service**, including to monitor the usage of our Service.

**To manage Your Account:** to manage Your registration as a user of the Service. The Personal Data You provide can give You access to different functionalities of the Service that are available to You as a registered user.

**For the performance of a contract:** the development, compliance and undertaking of the purchase contract for the products, items or services You have purchased or of any other contract with Us through the Service.

**To contact You:** To contact You by email, telephone calls, SMS, or other equivalent forms of electronic communication, such as a mobile application's push notifications regarding updates or informative communications related to the functionalities, products or contracted services, including the security updates, when necessary or reasonable for their implementation.

**To provide You** with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless You have opted not to receive such information.

**To manage Your requests:** To attend and manage Your requests to Us.

**For business transfers:** We may use Your information to evaluate or conduct a merger, divestiture, restructuring, reorganization, dissolution, or other sale or transfer of some or all of Our assets, whether as a going concern or as part of bankruptcy, liquidation, or similar proceeding, in which Personal Data held by Us about our Service users is among the assets transferred.

**For other purposes**: We may use Your information for other purposes, such as data analysis, identifying usage trends, determining the effectiveness of our promotional campaigns and to evaluate and improve our Service, products, services, marketing and your experience.

We may share Your personal information in the following situations:

* **With Service Providers:** We may share Your personal information with Service Providers to monitor and analyze the use of our Service, for payment processing, to contact You.
* **For business transfers:** We may share or transfer Your personal information in connection with, or during negotiations of, any merger, sale of Company assets, financing, or acquisition of all or a portion of Our business to another company.
* **With Affiliates:** We may share Your information with Our affiliates, in which case we will require those affiliates to honor this Privacy Policy. Affiliates include Our parent company and any other subsidiaries, joint venture partners or other companies that We control or that are under common control with Us.
* **With business partners:** We may share Your information with Our business partners to offer You certain products, services or promotions.
* **With other users:** when You share personal information or otherwise interact in the public areas with other users, such information may be viewed by all users and may be publicly distributed outside.
* **With Your consent**: We may disclose Your personal information for any other purpose with Your consent.

### Retention of Your Personal Data

The Company will retain Your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use Your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.

The Company will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period of time, except when this data is used to strengthen the security or to improve the functionality of Our Service, or We are legally obligated to retain this data for longer time periods.

### Transfer of Your Personal Data

Your information, including Personal Data, is processed at the Company's operating offices and in any other places where the parties involved in the processing are located. It means that this information may be transferred to — and maintained on — computers located outside of Your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from Your jurisdiction.

Your consent to this Privacy Policy followed by Your submission of such information represents Your agreement to that transfer.

The Company will take all steps reasonably necessary to ensure that Your data is treated securely and in accordance with this Privacy Policy and no transfer of Your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of Your data and other personal information.

If your personal data is transferred outside the European Economic Area (EEA) or the UK, we ensure appropriate safeguards such as:

* Standard Contractual Clauses (SCCs): Contracts ensuring the data is protected to GDPR standards.
* Adequacy Decisions: Transfers to countries approved by the European Commission or UK as having adequate protections.

### Disclosure of Your Personal Data

#### Business Transactions

If the Company is involved in a merger, acquisition or asset sale, Your Personal Data may be transferred. We will provide notice before Your Personal Data is transferred and becomes subject to a different Privacy Policy.

#### Law enforcement

Under certain circumstances, the Company may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency) .

#### Other legal requirements

The Company may disclose Your Personal Data in the good faith belief that such action is necessary to:

* Comply with a legal obligation
* Protect and defend the rights or property of the Company
* Prevent or investigate possible wrongdoing in connection with the Service
* Protect the personal safety of Users of the Service or the public
* Protect against legal liability

### Security of Your Personal Data

**We implement robust security measures, including:**

* Encryption: Your data is encrypted both in transit and at rest.
* Access Controls: Access to your data is restricted to authorized personnel only.
* Regular Audits: We conduct regular security audits and penetration testing to identify vulnerabilities.

While we strive to protect your data, no method of transmission over the Internet is entirely secure.

## Detailed Information on the Processing of Your Personal Data

The Service Providers We use may have access to Your Personal Data. These third-party vendors collect, store, use, process and transfer information about Your activity on Our Service in accordance with their Privacy Policies.

### Payments

We may provide paid products and/or services within the Service. In that case, we may use third-party services for payment processing (e.g. payment processors).

We will not store or collect Your payment card details. That information is provided directly to Our third-party payment processors whose use of Your personal information is governed by their Privacy Policy. These payment processors adhere to the standards set by PCI-DSS as managed by the PCI Security Standards Council, which is a joint effort of brands like Visa, Mastercard, American Express and Discover. PCI-DSS requirements help ensure the secure handling of payment information.

**Barclays Bank PLC:** Their Privacy Policy can be viewed at <https://www.barclays.co.uk/important-information/privacy-policy/>

When You use Our Service to pay a product and/or service via bank transfer, We may ask You to provide information to facilitate this transaction and to verify Your identity.

### Usage, Performance and Miscellaneous

We may use third-party Service Providers to provide better improvement of our Service.

**Google Places:** Google Places is a service that returns information about places using HTTP requests. It is operated by Google. Google Places service may collect information from You and from Your Device for security purposes. The information gathered by Google Places is held in accordance with the Privacy Policy of Google: <https://www.google.com/intl/en/policies/privacy/>

## GDPR Privacy

### Legal Basis for Processing Personal Data under GDPR

This Privacy Policy applies to processing of personal data under both EU GDPR and UK GDPR. For users in the UK, the Company acts as a Data Controller under UK GDPR. Our legal basis for processing your data under UK GDPR includes:

* **Compliance with a legal obligation under UK law.**
* **Performance of a contract with you.**
* **Legitimate interests pursued by us, balanced with your rights.**

In any case, the Company will gladly help to clarify the specific legal basis that applies to the processing, and in particular whether the provision of Personal Data is a statutory or contractual requirement, or a requirement necessary to enter into a contract.

### Your Rights under the GDPR

The Company undertakes to respect the confidentiality of Your Personal Data and to guarantee You can exercise Your rights.

You have the right under this Privacy Policy, and by law if You are within the EU, to:

* **Request access to Your Personal Data.** The right to access, update or delete the information We have on You. Whenever made possible, you can access, update or request deletion of Your Personal Data directly within Your account settings section. If you are unable to perform these actions yourself, please contact Us to assist You. This also enables You to receive a copy of the Personal Data We hold about You.
* **Request correction of the Personal Data that We hold about You.** You have the right to have any incomplete or inaccurate information We hold about You corrected.
* **Object to processing of Your Personal Data.** This right exists where We are relying on a legitimate interest as the legal basis for Our processing and there is something about Your particular situation, which makes You want to object to our processing of Your Personal Data on this ground. You also have the right to object where We are processing Your Personal Data for direct marketing purposes.
* **Request erasure of Your Personal Data.** You have the right to ask Us to delete or remove Personal Data when there is no good reason for Us to continue processing it.
* **Right to Object to Automated Decision-Making.** If we use automated decision-making or profiling that produces significant legal or similar effects, you have the right to:
  * Request human intervention.
  * Express your point of view.
  * Contest the decision.

Please contact us at <support@innova-drilling.com> if you would like to exercise this right.

* **Request the transfer of Your Personal Data.** We will provide to You, or to a third- party You have chosen, Your Personal Data in a structured, commonly used, machine- readable format. Please note that this right only applies to automated information which You initially provided consent for Us to use or where We used the information to perform a contract with You.
* **Withdraw Your consent.** You have the right to withdraw Your consent on using your Personal Data. If You withdraw Your consent, We may not be able to provide You with access to certain specific functionalities of the Service.

### Exercising of Your GDPR Data Protection Rights

You may exercise Your rights of access, rectification, cancellation and opposition by contacting Us. Please note that we may ask You to verify Your identity before responding to such requests. If You make a request, We will try our best to respond to You as soon as possible.

You have the right to complain to a Data Protection Authority about Our collection and use of Your Personal Data. For more information, if You are in the European Economic Area (EEA), please contact Your local data protection authority in the EEA.

## Facebook Fan Page

### Data Controller for the Facebook Fan Page

The Company is the Data Controller of Your Personal Data collected while using the Service. As operator of the Facebook Fan Page [www.facebook.com/InnovaDrillingandIntervention/,](http://www.facebook.com/InnovaDrillingandIntervention/) the Company and the operator of the social network Facebook are Joint Controllers.

The Company has entered into agreements with Facebook that define the terms for use of the Facebook Fan Page, among other things. These terms are mostly based on the Facebook Terms of Service: [www.facebook.com/terms.php](http://www.facebook.com/terms.php)

Visit the Facebook Privacy Policy [www.facebook.com/policy.php](http://www.facebook.com/policy.php) for more information about how Facebook manages Personal data or contact Facebook online, or by mail: Facebook, Inc. ATTN, Privacy Operations, 1601 Willow Road, Menlo Park, CA 94025, United States.

### Facebook Insights

We use the Facebook Insights function in connection with the operation of the Facebook Fan Page and on the basis of the GDPR, in order to obtain anonymized statistical data about Our users.

For this purpose, Facebook places a Cookie on the device of the user visiting Our Facebook Fan Page. Each Cookie contains a unique identifier code and remains active for a period of two years, except when it is deleted before the end of this period.

Facebook receives, records and processes the information stored in the Cookie, especially when the user visits the Facebook services, services that are provided by other members of the Facebook Fan Page and services by other companies that use Facebook services.

For more information on the privacy practices of Facebook, please visit Facebook Privacy Policy here: [www.facebook.com/privacy/explanation](http://www.facebook.com/privacy/explanation)

## CCPA Privacy

This privacy notice section for California residents supplements the information contained in Our Privacy Policy and it applies solely to all visitors, users, and others who reside in the State of California.

### Categories of Personal Information Collected

We collect information that identifies, relates to, describes, references, is capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular Consumer or Device. The following is a list of categories of personal information which we may collect or may have been collected from California residents within the last twelve (12) months.

Please note that the categories and examples provided in the list below are those defined in the CCPA. This does not mean that all examples of that category of personal information were in fact collected by Us, but reflects our good faith belief to the best of our knowledge that some of that information from the applicable category may be and may have been collected. For example, certain categories of personal information would only be collected if You provided such personal information directly to Us.

#### Category A: Identifiers.

**Examples:** A real name, alias, postal address, unique personal identifier, online identifier, Internet Protocol address, email address, account name, driver's license number, passport number, or other similar identifiers.

**Collected:** Yes.

#### Category B: Personal information categories listed in the California Customer Records statute (Cal. Civ. Code § 1798.80(e)).

**Examples:** A name, signature, Social Security number, physical characteristics or description, address, telephone number, passport number, driver's license or state identification card number, insurance policy number, education, employment, employment history, bank account number, credit card number, debit card number, or any other financial information, medical information, or health insurance information. Some personal information included in this category may overlap with other categories.

**Collected:** Yes.

#### Category C: Protected classification characteristics under California or federal law.

**Examples:** Age (40 years or older), race, color, ancestry, national origin, citizenship, religion or creed, marital status, medical condition, physical or mental disability, sex (including gender, gender identity, gender expression, pregnancy or childbirth and related medical conditions), sexual orientation, veteran or military status, genetic information (including familial genetic information).

**Collected:** No.

**New Rights Under CPRA:**&#x20;

California residents have additional rights under the California Privacy Rights Act (CPRA), effective January 1, 2023. These include:

Right to Correct Inaccurate Personal Data: You may request corrections to any inaccurate Personal Data we hold about you.

Right to Limit Use of Sensitive Personal Information: If we collect sensitive personal information (e.g., financial details, precise geolocation, or biometric data), you may request that we limit its use to only what is necessary to provide the services or fulfill legal obligations.

To exercise your CPRA rights, please contact us at [support@innova-drilling.com.](mailto:support@innova-drilling.com)

#### Category D: Commercial information.

**Examples:** Records and history of products or services purchased or considered.&#x20;

**Collected:** Yes.

#### Category E: Biometric information.

**Examples:** Genetic, physiological, behavioral, and biological characteristics, or activity patterns used to extract a template or other identifier or identifying information, such as, fingerprints, faceprints, and voiceprints, iris or retina scans, keystroke, gait, or other physical patterns, and sleep, health, or exercise data.&#x20;

**Collected:** No.

#### **Category F: Internet or other similar network activity.**&#x20;

**Examples:** Interaction with our Service or advertisement.&#x20;

**Collected:** Yes.

#### **Category G: Geolocation data.**&#x20;

**Examples:** Approximate physical location.&#x20;

**Collected:** Yes.

#### Category H: Sensory data.

**Examples:** Audio, electronic, visual, thermal, olfactory, or similar information.&#x20;

**Collected:** No.

#### **Category I: Professional or employment-related information.**

**Examples:** Current or past job history or performance evaluations.&#x20;

**Collected:** No.

#### Category J: Non-public education information (per the Family Educational Rights and Privacy Act (20 U.S.C. Section 1232g, 34 C.F.R. Part 99))

**Examples:** Education records directly related to a student maintained by an educational institution or party acting on its behalf, such as grades, transcripts, class lists, student schedules, student identification codes, student financial information, or student disciplinary records.

**Collected:** No.

**Category K: Inferences drawn from other personal information.**&#x20;

Examples: Profile reflecting a person's preferences, characteristics, psychological, trends, predispositions, behavior, attitudes, intelligence, abilities, and aptitudes.

Collected: No.

Under CCPA, personal information does not include:

* Publicly available information from government records
* Deidentified or aggregated consumer information
* Information excluded from the CCPA's scope, such as:
  * Health or medical information covered by the Health Insurance Portability and Accountability Act of 1996 (HIPAA) and the California Confidentiality of Medical Information Act (CMIA) or clinical trial data
  * Personal Information covered by certain sector-specific privacy laws, including the Fair Credit Reporting Act (FRCA), the Gramm-Leach-Bliley Act (GLBA) or California Financial Information Privacy Act (FIPA), and the Driver's Privacy Protection Act of 1994

### Sources of Personal Information

We obtain the categories of personal information listed above from the following categories of sources:

* **Directly from You**. For example, from the forms You complete on our Service, preferences You express or provide through our Service, or from Your purchases on our Service.
* **Indirectly from You**. For example, from observing Your activity on our Service.
* **Automatically from You**. For example, through cookies We or our Service Providers set on Your Device as You navigate through our Service.
* **From Service Providers**. For example, third-party vendors for payment processing, or other third-party vendors that We use to provide the Service to You.

### **Use of Personal Information for Business Purposes or Commercial Purposes**&#x20;

We may use or disclose personal information We collect for "business purposes" or "commercial purposes" (as defined under the CCPA), which may include the following examples:

* To operate our Service and provide You with our Service.
* To provide You with support and to respond to Your inquiries, including to investigate and address Your concerns and monitor and improve our Service.
* To fulfill or meet the reason You provided the information. For example, if You share Your contact information to ask a question about our Service, We will use that personal information to respond to Your inquiry. If You provide Your personal information to purchase a product or service, We will use that information to process Your payment and facilitate delivery.
* To respond to law enforcement requests and as required by applicable law, court order, or governmental regulations.
* As described to You when collecting Your personal information or as otherwise set forth in the CCPA.
* For internal administrative and auditing purposes.
* To detect security incidents and protect against malicious, deceptive, fraudulent or illegal activity, including, when necessary, to prosecute those responsible for such activities.

Please note that the examples provided above are illustrative and not intended to be exhaustive. For more details on how we use this information, please refer to the "Use of Your Personal Data" section.

If We decide to collect additional categories of personal information or use the personal information We collected for materially different, unrelated, or incompatible purposes We will update this Privacy Policy.

### Disclosure of Personal Information for Business Purposes or Commercial Purposes

We may use or disclose and may have used or disclosed in the last twelve (12) months the following categories of personal information for business or commercial purposes:

* Category A: Identifiers
* Category B: Personal information categories listed in the California Customer Records statute (Cal. Civ. Code § 1798.80(e))
* Category D: Commercial information
* Category F: Internet or other similar network activity
* Category G: Geolocation data

Please note that the categories listed above are those defined in the CCPA. This does not mean that all examples of that category of personal information were in fact disclosed, but reflects our good faith belief to the best of our knowledge that some of that information from the applicable category may be and may have been disclosed.

When We disclose personal information for a business purpose or a commercial purpose, We enter a contract that describes the purpose and requires the recipient to both keep that personal information confidential and not use it for any purpose except performing the contract.

### Sale of Personal Information

We do not sell your personal information for monetary consideration. However, under CPRA, “sale” includes “sharing” for targeted advertising purposes. You can opt out of such sharing by contacting us or using the “Do Not Sell or Share My Personal Information” link on our website.

Please note that the categories listed below are those defined in the CCPA. This does not mean that all examples of that category of personal information were in fact sold, but

reflects our good faith belief to the best of our knowledge that some of that information from the applicable category may be and may have been shared for value in return.

We may sell and may have sold in the last twelve (12) months the following categories of personal information:

* Category A: Identifiers
* Category B: Personal information categories listed in the California Customer Records statute (Cal. Civ. Code § 1798.80(e))
* Category D: Commercial information
* Category F: Internet or other similar network activity
* Category G: Geolocation data

### Share of Personal Information

We may share Your personal information identified in the above categories with the following categories of third parties:

* Service Providers
* Payment processors
* Our affiliates
* Our business partners
* Third party vendors to whom You or Your agents authorize Us to disclose Your personal information in connection with products or services We provide to You

### Sale of Personal Information of Minors Under 16 Years of Age

We do not knowingly collect personal information from minors under the age of 16 through our Service, although certain third party websites that we link to may do so. These third- party websites have their own terms of use and privacy policies and we encourage parents and legal guardians to monitor their children's Internet usage and instruct their children to never provide information on other websites without their permission.

We do not sell the personal information of Consumers We actually know are less than 16 years of age, unless We receive affirmative authorization (the "right to opt-in") from either the Consumer who is between 13 and 16 years of age, or the parent or guardian of a Consumer less than 13 years of age. Consumers who opt-in to the sale of personal information may opt-out of future sales at any time. To exercise the right to opt-out, You (or Your authorized representative) may submit a request to Us by contacting Us.

If You have reason to believe that a child under the age of 13 (or 16) has provided Us with personal information, please contact Us with sufficient detail to enable Us to delete that information.

### Your Rights under the CCPA

The CCPA provides California residents with specific rights regarding their personal information. If You are a resident of California, You have the following rights:

* **The right to notice.** You have the right to be notified which categories of Personal Data are being collected and the purposes for which the Personal Data is being used.
* **The right to request.** Under CCPA, You have the right to request that We disclose information to You about Our collection, use, sale, disclosure for business purposes and share of personal information. Once We receive and confirm Your request, We will disclose to You:
  * The categories of personal information We collected about You
  * The categories of sources for the personal information We collected about You
  * Our business or commercial purpose for collecting or selling that personal information
  * The categories of third parties with whom We share that personal information
  * The specific pieces of personal information We collected about You
  * If we sold Your personal information or disclosed Your personal information for a business purpose, We will disclose to You:
    * The categories of personal information categories sold
    * The categories of personal information categories disclosed
* **The right to say no to the sale of Personal Data (opt-out).** You have the right to direct Us to not sell Your personal information. To submit an opt-out request please contact Us.
* **The right to delete Personal Data.** You have the right to request the deletion of Your Personal Data, subject to certain exceptions. Once We receive and confirm Your request, We will delete (and direct Our Service Providers to delete) Your personal information from our records, unless an exception applies. We may deny Your deletion request if retaining the information is necessary for Us or Our Service Providers to:
  * Complete the transaction for which We collected the personal information, provide a good or service that You requested, take actions reasonably anticipated within the context of our ongoing business relationship with You, or otherwise perform our contract with You.
  * Detect security incidents, protect against malicious, deceptive, fraudulent, or illegal activity, or prosecute those responsible for such activities.
  * Debug products to identify and repair errors that impair existing intended functionality.
  * Exercise free speech, ensure the right of another consumer to exercise their free speech rights, or exercise another right provided for by law.
  * Comply with the California Electronic Communications Privacy Act (Cal. Penal Code § 1546 et. seq.).
  * Engage in public or peer-reviewed scientific, historical, or statistical research in the public interest that adheres to all other applicable ethics and privacy laws, when the information's deletion may likely render impossible or seriously impair the research's achievement, if You previously provided informed consent.
  * Enable solely internal uses that are reasonably aligned with consumer expectations based on Your relationship with Us.
  * Comply with a legal obligation.
  * Make other internal and lawful uses of that information that are compatible with the context in which You provided it.
* **The right not to be discriminated against.** You have the right not to be discriminated against for exercising any of Your consumer's rights, including by:
  * Denying goods or services to You
  * Charging different prices or rates for goods or services, including the use of discounts or other benefits or imposing penalties
  * Providing a different level or quality of goods or services to You
  * Suggesting that You will receive a different price or rate for goods or services or a different level or quality of goods or services

### Exercising Your CCPA Data Protection Rights

In order to exercise any of Your rights under the CCPA, and if You are a California resident, You can contact Us:

* By email: <support@innova-drilling.com>

Only You, or a person registered with the California Secretary of State that You authorize to act on Your behalf, may make a verifiable request related to Your personal information.

Your request to Us must:

* Provide sufficient information that allows Us to reasonably verify You are the person about whom We collected personal information or an authorized representative
* Describe Your request with sufficient detail that allows Us to properly understand, evaluate, and respond to it

We cannot respond to Your request or provide You with the required information if We cannot:

* Verify Your identity or authority to make the request
* And confirm that the personal information relates to You

We will disclose and deliver the required information free of charge within 45 days of receiving Your verifiable request. The time period to provide the required information may be extended once by an additional 45 days when reasonable necessary and with prior notice.

Any disclosures We provide will only cover the 12-month period preceding the verifiable request's receipt.

For data portability requests, We will select a format to provide Your personal information that is readily useable and should allow You to transmit the information from one entity to another entity without hindrance.

### Do Not Sell My Personal Information

You have the right to opt-out of the sale of Your personal information. Once We receive and confirm a verifiable consumer request from You, we will stop selling Your personal information. To exercise Your right to opt-out, please contact Us.

## "Do Not Track" Policy as Required by California Online Privacy Protection Act (CalOPPA)

Our Service does not respond to Do Not Track signals.

However, some third party websites do keep track of Your browsing activities. If You are visiting such websites, You can set Your preferences in Your web browser to inform websites that You do not want to be tracked. You can enable or disable DNT by visiting the preferences or settings page of Your web browser.

## Children's Privacy

Our Service does not address anyone under the age of 13. We do not knowingly collect personally identifiable information from anyone under the age of 13. If You are a parent or guardian and You are aware that Your child has provided Us with Personal Data, please contact Us. If We become aware that We have collected Personal Data from anyone under the age of 13 without verification of parental consent, We take steps to remove that information from Our servers.

If We need to rely on consent as a legal basis for processing Your information and Your country requires consent from a parent, We may require Your parent's consent before We collect and use that information.

## Your California Privacy Rights (California's Shine the Light law)

Under California Civil Code Section 1798 (California's Shine the Light law), California residents with an established business relationship with us can request information once a year about sharing their Personal Data with third parties for the third parties' direct marketing purposes.

If you'd like to request more information under the California Shine the Light law, and if You are a California resident, You can contact Us using the contact information provided below.

## California Privacy Rights for Minor Users (California Business and Professions Code Section 22581)

California Business and Professions Code section 22581 allow California residents under the age of 18 who are registered users of online sites, services or applications to request and obtain removal of content or information they have publicly posted.

To request removal of such data, and if You are a California resident, You can contact Us using the contact information provided below, and include the email address associated with Your account.

Be aware that Your request does not guarantee complete or comprehensive removal of content or information posted online and that the law may not permit or require removal in certain circumstances.

## Links to Other Websites

Our Service may contain links to other websites that are not operated by Us. If You click on a third party link, You will be directed to that third party's site. We strongly advise You to review the Privacy Policy of every site You visit.

We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.

## Changes to this Privacy Policy

We may update Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page.

We will let You know via email and/or a prominent notice on Our Service, prior to the change becoming effective and update the "Last updated" date at the top of this Privacy Policy.

We encourage you to review the updated policy periodically.

## Contact Us

If you have any questions about this Privacy Policy, You can contact us:

* By email: <support@innova-drilling.com>


# Innova Software Licensing

## 1.0 - Introduction <a href="#toc203917268" id="toc203917268"></a>

When first installed on a new computer, Well Seeker X or Innova Engineering will give the user access to the full capabilities of each program via a 2 day **evaluation license** which is incorporated within the respective install file.

After this evaluation period has expired, a full license must be purchased for the software. In some circumstances, Innova will grant an extended evaluation license to allow the user to continue trailing the software.

This document will guide the user through requesting and implementing a license. **Note: Well Seeker X and Innova Engineering each require their own separate license.**

## 2.0 – Requesting a License <a href="#toc203917269" id="toc203917269"></a>

Software licenses are computer specific. In order to generate a license, the user must provide Innova with their unique **computer code**, which is generated within the software itself. Users can do this via Innova’s license request feature The process differs slightly, depending on whether you still have an active license or trial period, or if your license has expired.

### 2.1 – Software License Expired <a href="#toc203917270" id="toc203917270"></a>

If your license or trial period of Well Seeker X or Innova Engineering has expired, you will no longer be able to use the software. When you open the program, the below dialog will display:

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9wBiuAnrTvYf8fRYySXx%2F0.png?alt=media" alt="" width="563">

Your unique computer code is displayed in the **computer code required for full license** field. Clicking on **OK** will close the program.

Click on **Request License** to display the Request License dialog. Fill in your details and in the comments box, enter any other relevant information – such as if you have spoken to a sales agent. Then click on **Submit.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FF5nkKf3dGyhdBviKS2BT%2F1.png?alt=media" alt="" width="362">

This will send your computer code as well as other identifying information to Innova. You should receive an automated email confirming receipt of your request. Innova will then process your request. If you have not yet made a purchase agreement, our sales team (<sales@innova-drilling.com>) will get in contact with you.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMb729HTaw1o7RgObTDjb%2F2.png?alt=media)

### 2.2 – Software License Still Valid <a href="#toc203917271" id="toc203917271"></a>

If your license or trial period of Well Seeker X or Innova Engineering has not yet expired, you will still able to use the software. In this case, follow the below steps to request a license.

In **Well Seeker X,** open the **Help** ribbon and then click on the **Info** icon in the **License** section:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FarFpRCuHzr2x3tUH3x9L%2F3.png?alt=media)

In **Innova Engineering,** open the **Help** menu and select **License Info**:

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FinS4M5ZIgVE1kMS3Wodo%2F4.png?alt=media" alt="" width="254">

This will open the License Details dialog. Your unique computer code is displayed in the **Computer Code** field. Click on **Request License** in the top right of the dialog to display the Request License dialog.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9XYc3CBZaROJCHyLese0%2F5.png?alt=media" alt="" width="563">

Fill in your details and in the comments box, enter any other relevant information – such as if you have spoken to a sales agent. Then click on **Submit.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNFvsUWHfS3zjK5uAcy8b%2F6.png?alt=media" alt="" width="362">

This will send your computer code as well as other identifying information to Innova. You should receive an automated email confirming receipt of your request. Innova will then process your request. If you have not yet made a purchase agreement, our sales team (<sales@innova-drilling.com>) will get in contact with you.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVGoARgnrdVVAvhaepTse%2F7.png?alt=media)

## 3.0 – Applying a New License to Well Seeker X or Innova Engineering <a href="#toc203917272" id="toc203917272"></a>

There are 2 ways in which a new license can be added to Well Seeker X or Innova Engineering. These are both detailed below.

### 3.1 – Automatic Download and Application <a href="#toc203917273" id="toc203917273"></a>

This method is only available if you requested your license using the license request method described in Section 2.0. Once your license request has been processed, you should receive an automated confirmation email:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIkTjS9iLBaho2MqVViQU%2F8.png?alt=media)

To download an apply your license, simply open Well Seeker X or Innova Engineering. The software will automatically download your new license.

To confirm, return to the License Details dialog. In **Well Seeker X,** open the **Help** ribbon and then click on the **Info** icon in the **License** section. In **Innova Engineering,** open the **Help** menu and select **License Info.** You should see the new expiry date for your license at the bottom of the dialog.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsDDG52AdwOuMaIgb02Ae%2F9.png?alt=media" alt="" width="563">

### 3.2 – Manual License Application <a href="#toc203917274" id="toc203917274"></a>

In some circumstances, Innova will send the license files directly to you. In this case, you will need to manually apply them.

#### 3.2.1 – Well Seeker X <a href="#toc203917275" id="toc203917275"></a>

The Well Seeker X license file will take the form of a .txt file with a file name starting with “**WS – LICENSE –“.** To apply it, follow these instructions:

1. Save your work and close Well Seeker X.
2. Download the Well Seeker X license file from the email attachment or download link sent from Innova and save it on your PC.
3. Place the license file in your Well Seeker X install directory. The default address will vary depending on if you are using the 64-bit or 32-bit version of Well Seeker X:
   1. For the **64-bit** version, the default address is ***C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x64)*****.**
   2. For the **32-bit** version, the default address is ***C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x86)*****.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0LT42z13BPogXZNO8L61%2F10.png?alt=media)

4. Re-open Well Seeker X, open the **Help** ribbon and then click on the **Info** icon in the **License** section. You should see your new license expiry date at the bottom of the dialog.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2AOV2Oky9JjJpMKvqw1j%2F11.png?alt=media" alt="" width="563">

#### 3.2.2 – Innova Engineering <a href="#toc203917276" id="toc203917276"></a>

The Innova Engineering license file will take the form of a .txt file with a file name starting with “**ENG – LICENSE –“.** To apply it, follow these instructions:

1. Save your work and close Innova Engineering.
2. Download the Innova Engineering license file from the email attachment or download link sent from Innova and save it on your PC.
3. Place the license file in your Innova Engineering install directory. By default, the install directory address is ***C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering.***

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4QeGQGILVknGdf6RW7mH%2F12.png?alt=media)

4. Re-open Engineering and go to Help >> License Info. You should see your new license expiry date at the bottom of the dialog.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRs5mtOLpdDZtgVfCcJ7P%2F13.png?alt=media" alt="" width="563">

## 4.0 – License Deactivation <a href="#toc203917277" id="toc203917277"></a>

It may become necessary to deactivate your license – for example, to transfer it to another computer. If so, follow the below steps to perform the deactivation. This process is carried out separately for Well Seeker X and Innova Engineering. An internet connection is required for Innova to receive automatic confirmation of your deactivation.

**IMPORTANT NOTE**: This will PERMANENTLY deactivate your Well Seeker X or Innova Engineering license on your machine. Unless you receive a new license, you will not be able to run the software on your machine.

In **Well Seeker X,** open the **Help** ribbon and then click on the **Info** icon in the **License** section:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FL0Mdjg4f6RrM627mlkqW%2F14.png?alt=media)

In **Innova Engineering,** open the **Help** menu and select **License Info**:

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFselUkF0EKG8cKsv8kUu%2F15.png?alt=media" alt="" width="254">

This will open the License Details dialog. Click on **Deactivate** in the top right of the dialog.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fw9mXH7WynhlXFAWtylt8%2F16.png?alt=media" alt="" width="563">

When the warning displays, click on **OK.** You should receive a message confirming that your license has been successfully deactivated, and the **Deactivate Code** field should now be populated in the License Details dialog. You can now close the software.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FK2srf2vkUUbLy4vqbt2W%2F17.png?alt=media" alt="" width="563">

Innova should receive an automatic confirmation that your license was deactivated. If we do not, we may ask you to send us your deactivation code. This can be found in a file called **WS – Deactivation Code.txt** or **ENG – Deactivation Code.txt**, stored in your Well Seeker X or Innova Engineering install directory. Attach the file to an email and send it to <support@innova-drilling.com> or <sales@innova-drilling.com>.

For **64-bit Well Seeker X**, the default install directory address is ***C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x64)***.

For **32-bit Well Seeker X**, the default install directory address is ***C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x86).***

For **Innova Engineering**, the default install directory address is ***C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering.***

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F22bfHFJUm9YwyRnaHAxR%2F18.png?alt=media)


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MhmaLg7dBHakvIsqQTJ%2F-MhmdVBMIGE700CqsAnb%2F0.png?generation=1629716088059165\&alt=media)

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 <sales@innova-drilling.com>
* **You will need to clearly specify which program you need a license for, either Well Seeker Pro, Innova Engineering or BOTH, as each program requires a separate license.**

Innova will then send out a new license in the form of a **LICENSE.txt** file. Once you have received this, follow the instructions below:

For **Well Seeker Pro:**

* Place the **LICENSE.txt** file in the Well Seeker Pro folder (most common directory path detailed below)
  * *C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO*
  * Same directory as **Well Seeker.exe**
  * If a LICENSE.txt file already exists in this folder, make a copy before you replace it. This can then be used as a temporary backup in case there are any issues with the new file.

For **Innova Engineering**:

* Place the **LICENSE.txt** file in the Innova Engineering folder (most common directory path detailed below)
  * *C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering*
  * Same directory as ***Innova engineering.exe***
  * If a LICENSE.txt file already exists in this folder, make a copy before you replace it. This can then be used as a temporary backup in case there are any issues with the new file.

**If you experience any issues during this process, please contact <sales@innova-drilling.com> for support**


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MfmCs69_1Y_wx6bMI03%2F-MfmLcfN0lBKzTwMtCKN%2F1.PNG?alt=media\&token=7fea3783-2c8b-431b-8c4a-c23b4f6be644)

* **This is important, because if the file extension is not changed, then the file will not work.**

For **Well Seeker Pro:**

* Place the **Well Seeker.exe** file in the Well Seeker Pro folder (most common directory path detailed below)
  * *C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO*
  * There will already be a file of the same name in this folder. Overwrite this file with the new one
  * ***Before overwriting, make a copy of this file (save it to a different folder) which can then be used as a temporary backup in case there are any issues with the new file.***

For **Innova Engineering**:

* Place the **Innova Engineering.exe** file in the Innova Engineering folder (most common directory path detailed below)
  * *C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering*
  * There will already be a file of the same name in this folder. Overwrite this file with the new one
  * ***Before overwriting, make a copy of this file (save it to a different folder) which can then be used as a temporary backup in case there are any issues with the new file.***

You have now installed the latest update and can open and run the programs as usual.

**If you experience any issues during this process please contact <sales@innova-drilling.com> for support.**


# Well Seeker X Guides

A selection of quick start guides for Well Seeker X


# Well Seeker X: Transition Guide

## 1.0– Introduction <a href="#toc135722907" id="toc135722907"></a>

Well Seeker X comes with a number of new and improved features compared to Well Seeker Pro. It also has a new user interface which may be unfamiliar for users accustomed to Well Seeker Pro. This document is designed to be a guide for users who are already familiar with Well Seeker Pro, and help them during the transition to Well Seeker X.

## 2.0 – Updated Features <a href="#toc192253589" id="toc192253589"></a>

### 2.1 – 64-Bit Capability <a href="#toc192253590" id="toc192253590"></a>

Unlike Well Seeker Pro, which is only available as a 32-bit program, Well Seeker X is available in both 32-bit and 64-bit versions. As a 64-bit program, Well Seeker X can access significantly more of your computers random access memory (RAM). This improves performance, allowing the program to perform memory intensive tasks faster and handle larger data sets.

For information regarding 64 bit version compatibility see Section 3.1.

### 2.2 – Main Interface <a href="#toc192253591" id="toc192253591"></a>

#### **Menu Ribbons**

The old method of accessing features using nested dropdown menus has been replaced with menu ribbons. Ribbons provide a much more user friendly way of accessing functions by displaying them directly on the screen in organized tabs, making it easier to perform actions, or change settings quickly without having to navigate through multiple nested menus.

You will find menu ribbons in the main Well Seeker window and in major dialog windows, such as the Daily Reports and Drill String Editor dialogs. The ribbons contain all of the functions previously contained in the dropdown menus, along with some new features.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2Z1HrwnpmReubOVwJNne%2F0.png?alt=media)

To free up space for the main user interface, the ribbons can be shrunk by toggling on **Simplified Mode** in the top right corner of the Well Seeker X window.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4hQ3pDD9E1qwePjY7v6k%2F1.png?alt=media)

The ribbon options can also be searched using the Search option in the top right of the main user interface.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fvo7NvWyBpJJkEAsSHvoC%2F2.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Object Explorer**

The Database Tree has been renamed the Object Explorer and has a number of improved features.

Levels in the tree now have an Active Well Indicator, represented by a green number, which indicates how many currently active wells are contained under each level. Additionally, the database can be searched by entering a well or plan name in the search bar at the top of the tree.

Innova have made it easier to access Reporting and other dialogs such as the casing and lithologies – the user can now access these dialogs from the menu ribbon when at actual well or plan level. In addition to this, the criteria for option selection is now less strict. For example, in Well Seeker Pro, the user could only open the Cost Codes dialog in the main UI when the Well level was selected in the Object Explorer. In Well Seeker X the user can open the Cost Codes dialog when the Well level, or any of its child items are selected in the Object Explorer, i.e., Well, Actual Well, Survey, Plan or Planned Wellbore. This makes it simpler for new users to be able to select relevant options.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4fqTjXTz1J09FMtYXptk%2F3.png?alt=media" alt="t." width="320">

#### **Quick Access Toolbar**

The quick access toolbar at the top of the main user interface gives the user customizable quick access to commonly used options.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWohS1ekjTiOLaXoDLu5k%2F4.png?alt=media" alt="" width="442">

#### **Interactive Status Bar**

The status bar at the bottom of the page is now interactive. The user can now click on the items in the status bar to:

1. Change unit sets.
2. Open current database location.
3. Start/Stop screen captures.
4. Open the real time data exchange.
5. Download IPMs.
6. View Data Sync status and toggle between online and offline modes
7. View WITS/WITSML status
8. View notifications.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXYJfzwxYC6opJVStH5Ts%2F5.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Light/Dark Mode**

Well Seeker X now has a dark mode. To toggle between light and dark modes, use the **Style** dropdown box, which you can find in the very top right corner of the Well Seeker X window.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEfsapp1rDDlFpgyeafxc%2Fimage.png?alt=media&amp;token=b013e747-547e-4a12-aba7-edecdb7f3aaf" alt=""><figcaption></figcaption></figure>

#### **Tear Off Panes**

In Well Seeker X, survey, plan and plot tabs can be detached completely from the Well Seeker window. Simply left-click on a tab and drag the tab outside the window. Drag the tab back into the Well Seeker window to restore it. This feature makes user customizable screen layouts even more achievable.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FornfVPrkQJazOZ8YeYX3%2F8.png?alt=media" alt="" width="563">

### 2.3– Daily Reporting <a href="#toc192253592" id="toc192253592"></a>

All Daily Reporting related dialogs have been reworked to improve performance, simplify the UI and reduce the need for double entry of data. Users familiar with the daily reporting system will notice that a number of features have been rearranged, or removed entirely. This section details the key changes to the Daily Reports system.

#### **Job Data**

Job data has been removed from the Daily Reports window into it’s own independent dialog. This dialog can be accessed by selecting the Actual Well level, or below, in the Object Explorer and selecting the Job Data button from the Home ribbon in the main Well Seeker interface.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0OsUsdEuPzTcWVeXYdvD%2F9.png?alt=media)

Data entered into this dialog applies to all daily reports. Other dialogs also source data from the Job Data – for example the Drill String Editor uses the rig name entered here.

The **Well Status, DD Coordinator and MWD Coordinator** settings have also been moved from the Daily Reports window to the Job Data dialog. This allows the user to set these values without needing to create a daily report.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvTavjxV5OBuICAtvRfhR%2F10.png?alt=media" alt="" width="563">

#### **Slide Sheet Integration**

A number of changes have been made to the way the Daily Reports window interacts with the Slide Sheet, to reduce user workload and remove double data entry.

The **Get DDR from slide sheet** and **Get Params** buttons have been removed. Instead, whenever the slide sheet is saved, the drilling activity is uploaded to Daily Reports. The daily activity section in the Daily Reports window will automatically populate with rotating and sliding activity, and the activity descriptions will be updated using the drilling parameters from the slide sheet. Activities uploaded from the Slide Sheet cannot be edited in the Daily Reports window.

24 hour & BHA run drilling parameters, drilling and circulating hours, etc. are all calculated from the slide sheet and stored in the background. To streamline the user interface, only fields that require user entry remain in the Daily Data section and the Mud Data section.

#### **Data Validation**

The Data Validation menu has been removed from the Daily Reports window in Well Seeker X. Instead, the program will scan the daily activities in real time. If any discrepancies are found, they will be highlighted in red to alert the user.

Additionally, in the Home ribbon there is a new Data Validation section that logs any errors found, along with a description. The user can use the controls to quickly navigate to each error

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FS9tRcalngl1vpuBhHrRL%2F11.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Miscellaneous Changes**

In addition to the key changes detailed above, the following minor changes have been made to simplify the UI and streamline data entry.

1. You can now rearrange the columns in the Daily Activity section in the same way that you can for survey tables, plan tables and the slide sheet. Simply left click and drag on the column header to move a column.
2. The toggle for using dropdowns for rig names & personnel has been removed. If any names have been entered into the Rig Names and Personnel Names tables (located in the Admin ribbon in the main interface) then dropdowns will automatically be enabled in the Daily Reports.
3. The Assembly Type and MWD Type selections have been moved to the Daily Data section.
4. Each day now has it’s own Personnel dialog. When a new day is created, the previous day’s personnel will be copied over. Field Supervisor and Drilling Supervisor have been removed.
5. Company Man’s Report options have been removed.
6. Date changes and report number changes will now not take affect until the user selects save. The user will be warned about duplicate dates when a date is selected, and will be warned about duplicate report numbers when clicking on Save.

### 2.4 – Drill String Editor <a href="#toc192253593" id="toc192253593"></a>

Users familiar with Well Seeker Pro will notice that some fields that could be manually altered, such as the Date In/Out and the Depth In/Out, have been removed. This data is now automatically retrieved whenever Daily Reports are saved.

The major change to the Drill String Editor is to the Performance Report. The dialog has been greatly simplified to reduce the need for double entry of data and has been split into two separate dialogs – one for motor related data, and another for MWD data. These two dialogs can be accessed via the **Drilling** and **MWD** options in the Run Data section of the menu ribbon.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fz3LSwJ3GkrcXX0OQMDZz%2F12.png?alt=media)

All drill string related reports, including performance reports, are now printed from the Drill String Editor using the Print BHA Excel and Print BHA PDF options in the menu ribbon. Additionally, some new tools relating to M/LWD have been added to the menu ribbon. These are referred to as the MWD Toolkit and are covered in the next chapter.

#### **Performance Report and MWD Report**

The Performance Report dialog has been greatly simplified in comparison to Well Seeker Pro. The user no longer has the option to manually enter drilling parameters or pull parameters from the Daily Reports. Instead, this information is automatically updated when the Slide Sheet is saved.

As a result, the dialog has been reduced to only the information that is still required to be manually entered: some additional run information, the reason for POOH and failure information. Additionally, the MWD run data has been split off and given it’s own dialog.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvOufg12dQ4B2p2Wnpra0%2Fimage.png?alt=media&amp;token=3e879e12-a541-4b75-9390-86505a8a0358" alt="" width="563"><figcaption></figcaption></figure>

#### **Rental Data**

If running a rental job, data can be input within the Rental Data dialog, negating the requirement to fill in the daily reports for such jobs. Toggle on the **Is Rental** option to indicate that the job is a rental job and enter the relevant run details. When this option is toggled on, the data entered here will ignore any data from the daily activity section of the daily reports.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVeivJBS4Bi2FXm7R74rW%2F15.png?alt=media" alt="" width="375">

### 2.5 – MWD Tool Kit <a href="#toc192253594" id="toc192253594"></a>

Well Seeker X adds three new MWD related tools to the Drill String Editor. In addition, the way that MWD surface system data is entered for performance reports has been updated. These tools can be found on the menu ribbon in the Drill String Editor.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmkwslF3fB6evEC41m6QI%2F16.png?alt=media)

#### **MWD Probe Config**

The MWD Probe Config tool allows the user to define the probe arrangement within the MWD/LWD tool. Well Seeker X will then combine this information with the BHA details to calculate the sensor offsets.

The Probe Config requires data to be present in the Probe Catalog, as it uses this to populate the options for selection. The Probe Catalog is an organization level record of the exact probe measurements that are uniform to specific probes, which is stored on the organizations server. This catalog can be accessed from the menu ribbon and will automatically pull to the local database when using Well Seeker X with an internet connection.

![A ](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDEyLenZ2hpcbJsrIiFKK%2F17.png?alt=media)

The user can then use the MWD Probe Config tool to arrange the desired probes in whatever order they wish. The program will calculate the sensor offsets, and when the user clicks Apply, the offsets will be automatically added to the MWD/LWD component properties.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnkQ9F3FgMNAFHMHPHcYt%2F18.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

#### **Surface System Config**

The MWD surface system has been separated from the motor performance report and given it’s own dialog. Items entered here are applied to all BHAs for the well, so that the user does not need to enter their information multiple times. If surface system components have been entered into the Inventory, they will be available here as dropdowns. If not, their serial numbers can be entered manually.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKbtrYLRgiI5WTJbbS5kL%2F19.png?alt=media" alt="" width="435">

#### **Non-Magnetic Material Spacing Calculator**

The Non-Mag Spacing Calculator from Innova Engineering has been added to Well Seeker X. This feature allows the user to predict the amount of non-magnetic material required above and below the directional sensor to keep interference from the drill string within an acceptable tolerance for uncorrected magnetic surveys. It can also evaluate whether the BHA meets these requirements.

To run the calculator, the user requires a completed BHA that contains an MWD/LWD component with directional sensor offset entered into the component details and magnetics data present within the Actual Well Properties. The user manually inputs the estimated Depth In and Out for the run and the maximum acceptable azimuth error. The calculation can be toggled between using the actual wellbore, or the principal plan for the well. Pole strength values are automatically assigned based upon the BHA components present, but these can be manually overwritten by toggling off the Auto slider and editing the pole strength values.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2VKPlQdxhzm4lq6fuG1y%2F20.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

#### **Pressure Drop Calculator**

The Pressure Drop Calculator can be used to calculate the pressure drop across positive pulse transmitters / pulsers or restrictors. The user should select either POPPET or RESTRICTOR from the Type column, and then enter the relevant parameters to calculate the pressure drop.

If there is a MWD/LWD type component in the string, the user can check the **Selected** checkbox and when they save and close the dialog, the poppet, orifice and pulse width values will be added to the MWD component properties.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FizgbufFjUXqHwwrmooDo%2Fimage.png?alt=media&amp;token=57fb2df5-f6b5-40a1-b156-0e43e9fcd4f6" alt=""><figcaption></figcaption></figure>

## 3.0 – Installation <a href="#toc192253595" id="toc192253595"></a>

### 3.1 Version Compatibility <a href="#toc192253596" id="toc192253596"></a>

Well Seeker X is available in two versions, 64 and 32 bit. In order to be able to run the Well Seeker X 64 bit version the PC must fulfil the below criteria:

1. **64 bit operating system (OS)**

To check the PCs OS version, right click on the Start Menu icon in your Windows task bar and select **System**. In the Device Specifications section, it will display in the System Type field what bit version of OS is installed.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrnqzabSLwVXpg69qvr2n%2Fimage.png?alt=media&amp;token=a7f941ba-5479-4eb9-8d98-0c4267b1327a" alt=""><figcaption></figcaption></figure>

2. **64 bit Microsoft Office / 365**

If Microsoft Office / 365 is installed on the user’s machine, and the user wishes to use the 64-bit version of Well Seeker X, then Microsoft Office / 365 must also be 64-bit. To check the PCs Microsoft Office / 365 version, open any Office program, e.g., MS Excel or Word. Select File > Account > About XXX, where XXX is the name of the software.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxBtkLzrQs5m5yAPbFidN%2Fimage.png?alt=media&amp;token=d64f7f1b-0772-4c4f-9126-8d79eff9f049" alt=""><figcaption></figcaption></figure>

If either of these conditions are not met, then the user should install the 32-bit version of Well Seeker X.

Only Well Seeker Pro or Well Seeker X can function on a PC at any one time. In order to use one, the other must first be uninstalled.

### 3.2 Installation Process <a href="#toc192253597" id="toc192253597"></a>

The below steps detail how the user can upgrade their installation of Well Seeker Pro to Well Seeker X:

1. Uninstall Well Seeker Pro using the “**Programs and Features**” feature in the Windows control panel.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUVOxXtuqz71aIxPC2QbD%2Fimage.png?alt=media&amp;token=fd3aa103-8128-4190-998f-89620096ed11" alt="" width="453"><figcaption></figcaption></figure>

2. Download the compatible Well Seeker X installer from the [**Innova Website**](https://www.innova-drilling.com/download/trial), and unzip it from the zip file.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLZ9FBF9HO1KMfflPmk91%2Fimage.png?alt=media&amp;token=321ee6f5-8b72-4b7d-b621-225e8f0a7f4d" alt=""><figcaption></figcaption></figure>

3. Run the compatible Well Seeker X installer. Follow the instructions on screen to install any required pre-requisite software. Once installation is complete, you will see the new Well Seeker icon on your desktop and in the Start Menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtjlPRN70E7Rsx2ZFp0m2%2Fimage.png?alt=media&amp;token=3f302c2e-d8c1-44ad-a753-de636d38d803" alt="" width="114"><figcaption></figcaption></figure>

## 4.0 – Troubleshooting <a href="#toc192253598" id="toc192253598"></a>

This section details some common issues that prevent Well Seeker X from installing or running, and how to resolve them.

#### **Compatibility between 64-bit and 32-bit databases**

Users should be aware that the version of Well Seeker X used to create a database will affect it’s compatibility with other versions of Well Seeker X and Well Seeker Pro.

The 64-bit version of Well Seeker X is able to open any database, whether it was created using 64-bit Well Seeker X, 32-bit Well Seeker X or Well Seeker Pro. However, 32-bit Well Seeker X and Well Seeker Pro cannot open databases that were created in the 64-bit version of Well Seeker X.

#### Not Unzipping the Installer

When downloaded from the Innova website, the installer is inside a zipped folder. If you attempt to run the installer while it is still inside the zipped folder, you will get the below error message. You must unzip the folder before you run the installer.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fw75fOxATPspTi9LF2Vl7%2Fimage.png?alt=media&amp;token=2b6faed3-db46-4441-8223-53edb51e7352" alt="" width="345"><figcaption></figcaption></figure>


# Well Seeker X: Installation Guide

## 1.0 – Introduction

This document is a guide for installing the Well Seeker X software on the user’s computer. Follow this guide to install Well Seeker X on a fresh computer, or upgrade from Well Seeker Pro.

## 2.0 - Compatibility

Before installing Well Seeker X, you should check which version your PC is compatible with.

Well Seeker X is available in two versions, 64 and 32 bit. As a 64-bit program, Well Seeker X can access significantly more of your computers random access memory (RAM). This improves performance, allowing the program to perform memory intensive tasks faster and handle larger data sets.

However, the 64-bit version has some additional requirements in order to run. Check the below criteria to see if you can run the Well Seeker X 64 bit version on your PC:

### **64-bit operating system (OS)**

To check the PCs OS version, right click on the Start Menu icon in your Windows task bar and select **System**. In the Device Specifications section, it will display in the System Type field what bit version of OS is installed.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvX3rhju1eo28fFAahCTp%2F0.png?alt=media)

### **64-bit Microsoft Office / 365**

If Microsoft Office / 365 is installed on the user’s machine, and the user wishes to use the 64-bit version of Well Seeker X, then Microsoft Office / 365 must also be 64-bit. To check the PCs Microsoft Office / 365 version, open any Office program, e.g., MS Excel or Word. Select File > Account > About XXX, where XXX is the name of the software.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6Ovk0s1blSQam31q2ZX9%2F1.png?alt=media)

If either of these conditions are not met, then you should install the 32-bit version of Well Seeker X.

## 3.0 – Download

The Well Seeker X installer can be downloaded from the Innova website. Follow the below link to go to our download page:

<p align="center"><a href="https://www.innova-drilling.com/download/trial"><strong>Download – Innova Drilling &#x26; Intervention</strong></a></p>

Click on **Existing Users**, then click on **Download x86** to get the 32-bit installer, or **Download x64** for the 64-bit installer.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGn1ofIcoG16uZ7FnN9pM%2Fimage.png?alt=media&amp;token=2ab42a02-7811-4a83-9309-af2be87cba9f" alt=""><figcaption></figcaption></figure>

## 4.0 – Uninstall Well Seeker Pro

If you are installing Well Seeker X to a new computer, you can skip this chapter and go straight to chapter **5.0 – Installation.** However, if you have Well Seeker Pro installed on your computer, you must uninstall it before you can install Well Seeker X. To do so, follow the below instructions:

To be safe, you should back up your database before uninstalling Well Seeker Pro. Open Well Seeker Pro and then go to **File >> Backup Database**. Save the backup file in a secure location, and then **close** Well Seeker Pro.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5KshG3XLtBLUscg0cd17%2F3.jpeg?alt=media)

Open the **Control Panel**. This can be found by searching for “control panel” in the search bar beside the Start Menu icon.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNeUmxZTQFuaoNJZFl4SA%2F4.png?alt=media" alt="" width="375">

Within the Control Panel, open **Programs and Features**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F61pYSHkVwKsOvV0fAW3Q%2F5.png?alt=media)

Select Well Seeker Pro from the list and then click on **Uninstall/Change**. Follow the instructions to uninstall Well Seeker Pro.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0Gu5S2aJud5CjNK2RZJx%2F6.png?alt=media" alt="" width="563">

## 5.0 - Installation

**When downloaded, Well Seeker X will be supplied as a zipped installation file which must be unzipped before use. Right click on the file and select “Extract All….” from the context menu.**

Select a location which you wish to extract the files to and click “Extract”. The installation files will be extracted to the selected location in a folder called “Well Seeker X”

Once the files have been extracted, open the Well Seeker X folder and double click on the “Well Seeker X vx.x.x.exe” file to begin the installation process.

Select the location which you wish to install Well Seeker X. The default location is “**C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X** **(x64)\\**”. If you wish to change the location the program is installed to click on the “…” button.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHtueYx8PlzBQI9rDGfp9%2F7.png?alt=media" alt="" width="289">

If you have read the terms and conditions and want to proceed without reading it again, click on the checkbox to agree with the licenses terms and conditions and click on “Install” to procee&#x64;*.*

If you wish to read the terms, click on “Licenses terms and conditions”, this will display the below screen. This information can also be printed for future reference by selecting the printer icon. Once read, select the “Accept” and “Install” button to begin installation.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4bQrdDFAMO96sGR5XSDO%2F8.png?alt=media" alt="" width="287">

The installer checks the computer for some prerequisite software, which is required for Well Seeker X to operate correctly. If any of these software items are missing from the computer, then the installer will go through the steps of installing them before installing Well Seeker X.

If the Microsoft ODBC Driver 17 for SQL Server is missing then the below figure will display. Select “Next”.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWqcfpUkxA0aJPU0nTems%2F9.png?alt=media" alt="" width="313">

Read the Microsoft ODBC Driver 17 for SQL Server license terms. Select “I accept the terms in the license agreement”. Select “Next”.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtDBKdmYXzsEW7v7QhWr5%2F10.png?alt=media" alt="" width="375">

In the Microsoft ODBC Driver 17 for SQL Server feature selection section, select “Next”.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2ifJsePchFszAxpCW8KO%2F11.png?alt=media" alt="" width="312">

In the Microsoft ODBC Driver 17 for SQL Server ready to install section, select “Install” and “Finish” when this installation is completed.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fc2Eu6FgwkMUdokh1ZpLS%2Fimage.png?alt=media&amp;token=25dbed6e-e148-4324-8575-08a4e798d506" alt=""><figcaption></figcaption></figure>

If the correct version of Visual C++ Redistributable for Visual Studio 2015-2022 is missing the bellow figure will display x64, x84 or both installations one after another. Click on the checkbox to agree with the license terms and conditions and select “Install” and “Close” once the installation is complete.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJPi8Q2gQ1HvgDiKHALAG%2F14.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPS20aEPhbnjQWv4X8juo%2F15.png?alt=media)

If another version of Visual C++ Redistributable for Visual Studio 2015-2022 is already present on the PC then the below window may appear. Select “Repair” and “Close” once the update is complete.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fi7Q68beyLGACPmVjDimu%2F16.png?alt=media" alt="" width="300">

Once prerequisite software are installed, if the copy of Well Seeker X is genuine the user will be presented with a dialog showing the verified publisher as “Innova Drilling and Intervention Ltd”. If not the software is not genuine and should not be used.

Click “Yes” to continue the installation.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4JbTiVGApjDZZ2U59l5K%2F17.png?alt=media" alt="" width="271">

Once the installation is complete the final dialog will display “Well Seeker X (x64) has been successfully installed”. Select “Finish” to close the dialog.

A Well Seeker X shortcut icon will have been added to the desktop and an entry for “Well Seeker X” will be in the start menu.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYvO8G0DbCi2syQy5mJ36%2F18.png?alt=media" alt="" width="286">

Finally, restart the PC to ensure that the Visual C++ Redistributable for Visual Studio 2015-2022 is fully functional, prior to opening Well Seeker X.

## 6.0 – Troubleshooting

This section describes two common troubleshooting scenarios that can occur during installation, and how to solve them.

### 6.1 – Installer Reports No Internet Connection

During installation, the user receives the below error message, despite being connected to the internet.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBTJB7WC5y3HV1LR4TXdM%2F19.png?alt=media)

This is caused by the user’s anti-virus software blocking the installer’s connection to the internet. To resolve this issue, temporarily disable your anti-virus before running the installer.

### 6.2 – Well Seeker X fails to Open

When the user launches the program, the Well Seeker X splash screen (pictured below) will display as normal, but the program will then close immediately.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmBAlTV5c7zYvTpzeeFb0%2F20.jpeg?alt=media)

This issue is usually caused by one of the prerequisite software, the Microsoft Visual C++ Redistributable package, requiring an update. To resolve this issue, follow the guide in this link: [**Well Seeker X Failure to Open | Innova Drilling & Intervention**](https://docs.innova-drilling.com/introduction/technical-notes/low-priority/well-seeker-x-failure-to-open)

### 6.3 - Not Unzipping the Installer

When downloaded from the Innova website, the installer is inside a zipped folder. If you attempt to run the installer while it is still inside the zipped folder, you will get the below error message. You must unzip the folder before you run the installer.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPRYr6xBDfQFBcJI9NbFa%2Fimage.png?alt=media&amp;token=ce52bf7a-7ef8-4b8b-a17a-5c0ebb9902b2" alt="" width="345"><figcaption></figcaption></figure>


# Well Seeker X: How To Guide

## 1.0 - Getting Started <a href="#toc195011828" id="toc195011828"></a>

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 <a href="#toc195011829" id="toc195011829"></a>

When you first open Well Seeker X, the screen will be configured as below.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6KQdUIhCJJw5RIwAlCcV%2F0.png?alt=media" alt="" width="563">

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2qRsAhD9eTGnkGpfhFhz%2F1.png?alt=media" alt="" width="563">

The user can also toggle the style between Light / Dark Modes.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPEZYuCkwY2Vv9fR2fVoW%2F3.png?alt=media" alt="" width="563">

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuV8i26hlPOeRrQVdQdxa%2Fimage.png?alt=media&amp;token=2848a8e2-52e7-40f2-af6f-6b4166443ff7" alt="" width="284"><figcaption></figcaption></figure>

The Object Explorer and Notifications panes can be toggled on/off by selecting the relevant option in the Settings tab.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FagnJznzOxKaI1vMHDNgc%2F4.png?alt=media" alt="" width="563">

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbO1aa93Vh5VDNYc7KqRW%2F5.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1tMsMznBFRVa0XvXo0fj%2F6.png?alt=media)

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fz09Ddp27aYhbWOSsxxR2%2F7.png?alt=media" alt=""><figcaption></figcaption></figure>

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGX7OXbT4F3HUn9c9eCCE%2F8.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNLQ2NfJ4lxY1iSlFdt3X%2F9.png?alt=media)

## 2.0 - Creating a new local database <a href="#toc195011830" id="toc195011830"></a>

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5o4w6wrMAIpmfDFas38k%2F10.png?alt=media)

* The window below will appear.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuMbV1Bp4uCuZf2mQ9eca%2F11.png?alt=media" alt="" width="563">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZxNMIEKgNJ1jrtoupmBo%2F12.png?alt=media)

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBJhk8CeiQrB1Df0wGeUn%2F13.png?alt=media" alt="" width="563">

You can navigate to the file location of your database by opening in the **Open Database Location** icon ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F85p6ak1JaRdXE6JlN55n%2F14.png?alt=media) in the bottom of the screen.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWXdxS7Mji6ZZRVFdAX5Z%2F15.png?alt=media" alt="" width="407">

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmyZesDo1OUwZM9pkkiAC%2F16.png?alt=media)

## 3.0 - Switching between Databases <a href="#toc195011831" id="toc195011831"></a>

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FG6HpAgPEfliLsF3dE1Yz%2F17.png?alt=media)

* 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 <a href="#toc195011832" id="toc195011832"></a>

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

### 4.1 - Unit Selection <a href="#toc195011833" id="toc195011833"></a>

The first thing to do is to make sure that you have the correct units selected.

* Click on the *Units* icon ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrmZbJjCv1cHul2vTQ5dh%2F18.png?alt=media)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:

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5Ru5ro9TjrkEMAITbHwE%2F19.png?alt=media" alt="" width="303">

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuDokS2Pxj5PcXZLDrVYV%2F20.png?alt=media)

* This will open the Unit Sets dialog box

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZ8wXfC1a3OUEnnftOuUZ%2Fimage.png?alt=media&amp;token=fd1fabc6-3bef-4603-b337-48742682203a" alt="" width="343"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEqOBPnYZ906av2gXaH62%2Fimage.png?alt=media&amp;token=3fe3aba7-43f3-4de4-a441-3795e29d1725" alt="" width="288"><figcaption></figcaption></figure>

1. **Depth**: Current units for measured depth and TVD. Options are Feet, US Feet and Meters.
2. **Diameter**: This defines the units used to display Casing OD and ID as well as hole size. Options are mm and inches.
3. **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.
4. **Flow Rate**: Current units for flow rate. User can choose between LPM and GPM.
5. **Pressure**: Current units for Pressure. User can choose between psi, bar, Kpa or Km/cm<sup>2</sup>
6. **Volume**: Current units for Volume. User can choose between BBLS and m<sup>3</sup>
7. **Mud**: Current units for Mud Weight. User can choose between PPG, SG, psi/ft<sup>3</sup>, lbs/ft<sup>3</sup> and Km/cm<sup>3</sup>
8. **Weight**: Current units for Weight. User can choose between klbs, Tons and kdaN
9. **Unit Weight**: Current units for Unit Weight. User can choose between lb/ft and kg/m
10. **Torque**: Current units for Torque. User can choose between kftlb and kNm
11. **Temperature**: Current units for Temperature. User can choose between degC and degF.
12. **Cost**: Current units for Cost. User can choose between $, EUR and GBP.
13. **Jets**: Current units for Jet size. User can choose between in<sup>2</sup> and mm<sup>2</sup>.
14. **Magnetics:** Current units for Magnetics. User can choose between Geolink/Tensor, SSP/SUCOP (ut), nt, nt (no XY), uT (XY Inversion) or EVO/Applied.
15. **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 <a href="#toc195011834" id="toc195011834"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKrLMgbyCuZShlRAZgWaq%2Fimage.png?alt=media&amp;token=f3df447c-7499-46f6-8fd7-61cd90487dc4" alt=""><figcaption></figcaption></figure>

### 4.3 - New Operator <a href="#toc195011835" id="toc195011835"></a>

* Right click on the database and select **Insert New Operator**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgaVKOCSLMEog6pHGdLPS%2Fimage.png?alt=media&amp;token=8ec858e8-277d-476e-9a21-a7867588ab4d" alt="" width="299"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJwaW9LfGnbJL8z6VOfS3%2Fimage.png?alt=media&amp;token=f1c408f7-54d8-4a16-a9cc-9cb37ff9f336" alt="" width="272"><figcaption></figcaption></figure>

### 4.4 - New Field <a href="#toc195011836" id="toc195011836"></a>

* Right click on the Operator and select Insert New Field.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCt1UNEGZtwZJUFNYb6BQ%2Fimage.png?alt=media&amp;token=2fec80a8-b6be-41f6-bf3c-144317495fd6" alt="" width="351"><figcaption></figcaption></figure>

* The Field Properties dialog will now appear.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbX4Woo6IFvScwnqzkZWR%2Fimage.png?alt=media&amp;token=a2109296-9ae8-457a-8532-1841b8fa1f2e" alt="" width="376"><figcaption></figcaption></figure>

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.

  <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqYt4HpGBx6YDOGYgvW5N%2Fimage.png?alt=media&amp;token=1771305b-bf99-4dbd-9a00-4ce048f37891" alt="" width="281"><figcaption></figcaption></figure>
* **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 <a href="#toc195011837" id="toc195011837"></a>

* Right click on the Field and select **Insert New Facility**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZmnK76kNXNdtReeopVTJ%2Fimage.png?alt=media&amp;token=41b239ce-0d1b-4d6d-ab1d-65f03898c808" alt="" width="271"><figcaption></figcaption></figure>

* The **Facility Properties** dialog will now appear

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZE3EGqk737QeB90ZWXfp%2Fimage.png?alt=media&amp;token=50bd835c-c85c-4c7f-b59c-0eff7551abab" alt=""><figcaption></figcaption></figure>

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 <a href="#toc195011838" id="toc195011838"></a>

* Right click on the Facility and select **Insert New Well**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FA1Vn2d8zx3s6MIOwlZPg%2Fimage.png?alt=media&amp;token=44256d4d-4a86-4751-8656-2e27b8b4c8a2" alt="" width="258"><figcaption></figcaption></figure>

* The **Well Properties** dialog will now appear

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsPpyd7gmYdQw9xCZhlvC%2Fimage.png?alt=media&amp;token=2d2b50ba-0a62-437a-9a45-dec9b40fd5d0" alt=""><figcaption></figcaption></figure>

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 <a href="#toc195011839" id="toc195011839"></a>

* Right click on the Well and select **Insert Planned Well.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpQaQMB9ODvW3clBJDN8Y%2Fimage.png?alt=media&amp;token=c026d87e-1fe7-49de-86a8-391abf149bed" alt="" width="316"><figcaption></figcaption></figure>

* The **Plan Properties** dialog will now appear.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2yFsGIjIy1t0BFdm05Xz%2Fimage.png?alt=media&amp;token=33465baa-8019-450d-87a5-f8541e117ee4" alt="" width="511"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FK9uq4m4JScfG2k5HaD7v%2Fimage.png?alt=media&amp;token=a84e04d5-94f2-4ecd-b008-98521acbf05e" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9RXZGPLtMwIkQ9BMnoGv%2Fimage.png?alt=media&amp;token=8f861e6f-4327-4c23-8d6e-c4e0f6e429ae" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FztUUG5gImsXLyczbtDWQ%2Fimage.png?alt=media&amp;token=dae972ee-886c-4ddb-9f2b-2dc73ec52e32" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4Yf2VdOD4VNV9Ey8VQ9g%2Fimage.png?alt=media&amp;token=1221f79d-031c-4872-a923-52a02fd85851" alt=""><figcaption></figcaption></figure>

* 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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHe55BaP8CTts4u2g5rOx%2Fimage.png?alt=media&amp;token=7519ea39-9ec3-45ad-b69c-c544ca9f5d3a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGLhl50tFOl8hwqui1RMi%2Fimage.png?alt=media&amp;token=d0610a09-c54a-4dba-ba1d-cbae4788352e" alt=""><figcaption></figcaption></figure>

### 5.1 - Show / Hide Columns <a href="#toc195011840" id="toc195011840"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FaOi7HSZjlXqnAIeZUzfH%2Fimage.png?alt=media&amp;token=453f910f-9893-4a65-93b2-a35c1aaee36f" alt=""><figcaption></figcaption></figure>

Or by searching in the ribbon search bar in the top right corner

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsrXzeWCYP1B1XDcgVhWK%2Fimage.png?alt=media&amp;token=e074c423-baad-44e1-a959-1c17edb7e433" alt="" width="563"><figcaption></figcaption></figure>

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 <a href="#toc195011841" id="toc195011841"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fr5CJB5oZ4uLXfrz2fH80%2Fimage.png?alt=media&amp;token=792464af-e506-4cc2-8fc9-51359d295d55" alt="" width="319"><figcaption></figcaption></figure>

* Click on **Add Target** and the Target Properties section will become editable for the new target.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwwUjPAp1A8pD6rDFn06Y%2Fimage.png?alt=media&amp;token=7b1e7d25-06bd-4066-b29b-194157a65c20" alt=""><figcaption></figcaption></figure>

* Target name, target center coordinates and display colour and line style can be selected.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyIDVz7WjEQtdhCO8VVvY%2Fimage.png?alt=media&amp;token=88ac60f3-4dbc-4293-84d5-68c7a3221060" alt="" width="563"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEYZYtfFaIJd7Qd3y67wC%2Fimage.png?alt=media&amp;token=1e1feff8-55de-4427-92b6-c00ce7f5ca57" alt="" width="563"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNdMfrWdkgCoPnvvh7XX9%2Fimage.png?alt=media&amp;token=f825b723-dca8-4c6c-b2f8-50d52b2a72f6" alt="" width="386"><figcaption></figcaption></figure>

* You will now be able to choose which levels the target will be visible on. Just check the required box and click *Save*.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FoCEaimOzDu77xejii0XF%2Fimage.png?alt=media&amp;token=c871411f-db0c-4dcf-a756-71b3e0c78c21" alt="" width="389"><figcaption></figcaption></figure>

### 5.3 - Adding a Lease Line or Hard Line <a href="#toc195011842" id="toc195011842"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7ot9PqkVunQ55zZUIor8%2Fimage.png?alt=media&amp;token=04cd4bdc-f9b1-44a3-a46e-b39e702950d8" alt="" width="563"><figcaption></figcaption></figure>

**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 <a href="#toc195011843" id="toc195011843"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMmwV9mqJWpHbFrXeFV1s%2Fimage.png?alt=media&amp;token=27f5a9c8-e104-4ecd-98c2-75476c0e9d34" alt="" width="322"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgamKeKHA9hUTsZPuJqzL%2Fimage.png?alt=media&amp;token=12b84754-7696-4457-aae7-f51876b28fe6" alt="" width="335"><figcaption></figcaption></figure>

### 5.5 - Adding Lithology Details <a href="#toc195011844" id="toc195011844"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1um7xmV7Jrjcndn9WE9g%2Fimage.png?alt=media&amp;token=84cd447d-ed2f-400c-8ffa-1e380a7ee358" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fy84dJ9njRTeF3ewcFl61%2Fimage.png?alt=media&amp;token=74522e18-56cf-45a0-a53f-66cb80ab50be" alt="" width="375"><figcaption></figcaption></figure>

### 5.6 - Adding Annotations <a href="#toc195011845" id="toc195011845"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FR2sFMUfcU3rzcZd0gKx2%2Fimage.png?alt=media&amp;token=aa861929-c1aa-4743-8be8-b73493eafa64" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUqtK272DvdZL1NSstD85%2Fimage.png?alt=media&amp;token=5b040855-805f-4072-8282-ba28a96ed4df" alt="" width="375"><figcaption></figcaption></figure>

## 6.0 - Creating a new Actual Survey <a href="#toc195011846" id="toc195011846"></a>

* Right click on the Well and select **Insert new actual well.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWqXNy8oGwXEYYL9q6HWU%2Fimage.png?alt=media&amp;token=a7740a3a-d658-4a01-af6b-220a0df782e7" alt=""><figcaption></figcaption></figure>

* The **Actual Wellbore Properties** box will now appear.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVIKaV019yv1AhMjBArVn%2Fimage.png?alt=media&amp;token=252767f4-4d65-4748-9105-6b16fed889a0" alt="" width="531"><figcaption></figcaption></figure>

* 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 <a href="#toc195011847" id="toc195011847"></a>

* Right click on the Actual Well and select **Insert new survey**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxWAcGNtFWiiKvI3jwUSg%2Fimage.png?alt=media&amp;token=ed913aef-ea50-46c5-9b46-f4e279620a5e" alt="" width="273"><figcaption></figcaption></figure>

* The **Survey Properties** box will now appear

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FobDAqHRm4opWrfTX8dGO%2Fimage.png?alt=media&amp;token=7d157a25-ae74-4695-9f46-94851329df09" alt="" width="437"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBSqX6e5SyMPzFm5yTRP6%2Fimage.png?alt=media&amp;token=c306b2b4-d974-4460-b805-8e5d8a1294a3" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBC6UXBTpxblhLZ1VrJsA%2Fimage.png?alt=media&amp;token=fbb5dcfe-64b8-4ce4-af92-9129ac2f24d7" alt="" width="242"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcZxPcIpPpdyqb8vhxhXv%2Fimage.png?alt=media&amp;token=10faeb45-45b2-4e1a-b655-1b518c91cd41" alt="" width="380"><figcaption></figcaption></figure>

* 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 <a href="#toc195011848" id="toc195011848"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXYWbUC6jbZish2ZHLneN%2Fimage.png?alt=media&amp;token=9afb60f9-dd9c-4fa7-bec6-f126f88a9685" alt=""><figcaption></figcaption></figure>

## 7.0 – Importing a Compass Export File <a href="#toc195011849" id="toc195011849"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6oPB0iMxkTfnETHvT3mv%2Fimage.png?alt=media&amp;token=bd27dd91-062d-4492-aef5-1cc0c28396af" alt="" width="563"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvtdtpVOFdX2p9ko0RE37%2Fimage.png?alt=media&amp;token=279ef656-2221-47ad-aacd-3f7f0cf4353c" alt="" width="512"><figcaption></figcaption></figure>

* **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 <a href="#toc195011850" id="toc195011850"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fn4XlUMHLG2fsCHGqtaQK%2Fimage.png?alt=media&amp;token=18859467-b65f-4719-a91f-ddf20676a9b7" alt="" width="563"><figcaption></figcaption></figure>

* **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) <a href="#toc195011851" id="toc195011851"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNkta8GiW0VkJjh5WjeZL%2Fimage.png?alt=media&amp;token=0ed2408d-ed4d-494a-833d-87d6e148024e" alt="" width="542"><figcaption></figcaption></figure>

The following instructions detail how to use this information to create a new CRS.

* Open the **Geomagnetic Calculator** by selecting **Tools > Geomag Calculator**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fhh39WZYW25SpeDWINrld%2Fimage.png?alt=media&amp;token=b0e09aec-6a9b-482b-baf7-e4b94b20cc6c" alt=""><figcaption></figcaption></figure>

* Click on the "**Mapping Grid**" button at the top left of the dialog.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FN5HCIOjpijzEvoF3vMCq%2Fimage.png?alt=media&amp;token=1a7ff64c-827e-4938-8385-c246e22aa8b4" alt=""><figcaption></figcaption></figure>

* Select **Add** at the top left of the Mapping Grid.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FszKJoC9ephHcc7TzMUkM%2Fimage.png?alt=media&amp;token=54c13c79-fc17-480c-8efa-0c3aeb3c96ce" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBTzmnPW3ymVUBSOTWPyY%2Fimage.png?alt=media&amp;token=11e9b94d-1924-41d7-bf7c-c7a7234f9df3" alt=""><figcaption></figcaption></figure>

Parameters in <mark style="color:red;">**RED**</mark> 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 <mark style="color:green;">**Polska 1992 / Transverse Mercator (Gauss-Kruger) Zone 3**</mark>
* **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 <mark style="color:green;">**Poland**</mark>.
* **Datum**: This is just text and does not directly affect any calculations. For this example it is <mark style="color:green;">**WGS1984**</mark>.
* **System**: This is just text and does not directly affect any calculations. <mark style="color:green;">**Polska 1992**</mark>
* <mark style="color:red;">**Ellipsoid**</mark>: This is important and you have to choose from a drop down list of 38 options. In this example you would choose <mark style="color:green;">**WGS 84**</mark>
* **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.
* <mark style="color:red;">**Units of Measure**</mark><mark style="color:red;">:</mark> This is a drop-down menu option and you can choose from 7 options. For this example, it would be <mark style="color:green;">**metre**</mark>
* **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 - <mark style="color:green;">**Transverse Mercator (Gauss-Kruger) Zone 3**</mark>
* <mark style="color:red;">**Projection Type**</mark><mark style="color:red;">:</mark> This is a drop-down menu and you can choose from 4 options – TM, 1SP (Standard Parallel), 2SP or STEREO. In this example, choose <mark style="color:green;">**TM.**</mark>
* <mark style="color:red;">**False Easting**</mark><mark style="color:red;">:</mark> <mark style="color:green;">**500000.00**</mark> m.
* <mark style="color:red;">**False Northing**</mark>: <mark style="color:green;">**-5300000.00**</mark> m.
* <mark style="color:red;">**Latitude of Origin**</mark><mark style="color:red;">:</mark> This should be input as a decimal <mark style="color:green;">-</mark> <mark style="color:green;"></mark><mark style="color:green;">**0.0000**</mark> deg.
* <mark style="color:red;">**Longitude of Origin**</mark><mark style="color:red;">:</mark> This should be input as a decimal <mark style="color:green;">-</mark> <mark style="color:green;"></mark><mark style="color:green;">**19.0000**</mark> deg.
* <mark style="color:red;">**Scale Factor**</mark><mark style="color:red;">:</mark> Ratio between measured distance on the map and on the ground - <mark style="color:green;">**0.99930**</mark> deg.
* <mark style="color:red;">**1st Standard Parallel**</mark><mark style="color:red;">:</mark> This information will be required if you select 1 SP or 2 SP from the Projection Type Drop down menu - Not applicable here
* <mark style="color:red;">**2nd Standard Parallel**</mark><mark style="color:red;">:</mark> 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:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSqzJzB4pIHRP7jelqeT0%2Fimage.png?alt=media&amp;token=0bc960ea-0739-4a9b-b715-66e274fcbfa7" alt="" width="456"><figcaption></figcaption></figure>

* Select Save CRS and your new CRS will be available to select from the mapping grid dropdown menu.

## 10.0 – Charts <a href="#toc195011852" id="toc195011852"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDpIhj8w7gilEHmzibDfD%2Fimage.png?alt=media&amp;token=10bd4114-1671-4115-8165-a5441f236c81" alt="" width="563"><figcaption></figcaption></figure>

With the desired reference data table open and selected, click the required chart icon from the Home toolbar.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fsy3nGRmojZqmDdBxeuAk%2Fimage.png?alt=media&amp;token=118115f4-d07f-4ff3-9e9e-183b4b765e3c" alt="" width="563"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeRJmo7GXUNZNBY5vzaA9%2Fimage.png?alt=media&amp;token=112c2bbc-f5f5-4a6b-bd5b-e77528f808d9" alt="" width="556"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0PqgHfNVMkICMT7KNz4V%2Fimage.png?alt=media&amp;token=2761d3c8-45bc-4cbd-a25e-a6fa3e952814" alt="" width="563"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvSBvC7pncrE7igM7vRAL%2Fimage.png?alt=media&amp;token=f5786a4a-1e07-46ea-80a5-9195c636b5dc" alt="" width="418"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9OzyVadN9GMII0v6ilpd%2Fimage.png?alt=media&amp;token=50554693-d4ca-4710-8dff-5b9eca14ba11" alt="" width="563"><figcaption></figcaption></figure>

### 10.2 - Chart Properties <a href="#toc195011854" id="toc195011854"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FshmsRMvn2AE5NbjkbJl7%2Fimage.png?alt=media&amp;token=2f929e69-ae55-4e52-a2aa-3c78aae887e8" alt="" width="473"><figcaption></figcaption></figure>

This is where most of the chart functionality is located, and allows the user to add labels, change colours and customise the plot.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5ee12OBbbzOmHLOwvhVR%2Fimage.png?alt=media&amp;token=64494bf9-5098-4921-b30d-26fd27f5a3c3" alt="" width="563"><figcaption></figcaption></figure>

### 10.3 - Chart Zoom and Chart Scales <a href="#toc195011855" id="toc195011855"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWfFikQhM5LfFJAR1xGUa%2Fimage.png?alt=media&amp;token=4c5a423e-4f28-4bc5-8ebd-48e9aea7c912" alt=""><figcaption></figcaption></figure>

### 10.4 - Grid Lines <a href="#toc195011856" id="toc195011856"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYx5aOYIXLcGWJlLDZ6N8%2Fimage.png?alt=media&amp;token=eb2e839b-f616-4c43-a01d-23dbf898fc91" alt=""><figcaption></figcaption></figure>

### 10.5 – Plot Defaults <a href="#toc195011857" id="toc195011857"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FENr3mHemC8WDPd4GRrFG%2Fimage.png?alt=media&amp;token=5bf20e37-a435-49da-900c-6d1f8eca4305" alt=""><figcaption></figcaption></figure>

## 11.0 – Wall Plot Composer <a href="#toc195011858" id="toc195011858"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGL6vSPywaiObN9rhGQP5%2Fimage.png?alt=media&amp;token=a9ca21ac-7e49-433a-a3a6-fe233d5d8080" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6C4ZFj1Iot6eShtE5HLy%2Fimage.png?alt=media&amp;token=d5ec4023-7d18-471a-948a-5dda8a0fb084" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQHyZb5Fw6J5MNlVgmZgA%2Fimage.png?alt=media&amp;token=55176ee7-e57f-4c42-947b-c8ad80723192" alt=""><figcaption></figcaption></figure>

### 11.1 - Saving a WPC Template <a href="#toc195011859" id="toc195011859"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhUleCIBesRvyrD5l5GlL%2Fimage.png?alt=media&amp;token=31391da5-2e5a-42aa-833a-77553ddfc24b" alt="" width="374"><figcaption></figcaption></figure>

### 11.2 - Table Text and Logo Size <a href="#toc195011860" id="toc195011860"></a>

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 <a href="#toc195011861" id="toc195011861"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFPdDL7ugcNYHiXVv9yyd%2Fimage.png?alt=media&amp;token=ad797607-ee31-496e-9e76-4e9ecd8b8f77" alt="" width="563"><figcaption></figcaption></figure>

### 11.4 - Screen Zoom <a href="#toc195011862" id="toc195011862"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fr1QjDzQZpX4CpiqwrClu%2Fimage.png?alt=media&amp;token=4ccb5b1e-3b8d-4473-bb34-99a461209f89" alt="" width="563"><figcaption></figcaption></figure>

The user can also hold CTRL and scroll the mouse wheel to zoom in and out.

## Appendix A – Well Planning Tools <a href="#toc195011863" id="toc195011863"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fr9aHZe6wPF4O9nMA0nYC%2Fimage.png?alt=media&amp;token=86e5e8a1-7a39-4d99-8da3-baa6102761e4" alt=""><figcaption></figcaption></figure>

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 <a href="#toc195011864" id="toc195011864"></a>

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 <a href="#toc195011865" id="toc195011865"></a>

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 <a href="#toc195011866" id="toc195011866"></a>

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 <a href="#toc195011867" id="toc195011867"></a>

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 <a href="#toc195011868" id="toc195011868"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fxyy0pHTR8flfd2hOvFjS%2Fimage.png?alt=media&amp;token=cdf71a9a-0730-44c2-94ef-b823acd5436b" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1GrYQOav09t8lhjk9mhb%2Fimage.png?alt=media&amp;token=18ea83b5-3ced-4612-84e3-f37392ba24eb" alt=""><figcaption></figcaption></figure>

### A.6 – 2D Planning <a href="#toc195011869" id="toc195011869"></a>

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 <a href="#toc195011870" id="toc195011870"></a>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAg1azN2sRRXuZn5b0Myp%2Fimage.png?alt=media&amp;token=01df264e-16fa-48a9-ba45-62de14c115c0" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9z5nBmNkoRd0LrF7BdTr%2Fimage.png?alt=media&amp;token=c05127c4-ff7e-447f-b7e5-64718ba65277" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fm72dFLYSRoRWLfgyT1Te%2Fimage.png?alt=media&amp;token=bb93b6ca-a7cd-469a-a2ef-20445aa1bb46" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfvtXnY4IMk6mZasYlWrL%2Fimage.png?alt=media&amp;token=6e43ca52-5042-4470-8d9d-2c072ddc3ef5" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fi4TsVwk20GKv6qqrLA86%2Fimage.png?alt=media&amp;token=226f6a73-aae9-4f30-ba93-87ca43091568" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ft93KiqlvEUsXauDrh19f%2Fimage.png?alt=media&amp;token=099680d3-c497-40f8-a3ac-3cb14ea1528c" alt=""><figcaption></figcaption></figure>

#### Slant Well <a href="#toc195011871" id="toc195011871"></a>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4PjOu3ImzebdATHgKh0y%2Fimage.png?alt=media&amp;token=2489abeb-9a48-4d53-8a9f-1fe9bc064f7f" alt="" width="563"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0FfcKdIIDKQzDWuQr4vA%2Fimage.png?alt=media&amp;token=77f01955-7e07-4ed0-8f6c-75c5b7641b75" alt=""><figcaption></figcaption></figure>


# Well Seeker X: Backing up a WS Db

## 1.0 - Introduction <a href="#toc194050167" id="toc194050167"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKHnlvEMTDZePVhiC1WOD%2F0.png?alt=media" alt="" width="509"><figcaption></figcaption></figure>

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFDJAxQHsfJx2cYQWLu2L%2F1.png?alt=media" alt="" width="563">

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwAxP5fmokdbEIqDuSss1%2F2.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FX0AgOpdmK05tjXynP6cm%2F3.png?alt=media)

## 2.0 – Backing up a Database <a href="#toc194050168" id="toc194050168"></a>

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.

If you are using **Well Seeker X version 3.0.3.4 or later**, an automatic backup feature is now available.

Well Seeker automatically creates a backup of the open local database every **two hours**. These backups are saved in the following folder:

* C:\Users\Username\AppData\Roaming\Well Seeker Pro\DB Backup

Up to **twenty versions** of the same database are retained. Once this limit is reached, the oldest backup is automatically overwritten.

### 2.1 – Backing up the current database <a href="#id-2.1_-_backing" id="id-2.1_-_backing"></a>

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNvUx3Tp5nOluQ8tDRyUe%2F4.png?alt=media)

* Choose an appropriate location to save the database and select an appropriate name. For example, **Master Db.mdb** or **Master Db (**<mark style="color:red;">**Date**</mark>**).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 <a href="#id-2.2_-_backing" id="id-2.2_-_backing"></a>

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 (**<mark style="color:red;">**Date**</mark>**).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 <a href="#toc194050171" id="toc194050171"></a>

When necessary, a backup database can be accessed when in Well Seeker by selecting **Home > Select** in the Database ribbon men&#x75;**.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ff2M2tCr59v2jgjfvlvJE%2F5.png?alt=media)

The user should then navigate to and select the relevant back up.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRyYMWxXM7Yt4dwE0GAMD%2F6.png?alt=media" alt="" width="563">

## 4.0 - Important Points to Note <a href="#toc194050172" id="toc194050172"></a>

### 4.1 - Back Up Location <a href="#toc194050173" id="toc194050173"></a>

The backup location should **NOT** be in the <mark style="color:red;">**Programs (x86) folder**</mark>. 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 <a href="#toc194050174" id="toc194050174"></a>

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. <mark style="color:red;">This uninstall process removes all the files which initially came with the install. This</mark> <mark style="color:red;"></mark><mark style="color:red;">**INCLUDES**</mark> <mark style="color:red;"></mark><mark style="color:red;">the original</mark> <mark style="color:red;"></mark><mark style="color:red;">**Well\_Seeker\_DB.mdb**</mark> <mark style="color:red;"></mark><mark style="color:red;">database</mark>. Although Innova recommends that users create their own database when they first start using the software some users prefer to work in the default. <mark style="color:red;">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.</mark>

### 4.3 – mdb / ldb Files <a href="#toc194050175" id="toc194050175"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSXR85eEpphJi7VLlMpQP%2F7.png?alt=media)

**Questions relating to any of the above can be sent to** [**support@innova-drilling.com**](mailto:support@innova-drilling.com)


# Well Seeker X: Changing Datum Elevations

## 1.0 - Introduction <a href="#toc193899675" id="toc193899675"></a>

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 <a href="#toc193899676" id="toc193899676"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFg5gvBr8LULGxN8Gj1QB%2Fimage.png?alt=media&amp;token=6c80e4bc-7572-4f59-8e83-87343bf97eab" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHOsVY1Psdnex1cHg5lcd%2Fimage.png?alt=media&amp;token=4a143a53-cd2a-42fa-861a-854cad4e7bb5" alt=""><figcaption></figcaption></figure>

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:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4jM6ROmmhUMR3ruVmiZr%2F4.png?alt=media)

The user has three options:

1. **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.
2. **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.
3. **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 <a href="#toc193899677" id="toc193899677"></a>

In this example, we have a simple set of surveys, referenced to the below left RTE (RTE Plan) @ 100Usft AMSL.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FO4hGlnAnQclHvT7vUOzI%2F5.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FM11vDtVa2TzInOc1lykW%2F6.png?alt=media)

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyaAi598OBc6UNmYKDz4I%2F7.png?alt=media" alt=""><figcaption></figcaption></figure>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWnKQiAvC3bOqMXLgxMIU%2F8.png?alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcbVahrZPs0KqFisVwlKo%2F9.png?alt=media)


# 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

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fe2AWfzfQxYShNhQj0nVx%2F0.png?alt=media)

2. Open the **IPM** folder.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FenMhCWarSxP60Ih1Q1KQ%2F1.png?alt=media" alt="" width="410">

3. Close Well Seeker X.
4. Paste your IPM file into the IPM folder.
5. Open Well Seeker X.
6. 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

1. Open Well Seeker. Select the **Tools** tab and select **Survey Tools** from the **IPM Files** section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWXNkCq83SqrbBrZFn7IJ%2F2.png?alt=media)

2. Click the **Add new IPM** button.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVmGqLwd0sd2Cdq8HLvZ7%2F3.png?alt=media)

3. Enter a suitable file name and hit save.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrHr5inDezjlYPtUyHrYe%2F4.png?alt=media" alt="A" width="563">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqbTQ55eb68svFTdydO3T%2F5.png?alt=media" alt="" width="494">

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgzQ8JYy9PD6VP4r0kIlX%2F6.png?alt=media" alt=""><figcaption></figcaption></figure>
6. Your new IPM will be available to select from the dropdown menus in the **Survey Properties** window and the **Plan Properties** window.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHNbXtpsjdLmssvb3ic8w%2F7.png?alt=media" alt="" width="511">


# Well Seeker X: Local Login Guide

## 1.0 – Introduction <a href="#toc194436801" id="toc194436801"></a>

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 <a href="#toc194436802" id="toc194436802"></a>

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 <a href="#toc194436803" id="toc194436803"></a>

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**](https://docs.innova-drilling.com/introduction/web-portal-manual/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**:

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVVxNIAWcy0PQsMZhh1Qk%2F0.png?alt=media" alt="" width="534">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FahVUZiUDH5EIgMCWhKpk%2F1.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCd3MEVcXiHLMIBb9dpNk%2F2.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3bedbFDyuZCatckDOME0%2F3.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fe6NWbDfzSen3SgpokYLz%2F4.png?alt=media)

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F922bzqwYGrVvhuhoNmYM%2Fimage.png?alt=media&amp;token=5c065000-ab41-4ba8-832f-45828fc3e94b" alt=""><figcaption></figcaption></figure>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FckStNrWY9wDUfGaOCsEN%2F7.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fg7XLYHg4Zb0ollUHOSbI%2F8.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnL5sYNQAUsfKAA22K3DU%2F9.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F04VdgBM5Aq0hJHRTCI0m%2F10.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRhZzbHdL1EhYdy8ECF6T%2F11.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgdDJAaXLNxmaUrJggJUb%2F12.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FiL51NwyjpqlsCdFwpxO1%2F13.png?alt=media)

### 2.2 – Create Users and Assign a Role <a href="#toc194436804" id="toc194436804"></a>

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**](https://docs.innova-drilling.com/introduction/web-portal-manual/19.0-user-management#id-12.1.1-adding-a-new-user) section of the Web Portal Manual.

### 2.3 – Enabling the Local Login Feature <a href="#toc194436805" id="toc194436805"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXb567hyrzrxdKG45VN1a%2Fimage.png?alt=media&amp;token=3fe4de17-e4a5-47ac-b65d-36b41254e437" alt="" width="209"><figcaption></figcaption></figure>

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**](https://docs.innova-drilling.com/introduction/technical-notes/well-seeker-pro-technical-notes/data-synchronization-feature-update) **document.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXjJzkPWerRAQqSadZPkY%2F16.png?alt=media)

## 3.0 – Well Seeker X Local Login Process <a href="#toc194436806" id="toc194436806"></a>

If the Local Login feature has been enabled the following will be true.

* Well Seeker X will open and immediately require valid login credentials

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQIr6QJ1TWMKqepf8Ft1d%2F17.png?alt=media)

* 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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FY2RxfFNty9ZQSRi5YF5H%2F18.png?alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6VK7Qvz4T9e5nOYDZIES%2F19.png?alt=media)

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: Project Ahead Guide

While a well is being drilled, it is often necessary to project ahead of the most recent survey for the purposes of anti-collision, or to see what is required to get back on plan. The following document is a guide to the **Project Ahead** and **Multi Nudge** tools within Well Seeker X.

## 1.0 - Introduction <a href="#toc195013065" id="toc195013065"></a>

The Project Ahead tool can be found on the ribbon menu **Home > Project Ahead Bit Projection** at the top of the screen.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIoWIHJardNlc98enuwdQ%2F0.png?alt=media)

Or searching for the name in the top right corner:

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzdLzzRyM0JsRhXyq2KDb%2F1.png?alt=media" alt="" width="563">

It is important to note that this option is only available when the user is in a **Survey**. If the user is in a **Plan**, or the **Actual Wellbore**, this option will be greyed out and they will be unable to select it.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrdFX6JPrFcSQZVuEmHZa%2F2.png?alt=media" alt=""><figcaption></figcaption></figure>

## 2.0 – Projecting Ahead

When in a survey, select the Project Ahead option. This will open the Project Ahead Box.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEelsCT2npO07cs7OBZnG%2F3.png?alt=media)

Note, that Line 1 at the top of the box will be populated with the last survey point. The projection will be made from this point.

The user can now select from the same Planning Tools which are available when creating a well plan, with the exception of the S-Well and Slant-Well tools, as these can only be plotted from surface.

## 3.0 - Planning Tools <a href="#toc195013067" id="toc195013067"></a>

Once the relevant planning tool has been selected and the values entered, the projection is calculated by selecting **Calculate**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQ6ILDw44CV1QdU3CRcIE%2F4.png?alt=media)

The projection can then be added to the survey by selecting **Append** and removed from the survey by selecting **Remove**.

Two of the more relevant projection options are discussed below.

### 3.1 - Trend Over <a href="#toc195013068" id="toc195013068"></a>

The **Trend Over** tool is only available in the **Project Ahead** dialog and is not displayed in the planning tools when in a well plan. This function allows the user to apply the build and turn trends seen in the previous surveys to the projection.

To select the Trend Over function, the user must select **Adjust** and then either **MD** or **CL**. This function will remain greyed out until these options have been selected.

![.](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSXJ3PHB27USH7KlwI7wm%2F5.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fi7qV71Ko5kzDC4jKwRKx%2F6.png?alt=media)

Select the Measured Depth (MD) or Course Length (CL) of the projection and the number of surveys to model the trend over, then hit the calculate button. The projection will appear in line 2, directly below the last survey in the Project Ahead box.

The tool works by averaging out the Build and Turn rates based on the number of surveys selected.

In the below example, **1** survey has been selected, so the projection just uses the build and turn rate calculated for the last survey.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fk97ogrsCwCadtszuuN45%2F7.png?alt=media)

In the below example, **3** surveys have been selected, so the projection calculates the average build and turn rate values over the last 3 surveys.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fo85LeI9lWn9j3qMvB7C7%2F8.png?alt=media)

**Average Build Rate**=<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGX4N7dLTlo3koUub2xLt%2Fimage.png?alt=media&amp;token=ecb63df3-ca0f-4df0-92d4-ac57f02f8679" alt="" data-size="original"> = **0.08°/100USft**<br>

**Average Turn Rate**= <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSPSXxL50IkSWfws3HvoZ%2Fimage.png?alt=media&amp;token=1bce43f1-78f2-4044-a605-01110a60ee42" alt="" data-size="original"> = **-0.71°/100USft**

### 3.2 - Optimum Align - Plan <a href="#toc195013069" id="toc195013069"></a>

Using the **Optimum Align** function, it is possible for the user to project back onto a plan.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZH5yzg6sLCt453PGzXOl%2F9.png?alt=media)

1. Select **Optimum Align**
2. In the target details section, select **Plan** - all the plans below the Well will be available to select from the drop-down menu – Select the relevant plan
3. In the **By MD** box, input the **Measured Depth** on the plan that you want to line up on. On entering the depth, the NS, EW, TVD, Inc and Azi will be automatically populated with the values that correspond to this depth
4. Select the relevant **Optimum Align Parameters**
5. Hit **Calculate**

**NOTE**, that once the projection has been calculated, the measured depth in almost all cases will not match the depth entered in the By MD box.

## 4.0 – Multi Nudge Projection <a href="#toc195013070" id="toc195013070"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcWmgH5F44TuB2dnzpEqh%2F10.png?alt=media)

When in a survey, this tool can be selected from the ribbon menu **Home > Multi Nudge Bit Projection** or by **searching in the** top right of the screen.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYfS99ArhuFaaAklIVfGn%2F11.png?alt=media)

When the tool first opens, the Tie-On line will be populated with the last survey in the listing. At this point the user can then select from 1 of 7 projection Methods.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKDJP7CwKIP3wwgIEy3h2%2Fimage.png?alt=media&amp;token=890c1d9d-d639-40e9-b78f-42d8d9df019e" alt=""><figcaption></figcaption></figure>

The Multi Nudge Projection box can be left open while the user is adding new surveys, and the tie-on line can be updated by selecting the ***Update Tie On*** button. Note, that the surveys do not need to be saved for this to happen.

If the box is closed and then reopened, it will automatically tie onto the last survey point. The projection setup will remain populated with whatever setup the user had selected previously, even when the program has been closed and reopened. To remove the input projections, the user can delete the lines one at a time or select ***Reset*** to remove all projections.

Projections can be added to the survey by selecting ***Append to Survey*** and can be removed by selecting ***Remove from Survey***. The Multi Nudge Projection window can remain open while using other Well Seeker functions, but all projections must be removed from the survey before new survey stations can be entered.

If the user has a slide sheet currently open, ***Get from Slide Sheet*** will pull the slide sheet entries in as projections.

**Note:** If the user has not input the motor yield for their slides in the slide sheet, the motor yield and the DLS will default to 15 in the Multi Nudge Projection.

The five projection methods are described below.

### 4.1 - CL/DLS/TFO <a href="#toc195013071" id="toc195013071"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIlL3D5PED5jeDxVpkvui%2F13.png?alt=media)

### 4.2 - CL/Slide (%)/TFO <a href="#toc195013072" id="toc195013072"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fz80kkYkf0Zz7OOigHfvl%2F14.png?alt=media)

In the example above, the slide (%) is 50% and the motor yield is 5°/30m, which results in a 2.5°/30m DLS.

### 4.3 - CL/Slide (Dist)/TFO <a href="#toc195013073" id="toc195013073"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCb2UMISCArY0QnRh5k66%2F15.png?alt=media)

In the above example, the Slide Distance is 4m (Course Length is 10m) and the motor yield is 5°/30m, which results in a 2.0°/30m DLS.

### 4.4 - INC/AZI/DLS <a href="#toc195013074" id="toc195013074"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmljYCJ8funh5RQCoHMGm%2F16.png?alt=media)

### 4.5 - Hold CL <a href="#toc195013075" id="toc195013075"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxVwjydIzDVHAEbLLL4VV%2F17.png?alt=media)

### 4.6 - Hold MD <a href="#toc195013076" id="toc195013076"></a>

This option allows the user to select Measured Depth (MD). The inclination and azimuth from the tie-on line will be held for the selected depth.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEJG4Uw8BlICPD4Z2vCBP%2F18.png?alt=media)

### 4.7 - MD/INC/AZI

This option allows the user to select Measured Depth (MD), Inclination (Inc) and Azimuth (Azi) to calculate the projection.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXqBSoRKnHSuqwaIGEkHE%2Fimage.png?alt=media&amp;token=107944a4-656f-4e1d-8296-31c1c79b8b39" alt=""><figcaption></figcaption></figure>

### 4.8 - Multiple Projections <a href="#toc195013077" id="toc195013077"></a>

The user can set up the Multi Nudge Projection with as many lines as required.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLDJYGQqZOAGrrTqpTqQ1%2F19.png?alt=media)

## 5.0 - Landing Data <a href="#toc195013078" id="toc195013078"></a>

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYYcBmo9yocU0nEC4zQgU%2F20.png?alt=media)

Note that this section will only work if a **principal plan** for the well has been assigned. To set a plan as a principal plan, right-click on the plan in the database tree and select **Properties.** In the Properties window check the **Set as principal plan** checkbox next to the well name.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0bGmD9vnGOZ8XPujq6KT%2Fimage.png?alt=media&amp;token=f62e1018-1268-4fa1-8696-25c4acdd6f81" alt=""><figcaption></figcaption></figure>

### 5.1 - Bit Position <a href="#toc195013079" id="toc195013079"></a>

The Bit row displays the deepest survey station in the currently opened survey sheet. As this is the most recent survey, to accurately use this projection tool, the user should make a projection to the bit to get the true bit position. To do this the user should make a projection in the top window and append it to the to the survey, as displayed in the image below. The Bit row will update automatically when the projection is added. If for any reason this does not happen, the **Update Bit Position** button can be used to force an update.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzvsOQIgpxZn25WSOV3vu%2Fimage.png?alt=media&amp;token=365ceb25-b509-4415-95a6-67d389061d33" alt=""><figcaption></figcaption></figure>

### 5.2 - Entering a Landing Point MD <a href="#toc195013080" id="toc195013080"></a>

When a MD is entered in the Target row, Well Seeker looks for this MD on the Principal Plan and then populates the rest of the cells in the row with the values from the plan. The Landing Data tool then automatically calculates the constant **Tool Face** and **DLS** required to reach that point on the **principal plan** from the bit position shown in the **Bit** row.

In the below example, the MD of the curve landing point (15984.76 USft MD) has been entered and the TVD, NS and EW coordinates in the projection match the plan at this depth. The Tool Face and DLS columns show the Tool Face and DLS required to reach this landing point from the current bit position. Note that the plan is open here for demonstration purposes. It does not need to be open for the Landing Data window to work.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1yoJXWUv0utB7kbBa3xA%2Fimage.png?alt=media&amp;token=83511b34-369b-4f43-8228-6b7327648239" alt=""><figcaption></figcaption></figure>

The **Select Critical Point** drop down box can be used to quickly select plan points from the principal plan as the landing target. If the principal plan is changed while the Multi Nudge Projection is opened, the list of plan points can be updated using the **Update** button.

The user can also enter a target using the **Find Landing** button. This button will automatically pick the plan point from the principal plan that has the highest inclination. If multiple plan points share the highest inclination, the Find Landing button will pick the shallowest.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRykXjVjmqRZ64wFV7LxE%2Fimage.png?alt=media&amp;token=fbac5b08-36e1-4911-940e-bf2b50ea8bba" alt=""><figcaption></figcaption></figure>

The **Append to Survey** button will add the Target row to the survey list as a projection, while the **Remove from survey** will delete it. Projections from both the Multi-Nudge section and the Landing Data section can be present on the survey list at the same time.

The landing data calculation should automatically update whenever new input data is added; however, if for any reason this does not happen, it can be updated manually using the **Calculate** button.

### 5.3 - Adjust TV <a href="#toc195013081" id="toc195013081"></a>

Selecting the **Adjust TVD** checkbox allows the user to change the TVD of the point selected in the above. The MD stays unchanged as this is what the program is using to determine the local coordinates of the landing point.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOx4wu2S6K9itXNrtyASv%2Fimage.png?alt=media&amp;token=791fa5fa-4c3f-487d-a35c-96c181f8f31c" alt=""><figcaption></figcaption></figure>

Note in the below example how the NS and EW local coordinates are still the same as the landing point line, but because the TVD has been shifted deeper the DLS, Tool Face and Inc have changed. The program is still aiming for a specific point here, only with an adjusted TVD.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F47n3yeMOniOyy1IsV9tp%2Fimage.png?alt=media&amp;token=55e32eb3-1ba1-407b-b341-69d7cdb6115c" alt=""><figcaption></figcaption></figure>

### 5.4 - Adjust Inc / Azi <a href="#toc195013082" id="toc195013082"></a>

This option is only available when **Adjust TVD** is selected.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFIMfqrsMIjnG5Ry6gQ6I%2Fimage.png?alt=media&amp;token=f7155a51-4d32-4a04-82cf-09d49d27bce2" alt=""><figcaption></figcaption></figure>

This allows the user to enter an Inc, Azi and TVD to project to. The main difference with this selection compared to the previous options is that the user is not projecting to a specific point i.e. the local coordinates are not fixed.

In the example below, the Inc, Azi and TVD are entered for the planned curve landing point. Note that the MD, NS and EW landing points are no longer the same as the landing point in the plan. This setup simply tells the user what dogleg is required to land out at horizontal for a given TVD. When new surveys are added, the bit line updates automatically and so does the landing point line.

**NOTE**: When you first open this dialogue, there is no requirement to enter a MD. It is possible to just select Adjust TVD and Adjust Inc / Azi and input the values. There is no need to add a MD unless you specifically want to hit an exact point.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOSEil60ocwHLjdS2ojL2%2Fimage.png?alt=media&amp;token=baee231d-aa30-4cc6-9662-6bb96e38add8" alt=""><figcaption></figcaption></figure>

### 5.5 – TVD Projection <a href="#toc195013083" id="toc195013083"></a>

The TVD Projection feature can be activated by clicking on the check box in the top right of the Landing Data window. This feature displays two new Target rows that are offset by a user specified TVD from the main Target row.

In the example below, TVD Projection 1 has been set as -10, so its target is the same as the Target row but 10 USft TVD shallower. TVD Projection 2 has been set as 10, so its target is 10 USft TVD deeper.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fj3nHTRU8JAAy0U8QXl4q%2Fimage.png?alt=media&amp;token=3c44b7c8-adba-4835-bd12-44f614f008ff" alt=""><figcaption></figcaption></figure>

The TVD projection feature can be used in tandem with the Adjust TVD and the Adjust Inc/Azi functions. TVD projections are for reference only and cannot be appended to the survey list.

### 5.6 – DLS to Land Chart <a href="#toc195013084" id="toc195013084"></a>

After selecting any Critical Point in the dropdown or hitting the calculate button in the Landing data section, a DLS to Land chart is displayed with a visual representation of the Dogleg Severity to Land. This chart will be presented by default in the units previously selected.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWbfVyxgY5TT2c6LhbGaE%2Fimage.png?alt=media&amp;token=1dc984d2-1252-4989-b30f-dd50bcb7f3ad" alt=""><figcaption></figcaption></figure>

A right-click in the chart area will display a context menu with options to edit the chart visualization,. These changes will return to default mode once the Multi Nudge Projection is closed and opened again.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FC3TlgtaxIr2ELounheha%2Fimage.png?alt=media&amp;token=4fc7a53a-f785-4ae6-9ddb-45f73633225f" alt=""><figcaption></figcaption></figure>


# Well Seeker X: Survey Correction Integration Guide

## 1.0 - Introduction <a href="#toc135722907" id="toc135722907"></a>

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 [**Well Seeker X How to Guide**](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-how-to-guide).

## 2.0 - Description <a href="#toc194913005" id="toc194913005"></a>

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7XfBquprlw9zseyE2asq%2F0.png?alt=media" alt="" width="563">

2. Select **Integrations** in the ribbon menu and select **MSA** in the Survey Correction section.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F22damvRcLva2z4onQmmr%2F1.png?alt=media" alt="" width="563">

This will open the Survey Correction Provider Settings window.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwcRh5zr8Oua3kxmX3Crv%2F2.png?alt=media" alt="" width="375">

Note that MSA option will be greyed out if a survey is not open.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJeXrvnKiGPlzFq9jy0Qp%2F3.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVoMisIooO1oVcEaHRiAH%2Fimage.png?alt=media&amp;token=007cbc98-c9a5-4410-a4d7-a6f27cdafe11" alt=""><figcaption></figcaption></figure>

4. Click on ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkJNLTVhbF6FcEhjJoAfY%2F5.png?alt=media) **Get Wells** to open the Well Selection dialog. Depending on your provider, the Well Selection dialog will look slightly different.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fx2BMbB7kvMEKYHyzLrrq%2F6.png?alt=media" alt="" width="482"><figcaption></figcaption></figure>

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fm2A5TWk2mTWnXENMjXTr%2F7.png?alt=media" alt="" width="563">

6. Click on ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWvImHqXR5wEPKMHfPkNI%2F8.png?alt=media) **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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDfTK8RSTrAzaduNZYGT4%2Fimage.png?alt=media&amp;token=6b90bc7e-fc43-4895-bb64-3d195442e0bf" alt="" width="239"><figcaption></figcaption></figure>
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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCv0ABsKUVG8Gl7jK1YHQ%2F10.png?alt=media" alt="" width="563">

8. Click on ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fq8pUvi0LagRm1ytTJsOk%2F11.png?alt=media)**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 ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjAY1QFkQvhwFylam3jOw%2F12.png?alt=media) **Cancel**.

### 3.0 - Superior QC Only features <a href="#toc194913006" id="toc194913006"></a>

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 <a href="#toc194913007" id="toc194913007"></a>

If the user has an API number for the well entered in the Daily Reporting section of Well Seeker, when the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWkiB1trtyWwe1pzH1kcJ%2F13.png?alt=media) **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.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGODKxykuGvB2SToopQRM%2F14.png?alt=media" alt=""><figcaption></figcaption></figure>

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGc6GWXlTYQe56lDWT1bJ%2F15.png?alt=media" alt="" width="375">

### 3.2 - Check Well Data <a href="#toc194913008" id="toc194913008"></a>

Clicking on ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjZxX7e2w1uJWIKstxEbS%2F16.png?alt=media) **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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZoyLUZ4UVCHDF5KbVZJz%2F17.png?alt=media" alt="" width="207">

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


# Updating Well Seeker X

Introduction

Innova regularly releases updates for the Well Seeker X software. These new releases may include new feature updates or they may address bugs which have been discovered.

Innova have three different methods of distributing updates to end users:

1. Via the inbuilt auto-update feature in Well Seeker X.
2. Distributing an updated Well Seeker.exe executable for users to implement manually.
3. Distributing an updated installer file.

This document provides a guide for adding updates using these three methods. If, after following the instructions below, you still require assistance with an update, you can contact Innova Support at **<support@innova-drilling.com>**.

## Using the WSX Auto-Update Feature

**Note that using this method to install an update will cause Well Seeker to close and restart. If the user is updating in the field, it is recommended to delay updating until there is a convenient break in operations.**

If Innova has made an update available for your organization, the next time you open Well Seeker X you should receive the below notification in the bottom right corner of the window:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmGxdsVYIwuLRrrM21GaP%2F0.png?alt=media)

Click on **OK** to close the notification, or click on **Install** to install the update. Well Seeker will download the update, then close and restart to implement it.

The update will also appear in the Notifications pane. This can be opened by clicking on the bell icon in the very bottom right corner of the Well Seeker X window.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuFMUP7oQ6WFdIwfHe8CL%2F1.png?alt=media)

If you missed the notification or chose not to install the update immediately, you can check for an update and download it at any time by following the below steps:

1. Backup your database by going to the **Home** ribbon and selecting **Backup**. Save your backup in a secure location.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPWzORaajJSug688J83tk%2F2.png?alt=media)

2. Go to the **Help** ribbon and click on **Check** in the Software Update section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFd7NgYts4YkZNasG9YKk%2F3.png?alt=media)

If your version of Well Seeker is up to date, you will receive the following message:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2WhJ9xzeHFKYMjeo2kjc%2F4.png?alt=media)

If an update is available, you will be given the option to download and install it. If you select **Yes**, Well Seeker will download the update, then close and restart to implement it.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbkyKROgjwcFyPga88gnI%2F5.png?alt=media)

3. After using the Check option, you can also download and/or install the update via the **Info** button.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDBzbhxgidlNTEgvQoFfQ%2F6.png?alt=media)

In the dialog that opens, you have three options:

a. Click on **OK** to close the dialog without downloading the update.

b. Click on **Download** to download the update to your PC. This allows you to manually apply the update at a later date. To do so, follow the instructions in the next chapter, **Manually Applying an Updated Well Seeker.exe**.

c. Click on **Download/Install**. Well Seeker will download the update, then close and restart to implement it.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcWozi7NSdr3NYTZh9cSz%2F7.png?alt=media)

4. Wait for Well Seeker to restart, then return to the **Help** ribbon and click on the **Info** button again. The dialog should display your new version number.

## Manually Applying an Updated Well Seeker.exe File

The auto-update feature described in the previous chapter downloads and applies an updated **Well Seeker.exe** executable file to the user’s PC. However, there are circumstances when this is not feasible. For example, you may wish to test an update before allowing Innova to distribute it to all users in your organization.

In these circumstances, Innova can send an updated **Well Seeker.exe** file directly, which you can then apply manually. To so, follow the below steps:

1. Double check whether you are using the 64-bit or 32-bit version of Well Seeker X. You can do this by going to the **Help** ribbon and clicking on **Info**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fml9mCXngCUrQDgcbpMJp%2F8.png?alt=media)

2. Backup your database by clicking the **Backup** button in the **Home** ribbon. Save your backup in a secure location. **Then close Well Seeker**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3yYDOcLQ2BujrDklE35z%2F9.png?alt=media)

3. Receive the updated **Well Seeker.exe** file from Innova. This will usually be provided as a zipped folder via email. Check that the version number in the name of the zip file matches the version you have installed. This is what you checked in Step 1. If the update is for a 64-bit version, the file name will contain **x64**. If it is for a 32-bit, the file name will contain **x86**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FI9QMiQczo0n4prf4MWBI%2F10.png?alt=media)

4. **Unzip** Well Seeker.exe from the zip file that you downloaded in the step above.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F184pVkaMzGPsjz2M4kz9%2F11.png?alt=media)

5. Copy and paste the unzipped **Well Seeker.exe** into your Well Seeker install directory, replacing the file that is already there. The default install directory address will depend on the version you are using:

* For the 64-bit version: **C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x64)**
* For the 32-bit version: **C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker X (x86)**

6. Re-open Well Seeker X, go back to the **Help** ribbon and click **Info**. This should display the new version number.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlUVFHY4W1U67IT0k22mo%2F12.png?alt=media)

## Updating using a WSX Installer

Occasionally, Innova may release a significant feature update for Well Seeker X, that requires the software to be uninstalled and then reinstalled with the new version. This section will guide the user through the steps required to do this..

**If you are using Well Seeker in the field, it is recommended that you wait until there is a convenient break in drilling operations before attempting to uninstall/reinstall Well Seeker.**

1. Double check whether you are using the 64-bit or 32-bit version of Well Seeker X. You can do this by going to the **Help** ribbon and clicking on **Info**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnpjSkeE0PGjlAUjQl7q5%2F13.png?alt=media)

2. Backup your database by clicking the **Backup** button in the **Home** ribbon. Save your backup in a secure location. Then **close Well Seeker**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnswBLvCTi9lOKoMeEwyH%2F14.png?alt=media)

3. Open the control panel and then open **Programs and Features**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzFa4bSv8yS8fhHKinb3h%2Fimage.png?alt=media&amp;token=9dc54f5c-d90e-423a-89d5-37e540b15e94" alt=""><figcaption></figcaption></figure>

4. Uninstall Well Seeker X.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fd3mf01vwOBAY64NiICBc%2F16.png?alt=media)

5. Download the zipped installer file. There are two ways to receive this file:

* We will send it to you directly, usually via email.
* If we have publicly released the new version, [**it will be available on our download page**](https://innova-drilling.com/download-2/). If downloading from this page, make sure to download the version that matches with the your version that you checked in Step 1.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNzT4IzQc20iEoN3t7aBk%2F17.png?alt=media)

6. Unzip the installer file from the zipped folder.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FD7DjoymWFN2MN0g5eW5c%2F18.png?alt=media)

7. Run the installer file to install the new version of Well Seeker X. Follow the instructions provided by the install wizard. For more information on the install process, view this page: [Well Seeker X: Installation Guide | Innova Drilling & Intervention](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-installation-guide)
8. Re-open Well Seeker X, go back to the **Help** ribbon and click **Info**. The version number should display the new version.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWbIF4QR0KTzvpckD9GYV%2F19.png?alt=media)

Some users may experience an issue where Well Seeker X initially launches, but then immediately shuts down after displaying the splash screen pictured below. If this happens, refer to the following [technical note](https://docs.innova-drilling.com/introduction/technical-notes/low-priority/well-seeker-pro-failure-to-open) to resolve the issue. If the issue persists after following the instructions in the technical note, contact <support@innova-drilling.com>

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWNJXEMz1NI5h8ZmL2U8h%2F20.png?alt=media)


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

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGGYAQslUnD8YuBgjMNpR%2F0.png?alt=media" alt="" width="533">

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fso4zUpsEDNPtolRjhJT7%2F1.png?alt=media" alt="" width="333"><figcaption></figcaption></figure>

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgsL0JRKrXYCQv2tguJ4z%2F2.png?alt=media" alt="" width="431">

Login using your username and password.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3IMH36xFkmdLIpXKWfVU%2F3.png?alt=media" alt="" width="362">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9yTzTDtRIXpn90V45jkd%2F4.png?alt=media" alt="" width="431">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAId0XYkaZb6V1SAaH19h%2F5.png?alt=media" alt="" width="563">

5. In the Admin ribbon, select **Rig Names.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZJmQzXW11IARFpKRjOni%2F6.png?alt=media" alt="" width="431">

6. 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. If Block Weight is changed it will update all wells using this rig.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fbu7JiXVGSRwskOoDP48k%2Fimage.png?alt=media&amp;token=6bc9b213-a551-4e08-818b-ef57936fed25" alt=""><figcaption></figcaption></figure>

7. Open the **Home** ribbon and select **Addresses.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuCqk5m2Vj4SJKX33NUZw%2F8.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FD5qNOdUc1uKvpolCNljb%2F9.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRO3FwE9t2l0iIZp3CwnB%2F10.png?alt=media)

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAx8SfC3loSJteG8kF4Jt%2Fimage.png?alt=media&amp;token=4cf46def-4e05-4502-b0c3-1b9bfd8bf698" alt=""><figcaption></figcaption></figure>

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

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5Tq7pfXXgfw8TB79IkIf%2F12.png?alt=media" alt="" width="431">

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxqQxAzgu0KdHHYfkaNcF%2Fimage.png?alt=media&amp;token=b1ad406d-c678-47c4-9333-e8584031c305" alt="" width="338"><figcaption></figcaption></figure>

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVnjLX2ZhKSzgmhSy6mu6%2F14.png?alt=media" alt="" width="380">

3. 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**](https://docs.innova-drilling.com/introduction/video-guides/how-to-videos/well-seeker-pro/daily-reporting/choosing-phase-and-activity-codes)

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fu0suasGpPHhx3DyahjnY%2Fimage.png?alt=media&amp;token=58aa44a9-7b46-40a9-86af-efb0a85b8992" alt=""><figcaption></figcaption></figure>

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWTSlXL0rsMWWC3hHAj0k%2F16.png?alt=media" alt="." width="383">

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

**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**](https://docs.innova-drilling.com/introduction/video-guides/how-to-videos/well-seeker-pro/daily-reporting/choosing-phase-and-activity-codes)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5EsydVAEAmKtCs1C6dOP%2F17.png?alt=media)

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

1. Review your **Compass import settings**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRY0lwRVMMhpnCVXpsqg4%2F18.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUOy8cW9Bk7fbwLrJgqMA%2F19.png?alt=media)

2. Select **Import Compass EDM file.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMJX1ZuW5hisXUxrfpbKv%2F20.png?alt=media)

3. 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](https://docs.innova-drilling.com/introduction/technical-notes/low-priority/edm-import-function-update)
4. 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.
5. Make sure that your principal well plan has been correctly designated. Right click on the well plan and select **Properties.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fabbdq2welbC7TFXvODEH%2Fimage.png?alt=media&amp;token=bf06be57-2995-40c9-b884-89124f60f450" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRmHUDHbWD6UXZYCtZ5Ai%2Fimage.png?alt=media&amp;token=e6b53b47-0ba2-4f85-ac7a-0d31a3d9536e" alt=""><figcaption></figcaption></figure>

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

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGKFjjZShB6Wu8UMUUIcK%2Fimage.png?alt=media&amp;token=a8673853-9fc6-4686-b647-b50071f9da97" alt="" width="462"><figcaption></figcaption></figure>

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5KMfYit0DRErADSl4TZo%2Fimage.png?alt=media&amp;token=6bfbcd0b-c654-4a52-963a-481a9c04992a" alt="" width="305"><figcaption></figcaption></figure>
3. Right click on the operator and select **Insert New Field.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtDcszU4fXSo9pD7qlPGk%2Fimage.png?alt=media&amp;token=64fdfb96-024e-4218-ab95-bc5bdce1749f" alt=""><figcaption></figcaption></figure>
4. 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**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPqZE1TVLbeR4EPLGzDQL%2Fimage.png?alt=media&amp;token=c8c14fbf-f798-4b12-8853-e2337d24b3c8" alt=""><figcaption></figcaption></figure>

5. Right click on the field and select **Insert New Facility.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVupjB4rbILNIg5MuD8nN%2Fimage.png?alt=media&amp;token=51208d69-a2ae-44ac-af6c-8e59f5d5d524" alt="" width="380"><figcaption></figcaption></figure>

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtbYCjgsjctwAXK2AJkJv%2Fimage.png?alt=media&amp;token=6896f0a6-8c21-4e26-ba4a-a3436ba3cd36" alt="" width="457"><figcaption></figcaption></figure>
7. Right click on the facility and select **Insert New Well.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FApzqedQUljIZBbR0y5Q3%2Fimage.png?alt=media&amp;token=f36cfcc9-7ed3-49fa-8cc9-1f89e253b8cb" alt="" width="449"><figcaption></figcaption></figure>
8. 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**.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8JGkRDteHpdd4ur0wDxY%2Fimage.png?alt=media&amp;token=eccbff36-6796-481c-8516-0d5e3d0d209d" alt="" width="379"><figcaption></figcaption></figure>
9. Right click on the well and select **Insert Planned Well.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5zpcZGDoCM8yBu6gi9B9%2Fimage.png?alt=media&amp;token=0b39effc-c7f2-445a-912c-e51810fb5e9a" alt=""><figcaption></figcaption></figure>

10. 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](https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/untitled-2) 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**.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvQTmg15j3Y9VYyqq8mD7%2Fimage.png?alt=media&amp;token=307cd2ab-78b9-4f2e-9dbd-95fd4bb2db87" alt=""><figcaption></figcaption></figure>
11. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvmTn4egqUETeDHSpcDRU%2Fimage.png?alt=media&amp;token=d0d656c2-1c0d-4ef5-857a-8e1f08186d71" alt=""><figcaption></figcaption></figure>
12. 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**.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzEaXZqUtJJeYpcMfVm4O%2Fimage.png?alt=media&amp;token=3cad00ff-6bd1-4bab-a499-27f6b593989a" alt="" width="511"><figcaption></figcaption></figure>

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

1. Right click at well level and select **Insert new actual well**.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0o3BrKZuMu28uSswIYmp%2Fimage.png?alt=media&amp;token=c18ec720-b962-4911-93b6-ff4f9aba3c63" alt="" width="437"><figcaption></figcaption></figure>
2. 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](https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/untitled-2) for tying your well onto its mother bore. After checking your inputs, click on **Apply** and then **Close**.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKEZWgPVmls4AYR9iN1TJ%2Fimage.png?alt=media&amp;token=5007c61c-26f6-4c30-b277-80078da6fa88" alt=""><figcaption></figcaption></figure>
3. Right click at actual well level and select **Insert new survey.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkuYNr2oM2Th2CApcQKXD%2Fimage.png?alt=media&amp;token=299abd4e-fc0d-4fee-9b1d-620ec7cb64c8" alt="" width="487"><figcaption></figcaption></figure>
4. Input and check **survey name, tie on details** and select **survey instrument/IPM**. After checking your inputs, click on **Apply** and then **Close**.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjXAABIRh3QP7aZ120w6T%2Fimage.png?alt=media&amp;token=112079ce-1e71-4245-af87-81c93365464c" alt="" width="422"><figcaption></figcaption></figure>
5. 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**.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUEvx6eRyV3bfszxIyFNc%2Fimage.png?alt=media&amp;token=52a590eb-394f-487a-814d-d11510d4e205" alt=""><figcaption></figcaption></figure>
6. Now click on the **Select Offsets** icon in the Home ribbo&#x6E;**.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdlY8N5ojoptgYw088JRD%2Fimage.png?alt=media&amp;token=d1ed13dc-32b3-4aad-8b58-6330f6040acb" alt=""><figcaption></figcaption></figure>
7. 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.

      <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsLyA4JX1VCxrVM60Y8yf%2Fimage.png?alt=media&amp;token=a348a187-b396-4f8f-b0b6-e269c1e5a689" alt=""><figcaption></figcaption></figure>
   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.

      <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6MDmWy7rebVhmlYVD2ew%2Fimage.png?alt=media&amp;token=15bd01c9-f259-4a00-988b-d2968ce10d59" alt="" width="324"><figcaption></figcaption></figure>
8. 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.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnicLgzxyE8oEGdATzY6Y%2Fimage.png?alt=media&amp;token=866ff5e3-71cc-44bc-961f-7c35b5a41ace" alt=""><figcaption></figcaption></figure>
9. 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.

      <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0BjENal9NcPLJsFzV0BW%2Fimage.png?alt=media&amp;token=572f0a88-b082-432f-a11e-143f2c2287b3" alt="" width="563"><figcaption></figcaption></figure>
10. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6J27fQDtWUfzjq7UHEkn%2Fimage.png?alt=media&amp;token=6d082f81-cd59-4327-8dde-6527241a6522" alt=""><figcaption></figcaption></figure>
11. 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.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrwlhSCmY6XzcrGqvPEsc%2Fimage.png?alt=media&amp;token=8cd9d6c9-42cd-42ad-b7d5-5c14eef9da49" alt=""><figcaption></figcaption></figure>

12. Click on the actual well in the object explorer, and then click on the **Daily Reports** button in the Home ribbon.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLoz7sE8W85xyf99ikBNK%2Fimage.png?alt=media&amp;token=152b8330-2f30-4cfd-8987-1bf3e86bdf12" alt="" width="472"><figcaption></figcaption></figure>
13. 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEQsBQKeDQogQJHmSv8Ic%2Fimage.png?alt=media&amp;token=b5a63e4d-34f9-433e-9a3f-ffff80ad98b8" alt="" width="342"><figcaption></figcaption></figure>

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.

14. Right click on the actual well and select **External Files**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlA9vCoM2pbslNfwNKObR%2Fimage.png?alt=media&amp;token=f531a9dc-c860-416f-80d6-f94d6dede8e9" alt="" width="335"><figcaption></figcaption></figure>

15. 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 BHA to the file if you wish using the drop down. Files can also be added by dragging and dropping the file in the dialog. The user can also rotate the files clicking on ‘Rotate’ button.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1EN9wYDKa1M6GwdLD2J8%2Fimage.png?alt=media&amp;token=209173ac-ddd5-48a3-aeeb-89a930510e44" alt=""><figcaption></figcaption></figure>

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

1. Open Well Seeker.
2. 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.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmTblFM42bzRJXUhhM73i%2Fimage.png?alt=media&amp;token=1785d938-01b9-452c-b9ce-cad7455da690" alt="" width="425"><figcaption></figcaption></figure>
3. You can confirm your currently selected database by checking the path displayed on the status bar at the bottom of your Well Seeker window.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYlxkx9r0eWlSpVDrhUr6%2Fimage.png?alt=media&amp;token=23907c17-579b-430f-8931-9b6e166cd0ae" alt="" width="563"><figcaption></figcaption></figure>
4. 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 sectio&#x6E;**.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyHmWIRVMQVoAAKE3j11H%2Fimage.png?alt=media&amp;token=18564616-8b2e-45f8-b579-a928f97df83c" alt="" width="454"><figcaption></figcaption></figure>
5. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3rXPBEPsydTCky4LVitK%2Fimage.png?alt=media&amp;token=a9b100f4-441e-45ac-9890-411bd6fd4410" alt="" width="461"><figcaption></figcaption></figure>
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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fmf7QRvH4Qpx0Ual9Ej5N%2Fimage.png?alt=media&amp;token=756ba78d-12ec-4253-a5dd-0127caf19d10" alt=""><figcaption></figcaption></figure>
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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPolD33TwCO1eHbcTkRWP%2Fimage.png?alt=media&amp;token=31705d3e-741f-49dd-bcad-667444f2b7c0" alt="" width="406"><figcaption></figcaption></figure>
8. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRewDJgDCmcVFQaFCo3dX%2Fimage.png?alt=media&amp;token=83552fd2-38dc-442b-9119-20ef4841bca4" alt="" width="563"><figcaption></figcaption></figure>
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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FS6Htgh2zQasV23ARbJJo%2Fimage.png?alt=media&amp;token=39207f44-09ff-49b9-af14-a20a78a3e835" alt="" width="418"><figcaption></figcaption></figure>
10. Right click on the well plan and select **Properties**. Check that all of the information is correct, and then click on **Close.**

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7vq0n5eY9iBvCQFVDiKH%2Fimage.png?alt=media&amp;token=733b925d-0c02-4b5a-aed0-c4bfc194535f" alt="" width="538"><figcaption></figcaption></figure>
11. Double Left click on the well plan to open it. Check that the well plan matches the well planning report.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fqsdfeq1gkLPBXuCmfVBh%2Fimage.png?alt=media&amp;token=628be48a-3235-402e-b466-34e5d46eef8b" alt=""><figcaption></figcaption></figure>
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.**<br>

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5smc72tnTq2L1GidbstC%2Fimage.png?alt=media&amp;token=11a5dfb6-f5b2-493d-8d45-b92b4ec199f7" alt=""><figcaption></figcaption></figure>
13. Click on the actual well in the object explorer, and then click on the **Inventory** button in the Home ribbon.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLzGRrv5g8QQyxzeTqIrc%2Fimage.png?alt=media&amp;token=5df9de0a-7ce1-4810-8d8a-dfbece73d262" alt="" width="528"><figcaption></figcaption></figure>
14. 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.<br>

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxiKZ897lPQB2x8m8nAGe%2Fimage.png?alt=media&amp;token=f3be1b85-9e5d-49f1-8989-ebafd0138eb0" alt=""><figcaption></figcaption></figure>
15. Click on the actual well in the object explorer, and then click on the **Drill String** button in the Home ribbon.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFo12HKvsqCriBltM48MT%2Fimage.png?alt=media&amp;token=642d2f13-13b2-437b-8860-afee3a76264a" alt="" width="563"><figcaption></figcaption></figure>
16. 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**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCh1EIA7V39ptwikFQzbC%2Fimage.png?alt=media&amp;token=0bddead5-af05-4439-a834-319e44db719e" alt=""><figcaption></figcaption></figure>

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

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKP8FZCfhtpp9rKdXxenQ%2Fimage.png?alt=media&amp;token=51f3ac1a-a001-4418-9442-ee024d3cdae4" alt="" width="557"><figcaption></figcaption></figure>
18. After inserting a component, fill in the necessary **Component Properties** on the right.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FohGsrxQjCLuZ4D6hgXtn%2Fimage.png?alt=media&amp;token=7196be0a-6e41-4e12-88be-36d7a5f07ec7" alt=""><figcaption></figcaption></figure>
19. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0LoH799SknWmqCTj8y8O%2Fimage.png?alt=media&amp;token=5d38d2eb-affb-4552-ae99-7e5dcab0b977" alt=""><figcaption></figcaption></figure>
20. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fpls6bYqJKHbJGELpOvdD%2Fimage.png?alt=media&amp;token=d55652f2-3e9b-4ab1-a8d9-5010cbbbf7a5" alt="" width="383"><figcaption></figcaption></figure>
21. 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.<br>

       <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlotPjBPCmAKlEoaIWpgI%2Fimage.png?alt=media&amp;token=20752eb3-93a3-46b5-8761-8c3110a4d131" alt=""><figcaption></figcaption></figure>
22. Click on the **Save** icon and then close the Drill String window.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fnh6zoz6zAZcNdtsIRSI7%2Fimage.png?alt=media&amp;token=481b9ea2-5596-44ff-897c-bd97875e1ecc" alt="" width="398"><figcaption></figcaption></figure>
23. Click on the actual well in the object explorer, and then click on the **Job Data** button in the Home ribbon.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjxfetlDPKheehJKBqw9P%2Fimage.png?alt=media&amp;token=006e1860-7179-49c7-a84c-0f3e30673424" alt="" width="563"><figcaption></figcaption></figure>
24. 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.<br>

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAaSwLzTqU1yIWzIqodrp%2Fimage.png?alt=media&amp;token=ccc91505-5169-4d73-9e2e-80f3ac055ebf" alt=""><figcaption></figcaption></figure>
25. Click on the actual well in the object explorer, and then click on the **Daily Reports** button in the Home ribbon.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F57zc48apyLCuOAOvWRx9%2Fimage.png?alt=media&amp;token=38cb59be-b904-447d-bfd8-3d14b4b55f49" alt="" width="563"><figcaption></figcaption></figure>

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

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FglLjDg5t4rNjv73GKa8R%2Fimage.png?alt=media&amp;token=279cea39-4435-4690-9ed3-4199c6fc07df" alt="" width="360"><figcaption></figcaption></figure>
27. Click on the **Personnel** icon in the home ribbon.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxAJEkYO7nLx5IN1x2psP%2Fimage.png?alt=media&amp;token=16d4cec6-6891-41e9-84ad-6cc47aff85f2" alt="" width="563"><figcaption></figcaption></figure>
28. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAbp0NsLefWnSrqdCcFM8%2Fimage.png?alt=media&amp;token=f7f97d9a-c709-4324-ab94-6bd4f8bb57c7" alt="" width="467"><figcaption></figcaption></figure>
29. 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.**

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F53wb2yETWMBo5t27W10M%2Fimage.png?alt=media&amp;token=d4603479-0a06-4ffc-a4b9-cdc89e9af450" alt=""><figcaption></figcaption></figure>
30. 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.**

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCCahiXicJ9p0lkIn9RGv%2Fimage.png?alt=media&amp;token=7f4cf378-3499-4865-a68d-bbaf18dcb4f5" alt=""><figcaption></figcaption></figure>
31. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fx8z7SGaqFKNHKtZyQwI3%2Fimage.png?alt=media&amp;token=cd8ea34b-6df4-4f72-b606-d3f646dbbf52" alt="" width="342"><figcaption></figcaption></figure>
32. 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtsRIneXOf8nkqAUiFcuS%2Fimage.png?alt=media&amp;token=ce5ccacd-ed5f-46cb-9a49-5e4529c3fecf" alt=""><figcaption></figcaption></figure>

### 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:

1. You must be using a license that is registered to your organization. For most users this will already be the case.
2. You must have an active internet connection.
3. 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:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsMclaIvXv8V7GiH5XFxY%2Fimage.png?alt=media&amp;token=f27dde8c-ae3a-4b24-9781-08c6ef914315" alt="" width="558"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUQ4yOD3DPn6s1m0sWEUU%2Fimage.png?alt=media&amp;token=4db81d0d-80ed-44bf-bd57-211c042a740a" alt="" width="475"><figcaption></figcaption></figure>

For a more detailed explanation of the Data Sync, see the following tech note: [Data Synchronization Feature Update | Innova Drilling & Intervention](https://docs.innova-drilling.com/introduction/technical-notes/well-seeker-pro-technical-notes/data-synchronization-feature-update)

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

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfcAhQfuDij7S6YBpevbA%2Fimage.png?alt=media&amp;token=94c7c287-ba11-4cd5-823d-8f67ce4c6261" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fo7l0iDS80xRtcmn9Oucf%2Fimage.png?alt=media&amp;token=e09a577b-476d-4f1f-b952-a66d36412966" alt=""><figcaption></figcaption></figure>

2. 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**.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSyUhDtDuiX9eCmjELcld%2Fimage.png?alt=media&amp;token=81556e63-b726-403e-9f70-b64b7f8d241c" alt=""><figcaption></figcaption></figure>
3. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fh76xnB0aSsXFeBuwCw2c%2Fimage.png?alt=media&amp;token=ed290be5-a387-4771-91ae-4872269a4197" alt="" width="563"><figcaption></figcaption></figure>
4. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0tSRmOfBhs9DtPlWXpEg%2Fimage.png?alt=media&amp;token=731fd188-79d4-41d9-b21c-4a5099039bf2" alt="" width="506"><figcaption></figcaption></figure>
5. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fwvq9AugNoLRpfOvNZeAv%2Fimage.png?alt=media&amp;token=6667b208-1898-4310-9bf4-38f6cc702c2b" alt="" width="552"><figcaption></figcaption></figure>
6. 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsW6eu2LHM6H730S53Kpq%2Fimage.png?alt=media&amp;token=480e3067-4048-4833-9ba4-854f354f94d7" alt="" width="348"><figcaption></figcaption></figure>

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

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0xfwKuj66Lgovdt1Zchn%2Fimage.png?alt=media&amp;token=0ebbe4bb-74ed-4ae8-ae1d-e972149346b1" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjOOizZmEhLax0sxIhyYC%2Fimage.png?alt=media&amp;token=fda46c9c-8c66-45aa-99f4-dc9e291a54e1" alt="" width="309"><figcaption></figcaption></figure>

2. 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 ribbo&#x6E;**.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7RxDtsvqEB6KPkdjHIP8%2Fimage.png?alt=media&amp;token=62555073-9da0-4871-b965-55e01f071faa" alt=""><figcaption></figcaption></figure>
3. In the slide sheet window, open the Serial/TCP WITS dialog by clicking on **Serial/TCP** in the WITS section of the Home ribbon.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FoeHwG8kimTLBUjnQbzzD%2Fimage.png?alt=media&amp;token=0c17dae2-98c0-4215-baf1-9929ff940f1e" alt=""><figcaption></figcaption></figure>
4. 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.

      <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnzhGr0d6NAD4uHhPfMEf%2Fimage.png?alt=media&amp;token=f8612233-e751-415b-852a-2dd6f5abff26" alt="" width="563"><figcaption></figcaption></figure>
5. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpG5yYNsTKT4MczWT7w8C%2Fimage.png?alt=media&amp;token=6c7f868d-4976-4219-ac83-c71f4e625d1f" alt="" width="533"><figcaption></figcaption></figure>
6. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnXCmaeBJOPFPvZGIkIzr%2Fimage.png?alt=media&amp;token=10bc4127-3cdd-4017-b171-e29ca8d1a8fe" alt="" width="563"><figcaption></figcaption></figure>
7. Minimize the WITS Comms window. Do **NOT** close it, as this will stop the incoming WITS data.
8. In the **Rig States** section of the ribbon, click on the **Settings** button to open the Rig States configuration dialog.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fapj1JAZA2Ek9NuW8cDk8%2Fimage.png?alt=media&amp;token=99df5be5-aebc-412f-a6c9-b3c26ef22248" alt=""><figcaption></figcaption></figure>
9. 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**](https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/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.<br>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGM3wERYvThOAuTQHdhzo%2Fimage.png?alt=media&amp;token=17d4b657-f47c-4032-b840-ba9e8933690f" alt=""><figcaption></figcaption></figure>

10. Minimize the Rig States window. Do **NOT** close it.
11. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6krksAVnGU9R8XZGnWeg%2Fimage.png?alt=media&amp;token=663a8936-c076-46e2-9e54-29cfdd1fb1d3" alt=""><figcaption></figcaption></figure>
12. 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.

1. 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.
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 displayed in the survey grid, they can be activated using the **Show/Hide** option in the **Settings** menu.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FarbEaV5N5becOBj2pBcX%2Fimage.png?alt=media&amp;token=e48c24c1-b024-4049-8eca-23ea893ccafd" alt=""><figcaption></figcaption></figure>
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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FiMA4YAqCxfY1a7cOx3NA%2Fimage.png?alt=media&amp;token=380f9e88-16f6-4e60-8029-5c66d243d1ad" alt="" width="506"><figcaption></figcaption></figure>
4. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwbRYjVnpB6MRn2lZlfze%2Fimage.png?alt=media&amp;token=2a4685c6-3c96-4080-8591-2db8c82a3ae4" alt=""><figcaption></figcaption></figure>
5. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYVYijusT7Q5XDjFFhJV0%2Fimage.png?alt=media&amp;token=5f6217d2-2583-4cfe-b9d8-426e12cb29b7" alt=""><figcaption></figcaption></figure>
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 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzvosW5hhTucMCG98uo0A%2Fimage.png?alt=media&amp;token=dd02da14-be51-45b6-a97b-8806d666a568" alt=""><figcaption></figcaption></figure>
7. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8dAMedhWkZQ6Q8GkiIlM%2Fimage.png?alt=media&amp;token=b7bdfc7b-810d-4913-b34a-ba98c46951e0" alt=""><figcaption></figcaption></figure>
8. 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRJvl5MIZ457NjPVp7k0J%2Fimage.png?alt=media&amp;token=ca3df676-95f3-421c-a113-328d62c47fa4" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYo5kJccr8j5oMR0VPq1R%2Fimage.png?alt=media&amp;token=7ef6b54f-b57b-4f6e-85c9-0f88a0bdd0a3" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVWtyfMCXBaQi5Fx8acTu%2Fimage.png?alt=media&amp;token=3476d338-3735-4abe-a21f-fc864faa0b8b" alt="" width="307"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQOOsE15e0L9Mml9pcjBv%2Fimage.png?alt=media&amp;token=96d0137e-0d26-41e2-a5c4-36a890483018" alt=""><figcaption></figcaption></figure>

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

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAwSIe21JjwWKyPy078Hf%2Fimage.png?alt=media&amp;token=c21aebea-f089-4fc2-91dc-a1a96aead547" alt="" width="562"><figcaption></figcaption></figure>
11. 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkKDjV74izdgJuuiPnxja%2Fimage.png?alt=media&amp;token=b630bcad-d05f-4c0d-903c-bec38a9ab031" alt="" width="465"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTdWNsZPXeZAsdWBK0Nii%2Fimage.png?alt=media&amp;token=2668bd86-a51d-4964-b860-a100cf801fff" alt="" width="401"><figcaption></figcaption></figure>

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.

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOYAUvzeyVhpRXr1S0np8%2Fimage.png?alt=media&amp;token=87de3648-fc96-4823-a9b8-0e826b7ac5bd" alt="" width="462"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhGggZcrKSh8jAz7uydBv%2Fimage.png?alt=media&amp;token=a6b8fde7-5f05-4450-947c-ac0065edfce8" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhCpYX0X06SjX5ESxku7N%2Fimage.png?alt=media&amp;token=ac5cd099-4282-40ff-900e-52d7f3ff9241" alt="" width="449"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMus2tsRW1OwQXJhUlW8n%2Fimage.png?alt=media&amp;token=e4a93f4f-70fe-4e42-aeb0-2e633b97d4d9" alt=""><figcaption></figcaption></figure>

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

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHdHdDN4RjIEVs1R7z12N%2Fimage.png?alt=media&amp;token=95add5f3-c252-466b-97e6-090bd4c34583" alt="" width="308"><figcaption></figcaption></figure>

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

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FArHAUnRObXZMs02TwazQ%2Fimage.png?alt=media&amp;token=30db63a3-3a12-42db-83b4-0c0087c6d8cf" alt="" width="440"><figcaption></figcaption></figure>

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

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEiO7gNmWy6wJszLhSqIw%2Fimage.png?alt=media&amp;token=6ef7a7f8-2d63-4eaa-851c-3d359053cd29" alt=""><figcaption></figcaption></figure>
16. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRBawZyjnE1WRs7cUp3EL%2Fimage.png?alt=media&amp;token=dfbf19de-0cea-4c97-96e0-e0c4598d4820" alt=""><figcaption></figcaption></figure>
17. Click on **Apply** and then close the Drilling Data dialog.
18. If MWD was present in the string, click on the **MWD** icon in the **Run Data** section of the ribbon.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLkGBOFSPW4l0ZOjLaQFz%2Fimage.png?alt=media&amp;token=6fb86fd8-474c-4039-babe-c3e7ea849b4c" alt=""><figcaption></figcaption></figure>
19. 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.<br>

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwgT1am3O1Az0Ydu2DV4o%2Fimage.png?alt=media&amp;token=c6d9bdee-28b0-470c-9283-5d3bdb254642" alt=""><figcaption></figcaption></figure>
20. **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 BH&#x41;**,** you can **Save** and then close the Drill String Editor.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHuMu7yxlmf2W0C6XYIHh%2Fimage.png?alt=media&amp;token=5efd81f9-0cd6-46cb-822d-23baf530e84d" alt=""><figcaption></figcaption></figure>

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

1. Open your internet browser and navigate to one of the below websites based on your servers geographic location:
   1. USA: <https://vantage.innova-drilling.com/>
   2. Europe: <https://vantageeu.innova-drilling.com/>
   3. UAE: <https://vantageuae.innova-drilling.com/>
2. Log in with your username and password.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Frq5M4IRysG0Dk93lhiTo%2Fimage.png?alt=media&amp;token=d12d23ad-4d0f-4229-bd51-2da5c6ec21ae" alt=""><figcaption></figcaption></figure>
3. 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.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ffz57fhCqwDvwPlpcbyR9%2Fimage.png?alt=media&amp;token=6de02139-7d52-4e41-a6d5-72c510ff1b76" alt=""><figcaption></figcaption></figure>
4. 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.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQoabUXdtiKRffTuZH4IT%2Fimage.png?alt=media&amp;token=f209eb85-219b-48d4-a58d-86181a6f9fca" alt=""><figcaption></figcaption></figure>

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

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMpdKdkLBMXKuv2C4Sycn%2Fimage.png?alt=media&amp;token=cba96672-4a29-4d96-b6cd-2da65c30c184" alt=""><figcaption></figcaption></figure>

Click on the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXxufm1YhgKEtp9LVh6de%2Fimage.png?alt=media&amp;token=8fd3552f-3069-4894-9184-e0ff4f8f4e8a" alt="" data-size="line"> icon beside a day to print the report for that day, or click on the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FaD5g3M1Gp9UcqUMVlt5g%2Fimage.png?alt=media&amp;token=f46ae346-5c34-47d1-9a2d-6bf7ea2b8f14" alt="" data-size="line"> icon in the bottom right to print all days in one report.

6. The **Surveys** page allows you to view the currently recorded surveys for the well. User can select to display only the grid, only the 3D chart or both. When both are selected, user can opt to split vertically or horizontally.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxoJTTyRvygcZkC7g7pDz%2Fimage.png?alt=media&amp;token=c27f91be-34c0-40d8-9cad-c07572fbe8c6" alt=""><figcaption></figcaption></figure>
7. On the Surveys page, click on the **Real Time AC** tab to the right of the survey grid or **RT AC** option in the top menu to display the real time anti-collision results for the well. This will automatically update every time data is pushed from the rig site.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7pFOfEURANwfHkc65en0%2Fimage.png?alt=media&amp;token=d2016e38-83aa-4b41-aa5a-562761bbcdc2" alt=""><figcaption></figcaption></figure>
8. 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 <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fb1A0W9wmVEERpenZQoic%2Fimage.png?alt=media&amp;token=50f62c5f-7ba8-4623-a9b2-7a9848244dbe" alt="" data-size="line"> icon beside a BHA to print a BHA or performance report.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJcVKd1xcRvGOWciEVUsk%2Fimage.png?alt=media&amp;token=3766b36a-13b3-44f1-a376-df2c7681b750" alt=""><figcaption></figcaption></figure>
9. 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.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFnpr8qkc1Vi80nVepj0m%2Fimage.png?alt=media&amp;token=0ec179f2-098c-4c6e-a5a0-7d0ab97eb344" alt=""><figcaption></figcaption></figure>

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](https://docs.innova-drilling.com/introduction/app-and-portal-guides/web-portal-data-acquisition-and-edr-guide)

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

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fw7ypohspjzHYzAUb1iFd%2Fimage.png?alt=media&amp;token=08223c98-f74c-40a4-8cd0-1100d367d411" alt=""><figcaption></figcaption></figure>

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

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fedc6o2RRsWxFoHfx7jn5%2Fimage.png?alt=media&amp;token=5cef71bb-7aab-4bdd-8792-5d248703c1ef" alt="" width="563"><figcaption></figcaption></figure>
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.<br>

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIk4Vm9Gxw8WESYXRUUIr%2Fimage.png?alt=media&amp;token=1385eb09-db0e-4c47-a8dc-34e273b69588" alt=""><figcaption></figcaption></figure>
4. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F95bUcigeVwjkIH3XaT6J%2Fimage.png?alt=media&amp;token=e3657a14-0ed1-487c-9099-7a6c4fc8d66b" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FggsFkmMUgHvMzNTsqy77%2Fimage.png?alt=media&amp;token=21b52567-4f49-4428-b1ed-1e9894fabf61" alt=""><figcaption></figcaption></figure>

5. Click on the actual well or below in the object explorer, and then click on the **Shipping Ticket** button in the Home ribbon.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdVwa76FN7qQugQCnJC2U%2Fimage.png?alt=media&amp;token=cc91946e-ed4c-4757-94c3-04baa27bdd91" alt="" width="519"><figcaption></figcaption></figure>
6. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFxXMIsbWEfO88hgykKGi%2Fimage.png?alt=media&amp;token=280d9b58-2e16-4a2f-ba3d-21ff1fe88f3c" alt="" width="355"><figcaption></figcaption></figure>
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 **Select Ready for Backload** button.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwcM4gY1Ig0P9HfQ8qRqI%2Fimage.png?alt=media&amp;token=42e5d2ea-a130-4146-8bcf-1aaa2c417b34" alt="" width="389"><figcaption></figcaption></figure>
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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F11HN82ZGlF2xYlwKNYd6%2Fimage.png?alt=media&amp;token=e120ad51-3266-45a4-8c0c-89ad32752fb3" alt="" width="561"><figcaption></figcaption></figure>
9. 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**](https://docs.innova-drilling.com/introduction/video-guides/how-to-videos/well-seeker-pro/daily-reporting/daily-reporting-qa-and-qc) 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.
10. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfLVPprY42LQmALCJp8b6%2Fimage.png?alt=media&amp;token=5ea62ac9-e96f-4158-ab96-9b5ff55b765c" alt="" width="475"><figcaption></figcaption></figure>

Check for the following:

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtNX0MDE2mhRJBz7U2p1l%2Fimage.png?alt=media&amp;token=db0d4d76-75d4-4091-abfd-d9c447eff8c6" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdKK4tP6xqrXSJLB7lmGz%2Fimage.png?alt=media&amp;token=58d76da5-df63-49a9-84c9-e0551f749c96" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FW6jD2i7kqjxThqIlpVUI%2Fimage.png?alt=media&amp;token=ca6e7aef-b116-40cd-af23-50aa36572514" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRfpngBu5oYOzBk2ZZYqM%2Fimage.png?alt=media&amp;token=f970bb1b-ef6a-4224-8ab7-0411460c9260" alt=""><figcaption></figcaption></figure>

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

11. 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 ribbo&#x6E;**.**

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgprJCWAy179XQVCw0KBK%2Fimage.png?alt=media&amp;token=15613116-fbec-43a8-b1e2-7232b6a149c8" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZQcD3XKnWvBsqIlGsRwC%2Fimage.png?alt=media&amp;token=c3a49e58-fc1c-4091-81b1-23b5a2ccbc8d" alt=""><figcaption></figcaption></figure>

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

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FW8k9w1VQF7LiTtyfBzcN%2Fimage.png?alt=media&amp;token=36565e81-20ca-4957-91eb-627464b7e24d" alt="" width="563"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKykBwuwrgFdRVESsawA7%2Fimage.png?alt=media&amp;token=10063bfc-f066-46e3-b6bd-2560634393ca" alt="" width="440"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRhbQiV1TYe3JOOPbdTJc%2Fimage.png?alt=media&amp;token=0cf2e8c8-2c11-4444-a58c-045023323d84" alt=""><figcaption></figcaption></figure>

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

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FT40jQ6l1MOInGOq30TEK%2Fimage.png?alt=media&amp;token=42db78e1-7ff6-4581-86a5-268d93e402d7" alt=""><figcaption></figcaption></figure>
14. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FETNL3GTlYOURF58eCkvH%2Fimage.png?alt=media&amp;token=823c6a13-1569-4879-bc9b-0584651bc0eb" alt=""><figcaption></figcaption></figure>
15. 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**.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWkUxJYUG3QBIVDY0VcWM%2Fimage.png?alt=media&amp;token=871f9ab9-2f27-4aae-915d-0d600a4be0d1" alt="" width="407"><figcaption></figcaption></figure>
16. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Flmambqdi22g7X5LkV0jl%2Fimage.png?alt=media&amp;token=263b7f9b-3888-4fd6-84e1-f7259d8ed80e" alt="" width="368"><figcaption></figcaption></figure>
17. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fw2QkYh1h52g3EBeAx5R9%2Fimage.png?alt=media&amp;token=99ce9986-bc87-4c38-be7e-24d0928b3736" alt="" width="490"><figcaption></figcaption></figure>
18. 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.

    <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqQqY30dsPDS3qlVoKJmK%2Fimage.png?alt=media&amp;token=ede31225-b7e7-4aa6-bfef-fcf2c135122f" alt="" width="494"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgdCAY0H2estpk3kh89yX%2Fimage.png?alt=media&amp;token=0480cb03-d1df-4848-96cb-f14b52119490" alt="" width="563"><figcaption></figcaption></figure>

## 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**](https://docs.innova-drilling.com/introduction/video-guides/how-to-videos/well-seeker-pro/daily-reporting/daily-reporting-qa-and-qc) on quality control for the reporting data.

1. Verify that the bottom line of the actual wellbore matches with the well plan, and that the actual well survey program is complete.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyoPBkn1boAWMORi4jznz%2Fimage.png?alt=media&amp;token=12b2e82b-a206-4170-acce-ee081aab1e54" alt=""><figcaption></figcaption></figure>
2. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkyqbS84DEPWvYYEZzqoq%2Fimage.png?alt=media&amp;token=82cfb996-f25a-49c8-8284-054cf921d9e1" alt="" width="475"><figcaption></figcaption></figure>

Check for the following:

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdaatIoCPq4dMX3hW4kt6%2Fimage.png?alt=media&amp;token=3cebb643-3fff-4036-9eca-b9b548550d2f" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlFZCrtKgUmMmH2AKQkll%2Fimage.png?alt=media&amp;token=899f8784-5d4e-4bbf-ade0-59756502114b" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBNStr7WPSvl1r0EH6twA%2Fimage.png?alt=media&amp;token=e364041c-0e90-4d0a-8a61-66eda54db806" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqM60cSc4jKBiaEzMCTio%2Fimage.png?alt=media&amp;token=1ba580a1-8f74-4510-92f6-eb41902d0ca9" alt=""><figcaption></figcaption></figure>

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

3. 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 ribbo&#x6E;**.**

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2KpnbETY1CkZ8KkBxVVz%2Fimage.png?alt=media&amp;token=b5e19ac8-d5ab-4b7b-9d8e-f0d670d70370" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWk2qOiygpkgSOT74K48R%2Fimage.png?alt=media&amp;token=44a35a53-ea47-4e8c-a300-cfcb98e4ce83" alt=""><figcaption></figcaption></figure>

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcS9JFRDOgguuNhLcLyz3%2Fimage.png?alt=media&amp;token=a6bd30d5-11a5-4d03-9cb7-9c3468444759" alt="" width="563"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhCbyJ20MkSkdwdx1AlGr%2Fimage.png?alt=media&amp;token=edf7453c-92df-487e-b1ba-92d6ed744bec" alt="" width="440"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHXoCQeX3SZKzb12boxBO%2Fimage.png?alt=media&amp;token=715ce7c7-983f-4786-b124-6fc8bc6e3208" alt=""><figcaption></figcaption></figure>

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

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYnWNcM4V9ejfn1rhmq38%2Fimage.png?alt=media&amp;token=0f25d8e9-67ce-479a-8dbb-26f58334139d" alt=""><figcaption></figcaption></figure>
6. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHT3cuKN4Q680OgcTcjl2%2Fimage.png?alt=media&amp;token=0a749db1-5897-4ca0-aed3-82cdaf3e635a" alt=""><figcaption></figcaption></figure>
7. 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.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2eUtISlbam6DZDqHp7Zb%2Fimage.png?alt=media&amp;token=8bb6b9a4-11be-4e30-8c66-7d87f9ea6291" alt=""><figcaption></figcaption></figure>


# Well Seeker X: Sidetrack Guide

## 1.0 – Introduction

The purpose of this document is to help guide the user through the steps required to create a sidetrack.

Depending on the requirements, it is possible to create 3 different types of sidetrack within Well Seeker:

1. A plan which sidetracks another plan
2. A plan which sidetracks a survey
3. A survey which sidetracks another survey

NOTE: It is not possible to create a survey which sidetracks a plan.

The steps required to create the sidetrack are the same, regardless of which of the above 3 options are required.

This document will detail the steps required to create a sidetrack under 2 different conditions:

1. When the sidetrack and the motherbore both have the same depth reference
2. When the sidetrack and the motherbore have different depth references

## 2.0 - Setup

In order to create a sidetrack, the user must first enter a well which will act as the motherbore. The motherbore can be either a plan or a survey. For the purposes of this guide, it will be assumed that the motherbore has already been created in Well Seeker.

### 2.1 – Depth Reference

Any well plan or survey which is entered in Well Seeker requires a depth reference to be assigned to it. In most cases this will consist of:

* A Ground Level Elevation above a System - Usually MSL
* A Datum above a System – Usually RTE or RKB above Mean Sea Level

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFGwMGQFHV8LOiWK2QaiW%2F0.png?alt=media)

When planning a sidetrack, it is important to know what the depth reference of the motherbore is and what the depth reference of the sidetrack is. There are 2 possible situations which the user may encounter.

The first situation is where the depth reference for the motherbore and sidetrack are the same. As the ground level is unlikely to change, the variable in most cases is the RTE above ground level, so this situation is usually experienced when the sidetrack is drilled with the same rig.

The second situation is where the depth reference for the motherbore and sidetrack are different. This is usually experienced when the sidetrack is drilled with a different rig, where the RTE above ground level is different when compared to the motherbore.

The following two sections detail the steps required to deal with these two situations.

## 3.0 –Sidetrack & Motherbore with the same depth reference

This section will cover the creation of a sidetrack using the same depth reference as the motherbore.

### 3.1 - Automatic method

#### 3.1.1 - Planned Sidetrack

To create a tie on plan, right-click in the Database Tree on an actual well or plan and select ‘Tie on plan’ from the context menu.

**Note:** The 'Tie on plan’ option is only available when right-clicking on an **Actual Well** level or **Plan** level in the Database Tree.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCeSQSLhsHX8q6ECiXRZy%2Fimage.png?alt=media&amp;token=1244431a-9555-4f1c-9e5c-452c5e1e9462" alt="" width="255"><figcaption></figcaption></figure>

A ‘Create tie on plan’ dialog will appear, prompting the user to fill in the following fields:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfM9YXvKwe4k6g462d5DA%2Fimage.png?alt=media&amp;token=5dbc05ca-0d5c-4a9f-aac6-fbe1d01e849f" alt="" width="174"><figcaption></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.

&#x20;

Firstly, the user needs to open the well properties and ensure that the Motherbore Depth Reference is checked as **Default**. In this situation it is likely that other than the Default datum on line 1, the motherbore depth reference will be the only other option. Once selected, hit **Apply** and then **Close**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0X57jOS3uRvezhedCqF1%2Fimage.png?alt=media&amp;token=1d187ae9-9912-4f7a-9846-b4cffad1f2a8" alt="" width="563"><figcaption></figcaption></figure>

#### 3.1.2 - Actual Wellbore Sidetrack

To create a sidetrack well, right-click in the Database Tree on an actual well and select ‘Create Sidetrack’ from the context menu.

**Note:** The 'Create Sidetrack' option is only available when right-clicking on an **Actual Well** level in the Database Tree.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhyNrgKwOgLLMa88dak1W%2Fimage.png?alt=media&amp;token=44984413-fac3-4533-a1c2-910480fb4d12" alt="" width="260"><figcaption></figcaption></figure>

A ‘Create Sidetrack’ dialog will appear, prompting the user to fill in the following fields:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlpARPwlVWs7ZCTfQ68Sw%2Fimage.png?alt=media&amp;token=f6ffa67a-8946-4e58-8fcf-04bc371a483c" alt="" width="176"><figcaption></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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8knzF1w3ZEtdNtaVZXiM%2Fimage.png?alt=media&amp;token=748e082f-3ec7-47db-b3b4-9b83327413de" alt="" width="553"><figcaption></figcaption></figure>

### 3.2 - Manual Method

Firstly, the user needs to open the well properties and ensure that the Motherbore Depth Reference is checked as **Default**. In this situation it is likely that other than the Default datum on line 1, the motherbore depth reference will be the only other option. Once selected, hit **Apply** and then **Close**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fzb3C1Q51aknjdnZpT17W%2Fimage.png?alt=media&amp;token=b9c035a2-52f5-4368-9702-d3dc9fc468e5" alt="" width="563"><figcaption></figcaption></figure>

In the Database Tree, right-click on the well containing the motherbore and select one of the following options:

* **Insert new actual well** if the sidetrack is a survey.
* **Insert planned well** if the sidetrack is a plan.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fuv20TOSwQizBXfZ6gxaK%2F2.png?alt=media" alt="" width="322">

The **Plan Properties/Actual Wellbore Properties** dialog will appear. Fill in the Properties, Vertical Section and Magnetics Sections as normal

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpSFv5tbufuvKHlkafR7u%2F3.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIfVjyxSWHXCTBaPwds4a%2F4.png?alt=media)

If the motherbore depth reference was correctly selected as default, then this should be referenced in the **Depth Reference** section. If it was not correctly selected as default, something else will be referenced here and the user will need to select the correct reference from the drop down menu.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FksyBILNIBonoklQYMVAK%2F5.png?alt=media)

If the user needs to do this, a warning box will appear. Choose the option **Preserve TVD’s**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrIQ1keIi9Cfyc4aSlbrU%2F6.png?alt=media)

In the **Sidetrack Details** section, check the “**Plan is tied to”** or **“Well is a sidetrack”** checkbox, depending on if you are creating a plan or survey.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4JJz8cjlHP4Ms2Mg6me4%2F7.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7OE8b0wlovr28fajol4i%2F8.png?alt=media)

Select the mother bore from the **Parent Well/Plan** drop-down box and enter the sidetrack depth in the **Sidetrack Depth** box. Note that the depth must be within the range of the motherbore i.e. a motherbore with a TD of 1000m MD can’t be sidetracked at 1010m MD etc. Then click on the **Create Tie-on / ST** box.

As soon as create sidetrack has been selected, the below warning will appear. This is warning that proceeding will reset the survey program in the plan or actual wellbore properties. This is not an issue as this section will currently be blank anyway. Select **Yes.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhRx2pU2aqRruzUNN6obb%2F9.png?alt=media" alt="" width="371"><figcaption></figcaption></figure>

The **Survey Program** and **Tie-On** sections will automatically update based on the sidetrack depth entered. The survey program will now mirror the survey program of the motherbore down to the sidetrack point, and the tie-on section will automatically show the details of the tie-on line. Click on **Apply** and then **Close** to close the **Plan Properties/Actual Wellbore Properties**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6ZX0jFA8SqA0hmBNVMEg%2F10.png?alt=media" alt="" width="563">

At this stage the process differs, depending on whether the user is creating a planned or actual sidetrack.

#### 3.2.1 – Planned Sidetrack <a href="#id-3.1_-_planned" id="id-3.1_-_planned"></a>

When the sidetrack is a plan, all the user needs to do is open the plan by double right clicking on the plan level. This will open the plan and the tie-on line in row 1 will mirror the sidetrack depth entered in the plan properties dialog.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4svCpYUHHAm5lwFfn5vi%2F11.png?alt=media)

The user can now build their sidetrack plan as per their planning requirements.

#### 3.2.2 – Actual Wellbore Sidetrack <a href="#id-3.2_-_actual" id="id-3.2_-_actual"></a>

When the sidetrack is an actual wellbore, the first thing the user needs to do after selecting the ST depth and closing the Actual Wellbore properties (Section 3.0) is to create a new survey. The actual wellbore will already contain the motherbore surveys from surface to the ST depth, but in order to enter the ST surveys, the user must first create a new survey.

To do this the user should right click on the actual wellbore and select **Insert New Survey**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQmTSxXKQKOmzD8bTYKRs%2F12.png?alt=media" alt="" width="323">

In the survey Properties Dialog, select **From Survey** in the tie-on section and from the drop-down section, select the survey that you want to sidetrack. Note that when the appropriate survey has been selected the MD cell will be populated with the deepest survey station for the selected survey. If required, the user can then manually overwrite this value with the appropriate ST depth.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fp31mG2RqzRrsumiDuxaC%2F13.png?alt=media" alt="" width="509">

The user can then select the appropriate Survey Instrument from the drop-down menu and select **Apply** and then **Close**.

The user can now double right click on the newly created survey. This will open the survey and the tie-on line in row 1 will mirror the tie-on depth entered in the survey properties dialog.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYGxVjh62XnVeCfPqV4PF%2F14.png?alt=media)

The user can now enter the appropriate surveys as they are received.

## 4.0 –Sidetrack & Motherbore with different depth references

This section will cover the creation of a sidetrack which has a different depth reference to the mother bore. This can happen, for example, when a well has been previously drilled with one rig and then sidetracked with a different rig.

In the Database Tree, right-click on the well containing the motherbore. Select **Properties** to open the **Well Properties** dialog.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FI0iyvaL6zufdkyYB7Sms%2F15.png?alt=media" alt="" width="322">

In the **Depth Reference** section, create a new depth reference in the line below the motherbore reference. Give your depth reference a name in the **Datum Name** column. In the **Elev above system** column, enter the depth reference height of the sidetrack. Enter the name of the rig used to drill the sidetrack (if available) in the **Rig** column. Enter the ground level elevation in the **Ground Elevation to MSL** box. At this stage it is important to check that the **Air Gap** has been calculated correctly. If this value is not correct, then an error has been made entering the data and this needs to be addressed.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3X7MECxQ7cvd4rEhQ8SC%2F16.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fc98CxckJYNPgPFbijGE1%2F17.png?alt=media)

In the above you can see that the RTE above ground level for Rig 2 is 5m greater than Rig 1. Once the user is happy the new elevation has been entered correctly it is **important to then select the new ST datum as the Default**. Selecting the new ST datum as default at this stage will save a lot of unnecessary steps during the rest of the process which can lead to mistakes being made, so this is an important selection to make. Click on **Apply** and then **Close** to close the Well Properties dialog.

In the Database Tree, right-click on the well containing the motherbore and select one of the following options:

* **Insert new actual well** if the sidetrack is a survey. Note, you can only sidetrack an existing survey with this option. If the motherbore is a plan, then this can only be sidetracked by another plan.
* **Insert planned well** if the sidetrack is a plan.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPhZ8CuQGSnL3F1HFbHjZ%2F18.png?alt=media" alt="" width="320">

The **Plan Properties/Actual Wellbore Properties** dialog will appear. Fill in the Properties, Vertical Section and Magnetics Sections as normal. Check to make sure the depth reference is correct. If the new ST datum was selected as **default** in the Well Properties dialog, then this should be correct.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fmgj4vtNpkmr6kEMmM40j%2F19.png?alt=media" alt="" width="563">

In the **Sidetrack Details** section, check the **Plan (or well) is a sidetrack** checkbox.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3N2R2GefSjz9whpLYRBr%2F20.png?alt=media)

Select the motherbore from the **Parent Well/Plan** drop-down box. This is now the point where the user should select the appropriate sidetrack depth. The sidetrack depth entered in the cell will be referenced to the Depth Datum selected in the plan properties dialog, which may differ from the motherbore. In the situation where the datum selected is different from the motherbore, the user needs to be very careful at this point to ensure they enter the correct depth.

Referencing the below diagram, if the user needs to sidetrack the motherbore at 1000m MD, then they should enter the sidetrack depth as 1005m MD.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F515R6tTC3fa1CHbRiznm%2Fimage.png?alt=media&amp;token=1f8a1537-3576-40eb-b0f6-9fbcabb89047" alt=""><figcaption></figcaption></figure>

Note that the depth must be within the range of the motherbore i.e. a motherbore with a TD of 1000m MD can’t be sidetracked at 1010m MD etc. Then click on the **Create sidetrack** box.

As soon as create sidetrack has been selected, the below warning will appear. This is warning that proceeding will reset the survey program in the plan or actual wellbore properties. This is not an issue as this section will currently be blank anyway. Select **Yes.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFvD01LEc4D2y0pf8fxbq%2Fimage.png?alt=media&amp;token=7a29f3dc-7fcf-41e6-b0cd-61a1a9c969b2" alt=""><figcaption></figcaption></figure>

The **Survey Program** and **Tie-On** sections will automatically update based on the sidetrack depth entered. The survey program will now mirror the survey program of the motherbore down to the sidetrack point, and the tie-on section will show the details of the tie-on line. Click on **Apply** and then **Close** to close the **Plan Properties/Actual Wellbore Properties**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQnJUIFj7HqZ9OafasHd6%2Fimage.png?alt=media&amp;token=2a643bf1-4be2-4a1e-a8c8-0e78aa5d7947" alt=""><figcaption></figcaption></figure>

At this stage the process differs, depending on whether the user is creating a planned or actual sidetrack. For instruction regarding this process, refer to Section **3.1 – Planned Sidetrack** and **3.2 – Actual Wellbore Sidetrack**.

### 4.1 – Checking the ST point is correct

As soon as the user has setup a planned or actual sidetrack the first thing they should do is check that the sidetrack point has been chosen correctly. One way to double check this is to compare the ST tie-on line with the interpolated sidetrack point on the motherbore.

In the below screenshot, the motherbore plan is on the left and the interpolate window shows the interpolated sidetrack point on the motherbore at 1000m MD. To the right is the sidetrack tie-on line. When the RTE between the motherbore and ST are different, it is expected that the MD and TVD will be different when comparing these, but if the inclination, azimuth, NS, EW and TVDss are the same, then the ST depth has been chosen correctly. If these values do not tie in, then the user should double check the sidetrack depth selected and adjust appropriately.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FV96ziG28RBOrEe6F1BC6%2Fimage.png?alt=media&amp;token=e8e4b59f-83fc-4a72-a158-defcb7319878" alt=""><figcaption></figcaption></figure>


# Plan v Actual Wall Plot Guide

## Introduction <a href="#toc200031170" id="toc200031170"></a>

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 <a href="#toc200031171" id="toc200031171"></a>

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:

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7fYQFzbPgd7JUApFhdR0%2F0.png?alt=media)

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

<div><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrDFRBtYtq3CLGb7SdzaZ%2F1.png?alt=media" alt="" width="195"> <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCPg48zZGLd0FVYDAPKF2%2F2.png?alt=media" alt="" width="211"></div>

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3nrwY7Zq5HKOJhBy5ZSW%2F3.png?alt=media" alt="" width="563">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHRD0ZBKSwFv9gAqZD60w%2F4.png?alt=media" alt="" width="563">

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:

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAhQeIBmoiGYi2c9me3HW%2F5.png?alt=media" alt="" width="563">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYBUmrWk9vMnXxWVyrCJU%2F6.png?alt=media" alt="" width="563">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjdGpmkD5EeLCL2GgJDt5%2F7.png?alt=media" alt="" width="563">

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

<div><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4dMNKtovHLBlo5FawxmN%2F8.png?alt=media" alt="" width="177"> <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpfPyhWM2YdopqnbhJUBW%2F9.png?alt=media" alt="" width="140"> <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCA8AHV7puQaZkPuiyCfo%2F10.png?alt=media" alt="" width="126"></div>

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjspKOGsdst3PzvS52Zp4%2F11.png?alt=media" alt="" width="563">

## Operations – Innova Portal <a href="#toc200031172" id="toc200031172"></a>

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:

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeZZJ0YnOtjVCyidxsTM8%2F12.png?alt=media" alt="" width="374">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXbYRMtykNb2vky3DoxlG%2F13.png?alt=media)

3. Click on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLcXCxHoa9DeVcK6fuljE%2F14.png?alt=media) 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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQejimiLvOVz3SHv8jSjw%2F15.png?alt=media)

4. 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 <a href="#toc200031173" id="toc200031173"></a>

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:

1. Open a survey or actual wellbore.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fv2Zcf6NmNmMYbKT6HiV6%2F16.png?alt=media" alt="" width="535">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtfXBbZcTH2uBjCaw5UR8%2F17.png?alt=media)

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:

1. Open a survey or actual wellbore.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmBFNIODF8WbdU0UaI2L7%2F18.png?alt=media" alt="" width="535">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FllU3n6g9RMBC9NUTgbLX%2F19.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ffa9UZR9oQi0G266khsw6%2F20.png?alt=media)

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTHpYXHAzuilYzNFmN018%2Fimage.png?alt=media&amp;token=9bfa85f7-534c-40e7-a825-3d6629d5d5cc" alt="" width="315"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9BYACP8cCpa3U7PtbR4A%2Fimage.png?alt=media&amp;token=1cc7cab8-2de3-4bab-81dd-2f62896a4a7e" alt=""><figcaption></figcaption></figure>


# Well Seeker X: MWD Reporting Guide

## Introduction <a href="#toc200369366" id="toc200369366"></a>

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 <a href="#toc200369367" id="toc200369367"></a>

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:**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyT9OBablgzBBp1AVi4Iu%2F0.png?alt=media)

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 <a href="#toc200369368" id="toc200369368"></a>

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:

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhNbHT00iiZCbcdFCSW9e%2F1.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXboEWkMNghR7OU6udAEe%2F2.png?alt=media)

3. Enter the probes owned by your organisation into the catalog.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYHTzL6oKjmHKOxu5afCB%2F3.png?alt=media)

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F58fHSAanLzTdlywVTW7r%2Fimage.png?alt=media&amp;token=5e33f083-bd54-4e3d-b84c-92709718182d" alt="" width="205"><figcaption></figcaption></figure>

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

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGCSDSb6tgMj5sYgMdEWV%2F5.png?alt=media)

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqgJ1whiyDILzyQWNM69o%2F6.png?alt=media" alt="" width="223">

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

### MWD Probe Templates <a href="#toc200369369" id="toc200369369"></a>

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.

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F07pPSk0JuZbxBV5QNhh1%2Fimage.png?alt=media&amp;token=719d802f-6037-44da-beed-78970e0611f3" alt=""><figcaption></figcaption></figure>

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZdZY7RnrVdIJpDujOrkc%2F8.png?alt=media" alt="" width="563">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8rlYgRvMTopf56MvePlg%2F9.png?alt=media)

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ff9z0VI6XB1VuGaj0AQrb%2F10.png?alt=media" alt="" width="563">

## Field Pre-Run Steps <a href="#toc200369370" id="toc200369370"></a>

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:

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMtkleog0EYzMKcRfaDGO%2F11.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FccSh2ixVOwE2yRocyr2d%2F12.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSFVXBQh87GX9d2D80dPC%2F13.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0cIxEK9uW6HlK3Ho4xGY%2F14.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQfpr8dgOd4r6iPIX6hGa%2F15.png?alt=media)

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FstTIW3ZLnvoddAQO6Vki%2F16.png?alt=media" alt="" width="363">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FltDcBoTwjuFFwsNmsYMB%2F17.png?alt=media" alt="" width="563">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2x6BCuSUONyR3wZhlks3%2F18.png?alt=media" alt="" width="362">

8. In the **BHA** section, fill in additional details for the probe string. Fields highlighted in <mark style="color:green;background-color:green;">**green**</mark> are editable.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAfdkdl0YqDzoGxvYG5EX%2F19.png?alt=media" alt="" width="392">

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

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJYiPQIDJnF1RwvaKKIJ2%2F20.png?alt=media)

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fhv7jnJbbtp5Vlhnz1GaL%2Fimage.png?alt=media&amp;token=3b55bff6-23dd-4fea-84f2-c265b5369764" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOyjhi6pZYcM4G517FSPd%2Fimage.png?alt=media&amp;token=5be7c7e1-5a82-4f5b-a367-283b418a3954" alt="" width="543"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmYVJeqgZKAz5BmRpdUzD%2Fimage.png?alt=media&amp;token=c4df95f4-f885-4963-9d76-51454e645755" alt="" width="345"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcoICyr2MQZa7EyKPfCcG%2Fimage.png?alt=media&amp;token=19dc6247-876a-4f32-bbf9-648bef237190" alt="" width="303"><figcaption></figcaption></figure>

## Field Steps During Drilling <a href="#toc200369371" id="toc200369371"></a>

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

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCwCeEgylZBIOGG6Hwaoz%2Fimage.png?alt=media&amp;token=2269fcd5-f1e3-4e95-b68b-d0fd28dfdcec" alt="" width="563"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5xK43ZQrxBMWNe1TjoNE%2Fimage.png?alt=media&amp;token=d0614a31-591b-44f8-a675-5dfc75d0f55f" alt="" width="487"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeMT3QPB9Jls8UdEtHQzZ%2Fimage.png?alt=media&amp;token=6080b38e-34e9-4b3c-bba2-e3418329a37a" alt=""><figcaption></figcaption></figure>

## Field End of Run Steps <a href="#toc200369372" id="toc200369372"></a>

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

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fs9Q7regC7ZG8aAKX0EVw%2Fimage.png?alt=media&amp;token=73530e9e-bef4-4ce2-8f59-9b063d1dcca4" alt="" width="488"><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fx6qJKTe9qqpyN0OkWf65%2Fimage.png?alt=media&amp;token=434500a7-58d9-4f23-80fe-39e2083bad79" alt=""><figcaption></figcaption></figure>

3. Enter any relevant comments in the **Run Summary** section.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzJVQnYKHkBemaxobYFFy%2Fimage.png?alt=media&amp;token=864ae65c-3003-432d-ac51-bb6d12da8a95" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCJwy8iMjTwoJe1nCUaMB%2Fimage.png?alt=media&amp;token=509f19d6-8e15-47a7-acaa-69989b5fbee2" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fx9IKIngcDkLaKyiLQDZf%2Fimage.png?alt=media&amp;token=a9ad6940-0919-4031-b020-75bc6f4a6686" alt="" width="244"><figcaption></figcaption></figure>

## Calculators <a href="#toc200369373" id="toc200369373"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlyiGY16HyqYcH8kQbsKA%2Fimage.png?alt=media&amp;token=948fc0c5-e5e7-49a9-a023-7a7264b078a9" alt="" width="498"><figcaption></figcaption></figure>

### Non-Magnetic Spacing Calculator <a href="#toc200369374" id="toc200369374"></a>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKdGZPiP7Swfd2WZrb3HT%2Fimage.png?alt=media&amp;token=b7a4d219-6563-45f5-acad-0f0a2a2faf39" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6aopiigUCK3NroDZEglp%2Fimage.png?alt=media&amp;token=88b6968a-db0d-4681-87fb-df043ea92733" alt="" width="434"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxfM5mKW0bW65jPPyMTyR%2Fimage.png?alt=media&amp;token=e759e6e3-6e8f-4a61-ac65-320506faaf8b" alt="" width="128"><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfT8tSzuKGdgMYKfKUMjo%2Fimage.png?alt=media&amp;token=147ffc95-9dab-4af7-bf0d-13759dcaa9a8" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSHhjPNgQdeGtsKFxFxXs%2Fimage.png?alt=media&amp;token=df37806e-d06a-45f9-ae67-27daf773f665" alt="" width="342"><figcaption></figcaption></figure>

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

### Pressure Drop Calculator <a href="#toc200369375" id="toc200369375"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYCsRMzkP8SClPs7rlBNN%2Fimage.png?alt=media&amp;token=c2708d34-e50d-41b6-bedc-29cd4dbfcf91" alt=""><figcaption></figcaption></figure>

**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 <a href="#toc200369376" id="toc200369376"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fx4pdb6FXl8WNJRyYecRk%2Fimage.png?alt=media&amp;token=1c97843f-7fe3-41c3-99ab-11f4481523e8" alt="" width="283"><figcaption></figcaption></figure>

The BHA for this example would look something like this:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrCOXARg1CWktDcixDQgk%2Fimage.png?alt=media&amp;token=cb7eb265-4650-4008-8897-9f744dc7c438" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fyi0xtsMEfRndtdkZHiAm%2Fimage.png?alt=media&amp;token=08d3658e-ddea-40e6-902c-537d47e5f8df" alt=""><figcaption></figcaption></figure>

The above equation has the following assumptions:

1. The **UBHO Pin to SS** measurement assumes that the lower end/helix probe is sitting on the set screw with no overlap.
2. 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIXWZO3bL8Jm8RbajJXD6%2Fimage.png?alt=media&amp;token=be41bb32-eac2-4ce3-9274-bddfb34db41d" alt=""><figcaption></figcaption></figure>

## Appendix B: Insertion Gear Calculation <a href="#toc200369377" id="toc200369377"></a>

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:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKIpgx8B1o7qyQwTDAf9n%2Fimage.png?alt=media&amp;token=becd60f0-29e5-454b-a746-27125e30bd74" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuXmBY2xcUHWqmgrfiNBR%2Fimage.png?alt=media&amp;token=35c63c58-68e6-4fdc-9a14-0a40ac2010b0" alt=""><figcaption></figcaption></figure>

## Appendix C: Sensor Offset in Top Mounted Configuration <a href="#toc200369378" id="toc200369378"></a>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfDfB4PZ3P1Zq63OSJo50%2Fimage.png?alt=media&amp;token=7c3bde45-d558-405a-aaa9-d144dfcc6d94" alt="" width="365"><figcaption></figcaption></figure>

The BHA for this example would look something like this:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fcn2xRjSR2BI7rQnsoo5W%2Fimage.png?alt=media&amp;token=e303abf6-f480-4d89-9e1e-18344000618b" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUfQFBJ4SmxFO1mdrddde%2Fimage.png?alt=media&amp;token=dc23e9a1-3ed4-4690-b6f9-61d3ee210529" alt=""><figcaption></figcaption></figure>

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:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeLOWGVH29b4uZxFW2NQp%2Fimage.png?alt=media&amp;token=4e06a429-23fd-41ce-afed-b25b5665b022" alt=""><figcaption></figcaption></figure>


# Well Seeker X: Data Sync Diagnostic Guide

## Introduction <a href="#toc209617693" id="toc209617693"></a>

A new diagnostic tool has been added to Well Seeker X in version 3.0.3.0 and later to assist admin users in identifying and resolving data synchronization and real time data exchange issues. This guide will introduce the Data Sync Diagnostic feature, describe how it works, and explain how it can help determine the cause of failed data sync attempts.

## Problem <a href="#toc209617694" id="toc209617694"></a>

The Data Synchronization and Real Time Data Exchange features perform the critical function of communicating between the organization’s server database and rig site computers. Occasionally, these features can fail due to configuration errors, missing information, data conflicts or connectivity issue.

Troubleshooting issues with the data sync or real time data exchange can be difficult if the user is not familiar with all of the requirements for a successful data sync or exchange.

## Solution <a href="#toc209617695" id="toc209617695"></a>

Innova have introduced the Data Sync Diagnostic tool to Well Seeker, to help the user quickly identify the cause of data sync and real time data exchange transmission issues. Additionally, relevant parts of the Data Sync Diagnostic tool have been integrated into the Real Time Data Exchange dialog.

### Data Sync Diagnostic Dialog <a href="#toc209617696" id="toc209617696"></a>

The Data Sync Diagnostic dialog can be accessed via the database tree. Right click on an actual well to access the context menu and select **Data Sync Diagnostic**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSQ4ZjJiLWvye5h7djK5n%2F2.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnpgBHQbnMuY6E1XbhNBd%2F3.png?alt=media)

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:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeXIsz1jytRBbNLykCsaB%2F4.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZCI1vuJIFDO9tFFQLffw%2F5.png?alt=media)

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

### Integration with Real Time Data Exchange Dialog <a href="#toc209617697" id="toc209617697"></a>

For extra convenience, the diagnostic information that is relevant to the Real Time Data Exchange has been integrated into the RTDE dialog. It can be viewed in the bottom right corner of the dialog.

!\[A screenshot of a computer

AI-generated content may be incorrect.]\(/files/G4nK2x1taifAPADmH0TX) !\[A screenshot of a computer

AI-generated content may be incorrect.]\(/files/AgfrMOeiboUXny8fhWbh)

For an explanation of the checks available in the Real Time Data Exchange dialog, see the section above.


# Well Seeker X: Reporting an Issue

## Introduction

Occasionally you may encounter an issue on **Well Seeker X** or **Vantage** that requires support from Innova in order to resolve. This guide explains the correct steps to follow, and the information required when reporting an issue.

### First Point of Contact

* **Field Engineers** – Your first point of contact should always be your **Coordinator**.
* If the Coordinator cannot resolve the issue, they will escalate it to **Innova Support**.
* If a Coordinator is not available, you can contact Innova Support directly by emailing: [**support@innova-drilling.com**](mailto:support@innova-drilling.com)

## Information to Include

When reporting an issue, it is essential to provide as much detail as possible. The more context you give, the quicker the support team can understand, investigate, and resolve the problem.

Please include the following where possible:

* What well are you working in?
* What task were you performing when the problem occurred?
* Which windows, tabs, charts, or dialogs were open at the time?
* Did any error messages appear? If so, what did they say?
* How long has the issue been happening?
* Does the issue occur consistently or intermittently?
* Screenshots of the issue or error message (where possible)

### Debugging File

For issues related to **Well Seeker X (WSX)**, many problems are caused by setup or database configuration. To speed up investigation, please include the **debugging file** when reporting your issue.

A debugging file is a **.zip** file that contains:

* A copy of your database
* A copy of your setup file
* Additional system information

There are two ways to generate and send the debugging file:

#### **Email Debug (Recommended)**

1. In Well Seeker, go to the Help menu.
2. Select Email Debug.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLS7eeZVYNtZfWfhvXc8u%2Fimage.png?alt=media&amp;token=2143e8d2-96b1-454f-9a21-1356c811b9d5" alt="" width="563"><figcaption></figcaption></figure>

3. If Outlook is your default email client, this will automatically create an email with the debugging file attached.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9VwQWzxe4egkbnlq5JuR%2Fimage.png?alt=media&amp;token=8e5d54d3-4431-42c4-8d0f-3c1d70ad2080" alt="" width="563"><figcaption></figcaption></figure>

#### **Create Debug (Manual Option)**

1. In the Help menu, select Create Debug.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FURv3jYLasHbqXFNlFD3c%2Fimage.png?alt=media&amp;token=716210b6-b7fe-4e58-bbf5-67e7ff1a0e30" alt="" width="547"><figcaption></figcaption></figure>

2. This saves the debugging file to your PC.
3. To attach manually:

   1. Select Open Debug to open the folder where the file is stored.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fw6jeEoz2cVGC2clmRjiA%2Fimage.png?alt=media&amp;token=6aa85f02-6e57-483e-9680-a696951c194d" alt="" width="472"><figcaption></figcaption></figure>

   b. Attach the file to your email to support.

### Screen Recorder Tool

Sometimes it is easier to demonstrate an issue with a short video rather than typing out a detailed description. WSX includes a built-in Screen Recorder tool, available from the Help menu.

* Use this tool to record what happens before, during, and after the issue occurs.
* If you are using WSX version 3.0.2.8 or later, the recorder will also capture audio along with the screen recording.
* Make sure all relevant Well Seeker windows are on your main screen (the recorder cannot capture external monitors).

To use the screen capture feature, follow the steps bellow:

1. Go to the **Help** ribbon, and in the Screen Capture section, click **Start**.\
   A red rectangle will appear around the capture area and a time counter will show how long the recording has been running in the status bar.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVKkVTqls4m1dxpgyfHQ6%2Fimage.png?alt=media&amp;token=cd258d9e-d744-4ed2-a7f8-29d02701bf0c" alt=""><figcaption></figcaption></figure>
2. Reproduce the issue you are experiencing.
3. When finished, go back to the **Help** ribbon and click **Stop** in the Screen Capture section.
4. Still in the Screen Capture section, click **Open**. This will take you to your Debug folder.
5. In the folder, you should see a video file called screenCapture.mp4. Play the file to confirm it recorded correctly.
6. Attach the screenCapture.mp4 file to your email to support.

## Summary

* Contact your Coordinator first – escalate to Innova Support if required.
* Always include detailed information about the issue.
* Provide screenshots whenever possible.
* For WSX issues, include the debugging file with your report.
* Use the Screen Recorder tool when possible for clearer issue reporting.

By following these steps, you will help Innova Support diagnose and resolve issues more quickly and effectively.


# Well Seeker X: WITS Setup Guide

## 1.0 - Introduction

The following document provides details regarding the WITS setup and functionality within Well Seeker X.

## 2.0 - WITS Types

WITS is a standardised format by which wellsite information is transferred e.g. bit depth, hole depth, rpm average etc.

At the rig site, WITS data is collected by the EDR (Electronic Drilling Recorder) system connected to the rig, which is usually provided by a company like PASON / TOTCO /NORALIS etc. Well Seeker X has three methods of retrieving this data:

* **Serial:** WITS data from the rig is transferred to the DD laptop via a serial cable.
* **UDP/TCP**: WITS data is transferred via an ethernet cable from the rig.
* **WITSML and MQTT WITS**: Data from the rig is uploaded to a central server, that Well Seeker X can access via an internet connection.

### 2.1 - Serial WITS

Serial WITS uses a serial cable to transfer the data from the EDR to WSX. 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFdarE9YX1DDYao31ygF7%2Fimage.png?alt=media&amp;token=4da8cc78-7d98-470a-9b55-a27d9c36a93a" alt=""><figcaption></figcaption></figure>

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 uses an ethernet cable to transfer data between the EDR and the laptop operating WSX. Note that some modern laptops do not have an ethernet port and will require an ethernet-to-USB adaptor. In Well Seeker X the user can set up UDP or TCP WITS using the **Serial / TCP WITS Comms** dialog.

**UDP WITS** requires the user to enter the port number that the data is being transmitted on. **TCP WITS** requires the user to enter the port number and the IP address of the computer outputting the EDR data.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGkWUHCkHvtZ1fSVHFGQG%2Fimage.png?alt=media&amp;token=faa6c944-33a3-427f-9983-1026d7523f45" alt=""><figcaption></figcaption></figure>

### 2.3 - WITSML/MQTT WITS

Instead of transferring WITS data from the EDR using a physical cable, the rig uploads the data to a server. Using the correct login credentials, the Well Seeker X user can retrieve the data via an internet connection.

**WITSML:** The user enters the URL of the data server, along with login credentials provided to them by the EDR data provider. Once connected, they can select the relevant well and data stream to start receiving WITS data to their computer.

**MQTT:** MQTT WITS is similar to WITSML but is tailored to two specific providers: Digidrill and KLX Wireless WITS. If using one of these providers, the user enters the URL and login credentials like normal. Once they are connected, they automatically receive the WITS data stream for their well.

## 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 X. Follow the below workflow to fully utilize the WITS features in Well Seeker X:

1. Use **WITS Mapping** to match the WITS Mnemonics with the incoming data.
2. If you want to receive surveys over WITS, configure the **WITS Survey Options** and the **Survey Update Email Template**.
3. Configure the drilling parameter thresholds in the **Rig States Settings**. **Note:** This dialog must be left open.
4. Set up the **WITS Data Reader** and start receiving data. **Note:** This dialog must be left open.
5. Activate **Live Rig States** to begin automatically populating the slide sheet using the incoming WITS data.

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.

| <ul><li>WOB</li></ul>            | <ul><li>STANDPIPE PRESSURE</li></ul> |
| -------------------------------- | ------------------------------------ |
| <ul><li>RPM</li></ul>            | <ul><li>MAGNETIC TF</li></ul>        |
| <ul><li>TOTAL GPM</li></ul>      | <ul><li>GRAVITY TF</li></ul>         |
| <ul><li>BIT DEPTH</li></ul>      | <ul><li>SURVEY MD</li></ul>          |
| <ul><li>HOLE DEPTH</li></ul>     | <ul><li>SURVEY INC</li></ul>         |
| <ul><li>HOOKLOAD</li></ul>       | <ul><li>SURVEY AZI</li></ul>         |
| <ul><li>Block Position</li></ul> | <ul><li>Torque (Optional)</li></ul>  |
| <ul><li>ROP (Optional)</li></ul> |                                      |

### 3.1 - WITS Mapping

Before using serial, UDP or TCP WITS, you should configure the WITS Mapping. This step is not necessary if you are using WITSML or MQTT WITS. The WITS Mapping dialog is accessed via the main interface. Open it by clicking on the **WITS** icon in the **Settings ribbon**or by searching in the search bar at the top right of the screen.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/vcEhJTkWUTpkUPonQmEh/Unknown%20image" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/JtZFfNLZmfX1K34TYlZ9/Unknown%20image" alt="" width="375"><figcaption></figcaption></figure>

1. The table contains each of the **Mnemonic** used in Well Seeker X and the corresponding channel **Record** and **Field ID**. The default Record and Field ID values come from WITS zero standard.
2. Configure the Record and Field ID for each Mnemonic so that they match with the Record and Field that is being output by the rig EDR system (e.g. PASON or TOTCO):
   1. For example, the EDR system is outputting the bit measured depth on **record ID 01**, **field ID 08**. We must have the WITS mapping set to the same for **bitMD** mnemonic.
   2. **Note** that EDR systems often output 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 if required.
   3. **Hookload MAX** is what is used when populating the PU/SO/ROT weights in the slide sheet.
   4. There is no standard mapping for RAW survey values **BX** **BY** **BZ**, so this is something which will need to be double checked.
3. Editing the last row in the table will cause a blank row to be created at the bottom, allowing the user to add more mnemonics if they wish. Click on the Mnemonic cell to choose from the available options in the dropdown menu.
4. Once the user is happy with the setup, hit Apply and then Close.

### 3.2 - WITS Survey Options

If you intend to receive surveys via WITS, you should configure your WITS survey options. These are accessed via the Slide Sheet.

Open a survey, and then click on **Slide Sheet**in the **Home**ribbon. The WITS Surveys section is located at the right hand end of the menu ribbon.

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

Configure the options per your requirements:

**Check for Surveys:** If you wish to receive surveys via WITS, this option must be checked. When selected Well Seeker will display any WITS Surveys which are received. When unselected, WITS surveys will be ignored.

**Inc/Azi** or **6 Axis:** Toggle between these options depending on the format of survey that you are receiving. If the WITS feed is sending surveys with the raw accelerometer and magnetometer values, select **6 Axis**. If it is sending calculated inclination and azimuth value, select **Inc/Azi**.

**QC Limits:** Only relevant if **6 Axis**is selected. Set the acceptable amount of tolerance for the dip, magnetic field strength and gravity field strength calculated from the raw survey data.

**Bit depth as Svy Depth:** If a new WITS survey is detected this option forces the survey depth to be set as the current bit depth.

**Auto Accept:** If this option is unchecked, the user will receive a message whenever a survey is transmitted. The message will allow the user to review the incoming survey and then either accept or reject it.

If this option is checked, 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.

**Auto Send Email:** If this option is checked, whenever a survey is accepted WSX will automatically send a survey update email. The survey update email and the intended recipients can be configured in the Survey Update Email Template dialog.

### 3.3 - Survey Update Email Template

The Survey Update Email Template dialog is accessed by clicking on the **Survey Email** option in the **Tools** section of the menu ribbon.

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

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/JC2TGvc0ZDKDFNx2SSAo/Unknown%20image" alt="" width="375">

Add recipients to the mailing list by entering their email address (e.g., **<email1@email.com>**) to the box at the top of the window and then clicking on the **add** button. Multiple addresses can be added at the same time by delimiting them with a comma (e.g., **<email1@email.com>,<email2@email.com>**). Remove addresses by selecting them in the list and clicking on the **delete** button. Well Seeker X will save all emails entered into the recipient list after the window is closed.

The email subject and body are automatically generated from information in the Survey, Slide Sheet and Daily Reporting dialogs, and cannot be edited.

A curve projection can be added to the email body by checking the **include** checkbox in the **Curve Projection** section. This requires a principal plan to be assigned to the well. Well Seeker X will automatically find the landing point on the plan and then estimate the landing TVD, inclination and azimuth based on the current trend in the Survey and Slide Sheet.

A projection to bit can be added to the email body by checking the **include** checkbox in the **Bit Projection** section. This can only be used if the deepest MD in the slide sheet is deeper than the deepest MD in the survey listing. You can enter the motor yield of any unseen sliding in the **Motor Yield** box. The motor yield and toolface of any unseen rotation can be entered into the **Rot**and **Rot TF**boxes, respectively.

### 3.4 - Rig States Settings

The Rig States Settings dialog is accessed by clicking on the **Settings** option in the **Rig States** section of the menu ribbon.

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

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/TMyEz1WgVrOWL8zxA6Zh/Unknown%20image" alt="" width="563">

The Rig States dialog is where the user can view the incoming WITS data from the **WITS Data Reader**, translated into readable values for the drilling parameters. It is also where the user configures the drilling parameter thresholds for real time state detection. The software uses these thresholds to deduce the current operation on the rig, allowing it to automatically record drilling and sliding activity.

1. When the WITS Data Reader is running, the incoming data will be displayed in the **Current WITS Data**and **Drilling Params**sections. Additionally, if toolface data is being received, this information will appear in the **Sliding TF**section.
2. Set your drilling parameter thresholds in the **Thresholds**section, as well as the RPM Buffer Size and RPM Buffer Threshold.
3. After entering your thresholds, you can optionally toggle **Auto Thresholds** on. If you set Auto Thresholds to YES, the thresholds will be locked and the software will dynamically adjust the RPM and Hookload thresholds as more data is received, to better deduce sliding and rotating activity. If set to NO, the thresholds need to be set manually.
4. You can also set the **Stall Pressure**. This is used for detecting and logging motor stalls. Logged stalls can be viewed by clicking on the **Motor Stalls** button in the menu ribbon.
5. The Rig States dialog uses the following logic to determine what is currently happening in the well e.g. Rotating, Sliding, Tripping, Circulating etc:
   1. **Is the Bit on Bottom?**&#x20;
      1. Is (Bit MD – Hole MD) < On bottom threshold
   2. **If on bottom, are you drilling?**&#x20;
      1. Pump Pressure > Threshold&#x20;
      2. WOB > Threshold&#x20;
      3. Hookload > Threshold&#x20;
      4. On bottom recorded when all 3 of the above are recorded = TRUE
   3. **If Drilling = TRUE, the logic is as follows**&#x20;
   4. The user sets the RPM Threshold, RPM Buffer Size and RPM Buffer Threshold.&#x20;
   5. The software stores the number of RPM values entered in the \[RPM Buffer Size] input, in the RPM Buffer.&#x20;
   6. If at least \[RPM Buffer Threshold] number of values are larger than the \[RPM Threshold] then the rig state is Rotating.&#x20;
   7. If not, then the rig state is Sliding.&#x20;
   8. For example if the RPM Buffer size is set to 10 and the RPM Buffer Threshold is set 7 and the RPM Threshold is set to 60, the buffer will store the last 10 RPM values received. If 7 or more of these values are 60 or above, then the rig states is rotating, otherwise the rig states does not see the pipe as rotating.
6. As an alternative to using the RPM Threshold, RPM Buffer Size and RPM Buffer Threshold, the user can toggle ON Advanced Slide Detect. In this mode, instead of inspecting the RPM, the software inspects the incoming torque values. If the torque values are oscillating in a sinusoidal pattern, the string is recognised as Sliding. If not, Rotating.
7. With the thresholds set up and the WITS Data Reader running, the **Current Rig State** section will now populate.
8. **NOTE:** If you want to use WITS data to automatically populate the Slide Sheet, you need to **Minimize** the Rig States dialog instead of closing it.

### 3.5 - WITS Data Reader

In order to receive WITS data, the WITS data reader needs to be running.

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

Well Seeker X has three WITS data readers, which are located in the **WITS** section of the menu ribbon in the **Slide Sheet** window. The data reader that you should use depends on the connection type:

* **Serial or Ethernet Cable:** Use the Serial/TCP WITS reader.
* **WITSML:** Use the WITSML reader.
* **Digidrill or KLX Wireless WITS:** Use MQTT WITS.

#### 3.5.1 - Serial / TCP WITS Comms

The Serial/TCP WITS Comms dialog is used to receive data via a serial or ethernet cable.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/ZgcDNFPiaUpmY7aXfyuz/Unknown%20image" alt="" width="563">

1. Set up the connection in either the **Serial WITS Settings** or **Ethernet WITS Settings** sections:
   1. If you are receiving data via a **Serial** cable, make sure that the cable is connected and then select the **Comm Port** from the dropdown box in the **Serial WITS Settings** section. Leave the **Baud Rate** as 9600 unless specified by the WITS provider.
   2. If you are receiving data via an **Ethernet** cable, select either **UDP WITS** or **TCP WITS** in the **Ethernet WITS Settings** section. Enter the IP address provided by the WITS provider in the **IP** box. If you are using TCP WITS, you will also need a **Port** number. You may also need to toggle on **Client Mode** – try toggling this on if you have issues receiving the data after you start reading.
2. The are some additional options in the **Options** section that are only relevant to specific WITS transmission systems:
   1. **Send Data Handshake (Pason):** Toggle this OFF if you are running a Noralis MWD system and receiving data from a Noralis WITS system. Otherwise toggle this ON.
   2. **Use SoloBox Mapping:** Toggle this on if you are receiving data from a SoloBox system. It will override the settings that you entered into the Serial WITS Settings or Ethernet WITS Settings sections.
   3. **Use RigSense Mapping:** Toggle this on if you are receiving data from a RigSense system. It will override the settings that you entered into the Serial WITS Settings or Ethernet WITS Settings sections.
3. Click on **Start Reading** in the bottom left. Whilst the WITS feed is running, you can see incoming data and any error messages in the **WITS Data Stream** section. Pause the data stream by checking the **Pause Messages** checkbox – the WITS feed will continue in the background. This allows the user to scroll through and read any messages. Once unchecked, all messages which were received during the paused interval will appear. The **Stop Reading** button will stop the WITS feed. Whilst the WITS feed is running, the status can be seen in the **WITS Status** section.
4. It is also possible to send data back to the server. In the **Server Data Sync** section , the **IP** and **Port** cells should be greyed out and not editable, and should already be filled with your company’s 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.
5. The **WITS Out** section allows you to transmit the WITS data that you are receiving to other computers at the rig site via a null serial cable. Toggle **Send WITS Out** to activate the feature. Choose the mnemonics that you want to send by checking the **Send** checkbox and entering a channel value beside each one. Note that this feature is only available to select when a serial cable has been connected to the computer and a Comm Port has been selected in the Serial Wits Settings section.
6. **Minimize** the WITS Comms window. Do **NOT** close it, as this will stop the incoming WITS data.

#### 3.5.2 - WITSML Comms

The WITSML Comms dialog is used to receive data by accessing a WITSML Server via an internet connection. To use the WITSML reader, the user needs valid login credentials for a WITSML server, provided by the server host.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/DI4OMoHEX5Ob5bZBYGiF/Unknown%20image" alt="" width="563">

1. Fill in the **Server URL**, **Username** and **Password** boxes in the **WITSML Server** section using the information provided by the server host. You also need to know the version of the server – either **1.3.1**or **1.4.1** – and select it from the dropdown box. You can check your credentials by clicking the **Test Connection** button. A message will display in the Messages section indicating if the connection was successful or not.
2. Click on the **Load Wells** button to get a list of wells and logs stored on the server. Select the desired log and trajectory by clicking on them in the list. **Note** that Well Seeker uses time-based logs for its paramater data, and trajectory logs for surveys.
3. Map the WITSML mnemonics to the Well Seeker mnemonics in the **Curve Mapping** section. There is no industry standard set of WITSML mnemonics, so you must set them manually. The Well Seeker internal mnemonics are listed on the right, with a column for the WITSML mnemonics on the left. Well Seeker will attempt to automatically match mnemonics that have the same name. The user should set the WITSML mnemonic by clicking on a row and selecting from the dropdown box.
4. Click on the **Start Reading** button. The **Selected Data** section will update to display the selected well, wellbore, log, and trajectory. Whilst the WITS feed is running, the user will see values in the **Value** column in the **Curve Mapping** section. They will also receive status and error messages in the **Messages** section. Pause the data stream by using **Pause Messages** button – the WITS feed will continue in the background. This allows you to scroll through and read any messages. Once unchecked, all messages which were received during the paused interval will appear. The **Stop Reading** button will stop the WITS feed.
5. It is also possible to send data back to the server. The **ICDS** **IP** and **ICDS** **Port** should already be greyed out and filled with your company’s details. If not, you are likely using the incorrect license, and should contact your company administrator. Check the **Send data to server** box to begin pushing data back to the server.
6. **Minimize** the WITSML Comms window. Do **NOT** close it, as this will stop the incoming WITS data.

#### 3.5.3 - MQTT/Wireless WITS

MQTT or Wireless WITS is used to receive wireless WITS data from two specific providers – Digidrill and KLX Wireless WITS. The user will need valid login credentials, provided by the service provider.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/e77GAGtbNqwU7ehDPcaF/Unknown%20image" alt="" width="375">

1. Select the service provider from the **Source** dropdown.
2. Enter the URL of the data source in the **Server URL** box. Enter your provided credentials into the **Username**and **Password** boxes. You can check if your credentials are correct by clicking on the **Test Connection**button. The message box below will display a response from the server.
3. Click on **Start Reading** to begin receiving data. Acknowledgement of incoming data packets will be displayed in the message box. The **Pause Messages**button will prevent the dialog from receiving any new messages allowing you to scroll up, while the data feed continues in the background. **Clear Messages** will delete all messages in the message box and **Write to File** will create a text file containing all messages in the message box. The Stop Reading button will stop the WITS feed.
4. It is also possible to send data back to the server. The **ICDS** **IP** and **ICDS** **Port** should already be filled with your company’s details. If not, you are likely using the incorrect license, and should contact your company administrator. Check the **Send data to server** box to begin pushing data back to the server.
5. **No WITS mapping is required here**.
6. **Minimize** the Wireless WITS window. Do **NOT** close it, as this will stop the incoming WITS data.

### 3.6 - Start Live Rig States

If you wish to use the WITS data to automatically fill in your slide/rotate activity and drilling parameters, you need to start Live Rig States. To do so, go to the **Rig States** section in the menu ribbon, and click on **Start**.

While Live Rig States is running, the phrase **‘Live Rig States’** will appear at the top of the slide sheet, and it will begin automatically populating. You will **not be able to manually edit the slide sheet**. If you have configured the survey options to do so you will also begin receiving surveys.

To stop the Live Rig States, go back to the **Rig States** section in the menu ribbon, and click on **Stop**.

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


# Well Seeker X: Rig States Guide

Introduces the user to the Rig States dialog, which is used in tandem with WITS to automatically populate the slide sheet.

## 1.0 - Introduction <a href="#toc157778942" id="toc157778942"></a>

During drilling operations, Well Seeker Pro has the ability to receive a WITS or WITSML feed from the rig site and use this data to automatically populate the Directional Driller’s slide sheet. To do this, Well Seeker X must use the WITS data to deduce the current operation on the rig – drilling, sliding, connection and so on – otherwise known as the **rig state**.

Well Seeker receives drilling parameters from the WITS/WITSML feed and compares them against user-defined thresholds. Depending on whether the incoming values are above or below the threshold, Well Seeker can infer what activity is currently happening on the rig. For example, if the string RPM is below the RPM threshold it can be inferred that the string is not rotating etc. Well Seeker then combines all of these parameters to deduce the current rig state.

The user can control this process by defining the drilling parameter thresholds in the **Rig States Dialog.** The purpose of this document is to introduce the user to the Rig States dialog in Well Seeker X, and detail the steps required to correctly setup and use it.

## 2.0 – Rig States Setup <a href="#toc157778943" id="toc157778943"></a>

Note that the Rig States dialog requires an incoming WITS or WITSML feed to function properly. For details on setting up a WITS/WITSML feed, see the following guide: [**WITS Setup & Remote Directional Drilling - Innova Drilling & Intervention (innova-drilling.com)**](https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/wits-setup-and-remote-directional-drilling)**.**

To auto-populate the slide sheet, the following channels need to be received from the WITS/WITSML feed:

* Weight on Bit
* RPM
* Total GPM
* Bit Depth
* Hole Depth
* Hookload
* Block Position
* Standpipe Pressure
* ROP (Optional – for recording parameters only)
* Torque (Optional – for recording parameters only)

In addition, if the user wants to receive survey and toolface data, the following channels are required:

* Magnetic Toolface
* Gravity Toolface
* Survey Measured Depth
* Survey Inclination
* Survey Azimuth

The Rig States dialog can be configured before or after setting up the WITS/WITSML feed. To do this, follow the below instructions:

1. In the Slide Sheet window, open the **Rig States Settings** dialog by clicking on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FicnvZGybS3XQk8ypdhIK%2Fimage.png?alt=media\&token=c2d67489-8886-45ef-88a9-ed4cd6cb0931) icon in the ribbon menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FF36aMe0fVUwMOJsFBLte%2Fimage.png?alt=media&amp;token=fbe19433-f44a-4327-80eb-6eed4fed2014" alt=""><figcaption></figcaption></figure>

2. Configure the rig parameter **Thresholds.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsB8ZU5YH806zTBIs9rBf%2Fimage.png?alt=media&amp;token=b6cd0ecc-56db-4bde-8b27-11d5980f7d5a" alt=""><figcaption></figcaption></figure>

The threshold value acts as a switching point. Any value below the threshold is effectively off, while any value recorded above the threshold is on. It should be set low enough that there is a clear demarcation between each activity, but not to zero. This will stop erroneous WITS values from accidentally changing the activity.

**RPM:** If the incoming RPM value is below the threshold, the pipe is considered to be not rotating. If it is above, it is rotating. When drilling, this is used to decide if the string is sliding or rotary drilling. Recommended value is \~50% of the rotating RPM.

The RPM threshold uses a buffer, which can be configured in the **RPM Buffer Parameters** section. The software stores the number of RPM values entered in the *RPM Buffer Size* input, in the RPM Buffer. If at least *RPM Buffer Threshold* number of values are larger than the *RPM Threshold* then the rig state is Rotating. If not, it is sliding.

As an alternative to using the RPM Threshold, RPM Buffer Size and RPM Buffer Threshold, the user can toggle ON Advanced Slide Detect. See below for more details

**Pump Pressure:** If the incoming standpipe pressure value is above the threshold value, then the pumps are considered on. If it is below the threshold, the pumps are off. Recommend value is between 0 and 100 psi

**Hookload:** If the incoming hookload value is lower than the threshold, the string is considered in slips. If it is above, then it is out of slips. Recommended value is block weight + 50%.

**On Bottom Delta:** The program calculates the difference between the Bit Depth and the total Hole Depth. If this value is smaller than the On Bottom Delta, then the bit is considered on bottom. If it is larger, then the bit is off bottom. Recommended value is less than 1 foot or metre.

**Stall Pressure:** Determines how much pressure is required above the average standpipe pressure for a motor stall to be automatically recorded in the Motor Stalls record. This can be viewed by clicking on the **Motor Stalls** option in the Slide Sheet menu ribbon. Pressure and flow data used to detect stalls can be viewed in the **Stall Detection** section.

**Mag to Grav X/O:** Angle at which the MWD tool has been set to change from transmitting magnetic to gravity tool face values.

**Auto Thresholds:** When YES is selected, Well Seeker will adjust the RPM and Hookload thresholds values dynamically and prevent the user from editing those thresholds. If NO is selected then all thresholds are editable and static. If a block weight has been entered in the **Rig Names** dialog, the software will use *block weight x 1.5* as the starting hookload value.

**Advanced Slide Detect:** As an alternative to using the RPM Threshold, RPM Buffer Size and RPM Buffer Threshold, the user can toggle ON Advanced Slide Detect. In this mode, instead of inspecting the RPM, the software inspects the incoming torque values. If the torque values are oscillating in a sinusoidal pattern, the string is recognised as Sliding. If not, Rotating. Incoming torque values can be seen in the section below the Thresholds section.

This setting is advised to be set to NO by default. Set to YES where sliding intervals are not being detected, due to RPM data values not displaying oscillation variation i.e., flatlining for multiple data points.

**Block Weight:** The weight of the rig travelling block. If auto thresholds is turned on and block weight > 0 then the hookload threshold will be block weight x 1.5.&#x20;

3. If necessary, configure the **RPM buffer**. RPM values from the WITS/WITSML feed can fluctuate, so in addition to the RPM Threshold, the Rig States dialog also uses the RPM Buffer to determine if you are rotating or sliding.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9wFrjDFvYUN58l3VnMgD%2Fimage.png?alt=media&amp;token=64dec056-e70f-40ee-9906-9bab5fb6d23a" alt=""><figcaption></figcaption></figure>

The **RPM buffer size** sets how many of the most recent RPM values to keep in the buffer, and the **RPM Buffer Threshold** sets how many values in the buffer need to be above the RPM threshold before Well Seeker considers the string to be rotating.

As an example, with an RPM Buffer Size of 9 and an RPM Buffer Threshold of 3 the below would be true.

* If there are 3 or fewer values in the RPM buffer that are > RPM Threshold then you are **sliding**.
* If there are 4 or more values in the RPM buffer that are > RPM threshold then you are **rotating**.

In most cases, these values can be left as the default.

4. Once the thresholds have been set up, **minimize** the Rig States dialog. **Do not close it.**
5. Once both the Rig States and the WITS/WITSML feed have been set up, you can click on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOA1mW7mMRLAxz8sSSs5k%2Fimage.png?alt=media\&token=86353d15-43a4-4c4d-ab98-6faafb9551e7)**Start** button on the toolbar to start automatically recording rotate and slide activity, as well as drilling parameters.\
   The message **“Live Rig States”** will appear below the ribbon menu. You will **NOT** be able to manually edit the slide sheet while the slide sheet is auto-populating. To pause recording, click on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnaUBZgYmWZcALTUpa2wr%2Fimage.png?alt=media\&token=862636f1-2895-4a5c-96ca-53301939420b) **Stop** button. This will allow you to edit the slide sheet again.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVLNgcbLEkRRPnubuz4BV%2Fimage.png?alt=media&amp;token=ff6eb02f-5a82-49be-b428-d25ef418528f" alt=""><figcaption></figcaption></figure>

The thresholds can be changed while the slide sheet is auto-populating. If you feel that the slide and rotate activity is not being accurately captured, try adjusting some of the thresholds.

## 3.0 – Monitoring Rig States <a href="#toc157778944" id="toc157778944"></a>

While receiving WITS data, the Rig States dialogue can be used to view the incoming drilling parameter data and the rig state inferred from that data. These will display regardless of whether auto-populate is turned on or off.

The **Current WITS Data** and **Drilling Params** sections display the data values taken from the WITS feed. They will display the most recently received values.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIJMrhEz0rSMs4PDsWk3u%2Fimage.png?alt=media&amp;token=2341d316-9b37-4c0b-ad4c-d020e263644f" alt=""><figcaption></figcaption></figure>

In the **Current Rig State** section, Well Seeker takes the values from the Current WITS Data and Drilling Params sections, and compares them to the user defined threshold values to deduce the activities displayed:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPSBDMVOK97Rp50R34DHN%2F6.png?alt=media)

* **On Bottom Delta >> On/Off Bottom**
* **Pump Pressure >> Pumps On/Off**
* **Hookload Threshold >> In/Out of Slips**

These activities are combined with the direction of the travelling block to deduce the **RigState** output. The slide sheet can only record rotating or sliding activity, but the RigState output can deduce other activities, such as reaming in/out, tripping in/out and connection. See the Troubleshooting section below for the full list of activities.

If the WITS feed is also sending toolface data, this will be displayed in the **Sliding TF** section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4iSjkBpvR1bvnNH4Y1YJ%2F7.png?alt=media)

The **Timers** section displays the last time a Pumps On, In Slips, Off Bottom or Survey event was recorded. The Duration column records how long the event lasted.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBB9QtIDrvQSTBXXklkBe%2F8.png?alt=media)

## 4.0 – Troubleshooting <a href="#toc157778945" id="toc157778945"></a>

If the slide sheet is not auto-populating in the way you would expect, follow the below steps to troubleshoot the issue:

1. Check the **Current WITS Data** and **Drilling Params** sections. As a minimum, the following channels need to be received from the WITS/WITSML feed for the Rig States dialog to function:

* Weight on Bit
* RPM
* Total GPM
* Bit Depth
* Hole Depth
* Hookload
* Block Position
* Standpipe Pressure

If a channel is not receiving data, it will display a null value of **-9999.25**. If one or more channels are displaying this value, it could indicate that the WITS channels have not been mapped correctly. Consult with the rig and change the WITS mapping by going to **Tools >> WITS Mapping.** For more detailed information on WITS mapping, refer to the following guide: [**WITS Setup & Remote Directional Drilling - Innova Drilling & Intervention (innova-drilling.com)**](https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/wits-setup-and-remote-directional-drilling)**.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrED4Smw3ERMTxpNzCReE%2F9.png?alt=media" alt="" width="424">

2. If **all** channels are not receiving data, this could indicate that the WITS feed is not being received at all. Make sure that the WITS or WITSML reader is reading. If it is, check that the message box is showing incoming messages. If not, there may be an issue with your connection.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FwQ8ii0ii9TiCtDhYFIAc%2Fimage.png?alt=media&amp;token=64a7d378-c64d-4222-b6c0-555efca50eff" alt=""><figcaption></figcaption></figure>

Check the physical connection between your computer and the rig WITS system. If you are using serial WITS, note that you should be using a **null modem** cable and not a regular serial cable.

3. Observe the **Current Rig State** section while rig activity is happening. If the activities being displayed in the section do not match with the activities on the rig, this can indicate that your thresholds have not been set properly.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzWSFc9lq7MRq002PHtqr%2F11.png?alt=media)

Each state displayed in the **RigState** field corresponds to a specific combination of threshold values and travelling block direction. The combination required for each is displayed in the table below.

If a cell is filled in **GREEN then the value is above the threshold**. If it is filled in **RED then it is below the threshold**. Cells filled in grey can be either above or below.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEZCbLqn2VHq9YZumQSjn%2Fimage.png?alt=media&amp;token=6c19a7b2-9a12-492a-a17b-ac4b29e35aa9" alt=""><figcaption></figcaption></figure>

If the combination of thresholds and block speed does not match with one of the rig states listed here, the displayed rig state will be **UNKOWN**.

### 4.1 – Contacting Innova <a href="#toc157778946" id="toc157778946"></a>

If having worked through all of the trouble shooting steps detailed above, you are still having issues, you can contact Innova support for assistance. When contacting Innova, to allow us to provide the most efficient support, please follow the below steps:

1. **Create a debugging file:** In the main Well Seeker window, select **Help** tab on ribbon menu and select **Email Dabug.** If Outlook is your default email client, this will automatically create an email with .zip file containing a copy of the current database, a copy of your setup file and a txt document containing system information.

   1. Clearly state the name of the well and Operator you are working in.

   Check the [**Report an Issue**](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-reporting-an-issue#debugging-file) guide if you need more information.
2. **Create a log file:** In the Slide Sheet window, toggle on **Error Logging**. This will create a log file that captures incoming rig parameter data and logs any errors. Start reading with the WITS feed and open the Rig States dialog, and let them run for some time to collect some data in the log file. This should ideally be done whilst performing the next step.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAgbbxJDPbiN5kzO3aEpO%2Fimage.png?alt=media&amp;token=ab0b6aa2-a5b9-49f9-b3b4-c03e11a57601" alt=""><figcaption></figcaption></figure>

1. **Record a screen capture of your Slide Sheet and Rig States dialog**: In the main Well Seeker window, select the **Help** tab on ribbon menu and select **Start Screen Capture.** This will begin recording a video of your screen. If you are using version **3.0.2.8** or later, the tool will also record audio along with the screen capture. Display your slide sheet and Rig States dialog on your screen, similar to the screenshot below, and begin auto-populating your slide sheet. Try to capture the issue occurring. When you are ready to stop recording, go back to the **Help** menu and select **Stop Screen Capture**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuM0TgQ3qGGssUwbMCjpX%2Fimage.png?alt=media&amp;token=477840e3-3437-434f-b030-29b810e477eb" alt=""><figcaption></figcaption></figure>

4. Open the **Help** menu again and select **Open Screen Capture**. This will open the **Debug** folder. The log file **rigStateLog.txt** and the screen capture **screenCapture.mp4** are located here.
5. Attach the debugging file, log file and screen capture file to an email, and send it to <support@innova-drilling.com>.
   * Include a detailed description of your issue.
6. Innova support will get in contact with you to provide assistance.


# Well Seeker X : ROGII Integration Guide

## 1.0 – Introduction

Well Seeker X includes integrated features with ROGII StarSteer geosteering software. This document will guide the user through the specifics of the setup and operation of these features.

To use any of the 3 features described below, the user will need:

* A stable internet connection.
* Valid username and password credentials. These credentials should be obtained from the users Solo Cloud provider.
* An Actual Well/ Survey setup in the Well Seeker database tree. For detailed steps regarding how to achieve this, refer to the [Well Seeker X: How to Guide.](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-how-to-guide)

The ROGII features are accessed via the Integrations Tab. The Target Lines and Solo Cloud options are only available when the user has a survey open, and Data Factory is only available when the user has selected Plan or Actual well level in the Object Explorer.

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

## 2.0 – Target Line Dip Angle Adjusted for Azimuth Changes

To seamlessly calculate geo-steering target line and plan changes that involve azimuth changes in the lateral, Well Seeker X provides the option to either hold the target line dip angle during azimuth changes or automatically adjust the dip angle to keep the plan within the intended geological plane. This behaviour is controlled by the **Adjust Dip on Azi** option in the **Settings** menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfU0MM2CWePX4YKTExDNM%2Fimage.png?alt=media&amp;token=57b46f16-c4fe-4996-a06a-8f0980c66dcc" alt=""><figcaption></figcaption></figure>

Both options are detailed below.

### 2.1 – Hold dip as azimuth changes (check box unchecked)

The Create Offset Plan tool creates a new plan line which will retain the new dip angle value, regardless of the azimuth change. For large azimuth changes, or small azimuth changes over large course lengths, this will result in the new target line deviating from the intended geologic plane.

Red = 90° dip well for reference.

Blue = Target line plan change with a 94° dip using the hold dip logic. 94°dip retained throughout, resulting in deviation from the formation plane.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FEVfsj3wc3WnpNpy6tM7P%2Fimage.png?alt=media&amp;token=0022ed19-b8a8-4a5a-81f3-d999a5121e9a" alt=""><figcaption></figcaption></figure>

Although in theory this option will result in deviation from the intended geological place, it gives the user the option to match the clients geosteering team’s numbers when they are also using this logic.

### 2.2 – Adjust dip as azimuth changes (check box checked)

The Create Offset Plan tool will recalculate the dip angle value incrementally as the azimuth changes. This keeps the plan and target line in the same plane as geologically intended.

In the below U-zontal example the plan update has a 95° dip angle on a 0° azimuth. As the azimuth changes from 0°, the dip angle also changes to remain in the same dip plane as the target line change intended.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIUuGW2FYlRzJ2K64L0lc%2Fimage.png?alt=media&amp;token=f0b105cf-03a5-488c-be0f-7377f493aa25" alt=""><figcaption></figcaption></figure>

Red = 90° dip well for reference.

Blue = Target line plan change with a 94° dip using new logic. 94°dip retained until azimuth change detected. Dip angle is then adjust to remain in the intended formation plane.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrT5CtvML2YQ8373wiali%2Fimage.png?alt=media&amp;token=8c0fe406-f97f-4891-ab55-b740ad8dcf5a" alt=""><figcaption></figcaption></figure>

The comparison below clearly shows the difference between the two methods.

Red = 90° dip well for reference.

Magenta = Target line plan change with a 94° dip using the hold dip logic. 94°dip retained throughout, resulting in deviation from the formation plane.

Blue = Target line plan change with a 94° dip using the adjust dip logic. 94°dip retained until azimuth change detected. Dip angle is then adjusted to remain in the intended formation plane.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMuo7uBZlkPY5NdOAl7Gw%2Fimage.png?alt=media&amp;token=8fac268b-bb6f-4e80-aaea-08f6c6490fec" alt=""><figcaption></figcaption></figure>

In addition, the display logic for the **Target Zone** that can be viewed on the plots has been updated. There are two scenarios:

1. Geo-Steering Updates table is blank. A 20ft up/down, 40ft left right target zone will be displayed around the principal plan trajectory.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLcwlyaAlYjvFZk9R1Z4Z%2Fimage.png?alt=media&amp;token=83120a15-542a-47f1-b37a-15024ef313f9" alt=""><figcaption></figcaption></figure>

2. Geo-Steering Updates table is populated. Geo-steering data will be displayed on the plots as per the table data.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjX16h01BLRv7FOyR6pNT%2Fimage.png?alt=media&amp;token=e39a6d9a-afd4-4ec4-adab-31ff89b3d461" alt=""><figcaption></figcaption></figure>

## 3.0 – Target Lines

The Target Lines tool provides a simplified workflow for configuring the target line integration. While the same setup can also be completed through the Solo Cloud section, the workflow within the Target Lines tool is more streamlined and is therefore the recommended approach where possible. However, this tool does not provide the ability to pull formation topsets, which can only be configured through the Solo Cloud section.

**Note:** This feature is only accessible when viewing a survey

### 3.1 – Target Lines Workflow

1. Open any survey under the well of interest
2. Go to **Integrations > Target Lines**

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

3. Confirm the API# is correct
   1. This cell is read only. If the value is missing or incorrect, the user can enter or amend the value via the **Job Data** dialog in the daily reporting section of the software.
4. Select ‘**YES**’ or ‘**NO**’ in the Auto Update dropdown
   1. **YES**: when a Target Line is starred, or an existing starred target line is adjusted in Solo Cloud, the Well Seeker user will receive a pop-up message within the Well Seeker interface, informing the user of the existence of the new target line and offering the user the choice of creating a new plan within Well Seeker. If the user selects to create a new plan, the plan will be automatically generated and selected as the principal plan. The new plan will also be added to the offset selector and will appear in any plots which are open. Once **YES** has been selected, the user can close the Solo Cloud dialog and continue operations. There is no requirement to access this dialog again. Even if Well Seeker is closed and reopened, any time this survey is opened, Well Seeker will be looking for target line changes. 1. If the user selects **YES**, set the frequency of updates in minutes using the **Update Rate (mins)** field.
   2. **NO**: The auto update will be disabled.
5. Input **Username** and **Password.**
   1. These are the ROGII credentials, not Well Seeker credentials
6. Click ‘Apply’
7. If the credentials are incorrect the **Status** will display **Credentials error: Invalid login or password.**

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/LavMZLbx2jB1uWUE3Ls5/Unknown%20image" alt="" width="563">

8. If the credentials are correct and Well Seeker finds a well with a matching API# in Solo Cloud, then the **Status** will display **OK**.

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

9. If the credentials are correct and Well Seeker finds more than one well with a matching API# in Solo Cloud, then the **Status** will display **Wells error: multiple wells found.**
   1. If more than one well is found, when the user hits ‘Apply’, the **Select Wells** dialog will open. The user should **Select** the checkbox of the relevant well and then select **OK**. Once a well has been selected, the status will update to **OK**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOAcBsYpOSKetQTMIfwsc%2Fimage.png?alt=media&amp;token=db6bd6a9-3b2b-4f6c-b0ca-c4e7d474f5a3" alt=""><figcaption></figcaption></figure>

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

10. If the credentials are correct and Well Seeker cannot find a well with matching API# in Solo Cloud, then the **Status** will display **Wells error: no wells found.**

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

## 4.0 – Solo Cloud

The Solo Cloud integration allows Well Seeker X to directly connect with Solo Cloud, eliminating the manual steps between the geosteering team and the directional driller. When a geosteerer creates or updates target lines in Solo Cloud, these updates are automatically pushed to Well Seeker. The directional driller receives an on-screen prompt and, upon acceptance, the target line data is used to generate a new plan. This plan is then automatically sent back to the geosteerer in Star Steer, creating a seamless closed-loop workflow.

In addition, the integration can also pull formation tops (topsets) from Solo Cloud and update Well Seeker’s lithology table, ensuring the directional plan is fully aligned with the latest geological interpretations.

### 4.1 – Entering User Credentials

1. Open any survey under the well of interest
2. Go to **Integrations > Solo Cloud** (This will only be available to select if a survey is open)
3. The **Solo Cloud** dialog will open.
   1. In the **Object Explorer** section, your organization name should display below Solo Cloud. If it does not, confirm that the ICDS Server IP and Port values in the **Real Time Data Exchange** dialog are correct.
   2. Input valid **Username** and **Password** credentials for the relevant Solo Cloud server, then click on the![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/sWYYP72Zb1CPinC4d3qw/Unknown%20image) **Connect** button in the toolbar. Once entered the Username and Password will be saved and used for all surveys present below the Actual Well.

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

4. At this point, if you are only planning to set up the target line portion of the integration, it is recommended that you proceed directly to section 3.0, as this details a more simplified workflow.

### 4.2 – Configuring and Managing Solo Cloud Target Line Updates

If the user’s only requirement is to configure the integration to automatically receive new target line updates, then it is recommended to use the Target Lines feature detailed in Section 2, as this provides a more streamlined workflow.

1. Expand the relevant **Organization**, **Well** and **Actual Well** items in the Object Explorer until you find the actual well you are working with and select it. As you select items in the Object Explorer, the Settings dialog will update accordingly.

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

2. Chose the **Auto Update** setting. Select **YES** or **NO**.<br>

   1. **YES:** When a new starred Target Line is added to the Solo Cloud database, or an existing starred line is changed in some way, the Well Seeker user will receive a pop up message within the Well Seeker interface, informing the user of the existence of the new target line and offering the user the choice of creating a new plan within Well Seeker. If the user selects to create a new plan, the plan will be automatically generated in Well Seeker and selected as the principal plan. This new plan will also be pushed to Solo Cloud. If the user chooses not to create a new well plan, nothing will change.
      1. If **YES** is selected, set the frequency of updates in minutes using the **Update Rate (mins)** field.
   2. **NO:** The user picks the target line and creates an offset plan manually from the Solo Cloud dialog.

   <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FaQlu53SZoGu242G8InYF%2Fimage.png?alt=media&amp;token=104e93a9-7163-4104-9e72-f39440bd31b5" alt=""><figcaption></figcaption></figure>
3. In the **Back to Plan Transition** field choose either **STEP** or **SMOOTH**. When the user creates a new offset plan in Well Seeker, it will be pushed back to Solo Cloud. This setting decides if the transition between the old plan and the new will be a step change, or a smooth transition.
   1. If **SMOOTH** is chosen, set the dogleg severity in the **Back to Plan DLS** field. Note that the smooth transition will **only** be displayed in Solo Cloud (below right). In Well Seeker, the transition is displayed as a step regardless of what is chosen here.

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

4. Check and expand the **Target Lines** level and select the relevant target line. Target lines that are currently Starred within Solo Cloud will display with a green T icon next to them. This is to indicate the most recent target line. The **Object Info** section will display the target line data when selected.

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

5. Click the ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/LXoW9j4Xs64IEqExTCdy/Unknown%20image)**Create offset** plan icon. The offset plan will then be automatically created and will be accessible in the Well Seeker database. Close the Solo Cloud dialog.
6. **NOTE**: When Auto Update is selected, the user will only need to manually create the first target line, after that a dialog will pop up on the screen any time a change in target line is detected.

When the plan is created, it is automatically added to the Object Explorer. The plan name includes the target line name, the date and time it was added to Well Seeker, and whether the transition type is STEP or SMOOTH (although all plans are generated as stepped plans within Well Seeker). The new offset plan is then automatically pushed back to Solo Cloud and set as the **principal plan** within Well Seeker.

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

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

How the user should then proceed depends on whether they chose **YES** or **NO** for the **Auto Update** setting

7. Selecting **YES**: If a new target line is created and starred, or the current starred target line is changed in any way (including target thickness) in Solo Cloud, the Well Seeker X user will receive a popup message, describing the new target. If the user clicks on **Ignore**, no change will be made in Well Seeker. If they click on **Accept**, a new offset plan will be created in the database tree and will be set as the principal plan for the well. It will also be automatically selected as an offset well so if a chart is open it will show up immediately.

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

8. Selecting **NO**: The user will not automatically receive an update if any changes are made in the Solo Cloud database. They should periodically re-open the Solo Cloud dialog to check if any updates have been added to their project. If a change has been made, the user should repeat the steps to create a new offset plan in their Well Seeker database tree.

**Note**: Well Seeker creates a new plan for EVERY target line change detected, even if this is just a change in an existing target line e.g. thickness.

### 4.3 – Target Line Plan Behaviour in Solo Cloud

Whenever the user accepts a new target line in Well Seeker, either through the auto-update feature or manually using the Solo Cloud dialog, it always results in a new plan being created in the Well Seeker database tree. At the same time, Well Seeker transmits the plan back to Solo Cloud and the StarSteer software.

However, this does not necessarily result in a new plan being created in the StarSteer interface. In StarSteer, each target line can only have one plan from Well Seeker associated with it. If a plan already exists for a target line, it will be overwritten by the new plan transmitted from Well Seeker. The date and time in the name of the plan will change to show when the update was received.

For example, the StarSteer user has two target lines for a well. Target Line 1 is currently starred and the user creates an offset plan from this. Below left is Well Seeker and right is Star Steer.

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

They then make a change to Target Line 1, and this change is sent to Well Seeker. The Well Seeker user accepts the target line change, which creates a new plan in Well Seeker (below left) and sends this back to Star Steer. Because Target Line 1 already has a plan associated with it in Star Steer, the plan is overwritten and the name is updated (below right).

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

The StarSteer user than changes the starred target line to Target Line 2, which does not currently have a plan assigned to it. This change is sent to the Well Seeker user, who accepts the change, and a new plan is transmitted back. Because Target Line 2 currently has no plan, a brand new plan is created in StarSteer.

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

### 4.4 – Pulling Formation Topsets from Solo Cloud

1. Follow section 2.1
2. Select **Topsets** and then the desired Topset group. Note that the check boxes will **NOT** be selectable. Only the text can be selected. The Object Info section will update with the relevant formation top data.

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

3. Select the **Pull Tops** icon. Select **Yes** to the overwrite existing lithologies message. Close the Solo Cloud dialog. The **Lithologies** table for the current actual wellbore will have been overwritten with the Solo Cloud Topsets data.

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

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/eEEZD29iPbgE8wssj3ZX/Unknown%20image" alt="" width="375">

## 5.0 – Data Factory

ROGII’s Solo Data Factory (SDF) is an operations-focused regulatory data hub that integrates public datasets, digitized well trajectories, and well logs within the Solo Cloud ecosystem. Through the Well Seeker integration, users can search for offset wells within a specified distance of the selected well and directly download the available trajectory survey data into the Well Seeker database.

**Note:** This feature requires credentials, provided by ROGII, to be entered in the Integrations section of your company’s **Innova Vantage** environment, the steps for which are detailed in the next section.

### 5.1 – Credentials Setup

1. Navigate to [vantage.innova-drilling.com](http://vantage.innova-drilling.com/) and login using Innova Vantage credentials. Once on the main page, navigate to [Integrations](https://vantage.innova-drilling.com/admin/integrations) using the hamburger drop down menu in the top left corner.

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

2. Select ROGII and enter your organization’s Solo Cloud credentials. The URL [**https://Solo.cloud**](https://solo.cloud/) will work for most cases, unless SSO is turned on for your Solo Organization, in which case you would specify your organization’s Solo Cloud URL (e.g. if Innova has SSO enabled, it would be [https://innova.solo.cloud](https://innova.solo.cloud/).

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

3. If the user tries to open the Data Factory dialog in Well Seeker without the correct credentials, an error message will be displayed.

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

### 5.2 – Importing a Well

1. Select an Actual Well or Plan in the Well Seeker object explorer.
2. Go to **Integrations > Data Factory**

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

3. Once connected, the user should be able to access, visualize, and download Solo Data Factory data from ROGII inside Well Seeker X.

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

1. The dialog will display the search area on the map. The centre of the search area will be the surface location of the selected well. The centre can be moved by left-clicking and dragging the middle point of the circle. Its radius can be changed by left clicking and dragging the points around the outside of the circle.
2. These can also be manually changed by entering values into the **Location** section of the ribbon. The search area can be hidden by toggling the **Show Radius** option.
3. Offset wells detected inside the search area are displayed in the table on the left.
4. The results can be filtered by survey tool using the **IPM** dropdown box in the ribbon menu.
5. They can also be filtered by name in the **Search Wells** field.
6. The wells can be selected by checking the **Import** check box beside each well.
7. Once the desired wells are selected, press **‘Import’** in the ribbon menu and the offset survey data will be downloaded to your database.


# Well Seeker X: Multi Leg Lateral Guide

Guides the user through setting up a multi-leg lateral well in Well Seeker X

## 1.0 – Introduction

Well Seeker X supports the management of wells containing multiple lateral legs.

A Multi-Leg Lateral is configured by designating an actual well as the motherbore and defining the number of additional lateral legs associated with the well. Each lateral is managed using its Unique Well Identifier (UWI), allowing Well Seeker X to maintain the correct relationship between the motherbore and its individual lateral legs.

Once configured, users at the rig site can create new lateral legs using the Create Sidetrack workflow. Well Seeker X automatically identifies the motherbore UWI, determines the appropriate UWI for the selected lateral leg, and creates the corresponding actual well.

Importantly, the newly created lateral is then automatically pushed from the rig's local database to the organization's remote server database.

Under the standard workflow, a new plan or lateral created at the rig exists only within the local rig database. To make this available to office-based users, the rig would need to manually export the well and send it to the office, where it would then need to be imported into the server database.

The Multi-Leg Lateral workflow removes this manual exchange. As soon as the new lateral is created at the rig, it is synchronized back to the server, providing office and other connected users with visibility of the new well without requiring any manual export, email, or import process.

This provides a consistent well structure based around the UWI while ensuring that new lateral legs created during drilling are automatically available across the organization.

## 2.0 – Configuring a Multi-Leg Lateral

### 2.1 – Designating the Motherbore

An actual well can be designated as the motherbore for a Multi-Leg Lateral from the **Actual Wellbore Properties**.

This option is only available when connected to the organization's **remote server database**.

If the well is accessed from a local database, the Multi-Leg Lateral options will be greyed out. So this is something that is setup in the office prior to the job starting.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/QmKSmEO8R9JlSja5jn2b/media/image3.png)

To configure the well:

1. When connected to the server, open the **Actual Wellbore Properties**.
2. Select the option to designate the actual well as a **Multi-Leg Lateral**.
3. Enter the number of additional lateral legs.
4. Ensure that the UWI is included in the motherbore well name using the exact required format, details of which are described in the next section.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/vEdO7llvKSGwLimAz4eS/media/image4.png)

#### 2.1.1 Unique Well Identifier (UWI)

The UWI should be appended to the end of the motherbore well name.

**Example:** 101/13-01-050-25W3/00

The /00 event code identifies the motherbore as Leg 1.

{% hint style="warning" %}
**Important: The UWI must be entered in the exact required format. Additional spaces or characters can prevent Well Seeker X from identifying the UWI when a new lateral is created.**
{% endhint %}

* **Correct:** 101/13-01-050-25W3/00

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/3EihqP8c2N1zjPOEwHn2/media/image5.png)

* **Incorrect:** 101/13-01-050-25W3 /00

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OTjEDF6bPSjMG62Y6jb4/media/image6.png)

The incorrect example contains an additional space before /00. Although the difference may appear minor, this will prevent Well Seeker X from correctly identifying the UWI.

#### 2.1.2 – Number of Lateral Legs

The number entered in the **#Legs** field in the Actual Wellbore Properties represents the number of additional lateral legs and should **NOT** include the motherbore. The motherbore is always considered **Leg 1**, and it’s UWI should always end in “**/00**”.

For example, if the well has a motherbore and three additional lateral legs, enter **#Legs = 3.** The resulting well structure will be:

| **Leg**    | **Leg Number** | **UWI ending** |
| ---------- | -------------- | -------------- |
| Motherbore | Leg 1          | …/00           |
| Lateral    | Leg 2          | …/01           |
| Lateral    | Leg 3          | …/02           |
| Lateral    | Leg 4          | …/03           |

The number entered in #Legs determines the available options in the Leg dropdown when creating a new lateral.

## 3.0 – Creating a Lateral Leg

Once the actual well has been configured as a Multi-Leg Lateral, a new lateral leg can be created at the rig site using the Create Sidetrack workflow.

Right-click the Actual Well and select Create Sidetrack.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/RPWmJNwdqtxYyNlnA9XW/media/image7.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/vtSshX9klctAlH0pCqEL/media/image8.png)

As the motherbore is always **Leg 1**, this will not be available for selection in the dropdown. If two additional legs have been configured, the available options will be, Leg 2 and Leg 3.\
Select the leg that is being created and click **Create**.

{% hint style="warning" %}
**Note: The UWI does not need to be entered again when creating each lateral. Well Seeker X automatically extracts and validates the UWI from the parent well or a matching well plan.**
{% endhint %}

If no valid UWI can be identified from the parent well or a matching well plan an error message will be displayed.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/eprMtLKiGGeYGZFBZUfw/media/image9.png)

New lateral legs created locally with valid UWIs will be automatically pushed to and created on your organization’s remote server database.


# Well Seeker X - Insert a Missing Daily Report

## Introduction

In some cases, a single or multiple Daily Drilling Reports (DDR) may be missing from the middle or the beginning of a well, that a user wish to add in.

When this happens, simply adding a new DDR and entering the missing date may not work. Well Seeker validates that DDR report numbers and dates remain in chronological order.

For example, if **DDR #5** is missing for **05 July 2019**, but DDRs #5 already exists for a later date, the existing DDRs must first be renumbered to create a gap for the missing report.

This guide explains how to insert the missing DDR while maintaining the correct DDR numbering and dates.

## Procedure

{% stepper %}
{% step %}

### Identify the Missing DDR

Open the Daily Reports section and identify the missing date.

In this example, the missing report is 05 July 2019.

The existing DDRs after the missing date are numbered consecutively, so a new DDR cannot simply be added as DDR #10 and assigned the missing date. WSX’s validation logic will flag this as an error and prevent a date from being saved to DDR #10 that is less than DDR #9.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzJGuIAqji9kbv13IPLPq%2Fimage.png?alt=media&amp;token=0c1f0e17-6a23-416a-b162-47d2fd9e32ed" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Renumber the Existing DDRs

Starting with the last DDR, renumber each report by +1, saving at each change.

In this example change:

* Report #9 → **Report #10**
* Report #8 → **Report #9**
* Report #7 → **Report #8**
* Report #6 → **Report #7**
* Report #5 → **Report #6**

{% hint style="warning" %}
**Important:** Change backwards from the last DDR. This prevents two DDRs from temporarily having the same number.
{% endhint %}

After renumbering, the DDR sequence should look like this, with report #5 available:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FoiyARLKnQAm0EH0bvY3o%2Fimage.png?alt=media&amp;token=ea31afcf-4f47-48bc-906d-4e553c7e985b" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Add the Missing DDR

Add a new DDR.

Set the DDR **Report #** to 5. Save the new DDR.

At this stage, do not edit the date until after the DDR has been saved with the correct report number.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FByJFX6DmGRlmB6kJjbZW%2Fimage.png?alt=media&amp;token=a820498e-98f8-41af-b35a-e99945df6bff" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Set the Missing Date

After saving the new DDR as Report #5, click in the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSfVkaLgLYYepuu7S5xFl%2Fimage.png?alt=media\&token=9af75947-14f3-413f-8655-dae25e71957d) to change the DDR date to 05 July 2019.

Save the DDR again.

The DDR sequence should now be chronological.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjqxaNep1lcB0fCjn5Xz3%2Fimage.png?alt=media&amp;token=f84f7131-a296-4d0c-a9cc-74b151505512" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select the Correct BHA and Phase

If the activity for the inserted day was non-drilling, then manually update the daily activity accordingly, to the row where on bottom drilling activity resumes. Then on the first row of drilling activity select the appropriate BHA and Phase. These values should match the BHA and phase that were active for the missing day's activities.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8TZ0VxJUMOobL1YZpReM%2Fimage.png?alt=media&amp;token=327c8328-c0ed-4a36-8df0-d35d10994227" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Slide Sheet

If applicable, open the relevant Slide Sheet and click in the save button. This allows the Daily Activity to update the drilling data associated with the newly inserted DDR.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fc8PLDTPAG35XPYVserFB%2Fimage.png?alt=media&amp;token=91e0b26a-c431-4caa-ab5b-693bb4a3b6dc" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4gLlHa6fUJSsZghOClDn%2Fimage.png?alt=media&amp;token=c827b14e-5439-4b06-97f5-c6cc66a9a12a" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Missing Report #1

If the missing Daily Drilling Report is **Report #1**, follow the same procedure described above, but renumber **all existing reports # by +1** until Report #1 becomes available.

Once Report #1 is available, add the new DDR as **Report #1** and enter the correct date.

### Missing Multiple Daily Reports

If **more than one day** is missing, the existing reports numbers must be increased by the number of missing reports.

For example:

* Drilling started on **01 October 2025**
* Drilling ended on **10 October 2025**
* DDRs currently exist from **Report #1 to Report #7**
* DDRs for **02, 03 and 04 October** are missing

There are **3 missing reports**, so the existing report numbers need to be shifted by **+3**. In this case, change the last existing report from **report #7** to **report #10**&#x20;

The reports should then be renumbered backwards to create gaps for reports #2, #3 and #4:

* Report #7 → **Report #10**
* Report #6 → **Report #9**
* Report #5 → **Report #8**
* Report #4 → **Report #7**
* Report #3 → **Report #6**
* Report #2 → **Report #5**
* Report #1 remains **Report #1**

This creates the required gaps for:

* **Report #2 – 02 October 2025**
* **Report #3 – 03 October 2025**
* **Report #4 – 04 October 2025**

The missing reports can then be added using the available numbers following the steps explained above.

{% hint style="warning" %}
**Important:** When multiple DDRs are missing, always increase the existing report numbers by the **number of missing reports**. Work backwards from the last report to avoid creating duplicate report numbers during the renumbering process.
{% endhint %}


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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN4SX0eaxA3Ay0UHhK%2F-MdN56BOwBmBZ35jSe0A%2F2.png?generation=1624975635811600&amp;alt=media" alt="Figure 1: Install page 1" width="375">

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN4SX0eaxA3Ay0UHhK%2F-MdN56BPjanN9FNjtq3z%2F3.png?generation=1624975635712234&amp;alt=media" alt="Figure 2: Install page 2 license terms and conditions" width="375">

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN4SX0eaxA3Ay0UHhK%2F-MdN56BQxAgb8erDNtWU%2F4.jpeg?generation=1624975635840617&amp;alt=media" alt="Figure 3: Genuine software certificate" width="375">

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.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN4SX0eaxA3Ay0UHhK%2F-MdN56BRh3Kb5IHhiqU3%2F5.png?generation=1624975635716630&amp;alt=media" alt="Figure 4: Install page 3 installation complete" width="375">

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.


# Hydraulics Module Quick Start Guide

A guide to the Hydraulics module within Innova Engineering.

This document will deal with the Hydraulics module within Innova Engineering and will detail the steps required to run these calculations.

## 1.1 - Setup

**Units**: It is important to ensure that the correct Units are selected before you do anything else as changing units after the data has been input can lead to mistakes. **Note: If air drilling is being modelled, SFCM must be selected as the Flow units to activate air drilling mode.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-McyFK_oa7rRcOXQjvi4%2F-McyGT2CksL2uah8iB-1%2F0.png?generation=1624542406570000\&alt=media)

**Note**: If the unit for Flow is selected as SFCM in the Units Menu, Engineering will assume that **air drilling** is being modelled. In this case the calculation will ignore Mud Weight, PV, YP and Mud Rheology, and instead assume the properties of air as the drilling fluid.

**Hydraulics Model Options** should then be checked from the Options menu. These mostly relate to the surge and swab calculations.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Md2QzdTARREHXckxSFm%2F-Md2RUELuwYf45CtuGNi%2F1.PNG?alt=media\&token=b32c95c6-4564-4989-8c63-db0f8638b2cd)

Surge and Swab is calculated by breaking down the measured depth into sections of a given length (Stand Length), where 30m / 100ft is the default. The program then does a lumped surge and swab calculation over this course length, where the pipe accelerates from 0 to the desired trip speed and then decelerating back to zero.

The acceleration and deceleration phases are calculated based on the trip speeds entered in the Engineering Parameters tab; the higher the trip speed the larger the acceleration effect. The generated outputs in the plot and data table, are the maximum surge or minimum swab values calculated over this interval.

Below is a description of each option:

* **Surge and Swab Parameters**:
  * Mud Compressibility: A compressibility factor for the mud in 1/psi. Default for most oil-based fluids is 3 x 10-6.
  * 10m Gel Strength: 10-minute gel strength, used to calculate the additional surge pressure required to break down the gels. Default is **12**.
  * Stand Length: Length of the stand used in the calculations. Default is **30m / 100ft**.
* **SnS - Include Pipe Acceleration**: This option allows the user to include or exclude pipe acceleration. When this is included, the calculation will use an acceleration and deceleration phase for each stand length. When it is not included, the trip speed will be used for the whole stand with no acceleration or deceleration phase. Default is **Off**.
* **SnS - Include Gel Strength Pressure Loss**: Include the additional pressure required to break down the gels. This is normally a relatively small value. Default is **Off**.
* **SnS – Continuous Circulation**: Used to model coiled tubing. Assumes circulation while tripping, this means that swab affects will be less and surge effects will be more depending on flow rate. The first flow rate in the flow grid of the Engineering Parameters tab is used to determine the annular velocity generated by the circulating fluid. Default is **Off**.
* **SnS – Limit Acceleration Effects**: This option limits the additional surge pressures due to acceleration to a maximum of 2 x the current max surge pressure. This stops very large (artificial) equivalent mud weights being generated when very shallow. Default is **On**
* **SnS – Continuous Tripping**: This option assumes continuous tripping, and as a result will only calculate one acceleration phase (on the first stand length) and one deceleration phase (on the last stand length). This option is best used to model coiled tubing. Default is **Off**.
* **SnS – Use Bit TFA for Open Ended Calcs**: This option allows the user to use the bit TFA when running open ended surge and swab calculations. This will only work for assemblies which have a bit and a TFA entered. When this selection is off, the program uses the internal diameter of the last component. Default is **Off**.
* **Pump Pressure Safety Factor:** This option allows the user to increase the SPP by a specified percentage. Pipe Pressure Loss, Annular Pressure Loss and SPP values are all adjusted to reflect the input Safety Factor.
* **MPD Data**: This option allows the user to enter a back pressure for Managed Pressure Drilling.
  * MPD Setup. The MPD Back Pressure is added as a fixed value to all of the SPP calculation totals and will also be reflected in the ECDs.
  * EMW Calculator: The user inputs the desired EMW increase at a specific TVD and the required back pressure to be applied is calculated. The user can then enter this value in the MPD setup.
* **Riser Boost Rate**: The boost flow rate across the riser is entered here. This additional flow in the riser annulus affects the annular pressure loss, annular velocity, hole cleaning and ECDs in the riser only. This in change in the riser values affects the SPP, annular pressure loss, hole cleaning and ECDs for the section. This is only applicable in wells where the **Well Geometry** includes a ‘**Riser**’. If the well geometry does not include a riser, any value entered here will have no effect on the calculated outputs.

## 1.2 - Required Inputs

In order to run Hydraulics, the following inputs are required.

**Drill String, Well Geometry & Fluids Tab**

* **Drill String**: Input the assembly as accurately as possible including the drill pipe to surface (note, for the last component e.g. DP to surface, the user does not have to input the exact length as the program will do this automatically based on the calculation depth. Inputting a value of 10 is fine). Note that once you have selected the component type it is possible to right click on the line and select "***select from Library***", which will open the components library.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Md2QzdTARREHXckxSFm%2F-Md2RzOoaj1XYyuU_yQv%2F2.png?alt=media\&token=816bb978-f931-4db0-9d95-2b8ed2b630fd)

Input the dimensions of the drill sting components into the Drill String grid:

* * **Description:** A description of the component entered, this is only used in the generation of reports and plays no part in any of the calculations.
  * **OD:** The outer diameter of the component in inches.
  * **ID:** The inside diameter of the component in inches.
  * **TJ OD:** If the component has a tool joint (such as drill pipe) enter the OD in inches into this column. If the “Include TJ in calculations” menu option is turned off this column will be disabled.
  * **TJ ID:** If the component has a tool joint (such as drill pipe) enter the ID in inches into this column. If the “Include TJ in calculations” menu option is turned off this column will be disabled.
  * **Length:** The length of the component in the system units.
  * **Component:** Select the component type from the drop-down list. The type of component that is selected will determine the properties displayed in the lower components grid.
* **Bit TFA**: This is selected in the component details section when the bit is selected. The user can select a fixed TFA or can input multiple nozzles and sizes and a TFA will be generated based on this selection.
* **Motor Pressure Drop**: This is selected in the component details section when the motor is selected.
* **MWD Pressure Drop**: This is selected in the component details section when the MWD is selected.
* **Well Geometry**: Input casing, liner and open hole details including depths and ID's. For Open hole, the ID is the OD of the bit.
* **Mud weight:** Mud density used in all hydraulics calculations
* **PV:** Mud plastic viscosity only used if Bingham Plastic hydraulics model is selected
* **YP:** Mud yield point only used if Bingham Plastic hydraulics model is selected
* **Mud Rheology**: The Fann dial readings of the drilling fluid, required for all hydraulics models except Bingham plastic.

**Surveys Tab**

* **Survey Selection**: Hydraulics calculations can be run against surveys and well plans. Data can be input as measured depth, inclination and azimuth in both Actual Surveys or Well Plan Surveys and the program will generate the rest of the numbers using whichever survey calculation method you have selected (Minimum Curvature Default). Hydraulics cannot be run against surveys input the RAW surveys section. Either enter the plan or surveys manually, import them or copy and paste the data directly into the cells.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Md2QzdTARREHXckxSFm%2F-Md2S9t70wnFlw5KjsDm%2F3.png?alt=media\&token=581b1eb2-ea2d-49dd-8a6a-53b7a8c107e0)

**Engineering Parameters Tab**

This is where the user can select the parameters they want, to run the Hydraulics calculation.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-McyFK_oa7rRcOXQjvi4%2F-McyGT2IJoGZsqNQmTrw%2F6.png?generation=1624542406626098\&alt=media)

* **Hydraulics Model** –four models are included as standard
  * Bingham Plastic
  * Power Law
  * Herschel Bulkley
  * Robertson Stiff
  * Bingham plastic uses PV and YP and mud weight, all other models use the fann readings and mud weight.
* **Surge / Swab** – Specifies if the surge and swab calculation to be carried out is open or close ended. If modelling for a casing or liner assembly and close ended is used, the pressure loss through the float / shoe is taken into account.
* **Surge / Swab Reference** – This is the reference point for the surge / swab calculation, select some common references from the combo box such as bit, shoe and bottom hole or click on the check box to enable a user defined depth.
* **User defined depth** – Only active if the enable check box has been ticked, this will disable the surge / swab reference combo above and the surge and swab reference depth can be entered in the edit box.
* **ROP** – Rate of penetration, this is used to calculate the cuttings loaded ECD’s and other hole cleaning parameters.
* **RPM** – The rotational speed of the drill string. Additional pressure will be added based on the RPM.
* **ECD Adj** – ECD adjustment is manual adjustment to all the ECD curves in order to better match the model with MWD PWD data.
* **SW Den** – Sea water density, which is used for riserless drilling calculations
* **Surface Pressure Losses** – The pressure loss through the surface equipment. This value is added to the total standpipe pressure calculated by the model.
* must
* **Flow rate**: This grid allows the flow rates for the hydraulics model to be entered. By default, the manual flow increment box is unchecked, and the user enters a flow rate in the middle cell of the grid. The software then automatically calculates flow rates above and below this base rate (±25% & 50%) with which to perform a sensitivity analysis. If you wish to override the automatic values generated, click the enable manual flow increment check box. This will leave the user with a single line and once filled a new line will be added. An unlimited number of flowrates can be entered.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Md2QzdTARREHXckxSFm%2F-Md2SiCh0gF8qune8_27%2F4.png?alt=media\&token=84003044-90ed-4495-be07-1aee2a38c299)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-McyFK_oa7rRcOXQjvi4%2F-McyGT2KQE7WI4DqZDeM%2F8.png?generation=1624542406647514\&alt=media)

* **Tripping Speed**: This grid allows the tripping speeds for the hydraulics model to be entered. By default, the manual tripping increment box is unchecked, and the user enters a tripping speed in the middle cell of the grid. The software then automatically calculates tripping speeds above and below this base rate (±25% & 50%) with which to perform a sensitivity analysis. If you wish to override the automatic values generated, click the enable manual trip increment check box. This will leave the user with a single line and once filled a new line will be added. An unlimited number of trip speeds can be entered but the first trip speed entered will be used for the reports. The tripping speed is used in Surge Swab calculations.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-McyFK_oa7rRcOXQjvi4%2F-McyGT2LBt9zRylnrjSE%2F9.png?generation=1624542406630497\&alt=media)

## 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 - Hydraulics**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Md2QzdTARREHXckxSFm%2F-Md2U3X9W7Tpicu0AfiT%2F5.PNG?alt=media\&token=04001c87-6e63-42a5-9850-32aa6a5df4de)

## 1.4 - Output

### 1.4.1 - Hydraulics Results

Once a calculation has been run, the hydraulics results section of the Engineering Parameters tab will be populated with the results. The results displayed are for the flow selected at the top right of this section. This flow is a drop-down menu which will contain the same flows input during the setup, so if only one flow was used, there will be only one available here. The depth can also be adjusted by clicking on the arrows to the right of the depth and it will scroll in 30m / 100ft intervals and display the results based on the depth and flow selected.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-McyFK_oa7rRcOXQjvi4%2F-McyGT2Osnfe7GbmWWTk%2F12.png?generation=1624542406725712\&alt=media)

Note that whatever results are displayed in this section (based on the flow and depth selected), will be output in the summary report.

### 1.4.2 - Reports

Once the calculation has been run, the **Hydraulics Summary Report** can be viewed by selecting the icon from the toolbar at the top of the screen. This contains an overview of the main values associated with the calculation and can be saved as a pdf.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdGAkEJyFBPTSbVH0HF%2F-MdGBXu-m5E36Y2vifCo%2F6.png?alt=media\&token=535e2120-f484-4c83-9ef3-4de7b0ec377d)

If required, a more detailed report can be generated by selecting "**File**" - "**Print Reports**” or selecting the icon on the toolbar (highlighted above). The required data can be selected, and a report can be generated either as excel of pdf. Note that when excel is selected the chart selection will be greyed out as these can only be output as pdf.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdGAkEJyFBPTSbVH0HF%2F-MdGC36g-CiXcl1LvmSL%2F8.png?alt=media\&token=5657963a-e4c7-46d5-8975-eec417a0e9bd)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdGAkEJyFBPTSbVH0HF%2F-MdGC7tsaKg3edjaTDNY%2F7.png?alt=media\&token=dfc5ef81-d8fb-495a-92f4-17183e88a92d)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-McyFK_oa7rRcOXQjvi4%2F-McyGT2Q2i7ZD13Xsgr4%2F14.png?generation=1624542406687807\&alt=media)

Some of the Hydraulics results are available to view by selecting the toolbars along the top. This is a quick way to access some of the more commonly used plots.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdGDigTdCwNdIt-OvVy%2F-MdGF-iBpT4gMicc-RFs%2F9.png?alt=media\&token=bbc0908d-b989-4d71-bb44-f6cab3b2b854)

All the Hydraulics plots and data are available to view by selecting the Hydraulics results at the top of the screen. The Data options display the numerical data used to generate the charts. Note that there is no option to view the data for the Annular Velocity Profile, CCI and Cuttings % Charts.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdGAkEJyFBPTSbVH0HF%2F-MdGDbnxEjSuVmPOhvck%2F10.png?alt=media\&token=e719f78c-29aa-488b-a6ee-f297940048fe)

## 1.5 - Hydraulics Charts

The hydraulics charts give a graphical representation of the theoretical values you would expect to see as the well is being drilled. Therefore, at each depth, the numbers displayed on the charts and the data tables can be directly compared with values recorded from the SPP gauge and down hole tools, as the well is being drilled.

### 1.5.1 - Pump Pressure Chart

This chart displays the standpipe pressure (SPP) expected at surface when the assembly is at any given depth. There will be a line displayed for each of the flowrates entered in the hydraulics section of the Engineering Tab. If pump liner data has been added to the pump data dialog in the tools menu, then this can also be represented on the chart via the add series dialog.

### 1.5.2 - ECD Chart

This chart displays the following lines for each of the flowrates entered in the hydraulics section of the Engineering Tab:

* **Clean ECD**: The ECD at the end of the string, for any given depth, based on a cutting’s free annulus.
* **Dirty ECD**: The ECD at the end of the string, for any given depth, based on a cutting’s loaded annulus. The volume of cuttings in the annulus is calculated based on the ROP entered in the hydraulics section of the Engineering Tab. If the ROP is entered as zero then the clean and dirty ECD lines will lie on top of each other.
* **ECD Snapshot**: The ECD snapshot line shows the expected ECD at each point in the annulus when the string is at a given depth. This depth relates to the deepest depth represented on the chart. This line is generated based on a cuttings free annulus, which means that the last point for both the Clean ECD line and the ECD Snapshot line will be the same.

A line representing the **Mud Weight** is also displayed on the chart.

### 1.5.3 - Surge & Swab Chart

This chart displays the surge and swab lines for each of the tripping speeds entered in the hydraulics section of the Engineering Tab.

The Y axis corresponds to the bit depth (bottom of the assembly being run) regardless of what has been selected as the reference point. The results, however, display the calculated values at the reference point based on the bit position. So if for example you have the reference point selected as the bottom of the hole, when you look at the chart, it will be displaying the surge and swab pressures at the bottom of the hole, when the bit is at any given depth.

The reference point is selected in the hydraulics section of the Engineering Tab and is displayed at the top of the chart.

## 1.6 - Hole Cleaning Charts

Innova Engineering Hydraulics Module contains 4 (snapshot) hole cleaning charts. A basic explanation is given below. For a more detailed explanation of these, see Innova's "***Hole Cleaning Guide***".

### 1.6.1 - Annular Velocity Profile Chart

Flow rate is the dominant factor in cuttings removal while drilling directional wells. An increase in flow rate will result in more efficient cuttings removal under all conditions. However, how high a flow rate can be increased may be limited by:

• The maximum allowed ECD

• The susceptibility of the open hole section to hydraulic erosion

• The availability of rig hydraulic power

This is a snapshot chart and shows the Annular Velocity at all different points in the wellbore when the assembly is at a given depth for the various flow rates.

### 1.6.2 - CCI (Cuttings Carrying Index) Chart

CCI (Cutting Carrying Index) is a measure of how clean a vertical (0-35° inc) well is.

• 0.5 or less and hole cleaning is poor & problems may be seen

• Greater than or equal to 1.0 indicates good hole cleaning

Annular Velocity and Mud weight (along with PV & YP values) are used in this calculation. The higher the annular velocity, the higher the CCI.

For sections of the wellbore where the inclination is greater than 35°, hole cleaning should be evaluated using the **Cuttings % Chart**.

This is a snapshot chart and shows the CCI at all different points in the wellbore when the assembly is at a given depth for the various flow rates.

### 1.6.3 - Cuttings % Chart

The Cuttings % plot represents the percentage of the annulus which is taken up with cuttings. Anything above 5% should be considered a problem.

Unlike the CCI plot, this measure of hole cleaning is not limited by inclination and can be used for any well profile. This calculation is also affected by ROP and RPM. Increased ROP, increases the cuttings %.

This is a snapshot chart and shows the Cuttings % at all different points in the wellbore when the assembly is at a given depth for a given ROP at various different flow rates.

### 1.6.4 - Minimum Flow Rate Chart

The minimum flow rate plot is a snapshot chart which shows the minimum flow required to keep the hole clean at all points in the wellbore for a range of ROPs at a certain depth.

The ROP value selected in the hydraulics setup (e.g. 10m/hr) will be used as the lowest ROP and 4 additional ROP values will be displayed which are automatically generated by the program and are pre-set percentages of the original (125%, 150%, 200% & 250%). These percentages are built into the program and are not adjustable by the user.

To interpret the plot, the user needs to find the largest flow rate for any one ROP and that will be the minimum flow that is required at that depth to keep the hole clean. This can be done by using the Screen Reader or the data table.


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

* &#x20;**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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Mcy1-ZdswoAKWPAD-5z%2F-Mcy1ncCG29XldO1DJa7%2F14.png?alt=media\&token=463fc8f3-a2c8-4a45-be26-5626431ff9c4)

* &#x20;**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.
* I**nclude 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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Mcy2lLHZ644UqTwf6g6%2F-McyCKQQb704ouOhZd3F%2F16.png?alt=media\&token=5c2cf896-2777-4b4d-948e-8cf5a38199df)

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

  &#x20;       **Conservative (Unloading Model)**: Sinusoidal limit x 1.4. This is the default.

  &#x20;       **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.&#x20;
* **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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-McxnvR-mDXSnLPJWfmN%2F-McxpKfFaawTNUxjIWvD%2F1.png?alt=media\&token=1aab2153-c2e0-4771-aa08-c627aa25dd13)

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.&#x20;

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Mcxpwz1y7Af-M-0Rd9f%2F-McxrKoMIUywKuKw2eGj%2F4.png?alt=media\&token=0e79ef6c-ef79-4f6d-b06f-9ad5dae6662b)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Mcxpwz1y7Af-M-0Rd9f%2F-McxrZgBRJ6hWTYfuQBY%2F5.png?alt=media\&token=fd3a4900-c129-495b-8b94-b8c5e99f3cb2)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Mcxpwz1y7Af-M-0Rd9f%2F-Mcxs245haZk4GV94Mh-%2F6.png?alt=media\&token=3788b57f-43b8-4dfd-b668-8cc6f13299be)

* **Calc Depth** – This is the depth the calculation will stop at and the depth the snapshot graphs and tables will display.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Mcxpwz1y7Af-M-0Rd9f%2F-Mcxs5svjOvrx_xARau_%2Fimage007.png?alt=media\&token=17964849-75d3-47a3-8321-deca8b96507c)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-Mct4sw2smDhMGt1xwQt%2F-Mct4xojvkRVjuTHLebo%2F7.png?generation=1624455504324584\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-McxsHJ-7eorFb2__7wP%2F-McxtCsQ4bhNNYm1XD37%2F10.png?alt=media\&token=000a8ef1-c5dc-4819-ab18-68447c1fa848)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-McxsHJ-7eorFb2__7wP%2F-McxtTOXI-iAwFIVCEMB%2F11.png?alt=media\&token=e5e4b931-1b07-49f6-a668-22cf786f8738)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-Mct4sw2smDhMGt1xwQt%2F-Mct4xoncpcJxWTE1ApV%2F11.png?generation=1624455504323321\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-Mct4sw2smDhMGt1xwQt%2F-Mct4xopwE872nnS4q2y%2F13.png?generation=1624455504333846\&alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-McxsHJ-7eorFb2__7wP%2F-McxumiKtOwwifdYMIcZ%2F12.png?alt=media\&token=d0132dd3-414a-409f-9ed9-f72570b40190)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-McxsHJ-7eorFb2__7wP%2F-McxuztykohboBrDZ-ko%2Fimage013.png?alt=media\&token=fcf51254-fc15-444e-b433-fe85da6ce737)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-McxsHJ-7eorFb2__7wP%2F-McxvZwbtQWGc_9vPqCH%2F13.PNG?alt=media\&token=3c6c0eb9-b709-4a1a-9084-f364f9d3c601)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-Mct4sw2smDhMGt1xwQt%2F-Mct4xotaDkFMC1EJfuV%2F17.png?generation=1624455504318921\&alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-McxsHJ-7eorFb2__7wP%2F-McxvhGUYQTexxcDZKZN%2Fimage017.png?alt=media\&token=503423fe-e309-4b00-9cb9-3342ae0501f7)

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

The casing wear is expressed as depth in ether inches or mm depending on what units are selected for Diameter. The depth of wear indicates depth of the groove which will be worn into the side of the casing over a period of time.

* **Casing Wear Rotating**: This is the predicted wear on the casing when the string has 0 ROP. This calculation uses the rotating side force.
* **Casing Wear SO**: This is the predicted casing wear calculated using the reaming slack off. This calculation uses the slack off side force.

### 1.6.8 - Drill Pipe Fatigue SS Chart

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.

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


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH2BanXSDnQi0DHC9H%2F-MdH2qFLAbcbW3M6D2Fa%2F3.png?alt=media\&token=c75ebb50-665f-441b-86d7-e9d280dda7c6)

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)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH2BanXSDnQi0DHC9H%2F-MdH2tmObffnxPJAq3vB%2F4.png?alt=media\&token=955c050e-0e34-4972-b060-1cf2e58b4060)

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 Standoff Quick Start Guide

A guide to the Casing Standoff output within Innova Engineering's Torque & Drag Module.

This document will deal with the Casing Standoff calculation within Innova Engineering's Torque & Drag Module and will detail the steps required to run this calculation.

## 1.0 - Introduction

The casing standoff calculation uses the data input by the user and calculates either:

* The casing standoff based upon a given centralizer spacing entered by the user, or
* The required centraliser spacing to achieve the users desired standoff. Based upon the minimum step value selected by the user the optimum centraliser spacing will also be calculated.

## 2.0 - Setup

In order to run the casing standoff calculation, a Torque and Drag calculation needs to be run. For T\&D setup, refer to the Torque & Drag Quick Start Guide.

## 3.0 - Required Inputs

Over and above the standard Torque & Drag inputs, the following inputs are required.

In the **Tools Menu** select - **Standoff Optimisation Parameters**

* **Desired Standoff**: This is the standoff which will be calculated when **Optimise Standoff** is selected in the Torque and Drag section of the Engineering Parameters tab on the main user interface

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH33OXTJOWSYJsX0o2%2F-MdH3YYlMpmFRZfu5ufh%2F0.png?generation=1624874564894276\&alt=media)

* &#x20;**Min Step Value**: The minimum step value between one optimum spacing and the next. Engineering looks at the **Required Spacing** values which provide the **desired standoff**, and groups similar values (which land within the step range) together to provide a single **Optimum Spacing** output for each of these points. This is basically a smoothing parameter. Larger step values encompass more of the optimum spacing values providing more of a smoothing effect.
* **Max Spacing**: The spacing value above which no centralisers will be recommended. This affects the Centralizer Spacing Summary in the Standoff Summary Report.

![Min Step Value = 5                                                                Min Step Value = 100](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH33OXTJOWSYJsX0o2%2F-MdH4D5eMRsIGAYyNkKc%2F1.png?alt=media\&token=679615de-fa9a-468a-84ed-324a985750e4)

In the above charts the yellow line represents the **Optimum Spacing** and the pink line is the **Required Spacing** (achieves the **Desired Standoff** exactly). These examples show the difference in the Optimum Spacing when different minimum step values (5 and 100) are entered.

In the **Options Menu,** select **Torque and Drag Model**. If running bow spring centralizers, the user can select the option to **Include Bow Spring Force** within the torque and drag calculation. Note that if a bow spring force has been entered in the casing component details, this will be included in the casing standoff calculation regardless of what is selected here.

In the **Drill String, Well Geometry & Fluids** Tab, for each casing selected, in the component details, the user has the following centralizer inputs available:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH33OXTJOWSYJsX0o2%2F-MdH3YYpBbu6p1A-2_0x%2F4.png?generation=1624874564955003\&alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH33OXTJOWSYJsX0o2%2F-MdH3YYoncNixAHBEbzU%2F3.png?generation=1624874564958372\&alt=media)

* **Centralizer Spacing**: The distance between Centralizers. If centralisers are only run across a certain interval, then the casing should be entered as separate sections in the string. **NOTE**: this value is ignored when Optimised Standoff is selected. This is a **required** input for the casing standoff calculation when Optimise Standoff is not selected.
* **Centralizer OD**: The Outside Diameter of the Centralizer. For bowspring centralisers the OD input may be larger than the ID of the hole This is a **required** input for the casing standoff calculation.
* **Centralizer Length**: The length of the centralizer blade which contacts the wellbore. This input is **not used** in the standoff calculation but is used for hydraulics.
* **Centralizer Blade Width**: The width of the individual centralizer blades. This input is **not used** in the standoff calculation but is used for hydraulics.
* **Centralizer Blade Count**: The number of blades on the stabilizer. This is **not used** in the standoff calculation but is used for hydraulics.
* **Bowspring Restoring Force**: The Force exerted by a centralizer against the casing to keep it away from the wellbore wall. This input is used in the standoff calculation to determine how much the bow spring centralizer has deformed for a given side force. The centralizer will never compress more than the body OD. The higher the side force the more deformation of the centralizer. If nothing is entered for the restoring force it is assumed that the centralizer is rigid. In the scenario where the include bow spring force option is selected and the running force cell is left empty, this value will be used for the running force in the T\&D calculation of the PU, SO and reaming values.
* **Centralizer body OD**: The OD of the body of the centralizer. This is **not used** in the standoff calculation but is used for hydraulics. It is also used to calculate percentage compression of a bow spring stabiliser, which can affect the T\&D results.
* **Running Force**: The maximum force required to insert a centralizer into a specified wellbore diameter. This input is **not used** in the standoff calculation but is used for T\&D. If entered, this value will supersede the bowspring restoring force in the T\&D calculation. The running force will be applied to the pickup, slack-off and reaming values and will increase / decrease with the well bore size. Running force is not applied to the T\&D calculation until the compression of the centralizer is greater than 50% and will gradually increase as the compression increases from 50% to 100%.
* **Centralizer Type**: The user can manually enter the centralizer type and make / model here. This is not used in any calculations.
* **Running Force Restrict. ID**: The restriction ID that 100% of the running force will be utilised in T\&D calculation. When no value is entered here, the program will apply the running force to the T\&D calculations based on the the amount of compression experienced by the bowspring centralizer at any given point in the wellbore. The more the centralizer is compressed, the higher the percentage of the running force which is applied. If the user enters a value here, the program will apply the maximum running force over any part of the wellbore where the ID is the same or less regardless of the compression.For example, Running Force = 2.1klbs, Running Force Restrict. ID = 8”. Any points in the well geometry that this component passes through with an ID less than or equal to 8” will have 2.1klbs of running force applied to the T\&D calculation. Any part of the wellbore where the ID is greater than the value entered here will just be treated in the usual way.

In the Engineering Parameters tab the user can choose:

* **Optimise Standoff**: This will override the centralizer spacing selected in casing component details, and output the spacing required to achieve the desired standoff

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH5LGeIz-_URCuHdp_%2F-MdH69Ejn9PPr-S4Iv54%2F2.png?alt=media\&token=cf7b6845-7ce9-45cc-a85b-3113e81f429d)

**Point to Note**: Optimised Standoff and Desired Standoff (in the Standoff Optimisation Parameters dialog) are linked. When the user changes the value in either of these boxes, it auto updates in the other.

## 4.0 - Running the Calculation

In order to generate the Casing Stand Off output, the user must run a Torque & Drag calculation. To do this, select either the icon displayed below (low and high resolution icons), or select **Calculate - Torque and Drag.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH5LGeIz-_URCuHdp_%2F-MdH6RKDgMzV6rSBSrSX%2F3.png?alt=media\&token=38afe2c4-39ab-420e-8cf6-736e11119e99)

## 5.0 - Outputs

Once the calculation has been run, the **Stand Off summary** report can be viewed by selecting the TAD Results Menu and then  Standoff Summary from the available options. This report can be saved as a pdf.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH5LGeIz-_URCuHdp_%2F-MdH7SaX3cbb3zBsUvuX%2F5.png?alt=media\&token=145d578a-c892-41d6-a8e5-927ab4e83e33)

The Casing Standoff Chart is available by selecting the **TAD Results Menu - Snapshot Charts - Casing Standoff**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH5LGeIz-_URCuHdp_%2F-MdH7u3TBvk-aqpIJYTW%2F6.png?alt=media\&token=974b9d0f-b717-4af5-8fb6-ab8bdc9ba89d)

The report can also be generated by selecting "**File**" - "**Print Reports**” or selecting the icon on the toolbar.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH5LGeIz-_URCuHdp_%2F-MdH8SidOsmZPXKBn9rT%2F7.png?alt=media\&token=5cdc93a6-8df8-49ef-a1bf-bbc232d5e66b)

&#x20;The three report options for Casing Stand Off can be found on the T\&D tab at the bottom right:

* **Standoff Summary**: This is the Report
* **Standoff Chart**: A graphical representation of the results
* **Standoff Data**: Base data used to generate the plots.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH5LGeIz-_URCuHdp_%2F-MdH91Dx8KBMTlLUMcHt%2F8.png?alt=media\&token=477ef841-9441-4c40-8933-9085422f5440)

The report can be generated either as **excel** or **pdf**.

### 5.1 – Standoff Summary Report

The standoff summary report is generated at the click of a button and contains the following:

* Centralizer spacing summary
* Drill string summary
* Centralizer stand-off results
* Standoff chart
* Side forces / centralizer forces chart
* Hookload chart

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH9D0kDpaMk7CXuVDQ%2F-MdHAn92_n1IJaUF8sAf%2F11.png?alt=media\&token=e712f4df-42d6-4a65-8d4b-5754d3acab44)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH9D0kDpaMk7CXuVDQ%2F-MdHAfEKDyn_L9BkQjL8%2F10.png?alt=media\&token=dfba1af5-8d0d-40f9-b90d-a72c0c8465bd)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH9D0kDpaMk7CXuVDQ%2F-MdHAW-lmfe1c0jtqJLj%2F9.png?alt=media\&token=3a530f2a-edf6-4c75-aa6c-f6875fe9fa4f)

### 5.2 - Casing Standoff Chart

The casing standoff chart is a snapshot chart which provides outputs for each point in the string from surface to the calculated depth.

#### 5.2.1 - Without Optimised Standoff

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH33OXTJOWSYJsX0o2%2F-MdH3YZ2JVi0VXRXhKha%2F18.png?generation=1624874564968933\&alt=media)

If **Optimise Standoff** has **NOT** been selected when the torque and drag calculation is run, the standoff chart will look like the above.

* **Inc**: Inclination
* **Cent OD**: Centralizer Outside Diameter
* **Deflection Mid Joint**: Deflection of the casing between 2 centralizers.
* **Deflection Centralizer**: Deflection of casing at the centralizer.
* **Standoff Mid Joint**: This is calculated as follows (1 – (**Deflection Mid Joint** / ((Hole ID – Casing OD)/2))) \* 100. It is effectively the percentage deflection from well bore centre. If the casing is centralised perfectly the standoff is 100%
* **Standoff Centralizer**: The Percentage Standoff at the Centralizer. This is calculated as follows (1 – (**Deflection Centralizer** / ((Hole ID – Casing OD)/2))) \* 100.
* **Cent Spacing**: The centralizer spacing as entered by the user in the component details section of the drill string editor (This line will **NOT** be present if Optimise Standoff is selected in the Torque and Drag section of the Engineering Parameters tab on the main user interface).
* **Restoring Force**: The restoring force of the bow spring centralizer which has been entered in the component details section of the drill string tab.
* **Running Force**: The running force of the bow spring centralizer which has been entered in the component details section of the drill string tab.
* **Side Force**: The side force exerted on the casing.

#### 5.2.2 - With Optimised Standoff

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH33OXTJOWSYJsX0o2%2F-MdH3YZ3ZOEt1XnoZ93D%2F19.png?generation=1624874564951917\&alt=media)

If **Optimise Standoff** has been selected (in the above this has been set at **60%**), when the torque and drag calculation is run, the standoff chart will have the addition of an Optimum Spacing line, and the Centralizer Spacing line becomes the Recommended Spacing line.

* **Rec Spacing**: Recommended Spacing, calculated based on the Optimise standoff value (This line will **NOT** be present if Optimise Standoff is not selected)
* **Opt Spacing**: This is the optimum spacing which applies the maximum step value to the Recommended Spacing (This line will **NOT** be present if Optimise Standoff is not selected).

All the other lines described in **Section 5.1.1 - Without Optimised Standoff**, are also available to be displayed in this chart if required.


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH1WqiYRWz-Icxo1hC%2F-MdH1dtUT9pz_bm9-BJ0%2F0.png?generation=1624874065873991\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH1WqiYRWz-Icxo1hC%2F-MdH1dtVBwhsZdyx9tDb%2F1.png?generation=1624874065876544\&alt=media)

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


# Cementing How To Guide

A guide to the cementing module within Innova Engineering.

This document describes the cementing module within Innova Engineering and details the steps required to correctly utilise its functionality.

## 1.0 – Getting Started

This document describes the cementing module within Innova Engineering and details the steps required to correctly utilise its functionality.

## 2.0 – Setup

* **Units**: Ensure that all units are correctly selected, based on requirements.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpAs29aF37HY2Un%2F0.png?generation=1624881377912003\&alt=media)

* **Options Menu – Cementing**: The default flow rate in the Cementing tab is barrels per minute (**bbls/min**). This option allows the user to “Use flow units as pump rate”, which means the flow rate used in the cementing tab will match whatever the user has selected as the flow units from the units menu. This is useful when using the cementing section to simulate pumping pills etc.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpBwkKWyQX6quiO%2F1.png?generation=1624881377913935\&alt=media)

## 3.0 – Required Inputs

To utilise the cementing modules functionality, the following inputs are required.

### 3.1 - Drill string, Well Geometry & Fluids Tab

* **Drill String**: Required inputs are component, description, OD, ID, TJ OD, TJ ID and length. Input the assembly as accurately as possible including the drill pipe to surface (note, for the last component e.g. DP to surface, the user does not have to input the exact length as the program will do this automatically based on the calculation depth. Inputting a nominal value of 10 is fine). Note that once a component type has been selected from the dropdown menu, it is possible to right click on the line and choose "***select from Library***", which will open the components library. The user can then select the appropriate component and select the option to insert it directly into the drill string grid.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpC_WOFiRCG9IQ_%2F2.png?generation=1624881377960808\&alt=media)

* **Bit / Float TFA**: If a float or bit has been included in the assembly, then it is important to enter the relevant TFA as this is required to calculate the pressure drop across this component, which is used in the **pump pressure** calculation. This is entered in the bit, casing or liner component details section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpDzSK9j30zlE6i%2F3.png?generation=1624881377919992\&alt=media)

* **Well Geometry**: Input casing, liner, riser and open hole details including depths and ID's. For open hole, the ID is the same as the OD. Note that the user should only enter the well geometry which is relevant for the section in question and should not enter the entire casing string here.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpErZC8OizcLk3-%2F4.png?generation=1624881377921950\&alt=media)

* **Fluid Properties:** Input mud weight, PV and YP. These inputs relate to the fluid in the wellbore prior to starting the cement job.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpFZC8V3Qyq9_xw%2F5.png?generation=1624881377915915\&alt=media)

### 3.2 - Surveys Tab

**Survey Selection**: Cementing calculations will be run using plan or survey data entered in the **Survey Tab** on the main user interface.

* If there are well plan surveys and no actual surveys, the program will automatically use the well plan.
* If there are actual surveys and no well plan surveys, the program will automatically use the actual.
* If there are both well plan and actual surveys the program will use whatever is deeper.

Data is input as measured depth, inclination and azimuth in both the Actual Surveys and Well Plan sections, and the program will generate the rest of the numbers using whichever survey calculation method has been selected (Minimum Curvature Default). Cementing calculations **are not** run against surveys input in the RAW surveys table. The user can either enter the plan or surveys manually, import them or copy and paste the data directly into the cells.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpGLKBTvwpb8RyD%2F6.png?generation=1624881377959864\&alt=media)

### 3.3 - Cementing Tab

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpHBsVudm_Mt-E8%2F7.png?generation=1624881378002515\&alt=media)

#### 3.3.1 – Volumes

This section displays the various volumes, capacities and displacements of the drill string and the annulus.

The top of this section details the different capacities of the drill string components. These components are taken directly from the drill string entered in the drill string tab, and the capacities are automatically calculated based on the dimensions (OD & ID) associated with these components. The annular capacities are detailed for the components, based on each of the lines entered in the Well Geometry section of the drill string tab. **NOTE**: A String Depth **MUST** be entered for this section to display correctly.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdHVnJLA0gm8hUGoNqU%2F-MdI1Am62qvoZwGomqgO%2F1.png?alt=media\&token=12be6096-567c-46f4-99af-1358118e126b)

The middle part of this section shows the various capacities, volumes and displacements for the well. **NOTE**: A String Depth **MUST** be entered for this section to display correctly.

The lower part of this section is the most important as the inputs here affect the entire cementing calculations.

* **String Depth**: Depth of the string when performing the cement job. The calculation will not run without a value entered here.
* **Displacement Type**: Select **Open Ended** or **Close Ended**. This affects the Displacement and Total Displacement calculated values.
* **Flow Rate**: Flow rate of cement job. This is used to calculate the **Top Down, Bottoms Up** and **Full Circulation** values. This input is not required to run the cementing calculation, as the pump rate for this is entered in the pumping schedule section.
* **Pump Output**: Volume pumped per stroke. Pump efficiency should be factored into this input i.e. if the book output is 0.1bbl/stroke and the pump is 95% efficient, then output should be entered as 0.095bbl/stroke. This input is essential as it is required for calculating the number of strokes in the Pumping Schedule section.
* **Stroke Rate:** This cell auto calculates based on the values entered for flow rate and pump output.
* **Hydraulics Model**: Select from **Bingham, Power Law, Herschel Bulkley** or **Robertson Stiff**. This affects the calculated Annular Pressure, Pump Pressure and ECD values in the Cementing Results dialog.

#### 3.3.2 - Cement Volumes

This section allows the user to quickly calculate the volumes required for the cementing operation.

Row 1 should contain the first fluid to be pumped and the user can enter the required top, and the bottom will be automatically populated. The top and bottom depths of the fluid represent where they will be in the Annulus at the end of the cementing operations. The user can then enter as many additional lines as required. It should be noted that the bottom depth of the fluid in the last row will always be equal to the **String Depth** value input in the Volumes section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpJnaEoFgaj1wNz%2F9.png?generation=1624881377916042\&alt=media)

The user can also enter the desired excess and the volume column will update automatically to reflect this excess percentage.

#### 3.3.3 - Pumping Schedule

Once the Cement Volumes and Cement Job Calculation sections have been input, the user can select **Create**, which will populate the Pumping Schedule table, with the description and calculated volumes from the Cement Volumes section. Note that this also considers the data input in the **Cement Job Calculation** section. It is also possible to complete this section manually. In order for the schematic to be represented correctly in the results dialog, excess volume should not be included in this section.

If the **Include Spacer** box is checked and then **Create** is selected, row one of the table will be created for a spacer, but the volume cell will need to be populated manually by the user. If the user has included a spacer in the cement volumes section, then the include spacer box should not be checked.

The **Use Rheometer Readings** check box toggles the Pumping Schedule table between PV, YP and 600 – 3 rpm dial reading inputs.

The user should fill in the Description, Volume, Wt, Pump Rate, and rheology values for each row. These inputs affect the calculated Annular Pressure, Pump Pressure and ECD values in the Cementing Results dialog.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpKxJutdY1eZR8N%2F10.png?generation=1624881377915762\&alt=media)

#### 3.3.4 - Cement Job Calculation

For conventional cement jobs the user should enter the **Shoe – Float Distance**. The shoe track capacity will be automatically calculated.

If cementing with a stinger, the user should check the **Cementing with inner string** box and enter the **Description, OD, ID** and **Length** of the stinger string. The capacity and total capacity of the inner string will be automatically calculated.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpLOtGjSUlDR_Ob%2F11.png?generation=1624881377915832\&alt=media)

Once the cementing tab has been completed, selecting Calculate, opens the **Cementing Results** Dialog.

## 4.0 – Cementing Data Input Sequence

It is suggested that data is input in the following order to increase input efficiency. This is, however, just a guide and the user can enter the data in whatever sequence they wish.

1. Ensure units are correctly selected, including the cementing flow units in the Options menu.
2. Input data in the Drill String table. Input the component, description, OD, ID, length and TJ OD / ID if applicable (Drill String, Well Geometry & Fluids Tab).
3. Input any relevant TFA details in the Component details table (Drill String, Well Geometry & Fluids Tab).
4. Input the Well Geometry (Drill String, Well Geometry & Fluids Tab).
5. Input the drilling Fluid Properties (Drill String, Well Geometry & Fluids Tab).
6. Input the survey data into the Well Plan or Actual Surveys table (Surveys Tab).
7. Input the String Depth (Cementing Tab).
8. Select the Displacement Type (Cementing Tab).
9. Input the Flow Rate (optional) (Cementing Tab).
10. Input the Pump Output (Cementing Tab).
11. Select the Hydraulics Model (Cementing Tab).
12. Input the Description, Top and Excess % for each fluid in the Cement Volumes table (Cementing Tab).
13. Input the Shoe – Float Distance (Cementing Tab).
14. Add cementing inner string Description, OD, ID and Length if applicable (Cementing Tab).
15. If a spacer is being included and was not added in the cement volumes section check the Include Spacer checkbox (Cementing Tab).
16. Select the Create button in the Pumping Schedule section (Cementing Tab).
17. Input the Weight (Wt), Pump Rate, fluid rheology and spacer volume (if applicable) data (Cementing Tab).
18. Select the Calculate button to run the cementing calculation and open the Cementing Results dialog (Cementing Tab).

## 5.0 – Running the Calculation

Once the user has entered all the required inputs, the user selects **Calculate** from the Cement Job Calculation section. This runs the cementing calculation and opens the cementing results dialog.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpMOcMX9kaxEH9P%2F12.png?generation=1624881377959374\&alt=media)

## 6.0 – Cementing Results Dialog

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpN0bxn5JX4ziFh%2F13.png?generation=1624881377984761\&alt=media)

The Cementing Results dialog displays all the information and results relevant to the cementing module. By utilising the scroll bar at the bottom of the dialog the user can view the three charts at different stages of the cement job.

### 6.1 – Cementing Schematic

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpO6DkTAmwd4yjN%2F14.png?generation=1624881377934046\&alt=media)

This is a visual representation of the well geometry, string and fluids at a given stage in the cement job, dictated by the position selected on the scroll bar. The values used to generate this schematic (MD, component OD & ID’s and well geometry OD & ID’s) are taken from the values entered in the **Drill String, Well Geometry and Fluids Tab**. The fluid labels can be toggled on or off by selecting **Chart Options** and checking or unchecking **Show Schematic Fluid Labels**.

* Changes in well geometry are marked by a label and dashed line.
* Areas out with the fluid flow path are white.
* Sea water is dark blue
* Drilling mud is brown.
* Spacer is light blue.
* Lead cement is dark grey.
* Tail cement is light grey.
* Displacement fluid is a variable colour.

### 6.2 – Pumping Schedule

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpP6_E5jt_J4zdn%2F15.png?generation=1624881377941312\&alt=media)

The Pumping Schedule chart depicts:

* The annular pressure at the string depth entered in the volumes section
* The equivalent circulating density (ECD) at the string depth entered in the volumes section
* The pump pressure at surface at a given stage in the cement job
* The Flow Rate

All the above outputs are dictated by the position selected on the scroll bar.

The X-axis can be toggled to display either Elapsed Time or Strokes by selecting **Chart Options** and checking or unchecking **X Axis – Strokes**.

### 6.3 – Cementing Results Dialog Scroll Bar

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdHVnJLA0gm8hUGoNqU%2F-MdI1cm1G5UGr6KWSxng%2F2.png?alt=media\&token=345a283d-20e4-4b65-9013-86beb1beb3c2)

The position of the slider on the scroll bar dictates the stage of the cement job depicted on the Cementing Schematic, Pumping Scheldule and ECD Snapshot. The user can click the play button for the slider to commence movement at a specific speed. This speed can be adjusted using the **+** and **–** keys to speed up and slow down the slider progression respectively. The user can then select the pause button to stop the slider at any point. The slider can also be manually dragged to any point in the scroll bar by the user.

### 6.4 – ECD Snapshot

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpRQ31cQm25nXEl%2F17.png?generation=1624881377964238\&alt=media)

The ECD Snapshot chart depicts the equivalent circulating density and the annular velocity, across all depths from surface to the string depth, at a given stage in the cement job, dictated by the position selected on the scroll bar.

The right-hand side of the chart shows the flow regime across all depths from surface to the string depth, at a given stage in the cement job, dictated by the position selected on the scroll bar. Red is Laminar Flow and Green is Turbulent.

Additionally, markers display the respective depths of the top of the various fluids in the annulus and any changes in the well geometry.

## 7.0 – Outputs

Within the Cementing Results dialog, the user can output the following via the **file** menu:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpS3hIejwqzI0ZV%2F18.png?generation=1624881377913970\&alt=media)

* PDF Cementing Report
* Excel Cementing Report
* Export Data

### 7.1 – Print PDF Report

The user selects **File > Print PDF Report**. This generates a report which can be saved to pdf format.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpTiuZUC49_tONh%2F19.png?generation=1624881378013791\&alt=media)

The report includes all the relevant data used in the cementing calculation and the charts displayed within the Cementing Results dialog, **as they appeared when the report was created**.

### 7.2 – Print Excel Report

The user selects **File > Print Excel Report**. This generates a report which can be saved to excel format.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdHVnJLA0gm8hUGoNqU%2F-MdI22SgkBtwnA4P7eBV%2F3.png?alt=media\&token=79d5af54-e0c0-4f85-ae2d-e842646e2163)

The report includes all the relevant data used in the cementing calculation and the charts displayed within the Cementing Results dialog, as they appeared when the report was created. These charts are allocated their own sheet within the excel document.

### 7.3 – Export Data

This option allows the user to export the data used to generate the Pumping Schedule and ECD Snapshot Charts.

## Appendix A – Context Menu

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpVGZEo-T6yDwOv%2F21.png?generation=1624881377970820\&alt=media)

The context menu is available in every plot by right clicking anywhere on the plot. This allows the user to change certain aspects of the plot based on their requirements.

**Viewing Style** – Allows the user to select the desired Chart style.

**Border Style** – Allows the user to select the desired Border style of the chart.

**Font Size** – Allows the user to select the desired font size, which will affect all fonts on the chart including title and axis labels. Large, Medium or Small.

**Plotting Method** – Allows the user to select the way the line is plotted: Point, Line, Bar, Points + Line, Spline Area.

**Data Shadows** – Allows the user to select between off, shadow and 3D.

**Grid Options** – Allows the user to change the grid options in the chart.

**Mark Data Points** – Adds the data points relating to the data labels

**Undo Zoom** – Resets the zoom on the chart. Pressing the Z button has the same effect.

**Maximise** – Maximises the chart to fill the screen. Escape button exits this view.

**Customization Dialog** – Opens a dialog with more user definable chart options.

**Export Dialogue** – Allows the user to Export the chart using multiple image formats: EMF, WMF, BMP, JPG and PNG. The user has 3 options:

* **Clipboard**: exports directly to clipboard, allowing images to be quickly added to word, excel & PowerPoint documents
* **File**: Creates an image file of the chart which can be used on its own or imported into any suitable document
* **Printer**: Sends the chart to the printer

The user can also choose the relevant Width, Pixels and DPI to use for the export. For Clipboard and File options, Pixels is the only available selection. When Printer is selected, the Millimetres, Inches and Points options become available to select.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHT32esyMhRB5LslLo%2F-MdHTXpWoATEt4ZKw3QC%2F22.png?generation=1624881377975557\&alt=media)


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH0hhPrKhx9b91SLWk%2F-MdH0xX8hN8VnNKb-MN9%2F0.png?generation=1624873884263211\&alt=media)


# 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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH-8hS-oxDyqcS3zGP%2F-MdH-LT2rJDP3Voa4y7x%2F0.png?generation=1624873462245789\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH-8hS-oxDyqcS3zGP%2F-MdH-LT3FpnCD-LhnBdn%2F1.png?generation=1624873462245612\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdH-8hS-oxDyqcS3zGP%2F-MdH-LT4w_C2CBrxxKKt%2F2.png?generation=1624873462245778\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH-8hS-oxDyqcS3zGP%2F-MdH0Y9ospD4GVVv-IxG%2F2.png?alt=media\&token=f20e4a5f-8d6d-4341-8b0b-39ca1da5553a)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdH-8hS-oxDyqcS3zGP%2F-MdH0Jr2s_Cz2Y3zuy2b%2F1.png?alt=media\&token=67f90546-098c-4f2b-ba1a-a3b820576cfc)

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.


# Jar Placement Guide

A guide to the jar placement module within Innova Engineering.

This document describes the jar placement module within Innova Engineering and details the steps required to correctly utilise its functionality.

## 1.0 – Getting Started

This document describes the jar placement module within Innova Engineering and details the steps required to correctly utilise its functionality.

### 1.1 – Units

* **Units**: Ensure that all of the units are correctly selected, based on requirements.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9552OlFEiClo9Y%2F0.png?generation=1624876853383760\&alt=media)

### 1.2 – Jar Placement Data Input Sequence

It is suggested that data is input in the following order to increase input efficiency. This is however, just a guide and the user can deviate from this sequence should they wish.

1. Input data in the Drill String table.
2. Input data in the Components Details table for each component.
3. Input the Well Geometry
4. Input the Mud Weight
5. Input the survey data into the Well Plan or Actual Surveys table.
6. Input the Flow Rate
7. Input the Calc Depth in the Torque and Drag section
8. Input WOB Rotate
9. Input Block Weight
10. Input Overpull if applicable
11. Select Tools > Jar Placement

### 1.3 – Required Inputs

To utilise the jar placement functionality, the following inputs are required.

**Drill string, Well Geometry & Fluids Tab**

* **Drill String**: Input the assembly as accurately as possible including the drill pipe to surface (note, for the last component e.g. DP to surface, the user does not have to input the exact length as the program will do this automatically based on the calculation depth. Inputting a nominal value of 10 is fine). Note that once a component type has been selected, it is possible to right click on the line and choose "***select from Library***", which will open the components library. The user can then select the appropriate component and insert it directly into the drill string grid.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdHDI1PZuJ1cI5U48lA%2F-MdHFOQ7cGU3uHA9hQ-n%2F1.png?alt=media\&token=015c745a-6bd5-4b01-8f11-f24a767a5015)

* **Bit TFA**: The bit TFA is required to calculate the pressure drop at the bit, which is used in the **pump open force** calculation. This is entered in the bit component details section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH97bGi4VuvsMbcS%2F2.png?generation=1624876853406527\&alt=media)

* **Mandrel Area**: The mandrel area of the jar. Sometimes referred to as the pump open area. Used when calculating the **pump open force**. This needs to be input in the jar component details section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH98yGwfTk9cHUaB%2F3.png?generation=1624876853489660\&alt=media)

* **Stroke Length**: The Free Stroke length of the jar. The stroke length of the jar controls the amount of time it takes for the hammer to hit the anvil, the longer the stroke the more time the hammer has to accelerate. Typical stroke lengths vary between 7 – 12”. It should be noted that the stroke length reported by the manufacturers is usually the total stroke length and should be halved for the purposes of this calculation. This needs to be input in the jar (and accelerator if included) component details section.
* **Well Geometry**: Input casing, liner, riser and open hole details including depths and ID's. For open hole, the ID is the OD of the bit. Note that the user should only enter the well geometry which is relevant for the section in question and should not enter the entire casing string here. The open hole MD value entered here, is the value used for **Hole Depth** in the jar placement dialog, which dictates the deepest bit measured depth used in the neutral point results.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH99UMiyqmLv0ngM%2F4.png?generation=1624876853391721\&alt=media)

* **Mud Weight:** This is required for calculating the **buoyancy factor**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9AsB_ETMeWxr23%2F5.png?generation=1624876853400799\&alt=media)

**Surveys Tab**

* **Survey Selection**: Jar placement calculations will be run using plan or survey data entered in the **Well Plan** table. In the absence of data in the Well Plan table, data from the **Actual Surveys** table will be used. Data can be input as measured depth, inclination and azimuth in both the Actual Surveys and Well Plan sections, and the program will generate the rest of the numbers using whichever survey calculation method has been selected (Minimum Curvature Default). Jar placement **cannot** be run against surveys input in the RAW surveys table. Either enter the plan or surveys manually, import them or copy and paste the data directly into the cells.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9BAjbeuiZXXsPy%2F6.png?generation=1624876853399654\&alt=media)

**Engineering Parameters Tab**

* **Flow rate**: If manual flow increment is selected, the first flow rate entered will be used in the calculation. If the automatic range is selected, the flow rate entered in line 3 will be used. The flow rate is used in the **Pump Open Force** calculation.
* **Torque and Drag Calc Depth**: The value input here will dictate the bit measured depth used in the **Jarring Results** table.
* **WOB Rotate**: The value input here will display in the WOB cell in the Jar Placement dialogs **Drilling Data** section. This is used in the **neutral point calculation**.
* **Block Weight**: Block weight entered here will be added to the values in the **HKLD Fire** column in the **Jarring Results** section.
* **Overpull**: If no overpull is specified the jarring results will be calculated for an overpull up to 500 klbs (250 Tons). If an overpull is specified the jarring results will be calculated up to the overpull value x 2

## 2.0 – Running the Calculation

Once the user has entered all the required inputs, the jar placement calculations are carried out automatically when the user opens the Jar Placement dialog via **Tools > Jar Placement** or selecting the icon from the toolbar.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdHDI1PZuJ1cI5U48lA%2F-MdHILLJjsK7pJkw3FTH%2F2.png?alt=media\&token=85850380-a17e-4cc5-a2e0-0be7703cf8fc)

## 3.0 – Jar Placement Dialog

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9EVEep3zzMVF5Z%2F9.png?generation=1624876853505602\&alt=media)

The Jar Placement dialog displays all the information and results relevant to the jar placement module.

### 3.1 - Drill String

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9F6_HQjP3Devwh%2F10.png?generation=1624876853452932\&alt=media)

Non-editable display of the drill string entered in the Drill String section of the main UI. Jars are highlighted in green and accelerators in orange.

### 3.2 - Jar Data

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9GlfRckExigEib%2F11.png?generation=1624876853444743\&alt=media)

Non-editable display of the jar and accelerator component details entered in the Drill String section of the main UI. Only **Stroke** and **Mandrel Area** affect the jar placement results. All other cells are for reference only.

* **Stroke**: This is the free stroke length and is used in the impact and impulse calculations.
* **Mandrel Area**: Is used in the pump open force calculation.

### 3.3 - Drilling Data

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9H2VZzD0X7zAvk%2F12.png?generation=1624876853460972\&alt=media)

Non-editable display of drilling data used in the jar placement calculations.

* **Hole Depth**: Value taken from the deepest MD entered in the Well Geometry section of the main UI. Dictates the deepest depth that the neutral point calculation is run.
* **Mud Weight**: Value from the Fluid Properties, Mud Weight cell. Used in the buoyancy factor calculation.
* **Buoyancy Factor**: Calculated using the below formula.

**BF = 1 – (MW/k)**

Where BF is buoyancy factor, MW is mud weight and k is a (mud weight unit dependant) constant. Buoyancy factor is used in the neutral point and jarring results calculations.

* **Flow Rate**: Value from the Engineering Parameters tab. If manual flow increment is selected, the first flow rate entered will be used in the calculation. If the automatic range is selected, the flow rate entered in line 3 will be used. Used in the pump open force calculation.
* **WOB**: Value from Torque and Drag sections WOB Rotate cell. Used in the neutral point calculation.
* **Hole Size**: Value from Well Geometry, Open Hole, ID cell. Used in the **Jar Size Check** and **Jarring Results** calculations.
* **Inclination at Bit**: Interpolated inclination from the survey listing at the **Hole Depth**. Used in the **Weight Below Jar BHL (Air)/(Mud)** calculation.

### 3.4 – Jar Checklist

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9IMHpV7pP1rTAm%2F13.png?generation=1624876853438144\&alt=media)

Non-editable display of calculated data.

* **Jar Size Check**: A pass or fail check based upon the jar size and the hole size. This is to confirm that the correct OD jar has been chosen for the given hole size. Note that a Fail in this cell has **NO** effect on the jarring calculations, which will be run regardless. All this cell does is highlights to the user if the size of the jar selected is suitable for the hole size based on a checklist which can be fully edited by the user. This is a warning and no more.
* **Jar is in**: **TENSION** or **COMPRESSION**. Based upon the input data, this cell shows whether the jar is currently in tension or compression.
* **Weight Below Jar Vertical (Air)**: The weight below the jar in a vertical well in the absence of a drilling fluid. Calculated by the sum of the component weights (input in the Drill String section of the main UI) beneath the jar.
* **Weight Below Jar Vertical (Mud)**: The weight below the jar in a vertical well, taking in to account the buoyancy effect of the drilling fluid. Calculated by multiplying the Weight Below Jar Vertical (Air) by the buoyancy factor.
* **Weight Below Jar BHL (Air)**: The weight below the jar at the bottom hole location (the bit depth) in the absence of a drilling fluid. Calculated by multiplying the Weight Below Jar Vertical (Air) by the cosine of the Inclination at Bit.
* **Weight Below Jar BHL (Mud)**: The weight below the jar at the bottom hole location (the bit depth), taking in to account the buoyancy effect of the drilling fluid. Calculated by multiplying the Weight Below Jar Vertical (Mud) by the cosine of the Inclination at Bit.
* **Pump Open Force**: The force generated by the flow of drilling fluid through the BHA that acts to open the jar. Calculated by the bit pressure loss multiplied by the Mandrel Area.
* **Neutral Point**: The MD of the point in the drill string that transitions from compression to tension based upon the input data. This is directly affected by the WOB.
* **Jar to Bit**: The distance from the top of the jar to the face of the bit.
* **Accelerator to Bit**: The distance from the top of the accelerator to the face of the bit.

### 3.5 – Pump Open Force Chart

The pump open force chart displays the pump open force versus the flow rate. The green vertical line depicts the currently selected flow rate.

For details on adjusting the chart settings see **Appendix A – Context Menu**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9Jz4NDRlP-XqWr%2F14.png?generation=1624876853455379\&alt=media)

### 3.6 – Neutral Point Road Map

The neutral point chart is a neutral point road map, which shows the WOB to avoid at every depth along the well path. The centre of the red area represents the neutral point. The red section represents a ±5% safety margin, and the orange area represents a ±10% safety margin. This gives the personnel on the job a WOB range to avoid for any given MD along the entire well path. Note that the 5% and 10% margins are the default values, but these can be changed based on user requirements via the **settings menu**.

For details on adjusting the chart settings see **Appendix A – Context Menu**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9KuSrFfr-8qlaJ%2F15.png?generation=1624876853437674\&alt=media)

### 3.7 – Jarring Up Chart

The jarring up chart displays the calculated jarring up impulse and impact at the jar, versus hook load.

For details on adjusting the chart settings see **Appendix A – Context Menu**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9Lvul2kkKO5Xlf%2F16.png?generation=1624876853436557\&alt=media)

### 3.8 – Jarring Down Chart

The jarring down chart displays the calculated jarring down impulse and impact at the jar, versus hook load. The area shaded in red indicates the hook load range in which the string is modelled as being helically buckled. The buckling will occur at some point in the drill string above the jar and simply indicates that it may not be possible to transmit the required weight to cock / fire the jar. This range is indicated in the jarring results table by lines highlighted in Orange.

For details on adjusting the chart settings see **Appendix A – Context Menu**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9MpMQDCZoEbkey%2F17.png?generation=1624876853484157\&alt=media)

### 3.9 – Jarring Results Table

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9Now58Nf3zf-0U%2F18.png?generation=1624876853479195\&alt=media)

The jarring results table showing the results of the jarring calculations. These results are the source of the data that is plotted in the **Jarring Up** and **Jarring Down** charts. Note, that in the jarring down section of the results table, any lines which are highlighted in orange, indicate the hook load range in which the string is modelled as being **helically** buckled. The buckling will occur at some point in the drill string above the jar and simply indicates that it may not be possible to transmit the required weight to cock / fire the jar. This range is represented in the jarring down chart by the red shaded area.

* **HKLD @ Fire**: The surface hook load used to fire the jar This takes in to account the string weight and pick up forces which need to be overcome before the jar starts to have overpull applied. The calculation assumes **CHFF 0.15** and **OHFF 0.25**.
* **OP @ Surf**: The overpull registered at surface for a given hook load.
* **OP @ Jar**: The overpull at the jar for a given hook load. This takes in to account the effects of drag.
* **Wt @ Surf**: The weight registered at surface for a given hook load.
* **Wt @ Jar**: The weight at the jar for a given hook load. This takes in to account the effects of drag.
* **Impact @ Jar**: The impact at the jar resulting from the jar firing when the associated hook load is registered at surface. Calculated utilising the length of the drill collars above the jar, the stroke length of the jar, the overpull/weight applied and the drag in the hole.
* **Impulse @ Jar**: The impulse at the jar resulting from the jar firing when the associated hook load is registered at surface. Calculated as the integral of impact force with respect to time.
* **Impact @ SP**: The impact at the stuck point (the bit) resulting from the jar firing when the associated hook load is registered at surface. Calculated utilising the length of the drill collars above the jar, the stroke length of the jar, the overpull/weight applied, the drag in the hole and the distance between the jar and the stuck point.
* **Impulse @ SP**: The impulse at the stuck point (the bit) resulting from the jar firing when the associated hook load is registered at surface. Calculated as the integral of impact force with respect to time.

## 4.0 – Outputs

Within the Jar Placement dialog, the user can output the following via the **File Menu**:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9Ois1Pkyr-iyc6%2F19.png?generation=1624876853436964\&alt=media)

* Jar placement report
* The jarring results table data
* Any of the charts present.

### 4.1 - Print Report

The user selects **File > Print Report**. This generates a report which can be saved to pdf format.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9PMGutkaWHMc8h%2F20.png?generation=1624876853460909\&alt=media)

The report includes all the data and charts displayed within the Jar Placement dialog.

### 4.2 - Print Results Grid to Text File

Exports the data in the Jarring Results table in a **.txt** file format.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9QrvbyycQbYunu%2F21.png?generation=1624876853472392\&alt=media)

### 4.3 - Export Charts

Additionally, the user can export any of the charts individually using the right click context menu and selecting **Export Dialog**. For more information on exporting charts see **Appendix A – Context Menu**.

## 5.0 – Settings Menu

The settings Menu gives the user access to the Jar Placement Settings dialog.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9RkfLtvyHlzxvs%2F22.png?generation=1624876853402195\&alt=media)

The Jar Placement Settings dialog is where the user can adjust the jar check size and neutral point chart safety factors.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9Sj3KS_372Srlr%2F23.png?generation=1624876853404461\&alt=media)

**Jar Check Size**: The user can enter the jar sizes and the relevant minimum and maximum hole sizes the jars are suitable to be run in. This information will be displayed on the main Jar Placement dialog in the jar checklist section. These sizes will also be used by the program for the **Jar Size Check**, where the user will be informed if the jar they have entered into the drill string is suitable, based on the hole size selected.

**Neutral Point Safety Factors**: The safety factors entered here are represented on the neutral point chart on the main Jar Placement dialog.

* Safety factor 1 is represented by the red highlighted area
* Safety factor 2 is the orange area displayed on either side of the neutral point line.

The default values are 5% and 10% respectively but can be changed here, as per the user’s requirements.

**Impulse/Impact Charts X Axis Hookload**: When checked, the X axis of the Jarring Up and Down charts will represent the Hookload at surface. If unchecked, the X axis will represent the relevant Overpull (Jarring Up) and Slack Off (Jarring Down) values.

## Appendix A – Context Menu

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9TvvMyGhxlXMvm%2F24.png?generation=1624876853437274\&alt=media)

The context menu is available in every plot by right clicking anywhere on the plot. This allows the user to change certain aspects of the plot based on their requirements. It should be noted that almost all of the functions available in this menu, are also available in the **Chart Properties**.

**Viewing Style** – Allows the user to select the desired Chart style.

**Border Style** – Allows the user to select the desired Border style of the chart.

**Font Size** – Allows the user to select the desired font size, which will affect all fonts on the chart including title and axis labels. Large, Medium or Small.

**Plotting Method** – Allows the user to select the way the line is plotted: Point, Line, Bar, Points + Line, Spline Area.

**Data Shadows** – Allows the user to select between off, shadow and 3D.

**Grid Options** – Allows the user to change the grid options in the chart.

**Mark Data Points** – Adds the data points relating to the data labels

**Undo Zoom** – Resets the zoom on the chart. Pressing the Z button has the same effect.

**Maximise** – Maximises the chart to fill the screen. Escape button exits this view.

**Customization Dialog** – Opens a dialog with more user definable chart options.

**Export Dialogue** – Allows the user to Export the chart using multiple image formats: EMF, WMF, BMP, JPG and PNG. The user has 3 options:

* **Clipboard**: exports directly to clipboard, allowing images to be quickly added to word, excel & PowerPoint documents
* **File**: Creates an image file of the chart which can be used on its own or imported into any suitable document
* **Printer**: Sends the chart to the printer

The user can also choose the relevant Width, Pixels and DPI to use for the export. For Clipboard and File options, Pixels is the only available selection. When Printer is selected, the Millimeters, Inches and Points options become available to select.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdHAwgtHDqETpa3a8Lc%2F-MdHCH9U40S7vKyx9mJR%2F25.png?generation=1624876853450145\&alt=media)


# QAQC SCC & MSA

A guide to Innova's QAQC, Short Collar Correction (SCC) and Multi Station Analysis modules within Innova Engineering.

## 1.0 - Introduction

The following document is a guide to Innova's QAQC, Short Collar Correction (SCC) and Multi Station Analysis modules within Innova Engineering.

The purpose of this document is to guide a new user through the layout, setup, calculation and outputs for these modules.

## 2.0 - QAQC Module

This module takes raw data from the MWD accelerometer (GX, GY & GZ) and magnetometer (HX, HY & HZ) and checks the generated outputs against the local geomagnetic data to ensure that the survey falls within accepted tolerances.

### 2.1 - Required Inputs

In order to run the QAQC check, the following inputs are required.

* **RAW Survey Data section** of the **Surveys tab**
  * **Latitude**: Required to calculate the SCC Delta Azi in the Magnetic Spacing Calculator
  * **HL Ref** – Reference magnetic field
  * **Dip Ref** – Reference magnetic dip angle
  * **TAC** – Total Applied Correction - Automatically calculated based on North Reference selected
  * **Grid convergence** – Angle between True North & Grid North from True North
  * **Declination** – Magnetic declination - Angle between True North & Magnetic North from True North
  * **North reference** – The north reference the surveys are referenced to. Either True or Grid.
  * This data is generally obtained from the well planning department who generate the data using programs like IGRF, BGGM & HDGM.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIPkCsDeIue3mOK%2F0.png?generation=1624976215162603\&alt=media)

* **Magnetic Units** associated with HX, HY & HZ.
  * Geolink / Tensor (mv), SSP / SUCOP (uT), nT, nT no XY inversion, EVO / Applied Physics or Vertex

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIQ2h9AX9ufBCSD%2F1.png?generation=1624976215175903\&alt=media)

* **Accelerometer Units:** Associated with GX, GY & GZ.
  * G or mG. The option to Invert Z Axis can be checked or unchecked irrespective of the accelerometer unit choice

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIRjlBBgSZUVad6%2F2.png?generation=1624976215170122\&alt=media)

* Raw data from the MWD tool (GX, GY, GZ, HX, HY & HZ) + Measured Depth

### 2.2 - RAW survey QC Limits

It is important that the correct QC limits are set. These values are the ± limits used to compare the measured values against the calculated values. If these limits are not accurate it is possible that surveys may pass, which should not pass and conversely surveys may fail, when they should pass.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JISPgoW1IZSMl7T%2F3.png?generation=1624976215232988\&alt=media)

The QC default limits set in Engineer are industry standard. It is however possible to change these if required. You can do this as follows:

* In the **Surveys** tab, select **Raw Surveys** from the **Survey Selection** drop down.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdN7cei_eAXoNAy0Hab%2F-MdN7rZj0ruOCOCBpnIC%2F1.png?alt=media\&token=96083d96-26d5-4cb8-9c27-c78337d931dc)

* Select **Options** from the top toolbar and then **Raw Survey QC Limits.**
* Note, that you can only access these values when you have **Raw Surveys** selected.
* Individual limits can now be changed as required.
* Note, that any changes made to these limits will only be valid for each specific project. When creating a new project, limits will be the default values until changed.

### 2.3 - QAQC calculation and Outputs

#### 2.3.1 – Calculation Setup

* Ensure that the correct units have been selected, fill in the RAW Surveys Tab data (HL, Dip etc) and ensure that you have the correct RAW survey QC limits assigned.
* Ensure that you have the correct survey calculation method selected: **Options** - **Survey Calculation Method**. The default is ***Minimum Curvature*** and is very unlikely to be anything other than this.
* Select **Raw surveys** from the survey selection drop down menu.
* You can now enter your raw MWD data on a survey by survey basis, or if you are retrospectively checking an existing survey you can add the whole thing in one go
  * You can copy and paste the data, or
  * Go to **File** - **Import Survey** - you can then select the file you want to import
  * Note that in the drop down file type menu, there is an option that says Navigator SCC .txt. This should be used when importing Navigator export files (Navigator export files also contain the Geomag data; therefore, once imported ensure the Geomag data that has been pulled in is correct)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdN7cei_eAXoNAy0Hab%2F-MdN80Vymy7BwVAUAypT%2F2.png?alt=media\&token=744ae9fb-0766-4906-bc28-a8087d6843c0)

#### 2.3.2 - Outputs

The generated HL, GT and Dip values are compared to the reference data in the RAW surveys Tab and any of the generated values out with the selected QC limits will be highlighted in RED. For a survey station to pass the QAQC procedure, they must fall within the QC limits and therefore not be highlighted.

Any surveys which have been highlighted should be rejected and retaken, **unless** it is possible to use the Short Collar Correction (SCC) algorithm to correct them to within the accepted limits.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdN7cei_eAXoNAy0Hab%2F-MdN8ESh9Iiypefj3YbE%2F3.png?alt=media\&token=fa8ea275-3927-417f-bc4f-b38a9e4e337b)

**The values in the SCC column's will be generated regardless of whether a survey passes QAQC or not, and should therefore be disregarded, unless of course you are using the correction.**

## 3.0 – Short Collar Correction Module

Short Collar Correction (SCC) corrects for magnetic interference in the Z axis. It should be noted that for the short collar correction algorithm to work correctly the Z axis must be aligned with the hole direction i.e. the Z axis points along hole. If this is not the case the short collar correction algorithm will not work. All major MWD companies with the exception of Schlumberger have the Z axis aligned with the along hole direction.

### 3.1 - Magnetic Calculator

Firstly, you need to ensure that the following data has been added to Engineering.

* Proposed BHA with the relevant components marked as non-magnetic
* Well Plan, in the Surveys Tab under Well Plan Surveys
* ***Raw Survey Data*** section and **Sensor offset** in the *Survey Corrections* section

You can now calculate the well path magnetics: **Calculate - Wellpath Magnetic Interference**

A window will now appear with the results and will look like the screen shot below.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIXG6UZNfALwesH%2F8.png?generation=1624976215235128\&alt=media)

**Results**

* **Azimuth:** The azimuth displayed is referenced to **Magnetic North** and will therefore look different when compared to the azimuth that was entered in the plan (which could be referenced to Grid or True North). The correction applied to the input azimuth is automatic and is based on the Geomagnetic data that you have entered in the Raw Survey Data Section.
* **Delta Bz**: The expected error between the **Theoretical Bz** and the Measured Bz (from MWD) for raw, uncorrected surveys.
* **Delta Azimuth**: The expected error in the raw uncorrected azimuth reading, <0.5 degrees is considered acceptable
* **Delta Dip**: The expected error between the calculated dip (from the geo-mag data) and the actual measured value (from MWD). This will be highlighted in red if the value is greater than the tolerance entered in the QC Limits dialog.
* **Delta HL**: The expected error between the calculated magnetic field strength (from the geo-mag data) and the actual measured value (from MWD). This will be highlighted in red if the value is greater than the tolerance entered in the QC Limits dialog.
* **Theoretical Bz**: The theoretical magnetic field strength expected in the Z axis with no interference.
* **SCC Delta Azi**: The expected error in the SCC corrected azimuth, <0.5 degrees is considered acceptable. This is affected by the Latitude entered in the Raw Survey Data section.

The **P1** and **P2** pole strength values are automatically selected based on the component type and size above and below the non mag components in the string. These can be overridden by the user if necessary, by checking the **override pole** box at the bottom right of the dialog and alternative values can then be entered by the user. Once entered, the user must select **recalculate**.

The whole output can be saved to pdf by selecting **File – Export to PDF**.

The data table can be exported to Excel by selecting **File - Export**.

These results can be used to make an informed decision as to whether there is a requirement to run the SCC algorithm, add additional non-mag or do nothing. Company policy will dictate what error values are considered acceptable.

### 3.2 - SCC Limitations

When it is deemed necessary to run SCC, careful consideration should be given to the planned well path, as there are defined limitations to the SCC which must be adhered to. Failure to follow these guidelines could result in surveys passing correction which should not. The SCC limits are listed in the table below.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdN7cei_eAXoNAy0Hab%2F-MdN8vSa3o5Fj_ZwJYBM%2F4.png?alt=media\&token=561b4161-ce0c-47ad-a2a4-7a0ab35fbfca)

* **Note 1** – If **possible, SCC should NOT be used** and the BHA should be correctly spaced with non-magnetic tubulars as required.
* **Note 2** – **SCC must NOT be used if the well path is known to be within these parameters.** Again, the BHA should be correctly spaced with non-magnetic tubulars as required.
* If the above parameters are encountered, then the SCC algorithm will not function correctly and erratic corrected data will be seen. It is therefore necessary to discuss beforehand with the Directional Driller/Company Representative as to an agreeable plan of action if the above criteria are expected to be encountered during the drilling that particular borehole.

**If the planned wellbore falls out with the above limitations, SCC should NOT be used, and you should ensure that the BHA has the correct non-mag spacing.**

### 3.3 - Running SCC

When running the SCC, raw survey data is added in the same way as you do for the QAQC.

As with the QAQC, any numbers which are out of spec are highlighted red and should not be used. However, there are 3 columns (Azi SCC, HL SCC & Dip SCC) which contain corrected values, and as long as all 3 of these columns are not red, the **Azi SCC** value can be used instead of the calculated azimuth.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIYONEuP9ZcCupK%2F9.png?generation=1624976215284233\&alt=media)

**If even one of these 3 cells are red, the corrected azimuth should not be used, and the survey should be retaken.**

## 4.0 – Multi-Station Analysis (MSA) Module

Multi Station Analysis is a technique which can be used to calculate Magnetometer biases in the X, Y & Z axis. This is achieved by examining the measured and theoretical values at each sensor over multiple stations to find corrections which minimise the errors. These corrections are then applied to all the raw values to produce corrected surveys.

### 4.1– MSA Setup

This section will assume that the user has input all data required to run SCC, as these steps must be complete before MSA can be calculated. In the Surveys tab on the main screen, select the MSA radio button located at the bottom right of the screen, this will open the Multi Station Analysis dialog.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIZDaqZaoTo9uVD%2F10.png?generation=1624976215256931\&alt=media)

* All the RAW surveys populated on the main screen can be found here – Note that these inputs are NOT editable on this page.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JI_Z9f5IXH0Xn26%2F11.png?generation=1624976215295555\&alt=media)

* The **HL Ref** box located at the top left of the screen will contain the value entered on the main surveys tab. This can however be changed on this screen if a more accurate value is supplied e.g. from an IFR model

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIaog9EL2IsVd3Z%2F12.png?generation=1624976215227698\&alt=media)

* **MSA Parameters:** The user can select the required Bias and SF start, stop and Step values. If the LSQ fit does not show a good curve with a minimum found these values can be adjusted to extend the range of the calculation. Changing the step size can speed up / slow down the calculation but a smaller step size can increase the accuracy.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIbiYxFSa8qxcY4%2F13.png?generation=1624976215172326\&alt=media)

* **Values in Use**: The user can choose which values to use for the calculation:
  * **Bz:** Choose between SCC or raw. This determines which Bz value is used in the MSA calculation. If there is a large amount of interference in the Z axis, select the SCC option as the Z axis interference from the drill string must be removed before the MSA calculation can be run. If, however the BHA is correctly spaced or the assembly is run in the SCC no-go zones, then the raw value should be used.
  * **Azimuth:** This selection determines which azimuth is used in the survey calculation and only affects TVD, NS, EW, DLS etc
  * **Inclination:** This selection determines which inclination is used in the survey calculation and only affects TVD, NS, EW, DLS etc

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIcTrba-VeVuH2D%2F14.png?generation=1624976215281308\&alt=media)

* **Apply Gt Weighting**: Surveys at a higher inclination are given more weighting in the calculation than surveys at lower inclinations. This is because they have more of an effect on azimuth. Ticking this box defines if the weighting is applied.
* **Override Correction**: When this box is ticked the user can manually edit the Bias X, Y, Z and Scale X, Y, Z values.

### 4.2 - Running MSA

To run the MSA calculation, select the “***Calculate MSA***” radio button. The MSA columns will populate with the relevant corrected values. As with the SCC results, anything out of spec will be highlighted in red.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIdTAl2mdkLtPKj%2F15.png?generation=1624976215288853\&alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIev9OM6OoFnD6G%2F16.png?generation=1624976215244241\&alt=media)

At the left-hand side of the screen, if required the user can deselect any survey station which is out of spec. Once the relevant surveys have been deselected it is possible to rerun the calculation. The lines which have been deselected will have blank cells in the MSA columns, and this station will not be included in the calculation.

## 5.0 - QAQC, SCC & MSA Reports & Outputs

The MSA report and output charts are separate from the QAQC and SCC reports.

### 5.1 – QAQC & SCC Report

Once a calculation has been run, if required the user can generate a report. This can be done by either selecting the Report icon or by going to **File - Print Reports**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdN7cei_eAXoNAy0Hab%2F-MdN9jLWsDBzOUxPKoBk%2F5.png?alt=media\&token=10daa46e-196d-4094-a1e9-33e117fd3693)

Select the **Surveys** tab and select raw surveys. It is possible to create the report as PDF or Excel. Then select **File - Print**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIhGPfC9Dx4NT4y%2F19.png?generation=1624976215241992\&alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIiyWrP07Q8aFyn%2F20.png?generation=1624976215271500\&alt=media)

### 5.2 – MSA Report

The MSA reports are accessed directly from the MSA window and are NOT available from the Print Reports section. Once MSA has been calculated the user can select **File – Print Report**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MdN7cei_eAXoNAy0Hab%2F-MdNA7eXgDA9rTCMTBqa%2F6.png?alt=media\&token=d1686e61-5fca-483a-8706-8f26996cf3ed)

This generates a PDF report which includes the MSA results, Magnetics, Pseudo Bias & SF values and a listing of the corrected surveys. Note that any stations which were deselected will not appear in this listing.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIkq6AHGDy1ee3z%2F22.png?generation=1624976215281873\&alt=media)

The user can also export the main MSA data table, as displayed on the main MSA interface. This can be exported as a .txt or Excel file. To export this data, select **File – Export**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIlG3Qx7Z477SoL%2F23.png?generation=1624976215253320\&alt=media)

### 5.3 **– MSA Charts & Data Tables**

In addition to the reports, the View menu contains QA/QC and other tools to evaluate the data.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIm0UF232SttHnT%2F24.png?generation=1624976215301119\&alt=media)

#### 5.3.1 – LSQ Data Table

The LSQ Data table shows the data from the least squares fit

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIn2482_sp30f8d%2F25.png?generation=1624976215293919\&alt=media)

#### 5.3.2 – Azimuth Comparison Chart

The Azimuth Comparison chart, provides the user with a visual representation of the Uncorrected azimuth against the SCC corrected azimuth and the MSA azimuth.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIoFuJtZqtq8rLm%2F26.png?generation=1624976215254665\&alt=media)

#### 5.3.3 – HL Comparison Chart

The HL comparison chart gives the user a visual representation of the reference HL against the measured (uncorrected) HL and the SCC & MSA corrected HL values. The chart also includes the tolerance lines which make it very easy to quickly identify any points which are out with the QC parameters

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIplfVlL2AZNjev%2F27.png?generation=1624976215262606\&alt=media)

#### 5.3.4 – Dip Comparison Chart

The Dip comparison chart gives the user a visual representation of the reference Dip against the measured (uncorrected) Dip and the SCC & MSA corrected Dip values. The chart also includes the tolerance lines which make it very easy to quickly identify any points which are out with the QC parameters

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIq2kpGSb8UTLgT%2F28.png?generation=1624976215276869\&alt=media)

#### 5.3.5 -BH BV Scatter Plot

The BH BV Scatter Plot shows the horizontal and vertical components of the sensor readings plotted against the QC values. Ideally, they should all reside within the limits

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIrJPexIOeusSDT%2F29.png?generation=1624976215275792\&alt=media)

#### 5.3.6 – LQS Chart

The LQS Chart shows the least squares fit. If a V shape curve is seen the minimum has been found and the calculation is a success. If any one of the charts does not show a “*minimum found*” the calculation must be re-run.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIsXwCXPnBvqpa_%2F30.png?generation=1624976215270256\&alt=media)

#### 5.3.7 - TF vs Azimuth Correction Plot

This Chart plots the difference in the RAW and MSA corrected azimuths against the HSTF recorded when the survey was taken. This chart gives a good visual representation of the number of surveys taken in each quadrant. For best results, an even spread is ideal, but it is **essential** that there are at least some survey points in each quadrant.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JItRpSIZUHNHg6a%2F31.png?generation=1624976215280045\&alt=media)

#### 5.3.8 - Delta Azi Plot

The Delta Azi Plot shows the difference in azimuth between the MSA and RAW azimuth and the SCC and RAW azimuth.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIu3PFCgH_j4f7S%2F32.png?generation=1624976215290218\&alt=media)

#### 5.3.9 - Delta Dip Plot

The Delta Dip Plot shows the difference in the dip between the MSA and RAW dip and the SCC and RAW dip.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIvfhkLdGCJYOjy%2F33.png?generation=1624976215266178\&alt=media)

#### 5.3.10 - Delta HL Plot

The Delta HL Plot shows the difference in the HL between the MSA and RAW dip and the SCC and RAW dip.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIwyVLY_uPLfiMi%2F34.png?generation=1624976215331828\&alt=media)

#### 5.3.11 - Corrected vs Uncorrected Surveys – Plan View Plot

This plot shows the difference between the corrected and uncorrected surveys in the plan view.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIxYhsk0GG6LlS2%2F35.png?generation=1624976215261447\&alt=media)

#### 5.3.12 - Corrected vs Uncorrected Surveys – Section View Plot

This plot shows the difference between the corrected and uncorrected surveys in the section view.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIyNhZuiSiENFAK%2F36.png?generation=1624976215276747\&alt=media)

#### 5.3.13 - GT Plot

The GT Plot shows the measured GT values against the value entered in the magnetics section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MdN6thtT_Eo62KlAVlh%2F-MdN7JIz409wnaVSYZMS%2F37.png?generation=1624976215262609\&alt=media)

#### 5.3.14 - Show Labels on Scatter

Selecting this option, displays labels on the BH BV Scatter plot.

#### 5.3.15 - Report Options

Allows the user to select which plots to include in the reports.


# SAG Quick Start Guide

A guide to the SAG survey correction module in Innova Engineering

## 1.0 - Introduction <a href="#toc134804781" id="toc134804781"></a>

SAG occurs when a BHA bends under its own weight when positioned between two points of stabilisation. The degree of bending is affected by the hole size, stabiliser size, distance between points of stabilisation, and tubular OD & ID. SAG causes MWD sensor misalignment in relation to the borehole, and accounts for up to 80% of wellbore TVD position uncertainty.

The purpose of this document is to guide the user through the setup, calculation and the interpretation of the results of the SAG module in Innova Engineering.

## 2.0 – Setup <a href="#toc134804782" id="toc134804782"></a>

Before inputting data, the user should configure the relevant options in the Units menu and the Options menu:

* **Units:** Ensure that all of the units are correctly selected, based on your inputs.
* **Options – Include Motor Bend in BHA Analysis:** This lets you toggle whether the program factors in the bend angle in your motor into the SAG calculation. See Section 7.2 for additional considerations when using this option.
* **Options – SAG Calculation Precision:** This will let you set the number of decimal places that the SAG results will be calculated to. Default is 3.

## 3.0 – Required Inputs <a href="#toc134804783" id="toc134804783"></a>

In order to run SAG, the user is required to enter data into the Drill String, Well Geometry and Fluids Tab and the Surveys Tab.

### 3.1 - Drill String, Well Geometry and Fluids Tab <a href="#toc134804784" id="toc134804784"></a>

In order to run SAG, the following parts of the Drill String, Well Geometry and Fluids Tab require data entered:

* **Well Geometry**: The wellbore geometry tells the program the size of hole that the assembly is in.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FByqAmNYkgQdxDc4zz9cL%2F0.png?alt=media)

* **Mud Weight:** The mud weight is used to calculate the buoyancy of the drill string.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgSzA5NB4QbKGazGdIVmE%2F1.png?alt=media" alt=""><figcaption></figcaption></figure>

* **Drill string – All components:** Enter your drill string into the Drill String section. This does not need to include any more than \~30m (100ft) of assembly beyond the last point of stabilisation. Beyond this point the remainder of the drill string will be lying on the low side of the hole and is not considered in the calculation. **All** components entered into the main Drill String table must have a **component type, length, OD** and **ID**. This includes items that don’t normally come with an ID, such as the motor or the bit.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Flba4vothwAY477oXYMyF%2F2.png?alt=media)

* **Drill String – Stabilizers:** As well as the above requirements, stabilizers require the following information entered into their component properties:
  * **Stab OD**: The outside diameter of the stabilizer.
  * **Stab Blade Length**: The length of the stabilizer blade that will be in contact with the side of the hole – **Watch your units, this will be in inches or mm, depending on your diameter unit.**
  * **Stab Distance from Bottom**: The distance from the Pin end shoulder to the bottom of the stab blade
  * **Note:** There is also space to enter stabilizer information into the component details for RSS, MWD/LWD, Motor, Turbine and Reamer component types. If you have stabilizer sleeves on any of these items in your BHA, don’t forget to enter the details for them as well.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRFp63uoBMqqC35vK3916%2F3.png?alt=media" alt=""><figcaption></figcaption></figure>

* **Drill String – Motor Bend:** If you have a motor in your BHA, you can enter the motor bend angle in the component details section. This is only required if you have the **Include Motor Bend in BHA Analysis** option toggled o&#x6E;**.**

### 3.2 – Surveys Tab <a href="#toc134804785" id="toc134804785"></a>

In order to run SAG, the following parts of the Surveys Tab require data entered:

* **Survey Offset:** The distance between the cutting surface of the bit and the MWD inclination sensor.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSqc3I204GCoqYHBIIJgU%2F4.png?alt=media)

## 4.0 – Calculation Types <a href="#toc499820553" id="toc499820553"></a>

Select the type of SAG calculation that you want to run from the drop down box in the Survey Connections section. Users have a choice of Single, Inclination Range or Surveys. Single and Inclination Range are configured in the Survey Corrections section.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtNXjBMCd2ehmUGBIO1Vp%2F5.png?alt=media)

### 4.1– Single <a href="#toc499820554" id="toc499820554"></a>

Selecting **Single** allows the user to calculate a SAG correction based on a single inclination:

* **Inc**: Inclination that the user requires SAG results for.
* **DLS**: Dogleg (°/30m or °/100ft depending on units selected). The program will use the dogleg to simulate hole curvature which affects the results. Zero represents a tangent.
* **TF**: The Toolface of the motor bend during the survey. If the **Include Motor Bend in BHA Analysis** option toggled is toggled off, this will have no effect.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnX6TIld0XMjDGgPMHLSv%2F6.png?alt=media)

### 4.2 – Inclination Range <a href="#toc499820555" id="toc499820555"></a>

Selecting **Inc Range** allows the user to calculate SAG over a range of inclinations:

* **Inc Start**: Initial Inclination.
* **Inc Stop**: Final Inclination.
* **Inc Step**: Step change in inclination between the initial and final. A step change of 2.5° will calculate SAG every 2.5° between the selected range.
* **DLS**: Dogleg (°/30m or °/100ft depending on units selected). The program will use the dogleg to simulate hole curvature which affects the results. Zero represents a tangent.
* **TF**: The Toolface of the motor bend during the survey. If the **Include Motor Bend in BHA Analysis** option toggled is toggled off, this will have no effect.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWBjfIyyOlqEZTFyqWB7Z%2F7.png?alt=media)

### 4.3 – Surveys <a href="#toc134804789" id="toc134804789"></a>

Selecting Surveys allows the user to calculate SAG on Actual Surveys, Well Plan Points or RAW Surveys, depending on what is selected. As well as the offset, the toolface of the motor is the only value in the Survey Corrections section that effects this calculation type. If the **Include Motor Bend in BHA Analysis** option toggled is toggled off, the TF will have no effect.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fw5TJFyyAQU90v1QEuImw%2F8.png?alt=media)

Select your survey type from the drop down box in the Survey Selection section, and then enter your surveys into the table. SAG can be run on **Raw Surveys**, **Actual Surveys** or **Well Plan** points. Whichever is selected in the Surveys tab when the calculation is run will be used.

Actual Surveys and Well Plan requires you to enter surveys using **Measured Depth, Inclination and Azimuth**. Raw Surveys require **Measured Depth**, raw **Accelerometer Values (G)** and raw **Magnetometer Values (H).** Make sure that you are using the correct units for your accelerometers and magnetometers.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FToINJdMTvVYbDQ5pyElM%2F9.png?alt=media)

## 5.0 – Running the Calculation <a href="#toc499820556" id="toc499820556"></a>

To run the calculation, open the **Calculate** menu and select **BHA Analysis and SAG Correction**. The calculation will run and the results window will appear. You may also receive a warning. The most common warnings are:

* **WOB greater than zero, SAG correction value may be incorrect:** The WOB parameter entered into the Engineering Parameters tab has an effect on the SAG result. Depending on your circumstances this may not be an error, but as surveys are usually taken when the bit is off bottom, the program will warn you if a value other than zero is entered.
* **No stabilizers:** You have not entered any information in the component details for stabilizers, or components with stabilizer sleeves.
* **BHA tangential point found before sensor for 1 or more surveys:** The tangential point is the point above the last stabilizer where the assembly touches the side of the hole. Anything above this point will be lying against the side of the hole and will therefore not be subjected to SAG. It is important to note that the tangential point changes depending on the curvature of the hole, and in some instances when running the calculation there will be some stations that will require correction and others that will not. Engineering runs through all of these calculations and assigns a 0° correction to those that do not. If you think you are getting this message in error, it is usually because you have set your survey offset too far back from the last stabilizer.

## 6.0 – Interpreting Results <a href="#toc134804791" id="toc134804791"></a>

The following outputs are displayed in the SAG Results window:

**Deflected Shape**: Shows how far the BHA is from the centre line of the well bore. The X-Axis shows the distance from the bit along the BHA. The Y-Axis shows the deflection. The blue dot represents the sensor position. Note that the displayed plot always represents the final survey station.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxRNpLJVjiaELgEf3tzeh%2F10.png?alt=media)

**BHA Slope**: Shows the angle of the BHA with respect to the centre line of the well bore. The X-Axis shows the distance from the bit along the BHA. The Y-Axis shows the slope. The blue dot represents the sensor position, and the slope at this position is the error that is being corrected by the SAG correction. The displayed plot always represents the final station.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbkGJ20ifAG0yn2X2Bbm6%2F11.png?alt=media)

Below the charts is the results table, which contains the following information:

* **MD**: Measured Depth of each survey station.
* **Inc (Org)**: The original uncorrected inclination of the survey.
* **Inc (Corr)**: The SAG corrected inclination.
* **Sag (Corr)**: The SAG correction to be applied to the uncorrected inclination to get the corrected inclination. Note that SAG correction is **always added**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F235BXz2hUyEkpAG0VOvh%2F12.png?alt=media)

## 7.0 - Reporting Results <a href="#toc134804792" id="toc134804792"></a>

After running the calculation, the SAG column will be populated in the Survey tab and in the MSA window. Select **SAG corrected Inc** from the **Inclination to Use** drop down to use the corrected inclination when calculating the TVD, NS, EW and VS values.

A SAG report can be created with the following steps:

1. Close the results window. In the main Engineering interface, open the **File** menu and select **Print Reports.**
2. Configure your format and other options in the **Options** section.
3. Select the **BHA Analysis and SAG** type to create a SAG report. You can customize the report using the below options:
   * [x] **BHA Overview and Calculation Parameters:** Displays the BHA you created in the Drill String tab as well as the parameters you entered in the fluid properties and survey corrections sections.
   * [x] **BHA Trend and SAG Correction Data**: Displays the results table from the SAG results.
   * [x] **BHA Deflected Shape and Slope Charts:** Displays the two charts from the results window.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5ehdP5jdHrJXcxBzyGsQ%2F13.png?alt=media)

## 8.0 – SAG Correction Considerations <a href="#toc134804793" id="toc134804793"></a>

Before running the SAG calculation there are a couple of things to consider:

### 8.1 – Minimum Inclination <a href="#toc134804794" id="toc134804794"></a>

From 0-3° inclination the potential correction will likely be invalid due to the difficulty with finding the point at which the top of the BHA contacts the wellbore, this is due to the hole not having a defined highside.

Due to this, most companies have a policy that SAG should not be applied until the inclination is >3°. However, >5° is also acceptable in certain circumstances.

### 8.2 – Motor Bend, Toolface and Surveys <a href="#toc134804795" id="toc134804795"></a>

This consideration applies when using the **Surveys** calculation type.

If the motor bend is not being modelled in Engineering (Bend angle is 0° in the motor component details, or **Include Motor Bend in BHA Analysis** is turned off) then it is possible to SAG correct all required survey stations in one go. If however, the motor bend is being modelled, then each station has to be SAG corrected individually, assigning the relevant Toolface for each survey. This is more labour intensive and therefore more susceptible to errors.

When the bend is not being modelled, the addition of new stations has no effect on previous corrections. This is not the case when modelling the bend. When a new survey station is added and the correction run, the program runs the correction against all of the previous stations using the assigned toolface. Since every station will likely have been measured on a different toolface, it is possible that the program may change some of the previous corrections based on the new toolface. For this reason it is important to carefully note the correction at each new station as it is calculated, and understand why you may see a difference when looking at earlier corrections.

It is recommended that you try toggling the option on/off and comparing results. If there is a negligible difference, it may be simpler to leave the option off.


# Remote Database Guides

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


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfDxKIDof-wqOu8B%2F0.png?generation=1632839058496221\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfDyercSdaOeII4N%2F1.png?generation=1632839058580015\&alt=media)

### 2.2 - WINSCP

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfDzJdJtDCJ4k4my%2F2.png?generation=1632839058572610\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE-q008SjhRFFoK%2F3.png?generation=1632839058582862\&alt=media)

## 3.0 - Login Details and Passwords

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-Mkgoj0X7m0_x1pGz6Sc%2F-MkgopM7GfXYCI3kaDr6%2FTable.PNG?alt=media\&token=d078b5b2-1cf1-4724-ba4a-79200502dfe3)

## 4.0 - Create an AWS Account

1\. Go to <https://aws.amazon.com/>

2\. Click “Create an AWS account” in the top-right corner.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE0QzO0p4qY6CmB%2F4.png?generation=1632839058576924\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE1b36Ei-OelZpw%2F5.png?generation=1632839058585238\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE25IGyxQpWFNMR%2F6.png?generation=1632839058594503\&alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE35IMNFf2WRlYJ%2F7.png?generation=1632839058660034\&alt=media)

## 5.0 - AWS Management Console

5\. Once an AWS account has been created, the user can then sign into the AWS Management Console.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE4NhBoEn7kBDeO%2F8.png?generation=1632839058481552\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE5CZOTPMZeYtBS%2F9.png?generation=1632839058582607\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE6OWNf4vjlRvKq%2F10.png?generation=1632839058577167\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE793_LrFSWojtn%2F11.png?generation=1632839058583736\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE8yUG2ESFMA9ax%2F12.png?generation=1632839058602743\&alt=media)

9\. With **Virtual MFA device** selected, click continue. You will see the below window.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE9ZQJ1DCKjVOTm%2F13.png?generation=1632839058589683\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEAgrlA3OtEj24M%2F14.png?generation=1632839058478348\&alt=media)

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*](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#create-iam-users)*. 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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEBf8DbZ64FmDZ5%2F15.png?generation=1632839058583270\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfECiENhsjjTHPhb%2F16.png?generation=1632839058584433\&alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEDjdeulwE7vhaC%2F17.png?generation=1632839058579228\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEE_CXH4Ksbwkpe%2F18.png?generation=1632839058578323\&alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEFC8KtsZ3dE3RF%2F19.png?generation=1632839058579972\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEGmxebHrurLhnc%2F20.png?generation=1632839058587870\&alt=media)

18\. This then takes you to the below window. Select **Next: Review.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEHBBkzB5imOldo%2F21.png?generation=1632839058589752\&alt=media)

19\. This then takes you to the below window. Select **Create User.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEIJ_uPHRRl71XX%2F22.png?generation=1632839058593015\&alt=media)

20\. This then takes you to the below window. Select **Close.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEJl1eKRv8BLE_l%2F23.png?generation=1632839058681246\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEK7YJ4pGKvT2RZ%2F24.png?generation=1632839058587880\&alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfELoSREESKWTXx5%2F25.png?generation=1632839058601164\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEMgBdcXq68JuAB%2F26.png?generation=1632839058580101\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfENdpOrRLGUWwKk%2F27.png?generation=1632839058579974\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEOcB110PEJwGig%2F28.png?generation=1632839058581991\&alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEPyKR7uiM5HETt%2F29.png?generation=1632839058594047\&alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEQwYQm77ARNfQz%2F30.png?generation=1632839058593375\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfERWWzbEcLFZDja%2F31.png?generation=1632839058587871\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfESpaA3up1Pus1m%2F32.png?generation=1632839058611711\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfETbbI0yqflmGho%2F33.png?generation=1632839058626578\&alt=media)

30\. **Step 1**: **Create Database:**

a. Choose **Standard Create** as the database creation method.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEUPoDVHBdQG92p%2F34.png?generation=1632839058581300\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEVeh8EUayb2J5-%2F35.png?generation=1632839058585346\&alt=media)

32\. **Step 3: Templates:**

a. Select **Dev/Test** as the template.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEWUy75VWOZ46iL%2F36.png?generation=1632839058581518\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEXIUIkz3DcaSAA%2F37.png?generation=1632839058590094\&alt=media)

34\. **Step 5: DB Instance Size:**

a. Choose **db.t2.medium (2 vCPU, 4 GiB RAM)** as the DB instance class.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEY1vOszs-ldebb%2F38.png?generation=1632839058588136\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEZSRxWtocHDV1K%2F39.png?generation=1632839058584444\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfE_s3eKch8CjOMP%2F40.png?generation=1632839058591151\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEa4RF6r9A7F_W2%2F41.png?generation=1632839058592778\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEb9HZD8Vy1hX2I%2F42.png?generation=1632839058578204\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEc12Nu4prT3EFA%2F43.png?generation=1632839058589074\&alt=media)

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 o&#x6E;**.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEd-1Gx0YBR7l7V%2F44.png?generation=1632839058585834\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEenSZem6bgwPw9%2F45.png?generation=1632839058584392\&alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEfLdCwYmKwgcg8%2F46.png?generation=1632839058579151\&alt=media)

42\. Select Services – RDS.

43\. Select Databases.

44\. Click on the Db identifier for the Db that you are interested in.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEg79fRnRFeVmu8%2F47.png?generation=1632839058590222\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEhlDdk8OWfIwCI%2F48.png?generation=1632839058626358\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEiBHwwcumwhIDI%2F49.png?generation=1632839058587017\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEjvu9FsbrC5nir%2F50.png?generation=1632839058593173\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEk-Jo5uEro5sNq%2F51.png?generation=1632839058654261\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfElZUjq0-aEoYgQ%2F52.png?generation=1632839058589067\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEmcrX72-CFlQZR%2F53.png?generation=1632839058487547\&alt=media)

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,&#x20;*****exactly*****&#x20;as it has been entered, as this is case sensitive and will be required to access the Db via Well Seeker.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEnFk86fqzICwbY%2F54.png?generation=1632839058651664\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEohqFqNs8EpCnG%2F55.png?generation=1632839058492216\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEp1kIW5-cH66_M%2F56.png?generation=1632839058497184\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEq_1PQQ5Tlgbjy%2F57.png?generation=1632839058500405\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEr6YnOYoRtw3LT%2F58.png?generation=1632839058596517\&alt=media)

71\. Click on Launch Instance – **select the latest Ubuntu server – 64-bit (x86).**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEsn64X39SOXS9b%2F59.png?generation=1632839058665643\&alt=media)

72\. Select the **Free Tier Eligible** option shown below.

a. Select **Review and Launch.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEt9_QW3JSMgAfi%2F60.png?generation=1632839058669122\&alt=media)

73\. Select **Edit security groups** and change the name to something suitable e.g. “EC2 Security Group.”

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEukMMKCDPeLj2B%2F61.png?generation=1632839058666206\&alt=media)

74\. Select **Launch**.

75\. Select to Create a new key pair and enter a key pair name.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEvElHEISP6xhgh%2F62.png?generation=1632839058646632\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEwXM8IScMTSyjk%2F63.png?generation=1632839058664056\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfExShFyBssLpRhn%2F64.png?generation=1632839058665632\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEyX4ot0W8xjdxw%2F65.png?generation=1632839058670874\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfEzZDDMO9_oyTUd%2F66.png?generation=1632839058655241\&alt=media)

## 11.0 – puTTYgen

85\. Open puTTYgen.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF-25Tzl-5wjOsc%2F67.png?generation=1632839058640779\&alt=media)

86\. Select load and select the PEM file (you will have to change the file type filter to all files (\*.\*)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF0MK4O9CGGkZC4%2F68.png?generation=1632839058654123\&alt=media)

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.

!\[Graphical user interface, application

Description automatically generated]\(/files/-MkgmfF1Ow7C4bugtbkU)

97\. Click login and click **yes** to the security notice.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF29T_B2VYtjpR3%2F70.png?generation=1632839058576805\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF3l7jSXcKJa1UP%2F71.png?generation=1632839058654555\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF4IthoyiLJOpEo%2F72.png?generation=1632839058700971\&alt=media)

102\. You will get the below left popup. Select OK and you get the below right.

!\[Graphical user interface, application

Description automatically generated]\(/files/-MkgmfF5DdAJFsm7sE7m)

103\. Open the attached **configICDS.json** in a text editor e.g. Notepad

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF6W4Ao8G0ruPFb%2F74.png?generation=1632839058656906\&alt=media)

a) **CompanyID:** Type **Company Name** (this will be supplied by Innova and must be written in **EXACTLY** the same way as its supplied). Make sure **Company Name** is inside double quotes

b) **Port**: Usually enter the **port** field as 42000 (no quotes) – this is the port which will be entered into the Well Seeker RT Data exchange for communication with the ICDS

c) **devmode**: Leave as false (no quotes)

d) **sqluser:** Set to the SQL Server master username used to access the database. Make sure this is inside double quotes

e) **sqlpass:** Set to the SQL Server master password used to access the database. Make sure this is inside double quotes

f) **sqlsvr:** Set to the SQL Server RDS database Endpoint. Make sure this is inside double quotes.

g) **sqldbname:** Set to the name of the database you wish the ICDS to connect to. This is the database name that you see when logged in to SQL server Management Studio. Make sure this is inside double quotes

h) **sqlport:** Set to the port used to connect to the SQL server database (no quotes), usually this is 41433

i) **externalPath:** Specifies where external files are stored. Input either **useDatabase** (stores files on the EC2) or **useS3** (stores files on an S3)

j) **sqldbnamewits:** If a user is pushing and storing WITs data to a database separate to the Well Seeker database, insert the name of the database here. Make sure this is inside double quotes. If this function is not used then leave a the doubles quotes empty

k) **transferWits:** If pushing WITs data to a second database then enter **true**, if not enter **false**

l) **allowActivePush:** If **true** is entered then a computer can push data back to a server database regardless of the well status. If **false** is entered then a computer can push data back to a server database only when the well status is Upcoming, Active or Standby. The well status is selected in the Daily Reports dialog

m) **awsAccessKeyID**: If storing external files on an s3, input the AWS Access Key ID of the IAM user. If not leave blank

n) **awsSecretKey**: : If storing external files on an s3, input the AWS secret key for the IAM user. If not leave blank

o) **awsRegion**: : If storing external files on an s3, input the region where the AWS service is hosted eg “us-east-2” or “us-west-2”. If not leave blank

p) **s3Bucket**: If storing external files on an s3, input the name of the S3 bucket which was created to store the Well Seeker external files. If not leave blank

q) Leave all other fields as they are

104\. Once completed, drag the **config.JSON** file to the same directory as the icdsServer file

105\. In the same sub directory as the icdsServer executable is located, create a directory called **icdsFileDir.**

a. To do this, right click under the icdsServer file and select **New – Directory**.

b. Your folder should now look like the below

c. This folder is where the logos and external files added to the remote database will be saved.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF7uYPcxmF7LVja%2F75.png?generation=1632839058581966\&alt=media)

106\. Close WinSCP. You will get the below. Selected **No**, so that the workspace is saved.

!\[Graphical user interface, application

Description automatically generated]\(/files/-MkgmfF8Pv1v-kroQq2v)

## 13.0 – PuTTY

107\. Open PuTTY

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfF9Np6OR6cH8dS6%2F77.png?generation=1632839058668979\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFACYfCuPwCx64i%2F78.png?generation=1632839058641218\&alt=media)

109\. Then click on **Connection - SSH – Auth.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFBVJ7LPhhOPKAC%2F79.png?generation=1632839058645035\&alt=media)

110\. Click **Browse** and select the **ppk file** created earlier.

111\. Click open.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFCDcAbEv0UM0gX%2F80.png?generation=1632839058572841\&alt=media)

112\. Click Yes to the security alert message. You then get the below.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFDt3mDjmM89EfX%2F81.png?generation=1632839058653057\&alt=media)

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>

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.

!\[Graphical user interface, text, application, email

Description automatically generated]\(/files/-MkgmfFEC7ECfwzM3ZaE)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFFULTNCRI6AHFQ%2F83.png?generation=1632839058582216\&alt=media)

115\. Check pm2 is running by typing **pm2 ls**

f. You should get below after entering this.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFGAG5PK1UW1HEB%2F84.png?generation=1632839058643431\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFHywraRTKNQtpg%2F85.png?generation=1632839058577919\&alt=media)

117\. Type: sudo apt-get update

a. You should get the below after entering this.

b. **At this point close and reopen putty**. If you do not do this, when you get to the point where you type a pm2 command, putty will tell you it is not recognised. Not sure why this happens, but it is a consistent error. Closing and reopening puTTY allows you to proceed without any issues.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFIgjS2UE3tDSU6%2F86.png?generation=1632839058690746\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFJtO5XykW66hgL%2F87.png?generation=1632839058663661\&alt=media)

c. If you do not do this step, then in the next step you will likely get an errored message like the one below.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFKqLcd9g0vDZ6Q%2F88.png?generation=1632839058577499\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFLaylmnlDvE_Y0%2F89.png?generation=1632839058655120\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFM5wkWPzr9XhMq%2F90.png?generation=1632839058645258\&alt=media)

## 14.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:

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFNgxh6RU_32XEO%2F91.png?generation=1632839058565827\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFOBCQ_UJEfGIL_%2F92.png?generation=1632839058654637\&alt=media)

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

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFPxE_nFKjncygn%2F93.png?generation=1632839058621637\&alt=media)

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

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFQKTWQDd0FAe0W%2F94.png?generation=1632839058654389\&alt=media)

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

i. The reason to allow all public IP addresses is because it is difficult to know the relevant public IP addresses for each rig computer which is out with the company’s network. Setting a range here could mean some rig computers are unable to communicate with the ICDS.

ii. For larger companies who have the relevant IT structure, they may want to set an IP range for computers in their network. This is more secure.

iii. If a company does select an IP range, and we end up having to provide support, they may need to add our IP addresses in as a rule otherwise we will not be able to access.

**3. Rule Three:**

a. Type: Custom TCP

b. Port: 41433

c. Select the security group assigned to the RDS.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFR-mTRbdA3Mqb0%2F95.png?generation=1632839058666227\&alt=media)

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

### 17.1 – SQL Server Management Studio (SSMS) RDS Login

If the user receives an error message and cannot log in to the RDS via SSMS then follow the below steps:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFSQRg1Ghai_bcn%2F96.png?generation=1632839058666732\&alt=media)

1\. Check the user’s computer has internet connectivity

2\. Check the Server type is **Database Engine**

3\. Check the Server name is the RDS endpoint, immediately followed by a comma, then a space and then the RDS port number, which is usually 41433. For example:

a. RDS Endpoint = exampleendpoint

b. RDS Port = 41433

c. Server name entered = **exampleendpoint, 41433**

4\. Check the authentication type is **SQL Server Authentication**

5\. Check the Login entered is the RDS Username the user created when setting up the RDS

6\. Check the Password is the RDS password the user created when setting up the RDS

7\. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 16.1 RDS for more details.

Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser

### 17.2 – Well Seeker Pro Database Login

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:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFTLtDrA3cSuB8h%2F97.png?generation=1632839058661802\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFU92E0XUGNeqDJ%2F98.png?generation=1632839058602664\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFVG6ECtdFJ0I0k%2F99.png?generation=1632839058701353\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFWoVPLLKyxyhUp%2F100.png?generation=1632839058585056\&alt=media)

9\. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 16.1 RDS for more details.

Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFX9G85ec-NAAvn%2F101.png?generation=1632839058656173\&alt=media)

**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:

1\. Ensure the real time data exchange and remote data fetch functions are working correctly. See 16.3 – Real Time Data Exchange / Remote Data Fetch for details. If they are then it rules out a number of potential causes for the issue. If both these functions are working, but you are still experiencing issues with the external files functions then proceed to the next step

2\. Ensure that during the database creation the step was followed that created the external files image path in the dbo.DB\_SETTINGS table. See 14.0 – Well Permissions, step 68 for details

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFYVfxn1OZGjmZ5%2F102.png?generation=1632839058598280\&alt=media)

3\. Ensure that the option **Push External Files** is selected on all computers trying to use the functionality

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgjvGONvY_jqGVgKei%2F-MkgmfFZSHT5cMmSrsau%2F103.png?generation=1632839058666214\&alt=media)


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMPsALTh_8QIBNut%2F0.png?generation=1632838189231386\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMPt0rXWRn1KOpj1%2F1.png?generation=1632838188970094\&alt=media)

### 2.2 - WINSCP

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMPuXXthMK9sUWEY%2F2.png?generation=1632838188957200\&alt=media)

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

## 3.0 - Login Details and Passwords

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.

!\[Graphical user interface, application, table

Description automatically generated]\(/files/-MkgjMPvojaztcb-PZC6)

## 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](http://www.azure.microsoft.com/)

3\. Click “Try Azure for free”

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMPwSk-Oz33MTs4I%2F4.png?generation=1632838188977237\&alt=media)

4\. Click “Start for free”

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMPxN7AFMFsHc-vs%2F5.png?generation=1632838188978047\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMPyPJujVHf5H1iX%2F6.png?generation=1632838188955611\&alt=media)

## 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**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMPzHK2DGKlOLW4C%2F7.png?generation=1632838188951841\&alt=media)

8\. Select **Create SQL database**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ-jdw4tu1I1S-5%2F8.png?generation=1632838188951548\&alt=media)

9\. Select subscription as **Free Trial**

10\. Under resource group, select **Create new**, and name the group appropriately

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ0CHp3MIQrkTQn%2F9.png?generation=1632838188989676\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ1UgUDWdts5Wiq%2F10.png?generation=1632838188978286\&alt=media)

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)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ217c4IUzfP51Y%2F11.png?generation=1632838188979057\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ33qRigBhW7Hnd%2F12.png?generation=1632838189217888\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ4qL6Y_JjDOq-Q%2F13.png?generation=1632838189172225\&alt=media)

17\. Add tag names for reference if desired

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ5xGbcvir6UMKo%2F14.png?generation=1632838189182654\&alt=media)

18\. Select **Review + create**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ6NUTydSRCiTBz%2F15.png?generation=1632838189176161\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ70DWnybrhby5n%2F16.png?generation=1632838189079183\&alt=media)

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)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ8Ovdx-6NJicS8%2F17.png?generation=1632838188985947\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ9ulQ80TzN87pm%2F18.png?generation=1632838188977571\&alt=media)

29\. In the Object Explorer Tree, navigate to the tables folder under your database

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQAEMFMkrRxQzBH%2F19.png?generation=1632838189078717\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQBOKeCxNmsopSZ%2F20.png?generation=1632838189087447\&alt=media)

## 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**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQCvnDChG2arPnA%2F21.png?generation=1632838189011119\&alt=media)

34\. Select **Add** and **Virtual Machine**

!\[Graphical user interface, text, application, email

Description automatically generated]\(/files/-MkgjMQDwwY\_IDY-UiQK)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQEqzsx1xNe8IBz%2F23.png?generation=1632838189185262\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQFu56Cf3H6y83I%2F24.png?generation=1632838189177494\&alt=media)

36\. In the **Disks** section

a. OS disk type, select **Standard SSD**

b. Encryption type, select **Default**

c. Select **Next : Networking >**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQGEPnQLlR2RyYo%2F25.png?generation=1632838189169616\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQHEHeq5Y1Y9D3C%2F26.png?generation=1632838189226532\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQINlu58IJDb-YB%2F27.png?generation=1632838189182878\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQJz1NIhNH9wlw-%2F28.png?generation=1632838189221188\&alt=media)

39\. In the **Advanced** section

a. Leave all as default and select **Next : Tags >**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQK8s0uDsCAXmLW%2F29.png?generation=1632838189210729\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQLV_Bb0gKWa8WH%2F30.png?generation=1632838189177737\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQMSUD0JlNCbO1K%2F31.png?generation=1632838189171408\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQN_RP2Q683ysYp%2F32.png?generation=1632838189225867\&alt=media)

47\. Select **Show firewall settings**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQOeyQLRg6QOcjn%2F33.png?generation=1632838189297426\&alt=media)

48\. At the bottom of the page select **Add existing virtual network**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQPVDrdb_yCqsa7%2F34.png?generation=1632838189229228\&alt=media)

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)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQQfdEJjIAMicUp%2F35.png?generation=1632838189171938\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQRyvLG0yugT33U%2F36.png?generation=1632838189185955\&alt=media)

51\. Select load and select the PEM file (you will have to change the file type filter to all files (\*.\*)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQSXfIt_GcVY-G_%2F37.png?generation=1632838189188812\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQTaWtORrUWKtG0%2F38.png?generation=1632838189014062\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQUCD9NVvaIEgz-%2F39.png?generation=1632838189177296\&alt=media)

62\. Click login and click **yes** to the security notice.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQVuIB4ED29CyaH%2F40.png?generation=1632838189013088\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQWhHUlmLTk_1kK%2F41.png?generation=1632838189169004\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQXKP9IrYXUnfoe%2F42.png?generation=1632838189189632\&alt=media)

67\. You will get the below left popup. Select OK and you get the below right.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQYtML0e-zZ5Qld%2F43.png?generation=1632838189176030\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQZPMPSxnLo5fBS%2F44.png?generation=1632838189177434\&alt=media)

68\. Open the attached **config .JSON** in a text editor e.g. Notepad

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQ_mWzhBTuJbF8X%2F45.png?generation=1632838189177873\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQaTvP98EhWyb1U%2F46.png?generation=1632838189064023\&alt=media)

71\. Close WinSCP. You will get the below. Selected **No**, so that the workspace is saved.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQb8qX5zcy_0Lvo%2F47.png?generation=1632838189176238\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQcEpTgSjH4JUsG%2F48.png?generation=1632838189072924\&alt=media)

## 11.0 – puTTY

72\. Open puTTY

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQdnWmGwPoWi0W4%2F49.png?generation=1632838189188928\&alt=media)

73\. In the Host Name Cell: Type virtual machine usernam&#x65;**@**&#x76;irtual 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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQeWfN-HFMTJXoz%2F50.png?generation=1632838189175863\&alt=media)

74\. Then click on **Connection - SSH – Auth.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQfz_6UydcxAiGc%2F51.png?generation=1632838189182738\&alt=media)

75\. Click **Browse** and select the **ppk file** created earlier.

76\. Click open.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQgSy8Y9Qh3-GZU%2F52.png?generation=1632838189075392\&alt=media)

77\. Click Yes to the security alert message. You then get the below.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQhCYnK4p4pF1oa%2F53.png?generation=1632838189182549\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQiFu9x-yIIH6CP%2F54.png?generation=1632838189176452\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQjZ7rvoXZt7u-J%2F55.png?generation=1632838189176212\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQkyMHaA_Ivy-9q%2F56.png?generation=1632838189074666\&alt=media)

80\. Check pm2 is running by typing **pm2 ls**

f. You should get below after entering this.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQloIi_qDYxHTB6%2F57.png?generation=1632838189217706\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQmNT-HFT1_qlwE%2F58.png?generation=1632838189080028\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQnRZDthsK9Le4O%2F59.png?generation=1632838189182740\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQoARv56zLYRyXT%2F60.png?generation=1632838189178996\&alt=media)

b. If you do not do this step, then in the next step you will likely get an errored message like the one below.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQpCrzzSAl0mIAE%2F61.png?generation=1632838189087317\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQqjLZ-Uw4Z-NMw%2F62.png?generation=1632838189182735\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQrL6ecYb9JfnUS%2F63.png?generation=1632838189171783\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQsNoebj3JVaCRz%2F64.png?generation=1632838189082189\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQt35bFYCbjPaCz%2F65.png?generation=1632838189185462\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQuSxpAqtC7hVha%2F66.png?generation=1632838189174390\&alt=media)

## 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**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQv93motqiLlfCN%2F67.png?generation=1632838189177273\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQwgZA23C0oNdtB%2F68.png?generation=1632838189182814\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQxaAzHmyr3si24%2F69.png?generation=1632838189185490\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQyahuOyTA3Ue2W%2F70.png?generation=1632838189211018\&alt=media)

106\. Your inbound rules should now resemble the below

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMQzhx2NSUF9J4Ji%2F71.png?generation=1632838189182711\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR-vWJckg7PGls-%2F72.png?generation=1632838189198444\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR0h6kgNtf8mJ95%2F73.png?generation=1632838189174478\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR1g8JHT2fzOQui%2F74.png?generation=1632838189186400\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR2aHrX5baBYgu7%2F75.png?generation=1632838189172375\&alt=media)

114\. Select Add. Add a third rule that denies outbound internet traffic, which has a larger priority value than the previous two rules

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR3DIdv1b6yY-mR%2F76.png?generation=1632838189229541\&alt=media)

115\. Your outbound rules should now resemble the below

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR4NnDJseUNHu6B%2F77.png?generation=1632838189213855\&alt=media)

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.

### 15.1 – SQL Server Management Studio (SSMS) Login

If the user receives an error message and cannot log in to the SQL database via SSMS then follow the below steps:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR5_pr2pM3gT443%2F78.png?generation=1632838189245737\&alt=media)

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

### 15.2 – Well Seeker Pro Database Login

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:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR6B5o6PHaVqzKd%2F79.png?generation=1632838189211624\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR7M6b80mzffBuA%2F80.png?generation=1632838189202084\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR8vlR6tkwFz4r7%2F81.png?generation=1632838189221195\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMR9AZDTqnGuQWP8%2F82.png?generation=1632838189234484\&alt=media)

9\. If the above checks still haven’t fixed the problem the remaining potential cause is the SQL database security settings. Log on to the Azure account, select the SQL database in question and review the security settings.

Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMRAC-oRoa3EWjMt%2F83.png?generation=1632838189229579\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMRBdxTxb_BDrFJk%2F84.png?generation=1632838189182736\&alt=media)

3\. Ensure that the option **Push External Files** is selected on all computers trying to use the functionality

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-MkgeNYeykyXW2D5qMN4%2F-MkgjMRCEh4gX64tikJ9%2F85.png?generation=1632838189289862\&alt=media)


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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7D6zZBqMWJWEMGO%2F0.png?generation=1632840487835540\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7D7vknzUxWZ1mkb%2F1.png?generation=1632840487794489\&alt=media)

### 2.2 - WINSCP

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7D81Af1TsRtILyW%2F2.png?generation=1632840487793033\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7D9g_MBFZi59zdg%2F3.png?generation=1632840487796151\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DAx372cUJSO-Jv%2F4.png?generation=1632840488069271\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DBiSzy47kyAucs%2F5.png?generation=1632840488067660\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DCUhxhRvmzrYuf%2F6.png?generation=1632840487818289\&alt=media)

5\. When you expand the database and open the tables tree item you will see there is nothing there

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DDb2bTodFYCos1%2F7.png?generation=1632840487799186\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DEnCOc2oO3dEeW%2F8.png?generation=1632840487799177\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DFX8XLorvRzN65%2F9.png?generation=1632840487801103\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DGArRpYDbBYMuK%2F10.png?generation=1632840487813435\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DHo__RIeC87-qT%2F11.png?generation=1632840488086231\&alt=media)

3\. Create a new directory called **icdsServer2**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DII3yYLSwzXBHg%2F12.png?generation=1632840488060510\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DJOT4B3aKb4Ar-%2F13.png?generation=1632840487803900\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DKkFl41pvvQ2hD%2F14.png?generation=1632840487801180\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DL4FWdFcyqm9Pa%2F15.png?generation=1632840488113853\&alt=media)

3\. Type **pwd**, which will show the current location you are in. This should be **/home/ubuntu**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DMiBQEludY1oFg%2F16.png?generation=1632840487901180\&alt=media)

4\. You now need to change the location by typing **cd /home/ubuntu/icdsServer2**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DNWI4APMdS8gSE%2F17.png?generation=1632840487855675\&alt=media)

5\. Now start the new instanc&#x65;**: 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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DO1qcv2l8Ze0Mn%2F18.png?generation=1632840488063157\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DPtVA5KmT-zSog%2F19.png?generation=1632840488059165\&alt=media)

## 5.0 – Creating an Additional DB Username / Login

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DQzaXGks92x9P4%2F20.png?generation=1632840488066138\&alt=media)

2\. Select Server Roles on the left-hand side of the dialog, and check **Public**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DR_wg7OI5sXbui%2F21.png?generation=1632840487839401\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DS5Nylpu3J2M7p%2F22.png?generation=1632840488064241\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DTWaiWfg7A12MI%2F23.png?generation=1632840488066732\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DUu1H87ikDz-l_%2F24.png?generation=1632840488059981\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DVEBEG6jH9qoIT%2F25.png?generation=1632840488138036\&alt=media)

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)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DWDWHS9Wj4ih9u%2F26.png?generation=1632840488059916\&alt=media)

7\. You will get the below left popup. Select OK and you get the below right

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DX-nK2duTRT07b%2F27.png?generation=1632840488096867\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DYkqEpSPwIAUun%2F28.png?generation=1632840488077656\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DZlDFugbtWLFzY%2F29.png?generation=1632840487851754\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7D_hsgT8-z3uR8U%2F30.png?generation=1632840488065331\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DaPyWA90H3P177%2F31.png?generation=1632840487848143\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DbIiVzESf8UTPE%2F32.png?generation=1632840488156463\&alt=media)

3\. Select the database that requires restoring

4\. Select the **Maintenance & backups** tab and scroll to the bottom section called **Snapshots**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DcUA13Tl0MxBpT%2F33.png?generation=1632840488155452\&alt=media)

5\. Select the snapshot that you want to restore to by selecting the checkbox and the selecting **Restore**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DduZ845yxQFoa1%2F34.png?generation=1632840488195271\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DepX3YCr2S3pKr%2F35.png?generation=1632840488062802\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DfpSMwOGMI4_h_%2F36.png?generation=1632840488062278\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dgbf0VPXX_tds7%2F37.png?generation=1632840488112262\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dhf-LE4YKdKyNZ%2F38.png?generation=1632840487861842\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DiS5SDRiISpxhm%2F39.png?generation=1632840488071135\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DjoqHPlNcQvFWH%2F40.png?generation=1632840487857120\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dkzo8MbKUBFHac%2F41.png?generation=1632840488066743\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dl5i-7SMRJFhmP%2F42.png?generation=1632840488185514\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DmZN6Hdq8-HKcL%2F43.png?generation=1632840488071771\&alt=media)

5\. Select the top left cell in the data table, right click and select **Copy with Headers**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dn5Dt7D9BVIOdO%2F44.png?generation=1632840488184997\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DovULh_RauG_5i%2F45.png?generation=1632840488078225\&alt=media)

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…**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dp_vHRTzae0a0r%2F46.png?generation=1632840488142284\&alt=media)

12\. Select **Next**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dq7J-F69g7DM6N%2F47.png?generation=1632840488068290\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DrpffSNta_Qg-f%2F48.png?generation=1632840488154872\&alt=media)

14\. Preview the data. Have a check and select **Next**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dsx1QKkUoHR4VN%2F49.png?generation=1632840488143493\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dtgh8C8Ps2Tr17%2F50.png?generation=1632840488139797\&alt=media)

16\. Select **Next** and then **Finish**. Once the results section indicates **Operation Complete** select **Close**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DufUcnK9sp_6uQ%2F51.png?generation=1632840488067894\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DvwdH7tTUE32Jx%2F52.png?generation=1632840488106335\&alt=media)

18\. From the toolbar select **New Query**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DwmIR7bePJNWX5%2F53.png?generation=1632840488060399\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Dx-GqQlcaTw5Qv%2F54.png?generation=1632840488081281\&alt=media)

21\. The Messages section will update to show the query was executed successfully

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DyRW2mnwGb0uaZ%2F55.png?generation=1632840488085109\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7DzrRVI6o5peebC%2F56.png?generation=1632840488193065\&alt=media)

A good guide to SQL commands can be found at the below web link

[SQL SELECT Statement (w3schools.com)](https://www.w3schools.com/sql/sql_select.asp)

## 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**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E--FEk53XZgbhq%2F57.png?generation=1632840488146565\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E08dm5cgkCA5dN%2F58.png?generation=1632840488060251\&alt=media)

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

i. The reason to allow all public IP addresses is because it is difficult to know the relevant public IP addresses for each rig computer which is out with the company’s network. Setting a range here could mean some rig computers are unable to communicate with the ICDS

ii. For larger companies who have the relevant IT structure, they may want to set an IP range for computers in their network. This is more secure

iii. If a company does select an IP range, and we end up having to provide support, they may need to add our IP addresses in as a rule otherwise we will not be able to access

**3. Rule Three:**

a. Type: Custom TCP

b. Port: 41433

c. Select the security group assigned to the RDS

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E1h6ujufHfEy8a%2F59.png?generation=1632840488073901\&alt=media)

## 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**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E2-1FWrRlSlM2X%2F60.png?generation=1632840488175990\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E3othGjjtUQHwx%2F61.png?generation=1632840487894158\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E4Q0TfK1wuJgHI%2F62.png?generation=1632840488064367\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E5YOYIrA99U2Wj%2F63.png?generation=1632840488066790\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E6alGuhWGMg1AA%2F64.png?generation=1632840487965877\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E7NUF6GVvOEfcO%2F65.png?generation=1632840488069789\&alt=media)

3\. Select the **Network Latency** button. A window will open displaying the average round trip time for 10 queries to the server database

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E81g3luEfhYuIc%2F66.png?generation=1632840487975062\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E9EJrC7_908b8q%2F67.png?generation=1632840488141970\&alt=media)

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

Well permissions have been put in place to give the admin control over what computers can pull what wells via the remote data fetch functionality from the SQL server database, if required. This might be the case when a company employs consultant rig personnel, who they do not want to have access to their historical well data. In order to access and setup well permissions follow the below steps:

1\. Log on to the SQL server database via Well Seeker Pro

2\. Once connected, select **Tools > Well Permissions**. This will open the Well Permissions dialog. Note that only Well Seeker users with Admin permissions can access the Well Permissions dialog

3\. Well Permissions can be set to two states:

a. Enable Individual Well Permissions **disabled**. To select this option uncheck the **Enable Individual Well Permissions** check box. This allows any company computer with Well Seeker installed on and a user who has the EC2 IP address and port number details to pull any and all well data from the SQL server database via the Remote Data Fetch dialog

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EAVYkSmPp_p4w4%2F68.png?generation=1632840487879314\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EBiZkDpKKeGtIF%2F69.png?generation=1632840488143214\&alt=media)

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

## 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 configICD&#x53;**.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**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7ECZ9P7MGkTOjjg%2F70.png?generation=1632840488149733\&alt=media)

3\. Select **Instances (running)**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EDL4D6XPDFevd0%2F71.png?generation=1632840488146847\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EEimIxJgPXoHDV%2F72.png?generation=1632840488187611\&alt=media)

5\. Under **Elastic Block Store** select **Volumes**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EFfEL5vUeicO8U%2F73.png?generation=1632840488137759\&alt=media)

6\. Select the volume that the EC2 is using. Select **Actions** and **Create Snapshot**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EG1_uyBOnJGjho%2F74.png?generation=1632840488202045\&alt=media)

7\. Enter a **Description** and select **Create Snapshot**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EHOnRKNdfuHDm5%2F75.png?generation=1632840488218183\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EIXIN7lHWEKHcu%2F76.png?generation=1632840488161952\&alt=media)

10\. Select the relevant EC2 instance and select the **Storage** tab

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EJ9Ug15wQx-uwd%2F77.png?generation=1632840488211579\&alt=media)

11\. Select **Replace root volume**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EK13-HqXdfdQhS%2F78.png?generation=1632840488180856\&alt=media)

12\. Select the desired snapshot from the dropdown menu and select **Create replacement task**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7ELdijkGXJEs-PF%2F79.png?generation=1632840488175981\&alt=media)

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

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.

### 18.1 – SQL Server Management Studio (SSMS) RDS Login

If the user receives an error message and cannot log in to the RDS via SSMS then follow the below steps:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EMDmfq8PKG0Ajo%2F80.png?generation=1632840488145939\&alt=media)

1\. Check the user’s computer has internet connectivity

2\. Check the Server type is **Database Engine**

3\. Check the Server name is the RDS endpoint, immediately followed by a comma, then a space and then the RDS port number, which is usually 41433. For example:

a. RDS Endpoint = exampleendpoint

b. RDS Port = 41433

c. Server name entered = **exampleendpoint, 41433**

4\. Check the authentication type is **SQL Server Authentication**

5\. Check the Login entered is the RDS Username the user created when setting up the RDS

6\. Check the Password is the RDS password the user created when setting up the RDS

7\. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 12.1 RDS for more details.

Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser

### 18.2 – Well Seeker Pro Database Login

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:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7ENPEZMSd_YP_0x%2F81.png?generation=1632840488149146\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EORihmV7W4nPD0%2F82.png?generation=1632840488166394\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EPDsfjlJtwVPjM%2F83.png?generation=1632840488162922\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EQd4TfXVp4TVi1%2F84.png?generation=1632840488159352\&alt=media)

9\. If the above checks still haven’t fixed the problem the remaining potential cause is the RDS security settings. Log on to the AWS account, select the RDS in question and review the security settings. See section 12.1 RDS for more details.

Note that if individual IP addresses have been specified in the security rules, it is not uncommon for a network router provided by a third party to change a computers public IP address. To see a computers public IP go to ip4.me in your web browser

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7ERkzd7aLvcsxJ3%2F85.png?generation=1632840488156728\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7ESnlrKl4IF9LqT%2F86.png?generation=1632840487996297\&alt=media)

3\. Ensure that the option **Push External Files** is selected on all computers trying to use the functionality

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7ET3LDXao_QTK9E%2F87.png?generation=1632840488191704\&alt=media)

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

## Appendix A – Login To WinSCP

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EUE5RK4BKNVLw8%2F88.png?generation=1632840488040796\&alt=media)![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EV_WJLM4hmXO1K%2F89.png?generation=1632840488145813\&alt=media)

8\. Click login and click **yes** to the security notice.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EWx0NnvkQCdc_r%2F90.png?generation=1632840488041091\&alt=media)

9\. You will now have the below, where you have created a drag and drop file explorer interface to the AWS EC2. If you do not see the Ubuntu folder on the right, its likely because you are already in it. Just select the only folder showing and it should then display the ubuntu folder.

**Note**: If you have been using the original database prior to setting this second database up, and have been performing data fetch operations, you may find there are a lot of zipped folders named “**Pull Files**” now present in the window, where there were previously none. This is expected.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EXQg8Vv9QmWFrE%2F91.png?generation=1632840488151745\&alt=media)

## Appendix B – Login to PuTTY

1\. Open PuTTY

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EYgDo94jpD_tus%2F92.png?generation=1632840488165593\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EZok5ZZdR9m0DM%2F93.png?generation=1632840488168233\&alt=media)

3\. Then click on **Connection - SSH – Auth.**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7E_iXEFYMnh1tsY%2F94.png?generation=1632840488138233\&alt=media)

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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EafChiR9q98jln%2F95.png?generation=1632840488144608\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EbessKlmkIxgvG%2F96.png?generation=1632840488149289\&alt=media)

3\. Stop the ICDS server. Type: **pm2 stop icdsServer**

4\. Now start the ICDS server. Typ&#x65;**: 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.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EcNzw7zLoENdTR%2F97.png?generation=1632840488153050\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7EdgYRdqCBd9oVO%2F98.png?generation=1632840488053673\&alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fintroduction%2F-Mkgppnt2wWrZZOsaaoR%2F-Mkgs7Eels5zloaFB4Pg%2F99.png?generation=1632840488196547\&alt=media)


# Vantage Guides

A selection of guides for using the features in the Innova Mobile App and Web Portal


# Automated Bit Grading Guide

This document teaches the user to use the ZerdaLab AI-based automatic bit grading system, integrated into Innova Vantage and Vision mobile app.

### 1.0 - Introduction

Manually grading drill bits is a subjective process, as it relies on individual expertise and experience of the assessors, as well as the assessment conditions, all of which can vary considerably.

Innova has teamed up with ZerdaLab to provide an AI-based grading system within Innova Vantage and Vision, which implements an objective, consistent and unbiased methodology wherever it is employed across the company.

This document will guide the user through the specifics of the setup and operation of this feature.

### 2.0 – Setup

This integration is only available via Innova Vantage and the Innova Vision mobile app. The user therefore requires the following to be able to access this feature:

* **Server Database Access**: Vantage and Vision operate with a server database, therefore access to a server database is required. This feature does not work with a local database.
* **Login Credentials**: The user must have login credentials that give them access to the Vantage and Vision. In addition this access must include user permissions that allow them to **add** as a minimum. Read only permissions will **not** allow the user to access this feature.
* **Stable Internet Connection**: This feature requires the user to upload images to the server database using either their phone, tablet or computer, which will require an internet connection

The grading is accessed directly via the Drill String Page, and the user requires the following setup:

* The database tree needs to be populated down to Actual Well Level
* There needs to be at least one BHA available
* The BHA needs to have a minimum of a Bit entered

### 3.0 – Required Inputs

Please note that this feature will only work for **PDC bits**. Tri cone bits must be dull graded manually in the conventional way.

For the automated bit grading to operate optimally, follow these rules:

* Upload one image of each blade and one image of the face of the bit. Do not upload multiple images of the same blade.
* The image of each blade must show all cutters on the blade and clearly show the face of each cutter.&#x20;
* All images should be well lit and clear, without any blurring.

The image below shows examples of good pictures to upload. Note, it is useful, but not required, to label the blades as this helps to ensure each one is photographed, with no duplicates.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBRcgSnFrTxT1kLgX6s1c%2F0.png?alt=media" alt="
" width="563">

### 4.0 – Innova Vantage Interface

The following section details the required steps to grade a bit using the automated feature in Innova Vantage.

* Login to [Vantage](https://www.icpwebportal.com/well-list) using valid login credentials
* From the Wells List page, search for the desired well and then select it from the list

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FObWRGN1xYjTmops6Q5RP%2F1.png?alt=media)

* Access the Drill String page, via the left hand menu. If there are no BHA’s here, then one must be added before you can proceed to the next step. The BHA must also include a bit.

![
](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOmkxP58K3IVDW0jvhxUm%2F2.png?alt=media)

* Select the 4 squares beside the appropriate BHA and select the BHA images option

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fol9oe39tXs4ZnQWqkcn7%2F3.png?alt=media)

* Images can now be uploaded. This can be done individually by selecting the picture icon to the right of each image, or by choosing **Select Multiple** from the bottom of the dialog.
  * Images can also be deleted individually or all at the same time via this dialog.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUwtIWokgu57hPgga2mCo%2F4.png?alt=media" alt="" width="563">

* Once an image has been uploaded, a new option will become available at the top right of the picture where the user can identify the picture as a drill bit.
  * This is important as this dialog is for any relevant BHA pictures and is not exclusively for drill bits.
  * Once a **minimum of 4 pictures** have been identified as drill bits, click on **Grade Bit** at the bottom of the dialog to run the ZerdaLab bit grading feature. Depending on the number of blades, you may require more than 4 oictures to accurately grade the bit.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnnnGoQj3qc9XYtQj9ZSy%2F5.png?alt=media" alt="" width="563">

* Wait for Vantage to contact the ZerdaLab server. After a minute or so, the Bit Grade dialog should appear with the results.
  * The user can then edit the results if they wish.
  * The **Bearing** grade will default to **Not Applicable**.
  * The output cannot provide the **Gauge** or **Reason POOH** results. The user must enter these manually.
  * Once the user is happy with the bit grade, they should click **Accept** to save the results.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDPPsAEshomP0jeozs417%2F6.png?alt=media)

* The results will be saved to the **Grade Out** property for the bit belonging to the selected BHA.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjmA35yeOzLcbWWIBPZYi%2F7.png?alt=media)

### 5.0 – Innova Vision Interface

The following section details the required steps to grade a bit using the automated feature in the Vision mobile app.

* Login to Vision using valid login credentials.
* Select the desired well from the Wells page by tapping on its name in the list.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNKzjG5GJuZjmf620nhQK%2F8.png?alt=media" alt="" width="223">

* Access the Drill Strings page by tapping on the **BHA** option at the bottom of the screen.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSZ0ukw0TVXiwuPQBQVkh%2F9.png?alt=media" alt="" width="219">

* Scroll to the desired BHA and tap the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmU2adcJoJVInK4pWi6NS%2F10.png?alt=media) **BHA Images** icon beside its name. If there are no BHA’s here, then one must be added before you can proceed to the next step. The BHA must also include a bit.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9pNF2xfav48rygTIeKYJ%2F11.png?alt=media" alt="" width="314">

* Images can now be uploaded.
  * Upload individual images from your phone gallery by tapping the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSc4d8KW4XyPEubCkOGsH%2Fimage.png?alt=media&amp;token=1ce86144-7409-4478-a1f0-268e8ba85dee" alt="" data-size="line"> icon.
  * Tap the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FM0miumg4NqafyHlvR0dF%2Fimage.png?alt=media&amp;token=538dfcb3-61a2-4b71-b2ef-d3b95c84199e" alt="" data-size="line"> button at the bottom of the dialog to upload multiple pictures at once from your phone gallery.
  * Tap the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsNC7wFLeuJze88kyzxgZ%2Fimage.png?alt=media&amp;token=77c2729c-c572-45d2-8039-84e48d8b559e" alt="" data-size="line"> icon to upload an image using your phone camera.
  * Images can be deleted by tapping the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXDhBkqqD3mvyI01Ewj6X%2Fimage.png?alt=media&amp;token=fef35aca-b3d4-490f-a7ab-03147eccc07f" alt="" data-size="line"> icon beside each image.
  * The <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZm7wat3slCscuZutnlOS%2Fimage.png?alt=media&amp;token=e5c6c063-ab66-41e5-bf63-49ff48a8aa4b" alt="" data-size="line"> button at the bottom will delete all images.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDopdHhTsgeEvx78LTxHG%2Fimage.png?alt=media&amp;token=a9eba9cf-0902-41ae-a5bf-8542874c2137" alt="" width="237"><figcaption></figcaption></figure>

* Tap the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9u9k8v4kk4vE4PngfgYc%2Fimage.png?alt=media&amp;token=98f8c75c-d92d-4624-8885-f60f72e1150a" alt="" data-size="line"> icon beside each image to identify the picture as a drill bit.
  * This is important as this dialog is for any relevant BHA pictures and is not exclusively for drill bits.
  * Once a minimum of 4 pictures have been identified as drill bits, tap the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9rhx2ReiM6GkSsqtLwNd%2Fimage.png?alt=media&amp;token=62101a38-51ef-4b21-8bcd-a34782b59da4" alt="" data-size="line"> button at the bottom of the dialog to run the ZerdaLab bit grading feature.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsWFs97SAWn2ORIUJM2pQ%2Fimage.png?alt=media&amp;token=0929c59e-510d-44ec-ae57-3e5e8fffe70a" alt="" width="317"><figcaption></figcaption></figure>

* Wait for Vision to contact the ZerdaLab server. After a minute or so, the Bit Grade dialog should appear with the results.
  * The user can then edit the results if they wish.
  * The **Bearing** grade will default to **Not Applicable**.
  * The Output cannot provide the **Gauge** or **Reason POOH** results. The user must enter these manually.
  * Once the user is happy with the bit grade, they should tap **Submit** to save the results.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDkeLgA4K3Aq1Ad2l5Wxw%2F21.png?alt=media)

* The results will be saved to the **Grade Out** property for the bit belonging to the selected BHA. To view the bit grading, return to the Drill Strings page and tap on the desired BHA to view its components.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPsqB5dREIP6QyH5bQwdP%2F22.png?alt=media)

* Tap on the Drill Bit component in the list.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8Jziog97FywAm8AlUn1y%2F23.png?alt=media)

* Scroll down to the **Grade Out** field. The bit grading can be edited by tapping on it.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyxJ9k1piB8avJlLcVQe1%2F24.png?alt=media)


# Oasis Integration Guide

A guide to integration with the Oasis ERP software by Merge Solutions, using Well Seeker X and Innova Vantage

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 Innova Vantage is contained under the **Well Seeker Pro Guides** section. To view it, follow the below link:

{% content-ref url="/pages/NaLeWnEoct4ZdC9jmI6B" %}
[Oasis Integration Guide](/introduction/legacy-documentation/quick-start-guides/well-seeker-pro-guides/oasis-integration-guide)
{% endcontent-ref %}


# Providing 3rd Party Access to Your Organizations Server Data

Guides a company administrator through creating a user on the Web Portal or Mobile App that is restricted to specific operators, products or features.

## 1.0 - Introduction <a href="#toc135722907" id="toc135722907"></a>

Your organization may wish to give third parties permissions based access to your server database data, so that they can view progress on drilling projects etc., via Vantage. To do this in a way that keeps your data secure and that respects the confidentiality of other clients, third party levels of access must be controlled.

The User Management section in Vantage contains options that allow you to customize the level of access for users viewing your organization’s data. Users can have their access customized in the following ways:

* Their permission to create new data, and edit or delete existing data. Removing all permissions turns the user into a ‘**view only**’ user, who can view data but not edit it.
* Their access can be restricted so that they can only view data for specific operators or wells.
* Their access to Products & Features can be restricted.

There are 2 different ways a third party user can be given access to a database:

* The first way is to create a new user within your organization and assign the appropriate role to this user. In this situation, everything about this user is controlled by you as a company administrator.
* The second way is to provide access to a user who already has login credentials for a different company. For example, an Operator may already have their own server database, where they have logins for all the appropriate members of their team. In this situation, it is possible to provide access to your companies database to one or all of these users. When doing this, the admin will assign an appropriate role and can restrict access to wells and features, but overall management of this user is controlled by their own admin.

This document will guide an admin through the process of adding a user in both of the above scenarios.

**Note: To perform the steps in this guide, you must be logged into the Web Portal as a user that has Admin permission and access to the User Management feature. To check your available features and permissions, click on the click on the Account Settings icon in the top right of any page and select Profile.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpSprZ1dArna5ANC5XB9G%2Fimage.png?alt=media&amp;token=4e213d39-22aa-48a9-9003-90ba10f6bd56" alt="" width="292"><figcaption></figcaption></figure>

## 2.0 – Creating a Restricted Role <a href="#toc182993732" id="toc182993732"></a>

User access is controlled through the creation and assignment of roles. A role is a set of user permissions that can be applied to multiple users. Follow the below steps to create a customized view only role that can then be applied to any user in your organization, and also any user from outside your organization:

1. Click on the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fbzt90ZeZpe8P1eT92IUA%2Fimage.png?alt=media&amp;token=23985649-0844-489c-b811-962b8969e2f1" alt="" data-size="line"> icon in the top left to open the main menu.
2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Roles.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbTeeFu2kEUZ7nfNdj5rJ%2Fimage.png?alt=media&amp;token=d40b1a01-abdc-4cc2-afc8-a005c021334d" alt="" width="269"><figcaption></figcaption></figure>

This will open the User Roles page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMNwohvqiAA0W4jEG7z6a%2Fimage.png?alt=media&amp;token=06f66722-c3de-456a-a518-bcae6bc695ec" alt=""><figcaption></figcaption></figure>

3. Create a new role by clicking in **Add Role** in the ribbon menu and filling in the fields in the dialog:
   1. Enter a name for the new role in the **Name** field.
   2. Give your role a brief description in the **Description** field
   3. Check the desired permissions for that role.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fo4KlgtVjvG7vMehCmNKG%2Fimage.png?alt=media&amp;token=463f945b-138e-4bae-8783-46ff5551351e" alt="" width="374"><figcaption></figcaption></figure>

4. Once you have filled in all fields, hit **Create** and the new role will be automatically added to the list. If you need to edit a role, select it by left clicking on it and then select **Edit** in the ribbon menu.
5. Left click on the role to select it, and then select **Operators** in the ribbon menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPKgCJSJ8SQFL95oF4YJX%2Fimage.png?alt=media&amp;token=6afa6fe9-27d9-4f4a-81af-3eee3d71b8c5" alt=""><figcaption></figcaption></figure>

6. Restrict the operators that the new role can access by checking **ON** the operator(s) that you want to grant access to, while leaving the others toggled **OFF**. In this example, we are allowing the role to only view data related to the operator ‘Black Oil & Gold, LCC’. Click on **Apply** to save your settings. **Note: Leaving all operators checked OFF will allow the role to access ALL operators.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FoDjiZrHrKBaQg3d8AuLm%2Fimage.png?alt=media&amp;token=0c0cd842-2dc1-482a-87e3-66520150cd51" alt=""><figcaption></figcaption></figure>

7. Click on the role to select it again, and select Products & Features

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVt3M5mK4yKSb0fFYYID5%2Fimage.png?alt=media&amp;token=d43784de-b09d-4087-a204-9e19def4c2cd" alt=""><figcaption></figcaption></figure>

8. Choose which features the new role will have access to in Vision, Vantage, API, Well Seeker and Vantage Data Link by checking the checkboxes in their respective columns.\
   If you allow access to any features in a column, you must also check the **Base** feature at the top of each column.

**Note:** Toggling off the **Base** feature available for Well Seeker will prevent the user from logging into your organization’s server database via Well Seeker. This is recommended if you are setting up a viewer only user, as the permissions defined in step 4 do not apply to Well Seeker. Access to other features in Well Seeker are controlled by the user’s license and cannot be restricted via Roles. The assigned operator access will apply when the user logs into your organization’s remote server database via Well Seeker.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSpvVqqMu5PVMHwAGrjoS%2Fimage.png?alt=media&amp;token=05109d8b-fcee-432b-afd8-2caeb476c5bd" alt=""><figcaption></figcaption></figure>

9. Click on the **Apply** button in the Products and Features window to save your settings. Setup of the view only and operator restricted role is now complete. The next step is to assign the role to a user.

## 3.0 – Assigning the Role to a User <a href="#toc182993733" id="toc182993733"></a>

Now that the customized view only role has been created, it needs to be applied to a user.

### 3.1 – Assigning to an Existing User <a href="#toc182993734" id="toc182993734"></a>

1. Click on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2t8jcYYOTZ2vugqZphtQ%2Fimage.png?alt=media\&token=51523cff-7859-4ef3-b5f9-318167aec27a) icon in the top left of the page to open the main menu. You can also access the Users page by clicking on Users option in the ribbon menu of the Roles page

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F89EF4EVDfxG5nNAQVPqi%2Fimage.png?alt=media&amp;token=d0f487c6-ccf4-4330-ab67-97da59324449" alt=""><figcaption></figcaption></figure>

2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Users.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlkLXDZ2YFoTxHuVCXVdk%2Fimage.png?alt=media&amp;token=1ce20570-a9fd-423b-8b07-06aabc5e5293" alt=""><figcaption></figcaption></figure>

This will open the Users page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fe9L5ViOUss3tHRlnsR0c%2Fimage.png?alt=media&amp;token=be1c58d3-ebd5-4179-9c3e-ff70033a60d9" alt=""><figcaption></figcaption></figure>

3. Left click in the Role for the existing user and select Edit in the ribbon menu to open the Edit User dialog where you can change the role users role. This is why it is important to name your roles appropriately, as this list may have quite a number of options available to choose from.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBWYnBCjDDe69LpjSM0EF%2Fimage.png?alt=media&amp;token=47407cce-e82c-4827-9a7e-6a9bb158611f" alt=""><figcaption></figcaption></figure>

4. When the user next logs into Vantage, they will now be restricted to the operators and features permitted by their Role. They will also not have permission to make any changes to the data in the database.

### 3.2 – Creating a New User and Assigning a Role <a href="#toc182993735" id="toc182993735"></a>

1. Click on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDlF9cw77OZFZeB8M8ryK%2Fimage.png?alt=media\&token=f059d04e-603e-49c5-9a0a-ebc64ff507a6) icon in the top left to open the main menu.
2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Users.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQKvejrMm0OjCLLiqDGP5%2Fimage.png?alt=media&amp;token=038b1167-1b3b-4d15-a9bf-a6b92a1b1a22" alt=""><figcaption></figcaption></figure>

This will open the Users page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpRAmsCYQh39rR1UygOqS%2Fimage.png?alt=media&amp;token=d481efd9-5239-44b0-8659-f671c17feb72" alt=""><figcaption></figcaption></figure>

3. Create a new user by clicking on **Add User** in the ribbon menu and filling in the fields in the Add User dialog.
   1. Email: Enter an email address for the new user in the Username field. The username must be a valid email address.
   2. Role: Select the restricted role that you created from the dropdown list.
   3. Units: select the default unit set for the new user. They can change this themselves after they log in.
   4. Group: Select the desired group in the dropdown list.
   5. Type the password and check the **Require Password Reset** option if you wish the user reset their password in the first access.

Left click on the User and select **Edit** in the ribbon menu to open the Edit User dialog where you can change the users details

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FoxU8tEtvQVmntAnMIan1%2Fimage.png?alt=media&amp;token=7cc5de66-4d3e-4cd7-86bb-69fcbb47b4cd" alt=""><figcaption></figcaption></figure>

4. Once all of the required fields have been filled in, the new user will automatically be added to the list of users for your organization.
5. When the user logs into Vantage, they will now be restricted to the operators and features permitted by their Role. They will also not have permission to make any changes to the data in the database.

## 4.0 - Additional Access Tools in the Users Page <a href="#toc182993736" id="toc182993736"></a>

Once a user has been assigned a role in the Users page, they can be granted access to additional operators beyond those defined by their role. They can also be restricted to specific wells, if required. To do so, follow the below steps:

### 4.1 – Access to Additional Operators <a href="#toc182993737" id="toc182993737"></a>

1. In the Users page click on the desired user and select **Operators** in the ribbon menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQWXp9ylUnKw9q6RErkAL%2Fimage.png?alt=media&amp;token=02af76e9-a76e-40d9-bc09-095317ec9d6d" alt=""><figcaption></figcaption></figure>

2. Toggle **ON** operators that you want the user to be able to access. Click on Apply to save your changes. The chosen operators will be **added** to the permitted operators granted by the user’s role. In this example, the user’s role grants access to Black Oil & Gold, LLC, but this specific user has also been granted access to Venture E\&P and Gold Resources.
3. Click on **Apply** to save your changes.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmAuZdNBbnYQNRuiaWjRF%2Fimage.png?alt=media&amp;token=906c7b7d-c76d-4e8a-8263-a9689f2af4dc" alt="" width="316"><figcaption></figcaption></figure>

### 4.1 – Well Restriction <a href="#toc182993738" id="toc182993738"></a>

1. In the Users page, click on the desired user, and select **Wells.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FG6qrXfPbg9IORXgV42k1%2Fimage.png?alt=media&amp;token=16f56455-d2a7-444b-9b17-32f9da92d589" alt=""><figcaption></figcaption></figure>

2. This will display a list of all wells contained under the operators that the user can access. The list can be filtered by typing in the search bar at the top of the list.\
   By default, the wells will all be toggled **OFF**. When this is the case, the user has access to **ALL** wells under the operators permitted by their role.\
   To restrict access for the user, toggle the wells you want them to be able to access **ON**. The user will now only be able to access wells that have been toggled on, and will not be able to access any wells that are toggled off.
3. Click on **Apply** to save your changes.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjKeJjfnt5Ih1Y5aTw9aK%2Fimage.png?alt=media&amp;token=08800364-afca-40a1-bc57-d001be64919b" alt="" width="299"><figcaption></figcaption></figure>

## 5.0 – Database Access <a href="#toc182993739" id="toc182993739"></a>

The Database Access page allows you to grant **users from other organizations** access to your organization's server database, using Vantage. To grant a user access to your organization's server database, follow these instructions:

1. Click on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxhkJH3l6JhcZER37acQn%2Fimage.png?alt=media\&token=977c1c68-fe2f-42a9-8563-5f8db0e773e0) icon in the top left to open the main menu.
2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Database Access.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1DwIMuzm6GnBEVxFCaTb%2Fimage.png?alt=media&amp;token=3dc82abf-808d-425c-9946-2f4679ec6c04" alt="" width="230"><figcaption></figcaption></figure>

3. Enter a valid username from another organization into the **UserName** field at the bottom of the page. Note, that if the email address used here is not being used within another Organizations user management, then this process will not work.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeWC1p66BSuLttBuMVl4z%2Fimage.png?alt=media&amp;token=37ab779c-2078-45cf-8cd2-886231d459c6" alt="" width="512"><figcaption></figcaption></figure>

Alternatively, you can grant access to all users registered under another organization by entering the organization's name. For example, typing **Innova** would grant access to all users in the Innova organization. This option removes the requirement to add lots of individual usernames, and ensures any new users are granted access automatically. Contact Innova directly to find out the correct nomenclature for any required organization.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FS1B8kvQXbLj6TYJKKXQX%2Fimage.png?alt=media&amp;token=66461a82-97e2-4448-badf-bb507565ea64" alt="" width="555"><figcaption></figcaption></figure>

4. In the **Organization** field, select the organization that you want to grant the user access to. In most cases, you will only have your own organisation as an option here.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FiUsrow8YMkVKulucAKWc%2Fimage.png?alt=media&amp;token=682aeee3-b088-4738-9766-7285a8a798f0" alt="" width="563"><figcaption></figcaption></figure>

5. In the **RoleId** field, choose the role that you wish to grant the user when they are viewing your organization.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9autBufc9Cyj8uh1yE51%2Fimage.png?alt=media&amp;token=44b943c9-1976-4d50-9df4-a240dcd8b24f" alt="" width="563"><figcaption></figcaption></figure>

6. If the user is successfully added, a row will be added to the table displaying their username and their source organisation to the page. Click on the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1Zo2ZRZxpzMzrT7BcQEw%2Fimage.png?alt=media&amp;token=b523f53f-112b-490f-b917-927d45048c01" alt="" data-size="line"> icon to expand the user, displaying the organisation(s) that they have access to.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrUEspNiXeQJgj5XYIPU9%2Fimage.png?alt=media&amp;token=ca848f95-91b2-4d91-a9db-5b09c39af161" alt="" width="563"><figcaption></figcaption></figure>

Each row in the expanded section displays the following:

**Organisation:** The organisation that the user has been granted access to.

**Role:** The role the user has when accessing the organisation.

**Access Granted By:** The name of the admin in your organisation that gave the user access.

**Access Granted Date:** The date this user was granted access.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNqLQ9Vyn5V4eWV6P3k9N%2Fimage.png?alt=media&amp;token=cbd3f45a-59b5-4626-8067-a6c0fbab04c6" alt="" data-size="line"> **Delete:** Clicking on the dustbin icon will revoke the user’s access to the organization.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fqz1jvrrzdV4goNyx02Ik%2Fimage.png?alt=media&amp;token=32e3774c-8e18-4cf6-ba9e-eff346bdd3e5" alt=""><figcaption></figcaption></figure>

Once a user has been granted access to your organization’s server data, they will able to view wells from both their organization and yours on their Wells List page, when logged into Vantage.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FT0ccS2pHRFL8dfpCnBik%2Fimage.png?alt=media&amp;token=1ae865bc-ef5b-47f8-9a7f-c72e89430e69" alt=""><figcaption></figcaption></figure>

For other pages, they can switch between their organization and yours by clicking on the ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjKqOd9iqrXHxaY7HpgD5%2Fimage.png?alt=media\&token=2bec2d50-45a5-467b-8b49-e7294f2f57dc) icon in the top right of every page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTKGeSVrteeB1GaOuYgYf%2Fimage.png?alt=media&amp;token=836ff6e6-db2f-4c5b-af1b-bce91d8f821e" alt="" width="398"><figcaption></figcaption></figure>


# Innova Vantage - Data Acquisition and EDR Guide

A guide to setting up and running the Electronic Data Reader (EDR) in the Innova Web Portal.

## 1.0 - Introduction

The Data Acquisition and EDR features within the Innova Web Portal allows the user to capture, store, view and manage EDR (Electronic Drilling Recorder) data in real time, or historically.

The purpose of this document is to introduce the user to the Data Acquisition and EDR features in the Web Portal, and detail some of the steps required to correctly setup and use these features.

## 2.0 - Feature and Permissions

To use the Data Acquistion and EDR features within the Web Portal, the organization requires the Data Acq and Real time features to be enabled respectively. Additionally, in order to interact with any of the data acquisition features the user requires **Admin permissions**. It should be noted that to view data in the EDR page, no special users permissions are required.

## 3.0 - Database Tree - Actual Well

The user will need to ensure they have a database structure in place that includes at least one **actual well**, as this is the level in the database tree that the EDR data is associated. Note, that this will not work in a plan, only in an actual well.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTdYGFe911VIUTZRPRxZg%2F0.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FztcUMTBfXluzWQdMsgbO%2F1.png?alt=media)

## 4.0 - Workflow

The following section will take the user through the data acquisition work flow, step by step.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fry6yX1nbv7hcyyj6cQXE%2F2.png?alt=media)

### 4.1 – Data Stores <a href="#toc155956372" id="toc155956372"></a>

The data store is an SQL server database that the EDR data is written to and stored in. The majority of companies will not require to add a data store, as they will use Innova’s own data store by **default**.

However, if a company does want to store data in their own data store, they can. To allow the Data Acquisition system access to store and retrieve EDR data to a company’s own data store, the user needs to input the following SQL Server database credentials for the relevant data store:

* **Name** (generic name given by the user to the store)
* **Server (IP/URL)**
* **Port**
* **Username**
* **Password**
* **Database Name**

To add these details to the Web Portal, the user should select the burger menu at the top left of the screen, then **Data Acquisition > Data stores**. The user can add the details at the bottom of the page next to the green plus icon. Once added the details will appear in the main list at the top of the page.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUpGTvnISkx9WGT5erLBv%2F3.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3ibVRSSDiCQBngiuTTf3%2F4.png?alt=media)

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfgGJG6LRjLOZaoNz88xD%2F5.png?alt=media" alt="" width="214">

The user can test that the connection details are valid by selecting the four square icon and **Test connection**. If successful, the user will get the below message. If unsuccessful, the details should be checked and adjusted accordingly.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdCLb1yq3ZsFsg3BFgjDt%2F6.png?alt=media)

### 4.2 – Data Source Setup <a href="#toc155956373" id="toc155956373"></a>

The data source can be one of the below options:

* **Well Seeker Pro**
  * WITS/WITSML connection to Well Seeker and Send Data to Server
  * Follow this link for a guide: [**WITS Setup & Remote Directional Drilling**](https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/wits-setup-and-remote-directional-drilling)
* **Well Seeker Client**
  * WITS connection to Well Seeker Client and Send Data to Server
  * Follow this link for a guide: [**Remote Client How to Guide**](https://docs.innova-drilling.com/introduction/well-seeker-pro-guides/remote-client-how-to-guide)
* **WITSML**
  * Can be pulled directly into the server
  * Can be pulled into a local Well Seeker Database and pushed to the server

If the data source is to be either Well Seeker or the Well Seeker Client see the above links for documents covering the setup. If the data source is WITSML, then the user requires to input the WITSML server credentials, followed by the configuration. To add the WITSML server credentials to the Web Portal, the user should select the burger menu at the top left of the screen, then **Data Acquisition > WITSML Servers**. The user can add the below details at the bottom of the page next to the green plus icon. Once added the details will appear in the main list at the top of the page.

* **Name** (generic name given by the user to the WITSML server)
* **Server (IP/URL)**
* **Username**
* **Password**
* **Version** (Select from the dropdown list)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsfwUpuhrbszZfCkucCIc%2F7.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVCViaXw4eYXiSMGby2PY%2F8.png?alt=media)

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1UztSO6OJpjRzIQwGYc7%2F9.png?alt=media" alt="" width="235">

The user can test that the connection details are valid by selecting the four square icon and **Test connection**.

### 4.3 – Data Configurations <a href="#toc155956374" id="toc155956374"></a>

Data Configurations is where a user selects a well to associate EDR data with and adjusts any required configuration settings for a real time EDR data connection if required.

#### 4.3.1 - Adding a well

To add a well to the list, the user should select the burger menu at the top left of the screen, then **Data Acquisition > Data Configurations**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1JwsKSQJnRLtm0NdFVMb%2F10.png?alt=media) ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fubh0EO8y2ZV6WChAeo1B%2F11.png?alt=media)

The user can add a well by selecting from the **ActualWell** dialog at the bottom of the page next to the green plus icon. Once selected the below dialog will open, allowing the user to search for and select any actual well in the database. Only actual wells that are not already present in the Data Configuration page listing will be visible. Once the check box for the desired well has been ticked, select the green plus icon and the well will appear in the main list as a new row.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Flpns8lOvclUKVSKlTdae%2F12.png?alt=media)

#### 4.3.2 – Rig State Thresholds <a href="#toc155956376" id="toc155956376"></a>

When EDR data is received live, or uploaded at a later date, it is possible to assign a relevant Rig State to each line of the data. The Rig State defines the operation being carried out at the time e.g. rotating, sliding, circulating etc. In order for rig state data to be inferred based upon the EDR data, the user must first select the rig state thresholds for the well. Select the four square icon for the relevant well and select **Rig state thresholds**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsHzE6JFFjbTL8rRWI2ci%2F13.png?alt=media" alt="" width="181">

Input the desired threshold values. See following video guide for an explanation of rig state thresholds: [**Rig States - Oscillating while Sliding**](https://docs.innova-drilling.com/introduction/video-guides/how-to-videos/well-seeker-pro/daily-reporting/rig-states-oscillating-while-sliding)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNGMX1txGX6auzB2hjcO3%2F14.png?alt=media)

Note that if the **Dynamic Thresholds** option is checked in the **Data Configurations** page, the portal will automatically adjust the hookload and RPM thresholds to better fit the captured data.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FgXTCCnXLB1CumcTiNsip%2F15.png?alt=media)

#### 4.3.3 – Capturing Live EDR Data <a href="#toc155956377" id="toc155956377"></a>

If EDR data is to be captured in real time then the below options need to be configured correctly:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUnJhhh1SUDuGlxEvMZoZ%2F16.png?alt=media)

* **Update Rate(s)** (user defined with a minimum value of 1)
* **Data Source** (Select from dropdown menu from Well Seeker, Well Seeker Client and WITSML)
* **Data Store** (If a new data store was added then select from the dropdown, otherwise leave as Default which will save to Innova’s database)
* **WITSML Server** (Select from the dropdown if a WITSML server was added): Note, this is only available to select if WITSML has been selected as the Data Source

If WITSML has been selected as the Data Source, the WITSML settings need to be configured. Select the four square icon to the left of the relevant well in the table and select **WITSML Config.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFg8pQ3ht8mMnBkNFN8Ht%2Fimage.png?alt=media&amp;token=0ecfa8dd-b08e-4ad1-bd8c-f6f3f6371fae" alt=""><figcaption></figcaption></figure>

In the expanded WITSML Config options, select the correct **well**, **wellbore** and **track** for the well in the tree on the left, and select the desired log type. In the Mnemonics section in the top right, assign the correct WITSML Mnemonic to the EDR parameters you wish to record. All other fields in the WITSML Config options are there for user information purposes and cannot be edited.

Select the four square icon for the relevant well and select **Start reading**. The **Status** will change to **RUNNING**. The data acquisition system will now save EDR data to the data store, and the rig states will be defined and recorded as the data is received.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcPwlIwWagZvQWcc2F2hH%2F19.png?alt=media" alt="" width="187"><figcaption></figcaption></figure>

Once there is no longer any requirement to capture WITS data, the user should select **Stop Reading**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fdao7k9og6fC7IS6gjZoM%2Fimage.png?alt=media&amp;token=6094282a-8085-42d7-b90d-c45cddb8cbfe" alt=""><figcaption></figcaption></figure>

**Note**: The data acquisition system will automatically stop logging for any wells that have data that is static for a period of 48 hours. If this occurs, The reader can be started again at any time if required by the user.

#### 4.3.4 - Loading Historic EDR Data

If EDR data is to be uploaded via a file e.g. a Pason/Totco export csv file, either at points during the well, or after the well is completed, then the user does not need to change any of the below configuration settings.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBW4qe7YlQLCbPlLiNKkn%2Fimage.png?alt=media&amp;token=a5cec6f7-417d-40c1-911c-db4963d47ef5" alt=""><figcaption></figcaption></figure>

Select the four square icon for the relevant well and select **Upload file**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fnpkcut5krQLiTdYstdWx%2Fimage.png?alt=media&amp;token=700d709f-b033-48ab-b9ac-acbdeb4a9a89" alt=""><figcaption></figcaption></figure>

The Import Data dialog will open. Select **SELECT FILES** and navigate to the desired file to import.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJb3RUCyaekcCwDPWeSJG%2Fimage.png?alt=media&amp;token=6196db8e-cf8d-4cf0-8c09-aae866fbaacc" alt=""><figcaption></figcaption></figure>

Once the file has loaded the column and row data will display as below. At the top left of the dialog, select the check box if the data being imported is referenced to UTC (Coordinated Universal Time) and select the Import Mode from the options of **overwrite** and **fill**.

The first row of the .csv file is assumed to be a header row and will display in the top of the table. The row below this (the second row) will be blank, allowing the user to Map the data via dropdown options. This is a critical step, as it identifies the data in each of the columns and ensures they are correctly assigned during the import process. Once completed, select **IMPORT**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOZsHl41jn7fFfX2UUduB%2Fimage.png?alt=media&amp;token=a2ea310f-f972-4f5b-82f9-ac88bb5374ad" alt=""><figcaption></figcaption></figure>

At this point the Status cell will read “**import in progress**”. Depending on the volume of data being imported, and the internet connection, this may take a while to complete. Once successful, the user will receive the pop up message, **File Uploaded**. Close the dialog by selecting **CLOSE**. The status of the file upload can be monitored on the **File History** page (**Burger menu >** **Data Acquisition > File History**).

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fcx71JzrZbpzpw4PNwtK4%2Fimage.png?alt=media&amp;token=65161191-d6c2-4472-bc87-3c186d5c0a3b" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVMPBkmYNhPFEZTD5E4pd%2Fimage.png?alt=media&amp;token=2c44df34-9c0b-4fbb-94e4-f55f51d4d4e4" alt=""><figcaption></figcaption></figure>

The user who initiated the file upload will also receive an email notification when the data upload has completed.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0AE0rET21vV4JOFgb91G%2Fimage.png?alt=media&amp;token=a3a2bdd2-70e1-415c-ae7a-39040cba01b1" alt=""><figcaption></figcaption></figure>

#### 4.3.5 – Managing Data <a href="#toc155956379" id="toc155956379"></a>

Once a well is completed and all the required data has been stored in the data acquisition system the user has options regarding what to do with that data.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDFDFtAJiBpuv824rjP3E%2Fimage.png?alt=media&amp;token=655aa114-77be-42f8-9d31-a03ad8bb5bee" alt=""><figcaption></figcaption></figure>

The user can export a copy of the EDR data for the well to a **.csv** file by selecting **Export raw data**. The user will receive a message notifying them that the export has been queued. The user will be able to monitor the export process on the **File History** page. Note that for large amounts of data, this can take some time. Once the export has completed, they will receive an email containing a link allowing them to download the .csv file, similar to the screenshot below. The file will also be available for download at any time via the File History page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLLoPTUOOEbOHatS3AolX%2Fimage.png?alt=media&amp;token=f56a058b-2f9e-4b7b-9d92-4e3024fbdd6b" alt=""><figcaption></figcaption></figure>

The user can reprocess the rig state data based upon the current rig states threshold values by selecting **Re-Process Data**. By selecting this option, each line of data will be reevaluated based on the current rig states threshold and an appropriate rig state will be assigned. In most circumstances, the user would use this after uploading historic EDR data via the **Upload File** function. However, it can also be used after capturing live EDR data, to regenerate the rig state values based on the currently selected **Rig State Threshold** values.

**Clear Data** is an Innova Admin feature only.

In order to keep the well list in the **Data Configuration** page manageable, the user can **Delete & Archive** the data. This removes the well from the list in the data configuration page and makes it no longer viewable in the EDR page. The data is downloaded and stored as a **.csv** file on Innova’s cloud storage system. The status of the archiving process can be monitored on the **File History** page. Note that for large amounts of data, this this can take some time. Once archiving is complete, the user will receive an email where they can download the data, as if they had exported it. The data can also be viewed, downloaded and restored at any time via the File History page.

### 4.4 – File History <a href="#toc155956380" id="toc155956380"></a>

The **File History** page keeps a record of all EDR data files that have been uploaded, re-processed, exported, archived and restored. The File History page can be accessed by selecting the burger menu at the top left of the screen, then **Data Acquisition > File History**.

In the File History table, the **Wellname** field shows the well that the data belongs to, and the **Status** field shows the task that was performed to generate the record. Clicking on the **>** icon to the left of each record will display a more detailed breakdown of the task, with time stamps.

Users can search for specific records using the search bat at the top of the page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F11PmazXO36HzZ9jeeeL5%2Fimage.png?alt=media&amp;token=76e4acd7-935f-410d-95fe-2195cd495624" alt=""><figcaption></figcaption></figure>

Clicking on the four square icon to the left of each record displays some additional options. Note, these will only be available if the row status is either **Archive complete** or **Export ready**:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FF1MwAoYEu66W24eMSNv7%2Fimage.png?alt=media&amp;token=81d563e9-c1ee-4f08-873d-97989a2dad99" alt=""><figcaption></figcaption></figure>

The **Download File** option allows the user to download the EDR data as a **.csv** file. This csv file, if required, can be used with the **Upload File** function in the **Data Configuration** page.

The **Restore Archive** option will restore the well and its data to the **Data Configuration** page and make the data visible in the EDR page again. This option allows the user to retrieve data that was archived using the **Delete & Archive** function in the **Data Configuration** page.

Archive data can be deleted using the **Delete Archive** option. Note that this is permanent, and any data deleted from the File History page in this way cannot be retrieved.

## 5.0 - EDR Page

The EDR page is where a well’s data, which is stored in the data acquisition system, can be viewed.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FObpKONawIyOheREUd0L5%2Fimage.png?alt=media&amp;token=f8e5ed3f-c9e3-4e89-9644-d49b42ca266e" alt="" width="119"><figcaption></figcaption></figure>

To access the EDR page select the burger menu at the top left of the screen, then **Well Views > EDR**.

The data stored in the data acquisition system for the currently selected well will be displayed. The user can change the referenced well via the well selection option at the top right of the page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FB8wvyx14S40biFyToJ8Z%2Fimage.png?alt=media&amp;token=3a472848-1417-4a9a-bf3c-b78f19629f20" alt=""><figcaption></figcaption></figure>

The EDR page display is broken down into sections:

* Mini-map
* Depth time activity bar
* Charts
* Side tabs
* Additional options

### 5.1 – Mini-map <a href="#toc155956382" id="toc155956382"></a>

The mini map displays the entire wells data set as time vs hole depth, time versus bit depth and time vs activity (colour coded bands). There is also a overlay that displays which section of the well data is current visible within the y-axis and charts sections. The overlay can be resized by dragging the top and bottom overlay edges to the desired time span and then the overlay can be moved by selecting the overlay centre and dragging to the desired location on the mini-map. This is a fast, effective way of being able to view a desired data range.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfeTlWeM59VeXzLwtibYv%2Fimage.png?alt=media&amp;token=37654054-eaa4-4411-a3c0-2967762f4308" alt=""><figcaption></figcaption></figure>

### 5.2 – Depth time activity bar <a href="#toc155956383" id="toc155956383"></a>

The depth time activity bar, displays data relating to the currently selected chart section.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRWdAHPubpYYmj1ZZRl44%2Fimage.png?alt=media&amp;token=b65fd904-5673-4462-b818-6314788bc0c3" alt=""><figcaption></figcaption></figure>

At the top left of the bar next to the chart legends, is tool tip data related to where the user is hovering the mouse cursor on the charts area, including hole depth, rig state inferred activity, date and time. The remainder of the bar displays the y-axis time date increments and the rig states inferred activity coloured areas.

### 5.3 – Charts <a href="#toc155956384" id="toc155956384"></a>

The charts section consists of a user definable number of tracks and each track displays a user definable number and selection of curves. Below is the default layout and configuration.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Flrl5UfcPUGWDXTRbVSgA%2Fimage.png?alt=media&amp;token=d4702158-de73-4f28-8b5f-67ac6481fb27" alt=""><figcaption></figcaption></figure>

#### 5.3.1 – Tracks <a href="#toc155956385" id="toc155956385"></a>

Tracks are the columns that curves can be displayed upon. Users can select to have as many or as few tracks as desired, but will realistically be limited by display dimensions.

To add a track, right click on a track main area and select **Add Track**. The new blank track will be inserted to the left of the track in question. Tracks can also be deleted in this manner.

The **Add Curve** option is also available from the right click context menu. Details of how to edit curve settings once added are included in the next subsection.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmiKc9TpmqvOkBN8Ri0aO%2Fimage.png?alt=media&amp;token=04cad8ff-8ef9-40f1-a60d-a89be269f55a" alt=""><figcaption></figcaption></figure>

In addition to using the mini-map functions, the user can scroll up and down the data using the mouse wheel and zoom in and out using the mouse wheel whilst the Ctrl button is depressed.

#### 5.3.2 – Curves <a href="#toc155956386" id="toc155956386"></a>

Curves are the individual lines that are plotted on the tracks and represent one of a number of predefined mnemonics that are saved in the data acquisition system.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxbKqBkZySc8blW2bLDWq%2Fimage.png?alt=media&amp;token=22daf3ab-e0eb-49ee-a1ba-802683d3ae9b" alt=""><figcaption></figcaption></figure>

To add or delete a curve right click on a curve legend and select the corresponding option.

To edit an existing curve, double left click on a curve legend and the below dialog will open.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkoS9PwHvwNfsfEY1SZOm%2Fimage.png?alt=media&amp;token=675c8c70-b3a6-4305-8364-1981c861e719" alt=""><figcaption></figcaption></figure>

The user can select the curve data type by selecting the **CURVE NAME** and selecting from a dropdown list. Colour is selected by either inputting the colour code, or selecting the colour tile and manually selecting the desired colour. Minimum and maximum display range can also be selected for a curve here.

An existing curve can also be dragged and dropped from one track to another, by holding down the left mouse button on a curve legend and dragging it to the curve legend area of another track and releasing the left mouse button.

### 5.4 – Side tabs <a href="#toc155956387" id="toc155956387"></a>

Side tabs allow additional dialogs to be displayed or hidden based on the users requirements. Below details the current side tabs.

#### 5.4.1. – Well Schematic <a href="#toc155956388" id="toc155956388"></a>

Displays a schematic of the current well. Conductor, casing and liner dimensions and measured depth data displayed is from the actual well **Casing** table. Open hole data is from the survey or slide sheet data, whichever is greater.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FezaTn8Iq0F0C7KqlOqqE%2Fimage.png?alt=media&amp;token=105b73a8-8a9d-440b-84a5-eb695f04aabe" alt=""><figcaption></figcaption></figure>

#### 5.4.2. – Directional <a href="#toc155956389" id="toc155956389"></a>

Displays directional drilling related data for real time drilling operations overview.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrJRNEyKQodsoHNl6YfU1%2Fimage.png?alt=media&amp;token=062d69f0-3a58-45ff-94d8-b3db5a62bce0" alt=""><figcaption></figcaption></figure>

### 5.5 – Additional Options <a href="#toc155956390" id="toc155956390"></a>

In the bottom right of the EDR page the user can hover over the pencil icon to display additional options.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FSLOu924yhDx2I5fOCjMV%2Fimage.png?alt=media&amp;token=7ebd0b3d-2a8c-4151-b869-bbb336b4a681" alt="" width="81"><figcaption></figcaption></figure>

**Reset Curves** gives the user the option to manually reset the curve data layout on the page to the default settings.

**Export to excel** produces an xlsx report that shows all of the raw tabulated data currently displayed within the tracks on the page over the same date/time range.


# Innova Vantage - Engineering Quick Start Guide

A guide to setting up, running and viewing Engineering case data in Innova Vantage

## 1.0 - Introduction <a href="#toc184999193" id="toc184999193"></a>

The Engineering Dashboard is a feature in Innova Vantage that allows the user to run Torque & Drag, Hydraulics, Surge & Swab, Casing Standoff, BHA Analysis, and Well Control calculations on wells located on the server database.

This document will guide the user through setting up an engineering case for their well, running the calculation and viewing the results.

For full details of every component in the Engineering Dashboard page, refer to: [Innova Vantage Manual - Engineering Dashboard](https://docs.innova-drilling.com/introduction/innova-engineering-manual/innova-vantage-manual/6.0-well-views/6.12-engineering-dashboard)

## 2.0 - Select a Well <a href="#toc184999194" id="toc184999194"></a>

Before using the Engineering Dashboard, the user must ensure that the correct well has been selected. The currently selected well is displayed in the top left of the page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FroIRb79zCadizWJvVdl1%2Fimage.png?alt=media&amp;token=b6734e6d-0e65-49dd-9047-bbb95984a634" alt="" width="563"><figcaption></figcaption></figure>

User can select a well by clicking on ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABkAAAAaCAYAAABCfffNAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAH0SURBVEhL7ZXLTxNRFIe/S913yTRhsCUpLsXE6MKYNAZ1rRj/ABOI1T5AEp+J2nba8iiBmIiWKmsCOyiJYW2QsHErC1wJIyVpV11yx4W2MtPLtCWw49ud3zk3X2ZuzozQ9PMWp0yHMzgNziRtIVQX363r3L83YMsOpGRhcQnTNG15KyglI/EYT0ef2DIpJeFIjOVi0Za3wjlnAODp+P8W84VPvE0Z9Vrr7KSnJ1Cva5TLFX5sbTljOEpSY2p6htGRYYQQvEmmAJgvzHGp76JzFIBfOzuE+m9RrVZtuaskNz2Dx+NhOBZFSknCSPNgcEj5JL3BIFkjxY1QiJXVVVtPKTmQEiklAOO5KYQQxKMRLMsimc7we2/PeYT1bxtkjRQXeoOs2B1qycLiEtvbP+v12GQOhCAeeYwQgoSRts03Q7knpmmyXCwS8Pv5vrlBwO9nbGKSd+9neTg0yKsXz5xHXFFKavh8Gpqm4fNpAGTHJyh8nicSDvPyeesiV4mK14kkH/JzRB+FG3bpKNqWACTTGWY/5hm4e8fZUnIsCUAqk+XqtevOWMmxJe3gKimV9uHfojWjNlPa/3vmMMoP5GE217+id3U5YyWWZdF3+UqDqKnE6/Vy+2Y/3brubNkoVyp8WVtjd7fxV9BUchK43slJcSZpiz/vlZdR/RmgfAAAAABJRU5ErkJggg==) icon close to the well name in the Wells Dashboard page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfqdmDH6WUVpru0MGoJoL%2Fimage.png?alt=media&amp;token=d83d4c17-f035-4041-8796-37172a7e1d8c" alt=""><figcaption></figcaption></figure>

By clicking in the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABcAAAAWCAYAAAArdgcFAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAGNSURBVEhL7ZNLSwJRGIbf0XCnK4M20a9o0WW0RbSRVl2w60KdTM2IiDTJUUfy0rLIFla0DamgIrvQIrNx0a/IdJOrdCvYSukcj5Rii6BnNbzvNw+Hb+ZwXd09FfwSCjpoJ/9yJhzrg44aDJiZMkKlUhH5SSKB5O0djg/iRP5eKGDRsURkANBBBwCwtrqCj2IRqdQTkb/lciiXy5AzGQDA/NwsOrVa5PJ5Yq4K8+QvmWdcXF4hGArTVQ2/dxNWwYLXbBZKpRK9fQP0SGs7l3wirIIFYkDCdfKGrms0LZd8IgSzCWJAQvzwiK4JmpJ73K46sbQVYq4Ezcg3XOtw2m0IRaLEifU8D8FsImar/Ejucbuw7LAjFIliN7ZPdHodjwWLmciqfCsf7O+H025DOLpdJwaASqXuZ6vRUF59KS3LmDBOY2cvRo8Arco5jqs9p2WZ6L6iUDRUsC/R48M984ay0Ol4aNRqDA2P0BVbPjk+hmDAD41aTVd1FEsleLwiTs/O6YotbxeNF9YG/q78E1xEfoVEnbHlAAAAAElFTkSuQmCC) icon close to the rig name in the Operations Dashboard page.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtHfJre3ec4KRA3IYp7xE%2Fimage.png?alt=media&amp;token=6fb839c0-f502-4a99-8ea8-55a90238908b" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPXJehgQ7CXxh42s0pVnA%2Fimage.png?alt=media&amp;token=82bb4c85-8a7e-47e3-b0ef-3a19b914c351" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9JWpF66KYbMfa1iXCFWA%2Fimage.png?alt=media&amp;token=ce5713cb-f800-4fb2-8b6a-cc16cc553aec" alt="" width="175"><figcaption></figcaption></figure>

Alternatively, the user can navigate directly to the Engineering Dashboard page by selecting the Engineering quick link within the Operations Dashboard cards.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F57trmby174PBFJsCSNSs%2Fimage.png?alt=media&amp;token=78b039eb-7552-4664-b98e-72a36ea6d284" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4Qc3FfuS3ThH1wkNusoY%2Fimage.png?alt=media&amp;token=119da9e2-a0d3-48cc-bdaa-37a30d719112" alt="" width="267"><figcaption></figcaption></figure>

## 3.0 - Understanding the Layout

The dashboard has two main sections:

* **Inputs** - where the user defines the model
* **Results** - where outputs are displayed

The user can opt to display Inputs only, Results only or both and split view vertically or horizontally by clicking in the ‘Split’ button.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmxW9DATM90lTgUtDqoHp%2Fimage.png?alt=media&amp;token=024e137a-b91d-4bea-a369-b0801795b14f" alt=""><figcaption></figcaption></figure>

## 4.0 - Workflow Overview <a href="#toc184999194" id="toc184999194"></a>

To generate results, the user should follow this workflow:

* Create/Select a case
* Add/Edit inputs
* Save changes to calculate
* View results

Note: Results will not update until inputs are saved.

## 5.0 - Inputs <a href="#toc184999194" id="toc184999194"></a>

Inputs are entered in the Input section. Before entering any inputs, the user should first create or select an Engineering case in the Selected Case section. Once a case has been created or selected, all the input options will then be available to populate.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fpl9iHdTDcoi3hNdinu31%2Fimage.png?alt=media&amp;token=9c7acfa7-7241-4c24-bcc1-31e08a02ae7c" alt=""><figcaption></figcaption></figure>

### 5.1 - Select Case

Different Engineering setups for the well are stored in the Vantage as cases.

If the user selects a well that does not yet have an engineering case, the system will automatically generate a case named Auto Generated Case, which can then be selected from the dropdown. Auto Generated Cases cannot be edited, but they can be copied and used as a starting point for running a manually entered case if desired.

A new case can be created by clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABMAAAASCAMAAACO0hVbAAAAAXNSR0IArs4c6QAAARpQTFRFHyElHyIlHyImIScqICYoICMmICQmICImICUnICMnIzcwICcoISQpJDcwICQnISUqJTsxJT0zJT4zJT0yIjItISYqJDsxJTwyIzYwJDkwJDkxIy8rJDMuJDYwJDoxJToxJj40JDUuJTkxJTsyIzYvISQqIS0qISwrISgoIzkxJD40JD0zJDwzIi8sJ088KFU/KFQ/KFM+JkI2KVU+JkY4JUI1JkI1JkM1KFE9Jkg4KFA9JkU3JkE1KVU/KVY/JkQ2KE07JUA0J0s5JUE1J0g6J007KFQ+KFA8KFI+KE88KVZAKlpBKl9CK15DKFVALXFMLGdIK2FEL39TLG1KLGlIMo9bMINVMpBcMo1bNZ1iNJhgNaNkN65qOrhvvPSfQgAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAADNSURBVChTY2BmYWVlgwNWdjYODgZmTi49fQMYMDTiZuNg4OE1NjE1gwFzC0s2PgZ+K2sBQRgQEhbUF2FnEPWyEUICYrZcDAyithAxcQEwJWYrAReT9PYXF0QVk5IOCJWRFUZWJ2jnExYZ6GsvjNArKB4UHRMbHeUgh2yeo3xwuIIjqnnCiiERSspo9oo72YGsRXGLkLIUkvv8nMEKoEBMX4WRQdXFVUBAGQoEBMzd1FgZ+NXdPdw9YcDdVo4JGH58Gppa2lCgpaPLysEBAA8MLHiS/TfEAAAAAElFTkSuQmCC)icon, or deleted by clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAAUCAMAAAC3SZ14AAAAAXNSR0IArs4c6QAAAO1QTFRFHyUnHSQmHiUnICUnIyYoMyorOywtPCwtOystOSssPSwtOyssNCkqOissOCorNiorNyorMykqMSgqMSkqOCssJicoMCkqJCYoLSgqLigqQi0vUzEyVTEzQi4vTC8wRS4vRC4vVTIzSC8wVjQ1WDQ1WTQ1VDM0QC0uVDEySS8wUjEyWjM0WzI0WjI0ZDc4bDk6azk6Yjc4cjs8Yjc3ej0+bTo6dzw9eDw9fz4/fj4/jEJDjUNDhEBAmkdIm0dIhkFBnUhJn0hJhkFCnEdHl0ZGrUxMuU9QvlFRoEhJoklJoUlJpUpKu1BQu09Q41tbnKyyEQAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAADWSURBVChTVZDXEoIwEEU3RgkJoihYY0Psvffe+/9/jjpqwPO0e+buzJ0FDOgPwOByx3lCwJNuF+AUT2cEaZ7C4DEl4kAyPSBzyhhRqNdLFcIY5fJHMTXbaGTV1/BVxNfcHx6Pw77lI7+Uv33sdLudY9svDjXr1JtMeydLs1XuPJsvZuecU12Wq/Xy4lT5a38w6F/zjlThthkON/eCrZTiaLvbbcdFxa5KAkFdDwa+7Y3Su7SAcgNCZllSBXLZDAEKV6o1Qb0SRoBRJBoTRCMIA/7/9Gt/AqjXIHnqQA3UAAAAAElFTkSuQmCC)icon.

Click on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAMAAAC6V+0/AAAAAXNSR0IArs4c6QAAAURQTFRFHyQmHiMlICUnIygqJissJiosJistJCorLTEzOT4/Mzc5IicpKi8xMDU3MTY4OT0/Njs7Njo8LTI1KjAyKzAyLjM1Nzw+NDk7LzQ2LDEzMDY4LTI0LzU3JiwuJCosKS4wIigqJywuMjc5Nzs9MjY4Mzg5LDI0Mzg6JSosNDk6NTo8Nzw9ODw+Njs8Oz9BOj9BOj9AO0BBPEBCPEJDREhJS09QUFRWWFxdWFtdRElKVFdZTVFTQ0dJRktMSExOSU1PW15gXGBhX2JkbW9xcXN1b3Fzb3JzcHN0d3p7eHp8eXt8Y2ZoZ2prb3FyaWxtaGtsbXBxa25vbG9whIeHk5SUh4mJkJGSjI2PjI2Ok5WWmJmahYeHjY6PgoSFhoiIjo+Qg4WGj5CRioyMk5WVnJ2dhYeIjI6PmZubkZKTkpOUkZOToaKisyZzbwAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAEBSURBVChTZZBnU8JAEIaXwwjE3IKShMSoKAG7QewFg5UoVuyi2Lv//7tLZkLO8Zn7cPfM3u68C4wxEKE3AzrRDimgM+YbBvFEyQmYceQuUqAUZR6CSbnVL9WN2JNWCQ1bTMcAInoGjbmt7Z2qN2/2InJH8iXXzs693b3agmUIsu9icf/y6vqmsZQOK/ntQeNwY3P9rtkvyPujh9mB7ODx49Af+bRsoXrSFOVz/b/EldWXssmVU6ESUdVf17Sc6b2F3xGN3PvH59f3Tz3bHkTZuO26bqWcp1uJEkHB5mSNYYvgyEcSUZKjSXss02a8GKfVMZAKE3rA5JTiL5lBRIQE+wV7kipayx6Y2gAAAABJRU5ErkJggg==) icon to create a copy of the selected case.

Clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAMAAABhEH5lAAAAAXNSR0IArs4c6QAAAUpQTFRFHSImGyAmGyAlGiAlHCEmHyQnHiMmHCImHyQmHiMnICUnLDErOj8uOz8vMzgtJCkoLzQrOT0uNDgtODwtOz8uNTktOTwuKy8pMTYsKi4qNDktKi8qO0AvP0QwPUEvPUIvPEAuPkIvP0MvPUEuPkMvPEEuUVU1RkoxQEQvWl43Sk8zQEUwW143QkYwQUUwSEwyWl03Q0cxSEsyV1s1QUUvT1M0UFM0WF03UFMzSUwyUlY0VVk1Sk4zWFs3WFs2WVw2QkcwREgxXmM4X2M5XGA3X2M4XGA4YGM5YGQ4YGQ5bG88YWQ5bnE8bG87YWQ4dnk/bXA8cXQ+cnQ8fX9Af4JBfoFAm51IgoRCk5VGlJZHgoVCgINBnaBJu75RvL9SsLJOsrRPpadMqatMvb5Su71Rv8BSvsBSz9BX1dVZ19dZxMZVwMJTwMFT7+9gfDepiAAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAADjSURBVChTY+DiYmBkggFmFlYgn5WFm4cXBmT4uNi4GNhlndwRwEONn4NBwFNdTk4eCuQ0NLUYGLR15HVBQEEDROrpO7Mx6BoogpiGXmpKINrIGyakoR7rIwgWcocJKevF+QqhCCkZ+8X7u5joIVQpCgekZ2SGiSjowTTKBXqJhuQm6JmG6ytBzRJLjBCXMBORNM+ykIMKCUamBkcFR4fGZFsqQoVUrJJykpOT01KC5OCOUFJQBAFVZaCNnmwMUu56QB7YjyBhazUGBk4bV1s7GLB305RmY2Dl5HMwhAFHGX4GLgCrwjelQPuWswAAAABJRU5ErkJggg==) icon enables the user to import a case from another well within the organizations server database. The user may search for cases using the search bar located on the top of the dialog by filtering via the column headers. Once the desired case has been identified, the user can select it and click the Import button to complete the action.

### 5.2 - Case Details

After a case has been selected, the other inputs can be entered / edited.

**Description:** User can input the case description/name in this field.

**Active:** Enabling this option designates the currently selected case as the active case.

**Trajectory:** This dropdown allows the user to select between **Composite**, **Surveys**, or **Plan**. When **Composite** or **Plan** is selected, an additional dropdown labelled Well Plan is displayed. When **Surveys** is selected, an edit icon ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAA8AAAARCAMAAAA11AaTAAAAAXNSR0IArs4c6QAAAMZQTFRFHyQmKC0uNjo8OT0/ODw+LzM1ICUnNTk7LTEzKy8xMjY4LjM0LjI0LDAyKS4wIycpJSosOj0/Njo7KS0vJysuLzI0JiosJystMDU2KCwuJywuIicoKC0vJCkrIygqKi4wIiYoJSkrISYoNDc5Mzc5NDg6JCorKi8xOj5ATlFTX2JjbW9wZmhpZ2lqZGhpfH9/a21vcnR1ZWdpeXt8hIaHl5iYg4WGjI6PnqCgx8jH0NDPwMDAzs3Nw8PDy8vLxsXFycjJxMTDSbj8rgAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAACaSURBVChTTY/XEoJADEWjFIm6a0EREMGy2LvYsOH//5S4moHzkJkzd9KgUFSIqarpUDIwo1yBKsuBKpDxGmcMFfJ6Y9E0M2+1l9fIQso79vFyWjmUu3iOb7Mu9TtedH+se/h3xM3ztfWDdJPs78/jZDf46s+H+/fBMuUd0lEbBTKVbqTVS0eRi9w7qAmwQ0GEIhyD7k4I5D58AN5AE0j3fqumAAAAAElFTkSuQmCC)becomes available, allowing the user to add, delete, or edit existing surveys for the well. Clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAAAAXNSR0IArs4c6QAAAM9QTFRFHSImHCEmHiMmHiMnICUnMTYsIicoJispNjstOj4uMzcsNzstOT4uJSopJCkoPEEvPkIvP0MvPEAuPUEvREkxRUkxVFg1U1c1W183RkkxQEQvQkYwQEQwQUYwTFAzUVQ0WVw2Wl42UFQ0SEwyQ0cwQUUwS08yWl02REgwWFw2T1M0VVk1Vlk1XmI4X2I4XmE4X2M5am07Y2Y5cnU+dnk/YWQ4aWw6foFBfoBBlJZGlplHkZNGiIpDlphHiItDj5FGkJJGg4ZBi45Eio1FoKNKwrWlsAAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAACzSURBVChTPc7XEsIgEEDRDUYxVjCKkcQWgz3YW+zl/79JHCFn3+7A7IIN2XpDq2fBBqsas6bGZNWCnNciVCMtLwdYcl8hNeIGPpcY8EKFNmcrtu4EfPEPNN89JedLj+hA2eGa9KlDfR14uJHbnTOITIhIQdw+94dnvoihfL7kaDg2L8jkfUz2RbXNbOFuqeRG6ppfKMeB8H+jiCAuA5rORGo+RZDB4VJqyxBnwEaokkLI/gIAyhuiy+hGIQAAAABJRU5ErkJggg==)icon will open the Tortuosity Editor dialog where the user can add tortuosity to better simulate real life conditions if desired.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6zuZiAPkE0zVxSc0Jo39%2Fimage.png?alt=media&amp;token=a9bf2d9b-dd49-4211-9d70-8a5bc1aa1743" alt=""><figcaption></figcaption></figure>

**Well Plan:** The user can select the plan under that well. Only available when Plan or Composite is selected in the Trajectory dropdown.\
If user doesn’t have a plan, it can be created by clicking on ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYRENNasATv4SiZOhtJST%2Fimage.png?alt=media\&token=2128384c-0559-4ffa-a70d-eb9bb217cbb1) icon. User can also edit the current selected well plan by clicking on ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FIn7WtEWyIlMWH61y569w%2Fimage.png?alt=media\&token=8449aa8c-ca5e-415e-b986-d5fdefd5e06b) icon. These options will open a dialog where the user can quickly add/edit MD, INC and AZI.\
User can refresh data, save changes or discard changes in this dialog.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmmntZ5hR0wyCA38OC0Qv%2Fimage.png?alt=media&amp;token=f80f2c9f-2aa9-4c73-a558-ca3ccf30cc6c" alt=""><figcaption></figcaption></figure>

**BHA:** Select the drill string that will be used for this case. Similar to Engineering Case options, BHA has the same buttons to edit, add, delete, duplicate and import the BHAs. Clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABMAAAATCAMAAABFjsb+AAAAAXNSR0IArs4c6QAAANhQTFRFHyQmICUnLDAyNjs9ODw+Nzw+Nzw9MDU2IiYoLzM1NDk7NDg6NDk6OT0/NTg6JCkrOT4/Mjc5MDU3MTY4KC0vJistKi8xLzQ2KzAyMzg6KC4wLjQ2LjM1LjI0LDEzMjg5NTo8MjY4LDI0KS8xJiwuNzs9KjAyJywuNTk7Oj5AOT5AOz9BO0BBTVFTW19fT1NUX2Jkenx9Zmlqd3l7dXd4bnBxfYCBioyMmZqakZOTjI6OjY+Qm52dj5CRwMDAysrKxcXFx8fHy8vKx8bHzMzLx8fGzMvL2NjXdtK5rwAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAACxSURBVChTbZDXGoIwFINPVRw4KWpBK+6BG7e49/u/kQUZRc3l/yWnTQAhBEEhYCwUjgiuorE4AIKELopJV6l0huWyOQnLvrCeBygMXYSLRJZxX2Fs4DCijlQSZKQ0Pq7KmPfRirHebDHPqGaczrMqn6XK/HI1axr3BtYWt7tZb7Avefeay8dzJzEXx1r71+GDfB+dTNtW0GOsh9TpUqeefe9P369detYuX/sJ9n6/O78BQagbs0CwgM8AAAAASUVORK5CYII=) icon will open the BHA Editor dialog, where the user can rename or edit the selected string.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fm0qSxhaWOxlNkWsO84RC%2Fimage.png?alt=media&amp;token=50095024-e1a6-465c-a422-d916ec4b94a6" alt=""><figcaption></figcaption></figure>

When a BHA is either created, copied or imported from the Engineering Dashboard page, this will be designated as an Engineering BHA, denoted by a blue BHA icon). An Engineering BHA will not be visible in the Drill String page, will not affect any KPI data and will not affect WSX BHAs.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUWHRv8rbSb40WrqVTrCW%2Fimage.png?alt=media&amp;token=80e006bc-e8dc-4e4f-8b88-1975c0a8f1c0" alt="" width="422"><figcaption></figcaption></figure>

Note that editing a standard BHA from the Engineering Dashboard page will edit that BHA in the Drill String Page, WSX and will affect KPI data.

**Hole Section:** Loads in a previously created Wellbore. This option allows the user to store multiple wellbores under the same case, so that they can quickly switch between different casing configurations. A new wellbore can be created by clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABcAAAAWCAMAAAAcqPc3AAAAAXNSR0IArs4c6QAAAM9QTFRFICUnICQnICMmICQmICImIjEtIjEuICIlIjItICYnJDoyJDsyKFM+KVQ/KFQ+KFI9J0s6J007J047J006J087Jks5Jko5J0w6JkY4KFM9J088J1A8J1E8Jkg4JUE1Jkk5Jkk4KFE9J0s5KlxDKlxCKVtBKVxCKVZAK2JGKmNFKmJFKmBEKmNGKmBDKmFEK2ZHK2dILXFMLnpRKmFFLGdHK2RHK2RGK2dHLGdIK2NGMo1aNJdeMYdXMYhYNqdoN61qOLBrOLNtNqRnNqNlOsF0NXVVIwAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAADlSURBVChTbZHpgsEwEICTUEuFNoo4W8QS6r7vYvf9n0nSCqX9fn5zZGYCgASG8Y0EoUQYhAKd1DAfDBUDjlM/frbmslz+TY65aVEBocFMEsZkGEIAAcekEIZgLizMjIynt4IoMUaZD1+M9aXuoVuO5tPK+DKp0Eifam16mdWqX57io3f9v3rHPP14l9Tni9PtvJg3yNc8Tfv33rOb0Tkd92/pxMxv4ZVoHrOX1QoWVvuu1R2eRyLGWt4BsL5f/oL2mbAA2Zt2p/TGbG9s+WMJ4PDVdqrY7vaOcDKAND2rK7K6hoR+AIfPJiZH5aJRAAAAAElFTkSuQmCC)icon, copied by clicking on ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAARCAMAAADjcdz2AAAAAXNSR0IArs4c6QAAAQVQTFRFHyQmHSEjGyAiICUnJSosKi8xJywuLDAyNDg6Mzc5MDU2LTEzKy8xKS0vKi4wKCwuLzQ1LzM1JystJSkrJiosJCgqLjI0IiYoLTI0ODw9ICQmKS4wIicpJistJSksNDc5NTk7OT0/KC0uUlRWQUVGTlFSS09QUlVXRUlKQERFQkZHTVBSXF9gXWBiX2Jjen1+d3p7bG9wbG5vdnl6Y2Zndnl5a25vZGdoYmVmen19bnFyZmpqfH5/bnBybW9wcXR1cHN0cnV2ZGZof4KCf4GCj5GSiIqLhIaHhoiJg4SFm52dkJKSkZOTlZeXjo6PhIeHiouMgIODjI2OkpOUmZqbqKmqoKKi8gdJKwAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAADJSURBVChTVc/ZUsJAEIXhBgKdMc2ESRDBQADZ3BCCO8qigCCyKcr7PwozSkzxX34Xp+pABLRoUCwCgDoL0g9A0w2iuIqTjEGUEZqYEEIYKDMUWKXR23gyLgNJUWA3mhXPa9WrQoqC5PXN+/RjNv+pHe7g9m5xSim+vD/6h9VZMm4PHnx4bK/OTbI+fbCerr72ANNsnQkdh5/9DXTwe+h1upvL7N8oIr/o9fsvr8yR4CjAnO26rs0RU5DNC/mJ/0ZkFAA0VgwqnGwB8EIZhFZzcEwAAAAASUVORK5CYII=)icon or deleted by clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAUCAMAAAC+oj0CAAAAAXNSR0IArs4c6QAAAZVQTFRFHSQmGiQmGSMlGyQmHiQnHyUnHiUnHiQmGiMmGSMmHCQmHyUmICUnMSorKigpPSwuMikrOywtOissJSYoPSwtPCwtOyssOSssMSkqMSgqMikqNCosPywtPi0uNiosNyorMykrNCkrNCorOCorPiwtMykqMCgpNSorMyorNyssKScpSC4wTi8xRC4vWTIzUjAyUTAyVDEyWDIzWTM0RC0uTC8wVDIzRy4vVDEzWzM0TC8xXTM1Sy8xQC0uSzAxQy4vQS0uXjU2XzY3XzY2UTEyUzIzWTQ1UjEzTjAyRi4wSS8wUzEzXDM1VzIzXjM0dzw9eT0+bzo7bzo6ez4+cTs7YTY3ajk5Yzc4YzY4ZDc4bDo6dTs+azk6cDs7czs9dTw+bTo6cDo7bTo7ZTc5dDs8gT9AhUFChUBBmEZGlUZGlEVFg0BAh0FChEBBnUdIt09PvFBRtE5OtU5PqktMsU1NrExMtk5PtU5Os05Os01Oq0xMuU9QsE1No0pKuk9QoElJoEhJx1RUyFRUxVNT615e8F9f41tbaCbgkwAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAECSURBVChTY+Dh4WFgZEIGzCxAIR5WNl5tHWSgy8cAFGbn19M3QAaGRgIMDAy8xiaCQijA1EyYgcPcQkgEBYiKWQowMFkZigNFxYTEJSSlhIREgWxxa2kGJhuwsK2tnX9AoL2DDLKwmGxafkFLa1thURBQPVy1qFxwY0ioo1N6k7M8siEKYcXhGRGZkSUuKMKKUaUhZdHlMRWu6MKxlXElmMJVIdXx+ejCSgk1bonuSeFlZiiGKCU3Z2XnpNbWeSgju0TIM7c+Ly+vIUVFDCoM8bygqpqkpKSaOih0QN7h9PJGCyoRIR8NBi5NIxVQ+CCAkImvFgMPt7alPT+ysLmfIAMABhtHLEr+iOQAAAAASUVORK5CYII=)icon. Click on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAATCAMAAACqTK3AAAAAAXNSR0IArs4c6QAAAMxQTFRFHyQmHiMlNDg6LjI0LDAyNjo8Ky8xLTEzNTk7JCgqKC0vKi4wJiosKCwuJystODw9JistJCgrNzs9KS0vJSosKy8wKi8xKS4wJCkrLDEyISUnIygqMjY4MTU3Mjc5LzQ2ICUnPEBBU1ZXQURGQkZIQUVHQUVGQkVHVFdZZmlqe35+Z2prb3BxdHZ3fn+Bf4GCiImKl5iZi42NgYOEgIKCm5uctbW2pqenpqiop6eowMDAzMzMx8fHy8vLxsbGxsXGy8rKxsbF3dvbyMjIMaWjuAAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAACjSURBVChTXc/XEoJADAXQyMLCgiD2BoINey9gwfr//6TiOhu8jye5mQlIREYhigxAschU1RgISYZU0QUZWfOPWHvZeRvasnKj475rI8r3wtV4XdAFsX50Ok/MoiiyIIwvG4LOl4Iovm7LH+FFa3C43ReVRDjB9PGcV7/CqTbczepcOKlmgxm/v1IPoSJNhWhNkBwXxdEMAN1toXg2+ACZVMD3XxWnEXFBVIuFAAAAAElFTkSuQmCC)icon to open the Hole Section Editor for the currently loaded wellbore, where the user can rename it, edit and show/hide the well schematic.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FPmidblqCFlyTNogA3hxD%2Fimage.png?alt=media&amp;token=19ec137d-5c46-4c20-b8e0-95cbe3a3a3a2" alt=""><figcaption></figcaption></figure>

### 5.3 - Parameters

After the case has been set up, the user can enter the 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.**

Not all input parameters are necessary to fill in. To check which parameters are necessary, user can select an option on **Calc Type** dropdown in the ribbon menu and all inputs that affect the selected calculation type will be highlighted in green.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FG5B16hdNMw7DGISMcEg5%2Fimage.png?alt=media&amp;token=2afc23ef-07da-4e18-9534-5e014bdd9a41" alt=""><figcaption></figcaption></figure>

To know more about the parameters the user can scroll over the parameters names tool tip or go to [Innova Vantage Manual - Engineering Dashboard](https://docs.innova-drilling.com/introduction/innova-engineering-manual/innova-vantage-manual/6.0-well-views/6.12-engineering-dashboard) for details.

### 5.4 - Errors & Warnings

If an error or warning event occurs while the Engineering Dashboard is running calculations, a notification will be displayed in this grid.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8L7o226Sr33BL1MxPG5o%2Fimage.png?alt=media&amp;token=81d51606-04bb-4916-9861-4c4f3ee9dfb6" alt=""><figcaption></figcaption></figure>

The user can filter the results using the filter controls at the top of each column or by selecting the icons at the top of the grid. Hovering over an icon will display a tooltip indicating the name of the filter

### 5.5 - Save

After the user has finished the inputs, it will be necessary to select the save icon in the ribbon menu to store the changes and run the calculations.
\
If a change has been made and not save yet, a warning will be displayed underneath the menu to inform about unsaved changes.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FabzHHC1ynfhTh7odHBwO%2Fimage.png?alt=media&amp;token=dd00d58d-e853-4c12-8bdc-48fb6b8d2f98" alt=""><figcaption></figcaption></figure>

## 6.0 - Results

Results can be viewed in two formats, **Dashboard** or **Chart** view.

### 6.1 - Dashboard View

The Dashboard view displays the results as cards. In this view the user can:

* Resize cards
* Filter results
* Select/deselect cards
* Save the layout as a template
* Import and export templates
* Reset layout

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhbtLCbcE8HZbkSNRAdlB%2Fimage.png?alt=media&amp;token=f665e2e5-2456-46a1-a862-d984e4a06a7f" alt=""><figcaption></figcaption></figure>

### 6.2 - Charts View

The Charts view displays the charts in the full screen area available, and charts can be selected from the dropdown in the ribbon menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FXi1Y9F1gREynlG5oq3CD%2Fimage.png?alt=media&amp;token=11b45a4f-5ca2-45f7-a5af-19f09b631f18" alt=""><figcaption></figcaption></figure>

### 6.3 - Exporting Results

* The results charts can be exported by clicking on the **Print** button and selected to be included in a pdf report, or by right clicking in the chart area and choosing either ‘save image as’ or ‘copy image’ from the context menu.
* Clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAA4AAAAOCAMAAAAolt3jAAAAAXNSR0IArs4c6QAAAXpQTFRFGB0fGBseGB4fFxkdGBweGBodGB0eGBMaGBAaGBwfGBkeGBgdGB4gGB8gGCUjFzIoFzEnFTEmFy0lFiciFCcgEjwnGCokGDcpGDUoGDYoGC8mHFQ8GE40FFA0D1kwD1EtFV83D00qFl83DUcnEEUoE0wtGFw3F184F144F1EzGEMuGF04GF44GF03GF85GFAyC2MzCmQzCXw/BnM3FWs+Enc+D3s/EWY4EXY/CW01Dmo1EXU/E2E4F2A5GGE6Hn1SHntQH3FMFHVGEX1CFnJDD39CD3xAD39AGntGGXNAEXdAEXlAH4NVF5JUGo5UGIROFo1PFoFGFINKH4ZWDoBEFIRLFopOFYhMFYxOJnRRIoVYKJBZIIlZLJdmK5RlLJhoIJ5iKJdkOpRkOZZkI7ZxIqxsIqxqKbh1L6tyLrp5Lbh3Lr16N6BpIqZoIaNmIahpI6hqIqVoIqprN9KKNtCJN9eNUaN3UqB1V6V7ZqyGcK6MaKiFqdG82+vjzoZvUgAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAC3SURBVBhXY2BgYGAEYiYmBgZmIM3AwirtY+8QFRsXH8nGwsDCzuGYkpqWXlxSmsHEyMAnI+vk6+efkJmVncjDyMAfkBOdFGgQlJuXHwyUFQgpq6l0NgwtKCyKAXGNkmvLjeVMwsIjXJg4GQRdK6qqTeUV3MzczRk4GYQsPCw9rRSVvKy9bYBcXmERUWUVVTV1DVtNIJeTi1vLTltHR1dbTx/IZWDgFBOXAAFJKZAjgW6GAQgXCQAAlSMf4AHeR20AAAAASUVORK5CYII=) icon in the top right side of each chart will print the data grid of the chart in Excel format.
* Clicking on the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAVCAYAAABCIB6VAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAIaSURBVEhLtZPNaxNRFMVPMyMJWDKrSVI6kxSald3YgBqr0BbRBBWUNNPsRREhJVQtdGWpq0ILIhUU+hckaYv+ASX9SD90kQq1rqptx8JgsrKE0GxyXeVN3iRYP8YfzOKde+Zw5859bT41QPgPOKyCXbBgQz+Aqih89R+wreP29rPc+dRgv6pCFEWrzDgjinj44D7eLSxwestgl8uF4fgQ3s5n8H59DWu5JSS0OARB4HzRG9exmltC7O4djI2PczX41AD51AAREV24fIWmpmeoXC7Toa7T1PQMhS6FafTpGB3qOn3d36dkapSuRaK0ms/T92KRUo+fUIe/i+o59aetvm6GfoCLfVdx+9ZN7Ox8wvrmJojMTRQEAdpQDKmRJJTOTryZm8OLl7OoVCqNfTKagr8dHVk9HA6HA16vF4ZhWEscLWf8K2q12qmhsHZsBx3+LqAx2G5Y8GImba39FbHhBGAdxaPkCIqlEjMNDvRjsH8AzyYnzTcBPJ+YQG5lGbnlFaZ5ZBmvX82yUXBXKhTqxfGPY3YOdgchSW70hcONNkiSG8HuIKonVaa5JTfn+eOt+F24jguFbW4UTpcTqqJgY2ur0YZoJIK9L3uc7pFl4J7p4WZc2P6IatX8PI8sQ/bI2N39bL4BoKfnHErFEt+E04lQ7/nmdWt18xJaHAlNY3+6zmImjXQ2i3R2nmmqouDDRr51sB00BdvNT5l80UP3TKb3AAAAAElFTkSuQmCC) icon in the top right side of the chart will display the data grid for that chart.
* Hovering over the ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABMAAAATCAMAAABFjsb+AAAAAXNSR0IArs4c6QAAAcJQTFRFGB0fERccFRodGR4fFBkdDBIZBw0XBgwWChAYFxwfDxQaDRIZDhQaDBEZFhseExkdGB4fDRMaEhgcEBYcBg0XDBIaCg8YExgdFhweDhMaFxweFRoeEBUbExgcGR0fERYbAggVGh8gGh4gHyMjHCEhHSIhGyAhMTUrNDctNTgtNjkuNDgtLDApJSklMDMrKy8oJCglJismLjEqJiomMDMqPkExP0IyTk85VVU8UlI7WFo+V1g9U1Q7WFk/V1c+U1Q8WFg+Vlc9TE05W1s/Wls/Wlo/UFE6R0k2VVY8Vlk/T085Xl9BXV1BXl5BXV1AXFxAX2BBYmNDenpPZGNDf31QZ2dGcnFKYWBCZWVFZmZFYWBDdHRMf35RdHNMaGpHf4JUf4FTlpNciIdVi4hWhIJTh4VVmpdegYBSiohWgIFUnptgt7JsvLdvvrlvuLRtr6porqpoq6hmvrlwwr9zw71ywbtxwr1xxb9zxsR23NR92tN+19F80Mp43duD59+D4NqA5d2C5NyC6OSF7+yK5uOF6+aG7eaG5+OF9/OO/faP6OGE5+CE9++L+PKM8u6K9vGN9u6L9+6L9u+L+fWP7u+P6+uL0lcIbQAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAADzSURBVChTY2AgBzAyMcO0sbCysXMwMnBymatzQwV5lAMTs4I0ePm8m7I1+UEKBQS1Kporq1pagwUD2nK0hUBiwjrV7SEWlqHFHVZs1poiLJwMDJyiSZ1hNj6+1rbVNXyCusmBQEEWxdwSOz9fX1/7xC5TMb3SFHEJBhaVsjwHH6CYY2qdk6SUvoE0AwOfTFq3v4Ozi6tbfr2hLIM4E8gObveegvCIyKj03gxWmIM5eaL7+idMnDS5UFUc7nc+Ho/4mJiEMDVGOUR4sMVOaWicWi4vhRRELEae6ZlxZkDHIgAzq1JRrZcCWkDyGZtgBq0ssmEAf6YyKP2WrTcAAAAASUVORK5CYII=)icon will display a tool tip for the chart controls.
* Clicking on Diagnostic prints a Hydraulics Diagnostic Report on txt. format.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3n7gDtU5CMDno7AFIpWU%2Fimage.png?alt=media&amp;token=ed7ae5af-eef5-477b-bd3c-28925c5c22db" alt=""><figcaption></figcaption></figure>

### 6.4 - Chart Preferences

Chart preferences can be configured in the ribbon menu by toggling the checkboxes.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fg9K7xNnqxKQNf91RntIS%2Fimage.png?alt=media&amp;token=0f5b3c62-7a92-4325-a739-5b09aa2d5bda" alt="" width="443"><figcaption></figcaption></figure>

* **Data Grids:** Will toggle from the chart view to data grids view.
* **Casing:** Adds lines to the chart to represent the casing shoe depths entered in the Hole Section table.
* **Legend:** Toggles the legend to the right of each chart on/off.
* **Labels:** Adds labels to the results.
* **Shade Buckling:** This will shade the area to the left of the buckling lines on these charts. Available on Drillers Hookloads, On Bottom Tension Snapshot, Off Bottom Tension Snapshot and Kick Tolerance.

### 6.5 - Real Time Data Options

In these options the user can control what real time data is displayed in the charts.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdYU6EjhfGBN7P0g9xi7E%2Fimage.png?alt=media&amp;token=83a9c2ab-3148-42bf-9bbf-2a881b2c33b1" alt=""><figcaption></figcaption></figure>

* **Refresh:** 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 button to update the charts.
* **Select BHAs:** Only relevant if Slide Sheet or WITS Data are toggled on. Allows the user to choose which BHA(s) have their real time data displayed on the chart. The user can toggle on multiple BHAs at the same time.
* **Slide Sheet:** 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 button.
  * **Display as Points/Line** ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEIAAAATCAMAAAATWCuIAAAAAXNSR0IArs4c6QAAAlVQTFRFAAAADhMVChASBg0PDRMVDBETDhQWGB0fFRocERcZCxATEBUXDxQWERYYCA4QFBkbGR0fFxweDhMWBQoMFhsdExkbCQ4QDxQXBgsNDxUXCg8RFRodCQ8RExgaFhocFRsdFBocEhcZEBYYCQ4RAgcJExgbCxASFRobBgwOFhscDRIVCxETDRIUBw0PAQYIAggKCA0PDBIUEBUYCA0QGR4gGh8hGx8hHiIkGiAiHCEiHiMmHiMkHCEjHCAiHSIkHyQmNTg7Njk7IicpLjM1KzAxJistICUnMDU2ICUmJSosLTIzIScpIiYoISYoMTY3ICQmNTk7Njo8LDEzLzM1LzQ2Ki4wJCgqIygqIycpPkNEP0NFPEBBPkJEPkJDREZIW15fTU9QUFNUREhJT1JTT1NUS09QS09RVllbTVFSR0tNQENFUFRWQUVHTlJTUFRVQ0dJSU1PUlZYTVFTUFNVT1NVVVhaV1tcRUlKSUxNXWBhXWBiZ2lqc3V2dnh5dXd4dHZ3e31+c3Z2dnh4bnFyb3FzYmVmdnl6Z2pscnV3cXR1am1ubG9wZmprZWlqYmVnc3Z4a25vam5vfYCBf4KDfYCCjI6Pk5aXio2Oi46Pg4aHkZOUiIqMhIeImpydvb6/u729uLm6u7y9s7S1ubu7qKmqtba3t7i5ra+wvr/Av8DBy8vMzMzN1NXWxcbHw8TF1dXWy8zM2NnZwMHCxsfIzs/P09XVz9DR0tPV3N3d3N3e3t/f09TV3d7e5OTl5ubm8/P0+Pf46+vs6enp5ebm5OTk4uLj////cGZo+gAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAHcSURBVDhPYzCPq66prcMJ6humNuKWrWtqanZgcIy30GbEDZicKpnxSLOwOrcwJESyseMBHC6tnPjk2bnaGBKTuCkygrGWIRluhAkTjwmGaUiuMOHlw2IZihH87Sk8EDU8jAIwxUhG8EZ1sAtiGIJshKDQqmnC7CKi7IIcqWkcWIwQ69wrKAIR5+eBm4VihPi86RKC5k6CHCIrV0vClCC5QqprDdAIaaAMt2u6JdQwdgwjZLrXusmaZmTKYXEFyAhBXnZ5QUmr+QusFaAqMIzgie6xUeRmUYJ7GdUV7MruC3uFPVas81SEqUAzYoaKIDejqmuWCTwo2FGMWM/qtWHjvr5Fm7wRaQnNiJk+i/vVfDfvn6UI8ymqEVv8ti5Rn3RgqT9SakQzYnLAwdkaToeOLdPEFiNSXdsCp5hp8VYF8cDjnB0tOFfMYbDVUVPOnhwsoYMtRiZs19UTY1HTN9Ax1JaFpUJUV6xYnpOam52XH1NQWGQH9QpKWBwuLsrLyyspzssrDVHFFiNGc/fu2AkCO3bu2h0KDXIkI1jLjuyBKNi58+hEYyxGsLPbuIWFQ0EEzJ3IOdXUHiYd7mQH8ynQI4nl8JzKwY8AWJIWuyCSPDzKgEZUxPJSlNm56wCMfcKhaxangQAAAABJRU5ErkJggg==): Slide Sheet data can be displayed as points or lines by choosing between these options.
* **WITS Data:** Toggle on display WITS data on the chart. Requires WITS data for the well to be stored in the Data Acquisition system. If the stored WITS data is updated, the charts must be refreshed by clicking on the Refresh button.
  * **Display as Points/Line** ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEIAAAATCAMAAAATWCuIAAAAAXNSR0IArs4c6QAAAlVQTFRFAAAADhMVChASBg0PDRMVDBETDhQWGB0fFRocERcZCxATEBUXDxQWERYYCA4QFBkbGR0fFxweDhMWBQoMFhsdExkbCQ4QDxQXBgsNDxUXCg8RFRodCQ8RExgaFhocFRsdFBocEhcZEBYYCQ4RAgcJExgbCxASFRobBgwOFhscDRIVCxETDRIUBw0PAQYIAggKCA0PDBIUEBUYCA0QGR4gGh8hGx8hHiIkGiAiHCEiHiMmHiMkHCEjHCAiHSIkHyQmNTg7Njk7IicpLjM1KzAxJistICUnMDU2ICUmJSosLTIzIScpIiYoISYoMTY3ICQmNTk7Njo8LDEzLzM1LzQ2Ki4wJCgqIygqIycpPkNEP0NFPEBBPkJEPkJDREZIW15fTU9QUFNUREhJT1JTT1NUS09QS09RVllbTVFSR0tNQENFUFRWQUVHTlJTUFRVQ0dJSU1PUlZYTVFTUFNVT1NVVVhaV1tcRUlKSUxNXWBhXWBiZ2lqc3V2dnh5dXd4dHZ3e31+c3Z2dnh4bnFyb3FzYmVmdnl6Z2pscnV3cXR1am1ubG9wZmprZWlqYmVnc3Z4a25vam5vfYCBf4KDfYCCjI6Pk5aXio2Oi46Pg4aHkZOUiIqMhIeImpydvb6/u729uLm6u7y9s7S1ubu7qKmqtba3t7i5ra+wvr/Av8DBy8vMzMzN1NXWxcbHw8TF1dXWy8zM2NnZwMHCxsfIzs/P09XVz9DR0tPV3N3d3N3e3t/f09TV3d7e5OTl5ubm8/P0+Pf46+vs6enp5ebm5OTk4uLj////cGZo+gAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAHcSURBVDhPYzCPq66prcMJ6humNuKWrWtqanZgcIy30GbEDZicKpnxSLOwOrcwJESyseMBHC6tnPjk2bnaGBKTuCkygrGWIRluhAkTjwmGaUiuMOHlw2IZihH87Sk8EDU8jAIwxUhG8EZ1sAtiGIJshKDQqmnC7CKi7IIcqWkcWIwQ69wrKAIR5+eBm4VihPi86RKC5k6CHCIrV0vClCC5QqprDdAIaaAMt2u6JdQwdgwjZLrXusmaZmTKYXEFyAhBXnZ5QUmr+QusFaAqMIzgie6xUeRmUYJ7GdUV7MruC3uFPVas81SEqUAzYoaKIDejqmuWCTwo2FGMWM/qtWHjvr5Fm7wRaQnNiJk+i/vVfDfvn6UI8ymqEVv8ti5Rn3RgqT9SakQzYnLAwdkaToeOLdPEFiNSXdsCp5hp8VYF8cDjnB0tOFfMYbDVUVPOnhwsoYMtRiZs19UTY1HTN9Ax1JaFpUJUV6xYnpOam52XH1NQWGQH9QpKWBwuLsrLyyspzssrDVHFFiNGc/fu2AkCO3bu2h0KDXIkI1jLjuyBKNi58+hEYyxGsLPbuIWFQ0EEzJ3IOdXUHiYd7mQH8ynQI4nl8JzKwY8AWJIWuyCSPDzKgEZUxPJSlNm56wCMfcKhaxangQAAAABJRU5ErkJggg==): WITS data can be displayed as points or lines by choosing between these options.
* **Depth Limits:** 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.
* **Depth Interval:** Determines the interval between real time data points displayed. For example, a value of 500 displays a data point every 500 meters or feet measured depth. This can help soften the appearance of noisy data.


# Innova Vantage - MFA Guide

A guide to setting up multi-factor authentication for your organization's users in the Web Portal interface.

## 1.0 - Introduction <a href="#toc135722907" id="toc135722907"></a>

Multi-factor authentication (MFA) is a commonly used method of online security. It requires a user to firstly input their username and password and secondly input a code generated by a third party app on a device the user has previously designated. This means in order to access a user’s account they must have a username, password and their authentication device available, which increases the security of the account.

MFA can now be enabled for use when logging onto the Innova Web Portal and the Innova Phone App. Additionally, if your Well Seeker Pro server database is hosted within Innova’s infrastructure, MFA can be enabled for use when logging onto a Well Seeker Pro server database.

This document will guide the user through the various use cases, which differ slightly based upon the organization’s user management system (Innova, Okta or Azure AD).

## 2.0 - Setup <a href="#toc135723036" id="toc135723036"></a>

MFA is turned off by default. It is up to an organization’s admins to turn on MFA for their existing users, if they desire to use this security feature. This is done via the User Management page in the Innova Portal.

To access the User Management page, log in to the Innova Web Portal, using credentials that have the **Admin** permission enabled. Open the main menu and select **User Management** and then **Users**.

MFA settings are managed on a user by user basis. Before changing any settings, check the **Auth Type** column.

If the Auth Type column displays a <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FV7xMMLCMrukdqwHXR5jY%2Fimage.png?alt=media&amp;token=8b200bc8-0761-4f71-ac21-c33db74acb81" alt="" data-size="line"> icon or a <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpWBSBtb3sAXlntH6ai9O%2Fimage.png?alt=media&amp;token=7fba79e2-f677-4144-a06c-b4c720266387" alt="" data-size="line"> icon, then your organization’s user credentials are managed using Azure AD or Okta, respectively. In this case, the password and MFA management functions in the Innova Portal will have no effect.

If the Auth Type column displays a <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsGsktOx6mSHziwkms2AZ%2Fimage.png?alt=media&amp;token=4688755a-581a-45be-87e1-8a1cd441f744" alt="" data-size="line"> icon, then user credentials are managed in the Innova Portal and the admin will be able to use the below functions to control the user’s MFA status:

* **MFA Enabled:** Click the button in the MFA Enabled column to toggle MFA on for that user. The user can then follow the steps in Section 3 below to set up MFA on their secondary device. The button will display green when MFA is enabled for the user.
* **Reset MFA Device:** Click on the <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3L30y0IcE8KvG8tCRn6T%2Fimage.png?alt=media&amp;token=58063e2d-8705-4286-a563-3b1ac1c44e90" alt="" data-size="line"> icon to the left of the User Name column and then select Reset MFA device from the menu that appears. Once selected a second dialog will open requiring user confirmation of this action. Select **YES** to continue, or **NO** to cancel the process. Once reset, the user will need to setup a new authenticator the next time they login to the Portal, app or Well Seeker.
* **API User:** Toggling the API User function on prevents a user from using MFA, and ensures that they can log in using their username and password only. It also prevents the MFA Enabled option from being toggled on. If MFA was previously enabled for the user, it will automatically be deactivated. The button will display green when API user is enabled.

## 3.0 - User Login Process <a href="#toc135723039" id="toc135723039"></a>

### 3.1 – MFA not enabled <a href="#toc135723040" id="toc135723040"></a>

If MFA has not been enabled then the user will login as usual.

### 3.2 – MFA enabled <a href="#toc135723041" id="toc135723041"></a>

If MFA has been enabled, one of two scenarios will occur:

1\. **This is the first time a user is logging in after MFA has been enabled, or the MFA authenticator has been reset:**

a. The user must register an MFA device. This must be done via the login page for the Innova Web Portal. It cannot be done in the App or Well Seeker.

b. The user inputs their username and password

c. The below screen will appear (for Okta and Azure AD organization users, a similar app specific version will appear)

d. Open an authenticator application on a chosen device, and scan the QR code (see the relevant authenticator app’s documentation for details on how to do this). A row named **Innova Drilling & Intervention** will be added in to the authenticator app in question, which will generate a six digit code at a pre-determined time interval. Input this six digit code into the six cells displayed below and select **SUBMIT MFA**

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2UFlAOUN7G8ol91dAEKs%2F5.jpeg?alt=media)

e. If correct the user will be logged in

If a user attempts to login to the Innova Phone App or Well Seeker Pro before registering an MFA device, they will receive a warning message.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYuFuawsPw3mfMpxOK0he%2F6.png?alt=media)

2\. **An MFA device has already been registered:**

a. The user inputs their username and password

b. The below screen will appear (for Okta and Azure AD organization users, a similar app specific version will appear)

c. Open the authenticator application on the registered device. Input the six digit code from the row **Innova Drilling & Intervention** into the six cells displayed below and select **SUBMIT MFA**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWXVYgYnwbleVygCWYaND%2F7.png?alt=media)

d. If correct the user will be logged in

The above process will also occur in a comparable order when logging into the Innova Phone App. Where an organizations Well Seeker Pro server database is hosted within Innova’s infrastructure, this will also occur when logging onto the server database in Well Seeker Pro.


# 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’**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGOpnvix92UxZhbM7X9bQ%2F0.png?alt=media)

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

<div><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNPwRhBKdZENa3Sxgbp9A%2F1.png?alt=media" alt="" width="308"> <img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0BMFCiDeRn75XBnHkxaq%2F2.png?alt=media" alt="" width="281"></div>

### 1.2 - Manually Translate a Page

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

* Click on the Translate icon ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeQCkDCCBh53Ix4YI4953%2F3.png?alt=media) in the address bar, next to the star/bookmark icon.
* In the pop-up menu, choose the target language.
* Click **‘Translate’**.

Or

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGpgwlkfm1mZG6cUC1qXT%2F4.png?alt=media)

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7Qpm03eZRWFZKSAviWGV%2F5.png?alt=media" alt="" width="220">

### 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 **“**&#x4F;ffer to translate pages that aren’t in a language I read.”

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9vZDUNc7AkzwOx1OgENp%2F6.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHvBerPVd43S4MhDL9nhK%2F7.png?alt=media)

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkkZN5oS8yYYVeNnfWbJL%2F8.png?alt=media" alt="" width="236">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYAZH5ll7ydC6KaDvzeFm%2F9.png?alt=media)

* Second Option
  * Click in the Translate icon ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FlsaDiWDhAJhgAZ1EremB%2F10.png?alt=media) in the address bar (if visible).
  * Click in the auto selected language.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1xRfo6COl4vpMvfVIJW0%2F11.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9ZzFlrOfqnF2JZ1rKDJk%2F12.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5YPt7lgMR7ylH9ZXvT57%2F13.png?alt=media)

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F84BxhFs7a6Lgdlhj0H6Q%2F14.png?alt=media)

### 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 [Innova website](https://innova-drilling.com/) and [Innova Portal](https://www.icpwebportal.com/).

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkVpjIYCSpLDfbZWemGNx%2F15.png?alt=media)

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOJVZ14rv51T8lN3Y8kXN%2F16.png?alt=media)

## 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 Vantage - Alert System

## 1.0 - Introduction

The Innova Vantage Alert System provides customizable notifications to help monitor wells, drilling activity, anti-collision monitoring, and data exchange. Alerts notify users of key operational events, ensuring timely awareness and supporting better decision-making.

Users can configure alerts through the User Management section and Account Settings in Vantage. Each user can select the type of alerts to receive and choose the notification method.

**Important:** Alerts are only sent for wells that are both **active** and marked as **favourite**. Wells that are either inactive or not marked as favourite will not generate alerts.

This guide explains how to configure alerts in Vantage and details available alert types, notification methods, and severity levels.

## 2.0 - Prerequisites

Before setting up the alerts, users should verify that the well is marked as a favourite and is active. To do this:

1. Navigate to the [Wells Dashboard](https://vantage.innova-drilling.com/well-list) in Vantage.
2. Locate the well you want to receive alerts for.
3. Check if a **star icon** appears next to the well name and if the Status is Active.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAkKMaYxFor5JNAB22yIo%2Fimage.png?alt=media&amp;token=8ce5b6d3-759a-43c8-858f-8c0c8877bf88" alt=""><figcaption></figcaption></figure>

4. If the well is Active but there is no star next to the well name, you can mark it as a favourite by:
   1. Clicking the Account Settigns at the top right of the page and selecting *Favorites*

      <figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FO6biQkjZ74OboEVtdBDC%2Fimage.png?alt=media&amp;token=48dbb5e9-1218-4969-913a-787d4c632398" alt=""><figcaption></figcaption></figure>
   2. Select either Rigs or Operators by clicking the field, choosing the desired option from the list and clicking on ‘**Submit’**. The favourite list will be updated and the page will be refreshed to reflect the selected options.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyknyCShB0mRx1dxZXzpn%2Fimage.png?alt=media&amp;token=d20d3493-2481-487c-81d5-a154820dd798" alt=""><figcaption></figcaption></figure>

**Note:** It is **NOT** possible to follow an individual well directly. Favourites can only be assigned at the Rig or Operator level.

Users can also check if the desired well has been marked as favourite by:

1. Clicking the Account Settings at the top right of the page and selecting Alerts.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtfAkKzStpEnjABUk6FQA%2Fimage.png?alt=media&amp;token=f34d3e49-cac0-420c-ac67-96c541d8a720" alt="" width="222"><figcaption></figcaption></figure>

2. Clicking the ‘Favorite Wells’ button in the ribbon menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJupzkzcuM5ncGJEAmmnl%2Fimage.png?alt=media&amp;token=475dbdc4-25e4-40d4-9a66-d7dbb7dbc2f1" alt=""><figcaption></figcaption></figure>

3. Checking if the desired well is listed in the dialog that opens.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5UJJ8cmHpOKCRsKyJK1b%2Fimage.png?alt=media&amp;token=33f28a36-b8d2-4084-aedd-9d9b59a546b5" alt=""><figcaption></figcaption></figure>

## 3. 0 - Setup

Configuring and maintaining alerts requires an Admin user with access to User Management.

Alerts can be assigned in three ways:

* **Users** – Assign alerts to a specific user. Only this user will receive the alerts.
* **Roles** – Assign alerts to a role. All users associated with the role will automatically receive the alerts.
* **Groups** - Assign alerts to a group of users that may or may not be Vantage users. All users associated in this group will automatically receive the alerts.

### 3.1 - Configuring alerts for a user

#### 3.1.1 - Users Page

1. Open the **main menu**.
2. Navigate to **User Management → Users**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJWgM9uc6y6xvXY4gaqnM%2Fimage.png?alt=media&amp;token=c685e0a2-e707-48f0-83ca-b1d52cfc4bc7" alt=""><figcaption></figcaption></figure>

3. Locate and select the user and click the **Alerts** icon at the ribbon menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQSVVHglWtLaghrgxco4x%2Fimage.png?alt=media&amp;token=47ea15f8-a2af-4416-8ae4-41fc00bfb4de" alt=""><figcaption></figcaption></figure>

4. Once in the Alerts section, alerts can be activated and customized according to operational requirements.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUMdKxSPTypdrGE9SVWR1%2Fimage.png?alt=media&amp;token=84ee6da0-7e61-4756-80d0-14adc8e99a5a" alt=""><figcaption></figcaption></figure>

5. Users can copy alerts from another user profile by clicking the **‘Copy from Users’** button located in the ribbon menu. This will open a dialog where the user can select another user from a dropdown list, choose whether to **Append** or **Overwrite** the alerts, and then click **‘Copy Selected’** to save the new alert settings.
   1. **Append:** Copies all alerts from the selected user and adds them to the existing alerts for the current user.
   2. **Overwrite**: Replaces all existing alerts for the current user with the alerts from the selected user.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCSjP8PFyR4Jg1LBhkdFc%2Fimage.png?alt=media&amp;token=e5bd8c03-5505-44e6-917d-a01f7b4935fb" alt=""><figcaption></figcaption></figure>

#### 3.1.2 - Account Settings

1. Open Account settings and select ‘Alerts’

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqpMOQzGCGPMhWEJA6oZm%2Fimage.png?alt=media&amp;token=1f3d1bcc-1cca-4871-b378-05370f589f31" alt=""><figcaption></figcaption></figure>

2. Once in the Alerts section, alerts can be activated and customized according to operational requirements.

**Note:** If the Alerts dialog is opened via the **Account Settings** menu, the **‘Copy From Users’** option will not be available. To copy alert settings from another user, this must be done through **User Management.**

### 3.2 - Configuring alerts for a role

1. Open the **main menu.**
2. Navigate to **User Management → Roles**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0tqdItqJA1CFIBmnROQL%2Fimage.png?alt=media&amp;token=882c26aa-1f53-4f20-9455-83501788cfce" alt=""><figcaption></figcaption></figure>

3. Locate and select the role and click in the **Alerts** icon at the ribbon menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FJpd4fsAe4sSn1RrbX062%2Fimage.png?alt=media&amp;token=6a62cfab-90dd-4fdd-8f70-75b0e4cd3acc" alt=""><figcaption></figcaption></figure>

4. Once in the Alerts section, alerts can be activated and customized according to operational requirements.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQyeJ4UjTTCDKwdxdif7S%2Fimage.png?alt=media&amp;token=1948b766-05ee-4c7e-aaef-89e3f3dae2ea" alt=""><figcaption></figcaption></figure>

5. Roles Alerts can be copied from another role by clicking the **‘Copy from Roles’** button located in the ribbon menu. This will open a dialog where the user can select another role from a dropdown list, choose whether to **Append** or **Overwrite** the alerts, and then click **‘Copy Selected’** to save the new alert settings.
   1. **Append:** Copies all alerts from the selected role and adds them to the existing alerts for the current role.
   2. **Overwrite:** Replaces all existing alerts for the current role with the alerts from the selected role.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fa685fHb65Djhc6wiboSj%2Fimage.png?alt=media&amp;token=84cdc2ac-0ce4-4859-a971-244c872fc7e5" alt=""><figcaption></figcaption></figure>

### 3.3 - Configuring alerts for a group

1. Open the main menu.
2. Navigate to **Groups → Alert Groups**.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkBTbMKP73Q7O7Q529DFv%2Fimage.png?alt=media&amp;token=3e827944-099c-4f67-bfe8-a81a61ae0f20" alt=""><figcaption></figcaption></figure>

3. To create a new group, click on ‘Add Group’ to open the Add Alert group dialog

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FI1k7ONatezQh67aJJZAV%2Fimage.png?alt=media&amp;token=3a03ca76-6e47-44bb-bab9-068f12aa1a1b" alt=""><figcaption></figcaption></figure>

4. Fill in the **Group Name**, **Units**, **Email**, **Rigs** and **Operators** fields and click on 'Add'

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTmHDgBySf8CwpLXPM7V2%2Fimage.png?alt=media&amp;token=d5f5fff0-a009-4214-8e9e-9691906981f1" alt=""><figcaption></figcaption></figure>

5. Locate and select the desired group and click in the **Alerts** icon at the ribbon menu

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqMULGPQM1zwa3gVOTYxq%2Fimage.png?alt=media&amp;token=f2810197-aa29-4cbc-acef-151d56af33f3" alt=""><figcaption></figcaption></figure>

6. Once in the Alerts section, alerts can be activated and customized according to operational requirements.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2DuEfiSlZRfmD2bDFaC1%2Fimage.png?alt=media&amp;token=b383bfa9-9e72-487f-a458-b65c29ce8506" alt=""><figcaption></figcaption></figure>

7. Group Alerts can be copied from another role by clicking the **‘Copy from Groups’** button located in the ribbon menu. This will open a dialog where the user can select another role from a dropdown list, choose whether to **Append** or **Overwrite** the alerts, and then click **‘Copy Selected’** to save the new alert settings.
   1. **Append:** Copies all alerts from the selected group and adds them to the existing alerts for the current group.
   2. **Overwrite:** Replaces all existing alerts for the current group with the alerts from the selected group.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcJpd28egOxZLWTC2t7pM%2Fimage.png?alt=media&amp;token=64981f42-7885-4fc0-b670-c4c4ce11e537" alt=""><figcaption></figcaption></figure>

### 3.4 - Alert Types

Innova Vantage supports seven alert types:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFFnBBulNLhijKgJ1mEOv%2Fimage.png?alt=media&amp;token=400538e5-3d90-45b8-bdd7-e9305b2f37e1" alt=""><figcaption></figcaption></figure>

* **Data Acquisition**: Notifications related to collecting and storing WITS data
* **Anti-Collision**: Alerts triggered by potential collisions.
* **Well Notifications**: Updates on well activity.
* **Drilling Parameters**: Alerts for key drilling metrics and thresholds.
* **Data Bridge:** Alerts for importing third party data activities.
* **Organization Notifications:** Alerts triggered by changes in Organization. This alert type is not tied to a specific well and does not need to have a favourite well linked to it.
* **BHA Notifications:** Alerts triggered by changes in BHA.

The Alerts dialog is separated into 2 grids. The alert types in the top grid and the alert details in the bottom grid. Selecting an alert will allow the user to add, edit or delete it.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGBfYTFAowXYlRQh1pnMW%2Fimage.png?alt=media&amp;token=10d72e95-9579-4cef-b52c-2990922cf8e3" alt=""><figcaption></figcaption></figure>

### 3.5 - Adding a New Alert

1. To add a new alert, click in the alert type you require and click on ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2H81rOpMTk2RkY6vBChF%2Fimage.png?alt=media\&token=0f112be1-1e6d-42ee-882e-851905d43852) icon in the ribbon menu.
2. Check the desired notification method in the Alert Settings section
   1. Dashboard Notification – Sends alerts directly to the Dashboard page.
   2. Email Notification – Sends alerts to the registered email address.
   3. SMS Notification – Sends alerts as SMS message to the registered phone number.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfVt8S8kqYwLnoWQA8n7S%2Fimage.png?alt=media&amp;token=86037ce1-a35f-4066-a336-0ba3c512fc1f" alt=""><figcaption></figcaption></figure>

3. Select the desired alert from the Alert Type dropdown menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAh36YQ7P4nIxaOMHWHXW%2Fimage.png?alt=media&amp;token=179549a4-1e3a-4dc4-ad8d-44bf0cdd783c" alt=""><figcaption></figcaption></figure>

4. Select the Severity from the dropdown menu options. This will set what notification type the user will receive and help prioritize responses.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5gdb3fh3jti5a1BtB5oi%2Fimage.png?alt=media&amp;token=a277ea23-8dc1-4fb9-b264-eec36569e6ac" alt=""><figcaption></figcaption></figure>

If ‘Email’ is the notification method selected, user will receive the following notifications:

i. **Info:** Informational alerts, no immediate action required

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5ninTQNgXVA5qD96acSZ%2Fimage.png?alt=media&amp;token=efc1981d-67c9-47ac-bf67-7620ca5125cc" alt=""><figcaption></figcaption></figure>

ii. **Warning:** Requires attention but not urgent

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FfcIWWOgnKhE0PRT9YXT3%2Fimage.png?alt=media&amp;token=8a54a1a1-450d-4a6b-b96e-245a5b155ecb" alt=""><figcaption></figcaption></figure>

iii. **Critical:** Requires immediate action

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsCTeO11O6fuRqKdrvHiJ%2Fimage.png?alt=media&amp;token=a4168ed9-7c04-47ff-aecf-0e823b3a2ec9" alt=""><figcaption></figcaption></figure>

**Note:** Some alerts may only have **‘Info’** available in the **Severity** dropdown menu.

5. Silence Alert Checkbox: Marking this checkbox will turn off the notifications for the alert. This can be used to temporarily disable notifications.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcKHnJ2on84NcSzWm96jj%2Fimage.png?alt=media&amp;token=47492aac-a4c0-46f0-a943-15a27e04fde0" alt="" width="527"><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FHZVz7NwGaNnJ6Xk1jb48%2Fimage.png?alt=media&amp;token=df3823d7-e93a-469d-8d18-91c70ed770ac" alt=""><figcaption></figcaption></figure>

6. User may have more configurations to set in the alert, like Phase, Rig, Min and Max values, Use Min Depth, Use Max Depth, Include Projections and Send Once. Set these options as desired and click **‘Add’** to save the alert.

### 3.6 - Special Considerations for Anti-Collision Alerts

Anti-collision alerts rely on the configuration in the [**Anti-Collision Dashboard**.](https://vantage.innova-drilling.com/anti-collision-dashboard) Ensure that dashboard settings are properly defined to generate relevant alerts.


# Innova Vantage - Data Insights Upgrade

## Introduction

The purpose of this document is to introduce the upgraded Data Insights page, previously known as Analytics.

The Data Insights page has been redesigned to provide a more logical layout, improved usability, and enhanced data visualization, making it easier to access and interpret key performance metrics.

Key upgraded features include save/load filter settings, save/load KPI layouts and the ability to visualize multiple KPIs alongside each other.

The interface is split across two tabs, **Select Wells** and **View KPIs**. The View KPIs tab replaces the long list of KPIs that used to appear down the left edge of Vantage.

Further details in this document will outline the improvements, highlight functional changes, and explain how to get the most from the new interface. The underlying workflow is the same:

1. Apply filters to reduce the well list to the desired wells
2. Select wells
3. View KPIs

## Workflow

### 1. Apply filters

The Selected Wells tab is where the user applies filters to display the desired group of wells for selection.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/EikRiQi14iuFZia2ZJPB/Unknown%20image" alt=""><figcaption></figcaption></figure>

* Filter options available in the ribbon at the top of the page and in the well grid column headers.
* Save existing filters templates and easily return to previous configurations. The import ability allows the old Analytics filter templates to be imported and utilized.

### 2. Select wells

* Select the checkboxes of the desired wells to be included in the KPIs.

### 3. View KPIs

The View KPIs tab is where the user can visualize and export the key performance indicators for their selected wells. The main benefit is that now users can view multiple KPIs at once.&#x20;

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/afNvdh8f6B0CMan9oGu1/Unknown%20image" alt=""><figcaption></figcaption></figure>

* The user can select up to eight (8) KPIs from the dropdown menu.
* To streamline future sessions, the user can mark KPIs as favourites by clicking the star icon located next to each KPI name in the dropdown and in the next use, these favourites will be in the top of the list.
* Certain KPIs include additional filter options, for example, the Motor KPI includes a Phase Filter that will automatically appear in the top menu when selected.
* The top menu also contains export controls, allowing the user to quickly download or share KPI data as needed.
* To improve efficiency and consistency across teams, the user can save, import and export KPI templates directly in the KPI Templates section.

Once KPIs are selected, their charts appear directly below the top menu. Each chart can be resized or repositioned by clicking and dragging its corners, similar to adjusting a browser window. This flexibility allows the user to arrange their workspace as desired.

* Right-clicking on any chart opens a context menu where the user can save or copy the chart image for reporting or presentations.
* For grid-style KPIs, such as the Motor KPI, a pencil icon menu is available as usual. From this menu, the user can export the data to Excel for further review, sharing, or reporting.

The enhanced View KPIs tab delivers a more dynamic and user-friendly experience, giving the user full control over how data is viewed and organized, all within one interface.


# BHA Trend Analyzer Guide

## 1.0 Introduction

The **BHA Trend Analyzer**, available in Vantage, is designed to support drilling engineers in planning and monitoring wellbore trajectories during the landing phase.

The tool integrates survey data, dogleg severity (DLS), formation tops, and motor yields into a single interactive workspace. This enables engineers to:

* Compare performance and trajectories against nearby offset wells.
* Evaluate whether the planned landing is achievable with available motor yields.
* Refine projections and tolerances both before and during drilling.
* Export structured datasets for further analysis and reporting.

The BHA Trend Analyzer provides insight into how achievable a landing is, and how the BHA is performing compared to expectations.

## 2.0 Required Inputs

To use the BHA Trend Analyzer, the following inputs are required:

* Your organization must have a server database in order to access Vantage and store the data.
* The well you wish to analyze must have survey data recorded.
* The well must have BHAs created for it. The user does not need to enter data into these BHAs, but a BHA is required to record slide sheet data.
* The well must have slide sheet data recorded. Note that only the date, start/end time, start/end depth and state fields are required. Fields like the toolface, motor yield or slide grade are not required.
* The well requires a principal plan to be assigned to it.

## 3.0 Motor Yields

The **Motor Yields** tab displays an MD/TVD vs. Dogleg Severity (DLS) chart. This helps engineers assess the achievability of the landing by comparing the principal plan with drilling performance data from their well and offset wells.

The results chart can be exported as an image by right-clicking and selecting **save image as** or **copy**.

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

The chart displays the following information:

<mark style="color:purple;">**Purple line**</mark> – Shows the dogleg vs TVD of the principal plan.

<mark style="color:blue;">**Blue dashed line**</mark>– Shows the TVD of the last recorded survey. This line will be annotated with the MD, inclination and azimuth of the survey.

<mark style="color:$danger;">**Pink dashed line**</mark> – Shows the TVD of the bit projection, taken from the last recorded slide sheet entry. Not that if the last survey is deeper than the last slide sheet entry, this will not display. The inclination and azimuth are calculated using the In Use value in the Motor Yields section.

<mark style="color:green;">**Green dashed line**</mark>– Shows the TVD of the landing point. This is taken from the Landing section in the menu ribbon above the chart. Note that this will not display if the last survey is deeper than the landing point.

<mark style="color:red;">**Red Line**</mark> – This is drawn between the bit projection and the landing point, and shows the average dogleg that the driller must achieve to hit the desired inclination and azimuth by the time they reach the landing TVD.

<mark style="color:red;background-color:red;">**Red Box**</mark> –Displays the tolerance window for the required landing dogleg. The tolerance window is defined in the Landing Tolerance section of the menu ribbon.

In addition to the lines defined above, the chart also displays the following data points for the currently selected well, as well as any selected offsets. All data points for a well can be toggled off by clicking on the well’s name in the Legend in the top right of the chart. Hovering over a data point will display additional information:

**Circles** – Dogleg Severity (DLS)

**Squares** – Build Rates (BR)

**Triangles** – Turn Rates (TR)

**Diamonds** – Motor Yields

### 3.1 Motor Yields Menu

The ribbon menu at the top of the page provides options to modify the results chart.

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

The ribbon menu contains the following functions.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/GyAlBJQjFFfdOpgVI3aN/Unknown%20image)**Refresh** – If the input data for the chart has been updated, click on this function to refresh the chart

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/nOJlHVNxA70m7e0NOfqM/Unknown%20image)**Export** – Exports the motor yield results data to Excel.

#### 3.1.1 Data

Users can toggle which parameters to display on the chart for the reference well and offsets:

* Motor Yields
* Dogleg Severity (DLS)
* Turn Rates (TR)
* Build Rates (BR)

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/wmuLxjbiD4ZWwvq3rlCN/Unknown%20image" alt="" width="563">

#### 3.1.2 Options

Users can select additional display options using checkboxes. These include:

* **Formations** – Shows formation tops in the chart.
* **Use Effective TR** – Replaces Turn Rate with Effective Turn Rate (calculated as TR × sin(Inc)).
* **Normalize Yields** – Smooth the motor yield data points by interpolating every 30m/100ft.
* **Plan** – Displays the principal plan on the chart.
* **Legend** – Shows the chart legend in the top right of the chart.

All of these can be enabled or disabled by toggling the associated checkboxes.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/abl4N12c2MnJ4LKODsDP/Unknown%20image" alt="" width="563">

#### 3.1.3 Filter

The Filters section allows the user to display only the desired range of DLS and Slide % results, and can be used to filter out outlying data points. Adjust the sliders to set the minimum and maximum value of each range.

The Filters section also includes dropdown menus for **Phase**, **Hole Size**, and **Formation** allow filtering based on reference well parameters. Selecting an option from any of these dropdowns automatically zooms in on the corresponding depth range.

**Note:** Only one of these dropdown filters can be applied at a time.

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

#### 3.1.4 Axis

The Axis section allows the user to adjust the size of the X and Y axis, by entering values into the respective Min and Max boxes. Clicking the curved arrow icon will reset the zoom to the default view. **Note:** The Y-axis can also be adjusted by scrolling the mouse wheel to zoom, and left click dragging to pan up and down.

Use the Y-Axis dropdown to toggle the Y-Axis between MD and TVD.

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

#### Landing

Users can adjust the desired landing point by entering new **TVD, Azimuth, and Inclination** values. The DLS value will automatically update to reflect the new landing configuration.

Alternatively, the user can select **Auto Landing** to automatically pick the landing point. The Trend Analyzer does this by finding the highest inclination in your principal plan. It will then find the shallowest point where the highest inclination occurs, and use the TVD, inclination and azimuth of that point as the landing.

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

#### Landing Tolerance

Landing tolerance allows the user to define an acceptable window around the required DLS to hit the landing point. Enter the tolerance above (high) or below (low) in TVD, and the DLS window will be automatically calculated. This also adjusts the size of the red box on the results chart.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/CV8S8ixgAx8UZS6jJ0Rc/Unknown%20image" alt="" width="563">

#### 3.1.7 Offsets

The Offsets section allows the user to add motor yield, dogleg, turn rate and build rate data from offset wells to the results chart. This gives the driller an idea of the performance they can expect to achieve during drilling.

Enter a distance (in Miles or Km depending on your unit set) into the **Radius** field. This will populate the dropdown box with offset wells within that radius. The wells can be filtered further by clicking on the <img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/izN8J12PsOp9EY8SJP1j/Unknown%20image" alt="" data-size="line"> icon. This allows the list to be filtered by hole size, assembly type and formation.

Select the wells in the list to display them on the results chart. The number of selected offsets will be displayed below the dropdown.

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

#### 3.1.8 Motor Yields

The Motor Yields section allows the user to define the current achievable motor yield. This value is used to define the inclination and azimuth in the bit projection on the chart. **Note:** You may need to scroll the menu to the right to see this section.

It has 3 non-editable fields:

* Last Yield – Shows the most recent motor yield calculated from the surveys and slide sheet.
* 3 Jnt Avg - Shows the 3 joint average motor yield.
* 4 Jnt Avg - Shows the 4 joint average motor yield.

The **In Use** value shows the motor yield value currently being used in the results chart. It defaults to the 3 jnt avg motor yield. It can be edited by the user or set back to default by clicking in the curved arrow.

## 4.0 Rotary Trends

The **Rotary Trends** tab runs the same data as the Motor Yields tab to visualize Build Rates (BR) and Turn Rates (TR) for the reference well and any selected offsets. This view enables engineers to identify build and turn tendency in their BHA during rotary drilling.

**Note: It is recommended that the Slide % be set close to zero, to eliminate sliding sections that will contain deliberate turn and build.**

### 4.1 Rotary Trends Chart

The rotary trends chart plots all of the surveys in the selected well by build rate and turn rate. Offset data can be added to the chart using the Offsets section in the menu ribbon. Individual wells can be hidden from the results by left clicking on their name in the legend in the top right of the chart.

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

The chart is divided into four quadrants:

* **Quadrant I:** Build & Turn Right
* **Quadrant II:** Build & Turn Left
* **Quadrant III:** Drop & Turn Left
* **Quadrant IV:** Drop & Turn Right

Average values for each quadrant are displayed in the results grid below the chart.

### 4.2 Rotary Trends Results Grid

The rotary trends results grid is displayed below the chart. If no points on the chart are selected, the results grid will show the average values of all of the results displayed in each of the four quadrants. The Hold Point row displays the average values of all of the results that lie within the designated build rate and turn rate thresholds. These thresholds can be changed in the Hold Point section of the menu ribbon.

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

The user can select specific points on the chart by left clicking and dragging a box around them. In this case, the results grid will change to show the minimum, maximum and average value for the selected data points. The Data section of the menu ribbon will also display the number of selected points.

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

The results grid can be exported to Excel format by right clicking on it and selecting **Export.**

### 4.3 Rotary Trends Menu

The ribbon menu at the top of the page provides options to modify the results chart.

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

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/bAOZjOfjuPMucOeu05NW/Unknown%20image) **Refresh Data** – If the input data for the chart has been updated, click on this function to refresh the chart.

#### 4.3.1 Zoom

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/Y5LnpNkGE9piDMx92T1h/Unknown%20image) **Show All Data** –Zooms the chart out to display all data points.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/dQA3PXRhamszF8qBrwd3/Unknown%20image) **Reset Zoom** –The chart can bee zoomed in or out by scrolling the mouse wheel. Clicking on ‘Reset Zoom’ will reset the zoom to default.

#### 4.3.2 Data

Users can select additional display options using checkboxes. These include:

* **Legend** – Shows the chart legend in the top right of the chart.
* **Use Effective TR** – Converts Turn Rate to Effective Turn Rate (calculated as TR × sin(Inc)).
* **Normalize Yields** – Smooth the motor yield data points by interpolating every 30m/100ft.

The **Displayed** counter shows how many points are currently displayed on the chart and the **Selected** and how many points have been selected. Select points by left clicking and dragging a box around the points on the chart.

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

#### 4.3.3 Filters

The Filters section allows the user to display only the desired range of Depth and Slide % results, and can be used to filter out outlying data points. Adjust the sliders to set the minimum and maximum value of each range.

**Note: It is recommended that the Slide % be set close to zero, so that the chart and grid only displays results for rotary sections.**

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

#### 4.3.4 Offsets

The Offsets section allows the user to add motor yield, dogleg, turn rate and build rate data from offset wells to the results chart. This gives the driller an idea of the performance they can expect to achieve during drilling.

Enter a distance (in Miles or Km depending on your unit set) into the **Radius** field. This will populate the dropdown box with offset wells within that radius. The wells can be filtered further by clicking on the <img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/izN8J12PsOp9EY8SJP1j/Unknown%20image" alt="" data-size="line"> icon. This allows the list to be filtered by hole size, assembly type and formation.

Select the wells in the list to display them on the results chart. The number of selected offsets will be displayed below the dropdown.

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

#### 4.3.5 Hold Point

The Hold Point section allows the user to set the Turn Rate and Build Rate thresholds for the Hold Point row in the results grid. Any results on the chart below these thresholds will be used to calculate the values in the Hold Point row.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/yUrBXYWv6wRQtFL6REDJ/Unknown%20image" alt="" width="563">


# Report Groups Guide

## 1.0 - Introduction

The Report Groups feature in Innova Vantage allows your organization to set up mailing lists that will automatically send regular reports on your active rigs. The Report Groups interface allows the user to customize each group for different recipients, rigs and report types. This allows your organization to easily provide stakeholders in your projects with regular updates.

## 2.0 - Workflow

Follow the steps below to create a new Report Group.

1. Click on the burger menu icon in the top left of your screen to open the main menu. Navigate to **Groups >> Report Groups.**

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/TBtHyQR5o2o2JPpPHJQ1/media/image1.png)

2. The Report Groups modal displays existing report groups. Click on one to display options on the menu ribbon:
   1. **Edit:** Allows the user to customise the settings for the report group.
   2. **Delete:** Removes the report group.
   3. **Test:** Manually sends a report email to the designated recipients, allowing the user to verify the setup of the report group.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/kCNSaI6L99V51TdTVThn/media/image2.png)

3. Click on **Add Group** to create a new group and open the Add Report Group modal.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/TBfFdaNHUomkDQpjtyRG/media/image3.png" alt="" width="375"><figcaption></figcaption></figure>

4. Give your group a descriptive name in the **Group Name** field.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/l7f8kycs7reDjhpfV0Uw/media/image4.png" alt=""><figcaption></figcaption></figure>

5. In the **Distribution List** section, add people to the mailing list by entering each email into the **Email** field and clicking the **Add** button.
   1. The emails entered here can be any valid email address. **They do not need to be members of your organisation.**
   2. Multiple emails can be entered at once by separating them with a semi-colon. E.g. <_email1@company1.com>; <email2@company2.com>.\_

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/BUAnenBQcXX9QFBEIKC7/media/image5.png)

6. In the **Group Selections** section, choose the reports that you wish to send using the **Report Types** dropdown. Choose the desired rigs from the **Rigs** dropdown. When it is time to send the reports, Vantage will use **active wells** under the selected rigs as the data source. If there are NO active wells in the database for a selected rig then no report will be included for that rig.
   1. **Note: Reports sent using this method will use the default unit set for your organization.**

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/oKqQtMiFUwlqZ7HrssDU/media/image6.png)

7. In the **Schedule** section choose how often you want the report email to be sent – either daily, weekly or monthly – using the **Frequency** dropdown. Use the **Time** field to set what time of day you wish the email to be sent.
   1. **Note: The Time field references your local PC time zone.**

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/O8XSiMv6blmxnv0Lc0BP/media/image7.png)

8. Selecting the **Enabled** checkbox activates the schedule, ensuring the report cycle is turned on. This option can be toggled off to pause the report email without needing to delete the report group. Then click on **Add** to save the new report group.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/lnuLjbZcPpi7jeEuUUC4/media/image8.png)

9. The report group will now start to automatically send the report email at the scheduled frequency and time.

## 3.0 - Report

Recipients on your mailing list will receive an email from <no-reply@icpwebportal.com> that will look like the below. If recipients do not receive the email, check their spam folders.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/0Vcvdle1ISQBBgkn2g3K/media/image9.png)

Currently, the available report is the Rig KPI Summary Report. This report includes:

* 24 hour summary and lookahead.
* 24 hour drilling KPI summary.
* Depth v Days and Depth v Cost charts.
* Activity Distribution chart.
* Tripping Speed and Connection Speed charts.
* NPT summary.

**Note: The report details the previous 24 hours activity, using a midnight-to-midnight format.** **I.E.,** **If the report is sent** **on a Tuesday, it will detail the activity between 00:00 – 24:00 on Monday.**

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/nKlounZogU3OwNyqZRr1/media/image10.png)


# Data Bridge: Importing 3rd Party Data

## 1.0 - Introduction

To maximise the accessibility, and ultimately the value of your operational data, all information must be stored in a single database using a consistent format.

As different service companies use different systems, this data often needs to be converted and re-entered manually - a time-consuming process.

To streamline the process of conglomerating data from multiple sources into the Innova system, Innova now supports automatic importing of planning and operational data that are either attached to an email, or embedded in the subject line of an email. This feature is called Data Bridge.

Data Bridge supports importing files exported from the following:

* **Baker Hughes** (Well Architect / Cadence)
* **Schlumberger** (Drill Plan / Drill Ops)
* **Landmark** Compass

Additional files/data can also be automatically imported into the Innova system:

* Survey updates
* Image files
* Mud Reports
* Certified Surveys

This document explains how to automatically import these files into the **Innova Suite**.

## 2.0 – Prerequisite Requirements

Before importing files, you must have:

* An Innova Server Database
* Access to Innova Vantage
* Login credentials to Innova Vantage which have Admin permissions

## 3.0 – Email Setup

Before files or data can be imported via email, the sender’s email address must first be authorised within Innova Vantage.

1. Log in to [**Innova Vantage**](https://vantage.innova-drilling.com/well-list) using an **Admin** account
2. Click the **burger menu** (top left) and select **Data Bridge**

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/q5EKmoSy3U3zVEFT2FuO/media/image1.png" alt="" width="188"><figcaption></figcaption></figure>

3. In the Data Bridge Settings dialog, click in the ’Add’ option to open a ‘+Add Data Bridge User’ dialog, where you can set email addresses that will be sending the files/data.When an email has been received by Data Bridge, a processing email will be sent to the **Reply To** email address added, followed by a completion/failure email to the **Reply To** email address.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/Y8AsDFP9dLRU8YlD81GK/media/image2.png)

4. For each email address, select the relevant import types to be authorized from the dropdown list.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/wXHrW7vyhMHNppo836sh/media/image3.png)

5. The settings available are used to correctly interpret the imported data.
   1. If the import type is **SURVEY, CADENCE, WELLARCHITECT, COMPASSEDM, OPENWELLS – CASING TALLY, DRILLPLAN**, or **DRILLOPS**
      1. Ensure that the correct Depth Units are selected.
   2. If the import type is any of the MUD REPORT options:
      1. Select the appropriate Mud Units for the report.
      2. Select the appropriate Date Format used within the report.

**Important:** If a file/data is sent from an unregistered email address, or the actions have been set incorrectly, then the import will fail.

## 4.0 – Baker Hughes

Baker Hughes data is split into two types — *planning* and *operations*.

**Important:**

* Import the **planning (Well Architect) file first**, otherwise the operational data import will fail.
* The API number must be entered in Well Architect before the export file is created. This is required for any well that Cadence data will be imported into, as the API number is used as the common well identifier between Well Architect and Cadence during the import process.

### 4.1 – Planning – Well Architect Files

Well Architect exports a single **.exp** file, containing well planning data (locations, CRS, elevations, targets, plans, offsets etc).

#### 4.1.1 – Importing a Well Architect File

You can import a Well Architect file in two ways:

**Option 1 – Via Innova Vantage:**

1. Go to the **Wells** tab on the Dashboard page.
2. Select **Import >** **Well Architect**

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/tAVwFxNY2bAeRjXoPqzC/media/image4.png)

3. Select the .**exp** file → click **Import**
4. Under *Set Actual Well Status to*, choose a status to assign to all imported Actual Wells

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/za2nZbBadEHhAxczsCaq/media/image5.png" alt="" width="563">

**Option 2 – Via Email:**

1. Email the file to [**OrganizationName**@feed.innova-drilling.com](mailto:OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: Open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered in Innova Vantage (**see Section 3.0: Email Setup**)
4. Email title must be: **Well Architect**
   1. Wells will be pulled in with the **Well Status** set to **Active**.
   2. Add the word **Historical** if submitting a completed well e.g. *Well Architect Historical*
   3. This will automatically set the **Well Status** to **Complete** in the Innova system.
5. Attach one or more unzipped .**exp** files

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/Bad6W0w7L8VYC7PJBW96/media/image7.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/o2KbFmHHO6v9LyVCizgr/media/image8.png)

### 4.2 – Operations – Cadence Files

Cadence exports operational data as a **single zipped folder**, typically containing:

* BHA / Cost / Daily Drilling / MWD / Parameter / Summary reports (.xml)
* Survey report (.csv)
* Optional Activity report (.csv) *(historical only)*

#### 4.2.1 – Importing a Cadence File

It is only possible to import Cadence files via email:

1. Email the zipped file to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
3. Your email address must be registered in Innova Vantage (**see Section 3.0: Email Setup**)
4. Before Cadence data can be imported, the corresponding Well Architect file for the well **must already have been imported.**
5. Email title must be: Cadence - API: api# *(**api# must match Well Architect file**)*

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/49XrkQPJQ7ZsMiscDDhm/media/image9.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/UsUSmRci9HmxNkPvV8Oz/media/image10.png)

## 5.0 – Schlumberger

Schlumberger data is split into two types — *planning* and *operations*.

**Important:**

* Import the **planning (Drill Plan) file first**, otherwise the operational data import will fail.
* The API number must be entered in Drill Plan before the export file is created. This is required for any well that Drill Ops data will be imported into, as the API number is used as the common well identifier between Drill Plan and Drill Ops during the import process.

### 5.1 – Planning – Drill Plan Files

Drill Plan exports a **zipped folder** containing several files (various formats) with well planning data (locations, CRS, elevations, targets, plans, offsets).

#### 5.1.1 – Importing a Drill Plan File

You can import a Drill Plan files in two ways:

**Option 1 – Via Innova Vantage:**

1. Go to the Dashboard page Wells tab.
2. Select **Import >** **Drill Plan**

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/9hU68VNllD73tAFNtXYn/media/image11.png)

3. Select the zipped file → click **Import**

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/QFCcSsFUDDPeqjRbqoVe/media/image12.png" alt="" width="563">

**Option 2 – Via Email:**

1. Email the file to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered in Innova Vantage (**see Section 3.0: Email Setup**)
4. Email title must be: **Drill Plan - API: api#**
   1. Wells will be pulled in with the **Well Status** set to **Active**.
   2. Add the word **Historical** if submitting a completed well e.g. *Drill Plan - API: api# Historical*
   3. Adding Historical, will set the **Well Status** to **Complete** in the Innova system
5. Attach a single zipped file

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/ZhL3W0VUFCu1HuvboSmR/media/image13.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/ZI1t7wFlyDNCPL8hn0rC/media/image14.png)

### 5.2 – Operations – Drill Ops Files

Drill Ops exports multiple **unzipped** files:

* Daily Journal as .html
* Steering report as .csv
* Bha report as .csv
* Survey report as .csv

#### 5.2.1– Importing a Drill Ops File

It is only possible to import Drill Ops files via email:

1. Email all four unzipped files to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
   1. You can add more than 4 files if you have them
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
3. Your email must be registered (**see** **Section 3.0: Email Setup**)
4. Before Drill Ops files can be imported, the corresponding Drill Plan file for the well **must already have been imported.**
5. Email title must be: **Drill Ops – API: api#** (api# must match the Drill Plan file)

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/S7a64mzbAdL8zcIIW6e6/media/image15.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/29Q4Lc6NB7UOjwVrKxHS/media/image16.png)

## 6.0 - Landmark

Landmark’s Compass planning data can be imported.

### 6.1– Planning – Landmarks Compass EDM Files

Landmarks Compass exports a **single .edm** file.

#### 6.1.1 – Importing a Compass File (.edm)

You can import a Compass .edm file in two ways:

**Option 1 – Via Innova Vantage:**

1. Go to the Dashboard page Wells tab.
2. Select **Import >** **Compass EDM**

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/ybn8Gpv5qMRbmM7jy3r1/media/image17.png" alt=""><figcaption></figcaption></figure>

3. Select the .**edm** file
4. Select the import options you want
5. Under *Set Actual Well Status to*, choose a status to assign to all imported Actual Wells
6. Click **Import**

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/NiRC6oCUXViB00Flx8DZ/media/image18.png" alt="" width="563">

**Option 2 – Via Email**

1. Email the file to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered (**Section 3.0: Email Setup**)
4. Email title must be: **EDM**
5. Attach one or more unzipped .edm files

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/w4dt5ECtFVRvk62Ixtkb/media/image19.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/P6cLC5tjUBZ4W8U0sUdp/media/image20.png)

#### – Importing a Compass File (.csv)

You can import a Compass .csv file by email.

1. Email the file to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png" alt=""><figcaption></figcaption></figure>

3. Your email address must be registered (**Section 3.0: Email Setup**)
4. Email title must be: **EDM CSV** or **CSV EDM**
5. Attach one or more unzipped .csv files

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/haOWA0XHR1lGLQt0YokJ/media/image21.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/z2XyZvu7OMd52SLQgtwC/media/image22.png)

## 7.0 – Surveys

Individual survey updates can be imported to a well. This is especially relevant when using the Innova Suite in a real time operations capacity.

1. Email sent to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered (**Section 3.0: Email Setup**).
4. Email title must meet the following formatting criteria to be recognized as a survey email and successfully imported:
   1. Includes the Well name, **EXACTLY** as it appears in the Innova system.
   2. Includes the fields:
      1. **MD:**
      2. **INC:**
      3. **AZI:**
   3. As an example, the below email title is acceptable as it fulfils the above criteria
      1. **Note**: The email title does not need to be in exactly the same format as below. As long as it contains the 4 key details in any order, then it should work.

FW: \[EXTERNAL] Survey – **Cerberus 14-28 - 3H (LH) - Lateral** - SURVEY **MD:** 153' **INC:** 0.07° **AZM:** 350.66° TVD: 153.00' VS: 0.09' DLS: 0.05

## 8.0 – Image Files

Image files can be imported and assigned to specific BHAs.

1. Email the files to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered (**Section 3.0: Email Setup**).
4. Email title must meet the following formatting criteria to be recognized as an image import email and be successfully imported:
   1. Includes the word **Image**
   2. Includes the fields:
      1. **BHA:**
      2. **API:**
   3. As an example, the below email title is acceptable as it fulfils the above criteria

**image api**:1234567890 **bha:4**

5. Attach one or more unzipped image files.

## 9.0 – Updating Well Status to Complete

In addition to the automatic update of the well status when the word *Historical* is included in the email title, as explained above, a well status can also be updated to **Complete** if the email title contains the word *Finals*.

1. Email a file to [**OrganizationName**@feed.innova-drilling.com](mailto:OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: Open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered in Innova Vantage (**see Section 3.0: Email Setup**)
4. Email title must meet the following formatting criteria to be recognized as a completed well:
   1. Includes the word **Finals**
   2. Includes the API #
      1. The API # needs to match an existing well in the Innova System.
   3. As an example, the below email title is acceptable as it fulfils the above criteria

**Finals** | 113001333 | Innova Natural Resources, LLC | H\&P 426 | Cerberus 14-28 – 5H(AN) - Curve | **API: 42301376880000**

## 10.0 – Import Open Wells Casing Tally – Auto Generated Engineering Case

An OpenWells casing tally pdf file can be imported. This will be added as a new Drill String within the Innova system, and an automatic casing run engineering case will be created for that well.

1. Email a file to [**OrganizationName**@feed.innova-drilling.com](mailto:OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: Open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered in Innova Vantage (**see Section 3.0: Email Setup**)
4. Email title must meet the following formatting criteria to be recognized as a completed well:
   1. Includes the word **Casing Tally**
   2. Includes the API #
      1. The API # needs to match an existing well in the Innova System.
   3. As an example, the below email title is acceptable as it fulfils the above criteria

**Casing Tally API: 42301376880000**

5. Attach one casing tally pdf file.

\
11.0 – Mud Reports
------------------

Mud reports can be imported via email and automatically used to create or update Daily Reports within the Innova Suite.

1. Email a file to [**OrganizationName**@feed.innova-drilling.com](mailto:OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: Open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered in Innova Vantage (**see Section 3.0: Email Setup**)
4. The email subject line must contain one of the following supported mud report identifiers:
   1. MUD REPORT AES DRILLING FLUIDS
   2. MUD REPORT BASIN FLUIDS
   3. MUD REPORT BUCKEYE
   4. MUD REPORT MILLER ASSOCIATES
   5. MUD REPORT NEWPARK FLUID SYSTEMS
5. As an example, the below email title is acceptable as it fulfils the above criteria:

**Mud Report Basin Fluids**

6. Attach the mud report PDF to the email.
   1. Multiple mud reports can be processed from a single email.
   2. Only supported mud report formats can be imported.
7. When a mud report is successfully processed, the system will extract the following information:
   1. Well Name
   2. Report Date
   3. Rig
   4. 600/300/200/6/3
   5. PV
   6. YP
   7. Mud Weight
   8. Chlorides
   9. Oil Water Ratio
8. Imported mud data will be applied to the corresponding Daily Report:
   1. If a Daily Report does not already exist for the report date, a new Daily Report will be created automatically.
   2. If a Daily Report already exists for the report date, the existing report will be updated with the imported mud data.

{% hint style="warning" %}
**Note:** Currently supported mud report providers are AES Drilling Fluids, Baker, Baroid, Basin Fluids, Buckeye, Miller Associates, Miswaco, Newpark Fluid Systems and Valence. Reports from other providers may not be recognized or processed.
{% endhint %}

## 12.0 – Certified Survey

Certified Surveys can be imported to a well. Files imported will be stored inside a folder called Directional and can be accessed via External Files on Well Seeker or File Manager on Vantage.

<div><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/bI3wL3FBHLfTCahaArT4/media/image23.png" alt="" width="375"> <img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/yGZMKqzyJtNKTqUAuG1B/media/image24.png" alt="" width="375"></div>

Once certified surveys are imported, the well status will change to TD.

1. Email sent to [**OrganizationName**@feed.innova-drilling.com](mailto:%20OrganizationName@feed.innova-drilling.com)
2. Replace **OrganizationName** with your organization’s name as shown in Vantage.
   1. To find this: open Vantage, hover over the user profile icon, and check the organisation name displayed under your email/login.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OPIFJFdz4sE2slwI1OrB/media/image6.png)

3. Your email address must be registered (**Section 3.0: Email Setup**).
4. Email title must meet the following formatting criteria to be recognized as a certified survey email and successfully imported:
   1. Includes the Well name, **EXACTLY** as it appears in the Innova system.
   2. Includes the fields:
      1. **API #**
      2. **Certified Surveys**
   3. As an example, the below email title is acceptable as it fulfils the above criteria
      1. **Note**: The email title does not need to be in exactly the same format as below. As long as it contains the 3 key details in any order, then it should work.

FW: \[EXTERNAL] **Cerberus 14-28 - 3H (LH) – Lateral**; **API#:1234567890**; **Certified Survey**

5. Attach one or more files (files can be zipped or unzipped).


# 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 Azure

Covers registration and configuration of an OAuth App on Microsoft Azure Portal

## Introduction

It is possible to register an OAuth app for the Microsoft Graph API from the . This document covers the steps required to register an app on the Azure Active Directory and configure permissions for it.

<mark style="color:red;">**Input all data as per this document. Naming conventions are critical for this function to work successfully!**</mark>

## 1.0 - Registering on Azure Portal <a href="#toc109119746" id="toc109119746"></a>

1\. Go to the Microsoft Azure Portal home page at [https://portal.azure.com](https://portal.azure.com/).

2\. Click on the icon in the top left of the page to open the side menu.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbSfiH20TDO8bitSbdrXI%2F0.png?alt=media" alt="" width="431">

3\. In the side menu, select **Azure Active Directory**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQUWtFH7C7bUbY4vFZeBh%2F1.png?alt=media" alt="" width="143">

4\. In the Azure Active Directory window, click **on App Registrations** and then select **New Registration**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fkp2uhCut9jIv9wptLvcU%2F2.png?alt=media" alt="" width="563">

5\. In the Register an Application screen, enter the following information:

* **Name**: ICPAPI
* **Supported Account Types**: Accounts in this organizational directory only

Under the Redirect URL (optional section) enter the following:

* **Select a Platform**: Web
* **Sign-On URL:** Not required

Then click on the **Register** button at the bottom of the page.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2WW6A6ZrNsqxSJfS39fC%2F3.png?alt=media" alt="" width="563">

6\. <mark style="color:red;">**On the newly created Overview page for the app take a copy of the Application (client) ID and the Directory (tenant) ID.**</mark> Hover over each code and select the Copy to Clipboard option when it appears. Save these IDs in a secure location.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjLWFqy5KLPkEisxWHpu5%2F4.png?alt=media)

7\. Create a new Client Secret: On the left of the page click on **Certificates & Secrets.** Then click on **Client Secrets** and **New Client Secret**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fmp5m2S9bWtHeZhJVpE6x%2F5.png?alt=media)

8\. In the window that opens on the right, enter the following:

* **Name (description)**: ICPAPI\_Handshake
* **Expires**: Choose an expiry date that suits you.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdGzlOdLxfpIpwn7ICvHL%2F6.png?alt=media)

Click **Add**- <mark style="color:red;">**A new Client Secret will be generated for you. This will be the only time you will see the Client Secret Value, so you better copy it to a secured location otherwise you won't be able to retrieve it again!**</mark> Click on the Copy to Clipboard icon to the right of the Client Secret Value to copy it.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyLgBqARTlmCjQ3Cbbiwq%2F7.png?alt=media)

## 2.0 - Configuring App Permission <a href="#toc109119747" id="toc109119747"></a>

**Note:** These steps require the user to have admin permissions in their organisation’s Azure Portal.

If the user has navigated away from the App Overview page, they can return to it by clicking on the icon in the top left of the page to open the side menu. Then select Azure Active Directory. In the Azure Active Directory select App registrations from the menu on the left and then select ICPAPI from the list.

1\. From the App Overview page, select **API Permissions** and then **Add a Permission.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fihei7oaeCGYOWO3CcygH%2F8.png?alt=media" alt="" width="498">

2\. In the window that opens on the right, click on **Microsoft Graph**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FhM4639M4rvtR034aC4Rd%2F9.png?alt=media" alt="" width="556">

3\. Click on **Delegated Permissions.** To select a permission, search for it in the search bar and then click on the check box to the left of its name. Select these two permissions:

* **User.Read.All**
* **Application.Read.All**

Click on the **Add Permissions** button to add the selected permissions.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOU79ZlGsMIWpP8o04ymZ%2F10.png?alt=media" alt="" width="563">

4\. In the API Permissions window, click on **Grant admin consent for Innova Drilling & Intervention**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFusBsbDvk8AFr985L3nZ%2F11.png?alt=media" alt="" width="563">

5\. In the menu on the left, click on **Expose an API** and then **Add a Scope**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1EytvjWQAVXtbSXinZd2%2F12.png?alt=media" alt="" width="484">

6\. In the window that opens on the right, click on **Save and Continue.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FuGFf5FHcREjk0jPQWZpq%2F13.png?alt=media" alt="" width="446">

7\. On the next page enter the following information and then click on **Add Scope**:

* **Scope name:** allow\_user&#x20;
* **Who can consent:** Admins and users&#x20;
* The **display name** and **description** entries are optional. Enter a name/description that you want admins and users to see when the consent to the scope later.
* **State:** Enabled.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FI7eCa2SVP7YQH9EJCiVr%2F14.png?alt=media" alt="" width="413">

8\. In the menu on the left click on **API Permissions** and then **Add a permission.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvuCYQTUwtv5s8JAtbP4h%2F15.png?alt=media" alt="" width="500">

9\. In the window that opens on the right, select **My APIs** and then click on your App/API.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOclMr0rrCb8Khl8JYsNJ%2F16.png?alt=media" alt="" width="563">

10\. Select the scope you just created by ticking the check box next to it, and then click on **Add Permissions.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FBGCADzek4lRer5km8bHE%2F17.png?alt=media" alt="" width="536">

## 3.0 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 Azure Active Directory. In addition to these steps, the system admin will require to turn on MFA for the organization, or for individual users within Azure Active Directory. For that process the user should refer to Azure Active Directory documentation.

1\. Once logged on to Azure Active Directory select **Home > App registration > ICPAPI > Authentication**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fh8wecgv6yvcJTQ5iu1Ys%2F18.png?alt=media" alt="" width="349">

2\. Use the call back URI for the single page web app. In the **Single-page application** section add the below URIs by selecting **Add URI**.

* *<https://www.icpwebportal.com>*
* *<https://icpwebportal.com>*
* *<https://eu.icpwebportal.com>*

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1gtCHyyJmB2LA5O2A1Xz%2F19.png?alt=media)

3\. In the **Mobile and desktop applications** section ensure that the URI below is available, if not add it. Check the selection box to select it.

* *<https://login.microsoftonline.com/common/oauth2/nativeclient>*

4\. In the **Mobile and desktop applications** section add the below URI.

* *com.icds-innova-dan://auth*

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FeSRIxBLWLWYPzeiju44O%2F20.png?alt=media)

5\. Scroll down to the **Implicit grant and hybrid flows** section. This is to turn on access tokens for authorization endpoint. Select the check boxes for the **Access tokens** and **ID tokens** options.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fmrb16TCqhOhBPfthAKQX%2Fimage.png?alt=media&amp;token=f87c76cf-48f4-4b6a-ab3e-96d97f3875af" alt="" width="511"><figcaption></figcaption></figure>

6\. Select the **Expose an API** section.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FjhfaTSPA4yE3mMiaWrcM%2Fimage.png?alt=media&amp;token=d3a5d001-8f99-4f5f-8155-777368a1e21e" alt=""><figcaption></figcaption></figure>

7\. Select **Add a scope** and input the below details and then select **Add scope**.

* Scope Name: *icpapi\_read*
* Who can consent: *Admins and users*
* Admin consent display name: *Read icp api*
* User consent display name: *icpapi read*
* State: *Enabled*

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4i1Bk8cvw4AJd1GJVMXt%2Fimage.png?alt=media&amp;token=f0965c3f-49b1-4939-ad72-633536ce7f2f" alt="" width="439"><figcaption></figcaption></figure>


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

<mark style="color:red;">**Input all data as per this document. Naming conventions are critical for this function to work successfully!**</mark>

## Procedure

1. Go to [www.okta.com](http://www.okta.com/) and log in to your account.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZKrkzEuKR3rLtnCTY8lB%2F0.png?alt=media" alt="" width="563">

2\. Click on **Admin** in the top right of the window to access the Admin Dashboard.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fq5Jdpy8TJIoSfLJhHl85%2F1.png?alt=media)

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FagOOeiXamnJHYCxOBtpw%2F2.png?alt=media" alt="" width="563">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fjzl4LVdTPwFk6KZdizVp%2F3.png?alt=media" alt="" width="563">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fr3TehXrBG0vMEziS2BIV%2F4.png?alt=media" alt="" width="556">

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

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fn08Xpuawl7h2HqIjfJg6%2F5.png?alt=media)

6\. On the next screen, named ‘icpApi’ in this case, click on the **Edit** button in the Client Credentials section.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F0HzzcuA4u5s1M3hFGpWu%2F6.png?alt=media" alt="" width="563">

Change the **Client Authentication** setting to **Client secret**, then click **Save**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5QQqcspcbQrEYgL5y7Zq%2F7.png?alt=media" alt="" width="563">

7\. <mark style="color:red;">Take a note of the</mark> <mark style="color:red;"></mark><mark style="color:red;">**Client ID, Client Secret**</mark> <mark style="color:red;"></mark><mark style="color:red;">and</mark> <mark style="color:red;"></mark><mark style="color:red;">**Domain**</mark><mark style="color:red;">. The Client ID and Client Secret can be copied to clipboard by clicking on the</mark> ![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FQXOO5bAByhc63DJ8Vzp3%2F8.png?alt=media) <mark style="color:red;">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).</mark> <mark style="color:red;"></mark><mark style="color:red;">**Provide these three pieces of information to Innova.**</mark>

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMCDldPcaUHYko4gR3pWx%2F9.png?alt=media" alt="" width="539">

8\. Scroll back up to the top of the screen and click on **Sign On**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyHAt8o1UgIQ9kiTEWVH4%2F10.png?alt=media" alt="" width="537">

9\. In the Sign On screen, scroll down to the User Authentication section and click on **Edit**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FnmHriNkuObckBejtEyCZ%2F11.png?alt=media)

Change the Authentication Policy to **Password Only** and then click on **Save**.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAeDlokPtZjZPDATO8gdI%2F12.png?alt=media)

10\. Scroll back up to the top of the screen and click on **Okta API Scopes.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fqj5LSf0llBQDV5q4frQl%2F13.png?alt=media" alt="" width="537">

11\. Click on **Grant** next to the **Okta.apps.read** scope to grant consent.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGjF9kl8tOeiZhPUZT61l%2F14.png?alt=media" alt="" width="534">

12\. Scroll back up to the top of the screen and click on **Okta API Scopes.**

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFey6GMOh0XPilV97W1D3%2F15.png?alt=media" alt="" width="530">

13\. Click on **Assign** and then **Assign to People**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FD1q3Nxik8r5JbC158C14%2F16.png?alt=media" alt="" width="533">

14\. Assign the relevant users by clicking on the **Assign** button beside each user, then click **Done**.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7FoeHgBW9qBJJ3p7fQqJ%2F17.png?alt=media" alt="" width="539">

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

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FMKCKCZLmNUOBM1P40C8G%2F18.png?alt=media" alt="" width="563">

Add the below to the call backs

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FVshexFV2x1ae6nRBWD9H%2F19.png?alt=media" alt="" width="563">

## 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*


# Vantage Data Link Guides


# Vantage Data Link: Installation Guide

## 1.0 - Introduction

This document is a guide for installing the Vantage Data Link software on the user’s computer. Follow this guide to install Vantage Data Link on a fresh computer.

## 2.0 - Download

The Vantage Data Link installer can be downloaded from the Innova website. Follow the below link to go to our download page:

<p align="center"><a href="https://www.innova-drilling.com/download/trial"><strong>Download – Innova Drilling &#x26; Intervention</strong></a></p>

Click on **Existing Users**, then click on **Download**.

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

## 3.0 - Installation

**When downloaded, Vantage Data Link will 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 “Vantage Data Link”

Once the files have been extracted, open the Vantage Data Link folder and double click on the “Vantage Data Link vx.x.x.exe” file to begin the installation process.

Select the location which you wish to install Vantage Data Link. The default location is “**C:\Program Files (x86)\Innova Drilling and Intervention\Vantage Data Link**”. If you wish to change the location the program is installed to click on the “…” button.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/Iu7Z5E2swD1ZIOK2VtpS/Unknown%20image" alt="" width="375">

If you have read the terms and conditions and want to proceed without reading it again, click on the checkbox to agree with the licenses terms and conditions and click on “Install” *to proceed.*

If you wish to read the terms, click on “Licenses terms and conditions”, this will display the below screen. This information can also be printed for future reference by selecting the printer icon. Once read, select the “Accept” and “Install” button to begin installation.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/d1eBgs8ERbl4G5wgtGHK/Unknown%20image" alt="" width="375">

The user will be presented with a dialog. Click “Yes” to continue the installation.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/0kbP5G0PYKoTlszJzoUG/Unknown%20image" alt="" width="375">

Once the installation is complete the final dialog will display “Vantage Data Link has been successfully installed”. Select “Finish” to close the dialog.

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

## 4.0 – Troubleshooting

This section describes common troubleshooting scenarios that can occur during installation, and how to solve them.

### 4.1 – File access error

During installation, the user receives a message referring to not having permission to access a file location on the PC.

This can be caused by the user’s anti-virus software blocking the installer. To resolve this issue, temporarily disable your anti-virus before running the installer.


# Vantage Data Link Guide

## 1.0 - Introduction

The Vantage Data Link (VDL) is a standalone application, that provides the user with a simple to use method of sending WITS data from any PC with a WITS connection, back to the server database, without the requirement for Well Seeker X (WSX) at the rig site. This WITS EDR data can then be visualized in Vantage and will be automatically stored by the Vantage Data Acquisition system.

Historically, getting WITS EDR data back to the server database has been reliant upon the WSX PC being connected to a WITS feed. However, in most cases this requires a physical cabled connection, and so WITS data transmission to the server database was being severed if the WSX laptop had to be moved, for example, when taking the laptop to the rig floor.

The VDL solves this problem, by allowing WITS data to be pushed back to an organizations server database by any PC with a WITS connection. The ideal candidates for this would be the MWD PC, or a dedicated WITS transmission PC.

## 2.0 - Workflow

The following are the recommended steps to follow when setting up a WITS connection using VDL:

* Install Vantage Data Link
* Ensure an administrator has assigned the intended user the correct role permissions
* Open VDL. Log in using Vantage login credentials
* Select a well to send WITS data to in the server database
* Confirm the correct Unit Set is selected
* Select or create a WITS mapping template
* Add or select a WITS connection
* Start Reading
* When the well is complete, open Vantage Data link and Stop Reading

## 3.0 - Installation

For installation instructions, please refer to [Vantage Data Link: Installation Guide](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-data-link-guides/vantage-data-link-installation-guide)

## 4.0 - Login

To be able to log in, the user must be assigned a role with the Vantage Data Link **Base** and **Data Acq** features enabled. These permissions can be configured by an administrator in the **User Management > Roles** page in Vantage.

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

Once this has been configured, the user can log in using their Vantage credentials following the next steps.

1. Click on ‘Log in’

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/oyE21dCHuLg6CUb3oQWV/Unknown%20image" alt="" width="375">

2. Enter the username email and select ‘Continue’
3. Enter Password and select ‘Continue’

<div><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/TBco3YIa4jVF6oK47wgX/Unknown%20image" alt="" width="375"> <img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/U67QnoLgKhNGFTJohvHv/Unknown%20image" alt="" width="375"></div>

4. Authorize access by selecting ‘Accept’

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/IOoWKwVYUyYTU2YQstpP/Unknown%20image" alt="" width="375">

## 5.0 - Overview

Vantage Data Link consists of three main tabs:

* Wells
* Rigs
* WITS

Before setting up a WITS connection, the user must first select a well. This can be done from either the Wells or Rigs tab.

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

A status bar is displayed at the bottom of the screen, showing connection information, regardless of the tab the user has selected:

* Service
* Request
* Data
* Records
* Well Name
* Template
* Unit Set
* Recent Errors

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

### 5.1 - Wells

The Wells tab displays all available wells for selection. Only wells with a valid status will be displayed. Any wells with no status or a status of N/A will not be available in this list. If the required well is not visible, this must be corrected in Vantage.

A single well can be selected by checking the row checkbox for the corresponding well name. Only wells with ‘Active’ status can be selected. If the user tries to select a well with another status, a message will be displayed in the bottom of the screen informing ‘Only Active wells can be selected’.

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

Once the well is selected, the well name will be displayed at the top-left corner and in the status bar.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrRXZXsjvGtUUg3c7psjE%2Fimage.png?alt=media&amp;token=e6784c2c-4856-4f75-b0ca-679f09fb23b9" alt=""><figcaption></figcaption></figure>

To assist in locating a specific well in the list, the user can apply filters by selecting the option at the top of the grid. The filters available are: **All**, **7d**, **60d**, **1y**, **Favorites** and **BHA in Hole**.

Favorite wells will have a yellow star in the icon and can be set by clicking in the Account Settings in the top-right corner and selecting **Favorites**. This will open a dialog where users can set the favorites based on Rigs, Operators or Districts.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/mezTrzTDjnA56RA2isz9/Unknown%20image" alt="" width="563">

Alternatively, users can use the search bar in the top of the screen to search for the desired well.

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

In the right side of the screen, user can use the ‘Refresh’ button to refresh the wells page, and select to display the grid, the map or both.

### 5.2 - Rigs

The Rigs tab provides an alternative way to select a well based on rig grouping instead of well listing. This tab is very similar to Wells, but the available filters will be only **Favorites** and **BHA in Hole.**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzOw6JpqijXkWsLo21ZuC%2Fimage.png?alt=media&amp;token=20268be9-aaf2-46d6-be57-c8b3cfcbc0ab" alt=""><figcaption></figcaption></figure>

If the most recently updated Active well for a Rig has been selected in the Wells tab, it will also be marked in the Rigs tab, and vice versa.

### 5.3 - WITS

The WITS tab contains three sections:

* Connection: Where the user can add or select a connection for WITS in and WITS out.
* Mapping: Where the user defines which WITS channel corresponds to which internal mnemonic used.
* Stream: Where the user can see incoming data and any error messages.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FyRcKVJavrc19jCeGBkXy%2Fimage.png?alt=media&amp;token=cca8e55a-3379-4ab9-abea-393f533c976c" alt=""><figcaption></figcaption></figure>

#### 5.3.1 - Connection

When adding a new connection, , user can add:

* WITS IN: Where the data will be sent from the Rig to Vantage Data Link.
* WITS OUT: Where the data will be sent from Vantage Data Link to an external display, third-party software, or the client cloud.

When adding any of these connections, user can opt between 4 types:

* TCP Client
* TCP Server
* UDP Client
* Serial

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

The user can create a new connection by selecting the desired option, filling in the required information and clicking on ‘Create connection’ button’.\
For **TCP Client** and **UDP Client** connections the required inputs are **Host** and **Port**. For **TCP Server** connection, only **Port** input is required. For a **Serial** connection the inputs needed are **Serial Port** and **Baud Rate**.

The connections added can be edited by clicking the **Edit** button. The connection for WITS in can also be deleted by clicking the **Delete** button.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/gLP7gjPIkwdRh0gNgBz8/Unknown%20image" alt="" width="375">

Once the user has created a valid connection and selected the **Start** button, the connection will attempt to start. If successful, the status will change to **Running**. A **Stop** button will then become available on Connection WITS IN, a **Start** button will appear in the Connection WITS OUT, and the Stream section will begin populating with data.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FYtYEmvu87oHiKvbXMPN1%2Fimage.png?alt=media&amp;token=8a741b4a-4e29-49f3-8780-437ec91cd4f7" alt="" width="226"><figcaption></figcaption></figure>

If the user wants to send WITS OUT, it is necessary to click in the Start button in the Connection-Out grid.
\
**Note:** Start and Stop button will only be available in the Connection-Out grid, when WITS IN is running.

Once a connection has started the Auto Start status will change to Auto Start. This means that if the user now closed the VDL application, and has their computer turned on, the VDL data stream will continue to run as a background task. Even if the user restarts their computer, the VDL will reinitiate as background task, without the user having to reopen the VDL application.

Once the well is completed, it is important that the user reopens the VDL application and selects **Stop**. This will stop the data stream and set the Auto Start status to Manual Start. This will prevent data from pushing to the selected well as a background task, when having the computer turned on.

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

#### 5.3.2 - Mapping

This section defines which WITS channel corresponds to which internal mnemonic used.

A **Template** dropdown is available for selecting a mapping template. The system includes three default templates that cannot be edited or deleted: **Default**, **RigSense** and **SoloBox**.When one of these system templates is selected, the only available options in the Mapping menu are **New**, **Duplicate**, and **Save As**.

If the user creates a new template, all Mapping menu options become available. The user can also edit the **Record** and **Field** columns in the Mapping grid by double-clicking the desired cell.

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

**Export:** Export and save the selected template to the user computer in .json format.

**New:** Creates a new Mapping template.

**Duplicate:** Duplicate the selected template.

**Rename:** Opens a dialog where the user can change the template name.

**Discard:** Discards any changes done in the mapping grid. Only available when the user has changed a Record or Field in the mapping grid.

**Save:** Saves all changes done in the mapping grid. Only available when the user has changed a Record or Field in the mapping grid.

**Save As:** Saves as a new template.

**Delete:** Deletes the selected template.

#### **5.3.2.1 - Unit Selection**

The units that will be assigned to each mnemonic can be seen in the right most Mapping column. It is important that the correct **Unit Set** is selected before starting a WITS connection, as the WITS data will be permanently stored based upon the unit set designation. The Unit Set can be changed by clicking in the Account Settings at the top-right corner and selecting **Change Units**.

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

#### 5.3.3 - Stream

The Stream section displays incoming WITS data once a connection is running. It displays values, timestamps, and error messages where applicable. Before starting a connection, the stream is empty. Once the user starts the stream, incoming records will appear in real time.Clicking on ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/TkAdDMK1aBSGYqdI82HN/Unknown%20image) will clear the Stream Buffer, ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/wAZRHYoLL4BSbLNmsk1T/Unknown%20image) and ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/Bc8oWLfWVbsvyd4DxX7s/Unknown%20image) will Pause/Resume stream polling and ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/0VZIgeTj844isHoeZ0VV/Unknown%20image) will scroll to the top of the page.

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

## 6.0 - Troubleshooting

* *I have set up my connection, but there is no **Start** button available:* This is because you have not selected a well yet. As soon as you have done this the Start button will appear.

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

* *I have set up my connection and selected **Start**, but the Stream section is not updating*: This means that data is not being transmitted on the connection that you have set up. Check the connection details and that the WITS data provider has WITS Out turned on.

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

* *I have data values appearing in my Mapping Value column, but they don’t look like the correct values*: Two potential issues
  1. The Mapping does not match the WITS Out providers Mapping. Check this to ensure that each channel matches the WITS Out providers exactly for any relevant data types. This is normally quite obvious, e.g., you are receiving a value of 15,000 for the rpmAvg data etc.
  2. The mapping is correct, but the unit selection is not correct. WITS data is sent unitless, as a simple number. It is important for the user to assign the correct units for each data type. A typical example of this is this the torqueAvg value seems too large/small, due to the value being transmitted as e.g., 15 or 15,000. In this case the torque units would need to be kftlbs or ftlbs respectively. Ensure that the correct unit set gets selected (see [5.3.2.1 Unit Selection](#_5.3.2.1_Unit_Selection) for details), otherwise this data will be saving to the database incorrectly.
* *When Vantage Data Link is running, it works correctly, but my other WITS software does not work at the same time*: Depending on the WITS Out and WITS hardware configuration, sometimes a single WITS Out feed can only be sent to one software at a time. E.g., if you have VDL and MWD WITS software both trying to use the same connection details, then one can effectively steal that port and prevent the other from using it. The solution to this is have the MWD/other WITS software use the main WITS Out feed connection, and then set up another WITS Out feed with different connection details to send data to VDL.


# Well Seeker X Manual

The full Well Seeker X manual


# 1.0 - System Requirements

## 1.1 - 64-Bit Requirements <a href="#hlk72494511" id="hlk72494511"></a>

Well Seeker X 64-Bit 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 greater.
* Microsoft Office 64-bit (x64) version 2007 or later.
* Windows XP, Windows 7 and Mac OS are NOT supported.
* Recommended screen resolution: 1920 x 1080.

&#x20;

## 1.2 - 32-Bit Requirements

Well Seeker X 32-Bit recommended system requirements:

* Intel i5 processor or equivalent.
* 4 GB of RAM.
* 500MB of hard disk space.
* Microsoft Windows 32-bit (x86) version 10 or greater.
* Microsoft Office version 2007 or later.
* Windows XP, Windows 7 and Mac OS are NOT supported.
* Recommended screen resolution: 1920 x 1080.

&#x20;

## 1.3 - Innova Vantage Requirements

Well Seeker Web client is compatible with the following browsers:

* Desktop browser: Microsoft Edge, Google Chrome, or Firefox.
* Mobile operating system: iOS or Android.

&#x20;

## 1.4 - Self-Hosted Remote Server

If your company wishes to host your remote server database, this is the recommended 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.


# 2.0 - End User License Agreement

**IMPORTANT NOTICE: PLEASE READ CAREFULLY BEFORE INSTALLING THE SOFTWARE:** This licence agreement (Licence) is a legal agreement between you (Licensee or you) and Innova Drilling and Intervention Limited of Union Plaza, 1 Union Wynd, Aberdeen, AB10 1DQ (Licensor, we or us) for the software (being one or more of Well Seeker X or Innova Engineering) (Software) which you have selected to either trial or purchase , which includes computer software, the data supplied with it, the associated media, and electronic documentation comprising the Installation Guide, the details of the Software available from the Licensor’s website and the PDF user manual provided with the download of the Software (Documentation).

THIS SOFTWARE REQUIRES (1) A COMPUTER WITH A MINIMUM OF 4Gb RAM AND 500MB HARD DRIVE, (2) MICROSOFT WINDOWS 7, 8, 10 OR 11 OPERATING SYSTEM AND (3) MICROSOFT EXCEL.

BY CLICKING ON THE "AGREE" BUTTON BELOW YOU AGREE TO THE TERMS OF THIS LICENCE WHICH WILL BIND YOU AND YOUR EMPLOYEES. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENCE, WE ARE UNWILLING TO LICENSE THE SOFTWARE TO YOU AND YOU MUST DISCONTINUE INSTALLATION OF THE SOFTWARE NOW BY CLICKING ON THE "I DO NOT AGREE" BUTTON BELOW. IN THIS CASE YOU MUST RETURN THE MEDIUM ON WHICH THE SOFTWARE IS STORED AND ALL ACCOMPANYING DOCUMENTATION TO US WITHIN 30 DAYS OF PURCHASE. IF YOU DO THIS YOUR LICENCE FEE WILL BE REFUNDED.

### **1. GRANT AND SCOPE OF LICENCE**

1.1In consideration of payment of an annual licence fee (except where the Software is downloaded on a trial basis), the Licensor hereby grants to you a non-exclusive, non-transferable licence to use the Software and the Documentation on the terms of this Licence. If you do not renew your licence fee in one year, your licence will come to an end one year from the date of download of the Software and your licence to use the Software will automatically come to an end. If you have selected the option to trial the Software, your licence to trial the Software is subject to the terms of this Licence and your licence to use the Software will come to an end thirty days from the date of download of the Software. You may only use the Software under a trial period once.

1.2 You may:

(a) install and use the Software for your internal business purposes only on one physical CPU;

(b) transfer the Software from one computer to another provided it is used on only one computer at any one time;

(c) receive and use any free supplementary critical software code or update of the Software incorporating "patches" and corrections of critical errors as may be provided by the Licensor from time to time; and

(d) use any Documentation in support of the use permitted under condition 1.1 as is reasonably necessary for its lawful use.

### **2. LICENSEE'S UNDERTAKINGS**

2.1Except as expressly set out in this Licence or as permitted by any local law, you undertake:

(a) not to copy the Software or Documentation except where such copying is incidental to normal use of the Software or where it is necessary for the purpose of back-up or operational security;

(b) not to rent, lease, sub-license, loan, translate, merge, adapt, vary or modify the Software or Documentation;

(c) not to make alterations to, or modifications of, the whole or any part of the Software nor permit the Software or any part of it to be combined with, or become incorporated in, any other programs;

(d) not to disassemble, de-compile, reverse engineer or create derivative works based on the whole or any part of the Software nor attempt to do any such things except to the extent that (by virtue of section 296A of the Copyright, Designs and Patents Act 1988) such actions cannot be prohibited because they are essential for the purpose of achieving inter-operability of the Software with another software program, and provided that the information obtained by you during such activities:

(i) is used only for the purpose of achieving inter-operability of the Software with another software program;

(ii) is not disclosed or communicated without the Licensor's prior written consent to any third party to whom it is not necessary to disclose or communicate it; and

(iii) is not used to create any software which is substantially similar to the Software;

(e) to keep all copies of the Software secure and to maintain accurate and up-to-date records of the number and locations of all copies of the Software;

(f) to supervise and control use of the Software and ensure that the Software is used by your employees and representatives in accordance with the terms of this Licence;

(g) to include the copyright notice of the Licensor on all entire and partial copies of the Software in any form;

(h) not to provide, or otherwise make available, the Software in any form, in whole or in part (including, but not limited to, program listings, object and source program listings, object code and source code) to any person other than your employees without prior written consent from the Licensor;

(i) not to use the Software via any communications network or by means of remote access.

2.2 You must permit the Licensor and his representatives, at all reasonable times and on reasonable advance notice, to inspect and have access to any premises, and to the computer equipment located there, at which the Software or the Documentation is being kept or used, and any records kept pursuant to this Licence, for the purpose of ensuring that you are complying with the terms of this Licence.

2.3 You confirm and warrant that you will not use or permit the use of the Software (whether through permission or act of omission) in any way which would breach (directly or indirectly) EU restrictive measures, including but not limited to financial and economic sanctions or the same as implemented by European Union member states.

2.4 You confirm and warrant that you will not use or permit the use of the Software (whether through permission or act of omission) in any way which would breach (directly or indirectly) U.S. restrictive measures, including but not limited to financial and economic sanctions or the same as implemented by the United States of America.

2.5 You shall indemnify us against any losses, liabilities, penalties, damages, costs, claims and expenses (including but not limited to legal fees and investigation expenses) incurred by, or awarded against, us as a result of any breach of the warranties set out in condition 2.3 or 2.4 by you or your associated persons, any person working for you or any third party retained by you.

### **3. SUPPORT**

The Licensor's technical support staff will endeavour to answer by telephone any queries which you may have regarding the use or application of the Software. For telephone support please contact the support email <support@innova-drilling.com> between the hours of 09:00 and 17:00 Monday – Friday.

### **4. INTELLECTUAL PROPERTY RIGHTS**

4.1 You acknowledge that all intellectual property rights in the Software and the Documentation throughout the world belong to the Licensor, that rights in the Software are licensed (not sold) to you, and that you have no rights in, or to, the Software or the Documentation other than the right to use them in accordance with the terms of this Licence.

4.2 You acknowledge that you have no right to have access to the Software in source code form or in unlocked coding or with comments.

### **5. WARRANTY**

5.1 The Licensor warrants that:

(a) the medium on which the Software is stored and distributed is (at the time it is supplied), and will be for the period of 90 days after that time (**Warranty Period**), free from defects in design, material and workmanship under normal use. If a defect in the medium occurs during the Warranty Period, the Licensor will replace it free of charge if you return it to the Licensor with proof of purchase and (so far as you are able) a documented example of such defect or error;

(b) always subject to condition 5.2 and 5.3, during the Warranty Period, the Software will, when properly used, perform substantially in accordance with the functions described in the Documentation (provided that the Software is properly used on the computer and with the operating system for which it was designed as referred to in the accompanying documentation), and the Documentation correctly describes the operation of the Software in all material respects; and

(c) it has tested the Software for viruses using commercially available virus-checking software, consistent with current industry practice.

5.2 YOU ACKNOWLEDGE THAT THE SOFTWARE HAS NOT BEEN DEVELOPED TO MEET YOUR INDIVIDUAL REQUIREMENTS AND THAT IT IS THEREFORE YOUR RESPONSIBILITY TO ENSURE THAT THE FACILITIES AND FUNCTIONS OF THE SOFTWARE AS DESCRIBED IN THE DOCUMENTATION MEET YOUR REQUIREMENTS.

5.3 YOU ACKNOWLEDGE THAT THE SOFTWARE MAY NOT BE FREE OF BUGS OR ERRORS AND YOU AGREE THAT THE EXISTENCE OF ERRORS SHALL NOT CONSTITUTE A BREACH OF THIS LICENCE. WE DO NOT WARRANT THAT THE CONTENT OF THE SOFTWARE IS ACCURATE, CURRENT OR ERROR-FREE AND WE EXPRESSLY DISCLAIM ANY WARRANTY OR REPRESENTATION AS TO THE ACCURACY OF THE CONTENT OF THE SOFTWARE AND DUE TO THE NATURE OF THE SOFTWARE, YOU AGREE AND ACKNOWLEDGE THAT YOU WILL VERIFY ANY RESULTS OBTAINIED FROM YOUR USE OF THE SOFTWARE.

5.4If, within the Warranty Period, you notify the Licensor in writing of any defect or fault in the Software in consequence of which it fails to perform substantially in accordance with the Documentation, and such defect or fault does not result from you having amended the Software or used it in contravention of the terms of this Licence, the Licensor will, at its sole option, repair or replace the Software, provided that you make available all information that may be necessary to assist the Licensor in resolving the defect or fault, including sufficient information to enable the Licensor to recreate the defect or fault.

### **6. LICENSOR'S LIABILITY**

6.1 This condition sets out the entire liability of the parties (including any liability for the acts or omissions of their respective employees, agents and subcontractors) to each other in respect of:

(a) any breach of this Licence however arising;

(b) any use made or resale of the Software or the Documentation by you, or of any product or service incorporating any of the Software or the Documentation; and

(c) any representation, statement or tortious act or omission (including negligence) arising under or in connection with this Licence.

This condition is always subject to the warranties set out at condition 5 above.

6.2Nothing in this Licence shall limit or exclude the liability of either party for:

(a) death or personal injury resulting from negligence; or

(b) fraud or fraudulent misrepresentation; or

(c) breach of the terms implied by section 12 of the Sale of Goods Act 1979; or

(d) breach of section 2 of the Consumer Protection Act 1987; or

(e) the deliberate default or wilful misconduct of that party, its employees, agents or subcontractors.

6.3 Without prejudice to conditions 2.4 and 6.2, neither party shall under any circumstances whatever be liable to the other, whether in contract, delict (including negligence) or restitution, or for breach of statutory duty or misrepresentation, or otherwise, for any:

(a) loss of income;

(b) loss of business profits or contracts;

(c) business interruption;

(d) loss of the use of money or anticipated savings;

(e) loss of information;

(f) loss of opportunity, goodwill or reputation;

(g) loss or deferral of production;

(h) loss of product;

(i) loss of, damage to or corruption of data; or

(j) any indirect or consequential loss or damage of any kind howsoever arising and whether caused by tort (including negligence), breach of contract or otherwise;

provided that this condition 6.3 shall not prevent claims for loss of or damage to your tangible property that fall within the terms of condition 5 or any other claims for direct financial loss that are not excluded by any of categories (a) to (j) inclusive of this condition 6.3.

6.4 Subject to condition 6.2 and condition 6.3, the Licensor's maximum aggregate liability under or in connection with this Licence, whether in contract, delict (including negligence) or otherwise, shall in all circumstances be limited to the annual licence fee paid.

6.5 Subject to condition 6.2 and condition 6.3, the Licensor's liability for infringement of third party intellectual property rights shall be limited to breaches of rights subsisting in the UK.

6.6 This Licence sets out the full extent of the Licensor's obligations and liabilities in respect of the supply of the Software and Documentation. In particular, there are no conditions, warranties, representations or other terms, express or implied, that are binding on the Licensor except as specifically stated in this Licence. Any condition, warranty, representation or other term concerning the supply of the Software and Documentation which might otherwise be implied into, or incorporated in, this Licence, or any collateral contract, whether by statute, common law or otherwise, is hereby excluded to the fullest extent permitted by law.

### **7. TERMINATION**

7.1 The Licensor may terminate this Licence immediately by written notice to you if:

(a) you fail to pay the any Licence fees due;

(b) you commit a material or persistent breach of this Licence which you fail to remedy (if remediable) within 14 days after the service on you of written notice requiring you to do so; or

(c) a petition for a bankruptcy order to be made against you has been presented to the court; or

(d) the Licensee (where it is a company) becomes insolvent or unable to pay its debts (within the meaning of section 123 of the Insolvency Act 1986), enters into liquidation, whether voluntary or compulsory (other than for reasons of bona fide amalgamation or reconstruction), passes a resolution for its winding-up, has a receiver or administrator manager, trustee, liquidator or similar officer appointed over the whole or any part of its assets, makes any composition or arrangement with its creditors or takes or suffers any similar action in consequence of its debt.

7.2 Upon termination for any reason:

(a) all rights granted to you under this Licence shall cease;

(b) you must cease all activities authorised by this Licence;

(c) you must immediately pay to the Licensor any sums due to the Licensor under this Licence; and

(d) you must immediately delete or remove the Software from all computer equipment in your possession and immediately destroy or return to the Licensor (at the Licensor's option) all copies of the Software then in your possession, custody or control and, in the case of destruction, certify to the Licensor that you have done so.

### **8. TRANSFER OF RIGHTS AND OBLIGATIONS**

8.1 This Licence is binding on you and us and on our respective successors and assigns.

8.2 You may not transfer, assign, charge or otherwise dispose of this Licence, or any of your rights or obligations arising under it, without our prior written consent.

8.3 The Licensor may transfer, assign, charge, sub-contract or otherwise dispose of this Licence, or any of his rights or obligations arising under it, at any time during the term of the Licence..

### **9. NOTICES**

All notices given by you to the Licensor must be given to Innova Drilling and Intervention Ltd at Union Plaza (6th Floor), 1 Union Wynd, Aberdeen, Scotland, AB10 1DQ. The Licensor may give notice to you at either the e-mail or postal address you provided to it when purchasing the Software. Notice will be deemed received and properly served 24 hours after an e-mail is sent, or three days after the date of posting of any letter. In proving the service of any notice, it will be sufficient to prove, in the case of a letter, that such letter was properly addressed, stamped and placed in the post and, in the case of an e-mail, that such e-mail was sent to the specified e-mail address of the addressee.

### **10. EVENTS OUTSIDE THE LICENSOR'S CONTROL**

10.1 The Licensor will not be liable or responsible for any failure to perform, or delay in performance of, any of his obligations under this Licence that is caused by an event outside his reasonable control (Force Majeure Event).

10.2 A Force Majeure Event includes any act, event, non-happening, omission or accident beyond our reasonable control and includes in particular (without limitation) the following:

(a) strikes, lock-outs or other industrial action;

(b) civil commotion, riot, invasion, terrorist attack or threat of terrorist attack, war (whether declared or not) or threat or preparation for war;

(c) fire, explosion, storm, flood, earthquake, subsidence, epidemic or other natural disaster;

(d) impossibility of the use of railways, shipping, aircraft, motor transport or other means of public or private transport;

(e) impossibility of the use of public or private telecommunications networks;

(f) the acts, decrees, legislation, regulations or restrictions of any government.

10.3 The Licensor's performance under this Licence is deemed to be suspended for the period that the Force Majeure Event continues, and he will have an extension of time for performance for the duration of that period. We will use our reasonable endeavours to bring the Force Majeure Event to a close or to find a solution by which our obligations under this Licence may be performed despite the Force Majeure Event.

### **11. WAIVER**

11.1 If the Licensor fails, at any time during the term of this Licence, to insist on strict performance of any of your obligations under this Licence, or if the Licensor fails to exercise any of the rights or remedies to which he is entitled under this Licence, this shall not constitute a waiver of such rights or remedies and shall not relieve you from compliance with such obligations.

11.2 A waiver by the Licensor of any default shall not constitute a waiver of any subsequent default.

11.3 No waiver by the Licensor of any of these terms and conditions shall be effective unless it is expressly stated to be a waiver and is communicated to you in writing.

### **12. SEVERABILITY**

If any of the terms of this Licence are determined by any competent authority to be invalid, unlawful or unenforceable to any extent, such term, condition or provision will to that extent be severed from the remaining terms, conditions and provisions which will continue to be valid to the fullest extent permitted by law.

### **13. ENTIRE AGREEMENT**

13.1 This Licence and any document expressly referred to in it constitute the whole agreement between us and supersedes any previous arrangement, understanding or agreement between us, relating to the licensing of the Software and Documentation.

13.2 We each acknowledge that, in entering into this Licence (and the documents referred to in it), neither of us relies on any statement, representation, assurance or warranty (Representation) of any person (whether a party to this Licence or not) other than as expressly set out in this Licence or those documents.

13.3 Each of us agrees that the only rights and remedies available to us arising out of or in connection with a Representation shall be for breach of contract as provided in this Licence.

13.4 Nothing in this clause shall limit or exclude any liability for fraud.

### **14. LAW AND JURISDICTION**

This Licence, its subject matter or its formation (including non-contractual disputes or claims) shall be governed by and construed in accordance with Scots law and submitted to the non-exclusive jurisdiction of the Scottish courts.


# 5.0 - Main User Interface

When Well Seeker X is run, it opens to the main user interface. The main interface is where the user can view the database structure, any opened surveys, plans and charts, and access most of the Well Seeker features via the menu ribbons.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FX6nzCpGE6khy5YDbtC8T%2Fimage.png?alt=media&amp;token=de645ec9-c64f-47ce-8fbf-0c55388f174b" alt=""><figcaption><p>Figure 1: Main Well Seeker X interface</p></figcaption></figure>

The main user interface is split into a number of sections, which are described in the chapters below.

## 5.1 - Survey, Plan & Chart Viewing Area

The majority of the Well Seeker X interface is made up of the Viewing Area. Double clicking on a survey, actual wellbore, plan or planned wellbore in the Object Explorer will open it in the Viewing Area. When viewing one of these objects, the user will be able to display charts in the Viewing Area by clicking on one of the options in the Home ribbon menu.

When multiple objects are displayed at the same time, the user can switch between them by clicking on the tabs at the top of the viewing area. Items can be closed by clicking on the **x** in each tab.

![Figure 2: Object tabs in the Viewing Area](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FigamAeSkGfADB6DghxvI%2F1.png?alt=media)

When viewing a survey, actual wellbore, plan or planned wellbore, the columns in the table can be rearranged by left clicking and dragging the column headers. Columns can be shown or hidden using the Show/Hide option in the Settings ribbon.

### 5.1.1 - Splitting and Separating the Viewing Area

The Viewing Area can be split to display multiple tabs at the same time. To do so, left click on the tab name and drag it towards the right or bottom edge of the viewing area, until the area is highlighted in blue. To remove the split, left click on the tab name and drag it towards the other tabs.

![Figure 3: Splitting the Viewing Area](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Ff5rtGGDW6V95xHm4zDWq%2F2.gif?alt=media)

Tabs in the Viewing Area can also be separated from the Well Seeker X interface into their own independent windows, allowing the user to move them to a separate monitor. To do so, left click on the tab name and drag it outside of the main Well Seeker X window. To undo the separation, left click on the tab name and drag it back to the Viewing Area the main window.

![Figure 4: Separating the Viewing Area into another window](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F51tgfkWnER6KZpbBI2SM%2F3.gif?alt=media)

## 5.2 - Object Explorer

The Object Explorer allows the user to navigate through and manipulate the data stored in their Well Seeker X database.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FCfGXciuT7xpHWB6vBTLm%2F4.png?alt=media" alt="Figure 5: Object Explorer" width="326">

The Well Seeker database is structured in a branching tree format, split into eight levels. Levels can be expanded and collapsed by clicking on the ‘+’ and ‘-‘ symbols at each level. Right clicking on a level will display a context menu with options available for that level. Double clicking on a survey, plan, actual wellbore or planned wellbore will open them in the Viewing Area.

For more details on the Object Explorer, see [**Section** **7.0 - Object Explorer**](/introduction/innova-engineering-manual/well-seeker-x-manual/7.0-object-explorer).

## 5.3 - Menu Ribbons

The menu ribbons are located at the top of the main user interface, and are where the user can access most of the Well Seeker X features.

![Figure 6: Well Seeker X menu ribbon](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FvwRJ6rcpLja5TQnSyPqa%2F5.png?alt=media)

The user can switch between ribbons by clicking on their names at the top of the interface. A detailed breakdown each ribbon and their features can be found in [**Section 8.0 - Menu Ribbons**](/introduction/innova-engineering-manual/well-seeker-x-manual/8.0-menu-ribbons)

Some features are only available depending on the item that you currently have selected in the Object Explorer, or are currently viewing in the Viewing Area. For example, chart features can only be used if the user is viewing a survey, plan, actual wellbore or planned wellbore in the Viewing Area. Additionally, the Chart Properties ribbon can only be opened if the user is viewing a chart in the Viewing Area.

The menu ribbons have some additional options, described in the chapters below.

### 5.3.1 - Search

The menu ribbons can be searched by typing in the Search box in the top right corner of the interface. Enter a key word and Well Seeker X will display associated ribbon menu options.

![Figure 7: Ribbon menu search](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLqiSzUPh4ZWGqVxDXhDB%2F6.png?alt=media)

### 5.3.2 - Simplified Mode

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 the ribbon and reduces the area it takes up in the interface.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FAPrWwonoevGvIzaNzCm7%2F7.png?alt=media" alt="Figure 8: Simplified Mode toggle and simplified menu ribbon" width="375">

## 5.4 - Quick Access Bar

The Quick Access Toolbar is located in the top left of the Well Seeker X interface, above the menu ribbons. It allows the user to pin their favourite menu ribbon options, so that they can be more easily accessed.

![Figure 9: Quick Access Toolbar](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FT6vcHW54aEZrnQ7EYNsA%2F8.png?alt=media)

To add an option to the Quick Access Toolbar, right click on it in the menu ribbon and select **Add to Quick Access Toolbar.**

![Figure 10: Adding to the Quick Access Toolbar](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F8s1wsv9aiFwpzLSKOtQ2%2F9.png?alt=media)

To remove an option from the Quick Access Toolbar, right click on it and select **Remove from Quick Access Toolbar.**

![Figure 11: Removing an option from the Quick Access Toolbar](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F08tR2wI56E8bSr3Nf6Rv%2F10.png?alt=media)

## 5.5 - Status Bar

The Well Seeker X status bar is located at the bottom of the main user interface. It provides the user with information on the programs current operation, such as the database location, current unit set and the status of data feeds like the Real Time Data Exchange and WITS. It also provides shortcuts to a number of functions.

![Figure 12 - Status bar location](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fr1ifHlH4I3I6eyV6EmyQ%2F11.png?alt=media)

The status bar contains the following items:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FpA9Z7klXxRLq6k8JdZ9v%2Fimage.png?alt=media&amp;token=52ccf7db-ba48-4cc9-948c-19ccb27c1225" alt=""><figcaption><p>Figure 13: Status bar items</p></figcaption></figure>

The function of each item is as follows:

**Status message:** Displays the current activity being performed by Well Seeker X.

**Select unit set:** Opens the Unit Sets dialog, allowing the user to switch between unit sets.

**Current unit set:** The unit set currently being used.

**Open database location:** Opens the folder location of the currently selected local database.

**Database location:** Displays the file path of the currently selected local database. If the user is logged into a remote server database, this will display “Remote Database – “ and the name of the database.

**Chart Image:** Exports the currently viewed chart as a jpg image. This option is only available if a chart is open in the Viewing Area.

**Open capture location:** Opens the folder where screen captures made in Well Seeker are saved. The screen capture file is always called **screenCapture.mp4**. Note that whenever a new screen capture is made, the old file is overwritten with the new recording.

**Start/Stop Screen Capture:** Click on this icon to begin recording a screen capture of your main computer monitor. This screen capture can be sent to Innova for technical support purposes. A red square around your screen indicates that it is being recorded, and a timer will appear on the status bar, and the Start/Stop Screen Capture icon will have a green indicator. Record yourself performing the activity that you are having technical issues with, and then click on the Start/Stop Screen Capture icon again to stop the recording. In Well Seeker X version 3.0.2.9 or later, the screen capture will record sound. Use the **Open capture location** icon to the left to find your newly created recording.

**Data Exchange:** Opens the Real Time Data Exchange dialog.

**Data Exchange status:** If the real time data exchange is running, this will display a countdown until the next data push up to the server. If the previous data push was successful, the Data Exchange icon will be green:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F3FA0PNmvaoBYA3GMnx2X%2F14.png?alt=media)

If the previous push failed, it will be red:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFNACIqKJVt9nZ9IOto5A%2F15.png?alt=media)

If the user performs a successful manual push, the icon will be green and the time of the push will be displayed:

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRdvbwYeDTLgfTxYUHCCg%2F16.png?alt=media)

If the user attempts a manual push and it fails, the icon will be red and the time of the failed push will be displayed.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FrXJPtVuiGjtYaZ57zMQD%2F17.png?alt=media)

If the data exchange is not active, the status will display “DX OFF”.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FzzRQswAUbS6iu5RVgKr7%2F18.png?alt=media)

**Import IPMs:** Imports the survey error model IPM files stored on your organisation’s remote server database. Note that this will overwrite the IPMs stored locally on your PC.

**IPM status:** When Well Seeker X starts, it contacts your organisation’s remote server database and checks if the IPM files on your PC match with the files on the server. If they do, the icon will be highlighted green and you will see the message “IPMS OK”.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FX0uOMwR86PacIJCyOC0a%2F19.png?alt=media)

If they do not match, the icon will be highlighted red and you will see the message "IPMS Out of date”. In this case, you may wish to click on the icon to download the IPMs from your organisation’s remote server database.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F7Q8wpdUEQ0bTAVZFy0gF%2F20.png?alt=media)

**Data Sync status:** If your organisation has data synchronisation enabled, you can view the status of the data sync connection here. If everything is working normally, the icon will be highlighted in green. If there are any issues, it will be red. Clicking on the data sync icon will toggle the data sync offline.

**WITS status:** If the user is running the WITS or WITSML reader, the status of the data feed can be seen here. If Well Seeker is successfully receiving data, the icon will be highlighted green. If there is an error, it will highlight red.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FNmH68PgEjOqbvMub8wO2%2Fimage.png?alt=media&amp;token=f54dc257-f6cc-431b-bbe8-7c1b12861d45" alt="" width="133"><figcaption></figcaption></figure>

**Notifications:** If any notifications for Well Seeker are available (e.g. a software update) the icon will display a number. Clicking on the notifications icon will toggle the display of the notifications panel, where any outstanding notifications can be viewed.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FC5SdfXxShUk0HUjg89Ch%2Fimage.png?alt=media&amp;token=cd9f9591-c084-4556-bd9f-e72a5c14bae9" alt=""><figcaption></figcaption></figure>

## 5.6 - Light & Dark Mode

The Well Seeker X interface can be toggled between light and dark themes by clicking on the **Style** dropdown in the top right corner of the main interface.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FmJRRiIrJs5YCY8F7fP4j%2Fimage.png?alt=media&amp;token=1286b196-5926-4ec0-82ce-ae6a65d2d204" alt=""><figcaption></figcaption></figure>

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F9SUOFEfpXk2I7VWiYk87%2Fimage.png?alt=media&amp;token=6f34c581-b694-46be-abb5-435c02e03813" alt=""><figcaption><p>Figure 14: Light/Dark Mode</p></figcaption></figure>


# 6.0 - Well Seeker X Database Structure

The Well Seeker X Database is divided in to 8 different levels. Many of these levels have their own properties associated with them. A new level can be created by right clicking on the level above it and choosing the **Insert New** option from the context menu. When a new level is created, it’s properties dialog will open automatically. To access the properties for an existing level, right click on it and select **Properties** from the context menu.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FRJaOHmTaIQ0YrNQIod2y%2Fimage.png?alt=media&amp;token=5b9e086a-07b2-4554-bc51-f8200801ae25" alt="" width="416"><figcaption><p>Figure 15: Well Seeker X Database Structure</p></figcaption></figure>

In Well Seeker X, all objects in the database tree (except for surveys) must have a unique name.

If your organization is running the Data Sync feature, any changes made to object names will be passed down to local users at the rig site. The procedure for this is as follows:

1. An administrator changes the name of an object on the organization’s remote server database. The original name and the new name are recorded in the background.
2. At the rig site, the user will be running Well Seeker on a local database. So long as the Data Sync feature is active and they have a working internet connection, Well Seeker will check for name changes every 6 minutes.
3. If the original object name exists in the local database, it will be automatically updated to the new name and the user will receive a notification confirming the name change.

Having object names match on both the server and the local database is a requirement for correct functioning of the [**Data Sync**](/introduction/technical-notes/well-seeker-pro-technical-notes/data-synchronization-feature-update) feature and the [**Real Time Data Exchange**](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/pages/BscELisQNqe1MsU1Q5dz#id-8.2.3.1-push-real-time-data-exchange)**.**

**Use the navigation tree on the left to view the page for level of the Well Seeker X database, or follow the links below:**

{% content-ref url="/pages/mj4WPPX5iNDvw81409z0" %}
[6.1 - Level 1: Well Seeker Database](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.1-level-1-well-seeker-database)
{% endcontent-ref %}

{% content-ref url="/pages/0c4fbeb4361e3ec4e4ad1388dd119264817f9856" %}
[6.2 - Level 2: Operator](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.2-level-2-operator)
{% endcontent-ref %}

{% content-ref url="/pages/iO8tiSTpShFpeu3NHQdh" %}
[6.3 - Level 3: Field](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.3-level-3-field)
{% endcontent-ref %}

{% content-ref url="/pages/wo5K27T9QF8zmDt7CwhC" %}
[6.4 - Level 4: Facility](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.4-level-4-facility)
{% endcontent-ref %}

{% content-ref url="/pages/aVv2dzau2Mwll11fAQSC" %}
[6.5 - Level 5: Well](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.5-level-5-well)
{% endcontent-ref %}

{% content-ref url="/pages/QskrWqWXgW7VqzCNaudf" %}
[6.6 - Level 6: Planned Well](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well)
{% endcontent-ref %}

{% content-ref url="/pages/oKc5uON0HNLStAUGNIhb" %}
[6.7 - Level 6: Actual Well](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.7-level-6-actual-well)
{% endcontent-ref %}

{% content-ref url="/pages/8K2L260sjvNuKIX6XSAh" %}
[6.8 - Level 7: Survey](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.8-level-7-survey)
{% endcontent-ref %}


# 6.1 - Level 1: Well Seeker Database

The Well Seeker X top level is simply the currently selected database file and has no properties associated with it. You can see the file path for the currently selected database in the Status Bar at the bottom of the main interface.

When first opened, Well Seeker X will load the default database **Well\_SeekerDB.mdb**, which is located in the user’s roaming directory. To access the user’s roaming folder, open the **Settings** ribbon and in the Setup File section, click on **Open**.

Multiple Well Seeker X databases can be created and can be named differently from the default. To create a new database, open the **Home** ribbon and in the Database section, click on **New**. Once created, the new database will not be automatically loaded. This must be done by returning to the Database section and clicking on **Open**. When Well Seeker X closes, it will store the file path of the last database it was accessing in the user’s setup file (**setupWS.ini**) and attempt to reconnect to it on start-up.

Ensure that the database is created in a directory which the user currently has write permissions to. The user will not be able to create a new database with Well Seeker X in the Program files directory, or directly to the C:\ root directory. Once created, a new database can be moved to the desired location using Windows Explorer. **Note:** It is strongly recommended that you do not store a Well Seeker database in a OneDrive folder, as this can cause erroneous behavior.

Should Well Seeker X fail to connect to the database specified in the **setupWS.ini** because the database has been deleted, or moved, or the database name has been changed, then the user will receive a warning and will be asked if they wish to manually select a database. The user can then browse the computer and select the relevant database they wish to access.


# 6.2 - Level 2: Operator

Operator represents a specific oil company or business unit and contains settings which will affect all levels and all fields and wells below it. The anti-collision rules for all wells under the operator are defined here.

![Figure 16: Operator Properties](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/rtnbOrDhPlegmqG8yLkB/Unknown%20image)

The Operator Properties dialog will automatically open when a new operator is created. To access the Operator Properties for an existing operator, right click on it in the Object Explorer. The Operator Properties dialog has the following features:

### **6.2.1 - Company Properties**

**Name:** This is the name of the operator and any change made here will be reflected in the Object Explorer.

**Contact:** A contact for the operator can be entered. This is for information purposes only.

**Address:** The address of the operator; this is for information purposes only.

**Primary Logo:** The logo is the default logo which can be displayed on reports. Click on the Select Logo button to choose an image from your device, or the Clear button to remove the selected image. Well Seeker X supports bmp, png and jpg formats. The logo file size must be less than 2 MB.

**Secondary Logo:** This is an additional Logo which can be added to plots and reports allowing the user to show their company logo as well as the clients.

**Set Password**: At every level in the database structure, the user has the option to lock the properties via a “**Locked**” checkbox at the bottom left of each dialog. When locked, the user is unable to edit any of the inputs at this level without the relevant password. This option opens the set password dialog, where the user can enter and where necessary change their chosen password.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/oAoXOYZ7T2wVf3dK2cE6/Unknown%20image" alt="Figure 17: Set Password Dialog" width="563">

**Locked**: This checkbox allows the user to lock all the editable cells in the dialog. If NO password has been entered in the set password section, then the user can freely select to lock and unlock the dialog. If a password has been added, then the user must enter the relevant password to both lock and unlock the dialog.

**Customer is a Directional Company:** The user can check this box to mark the operator as a directional company. This is just for reference and has no other function in the software.

### **6.2.2 - Anti-Collision Settings**

The Anti-Collision Settings section allows the user to define the rules for generating ellipse of uncertainty and calculating anti-collision results for the operator. These rules will apply to all wells contained under the currently selected operator.

**Scan Method**: This is the anti-collision scan method used for all proximity scans. Well Seeker X currently supports three options:

* **3D Closest Approach**: Finds the closest approach of the offset well in 3D space. To visually represent the scan, imagine an ever-expanding sphere with its origin at the point of interest on the **reference** well. The point on the offset well which first touches the sphere is the point of closest approach. A 3D scan will always find the point of closest approach regardless of which direction the offset well is coming from.
* **Travelling cylinder North / High side:** The scan describes a circular plane perpendicular to the wellbore. To visualize, imagine a 2D disc with its origin at the point of interest on the **reference** well with its axis perpendicular to the well bore. The point at which the offset well intersects the disc is the point of closest approach. Travelling cylinder scans can miss or be very late to detect offset wells which approach near perpendicular to the reference. This scan should be used with caution or when backed up by an accompanying 3D closest approach scan. The difference between the North / High side scans is simply the reference angle used when determining the direction of the offset well. High side references the offset well to the high side of the current well bore, this can lead to confusing outputs as at low inclinations the high side of the wellbore can swing dramatically between survey points. North referenced travelling cylinder scans use North (True or Grid, whichever is selected at Field Level) as the reference where the high side angle is calculated and the current wellbore azimuth is added.
* **Horizontal Scan:** Finds the point of closest approach of the offset well by scanning horizontally on the reference wells current TVD. This scanning method is rarely used as it can miss potential collisions.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OfPpfJ831zeTZECmJjWb/Unknown%20image" alt="Figure 18: AC Scan methods" width="563">

**Error Surface:** This describes the error surface used to calculate separation or clearance factors in Well Seeker X. It currently supports three methods:

* **Circular Conic:** Uses the ellipse semi major axis as the error radius regardless of which direction the wells are approaching from. This can lead to very pessimistic AC results.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/9qHjNi5QNAZCHSXII0iy/Unknown%20image" alt="Figure 19: Circular Conic Error Surface" width="563">

* **Pedal Curve:** This method describes the errors as an ellipse (elliptical conic); however, it uses the **pedal radius** in separation factor calculations. This is the radius of the ellipse perpendicular to the line of closest approach.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/xCT1vKWOmGWPYOYK0YZI/Unknown%20image" alt="Figure 20: Elliptical Conic Error Surface" width="563">

* **Combined Covariance:** This method uses the same error radius as elliptical conic; however, the total error radius is calculated by root sum squaring (RSS) the two radii. This method should be used only with errors at 2.79 Sigma and above.
* **Ellipsoid Scalar Expansion:** This method describes errors as a 3D ellipsoid. The reference and offset ellipsoids are then expanded using the same scale factor until they come into contact. The scale factor required to achieve this is the separation factor. Ellipsoids that are already touching before scalar expansion have a SF of 1. Ellipsoids that overlap before scalar expansion have a SF of <1. This method requires greater CPU power than the other methods.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/iaEVFPNzld8uMfHQDRFV/Unknown%20image" alt="Figure 21: Ellipsoid Scalar Expansion. Original errors are dark, expanded errors are light" width="563">

**Warning Type:** This defines the type of warnings which Well Seeker X will flag on the anti-collision report and it has two settings:

* **Error Ratio:** This is also known as “**Clearance factor**” or “**Separation Factor**”. It is calculated by dividing the centre to centre distance by the summed radius of the EOU. The error surface defines the total error radius. Well Seeker uses the **Pedal Curve Method** when calculating the reference and offset error radius values.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGERSooW4HoMa9klLguFh%2Fimage.png?alt=media&amp;token=219e7226-e19d-4a14-81bd-63a950532932" alt=""><figcaption></figcaption></figure>

![Figure 23: Error Ratio Warnings Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/oh0EfPI9NgTpcWZiWABC/Unknown%20image)

* **Rules Based:** This allows the user to define an Anti-collision rule which can be either an Error ratio or a depth ratio. In the **Type** column the user can select from the following options:
  * **Error ratio:** This is just a normal separation factor-based rule and works in the same way as the Error Ratio option above. Note the user does not need to enter anything in the Max Radius cell for this rule.
  * **Depth ratio:** This option takes the current measured depth and multiplies it by the ratio. This value is then the C-C distance warning limit at that given depth. If the C-C distance at this depth is less than this value Well Seeker will flag this with a warning. The user can set the max radius to limit this; however, the user does not need to enter a maximum radius for the rule to work. For example, if the depth ratio was set at 0.1 at a measured depth of 100m, the rule would be a minimum C2C of 10m. Anything less than this would be flagged.
  * **Min C-C Distance:** This option lets the user select a radius, which acts as the C-C distance warning limit along the entire well and if you end up with a C-C distance less than the radius entered, you will get a warning. This differs from the above since the radius is fixed and does not change based on depth. Note the user does not need to enter anything in the Ratio cell for this rule.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F610uhgLU8ieiVkpfp4dD%2Fimage.png?alt=media&amp;token=58abb02a-7c53-4f36-afbe-174605faa66c" alt=""><figcaption><p>Figure 23: Rules Based Warnings Dialog</p></figcaption></figure>

It is possible to combine these AC rules. This allows the user to include multiple warnings when running the AC calculations. For example, the user could have the standard error ratio warnings selected at the same time as the minimum centre to centre. In the above, if the warnings on lines 1-4 were selected, this will flag the various levels for SF and also flag any point with a C-C of less than 5m/ft (whatever the selected units are)

The warning types are defined in the warning type grid and can be named however the user desires and there can be an unlimited number of rules which can be evaluated. The warning grid will change depending on whether rules based, or error ratio is selected.

**Errors Evaluated @ Sigma:** Sets the number of standard deviations used when calculating separation factor. Separation factor in anti-collision reports and the real time AC will be displayed to this sigma value. Default value is 2.

All other survey error outputs use the **Errors Output @ Sigma** setting below.

**Errors output @ Sigma:** Sets the number of standard deviations used for calculating all survey error outputs EXCEPT for separation factor. Ellipse semi-major and semi-minor values for error ellipse reports, anti-collision reports, real time AC and plots will be displayed to this sigma value. Default value is 2.

For separation factor calculations, the software uses the above **Errors Evaluated @ Sigma** setting.

Increasing the sigma value increases the size of error ellipses, but also increases the probability that the wellbore is inside the error ellipse. The below table represents the confidence levels for one, two- and three-dimensional Gaussian distribution with equal standard deviations in all directions.

![Figure 25: Confidence Level Table](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/HsJxuZ5PcQlOyfNHJjpk/Unknown%20image)

When using the **Pedal Curve** **method** (as is used within Well Seeker), the probability of collision is effectively broken down into a **one-dimensional** problem, therefore at 1 sigma there is a 68% chance that the well path will reside inside the EOU and this increases to 95% at 2 sigma. This value also determines at what sigma level the error ellipse sizes are displayed on the error ellipse report. The below picture shows a visual representation of the pedal curve around an ellipse of uncertainty.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/fkuwHVlLFJwBAGFs5DFV/Unknown%20image" alt="Figure 26: Pedal Curve" width="563">

**Casing:** This option allows the user to decide if the casing radius is to be considered in the anti-collision calculation.

**Include Casings:** If “**yes**” is selected in the casing option, this option defines how the casing radius is used in the separation factor calculation.

If “**Add**” is selected, the radius is added to the error radius and survey bias.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FGkxtJdCwk2AKTPM3ce27%2Fimage.png?alt=media&amp;token=30e4ac58-bf55-4e56-a095-f2a2ba0510c5" alt=""><figcaption></figcaption></figure>

If “**subtract**” is selected, the casing radius is subtracted from the centre to centre distance.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDbTAvLfCpOJV0PW05E9W%2Fimage.png?alt=media&amp;token=ca963b05-88e9-43d3-a39a-ddba130dfb19" alt=""><figcaption></figcaption></figure>

It should be noted for top hole sections where the centre to centre distances are small, this option can give a negative centre to centre distance.

**Errors Calculated From:** This option allows the user to define where the EOU calculation starts from. For land wells and jack-ups, “surface” is usually selected. However, for deep water wells, “mudline” is usually selected.

**TC Plot Safety Factor**: This option allows the user to apply a safety factor to the errors which are generated in the travelling cylinder plot. With a value of one entered here (default), the ellipses will generate as per normal i.e. no safety factor applied, which means touching the No-Go line on the plot effectively equates to a SF of 1. If the user enters a value of for example 1.2 here, the ellipses displayed on the TC plot will be 20% larger, 1.5 will be 50% larger etc, giving the safety factor required. **Note**: This value cannot be anything less than 1

**Warnings Grid:** This allows the user to define the warning rules which will be displayed on anti-collision reports. If “Error Ratio” is selected as the warning type, the grid will display “Name” and “Ratio” Columns. The name will be displayed on an anti-collision report if the separation factor is less than or equal to the value in the “Ratio” column. If “Rules Based” is selected as the warning type, the grid will have the additional columns “Type”, “Max Radius” and “Active”. The type column specifies if the value entered in the “Ratio” column is a clearance factor or a depth ratio. The “Max Radius” Column only applies to depth ratios and specifies the maximum radius to be added to the total error radius. The “Active” column specifies if the rule will be evaluated or not.

### **6.2.3 - WPTS Separation Rule**

**WPTS Separation Rule:** Toggling on the **Use WPTS Separation Rule**option on instructs the software to use the WPTS Separation Rule to calculate the separation factor value when running anti-collision. It also allows the user to set the value for the two additional parameters used in the calculation – the surface margin and project ahead uncertainty.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/HXORsNAoGozEIylhFkzw/Unknown%20image" alt=""><figcaption><p><strong>Figure 27: WPTS Separation Rule</strong></p></figcaption></figure>

**Surface Margin:** The surface margin term increases the effective radius of the offset well and accommodates for small, unidentified errors. It also defines the minimum acceptable slot separation during facility design and ensures that the separation rule will prohibit the activity before nominal contact between the reference and offset wells, even if the position uncertainty is zero. Default value is 0.3m or 0.984ft.

**Projection Ahead Uncertainty:** Quantifies the 1 standard deviation uncertainty in the projection ahead of the current survey station. The size of this value represents uncertainties such as directional sensor to bit distance, survey interval, angular control from the BHA, drilling experience in the current formation and the operator’s general attitude towards risk. Default value is 0.5m or 1.64ft

### **6.2.4 - Alert Separation**

Allows the user to set a minimum allowable separation distance (MASD) for wells under the selected operator. When creating an anti-collision report or using the Real Time Anti-Collision tool, if the centre-to-centre distance between the reference well and an offset drops below the MASD, the user will receive a warning.

![Figure 28: Alert Separation](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/yJVW8RbcxQbDhaSC8Jpo/Unknown%20image)

**Minimum Separation:** The minimum allowable centre-to-centre distance between the reference well and an offset.

**Plus Cone Of Expansion / 1000:** The minimum allowable distance will increase, every 1000 units of Measured Depth, by the value entered here. The minimum value is 5.

The formula for the minimum allowable separation distance is as follows:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFBLrifpsYU3c8jyTZmB0%2Fimage.png?alt=media&amp;token=c0fc6c73-1991-467e-8044-d51a7c6bd528" alt="" width="563"><figcaption></figcaption></figure>


# 6.3 - Level 3: Field

The field level represents a specific oil or gas field on which the operator can have any number of facilities. Fields define the mapping grid (aka Co-ordinate Reference System) to be used when calculating geographic coordinates.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FZACEX3q5d0K6yQDwZG3d%2Fimage.png?alt=media&amp;token=5be4424b-17ac-4351-bf38-9843b2dbcc3d" alt=""><figcaption><p>Figure 28: Field Level properties</p></figcaption></figure>

The Field Properties dialog will automatically open when a new field is created. To access the Field Properties for an existing field, right click on it in the Object Explorer. The Field Properties dialog has the following features:

### 6.3.1 - Properties

**Field Name:** Name of the field which will be displayed in the Object Explorer.

**Mapping Grid:** The dropdown box sets the co-ordinate reference system (CRS) which will be used to convert between grid co-ordinates, local co-ordinates and latitude/longitude values. Clicking on the **mapping grid** button will open the **CRS Editor**. See [**section 8.3.2.2 – Co-ordinate Reference System (CRS) Editor.**](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/pages/52c4f638fd9a9b3afde1069a80f1d53ff2a3dd9a#id-8.3.2.2-co-ordinate-reference-system-crs-editor)

**Locked:** This checkbox allows the user to lock all the editable cells in the dialog. If NO password has been entered at Operator level in the set password section, then the user can freely select to lock and unlock the dialog. If a password has been added at Operator level, then the user must enter the relevant password to both lock and unlock the dialog.

### 6.3.2 - Field Local Grid

**Local Coordinate System:** This defines the reference point for the well location, and is used to calculate the local NS and EW values when viewing surveys or plans. If **Well Centred** is selected, the reference point will be the well head, as defined in the Well Properties dialog. This will mean that the NS and EW will be zero at surface. If **Facility Centred** is selected, the reference point will be the facility centre location, as defined in the Facility Properties dialog. This option is commonly used for facilities with multiple slots.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F06OgCqD67rEweswYlVRm%2Fimage.png?alt=media&amp;token=ae2ed94b-b560-4d68-a783-4f4a7b879146" alt="" width="374"><figcaption><p>Figure 29: Local Co-ordinate reference</p></figcaption></figure>

**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. 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. If unchecked (default) then these coordinates will not appear in the field data box in the reports.

### 6.3.3 - Field Reference Point

**Field reference point:** This is the reference location used for the field. The reference point can be entered either as a latitude & longitude or as a map coordinate. This is defined by selecting the “Grid North / East” or “Lat / Long” radio button. The grid convergence for the field reference point is displayed in the edit box marked “Grid Convergence”. This value will be applied when converting between grid north and true north.

### 6.3.4 - System Vertical Datum

**System vertical datum:** This is datum which all TVDs stored in the database 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.


# 6.4 - Level 4: Facility

A facility represents a central location under which a number of wells will be grouped, such as an onshore pad or offshore platform.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FxjtYzfdOMprONjI3fxjm%2Fimage.png?alt=media&amp;token=d18c4325-d76b-4acb-88cc-a0976869ad38" alt=""><figcaption><p align="center">Figure 30: Facility Properties</p></figcaption></figure>

The Facility Properties dialog will automatically open when a new facility is created. To access the Facility Properties for an existing facility, right click on it in the Object Explorer. The Facility Properties dialog has the following features:

### 6.4.1 - Properties

**Name:** The name of the facility which will be displayed in the Object Explorer.

**Azimuth North Reference:** Either true north or grid north can be used as the azimuth reference. It is assumed that the azimuths entered into survey grids will be referenced to the option selected here.

**Local Coordinate Reference:** This defines the reference point for the well location, and is selected in the Field Properties dialog.

**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. When either on or off is selected, the user should then select apply. If there are a lot of lease lines and / or a lot of plans and surveys, then it may take a moment for Well Seeker to process this selection.

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

**Templates:** Opens the Template Editor.

**Locked:** This checkbox allows the user to lock all the editable cells in the dialog. If NO password has been entered at Operator level in the set password section, then the user can freely select to lock and unlock the dialog. If a password has been added at Operator level, then the user must enter the relevant password to both lock and unlock the dialog.

### 6.4.2 - Template Editor

Clicking the templates button gives the user access to the Template Editor dialog. A template represents a number of surface locations, which the user can select from at Well Level. Templates are usually used for offshore platforms or subsea wells.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F4jihdj3Tgyv5LtlIrcBb%2Fimage.png?alt=media&amp;token=c831576d-214f-4385-b170-ecf2f5e16faf" alt=""><figcaption><p>Figure 31: Rectangular Template</p></figcaption></figure>

Click on **Create** New to create a new template, and enter the template name in the **Name** field. Enter a prefix in the **Slot Prefix** field, which will be applied to individual slot names. Save your changes at any time by clicking on the Apply button.

A facility can have more than one template associated. Previously created templates can be selected from the **“Select template”** combo box.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTD7yXpyvqODG6BHf553Q%2Fimage.png?alt=media&amp;token=c1422638-53bd-4814-96c2-201980f603f7" alt=""><figcaption><p align="center">Figure 32: Template properties</p></figcaption></figure>

The current template will be deleted by clicking the **Delete** button. Templates cannot be deleted if one or more slots are in use by the well level.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcubBFx9GzedqgS2pFkZF%2Fimage.png?alt=media&amp;token=5d9d4c5f-b10a-4e9c-a3cb-8b62266b2775" alt="" width="203"><figcaption><p align="center">Figure 33: Template Centre</p></figcaption></figure>

The centre of the template describes the offset of the centre of the template to the facility reference point in terms of North / South and East / West co-ordinates.

The template geometry is defined by selecting the appropriate radio button in the geometry section.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F2xVOXm5kFKsBrQX5Zc4s%2Fimage.png?alt=media&amp;token=6342b674-89f4-440f-8155-4f884e97d61c" alt="" width="242"><figcaption><p align="center">Figure 34: Template geometry</p></figcaption></figure>

Rectangular templates are defined by parameters in the rectangle section of the dialog.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fg09eiEJYd6lwfhDOnI3S%2Fimage.png?alt=media&amp;token=15c88cc8-99a6-4dbb-85cf-9c28b1f640fd" alt="" width="298"><figcaption><p align="center">Figure 35: Rectangular templates</p></figcaption></figure>

The offset from the template centre is defined by the first two edit boxes and this represents the offset from the centre point defined in the template centre section. The number of rows and columns are defined in the “Rows” and “Columns” edit box and the clockwise rotation of the template is defined in the rotation section. The X and Y spacing is defined by the X and Y spacing boxes and the slot numbering can be specified from the drop-down menu.

Circular templates can be defined by the parameters in the Circle section.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fv5Hf5HsiWelYpSr6OcXU%2Fimage.png?alt=media&amp;token=5f3bc7b4-13fc-4985-a015-1cc970e901a5" alt="" width="227"><figcaption><p align="center">Figure 36: Circular template geometry</p></figcaption></figure>

If single slots are selected from the geometry section, then the slot locations and names are entered in the grid at the bottom of the dialog.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FFywKYglPvVGHnK0KuFKd%2Fimage.png?alt=media&amp;token=082ef148-c9c7-462a-9373-a3670cf90647" alt="" width="432"><figcaption><p align="center">Figure 37: Slot locations</p></figcaption></figure>

If rectangular or circle geometries are selected, the slots can be converted to single slots by clicking the **convert to single slot** button. It should be noted that this operation is not reversible.

### 6.4.3 - Facility Reference Point

**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. The reference point can be entered either as a latitude & longitude or as a map coordinate. This is defined by selecting the “Grid North / East” or “Lat / Long” radio button. The grid convergence for the facility reference point is displayed in the edit box marked “Grid Convergence”. This value will be applied when converting between grid north and true north.

### 6.4.4 - Facility Location Uncertainty

**Facility Location Uncertainty:** The horizontal and vertical uncertainty of the facility entered at 1 sigma. This value is used for EOU calculations.

### 6.4.5 - Rig Directions

**Rig Directions:** Provides a space where the user can leave a note on the location of the rig.

***

&#x20;\[DH1]Help


# 6.5 - Level 5: Well

Well level in the object explorer defines the properties of the surface location of a single wellhead.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FX6HfM2YjDz8Irg14bAs3%2Fimage.png?alt=media&amp;token=75d1f22b-0e40-48e7-9134-c6ff98b86508" alt=""><figcaption><p align="center">Figure 38: Well Properties</p></figcaption></figure>

The Well Properties dialog will automatically open when a new well is created. To access the Well Properties for an existing well, right click on it in the Object Explorer. The Well Properties dialog has the below features:

### 6.5.1 - Properties

**Name:** The name displayed in the Object Explorer.

**Description:** A description of the well, used only for information.

**Location Uncertainty:** The vertical and horizontal location uncertainty of the well head entered at 1 sigma. This location uncertainty will be added to the starting error ellipse when running an anti-collision scan.

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

**Locked:** This checkbox allows the user to lock all the editable cells in the dialog. If NO password has been entered at Operator level in the set password section, then the user can freely select to lock and unlock the dialog. If a password has been added at Operator level, then the user must enter the relevant password to both lock and unlock the dialog.

### 6.5.2 - Wellhead Location

Describes the surface location of the well. The user as four options:

* **Slot:** If a template has been created at facility level, the well head location can be assigned to a slot from the template. Select the slot from the drop-down list. If the slot is moved the well will move along with it.
* **Offset from facility:** The well head location is defined by an offset from the facility reference point. This is specified in local north/south and east/west coordinates.
* **Map:** The map coordinates of the well head expressed in northings and eastings.
* **Geographic:** The latitude and longitude of the well head.

Note that when a value is entered for one option, the values for the other options will be calculated.

**Grid Convergence:** The grid convergence at the well head location.

**Scale Factor:** The scale factor of the CRS selected at field level.

### 6.5.3 - Depth Reference

The depth reference grid allows the user to enter the elevation and details of multiple depth references which have been used. A depth reference usually represents the rotary table elevation of a drilling rig, and if multiple rigs have been used to drill the well, they can be entered here. Entering the details for one depth reference will create a new row underneath it, so that a new one can be entered.

**Datum Name:** The name which will be displayed on reports and when selecting the depth datum at actual well or plan level.

**Elevation above system:** The elevation above the system vertical datum of the depth reference – unless this has been changed in the Field Properties, this will be Mean Sea Level.

**Rig:** Optionally enter a rig name as a reference. This is not used anywhere else.

**Default:** Marking a depth reference as the defaults means that it will be automatically assigned to any new actual wells or plans created under this well.

Once the elevation is entered the specifics of the datum can be entered in the section to the right of the grid.&#x20;

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F24Ssf52GpkDwN1wUFgjk%2Fimage.png?alt=media&amp;token=8338bd4e-2b8a-4214-a49f-fc06d04d8c86" alt=""><figcaption><p align="center">Figure 39: Depth Datum details</p></figcaption></figure>

If the datum is for an offshore rig, the first edit box will be the water depth. If the well is onshore, the edit box will represent the elevation of ground level above MSL.

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.


# 6.6 - Level 6: Planned Well

When the user right-clicks at Well level, they will be given the choice to insert a **planned well** or **actual well** below it. A planned well is a well trajectory that is constructed using planning tools, as opposed to an actual well, which is constructed using recorded surveys. Whenever a planned well is created, a planned wellbore is automatically created on the level below it.

The planned well level is made up of three components - the Plan Properties, Planning Tools and the Planned Wellbore. **Use the navigation tree on the left to view the page for each component, or follow the links below:**

* [**Plan Properties**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well/6.6.1-plan-properties) **-** Where the user defines configures various properties of the plan.
* [**Planning Tools**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well/6.6.2-planning-tools) **-** Where the user creates their plan points using Well Seeker X's suite of planning tools.
* [**Planned Wellbore**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well/6.6.3-planned-wellbore) **-** An interpolated listing of the plan.


# 6.6.1 - Plan Properties

The Plan Properties dialog will automatically open when a new plan is created. To access the Plan Properties for an existing well, right click on it in the Object Explorer.

The Plan Properties dialog has the below features:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FLInZgEeBESi8Am9CsaAY%2Fimage.png?alt=media&amp;token=f48644a8-3a9c-423c-82b3-0de4afdc372e" alt=""><figcaption><p>Figure 40: Planned Well Properties</p></figcaption></figure>

### **6.6.1.1 - Properties**

**Name:** The name displayed in the Object Explorer.

**Description:** A description of the plan used only for information purposes.

**Set as principal:** If this option is selected, a red box will appear around the plan icon in the database viewer. Only one principal plan per well can be selected per well. This plan will be used in the distance to calculations in the survey view.

**Complete:** If this option is selected, this plan will not be available to select in the Offset Selector. Use this option to hide drilled/completed wells to reduce clutter when selecting offsets in future wells.

**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 Chart Defaults ribbon.

**Survey Tools:** Clicking on this button will open the Survey Tool Editor. If the user selects a row in the survey program by clicking on its row number and then clicks on Survey Tools, they can use the ‘select IPM’ button in the Survey Tool Editor to choose an IPM for that row.

**Force Colour:** Located in the bottom-right of the dialog, toggling this option on will force this plan to always use the selected colour when displayed on charts. This supersedes any colour options for this plan in the ‘Chart Properties’ dialog.

**Locked:** This checkbox allows the user to lock all the editable cells in the dialog. If NO password has been entered at Operator level in the set password section, then the user can freely select to lock and unlock the dialog. If a password has been added at Operator level, then the user must enter the relevant password to both lock and unlock the dialog.

### **6.6.1.2 - Vertical Section**

Details of the vertical section (used for section plots and vertical section calculations) are entered here. The VS azimuth and the origin point must be entered in order to correctly calculate vertical section. When Bottom Hole Location is selected, the program will draw a straight line from the VS origin point to the last planned point and the azimuth of this line will be used as the vertical section. It is important to note that if this is selected, the vertical section will change every time a new survey is added.

### **6.6.1.3 - Depth Reference**

A list of depth references available to the well can be selected from the drop-down menu. The available depth references are defined in the Well Properties, one level up. If the depth datum is changed and there are currently surveys entered, a dialog will appear asking if you wish to change the TVDs or preserve them. If the user chooses to **Change TVDs**, the TVD values of the surveys will be changed in order to preserve the TVD Subsea values. If the user chooses to **Preserve TVDs**, the TVD Subsea values will change in order to preserve the TVD.

**Note:** Changing a depth datum with surveys already entered can seriously corrupt your data and a backup should be made prior to this.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTIyss7QAA46y1P3AqsGr%2Fimage.png?alt=media&amp;token=766d5468-13ac-4bc8-ba07-c436e3bcacef" alt=""><figcaption><p align="center">Figure 41: Changing the depth reference</p></figcaption></figure>

### **6.6.1.4 - Magnetics**

The magnetics grid allows the user to calculate geomagnetic data for the well location using any of the models available in the Well Seeker X magnetics directory. The geomagnetic data marked as Active will be used whenever ellipse of uncertainty need to calculated for the plan.

**Date:** The date used to calculate the geomagnetic data. This input is required if the user is using any model other than User Defined.

**Model:** Select the desired geomagnetic model from the dropdown box. By default, the IGRF and WMM models will be available. If your organisation has purchased the BGGM or HDGM models, contact Innova support (<support@innova-drilling.com>) for instructions on how to integrate them into Well Seeker X. The user my also select User Defined, allowing them to manually enter the declination, dip and total field values.

**Declination, Dip, Total Field:** These values will be automatically calculated using the selected model, date entered into the Date field, and the surface location of the plan. If User Defined was selected as the model, these values can be manually entered.

**Active:** Only one row can be marked as active at a time. The active row is the one used to ellipse of uncertainty for the plan.

**Export Geomag Data:** Located to the bottom-right of the Magnetics grid, this option exports the geomagnetic data as a document. Select the line in the ‘Magnetics’ section that you want to export the geomagnetic data for. Then select the report format as ‘PDF’ or ‘Excel’ from the drop down menu, before selecting ‘Export’ to generate the report.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F06YVp3qwUmNNGw0ut7FV%2Fimage.png?alt=media&amp;token=bdbaadf2-de18-4736-a446-808669d17dd1" alt=""><figcaption><p align="center">Figure 42: Magnetics</p></figcaption></figure>

### **6.6.1.5 - Survey Program**

The survey program specifies how the planned wellbore is constructed and which IPMS’s will be used to generate error ellipses.

Normally the survey program is constructed automatically when the user saves their plan in the Plan View. However, the user may need to manually reconstruct the plan to resolve and error, or split it into sections that use different survey tools.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcjzyCrTHSNnxLKZEcpD9%2Fimage.png?alt=media&amp;token=f27462e5-efbe-4123-928e-9647cbf533f4" alt=""><figcaption><p align="center">Figure 43: Survey Program</p></figcaption></figure>

Rows in the survey program can be deleted by clicking on their row number and then pressing the delete key on your keyboard. In a new row, start by selecting the plan from the dropdown box in the **Survey** column. The **Depth From** and **Depth To** columns will populate down to the deepest point on the plan. If the plan is split into multiple rows, these can be edited to define the depth range of each row.

Lastly, the survey tool for each section of the plan should be selected from the dropdown in the **IPM** column. If the select survey tool is highlighted in red, it means that the required IPM file is missing on your PC. The Survey Tool Editor can be opened by clicking on the **Survey Tools** button at the top-right corner of the dialog.

If the plan is a sidetrack of another well or plan, the survey program from the motherbore will be included in the survey program, down to the tie-on point. These rows will be greyed out and un-editable.

&#x20;

### **6.6.1.6 - Tie-On / Sidetrack Details**

The plan can be turned into a sidetrack of another well or plan using the options in this section. Follow the process below to turn the plan into a sidetrack. A more detailed explanation can be found on [**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)

1. Click on **Plan is tied to**, to activate the other features.
2. Use the **Parent Well / Plan** to select the motherbore that this plan will be tied to. Only actual wells and plans under the same well will be available.
3. Enter the tie-on/kick off depth of the sidetrack in the **Tie On/ST Depth** box. This is referenced to the depth reference of this plan, not the parent well.
4. Choose an option from the **Errors Start** dropdown. This sets where anti-collision ellipses begin when running anti-collision between the sidetrack plan and it's mother bore. If **ST Point** is selected, the error ellipses for both will start at the sidetrack kick-off point, with an initial magnitude of zero. If **Surface** is selected, the error ellipses will start at surface as normal. If the plan was imported from a Compass EDM file, this option will match the choice in the EDM file. Otherwise, it will default to ST Point. Note that this only applies to anti-collision run between the mother bore and the sidetrack. For anti-collision scans against any other well or plan, the errors will start from surface.
5. Click on the **Create Tie-On/ST** button. This will update the survey program with all the surveys up to the side track point from the parent well. It should be noted that all previous survey program lines will be deleted.
   1. Annotations, Casings, and Formations will be copied from the motherbore into the sidetrack. Duplicate entries will be identified based on MD and will be cleaned up. Only entries above the sidetrack point will be copied. The same behaviour applies when creating a Sidetrack using the options in the context menu.

### **6.6.1.7 - Tie-On**

**Tie-On:** This section specifies where the plan will tie on to:

* **Surface:** The plan will tie on to the well head location
* **User defined:** The user can enter the MD INC AZI NS EW and TVD the plan will be tied on to.
* **From survey / plan:** This option is only available if the plan is a side track, select the survey file of plan to tie on to and type the MD which you wish to use. The INC AZI NS EW and TVD will be interpolated from the survey or plan selected.

### **6.6.1.8 - Depleted Zone**

This section allows the user to set up a depleted zone for the plan, which can then be displayed on the 3D Chart. The depleted zone is elliptical; the **Up** and **Down** entries define the radius of the ellipse above and below the wellbore. The **Width** entry defines the radius of the ellipse to both the left and the right of the wellbore. The **Start** and **End** fields set the measured depth where the depleted zone starts and ends. The **Rotation** entry can be used to change the orientation of the ellipse. And lastly, the **Shape** dropdown can be used to choose to display the depleted zone as an Ellipse or a Rectangle.


# 6.6.2 - Planning Tools

The plan view gives the user access to the Well Seeker X’s powerful array of well planning tools. It can be accessed by **double left-clicking** on the plan in the Object Explorer.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F6pJtUHKlbEtdIuykpoUI%2Fimage.png?alt=media&amp;token=e929d86f-14d9-4b45-8e44-a579d6cf8ed4" alt=""><figcaption><p align="center">Figure 44: Plan View</p></figcaption></figure>

The planning tools are displayed at the bottom of the plan view and are accessed by clicking on the various radio buttons and edit boxes provided. Once the details for a planning method are entered, the **calculate** button should be pressed to add it to the grid.

MD INC and AZI can be entered into the grid directly if desired and this will be assumed to be an **ADJ MD** method. Once a planning method has been used, a solid blue line is displayed under the last line of the method and the parameters used to generate it have the parameters editable in white cells. All other cells are greyed out. Changing one of the planning method cells will force the plan line and all lines below it to recalculate. A line can be deleted by left clicking on it’s row number and pressing delete on your keyboard. Deleting a single line of a planning method will result in all lines for the method being deleted.

Saving the plan will force the planned wellbore to be re-calculated. The planned wellbore is interpolated at the currently selected dogleg parameter, defined in the unit set.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKohq40KlkJSx3i2ss2fV%2Fimage.png?alt=media&amp;token=585df048-bb1b-4bb0-9104-f2f90f7f2f71" alt=""><figcaption><p align="center">Figure 45: Directional Planning Tools</p></figcaption></figure>

The above planning tools are only available when in a plan. If the user accesses the planned wellbore, the grid is not editable and the planning tools will not be displayed.

## **6.6.2.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.

## **6.6.2.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.

## **6.6.2.3 - Dogleg Toolface**

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.

## **6.6.2.4 - Hold**

**CL:** Enter a CL 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

## **6.6.2.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 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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FtunKEm6FaORIkQPHxZ4M%2Fimage.png?alt=media&amp;token=b4ddfcd8-9d66-4124-b7eb-486e0db315f2" alt=""><figcaption><p align="center">Figure 46: Thread Target Dialog</p></figcaption></figure>

## **6.6.2.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.

### **6.6.2.7 - S-Well**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FsUvamwPYxC2jQ2AGHXOA%2Fimage.png?alt=media&amp;token=d2a9b3ba-8602-46e4-a2b4-091c7c196330" alt="" width="563"><figcaption><p align="center">Figure 47: S-Well</p></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FN2GwrjmmX9BboZR7cquQ%2Fimage.png?alt=media&amp;token=ea597c03-869d-4370-bbec-38269c7d3af7" alt=""><figcaption><p align="center">Figure 48: S-Well Planning Tools</p></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F5oNF7kciom7Vkx7LNmOB%2Fimage.png?alt=media&amp;token=646e4647-2506-427f-948e-6a2ab8b58dc6" alt=""><figcaption><p align="center">Figure 49: SWELL_OPT1</p></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1jLQoEIoWexSXwdNyT0S%2Fimage.png?alt=media&amp;token=dd165641-f6dd-44e9-b21f-2383164e7766" alt=""><figcaption><p align="center">Figure 50: SWELL_OPT2</p></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FdDeXjqkjQuMKB2cOQt3o%2Fimage.png?alt=media&amp;token=9753effb-2db7-48d0-b3e4-c8a9a270dc4a" alt=""><figcaption><p align="center">Figure 51: SWELL_OPT3</p></figcaption></figure>

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

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FcTIhRbhNV0XaBtdMxYz1%2Fimage.png?alt=media&amp;token=86292791-9e28-44e4-a484-7fb25afe5b55" alt=""><figcaption><p align="center">Figure 52: SWELL_OPT4</p></figcaption></figure>

### **6.6.2.8 - Slant Well**

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FbuXM2IFCobN73K1mOe3i%2Fimage.png?alt=media&amp;token=9bb6b14c-4196-4fc8-a6c9-252801655cd1" alt="" width="563"><figcaption><p align="center">Figure 53: Slant Well</p></figcaption></figure>

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.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fb09bToSK8nVmJoxHtpCp%2Fimage.png?alt=media&amp;token=b9c5fb7b-8de8-4d52-97d6-50bc862d96e6" alt=""><figcaption><p align="center">Figure 54: Slant-Well Planning Tools</p></figcaption></figure>


# 6.6.3 - Planned Wellbore

Whenever a planned well is created, a planned wellbore is automatically created below it. It can be viewed by **double left-clicking** on the item one level below the plan, which will always have the suffix ‘planned wellbore’.

The planned wellbore represents the planned well path from surface and is an interpolated listing of the plan. It is constructed using the plan created in the Plan View, using the planning tools, and the survey program in the Plan Properties.

The planned wellbore cannot be edited, and is automatically deleted if the planned well is deleted.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FM971DLptN7gBIL2geVIF%2Fimage.png?alt=media&amp;token=f1ded78c-c432-4ec3-b753-d9525ac8198b" alt=""><figcaption><p>Figure 55: Planned Wellbore</p></figcaption></figure>


# 6.7 - Level 6: Actual Well

When the user right-clicks at Well level, they will be given the choice to insert a **planned well** or **actual well** below it. An actual well represents a well that has already been drilled or is currently being drilled. It is constructed using recorded surveys, as opposed to a planned well, which is constructed using planning tools.

Surveys are added to the actual well by right clicking on it and selecting **Insert New Survey**. Additionally, whenever a planned well is created, a planned wellbore is automatically created on the level below it.

The actual well level is made up of two components - the Actual Well Properties and the Actual Wellbore. **Use the navigation tree on the left to view the page for each component, or follow the links below:**

* [**Actual Well Properties**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.7-level-6-actual-well/6.7.1-actual-well-properties) **-** Where the user defines configures various properties of the actual well.
* [**Actual Wellbore**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.7-level-6-actual-well/6.7.2-actual-wellbore) **-** A representation of the full well path from surface to TD, constructed from the surveys entered at Survey Level.


# 6.7.1 - Actual Well Properties

The Actual Well Properties dialog will automatically open when a new plan is created. To access the Actual Well Properties for an existing well, right click on it in the Object Explorer.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fq2czyTQ0agcBjm0vHcpD%2FScreenshot%202026-05-07%20115151.png?alt=media&amp;token=600cb885-d165-47cc-91ad-0ff40f07b049" alt=""><figcaption><p>Figure 56: Actual Well Properties</p></figcaption></figure>

### **6.7.1.1 - Properties**

**Name:** The name displayed in the Object Explorer.

**Description:** A description of the wellbore used only for information purposes.

**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 Chart Defaults ribbon.

**Force Colour:** Selecting this option and choosing a colour will ensure that this actual well will always be displayed in this colour in all the plots. This supersedes any colour options for this actual well in the ‘Chart Properties’ dialog.

**Locked:** This checkbox allows the user to lock all the editable cells in the dialog. If NO password has been entered at Operator level in the set password section, then the user can freely select to lock and unlock the dialog. If a password has been added at Operator level, then the user must enter the relevant password to both lock and unlock the dialog.

### **6.7.1.2 - Vertical Section**

Details of the vertical section (used for section plots and vertical section calculations) are entered here. The VS azimuth and the origin point must be entered in order to correctly calculate vertical section. When Bottom Hole Location is selected, the program will draw a straight line from the VS origin point to the last survey point and the azimuth of this line will be used as the vertical section. It is important to note that if this is selected, the vertical section will change every time a new survey is added.

### **6.7.1.3 - Depth Reference**

A list of depth references available to the well can be selected from the drop-down menu. The available depth references are defined in the Well Properties, one level up. If the depth datum is changed and there are currently surveys entered, a dialog will appear asking if you wish to change the TVDs or preserve them. If the user chooses to **Change TVDs**, the TVD values of the surveys will be changed in order to preserve the TVD Subsea values. If the user chooses to **Preserve TVDs**, the TVD Subsea values will change in order to preserve the TVD.

**Note:** Changing a depth datum with surveys already entered can seriously corrupt your data and a backup should be made prior to this.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2F1odTYsdO2hYj8w1pyftx%2Fimage.png?alt=media&amp;token=add0e156-7b65-4018-9ae9-d73ae86c75b4" alt=""><figcaption><p>Figure 41: Changing the depth reference</p></figcaption></figure>

### **6.7.1.4 - Magnetics**

The magnetics grid allows the user to calculate geomagnetic data for the well location using any of the models available in the Well Seeker X magnetics directory. The geomagnetic data marked as Active will be used whenever ellipse of uncertainty need to calculated for the plan.

**Date:** The date used to calculate the geomagnetic data. This input is required if the user is using any model other than User Defined.

**Model:** Select the desired geomagnetic model from the dropdown box. By default, the IGRF and WMM models will be available. If your organisation has purchased the BGGM or HDGM models, contact Innova support (<support@innova-drilling.com>) for instructions on how to integrate them into Well Seeker X. The user my also select User Defined, allowing them to manually enter the declination, dip and total field values.

**Declination, Dip, Total Field:** These values will be automatically calculated using the selected model, date entered into the Date field, and the surface location of the plan. If User Defined was selected as the model, these values can be manually entered.

**Active:** Only one row can be marked as active at a time. The active row is the one used to ellipse of uncertainty for the plan.

**Export Geomag Data:** Located to the bottom-right of the Magnetics grid, this option exports the geomagnetic data as a document. Select the line in the ‘Magnetics’ section that you want to export the geomagnetic data for. Then select the report format as ‘PDF’ or ‘Excel’ from the drop down menu, before selecting ‘Export’ to generate the report.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOwtQd4OJyEaS2mLfQWfY%2Fimage.png?alt=media&amp;token=db5d9edf-9e41-4e79-85a7-fba2896411d4" alt=""><figcaption><p align="center">Figure 58: Magnetics</p></figcaption></figure>

### **6.7.1.5 - Survey Program**

The survey program specifies how the actual wellbore is constructed and which IPMS’s will be to generate error ellipses.

When the user first saves a survey, they will be asked if they want to add it to the survey program. This means that under normal operations the survey program will not ned to be manually edited. However, the user may need to manually reconstruct the plan to resolve and error, or to change which parts of the wellbore are covered by specific surveys.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FDGGMnnZjLDrTZ47JoOqe%2Fimage.png?alt=media&amp;token=fd67f7f7-3f77-408e-84ac-9871c5cf5c62" alt=""><figcaption><p align="center">Figure 59: Survey Program</p></figcaption></figure>

Rows in the survey can be deleted by clicking on their row number and then pressing the delete key on your keyboard. In a new row, start by selecting the desired survey from the dropdown box in the **Survey** column. The user should start with the shallowest survey. The **Depth From** and **Depth To** columns will populate down to the deepest station in the selected survey. If there are overlapping surveys present for the well, modify the Depth From and Depth To values to specify which parts of the survey you want to use.

**Note:** The Depth From value should always equal the Depth To value in the row above it – do not leave any depth gaps.

The survey tool for each survey is displayed in the **IPM** column. If the select survey tool is highlighted in red, it means that the required IPM file is missing on your PC. The Survey Tool Editor can be opened by clicking on the **Survey Tools** button at the top-right corner of the dialog. This value is not editable here – survey tools are chosen in the Survey Properties dialog.

If the actual well is a sidetrack of another well, the survey program from the motherbore will be included in the survey program, down to the tie-on point. These rows will be greyed out and un-editable.

### **6.7.1.6 - Sidetrack Details**

The actual well can be turned into a sidetrack of another well using the options in this section. Follow the process below to turn the actual well into a sidetrack. Note that actual wells can only be sidetracked from other actual wells, not plans. A more detailed explanation can be found on [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)

1. Click on **Well is a sidetrack**, to activate the other features.
2. Use the **Parent Well** to select the motherbore that this actual well will be tied to. Only actual wells under the same well will be available.
3. Enter the kick off depth of the sidetrack in the **ST Depth** box. This is referenced to the depth reference of this actual well, not the parent well.
4. Choose an option from the **Errors Start** dropdown. This sets where anti-collision ellipses begin when running anti-collision between the sidetrack and it's mother bore. If **ST Point** is selected, the error ellipses for both will start at the sidetrack kick-off point, with an initial magnitude of zero. If **Surface** is selected, the error ellipses will start at surface as normal. If the actual well was imported from a Compass EDM file, this option will match the choice in the EDM file. Otherwise, it will default to ST Point. Note that this only applies to anti-collision run between the mother bore and the sidetrack. For anti-collision scans against any other well or plan, the errors will start from surface.
5. Click on the **Create Sidetrack** button. This will update the survey program with all the surveys up to the side track point from the parent well. It should be noted that all previous survey program lines will be deleted.
   1. Annotations, Casings, and Formations will be copied from the motherbore into the sidetrack. Duplicate entries will be identified based on MD and will be cleaned up. Only entries above the sidetrack point will be copied. The same behaviour applies when creating a Sidetrack using the options in the context menu.

### **6.7.1.7 - Build Rate to Land**

By default, the **BR to Land** column, displayed in the actual wellbore and survey views, is calculated from the principal plan. Force landing allows the user to enter a TVD, INC and AZI to project to, without having to make an alteration to the principal plan. This information only affects the **BR to Land** column data.

### **6.7.1.8 - Depleted Zone**

This section allows the user to set up a depleted zone for the actual well, which can then be displayed on the 3D Chart. The depleted zone is elliptical; the **Up** and **Down** entries define the radius of the ellipse above and below the wellbore. The **Width** entry defines the radius of the ellipse to both the left and the right of the wellbore. The **Start** and **End** fields set the measured depth where the depleted zone starts and ends. The **Rotation** entry can be used to change the orientation of the ellipse. And lastly, the **Shape** dropdown can be used to choose to display the depleted zone as an Ellipse or a Rectangle.

### 6.7.1.9 - Multi-Leg Lateral

This section allows the co-ordinator to designate the actual well as the motherbore for a multi-leg lateral from this section. This is only available when connected to the user organization’s remote server database. If accessed on a local database, this options will be greyed out.

Check the checkbox and then enter the number of legs, not including the motherbore. At the rig site, the directional driller can create a new leg using the Side Track Wizard. See more information in section [**7.2 - Create Sidetrack**](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.7-level-6-actual-well/pages/c45c2ab14a36a639521d717029497f2a0fc48df6#id-7.2-create-sidetrack).

Note that the name of the motherbore must have a UWI appended to the end of the name, with the same format as below:

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2Fp1XYkgeCfmi5ggxjGTDW%2Fimage.png?alt=media&amp;token=3721c66d-01e3-48cb-92f5-b842864d5263" alt="" width="435"><figcaption></figcaption></figure>


# 6.7.2 - Actual Wellbore

Whenever an actual well is created, an actual wellbore is automatically created below it. It can be viewed by **double left-clicking** on the item one level below the actual well, which will always have the suffix ‘actual wellbore’.

The actual wellbore represents the full well path from surface to TD. It is constructed using the surveys associated with the actual well, as directed by the survey program in the Actual Well Properties.

The actual wellbore cannot be edited, and is automatically deleted if the associated actual well is deleted.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FI4cByqr0wcW1rmrctKKL%2Fimage.png?alt=media&amp;token=0f3b4051-34da-41db-ad8f-523ca492fd76" alt=""><figcaption><p>Figure 60: Actual Wellbore</p></figcaption></figure>


# 6.8 - Level 7: Survey

A survey represents a set of surveys taken with a single survey tool. An actual wellbore is made up of multiple surveys, combined together according to the survey program for the actual well.

To create a new survey for an actual well, right click on it and select **Insert New Survey.**

The survey level is made up of two components - the Survey Properties and the Survey View. **Use the navigation tree on the left to view the page for each component, or follow the links below:**

* [**Survey Properties**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.8-level-7-survey/6.8.1-survey-properties) **-** Where the user defines configures various properties of the survey.
* [**Survey View**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.8-level-7-survey/6.8.2-survey-view) **-** Where the user enters the survey stations.


# 6.8.1 - Survey Properties

The Survey Properties dialog will automatically open when a new plan is created. To access the Survey Properties for an existing survey, right click on it in the Object Explorer.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FqYLSyEH1GvNfVeWkC0hr%2Fimage.png?alt=media&amp;token=31fe1533-c696-46c6-824a-bf20cf112930" alt=""><figcaption><p align="center">Figure 61: Survey Properties</p></figcaption></figure>

**Name:** The name displayed in the database viewer tree.

**Tie-On:** This section specifies where the plan will tie on to:

* **Surface:** The survey will tie on to the well head location
* **User defined:** The user can enter the MD INC AZI NS EW and TVD the survey will be tied on to.
* **From survey:** Select the survey file to tie on to and type the MD which you wish to use. The INC AZI NS EW and TVD will be interpolated from the survey or plan selected. If the well is a sidetrack then surveys from the parent well are also available.

**Survey Instrument:** Select the error model which will be used to calculate the EOU for all surveys stations in the survey file. Clicking the **Survey Tools** button will bring up the survey tool editor. The user can also select an error model by opening the survey tool editor, selecting a model and clicking on the ‘select IPM’ button.

**Locked:** This checkbox allows the user to lock all the editable cells in the dialog. If NO password has been entered at Operator level in the set password section, then the user can freely select to lock and unlock the dialog. If a password has been added at Operator level, then the user must enter the relevant password to both lock and unlock the dialog.


# 6.8.2 - Survey View

The survey view allows the user to enter survey data into survey files and is accessible by **double left-clicking** on a survey in the Object Explorer.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FkAqcay34cUzzZGfixpNk%2Fimage.png?alt=media&amp;token=7fe4a73c-ae6c-403a-8704-36b19aedd066" alt=""><figcaption><p align="center">Figure 62: Survey View</p></figcaption></figure>

The tie-on line for the survey is not editable from the grid and can only be changed in the survey properties dialog. Enter **Measured Depth (MD), Inclination (INC)** and **Azimuth (AZI)** values into their respective columns, and all other parameters will be calculated.

The distance, Up Down, Left Right, TC X, TC Y, TFO HS, TFO + Azi and BR to Land columns will only be populated if a **principal plan** is present. The BR to Land column data can be overridden if the Force Landing option is selected in the Actual Wellbore Properties. The proximity calculations are performed using the scan method specified at operator level.

If a principal plan is present, the PLAN INC and PLAN AZI columns will also populate. Using the 3D closest approach method, these show the inclination and azimuth of the nearest point on the plan from that station.

The slide seen, slide remain and motor yield columns require data to be entered into the [**Slide Sheet**](/introduction/innova-engineering-manual/well-seeker-x-manual/11.0-reporting/11.11-slide-sheet).

The user can customise which columns are available by going to the **Settings** ribbon and selecting [**Show/Hide Columns**](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.8-level-7-survey/pages/a53f902c42d6891b0ed41a082c42fe71040d7b69#id-8.4.7-show-hide-columns)**.**

Right-clicking on a survey station will show the context menu. From there the user can copy and paste survey stations, delete stations, and insert a new blank row above the selected station. If the 3D chart is open for the current survey, selecting *Go to survey* will move the fly down sphere to that station.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FOLtaM9DVNMwxi8NmSVIB%2Fimage.png?alt=media&amp;token=86e18b3d-7cd8-4d3a-8b8c-efd78d49894d" alt=""><figcaption></figcaption></figure>


# 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**](/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.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/oY8D1aXEMEaAn5MMMiF7/Unknown%20image" alt="Figure 63: Object Explorer" width="563">

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)

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/MMFgWYEDlpvJMEv2oG3p/Unknown%20image" alt="Figure 65: Database viewer menu" width="375">

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

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.

If the actual well has been designated as a multi-leg lateral by an administrator, instead of a Sidetrack # option, the user will see a **Leg** dropdown box instead. The user should select the desired leg number from the available options.

<figure><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FWvkuqqXtWRZ5tOHLGVhu%2Fimage.png?alt=media&amp;token=5a39ad86-1adf-4ed6-ae78-89059fdf3fb9" alt="" width="264"><figcaption></figcaption></figure>

When the user clicks **Create**, Well Seeker will automatically extract and validate the UWI from the parent well or matching well plans. If no valid UWI is identified, the process will stop to prevent incorrect well creation. The UWI is very important for this functionality as the process will not be allowed to run without it. The UWI event code is automatically updated according to the selected leg number:

* Mother bore = Leg 1 (/00)
* Additional laterals automatically assigned (/02, /03, etc.)

The new lateral leg will be automatically pushed to and created on your organization’s remote server database.

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

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/qXWdATiddJNoE5wfowwu/Unknown%20image" alt="" width="375">

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

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/rnuEeRO1BxQUMzG9Uh8g/Unknown%20image" alt="Figure 68: Casing Details Dialog" width="563">

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.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OeFO9La7IZUXRODZkZM3/Unknown%20image" alt="Figure 69: Casing Delete Confirmation" width="563">

### 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="/pages/a498fd18a7950d80defc88e4f275125df570f538" %}
[7.7 - Targets](/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.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/NQebsunDIjzAqBTXlGem/Unknown%20image" alt="Figure 84: Annotations Dialog" width="563">

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.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/6JAP313u1qtaQKJpxFHt/Unknown%20image" alt="Figure 85: Lithologies Dialog" width="563">

### 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:

{% content-ref url="/pages/SKxgnriD5fiCcLAsRvod" %}
[11.0 - Reporting](/introduction/innova-engineering-manual/well-seeker-x-manual/11.0-reporting)
{% endcontent-ref %}

![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**](/introduction/innova-engineering-manual/well-seeker-x-manual/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><img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FUdxoDPZA4OM6P4yN0IFA%2Fimage.png?alt=media&amp;token=6c38e101-c7f2-4adc-ae88-211820128072" alt=""><figcaption></figcaption></figure>

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)

Checking the **Change Dip** checkbox will apply a TVD shift and track azimuth changes, but maintain a constant inclination/dip. If left unchecked it will mirror the original plan dip, inclination and azimuth values with a TVD shift applied.

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.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/46a9mjpbWTZYkxBf5HYh/Unknown%20image" alt="Figure 97: Section View Plot with Geo Steering Data" width="563">

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)

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/QhVtq8vlxxVu2J0oAYyk/Unknown%20image" alt="Figure 99: Chart Properties Dialog" width="563">

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 [**Push (Real Time Data Exchange)**](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/pages/BscELisQNqe1MsU1Q5dz#id-8.2.3.1-push-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:

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/bcT98tnIsT2BXB8yrTcP/Unknown%20image" alt="Figure 102: Toggling data sync status" width="563">

**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 **Batch**, 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, Batch** or **TD**, but this can vary depending on your company’s policy.


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

![Figure 70: Targets Dialog](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/l8S5F5d2OYm96vMIFTuF/Unknown%20image)

### 7.7.1 - Targets Toolbar

The targets toolbar is displayed at the top of the dialog, with the following functions:

![Figure 71: Targets Toolbar](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/60UIF7eGA4IBPYKlrNNm/Unknown%20image)

**Save Target:** Saves any changes made to the currently selected target.

**New Target:** Creates a new target.

**Delete Target:** Deletes the currently select target.

**Copy Target:** Creates a duplicate of the currently selected target

**Export Target:** Exports all of the targets currently displayed in the targets grid to a .mdb format export file.

**Import Target:** Imports the targets contained in a target export file. Note that targets in Well Seeker X must have a unique name. If the software detects that the name of an imported target matches the name of an existing target, the imported target will have a timestamp appended to it’s name. Imported targets are assigned at the level selected **when the Targets dialog was opened**.

**Bulk Import Targets:** Opens the Bulk Targets Import dialog. This allows the user to quickly create multiple point targets by entering their co-ordinates into the table. Before entering the data the user should select how the lateral co-ordinates of the new targets are referenced – either local displacement from the wellhead, grid northings/eastings or latitude/longitude. They should also choose the vertical depth reference – TVD or TVD subsea. The user can then type or paste their data into the table and click on **Import** to create the targets.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/5gj0V4dev1FHQTMxDltT/Unknown%20image" alt="Figure 72: Bulk Import Targets" width="375">

### 7.7.2 - Targets Grid

The targets grid contains a list of the targets that are available for selection. Targets will only be visible in the grid if they are currently associated with the level the dialog was opened from. If you wish to see targets from other wells/plans under the same field, use the **drop-down box** above the grid to move up to a higher level. When the target dialog is first opened, the filter is set to the current level by default.

![Figure 73: Targets grid](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/5bUh0zAJbS517WxhoHzc/Unknown%20image)

The check boxes beside each target can be clicked to associate the target with the desired level. To plot a target on a chart or use it in planning, it must be associated with actual or plan level. Targets are always available to the field level.

The deepest level the target can be assigned to is dependent on which level the dialog was opened. For example, if the dialog was opened at well level, it would not be possible to associate the target with any actual wells or plans but it would be possible to associate the target with other wells and facilities.

Regular targets and lease lines are contained in separate lists. To switch from viewing targets to viewing lease lines, click on the **Show Lease Lines** checkbox. Note that only polygon shaped targets can be turned into lease lines.

Clicking on a target’s name in the grid will select it so that it’s properties and shape can be edited.

### 7.7.3 - Target Properties & Vertical Depth

Use the **Name** box to edit the name of the target. The name shown in the grid will not update until the user saves their changes.

Enter the TVD of the centre point of the target in the TVD box. The centre point is the point that the planning tools will navigate to, regardless of the shape of the target. \*\*Note that the reference point for the TVD depends on the level that the dialog was opened at, and does not change if the level is changed using the dropdown box above the grid.\*\*For Field, Facility, and Well level the TVD datum will be the system datum, and for actual and planned wells, the datum will be the depth reference selected in the Actual/Planned Well Properties.

The reference point currently in use is displayed the TVD edit box.

![Figure 74: Target Properties and Vertical Depth](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/DptuJmimenjvIdIjesjv/Unknown%20image)

### 7.7.4 - Colour and Line Style

Toggle the Force checkbox to lock the target to the selected colour and line style. This means that when a target is displayed on a plot, it will always display with that colour and line style. This will also prevent the colour and style from being changed using the Chart Properties dialog.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/nq8RYRv30CMRPiWDr0Uo/Unknown%20image" alt=""><figcaption><p>Figure 75: Colour and Line Style</p></figcaption></figure>

### 7.7.5 - Drillers Target

To create a drillers target enter the confidence level required in the confidence box. This represents the statistical likelyhood that if the drillers target is hit the well will be within the geological target. Click the create drillers target button and select the well path which will be used to create the target. If the well path does not reach the targets TVD an error will be displayed. If the errors are small enough and the confidence level selected allows, the drillers target will be created and displayed on the plot. If the survey errors are too large or the confidence level too high an error will be displayed. Selected confidence must be less than 100%.

![Figure 76: Drillers Target](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/oOg3zpvbnFafmLK7MIxW/Unknown%20image)

### 7.7.6 - Target Center

The target centre location can be defined in three ways by selecting the appropriate radio button:

* **Local:** Local coordinates relative to the local datum. \*\*Note that the reference point for the local datum depends on the level that the dialog was opened at, and does not change if the level is changed using the dropdown box above the grid.\*\*The current datum is shown in the text at the bottom of the target centre frame.
* **Map:** Enter the grid northing and easting location of the target. This is usually the best way to enter the target centre location as it leaves no room for confusion which can occur with local coordinates.
* **Geographic:** Enter the target latitude / longitude.

![Figure 77: Target Centre](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/83qQqbgyMSk9ECOkRKJB/Unknown%20image)

### 7.7.7 - Target from horizontal displacement

When a target is supplied as a horizontal displacement and azimuth from the surface location, the user can use this section to generate the desired local coordinates. Once these details are added and calculate has been selected, the program will automatically populate the target’s local coordinates. This option will only be available when **local** is selected in the target centre section.

<figure><img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/k6ucdLyqhFumv3gghXsJ/Unknown%20image" alt=""><figcaption><p>Figure 78: Target from Horizontal Displacement</p></figcaption></figure>

### 7.7.8 - Target Shapes

After configuring the target co-ordinates on the left hand side of the Targets dialog, the user can move over to the right hand side to define it’s shape. Choose a shape for the selected target by clicking on one of the tabs. This will then display additional options that can be used to further configure the shape.

#### **7.7.8.1 - Point Targets**

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/znPiwGAudgbNAiYSamvh/Unknown%20image" alt="Figure 79: Point Targets" width="563">

No data is required for entering a point target.

#### **7.7.8.2 - Circular Targets**

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/K1cfHrZEDng9GKztE5Ao/Unknown%20image" alt="Figure 80: Circular Targets" width="563">

**Dip Angle**: The dip angle of the target horizontal plane. Note that this is applied after the rotation setting.

**Dip Azimuth:** The azimuth of the dip direction

**Thickness Up**: The distance from the target centre to the top of the target

**Thickness Down**: Distance from the target centre to the bottom of the target

**Radius**: The target radius

**Aiming Point Offset From Target Centre**: Offsets the centre of the circle north/south and east/west from the target co-ordinates. Note that the target itself does not change, just the position of the circle.

**Arc Properties**: Allows half-moon targets or equivalent to be created. Specify the start angle of the arc and the end angle.

#### **7.7.8.3 - Elliptical Targets**

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/XV1l42fxQSUMC3ChelG6/Unknown%20image" alt="Figure 81: Elliptical Targets" width="563">

**Dip Angle**: The dip angle of the target horizontal plane. Note that this is applied after the rotation setting.

**Dip Azimuth:** The azimuth of the dip direction

**Thickness Up**: The distance from the target centre to the top of the target

**Thickness Down**: Distance from the target centre to the bottom of the target

**Semi-Major**: The length of the ellipse semi major axis

**Semi-Minor**: The length of the ellipse semi minor axis

**Aiming Point Offset From Target Centre**: Offsets the centre of the ellipse north/south and east/west from the target co-ordinates. Note that the target itself does not change, just the position of the ellipse.

**Arc Properties**: Allows half-moon targets or equivalent to be created. Specify the start angle of the arc and the end angle.

**Rotation**: The rotation angle from north of the target centre line. Note that this is applied before the dip angle is applied.

#### **7.7.8.4 - Rectangular Targets**

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/hDO2BCnAXeD5gfB2ZnVN/Unknown%20image" alt="Figure 82: Rectangular Targets" width="563">

**Dip Angle**: The dip angle of the target horizontal plane. Note that this is applied after the rotation setting.

**Dip Azimuth:** The azimuth of the dip direction

**Thickness Up**: The distance from the target centre to the top of the target

**Thickness Down**: Distance from the target centre to the bottom of the target

**Length**: The length of the target

**Width**: The width of the target

**Aiming Point Offset From Target Centre**: Offsets the centre of the rectangle north/south and east/west from the target co-ordinates. Note that the target itself does not change, just the position of the rectangle.

**Rotation**: The rotation angle from north of the target centre line. Note that this is applied before the dip angle is applied.

### **7.7.9 - Polygon Targets & Lease Lines**

Polygon targets can be used for defining unusual shaped drilling targets as well as **lease lines** and **hard lines**. They are constructed by entering the locations of the corners of the shape into the table.

<img src="https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/zq9oEpdLv8W4hYcjhlHn/Unknown%20image" alt="Figure 83: Polygon Targets" width="563">

**Target Co-ordinates:** The user can choose to enter the co-ordinates of each corner using local XY values or map values. If *local values* are selected, enter the local NS and local EW values with respect to the target centre defined on the left hand side of the dialog. If *Map* is selected, enter the co-ordinates as grid northings and grid eastings. Entering one value type will cause the other to be automatically calculated. The BRG and DIST columns represent the bearing and distance of each corner from the previous corner.

**Rotation:** The user can toggle this option on and enter a value in degrees to rotate the target, with the target centre as the centre of rotation.

**Target Thickness:** If the user selects Constant here, they can enter a target thickness above (Up) and below (Down) to the target. If Individual is selected, they can use the table to define the target thickness at each point.

**Formation Properties:** Toggle the checkbox to allow a dip angle and azimuth to be added to the target.

**Offset Poly**: This option allows the user to reduce the size of a polygon target by a set distance. This is useful for creating a hard line from a lease line at know set back distance. Enter a positive value into the *Distance to Offset* box to enlarge the polygon, or a negative value to shrink it. Then click on the *Offset Poly* to create a new lease line with the offset applied. Complex polygons may have their corners / edges rounded or smoothed to account for shrinking.

**Lease Line/Hard Line:** A polygon target can be turned into a lease line or hard line by checking the **Is a Lease Line** or **Is a Hard Line** checkbox. This enables them to be used with lease line specific features such as the Real Time AC and lease line intersection annotations on plots.

It is important to understand that once this has been checked, Well Seeker will see this as a lease/hard line and not a target. The next time the user opens the target box, the lease line will no longer be visible. To see these lines, the user can select the “***Show Lease Lines***” option above the Targets Grid. This filter will hide the targets and display only the lease lines and the hard lines.

Lease lines will still be available to plot and can be manipulated in a similar way to regular targets in the chart properties.




---

[Next Page](https://docs.innova-drilling.com/introduction/llms-full.txt/1)