SOP-5-I-MES0006-C Defect Codes Maintenance

SFDC Configuration Defect Codes Version MDS Portal xx-x Work Instruction

This Work Instruction is Sanmina's corporate standard. This document is under revision control. The latest revision is located on SanminaNet. Once printed it is an uncontrolled copy. All alterations to this work instruction require approval. Contact the IT Global Education and Training Department to submit suggested alterations and or updates.

This edition applies to MDS Portal xx-x Application and all subsequent releases and modifications until otherwise indicated in new revisions.

Introduction

The Shop Floor Data Collection System (SFDC) communicates interactively with the Customer Order Processing System (COPS), and Statistical Process Control/Statistical Quality Control (SPC/SQC). The Manufacturing Data System (MDS) makes the communication between these systems possible.

SFDC provides real-time information used by SPC/SQC and MESWeb to create quality control reports. The data configuration for SFDC PC is handled within the Manufacturing Data System (MDS), which is a complete factory automation system. The SFDC System uses barcode scanning, both manual and automated, to monitor and control a single product line or an entire plant. SFDC Configuration collects data, provides analysis, maintains unit histories, and controls product movement on the manufacturing floor.

The system provides Access Control between the modules of the application, including the functionalities of each screen. The current version has an SFDC Configuration screen which provides access to all screens and its functionalities (view, add, edit, delete, print and generate output file), and a View-Only mode screen which only supports view, print and output to file; to support these screen modes, the MDS user or group of users have specific profiles, which provides specific access to MDS screens and functionalities.

Defect Codes Maintenance

Defect and Repair Codes are maintained through Defect Codes Maintenance from the SFDC Configuration Maintenance module.

List Defect Codes

To list Defect Codes, click on Defect Codes Maintenance in the SFDC Configuration menu.

The list of defect codes is displayed:

Figure 1: Defect Code List

The user is able to Add, Import, Print/Export, Edit and Delete Defect Codes.

• Defect Codes beginning with 'B' are displayed in blue. (Colors: feature to be developed)

These codes are known as Process Indicator defects. Process Indicator codes do NOT negatively affect process yield. A process indicator is only used to document a marginal attribute to indicate that it was noted, reviewed and found to be acceptable by the reviewer. Documentation of process indicators provides a measure of the frequency of marginal attributes.

• Defect Codes beginning with “K” are displayed in green.
• All other Defect Codes are displayed in black.

Note: All defect codes that begin with the letter B are called process indicators. They are unique in that they will not impact yield and they will not trigger a failure in SFDC. Any defect code that begins with K is a standard defect code, will result in a failure and impact the yield. B defect codes are used to indicate the current condition of a process, but not fail a unit because of it.

Add Defect Code

This functionality adds a defect code in the system.

1. To add a Defect Code, click the Add button.

Figure 2: Add Defect Code

The Defect Code Form is displayed:

Figure 3: Defect Code Form

1. Populate the mandatory fields (indicated in blue) to add a Defect Code. If the mandatory fields are not populated, an error message is displayed.

Defect Code: must be 4 unique characters

As a general rule:

• Defect Code format will begin with “B” for Process Indicators. For example: B174 Probe Mark

Process Indicator codes do NOT negatively affect process yield. A process indicator is only used to document a marginal attribute to indicate that it was noted, reviewed and found to be acceptable by the reviewer. Documentation of process indicators provides a measure of the frequency of marginal attributes.

• Defect Code format will begin with “K” for Symptom Codes. For example: K001 Boot Strap Failure. Symptom Codes define the symptom of the failure, not an actual defect. Symptom Code defects negatively affect process yield the same as all other defects.

• Defect Code format will begin with “R” for Repair Codes. For example: R001 Replaced Missing Components. Repair Codes are used to indicate specific repair activity for a recorded defect. For example, the Repair Code for the “Missing” defect code may be “Replaced Missing Components”. The four character Repair Code is used in place of “Yes” and/or “No” for defect repair activity.

