all project controls professionals know how critical is it to monitor our project’s critical path. and we all know that comparing our project performance to a baseline is also essential. most of us are doing this critical path and baseline monitoring in primavera p6 every day. but what about monitoring our project’s critical path vs our baseline critical path in p6?
of course, as we execute a p6 schedule, over time, the schedule will diverge from it’s baseline. the myriad of changes, out-of-sequence fixes, late or early work will be inevitable. and it will happen that those changes will also affect our original critical path.
are we able to check our path and compare it to the baseline critical path in p6?
the answer is yes.
although comparing 2 projects usually involves a tool like claim digger or change inspector, it’s possible to do a visual comparison of current project vs the baseline using the p6 gantt chart. but here are the steps needed to let you compare your critical path to your baseline’s critical path.
displaying the baseline critical path in p6
let’s start by assuming we have a well-built project schedule that has not yet started. we have created a baseline and assigned it as a project baseline in p6.
in the gantt chart shown above, the thicker bars represent the current project schedule while the slimmer bars below the thicker bars are for the baseline schedule. the thick red bars show the critical activities in the current schedule. it is possible to display baseline bars in red to highlight the baseline critical path activities.
step 1 – setting a baseline filter
before we set the bars, let’s set-up a filter which we will use to reference the baseline total float. the filter, called baseline critical has the settings bl total float is less than or equals 0d. (note: you must have a project baseline assigned to your project in order to be able to pick the field bl project total float. otherwise, this field is not available.)
click ok to save the filter and exit the filter window. we will need this filter for later.
step 2 – add a bar to the gantt chart settings
in order to display the baseline critical path in p6, we’ll start with the default “classic wbs layout” is an activity layout that ships with p6. it’s already set up to display current critical activities. i recommend you can save a copy of this layout as we will make changes to it. (ps: don’t forget these must-have layouts for everyday p6 excellence.)
once done, from the p6 menu, click on views >> bars to open the bars dialog box.
click on the add button and this will add a new row of bar option as shown below.
under the name column of the bars dialog and in the newly created row, double-click and type the name baseline critical as shown below.
on the new baseline critical row and under the timescale column, select project baseline bar from the dropdown menu as shown below. this step makes sure the bar pull data from the project baseline that set for your project.
step 3 – setting a filter for the baseline critical path bar
we’re getting closer to displaying the baseline critical path in p6. on the new baseline critical row and under the column filter, click the words all activities and this will open a new filters dialog.
ensure that all selected filters is selected under the show activities that match option (arrow 1) and the replace activities shown in current layout is selected under when applying the selected filters(s): (arrow 2). tick the baseline critical filter we created earlier (arrow 3). now, click on the apply button (arrow 4) and then ok button (arrow 5) to close the filter dialog.
step 4 – setting the bar style
still with the new baseline critical row selected, under the bar style (see image below), change the shape to a slimmer bar (arrow 1); change color to red (arrow 2) and then change row to 2 (arrow 3). a look at the preview column will show a slimmer red bar for our new baseline critical row (arrow 4).
now click apply and then ok in the bars dialog to return to our gantt chart. let’s check the results.
we can now clearly see that some of the baseline bars are showing red. those red bars are displaying the baseline’s critical path.
baseline critical path in p6 : doing a visual comparison
our gantt chart does not show any changes from the original gantt chart we started with in the first image of this post and that is because the our current schedule in this example has not changed from the baseline schedule.
therefore, assuming that after further review, the project team has decided to revise some activities duration thereby changing the current schedule’s critical path. the gantt chart below shows how this new critical path differs from the baseline critical path in p6.
doing a visual scan of the current & baseline bars, our current critical path is now showing much different from the baseline critical path. the result is very useful. as we work in our schedule, we can now monitor whether changes we make are triggering a change in our critical path as compared to our baseline critical path.
conclusion
it’s not easy to notice when the changes you make to a schedule are altering your project’s critical path. it can sometimes catch you off-guard. as you become really familiar with a schedule, you’ll know where the project’s critical path lies; you’ll know that it runs through phase 1, area c and then through coat pipelines. you’ll just know because you’ve stared at the project for so long.
but you shouldn’t have to rely on your memory.
this method seems to be the easiest and most reliable way to show the baseline critical path in p6; right in p6 and not by exporting and running a comparison in some other tool.
i hope you find this post useful and if you’ve come up with another method of comparing baseline & current critical paths, please share it with us.
