|
You bring up some good points. I never discount your input - you're normally right on. I appreciate reading your input to the group. -----Original Message----- From: Leleux@shur-lok.com [mailto:Leleux@shur-lok.com] Sent: Thursday, June 06, 2002 12:42 PM To: mapics-l@midrange.com Subject: RE: Recording Machine Down Time [ Converted text/html to text/plain ] Does not distort payroll. In terms of division of man-hours, it all depends on how you look at it. We have a woman working three screw tappers, her time is split between the two machines as she is capable (and expected) to do so. Each job is getting 1/3 her time. So machine 1 becomes unavailable for tooling reasons, she clocks off that job, onto the 'waiting for tool repair' job. The two running jobs still get 1/3 her time, and the waiting job gets 1/3. Our philosophy is that since she divides her time anyway, the remaining jobs shouldn't go to 1/2 because they don't need that level of attention - nor will they get it as that would falsely increase the cost of that job. She may spend her time cleaning her area (we have a job for that!) or prepping for another job (not necessarily setup). We can analyze the 'variance' jobs and get some feedback on shop problems, such as tool repair, raw material shortages, etc. And hopefully get to the bottom of things, all in the name of improvement, not punishment. Can't answer the overhead issue at the moment, but I think it would and should if the employee is under-utilized. Kinda like a very expensive CNC being used for penny parts, you still gotta pay for the machine even if the jobs don't. Forgive me if my explanations are oversimplified or shortsighted, I'm a techie! Philip Freimann <PFreimann@cranecams.com> Sent by: mapics-l-admin@midrange.com 06/06/2002 08:23 AM Please respond to mapics-l To: "'mapics-l@midrange.com'" <mapics-l@midrange.com> cc: Subject: RE: Recording Machine Down Time We do that to. But in this case the employee is on another job - he is not idle - the machine is idle. If you created a "job" for the machine down time - the hours charged to it would go as indirect labor hours. Wouldn't that distort the overhead and labor or payroll hours? We also have a stand alone maintenance and repair system - but that would only record the time a repair person is actually working on the machine, which could be quite different from it's total down time. -----Original Message----- From: Leleux@shur-lok.com [mailto:Leleux@shur-lok.com] Sent: Thursday, June 06, 2002 11:24 AM To: mapics-l@midrange.com Subject: Re: Recording Machine Down Time [ Converted text/html to text/plain ] We have 'job's set up for specific activities such as 'waiting for raw material', meetings, 'waiting for tool repair' etc. You can create a 'job' for a specific machine (work center) to be used when it's down. We have a report that analyses employees variance time, if they're not on a job......enquiring minds want to know why! I wonder if MAINCOR addresses it? Since there is a web client that can be used in the shop, the machinist could enter the data. Good question, especially since we have MAINCOR! Philip Freimann <PFreimann@cranecams.com> Sent by: mapics-l-admin@midrange.com 06/06/2002 07:46 AM Please respond to mapics-l To: "'mapics-l@midrange.com'" <mapics-l@midrange.com> cc: Subject: Recording Machine Down Time Has anyone found a creative way to record the period of time that a machine is not available? The operator is moved to another job, so he can not record time against it. The Maintenance person might not get to it for days - if waiting for parts, so the amount of time they spend "on the repair" is not relevant. We can't record indirect hours that would be added to the overhead. Philip R. Freimann Director of Information Technology Crane Technologies Group (386) 252-1151, ext. 1,4282 mailto:PFreimann@CraneCams.com _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l or email: MAPICS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l or email: MAPICS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l or email: MAPICS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l or email: MAPICS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.