Nonconformance (NC) 
The Nonconformance functionality provides a mechanism for the logging, tracking and dispositioning of failed or defective parts or assemblies. It allows you to do the following:
With the help of closed loop system, document the Nonconformance Management process
Expedite the disposition of nonconforming parts / material
Ensure that the appropriate resources receive nonconformance work tasks for which they have been designated and provide traceability
At various steps on your routings, there are operations where a product is tested or inspected for quality standards. When a product does not comply with a quality specification, the operator or machine at that step logs one or more nonconformances (NCs) against that particular SFC number.
You can log a nonconformance code for a product defect. This includes test or product quality defects, such as a scratch on a chassis.
When an operator logs an NC code, the definition of the NC code determines the disposition of the SFC number to one of the following locations:
The first step on a disposition routing
Disposition group options
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 Routing Scripts with Nonconformance Codes, Nonconformance Disposition)
What nonconformance data you want to collect for analysis, integrity checking and traceability to quality issues
Which nonconformance codes you want operators to use when they log NCs, and how you want to organize them (see NC Code)
How to group NC codes for visibility to the operators when they log NC codes (see NC Group Maintenance)
How you use nonconformance codes to generate real-time messages for yield and consecutive nonconformances (see Real-Time Warnings Maintenance)
What nonconformance plug-ins to display during the nonconformance process in the Production Operator Dashboard (POD) (see Setting Up PODs for Nonconformance)
What nonconformance plug-ins to display within the Visual Test and Repair POD to support the nonconformance process (see Visual Test and Repair (VTR) POD)
How you use DPMO categories to track quality issues (see DPMO)
Integration
If you use the SAPMEINT component, see Transfer of Nonconformance Data to Quality Notification.
To record the NC codes resulting from the testing or inspection, analysis and repair of PCA boards or other materials, you can use Visual Test and Repair. It enables you to view and interact with a graphical model of the board (see Visual Test and Repair (VTR)).
You log NC codes for defects of SFC number when you perform sampling. Depending on the total severity of the NC codes that were logged for the sample SFC numbers, the sample is either accepted or rejected (see Sampling).
Features
Nonconformance involves the following features:
Logging of failure NC codes against SFC numbers
You log primary and secondary NC codes against an SFC number in the Log NC plug-in in the Operation POD.
Analysis of the failure and logging of defect and repair NC codes
Once the failure NC code has been logged, it is displayed in the NC Tree. You can perform the analysis of the failure and log one or more defect NC codes. Similarly, for each defect NC code that has been logged and displayed in NC Tree, you log a repair NC code.
Control of the nonconforming products disposition
Assignment of incident numbers to logged nonconformances
Calculation of defects with the standardized DPMO (defects per million opportunities) methodology as defined in the IPC-9261 standard for printed board assembly manufacturing
Display of real-time schematics in the Visual Test and Repair POD with integration to nonconformance plug-ins
The figure below illustrates the primary flow of user actions when using Log NC to support the testing / inspection, analysis and repair of a PCA board or a product assembly:
