Horizon56 Product Description

See product description of Horizon56 software at https://horizon56.io/legal/ProductDescription

Description of RigFlow Software solution

RigFlow provides information and instructions normally captured in Work Instruction documents in a digital format to rig personnel involved in the well construction process. Further in allows users report back on activities completed on ongoing basis and is a tool to orchestrate well construction activities.

1. RigFlow Software usage

All personnel on a rig involved in the well construction operations should have access to RigFlow. A role with access to RigFlow is an Authorized Role. The list of Authorized Roles is defined in the interface between RigFlow and RigBridge. As an example, this could be a “Offshore Drilling Engineer” (Operator), “Tourpusher” (Drilling Contractor) or “Offshore Data Analyst” (Service Company). The specific list of Authorized Roles will be agreed for each deployment. Access is provided via a role-based log-in for each Authorized Role, provided electronically to either the specific Authorized Role or to the organization responsible for that role.

2. RigFlow information structure

RigFlow provides information of well construction instructions as provided by the RigBridge solution. In RigFlow the information is grouped as follows:

  • Level 4 (Task) corresponding to content of a Work Instruction
  • Level 5 (Activity) – Groups of Steps
  • Level 6 (Step) – Individual operations

In-case required information is not provided correctly into RigBridge or similar system, for whatever reason, RigFlow will as a result, be unable to relay the information to Authorized Users involved in the well construction operations.

2.1 Specification of information of a Task

Multiple Level 4 (Task) data sets (i.e. similar information as captured in a Work Instructions), can be pushed from RigBridge to RigFlow. The status of a Task can be set to the following statuses:

  • Approved status indicates that the Task Action plan has been reviewed and approved in RigBridge and can now be pushed for operations in RigFlow.
  • Active status indicates that rig operations as detailed in this Task is currently ongoing on the rig.
  • Complete status indicates that all work on the task action has been completed and task objective delivered.
  • Abandoned status indicates that either no work was performed on the given task action plan or that it was partially complete prior to being disregarded (full task objective not delivered).

The information of a Task from RigBridge, or similar systems, is structured in four categories further described below:

  • Operations (“Action Plan”)

The information from RigBridge related to Activities and Steps are presented in the sequential order for execution. The responsible role (i.e. an Authorized User) for each Step as assigned, can complete each Step in RigFlow once the specific rig operation has been performed. Once this is done, the next Step will commence. For each completed step, the corresponding timestamp and bit depth (as captured by the drilling control system) will be recorded.  Additionally, all times captured in RigFlow will be as per the actual timestamp. Adjustments to cater for standard 15min breakdowns of rig activities can be performed in the current respected reporting systems manually if required.

  • Preparations (Preparational activities)

Preparational activities are assigned to a specific role, and in relevant groups of preparational activities in RigBridge. In RigFlow, preparational activities are listed per role. Each preparational activity can be set to “Not done”, “Completed” or “Not applicable”. Once preparational activities are completed on the rig, this must subsequently be reported in RigFlow via either mobile device or laptop-based access. It is the responsibility of Equinor to specify the preparations, and responsibility of the assigned role to ensure preparational activity statuses are correctly reported in RigFlow.

  • Information (Overarching well info)

Information relevant for entire well section and level 4 Task, divided into sections “Well Status”, “Main risks”, and “Technical data”. The information is static, and the information from RigBridge.

  • Attachments

Attachments of following file types PDF’s, JPEG and PNG files are available in RigFlow.

3. Revisions to instructions

All information from a Task can be amended, deleted, moved, or otherwise changed by sending a revised Level 4 (Task) from RigBridge to RigFlow. Steps that have either been completed or are ongoing in RigFlow cannot be changed.

4. Notification Log

In RigFlow, an overview is provided of the changes to the information received from RigBridge in-case of revisions to a level 4 Task.

5. Operation Log

In RigFlow an operation log is available providing an overview of completed steps. This information can be extracted as input to a reporting system.

6. User comments

In RigFlow users can register comments related information provided in RigFlow related to both Action Plan and Preparational Activities. Each comment is registered with a corresponding timestamp and bit depth.

7. Insights and lessons learned info

In RigFlow users can register lessons learned comments to specific areas that potential to be improved. All Insight information flows back to RigBridge.

8. Deviation to plan (use of Actions)

In-case the rig operation deviates from the instructions provided from RigBridge, deviations can be created and registered in RigFlow by adding “Actions”. Actions are equivalent to new level 6 Steps. Adding actions is uncontrolled (no approval required).

9. Reporting from RigFlow

As the operation progresses, the “as-run” content of the Action Plan be pushed back to RigBridge in real time. Further “as-run” activities can be extracted in various formats incl. to OpenWells, IFS, cvs format and more.

10. Release Notes

Release note #date# – make link to separate site with release note

Release note #date# – make link to separate site with release note

Release note #date# – make link to separate site with release note