Context
RCPSP, MSRCPSP, research gap and contribution.
G09
Project Control
Research presentation · Group G09
IEEE Access · Volume 12 · 2024
A Greedy and Parallel Scheduling approach for reducing project makespan through proficiency-aware assignment, parallel task groups, and active reuse of free resources.
Presented by
Course Instructor
Prof. Mohsen VarmazyarPresentation roadmap
RCPSP, MSRCPSP, research gap and contribution.
Task graph, weighted skills, notation, objective and constraints.
Five coordinated algorithms in the GPS scheduling loop.
Seven simulation experiments against the PSS benchmark.
Interpretation, limitations, future work and takeaways.
Problem evolution
The paper studies software projects in which activities are linked by precedence, people possess several skills, and proficiency differs by person and skill.
Schedule activities under renewable resource limits and dependency constraints.
Every task requires skills; every human resource masters one or more skills.
Skill proficiency is heterogeneous and represented by values in the interval \([0,1]\).
Related work and gap
Can model multiple objectives and constraints, but become computationally demanding as problem size grows.
Produce solutions quickly, but do not guarantee optimality and often simplify resource capability.
Explore large search spaces, yet many studies assume homogeneous proficiency or limited collaboration.
Research objective and contribution
Select the available resource with the highest matching skill proficiency.
Partition the precedence graph into dependency-safe subsets that can execute concurrently.
Assign spare resources to the latest-finishing scheduled task to reduce its finish time.
When the earliest task finishes, redirect its resources to remaining tasks in the same group.
Problem setup
Tasks inside the same parallel subset have no precedence relation with one another.
Task set:
\(T=\{t_0,t_1,\ldots,t_n,t_{n+1}\}\).
Directed acyclic graph of task precedence relations.
Dummy start and dummy end tasks.
Total effort and task duration used by the scheduling model.
Notation · sets and task state
Notation · resources and timing
Model inputs
\(t_i s_j\in\{0,1\}\)
A value of \(1\) means task \(t_i\) requires skill \(s_j\).
\(r_k s_j\in[0,1]\)
The value expresses the proficiency of resource \(r_k\) in skill \(s_j\).
Illustrative feasible match: if \(t_1\) requires \(s_1\) and \(w_{r_2s_1}=0.9\), then \(w_{r_2s_1t_1}=1\) records the assignment.
Mathematical formulation · objective and constraints (2)–(4)
The start time of the dummy end node represents project completion.
A successor starts only after its predecessor finishes.
The assignment satisfies the required headcount for each task–skill pair.
For a given task, one resource contributes through at most one skill.
Mathematical formulation · constraints (5)–(9)
Every project task requires at least one skill.
At least one resource performs every project task; the published qualifier is typographically ambiguous.
Start times and durations are non-negative.
Published notation is ambiguous; the prose intends assigned resources to possess skills required by the task.
Finish time equals start time plus duration.
Notation verification
The problem-formulation paragraph calls \(d_{t_i}\) a deadline, but Table 1, Equations (2), (7), (9), and the algorithm discussion use it as task duration. The slides use “duration.”
Constraint (4) directly limits one skill contribution per resource for a given task. The broader “one task at a time” claim appears in prose and is not overstated as a standalone mathematical guarantee.
The results prose points to Figures 7 and 8 for Experiments 6 and 7. Their actual captions are Figure 8 (duration) and Figure 9 (resource demand), which this presentation follows.
GPS framework
Orchestrate groups
Extract independent tasks
Advance by completion events
Choose maximum proficiency
Accelerate latest finisher
Algorithm 1 · Top-level orchestrator
Algorithm 2 · CreateParallelTasksGroups
Algorithm 3 · ScheduleTasksSubset
Algorithm 4 · AssignResources
Algorithm 5 · AssignExtraResources
Why GPS can shorten a parallel group
A finishes first; its assigned resources become available.
Freed and surplus resources are redirected to reduce the latest finish.
Simulation setup
All six factors are sampled within the reported ranges.
One factor varies while the other five remain fixed.
Benchmark: Parallel Scheduling Scheme (PSS), selected by the authors for its relevance and established use.
Experiment 1 · Random projects
The paper separately reports “average completion gap” values of 9.80 days for GPS and 2.88 days for PSS without defining them as the direct difference. The headline comparison therefore uses \(58.96-50.42=8.54\) days.
Sensitivity results · Experiments 2 and 3
Sensitivity results · Experiments 4 and 5
Sensitivity results · Experiments 6 and 7
Synthesis of experimental evidence
Critical assessment
Weighted best fit and event-driven resource reuse directly target the two gaps identified by the authors.
Six sensitivity experiments explain the conditions under which the advantage expands or contracts.
No industrial case study or real project dataset is reported.
The study does not establish superiority against a broad set of contemporary exact and metaheuristic methods.
Costs, uncertainty, skill evolution, switching, preemption and broader allocation constraints are outside the evaluated model. The paper also does not provide a formal computational-complexity analysis.
Several formulas and result references need careful interpretation, as documented earlier in this presentation.
Conclusion
GPS combines a greedy best-fit rule with parallel scheduling and repeatedly reassigns surplus or newly freed resources to reduce the latest finish time.
Heterogeneous skill weights produce more realistic resource selection than interchangeable-capacity assumptions.
The principal operational gain comes from keeping resources productive while parallel tasks finish at different times.
Across the reported simulations, GPS achieves a lower makespan than PSS in almost all tested settings.
G09Group G09 · Project Control