S
Stuart Penning
I have found that baseline data gets corrupted when the tasks are moved in
schedules that have been baselined.
To reproduce the problem, do this in a new project:
1. Create 1 summary task, having one sub task (1 day will do).
2. Create a resource with a cost per hour ($1 will do) and assign that
resource to the sub-task.
3. Baseline the whole project and save.
4. Set the project status date to the day before the summary task start date
(EVM calcs are done based on this date).
Now, switch to the EVM table in the Gantt chart view and add the CPI and SPI
columns. The CPI and SPI will be 0 on summary and sub-task - this is correct.
Open the bottom pane so that you have a combination view with the top being
the Gantt chart with the EVM table and the bottom being the standard task
usage view. Add the actual work row to the task usage pane. Now you should be
able to see 8 hours work and a blank for actual work, on the day for the
subtask.
Select the sub-task. Enter an amount of hours equal to the work value, into
the actual work row, on the expected date for the subtask (in the task usage
pane). Now change the status date to the last date and observer that the CPI
and SPI calculations are correct and both show as 1.
Move the subtask to the top of the list of tasks, so that it is the first
task and not a sub-task any longer. You will notice the CPI and SPI values
are now wrong.
If you have a large project, with many levels and you do this to re-organise
the project, the CPI and SPI values are useless and cannot be used for EVM.
This problem also corrupts the EVM Olap cube extension data.
The obvious solution to re-baseline the project does !NOT! work becuase the
re-baseline algorithm takes the actuals that have been entered and uses them
for the new baseline. If you do this, you loose your baseline infomation
completely, for tasks that contain actual values.
Please help - I think MS might need to produce a bug fix, but I am not sure...
This problem is preventing my company (a very large IT consulting company)
from using MS Project and Project server for Earned Value Management.
schedules that have been baselined.
To reproduce the problem, do this in a new project:
1. Create 1 summary task, having one sub task (1 day will do).
2. Create a resource with a cost per hour ($1 will do) and assign that
resource to the sub-task.
3. Baseline the whole project and save.
4. Set the project status date to the day before the summary task start date
(EVM calcs are done based on this date).
Now, switch to the EVM table in the Gantt chart view and add the CPI and SPI
columns. The CPI and SPI will be 0 on summary and sub-task - this is correct.
Open the bottom pane so that you have a combination view with the top being
the Gantt chart with the EVM table and the bottom being the standard task
usage view. Add the actual work row to the task usage pane. Now you should be
able to see 8 hours work and a blank for actual work, on the day for the
subtask.
Select the sub-task. Enter an amount of hours equal to the work value, into
the actual work row, on the expected date for the subtask (in the task usage
pane). Now change the status date to the last date and observer that the CPI
and SPI calculations are correct and both show as 1.
Move the subtask to the top of the list of tasks, so that it is the first
task and not a sub-task any longer. You will notice the CPI and SPI values
are now wrong.
If you have a large project, with many levels and you do this to re-organise
the project, the CPI and SPI values are useless and cannot be used for EVM.
This problem also corrupts the EVM Olap cube extension data.
The obvious solution to re-baseline the project does !NOT! work becuase the
re-baseline algorithm takes the actuals that have been entered and uses them
for the new baseline. If you do this, you loose your baseline infomation
completely, for tasks that contain actual values.
Please help - I think MS might need to produce a bug fix, but I am not sure...
This problem is preventing my company (a very large IT consulting company)
from using MS Project and Project server for Earned Value Management.