Create requested allocations for a resource plan Requested Allocations are automatically created when a resource plan is submitted and is in Planning state. If required, resource requesters can create new requested allocations for a resource plan in Planning or Rejected state. Resource managers can create requested allocations for the plans in Requested state. Before you beginRole required: resource_user About this task A requested allocation does not have an allocation for a named resource. It only details the start date, end date, and the planned hours. To specify the breakup of resource requirements for monthly or weekly Allocations types, you can modify the requested allocations. For example, you have requested 100 hours of a resource from January to February, but you want 20 hours in January and 80 hours in February. You can specify these details on the Requested Allocations form. Procedure Navigate to Resource > Resource Plans > Planning or Rejected. Open a resource plan. In the Requested Allocations related list, click New. On the form, fill in the fields. 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 Number of units for the full-time equivalent selection for the requested allocation record.If a resource is requested as FTE, then the requested hours for each requested allocation record is calculated first. A total of all hours is then rolled up as planned hours on the resource plan. 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 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 Number of hours to allocate to the requested allocation record.By default, the planned hours on the resource plan form are proportionally distributed among all the requested allocations based on the number of working days for each requested allocation record. However, it is possible to override the requested allocation hours or the FTE. Requested cost Estimated cost of resource. Requested cost = Requested hours * hourly rateThe hourly rate is derived from one of the following sources: Labor rate card for user resource plans. Role rate when resource is requested by resource role, if the role has a rate. Group hourly rate if role does not have a rate or if the role is null. System property com.snc.time_card.default_rate if all the other conditions fail. Requested costs roll up to the Planned cost field on the resource plan. To save the record and return to the resource plan, click Submit. Example If a resource is requested from September 1 to Nov 30 for 360 hours, requested allocation records are created as follows: Case 1: Plan duration allocation type For a plan duration allocation type, the following requested allocation records would be created: Allocation start Allocation end Requested hours Sep 01 (Resource plan start date) Nov 30 (Resource plan end date) 360 Case 2: Monthly allocation type For a monthly allocation type, 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 a weekly allocation, requested allocation records created similar to monthly. Three allocation records, one for each month are created.