FTE not as expected if availability does not match the Standard Calendar
Article ID: 35295
Updated On:
Products
Issue/Introduction
The Full-Time Equivalent (FTE) seems to be incorrectly computed for resources whose availability does not match the Standard (base) Calendar
Steps to Reproduce:
- Create a base calendar in Clarity
- Set shifts for 7 hours (Example: 8:00 am - 12:00 pm and 1:00 pm - 4:00 pm) for all working days (Monday-Friday)
- Define a resource and attach this calendar to that resource. The availability will automatically be set to 7 as expected
- Now look at the out of the box weekly details portlet and see the resource availability in FTE units
Expected Result: Expecting the resource availability to be one (1) FTE since you do not have any allocations for that resource and they are working all 7 hours as per the resource calendar.
Actual Result: The resource availability is shown as 0.88 (which is 7/8).
Cause
This is working as designed. FTE is calculated based on the Standard Calendar not a resource's base calendar. So, if the standard calendar has 8 hour shifts, and a resource's availability is 7, it will divide the 7 hours of availability by the 8 hours on the standard calendar.
Similarly, if the standard calendar has more/less workdays than the resource's calendar, the FTE will divide the resource's availability by the availability on the standard calendar for that same period. For example, if the standard calendar has 19 eight hour work days for one month and the resource has 20 eight hour work days for this same month, the FTE for the resource for this month will be 20 divided by 19 or 1.05 FTE.
Resolution
As mentioned in the cause section, this is working as expected. This applies to both the Classic and Modern User Experience (UX).
The same logic also applies to the number displayed when "Days" is the "Work Effort Unit of Measure".
Additional Information
Feedback
