Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Period performance and earned value: financial periods, Store Period Performance and EV columns

Period performance and earned value: financial periods, Store Period Performance and EV columns

Set up financial periods for a project or the whole company, store each period's actual units and cost, earned value and planned value as an immutable record, and read earned value per activity in the Planner against the project baseline.

On this page

A schedule shows actuals to date. Monthly cost reporting needs actuals per period: what was spent in October, not just everything up to now. P6 does this with financial periods and Store Period Performance. os.construction does the same, with one difference: a stored period is an immutable record that’s never overwritten.

Everything here works from the schedule’s own resource assignments, with their units, rates and actual costs. Nothing reads or writes the Accounting ledger. You need Schedule admin.

Financial periods

A financial period is a named date range, usually a month, that period performance is stored into. Manage them in the Period performance section of Schedule › Resources & cost › Costs & EVM.

  • Add financial period with a name (up to 80 characters), a start and an end date, and a scope: This project, or Company-wide so every project uses the same calendar. Company-wide periods are managed by company admins.
  • Use Accounting periods copies one Accounting fiscal year’s periods as company-wide financial periods, so cost reporting lines up with the books. The copies are read only, and the adjusting period 13 is skipped. Nothing is posted to Accounting.
  • Periods of one scope can’t overlap, and each spans at most a year.
  • A period’s dates and scope are fixed once created. You can rename it through the API, and delete it while no project has stored performance in it.

Store period performance

  1. Save and calculate the schedule with its data date at or after the end of the period you want to store.
  2. Choose the period. In the financial periods table, Store period performance appears on each period that has ended by the saved version’s data date and comes after the last stored period.
  3. Store. The current saved version’s actual units and actual cost to date are recorded for every activity and every resource assignment, together with each activity’s earned value and planned value to date. Actual this period is the to-date figure minus the previous stored period’s.

Periods are stored in date order. Once a later period is stored, earlier ones are frozen. You can store the latest period again, for example after correcting actuals: choose Store again…, then Confirm: store again (supersedes). That adds a new run that takes over from the earlier one, and the earlier run is kept. Runs can’t be edited or deleted, and every store is audited.

From an accepted schedule update

When an update period is approved, the Updates page offers Store period performance for that update. It stores the update’s accepted version, not whatever the plan looks like today, into a financial period that ended by the update’s data date.

Where the stored figures show

  • Period performance on the Costs & EVM page lists every stored period in date order: actual cost this period and to date, actual units this period, earned value and planned value to date, and the version, data date and run each came from.
  • The Planner’s Actual This Period Units and Actual This Period Cost columns show the latest stored period for each activity.

Earned value columns in the Planner

The Planner’s Columns dialog has an Earned Value category of per-activity columns, worked out for the saved version with P6’s definitions:

Column How it’s calculated
Budget At Completion (BAC) Budgeted cost of the activity’s resource assignments and expenses
Planned Value Cost (BCWS) The project baseline’s cost, spread evenly over the baseline’s working days, up to the data date
Earned Value Cost (BCWP) BAC × the Performance % Complete of the earned value technique
Actual Cost (ACWP) Actual cost of the activity’s resource assignments and expenses
Cost Variance, Schedule Variance EV − AC, and EV − PV
Cost Performance Index, Schedule Performance Index EV ÷ AC, and EV ÷ PV
Cost Variance Index, Schedule Variance Index CV ÷ EV, and SV ÷ PV
To Complete Performance Index (BAC − EV) ÷ (EAC − AC)
Accounting Variance PV − AC; negative when actual cost runs ahead of the planned cost
Estimate To Complete Cost, Estimate At Completion Cost ETC under the ETC technique, and AC + ETC
Variance At Completion Cost BAC − EAC
Duration % of Planned Actual duration ÷ the project baseline’s at completion duration; can exceed 100

