it’s not very easy to find relationship lag in primavera p6 project schedules. there aren’t really any features to highlight which relationships have lag or lead time.
but understanding how leads or lags are used on your primavera p6 project is a vital part of analyzing a project schedule.
we need a process to find relationship lag in primavera p6 schedule.
and i’m going to show you two.
what is a lag or lead in primavera p6
lag time is a duration that is added to a relationship link to impose a wait time between an activity and it’s successor in primavera p6.
if the lag is a positive duration, then the successor activity will have a wait period before starting.
if the lag is a negative duration (also called a lead or lead time), then the successor will overlap the predecessor activity.
lags can be applied to any relationship type to help you model your project’s work and any waiting periods between activities. lags are an inherent part of pert diagraming method (program evaluation review technique) that we use to build cpm schedules.
why you should avoid using relationship lag in your primavera p6 schedule
so here’s the deal with lag and lead times in primavera p6.
relationship lag is a very convenient tool to help us model our work in primavera p6. using lag on dependencies can be very helpful to add in periods of wait or non-work or even to create overlapping activities as in the diagram above.
however, the concensus and best practice is that the use of relationship lag should be minimal if it’s used at all.
why?
according to the practice standard for scheduling, a document prepared by scheduling experts at the project management institute, using relationship leads or lags add significant schedule risk to a project. the main reason is the lack of visibility of lag delays on project schedules. (pmi isn’t the only one with this recommendation)
lag time is hard to identify and document – it isn’t obvious when looking at the gantt chart or when analyzing a schedule’s dates.
when lag time is used on a schedule, schedulers very rarely document why the delay was added, causing construction managers to scratch their heads. time is money, after all.
as a best practice, any lag or lead should always be documented in a primavera p6 notebook topic on the activity.
or better yet, follow pmi’s standard and use full activities to represent lead or lag delays. this approach makes lags and leads very visible on a project schedule and also allows for more flexibility.
it’s common for less experienced planners to submit schedules with relationship lag. but be aware that your client may not accept your schedule. construction claims consultants will do the same.
in primavera p6, we really need to be able to find out if a schedule uses relationship lag.
unfortunately, inside the activity screens in p6, there seems to be no way to sort or filter activities by lag. so we need another approach, one that is easy and reusable.
can i use primavera p6’s new relationship details fields?
as of primavera p6 16.1, 2 new fields were added to primavera p6 to help get better visibility on relationship dependencies: predecessor details & successor details.
these 2 new fields were added to give the p6 activities screen a similar feel to microsoft project. the successor details field lists an activity’s successors, and also displays the lag or lead in format like this:
- a1205: fs +1d
- a2540: ss -3d
here’s a visual so you can see these 2 details fields in action:
while predecessor & successor details fields can help us gain some visibility on which activities have lags, it’s entirely a visual scan and search effort.
there is no infallable way to apply a filter to these fields to extract only those activities that have a lag or lead in their relationship. unfortunately, we have to resort to other tactics to see clearly the lags and leads in a primavera p6 schedule.
how to build a relationship lag report in primavera p6
fortunately, the reports section of primavera p6 has the ability to access and filter on the primavera p6 “lag” field.
it’s pretty easy to build reports in primavera p6. and the reporting features are able to report on a project’s relationships. using filters, we can create a nice report that shows only activities that have relationships with leads or lags. here’s how:
step 1 – create a new report
you don’t have to have a project open to do build this report.
navigate over to the primavera p6 reports screen: tools menu -> reports -> reports.
click the add button on the command bar, or right-click and choose add from the menu to add a new report to your primavera p6 database.
step 2 – choose the report subject
when the report wizard comes up, click next to create a new report. on the following screen, select the “activity relationships” subject area and click next.
step 3 – choose columns
select the columns as shown. click ok.
**note: i’ve discovered that both the “predecessor id” and “successor id” columns will always be renamed by primavera to “activity id” in the output of the report. if you click ok after selecting columns and go back to the column choosing screen, these two columns are renamed to “id”. i can’t change them either….c’est la vie!
step 4 – turn off group and sort
click the group and sort button and set it to <none> or leave the group by field blank. click ok.
step 5 – set a custom p6 filter to find lag
click the “filter…” button. in the parameter dropdown, find and select “lag”.
set the conditional dropdown to “is not equal to” and type ‘0’ in the value column.
this combination will filter for both lags and leads (ie: negative lags).
click ok to save your filter.
step 6 – save your primavera p6 relationship lag report
click next.
on the following screen, name your report “relationship lag report”. click next.
before you click run report on the report generated screen, click next again and save your report. click finish to close the wizard.
it’s ideal to save your report first before running it. it may not run if you do not have a project open first.
step 7 – open a project and run the primavera p6 lag report
open a project and then run your report from the reports screen.
to run the report, right-click on the report name and choose run -> run report from the pop-up menu.
you will see a lag report that looks similar to the above screenshot.
step 8 – [optional] send the report to excel for more filtering abilities
some people don’t know that you can send primavera p6 report data to a .csv file to open in excel. excel will have more filtering features for you to use on the data, so it can be really handy.
when you the run the report, rather than choose the default print preview option, choose “delimited text file” and specify a filename.
open the .csv file in excel and enjoy!
conclusion
having this report pre-built will help you be prepared anytime you need to run some analysis on a schedule, perhaps even a schedule a contractor has submitted. so keep it in your arsenal of analysis tools.
it’s worth mentioning that another approach that works is to export your project data to an excel .xls using file->export, including the relationships table.
you can then use the filtering tools in excel to filter relationships that have lead or lag delays.
i prefer to avoid excel in this case because the export takes too many clicks to produce the report. my p6 report can be run with 3-4 mouse clicks max with the same end result.
if you must use lags on your schedule, go ahead. unless your client refuses to let you use them, you are welcome to use lags on your schedule.
however, my recommendation is to use them sparingly. finding lags on your schedule is not the only issue you will encounter with lags, there are others i won’t go into here. the key here is to 1) be aware, and 2) document document document.
editor’s note: this post was originally published may 2012 but has been completed updated and revamped for completeness and accuracy.
