Ethylene Product Pump Mechanical Seal Design Enhancements through Advanced Analysis
Bibliographic record
Abstract
One of the largest ethylene and polyethylene production complexes in the world located in Alberta Canada was dealing with marginal reliability of the mechanical seals on their ethylene product pumps. The ethylene product pumps are classified as API 610 BB5 types and the duty conditions for the mechanical seals are arduous, experiencing seal chamber pressures continuously above 1000 PSIG at sub-zero temperatures. The pumps operate at shaft speeds above 5,000 RPM providing additional challenges for the mechanical seal to overcome. The heritage mechanical seals utilized in this application were a dual unpressurized configuration supported by an API Piping Plan 11 and 52. Through close collaboration with the end user, the supplied seal provided by the manufacturer was able to achieve an 18 – 24 Mean Time Between Repair (MTBR). Known failure modes of the existing mechanical seal identified during failure analysis activities were addressed through modification of the seal to the existing iteration. The most recent limiting factor in seal performance was attributed to breakdown of thedynamic secondary sealing element in both the process and containment seals. The dynamic secondary seal, or o-ring, experienced a high degree of abrasion and breakdown. It was the seal manufacturer’s recommendation to address the root cause of seal failures by proposing an alternative configuration. The alternative seal configuration utilized active seal face features for optimized sealing of the ethylene while incorporating a non-pusher secondary seal (NPSS) to both the process and containment seals to address the dynamic o-ring concerns. Additionally, improvements to the circulation and cooling of the Plan 52 loop were identified and optimized through CFD modeling of the internal circulation device and support system piping. All modifications were incorporated into a redesigned seal cartridge that was installed during a unit outage in September 2021. Performance of the new design to date has been extremely satisfactory despite several documented upsets in the process stream.
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.002 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| 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.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".