Working across multiple servers?

[al biglan]

I'm in a situation where it would be advantageous to set up three separate
Project Servers each holding a set of schedules for a single "Program" (three
different locations with slow network connections between each)
Is it possible (don't think it is) to link/integrate the schedules across
the three servers? For example, create a Master Project in each of the three
sites, then for the site where I reside in, create another Master Project for
the overall program that pulls in the other schedules. I'm not _so_
concerned about sharing resources, but this would be nice.

Is something like this possible? (Don't have to use Master Projects...)

Thanks
-al

 

[Dale Howard [MVP]]

Al --

First of all, if you set up three Project Server instances, I do not believe
you can integrate the date from all three instances, such as creating a
master project with plans from each instance.

Second, are you absolutely certain you need three Project Server instances
to accomplish your purpose? An alternate approach for tracking three
seprate programs would be to use a single Project Server instance, and
create a enterprise Project outline code field called Program that lists
each program. You would need to create this enterprise Project outline code
field in the Enterprise Global and make it a Required field. When you do
so, every PM would then have to select a program from the Program list
before he/she would be allowed to save the project in the Project Server
database.

In addition, you could create one or most custom Project Center views that
include the Program outline code field, with grouping applied on that field.
This will show the projects in the database grouped by program, which would
be very useful. In addition, you could also create one or more custom
Portfolio Analyzer views that use the Program outline code field in the
Columns or Filter Fields drop areas. This would break down the information
for each program.

Just some ideas. Hope this helps.

 

[Gary L. Chefetz \(MVP\)]

Al

It sounds to me that you should consider deploying one instance of Project
Server in the location with the most advantageous Internet connection and
use Terminal Services to serve your remote offices.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-