MétaCan
Menu
Back to cohort
Record W2810704612 · doi:10.1177/875697280003100202

Project Management and Communication of Product Development through Electronic Document Management

2000· article· en· W2810704612 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 · 2000
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicQuality Function Deployment in Product Design
Canadian institutionsRoyal Military College of Canada
Fundersnot available
KeywordsDocument management systemProject managementKnowledge managementWorkflowProcess managementNew product developmentComputer scienceBusiness process reengineeringEngineering managementBusinessEngineeringSystems engineeringOperations managementLean manufacturing

Abstract

fetched live from OpenAlex

While the literature on project management and product development is voluminous, in reality little of it addresses the questions of document management of new organizational procedures to increase project development productivity, and of software development tools required to support and control these procedures. This research study develops a new methodology to integrate project management (activities, milestones, and resources) and document management (responsibilities, authorizations, workflows, archives, and storage). The aim of the integration is threefold. First, it aims to plan and to control activities and documents essential for product development. Second, it aims to ensure the management of documents in terms of responsibilities, authorizations, dissemination, and storage. And third, it aims to trace and locate documents for any type of product. Further, this study shows the value of electronic document management (EDM) in terms of improving the management and communication of concepts and ideas, whether it be for project teams or organizations, for reengineering basic business processes, or for leveraging long-run organizational memory through documents.

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.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Other · Consensus signal: none
Teacher disagreement score0.847
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0010.000
Scholarly communication0.0010.002
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.029
GPT teacher head0.270
Teacher spread0.240 · 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