Hi Mike,
My comments are inline with your last reply.
Julie
----------------------------------------------------------------------------
Julie Wrote
Hi Mike,
Quick question -- is the extract above from the Task Usage view
*before* the Actual Finish date of the task? I can reproduce what
you
report - Task BCWP <> Assignment BCWP even after rebaselining when I
look at data from before the task's actual finish date. However, at
the task finish date and beyond, all time-phased data shows ACWP =
BCWP = BCWS for both assignment and task lines.
Julie- Hide quoted text -
- Show quoted text -
--------------------------------------------------------------------------------------------
Mike said:
Julie ~ It is copied from the left side of task usage view not from
the time phased data on the right of the task usage view.
[Julie] Thanks, I can see the same thing in testing when the status
date is before the finish date of the task.
I've done some more digging, and it appears MSP just can't add.
[Julie] I'm not willing to disagree with you at this point but I
think there is an explanation as to why Assignment BCWS and Task BCWS
don't match on tasks that are not 100% complete. At a task level BCWS
is based upon % complete -- a duration measurement. At the assignment
level, it appears to be based upon % work complete -- a work
measurement. It's fairly easy to create a circumstance where % work
complete and % complete are not equal. If the task is in progress,
Task BCWP <> Assignment BCWP if % complete <> % work complete.
However, if the task is complete (no remaining duration and no
remaining work) all should equal at the end. When rebaselining, all
completed tasks' variances should go to zero. I do still see
differences in BCWP on a task and assignment level if I look at
time-phased info before the finish date.
All
the schedules we use are fairly large (2000-8,000 lines/5-10mg) are
resource loaded with rates that varying by year and run 3-5 years.
I have numerous tasks similar to the example I gave in the earlier
post where “P” is added incorrectly, some where “S” is wrong. Some
have multiple resources, some have one. Some are closed, some are in
progress. I have some with large deltas, some small. What’s more
aggravating when looking at the time phased data, actual, work,
baseline work all have the same values!?!
[Julie] I would expect Actual Work, Work, and Baseline Work to be the
same if you've re-baselined and the task is 100% work complete.
I've rebaselined the same file several times (copied the original
from
the server to my computer) and gotten different result each time.
However, none of the results were the same. Sometimes BCWP is off
sometimes it’s BCWS and sometimes it's both!
I initially thought the issue was due to the file being corrupted/
bloated as you suggested. I followed the directions on the FAQ site
(thanks). The file got a little smaller but no change to the outcome
of rebaselining. I tried earlier version of the file, I even used a
different project’s file to see if it would rebaseline properly and
none of them did.
I’m now trying to figure out how to “fix” the data and can’t seem to
figure how. I was expecting to see anomalies when looking at the
various views/table in MSP but have found any.
[Julie] I'm not sure there is a fix. It appears as though comparing
assignment earned value to task earned value is a path to madness.
Does there appear to be an use at looking at solely task earned value
and not trying to reconcil the assignment data with the task data.
At this point I’m totally frustrated, and not sure what to do next to
resolve the issue.
[Julie] I understand completely and really wish I could come up with
a wonderful answer for you. Like you, I've spent more time in earned
value calculations over the last day that I ever really want to
I do appreciate your help!!
[Julie] Thanks for that, Mike. I'll keep pondering and experimenting
and see if I can duplicate what you report. And then figure out why!
