A
AndrewO
Hello,
Here is my situation: I am using Project Pro 2007. I am working on a
project for an IT company which allows various amounts of downtime on
Saturdays. Some Saturdays they allow 6 hours, some Saturdays 10, some
Saturdays none. I have created a calendar with the only working days
as Saturdays with a 10 hour work day, and then created exceptions for
each 6 hour Saturday, and marked the prohibited Saturdays as non-
working time.
I then created a resource, meant to be used as a generic resource,
whose base calendar is this special "downtime windows" calendar.
This almost works perfectly... If I have a task that is expected to
take a full 6 hour downtime window, I assign it to the "downtime
worker" resource, and give it a 6h duration and project neatly moves
the task to the next available 6 hour Saturday.
The problem is that if I have a job which is expected to take between
6 and 10 hours, Project will automatically schedule the first 6 hours
in the next available 6 hour window, then the remaining hours in the
next window. But we can't leave things broken during the week,
obviously. So if the schedule goes 6-6-10, I expect a 9 hour task to
be done on the third Saturday, but instead Project puts 6 hours in the
first one and the 3 hours remaining go in the next 6 hour Saturday.
I suppose I could make another calendar, so there would be one for the
6hr, and one for the 10h windows, and a resource that uses each and
then assign each task to the right resource, but that seems like more
pain than I should have to go through. I've played with the split
options, but those only seem to deal with splits induced by leveling.
Short version of the question: is there any way to ensure that a task
starts only when there is enough time left in the day to complete the
task the same day it starts?
Here is my situation: I am using Project Pro 2007. I am working on a
project for an IT company which allows various amounts of downtime on
Saturdays. Some Saturdays they allow 6 hours, some Saturdays 10, some
Saturdays none. I have created a calendar with the only working days
as Saturdays with a 10 hour work day, and then created exceptions for
each 6 hour Saturday, and marked the prohibited Saturdays as non-
working time.
I then created a resource, meant to be used as a generic resource,
whose base calendar is this special "downtime windows" calendar.
This almost works perfectly... If I have a task that is expected to
take a full 6 hour downtime window, I assign it to the "downtime
worker" resource, and give it a 6h duration and project neatly moves
the task to the next available 6 hour Saturday.
The problem is that if I have a job which is expected to take between
6 and 10 hours, Project will automatically schedule the first 6 hours
in the next available 6 hour window, then the remaining hours in the
next window. But we can't leave things broken during the week,
obviously. So if the schedule goes 6-6-10, I expect a 9 hour task to
be done on the third Saturday, but instead Project puts 6 hours in the
first one and the 3 hours remaining go in the next 6 hour Saturday.
I suppose I could make another calendar, so there would be one for the
6hr, and one for the 10h windows, and a resource that uses each and
then assign each task to the right resource, but that seems like more
pain than I should have to go through. I've played with the split
options, but those only seem to deal with splits induced by leveling.
Short version of the question: is there any way to ensure that a task
starts only when there is enough time left in the day to complete the
task the same day it starts?