Requested allocations

As a resource requester, you can create allocations for your resource plan using the Requested Allocations related list.

Before you begin

Role required: resource_user, admin

About this task

Resource users can create requested allocations for plans in Planning or Rejected state. Resource Managers can create requested allocations for plans in Requested state.

Resource requester can modify the requested allocations to specify the breakup of resource requirements for monthly or weekly Allocations types. For example, a resource requester has requested 100 hours of a resource from Jan to Feb, but wants 20 hours in Jan and 80 hours in Feb. The requester is allowed to specify these details in requested allocations.

Procedure

  1. Navigate to Resource > Resource Plans > Requested.
  2. Open a resource plan.
  3. In the Requested Allocations related list, click New.
  4. Fill in the fields as appropriate.
    Table 1. Requested Allocation form
    Field Description
    Start date Start date for the requested allocation record.
    End date End date for the requested allocation record.
    FTE The number of units for the full-time equivalent selection for the requested allocation record. See Resource plans for an explanation of FTEs.
    Note: Capacity is not derived from FTE, but from schedules. Both FTE and schedules must be in synchronization with each other.
    Resource plan The resource plan number to which the requested allocation record is attached. This field automatically populates if the requested allocation record is accessed from a resource plan.
    Requested hours The number of hours to allocate to the requested allocation record.
    Requested cost The estimated cost of resource

    Requested cost = Requested hours * hourly rate

    The hourly rate is derived:
    • from labor rate card for user resource plans.
    • from role rate when resource is requested by resource role and, if the role has a rate.
    • from group hourly rate if role does not have a rate or if the role is null.
    • from system property com.snc.time_card.default_rate if all the above conditions fail.

    Requested costs roll up to the Planned cost field on the resource plan.

  5. Click Submit to save the record and return to the resource plan.
    Note:
    • A requested allocation does not have an allocation for a named resource. It only details start date, end date, and the requested hours.
    • By default, the planned hours on the resource plan form get proportionally distributed among all the requested allocations based on number of working days for each requested allocation record. However, it is possible to override the requested allocation hours and/or FTE.
    • If a resource is requested as FTE, then the requested hours for each requested allocation record is calculated first. A total of all of them is then rolled up as planned hours on the resource plan.

Example

If a resource is requested from Sep 1st to Nov 30th for 360 hours, requested allocation records are created as follows:

Case 1: For allocation type Plan Duration, the following requested allocation records would be created:

Allocation start Allocation end Requested hours
Sep 01 (Resource plan start date) Sep 30 (Resource plan end date) 360

Case 2: For allocation type Monthly, hours are proportionally distributed based on working days as follows:

  • Total working days for the planned duration = 65
  • Hours to allocate per working day = 360/65 = 4

The following requested allocation records would be created:

Allocation start Allocation end No. of working days Requested hours
Sep 01 Sep 30 22 22 * 4 = 88
Oct 01 Oct 31 21 21 * 4 = 84
Nov 01 Nov 30 22 22 * 4 = 88

For Weekly allocation type, requested allocation records created similar to monthly.