MétaCan
Menu
Back to cohort
Record W4405398107 · doi:10.5267/j.jpm.2024.12.002

Resource-constrained project scheduling problem: Review of recent developments

2024· article· en· W4405398107 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

VenueJournal of Project Management · 2024
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceScheduling (production processes)Operations researchMathematical optimizationEngineeringMathematics

Abstract

fetched live from OpenAlex

The Resource-Constrained Project Scheduling Problem (RCPSP) remains a critical area of study in project management, focusing on optimizing project schedules under constraints such as limited resources and task interdependencies. This review synthesizes advancements from 2016 to 2024, encompassing problem variants, optimization techniques, objectives, and real-world applications. Key developments include the evolution of hybrid metaheuristics, multi-objective optimization approaches, and the integration of stochastic models to enhance robustness against uncertainties. Furthermore, the application of machine learning and sustainability-driven models has expanded the practical scope of RCPSP in dynamic and complex environments. Challenges such as scalability, uncertainty management, and the need for practical implementations are addressed, with future directions emphasizing AI integration, decentralized scheduling, and real-time adaptive solutions. This study provides a comprehensive perspective on RCPSP, bridging theoretical research with practical implications for diverse industries.

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.020
metaresearch head score (Gemma)0.003
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: Methods · Consensus signal: none
Teacher disagreement score0.921
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0200.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0030.005
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0020.001
Research integrity0.0000.001
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.134
GPT teacher head0.417
Teacher spread0.283 · 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