Explainer

A practical workflow for product-change notices

A PCN should trigger a controlled impact assessment, not an email-forwarding exercise. This workflow gives engineering and purchasing one record of the dates, evidence, decisions and actions.
Product-change notice workflow with component records and approval stages, created as an illustrative editorial image

Illustration created for The Electronics Brief.

A product-change notice can describe anything from a harmless document correction to a material, site or process change that invalidates part of an existing qualification. The first task is to establish exactly what has changed and which approved builds are exposed.

1. Preserve the source notice

Save the original notice, attachments, revision and receipt date. Record the manufacturer, affected part numbers, stated reason, implementation date, last-order date and contact route. Do not rely on a distributor summary where the manufacturer's notice is available.

2. Match exact parts to exact uses

Compare the affected manufacturer part numbers with the approved BOM, alternates list, service inventory and open orders. Include suffixes, package, temperature grade and packing method. Assign an owner for every affected product or assembly.

3. Classify the change

Record whether the change affects form, fit, function, reliability, compliance, firmware, process, manufacturing location, materials, marking, packing or documentation. A supplier's description of a change as minor is useful context, but it is not your impact assessment.

4. Request the evidence your application needs

Ask for comparison data, qualification reports, change-control detail, samples and traceability arrangements. Check whether the evidence covers the exact package and manufacturing route you buy. If a safety, automotive, medical, aerospace or customer-specific approval applies, map the change to that requirement.

5. Decide the validation route

Engineering should state whether document review is sufficient or whether inspection, bench testing, environmental testing, EMC work, firmware regression or customer approval is required. Purchasing should confirm availability of old and new material, date-code separation, minimum order, lead time and last-time-buy conditions.

6. Control implementation

Define the first acceptable date code or lot, receiving controls, stock segregation and BOM or drawing revision. Record who approved the decision and any conditions. Communicate it to contract manufacturers and other sites that may receive the part.

7. Close the record

Link the notice, evidence, test results, supplier correspondence and approval in one record. Keep unresolved questions visible. Closure means the change has been assessed and controlled; it does not merely mean the email has been filed.

Record fields: notice reference; affected parts; internal assemblies; dates; change classification; evidence received; validation required; stock action; approvals; open questions.

Continue reading