To “Right Size” Fractures, Producers Adopt Robust Monitoring and Custom Completions
Bibliographic record
Abstract
As the shale sector looks for ways to improve well results, momentum is building to take a much closer look at how and where hydraulic fractures are created while pressure pumping fluids into tight, complex reservoirs. The effort is being driven by unresolved questions over optimal well spacing and fracturing techniques. They are two closely related issues that dovetail into sector-wide production shortfalls associated to frac hits, a common well-to-well effect that experts in the technical community have recently named fracture-driven interactions. One of the biggest challenges in overcoming these issues is to learn how to control the size of hydraulic fractures (the general emphasis is on reducing their lateral and vertical extensions) with a far finer degree of accuracy and finesse than is realistic today. There is an expanding array of diagnostic studies and new technologies working to this end. Several of the latest examples were highlighted at the recent Unconventional Resources Technology Conference (URTeC) in Denver. Operators both large and small used the conference as an opportunity to express support for the broader use of tools considered to be classic components of petroleum and reservoir engineering: wellhead and bottomhole pressure gauges. These two technological cousins are nothing new to the oil field, but have only recently become viewed as essential among those seeking affordable answers about how their fractures behave during the treatment. “The industry badly needs a low-cost, stage-by-stage method that we can use for assessing the reservoir quality, the completion design, and fracture complexities,” said Michael Sullivan, a reservoir diagnostics advisor with Chevron, during a technical session at URTeC. “Unfortunately, the high-cost and operational complexity is a barrier to most other stage-level assessments. What we need is something we can afford to do.” Sullivan was presenting a paper (URTeC 970) that describes how Chevron’s Canadian asset team in the Duvernay Shale recently began using “free” wellhead pressure data to estimate each fracturing stage’s performance. His hope is that others follow the workflows as Chevron looks at more than half-a-dozen ways to use the data (including perforation cluster efficiency analysis and frac hit identification) to refine its completions approach. Sullivan highlighted that the new learnings are thanks to pressure gauges it uses per standard procedure, meaning they are on wellheads whether the data is analyzed or not. To drive down costs further, Sullivan advised other operators to buy their own gauges vs. renting them from service companies. “What I’ve been emphasizing around our company is that this is a measurement we can afford to make—so let’s make sure we’re getting the most out of it,” he•added.
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.022 | 0.043 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.002 |
| Science and technology studies | 0.003 | 0.005 |
| Scholarly communication | 0.006 | 0.010 |
| Open science | 0.005 | 0.006 |
| Research integrity | 0.003 | 0.005 |
| Insufficient payload (model declined to judge) | 0.023 | 0.030 |
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".