Defect Description: Intuitive Description of the defect, limited to 30 characters

String 1 and String 2: Editable user-defined fields

Code Type: Defect Code, Repair Code or Symptom Code

Note: Align the Code Type with the Defect Code formatting discussed above.

1. Click Save to add Defect Code, or click Cancel to cancel.

The new Defect Code list is displayed in the defect list.

Edit Defect Code

This functionality enables the user to edit the available fields to update a Defect Code.

Note: Be aware that modifying Defect Codes will affect the historical defect information for any serial number with the defect recorded. Take care when editing to avoid changing the code description in such a way that it is completely different than the original. It is best to create a new Defect Code in this situation.

1. To Edit a defect code, select a defect and click the Edit button.

Figure 4: Defect code List - Edit

The Defect Code Form page is displayed:

Figure 5: Defect Code Form

1. Make desired updates in the Defect Code Form and click on Save to confirm the updates.

Delete Defect Code

This functionality deletes the selected Defect Code.

Note: It is not possible to delete Defect Codes that have activity recorded.

1. To delete a Defect Code, click the Delete button for desired defect code.

Figure 6: Defect code List - Delete

A confirmation message is displayed:

Figure 7: Confirmation Message

1. Click Yes to confirm the deletion action, or click No to cancel the action.

The Defect Code has been deleted from the database.

Import Defect Codes

This functionality imports Defect Codes into the database from a comma separated value (.csv) file.

1. Create a template file using notepad: sample file name 'template.csv'

1. Add the following column headers:

Defect Code,Defect Code Description,Code Type

1. Add the desired Defect Code records below the header row separated by comma:

For example:

D000,Defect Code Test,Defect Code

R001,Repair Code Test,Repair Code

K002,Symptom Code Test,Symptom Code

1. Save the file.

1. To import Defect Codes (.csv file created above), click the Import Defect Code button.

Figure 8: Import Defect Codes

The Import Defect Codes page is displayed:

Figure 9: Import Defect Codes page

File:Dco09.png

1. Enter path, or navigate, to desired .csv file to be imported and click Open.

1. Select either Skip when exists or Update when exists.

Skip when exists: Skips defect(s)s upon import if the Defect Code exists in the database.

Update existing defect: Updates defect(s) upon import if the Defect Code exists in the database.

The selected file will be imported.

Print/ Export Filtered Defect Codes

This functionality enables the user to print filtered Defect Codes. The report results include the Defect Code, Description, and Code Type.

1. To print filtered Defect Codes, click the Print/Export Filtered Defect Codes in the Task page.

Figure 10: Print Filtered Defect Codes

A report is generated and the user is able to save the file or print it.

Figure 11: Print/Export report result

Appendix A

COPS	Customer Order Processing System
FES	Factory Execution Systems
MDS	New Manufacturing Data System (Java technology)
GLAD	Global Administration
LDAP	Lightweight Directory Access Protocol
Mfg	Manufacturing
MES	Manufacturing Execution Systems
MDS	Manufacturing Data System
PRAC	Process Access
SFDC	Shop Data Floor Collection
SPC	Statistical Process Control
SQC	Statistical Quality Control

Appendix C

Glossary

Access Control

it is a module that will set the permissions for users and external customers of Sanmina

administrator

the System Administration has full access - all plants, all reports, all users.

component

A component is a specific piece of data that appears on a label, for example: bar code, part numbers, graphic images, line or text. Hence, label components are broken down into several different types: text, graphic images, MDS database values, or a combination of text and database values.

framework

In software development, a framework is a defined support structure in which another software project can be organized and developed. A framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project.

SFDC Configuration

The rules used to define how SFDC collects data, provides analysis, controls processing and maintains unit histories

Site Minder

Universal login of Sanmina

username

the username is the siteminder username (or a partial string)

Document Revision History

Date	Author	Title	Version	Change Reference
05/09/13	Elaine Fonaro	Technical Writer	v 1.0	This is the first revision of MDS User’s Guide