p6 analytics burn down details: data flow · overview oracle primavera p6 analytics includes the...

P6 Analytics Burn Down Details: Data Flow

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 the 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 (that data which is updated on a daily basis), 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 data flows on a daily basis from P6 updates to P6 Analytics metrics and KPIs. Separate documents detail how both activity counts and units are collected.

Definitions Before looking at the individual scenarios, it is important to define some common terms used 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. Any metrics available in P6 Analytics,

Primavera – Burn Down Subject Area, with the word “baseline”, come from this data capture.

(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. Burn

Down projects require that data captures occur at least once a day.

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. The tables are divided by counts and units.

Counts

Metric Definition

Baseline Not Started Count (Values 1 or 0) For each activity on a particular day if the activity status in the “baseline” data capture (T‐0), is “Not Started”, then Value = 1. If any status other than “Not Started”, then Value = 0.

Not Started Count (Values 1 or 0) For each activity on a particular day if the activity status in the current schedule is “Not Started”, then Value = 1. If any status other than “Not Started”, then Value = 0.

Baseline In Progress Count (Values 1 or 0) For each activity on a particular day if the activity status in the “baseline” data capture (T‐0) is “In Progress”, then Value = 1. If any status other than “In Progress”, then Value = 0.

In Progress Count (Values 1 or 0) For each activity on a particular day if the activity status in the current schedule is “In Progress”, then Value = 1. If any status other than “In Progress”, then Value = 0.

Baseline Completed Count (Values 1 or 0) For each activity on a particular day if the activity status in the “baseline” data capture (T‐0) is “Completed”, then Value = 1. If any status other than “Completed”, then Value = 0.

Completed Count (Values 1 or 0) For each activity on a particular day if the activity status in the current schedule is “Completed”, then Value = 1. If any status other than “Completed”, then Value = 0.

Sheduled and Completed Count

(Values 1 or 0) For each activity on a particular day if the activity was scheduled to complete (according to the “baseline data capture (T‐0)) and actually did complete (current schedule), then Value = 1. Otherwise, value is 0.

Scheduled and Not Completed Count

(Values 1 or 0) For each activity on a particular day if the activity was scheduled to complete (according to the “baseline data capture (T‐0)) and did not complete (current schedule), then Value = 1. Otherwise, value is 0.

Not Scheduled and Completed Count

(Values 1 or 0) For each activity on a particular day if the activity was not scheduled to complete (according to the “baseline data capture (T‐0)) but did complete (current schedule), then Value = 1. Otherwise, value is 0.

Emergent Remaining Count (Values 1 or 0) For each activity on each day if the activity did not exist in the "baseline" data capture (T‐0) and the activity status is “Not Started” or “In Progress” in the current schedule, then Value = 1. If the activity did exist in the "baseline" data capture (T‐0) or the activity status is "Completed", then Value = 0.

Emergent Count (Values 1 or 0) For each activity on a particular day if the activity did not exist in the “baseline” data capture (T‐0), then Value = 1. If the activity did exist in the “baseline” data capture (T‐0), then Value = 0.

Total (Value 1) For each activity on a particular day a count of the activity. 1 is the only valid value for this metric.

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 sum of all actual units for this activity throughout the life of the activity up to the point in time data capture.

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 to correctly account for a non‐midnight data date scenario.

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

Data Flow from P6 to P6 Analytics

The following pages show how the activity use cases in the documents Burn Down Details (Counts) and Burn Down Details (Units) flow from P6 to P6 Analytics during each day’s data capture run.

Initial data capture occurs on 2/16/2014 (“baseline” (T-0) data capture)

Work Down Date – 2/16/2014

Data Date – 2/17/2014 00:00

ETL Process Date (Data Capture Date) – 2/16/2014

P6

Schedule Updates

AC1: Started and Completed Before Work Down Date (02/16/2014) o Status: Complete o Actual Units: 10 * o Remaining Units: 0

AC2: Started Before Work Down Date (02/15/2014), will complete on Day 1 (02/17/2014) o Status: In Progress o Actual Units: 34 o Remaining Units: 6

AC3: Started and Completed on Work Down Date (02/16/2014) o Status: Complete o Actual Units: 10 o Remaining Units: 0

AC4: Started on Work Down Date (02/16/2014) and Completed on Day 1 (02/17/2014) o Status: In Progress o Actual Units: 14 o Remaining Units: 16

* Since this occurred prior to the Work Down Date it will be filtered out of the Burn Down charts by default.

P6 Analytics Counts

Metric Value Details

Original Remaining 5 Total non‐complete activities remaining at the time of this data capture (02/16/2014) up to the data date (02/17/2014 00:00). (AC2, AC4, AC5, AC6, AC8)

Emergent Remaining 0 No emergent activities exist at the time of this data capture.

Total # of Activities 6 Total number of activities, not including those completed before this data capture. (AC2, AC3, AC4, AC5, AC6, AC8)

Baseline Work Down 5 Total non‐complete activities remaining, since this day’s capture is the “baseline” (T‐0) data capture. (AC2, AC4, AC5, AC6, AC8)

Current Work Down 5 Forecasted total non‐complete activities remaining at the end of this day. (AC2, AC4, AC5, AC6, AC8)

Units


Original Remaining 52 Remaining Units Burn (52). (AC2(6), AC4(16), AC5(10), AC6(10), AC8(10))


Total Man Hours 110 Total man hours, not including those completed before this data capture. (AC2(40), AC3(10), AC4(30), AC5(10), AC6(10), AC8(10))

Baseline Work Down 52 Remaining Units, since this day’s capture is the “baseline” (T‐0) data capture. (AC2(6), AC4(16), AC5(10), AC6(10), AC8(10))

Current Work Down 52 Forecasted total Remaining Units at the end of this day. (AC2(6),

AC4(16), AC5(10), AC6(10), AC8(10))

Day 1 (data capture occurs on 2/17/2014)


Data Date – 2/17/2014 13:00


P6

Schedule Updates

AC2: Started Before Work Down Date, Completed on Day 1 o Status: Complete o Actual Units: 40 o Remaining Units: 0

AC4: Started on Work Down Date and Completed on Day 1 o Status: In Progress o Actual Units: 25 o Remaining Units: 5

AC5: Started and Completed on Day 1 (As Scheduled) o Status: In Progress o Actual Units: 5 o Remaining Units: 5

AC8: Stared and Completed Day 1 (Deleted on Day 3) o Status In Progress o Actual Units: 5 o Remaining Units: 5

P6 Analytics Counts


Original Remaining 4 Total non‐complete activities remaining at the time of this data capture (02/17/2014) up to the data date (13:00). (AC4, AC5, AC6, AC8)


Total # of Activities 6 Total number of activities, not including those completed before the “baseline” (T‐0) data capture. (AC2, AC3, AC4, AC5, AC6, AC8)

Baseline Work Down 1 Total non‐complete activities remaining at the end of this day (02/17/2014) according to the “baseline” (T‐0) data capture. (AC6)

Current Work Down 1 Forecasted total non‐complete activities remaining at the end of this day. (AC6)

Units


Original Remaining 25 Non‐emergent Remaining Units Burn (10) + Remaining Units (15). (AC4(5), AC5(5), AC6(10), AC8(5))


Total Man Hours 110 Total man hours, not including those completed before the “baseline” (T‐0) data capture. (AC2(40), AC3(10), AC4(30), AC5(10), AC6(10), AC8(10))

Baseline Work Down 10 Remaining Units at the end of this day based on the “baseline” (T‐0) data capture. AC6(10)

Current Work Down 10 Forecasted total Remaining Units at the end of this day. AC6(10)



Data Date – 2/18/2014 13:00


P6

Schedule Updates

AC4: Started on Work Down Date and Completed on Day 1 o Status: Completed o Actual Units: 30 o Remaining Units: 0

AC5: Started and Completed on Day 1 (As Scheduled) o Status: Completed o Actual Units: 10 o Remaining Units: 0

AC8: Stared and Completed Day 1 (Deleted on Day 3) o Status: Completed o Actual Units: 10 o Remaining Units: 0

AC6: Started on Day 2 and Completed on Day 3 (Late) o Status: In Progress o Actual Units: 5 o Remaining Units: 5

AC7: New Activity 1 added on Day 2 and Completed on Day 3 o Status: Not Started (NEW ACTIVITY) o Actual Units: 0 o Remaining Units: 10

P6 Analytics Counts


Original Remaining 1 Total non‐complete activities remaining at the time of this data capture (02/18/2014) up to the data date (13:00). (AC6)

Emergent Remaining 1 New activity added and not complete at the time of this data capture. (AC7)

Total # of Activities 7 Total number of activities, not including those completed before the “baseline” (T‐0) data capture. (AC2, AC3, AC4, AC5, AC6, AC8 and AC7)

Baseline Work Down 0 Total non‐complete activities remaining at the end of this day (02/18/2014) according to the “baseline” (T‐0) data capture. Not including emergent.

Current Work Down 0 Forecasted total non‐complete activities remaining at the end of this day.

Units


Original Remaining 25 Non‐emergent Remaining Units Burn (0) + Remaining Units (5). (AC6(5))

Emergent Remaining 10 Emergent Remaining Units Burn. (AC7(10))

Total Man Hours 120 Total man hours, not including those completed before the “baseline” (T‐0) data capture. (AC2(40), AC3(10), AC4(30), AC5(10), AC6(10), AC8(10), AC7(10))

Baseline Work Down 0 Remaining Units at the end of the day based on “baseline” (T‐0) data capture.

Current Work Down 10 Forecasted total Remaining Units at the end of this day. (AC7(10))



Data Date – 2/19/2014 13:00


P6

Schedule Updates

AC8: Started and Completed Day 1 (Deleted on Day 3) o Status: DELETED o Actual Units: 30 o Remaining Units: 0

AC6: Started on Day 2 and Completed on Day 3 (Late) o Status: Completed o Actual Units: 20 (+10 from Planned Units) o Remaining Units: 0

AC7: New Activity 1 added on Day 2 and Completed on Day 3 o Status: Completed o Actual Units: 5 (‐5 from Planned Units) o Remaining Units: 0

P6 Analytics Counts


Original Remaining 0 Total non‐complete activities remaining at the time of this data capture (02/19/2014) up to the data date (13:00).


Total # of Activities 7 Total number of activities, not including those completed before the “baseline” (T‐0) data capture. (AC2, AC3, AC4, AC5, AC6, AC8 and AC7)

Baseline Work Down 0 Total non‐complete activities remaining at the end of this day (02/19/2014) according to the “baseline” (T‐0) data capture.

Current Work Down 0 Forecasted total non‐complete activities remaining after that day.

Units


Original Remaining 0 Non‐emergent Remaining Units Burn (0) + Remaining Units (0).

Emergent Remaining 0 Emergent Remaining Units Burn.

Total Man Hours 115 Total man hours, not including those completed before the “baseline” (T‐0) data capture. (AC2(40), AC3(10), AC4(30), AC5(10), AC6(10), AC8(10), AC7(5))

Baseline Work Down 0 Remaining Units at the end of the day based on “baseline” (T‐0) data capture.

Current Work Down 0 Forecasted total Remaining Units at the end of this day.

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: data flow · overview oracle primavera p6 analytics includes the...

Documents