p6 analytics burn down details: units - oracle · overview oracle primavera p6 analytics includes a...

P6 Analytics Burn Down Details: Units

Disclaimer

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Contents of this document are Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Overview Oracle Primavera P6 Analytics includes a Subject Area called Primavera – Burn Down, and

corresponding database tables in the STAR schema. In the simplest of terms, Burn Down is a set of calculations that display how a project will progress if everything goes “according to plan”. Primavera P6 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. P6 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.

The following document is meant to serve as an example of common activity scenarios that will be encountered while using the Burn Down feature and the expected outcomes after data is migrated from P6 to P6 Analytics This document details how the Units flow on a daily basis from P6 updates to P6 Analytics metrics and KPIs. Separate documents detail how activity counts and the overall data flow are collected in a similar fashion.

Definitions

Before we look at the individual scenarios, it is important that we define some common terms that you will see throughout this document.

Work Down Date – Represents the date on which the initial (or “baseline”) data capture is

taken. This is sometimes referred to as the T‐0 capture. The data that is captured on this date

provides the “baseline” (T‐0) capture used for the Burn Down process in P6 Analytics. Once

captured in P6 Analytics, this data will not change. (Note: The term “baseline” in this document

has no connection to the baseline that exists in P6.)

Data Date – The P6 project’s Data Date at the time the data is captured.

ETL Process Date (Data Capture Date) – The date the data is captured in P6 Analytics.

Metrics and Key Performance Indicators Defined The Following table defines the metrics and key performance indicators (KPIs) that will be shown throughout the scenarios below. Units

Metric Definition

Baseline Units For each activity on a particular day in the “baseline” data capture (T‐0), the amount of Planned Units.

Remaining Units For each activity on a particular day in the current schedule, the amount of Remaining Units. Calculated as Planned Units – Actual Units.

Actual Units For each activity on a particular day in the current schedule, the amount of Actual Units.

At Completion Units For each activity on a particular day in the current schedule, the amount of At Completion Units. Calculated as Actual Units + Remaining Units.

Remaining Units Burn For each activity on a particular day in the current schedule, the amount of Remaining Units distributed over the remaining activity duration.

Actual Units Burn For each activity on a particular day in the current schedule, the amount of Actual Units distributed over the remaining activity duration.

Total Units For each activity on a particular day in the current schedule, the amount of Actual Units Burn + Remaining Units Burn + either the Remaining Units(for the day of the data capture) or Actual Units that occurred after the data date(for the day prior to the current capture). This is to account for a data date other than midnight.

Daily Update Sequence Used In order to properly calculate Burn Down metrics and KPIs, the schedule must be updated and the data capture process between P6 and P6 Analytics must be run daily.

The steps for daily updating are as followed:

1. Update the status of activities in P6 (Actual and Remaining Units, Actual Start and Finish, etc.),

advance the data date accordingly, schedule the project, and apply actual.

2. Publish the project after step 1 has been completed.

3. Run the data capture process (ETL process).

Details for Scenario The following details apply to the scenarios covered in this document:

Work Down Date is 2/16/2014

Data Date for the initial data capture is 2/17/2014 00:00

Each data capture after the initial data capture will use a data date time of 13:00

All Activity calendars have non‐work time of 00:00‐02:00 and 10:00‐12:00 (20 hour work day)

Summary of data capture runs: o Initial data capture occurs 2/16/2014, Data Date of 2/17/2014 00:00 o Data capture occurs 2/17/2014, Data Date of 2/17/2014 13:00

o Data capture occurs 2/18/2014, Data Date of 2/18/2014 13:00 o Data capture occurs 2/19/2014, Data Date 0f 2/19/2014 13:00

Use Cases

Use Case AC1: Completed Before Work Down Date

Description Activity completes before the Work Down Date (02/16/2014).

P6 Values Field Planned Value Actual Value Start 2/14/2014 08:00 2/14/2014 08:00 Finish 2/14/2014 18:00 2/14/2014 18:00 Duration 10 hours 10 hours Units 10 10

