J
John Sitka
1.) Priority based automated resource assignment, reassignment and
calculation to illiminate overallocation.
I'm trying to develop what this really should be "called" so please
interpret via this example.
We have a set of resources in a pool that can all handle a certain task.
R1 does it best and is the preferred resource
R2 does an OK job of it
and R3 is used only if it means we can finish this project on time.
Well On time is a very big priority so no one here will complain if R3 is
available and gets used.
Now can I set up project to level in such a way that a trial and error
distribution of these
resources across the set of tasks they are valid for takes presedence over
moving the
timeline to illiminate overallocations.
2.) Variable Critical Path.
Again when it comes to leveling this is a means of allowing exceptions to
the predecessors when the
only other option is to move an end date.
The concept can best be described as....
It is nice that each task follows the next one but there is a level of
parallelism or alternate routing
that can take place when certain milestones are reached. The general plan
would not need to recognize the
alternates when there is no overallocation, and the plan would have a
logical and well defined flow.
A task reordering would only become necessary when an overallocation exists.
This reordering could of
course follow many branches or split to a parrallel subtask then come back
online. How to define?
Will it interact in a prioritized way with the two other constraints on the
project.
In Summarys......
Usual leveling until the end date is pushed late.
Then resource reassignment to alternates when usual leveling pushes end
date.
Then utilize critical path alternates when both usual levelling and
resources reassignment
fail to remove overallocations AND pushes end date.
I hope this is clear but I will try again as I wirte it out a couple times.
But these are the requirements of the software we need for our schedule.
What I need to know is if Project can do this for me. Any form or concept
is fine but the result needs to be that the levelling is constrained by end
date
and the other alternatives be tried first. Those alternatives would be the
suitable
but not previously chosen resource or the alternate path or order of tasks.
Automated of course because obviously there would be a huge number of
possible
combinations that would need to be tried during the leveling process to find
the best result.
Thanks.
calculation to illiminate overallocation.
I'm trying to develop what this really should be "called" so please
interpret via this example.
We have a set of resources in a pool that can all handle a certain task.
R1 does it best and is the preferred resource
R2 does an OK job of it
and R3 is used only if it means we can finish this project on time.
Well On time is a very big priority so no one here will complain if R3 is
available and gets used.
Now can I set up project to level in such a way that a trial and error
distribution of these
resources across the set of tasks they are valid for takes presedence over
moving the
timeline to illiminate overallocations.
2.) Variable Critical Path.
Again when it comes to leveling this is a means of allowing exceptions to
the predecessors when the
only other option is to move an end date.
The concept can best be described as....
It is nice that each task follows the next one but there is a level of
parallelism or alternate routing
that can take place when certain milestones are reached. The general plan
would not need to recognize the
alternates when there is no overallocation, and the plan would have a
logical and well defined flow.
A task reordering would only become necessary when an overallocation exists.
This reordering could of
course follow many branches or split to a parrallel subtask then come back
online. How to define?
Will it interact in a prioritized way with the two other constraints on the
project.
In Summarys......
Usual leveling until the end date is pushed late.
Then resource reassignment to alternates when usual leveling pushes end
date.
Then utilize critical path alternates when both usual levelling and
resources reassignment
fail to remove overallocations AND pushes end date.
I hope this is clear but I will try again as I wirte it out a couple times.
But these are the requirements of the software we need for our schedule.
What I need to know is if Project can do this for me. Any form or concept
is fine but the result needs to be that the levelling is constrained by end
date
and the other alternatives be tried first. Those alternatives would be the
suitable
but not previously chosen resource or the alternate path or order of tasks.
Automated of course because obviously there would be a huge number of
possible
combinations that would need to be tried during the leveling process to find
the best result.
Thanks.