Stored period performance
Forum Sponsor
Top Posters
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts
Hi Francis,
As Mr. david say, store period perfomance is for storing periodical actuals..it is important when your activities are resource & cost loaded.
Actual to date fields of resource/cost of the activity shows the cumulative actual so far. Meaning, if an activtiy started 2 months before and achieved 60% progress, we get 60% of the budgeted cost as the earned value (and actual to date, unless you edit it manually). But it does not tell you what progress/value you achieved in last month. may be in 1st month you achieved 20% progress and in second month 40%. Only when you do store period perfomance BEFORE each update, you get the periodical value (actual this period). When you do the store period perfomance, P3 sets all actual this period to zero, so that periodical increment of actual to date is stored here.
regards
Sonia
Hi David,
Thanks for your mail,
now application looks some what ok for me,
In what context it has to be used ,
but if any example can be given to illustrate this and the steps involved in this,
Thanks
The fact that you are using cost accounts leads me to believe you need this option.
I primarily work with Oil and Gas clients in the North Sea, and what we tend to call "Earned value history" rather than "Past period Actuals" has been an issue for 25 years.
Let us assume that an activity has a duration that extends through several reporting periods, say 5 weeks. Week one the activity starts, but percent complete is zero, week two it is still zero, week three it is still zero, week four we get 80% complete reported.
Without Past Period Actuals, Primavera only knows the start date and 80% complete, thus it reports 20% earned each week. With PPA, the real earned value per period is held, along with the actual hours each week, rather than the total actual hours divided by 4.
Without PPA the historic part of an "s" curve CHANGES as Primavera averages the "to date" Earned and actual values over the number of periods, With PPA the correct period values are held.
Of course no one who is involved in planning - "what happens next"- cares about this, but cost engineers - "when did we spend what" do. If you are using Primavera for earned value analysis and costing as well as planning you need this.