Store Period Performance takes a snapshot of progress at the end of a financial period. For each activity and resource assignment it records the actual units and cost to date. The difference from the previous stored period becomes actual this period. Earned value and planned value to date are usually stored alongside, so the period’s cost performance can be reported later exactly as it stood.
Worked example
Illustrative: at the end of September the store records $3.5M actual cost to date and $3.6M earned value. At the end of October it records $4.2M and $4.3M. October’s actual cost this period is $0.7M, and its earned value this period is $0.7M. If September’s actuals are later found to be wrong, the correction goes into October; September’s stored figures stay as reported.
Why it matters
Monthly cost reports, S-curves of actual spend and period CPI all depend on stored periods. To-date figures alone can’t show when money was spent, and recomputing past periods from today’s data changes reports that have already been sent.
Common mistakes
- Storing a period before the data date has reached its end, so the period is only partly complete.
- Re-storing an old period after correcting actuals, which rewrites a reported month.
How os.construction handles it
The Costs & EVM page stores a saved version into a period that has ended by its data date, and an approved schedule update can store its accepted version. Periods are stored in date order and earlier ones are frozen. Storing the latest period again adds a superseding run and keeps the earlier one; P6 overwrites instead. Runs are immutable and audited, and nothing is posted to the ledger. See Period performance and earned value.