### Post

3 followers Follow

# FTE calculation accuracy improvement

At the moment FTE is calculated as (number of working days this month X number of hours a day) / (number of hours a day X number of days in a month which comes from organizational calendar). The number of days in a month should be based on how many working days there are in a month, so if a resource is fully loaded for the month, their FTE should be equal to 1. At the moment this depends on the number of working days in a month.

Example: Say the days in a month organizational calendar setting is 20 days, a resource is 100% loaded and there are 22 working days this month. FTE = (22 d X 8 h) / (20 d X 8 h) = 176 / 160 = 1.1

Please make the number of working days a month a dynamic number instead of static number pulled from the settings.

For future reference please use CR-403160.

Roland Pumputis Not planned

Has this ever been implemented?

Instead you should create a function that we can call to give us the number of Working Days instead of trying to calculate anything for us.

Function should be like --

WorkingDays(<FromDate>,<option>,<ToDate>)

<ToDate> - would be OPTIONAL; but if <option>='to' then you know it is FROM TO DATES

<option> - would be things like 'To, 'Previous 3 Months', 'Previous Month', etc

<FromDate> - would obviously be the "starting point" of the calculation

Finally, this would ALL be based on UTC time unless you want to add another final option <timezone> to allow one to select.

We need a function like this to DYNAMICALLY calculate the number of working days based on our Org Calendar, so it can take into account Holidays and other "anomalies". This can then be used to calculate things like Utilization more accurately; because there are BIG differences between WORK LOAD, BILLABLE TIME, REVENUE GENERATING TIME, etc so we need to be able to do some calculations ourselves...

EVERYONE reading this MUST VOTE; otherwise, no enhancements are ever planned and we ALL needs this...

Hi Wilfredo,

Best regards,

Roland

Hey Roland,

Unfortunately, this function is not available in REPORTS and this is where we need to do Utilization Calculations for displaying to Management.

The nice thing about REPORTS is that they are "dynamic"; but once you start to do all these "heavy calculations", there should be some way to "cache" or "index", because I also get failures on some reports; because we put too many Calculated Fields.

You should be able to add up all the Timesheet durations in a report and then DIVIDE by different Data Calculations; but you "stripped them all out".

Scheduling a job is not acceptable; because that just aggregates values and Managers want to be able to "drill down" in Real-Time.