Valve Automation for Oil Pipeline Safety
Bibliographic record
Abstract
Most pipeline codes, do not stipulate any requirement for block valve spacing nor for remote pipeline valve operations along transmission pipelines carrying low vapor pressure petroleum products. This requirement is generally industry driven for their desire to proactively control hazards and mitigation of environmental impacts in the event of pipeline ruptures or failures causing hydrocarbon spills. This paper will highlight a summary of pipeline codes for valve spacing requirements and spill limitation in high consequence areas along with a criteria for an acceptable spill volume that could be caused by pipeline leak/full rupture. A technique for deciding economically and technically effective pipeline block valve automation for remote operation to reduce oil spill and thus control of hazards is also provided. The criteria for maximum permissible oil spill volume, is based on industry’s best practice. The application of the technique for deciding valve automation as applied to three initially selected pipelines (ORSUB, OSPAR and ORBEL) is discussed. These pipeline represent about 14% of the total (6,800 kilometers, varying between 6” to 42”) liquid petroleum transmission lines operated by Petobras Transporte S.A. (Transpetro) in Brazil. Results of the application of the technique is provided for two of the pipelines: OSPAR (117 Km, 30” line) and ORBEL II (358 Km 24” line), both carrying large volumes of crude oil.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.007 | 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".