have you ever had a primavera p6 situation where all predecessors of an activity are 100% complete but the activity’s start date isn’t pushed to the data date as expected? similarly, you might also see the activity’s finish date is much later than the it’s remaining duration from data date? if you answered yes then this quick tip might help you find the offending activity cause these problems.
the problem
to illustrate this problem with out-of-sequence activities in primavera p6, let’s have a look at this schedule with data date of 02-aug-16.
there are 2 activities with unexpected dates, dummy activity 05 and dummy activity 06, so let’s investigate further. if i select dummy activity 05 and have a look at the predecessors of this activity in the details form, it clearly shows that all the predecessors to dummy activity 05 are completed, therefore one would expect dummy activity 05 to have a start date of 02-aug-16 and not 09-aug-16.
following same steps, dummy activity 06 should have a finish date of 15-aug-16 and not 22-aug-16 since all its predecessors are also completed.
these 2 scenarios normally prompts the question; “why are the dates not as expected”?
the simple answer is that these activities were executed in an order different than the order we had planned (called out-of-sequence progressing). at the same time, we’re using a scheduling setting in primavera p6 called retained logic. retained logic handles how primavera p6 will schedule progressed activities and in the case where activities are progressed out-of-sequence, p6 will ensure the schedule still retains the original logic between activities.
the solution
a way to trace the activity or activities currently driving the dates of dummy activity 05 and dummy activity 06 is to add 2 fields to the predecessors section of the relationships tab of the details form: early start and early finish.
all activities that are 100% complete should have early start and early finish dates on same date as the data date, therefore any completed predecessor with early start and/or early finish dates other than the data date is the offending activity causing dummy activity 05 and dummy activity 06 to display wrong dates.
from image above, dummy activity 04 has early start and early finish dates of 08-aug-16 despite been 100% complete, therefore pushing the start date of dummy activity 05 to 09-aug-16.
if we check dummy activity 04, we will notice that its predecessor, dummy activity 01, is still in progress with an early finish date of 08-aug-16 and it is this date that has been cascaded to dummy activity 05 based on retained logic setting.
now that i have found the offending out-of-sequence activity.
changing the relationship logic between dummy activity 01 (which is still in progress) and dummy activity 04 (which is 100% complete) from fs to ss should solve the problem as shown in the figures below.
the start date of dummy activity 05 is now 02-aug-16 as expected and also the finish date of dummy activity 06 is also now 15-aug-16 as expected. similarly the early start and early finish dates of all the completed predecessors are now 02-aug-16 as expected.
conclusion
i know that after tracing the out-of-sequence activity, i then changed the relationship type from finish-to-start to start-to-start. but before you follow suit, it is best you do the following:
- check that the project’s planning procedure to see if your specification allows changing of activities relationship logic post-baseline.
- check with the project engineers to find out what the revised relationships for the out-of-sequence activities should be.
finally, i hope you have found this quick tip useful and as always i would welcome your comments below. what do you think?