Results Because this activity has a start and finish date prior to the Work Down Date, no Burn Down metrics are gathered (except actual units burn, total units, and activity count (Total)). However, this activity would reside in full form in Activity History.

P6

P6 Analytics

Metrics Value Explanation

Baseline Units 0 No “baseline”(T‐0) units are captured for this activity in Burn Down, since the activity was completed before the Work Down date (02/16/2014).

Remaining Units 0 Because this activity has a status of Complete, no Remaining Units exist for this activity in the current schedule at the time of the data captures (02/16/2014‐02/19/2014).

Actual Units 0 Because Actual Units for this activity occurred on days before the initial data capture, no Actual Units exist for this activity in the current schedule at the time of the data captures (02/16/2014‐02/19/2014).

At Completion Units 0 Because At Completion Units for this activity occurred on days before

the initial data capture, no At Completion Units exist for this activity in the current schedule at the time of the data captures (02/16/2014‐02/19/2014).

Remaining Units Burn 0 Because this activity started and completed before the initial data capture (02/16/2014), no Remaining Units Burn are calculated for this activity.

Actual Units Burn 10 Because this activity incurred Actual Units in the past, at the time of the initial data capture (02/16/2014), this activity will show that amount in the Actual Units Burn. (Can be filtered out if required.)

Total Units 10 Calculated as Actual Units Burned (10) + Remaining Units Burned (0) + Remaining Units (0).

Use Case AC2: Started Before Work Down Date, Completed on Day 1

Description Activity starts prior to the Work Down Date and is finished 1 day after the Work Down Date.


Results Since this activity starts before the Work Down Date and ends 1 day after the Work Down date, Burn Down metrics will be gathered for this activity.

If you don’t want to track this type of activity, it can be filtered out.

P6

P6 Analytics Data Capture Date: 02/16/2014 P6 Data Date: 02/17/2014 00:00


Baseline Units 0 Because the initial data capture occurred on 2/16/2014, the data date for the initial data capture was 2/17/2014 00:00, there are no baseline units for this day (02/16/2014).

Remaining Units 0 Because the initial data capture occurred on 2/16/2014, the data date for the initial data capture was 2/17/2014 00:00, there are no remaining units for this day (02/16/2014).

Actual Units 20 Because the initial data capture occurred on 2/16/2014, there are 20 Actual Units for this activity on this day (02/16/2014).

At Completion Units 20 Calculated as Actual Units (20) + Remaining Units (0).

Remaining Units Burn 6 Because the initial data capture occurred on 2/16/2014, the data date for the initial data capture was 2/17/2014 00:00, based on the activity start and end date, work/non‐work time, there are 6 Remaining Units Burn.

Actual Units Burn 34 Because the data capture occurred on 2/16/2014, the data date for the data capture was 02/17/2014 00:00, and based on the activity start date, work/non‐work time, this activity has incurred 34 Actual Units to date and thus has 34 Actual Units Burn.


Data Capture Date: 02/17/2014 P6 Data Date: 02/17/2014 13:00


Baseline Units 6 “Baseline”(T‐0) data is captured for this activity since there were Remaining Units (6) on this day (02/17/2014) at the time of the initial data capture (02/16/2014).

Remaining Units 0 There are no Remaining Units for this activity in the current schedule on this day (02/17/2014 13:00) at the time of the data capture (02/17/2014).

Actual Units 6 Actual Units (6) exist for this activity on this day (02/17/2014) at the time of the data capture (02/17/2014).

At Completion Units 6 At Completion Units (6) exist for this activity on this day (02/17/2014) at the time of the data capture (02/17/2014).

Remaining Units Burn 0 Remaining Units Burn are 0 since there are no longer any Remaining Units for this activity at the time of the data capture (02/17/2014).

Actual Units Burn 40 Actual Units Burn (40) reflects the total amount of Actual Units for this activity at the time of the data capture (02/17/2014).

