Oracle Projects enables you to replan a workplan based on the progress collected for the tasks.
For example, during the execution of a workplan, resources and task managers report progress. After reviewing the progress, as a project manager, you observe that the estimate at completion and the schedule based on the actual dates has deviated from the planned values. Estimate at completion is the actual cost and quantity of work completed to date plus the predicted costs and quantities likely to be used in the future.
You can choose to replan the workplan so that the plan reflects the latest estimates.
You can apply the submitted progress to a working workplan version. Oracle Projects calculates the new plan amounts using the following formula:
Plan = Actual + ETC
Note: Oracle Projects uses the conversion rate that is effective on the
start date of the PA Period or GL Period associated with the actual transaction to convert actual cost from the transaction currency to the planned currency when the currencies are different.
After you apply the progress, you can further modify the ETC on the tasks or resources.
If no resource assignments exist for a task, you can directly modify ETC at the task level. Otherwise, you must modify ETC at the resource assignment level. You can modify ETC by period if periodic data is available for the resource assignment.
You can modify the physical percent complete for a task for the working workplan version. Oracle Projects rolls up the revised physical percent complete to higher task levels.
Optionally, you can send the workplan to an external scheduling tool to adjust the schedule by actual dates.
The progress values are available for the latest published version when you publish the working workplan version.
Note: When you publish the working workplan version, Oracle Projects publishes the workplan with the existing progress data for the working version and creates a new progress record for the next progress cycle As of Date.
Oracle Projects deletes all future and previous working progress records with As of Dates that correspond to the new progress record that it created during workplan publishing.
Example of Using Progress to Replan a Workplan
This example shows how you can apply progress to a working workplan version. In this example, all effort is in hours and the currency is U.S. Dollars.
Initially, you plan the original workplan version.
The following table shows the planned values for task 1.1 for the latest published workplan version.
Planned Effort Planned Cost
100 1000
Next, you collect progress for task 1.1.
The following table shows progress values for the latest published workplan version for task 1.1, as of 01-JAN-2005.
Planned
Effort Planned
Cost Actual
Effort Actual
Cost ETC
Effort ETC Cost As of Date
100 1000 25 250 120 1200 01-JAN-2005
When you review the progress, you observe that the estimate at completion effort is 145 hours (25 hours plus 120 hours), while the planned effort is 100 hours. You also see that the estimate at completion cost is 1450 USD (250 USD plus 1200 USD), while the planned cost is 1000 USD. As a result, you decided to replan the workplan.
Once you submit the progress for the latest published workplan version, you can apply the progress to a selected working workplan version. After you apply the progress, Oracle Projects updates the planned values for task 1.1. The following table shows the updated planned values for the working workplan version for task 1.1.
Planned Effort Planned Cost Actual Effort Actual Cost ETC Effort ETC Cost
25 + 120 = 145 250 + 1200 = 1450 25 250 120 1200
You can choose to publish this workplan version to make all stakeholders aware of the revised planned values. You can make further changes to the ETC before you publish.
While you are replanning the workplan, a team member submits additional progress records before you publish the working workplan version. The following table shows the new progress values for the latest published workplan version for task 1.1, as of
08-JAN-2005.
Planned
Effort Planned
Cost Actual
Effort Actual Cost ETC Effort ETC Cost As of Date
100 1000 35 350 90 900 08-JAN-2005
Note: The ETC values for the current working and published workplan versions can be different. In this example, after you submit the
additional progress records, the published workplan version has an ETC Effort of 90 hours and an ETC Cost of 900 USD for task 1.1, while the current working workplan version has an ETC Effort of 120 hours and an ETC Cost of 1200 USD for task 1.1.
After you publish the working workplan version, Oracle Projects submits a new progress record with the replanned values from the working version. Oracle Projects assigns the new progress record the next As of Date according to the progress cycle for
the workplan. In this example, Oracle Projects assigns 15-JAN-2005 for the As of Date.
Oracle Projects then uses the updated planned and actual values from the new progress record to recalculate ETC Cost and Effort.
You review progress values after you publish the working workplan version without applying the latest progress. Oracle Projects always uses the latest Planned Cost and Effort from the working workplan version to update the new published workplan version. In this example, the Planned Cost is 1450 USD and the Planned Effort is 145 hours. For the new published workplan version, you observe that Oracle Projects used an Actual Cost of 350 USD and an Actual Effort of 35 hours to recalculate ETC Cost and Effort (Plan - Actual = ETC). As a result, ETC Cost and Effort for the new published workplan version do not match ETC Cost and Effort for the working workplan version.
For example, the ETC effort for the new published version is 110 hours (145 Planned hours - 35 Actual hours = 110 ETC hours), while the ETC Effort for the working version continues to be 120 hours (145 Planned hours - 25 Actual hours = 120 ETC hours). This difference in ETC is present because you did not apply the latest progress to the working workplan version before you published it and, as a result, the latest Actual Cost and Effort values are not available to the working workplan version.
The following table shows the progress values for the new published workplan version.
Planned
ETC Effort ETC Cost As of Date
145 1450 35 350 145 - 35 = 110 1450 - 350 = 1100 15-JAN-2005
Alternatively, you can apply the latest submitted progress to the working workplan version, revise ETC as needed, and then publish the working workplan version to ensure that the ETC values are the same for the working workplan version and the new published workplan version. In this case, Oracle Projects uses the revised ETC values from the working workplan version to update the new published workplan version.