{"id":7900,"date":"2018-01-23t10:01:44","date_gmt":"2018-01-23t15:01:44","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=1184"},"modified":"2021-10-08t14:19:18","modified_gmt":"2021-10-08t18:19:18","slug":"find-relationship-lag-primavera-p6","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/find-relationship-lag-primavera-p6\/","title":{"rendered":"how to find relationship lag in primavera p6"},"content":{"rendered":"

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.<\/p>\n

but understanding how leads or lags are used on your primavera p6 project is a vital part of analyzing a project schedule.<\/p>\n

we need a process to find relationship lag<\/a> in primavera p6 schedule.<\/p>\n

and i’m going to show you two.<\/p>\n

what is a lag or lead in primavera p6<\/h2>\n

lag time is a duration that is added to a relationship link to\u00a0impose a wait time between an activity and it’s successor in primavera p6.<\/p>\n

\"lag
b will wait 4 days after a is finished to start<\/figcaption><\/figure>\n

if the lag is a positive duration, then the successor activity will have a wait period before starting.<\/p>\n

if the lag is a negative duration (also called a lead or lead time), then the successor will overlap the predecessor activity<\/a>.<\/p>\n

\"lead
b will start 2 days before a’s finish date creating an overlap<\/figcaption><\/figure>\n

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.<\/p>\n

why you should avoid using relationship lag in your primavera p6 schedule<\/h2>\n

so here’s the deal with lag and lead times in primavera p6.<\/p>\n

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.<\/p>\n

however, the concensus and best practice is that the use of relationship lag should be minimal if it’s used at all.<\/p>\n

why?<\/p>\n

according to the practice standard for scheduling<\/a>, a document prepared by scheduling experts at the\u00a0project management institute<\/a>, using relationship leads or lags add significant schedule risk to a project. the main reason is the lack of visibility <\/strong>of lag delays on project schedules. (pmi isn’t the only one with this recommendation<\/a>)<\/p>\n

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.<\/p>\n

when lag time is<\/span> 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.<\/p>\n

as a best practice, any lag or lead should always be documented in a primavera p6 notebook topic on the activity.<\/p>\n

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.<\/p>\n

\"example
an example of replacing a lag with an activity in primavera p6<\/figcaption><\/figure>\n

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.<\/p>\n

in primavera p6, we really need to be able to find out if a schedule uses relationship lag.<\/p>\n

unfortunately, inside the activity screens in p6, there seems to be no way to sort or filter activities by lag. \u00a0so we need another approach, one that is easy and reusable.<\/p>\n

can i use primavera p6’s new relationship details fields?<\/h3>\n

as of primavera p6 16.1<\/a>, 2 new fields were added to primavera p6 to help get better visibility on relationship dependencies: predecessor details & successor details.<\/p>\n

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:<\/p>\n