Total Units 40 Calculated as Actual Units Burned (40) + Remaining Units Burned (0) + Remaaining Units (0).

Data Capture Date: 02/18/2014 P6 Data Date: 02/18/2014 13:00 Data Capture Date: 02/19/2014 P6 Data Date: 02/19/2014 13:00


Baseline Units 0 For these data capture days (02/18/2014 & 02/19/2014), according to the “baseline” (T‐0) data capture this activity status is complete. Therefore, the Baseline Units for these days is 0.

Remaining Units 0 No Remaining Units exist for this activity at the time of these data captures (02/18/2014‐02/19/2014), since the activity completed on 02/17/2014.

Actual Units 0 No Actual Units exist for this activity at the time of these data captures (02/18/2014‐02/19/2014), since the activity completed on 02/17/2014.

At Completion Units 0 No at Completion Units exist for this activity at the time of these data captures (02/18/2014‐02/19/2014), since the activity completed on 02/17/2014.

Remaining Units Burn 0 No Remaining Units Burn exist for this activity at the time of these data captures (02/18/2014‐02/19/2014), since the activity completed on 02/17/2014.

Actual Units Burn 40 Actual Units Burn (40) reflects the total amount of Actual Units for this activity at the time of theses data captures (02/18/2014 – 02/19/2014).


Use Case AC3: Started and Completed on Work Down Date

Description Activity starts and completes as scheduled on the Work Down Date.


Notes Normal outage activity, all metrics captured.

P6



Baseline Units 0 Because the initial data capture occurred on 2/16/2014, but the data date was 2/17/2014 00:00, there are no baseline units for this day (02/16/2014).

Remaining Units 0 Because you can’t have Remaining Units prior to the data date, this data capture occurred on 2/16/2014, but the data date was 2/17/2014 00:00, there is no Remaining Units for this day (02/16/2014).

Actual Units 10 Actual Units (10) exist for this activity on this day (02/16/2014) at the time of the data capture (02/16/2014).


Remaining Units Burn 0 No Remaining Units Burn are calculated for this activity since it started and ended on the Work Down date (02/16/2014).

Actual Units Burn 10 At the time of the initial data capture (02/16/2014 00:00), this activity had Actual Units, that amount will be displayed in this metric. (Can be filtered out if required.)


Data Capture Date: 02/17/2014 P6 Data Date: 02/17/2014 13:00 Data Capture Date: 02/18/2014 P6 Data Date: 02/18/2014 13:00 Data Capture Date: 02/19/2014 P6 Data Date: 02/19/2014 13:00


Baseline Units 0 For these data capture days (02/17/2014 ‐ 02/19/2014), according to the “baseline” (T‐0) data capture this activity status is complete. Therefore, the Baseline Units for these days is 0.





Actual Units Burn 10 Actual Units Burn (10) reflects the total amount of Actual Units for this activity at the time of these data captures (02/17/2014 – 02/19/2014).


Use Case AC4: Started on Work Down Date and Completed on Day 1

Description Activity starts on Work Down Date and completes as scheduled on Day 1.



P6





Actual Units 14 Actual Units (14), because the activity started at 08:00AM and worked the rest of the day (16) minus hours 22:00 thru 24:00 which are non work hours (2).


Remaining Units Burn 16 At the end of this day (02/16/2014), there will be 16 remaining units burn on this activity that will be used over the remaining life of this activity.

Actual Units Burn 14 Actual Units Burn (14) is the sum of all actual units for this activity throughout the life of the activity up to this point in time data capture. (Can be filtered out if required.)




Baseline Units 16 According to the “baseline” data capture (T‐0), the amount of Planned Units (16) for this day (02/17/2014). Since this activity is scheduled to finish on this day 02/17/2014 18:00, baseline units for this day are 16, considering work time and non‐work time (00:00 – 02:00).

