Multi-Row Steel PDC Drill Bit Technology Redefines Performance Standards in Hard, Interbedded, and Abrasive Applications
Bibliographic record
Abstract
Abstract One of the biggest ongoing challenges to the successful production of many hard, interbedded and abrasive applications is the ability to improve drilling efficiency. In many of these applications, the use of PDC drill bits has been sporadic as many formations have been labeled ‘not PDC drillable’. As a result, these intervals often include several trips to change out drill bits (both rollercone and PDC drill bits of different types) in an attempt to maximize drilling performance. While PDC drill bits have generally proven to drill with higher ROP than rollercone bits, in these difficult drilling environments, the ROP differential can be very small, and the durability differential can be very large. A new line of steel bodied drill bits has recently been introduced that has shown dramatic improvements in drilling efficiency in highly difficult Western Canadian drilling applications. These new steel bodied drill bits incorporate a second row of PDC cutters to add durability to the bit while still remaining aggressive enough to drill at a high ROP. The use of steel as a body material makes it possible to have the best of both worlds – a bit with very high diamond volume for excellent durability (two rows of PDC cutters per blade) while also achieving a high void volume and large junk slot area for excellent cleaning. New techniques have also been developed to protect the steel body from the typical erosion and wear that has historically been seen in highly abrasive applications. Recent runs with this new line of drill bits have been recorded in intervals and through formations previously only drilled with rollercone bits. The new technology developed for these bits allows higher ROP and longer runs in demanding applications. In one challenging well in British Colombia, a series of these new steel multi-row bits drilled nearly twice as fast and over 30% more footage per bit than a direct offset well – saving days off the drilling curve.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".