BD Field Development: First Kujung Horizontalnear HPHT - Critical Sour Wells Offshore Indonesia
Bibliographic record
Abstract
Abstract The Company had successfully drilled 4 challenging BD Development Wells (1 vertical and 3 horizontal). BD Field reservoir is aKujung 1 limestone reef, considered near HPHT and critical sour with 8,100 psi Bottom Hole Pressure (BHP), 300℉ Bottom Hole Temperature (BHT), 5.5% CO2 and 5,000 ppm H2S. This paper highlights the design phase and well deliverability covering pressure window, casing design, material selection, wellhead and Christmas tree, directional drilling planning, drilling fluid, cementing consideration, well completion, annulus pressure management, and project challenges. The data from two offset wells with surface location radius fewer than 2,000 ft from BD Platform were used as reference for lessons learnt and design for the casing seat selection. Based on the Wellbore Stability Study and the offset wells data, there exists a narrow mud weight window between pore pressure and fracture pressure. The directional plan was developed to have sufficient well separation in the upper hole section and enable fewer dog leg severity requirement to drill in the down hole section. Material selection for casing was designed based on the expected life of the well and reservoir properties in accordance to the requirements of NACE. Drill-in fluid system (Potassium Formate and Manganese Tetraoxide) with mud weight of 14.9 ppg was used to drill the limestone reservoir section providing minimal damage to the reservoir. Production casing cement was tested and analyzed in the laboratory for 60days in the HPHT chamber simulating reservoir properties. Open Hole Monobore Completion approach was selected to complete the well. In order not to compromise well integrity, annulus pressure management technique was fully implemented during drilling, completion, and well clean up phases. The wells were successfully executed despite several challenges which required unique mitigations to manage. During well clean ups, all wells were able to exceed the Absolute Open Flow (AOF) expectations.
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.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| 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".