Primavera P6 en het langste pad
Er komt meer kijken bij het tonen van hét kritieke pad in Primavera dan je projectmanager zich kan voorstellen. Met Primavera kan je bepaalde instellingen wijzigen om om te definiëren welke activiteiten kritiek zijn: je kan een drempelwaarde voor de totale float definiëren of kiezen voor het langste pad in plaats van een op total float-gebaseerd kritiek pad.
Waarschijnlijk ben je geïnteresseerd in alle activiteiten die een bepaalde mijlpaal behalen. En het is veel logischer om het langste pad naar deze mijlpaal te bewaken in plaats van het kritieke pad bepaald door totale float. Deze zeer nuttige optie is echter een beetje verborgen in Primavera P6 en ik wil het graag met je delen! Het is een methode die ik gebruik voor ELK PROJECT. Deze blog is engelstalig.
Total Float vs Longest Path
Standard settings in Primavera P6 define critical activities as activities with “Total Float less than or equal to 0” (ref. red rectangle in picture below). One can choose to change this “0” to any positive or negative value according to the analysis in mind.
A second option is to choose for the ‘Longest Path’ option to define activities’ criticality. In this case, activities will be critical if they are part of the path of driving relationships towards the activity or activities with an early finish date which is the same as the calculated early finish date of the project (ref. blue rectangle in picture above). In many cases, the longest path option allows for a more useful analysis since it better deals with multiple calendars and constraints. However, this basic feature only offers the possibility to show the path towards the ‘last’ activity or activities of the project.
Longest path towards ANY activity
Would it not be a great idea to use this longest path method towards ANY activity? Well fortunately, it is possible and can be done in just a few steps:
Go to the ‘Advanced’-tab in Schedule Options and apply settings as per the red rectangles in the screenshot below. You can ignore ‘Specify the number of paths to calculate’.
Choose the activity for which you want to analyse the longest path (ref. blue rectangle in the screenshot above).
Click ‘Close’ and then ‘Schedule’ (ref. screenshot below)
Create and apply a filter named ‘Float Path = 1’ as per illustration below:
And that is it! Primavera P6 will only show you now the longest path towards the activity of your choice!
Note: you cannot use the built-in filter ‘Longest Path’ or the built-in attribute ‘Longest Path’ to create your own filter as this will only work for the longest path towards project finish (ref. picture below)
Not what you expected?
You can’t find what I’ve promised? The bullet points below will most probably provide the explanation:
- You don’t see any activities except for the chosen activity:
The activity has no predecessors, is bound by a constraint or has a driving predecessor in another project.
- The longest path doesn’t go back to the data date:
The first activity of the longest path is bound by a constraint or a driving predecessor in another project.
- There are time gaps in the longest path:
This is exactly what you want! This is caused by the use of multiple calendars and proves that the longest path can deal with this. Driving relationships are taken into account instead of total float for determining the path.
- There are activities with driving relationships that are not shown:
Aah, you’ve found a good one! Unfortunately, this method can only show one path towards an activity. So even if 2 or more activities are driving on this path, only one of them will be shown. When using the Primavera P6 built-in features (ref. ‘Note’ in the previous paragraph), all these activities will be shown, but then the drawback is that this only works towards the final activity / activities. With some manipulations (to e.g. durations or lags) you could temporarily take some activities off the longest path after which the missing ones will appear for further analysis.
One of the benefits of using total float to define criticality, is that you have a metric to also monitor activities which are near-critical. The most important activities to monitor are the ones with no float, but of course you want to keep an eye on activities with very limited total float as well.
Analogue to this and related to the longest path method, we can refer to sub-critical float paths that can be displayed as well. To depict the float paths that are less critical, you can use the option ‘Specify the number of paths to calculate’ which I told you to ignore under ‘Step 1’. For more details regarding this matter, you’ll have to come back to this website for a future blogpost.
It is surprising that in Primavera P6, you need somewhat of a workaround for a very useful method as described above. The vast majority of project planners will merely submit a list of activities with no (or limited) total float when asked to perform a critical path analysis (by using the standard functionality of Primavera P6). In many situations, this won’t provide sufficient insights to the project management team and / or the project owner to fully understand the schedule’s criticality and adequately steer the project’s execution. The longest path method, and some extra clicks as described in this blogpost, will add a great deal of clarity to accomplish the desired project goals.