' Enterprise Standard Calendars are Needed. ' message

[Ray Chiu (a1ahardware.florida at gmail)]

SYMPTOM
=======
I wanted populate MSPS07 with enterprise projects, however, I received the
message above.

The message continues with:
Enterprise Standard Calendars are Needed.
Enterprise standard calendars are required to:
Build a team for a non enterprise project
Save a non-enterprise project into the server
Import resources to the enterprise
This may result in changes to schedule dates. Do you want to continue?

BACKGROUND INFORMATION
======================

I thought I created "Enterprise Calendars" via PWA through Server Settings
-> Enterprise Calendars (required Project Pro to be connected to EPM). Upon
closer inspection, these are branded in Project Pro as 'Base Calendar'. I
would guess these are not 'Enterprise Standard Calendars' That being said I
am not sure how 'Enterprise Standard Calendars' are created (I don't recall
these in the 2003 version, however, I could be wrong).

When saving the project to MSPS07, there is a drop down box and I can choose
from the list of 'Enterprise Calendars' that I configured earlier today.


QUESTIONS
=========

I have tried to do some research in this Newsgroup and MSDN: I hope that I
have taken due diligence before posing my questions:

Q1) What is the cause of the message and how do I remedy this? I would have
thought that selecting one of the 'Enterprise calendars' would be enough,
however there is something missing that I have not configured.

Q2) If I were to choose to continue, I don't think this would hurt because I
do not plan to use non-enterprise projects or import resources to the
enterprise. Is this assessment correct?

 

[Dale Howard [MVP]]

Ray --

The warning message you see if normally shown while importing a
non-enterprise project into the Project Server database using the Import
Project Wizard. You see this warning message because a non-enterprise
project contains a non-enterprise Standard calendar, but Project Server
requires that the project contain only enterprise calendars by default. If
you click the Yes button, the system replaces the non-enterprise Standard
calendar with an enterprise Standard calendar. This is a good
thing...provided that the two calendars match as far as working time and
nonworking time. If your Project Server administrator added nonworking time
to the enterprise Standard calendar, such as company holidays, the PM of the
non-enterprise project did not add company holidays to the non-enterprise
Standard calendar in the project, then the project schedule changes when you
import the project into Project Server (it shifts the schedule based on
company holidays). Hope this helps.





"Ray Chiu (a1ahardware.florida at gmail)"

 

[Rod Gill]

I save the schedule to Baseline10 before importing and after import review
Baseline10 using a Tracking Gantt - Baseline10 View I create in project
server to evaluate any changes made during import.

--

Rod Gill
Project MVP

NEW!! Project VBA Book, for details visit: http://www.projectvbabook.com

 

[Dale Howard [MVP]]

Rod --

What a great idea on how to use the additional Baseline fields! Thanks for
sharing.

 

[Rod Gill]

Thanks Dale. If you like that one, then my other use is:

If you manage projects by phase or iteration, Save to Baseline1 when you
have agreed the schedule for Phase/iteration 1, then to Baseline 2 for
phase/iteration 2 and so on.

Save to the normal baseline every week just before updating the schedule
(especially if you use time sheets that update Project automatically). This
lets you review progress each week and spot trends. For example if you lose
half a day on average every week, then it doesn't take rocket science to
calculate how late the project is likely to finish unless something is
changed!

This technique adds most value in time critical projects. To support this
technique, create copies of the tracking Gantt view (using View, more views)
to show current schedule against Baseline1 - 10.

--

Rod Gill
Project MVP

NEW!! Project VBA Book, for details visit: http://www.projectvbabook.com

 

[Mike]

Thanks Dale. If you like that one, then my other use is:

If you manage projects by phase or iteration, Save to Baseline1 when you
have agreed the schedule for Phase/iteration 1, then to Baseline 2 for
phase/iteration 2 and so on.

Save to the normal baseline every week just before updating the schedule
(especially if you use time sheets that update Project automatically). This
lets you review progress each week and spot trends. For example if you lose
half a day on average every week, then it doesn't take rocket science to
calculate how late the project is likely to finish unless something is
changed!

This technique adds most value in time critical projects. To support this
technique, create copies of the tracking Gantt view (using View, more views)
to show current schedule against Baseline1 - 10.

--

Rod Gill
Project MVP

NEW!! Project VBA Book, for details visit:http://www.projectvbabook.com

"Dale Howard [MVP]" <dale(dot)howard(at)msprojectexperts(dot)com> wrote in
message






- Show quoted text -

A supplement to Rod's comment: be aware that Baseline 10 duration is
affected by by the calendar options setting so moving from default
desktop setting of 8 hour days to a new enterprise standard of 7.5
days will change baseline 10 dates. So add 2 further steps and paste
baseline 10 duration to a local text field. In turn this can be
copied and pasted into the new enterprise project b10 duration to
reset b10 dates to original state.

regards

Mike