Rig State detection

The rig state plugin can be found in the marketplace

Global Parameters

The global parameters are initially configured with values predefined by the RigState plugin itself, but can be modified by the user. Changing these parameters is reflected in all rigs that do not have a customized set of parameters (Presets), resulting in a global impact on the Live.

Steps to configure:

1. Access the RigState configuration screen.

1. Find the parameter you wish to update and enter the new value and save.

Physical Model Configuration - Presets

Presets are sets of customizable hyperparameters for rigs, allowing different rigs to use distinct parameters in the RigState state detection algorithms. By default, each rig receives an initial Preset that reflects the values of the global parameters. Additionally, it is possible to create, duplicate, and delete new Presets as needed.

Steps to use Presets:

The Physical Model Configuration modal can be accessed through the Asset Rig configuration dropdown menu.

Create Preset

1. Click the "Create New Preset" button and enter a name for the Preset.

1. Change the parameters as necessary and save.

Update Preset

1. Select the Preset you wish to duplicate.

1. Click the Duplicate button.

1. Enter the name of the new Preset.

1. Change the parameters as necessary and save the modifications.

Delete Preset

1. Select the Preset you wish to delete.

2. Click the Delete button.

1. Confirm the deletion of the Preset.

Activate Preset

1. Select the preset you wish to activate.

2. Click the activate button.

Pipes functions

State detection is performed through Pipes functions that must be used in the Pipes console. Below is an example of a Pipes query to apply the RigState algorithm, according to the configuration of the RigState screen.

-- Be sure that the channels below are configured in "Identification" column in "Standard Channels" page.
def @@mnemonics: 
(@@channels.weight_on_bit, 
@@channels.hole_depth, 
@@channels.rotary_speed, 
@@channels.rate_of_penetration, 
@@channels.bit_depth, 
@@channels.fluid_flow, 
@@channels.block_position, 
@@channels.weight_on_hook,
@@channels.standpipe,
@@channels.torque);

def @@event:'SomeEventType':const; -- The 'SomeEventType' should be replaced by type of generated event in Rigs Data Management.
def @@rigName:'SomeRigName':const; -- The 'SomeRigName' should be replaced by the Rig name.

@@event .timestamp:adjusted_index_timestamp mnemonic!:@@mnemonics
=> @rig_state_full @@rigName, null,  @@mnemonics

Available Functions

The Rig State plugin offers the following functions for state calculations:

• @rig_state

This function generates a simplified list of events, presenting only the title of the state and the corresponding color that represents it.

• @rig_state_full

This function generates a comprehensive list of events, presenting the states in detail. It includes the title of the state, the corresponding color, indicators, parameters used, and information about missing data.

• @normalized_indicators

This function calculates all the indicators used by the RigState algorithm based on the normalized events and returns these indicators, along with the parameters used in the calculations.

The old opmode functions are still available for compatibility reasons:

• drilling.normalized_opmode

• normalized_operation_mode

To use the configuration of a specific rig one can use one of the functions that receive the rig name as the first parameter:\

• drilling.rig_state

• drilling.normalized_rig_state

Above an example of the query used to retrieve the rig state of a rig by name:

def @@mnemonics: (@@channels.weight_on_bit, @@channels.hole_depth, @@channels.rotary_speed, @@channels.rate_of_penetration, @@channels.bit_depth, @@channels.fluid_flow, @@channels.block_position, @@channels.weight_on_hook); event_type .timestamp:adjusted_index_timestamp mnemonic!:@@mnemonics

=> expand drilling.normalized_rig_state("rigName", adjusted_index_timestamp#, mnemonic, value#, uom, @@mnemonics!) every 15 seconds => @set operating_mode != prev(operating_mode) ? random(), 0 as r => @throttle 2 min by operating_mode, r => @filter operating_mode != 'UNDEFINED' && operating_mode != null => @yield newmap(operating_mode, 1:object(), 'timestamp', timestamp#, '__color', newmap(operating_mode, __color)\

Dashboards

In the following image, it is possible to see the result of the stand length changed in the rig configuration, for the same time period on the dashboard the representation is updated due to the new value passed to the physical model algorithm.\

Unit configuration

It is possible to configure the rig state detection units constants per rig

Default Value - RigState Parameters

This topic describes how to configure the Rig State detection and it defines all parameters considered and how they impact the Rig State detection.

Default settings and guidelines for adjustment per rig