Skip to content
ProjectControls.com
Oracle Primavera - PM6

Maintaining a Continuous Critical Path While Using a 24-Hour Calendar for Relationship Lag

In the Open Standard
Emily FosterMember for 15 years 2 months
Created
2
2
0

Defining a 24 Hour Calendar for scheduling relationship lag works well to schedule the seven day weekly curing of material. The critical activity definition, however, may require adjustment. If you are not monitoring activity constraints then define critical activities as longest path. Here we look into this more http://ow.ly/JL6V3087oIl

Save Follow Follow forum Report
Reply New topic

2 replies

Oldest first
  1. 0
    David Kelly ·
    #1

    I would like to add something

    I would like to add something to an excellent article.

     

    I am a “longest path” fan, and recommend “24 hour calendar” for lag to all of my students. Many of my clients work with several complex activity calendars with variable working hours per day. I would recommend entering the lag in hours, rather than days. All durations in P6 are held in hours, such that if you enter a duration of a lag in days, P6 will multiply the number by a calendar dependent constant and schedule that number of hours, NOT the number of days you entered. Rather than risk an unwelcome multiplication, enter the lag in hours. P6 lets you type “24h” into a duration field even if your current user preference is set to Days.

     

     

    Report
  2. 0
    Emily Foster ·
    #2

    hi David, Thakns for the

    hi David,

     

    Thakns for the positive feedback. I've added a paragraph just under Figure 2 which incorporates your point and makes it read a little better.

    Thanks,

    Emily

    Report

Log in or join to reply

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

Log inJoin free

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