Incorporating Well Control Support Functions into a Broader Oil Spill Response Organization
Bibliographic record
Abstract
ABSTRACT This paper seeks to better prepare the oil spill response community for incorporating well control into a response organization, based on conditional considerations rather than long and firmly held assumptions. Techniques used to control a well, after a blowout, are more closely related to technical well drilling and control activities rather than to operations intended to address oil in the environment. When oil is released from a well in the Outer Continental Shelf (OCS), response organizers need to consider various factors influencing the organization that may exist at the time. These include a working knowledge of well control by response leadership; strength of responder relationships; and response complexity (to include authority, stakeholder and public expectations). This is particularly true when incorporating the well control support function in the oil spill response operational planning processes, usually facilitated by the Incident Command System (ICS). Within the last three years, complex well control operations were uniquely incorporated into response organizations during two Government Initiated Unannounced Exercises (GIUEs) and during the DEEPWATER HORIZON incident. Three options will be presented. Considerations for incorporating well control into a response organization will be presented using the case studies noted previously and by comparing similar lessons learned from the salvage industry in the late 1990's. Options presented help demonstrate that response organization flexibility is key to a successful response. This paper seeks to illuminate options surrounding placement of well control within an incident command structure based upon unique incident situational realities.
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.005 | 0.007 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.004 | 0.002 |
| Scholarly communication | 0.006 | 0.004 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.010 | 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".