Show TOC

Component documentationNonconformance (NC) Locate this document in the navigation structure

 

The Nonconformance feature helps you improve product quality and customer responsiveness by allowing you to do the following:

  • Track failure, defect, and repair information about SFC numbers

  • Control the disposition of nonconforming products

  • Assign incident numbers to logged nonconformances

  • Calculate defects with the standardized DPMO (defects per million opportunities) methodology as defined in the IPC-9261 standard for printed board assembly manufacturing

  • Display up-to-date engineering schematics graphically in the Printed Circuit Assembly (PCA) Dashboard, allowing you to display engineering changes in real time

At various steps on your routings, you can include operations where a product is tested or inspected for defects. When a product does not meet a quality specification, the operator or machine at that step nonconforms, or logs a nonconformance (NC) against that particular SFC number.

Note Note

You can log a nonconformance code for a product defect. This includes test or product quality defects, such as a scratch on a chassis.

End of the note.

When an operator logs an NC, the system can automatically send the nonconforming SFC number to one of the following locations:

  • The first step on a disposition routing

  • A disposition function

  • Another step on the current routing for analysis or repair

    Operators at these steps can log additional NCs against the SFC number to detail its current condition.

Implementation Considerations

When you set up nonconformance, you must decide:

  • How you want routing branching and dispositioning to behave in the system (see Branching with Nonconformance Codes and Scripting, Nonconformance Dispositioning)

  • What information you want to collect for analysis, integrity checking, and other uses when operators log nonconformances

  • Which nonconformance codes you want operators to use when they log NCs, and how you want to organize them (see NC Code)

  • How you use real-time warnings (see Real Time Warnings Maintenance)

  • How you want the Production Operator Dashboard (POD) to behave and appear for operators who log nonconformances (see Setting Up PODs for Nonconformance)

  • How you want the PCA Dashboard in the POD to behave and appear for operators who work with nonconformances against PCA boards

  • How you use DPMO (see DPMO)

Integration

If you use the SAPMEINT component, see Transfer of Nonconformance Data to Quality Notification