Autoscheduling without Resource Constraints still checks resources

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Autoscheduling with the Resource Constraints option disabled still takes into account resource properties.

Steps to Reproduce:

1. Create a new project, and add a team member.
2. Create two tasks (e.g.: one from 6/1/23 to 7/31/23, and another from 7/1/23 to 8/31/23) and assign the team member to both.
3. For each of the two assignments, edit the ETC Detail and edit so that a full week in common, the ETC is 0 (e.g.: 7/17/23 to 7/21/23).
4. Allocate from Estimates this team member.
5. Autoschedule the project with an autoschedule date of 7/17/23, with Resource Constraints enabled.

Expected and Actual Results: A tentative schedule is proposed where the two tasks are not overlapping, and the start date is 7/24/23 (it skips the week with no allocation).

6. Delete the tentative schedule and repeat the same autoschedule with Resource Constraints disabled.

Expected Results: As resource constraints are not taken into account when autoscheduling, the two tasks overlap and start on 7/17/23.

Actual Results: The two tasks overlap, but start on 7/24/23.

Environment

Release : 16.0.0

Cause

DE70077

Resolution

Autoschedule and Resource Constraints

If you clear the check box, Autoschedule treats resources as if they have unlimited availability. Each task is scheduled against the total availability for the resource, but not against the remaining availability for the resource which takes other task assignments into consideration. This results in the shortest possible schedule, but it can also cause over-commitment of resources.