I am trying to figure out how to calculate the remaining load for an operation like under Job Tracker > Job Details > Operations > List > Load.
I can add up the actual prod and setup times from JobOper. Do I get the load by subtracting this from the Est prod and setup times, or is Remaining Load stored somewhere? How can I calculate it if I am wrong?
I ended up using the ResourceTimeUsed table. I subtracted actual time from Estimated time and the results match the values from Job Tracker.
@NateS This is just for clarity. Your solution works based on the Load Relieved by setting which must be Hours. If you use quantity then you can sum the Earned Hours from LaborDtl.
From Help
Example(s)
The following example(s) illustrate how you use the Load Relieved By functionality.
Quantity Method Example
You indicate that load is relieved by Quantity. You estimate an operation to take .5 hour per piece for 50 pieces, for a total estimate of 25 hours (.5 x 50). After an employee reports 8 hours and 15 pieces, the load remaining is 17.5 hours (35 pcs left x .5 hrs/pc). Note that the scheduling engine always assumes the remaining pieces will be completed in the time originally estimated.
Hours Method Example
You indicate that load is relieved by Hours. You estimate an operation to take 40 hours to do 100 pieces. After an employee reports 8 hours and 15 pieces, the load remaining is 32 hours (40 hrs total - 8 hrs reported).
Thank you @gpayne! This is great.
I am finding some inconsistencies between my BAQ pulling from the RTU table and the Load listed on Job Tracker. The differences are very minor, but I can’t explain them. For example, on one job I can see the load matches between my BAQ and the Job Tracker for four out of five entries. The fifth entry doesn’t quite match. The load listed in Job Tracker is a little bit less than the load listed in my BAQ. Comparing the values I can see that the actual prod hours and Est Prod hours listed in my BAQ are not the same as the values displayed on JobTracker > Job Details > Operations > List. Most of the time these values all match up perfectly.
What would cause these values to get out of sync? I imagine that the initial estimates are pulled into the RTU table when the job is scheduled. Maybe something happened after the job was scheduled that changed the estimated time? I am not sure how this explains the difference in actual production time.
I am so confused!