here is a description of this problem i found on google groups which matches my situation... has anyone found a solution to this? In short, if i manually enter leveling delay or let project do leveling, and then i baseline, the baseline copies the right start date, but then changes the current start date to the start date at time of leveling + leveling delay. what? i think it should just take a copy. the schedule should not change when i save a baseline. this problem can be recreated by creating two 8 hour tasks, telling project to level, and then saving a baseline. you can also just add the levelling delay and do the levelling yourself. you'll be surprised by the post-baseline state.. in fact, it even moves a tasks end date to a point beyone the end date listed for the phase/summary task that the task is part of. ?!
The Spaniard Jul 6 2004, 10:30 pm show options
Newsgroups: microsoft.public.project.pro_and_server
From: "The Spaniard" <thespaniar...@hotmail.com> - Find messages by this author
Date: Wed, 07 Jul 2004 05:30:58 GMT
Local: Tues, Jul 6 2004 10:30 pm
Subject: Baselining postpones the start of leveled tasks?! What's happening?
Reply to Author | Forward | Print | Individual Message | Show original | Report Abuse
Has anyone come across this problem?
I'm having the following issue in MS Project 2002 Professional/Enterprise
Server. After assigning a resource to several tasks that have the same
predacessor task and could logically start simultaneously, the resource
is, predictably, overallocated.
By choosing the resource sheet view, highlighting the resource, choosing
tools, leveling, level selected resource, Project adds values to the
Leveling Delay Column on the Entry Table/Gantt View and shifts each task
alleviating the overallocation. GREAT! Exactly what I was trying to
accomplish.
Now I choose to baseline the selected tasks which results in an unexpected
behavior in the program. Each task that has a value in the Leveling Delay
Column is pushed out into the future by the precise amount of elapsed time
indicated in the Leveling Delay Column. The outcome is that five one day
tasks that had been leveled to fill one week of duration become staggered
out over five weeks!
As I understood baselining, it simply copies current
start/finish/duration/cost etc. fields to corresponding baseline versions
of those fields, a passive activity I thought.
Is this a bug? Any insight would be much appreciated.
One additional note - The Leveling Delay added by the leveling function
adds values only to the column mentioned above. Individual assignment
delay, and plain old delay, are not affected (the values seen in a split
window with resource schedule view chosen). Will the real delay please
stand up.
The Spaniard Jul 6 2004, 10:30 pm show options
Newsgroups: microsoft.public.project.pro_and_server
From: "The Spaniard" <thespaniar...@hotmail.com> - Find messages by this author
Date: Wed, 07 Jul 2004 05:30:58 GMT
Local: Tues, Jul 6 2004 10:30 pm
Subject: Baselining postpones the start of leveled tasks?! What's happening?
Reply to Author | Forward | Print | Individual Message | Show original | Report Abuse
Has anyone come across this problem?
I'm having the following issue in MS Project 2002 Professional/Enterprise
Server. After assigning a resource to several tasks that have the same
predacessor task and could logically start simultaneously, the resource
is, predictably, overallocated.
By choosing the resource sheet view, highlighting the resource, choosing
tools, leveling, level selected resource, Project adds values to the
Leveling Delay Column on the Entry Table/Gantt View and shifts each task
alleviating the overallocation. GREAT! Exactly what I was trying to
accomplish.
Now I choose to baseline the selected tasks which results in an unexpected
behavior in the program. Each task that has a value in the Leveling Delay
Column is pushed out into the future by the precise amount of elapsed time
indicated in the Leveling Delay Column. The outcome is that five one day
tasks that had been leveled to fill one week of duration become staggered
out over five weeks!
As I understood baselining, it simply copies current
start/finish/duration/cost etc. fields to corresponding baseline versions
of those fields, a passive activity I thought.
Is this a bug? Any insight would be much appreciated.
One additional note - The Leveling Delay added by the leveling function
adds values only to the column mentioned above. Individual assignment
delay, and plain old delay, are not affected (the values seen in a split
window with resource schedule view chosen). Will the real delay please
stand up.