MétaCan
Menu
Back to cohort
Record W2334906368 · doi:10.1061/41020(339)8

Project Information Management in Mega Oil Sands Projects

2009· article· en· W2334906368 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueConstruction Research Congress 2009 · 2009
Typearticle
Languageen
FieldEngineering
TopicReservoir Engineering and Simulation Methods
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsProject management triangleProject managementWork (physics)Extreme project managementKnowledge managementInformation managementInformation systemProgram managementComputer scienceProject management 2.0Project charterEngineering managementProcess managementInformation technologyProject planningProject stakeholderOPM3BusinessEngineeringSystems engineering

Abstract

fetched live from OpenAlex

Emerging Information and Communication Technologies offer major improvements to the practice of project management in the construction industry, yet these systems are complex and are not easily adopted into current practice. Furthermore, experiences with transformative information and communications technologies in other industries suggest that these benefits cannot be fully realized unless the overall work processes and management practices also evolve. This suggests that current work in construction project information and communications technologies cannot achieve its full potential unless we also develop our practices for managing information on projects. Project Information Management (PIM)—the practice of managing a construction project's information systems—should be developed into a more formal and explicit sub-discipline of project management. We propose an overall framework for Project Information Management, structured around four dimensions of goals and objectives, the project elements, the information system elements, and the management practices. Case studies are conducted to support our proposal.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.655
Threshold uncertainty score0.628

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.043
GPT teacher head0.352
Teacher spread0.308 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it