Critical Path Calculation

Hi,

I noticed that for tasks with planning modes in "Regular ...." are set to be not on critical path regardless of the dates. May you share the concept behind and more on the logic of critical path calculation?

I tried to change the condition in the code to not include the profile in "Regular ..." planning modes for setting task not on critical path, which then the tasks can be indicated as on critical path according to the dependencies and dates. May you advise if this modification with have other effects on other functions, reports or export? Thanks.

Rainbow

Hi Babynus,

Thanks for your reply. I agree that "Regular between dates" are supposed to be fixed tasks, which they should be constrained by the validated dates and allows to evenly distribute work assigned between two dates.

Regarding the statement:

So, as for the definition of critical path calcvulation, they should always be on critical path, but this has no meaning.

I found that even the "Regular between dates" tasks are on the critical path, it is not indicated in the Gantt chart by the red lines similar to other critical tasks. (I repeated the case in demo site - Project2a.)

As I cannot see the indications, I looked into the codes and tried to change to code to enable indication of the "Regular between dates" task which are on the critical path. However, I am unsure of any other impacts to the system as I haven't fully studied all the codes and logic yet. Therefore, would like to seek your advice as it is important for project management that the critical path to be identified to pay attention to for no delays.

Critical Path: The continuous string(s) of critical activities in the schedule between the Start and Finish of the project. The sum of the activity durations in the Critical Path is equal to the Project’s Duration; therefore, a delay to any Critical Activity will result in a delay to the Project Completion Date.

(www.pmi.org/learning/library/critical-pa...ions-scheduling-8040)

Ref:
en.wikipedia.org/wiki/Critical_path_method
en.wikipedia.org/wiki/Float_(project_management)

Thanks,
Rainbow

 

Hi Babynus,

In my experience, the planning mode "Regular between dates" are mostly used for tasks with float which the project manager would like to assign the task to start and finish at specific dates within the float. Especially when there is resource assignment for a task, sometimes the system calculated plan start and end dates considering the resource availability do not match with the desired dates by some project managers.

Moreover, if using the 'Fixed Duration' planning mode with resource over-allocation(i.e. assigned work for a resource exceed %) or under-allocation (i.e. work assigned is less than validated duration of task), the duration is often not planned as validated duration. For over-allocation, I understand that, while for under-allocation, sometimes it is not due to resource work but other factors such that the task need to start and finished on defined date.

Thanks,
Rainbow