FYI

If it is P6 you talking about, you can edit your stored PP provided you have the access right

HTH

Regards

Alex

(I use PP to predict the project end date and the 20/80 rule work pretty good)

Hi Mohhammed,

There is no way to undo stored values in a project. But if you have to undo then i can suggest you to create a new schedule and export-import all data and relations from existing schedule.

Store period performance should be a must if you have an opportunity for a forensic analyses. A good resource loaded and tracked schedule could show what-how the works done months ago with just a few clicks.

The worst nightmare about store perion performance is being seen if you are changing budgets, durations of activities while revising or re-forcaasting schedule. You will have variances and you will need rewrite some resource values or global change a few times to clear the variances. I also encounter import-export problems for percentage completes in P3.

As conclusion it is not a must but it is a should. It isnt must due to : "The best schedule is the schedule you can manage".

Regards,

Safak

RA (SDK)? Sounds new to me. Would you mind to elaborate further.

If the Stored Period Performance of a certain schedule is done quarterly and let us say we want to switch to store our schedule in monthly or weekly, is there any short way to update considering an available data in spreadsheet. Does "Import" tools is applicable?

In order to overcome the 0 actual / unit problem I usually run a global change that impose any resource that had a 0 this period with a $0.1 prior to store period performance, that way it is always correct

sure u can continuously update and store period performance in the same p3 file (for each monthly update). But it is useful if you maintain p3 files separately such ud01, ud02, ud03 for each monthly update. It would be meaningful(filemaintenance) to supply the files to client, u can check for any slippage in time as compared to previous monthly update by keeping ud03 as target for updating progress in ud04, also useful for preparation of disruption analysis as and when required.

Dear Ali,

The following procedure will show you the importance of store period performance.

Let us say each monthly update shall be denoted as ud01 (jan), ud02(feb), ud03(mar) for ideal cases.........

Assume some 50 number of foundations in a design unit, you are respresenting it as an activity and loaded with a resource called BQFdn and assigning 50 in Budgeted Quantity.

Assume some foundation works commenced in Feb, say 10 no of foundations completed before the status date of ud02. you update this status in actual to date field by entering 10 and schedule the program. in the next update say ud03(you have to copy ud02 as ud03 first), before statusing the activity(or any activities) you must store the period performance option in ud03 file, then you can notice the actual this period field will show 0 for the foundation activity, which means the number of 10 foundations completed in the previous month has been stored in the database, and ready for fresh-update to display the progress in march(ud03 update), then start to status the activity say another 20 foundations completed, enter the actual to date as 30 and schedule the project(remember again you should not press the store period performance)in ud03 file. so that you can see the historical actual number of foundations completed when you run the s-curve as well early finish date for remaining foundations will be shown in the s-curve.

of course our fellow planners clearly explained about EV............ if you still have some doubt you can use any google search engine to search for EVM concepts.........

hope the above will clarify the importance of store period performance.

DOH!

It’s an option.

Store period performance will store the EV (quantity & cost) for the datadate you store it on. If you don’t do that, P3 will level out the EV on each task.

Example:

Task takes 10 days with a BQ of 100. After day 5, you are 50%. This means that you have an EV of 10 per day. If you are still 50% after 10 days, you will have a EV of 5 per day! That means that the historic date from the first 5 days will be spread over the 10 days that the task is in progress and thus your progress line will drop in the S-Curve.
If you store period performance, the EV of 50 will remain on the 5 days and the other 5 days that you didn’t earn anything will have a EV of 0 (zero). Your progress line will show the EV of 50 in the first 5 days and a horizontal line the next 5 days.

Hope this is clear enough.