Why does BCWS (Earned Value) indicate wrong numbers?

[Jens]

I am trying to get SPI reporting out of a 700 line item schedule. In order to
produce cost information that's needed to run Earned Value calculations, I
assigned each task to one resource (Mr. Wizard) and assigned a rate of 1$/hr
for standard and over time.

The BCWS keeps showing an increase in value even for tasks that should not
have started begun per schedule (status date and current date aren't the
issue).
I created a short sample project in which all EV calculations work fine -
all settings for Calculations are identical.

Also the SPI rolls up with some sort of average, and does not ignore the 0%
on tasks that have not passed their start date in the big schedule. Again, in
the small sample file it does this correctly.

What can be the reason for this failure to compute the right BCWS in the
bigger schedule? I need to create a Schedule performance report ASAP and
can't get passed this barrier.... besides the answer, I'd be glad to hear
other ideas for automatic status metrics.

 

[Catfish Hunter]

The only way I have had success in making this work is take your baseline
(original) schedule to excel and do your calculations there.
MS Projects adds and removes man-hours to task. If a task takes longer it
adds man-hours and ...........
Hope this helps.