Discussion:
ProjDateDiff with resource calendars exceeding 100%
(too old to reply)
d***@gmail.com
10 years ago
Permalink
Hello all,

I am using MS Project 2013 and trying to calculate utilization of a resource.

As this is an estimation exercise I am using resources as resource pools by giving them greater than 100% max units.

For example: The resource "Developers" will have a max units of 300% representing the fact that I will have 3 developers assigned.

This avoids me having to juggle resource names around tasks to get the best utilization and avoid leveling delays.
This also of course comes with the assumption that everyone in that pool is interchangeable.

This works well and has for some time. No problems yet.

I am now trying to calculate utilization of that resource so I can determine how much extra work I can absorb or if it is too risky because the utilization is too high (i.e. 97%) and I won't be able to absorb issues and extra work that come up.

In my resource sheet, I am creating a custom field for utilization and here is the formula:
( [Work] / ProjDateDiff( [Start], [Finish], [Name] ) ) * 100

I have tried with and without the calendar parameter and it does not make a difference since it is in the resource view, that is the default when the calendar parameter is omitted.

My problem is as follows
When I assign all the work out, some tasks at 200% and some at 400% and so on, my total 'Work' is greater than the result of ProjDateDiff( [Start], [Finish], [Name] ).

I can only assume that this is because ProjDateDiff is assuming max units will not exceed 100%.

Is there any way to get ProjDateDiff (or a similar function) to acknowledge max units exceeding 100%?

My next test is to do the reverse:
Quadruple the hourly rate and then express the allocation in percentages of that.
For example:
- Max Units = 100%
- Rate = 4 time the normal
This would represent 4 people in this resource pool
Resource allocation on tasks would be:
- 25% = 1 resource
- 50% = 2 resources
- 75% = 3 resources
- 100% = 4 resources

However, this only works for costing and actually causes problems in time calculations because 25% of a resource is only a 2 hour day when in reality it needs to be an 8 hour day.

Any help would be greatly appreciated.
d***@gmail.com
10 years ago
Permalink
After this problem is solved (IF), my next question is going to be about acknowledging varying max units over time.

Specifically when I enter resource availability table in the resource itself and say
from day x to date y available at 200%
from date a to date b available at 400%
and so on.

Loading...