Skip to content
ProjectControls.com
Primavera Project Planner - P3

Earned Value Reporting - Historical Values

In the Open Standard
Alan SmithMember for 21 years
Created
6
3
0
Thanks for reading this folks, but I need some information or help in attemtpting to resolve a bit of a glitch with our EV reporting.
Essentially we notice that when we look back at last weeks or last months recorded values they have in fact changed somewhat substantially to those which we had graphically recorded.
We get the scenario whereby we can record for instance last week a value of 8230 Earned Value hours, whereas after updating this week and re-scheduleing with this weeks date the figures for last week are now indicating an EV of some 5436 Hrs.
I have always laboured under the simple logic that historical values are cast in stone and would not change following routine weekly updating of progress.
I can send pdf representaion of our values should anybody want to see exactly where we are coming from.

Any help advice would be appreciated.
Regards
Alan
Save Follow Follow forum Report
Reply New topic

6 replies

Oldest first
  1. 0
    Anoon Iimos ·
    #1
    i don’t exactly understand what you’re saying but i got a guess something like this:

    perhaps you got some corrective works carried out, which means that you have taken out some pieces and you need to reinstall it again; this shall only apply to your Current Project.

    whereas, your baseline/target schedule will tell you exactly where you’re supposed to be at a certain time (this you need to cast in stone); while your Current Project may become erratic, you’ll need to get exactly (actual) what you have at a certain time (data/status date); from there you can make the comparison...
    Report
  2. 0
    Joao Ribeiro ·
    #2
    If you are using P3, that may come from not closing out the period before updating.
    HTH
    Report
  3. 0
    Alan Smith ·
    #3
    Joao,

    Of course, what a simple thing to forget. guess that comes from too many contracts on differnt sites with different operating systems.
    Guess we should try that and see how it goes.

    Regards

    Alan
    Report
  4. 0
    Brennan Westworth ·
    #4
    Errors in period performance can also be caused by trying to save "0" periods.

    P3 does not close off periods with "0" performance and instead spreads this into the following period as if the period wasnt closed off at all.

    As a work around, you need to record something (0.01) for each resource that has recorded 0 for the period but is still in progress.

    A real pain in the A$$ :)

    Report
  5. 0
    Alan Smith ·
    #5
    Store Period Performance was the right answer, silly thing is I used to do this on a previous contract. Mind must be going. Thanks lads I am indebted.

    Regards

    Alan
    Report
  6. 0
    Alex Wong ·
    #6
    Hi

    Since your EV(hrs) is dropping substaintially, I suggest you get your previous schedule and run a simple report of

    Act id | Description | Budgeted Hr | % Complete |EVhr

    Compare the two plan and identify which one is droping in value

    I supspect that it might be your budgeted value where when you update you might zero some of your budgeted value

    Cheers

    Alex
    Report

Log in or join to reply

ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.

Log inJoin free

Existing members: your original username and password still work. Forgot password?