(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.
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
Printer-friendly version
Send to friend
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
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.
Email: PPadmin@planningplanet.com
Replies