Need of Component Obsolescence Management

Component Obsolescence Management is essential to anticipate and mitigate the risk of costly redesign cycles. Obsolescence is most effectively managed when it’s considered from the beginning of product development at the design stage. Obsolescence management techniques can be categorized as either production engineering-based techniques (that attempt to control an existing situation) or design-based techniques (that attempt to minimize the initial problem). While there are no quick or easy solutions, using production- and design-based obsolescence management techniques can minimize the problems faced on long life-cycle programs.

A centralized obsolescence notification system can save millions of dollars in just plain resource hours. There’s an ongoing problem with EOL notification that permeates the industry and requires attention from the highest levels. As an example, a component is built for an OEM application and delivered to one of their plants, where it’s built into an assembly. Then they send it on to another plant to be assimilated into another assembly. From there, it might go on to other one or two locations for further integration and assembly. However, the component that was designed-in for a two-year production order goes out of production in the second year. So an EOL notice is sent to the procurement office contact who bought the part. Maybe the contact is still there, maybe not, and the notice never goes on to the other four facilities in which the product was assembled. There’s a lack of incentive on the part of either the supplier or the purchaser to notify others down the line.

Rainwater harvesting: The Sequel

agreed lol. although more boring than the original.

awesome, very interesting.....NOT

is this a computerized thing? or someone made an account and posted this? please enlighten me. i wonder if they come back to check responses..

Computerized.