Module Land Transport Stability for Energy and Industrial Facilities
Bibliographic record
Abstract
A key aspect of modular construction is the interface between engineering and moving operations. While conventional “stick built” operations consider construction loads as operational load cases, modular construction involves moving and lifting operations of very significant loads and sizes, which require a more formal approach to between the engineering, planning, and execution of such operations. Overlooking the engineering of these critical moving operations at the front end of the project can result in costly failures with severe outcomes involving personnel safety, project costs, and schedule overruns. To avoid unnecessarily costly or unsafe designs at the later stages of a project, the interface points between equipment or module and trailer must be established starting in the beginning stages of the project among the project team. The land transport stability is determined by checking axle loadings, combined geometric stability, dynamic stability angle, and trailer spine beam analysis. A calculation example of these checks is also included in the Appendix of this paper. An SPMT transport stability calculation example is included in the Appendix of this paper. The calculation example, information, resources, and recommended future works provided in this paper will give practicing engineers a more thorough understanding of land transport module designs and analyses.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.013 | 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".