These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!

 FAQ Members List Calendar Search Today's Posts Mark Forums Read

 dmabram Member 2008-02-06, 01:27 PM I am having a problem allocating resources for tasks that should happen in parallel. I have a 2 day task that is constrained over 3 days, lets say it is constrained to start Jan 1-3. I have a 1 day task constrained over exactly 1 day, lets say its constrained Jan 2-Jan2. I assigned one resource to both tasks. In theory there are three days of effort, three days duration, and the resource should allocate properly without over or under allocation during that time period. This works fine if the task constraints are such that the tasks can be done in their entirety in series. If the constraints requires the tasks get worked in parallel to complete (that is employee starts task 1, works it for a day, starts task 2, works for a day to completion, finishes task 1 the third day) the resource is always shown as over-allocated during the overlap. Is there another way to model to fix this issue without hackery (breaking task 1 into 2 tasks, constantly juggling percent allocation)? When you have lots resources and lots of tasks with fixed date constraints, it seems working tasks in parallel in this manner is a necessity. Post 1
 dmabram Member 2008-02-09, 08:40 PM Is it possible to have this logged as a bug or feature request? Post 2
Quote:
 Originally Posted by dmabram I am having a problem allocating resources for tasks that should happen in parallel. I have a 2 day task that is constrained over 3 days, lets say it is constrained to start Jan 1-3. I have a 1 day task constrained over exactly 1 day, lets say its constrained Jan 2-Jan2. I assigned one resource to both tasks. In theory there are three days of effort, three days duration, and the resource should allocate properly without over or under allocation during that time period. This works fine if the task constraints are such that the tasks can be done in their entirety in series. If the constraints requires the tasks get worked in parallel to complete (that is employee starts task 1, works it for a day, starts task 2, works for a day to completion, finishes task 1 the third day) the resource is always shown as over-allocated during the overlap. Is there another way to model to fix this issue without hackery (breaking task 1 into 2 tasks, constantly juggling percent allocation)? When you have lots resources and lots of tasks with fixed date constraints, it seems working tasks in parallel in this manner is a necessity.
There isn't a way to do this besides the work-around you pointed out. I'll file a request for this in our database.

 cwingrav Member 2009-05-18, 06:16 PM Would love to see this but not as a feature request but a bug as dmabram suggested. Post 4