Re: Calendars tasks and resources

The might well be people working around the clock during an outage but does an individual person - Catfish Hunter, for example - work around the clock without any time off for sleep or meals? That's the problem I have with the 24 hour clock in most circumstances. Tasks and resources will be broken down to the level of "Catfish and his assistant Catminnow are assigned to replace the superheater tubing on Boiler Number 3 starting Monday." No one else is assigned to do that specific job. The 24 hour calendar says that once they start that job, the two Cats aren't relieved by anyone else for any reason and they don't go home until the job is done. IMHO, the calendar does not describe when people generically are available - it describes when one single individual named worker is available. To get 24/7 coverage requires more than one person, hence it also requires more than 1 calendar, a calendar for each shift that collectively results in a 24 hour coverage.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs



"Catfish Hunter" <CatfishHunter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:24EE6208-4AC0-414E-83F9-1CD4692726C4@xxxxxxxxxxxxxxxx
All the schedules I work on are outage. On outages people work around the
clock. It's much easier to have resources set to 24 hours a day. If you set
up a resource for "boiler makers working 6-10's, boiler makers working
6-12's........." you can't see how many boiler makers you need without taking
the data to Excel. That's why I let the task calendar set the working time.


"Steve House [Project MVP]" wrote:

The point is that the 24 hour calendar implies that once it starts, work on
a task proceeds without interuption until it's complete. Since a task is
the work performed by a single person or by a team, that means there is no
non-working time for the people assigned between when the task begins and
when it ends. If the task takes 5 days the resource doesn't eat or sleep or
go to the bathroom for the full 5 days work is going on. Machines work like
that but people don't and 99.999% of projects need to be scheduled around
the working times of the individual people doing the work, the times when
they are physically present so they can do the job at hand. You might think
shift work where there's a day-shift resource and a swing-shift resource and
a grave-shift resource with all 3 assigned and working on the task so it
proceeds around the clock means the 24 hour calendar applies but it
doesn't - you really should see the composite schedule that results from 3
separate 8-hour working calendars back-to-back, and is really quite
different from what you get with the 24 calendar.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs



"Catfish Hunter" <CatfishHunter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:488EF67A-EDFD-4650-A6D8-E0EEDE82BF9D@xxxxxxxxxxxxxxxx
> The tasl calendar will take over and allow Joe to eat a 2 bologana
> sandwichs
> at lunch and twinkees for his break twice a day. Depending on how the
> calendar is set up.
>
> "Steve House [Project MVP]" wrote:
>
>> So when you asdsign Joe to do a 5 day task, once it starts you don't
>> allow
>> him any time off until he's done 5 days later, not even a single lunch
>> break?
>> -- >> Steve House [MVP]
>> MS Project Trainer & Consultant
>> Visit http://www.mvps.org/project/faqs.htm for the FAQs
>>
>>
>>
>> "Catfish Hunter" <CatfishHunter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message
>> news:08192BF2-6AE9-46B2-A8AD-9AF9768E1249@xxxxxxxxxxxxxxxx
>> > My preferance is to set all resource calendars to 24 hours (make
>> > resources
>> > available 24 hours a day) and let the task calendar dictate the >> > working
>> > times.
>> >
>> > "DavidC" wrote:
>> >
>> >> Hi,
>> >> Thought this might be a salutory lesson for some.
>> >>
>> >> My project has a number of work fronts, of which one area works one >> >> 10
>> >> hour
>> >> shift whilst everywhere else they work 2 10 hour shifts. By not
>> >> allocating
>> >> the 10 hour shift calendar to those tasks being carried out by the
>> >> resoruces
>> >> working 1 10 hour shift I kept getting changes to durations being >> >> made
>> >> automatically after changing the duration on one task, even those
>> >> tasks
>> >> were
>> >> not directly related other than through the resources. Problem was
>> >> though
>> >> that on those tasks they used a resource which was used for the 2 >> >> 10
>> >> hour
>> >> shifts (crane) and that was driving the work values based on the
>> >> duration
>> >> which was initially set to the 2 10 hour shift calendar.
>> >>
>> >> Setting the calendar on the task that related to the area, the >> >> summary
>> >> days,
>> >> durations and related work values all lined up properly.
>> >>
>> >> So simple a solution yet I overlooked not specifically setting the
>> >> task
>> >> calendar and leaving it to default to the project calendar.
>> >>
>> >> Follow the basics and do not shortcut.
>> >>
>> >> For what it is worth,
>> >>
>> >> regards
>> >>
>> >> DavidC
>>
>>



.

Relevant Pages

  • Re: Calendars for multi-resource tasks
    ... the resource's calendar governs the task as soon as the resource is ... >> schedule needs to be something OTHER than either the Project Calendar ... allocating the appropriate calendar to each task i.e. ...
    (microsoft.public.project)
  • Re: switch between calendars
    ... record when a resource actually starts only when the pick the task ... task with 5 days duration starting Monday and ending Friday at 5:00 pm ... the task calendar to the 10hr per day calendar the task duration will ... constrained all tasks with a SNET constraint, ...
    (microsoft.public.project)
  • Re: Calendars for multi-resource tasks
    ... calendars" are and how they relate to resource calendars. ... scratch or copying an existing one, you are creating a base calendar. ... You can create two base calendars in Change Working Time, ...
    (microsoft.public.project)
  • Re: Can Resources Work More Than 24 hours Per Day? : Aside
    ... If I say a task begins Monday and ends Friday and my calendar is MS Project's 24 hour calendar, that means that once work starts on that task on Moday morning, it is not interrupted until the task is complete. ... Even we're thinking about a machine as the resource, most machines only function when their human operators are there to control them, so the same logic applies - the 24 hour calendar implies that the machine's operator will be expected to be on duty 24/7 for the entire duration. ... If Joe is polishing the fids, work will only take place on the polishing task for the portion of the day that is Joe's work shift - the fact that there are 16 more hours in the calendar day when someone else could be polishing fids is irrelevant. ... So if you assigned 3 custodians to the task and it had an 8 hours duration, you would assign them at 300% and the result would be their performing 24 man-hours of work over the course of an 8 hour task duration. ...
    (microsoft.public.project)
  • Re: Actual Work moving to future
    ... Remember, for MSP % Complete refers only to duration, not work. ... resource) and I update the progress to show 50% done, ... shows a day shift, 8 hour work day. ... >> Project calendar so tasks prior to having their resource assigned will ...
    (microsoft.public.project)