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

42Q Home > Shop Floor Control > Configuration > Defect Codes Maintenance
 

 

Shop Floor Configuration Defect codes Maintenance  Version MES 15.79 Revision G1        

 

Introduction

42Q’s powerful data collection system collects critical information from a plant’s shop floor, utilizing shop floor data collector, an intuitive tool developed by 42Q’s experienced manufacturing team. The aggregate information is stored in a cloud database, and available to MESWeb, where quality reports are generated. The 42Q system uses manual and automated barcode scanning to collect data for a product line or plant. Thus, 42Q plays an important role in maintaining unit histories and directing product movement on the manufacturing floor. The current version of 42Q includes configuration capabilities, which provide access to all sub-modules pages and their functionalities (view, add, edit, print/generate output files). 

 

 

Defect Codes Maintenance

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

This module allows defects found after a component is manufactured to be recorded. According to the number of records, the operator will be able to identify a defect to a specific component and reference that defect in the future.

 

To access Defect Codes Maintenance, navigate to Shop Floor Control > Configuration > Shop Floor Configuration > Defect Codes

Note: A user only has access to the modules assigned to his/her profile.

 

 

List Defect Codes

To list Defect Codes, click on Defect Codes Maintenance in the Shop Floor 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.
  • 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 Shop Floor. Any defect code that begins with K is a standard defect code, which will result in a failure and impact the yield. B defect codes are used to indicate the current condition of a process.

 

 

 

Add Defect Code

This functionality adds a defect code in the system.

To add a Defect Code, select the Add button. The Defect Code Form is displayed:

 

Figure 2: Add Defect Code

2. Populate the mandatory fields (indicated in red) to add a Defect Code. If the mandatory fields are not populated, an error message displays.

 

Defect Code: must be four unique characters

As a general rule:

• Defect Codes that begin with “B” represent 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 Codes that begin with “K” represent 'Symptom Codes'. For example: K001 BootStrap Failure. Symptom Codes define the symptom of the failure, not an actual defect. Symptom Code defects negatively affect the process yield the same as all other defects.

Defect Codes that begin with “R” represent 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.

 

3. Select Save to add Defect Code, or select Cancel to cancel. The new Defect Code list is now 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.

 

To edit a defect code, select a defect and click the Edit button. The Defect Code Form page is displayed.

 

Figure 3: Edit Defect Code

 

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

 

 

 

Delete Defect Code

This function deletes the selected Defect Code.

 

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

 

1. To delete a Defect Code, select the Delete button for desired defect code. A confirmation message is displayed. Select Yes to confirm the deletion action, or select No to cancel the action.

 

Figure 4: Delete Defect Code

 

 

Map Defect X Process

This functionality maps defect codes by processes. By mapping defect codes according to processes, the selection of defect codes, repair codes, and symptom codes can be controlled. If defect codes are not mapped to a process, all defect codes will be available to the user.

 

To access Map Defect Codes by Process, select the button located above the Defect Code list.

 

Figure 5: Map Defect X Process

 

The Defect X Process screen displays. In the panel on the left, all available defects are listed. In the panel on the right, all available processes are listed. The center columns are empty until defects and/or processes are selected and moved into them.

 

Figure 6: Available Defects/Processes

 

 

Panels, sorting and filtering

 

For each column in the panels, sorting and filtering options are available. Columns and Filters have sub-selections available.

 

Figure 7: Sorting/Filtering Options

 

Columns can be filtered by Code, Type, or Description depending on which column the user chooses to select.   Filters can be sorted according to the specific column. If under Code, enter a specific Code. If under Type, enter Defect, Repair, or Symptom. If under Description, enter the first characters of the description and all applicable options will display in the available panel.  

 

1. Once the list of desired defect codes is displayed, select the appropriate codes and move them into the Selected Defects panel. Defect codes can be moved by the double-clicking or dragging and dropping method. To remove a defect code from the selected panel, double-click or drag and drop it back into the available panel.
2. Continue to the Available Processes panel. Filter and move the available processes into the Selected Processes panel.

 

Figure 8: Map Defects

 

3. Select Save to map the selected defects to the selected processes. A confirmation will prompt. Select Yes to confirm or No to cancel.
4. Select Clear to remove all defects and processes from the selected panels. 
5. Once mappings are saved, a message will display confirming their creation.

Located at the bottom of the Map Defect X Process page is a panel labeled Defect Control By Process Mapping that displays the mapped defect codes. Once mapping has been completed, the selected defect codes and processes will be available to edit or delete from this panel.

 

Figure 9: Defect Control by Process Map

 

Located in this panel are two tabs titled Defects and Processes. The Defects tab lists the selected defects for the selected process/processes. The Processes tab lists the selected processes that contain the selected defects.    In either tab, the user can select a Defect code or Process and edit or delete it.   

 

