Sharing Project Server between 2 business units

[Texas Tonie]

My company has 2 business units that want to implement project server.

Each business will have mostly non-overlapping project-level enterprise
custom field definitions.

How should we implement this - have 2 instances of Project server on the
same server, or have one instance and limit the number of custom fields with
default entries where the field applies to only one of the 2 BU's.

Has someone faced this dilemma before - and how was it resolved?

A curious Texas Tonie.

 

[Ben Howard]

Hi Texas Tonie,
It basically comes down to the single query - "if you'll never require
consolidated reporting or a consolidated resource pool, then you can easily
use two instances". I've done this and as long as the customer is happy with
the above statement and the duality of backing up another 4 databases, then
it's a nice way to go. I've other customers who have decided to stick with a
single instance for both BUs.

 

[Dale Howard [MVP]]

Texas Tonie --

If you have resources who need to work in projects in both business units,
then you will have to use a single Project Server instance. Otherwise, if
each business unit will ONLY use its own resources, and not share them with
the other business unit, then you can set up and use two separate Project
Server instances. Hope this helps.