C
CK_PMP
I've built a schedule that uses a mix of elapsed days ("edays") and business
days ("days"). Some tasks are given in terms of one, and some in terms of
another. (Yes, it's necessary). I'm assigning resources to tasks not by the
normal utiliation percentage, but rather by the number of hours (work) each
resource will be devoting to a particular task, and letting MS Project
calculate their actual utilization over the span of the task. These are not
"effort-driven" tasks, but rather fixed-duration tasks. (e.g., we have 30
days to complete task X, and I'm assigning folks to work between 4 and 16
hours each on task X between 09/01/08 and 09/31/08).
This works great for tasks that are given in terms of working days ("days"),
as Project uses the default calendar and assumes 8 hrs/day. (So someone who
will devote 4 hours to a 5 day task will have a utilization of 10%).
However, it doesn't work at all for tasks given in total elapsed days, since
Project is assuming 24/7 working hours. I want to be able to specify that a
task will take place over 30 elapsed days, but will only be worked on during
normal work hours as specified in the project calendar. The Gantt Chart is
using the standard work calendar. Unfortunately, individual tasks that are
given in terms of edays can be forced to use the standard calendar (they
default to "None.")
There are two possible fixes:
1) Most desirable would be to force Project to only count work against
normal working hours, even if a task is expressed in "edays."
-OR-
2) Do a universal translation from edays to days. There are far too many
tasks to to this manually. A universal replace wont work because "30 edays"
is a very different duration than "30 days." So I'd need Project to determine
when 30 edays means 20 days and when it means 19 days, and so forth, based on
the calendar.
Thanks in advance.
days ("days"). Some tasks are given in terms of one, and some in terms of
another. (Yes, it's necessary). I'm assigning resources to tasks not by the
normal utiliation percentage, but rather by the number of hours (work) each
resource will be devoting to a particular task, and letting MS Project
calculate their actual utilization over the span of the task. These are not
"effort-driven" tasks, but rather fixed-duration tasks. (e.g., we have 30
days to complete task X, and I'm assigning folks to work between 4 and 16
hours each on task X between 09/01/08 and 09/31/08).
This works great for tasks that are given in terms of working days ("days"),
as Project uses the default calendar and assumes 8 hrs/day. (So someone who
will devote 4 hours to a 5 day task will have a utilization of 10%).
However, it doesn't work at all for tasks given in total elapsed days, since
Project is assuming 24/7 working hours. I want to be able to specify that a
task will take place over 30 elapsed days, but will only be worked on during
normal work hours as specified in the project calendar. The Gantt Chart is
using the standard work calendar. Unfortunately, individual tasks that are
given in terms of edays can be forced to use the standard calendar (they
default to "None.")
There are two possible fixes:
1) Most desirable would be to force Project to only count work against
normal working hours, even if a task is expressed in "edays."
-OR-
2) Do a universal translation from edays to days. There are far too many
tasks to to this manually. A universal replace wont work because "30 edays"
is a very different duration than "30 days." So I'd need Project to determine
when 30 edays means 20 days and when it means 19 days, and so forth, based on
the calendar.
Thanks in advance.