Rig-state classification supplies the operational meaning that raw channels do not contain. The same torque, flow, hook load, or bit movement can support different conclusions while drilling, reaming, circulating, tripping, or making a connection. State errors therefore propagate directly into KPIs, models, event detection, and alerts.

Rig state is a derived engineering variable

There is usually no single rig-state sensor. Operational state is inferred from patterns among several channels:

For example, a classification system might consider relationships among:

  • bit depth,
  • hole depth,
  • block movement,
  • hook load,
  • surface RPM,
  • pump activity,
  • standpipe pressure,
  • ROP.

The exact implementation can vary. But conceptually the problem is similar to what an experienced engineer does while watching traces. If:

  • bit depth is near hole depth,
  • hole depth is increasing,
  • pumps are on,
  • surface rotation is present,

the evidence is consistent with rotary drilling. If hole depth is increasing but surface RPM is absent while a mud motor is active, the operation may instead be slide drilling. If:

  • bit depth is changing,
  • hole depth is not,
  • pumps and rotation are active,

the system may be observing reaming rather than drilling. The important point is not a specific threshold set. It is that multiple measurements are interpreted together to create an operational label.

The same surface-torque value shown in rotary drilling, rotating off bottom, reaming, and static contexts.

The same surface-torque value supports different engineering interpretations depending on the operation.

Once rig state is available, the same dataset can be routed into mechanically meaningful analyses:

Analysis Eligible state information
Drilling performance Actual drilling; exclude reaming, circulation, connections, and tripping.
Torque and drag Separate pick-up, slack-off, and rotating-off-bottom measurements for their calibration roles.
Hole cleaning Treat drilling, static time, reaming, rotation, and off-bottom circulation as different evidence.
Connection performance Use transitions through off-bottom activity, slips, and return to drilling.
Dysfunction surveillance Activate calculations only when the operating state supports their physical interpretation.

This means rig state is not simply another chart trace. It acts more like a routing variable. It determines which analytics should receive each portion of the data.

Operational-mix dashboard summarizing the last 24 hours and comparing day and night shifts.

A rolling operational-mix view turns the classified state stream into a quick 24-hour and shift-level summary.

Mixed states corrupt downstream results

Imagine evaluating WOB performance over one hour. During that hour:

  • 38 minutes were drilling,
  • 8 minutes were connections,
  • 6 minutes were reaming,
  • 8 minutes were off bottom.

If all data are included, median WOB might be 18 klbf; during actual drilling it may be 32 klbf. Only the second describes the drilling practice. The same contamination can occur with:

  • ROP,
  • torque,
  • differential pressure,
  • RPM,
  • flow,
  • MSE,
  • connection time,
  • trip speed.

This is one reason sophisticated-looking statistics can still be wrong. A percentile calculated over the wrong operational population is still the wrong answer. Before calculating:

  • average,
  • median,
  • P10,
  • P50,
  • P90,

the first question should often be:

Which operational states belong in this population?

Synthetic one-hour rig-state and WOB chart comparing an all-state average with a drilling-only distribution.

All values may be valid, yet mixed-state statistics still describe the wrong operational population.

If ten minutes of reaming are incorrectly classified as drilling, the error propagates:

  • ROP statistics: Average drilling ROP is reduced because footage is not increasing normally.
  • MSE: The calculation may interpret mechanically different data as cutting performance.
  • Slide/rotate percentages: The footage or time allocation becomes incorrect.
  • Connection timing: State boundaries may shift.
  • Hole cleaning: Reaming activity that should count as proactive pipe movement may disappear from the event history.
  • Torque and drag: Hook-load points may be assigned to an inappropriate mechanical condition.

The rig-state error itself may seem small. But the error is multiplied across every downstream calculation that trusts the classification. This is why operational-state classification should be treated as infrastructure, not merely a visualization feature.

Models and transitions need state context

A real-time hydraulic model may compare steady-drilling pressure with expected circulating pressure. While pumps are:

  • ramping up,
  • ramping down,
  • off,
  • or operating during a different rig activity,

the same comparison may not be meaningful. SPE-191797 specifically notes that applications of a real-time hydraulic model require knowledge of rig state, such as drilling, tripping, or circulation, in addition to real-time channels and contextual information.[1] That is a significant point. The physical equations may remain valid. But the boundary conditions have changed. A real-time model therefore needs to know not only:

