though not a widely recommended practice, there are times when one might want to de-progress or remove actuals from a primavera p6 schedule. some reasons for wanting to return a schedule after weeks or months of progress updates to its state at project start are:
- baseline not being set before applying actuals
- wrong or no resource assignments applied when baseline was set
- wrong logic relationships in schedule when baseline was set?
a downside to removing actuals from a schedule is that the “new” schedule will need to be progressed again to the last reporting date. this means all periodic updates carried out on the last schedule have to be repeated with same data as before.
here’s how to remove actuals from a p6 schedule
this quick tip will show how to remove actuals from a primavera p6 schedule, returning the project to its planned values at project start in 7 steps. it shouldn’t matter what version of p6 you have. we assume prior knowledge of how to use p6’s global change facility. assuming we have the schedule in figure below from which we want to remove all traces of actuals with the following additional columns visible in the layout aside the usual suspects: performance % complete, original duration, actual duration, remaining duration, actual labor units, actual nonlabor units & actual total cost.
all the columns listed above will be used to confirm at the end of the tutorial if we have returned our schedule to its original state at project start.
step 1 – project calculation tab setting
in the projects view, select the open project and click on the calculations tab.
in the calculation tab, ensure that the link budget and at completion for not started activities checkbox is ticked and then select the reset remaining duration and units to original option button.
this step is required so that when we change the status of all our activities to not started, the remaining duration for our activities will be changed to same values as original duration.
in the next 2 steps, we need to change all actual labor units & actual nonlabor units to 0. one way of doing this is to use the fill down facility, but imagine if you have a schedule of thousands of activities, then the use of fill down will be tedious. my preferred method is the use of global change as this enables one to save and reuse the global change in other schedules if required.
step 2 – global change actual labor units & cost
run the global change shown in the figure below to change all actual labor units & actual labor cost to 0.
step 3 – global change actual nonlabor units & cost
run the global change shown in the figure below to change all actual nonlabor units & actual nonlabor cost to 0.
step 4 – global change actual material units
run the global change shown in the figure below to change all actual material units to 0.
step 5 – global change expense cost % complete
run the global change shown in the figure below to change all actual expense cost to 0 by changing expense cost % complete to 0.
step 6 – global change activity status
run the global change shown in the figure below to change activity status for all activities to not started.
step 7 – schedule as at planned start
run time analysis (f9) as at project start by setting the data date to project planned start. you can get the project planned start from the dates tab of the projects view.
result
our schedule should now have the following for all activities as shown in figure below:
- performance % complete = 0
- original duration = remaining duration
- actual labor units = 0
- actual non-labor units =0
- actual total cost= 0
the schedule has no actuals and is now ready to readdress the reason for removing all actuals. use these steps and save the global change scripts so you can have the ability to remove actuals at your fingertips.
your turn
have you ever had to remove actuals from a schedule? why? what approach did you take?
