Local vs Enterprise Calendar

[Randy]

Is there a down side to allowing local calendars? We are in the process of
having our PMs migrate their projects from 2002 to 2003. Apparently on 2002
we allowed local calendars and on 2003 we are not. Well, the masses are up
in arms over this so I'm trying to figure out the pros and cons. My
assumption is that even if they use local calendars that resource
availibility will still be pulled from the enterprise standard calendar.
Hopefully someone can clarify this for me.

Thanks!

Randy

 

[Dale Howard [MVP]]

Randy --

Allowing local calendars gives your project managers to set their own custom
calendars to their projects as the Project Calendar and Nonworking Time
Calendar, and to tasks as Task Calendars. I would simply ask you two
questions:

1. What types of custom calendars are your PM's creating in their projects?
2. Why can't your Project Server administrator can't create these calendars
for your PM's in the Enterprise Global?

If you determine the types of calendars needed in question #1 and then the
Project Server administrator creates them in #2, everybody should be happy.
Also, when you open the Enterprise Resource Pool, you must set the Base
Calendar for each resource using one of the enterprise calendars found in
the Enterprise Global. Hope this helps.

 

[Randy]

Dale,

1) Our PMs have varying needs such as a calendars with no holidays, 7 day
work week calendars, etc..
2) I am the server admin and could create those calendars but our concern is
that the people may not pay attention and choose the wrong calendar which
would mess up their plans. We are trying to keep things simple.

If they are allowed to use local calendars is their project plan, wouldn't
that open up the possibility of them changing working times, etc..., from our
standards to whatever they want thus throwing everything off? Also, how
would resource scheduling be reflected across the enterprise?

Randy

 

[Dale Howard [MVP]]

Randy --

If you want to keep things as simple as possible, and don't want the use of
local base calendars to foul up project scheduling, I would suggest the
following path:

1. Determine every custom calendar needed by your PM's
2. Create each of these calendars in the Enterprise Global file
3. Make this a training and performance issue and require your PM's to set
the Project Calendar and Nonworking Time Calendar in each project

In step #3, you have to teach your PM's a process they must use to define a
new project, which should include the setting of these two calendars. Then
your project managers must demonstrate their compliance with this process by
actually following this process.

When we work with clients on Project Server implementations, we teach their
project managers a 4-step process they should use to define a new project,
and one of the steps involves setting the Project and Nonworking Time
calendars in their project. Hope this helps.