New Advancements in Flowback Analysis for Rapid Diagnostics and Integrated Hydraulic Fracture Optimization
Bibliographic record
Abstract
Abstract There is a large technological gap between the end of the frac and until operators accumulate long term production data to perform a meaningful lookback. Over the last 10 years flowback analysis (FBA) has emerged as a successful technology to address this problem by utilizing only commonly gathered production test data. FBA provides operators with a low-cost technology to perform rapid diagnostics and rapid lookbacks within days of opening the well to flow. In this paper, several case studies from prolific North America tight and shale plays will be presented to demonstrate the immense value of FBA for rapid diagnostics and rapid lookbacks. The presented case studies will focus on the interpretation of FBA results to identify hydraulic fracture optimization opportunities and improve future well performance. A new set of physics-based correlations are also demonstrated, which link effective stress (from DFIT), fracture area/stimulated volume (from FBA) and long-term pressure-normalized productivity, to extend the application of FBA to a large-scale field development. It allows operators to use extensive horizontal well base to predict and select optimal completion design ahead of pumping and to high grade the land base for full field development, forecasting and budget planning purposes. FBA is closing a significant technological gap in diagnostics methods from the time well has been completed to the time until we gather enough long-term production data to perform lookback or design evaluation. By integrating FBA diagnostics into hydraulic fracture optimization workflows, operators can promptly evaluate the efficacy of their fracture treatments and identify wells that are likely to underperform long-term within days of finishing pumping, enabling them to apply these insights to subsequent wells or pads. FBA provides results 6-12 months faster than other low-cost diagnostics (i.e. rate-transient analysis on long-term production data). By incorporating FBA into hydraulic optimization workflows, operators can quickly identify numerous commonly observed detrimental effects including small or unexpected fracture geometry, fracture skin damage, insufficient or degrading conductivity, and poor cluster efficiency. Through rapid diagnostics, operators are able to quickly identify optimization opportunities and drive their learning curve ahead of their capital spending.
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.006 | 0.006 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.005 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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".