BCWP discrepency

[Neil A]

Hi,
A couple of projects I deal with have a discrepency in the value of BCWP,
depending on where you look at it. The problem initially arose because some
reports we generate from the Project Server database had a different value to
what I was seeing for Task 0 in Project Pro, and what I saw in a PWA view.

It then turned out that different users would see different values in
Project Pro itself, i.e. I would see 113,319, and someone else would open the
same project and see 114,251. Of 5 users I've checked with, 3 are in one
camp, and 2 in the other. At this stage, we haven't found any differences in
the version of Project Pro (11.0.2003.0815.15) or our options.

Any suggestions gratefully received.

 

[Andrew Lavinsky]

IMHO, a couple things might be the issue:

1) Publishing projects to Server to update the BCWP calculations
2) Inconsistent status dates in the MPP files...one check on this is whether
or not Actual Cost lines up across projects/users. If Actual Cost is consistent,
then usually the BCWP issue would be caused by varying status dates by users
(i.e. if your status date is at the end of the project, BCWP should equal
AC).

Both are possibilities, and potential pathways to figure out what's going on.

-A

 

[Neil A]

I found the problem - and I was wrong about there being no sign of different
versions. It turns out that some clients had SP1 aplied, and some didn't.
Applying SP1 resolved the issue in Project Pro, and subsequent publishing
made it consistent everywhere.