Changing Local Resources to Project Server Account Resources

[Al_at_FM]

Due to the number of local resources working on several projects, for which
we are tracking the actual hours worked, we have decided to set up Project
Server accounts for each resources and have the project managers enter their
actual time using the Adjust Actuals facility in PWA. The problem we
anticipate with this approach is lost visibility of the historical actuals up
to the point of the change.

In addition to the ease of entering the actuals (using adjust actuals), we
expect to do better analysis using Resource Assignment views, Portfolio
Analyzer, etc.

Does anyone have any suggestions on how best to associate the "historical
actuals" to the new project server account resources who are the same persons
as the former local resources? Thanks in advance for your help.

 

[Dale Howard [MVP]]

A1_at_FM --

Here's one way to address this issue:

1. Add the new enterprise resources to the team in each project.
2. Select a task to which a local resource is assigned.
3. Click Window - Split to apply the Task Entry view.
4. In the Task Form (lower pane), click the name of the local resource in
the Resource Name column, and from the pick list select the new enterprise
resource.
5. Click the OK button.
6. Repeat steps 4-5 for every task to which a local resource is assigned.

Following this process will transfer the historical actuals from the local
resource to the new enterprise resource. I realize this may be a lot of
work if you have local resources assigned to many tasks in each project, but
it will satisfy your reporting requirements in spite of the extra work.
Hope this helps.

 

[Al_at_FM]

WOW! Thanks for your prompt response. We will try this and let you know how
it works for us. One follow up question: For your solution, does it matter
if the enterprise resource name is different from the local resource name.
We currently have a suffix ("- C") on the local resources and was thinking of
using "-- C" for the enterprise resources. Advise.

Again, thank you so very much. Also note that we just purchased the book
"Administering am Enterprise PMO" and are looking forward to reading it.

 

[Dale Howard [MVP]]

A1 --

I DO NOT recommend using the dash character in the names of enterprise
resources. Special characters are known to cause problems with building the
OLAP cube, so avoid the dash character in resource names. Otherwise, give
the local resources a name that is easy to identify and try the process.
Let us know how it turns out.