The same category has the labor units family, as in P6: Planned Value Labor Units, Earned Value Labor Units, their cost and schedule variances, performance and variance indices, Estimate To Complete Labor Units, Estimate At Completion Labor Units, Variance At Completion Labor Units, Performance % Complete by Labor Units and Accounting Variance Labor Units. The Costs and Units categories add cost and units % complete by resource type, Cost % of Planned, and variances of total, labor, nonlabor, material and expense cost and of labor and nonlabor units against the project baseline (Variance - BL Project Total Cost and so on). Per-slot cost columns, such as BL1 Total Cost and Variance - BL1 Total Cost, are under Baselines.

Planned value uses the project baseline from Assign Baselines in the Planner. If none is assigned, the current schedule is the basis, as in P6. An activity that isn’t in the baseline has no planned value. Which of the baseline’s values and dates phase planned value follows When calculating earned value from a baseline use on Schedule › Settings: Budgeted values with current dates (the default), Budgeted values with planned dates or At Completion values with current dates. P6 keeps this as a database-wide admin preference, so it isn’t in XER or P6 XML files.

Indices, percentages and variances aren’t added up on Group & Sort bands, because P6 works them out from a band’s own totals instead. The columns reload after every save, so draft edits show once you save and calculate. An activity without resource costs shows —. See Views and layouts.

Earned value techniques

How much of an activity’s budget counts as earned, and how the remaining cost is forecast, follow P6’s earned value settings. Set them for the project on Schedule › Settings. A WBS element can carry its own technique: select it in the Planner’s WBS window and set its earned value technique, custom percent complete, ETC technique and performance factor, or leave a field on Inherit to take it from the parent WBS, then the project. Imported P6 files bring their WBS settings with them. Activities use their nearest WBS’s setting, then the project’s. P6 has no inheritance, so on export a WBS field left on Inherit is written as the value it inherits.

Technique for performance % complete Earned value is
Activity percent complete (the default) The activity’s % complete under its % complete type: physical (from weighted steps when that option is on), duration or units
0 / 100 Nothing until the activity finishes, then all of it
50 / 50 Half when it starts, the rest when it finishes
Custom percent complete Your percentage when it starts, the rest when it finishes
WBS milestones percent complete The weighted milestones of the nearest WBS; without them, the activity’s weighted steps
Activity percent complete using resource curves Each assignment’s curve at the activity’s % complete, weighted by budgeted cost
ETC technique Estimate to complete (ETC)
ETC = remaining cost for activity (the default) The activity’s remaining cost
PF = 1 BAC − EV
PF = custom Your performance factor × (BAC − EV)
PF = 1 / CPI (BAC − EV) ÷ CPI
PF = 1 / (CPI × SPI) (BAC − EV) ÷ (CPI × SPI)

EAC is actual cost + ETC, and variance at completion is BAC − EAC. When CPI or SPI can’t be worked out, for example with no actual cost yet, the factor falls back to 1 and the result says why. The techniques apply to the Planner’s Earned Value columns, the Costs & EVM dashboard and Store Period Performance, and each stored run records the technique it used. The cash-flow forecast still spreads remaining cost by activity % complete, so changing the technique moves earned value, not the forecast.

Limits

  • Actuals are the schedule’s resource actuals. They aren’t reconciled to job cost or the ledger; for that, see Budget reconciliation and the Insights earned value views.
  • Planned value is spread evenly over working days. Resource curves shape Resource Usage, but not planned value.
  • P6’s use project baseline for earned value flag is kept but not applied: planned value always uses the project baseline.
  • From XER, only the activity percent complete technique and the remaining cost, PF = 1 and PF = 1 / CPI ETC codes are decoded. Other codes are kept and written back unchanged, never guessed. P6 XML carries every technique by name.
  • Stored period performance is written to XER and P6 XML on export, up to the version’s data date. Financial periods from an imported file are kept and written back, but can’t be edited.
  • A very large schedule can have too many activity and assignment rows to store in one period; the store is then refused with the reason.
  • Mistake: Storing a period before its data date has passed

    In the app: Advance the data date to the end of the period, save and calculate, then store.

  • Mistake: Expecting to fix an old period by storing it again

    In the app: Only the latest period can be stored again. Correct the actuals in the current period instead.

  • Mistake: Comparing PV with no project baseline assigned

    In the app: Assign the project baseline first. Without it, planned value follows the current schedule.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file