Prev: Event ID 7882
Next: Have to restart World Wide Web Publishing Service
From: Paul Billings on 16 Nov 2009 12:59
On Nov 14, 10:16 pm, Jim Aksel <JimAk...(a)discussions.microsoft.com>
wrote:

> That being said, I would have a specific RainDelay calendar that is a copy
> of the real work calendar.  I would then follow Gerrard's plan and set days
> to Non-Working in the Weather Calendar.  I would assign the Weather calendar
> to those tasks that would stop work waiting for the weather.  

One thing has bothered me about this concept of using calendars--
really it's about "scheduling" delays. By the vary nature of
"scheduling", it's useful only when discussing future work. However,
I'd be hard pressed to schedule a rain delay on July 17 of next year!
Assuming one is tracking with sufficient detail, any delay due to
weather will show up as a gap when actual hours are recorded. If one
is not tracking at such a level, then they've effectively stated that
they are not interested is such details. Why is a weather delay any
different than capturing (or not) whether your roofer didn't work
because his truck broke down?

Paul
First  |  Prev  | 
Pages: 1 2
Prev: Event ID 7882
Next: Have to restart World Wide Web Publishing Service