To use MPM's Replanning function effectively, you should understand how it works and the assumptions that the function makes. There are exceptions to these rules if you are setting baseline equal to actuals when there is no established baseline.
You can replan a project only if the following criteria are met:
The WBS element(s) must have at least one estimate, even if the estimate has a zero balance. If there are no estimates, MPM skips the WBS element when it performs the replan.
If there are estimates, the WBS element(s) must have appropriate cumulative values through the replan month. If there are no cumulative values, MPM skips the WBS element(s) when it performs the replan.
You can perform a replan on in-process and completed work packages only. You cannot replan future projects that have not started.
In-process work packages have one or more of the following:
Cumulative BCWS (Budgeted Cost of Work Scheduled)
Cumulative BCWP (Budgeted Cost of Work Performed)
Cumulative ACWP (Actual Cost of Work Performed)
Work packages are defined as completed when the WBS percent complete equals 100%.
When replanning, no assumptions are made about future BCWS or the milestones for BCWP. It is your responsibility to replan future work by manually adjusting BCWS and milestone weights for BCWP after replanning.
When you perform a replan, the following happens:
Replan estimates are stored in the format Replan *EOC code (for example: Replan *L).
BCWS is adjusted at all costing levels (equivalent persons, hours through total price).
BCWP is adjusted at costing levels hours through total dollars.
Standard hours are not calculated.
BCWS is summed at each burden level if you are setting Baseline = Earned Value or Actuals. Therefore, detailed burdening information for a replan estimate is not available.
If you want to restore your data to its before replan state, it is always best to go to the backup you made of the data prior to the replan. If, for some reason, you cannot go to the backed up data, you may use the procedures that follows for the options listed.
If you perform a replan using the Set Basline = Actuals or Set Baseline = Earned Value option, replan estimates can be deleted using the Delete Project Data option in Project Maintenance.
If you have incorrectly performed a replan using Set Earned Value = Actuals and want to restore the date to its before replan state, you can restatus and recalculate BCWP in the replan month.
If you perform a replan using the Set Baseline and Earned Value = Actuals option, you can delete replan estimates using the Delete Project Data option in Project Maintenance, then restatus and recalculate BCWP in the replan month.
Distributed elements may not be replanned. Replanning should be done within the subproject and results will be rolled up and transferred via the normal distributed update cycle.
Replans can be performed more than once on a WBS. If you perform a replan more than once in the same month, the earlier value is cleared and the new replan is performed.
If you have performed one or more replans and then go back and make changes to data that occurred prior to the replan, you must also go back and redo the replans from the earliest to the latest in sequence.
All replans are calculated by adjusting cumulative values through the month and year specified for the replan.
The Replanning function is designed to be used when the WBS elements being replanned have BCWS, BCWP, and ACWP loaded at the same level of the WBS tree. If estimates and actuals are entered at different levels, you must replan the project manually.