Working locally through Project Server

C

crizco

We are running Project Server 2003. Not everyone is ready to publish their
plans onto EPM, so they want to work locally with a server connection (and
eventually move to EPM). Can anyone tell me what the main pro's con's are for
this? I realize you are not getting the full power of EPM, however you can
get access to some things through the server connection without publishing. I
would like to inform these people what they can expect or not expect from
doing work this way.
 
D

Dale Howard [MVP]

crizco --

The big advantage of doing this is that the projects do not appear in the
Project Center page in PWA until after the PM imports the project. This
keeps "half baked" projects from appearing in the Project Center. Make sure
that the PM builds the project team using Tools - Build Team from Enterprise
so that the system automatically maps each resource when the PM imports the
project using Tools - Enterprise Options - Import Project from Enterprise.
Hope this helps.
 
C

crizco

Yes, thanks Dale

Guess the only draw back is that once the resources are loaded through Build
Team, when you go back into the plan (remaining local through the
connection), the Enterprise Resources turn to local. You don't see it in the
Resource Sheet but you see it indicated in the Build Team screen. So if any
vacation is entered or changes made to the resources from the Enterprise
Resource Pool, they won't get the updates uless they go back to 'Build Team'
and replace the Enterprise version with the local version. Calendar updates
and other Enterprise views seem to refresh to the local file, but not the
Enterprise resources (again, unless they refresh them through the Build
Team).
 
Top