How to set a resource calander working day to 24hrs

[John Sitka]

....not like 12:00AM to 11:59PM cause then it throws .98 hours in Resource
view.

I would like true whole hours.

 

[Dale Howard [MVP]]

John --

The 24 hours working calendar that ships with Microsoft Project shows the
time as 12:00 AM to 12:00 AM. Can't you use this calendar as the Base
Calendar for the resource?

 

[John Sitka]

Yeah that's the stuff


Thanks.

John --

The 24 hours working calendar that ships with Microsoft Project shows the
time as 12:00 AM to 12:00 AM. Can't you use this calendar as the Base
Calendar for the resource?

 

[John Sitka]

Shoot it still isn't clear to me.

Master Project
Resource Pool Project
Project A
Project B

Master Project Tools>Change Working Time it allows me to edit the various
calendars for the project.
Where do I set my Master Project calendar?


Real world is..... Master Project Mon->Fri = 24 hours, Sat = 10 hours, Sun
closed.
I asume the resource pool would have the same set up with each resource
having it's own calendar.
Each Project is worked on continuously and simultaneously during the above
mentioned working hours of the enterprise
so I imagine that they to should have project calendars and working times
set as the Master.

 

[JulieS]

Hi John,

Set the resource's base calendar to the 24 hour calendar
that already exists in MS Project. (It's an additional
base calendar.) The working time is set to 12:00 AM to
12:00 AM.

Hope this helps.
Julie

 

[Mike Glen]

Hi John,

Also, you might like to have a look at my series of Microsoft Project
lessons in the TechTrax ezine, particularly Lesson 12 - Working Patterns, at
this site: http://tinyurl.com/2xbhc (Perhaps you'd care to rate it before
leaving the site, Thanks.)

Hope this helps - please let us know how you get on

Mike Glen
MS Project MVP

 

[Steve House]

Are you really really sure you want to do this anyway? The 24-hour calendar
means that when a resource starts on a task he will work 24/7 without a
break, without a nap, without a meal until the task is completed. Since
most resources are either people or teams who work together as a unit it
doesn't seem very likely that this is an accurate model of their real work
pattern. It means that your resource might start on a task Monday, for
instance, and work for 2, 3, 4 days without a break? Do you really expect
them to do that?

--
Steve House [MVP]
MS Project Trainer/Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs

 

[John Sitka]

This is a manufacturing environment. Very large and expensive machines that
run 24/7. If they aren't doing something it costs money.
This is the three shift situation our company faces during busy times when
it comes to some of our resources.
One of my posts inquires about the relationship between a project calendar
and a resource calandar. The doors of the plants
may generally be considered open for two shifts most of the time but some
premium resources are on the 24 hour system.
For instance I got fooled by the start date of a project when it only
allowed me to use a 24 hour resource for part of the first day.
This was because the project calendar followed the two shift model and not
the three. Thus even on the first task there was a failure
in the work for that day.
But your point brings up the incredible challange faced in modelling the
real world within this application. Resource boundries are
very difficult to define. Only the responsible people for this machine can
truely define their productivity or booking. This is confouned further
when there may be multiple responsible persons competeing for the same
resource. From a status and decision making point of view it makes sense to
use the responsible
person as the resource. But the physical machine can only accomplish one
task at a time so it is the true constraint. Assignments
whether scheduled or not can change hourly when the experienced manager
realise that a slight window of opportunity such as a tool head change
and set up may be the best time to attack a project that could best be
described as a "party crasher". These projects materialise and dematerialize
constantly throughout a week. Normally just before the project's fixed and
final delivery date (miss that date and severe penalties ensue) or within
the year once they have been delivered and put in production then need
"tweaking" after a break in period. These party crasher projects therefore
are of
the utmost urgency. I believe this type of scheduling and project
management generally falls under the expertise of Manufacturing Engineers.

 

[Jan De Messemaeker]

Hi John,

When you know project it isn't that difficult.
It's not your project calendar that fooled you on the first day, it's tools,
options, calendar, default start time.
And the rules are simple: taks without resources nor task calendar are
scheduled as per the project calendar (but there is this matter of the
default start as long as they aren't linke or anything)
Assignments are scheduled as per the resource calendar but taking into
account the task calendar.

HTH

 

[John Sitka]

I guess I should start off every question with a context of

ResourcePool
Master Project
insert Project1
insert Project2
........
insert Project<n>


I have these set properly now. And thanks for the simple rule

And the rules are simple: taks without resources nor task calendar are
scheduled as per the project calendar (but there is this matter of the
default start as long as they aren't linke or anything)


Assignments are scheduled as per the resource calendar but taking into
account the task calendar.

That confused me a bit so I looked it up

If you have a task calendar applied as well as resources assigned, the task
is scheduled
during the working times that the task calendar AND resource calendars have
in common.