Rational Stress Limits and Load Factors for Finite Element Analyses in Pipeline Applications: Part III — Elastic-Plastic Load Factor Development
Bibliographic record
Abstract
In this paper, a methodology is presented to develop load factors for use in elastic-plastic assessments of pipelines and their components. The load factors are based on the pipe material properties and the ASME pipeline code’s design margin for the service and location of the pipeline installation [1, 2]. These codes are recognized by 49 CFR 192 and 195 [3, 4]. Minimum required load factors for internal pressure loads can be derived analytically based on design equations from the ASME B31 piping codes and minimum material requirements for API 5L line pipe [6]. Once the load factor is established for a particular case, the elastic-plastic methodology may be used in the Finite Element Analysis (FEA) of pipelines and related components. This methodology is particularly useful in the assessment of existing systems when linear elastic numerical analysis shows that local stresses may exceed the elastic design limits. Two case studies are presented showing analyses performed with Abaqus [5], a commercial, general purpose FEA software package. The first case study provides an assessment of a large diameter elbow where the stress on the outer fibers of the intrados exceeded the longitudinal stress limits from B31.8. The second case study examines an assessment of a tee connection where the stresses on the ID exceeded the yield strength of the component. In addition to the case studies, the paper also presents the results of a full-scale test that demonstrated what margin was present when the numerical calculations were based on specified minimum properties. This paper is not intended to revise or replace any provision of B31.4 and/or B31.8 [1, 2]. Instead, it provides the means for calculating load factors that can be used with an elastic-plastic analysis approach in a manner that provides the same design margins as the ASME B31 codes. The approach described in this paper is intended for use in the detailed FEA of pipelines and their associated components.
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.003 | 0.008 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.006 | 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".