Capturing & Tracking Rework Costs

Yahoo Archive
1
Or train your people to report the labor as Rework Labor.

Or check off 'added operation' exclusively only when they are rework OPs added.

Or...?

Any of that practical in your environment?

Rob Brown

--- On Wed, 4/15/09, jplehr <jlehr@...> wrote:
From: jplehr <jlehr@...>
Subject: [Vantage] Capturing & Tracking Rework Costs
To: vantage@yahoogroups.com
Date: Wednesday, April 15, 2009, 9:12 AM

















Vantage 8.03.406



I am submitting this question as written by one of our Operation Managers. Any help or thoughts will be huge.



Question: We want to track the total cost of any rework on a job. We add each operation to the job that is a rework operation. So if the standard ops were:10, 20, 30, 40 & 50, we would add ops: 21, 22 & 23 as rework. We need a way that we can run a cost report that will segregate the material and labor against operations 21, 22, & 23 by whatever code we assign to them.



The possible answer I have asked about is the Analysis Code. This code has a field that can be entered on each operation individually. If we can establish different codes for each reason (or person), we could assign this code to every operation that is rework or remake. Then we could run a report by a specified date range to call up the total cost of each code separately—to track each code—or as a group to track total rework/remake costs over a period of time.



Jeff
2
Vantage 8.03.406

I am submitting this question as written by one of our Operation Managers. Any help or thoughts will be huge.

Question: We want to track the total cost of any rework on a job. We add each operation to the job that is a rework operation. So if the standard ops were:10, 20, 30, 40 & 50, we would add ops: 21, 22 & 23 as rework. We need a way that we can run a cost report that will segregate the material and labor against operations 21, 22, & 23 by whatever code we assign to them.

The possible answer I have asked about is the Analysis Code. This code has a field that can be entered on each operation individually. If we can establish different codes for each reason (or person), we could assign this code to every operation that is rework or remake. Then we could run a report by a specified date range to call up the total cost of each code separately—to track each code—or as a group to track total rework/remake costs over a period of time.

Jeff
3
One way we have done it in the past is we add an entirely new assembly
with the requisite steps for a part number the original part prefixed
with RWK (rework). This had a few benefits in that with crystal it was
simple to filter by job and the RWK assembly. The down side was that
you would then be 'making' a non system part number. Cost isolation was
(for us) simple at that point. We are from our experiences now moving
to a different method whereby we accept the parts from DMR to a new RWK
Job as material and then link that new job to the original job. Now we
have all costs isolated to a unique job that is easily tied back to the
original. The only caveat to the whole affair is how the quantities
that were originally debited to the operation from the nonconformance
are completed. Well be addressing that with a BPM/Service connect
solution.



Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of jplehr
Sent: Wednesday, April 15, 2009 8:13 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Capturing & Tracking Rework Costs





Vantage 8.03.406

I am submitting this question as written by one of our Operation
Managers. Any help or thoughts will be huge.

Question: We want to track the total cost of any rework on a job. We add
each operation to the job that is a rework operation. So if the standard
ops were:10, 20, 30, 40 & 50, we would add ops: 21, 22 & 23 as rework.
We need a way that we can run a cost report that will segregate the
material and labor against operations 21, 22, & 23 by whatever code we
assign to them.

The possible answer I have asked about is the Analysis Code. This code
has a field that can be entered on each operation individually. If we
can establish different codes for each reason (or person), we could
assign this code to every operation that is rework or remake. Then we
could run a report by a specified date range to call up the total cost
of each code separately-to track each code-or as a group to track total
rework/remake costs over a period of time.

Jeff





[Non-text portions of this message have been removed]