Horizon56 product description

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

Description of RigBridge Software solution

RigBridge is a Software solution for creating and organizing date in a digital format otherwise captured in Work Instructions. RigBridge natively integrates to RIgFlow. RigBridge allows the Plan Author to build up a detailed operation procedure in a consistent manner with feedback functionality.

1. Data Structure

In RigBridge and RigFlow activities are organized in a hierarchical structure under each Well. The data hierarchy is shown below:

LevelLevel DescriptionExample
Rig
1WellMD-CPH-1A
2EventDrilling
3PhaseIntermediate Section
4TaskDrill 8½” hole section
5ActivityDrill out 13-3/8” shoetrack
6StepTag top of cement
Table: In RigBridge and RigFlow, a plan is a Task that consists of a hierarchy of Activities and Steps.

In RigBridge and RigFlow, the information captured in a Work Instruction document today is considered a Task, with several Activities. Each Activity is sub divided into Steps.

2. Operational Coding structure

RigBridge has a built-in coding structure with a set of operational codes for each level in the data structure. This coding structure can be adapted to suit Maersk Drilling and the individual operators existing coding structure if required. When defining an Event, Phase, Task, Activity and Step in RigBridge an appropriate code shall be selected by the plan author. This code is transferred through to RigFlow and further on to the reports that are generated in RigFlow. It is therefore important to get the correct code set up in RigBridge to minimize the need to revisit codes later in the execution and post-execution phase.

3. Data input

In RigBridge wells are organized by each well. Under each well data is organized according to the structure outlined in the section above. For each level additional data can be defined by the plan author.

LevelDescriptionData input fields
1WellTitle
2EventTitle, Code
3PhaseTitle, Code
4Plan Title, Code, Revision, Planned start, Planned finish, Information, Objectives, Risks, Well Status, Technical Data, Preparations, Operations (list of Activities), Attachments
5Activity Title, Code
6Step Title, Responsible, Code, Instructions, Risks & warnings, Operational parameters, Report back and reminders
Table: Data input fields

3.1 Plan (level 4) specification

A Work Instruction documents corresponds to a Plan in RigBridge and therefore consists of multiple data fields that are editable to the user.

  • Title, Code, Revision, Planned start and Planned finish resides in the Plan data table and are editable to the plan author. Planned start defines the sort order of the plan once it is transferred to the execution environment in RigFlow.
  • Objectives, Risks, Well Status, Technical Data (grouped under Information) and Preparations are free text fields editable to the plan author. A basic free text editor is available for these fields.
  • Operations is the list of Activities that can be further defined at the subsequent data level.
  • Preparations are the list of the preparations that can be targeted specific roles. The preparation description is a free text field editable to the plan author whereas the target role is picked from a predefined list.
  • Attachments are the list of attachments to the plan. The plan author can upload any number of attachments to the plan either as .pdf or .jpg files.

3.2. Activity (level 5) specification

Activities are editable to the user. Activities are defined by a title (free text) and a code (predefined list).

3.3. Step (level 6) specification

Steps contains the actual operational instructions and therefore consists of multiple data fields that are editable to the plan author.

  • Title (free text), Responsible role (predefined list), and Code (predefined list) resides in the Plan data table and are editable to the plan author.
  • Instructions and Risks & warnings are free text fields editable to the plan author. A basic free text editor is available for these fields.
  • Operational parameters provide a structure for collating operational parameters that are relevant for the step. These will then be presented to the driller in a consistent manner.
  • Report back and reminders provides a structure for defining specific points for the driller to report back on during execution of the plan either as a check, a number or free text. These will then be presented to the driller in a consistent manner.

4. Approval Process

RigBridge contains a review and approval workflow that can manage the approval process from draft to publishing the plan to RigFlow. The approval flow can be customized. The default workflow handles the plan through five statuses:

  • Onshore draft
  • Offshore draft
  • In review
  • Awaiting approval
  • Published

The plan author has control over the plan status and can progress the plan forward through statuses. When the status is set to Awaiting approval the plan author can select roles that will be requested to approve the plan. The selection is done from a predefined list of roles. Once all Approvers have approved the plan the plan can be published. This will transfer the plan to the execution environment in RigFlow. There is an option for the plan author to override the approval process and publish the plan without approval.

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