Remaining Units 5 On this day in the current schedule, the amount of Remaining Units. Calculated as Planned Units – Actual Units. Since the data date for this day is 02/17/2014 13:00, this activity is scheduled to finish 02/17/2014 18:00, there are 5 hours remaining.

Actual Units 11 Actual Units (11) for this activity on this day (02/17/2014) at the time the data is captured. Since this activity is scheduled to finish on this day 02/17/2014 18:00, Actual units for this data capture are 11, considering work time and non‐work time (00:00 – 02:00).


Remaining Units Burn 0 Remaining Units Burn (0), because this activity is scheduled to complete on this day (02/17/2014).

Actual Units Burn 25 The sum of all actual units captured for the history of the activity up to this point in time. (Can be filtered out if required.) Acutal Units Burn (25) is calculated as Actual Units from 02/16/2014 data capture (14) plus Actual Units from 02/17/2014 data capture (11).



In addition to capturing data for 02/18/2014, the data capture process on this day (02/18/2014) also goes back 1 day in time to record what the Actual Units were at the end of the previous day (02/17/2014 24:00). For the previous days data capture (02/17/2014), the data date at the time of the capture was 02/17/2014 13:00. Because the data date is in the middle of the day, Actual Units are only recorded on 02/17/2014 up until 13:00. The remaining Actual Units (those units that occur between 13:00 and 24:00) are “back filled” for the data capture on 02/17/2014 when the data capture on 02/18/2014 is run.









Use Case AC5: Started and Completed on Day 1 (As Scheduled)

Description Activity starts and completes as scheduled on Day 1.



P6



Baseline Units 0 Activity is not planned to start until 02/17/2014, therefore for this day, Baseline Units are 0.


Actual Units 0 No Actual Units exist for this activity at the time of the data capture (02/16/2014), since the activity has not started.


Remaining Units Burn 10 Remaining Units Burn (10) are calculated for this activity since the activity has not started and has 10 units remaining to burn.

Actual Units Burn 0 No Actual Units Burn exist for this activity at the time of the data capture (02/16/2014), since the activity has not started.




Baseline Units 10 On this day in the “baseline” data capture (T‐0), the amount of Planned Units (10).


Actual Units 5 Actual Units (5) for this activity on this day (02/17/2014) at the time the data is captured. Since this activity is scheduled to finish on this day 02/17/2014 18:00, Actual units for this data capture are 5, considering work time and non‐work time.





Use Case AC6: Started on Day 2 and Completed on Day 3 (Late)

Description Activity starts on Day 2 and is originally scheduled to complete on Day 2. Activity pushes in the schedule and is completed late on Day 3.

P6 Values Field Planned Value Actual Value Start 2/18/2014 08:00 2/18/2014 08:00 Finish 2/18/2014 18:00 2/19/2014 18:00 Duration 10 hours 20 hours Units 10 20 (+ 10 from

Planned)

Notes Additional units required are reflected in the Actual Units Burn, the delta can be seen when compared to the Baseline Units.

P6

P6 Analytics Data Capture Date: 02/16/2014 P6 Data Date: 02/17/2014 00:00 Data Capture Date: 02/17/2014 P6 Data Date: 02/17/2014 13:00


Baseline Units 0 Activity is not planned to start until 02/18/2014, therefore for these days (02/16/2014 & 02/17/2014) Baseline Units are 0.

Remaining Units 0 Remaining Units (0) because this activity is not scheduled to start until 02/18/2014.

Actual Units 0 Actual Units (0) because this activity is not scheduled to start until 02/18/2014.



Actual Units Burn 0 Actual Units Burn is the sum of all actual units captured for the history of the activity up to this point in time. (Can be filtered out if required.) Acutal Units Burn (0) is calculated as Actual Units from 02/16/2014 data capture (0) plus Actual Units from 02/17/2014 data capture (0).









