I would be interested in this as well.  I would like to give the shop user feedback on their performance in a very simple format.  I see it as a simple red light / green light  result of comparing actual time against the labor routing for that sequence.  

Hmmm... Intriguing... It's a little less kludgy than DE-H-A in that the data is imported somewhat elegantly and just has to be confirmed with DC-H... It does prevent me from having to touch the other tables. I've looked at some of the WO related tables and I'm not too keen to ever see them again. I'll keep that in mind, thanks!

Define shifts with no breaks or buffers (Buffer and start time the same; buffer and end time the same) and assign all employees and all work to shift 1.  Regardless of time in or time out, if there are no breaks or buffers defined, the program will use the actual time.

One more question....
 
Theres no real good way of tracking downtime with Evo is there? For instance, people might not be able to work because their machine broke, they might get called away to help with something else for a moment, there might be a part shortage, they might be in a meeting, etc. These things shouldn't be charged to a work order but they still happen. Is there no way in Evo to track that time to see what sort of downtime is happening and why? In my mind this is part and parcel of a total labor tracking package. Of course, it doesn't fit as well into an accounting package as it's not directly charged to anything but it's still useful to know how often someone gets called away, how much time was spent in meetings, how often people are waiting on broken equipment, etc.

yes, you can create an Indirect work order and have them charge the down time to that.. We have customers that do that. (create a type I work order then you never close WO# 999999-999)