MétaCan
Menu
Back to cohort
Record W1999268031 · doi:10.1139/l01-058

A structure for government requirements in publicprivate partnerships

2001· article· en· W1999268031 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2001
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicPublic-Private Partnership Projects
Canadian institutionsnot available
Fundersnot available
KeywordsGeneral partnershipProcurementGovernment (linguistics)Private sectorNegotiationPublic–private partnershipBusinessDimension (graph theory)Public sectorFinancePublic administrationEconomicsMarketingEconomic growthPolitical scienceLaw

Abstract

fetched live from OpenAlex

A spectrum of requirements for the procurement of public infrastructure under various public–private partnership arrangements has been communicated by governments to the private sector participants. This paper suggests a structure for these requirements and demonstrates how they have been realized in public–private partnership projects. Government requirements are categorized and described under a structure of three dimensions: rights, obligations, and liabilities. Each dimension is further defined and explained through a number of attributes. The structure provides insights as to the basis for the different modes under public–private partnerships such as build–operate–transfer, build–own–operate–transfer, and build–transfer–operate. The structure is used to examine government requirements in a number of public–private partnership transportation projects. The results show that, for each dimension and its related attributes, comprehensive and clear articulation of government requirements is generally needed. This will reduce the amount of supplemental materials issued for the request for proposals, help consortiums in responding with proposals that can fit the requirements and reduce the amount of time spent in negotiations and (or) the need for contract amendments to reflect marketplace realities missed earlier.Key words: public–private partnerships, concessions, development agreements, franchise agreements, transportation 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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.876
Threshold uncertainty score0.872

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.002
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.045
GPT teacher head0.226
Teacher spread0.182 · 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