Difference between revisions of "SOP-42Q-MES0042 Data Collector"

From 42Q
Jump to navigation Jump to search
Line 493: Line 493:
 
<br/> 2. After viewing, select '''Close '''to exit.
 
<br/> 2. After viewing, select '''Close '''to exit.
  
== <span class="mw-headline" id="Document_Revision_History">Document Revision History</span> ==
 
  
{| border="2" cellpadding="4" cellspacing="0" width="100%"
+
= <span class="mw-headline" id="Document_Revision_History"><span class="mw-headline" id="Document_Revision_History"><span class="mw-headline" id="Document_Revision_History">Document Revision History</span></span></span> =
 +
 
 +
{| border="1" class="wikitable"
 +
|-
 +
! style="text-align: center; background-color: rgb(0, 168, 168);" | Date
 +
! style="text-align: center; background-color: rgb(0, 168, 168); width: 92px;" | Author
 +
! style="text-align: center; background-color: rgb(0, 168, 168); width: 94px;" | Title
 +
! style="text-align: center; background-color: rgb(0, 168, 168); width: 31px;" | Version
 +
! style="text-align: center; background-color: rgb(0, 168, 168);" | Change Reference
 +
! style="text-align: center; background-color: rgb(0, 168, 168);" | Approved by
 +
|-
 +
| 03/19/14
 +
| style="width: 92px;" | Ashley Martin
 +
| style="width: 94px;" | Technical Writer
 +
| style="width: 31px;" | v 1.0
 +
| This is the first revision of the Data Collector User Guide.
 +
| &nbsp;
 +
|-
 +
| 04/12/14
 +
| style="width: 92px;" | Ashley Martin
 +
| style="width: 94px;" | Technical Writer
 +
| style="width: 31px;" | v 1.0
 +
| Edited and content added.
 +
| &nbsp;
 +
|-
 +
| 04/27/16
 +
| style="width: 92px;" | Dane Parker
 +
| style="width: 94px;" | Technical Writer
 +
| style="width: 31px;" | v 1.0
 +
| Formatted to 42Q.
 +
| &nbsp;
 +
|-
 +
| 02/20/16
 +
| style="width: 92px;" | Elaine Fonaro&nbsp;
 +
| style="width: 94px;" | Technical Writer
 +
| style="width: 31px;" | v 1.
 +
| Images Updated.
 +
| &nbsp;
 
|-
 
|-
| align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Date</font>
+
| 03/27/18
| align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Author</font>
+
| style="width: 92px;" | Elaine Fonaro
| align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Title</font>
+
| style="width: 94px;" | Technical Writer
| align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Version</font>
+
| style="width: 31px;" | v 1.0
| align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Change Reference</font>
+
| Applied new Template for format.
 +
| &nbsp;
 
|-
 
|-
| 03/19/2014
+
| 01/25/21
| Ashley Martin
+
| style="width: 92px;" | Marisol Vargas
| Technical Writer
+
| style="width: 94px;" | Technical Writer
| A
+
| style="width: 31px;" | v 1.0
| This is the first revision of Data Collector User Guide
+
| Update Document Revision History to meet the standard and corrected some typos.
 +
| &nbsp;
 
|}
 
|}

Revision as of 18:22, 26 January 2021

42Q Home > Production > Data Collector 

RTENOTITLE

 

Production
Data Collector
Version MES15 Portal 1.0
Work Instruction

 

This Work Instruction is 42Q's corporate standard.
 This document is under revision control. The latest revision is located on Intranet.
 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 MES 15 Portal 1.0 and all subsequent releases and modifications until otherwise indicated in new revisions.

 

Data Collector

Data Collector is a tool implemented on the shop floor that displays uploaded work instruction documents, deviations, CAD views of devices, and recorded and repaired defect codes, all based on unit serial scanning. Data Collector also allows the user to view the device's location in production. The time a serial number is scanned, where the device came from, its current position, as well as where the device will pass to will display.

 

System Requirements

