You use this activity to create nonconformance clients.
A nonconformance client defines nonconformance options for operators who enter failure, defect, and repair information in the system. For more information, see NC Clients.
After you create a nonconformance client, you can use it in the POD (see Setting Up PODs for Nonconformance).
The following tables describe fields requiring explanation:
Field | Description |
---|---|
|
|
| Specifies which NC code fields to preload from the primary NC code when you log a secondary NC code:
|
| Specifies the disposition routing where the system sends the removed component |
| If entered, overrides the VTR model location value that is specified in the |
| If selected, the system automatically selects the default NC code in the |
| If selected, the |
| If selected, the system automatically dispositions the nonconformed SFC numbers or process lot based on the NC code configuration |
| If selected, the system automatically opens the |
| If selected, you can log primary NC codes |
| If selected, you can log an additional nonconformance against a failure, defect, or repair that has been logged and closed |
| If selected, prompts operators to log a secondary NC code when they log a primary NC code |
| If selected, a link to the |
| If selected, the |
Field | Description |
---|---|
|
|
| If selected, NC code descriptions appear in the |
Field | Description |
---|---|
| The nonconformance list created in The list controls the columns that appear and in which order they appear. |
| If selected, allows operators to change NC code states. |
Field | Description |
---|---|
| Defines the number of verified defect bars to display Note The value must be greater than 0. End of the note. |
| If selected, displays component and component description on the |