Phantom Users-Replacing a Phantom User with a Named Resource

When a project request is submitted, the various roles required for the project are converted to Phantom Users. This gives the Resource Pool Managers the ability to determine which named resource makes the most sense from both a capacity and skill perspective to name on the project. This article will explain the process in which the Resource Managers are notified and the steps to replace the Phantom User.

How to Use the Resource Management Module in BCWorks LinkedIn Video

• Summary:

  • There was a need to have a report detailing projects that have Phantom Users attached as associated resources. This report will be used for communication to those Resource and Project Managers associated with the project, in order to replace the Phantom User with a named resource.

• Result

  • A report was created to be emailed out to both the project’s Resource Manager, the project’s BCWorks Manager, and the PMO Office email. This report was created by the BCWorks technical resource (Rober Herbstzuber).

    • Cadence: First Monday of every month.

• Procedure:

  • The Resource Manager and BCWorks Managers review the emailed report, and the Phantom User associated with their project. A link is contained within the email that goes directly to their BCWorks project with the associated Phantom User.

 

• The Resource/BCWorks Manager clicks on the link of the associated Phantom User, and is automatically brought to the BCWorks project. 

• Once in the project, the Resource/BCWorks Manager must scroll down to the “Resources” section of the project, and click on it to see all resources associated with the project (which will include the Phantom User).

• The BCWorks Manager needs to contact the Resource Manager to figure out who should be assigned to the project. Once that person has been identified, the BCWorks Manager must add the named Resource

 

• The BCWorks Manager must go to “Actions” and “Add Resource” to add the named Resource.” The Phantom User is identified, and will be replaced by adding a named Resource and removing the Phantom User. 

 

 

• Once the named resource is added, the Phantom User must be deleted.

 

 

• The phantom is now removed, leaving the named resource