Re: Calendars tasks and resources

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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: Multiple shifts and resource usage
    ... "Trevor Rabey" wrote: ... used the Standard Calendar to start the project at 08:00 on Day 1. ... You need a day shift resource and an afternoon shift resource and each ...
    (microsoft.public.project)
  • Re: 24 Hour Schedule
    ... A good example of one of our multiple day tasks is cleaning a column. ... usually assign a task to a specific team that works 1 and only 1 shift. ... it'll run for 5 working days with the resource assigned doing 8 hours ... To change the calendar assigned to a specific task, ...
    (microsoft.public.project)
  • Re: Actual Work moving to future
    ... You really can use a typical resource as ... > the resource that works them is assigned at the resource calendar assumes ... > calendars that conform to each shift. ... > will show the correct total duration and elapsed time for the Project, ...
    (microsoft.public.project)
  • Re: Actual Work moving to future
    ... You really can use a typical resource as ... > the resource that works them is assigned at the resource calendar assumes ... > calendars that conform to each shift. ... > will show the correct total duration and elapsed time for the Project, ...
    (microsoft.public.project)
  • Re: Calendars tasks and resources
    ... available 24 hours a day) and let the task calendar dictate the working times. ... shift whilst everywhere else they work 2 10 hour shifts. ... not directly related other than through the resources. ... durations and related work values all lined up properly. ...
    (microsoft.public.project)