We globally reschedule every night (Monday - Friday), and I have created a Priority Dispatch Dashboard that drives the shop schedule.
The owner wants to view a report of the operations that were scheduled to be completed today, and see if they were completed when scheduled (Hit) or were not able to be completed on their original scheduled day (Miss).
With having Epicor globally reschedule every day, it changes the operation start dates that were not completed when scheduled to a new date, making it difficult to track which operations were not completed as well as how many times an operation has been rescheduled.
Does anyone have any insight or suggestions that could help us out in this situation?
Thanks in advance for any support you can provide.
We started down that path and realized how many operations you complete can become somewhat arbitrary. To know if we were hitting schedule we pivoted to tracking relieved hours form the schedule on a daily basis. I built a custom process to do this. Pretty sure it uses the Load Hours and Resource Time Used tables. Runs weekly on sunday and off loads to a UD table for memorial
Thanks for sharing this Josh, it’s pretty awesome and the concept might come in handy in a future report.
Is your labor entry method based on Time & Quantity? We’re quantity only and unfortunately, the owner is very specific about seeing hits/misses, regardless of the difficulty.
Currently, we’ve got an MS Access table that is pulling and storing the Jobs/Opr/Dates before they’re globally rescheduled, and if the same Jobs/Opr show up the next day, we know it was rescheduled and was not completed. This allows us to count the number of hits/misses, but I know there has to be a better way of doing this in Epicor. I’m wondering if there is a way to have the global rescheduling process take all of the operations that were not completed and need to be rescheduled and record them in a UD table.
