- sys_workdown_date: 3/31/2013
- Data Date: 3/31/2013
- ETL Process Date: 3/31/2013 11:59 p.m.
On Day 0, two activities are started and in-progress. One activity is started and completed on 3/31/2013. At the time the ETL process is run, the schedule is captured in the Burn Down.
This ETL process capture point becomes the Burn Down baseline of the schedule in Primavera Analytics, as 3/31/2013 is the date specified in the sys_workdown_date Project UDF value. All activities completed on or after the 3/31/2013 date until the project’s Finish Date receive these baseline metrics.
Schedule Updates
- Started before Outage Project Snapshot Spanning into Outage - AC2
- Status: In-progress
- Actual Units: 48
- Remaining Units: 2
- Completed Day of Outage Project Snapshot - AC3
- Status: Complete
- Actual Units: 10
- Remaining Units: 0
- Pre-Outage Work Spanning into Outage - AC4
- Status: In-progress
- Actual Units: 24
- Remaining Units: 6
Burn Down Hours
Burn Down Hours Summary
- 38 Baseline Hours remain
- 38 Actual Hours remain
- 130 Total Hours (Actual and Remaining)
At the time the ETL process is run on 3/31/2013 there are 38 hours remaining in the schedule. There are 130 Total Hours remaining, which is a combination of the Actual Units Burn and Remaining Units Burn.
The table shows a subset of the activity metrics that are summarized in the Burn Down Hours line-bar chart.
Burn Down Counts
Burn Down Counts Summary
- 5 Baseline Activities remain
- 5 Actual Activities remain
- 7 Total Activities (Complete and Remaining)
At the time the ETL process is run on 3/31/2013, there are five activities with hours remaining in the schedule. There are seven Total Activities, which include activities with Remaining Units and all other activities included as of the sys_workdown_date ETL process snapshot.
The table shows a subset of the activity metrics that are summarized in the Burn Down Counts line-bar chart.
