MétaCan
Menu
Back to cohort
Record W2057456963 · doi:10.1002/pmj.20193

Attitude-Based Strategic Negotiation for Conflict Management in Construction Projects

2010· article· en· W2057456963 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

VenueProject Management Journal · 2010
Typearticle
Languageen
FieldComputer Science
TopicMulti-Agent Systems and Negotiation
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsNegotiationOrder (exchange)Conflict resolutionManagement scienceProcess managementProject managementProcess (computing)Decision support systemKnowledge managementComputer scienceBusinessOperations researchEngineeringPolitical scienceSystems engineeringArtificial intelligence

Abstract

fetched live from OpenAlex

An innovative negotiation methodology for managing conflicts in construction projects is presented in this article where multiple decision makers are involved. The proposed negotiation methodology has a unique ability to consider the attitudes of the decision makers, which is an important psychological factor in the negotiations that take place in various stages of a construction project. The methodology is developed at the strategic level of decision making in which the graph model for conflict resolution (GMCR) is employed in assisting decision makers, such as project managers, to achieve the best strategic decision, given the competing interests and attitudes of the decision makers. A real-life case study is used to illustrate how the proposed methodology can be conveniently applied in practice and to demonstrate the importance and the benefits of incorporating the attitudes of multiple decision makers into the negotiation process in order to better identify the most feasible resolutions. The proposed negotiation methodology has been implemented in a negotiation decision support system that assists project managers in tackling real-world controversies, particularly in complex disputes that occur in construction projects.

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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.824
Threshold uncertainty score0.779

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.0010.001
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.059
GPT teacher head0.309
Teacher spread0.250 · 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