Resource booking business processes track personnel assignments at the company and shell levels. These BPs go through an assignment workflow to fill the personnel openings for a project. The process draws personnel only from the allocated roles on a project’s or shell’s allocation sheet. Personnel are “hard” or “soft” booked until the assignment workflow reaches its end step, at which time the personnel are then considered either hard-booked or rejected. The booking BP allows users to manually balance personnel resources over the duration of the project.
Note: The Resource Booking BP is not available in generic shells. However, users can book resources via manual entry on the Booking Summary Sheet.
Only one resource booking BP is allowed at the company, project, or shell level, but that BP can be modified if necessary. The resources and their costs from this business process are rolled up to both the Company and Project/Shell Cost Sheets. Resource bookings also integrate with the Schedule Manager in assigning resources to project schedule activities.
If necessary, you can design a Resource Booking BP to manage overbooking, which happens when resources are booked for more hours than a role has been allocated.
Resource booking BPs typically enter hours and cost information onto company and project cost and booking sheets as follows:
|
The Resource Booking BP enters this information: |
Onto this sheet: |
|
The name and hours of hard-booked personnel when the BP reaches terminal status. By default, costs are calculated based on the rate obtained from the Role Attribute form. Users can override the rate directly from the booking sheet. |
Project Booking Sheet |
|
Same |
Company Booking Sheet |
|
Costs from the Project Booking Sheet. These costs will be added and reported against undistributed costs. Once a WBS code is assigned, costs are reported based on the BP status (e.g., “Pending” for soft bookings; “Approved” for hard bookings). |
Project Cost Sheet |
|
Costs from the Project Booking Sheet. These costs will be added and reported against the project cost code. Costs are reported based on the BP status (e.g., “Pending” for soft bookings; “Approved” for hard bookings). |
Company Cost Sheet |
For Resource business processes to work effectively in Primavera Unifier, you will need to create the following components in Primavera uDesigner:
| • | Upper form |
| • | Workflow |
| • | Log |
| • | Link to a reference process (depending on the BP setup) |
The following table outlines the design steps necessary to create a these business processes.
|
This structure will include the data elements to be used on the forms. (If the data structure has not already been created, see the instructions beginning with Creating a Data Structure.) |
||||||||||||
|
This step initializes the design process for the BP. See Starting a New Design. |
||||||||||||
|
See the instructions beginning with Starting an Upper Form. Mandatory fields for the upper form are:
|
||||||||||||
|
See the instructions beginning with Starting a Detail Form. Mandatory fields for the detail form are:
|
||||||||||||
|
See the instructions beginning with Starting a Workflow. |
||||||||||||
|
See Designing a Log. |
Oracle Corporation
Primavera Unifier 9.10 • Copyright © 1998, 2012, Oracle and/or its affiliates. All rights reserved.