The Calculation option in Microsoft Project is set to On by default. As a result, when you open a CA Clarity PPM project in Microsoft Project, the project is recalculated. The start and finish dates of tasks are automatically adjusted to respect the dependency chain between them. For example, create two tasks, Task 1 and Task 2, with a Finish/Start dependency between them. The start date of Task 2 is calculated relative to the finish date of Task 1 based on the dependency link. The Gantt chart is also updated accordingly. The subsequent tasks are calculated similarly summing up the task level values for Remaining Work, Actual Work, and Work at the Summary Task level.
Prerequisites:
You can set the Calculation option in Microsoft Project to Off (manual), so that a CA Clarity PPM project is not recalculated when you open it in Microsoft Project. When you use manual calculation, Microsoft Project performs in these ways:
In the following example, the remaining work for Project 1 and Summary is not calculated and displays as zero hours. This happens because the project is not calculated when manual calculation is enabled.

Press F9 or use the Calculation Needed button in Microsoft Project to calculate the project. Microsoft Project calculates the plan and the rolled up values of all the tasks are displayed. Also, the tasks appear on the Gantt chart based on the Finish/Start dependency relationships.
When you enable manual calculation, tasks remain stationary on the Gantt chart and hours do not roll up to the summary task or project levels.
For example, enable manual calculation in Microsoft Project and also set the loading pattern to uniform in CA Clarity PPM. You then create a project in CA Clarity PPM with three tasks. Create a summary task and demote tasks as children under the summary task. Apply Finish/Start dependencies and identify remaining work and record actual work.
Open the CA Clarity PPM project in Microsoft Project. Because manual calculation is enabled, the project is not calculated and the results appear as shown in the following figure:

Press F9 to calculate the project. The results appear as shown in the following figure:

When you enable manual calculation, the summary task dates are not automatically calculated.
For example, enable manual calculation in Microsoft Project and also set the loading pattern to uniform in CA Clarity PPM. You then create a project in CA Clarity PPM with some tasks without dependencies. Create a summary task and demote tasks as children under the summary task. Drag the tasks manually on the Gantt chart to reflect the requirements of the project manager.
Open the CA Clarity PPM project in Microsoft Project. Because manual calculation is enabled, the project is not calculated and the results appear as shown in the following figure:

Press F9 to calculate the project. The results appear as shown in the following figure:

For manual calculation to work, you must configure settings both in Microsoft Project and CA Clarity PPM in any order:
You must set the calculation option to Off in Microsoft Project. This setting is global and is saved in the .mpp file of each project. Any .mpp project that is created after configuring this setting inherits this setting.
Note: For .mpp projects that were created before configuring this setting, the project manager must update the global setting for that project. To update the global setting, open the plan in Microsoft Project from CA Clarity PPM and follow these steps.
Microsoft Project 2007
Follow these steps:
Microsoft Project 2013 or 2010
Follow these steps:
You must set the loading pattern to uniform using you administrator permissions.
Follow these steps:
The following exceptions apply when manual calculation is enabled:
If you use timesheets, the actual hours that are recorded against tasks could override the configuration. The start date, finish date, or both can change.
For example, Task 1 starts on May 1 and Ken records eight hours on April 20, a date before the task starts. The next time the project is opened in Microsoft Project, the start date of the task changes to April 20. The same is true if Ken records actual hours against the task after its finish date. Microsoft Project moves the finish date to the last recorded actual hours.
Resource leveling also calculates the project. Do not use resource leveling if you do not want Microsoft Project to calculate your project.
Applying task constraints may trigger Microsoft Project to calculate the project even though the global setting for the Calculation option is set to Off.
Resource leveling in Microsoft Project schedules the project based on the availability of the team members so that no resource is overallocated. Resource leveling delays tasks, splits tasks, and delays resource assignments to adjust the resource allocation. Resource leveling also calculates the project as it resource levels. Therefore, level the resources only if you want Microsoft Project to calculate your project.
Follow these steps:
Microsoft Project automatically sets the start date for both the tasks to be today or the start date of the project depending on your Microsoft Project configuration.
The tasks remain stacked one upon the other indicating that the plan must be calculated.

The tasks remain stacked one upon the other indicating that the plan must be calculated. As you can see below, the resource is expected to work 16 hours that day.

Microsoft Project automatically calculates or schedules the tasks so that the resource works eight hours a day of availability and therefore resolves overallocation. If you do not want the task positions to move, do not resource level.

When you apply task constraints, automatic calculation may be triggered even if the global setting is manual.
Follow these steps:
Microsoft Project automatically sets the start date to be today or the start date of the project depending on your Microsoft Project configuration.
Microsoft Project marks Task 1 with a Start No Earlier constraint. Hover over the Calendar icon to see this constraint.
Microsoft Project automatically sets the start date to be today or the start date of the project depending on your Microsoft Project configuration.
Microsoft Project marks Task 2 with a Start No Earlier constraint. Hover over the Calendar icon to see this constraint.
When you create task constraints, Microsoft Project automatically calculates the tasks even though the global setting for the Calculation option is set to Off.

The following example shows how reconciling resource overallocations manually does not trigger automatic calculation.
Follow these steps:
Microsoft Project automatically sets the start date to be today or the start date of the project depending on your Microsoft Project configuration.
The tasks remain stacked one upon the other indicating that the plan must be calculated.

The task remains frozen on the date you manually set indicating that the plan must be calculated.

|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|