I am creating an employee utilization report for our new Manager of Forced Efficiency (no, he does not carry a whip). In the process I discovered what looks like a very useful field in the LaborDtl table called EarnedHrs. I had been trying to calculate exactly the same thing manually. This works great for 'P' types but for 'S' (setup) it is providing very inconsistent results....such as for one employee on two consecutive jobs...
Quoted Time........ActualTime.......Actual Hrs......Earned Hrs
1.50......................... .90 .............. .90 ............... 0.00
1.70 ...................... 1.60 ............. 1.60 ............... 1.70
Both operations were marked as complete.
In both cases the employee completed the setup in less than the quoted time and should have earned the quoted time. Why would the first one earn him zero hours? We have not found a common thread in the results. The explanation in the data dictionary is sort of confusing...if not outright wrong in my printed 5.20 version....
"For setup labor the earned hours is the lessor (sp) of (Est.Setup - ActSetup) or LaborDtl.BurdenHrs". When I look at burden hrs it is always the same as labor hours so it could never be "lesser" than the difference of Est - Act. Basically what we want is the employee to earn the quoted time if they complete thr setup in equal of less time or else earn zero if they went over or the operation was not complete. Yes, I know this gives the person completing the setup a huge chance of being under quoted and over-earning the hours but I'm told it all averages out. We almost always do setups in one shot. Job 2 above does what we want but the number one being zero earned hours is wrong. Any known reason for this?
Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.
[Non-text portions of this message have been removed]
Quoted Time........ActualTime.......Actual Hrs......Earned Hrs
1.50......................... .90 .............. .90 ............... 0.00
1.70 ...................... 1.60 ............. 1.60 ............... 1.70
Both operations were marked as complete.
In both cases the employee completed the setup in less than the quoted time and should have earned the quoted time. Why would the first one earn him zero hours? We have not found a common thread in the results. The explanation in the data dictionary is sort of confusing...if not outright wrong in my printed 5.20 version....
"For setup labor the earned hours is the lessor (sp) of (Est.Setup - ActSetup) or LaborDtl.BurdenHrs". When I look at burden hrs it is always the same as labor hours so it could never be "lesser" than the difference of Est - Act. Basically what we want is the employee to earn the quoted time if they complete thr setup in equal of less time or else earn zero if they went over or the operation was not complete. Yes, I know this gives the person completing the setup a huge chance of being under quoted and over-earning the hours but I'm told it all averages out. We almost always do setups in one shot. Job 2 above does what we want but the number one being zero earned hours is wrong. Any known reason for this?
Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.
[Non-text portions of this message have been removed]