Project: Maximum Work per Resource Assignment (83701)

MORE INFORMATION

Consider the following example: A task's resource has the maximum hours assigned and it is a resource driven task. The task's duration, assuming a 24-hour seven-day-week calendar and 100 resource units, would be about 2 months. This may not be long enough in cases where a resource is scheduled to work constantly for 2 or more months.

In Project 3.0, one way you can work around this constraint is to fix the task's duration at the correct amount. Then, add the same resource more than one time and add the appropriate amount of delay in order to force the resource to "span" the same amount of time as the task. By doing this, you can cause the resource's cost and work to appear continuous for the task's duration when looking at a view such as the Resource Usage.

In Project versions 1.0 and 1.1, you can fix the task's duration, but you cannot apply the same resource to the same task more than once. You could, however, apply multiple resources to the tasks that have the same name but different ID numbers so that for a given task you can track the total work and cost information. When you view a Resource Usage view, however, all of the work and costs for the resources will occur during the first 141,191.33 hours (scheduling from start). To prevent this, you can modify the resource calendars so that each successive resource assignment cannot begin working until the prior resource is finished working.