Whether to use 'Oracle Project Resource Management'
Gust post by
Rajan Gupta, Senior Consultant, Infosys
Oracle Project Resource Management (PJRM) is a self-service application in Oracle Enterprise applications and provides a solution to effectively manage resource allocation on projects in project centric organizations. PJRM has been a buzz word in PPM when Oracle started rolling out PPM solutions to its customers. The effective goal of implementing PJRM application is to find the right people for the right projects at the right time which is ultimately achieved by streamlining the demand and supply of resources in an organization. Project Resource Management considers only labor resources and assignment of those resources at the Project level only (not at task level) and is a not time based application.
Key Features include-
- Central Resource Repository integrated with HRMS.
HR resources that are maintained in resource pool of PJRM are only those resources which are eligible based on certain validations defined in Job setup, Org Hierarchy etc. This helps in segregating the resources in an organization based on staffing and scheduling needs.
- Project Staffing and Scheduling.
PJRM allows Project Managers (Demand side) to create resource requirements based on Project needs. Staffing Manager (Supply side) can nominate candidate as well as assign candidate by matching resources based on resource availability, job levels and skills set required.
- Utilization reporting. Utilization reports which include actual and forecast utilization can be built based on resources allocation and capacity. Those can be generated at the organization level as well as resource manager level.
Key Considerations while implementing Project Resource Management
- PJR should be used in very process centric organizations. Value out of the application is made out only when processes are followed and data is properly maintained. Resource search of candidates relies on 3 parameters- Resource availability, Skills Set and Job levels.
- Resource availability is automatically calculated based on calendar setup and resource allocation. However Project Manager should very diligently define hours to be required while creating a resource requirement on the project. Project Resource Management consists of 2 types of resource allocation on projects that are Delivery Assignment and Administrative assignment. Delivery assignments are scheduled allocations on projects however administrative assignment are non-billable and non-work assignment such as Vacation, Sick leave. Maintaining administrative assignments creates an overhead for the stakeholders of the application and stake holders should decide the granularity of information that is useful to them.
- Job levels define the seniority of users in an organization and skills are pre-defined for each role. Skills set can be added while creating a resource requirement as well as searching resources. Skills set should be an ongoing process and can be accrued quarterly or bi-annually.
- Segregation of resources eligible for Staffing - Project Resource Management maintains central resource pool that maintains data about resources availability, skill set, resume, address, job, email, work information, location etc. All the resources in an HR organization need not to be defined in resource pool. This refines the resource search and improve performance of the application.
Selection of resources based on jobs and organization hierarchy has to be made to refine the structure.
- Integration between Project Resource Management and Project Management - Out of box functionality in Projects module allows integration between Project resource management and Project Management. Integration can be achieved either by Bottom-up approach as well as Top-down approach. In a top-down approach, resources are allocated on Projects by creating resource assignments on the projects and then assigning those resources at tasks in Project Management. However in a bottom-up approach team roles are created based on task assignments and then are rolled up to a project level role. Though the bottom up approach has been provided, but it is highly recommended not to use bottom up approach. It can be only be used if resource availability and capacity data does not matter to project stakeholders as it create the work schedule based on allocation method (viz. spread curve) and therefore spoils the works schedule while creating a team role based on task assignment and does not exactly reflects the project or task role required hours. Creating a role from top-down approach is a much cleaner way of resource assignments and provides more flexibility of creating a resource request by assigning resource for either percentage of capacity of calendar or by defining different work pattern for a certain period of time.
- Integration between Oracle Time and Labor and Project Resource Management - Objectives of the Project resource Management and Oracle time and labor totally different as one captures resource planning and other calculates actual. There is no out of box functionality available which integrates these two modules.
- Non project centric and small organization - Project Resource Management is not that beneficial for small organizations where there are few projects, non skills based organizations, not much movement of resources across projects or where there are few resources. It is generally used for mid-sized and large-sized organizations.