Resource Demand

Resource Demand - Entering Committed Values

The Resource Demand screen allows Committed values to be allocated to a Project Manager's Resource requests or resource allocations created directly into the Resource Demand screen. There are multiple ways to enter Committed values into the Resource Demand table.

Typing Committed Values

You can type values directly into the Committed cell.

If you type values directly into a period that contains a Proposed value following these rules:

• Rule 3
• Rule 3.1
• Rule 5

If you type values directly into a period that contains no Proposed value following this rule:

• Rule 4

Note: You can type any value into the Committed cell, even if the resource does not have availability for that period.

Autofill

The Autofill feature copies the value from the Proposed cell into the Committed cell following these rules:

• Rule 3
• Rule 3.1
• Rule 5

There are two Autofill options:

1 An Autofill button at the bottom of the Resource Demand table.

This button only becomes active if there are visible requests that don't have committed values: therefore, there is a value within the Proposed field and no value within the Committed field. This button will Autofill any requests that are visible in the table. Therefore, if a project is folded and you don't see all its requests, the autofill won't apply to those non-visible requests.

2 An Autofill option on the row menu.

This button only becomes active if there are requests that have not been previously actioned visible for this resource: therefore, there is a value within the Proposed field and no value within the Committed field.
This button will Autofill any requests for the selected resource that are visible in the table.

Click to Copy

You can click either the Proposed or Availability value for a resource to copy that value into the Committed field. This process will overwrite the Committed value if there is already one in the cell.

The difference with this function is that:

• If you click the Proposed value this will copy the Proposed value to the Committed field, but it will only copy hours up to what is available for that resource in that period. So, it may not copy the full Proposed value if the Resource is not available for the full amount.
• If you click the Availability value this will copy the Proposed value to the Committed field, but it will only copy hours up to what is available for that resource in that period. So, it may not copy the full Proposed value if the Resource is not available for the full amount.

When you use Click to Copy the data copied into the Committed field still follows these rules where the Resource has availability.

• Rule 3
• Rule 3.1
• Rule 5

Note

The % Capacity mode has different precision than the Hours mode. This may lead to discrepancies if you execute the Click to copy in % Capacity mode and then switch to Hours mode.
Click to Copy in % Capacity will copy the % with lower precision. It will not copy the hours.
If Hours are your source of truth, we recommend to use Click to Copy in Hours mode to avoid any discrepancies issues.

Calendar Exceptions

Calendar Exceptions are used to input non-working time for Resources. If using Autofill, days with calendar exceptions will not automatically have allocations placed against them, and the hours will be distributed across the rest of the days that are part of the period selected. Resource Managers can always manually override this if the allocation must fall on a day with a resource calendar exception.

Calendar Exceptions can be created at the Default Calendar level (for an organisation to set non-working days for all Resources allocated to that Default Calendar) or at the Resource level (to set non-working days for an individual resource).

Days with Calendar Exceptions will show in the Resource Plan and Resource Demand screen with 0 Capacity.

• If hours are proposed for days with a Calendar Exception they will show as red, and if the Resource Manager chooses to Autofill their Committed hours it will Commit 0 hours to that period. Specific hours manually entered this period will show as an overallocation.
• If hours are proposed to a higher calendar time period that contains a Calendar Exception, the allocation will not be added to the days with a Calendar Exception and will be shared evenly between the working days in that period. Due to this, these working days could become over allocated and will need to be managed. For example:
  • If a PM has requested a resource for the whole week by adding 40 hours or 1 FTE to the weekly view, and that week has one Calendar Exception day within it, those 40 hours will be spread evenly over the 4 remaining days making each of them over-allocated by 25%
  • If a PM has requested only 4 of the days within a week that contains one Calendar Exception day this allocation will be allocated to the 4 working days correctly.