1. To edit created mapping, select a specific defect or process, and then select Edit.
2. The defects and processes attached to the selection will appear in the Selected Defects and Selected Processes panels. The user can move either the defects or processes from these panels by double-clicking or dragging and dropping back into the available panels. 

 

Figure 10: Edit Map

 

3. To delete a created mapping, select either a defect code or process and then select Delete.
4. A confirmation will prompt. Select Yes to confirm or No to cancel.

 

Figure 11: Delete Map

 

Note: Once defect codes have been mapped to the appropriate processes, the user must install the updates using theDownloads and Services portlet located under Administration in the SFDC Administrator heading.

Mark as Enabled/Disabled

With the functionality, the user can mark single or multiple defect codes as enabled or disabled. If a defect code is enabled, it can be mapped to a process. If a defect code is disabled, it will no longer be available to be mapped to any processes. The user may need to disable a defect code without deleting it if it still exists in certain processes.

 

1. To disable defect codes, select the appropriate defect codes, and then select More.

2. Select Mark as Disabled.

 

Figure 12: Disable Defect Codes

 

The following screen will display:

 

Figure 13: Disabled Defect Codes

 

3. To enable defect codes, select the appropriate defect codes (now in red), and then select More.

4. Select Mark as Enabled.

 

Figure 14: Enable Defect Codes

 

The following screen will be display:

 

Figure 15: Enabled Defect Codes

 

 

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 filename template.csv.

2. Add the following column headers:

Defect Code, Defect Code Description, Code Type

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

For example:

D000, Defect Code Test, Defect Code

R001, Repair Code Test, Repair Code

K002, Symptom Code Test, Symptom Code

4. Save the file.

5. To import Defect Codes (.csv file created above), select the Import Defect Code button. This displays the import Defect Codes pop-up.

 

Figure 21: Import Defect Codes

Import Defect Codes

 

6. Enter the path or navigate to desired .csv file to be imported and select Open.

7. Select either Skip existing defect (if applicable) or Update existing defect (if applicable).

Skip existing defect: Skips defect(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 is imported.

Print/ Export Filtered Defect Codes

This portlet 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. A report is generated and the user is able to save the file or print it.

 

Figure 22: Print Filtered Defect Codes

Print Filtered Defect Codes

 

Figure 23: Print/Export Report Result

RTENOTITLE

 

Additional Operation And Disable Additional Operation Flex Fields Configuration

To use the additional operation feature, users have to configure the additional_operation flex field under defect code form.

 

Additional Operation Configuration

To use the additional operation, follow the next step list:

1. Access the Defect Codes module.
2. In the Defect Code field, enter the Defect Code.
3. Click on the Filter button to search the Defect Code.

 

Figure 24: Search Defect Code

24 Defect Codes Search Defect Code.png

4. Select the Defect Code (e.g. CXAC).
5. Click the Edit button.

 

Figure 25: Edit Defect Code

25 Defect Codes Edit Defect Code.png

6. Select the Flex Field Form tab.
7. In the additional_operation field, enter the value (the value can be any Conduit command).
8. Click on the Save button to save changes.

 

Figure 26: Flex Field Form Setup

26 Defect Codes Flex Field Form Setup.png  

Note: It can only be added one Conduit command in the additional_operation field.

 

Disable Additional Operation Configuration

The disable_additional_op_param_ovr functionality will help the user to replicate automatically the data required for the duplicated fields between the commands on additional operation configured.

The following is an example using the RepairDefect command in the additional operation.

1. Access the Defect Codes module.
2. In the Defect Code field, enter the Defect Code.
3. Click on the Filter button to search the Defect Code.

 

Figure 27: Search Defect Code (RepairDefect)

27 Defect Codes Search Defect Code (RepairDefect).png

 

4. Select the Defect Code (e.g. CXAC).
5. Click the Edit button.

 

Figure 28: Edit Defect Code (RepairDefect)

28 Defect Codes Edit Defect Code (RepairDefect).png

 

6. Select the Flex Field Form tab.
7. In the additional_operation field, enter the value, the value is the Conduit command RepairDefect.
8. In the disable_additional_op_param_ovr field, enter the value true or yes, in order to enable it
9. Click on the Save button to save changes

 

Figure 29: Flex Field Form Setup

29 Defect Codes Flex Field Form Setup.png

 

Appendix A

Glossary

Access Control

It is a module that will set the permissions for users and external customers of 42Q

Administrator

The System Administrator 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, lines, or text. Hence, label components are broken down into several different types: text, graphic images, MES 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.

Shop Floor Configuration

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

SiteMinder

Universal login of 42Q

Username

The username is the SiteMinder username (or a partial string)

---