RE: Recording Machine Down Time

[Chris.Kosieracki@xxxxxxxxxxxxxxxxxxxx]

How about creating an item master and balance record for each machine, then
performing an IS transaction with reason code each time it goes down, and an
RC transaction each time it's put back into service. Since all of the IMHIST
transactions are time stamped it would be fairly easy to run a query/report
on downtime. This approach would also allow you to easily see the state of
each machine. In stock means its up, out of stock means it's down.

-----Original Message-----
From: Philip Freimann [mailto:PFreimann@cranecams.com]
Sent: Thursday, June 06, 2002 10:24 AM
To: 'mapics-l@midrange.com'
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.