Effectiveness of Alliances between Operating Companies and Engineering Companies
Bibliographic record
Abstract
Operating companies have formed ongoing alliances with engineering contractors for revamp work in operating plants. For the operating company, the alliance helps reduce overhead by eliminating cyclical work, allowing the company to focus on its core business. Ongoing alliances are different than traditional alliances, in that revamp work is harder to estimate and more likely to grow in scope and cost than new capital projects. Hence, ongoing alliances are fertile grounds for breeding mistrust. A study of five ongoing alliances found three distinct types of alliances. Operating and engineering companies have different motives for forming alliances. Key success factors include maintaining a core team, a climate of trust, and good procedures. Key factors that affect satisfaction within an alliance include the age of the alliance, the avoidance of traditional financial measures of performance and incentive fees, and close integration of operating and engineering company staff. Best practices for ongoing alliances are identified.
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.015 | 0.090 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.005 | 0.005 |
| Open science | 0.001 | 0.007 |
| Research integrity | 0.001 | 0.001 |
| 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".