A torque-and-drag model becomes operationally useful only after its baseline matches the actual drillstring and rig. Pipe-weight assumptions, block-weight offsets, state selection, and local friction can otherwise produce plausible curves for the wrong system. The calibrated residual is usually more informative than the fitted friction factor alone.
Know what the model predicts
At its core, torque-and-drag modeling describes how forces are transmitted through a drillstring in a wellbore. The drillstring has:
- buoyant weight,
- axial tension or compression,
- contact forces against the hole,
- friction at those contacts,
- and, when rotating, torque required to overcome mechanical resistance.
A common soft-string representation treats sliding friction conceptually as:
$$F_f = \mu N$$
where:
- \(F_f\) is friction force,
- \(\mu\) is the friction factor,
- \(N\) is normal contact force.
The normal force itself depends on:
- trajectory,
- drillstring weight,
- tension,
- inclination,
- curvature,
- and other mechanical conditions.
Integrating those forces along the drillstring produces state-specific surface predictions:
| State | Expected response |
|---|---|
| Pick-up | Friction resists upward movement, so hook load exceeds static string weight. |
| Slack-off | Friction acts in the opposite direction, so hook load falls below static string weight. |
| Rotating off bottom | Rotation changes the frictional response and provides another condition for comparison with modeled torque. |
These relationships create the familiar torque-and-drag or broomstick plot.
Calibrate weight and friction separately
Drillpipe is commonly described by nominal values. For example:
- nominal OD,
- nominal weight per foot,
- grade,
- connection.
Those values are necessary for engineering design. But the effective weight represented in a real torque-and-drag model may differ enough from the nominal value to matter over a long string. SPE-191426 discusses several practical reasons.[1] Actual pipe assemblies include connections and tool joints that do not have the same cross section as the pipe body. Over time:
- tool joints wear,
- coatings may deteriorate,
- connections experience repeated make-up and break-out,
- manufacturing tolerances accumulate,
- and actual assembly dimensions differ from simplified nominal descriptions.
A small error per foot becomes meaningful when multiplied by tens of thousands of feet of pipe. The published field implementation found that changing adjusted drillpipe weight materially shifted modeled hook-load behavior and therefore needed to be addressed before friction calibration.[1] Describing a well by a single 0.20 or 0.30 friction factor can be useful shorthand, but mechanical behavior may vary with depth. Different intervals may include:
- casing,
- open hole,
- different mud exposure,
- tortuous sections,
- ledges,
- cuttings accumulation,
- changing contact behavior,
- or local hole-quality problems.
SPE-191426 describes automatically fitting open-hole friction factors against measured hook-load behavior at different measured depths.[1] This turns friction from one constant input into something closer to a depth-dependent diagnostic signal. Instead of asking only:
What friction factor best describes the whole well?
the more useful questions are which friction factor reproduces measured behavior at the current depth and how that inferred value changes along the hole.
Depth-dependent calibration can reveal intervals where measured mechanical behavior requires more drag than the surrounding hole.
Use only state-valid observations
The torque-and-drag equations depend on the mechanical condition being modeled. A hook-load point collected during:
- pick-up,
- slack-off,
- rotation,
- a connection,
- reaming,
- static conditions,
cannot simply be thrown into the same calibration dataset. The observations represent different physical states. SPE-191426 explicitly relied on rig-state classification to identify conditions such as:
- pick-up,
- slack-off,
- rotating off bottom,
- and connections
for appropriate use in calibration.[1] This illustrates why operational-state detection is so important in automated drilling analytics. Raw data says: Hook Load = 438 klbf. Context says: Hook Load = 438 klbf while tripping out at this depth with this drillstring configuration. Only the second statement is useful for friction calibration.
Interpret residuals, not absolute hook load
Another way to interpret the system is to examine the residual:
$$R = HL_{\mathrm{measured}} - HL_{\mathrm{modeled}}$$
where \(HL\) is hook load. If the calibrated model normally reproduces trip-out hook load closely, but measured hook load suddenly exceeds the modeled response by 30 klbf, that residual may be more immediately useful than asking what single friction factor would make the point fit. Why? Because a localized residual can represent:
- a tight spot,
- accumulated cuttings,
- ledge interaction,
- temporary pack-off tendency,
- wellbore geometry effects,
- or another transient mechanical condition.
Forcing every abnormal observation into a new friction factor can turn an event into a calibration change. Sometimes the correct conclusion is The baseline model remains valid, but the well has produced an abnormal mechanical event. This leads to an important distinction:
- Calibration: updates the normal model.
- Surveillance: detects departures from the normal model.
Those functions should work together without becoming the same thing. Which measurement is an overpull: 450 or 470 klbf? There is no answer without context. At one depth, modeled pick-up weight may be 430 klbf; at another, it may already be 465 klbf. The meaningful quantity is the residual from the depth-dependent expected hook load. That is why calibrated torque-and-drag models are powerful for event detection. The model supplies a mechanical baseline that changes with:
- depth,
- trajectory,
- drillstring configuration,
- and frictional conditions.
The surveillance logic can then evaluate whether the actual measurement departs unusually from that baseline. SPE-191426 applied this concept to identifying probable overpull and underpull events while tripping.[1]
Mechanical events are best interpreted as departures from a depth-dependent expected response rather than by absolute hook load alone.
Carry mechanical learning forward
The mechanical information learned while drilling has value later in the well. If calibrated trips repeatedly identify:
- elevated inferred friction,
- recurring overpull,
- or difficult depth intervals,
those observations can inform expectations for casing. SPE-191426 extended the real-time modeling workflow to a subsequent production-casing run and compared casing behavior against the mechanical trends learned earlier in the well.[1] This is an important idea. The value of a calibrated T&D model is not limited to explaining what is happening now. It can preserve information from one operation for use in the next one. That creates a continuous workflow:
BHA trips → learn mechanical response → identify troublesome intervals → update hole understanding → inform cleanout or casing strategy.
This is more useful than generating a new offline T&D spreadsheet each time the operation changes. A defensible workflow follows:
| Stage | Required work |
|---|---|
| Build the physical model | Load surveys, drillstring components, casing geometry, BHA, mud weight, and pipe properties. |
| Establish the weight baseline | Verify block weight and effective drillpipe weight before interpreting disagreement as friction. |
| Classify the operation | Separate trip-out, trip-in, rotation-off-bottom, connection, and incompatible states. |
| Fit baseline friction | Use appropriate trip and rotating observations to represent normal measured behavior. |
| Check stability | Look for smooth, credible depth trends and intervals forcing implausible fits. |
| Monitor residuals | Identify excessive positive or negative hook-load deviation, erratic response, and repeated local anomalies. |
| Separate change from event | Recalibrate for a persistent baseline shift; treat an isolated overpull as an event. |
| Preserve and reuse depth context | Carry difficult intervals into later BHA trips, cleanout planning, reaming, and casing forecasts. |
Measured trip-out hook load agrees with the calibrated model over most of the well, while the zoomed difficult interval and synchronized trip view preserve the localized elevated response for engineering review.
Related technical resources
- Using Physical Models as Real-Time Reference Signals in Drilling Analytics
- Interpreting Surface WOB, RPM, and Torque in the Context of Downhole Conditions
- How Survey Interval Affects Wellbore Tortuosity Analysis
References
- Shahri, M., Wilson, T., Thetford, T., Nelson, B., Behounek, M., Ambrus, A., D'Angelo, J., and Ashok, P. Implementation of a Fully Automated Real-Time Torque and Drag Model for Improving Drilling Performance: Case Study. SPE-191426-MS, SPE Annual Technical Conference and Exhibition, Dallas, Texas, 2018.