ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> Direct Labor Interfacing?
http://www.istechforum.com/YaBB.pl?num=1190054500

Message started by kkmfg on 09/17/07 at 11:41:40

Title: Direct Labor Interfacing?
Post by kkmfg on 09/17/07 at 11:41:40

I'm toying with the idea of writing an application that runs in our shop that grubby people can use to figure out what they need to be working on. By this I mean, a program with a large font and that requires minimal touching of the keyboard and mouse. Also, I hope to allow them to sign in and out of jobs right there on the spot.

This would require that I can get the Work Order and routing data directly out of DBA through ODBC. That I think I can do. The problem is, is it safe to attempt to directly place the labor data into DBA/EVO's database? I'd really rather not have to use some kludgy way like using DE-H-A. That would require a batch import only every so often and that sucks.

Any pointers would be appreciated.

Title: Re: Direct Labor Interfacing?
Post by JDlugosh on 09/17/07 at 17:10:32

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.

Title: Re: Direct Labor Interfacing?
Post by Lynn_Pantic on 09/17/07 at 17:16:28

If you know what you are doing, you could populate the BKDCPLAB table. Look at the BKDCA.SRC on the DBA 2002.4 or 2004.1 CD to get the basic logic for clocking in and out. The trickiest part is when multiple jobs are involved. If your people are always working only one job at a time, it would be pretty straightforward. Using the BKDCPLAB (unposted labor) table would then enable DC-D reporting, DC-G editing as needed and require the DC-H posting so you would have error checking and not have to worry about all the spaghetti logic of posting to the GL and Job Cost and updating routings etc.

Title: Re: Direct Labor Interfacing?
Post by kkmfg on 09/17/07 at 17:45:22

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!

Title: Re: Direct Labor Interfacing?
Post by kkmfg on 09/18/07 at 07:08:59

DC-A won't do squat unless you define shifts... I don't want to define shifts and assign employees to the shift. We don't always have people working 8-4:30 with a half hour lunch. What if people take an hour lunch on payday (which they do)? What if sometimes people work 8:30 - 5 instead (which they do)? If I directly input data into the table can I skip the shifts or will DC-H mess up then? All I want is to track the # of hours worked on a project. I don't care about overtime or shifts or anything like that.

Title: Re: Direct Labor Interfacing?
Post by Lynn_Pantic on 09/18/07 at 07:19:24

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.

Title: Re: Direct Labor Interfacing?
Post by kkmfg on 09/18/07 at 07:24:00

Cool! Thanks!

Title: Re: Direct Labor Interfacing?
Post by kkmfg on 09/18/07 at 07:37:39

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.

Title: Re: Direct Labor Interfacing?
Post by Lynn_Pantic on 09/18/07 at 07:39:21

Status "I" (Indirect) work orders can be used to charge downtime and you can make them as simple or complex as you want in terms of multiple work orders or sequences for different reasons for the downtime.

Title: Re: Direct Labor Interfacing?
Post by NovaZyg on 09/18/07 at 07:43:13

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)

Title: Re: Direct Labor Interfacing?
Post by kkmfg on 09/18/07 at 07:44:45

Great! You guys have all the answers today! ;-)