What are the inputs?

but also:

Is the system currently in the operating condition this calculation assumes?

The transition can matter as much as the current label. A drilling connection follows drilling → off bottom → connection preparation → slips/activity → out of slips → return to bottom → drilling. Those boundaries separate where the cycle time is spent instead of reducing the operation to total connection time. A trip similarly repeats movement → slips → connection → movement. State transitions provide the event boundaries needed for repeatable performance metrics.

Synthetic connection-performance dashboard showing weight-to-weight connection time over bit depth.

Rig-state transition boundaries make repeatable connection-performance tracking possible.

Uncertainty is a valid state

A common temptation in classification systems is to require every second of data to have a named state. That can create false precision. There are situations where:

  • sensors are missing,
  • channels disagree,
  • transitions are occurring,
  • the rig is performing an unusual hybrid activity,
  • or the available evidence simply does not support a unique interpretation.

In those cases, an unknown or unclassified state can be technically preferable. The downstream analytics can then:

  • exclude the uncertain interval,
  • reduce confidence,
  • or request more context.

This is better than confidently labeling the interval incorrectly. The principle is the same one we encountered in sensor validation and washout diagnosis:

uncertainty is information.

A mature system should preserve it.

Worked connection example

A synthetic ten-minute connection sequence shows the routing effect:

Time State and evidence Analytical treatment
14:00–14:04 Rotary drilling: depth increasing, bit near bottom, pumps on, 120 RPM, steady torque, ROP near 180 ft/hr Include in ROP, MSE, dysfunction, and parameter-performance analysis.
14:04–14:05 Off bottom before the connection Stop contributing to drilling-performance statistics.
14:05–14:07 Connection: static bit depth, no rotation, changing pump activity Include in flat-time and connection analysis.
14:07–14:08 Circulation/preparation with staged pumps and brief rotation Do not evaluate pressure transients as steady drilling.
14:08–14:10 Return to bottom and resume drilling Restart the eligible ROP and MSE population after the transition.

A time-series plot sees ten minutes of continuous sensor data. A state-aware system sees five operational segments. That distinction is the foundation of meaningful automated analysis.

Aligned synthetic hole-depth, bit-depth, block-position, pump-rate, RPM, and rig-state tracks around a connection.

Aligned synthetic traces show the transition from drilling through a connection and back to bottom.

AI-augmented daily operational timelog assembled from classified rig-state events.

same classified events support an automatically assembled daily timelog while keeping each summary linked to its source interval.

Store one auditable classification

Once a robust state classification is generated, there is a strong architectural argument for treating it as a first-class data product. Otherwise:

  • the ROP module defines drilling one way,
  • the connection module defines it another way,
  • torque-and-drag uses a third rule,
  • reporting uses a fourth.

Then the same ten-minute interval can be categorized differently depending on which page is open. A better architecture is one operational interpretation → many downstream consumers with versioning and traceability when the classifier changes. This makes KPI definitions reproducible. If historical results change after classifier improvements, engineers can understand why. That is particularly important when comparing:

  • rigs,
  • crews,
  • wells,
  • time periods,
  • or performance before and after operational changes.

Synthetic entire-well rig-state history arranged by date and hour.

An entire-well state history provides a compact operational audit trail.

It may be tempting to create extremely detailed labels for every possible rig activity. More categories are not automatically better. A useful state taxonomy should be detailed enough to separate operations that matter mechanically or analytically, while remaining:

  • stable,
  • interpretable,
  • generalizable across rigs,
  • and supportable by the available sensors.

If two states cannot reliably be distinguished with the existing channels, separate labels add false precision. The taxonomy should follow the downstream engineering question: distinguishing drilling from reaming is valuable; splitting nearly identical transition states is not unless a calculation uses the difference.

Related technical resources

References

  1. Shahri, M., Kutlu, B., Thetford, T., Nelson, B., Wilson, T., Behounek, M., Ambrus, A., and Ashok, P. Adopting Physical Models in Real-Time Drilling Application: Wellbore Hydraulics. SPE-191797-MS, SPE Liquids-Rich Basins Conference, North America, Midland, Texas, 2018.