Create an operational resource plan

You can create an operational resource plan and allocate a certain portion of your teams capacity for operational work, such as KTLO, administration, meeting, or training.

Before you begin

Role required: resource_manager, admin

Procedure

  1. Navigate to Resources > Resource Plans > Create New Operational Plan.
  2. Fill in the fields as appropriate.
    Table 1. Operational resource plan form
    Field Description
    Number Automatically generated identification number for the operational resource plan.
    Resource type Category of a resource. Select Group resource to select a group or User resource to select an individual user.
    Group resource Group for which the operational resource plan is created.
    User resource User for whom the operational resource plan is created.
    Members preference
    Note: This field appears only when Group resource is selected in Resource type.
    You can select All members from the group or Specific members from the group. The default is set to All members.
    • If All members is selected, the resource plan includes all members of the group and time is proportionally divided among group members depending upon their capacity. Before making the hard allocation, if all members are not required, a resource manager can select only specific members from the group.
    • If Specific member is selected, a request is made for the specified members. The requested hours are proportionately split among specified users of the group, based on their available capacity.
    Role
    Note: This field appears only when All members are selected in Members preference.
    From the group resource, select the specific resource role that you want to associate with the plan.
    Skills
    Note: This field appears only when All members are selected in Members preference.
    From the group resource, select the specific skill(s) that you want to associate with the plan.
    Request type Type of request: Hourly or % Capacity. Select Hourly to estimate the work in terms of hours. Select %Capacity to estimate the work in terms of their capacity.
    Planned hours Estimated number of hours required to complete the operational work.
    Number of hours allocated for operational work Hours of a resource allocated for operational work.
    Name Descriptive name for the operational resource plan.
    Operational work type Type of operational work: KTLO, Training, Admin, or Meeting. The default is set to KTLO.
    Start date

    Date when the operational resource plan starts.

    End date Date when the operational resource plan ends.
    Allocation type Resource distribution type that determines the type of allocation records. The value in this field determines how the planned hours are distributed across the resource plan duration, among requested resources. Select any of the following options:
    • Weekly: Creates week-long allocations up to the end of the planned end date.
    • Monthly: Creates month-long allocations up to the end of the planned end date. Mon is the default value.
    • Plan Duration: Creates one allocation for each user for the entire duration of the resource plan.
    For example, if a resource is requested from Jan. 1sto Mar. 31st, the following records are created for each type:
    • Monthly: 3 allocation records, one for each month.
    • Weekly: 14 allocation records, one for each week with Monday being first day of the week.
    • Plan Duration: Only 1 record for the entire duration of the resource plan.
    Allocation spread Type of allocation spread. The value in this field determines the manner in which the allocated hours are spread while creating hard allocations. Select any of the following options:
    • Even: Creates resource events for the resource by splitting the hours evenly across all the working days for the allocation duration.
    • Front Load: Creates resource events for the resource by filling up all the available slots of the resource from the start date of the allocation.
    For example, if a resource is requested for 30 hours in Week 10, then
    • Selecting Even equally divides 30 hours to all weekdays, which are 6 hours per day for a five day working week.
    • Selecting Front Load consumes all the available hours on Monday, moves on to Tuesday, and so on, until all the 30 hours are allocated. If the resource is not available for 30 hours in Week 10, it over-allocates by filling up the remaining hours from start date up to 24 hours per day.
    State A plan starts in the Planning state. The plan moves to the Requested state after its submission.
    Planned cost Amount in Planned Hours multiplied by the hourly rate of the specified user or group resource. Planned cost is a first draft estimate of the resource plan cost.

    Planned cost is rolled up from Requested Allocations for plans in the Planning/Requested state and from resource allocations for plans in the Allocated state.

    Note: While requesting for resources from a group, if a resource role is specified, then the planned cost is calculated from the hourly rate of the specified role.
    Allocated cost Amount on all resource rate cards multiplied by total allocated hours. Used to give a more accurate estimation on the cost of the plan when it is being allocated.

    If no labor card is found for the user, then the hourly rate is taken from the following time card property: Default hourly rate used when processing time cards if we cannot get a rate from labor rate cards (in system currency).

    Notes Additional correspondence and information.
    Related Links
    Copy Resource Plan Copies the opened resource plan to create a new resource plan.
    Related Lists
    Requested Allocations List of requested allocations for the resource plan.

    The number of requested allocation records created depends on the value of Allocations type field. For example, if a resource is requested from Jan first to Mar. 31st, the following requested allocation records are created for each type:

    • Monthly: 3 allocation records, one for each month.
    • Weekly: 14 allocation records, one for each week with Monday being the first day of the week.
    • Plan Duration: Only 1 record for the entire planned duration of the resource plan.
    Resource Allocations List of resources allocated to the plan.