In MSP 2003, working days in lag relationships are computed based on the Successor Activitys calender. This defaults to the Project Calendar if no other calendar is specified for the successor activity. (I think P3 uses the Predessesors calendar).
[This is a correction I just learned today, so I thought Id post it for the record.]
BR, tom
Member for
19 years 5 months
Member for19 years6 months
Submitted by Ioannis Leontiou on Mon, 2006-05-15 17:27
Member for
24 years 6 monthsRE: Lag’s Calendar
There are two other options for lags:
Elapsed lags, say FS+10edays will give you an elapsed lag ignoring the Successor calendar.
Percent Lags, say FS-50% which will allow the successor to start 50% through the duration of the predecessor.
P3 and SuerTrak use the predecessor calendar but Primavera Enterprise gives several options.
Paul E Harris
Eastwood Harris Pty Ltd, Melbourne, Australia
Planning and Scheduling Training Manual & Book Publishers & Consulting
www.eh.com.au
Member for
18 years 11 monthsRE: Lag’s Calendar
In MSP 2003, working days in lag relationships are computed based on the Successor Activitys calender. This defaults to the Project Calendar if no other calendar is specified for the successor activity. (I think P3 uses the Predessesors calendar).
[This is a correction I just learned today, so I thought Id post it for the record.]
BR, tom
Member for
19 years 5 monthsRE: Lag’s Calendar
It uses Default Calendar, Unless yuo had configured and assign a Task Calendar for the tasks reference to
Member for
20 yearsRE: Lag’s Calendar
Thanks Ronald.
Im not a MSP user ... so i dont use to read MSP threads ... thats why i didnt know about that.
Thanks again.
Regards.
Marcio Eduardo
Member for
22 years 10 monthsRE: Lag’s Calendar
I have been told that MS Project lags are calculated using the Default Calendar.
Member for
20 yearsRE: Lag’s Calendar
And where can I configure this??
Thanks