Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tip
titleSo many fields!

The PPR report contains hundreds of fields, and keeping track of them can be difficult. This section helps you get a handle on what each field means.

You'll finding a naming schema that recurs throughout the report. Substitute in hours, system revenue, odc revenue, etc for the letter XThe first thing to understand is that many of the fields have similar names. The reason is because we using a naming schema. By understanding the schema, you can quickly narrow down the fields you are actually interested in. There are six fields in the schema. Simply substitute in the metric you are looking for (revenue, hours, etc).

  1. Actual X
  2. Actual X to date
  3. Projected X
  4. Projected X to date
  5. Projected X to completion
  6. X at completion

So what do each of these actually mean? To start, keep in mind that they all They differ based on the date ranges that they cover. You'll see three distinct ranges.

  • From start to end of project (actual, projected, actual/projected mix)
  • From start to use actuals through date (actual, projected)
  • From use actuals through date to end (projected)

The graphic below helps visualize them. See below the image for some real world examples of using them. ("UATD" stands for "Use Actuals Through Date")

So why do we have all the fields and why would you choose one over another? I think the best example is when you want to look at the difference between what work was expected and what work was actually done. This is what our variance report shows. For example, you might use -

  • Projected X vs. Actual X. Show the variance between the work planned and the work that was actually done
  • Actual X to date vs. Projected X to date. Very similar to the last example, but you only care about the variance up to a specific date.
  • Projected X vs. X at completion. Show the difference between my initial plan and what I am likely to deliver.

...