Deleted After Outage Start Use Case
This use case describes what happens when an activity is completed as scheduled on Day 1 and deleted on Day 3.
P6 Values Table
Field | Planned Value | Actual Value |
|---|---|---|
Start | 4/01/2013 12:00 a.m. | 4/01/2013 12:00 a.m. |
Finish | 4/01/2013 10:00 a.m. | 4/01/2013 10:00 a.m. |
Duration | 10 hours | 10 hours |
Units | 10 | 10 |
Burn Down Results
- 3/31: When the ETL process runs, this activity has 10 Remaining Units and it is scheduled to finish on Monday, 4/01/2013 (Day 1).
- 4/01: The activity is completed in P6 and counted as complete when the ETL process runs. The Actual Units Burn value of 10 will continue to be captured after completion so Cumulative Totals can be counted by day.
- 4/02: There will be no change on 4/02.
- 4/03: The activity is deleted in P6 and, when the ETL process runs, all records for this activity are removed from the Burn Down subject area.
Day | Remaining Units Burn | Actual Units Burn | Completed | Emergent Count |
|---|---|---|---|---|
Day 0 (3/31) (Day and values deleted) | 0 | 0 | 0 | 0 |
Day 1 (4/01) (Day and values deleted) | 0 | 0 | 0 | 0 |
Day 2 (4/02) (Day and values deleted) | 10 | 0 | 0 | 1 |
Day 3 (4/03) (Day and values deleted) | 0 | 10 | 1 | 0 |
Note: Alternatively, this activity can be marked or coded as deleted in P6. The activity is not physically deleted, but is filtered out in Oracle Business Intelligence.
Last Published Tuesday, December 5, 2023