Actual Units Burn 5 The sum of all actual units captured for the history of the activity up to this point in time. (Can be filtered out if required.) Acutal Units Burn (5) is calculated as Actual Units from 02/16/2014 data capture (0) plus Actual Units from 02/17/2014 data capture (0) plus Actual Units from 02/18/2014 data capture (5).





Baseline Units 0 For this data capture (02/19/2014), according to the “baseline” (T‐0) data capture this activity status is complete. Therefore, the Baseline Units for this day is 0.

Remaining Units 0 No Remaining Units exist for this activity at the time of this data capture (02/19/2014), since the activity was planned to complete on 02/18/2014.

Actual Units 6 There are 6 Actual Units for this activity on this day (02/19/2014) at the time the data is captured (02/19/2014).


Remaining Units Burn 0 No Remaining Units Burn exist for this activity at the time of this data capture (02/19/2014), since the activity completed on 02/19/2014.



Use Case AC7: New Activity 1 added on Day 2 and Completed on Day 3

Description Emergent activity added to the schedule on Day 2, planned to start and finish on Day 3. Completed early on Day 3.

P6 Values Field Planned Value Actual Value Start 2/19/2014 08:00 2/19/2014 08:00 Finish 2/19/2014 18:00 2/19/2014 13:00 Duration 10 hours 5 hours Units 10 5 (‐5 from Planned)

Notes No Baseline Units are captured since the activity was not in the schedule when the initial capture occurred (Work Down Date).

P6



Baseline Units 0 Activity did not exist at the time of the “baseline” (T‐0) data capture (02/16/2014).

Remaining Units 0 Remaining Units (0) because this activity is not scheduled to start until 02/19/2014.




Actual Units Burn 0 The sum of all actual units captured for the history of the activity up to this point in time. (Can be filtered out if required.) Acutal Units Burn (0) is calculated as Actual Units from 02/18/2014 data capture (0).

Total Units 10 Calculated as Actual Units Burned (0) + Remaining Units Burned (10).




Remaining Units 0 No Remaining Units exist for this activity at the time of this data capture (02/19/2014), since the activity is planned to complete on 02/19/2014.

Actual Units 5 There are 5 Actual Units for this activity on this day (02/19/2014) at the time the data is captured (02/19/2014).





Use Case AC8: Started and Completed Day 1 (Deleted Day 3)

Description Activity started and completed as scheduled on Day 1, but later removed from the schedule on Day 3.


Notes Activity deleted from the schedule will no longer show in Burn Down. Another option is to designate an Activity Code/UDF to mean “Deleted”, and filter it out in P6 Analytics, rather than physically deleting it from P6.

P6








Actual Units Burn 0 Actual Units Burn (0) is the sum of all actual units for this activity throughout the life of the activity up to this point in time data capture. (Can be filtered out if required.)









Actual Units Burn 5 The sum of all actual units captured for the history of the activity up to this point in time. (Can be filtered out if required.) Acutal Units Burn (5) is calculated as Actual Units from 02/16/2014 data capture (0) plus Actual Units from 02/17/2014 data capture (0) plus Actual Units from 02/18/2014 data capture (5).





Remaining Units 0 No Remaining Units exist for this activity at the time of this data capture (02/18/2014), since the activity completed on 02/17/2014.

Actual Units 0 There are 0 Actual Units for this activity on this day (02/18/2014) at the time the data is captured (02/18/2014), since the activity completed on 02/17/2014.



Actual Units Burn 10 The sum of all actual units captured for the history of the activity up to this point in time. (Can be filtered out if required.) Acutal Units Burn (10) is calculated as Actual Units from 02/17/2014 data capture (10).


Data Capture Date: 02/19/2014 P6 Data Date: 02/19/2014 13:00 (after deletion)

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

oracle.com

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

This document is provided for information purposes only, and the contents hereof are subject to change without notice. This

document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in

law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any

liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This

document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our

prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and

are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are

trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0113

p6 analytics burn down details: units - oracle · overview oracle primavera p6 analytics includes a...

Documents