User guide

Understanding What a PCN Is
6-2: Generating PCNs and Uploading BOMs
Design Purpose of PCNs
PCNs are like ECOs, except they apply to prototype assemblies instead of those in
quantity production for a released product. This implies that PCNs are designed
to:
• Control the components, subassemblies, mechanical and schematic drawings,
etc., of products that will eventually be released into full production.
• Publicize any changes to these components.
• Alert Purchasing to long lead-times for parts so that the prototype assemblies
can be put together in a reasonable time frame, and so quantity purchases can
be made in a timely fashion.
• Notify Component Engineering which parts will make up the assembly, so
component engineers can make sure that approved vendors are available for
the parts and that the parts themselves have been approved for quality.
• Warn Test Engineering that components might have changed so their test
plans might be affected.
• Provide reviewed and controlled files for various outside agencies such as
layout and fabrication houses that need to obtain design information.
• Influence parts buying by subcontract manufacturing houses, who receive the
PCNs in hardcopy and may use them to update their own internal systems.
How PCNs Affect Other Groups
PCNs affect many groups within Bay Networks. Those mentioned here are just to
give you a better idea of how PCNs might be interpreted by others.
Commodity Supplier Management and PPM
The additions and deletions of components that you make to a BOM when you
submit a PCN are seen differently by CSM and PPM (Product Purchasing
Management) groups. CSM, for example, might be most interested in the fact that
there is no approved vendor for your additions, or that the number of your
additions might change which vendor is used. PPM, on the other hand, might be
more interested in the list of additions, or parts with no cost information.