H
Hameer (Equina)
Use-case:
Currently, we set min-max per month etc that ties in to the employees FTE obligations to their department. And when FTE changes, we auto-update min/max, but this is cumbersome. It is even more tricky when one person's FTE change impacts everyone elses FTE. So wanted to suggest an alternative approach for future or if this is something you have solved previously.
So, to play this out...
Department FTE needs: 2.0 FTE
Number of Employees: 3
Employee A: 0.75 FTE
Employee B: 0.75 FTE
Employee C: 0.5 FTE
Employee C retires and the department is unable to hire a replacement.
REACTION 1
: Department works short and Employee A and B's FTE remains unchanged. This one is easy we as we don't have to touch the min/max rules for those employees.
REACTION 2
: Department needs to adjust Employee A and B's FTE to 1.0 FTE to cover the loss. This requires a re-update of all the min-max rules.
Suggestion: Have an FTEDefinition object for what is 1.0 FTE per defined period:
FTEDefinition: [
{
"id": "1.0",
"includeShiftTags": [],
"period": "YEAR",
"hoursPerPeriod": null,
"shiftsPerPeriod": null,
"daysPerPeriod": null,
}
]
And then Each employee object has a LIST field for their FTE obligations, each containing the FTEFraction and the associated FTEDefinition.
This will allow an easy way to establish the baseline requirements and still allow us to capture more nuance with the existing period rules. Not sure whether would you translate the FTE obligation on the back end to to a HARD max and soft MIN?
Created by Jurriaan Persyn
·