View Full Version : What do you do when a part goes Obsolete and How do you Initiate such a Process?
haueyman 25th February 2008, 10:36 AM What do you do when one of your parts go obselete, what tool or document do you use to initiate the process in you company to start the obselete process.
We issue a ECN (Engineering Change Notice), but we use this when anything changes for a part. I don't feel this is the proper tool to use when a part is going obselete and I wanted to see what others do.
Geoff Withnell 25th February 2008, 10:44 AM What do you do when one of your parts go obselete, what tool or document do you use to initiate the process in you company to start the obselete process.
We issue a ECN (Engineering Change Notice), but we use this when anything changes for a part. I don't feel this is the proper tool to use when a part is going obselete and I wanted to see what others do.
Actually, using an ECN is not that uncommon. For both parts, processes and documents that go obsolete, my preferred method is to issue one last revision, which states "Part/Process/Document/#xxxxxxx is obsolete." If there is a replacement, the ECN can also state this. This method assures that someone looking up the relevant part will find the info that it is obsolete.
Geoff Withnell
haueyman 25th February 2008, 10:52 AM Actually, using an ECN is not that uncommon.
Geoff Withnell
Wow, that is suprising, it just seems that an Engineering change is not happening other than the part is going obselete, and who initiates that, Materials?
Jim Wynne 25th February 2008, 10:56 AM Wow, that is suprising, it just seems that an Engineering change is not happening other than the part is going obselete, and who initiates that, Materials?
Obsolescence is a configuration change, and that's what this sort of control is all about. Using the ECN process is usually better than creating another document and/or process.
Geoff Withnell 25th February 2008, 10:57 AM Wow, that is suprising, it just seems that an Engineering change is not happening other than the part is going obselete, and who initiates that, Materials?
Could be Materials. Whoever decided (and had the horsepower) to make the part obsolete. Using the ECN process to do so makes sure all the stakeholders know that the action has been taken, so assembly parts lists get changed, for example.
Jim Wynne 25th February 2008, 11:00 AM Could be Materials. Whoever decided (and had the horsepower) to make the part obsolete. Using the ECN process to do so makes sure all the stakeholders know that the action has been taken, so assembly parts lists get changed, for example.
Yes--there should be a standard process in place that addresses things like disposition of existing stock, updating BOMs, etc. The ECN shouldn't be seen as something that's invoked only when a part physically changes somehow.
Wes Bucey 25th February 2008, 11:53 AM Just so we are all on the same page.
An Engineering Change (order, notice, request, whatever) is just one step in the revision process. The document still has to go through a formal process of revision. That revision may be a change of some sort or it may be a declaration of obsolescence.
Typically, documents are declared "obsolete" only when they are replaced by something. If a company stops making widgets (GM going out of the minivan business, for example), they probably do not perform a complete housecleaning of any and all documents related to widgets as "obsolete." (GM does still support its minivans with parts and service.) If, however, the company replaces the widget with a "gidget" that performs many of the same functions as a widget, but has completely different form and fit and would probably be purchased by folks looking for a widget, then the widget is declared "obsolete, replaced by gidget."
Jim is absolutely on the mark when he saysYes--there should be a standard process in place that addresses things like disposition of existing stock, updating BOMs, etc. The ECN shouldn't be seen as something that's invoked only when a part physically changes somehow.
Think of the Engineering Change [fill in the blank] as the "Why" and the "How" that explains circumstances surrounding the change.
:topic:I recently had occasion to learn what GE means when it says a product is obsolete. My kitchen stove worked wonderfully for 16 years and then the clock mechanism which controlled the automatic on/off oven and self-cleaning cycle just failed. When I tried to get a replacement, GE said, "That model and all its parts are obsolete. We no longer support it."
"OK. I replied. What have you got that I can retrofit?"
The response was, "Nothing. Perhaps you could try a junk dealer to see if there are any old models with a working device!"
Obviously, I could have pursued the matter further, but I just bought a new stove of another maker and make it a point to NEVER buy GE products again. My thinking was, "GE obviously doesn't want me as a customer or they would have trained the phone staff to be more helpful, perhaps even referring me to an engineer who might have a suggestion for repair or a workaround."
haueyman 25th February 2008, 12:04 PM Think of the Engineering Change [fill in the blank] as the "Why" and the "How" that explains circumstances surrounding the change.
[/I]."
Great thank you for your wisdom, I need that more often. That really helps with understanding why I would use the ECN and not something different.:applause:
:thanks:
|
|