Hardware Requirements (minimum)

  • Server requirement
  • with VM ESXi
  • Preferably 64-bit machine
  • Core Duo processor 2GB RAM
  • 80GB hard disk space


Client requirement

  • Core Duo processor
  • 1GB RAM
  • 20GB hard disk space
  • Minimum resolution at 1024x768 (17"/19" monitor is recommended)
  • Support smart terminals (Linux LTSP, WYSE, and Extension terminals)

 

Software Requirements

Windows XP or Ubuntu
Chrome 12.0 or newer (Recommended browser)
Firefox 7.0 or newer, with Adobe Reader disabled (if it's installed), and the extension pdf.js installed.
MES deployed with at least 1 SFDC Host PC

 

Prerequisite Configurations:

  • Configuring User in Employee Validation portlet;
  • Configuring Station ID in Device Maintenance portlet;
  • Uploading agile/local (deviation) documents.

 

1. To access the Data Collector page, navigate to Production '>'Data Collector.

 

Figure 1: Data Collector Main Page

RTENOTITLE


Station ID- Station ID is a label used to define device IDs used at a particular workstation. Its purpose is to group and limit the available device IDs for any defined workstation.  By limiting the available device numbers at a workstation, eliminates confusion to the operator, and prevents issues where two users might be trying to access the same device at the same time.

Note: If this is the users first time accessing the portlet, a window will display asking for a Station ID. The user must enter a valid Station ID that has been activated in Device Maintenance and select OK to continue.


Note: If the login Station ID is changed or de-activated under Device Maintenance, this window will pop up again even if it is not the users first time accessing the portlet.

If this is not the users first time accessing the page, when Data Collector is selected, the DC Emulator screen will be displayed.

Employee Validation

Employee Validation controls the ability of a user to scan a part number (serial) at a particular process. Also configured in Employee Validation are certificates of inspection. If a certificate has not been defined for a process, then a user can scan.  However, a certificate and class must be configured for a process in order to control scanning at that process. EV data will only be displayed if the selected device number has a controlled process associated with it. If a certificate is defined for a specific serial at that process, then data for that part number will be displayed.

Located at the top of the Data Collector main screen is an EV Details information box. This expandable section lists the Employee Number, Employee Validation Certificate, and Expiration Date if defined.

 

Figure 2: EV Details

02 Data Collector EV Details.png

 

  • Employee Number: Displays the Employee Number of the user that is logged into the system.
  • EV Cert: The certificate tied to the scanned serial.
  • Exp Date: The expiration date of the scanned serial.

Note: If a serial is scanned on a non-configured EV, there is no certificate to find, therefore, no information will display.

Production Scanning

The main Data Collector screen contains various items that are pertinent to the device scanning.

 

Figure 3: Serial Scanning

03 Data Collector Unit ID.png

 

  • Unit ID: This is a list of all configured, active Unit IDs for a defined Station ID. Unit ID = Shop Floor ID + Device ID + Description, which requires pre-configurations in Device Maintenance. Select one from the drop-down list.

 

Note: Only select the Unit ID that applies to the job function.

 

  • Scan Log (black area): This is a read-only field displaying SFDC scanning messages, including both user inputs and system prompts.
  • Data Input (blue area): Scan or manually input text into this field.

 

Note: The Input Data field provides visual feedback for the scanned serial by displaying the following colors:

 

  • Green= Pass
  • Yellow= Error
  • Red= Fail
  • Black= No Error

 

Figure 4: Serial Information

04 Data Collector Serial Information.png

 

 

  • S/N: This is a read-only field displaying the currently scanned S/N.
  • P/N: This is a read-only field displaying the Part Number for the currently scanned S/N.
  • Rev: This is a read-only field displaying the current revision for the scanned S/N.
  • S/O: This is a read-only field displaying the shop order for the scanned S/N.

 

Figure 5: Process Flow

05 Data Collector Process Flow.png

 

  • From: The Process name from which the scanned S/N came from.
  • Current: The Process name in which the S/N is currently scanned.
  • Pass: The Process name to which the scanned S/N will pass to.

 

The Standard Tab contains the following functions to aid in the scanning and defect recording processes:

  • RTENOTITLE END- Terminates the current transaction and moves the unit to the next Pass/Fail Location.
  • RTENOTITLE YES- Sent to SFDC as a response to yes/no prompts.
  • RTENOTITLE MENU- Returns the user to the Menu Selection Prompt.
  • RTENOTITLE RELEASE- Releases a scanned unit at its station. The unit remains at this station until it is passed, failed, or moved.
  • RTENOTITLE NO- Sent to SFDC as a response to yes/no prompts.
  • RTENOTITLE NEXT- Skips adding of the prompted attribute or component and proceeds to the next one or goes on to the Menu Selection Prompt.
  • RTENOTITLE RESET- Exits the current transaction and returns back to Employee prompt without passing the unit to the next station. This will not back out any transactions already processed, such as components added or defects recorded.
  • RTENOTITLE N/A- Sent to SFDC as a response to yes/no prompts.
  • RTENOTITLE LOGOUT- Logs the user out of the current station.
  • RTENOTITLE Record Defect- Allows the user to record defects against the serial number.
  • RTENOTITLE Repair Defect- This allows the user to repair defects recorded against the serial number.
  • RTENOTITLE Unit Defects- Lists all recorded and repaired defects for the serial number. 
  • RTENOTITLE Top Defects- Lists the top five defects for the serial number.
  • RTENOTITLE Repair Notes- This allows the user to view, add, edit, or delete repair notes attached to repaired defect codes.
  • RTENOTITLE Measurement- Displays parametric data captured via Measurement.
  • RTENOTITLE Unit History- Displays the complete history of a particular serial number.
  • RTENOTITLE DTC In-Use- Frees up the device by logging out the previous user if that user forgot to logout from the device.

 

Serial Scanning

Upon a valid serial scanning, all documents that have been pre-configured for the scanned serial will be displayed in the Doc View panel.

  • Files will be grouped by the document type in tabs.
  • Select the document type tab to view documents.
  • CAD View is a tab tailored for the displaying of CAD files.

View Document

After a successful serial scan, any documents that are configured in Upload Agile Document/Upload Local Document will be displayed. If there are multiple documents, the default document of the default document type will always be displayed. The remaining documents will be placed in tabs for seamless navigation.

1. Select one Unit ID from the drop-down list labeled Select Unit ID.

2. Scan or input a serial number in theData Input field.

3. The default document will display in the display window.

 

Figure 6: Multiple Documents

06 Data Collector Multiple Documents.png

 

4. If there are multiple documents mapped to the scanned serial, the subsequent documents will be available to view from tabs located above the display window. To select a different document, choose which document to view by selecting the appropriate document tab.

CAD View

After a successful serial scan, the CAD view of the device will display in a tab located below the Data Input field. The CAD view is a computer-aided drawing of the device that is presented to the user for reference. Multiple layers are available to view through the navigational panel located to the right of the CAD.

Note: A CAD drawing must be configured at the scanning process to be displayed.

1. Select one Unit ID from the drop-down list labeled Select Unit ID.

2. Scan or input a serial number in theData Input field.

3. The CAD will be available in the tab panel. Select the CAD tab to view the device.

Note: The user can search for a component in a CAD by the reference designator. The reference designator that is specified as part of a recorded defect or repair is automatically displayed by using recorded or repaired switches.

 

Figure 7: CAD View

08 Data Collector CAD View.png

 

Record & Repair Defect

The record and repair defects functions allow for:

  • Advanced defect recording with PTS integration for component validation. An entered reference designator is validated against the BOM in PTS, in order to ensure that the component exists.
  • Advanced repair recording with PTS integration for validation of replacement component validation. Based upon the reference designator, the component is validated against the BOM in PTS. A Material Barcode field is included in order to validate the replacement component, ensuring the correct part number, manufacturer, valid data code, etc. are used.
  • Web service link to SFDC Measurement for displaying parametric records for an entered serial number. The Measurement server must be configured in MES Portal in order for records to be accessed. All available records found for the scanned serial number are displayed.
  • Top 5 defects and repairs based upon the part number of the scanned serial number. The display is based upon defects/repairs entered by the GUI in the Portal. Historical data from SFDC is not used. Chart display or list of defect/repair codes with description.
  • Tech Notes field for the recording of troubleshooting information.

Note: In order to work with this functionality, PTS integration must be properly configured. If PTS integration is not set up, the reference designators will not be validated.

Record Defect

The user can record defects against a serial number to document marginal attributes, monitor yields, and create reports containing current and historical yields.

1. To record a defect against a serial number, select one Unit ID from the drop-down list labeled Select Unit ID.

2. Scan or input a serial number in theData Input field.

3. Select the Record Defect icon from the Standard panel.

 

Figure 8: Record Defect

09 Data Collector Record Defect.png


The Record Defect form displays. Enter the following information:

  • The Defect Code field will display a drop-down list of available defect codes. The list filters to matching codes as characters are entered into the field. All available defect codes are listed unless a pre-defined list is configured in the Defect GUI module in MES.
  • The Reference Designator field is used to enter a reference designator of a failed component. This is the same as what would be entered when recording a defect at a standard data collector using the RCDFC or customized Record Defects command.
  • The Pin 1 / Pin 2 fields are used to enter the pin numbers of a defective component. The function is the same as what would be entered when recording a defect at a standard data collector using the RCDFC or customized Record Defects command.
  • The Quantity field is used to enter the total number of defects for the entered defect code. If a different defect is present, then a separate defect should be recorded using the correct defect code and information. The function is the same as what would be entered when recording a defect at a standard data collector using the RCDFC or customized Record Defects command.
  • The Side field is used to enter 0 or 1 for the side of the assembly. This is the same as the Surface field when recording a defect at a standard data collector using the RCDFC or customized Record Defects command.
  • The Repair check box is selected when the entered defect is being repaired at the same time the defect is being recorded. Selecting it will cause the pane to expand and all the fields found under the Repair tab are displayed.

4. Select Record to record the defect without repairing it. Select Reset to clear all fields. Select Close to exit.

Repair Defect

The user can repair recorded defects while recording them, or at a later date using the repair defect function.

Repair Defect While Recording:

1. To repair a defect while recording, select the Repair option located below the record defect form.

2. Enter the Material Barcode, Repair Code, and/or Repair Note and then select Record.

Note: The Repair Code is the only required field.

 

Figure 9: Repair Defect While Recording

10 Data Collector Repair Defect While Recording.png


Note: The user can access defects to repair after recorded by selecting the Repair Defect or Unit Defects icons.

Repair Defect Icon:

1. To repair a defect after recording, select the Repair Defect icon.

2. Enter the Reference Designator, if known. This will limit the Defect Code drop-down selections to the specific defect code to repair.

 

Figure 10: Reference Designator

11 Data Collector Reference Designator.png

 

3. If the reference designator is unknown, select the defect code from the list in the Defect Code drop-down box provided.

 

Figure 11: Defect Code Selection

12 Data Collector Defect Code.png


Note: The Defect Code field is mandatory but the Reference Designator field is not.

4. After selecting the defect to repair, enter the Material Barcode, Repair Code, and/or Repair Note and then select Record.

Note: The Repair Code is the only required field.

 

Figure 12: Repair Defect

13 Data Collector Repair Code.png

 


Unit Defects

The Unit Defects function lists all recorded and repaired defects. Recorded defects are displayed in red, repaired defects are displayed in green. The user can repair defects from the Unit Defects screen by double-clicking on any red defect listed.

1. To repair a defect from the Unit Defects screen, select the Unit Defects icon.

2. The unit defects screen displays all defects that have been recorded and repaired for that serial number. Select a red defect by double-clicking on it.

 

Figure 13: Unit Defects

14 Data Collector Unit Defects.png


3. The repair form displays with the reference designator and defect code pre-populated.

4. Select the repair code and enter the material barcode or Repair note if desired.

5. Select Record to repair the defect.

 

Figure 14: Repair Defect

15 Data Collector Repair Defect.png


The defect will now appear in green on the Unit Defects screen.

 

Figure 15: Repaired Defect

RTENOTITLE

 

After repairing all defects, to pass a serial number to the next location in the route, select END. If all actions have been correctly completed, the unit will pass to the next location, if not, a red box displays.

 

Figure 16: PASS to

17 Data Collector PASS to.png

 

Figure 17: FAIL to

18 Data Collector FAIL to.png

 

Top Defects

The Top Defects function lists the top five defects for the previous 30-day cycle for a particular part number.

1. To list the top five defects, select one Unit ID from the drop-down list labeled Select Unit ID.

2. Scan or input a serial number in theData Input field.

3. Select the Top Defects icon located in the standard panel.

4. The Top Defects form displays. The default view is a pie chart with data from the last 30 days.

 

Figure 18: Top Defects

19 Data Collector Top Defects.png


5. To view the defect code descriptions, select the box located above the pie chart.

 

Figure 19: Top 5 Defect Codes

20 Data Collector Top 5 Defect Codes.png

 

6. Select Close to exit after viewing.

Repair Notes

The Repair Notes function allows the user to view, add, edit, or delete repair notes attached to repaired defect codes.

1. To access Repair Notes, select one Unit ID from the drop-down list labeled Select Unit ID.

2. Scan or input a serial number in theData Input field.

3. Select the Repair Notes icon from the standard panel.

4. The Repair Notes search form displays.

 

Figure 20: Search Repair Notes

21 Data Collector Search Repair Notes.png

 

5. The Part Number is pre-populated according to the serial scan. If the reference designator is known, the user can enter it to limit the defect code selections.

6. Select a defect code from the Defect Code drop-down box.

7. Select the repair code associated with the defect code from the Repair Code drop-down box.

8. The user can set date parameters by entering a Start Date and anEnd Date in the fields provided to narrow the search field.

9. Select Show Delete Defect Note, if deletion is desired.

10. Select Search to display the repair notes for that particular defect code.

 

Figure 21: Repair Notes

22 Data Collector Repair Notes.png


The Create Date, Part Number, Reference Designator, Defect Code, Repair Code, and Badge Number fields are greyed out and unavailable to edit.

11. To edit the current repair note, type directly into the Note field.

12. To add a repair note select Add and enter repair note. Select Save to confirm.

13. To delete a repair note, select Delete located below the Note field.

Once multiple notes have been added, they are available to view in pages that can be navigated with arrows located below the Note field.

 

Figure 22: Multiple Notes

23 Data Collector Multiple Notes.png

 

Measurement

The Measurement icon displays parametric data captured via Measurement.

Note: SFDC must be configured to communicate with the measurement server in order to get parametric data.

(This function is currently under construction.)

Unit History

The Unit History icon displays the complete history of a particular serial number. Information displayed includes:

  • Date
  • Time
  • Employee
  • Station
  • Action (Create Record, PASS to, Defect Sequence, Repair Defect)
  • Data

1. To view the unit's history, select the Unit History icon.

 

Figure 23: Unit History

24 Data Collector Unit History.png


Figure 24: Navigate Unit History

25 Data Collector Navigate Unit History.png


2. After viewing, select Close to exit.


Document Revision History

Date Author Title Version Change Reference Approved by
03/19/14 Ashley Martin Technical Writer v 1.0 This is the first revision of the Data Collector User Guide.  
04/12/14 Ashley Martin Technical Writer v 1.0 Edited and content added.  
04/27/16 Dane Parker Technical Writer v 1.0 Formatted to 42Q.  
02/20/16 Elaine Fonaro  Technical Writer v 1. Images Updated.  
03/27/18 Elaine Fonaro Technical Writer v 1.0 Applied new Template for format.  
01/25/21 Marisol Vargas Technical Writer v 1.0 Update Document Revision History to meet the standard and corrected some typos.