PCN Process and Notification Specification...

R

Ricky

Guest
I\'m being asked by a potential customer if I\'m familiar with \"PCN process and notification\". My company does not normally make changes to products other than to substitute components that are functionally equivalent. A different brand of resistor, or capacitor, sometimes chips, are used when the original part is not available. I don\'t generate a PCN for such changes.

Is there any sort of a formal specification for when a PCN needs to be generated?

One of the things I plan to do on this new design, is to provide the ability to use modified pinouts of otherwise similar parts. One of the parts I use has options for polarity of the control on an analog switch. They\'ve always been bought as the low true enable version. There\'s also a high true enable version and one with mixed polarities. By \"telling\" the FPGA which version is on the board, the polarity can be configured using a pair of resistors, or possibly just one.

I would make these configuration selections available in a status register, so the system can track and report the BoM options. But these would not be PCN issues.

How do you decide what is and what is not PCN worthy?

--

Rick C.

- Get 1,000 miles of free Supercharging
- Tesla referral code - https://ts.la/richard11209
 

Welcome to EDABoard.com

Sponsor

Back
Top