Egyptian LNG - The Value of Standardisation
Bibliographic record
Abstract
This reference is for an abstract only. A full paper was not submitted for this conference. Abstract Key decisions at the beginning of any grassroots LNG project critically impact the ultimate success of the project. The variables to consider are numerous but from a high-level perspective, commercial variables such as available gas reserves, finance ability, corporate objectives and market penetration must be considered in combination with project related variables such as schedule, capital expenditures, and life cycle costs. The ultimate objective is to develop a strategy providing the highest rate of return to the owners whilst taking full account of the risks that can be managed by the owners. Shipping logistics, pre-investment for expansion trains, safety and environmental impact, technology selection and EPC contracting strategy all come into consideration early on in the process. One of the factors that most shape a LNG project is train capacity. Given the importance of economies of scale, the LNG train size that is chosen, along with the associated refrigeration turbine/compressor configuration, is a key decision that impacts almost all other variables. However, since the train capacity impacts so many project factors, the correct choice for one project is not necessarily the correct choice for another. The unique challenges that each project faces must be considered in order to arrive at the best decision for a given project. This paper draws on the experience of the Egyptian LNG project which is one of several grassroots projects started in the 2000's that remained with the nominal train size of 3.6 MTPA that became standard in the last half of the1990's. It should be noted that 3.6 MTPA is an annualized FOB rate - the actual PFD rate or design rate of the facility is over 4 MTPA. Some other contemporary projects have designed at 5 MTPA and one recent project has announced a 7.5MTPA train. Is it possible for smaller trains to compete in today's LNG business? The overall strategy for the Egyptian LNG project has been to standardize on the design developed for Atlantic LNG Trains 1–3. In this paper, we will provide an evaluation of the key considerations leading to this strategy and show that highly competitive capital costs can be achieved with smaller trains whilst also significantly reducing project schedule and minimizing owner risk.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.007 | 0.000 |
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 teacher head, 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".