K
Kerry
we've finally got our management team looking a at resrouce capacity But,
we use generic resrouces when we're not sure who is going to perform a task.
Then prior to the task becoming active, we force a real beating heart on the
task.
Here's the question. Using Resource Center, they are selecting all their
resources, to see what they have on their plate. To see everything, they
include the generic resources. For instance, if they're our DBA team, they
select all the DBA's, and the generic DBA's. In some cases we have identified
multiple generics for one team, due to the different skill sets. So there
could be a number of generics.
Here's the problem. The generics are set 80% available units, just like the
real resources, so assiging a generic won't impact schedules. What that does
increase the teams capacity in resource center (which really isn't true). Is
there any way around the capacity being overstated, with generics, without a
negative impact on the schedules? I'm guessiing we can't have our cake and
eat it too.
we use generic resrouces when we're not sure who is going to perform a task.
Then prior to the task becoming active, we force a real beating heart on the
task.
Here's the question. Using Resource Center, they are selecting all their
resources, to see what they have on their plate. To see everything, they
include the generic resources. For instance, if they're our DBA team, they
select all the DBA's, and the generic DBA's. In some cases we have identified
multiple generics for one team, due to the different skill sets. So there
could be a number of generics.
Here's the problem. The generics are set 80% available units, just like the
real resources, so assiging a generic won't impact schedules. What that does
increase the teams capacity in resource center (which really isn't true). Is
there any way around the capacity being overstated, with generics, without a
negative impact on the schedules? I'm guessiing we can't have our cake and
eat it too.