What advantage are Enterprise Resource Pools

[John Sitka]

Beyond all the WSS/Web based stuff?

When it comes down to scheduling what does the use of Enterprise Resource
Pools
enhance.

 

[RickD]

Eac resource is only defined once within an enterprise, therefore it provides the ability to manage each reource and its assignments and utilization.

 

[John Sitka]

Does not the use of a resource pool (desktop) allow
"the ability to manage each each reource and its assignments and
utilization" ?

Eac resource is only defined once within an enterprise, therefore it

provides the ability to manage each reource and its assignments and
utilization.

 

[RickD]

The desktop resource pool is the pool of resources assigned to one specific project. As far as the PM is concerned, even with the Server edition, that is still the focus

Each of those resources in that plan may also be assigned to other projects that are starting, finishing or continuing. By having the ability to examine where all or specific resources are assigned, a resource manager can determine whether there are resource contention issues

The PM who has a resource in their local resource pool (in their plan) would certainly be concerned if that resource is still assigned to another project. The local view doesn't provide that perspective; the enterprise view does.

 

[Dale Howard [MVP]]

John --

I personally believe there are a couple of advantages of using Project
Server's Enterprise Resource Pool over using a shared resource pool:

1. The shared resource pool is an antiquated technology that is prone to
corruption, which means when the shared resource pool becomes corrupted you
will no longer be able to open it

2. The Enterprise Resource Pool is a current technology that is very stable
and is resistant to corruption

3. The shared resource pool uses a "big footprint" with each project since
it shares EVERY resource in the pool with every sharer project

4. The Enterprise Resource Pool uses a "small footprint" with each
enterprise project since it only shares those resources that are members of
the project team selected by the manager of the project

5. Project managers can add or change any resource in the shared resource
pool, which defies most organization's resource management methodologies for
centralized resource management

6. With the Enterprise Resource Pool, only the Enterprise Resource Pool
administrator(s) can add, modify, or inactivate resources

Just a couple of thoughts. Hope these help.

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
Denver, Colorado
http://www.msprojectexperts.com
"We wrote the book on Project Server"

 

[John Sitka]

Thanks Dale.
We need a finite scheduling solution that can tell us when and
how to set the outsourcing machine in motion when we land a large
package of work. Hundred Projects with a hundred tasks all from the
same resource pool. We don't know if Project could handle it but we also
don't want to
go shopping for something until we know what project can do.
Thus we need to try to get Project to work. All I see so far is that wel
will need to feed it like
crazy. I also can't see how the "what if" scenerio performance could be any
good in the file
based version. I also like
the distributed (web) model for task status updates. I can't see how any
schedule
would work without up to the minute revisions to status but maybe I just
don't get it.
The ERP package folks are starting to sniff around and then they talk about
barcoded
labor collection at work centers and rollouts like that. My thought is "yeah
right"; an electronic
task list per value stream manager submitted for approval to the project
manager
is a much better model for us. Two folks I talked to didn't know what I was
getting at.