Store Period Performance Overview

Primavera Cloud allows you to capture historical records to track actual units and costs to date using store period performance capabilities in your current schedule. Capturing this data will allow you to bill for work completed and capture the labor, nonlabor, and material costs and earned value metrics for analysis.

Store period performance captures period values for reporting cycles. Reporting cycles should represent your billing cycles; for example, if you will be billing for work done weekly, then the reporting cycle that you set should also be weekly. The first reporting cycle for your project starts on or slightly before the earliest Start Date of an activity in the project. At the end of each reporting cycle, you will update activity actual start dates, percent complete, and costs or units. You will also schedule the project, advancing the data date to be on or after the reporting cycle finish date, and recalculate costs. Then, store the period performance to capture the period values. Earned value metrics can also be captured each period by setting an earned value baseline when setting up store period performance and updating earned value fields.

The following fields form the basis of store period performance and their calculations:

Actual This Period Units and Costs: These fields represent the values for the current reporting cycle being updated and that has not yet been stored. After running store period performance, these units return to 0 until you update period performance values for the next reporting cycle.
Prior Actual Units and Costs: These fields are the accumulations of all totals up to the last closeout date. This is historical data for an activity. These fields are read-only and won't be updated when you schedule the project or recalculate project costs. They also won't be updated if you set a scenario or baseline as the current schedule or if you update the price per unit for resource assignments (although the updated price per unit will be reflected in future stored periods).
Actual Units and Costs: These fields are the total units or costs of all prior periods plus the current period being updated. The values entered here are spread evenly across all workdays from the Actual Start date to the Data Date.

To learn more about Earned Value metrics, see Understanding Earned Value Fields.

Store period performance values will roll up to the activity. Therefore, you can enter data for the activity's resource assignments, and the sum for each field will be calculated to represent the value for the activity as a whole. Similarly, if you enter labor units or costs against an activity with multiple resource assignments, then the values will be distributed across the resource assignments of that type. If timesheets are linked to resources, then store period performance will use the timesheets data to update the hours worked for a resource. You can also add your units and cost values directly against an activity or milestone. Entering period data against the activity uses the project rate amount to determine the costs. Although there are several options for entering period data, it is recommended that you do not change the method you use after you have started storing period data.

Certain store period values can be tracked over time in the activity usage histogram. See Activity Usage Overview for more information.

You can delete an activity that has stored period values associated with it. The period values will also be deleted.

Before getting started with store period performance, you should define the reporting cycle and configure the earned value baseline that you want to use for the project.

Related Topics