MétaCan
Menu
Back to cohort
Record W1998536527 · doi:10.1108/17538371211214941

Practical difficulties encountered in attempting to implement a partnering approach

2012· article· en· W1998536527 on OpenAlex
Wenche Aarseth, Bjørn Andersen, Tuomas Ahola, George Jergeas

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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueInternational Journal of Managing Projects in Business · 2012
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsOriginalityKnowledge managementProcess managementKey (lock)Value (mathematics)Computer scienceProject managementEmpirical researchManagement scienceBusinessSociologyManagementEngineeringQualitative researchEconomics

Abstract

fetched live from OpenAlex

Purpose The purpose of this paper is to present practical difficulties in attempting to implement a partnering approach. Design/methodology/approach The paper comprises empirical evidence from case studies in Norway and Canada and an extensive literature review on partnering. Findings The authors identified a lack of shared understanding of key partnering concepts, missing initial effort to establish shared ground rules, communication difficulties in inter‐organizational relationships and unclear (perceived) roles and responsibilities. In existing partnering literature, a large number of construction studies have identified conceptual partnering models. However, studies that describe partnering models to take these practical difficulties into account have not been found and the paper develops a practical model that outlines the phases of a typical partnering effort. Research limitations/implications Partnering has both a legal/contractual side and a management/collaboration side. This paper looks at the management and collaboration aspects of partnering only. Practical implications The paper will be a very useful source of information and advice for project managers who are attempting to implement partnering in projects. Originality/value The paper presents organizational challenges and difficulties in attempting to implement partnering and a practical model which takes these difficulties into account.

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.005
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.125
Threshold uncertainty score0.444

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.001
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0010.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.209
GPT teacher head0.455
Teacher spread0.246 · 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