Difference between revisions of "SOP-42Q-MES0009 Mfg Line Maintenance"
Line 7: | Line 7: | ||
| | ||
− | <center>'''Shop Floor Configuration'''</center> <center>'''MFG Line Maintenance'''</center> <center>'''Version MES15 | + | <center>'''Shop Floor Configuration'''</center> <center>'''MFG Line Maintenance'''</center> <center>'''Version MES15 1.0'''</center> <center> </center> <center>This SOP is 42Q's corporate standard.</center> <center> This document is under revision control. The latest revision is located on Intranet.</center> <center> Once printed it is an uncontrolled copy. All alterations to this work instruction require approval.</center> <center> Contact the IT Global Education and Training Department to submit suggested alterations and or updates.</center> |
− | |||
− | <center>This | ||
''This edition applies to MES15 Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.'' | ''This edition applies to MES15 Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.'' | ||
Line 16: | Line 14: | ||
| | ||
− | == <span class="mw-headline" id="Shop_Floor_Configuration">Shop Floor Configuration</span> == | + | == <span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration">Shop Floor Configuration</span></span> == |
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). | 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). | ||
Line 22: | Line 20: | ||
| | ||
− | == <span class="mw-headline" id="MFG_Line_Maintenance">MFG Line Maintenance</span> == | + | == <span class="mw-headline" id="MFG_Line_Maintenance"><span class="mw-headline" id="MFG_Line_Maintenance">MFG Line Maintenance</span></span> == |
<span id="docs-internal-guid-7498de52-b935-4fe2-66ec-ce3f3c983bdb">This portlet enables users to assign data collector (scanning) locations to a manufacturing line. Production data collected in the Manufacturing Line portlet is integrated with </span>[https://docs.google.com/document/d/1ecf9ekqFdTm7eVOxRX5YZaavkD7tIwBaLB4fqtB8pLA/edit 42Q Live] where critical line status is displayed on dashboard systems according to target yields. | <span id="docs-internal-guid-7498de52-b935-4fe2-66ec-ce3f3c983bdb">This portlet enables users to assign data collector (scanning) locations to a manufacturing line. Production data collected in the Manufacturing Line portlet is integrated with </span>[https://docs.google.com/document/d/1ecf9ekqFdTm7eVOxRX5YZaavkD7tIwBaLB4fqtB8pLA/edit 42Q Live] where critical line status is displayed on dashboard systems according to target yields. | ||
Line 36: | Line 34: | ||
| | ||
− | === <span class="mw-headline" id="Add_MFG_Lines">Add MFG Lines</span> === | + | === <span class="mw-headline" id="Add_MFG_Lines"><span class="mw-headline" id="Add_MFG_Lines">Add MFG Lines</span></span> === |
This portlet enables the user to add manufacturing line configurations to the database. | This portlet enables the user to add manufacturing line configurations to the database. | ||
Line 60: | Line 58: | ||
| | ||
− | <u>''' | + | <u>'''Note'''</u>: If the manufacturing line is WIP location line, the name must end with "WIP". |
− | <u>''' | + | <u>'''Note'''</u>: The Site ID can be changed if all Site ID references were updated in the SFDC Miscellaneous Configuration sub-module. If it is a WIP location line, it is not possible to create an escalation for this manufacturing line. |
− | '''Man Power''', '''Work Hour''', '''Min Sample Size''', fields are going to be enabled only after the user selects enters the mandatory MFG Line Form fields. The Man Power and Work Hour parameters are defined and will reflect in the SOMS reports. The Man Power parameter can be also defined on the fly as a report parameter.<br/> <br/> Also the report requires all Mfg Line | + | '''Man Power''', '''Work Hour''', '''Min Sample Size''', fields are going to be enabled only after the user selects enters the mandatory MFG Line Form fields. The Man Power and Work Hour parameters are defined and will reflect in the SOMS reports. The Man Power parameter can be also defined on the fly as a report parameter.<br/> <br/> Also, the report requires all Mfg Line setups including Data Collectors and Multi-Pass Location setup – the same used to set up SOMS Global Status reports. |
− | <u>''' | + | <u>'''Note'''</u>: The '''Man Power '''and '''Work Hour''' fields will be used in the MES Web reports. |
| | ||
Line 158: | Line 156: | ||
</ol> | </ol> | ||
− | <u>''' | + | <u>'''Note'''</u>: One Location can not be assigned for multi-lines. |
| | ||
Line 178: | Line 176: | ||
3. Select '''Ok''' to confirm, or select '''No''' to cancel the update action. | 3. Select '''Ok''' to confirm, or select '''No''' to cancel the update action. | ||
− | === <span class="mw-headline" id="Delete_Mfg_Lines">'''Delete Mfg Lines'''</span> === | + | === <span class="mw-headline" id="Delete_Mfg_Lines"><span class="mw-headline" id="Delete_Mfg_Lines">'''Delete Mfg Lines'''</span></span> === |
This portlet enables the user to delete an existing manufacturing line configuration. It is only possible to delete a manufacturing line if it does not have any Data Collector locations assigned to it. The user must first remove all assigned Data Collector locations from the manufacturing line configuration prior to deleting. | This portlet enables the user to delete an existing manufacturing line configuration. It is only possible to delete a manufacturing line if it does not have any Data Collector locations assigned to it. The user must first remove all assigned Data Collector locations from the manufacturing line configuration prior to deleting. | ||
Line 194: | Line 192: | ||
| | ||
− | === <span class="mw-headline" id="Print.2FExport_Filtered_MFG_Lines">'''Print/Export Filtered MFG Lines'''</span> === | + | === <span class="mw-headline" id="Print.2FExport_Filtered_MFG_Lines"><span class="mw-headline" id="Print.2FExport_Filtered_MFG_Lines">'''Print/Export Filtered MFG Lines'''</span></span> === |
This portlet enables the user to print/export filtered manufacturing lines. | This portlet enables the user to print/export filtered manufacturing lines. | ||
Line 212: | Line 210: | ||
| | ||
− | === <span class="mw-headline" id="Import_Escalation_Data">'''Import Escalation Data'''</span> === | + | === <span class="mw-headline" id="Import_Escalation_Data"><span class="mw-headline" id="Import_Escalation_Data">'''Import Escalation Data'''</span></span> === |
To import escalation data, | To import escalation data, | ||
Line 232: | Line 230: | ||
E43_HO,M200_ICT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30 | E43_HO,M200_ICT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30 | ||
− | '''<u> | + | '''<u>Note:</u> '''CSV file format is currently the same in use by plants to maintaining SOMS Escalation and map coordinates. |
| | ||
− | === <span class="mw-headline" id="Export_Escalation_Data">'''Export Escalation Data'''</span> === | + | === <span class="mw-headline" id="Export_Escalation_Data"><span class="mw-headline" id="Export_Escalation_Data">'''Export Escalation Data'''</span></span> === |
This portlet will export all escalation Data and save it in a ZIP file. | This portlet will export all escalation Data and save it in a ZIP file. | ||
Line 250: | Line 248: | ||
[[File:SOP-5-I-MDS0037-C RA1 MDS Mfg Line Maintenance 11.jpg|700px|SOP-5-I-MDS0037-C RA1 MDS Mfg Line Maintenance 11.jpg]] | [[File:SOP-5-I-MDS0037-C RA1 MDS Mfg Line Maintenance 11.jpg|700px|SOP-5-I-MDS0037-C RA1 MDS Mfg Line Maintenance 11.jpg]] | ||
− | = <span class="mw-headline" id="Appendix">Appendix</span> = | + | = <span class="mw-headline" id="Appendix"><span class="mw-headline" id="Appendix">Appendix</span></span> = |
'''Glossary''' | '''Glossary''' | ||
Line 284: | Line 282: | ||
| | ||
− | == Note == | + | == <span class="mw-headline" id="Note">Note</span> == |
Unit Status definitions Deprecated from Assembly Maintenance, Attribute Maintenance, MFG Hold, '''MFG Line''', Location Maintenance, Data Collector Maintenance they are used/assigned by the system for internal purposes. | Unit Status definitions Deprecated from Assembly Maintenance, Attribute Maintenance, MFG Hold, '''MFG Line''', Location Maintenance, Data Collector Maintenance they are used/assigned by the system for internal purposes. | ||
Line 305: | Line 303: | ||
| | ||
− | + | = <span class="mw-headline" id="Document_Revision_History"><span class="mw-headline" id="Document_Revision_History">Document Revision History</span></span> = | |
− | |||
− | = <span class="mw-headline" id="Document_Revision_History">Document Revision History</span> = | ||
{| border="1" class="wikitable" | {| border="1" class="wikitable" |
Revision as of 21:47, 26 May 2021
42Q Home > Shop Floor Control > Configuration > Mfg Line Maintenance
This edition applies to MES15 Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.
Contents
Shop Floor Configuration
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).
MFG Line Maintenance
This portlet enables users to assign data collector (scanning) locations to a manufacturing line. Production data collected in the Manufacturing Line portlet is integrated with 42Q Live where critical line status is displayed on dashboard systems according to target yields.
To access the Shop Floor Configuration, select Shop Floor Configuration on the menu. The main Shop Floor Configuration and sub-modules page are displayed:
Figure 1: MES MFG Line Maintenance
NOTE: A user only has access to the modules assigned to his/her profile.
Add MFG Lines
This portlet enables the user to add manufacturing line configurations to the database.
1. To add manufacturing lines, click the Add icon. The MFG Line Form is displayed.
Figure 2: MFG Line Form
To add or edit a manufacturing line,
1. Enter the Name and the Site ID in the respective fields. If it is a WIP Location Line, at least one location must be assigned. Otherwise, the Pixel X and the Pixel Y, and at least one scanner must be assigned.
The name must be created according to the following rules:
- 2 chars for Level or Modules (areas of interests) - Ex: L1; M2
- 2 chars to group Process Lines - Ex: L110; M250
- 1 char with "_" + Process Name + 1 char with "_" - Ex: L110_SMT_; M250_PTH_
- Line name - Ex: L110_SMT_Line1; M250_PTH_Line2.
- Project Name: The project name of the line, which is used here to distinguish between different projects with the same configuration. For example, if the project name is G18, the full manufacturing line name will be L110_SMT_Line1_G18; M250_PTH_Line2_G18.
Note: If the manufacturing line is WIP location line, the name must end with "WIP".
Note: The Site ID can be changed if all Site ID references were updated in the SFDC Miscellaneous Configuration sub-module. If it is a WIP location line, it is not possible to create an escalation for this manufacturing line.
Man Power, Work Hour, Min Sample Size, fields are going to be enabled only after the user selects enters the mandatory MFG Line Form fields. The Man Power and Work Hour parameters are defined and will reflect in the SOMS reports. The Man Power parameter can be also defined on the fly as a report parameter.
Also, the report requires all Mfg Line setups including Data Collectors and Multi-Pass Location setup – the same used to set up SOMS Global Status reports.
Note: The Man Power and Work Hour fields will be used in the MES Web reports.
Adding Escalation E-mails:
Add Escalation e-mails by
1. Entering an email address and selecting the Add icon. The escalation emails allow adding four levels of emails. Level 2, Level 3, and Level 4 tabs become available only when the information in the previous tab has an email address assigned to it.
Figure 3: Escalation
Using the available filters:
Scanners can be filtered by Shop Floor ID, Device Number, or Location Name using the Available Scanners field under the Associated Scanners tab:
- To filter by location, enter the Location name. (e.g., S076).
- To filter by Shop Floor ID, enter the shop floor ID (e.g., p99dcuat1).
- To filter by Device, enter the Device number (e.g., 76).
Removing Escalation E-mails:
- To remove a specific e-mail,
- Select the desired e-mail to be removed and select Remove Selected Item.
- To remove all e-mails,
- Select Remove All Items.
- Select Ok to save, or Cancel to cancel the operation.
Figure 4: Removing E-mail from Escalation
Adding or Removing scanners Tab:
Figure 5: Scanners Tab
- To add a scanner,
- Select it from Available Scanners in the drop-down list.
- To remove a specific scanner,
2. Select the desired scanner, select Remove Selected Item.
- To remove all scanners,
3. SelectRemove All Items.
4. Select Ok to save, or Cancel to cancel the operation.
Adding or Removing Locations:
The Locations Tab allows the setup of manufacturing lines by locations, instead of scanners.
Figure 6: Locations Tab
The assignment between the Location and Line is available on the Locations Tab.
- To add a location,
- Select it from Available Locations in the drop-down list.
- To remove a specific location,
- Select the desired location, select Remove Selected Item.
- To remove all locations,
- Select Remove All Items.
- Select Ok to save, or Cancel to cancel the operation.
Note: One Location can not be assigned for multi-lines.
Edit MFG Lines
This portlet enables the user to edit manufacturing line configurations. The steps for editing manufacturing lines are the same as those for adding. For further information, see the Add MFG Line section above.
To edit manufacturing lines,
1. Select the desired line and select Edit.
Figure 7: MFG Line List – Edit
2. Update the information in the MFG Line Form as needed.
3. Select Ok to confirm, or select No to cancel the update action.
Delete Mfg Lines
This portlet enables the user to delete an existing manufacturing line configuration. It is only possible to delete a manufacturing line if it does not have any Data Collector locations assigned to it. The user must first remove all assigned Data Collector locations from the manufacturing line configuration prior to deleting.
To delete a manufacturing line,
1. Select the desired manufacturing line, then select Delete. A confirmation message is displayed.
Figure8: MFG Line List - Delete
2. Select Yes to confirm, or No to cancel the action.
Print/Export Filtered MFG Lines
This portlet enables the user to print/export filtered manufacturing lines.
To print filtered MFG Lines,
1. Select Print/Export Filtered MFG Lines. A report is generated and the user is able to save the file or print it.
Figure 9: Print/Export Filtered MFG Line
Figure 10: Print/Export Filtered MFG Lines Result
Import Escalation Data
To import escalation data,
- select Import Escalation Data.
Figure 11: Import Escalation Data
2. Choose the .csv file and save it.
The .csv file has the following format:
SITE (String), LINE (Mfg Line name defined on precondition 2), x (Always empty), y (Always empty), x Pixels (Integer), y Pixels (Integer), Escalation 1, Escalation 2, Escalation 3 and Escalation 4 - see example below (figure 11):
E43_HO,M110_SMT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30
E43_HO,M200_ICT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30
Note: CSV file format is currently the same in use by plants to maintaining SOMS Escalation and map coordinates.
Export Escalation Data
This portlet will export all escalation Data and save it in a ZIP file.
1. Choose the local directory and select Save. The ZIP file with the .csv file will be saved locally.
Figure 12: Export Escalation Data
Figure 13: CSV File Generated.
Appendix
Glossary
Access Control
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, line, 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 FloorConfiguration
The rules used to define how Shop Floor collects data provides analysis, controls the processing and maintains unit histories
Site Minder
Universal login of 42Q
Username
The username is the SiteMinder username (or a partial string)
Note
Unit Status definitions Deprecated from Assembly Maintenance, Attribute Maintenance, MFG Hold, MFG Line, Location Maintenance, Data Collector Maintenance they are used/assigned by the system for internal purposes.
- In Container (36)
- In Transit (37)
- Temporary Ship Status (45)
- CRM Received (46)
- CRM Released (47)
- CRM RESERVED (48)
- CRM Finished (49)
- Killed (51)
- Killed RBF (52)
- Killed (56)
- Batch Old ID (63)
- Not DB of Record (70)
For more information please visit the 42Q-MES0160-C Unit Status Definition Work Instruction
Document Revision History
Date | Author | Title | Version | Change Reference | Approved by |
08/16/13 | Elaine Fonaro | Technical Writer | v 1.0 | This is the first revision of MES Mfg Line User ’s Guide | |
02/10/14 | Dane Parker | Technical Writer | v 1.0 | Grammar and images review | |
02/12/14 | Elaine Fonaro | Technical Writer | v 1.0 | Formatting | |
07/12/15 | Kala Burson | Technical Writer | v 1.0 | Linked TOC and Figures; corrected Figure references within the doc; basic grammatical corrections. | |
04/25/16 | Elaine Fonaro | Technical Writer | v 1.0 | Converted to 42Q | |
07/21/16 | Molly Kitts | Technical Writer | v 1.0 | Converted to Google Doc | |
04/03/17 | Martha Jordan | Technical Writer | v 1.0 | Rewrite SFDC introductory paragraph according to current 42Q functionality | Bob Moss |
04/11/18 | Elaine Fonaro | Technical Writer | v 1.0 | Applied new Template for format. Added information about Man Power, Work Hour, Min Sample Size fields. |
|
10/31/18 | Elaine Fonaro | Technical Writer | v 1.0 | Added a new functionality: Add/Delete Locations tab; Updated images 02, 03, 04, 05, 06 and 07. | |
08/11/20 | Elaine Fonaro | Technical Writer | v 1.0 | Updated occurrences of SFDC Configuration to Shop Floor Configuration and new images | |
12/17/20 | Marisol Vargas | Technical Writer | v 1.0 | Added deprecated statuses and portlets affected note | Juan Lopez |