Ignoring Resource Calenders While Scheduling

[eswar]

hi,
i have saved some test projects on to my test server and there are many
common resources in those projects. wht i noticed is that the scheduling gets
adjusted automatically based on the resource availability. so i removed this
by checking "Scheduling ignores resource calanders", under Advance tab in
Task Information Dialouge box. wht i want to know is:

- are there any disadvantages of using this kind of scheduling?

regards
Eswar

 

[Jan De Messemaeker]

Hi,

First, the option you put on ONLY works for tasks that also have a task
calendar, if not it has no action.

And as for the consequences: Project will then happily schedule a resource
while he/she is on holiday or in general during nonworking time.
That doesn't sound like realistic to me.

It has no effect whatsoeber on resource overallocation, to solve that you
need resource leveling.
HTH

 

[Gérard Ducouret]

Hello Eswar,
If you are able to check the "Scheduling ignores resource calandars" option
on every task, that means that you attached a specific calendar to each
task. It's a very strange way to schedule tasks, unless you have a good
reason to do that ?

Gérard Ducouret

 

[eswar]

hi,
thanks for the reply. so, from this can i infer that in a system where
resources are matrixed, this can kind of setup can be useful. matrixed
systems i mean; the resources are assaigned to more than one project and
sometimes need to work overtime. a system where in duration is more important
than the work. hope i am clear at expressing my doubt!! can u pl clarify my
doubt. i am concerned because this is an real time issue.

regards
Eswar

 

[Jan De Messemaeker]

Hi,

If you do not activate Resource leveling explicitly, scheduling does not at
all react to resource load/overload.
HTH

 

[eswar]

hi gerard,
there is one reason. say, there are some tasks that are more duration
oriented. they can't afford to have delays. then in that case resources have
to finish the job(though they are going to work overtime) in time. and they
may not be paid for that overtime.
in such setups, can we go for this setting?

regards
Eswar

 

[Gérard Ducouret]

Hi Eswar,
I'm afraid this kind of setup will be a little dangerous: if somebody
scheduled some vacation days in the resource calendar, you will not be
warned of the delay issue.

 

[eswar]

hi gerard,
thanks for that. i think this reason is good enough for me to stop
implementing such setup

regards
eswar

Hi Eswar,
I'm afraid this kind of setup will be a little dangerous: if somebody
scheduled some vacation days in the resource calendar, you will not be
warned of the delay issue.
--
Gérard Ducouret [Project MVP]

hi gerard,
there is one reason. say, there are some tasks that are more duration
oriented. they can't afford to have delays. then in that case resources have
to finish the job(though they are going to work overtime) in time. and they
may not be paid for that overtime.
in such setups, can we go for this setting?

regards
Eswar

 

[Steve House [Project MVP]]

The biggest disadvantage is that tasks are driven forward by resources doing
work. Work only takes place when the bodies that do it are physically
present. Resource calendars define when bodies are present. No one is on
the property during the non-working times in the calendar and so tasks
cannot take place during those times. Ergo, the only way to insure that the
work is only scheduled at such times that it is physically possible to do it
is to have the resource calendars drive the schedule. Schedules where tasks
ignore them will prove unworkable. So the biggest disadvantage to doing it
the way you are is that the resulting schedule will have absolutely no
correspondence to what is actually going to happen when you attempt to do
the project.