Skip to content

Primavera Can’t do this. Getting desparate

David KellyMember for 21 years 11 months
Created
5
4
0
Can Open Plan do this?

Resource levelling and mandatory lag

Example.

A work instruction becomes an activity in P6.

Work instruction “a” is an isolation of a piece of equipment.

Work instruction “b” is the work to be performed when the isolation has been performed.

It is essential that the work is performed immediately after the isolation is performed.



A finish-to-start relationship does this very well when scheduling. Unfortunately since there is no “mandatory lag” capability in P6, when the project is levelled, there is no way to ensure that activity “b” follows immediately after activity “a”.

Any Ideas team?

5 replies

Oldest first
  1. 0
    Gary Whitehead ·
    I’ve never levelled in Open Plan and now I don’t have the software to try it out, so can’t help you there.

    Would a work-around be to combine instructions a and b into one? Maybe with a zero-resource activity acompanying if you need to show the specific isolation date?
  2. 0
    Vladimir Liberzon ·
    In Spider Project it is called strong link.
  3. 0
    Keith Courneyea ·
    In Open Plan set Resource Scheduling ’Type’ on the Advanced tab of the Activities dialog box to the value of ’Immediate’. This will cause the activity to be scheduled immediately after it’s logical predecessor. Use this sparingly.

    Keith
  4. 0
    Rafael Davila ·
    If your software, Open Plan or P6 have zero float constraints as Suretrak does then you can schedule the successor activity with a f-s link from the predecessor along with a zero float constraint then with a lag on this link you probably will get a mandatory lag.
    To see if this holds true after resource leveling try it in your software, then run the resource leveling and let us know.
  5. 0
    Jorge Payne ·

    Have activity 'B' be the

    Have activity 'B' be the FS predecessor to activity 'A'.  Then apply a lead equal to the duration of B + 1.  Now if activity B gets postponed by other predecessors, A gets pulled along also "just in time".  Notice that A will never drive B since its not a predecessor, but its early dates will always immediately preceed B.  This works whenever you have an activity with shelflife.

Log in or join to reply

ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.

Existing members: your original username and password still work. Forgot password?