| Solution ID: prim29778 |
| Why is the Planned (Original) Duration for Resource Assignments different than the Activity Planned (Original) Duration? |
| Status: Reviewed |
| Version(s): 4.1, 5.0 |
| Problem: | Why is the Planned (Original) Duration for Resource Assignments different than the Activity Planned (Original) Duration? Example: Activity Planned Duration = 20h Resource Planned Duration = 100h
|
| Problem: | How to get the Resource dates to be different that the activitys’? |
| Fix: | Version 4.1 and greater has a new feature called “non-driving resources”. This feature is controlled by the Resource column called Drive Activity Dates. With the box unchecked, the resource assignment will be considered non-driving and will not affect activity dates, durations, or costs. In the above example, both resources are non-driving. Therefore, the resource assignment’s Planned Duration will not roll-up to the activity level duration. If the desired result is to have the resource assignments drive the activity, check the box “Drive Activity Dates”. If the desired result is to have the Resource assignments not drive the activity and work on different dates, uncheck the box “Drive Activity Dates”. Then a lag can also be placed on the Resource for it to start after the activity. Note: The resource calendar will be ignored if the Activity Type is set to Task Dependent. The only time the Resource calendar is used is if the Activity type is Resource Dependent. |
