Using Burn Down for P6 EPPM Data

Primavera Analytics contain an additional way that data can be analyzed outside of the standard P6 EPPM methods. Primavera Analytics includes additional tables and configuration for Burn Down.

Burn Down is a set of calculations that display how a project will progress if everything goes "according to plan". Primavera Analytics includes metrics and Key Performance Indicators (KPIs) for both the current project data, as well as any point in the past for which the data was captured. These metrics and KPIs include both current and historical activity counts, units, and costs. Primavera Analytics has the ability to track and monitor how the current schedule is executing in relationship to how it was supposed to progress at the start of the project (T‐0). This includes, but is not limited to, any new activities that were added to the current project that did not exist at the start of the project (emergent), activities that have been removed in the current schedule that existed in the point in time capture of the project (deleted), and activities whose start or finish has changed since the point in time capture of the project.

Use the following sections to learn more about the additional functionality, how to set it up in P6 EPPM, and how to work with the data in Primavera Analytics.

Note: Oracle provides several white papers that detail aspects of Burn Down:

Burn Down Detail Data Flow: http://www.oracle.com/webfolder/technetwork/tutorials/primavera/OnlineLearning/WhitePapers/BurnDown_Details_DataFlow.pdf
Burn Down Units Details: http://www.oracle.com/webfolder/technetwork/tutorials/primavera/OnlineLearning/WhitePapers/BurnDown_Details_Units.pdf
Burn Down Counts Details: http://www.oracle.com/webfolder/technetwork/tutorials/primavera/OnlineLearning/WhitePapers/BurnDown_Details_Counts.pdf

Related Topics