Difference between revisions of "Configuration"

From 42Q
Jump to navigation Jump to search
 
(377 intermediate revisions by 10 users not shown)
Line 1: Line 1:
== SFDC Configuration ==
 
1. To access the SFDC Configuration module, click on''' SFDC Configuration '''in the main MDS Modules window.
 
  
'''Figure 1: MDS Client Modules – SFDC Configuration Maintenance'''
+
<small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Shop_Floor_Control|Shop Floor Control]] > Configuration</small><br/> &nbsp;
  
[[File:sfdc01.png]]
+
== <span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration">Shop Floor&nbsp;Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
'''GENERAL NOTES''':
+
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).<br/> &nbsp;
a)A user only has access to the modules assigned to his/her profile. Profile permissions are granted in the MDS PRAC (Program Access Control) Module by the Program Admin user.  
 
  
b)Any/all reports printed from jMDS modules will print to the default printer for the workstation.
 
  
2. The SFDC Configuration main window is displayed.
 
  
'''Figure 2: SFDC Configuration Modules'''
+
== <span class="mw-headline" id="Kit_Verify_Layout"><span class="mw-headline" id="Kit_Verify_Layout"><font size="4">Kit Verify Layout</font></span></span> ==
  
[[File:sfdc02.png]]
+
{| cellpadding="10" cellspacing="0" style="font-size: 13px; border-style: solid; border-color: blue; border-width: 2px; width: 924px;"
 +
|-
 +
| style="width: 894px;" |
 +
[[SOP-42Q-MES0078_Kit_Verify_Layout|'''42Q-MES0078 Kit Verify Layout&nbsp;''']]
  
 +
The Kit Verify Layout module allows users to validate all components in a kit and provides a visual layout mapping to aid in component placement.
  
This is the main SFDC Configuration Module window.
+
|}
  
== Kit Verify Configuration  ==
+
&nbsp;
  
The Kit Verify consolidates or validates all of component that we have in a “Kit” that warehouse give to the floor versus the shop order, in order to know if we have missing component in the Kit.
+
== <span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multi-level_Containerization_Configuration"><span class="mw-headline" id="Multilevel_Containerization_Configuration"><span class="mw-headline" id="Multilevel_Containerization_Configuration"><span class="mw-headline" id="Multilevel_Containerization_Configuration"><span class="mw-headline" id="Multilevel_Containerization_Configuration"><span class="mw-headline" id="Multilevel_Containerization_Configuration"><span style="font-size:large;"><span class="mw-headline" id="Multilevel_Containerization_Configuration"><span class="mw-headline" id="Multilevel_Containerization_Configuration">Multi-level Containerization Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
This module is integrated to MDS Client Application and will be available to all Sanmina's Plants.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0018-C_RA1_Multi-Level_Containerization_Configuration|42Q-MES0018 Multi-Level Containerization Configuration]]'''
 +
The Multilevel Containerization Configuration module described here is used for registering and storing serial numbers placed in a container, box, or packaging that will be sent to customers at the end of production.
  
<br>
+
|}
  
=== Layout Configuration  ===
+
&nbsp;
  
The function of this interface is to allow the user to '''Add''', '''Copy''' or '''Edit '''an assembly layout in the Kit Verify MDS Database.
+
== <span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation"><span style="font-size:large;"><span class="mw-headline" id="Employee_Validation"><span class="mw-headline" id="Employee_Validation">Employee Validation</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
<br> '''Note 1''': If Oracle does not send the reference Designator information to MDS the system will allow entering it manually.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0019-C_RA1_Employee_Validation|42Q-MES0019 Employee Validation]]'''  
 +
The module is responsible for creating training that the operator should complete working in certain manufacturing processes. All operator control (registration and maintenance of information) and required training and certificates for the operator's work on the shop floor (especially in medical locations) will be administered by this feature.
  
To access the Layout functionality, click on '''Layout Configuration '''at Tasks panel.
+
|}
  
<br> '''Figure 4: Choose Layout Configuration'''
+
&nbsp;
  
[[Image:KV04.png]]
+
== <span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration"><span class="mw-headline" id="SQC_Configuration">SQC Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
<br> The Layout main window displays:  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0023-C_RA1_SQC_Configuration|42Q-MES0023 SQC Configuration]]'''
 +
Module developed for storing data imported from a manually entered spreadsheet. SQC Configuration then compares this data with real data collected by the SFDC / MES application. This module is important because it calculates/measures the required time to produce a unit (HPU - Hour Per Unit).
  
'''Figure 5: Layout Configuration Main Window'''
+
|}
  
[[Image:KV05.png|800px|KV05.png]]
+
&nbsp;
  
<br> This screen will display all available Layout Configurations by Part Number, Project and Model.
+
== <span class="mw-headline" id="Labor_Maintenance"><span class="mw-headline" id="Labor_Maintenance"><span class="mw-headline" id="Labor_Maintenance"><span class="mw-headline" id="Labor_Maintenance"><span class="mw-headline" id="Labor_Maintenance"><span class="mw-headline" id="Labor_Maintenance"><span class="mw-headline" id="Labor_Maintenance">Labor Maintenance&nbsp;</span></span></span></span></span></span></span> ==
  
<br>
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[42Q-MES0182-A_Labor_Maintenance|42Q-MES0182-A &nbsp;Labor Maintenance]]'''
 +
'''Labor Maintenance&nbsp;'''is an Administrative portlet, that allows to change and modify the time registered by the operators tracked in Production Workbench and OEE Workbench.&nbsp;
  
==== Layout Configuration List  ====
+
|}
  
This screen displays all Layouts available and the user can edit or use the copy function.
+
&nbsp;
  
<br> '''Figure 6: Layout Configuration Filter'''
+
== <span class="mw-headline" id="Algorithm_Maintenance"><span class="mw-headline" id="Algorithm_Maintenance"><span class="mw-headline" id="Algorithm_Maintenance"><span class="mw-headline" id="Algorithm_Maintenance"><span class="mw-headline" id="Algorithm_Maintenance"><span class="mw-headline" id="Algorithm_Maintenance"><span class="mw-headline" id="Algorithm_Maintenance"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool"><span style="font-size:large;"><span class="mw-headline" id="Algorithm_Tool"><span class="mw-headline" id="Algorithm_Tool">Algorithm Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
[[Image:KV06.png|800px|KV06.png]]  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-42Q-MES0021_Algorithm_Maintenance|42Q-MES0021 Algorithm&nbsp;]]'''[[SOP-42Q-MES0021_Algorithm_Maintenance|'''Maintenance&nbsp;''']]  
 +
The Algorithm Tool provides the ability to create and modify serial number algorithms. It adheres to the format used by customers and engineers when writing specifications for serial number algorithms, integrated with Shop Floor Configuration, and generates serial numbers (shop order and containerization modules) and MAC addresses.
  
<br>
+
|}
  
==== Adding a Mapping (Layout configuration)  ====
+
&nbsp;
  
To create a Control Config, the user must to click on'''Create Control Config''' on Tasks panel.
+
== <span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels"><span style="font-size:large;"><span class="mw-headline" id="MDS_Labels"><span class="mw-headline" id="MDS_Labels">MDS Labels</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
<br> '''Figure 7: Add Mapping from Tasks panel'''  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0022-C_RA1_MDS_Labels|42Q-MES0022 MDS Labels]]'''  
 +
This Web application gives plants the ability to create, update, print, and share labels without the need for IT resources. It enables plants to easily define and access various different data sources like MDS, and MESR, along with a variety of other database types. It allows users to map label fields to these data sources in order to create dynamic labels. It also enables plants to extract statistical information about the labels that are managed in MDS Labels as well as monitor the audit information.
  
[[Image:KV07.png]]
+
|}
  
<br> The Layout Configuration screen displays:
+
&nbsp;
  
<br> '''Figure 8: Layout Configuration screen '''
+
== <span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin"><span style="font-size:large;"><span class="mw-headline" id="CMMS_Admin"><span class="mw-headline" id="CMMS_Admin">CMMS Admin</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
[[Image:KV08.png|800px|KV08.png]]  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0073-C_CMMS_Admin|42Q-MES0073 CMMS Admin]]'''
 +
42Q’s CMMS (Computerized Maintenance Management&nbsp;System) tools are designed to manage a plant’s assets. The administration module of CMMS (CMMS Admin) is designed for administrators (manufacturing engineers) to perform pre-configuration tasks so that plant machinery and equipment are properly maintained. Within the CMMS Admin portal, plant administrators define groups responsible for repair and maintenance, set notification alerts, and add plants, departments, and projects to the CMMS system. There are seven sub-modules available to local system administrators.&nbsp;
  
<br> '''Note1''': at least one Ref. Designator must be defined and mapped.
+
|}
  
Fields that User can enter/select:
+
&nbsp;
  
#'''Part Number;'''
+
== <span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset"><span style="font-size:large;"><span class="mw-headline" id="CMMS_Asset"><span class="mw-headline" id="CMMS_Asset">CMMS Asset</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
#'''File'''
 
#'''Project;'''
 
#'''Model;'''
 
#'''Reference Designator;'''
 
#'''Browse to find the layout file;'''
 
  
Follow the steps below to define a layout for a part number:
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0074-C_CMMS_Asset|42Q-MES0074 CMMS Asset]]'''
 +
Within CMMS Asset, administrators and engineers configure maintenance details related to a plant's assets. There are 12 sub-modules available to local system administrators.&nbsp;
  
#Select the desired Part Number; inform the Project and the Model as needed.
+
|}
#Click on the “'''Browse'''” button to select the new assembly layout. The system will show the File Dialog window and the user can select the image. The system disables the button and the path text box and the image will appear in the layout box;
 
#On the '''Ref. Designator''' list, the user must to create as many Reference Designators as required which will then automatically appear as disabled;
 
#The user has to click in '''Square''' or'''Circle''' form Button and draw a Square or Rectangle in Layout;
 
#Click on the Add “+” button.
 
#At the same time a new row with the reference designator information will appear in the “UI control” box with the following variables:
 
  
'''Figure 9: Components Designator'''
+
&nbsp;
  
To view the Reference Designator Information, click on the View button in the Layout Configuration window.
+
== <span class="mw-headline" id="Tooling_Control"><span class="mw-headline" id="Tooling_Control"><span class="mw-headline" id="Tooling_Control"><span class="mw-headline" id="Tooling_Control"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span style="font-size:large;"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Mapping"><span class="mw-headline" id="Tooling_Control">Tooling Control</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
[[Image:KV09.png]]  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[42Q-MES0142-C_Tooling_Control#Tooling_Mapping|42Q-MES0142 Tooling Control]]'''
 +
CMMS Tooling Control is the sister companion to CMMS Asset, 42Q’s definitive solution for asset maintenance. Tooling Control manages machine tooling equipment such as jigs, stencils, and test fixtures, according to their usage (cycle/hit count) and/or expiration date. The Tooling Mapping module creates an association between the product’s Part Number (associated with the Shop Floor ID and configured in MES 101) and the Asset Type defined in CMMS Asset. This connection allows the system to identify tooling usage counts via scan activity on the Product’s Part Number. Tooling Mapping sends tooling requirements to conduit, 42Q’s Production Scanning portal.
  
a.X coordinate;
+
|}
  
b.Y coordinate;  
+
== <br/> <span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span style="font-size:large;"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration"><span class="mw-headline" id="OEE_Configuration">OEE Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
c.Width;  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[42Q-MES0136-C_OEE_Configuration|42Q-MES0136 OEE Configuration]]'''
 +
The OEE Configuration modules allow users to define the following: Shift, Plant Calendar, Work Center, Root Cause Category, and Root Cause. Users complete the following tasks within OEE Configuration: Map Tag IDs to Assets&nbsp;(Tag Mapping), Define&nbsp;Up/Down Thresholds&nbsp;for Asset Types, Import Tag Mapping, Import Up/Down Thresholds, SetTarget UPH&nbsp;for Mfg Line, Process Part Number, and&nbsp;Shop Order.
  
d.Height;
+
|}
  
<br>
+
&nbsp;
  
#To delete the component, click on '''Delete''' icon.
+
== <span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Target_Maintenance"><span class="mw-headline" id="Target_Maintenance">Target Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
#After adding all reference designators the user has to click on the “'''OK'''” button and the system will insert all these rows into the MDS Database;
 
  
==== Editing a Layout Configuration  ====
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0084-C_Target_Maintenance|42Q-MES0084 Target Maintenance]]'''
 +
Targets are meant to be used as a source of any custom data. This work instruction is intended to guide users on how to manage and maintain targets faster and more efficiently. It also helps any MES Application customization. This user guide will show how to create data, add columns (attributes), and define the data type.
  
'''Figure 10: Edit Layout configuration'''
+
|}
  
[[Image:KV10.png|800px|KV10.png]]
+
&nbsp;
  
To edit a Mapping, the user must to select a Mapping and click on Edit icon.
+
== <span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration"><span style="font-size:large;"><span class="mw-headline" id="MES-Fuji_Configuration"><span class="mw-headline" id="MES-Fuji_Configuration">MES-Fuji Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
The Layout Configuration window displays with the existing layout information.
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
|
 +
'''[[MES_Fuji_Configuration|42Q-MES0146&nbsp;MES Fuji Configuration]]'''
  
<br> '''Figure 11: Layout Configuration'''
+
Per manufacturing industry best practice, a typical production line in 42Q’s MES consists of an &nbsp;SFDC (Shop Floor Data Collector) station and a PTS (Parts Traceability System) workstation configured for advanced traceability.
  
[[Image:KV11.png]]
+
|}
  
Note that the following fields can not be updated:
+
&nbsp;
  
#'''Part Number'''
+
== <span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish"><span style="font-size:large;"><span class="mw-headline" id="Configuration_Publish"><span class="mw-headline" id="Configuration_Publish">Configuration Publish</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
#'''Layout'''
 
#'''Project'''
 
#'''Model.'''
 
  
The Ref Designator can be removed from the list or included in the list.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[42Q-MES0112-C_RA1_Configuration_Publish|42Q-MES0112 Configuration Publish]]'''
 +
42Q’s Configuration Publish portlet is used to publish configuration changes for Conduit. For example, when a Part x Route association is configured or a Route is changed, users can publish the configuration for use with Production Scanning. Configuration Publish has the ability to automatically publish these configurations, or users can manually publish them within the portlet.
  
To obsolete a configuration, check the '''Obsolete''' box.
+
|}
  
<br>
+
&nbsp;
  
==== Copying a Layout Configuration (mapping)  ====
+
== <span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline"><span class="mw-headline"><span class="mw-headline"><span class="mw-headline"><span style="font-size:large;"><span class="mw-headline"><span class="mw-headline">Command Register</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
This option allows the user to create a new layout based on a pre existing layout (this module allows the user to copy and modify an existing assembly layout).  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-42Q-MES0143-C_Command_Register|42Q-MES0143 Command Register]]'''
 +
The Command Register provides the users the ability to customize and manage Auto Commands, Macros, and Process Control that are available for a given shop floor ID.
  
Follow the steps bellow to copy a layout:
+
|}
  
<br>
+
&nbsp;
  
#The user must create a new relation between the project and the model;
+
== <span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration"><span style="font-size:large;"><span class="mw-headline" id="QCP_Configuration"><span class="mw-headline" id="QCP_Configuration">QCP Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
#Select the layout in the list and click the “'''Copy'''” button;
 
  
#The image will appear in the layout box, and all records will appear in the “UI control” grid;  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
#Select the part number that will have the layout chosen;  
+
|-
#In case the user wants to change any reference designator he/she has to select it on the assembly layout and the reference designator row that was selected will appear in the “UI control” grid.;
+
| '''[[SOP-42Q-MES0150-C_QCP_Configuration_Portlet|42Q-MES0150 QCP Configuration Portlet]]'''  
#Once the modification has been finished, the user has to click on'''OK''' button;
+
The QCP Configuration Portlet provides the users with administrator's&nbsp;profiles, the ability to create checklists with pre-configured questions for specific stations.
  
The system updates the information into the MDS database.
+
|}
  
=== Test Configuration  ===
+
&nbsp;
'''Figure 25: Test Configuration window'''
 
  
[[Image:KV25.png|800px|KV25.png]]
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Assembly_Maintenance"><span style="font-size: large;">Shop Floor Configuration - Assembly Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
<br> This screen shows all Test Configurations.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0002-C_RA1_Assembly_Maintenance|42Q-MES0002 Assembly Maintenance]]'''
 +
This Assembly Maintenance module described in this document defines the procedures for assembling a product, along with the steps for each component’s integration. When the user enters information into the workstation, the description of how to perform specific labor will display. This description is available on the scanner, located at the station display, and may also inform the user on the exact location of where the component should be placed in the part.
  
<br>
+
|}
  
=== Performing Searches  ===
+
&nbsp;
  
To perform searches, there are there are just one field available:  
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Attribute_Def_Maintenance">Shop Floor Configuration - Attribute Def Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
<br> Filters Fields:  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0003-C_RA1_Attribute_Def_Maintenance|42Q-MES0003 Attribute Def Maintenance]]'''
 +
The Attribute Definition Maintenance module described in this documentation creates attributes that are tied to specific products during the manufacturing process. It also creates the steps that should occur at the attribute check/validation.
  
#'''Part Number;'''
+
|}
#'''Test Configuration Name'''
 
#'''Top Level Assembly'''
 
#'''Location'''
 
  
Enter the information and click on '''Filter'''.
+
&nbsp;
  
To clear the filter fields, click on '''Clear'''.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Collector_Maintenance">Shop Floor Configuration - Data Collector Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
<br>
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0004-C_RA1_Data_Collector_Maintenance|42Q-MES0004 Data Collector Maintenance]]'''
 +
The Data Collector Maintenance module described here defines the equipment reading (data collector) that will be used at a particular workstation.
  
=== Adding/Editing Test Configuration;  ===
+
|}
  
See bellow the '''Add/Edit '''steps.
+
&nbsp;
  
<br> 1. To add a Test Config, the user must to click on '''Add Test Config''' on Tasks panel.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Data_Editor_Maintenance">Shop Floor Configuration - Data Editor Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
'''Figure 26: Create Test Configuration'''  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0005-C_RA1_Data_Editor_Maintenance|42Q-MES0005 Data Editor Maintenance]]'''  
 +
The Setup Data Editor is a text, tab-delimited mechanism used for defining various pieces for Shop Floor configuration. Various parts of configuration can be defined, but generally, it is used for the configuration that is text string-based and does not lend itself well to a table structure. Examples are defining scan macros, auto command lines, and serial input masking lines for product numbers.
  
[[Image:KV26.png]]
+
|}
  
<br> 2. To edit or delete a Test Config, the user must to select the config in Test Config List and click on Edit or Delete icon.
+
&nbsp;
  
3. Click on '''Create''' '''Test Configuration''' in the Tasks Panel. The Create Test Configuration window displays.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Defect_Codes_Maintenance">Shop Floor Configuration - Defect Codes Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
'''Figure 27: Test Configuration Details'''  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0006-C_RA1_Defect_Codes_Maintenance|42Q-MES0006 Defect Codes Maintenance]]'''  
 +
The Defect Codes Maintenance moduled described here allows for the recording of defects found after a component is manufactured. According to the number of records, the operator will be able to identify a defect for a specific component and reference that defect in the future.
  
[[Image:KV27.png]]
+
|}
  
<br> To add a test configuration, the user must to follow the following steps:
+
&nbsp;
  
<br> 1. To create or edit a test configuration it's required to inform the top level Part Number.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Location_Maintenance">Shop Floor Configuration - Location Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
2. To add a part number, a test configuration or a test configuration group to the test configuration, click on the "+" icon.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0007-C_RA1_Location_Maintenance|42Q-MES0007 Location Maintenance]]'''
 +
The Location Maintenance module described here is used to register workstations and define the specific process that should be available at each workstation.
  
3. The '''Test Configuration Items Selection''' popup displays.
+
|}
  
'''Figure 28: Test Config Items Selection'''
+
&nbsp;
  
[[Image:KV28.png]]
+
&nbsp;
  
<br> 4. The user must enter a search item (your criteria: Part Number only, a Test Configuration Group or a Test Configuration only) and click on Find.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Hold_Maintenance">Shop Floor Configuration - Mfg Hold Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
5. Double click on the result.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0008-C_Mfg_Hold_Maintenance|42Q-MES0008 Mfg Hold Maintenance]]'''
 +
The Manufacturing Hold Maintenance module described here allows the operator to place a particular component on hold, either for lack of material or if it requires an unavailable process. The component will bypass the process and continue on the production line.
  
6. Fill mandatory fields (part number and quantity) in "Test Configuration Unit Information".
+
|}
  
'''Figure 29: Test Configuration Details'''
+
&nbsp;
  
[[Image:KV29.png]]
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Mfg_Line_Maintenance">Shop Floor Configuration - Mfg Line Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
7. Click on '''Ok''' button.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0009-C_RA1_Mfg_Line_Maintenance|42Q-MES0009 Mfg Line Maintenance]]'''  
 +
The Manufacturing Line Maintenance module described here allows users to map a point on a production line where information must be collected, such as the error rate. This helps measure the efficiency of the manufacturing process by Data Collectors located at a workstation (Locations). If the rate is higher than acceptable, the system sends a message requesting action to alleviate the problem.
  
'''Note1''': Obsolete Part Numbers do not display. The Part Number chosen will display in "Configuration Hierarchy".
+
|}
  
The user can see the "Test Configuration Selection" window with "Test Configuration", "Part Number" and "Test Config Group"
+
&nbsp;
  
'''Note2''': It's possible to add more than one Test Configuration, Part Number or Test Config Group to create a Test Configuration.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Misc_Configuration_Maintenance">Shop Floor Configuration - Misc Configuration Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
8. The information is saved in the database.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0010-C_RA1_Misc_Configuration_Maintenance|42Q-MES0010 Misc Configuration Maintenance]]'''
 +
The Misc Configuration Maintenance module described here inserts the data that was created in the Shop Floor ID functionality into the configuration. This data is necessary because it indicates a shift in the schedules on which the lines will be working, and it also informs the system of data collection that will be used in the database at those times.
  
9. The "Test Configuration" window closes and the Test Configuration created is displayed.
+
|}
  
10. To delete a part number, a test configuration or a test configuration group from the control configuration, the user must select the item and click on the "-" icon.
+
&nbsp;
  
=== Part Process Control; ===
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Part_Maintenance">Shop Floor Configuration - Part Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
To manage Part Process Control, the user must to click on P'''art Process Control''' on Tasks panel.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-42Q-MES0011_Part_Number_Maintenance|42Q-MES0011 Part Maintenance]]'''  
 +
The Part Maintenance module described here allows you to create a code (part number) and description for a particular product/component produced.
  
<br> '''Figure 30: Selecting Part Process Control'''
+
|}
  
[[Image:KV30.png]]
+
&nbsp;
  
<br> The Part Process control Window displays.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Product_Route_Maintenance">Shop Floor Configuration - Product Route Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
<br> '''Figure 31: Part Process Control'''  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0012-C_RA1_Product_Route_Maintenance|42Q-MES0012 Product Route Maintenance]]'''  
 +
The Product Route Maintenance module described here can be used for enabling the creation of the path (route) the product should follow in the production line.
  
[[Image:KV31.png|800px|KV31.png]]
+
|}
  
<br> This screen displays all Part Process Control available.
+
&nbsp;
  
<br>  
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Record_Components_Maintenance">Shop Floor Configuration - Record Components Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
==== Editing or Deleting from Part Process Control List  ====
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0013-C_RA1_Record_Components_Maintenance|42Q-MES0013 Record Components Maintenance]]'''
 +
The Record Components Maintenance module described here notifies the process of a particular component that its serial number is connecting with the serial number of the final product.
  
'''Figure 32: Editing a configuration from Part Process Control List'''
+
|}
  
[[Image:KV32.png|800px|KV32.png]]
+
&nbsp;
  
<br> To Edit a Control Config, the user must to click on edit icon in the list.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Revision_Change_Maintenance">Shop Floor Configuration - Revision Change Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
The edit page displays:
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0014-C_RA1_Revision_Change_Maintenance|42Q-MES0014 Revision Change Maintenance]]'''
 +
The Revision Change Maintenance module described here is used to update the specification (revision) of a product. When the user needs to change any feature or component of a product, this feature is used to apply changes and the product is manufactured with the new specification (new revision).
  
<br> '''Figure 33: Part Process Control definition'''
+
|}
  
[[Image:KV33.png]]
+
&nbsp;
  
<br> To'''update''' a part process control config it is required that the user type a unique name, the config type (process or location) and the max passes.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Shop_Floor_ID_Maintenance">Shop Floor Configuration - Shop Floor ID Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
'''Note:''' All items of the control must be of the same type: process OR location.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0015-C_RA1_Shop_Floor_ID_Maintenance|42Q-MES0015 Shop Floor ID Maintenance]]'''  
 +
The Shop Floor ID Maintenance module described here is used to create a configuration that joins the SFDC with the database that will be used by MES applications. The configuration has the same name as the Data Collector system.
  
At least one process or one location is required; the part number list is optional information.
+
|}
  
To add a process or a location to the control config:
+
&nbsp;
  
1. Click on the "+" icon below Process/Location list.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration_-_Sampling_Plan_Configuration">Shop Floor Configuration - Sampling Plan Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
2. The Process popup displays:
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0016-C_RA1_Sampling_Plan_Configuration|42Q-MES0016 Sampling Plan Configuration]]'''
 +
This module registers the percentage of products that deviated from their respective routes and analyzes the data for quality.
  
'''Figure 34: Process Popup'''
+
|}
  
[[Image:KV34.png]]
+
&nbsp;
  
<br> 3. Execute the filer to select an available process.
+
== <span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span style="font-size:large;"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance"><span class="mw-headline" id="Shop_Floor_Configuration_-_Traveler_Maintenance">Shop Floor Configuration - Traveler Maintenance</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
4. Click on '''OK''' button.  
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0017-C_RA1_Traveler_Maintenance|42Q-MES0017 Traveler Maintenance]]'''  
 +
The Traveler Maintenance module described here is used for creating an information list that contains the components a product needs for assembly. It is used to track components that have been inserted in the product on the production line.
  
5. The selected process must display at the process list.
+
|}
  
To delete a process or a location from the control config, select the process or location and click on the "-" icon below Process/Location list.
+
&nbsp;
  
Click on '''Ok''' to confirm.
+
== <span class="mw-headline" id="Quick_Action_Configuration"><span class="mw-headline" id="Quick_Action_Configuration"><font size="4">Quick Action Configuration</font></span></span> ==
  
<br> To add a part number to the control config, the steps are the same to add process:
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| [[Quick_Action_Configuration|'''MES0188-A-Quick Action Configuration''']]
 +
Quick Action Configuration is a tool designed to allow authorized users with administrator or engineering access to trigger macros and commands with a simple click, to connect actions with equipment, by creating buttons or quick actions.
  
1. Click on the "+" icon below'''Part''' list.
+
|}
  
2. The part Popup displays:
+
&nbsp;
  
'''Figure 35: Part Number dialog'''
+
== <span class="mw-headline" id="Event_Link"><font size="4">Event Link</font></span> ==
  
[[Image:KV35.png]]
+
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| [[Event_Link|'''42Q-MES0189-A &nbsp;Event Link''']]
 +
<span style="font-size: 13px;">Event Link acts as a bridge between the quick action button and the equipment, making communication available and ensuring the button reflects real-time equipment status.</span>
  
<br> 3. Execute the filer to select an available part number.
+
|}
  
4. Click on '''OK''' button.
+
&nbsp;
 
 
The selected part must display at the process list.
 
 
 
<br> '''Figure 36: Deleting from Part Process Control List'''
 
 
 
[[Image:KV36.png|800px|KV36.png]]
 
 
 
<br> To delete a Control Config, select the control and click on '''Delete ''' icon in the main Part Process Control list window.
 
 
 
Click on '''Ok''' to confirm.
 
 
 
==== Creating a Control Configuration  ====
 
 
 
To create a Control Config, the user must to click on'''Create Control Config''' on Tasks panel.
 
 
 
<br> '''Figure 37: Create a Control Config'''
 
 
 
[[Image:KV37.png|800px|KV37.png]]
 
 
 
<br> The Part Process Control Definition displays:
 
 
 
<br> '''Figure 38: Part Process Control Definition'''
 
 
 
[[Image:KV38.png]]
 
 
 
To create or edit a part process control config it is required to the user informs:
 
 
 
<br>
 
 
 
#'''Name;'''
 
#'''Config Type and'''
 
#'''Max Passes.'''
 
 
 
'''Note:''' All items of the control must be of the same type: process OR location.
 
 
 
<br> At least one process or one location is required; the part number list is optional information.
 
 
 
<br> To add a process or a location to the control config:
 
 
 
<br> 1. Click on the "+" icon below Process/Location list.
 
 
 
2. The process Popup displays:
 
 
 
'''Figure 39: Process Popup'''
 
 
 
[[Image:KV39.png]]
 
 
 
<br> 3. Execute the filer to select an available process.
 
 
 
4. Click on '''OK''' button.
 
 
 
5. The selected process must display at the process list.
 
 
 
To delete a process or a location from the control config, select the process or location and click on the "-" icon below Process/Location list and click on '''Ok''' to confirm.
 
 
 
To add a part number to the control config, the steps are the same to add process:
 
 
 
<br> 1. Click on the "+" icon below Part list.
 
 
 
The part Popup displays:
 
 
 
'''Figure 40: Part Number'''
 
 
 
[[Image:KV40.png]]
 
 
 
2. Execute the filer to select an available part number. 3. Click on '''OK''' button. 4. The selected part must display at the process list.
 
 
 
To delete a part number from the control config, select the part number and click on the "-" icon below Part list.
 
 
 
<br> '''Figure 41: Deleting Control Config from Part Process Control List'''
 
 
 
[[Image:KV41.png|800px|KV41.png]]
 
 
 
<br> To delete a Control Config, select the control and click on '''Delete ''' icon in the main Part Process Control list window and click on '''Ok''' to confirm.
 
 
 
=== Group Test Configuration;  ===
 
 
 
To manage Groups Test Config, the user must to click on '''Group Test Configuration '''on Tasks panel.
 
 
 
<br> '''Figure 42: Test Configuration'''
 
 
 
[[Image:KV42.png]]
 
 
 
<br> To access the Group Test Config, click on Group Test Configuration in the Tasks panel.
 
 
 
<br> '''Figure 43: Group Test Configuration List Filter'''
 
 
 
[[Image:KV43.png|800px|KV43.png]]
 
 
 
<br>
 
 
 
==== Sorting Colum  ====
 
 
 
The application allows to sort all columns of the list (ascending or descending), including the multi-column sorting keeping the "control" key pressed.
 
 
 
<br>
 
 
 
==== Adding a Test Config Group  ====
 
 
 
'''Figure 44: Adding Test Config Group'''
 
 
 
[[Image:KV44.png|800px|KV44.png]]
 
 
 
<br> To add a Group, click on '''Add Test Config Group''' on Tasks panel.
 
 
 
The Test Config Group window displays:
 
 
 
<br> '''Figure 45: Adding Test Config Group'''
 
 
 
[[Image:KV45.png]]
 
 
 
<br> To create or edit a test config will be required to the user informs:
 
 
 
<br>
 
 
 
#'''Group Name;'''
 
 
 
To create or edit a test config group it will be required to the user to inform a unique group name.
 
 
 
All items of the group must be of the same type: test config OR part number.
 
 
 
To add a test config or a part number to the group:
 
 
 
<br> 1. Enter the new group name and click on the "+" icon.
 
 
 
2. The Test Config Items popup displays:
 
 
 
'''Figure 46: Config Items Popup'''
 
 
 
[[Image:KV46.png]]
 
 
 
<br> 3. Execute the filter to select an available Test Config or part number.
 
 
 
4. Click on '''OK''' button.
 
 
 
5. The selected test config or part number must display at the group name element list.
 
 
 
To delete a test config or a part number from the group, the user must to select the test config or the part number and click on the "-" icon.
 
 
 
<br> '''Figure 47: Deleting Group Elements'''
 
 
 
[[Image:KV47.png]]
 
 
 
<br> Click on '''Ok''' to confirm.
 
 
 
==== Editing a group name.  ====
 
 
 
'''Figure 48: Deleting Group Elements'''
 
 
 
[[Image:KV48.png|800px|KV48.png]]
 
 
 
<br> To edit a group, select the group and click on Edit icon.
 
 
 
The same window to create a group displays. The user is able to change the group name or add/delete part numbers/test groups clicking on “+” icon to add or “-” icon to delete.
 
 
 
<br> For more information, see the topic [#_Adding_a_Test 2.8.4.2 - Adding a Test Config Group].
 
 
 
<br>
 
 
 
==== Deleting a group name.  ====
 
 
 
'''Figure 49: Deleting Group Names'''
 
 
 
[[Image:KV49.png|800px|KV49.png]]
 
 
 
<br> To delete a Group, select the group and click on Delete icon.
 
 
 
Click on '''Ok''' to confirm.
 
 
 
<br>
 
 
 
=== Integration  ===
 
 
 
To integrate a Top Assembly, scan or type the Component Serial Number according to the requested Ref. Designator.
 
 
 
To integrate a Test Config, the user must to click on '''Integration''' on Tasks panel.
 
 
 
<br> '''Figure 50: Test Configuration - Integration'''
 
 
 
[[Image:KV50.png]]
 
 
 
<br>
 
 
 
==== Finding Top Assemblies to Integrate  ====
 
 
 
When the user clicks on "'''Integration'''" from Tasks panel, the screen to find and select the top assembly to integrate components is displayed.
 
 
 
<br> '''Figure 51: Select the Top Assembly'''
 
 
 
[[Image:KV51.png]]
 
 
 
<br> Follow the steps below:
 
 
 
#Go to Kit Verify  Test Configuration  Integration, leave the Serial Number field empty or enter a S/N and click on '''Filter'''.
 
 
 
'''Note''': Only top assembly serial numbers in status &gt;=20 which have a test configuration created for the main part number must be displayed. The paginator buttons (previous and next) are displayed and 10 serial numbers are displayed per page.
 
 
 
<br>
 
 
 
==== Showing Integration Information  ====
 
 
 
'''Figure 52: Integration Information'''
 
 
 
[[Image:KV52.png]]
 
 
 
<br> Follow the steps below:
 
 
 
#Go to Kit Verify  Test Configuration  Integration, fill the Serial Number field with the top assembly;
 
#Double click on top assembly;
 
#The test configuration tree view which was created for the main part number is displayed and beside that the components to integrate to the serial numbers are displayed;
 
#Click on Serial Number for the related part number, fill with one of the serial numbers created according to the pre condition 2 and press enter;
 
#The serial number is recorded to the part number and the application points to the next serial number to be filled;
 
#Repeat the step 3 for the remaining serial numbers and click '''OK'''<nowiki>;</nowiki>
 
#The message "Are you sure you want to create a new component integration?" is displayed.
 
 
 
=== Alert Distribution ===
 
To access the Alert Distribution functionality, from Tasks panel, click on '''Alert Distribution'''.
 
 
 
 
 
'''Figure 53: Shop Order List'''
 
 
 
[[File:KV53.png]]
 
 
 
 
 
The alert distribution list should be like a profile. We can select the user for each program and these users will receive an email alert base on xml template.
 
 
 
 
 
The Alert Distribution list displays:
 
 
 
 
 
'''Figure 54: Alert Distribution'''
 
 
 
[[File:KV54.png|800px]]
 
 
 
 
 
From this screen, the user is able to add, edit, copy or delete alerts distribution. See the next topics for more information.
 
 
 
 
 
==== Adding Alert Distribution ====
 
'''Figure 55: Adding Alert Distribution'''
 
 
 
[[File:KV55.png|800px]]
 
 
 
The Add Alert Distribution window displays:
 
 
 
 
 
'''Figure 56: Add Alert Distribution'''
 
 
 
[[File:KV56.png]]
 
 
 
 
 
To add an Alert Distribution, follow the steps bellow:
 
 
 
# In Task Panel click in "'''Add Alert Distribution"''' option;
 
# Fill the mandatory fields (Distribution Name and Receivers);
 
# Click in "'''Ok'''" button;
 
# Confirm the Alert Distribution creation.
 
 
 
The "Alert Distribution" window closes and the "Alert" is displayed with the recorded "Alert" in the table.
 
 
 
The user can search for receivers. Click on “+” to add or “-” to delete.
 
 
 
==== Editing Alert Distribution ====
 
'''Figure 57: Editing Alert Distribution.'''
 
 
 
[[File:KV57.png|800px]]
 
 
 
 
 
Follow the steps bellow to edit an alert distribution:
 
 
 
 
 
# On the Alert Distribution list, select an existing Alert;
 
# Click the Edit icon; The Alert Distribution screen displays. It is the same for Add Distribution alert.
 
# Change the mandatory fields;
 
# Click "'''OK'''" button
 
# Confirm the Edit.
 
 
 
==== Copying Alert Distribution ====
 
'''Figure 58: Copying Alert Distribution'''
 
 
 
[[File:KV58.png|800px]]
 
 
 
 
 
The copy feature allows the user to copy alert information. Follow the steps bellow:
 
 
 
 
 
# On the Alert Distribution List, select an existing Alert;
 
# Click the Copy Icon;
 
# Change the mandatory fields;
 
# Click "'''OK'''" button.
 
 
 
==== Deleting Alert Distribution ====
 
'''Figure 59: Deleting Alert Distribution'''
 
 
 
[[File:KV59.png|800px]]
 
 
 
 
 
Follow the steps bellow to delete an Alert:
 
 
 
 
 
# On the Alert Distribution List, select an existing Alert;
 
# Click the Delete icon;
 
# Click "'''OK'''" button.
 
# A confirmation box displays.
 
# The Alert is deleted.
 
 
 
== Multi-Level Container Configuration  ==
 
This chapter describes how the user manages the Multi-Level Containerization MDS Module. It details all functionalities and actions that can be performed by users.
 
 
 
 
 
'''GENERAL NOTES:'''
 
 
 
 
 
* Most error and informational messages are displayed in a dialog box. Click '''OK''' or press '''Enter '''to dismiss the dialog window. '''Yes''' or''' No''' buttons may also be provided to answer questions presented by the message dialog window.
 
* The user Profile defines what the user can access.
 
 
 
'''Figure 3: Multi-Level Container Configuration'''
 
 
 
[[File:MLC03.png|700px]]
 
 
 
The user is able to perform actions like create, print/export filtered results, edit, copy, delete, view or print/export containers configuration.
 
 
 
 
 
The next topics will describe all available Container Configuration functionalities.
 
 
 
=== Container List ===
 
The '''Container List''' displays all container levels and allows performing the following actions:
 
 
 
# '''Filter''' '''Data'''
 
# '''Edit a Container Configuration'''
 
# '''Copy a Container Configuration'''
 
# '''View a Container Configuration'''
 
# '''Delete a Container Configuration'''
 
# '''Print/Export details of a Container Configuration'''.
 
 
 
Note that it is possible to execute two actions from the Task Panel:
 
 
 
 
 
# '''Add a new Container Configuration'''
 
# '''Print/Export all Filtered Container Configurations'''
 
 
 
=== Filter Settings ===
 
To perform searches, there are four available fields:
 
 
 
'''Container Level''': Predefined container levels are: “99 LOT”, “100 BOX”, “110 SKID” and “120 PALLET”; levels 101-999 are Multi-Level Containers and are handled only by MDS Client.
 
 
 
'''Level Description:''' The default description for the level.
 
 
 
'''Part Number: '''A number which serves to uniquely identify a part (product).
 
 
 
'''Project ID:''' The project identification number.
 
 
 
 
 
Also, the user can select additional options from the Options section:
 
 
 
'''Active''' (All, No, Yes): NO implies inactive for containerization. Default=YES;
 
 
 
'''Shop Order controlled''' (All, No, Yes): YES allows only units from a single shop order to be containerized together. Default=NO;
 
 
 
'''Revision Controlled''' (All, No, Yes): YES means only one revision can be containerized together. Please correct and check the default value.
 
 
 
 
 
Enter the information or combination of information and click on '''Find'''.
 
 
 
 
 
'''Figure 4: Filter Settings'''
 
 
 
[[File:MLC04.png|700px]]
 
 
 
 
 
To clear the fields’ contents, click on '''Clear''' button to start a new filter.
 
 
 
=== Edit Container Configuration ===
 
To edit a container configuration, go to '''MDS Client > Multi-Level Containerization > Container Configuration> Container Configuration list''', select an existing Container Configuration and click on '''Edit''' Icon.
 
 
 
 
 
'''Figure 5: Multi-Level Container Configuration - Edit'''
 
 
 
[[File:MLC05.png]]
 
 
 
 
 
The Container Configuration Maintenance screen displays:
 
 
 
 
 
'''Figure 6: Container Configuration Maintenance - Edit'''
 
 
 
[[File:MLC06.png]]
 
 
 
 
 
All the container configuration information is updated according to the updates applied and the container configuration is displayed in the container configuration's list.
 
 
 
 
 
'''Container Level, Part Number '''and '''Project ID''' cannot be edited, as they are the keys of the record.
 
 
 
 
 
'''Note''': For more details about a field’s description, see the [#_5.1.2a_Create_Container Create Container Configuration] topic.
 
 
 
=== Copy Container Configuration ===
 
To copy Container Configuration definitions, go to '''Container Configuration> Container Configuration list''', select an existing Container Configuration and click on the '''Copy''' icon.
 
 
 
 
 
The Container Configuration Maintenance window is displayed:
 
 
 
 
 
'''Figure 7: Container Configuration Maintenance - Copy'''
 
 
 
[[File:MLC07.png]]
 
 
 
 
 
Change the necessary information and click on the "'''Ok'''" button. The new Container configuration created is displayed on Container Configuration List.
 
 
 
 
 
=== Delete Container Configuration ===
 
To delete a container configuration, go to '''Multi-Level Containerization > Container Configuration> Container Configuration list''', select an existing Container Configuration and click on '''Delete''' Icon.
 
 
 
 
 
'''Figure 8: Multi-Level Container Configuration - Delete'''
 
 
 
[[File:MLC08.png]]
 
 
 
 
 
A confirmation message displays. Click on '''Yes '''to confirm the deletion or '''No''' to cancel. The Container Configuration will be deleted from the containers list.
 
 
 
=== View Container Configuration ===
 
To view the container information, go to '''Multi-Level Containerization > Container Configuration> Container Configuration list''', select an existing Container Configuration and click on the '''view''' Icon.
 
 
 
The container configuration maintenance window displays:
 
 
 
 
 
'''Figure 9: View Container Configuration Window'''
 
 
 
[[File:MLC09.png]]
 
 
 
'''Note''': all the fields are read only.
 
 
 
=== Print/Export Container Configuration ===
 
1) To print/export containers, go to '''Multi-Level Containerization > Container Configuration> Container Configuration list''', select an existing Container Configuration and click on the '''Print/Export Container Configuration''' Icon.
 
 
 
A report is generated. In the viewer screen, click on "'''Save'''" or “'''Print'''” button to save or print the report result.
 
 
 
=== Container Task Panel ===
 
From the '''Task Panel''' the user is able to create a new container configuration and print/export all filtered container configuration created.
 
 
 
 
 
=== Create Container Configuration: Level 99 (LOT) /Level 100 (Container) ===
 
There are different configurations for Containers Level 99 (LOT) and level 100 (Container). See bellow the differences between them.
 
 
 
 
 
'''<nowiki>** Container Level = 99: </nowiki>Configuration '''
 
 
 
 
 
To create a container configuration, go to '''Multi-Level Containerization > Container Configuration > Task Panel '''and click on '''Add Container Configuration'''.
 
 
 
The Container Configuration Maintenance screen is displayed:
 
 
 
 
 
'''Figure 10: Container Configuration Maintenance'''
 
 
 
[[File:MLC010.png]]
 
 
 
 
 
Container Configuration fields description:
 
 
 
'''Container Level''': defines the container level (99 to 999) – default is Empty. For this topic, the level used is 99(LOT). The default Container Levels, 99 - LOT, 100 - CONTAINER, 110 - SKID and 120 - PALLET cannot be edited or deleted, it’s created automatically by the application.
 
 
 
 
 
'''SFDC Lot Rules:'''
 
 
 
* '''S/N Procedure: '''not used when Serial Mask is specified. The field can contain either (i) a predefined program filename or (ii) an algorithm number, if the algorithm was defined using the Algorithm Tool – default Empty;
 
* '''Lot Mask''': not used when Serial Algorithm Procedure is specified. Up to 30 characters in length. The mask of the serial number for the container or lot. Using a serial mask, container serialization schemes can be different per part number – default Empty;
 
 
 
To manage the container levels click on Manage icon:
 
 
 
'''Figure 11: Container configuration Maintenance'''
 
 
 
[[File:MLC011.png]]
 
 
 
The Manage Level screen is displayed:
 
 
 
 
 
'''Figure 12: Container Level Maintenance'''
 
 
 
[[File:MLC012.png]]
 
 
 
The user is able to '''Add''', '''Edit''' or '''Delete''' container levels.
 
 
 
==== Create a new container level ====
 
To add a container level, click on the '''Add''' icon in the bottom of the window. The '''Add Container Level''' window displays.
 
 
 
 
 
'''Figure 13: Container Level - Add'''
 
 
 
[[File:MLC013.png]]
 
 
 
Enter the "'''Container Level'''" with a value between 99 to 999 and the "'''Level Description'''" with a value that does not exist in the database. Click on '''OK''' to finish.
 
 
 
The new container level will be displayed in the containers level list and the user will be able to select it when creating/editing a container configuration.
 
 
 
 
 
==== Edit/delete a container level ====
 
'''Edit/delete container level''': (maintenance button) can be performed at any time except for a default value or a container definition that already exists for that level; otherwise, if there are no definitions, editing or deleting a container level is allowed. '''Type 99 (LOT) cannot be edited'''. Also, all types without a container configuration associated can be deleted. If a definition already exists, then the container level cannot be modified.
 
 
 
 
 
'''Figure 14: Container Level – Edit '''
 
 
 
[[File:MLC014.png]]
 
 
 
 
 
'''Figure 15: Container Level - Delete'''
 
 
 
[[File:MLC015.png]]
 
 
 
 
 
'''<nowiki>** Container Level = 100: </nowiki>'''SFDC Container Rules section
 
 
 
New configuration was added for level 100 and will run just in the MDS Client. Just configuration with algorithm type = Container will run in the SFDC.
 
 
 
 
 
It supports the following options:
 
 
 
* Revision Controlled;
 
* Shop Order Controlled;
 
* Auto Close;
 
* Dimensions (MDS Client only);
 
* Shipping Level
 
* Multi Part
 
* S/N Procedure
 
* Container Mask
 
 
 
'''General Rules:'''
 
 
 
After entering all mandatory fields, click on the "'''OK'''" button and confirm the configuration creation. The container configuration list is updated with the new container configuration, with the inserted data.
 
 
 
It is necessary to use the same "Level" for all records with the same "Description". For example, if you create a level 120 and say that the name is "Overpack Box", then any other record which is added later that has the description "Overpack Box" needs to be level 120.
 
 
 
'''Note''': The application cannot show obsolete part numbers for selection during the creation of a container configuration.
 
 
 
 
 
=== Create Multi-Level Configuration Containers: Type > 100 ===
 
To create a new Container Configuration, click on '''Add Container Configuration''' button in the task panel.
 
 
 
 
 
'''Figure 16: Add Container Configuration'''
 
 
 
[[File:MLC016.png|700px]]
 
 
 
 
 
The Container Configuration Maintenance window is displayed:
 
 
 
 
 
'''Figure 17: Multi-Level Container Configuration Maintenance'''
 
 
 
[[File:MLC017.png]]
 
 
 
 
 
The following fields are displayed just for containers >100: '''Container Level, Level Description, Part Number''', '''Project ID, Active, Capacity''', '''Label Program '''and''' Disable printing when container is not full''' (checking this option, the container configuration will print only when the container is full).
 
 
 
 
 
The following check boxes are displayed as Multi Level Container Rule:
 
 
 
* '''Revision Controlled''': '''Revision Controlled''' (All, No, Yes): YES means only one revision can be containerized together. Please correct and check the default value.
 
* '''Shop Order Controlled''': Yes / No. Yes allows only units from a single shop order to be containerized together – default No;
 
* '''Shipping Level''': Yes / No. Yes defines that a specific container is the Shipping level of containerization – default No;
 
* '''Auto Close''': Yes / No – default No;
 
* '''S/N Procedure''': Show all “COPS Container” algorithms created in Algorithm Tool – default Empty. Not used when Serial Mask is specified. The field can contain either (i) a predefined program filename or (ii) an algorithm number, if the algorithm was defined using the Algorithm Tool – default Empty;
 
* '''Multi Part:''' Allow multiple part number in a container. It is possible to add elements from another part number, but it must have the same Project Id.
 
 
 
In Addition, the user can define the Container dimension filling the weight (kg), height (m), length (m), volume (m3) and width (m). Selecting the Dimension per Unit flag, it is possible to fill for each configuration container. If the dimension is in different measure, the data will be converted.
 
 
 
 
 
=== Print/Export All Filtered Container Configuration ===
 
To '''Print/Export''' all Filtered Container Configurations, click on '''Print/Export Container Configurations''' button in the tasks panel.
 
 
 
A report is generated:
 
 
 
'''Figure 18: Print All Filtered Container Configuration'''
 
 
 
[[File:MLC018.png|700px]]
 
 
 
 
 
The user can perform some actions (print, save, fit page…) by clicking on the buttons in the top of the report.
 
 
 
== Multi-Level Containerization Browser ==
 
The '''Multi-Level Containerization Browser''' displays all multi-level containers created. All container details can be viewed (Container Configurations, container IDs (if it is child show the parent information, in case it has containers inside the screen must displays the tree with all child information).
 
 
 
 
 
The containers can be opened for containerization from the list (open a container calls the Multi-level Containerization screen).
 
 
 
 
 
The user is able to scan a specific Container ID or a containerized serial number, then the application calls Multi-level Containerization screen. If user scans a non containerized serial number, the application finds the container configuration for the serial part number and displays the available container levels to create a new Container ID.
 
 
 
 
 
=== Accessing the Multi-Level Containerization Browser  ===
 
To access the Multi-Level Containerization Browser, go to '''MDS Client > Multi-Level Containerization > Multi-Level Containerization Browser'''.
 
 
 
 
 
'''Figure 19: Multi-Level Containerization Browser.'''
 
 
 
[[File:MLC019.png]]
 
 
 
 
 
The Multi-Level Containerization Browser window displays:
 
 
 
 
 
'''Figure 20: Multi-Level Containerization Browser '''
 
 
 
[[File:MLC020.png|700px]]
 
 
 
 
 
The next topics will describe all available Containerization functionalities.
 
 
 
 
 
=== Containerization Browser List ===
 
The '''Containerization Browser List''' displays all multi-level containers created and allows performing the following actions:
 
 
 
 
 
* '''Filter''' '''Data '''
 
* '''Containerize''' (add units at containers)
 
* '''View a Container'''
 
* '''Delete a Container'''
 
* '''Export Shippable Containers '''
 
* '''Print/Export Containers'''
 
 
 
Note: It is possible to execute three different actions from the Task Panel:
 
 
 
 
 
* '''Open/Containerize '''(create or open a container)
 
* '''Create Parent Container'''
 
* '''Print/Export all Filtered Containers'''
 
* '''Export Filtered Container'''
 
 
 
=== Filter Settings  ===
 
 
 
'''Figure 21: Containerization Browser Filter'''
 
 
 
[[Image:MLC021.png]]
 
 
 
<br> To create a filter, follow the steps below:
 
 
 
<br> 1) Fill in one or more of the following filter options then click on the "'''Filter'''" button or press "'''Enter'''":
 
 
 
*Container ID
 
*Part Number
 
*Shop Order
 
*Revision
 
*Container Level
 
*Project ID
 
 
 
*Container Status: displays the containers opened or closed;
 
*Created Date: displays all containers created on the chosen date;
 
*Serial Status and
 
*Shipping Level.
 
 
 
2) Select the Created Date:
 
 
 
*From/Until: displays the containers created in the data range selected;
 
 
 
'''Note: '''
 
 
 
Container Status: displays the containers '''“Opened”''', '''“Closed”''', '''“Close/Sent”''', '''“Empty”''', '''“Open/Sent”''' (for any container that was closed and sent/exported to Oracle and '''“Closed/Sent”''' for a container that was closed and then sent to Oracle.
 
 
 
<br> '''Serial Status:''' displays the containers “Completed”, “Shipped”;
 
 
 
'''Shipping Level: '''displays the containers “Yes”, “No”, “All”;
 
 
 
<br> To clear the entered information for a filter, click on "'''Clear'''" button.
 
 
 
<br>
 
 
 
==== Add elements inside container  ====
 
 
 
To add elements (element can be serials or containers) inside a container, go to '''Multi-Level Containerization &gt; Multi-Level Containerization Browser''' and click on "Open/Containerize" on the Tasks panel or click on Containerize icon in the list.
 
 
 
<br> The difference between these actions is that clicking on "'''Open/Containerize'''" in the Tasks panel, displays a dialog to the user prompting for the container id or the serial number.
 
 
 
<br> '''Figure 22: Open/Create Container'''
 
 
 
[[Image:MLC022.png]]
 
 
 
<br> '''Figure 23: Multi-Level Containerization Browser'''
 
 
 
[[Image:MLC023.png]]
 
 
 
<br> The Multi-Level Containerization window displays:
 
 
 
<br> '''Figure 24: Multi-Level Containerization'''
 
 
 
[[Image:MLC024.png|700px|MLC024.png]]
 
 
 
The Multi-Level Containerization displays the following information about the parent container selected in the list:
 
 
 
*Container ID; Part Number; Created Date; Container level; Project ID; Status; Capacity, Add Serial/Container and Remove Serial/Container, String 1 and String 2.
 
 
 
The Container hierarchy is displayed under the "Container Elements" section and the serial numbers in the container are displayed. Clicking on a serial number in the hierarchy, the Location and Containerized Date are displayed.
 
 
 
<br> To add a serial number to a container, type/scan a serial number and press '''Enter'''.
 
 
 
The serial number is added under the container in the "'''Container Elements'''" section.
 
 
 
'''NOTE''': MULTI-PART Containers allows inserting serials that belongs to different part numbers, but they must comply with the mask.
 
 
 
The "'''Capacity'''" is incremented by one unit and the capacity bar reflects the serial added as percentage, if the container capacity is 0, the application assume the max capacity allowed = 999.99 for this container.
 
 
 
'''Note: '''To add a container inside another container, the Container to be added must be a lower level. You can add a container that is level 102 to another that is level 104 for example, but you can’t add it to a container that is level 101.
 
 
 
The'''Remove All Elements '''and '''Close/Print''' container buttons are displayed in the tasks panel, and if the configuration has Dim per Unit check box checked, a dialog for manage '''Dimensions '''is displayed.
 
 
 
'''Note:''' The application will not allow users to edit a container that's open for editing by another user. A message is displayed and shows the user name that is using that container.
 
 
 
<br>
 
 
 
==== Remove all elements from an opened container  ====
 
 
 
To remove elements from an opened container, go to'''Multi-Level Containerization Browser''' and click on the "'''Containerize'''" icon for the container created.
 
 
 
Click on "'''Remove all Elements'''" task on panel.
 
 
 
'''Figure 25: Remove All Elements'''
 
 
 
[[Image:MLC025.png]]
 
 
 
All the container elements will be removed from the main container hierarchy.
 
 
 
Click on "'''OK'''" to save and go back to "'''Containerize'''" for that container.
 
 
 
The container is displayed without any elements inside.
 
 
 
==== Remove elements from an opened container  ====
 
 
 
Follow the steps below to remove elements from containers:
 
 
 
To remove elements from an opened container, go to '''Multi-Level Containerization Browser''' and click on the "'''Containerize'''" icon.
 
 
 
The Multi-Level Containerization window displays:
 
 
 
<br> '''Figure 26: Multi-Level Containerization'''
 
 
 
[[Image:MLC026.png|700px|MLC026.png]]
 
 
 
To remove a Serial or Container, type/scan the Serial Number or Container ID in the '''Remove Serial/Container''' field and press “Enter”. Another method is to select the desired Container or Serial Number in the Container Elements list and double click it.
 
 
 
Save the container by clicking on "'''OK'''" and go back to "'''Containerize'''" for that container.
 
 
 
==== Close/Print container  ====
 
 
 
To print labels, it is necessary define a '''Label Program''' (editable combo box) during the container configuration, otherwise, just the Close option is displayed to the user.
 
 
 
Go to'''Multi-Level Containerization &gt; Multi-Level Containerization Browser &gt; Containerize.'''
 
 
 
<br> The Multi-Level Containerization window displays:
 
 
 
'''Figure 27: Close/Print Container'''
 
 
 
[[Image:MLC027.png|700px|MLC027.png]]
 
 
 
Click on "'''Close/Print Container'''" button in the Tasks panel.
 
 
 
If the Dim Per Unit Option is set in the container configuration, the user will be able to update the container dimension if necessary.
 
 
 
The Print Container Label window is displayed with the following fields:
 
 
 
<nowiki>* Label program (label type + print queue) - ready only. C</nowiki>onfigured in the Container Configuration; <nowiki>* Label Type – combo box;</nowiki> <nowiki>* Print Queue – configured in the Container Configuration;</nowiki> <nowiki>* Init. Printer – YES/NO</nowiki>
 
 
 
If the label type and print queue configuration is not defined in the container definition, a label type setup in the Label Maintenance module can be used.
 
 
 
Printing a label automatically closes the container. The "Close" icon is disabled for this container in the list.
 
 
 
<br>
 
 
 
==== Automatically close a full container  ====
 
 
 
If the "'''Auto Close'''" option is enabled in container configuration, a full container will automatically be closed.
 
 
 
<br> 1) Go to '''Multi-Level Containerization &gt; Multi-Level Containerization Browser''' and click on "'''Containerize'''" icon.
 
 
 
The Multi-Level Containerization window displays.
 
 
 
Type/Scan and add all serial numbers allowed in the container and click on "'''OK'''" to confirm.
 
 
 
<br> After performing these steps, the "'''Add Serial/Container'''" field is disabled and the container will be closed automatically and displayed in the list with status = closed.
 
 
 
=== View Container ===
 
Follow the steps below to view the container information.
 
 
 
Go to''' Multi-Level Containerization > Multi-Level Containerization Browser''' and click on "'''View Containe'''r" icon for a container from the list.
 
 
 
'''Figure 28: View Container'''
 
 
 
[[File:MLC028.png]]
 
 
 
The container view screen is displayed with all the container information, including the serial numbers/containers hierarchy. All information is displayed as ready only.
 
 
 
'''Figure 29: Container Information'''
 
 
 
[[File:MLC029.png|700px]]
 
 
 
Clicking on a serial number in the hierarchy, the following information of the serial is displayed:
 
 
 
# Location
 
# Containerized Date
 
 
 
=== Delete Container  ===
 
To delete a container, it must be empty (with '''no''' serials or containers inside).
 
 
 
Go to '''Multi-Level Containerization > Multi-Level Containerization Browser''', click on "'''Delete'''" icon.
 
 
 
 
 
'''Figure 30: Delete Containers'''
 
 
 
[[File:MLC030.png]]
 
 
 
A Confirmation message is displayed.
 
 
 
'''Figure 31: Confirmation Message'''
 
 
 
[[File:MLC031.png]]
 
 
 
Click on '''YES''' to confirm. The container is deleted from the list.
 
 
 
=== Export Container from List  ===
 
Go to '''Multi-Level Containerization Browser''' and click on "'''Export'''" icon.
 
 
 
 
 
'''NOTE:'''
 
 
 
It is necessary to configure an FTP server defined for the plant and remember that only the containers flagged as '''“shipping Level”''' can be exported.
 
 
 
FTP server must be configured on Generic Attribute sub-module using the following attributes: '''(ctr_export_ftp_dir''', '''ctr_export_ftp_password''', '''ctr_export_ftp_server''', '''ctr_export_ftp_user''').
 
 
 
'''Attribute recursive_ctr_export = YES''' configured on Generic Attribute sub-module.
 
 
 
 
 
'''Figure 32: Export Containers'''
 
 
 
[[File:MLC032.png]]
 
 
 
 
 
A Confirmation message is displayed:
 
 
 
 
 
'''Figure 33: Message Confirmation'''
 
 
 
[[File:MLC033.png]]
 
 
 
 
 
Confirm the export clicking "'''Yes'''".
 
 
 
A message saying that the container was exported with success is displayed:
 
 
 
 
 
'''Figure 34: Export Information Message'''
 
 
 
[[File:MLC034.png]]
 
 
 
The ftp "datafile" folder is opened and a .dat file generated for the container exported on the previous step is displayed in that folder. The file name is '''"ctr" + organization_code + datetime + ".dat"'''.
 
 
 
'''NOTE''': The exported file can be used on the Roboship Oracle (Oracle program that receive the exported files from MDS Client and load it in the Oracle.
 
 
 
=== Print/Export Container  ===
 
Follow the steps below to print/export containers:
 
 
 
 
 
'''Figure 35: Print/Export Reports'''
 
 
 
[[File:MLC035.png]]
 
 
 
Click on "'''Print/Export Container'''" icon;
 
 
 
 
 
The '''Choose…''' dialog displays:
 
 
 
 
 
'''Figure 36: Choose Dialog'''
 
 
 
[[File:MLC036.png]]
 
 
 
 
 
==== Report Type Simple ====
 
Select Type = Simple;
 
 
 
The Container will''' '''be printed:
 
 
 
 
 
'''Figure 37: Simple Report'''
 
 
 
[[File:MLC037.png|700px]]
 
 
 
 
 
In the Jasper Viewer click on "'''Save'''" button, enter the Filename and click to save.
 
 
 
 
 
==== Report Type Detailed ====
 
Follow the steps below to print/export containers:
 
 
 
 
 
Click on "'''Print/Export Container'''" icon
 
 
 
The Choose… dialog displays:
 
 
 
 
 
'''Figure 38: Chose Detailed'''
 
 
 
[[File:MLC038.png]]
 
 
 
 
 
Select Type = Detailed
 
 
 
The Container will be printed:
 
 
 
 
 
'''Figure 39: Detailed Report'''
 
 
 
[[File:MLC039.png|700px]]
 
 
 
 
 
In the Jasper Viewer click on "'''Save'''" button, enter the Filename and click to save.
 
 
 
 
 
=== Container Task Panel  ===
 
 
 
From the '''Task Panel''', the user can open or create a new container, create a parent container and print/export all filtered container configuration.
 
 
 
<br>
 
 
 
==== Containerize – Opening a Container  ====
 
 
 
Containers can be “opened” for serial number adding or removal and “closed” when full or when the operation requires modification of the contained containers.
 
 
 
<br> To open a container, follow the steps below:
 
 
 
<br> Go to '''Multi-Level Containerization Browser '''and click on "'''Open/Containerize'''" task on panel;
 
 
 
<br> '''Figure 40: Open/Containerize'''
 
 
 
[[Image:MLC040.png]]
 
 
 
<br> The '''Open/Create Container''' window displays. By default, the '''Open/Containerize '''option is setting. Type a serial number that is inside the container or a container ID already created.
 
 
 
*'''A CONTAINER ID is typed:'''
 
 
 
a) If the container id is not containerized, opens the container id entered (the dialog won't show the non completed possible parents for that container). If the user wants to containerize the container id, a new container should be created or scan parent container ID.
 
 
 
b) If the container id is containerized, displays a warning stating that the container is already inside another container, and then opens the container typed.
 
 
 
<br>
 
 
 
*'''A SERIAL NUMBER is typed:'''
 
 
 
a) If the serial number is not containerized, a list of configurations will be displayed (the serial number will be automatically added).
 
 
 
b) If the serial number is containerized, displays a warning stating that the serial is already inside a container, and then opens the parent container&nbsp;
 
 
 
<br> The container that has the serial number entered is opened for containerization and is displayed for editing in the multi-level containerization screen.
 
 
 
<br> '''Figure 41: Container Edition'''
 
 
 
[[Image:MLC041.png|700px|MLC041.png]]
 
 
 
<br> The user is able to add or remove serial/container by typing or scanning the serial/container in the '''Add Serial/Container '''or'''Remove Serial/Container '''field and hitting '''Enter'''.
 
 
 
Any attribute related to the container can be added in the'''String One '''and/or '''String Two '''fields.
 
 
 
Click on '''Save''' to save the data.
 
 
 
<br> '''NOTES:'''
 
 
 
'''Figure 42: Remove All Elements'''
 
 
 
[[Image:MLC042.png]]
 
 
 
If the user needs to remove all elements from container, go to the Tasks panel and click on '''Remove All Elements'''.
 
 
 
'''Figure 43: Remove All Elements'''
 
 
 
[[Image:MLC043.png]]
 
 
 
To close a container, it can not be empty. Click on '''Close/Print Container''' in the Tasks panel. A confirmation message is displayed before close/print the container.
 
 
 
<br> These notes are the same for creating new containers.
 
 
 
<br>
 
 
 
==== b Containerize – Creating a New Container  ====
 
 
 
Go to '''Multi-Level Containerization Browser''', click on "'''Open/Containerize'''" task on panel;
 
 
 
The Open/Create Container window displays:
 
 
 
<br> '''Figure 44: Open or Create a Container '''
 
 
 
[[Image:MLC044.png]]
 
 
 
<br> The '''Open/Create Container''' screen displays:
 
 
 
<br> '''Figure 45: Open/Create Container'''
 
 
 
[[Image:MLC045.png]]
 
 
 
<br> For this example, note that the container configuration created before is displayed in the '''Available Containers''' list.
 
 
 
<br> Double click on a container configuration or click on '''OK''' to associate it to a new container;
 
 
 
<br> The multi-level containerization screen is displayed with the serial number added to the elements hierarchy. A new container ID is created.
 
 
 
<br> Now, the user can add elements to the container until the capacity is reached.
 
 
 
<br> '''Figure 46: Container Elements'''
 
 
 
[[Image:MLC046.png]]
 
 
 
<br> Click on '''Ok '''to save the new container. A Confirmation message displays. Click on '''OK''' to confirm.
 
 
 
<br>
 
 
 
==== Create Parent Containers  ====
 
 
 
Go to '''Multi-Level Containerization Browser''', click on "'''Create Parent Containerize'''" task on panel;
 
 
 
The Open/Create Container popup displays:
 
 
 
<br> '''Figure 47: Create Parent Container '''
 
 
 
[[Image:MLC047.png]]
 
 
 
<br> Note that the default is '''Create Parent Container''' selected.
 
 
 
<br>
 
 
 
*'''A SERIAL NUMBER is typed:'''
 
 
 
a) If the entered serial number is not containerized, a list of configurations is displayed (the serial number is automatically added).
 
 
 
b) If the entered serial number is containerized, displays a warning stating that the serial is already inside a container, and then opens the parent container.
 
 
 
<br>
 
 
 
*'''A CONTAINER ID is typed:'''
 
 
 
a) If the entered container id is not containerized, a list of configurations is displayed (the container is automatically added).
 
 
 
b) If the entered container id is containerized, displays a warning stating that the serial is already inside a container, and then opens the parent container.
 
 
 
<br> After entering the container id/serial, the '''Open/Create Container''' dialog is displayed. Select an available container configuration and click on '''OK'''.
 
 
 
<br> '''Figure 48: Open/Create Container'''
 
 
 
[[Image:MLC048.png]]
 
 
 
<br> The Parent Container is created and other containers can be added. Only closed containers can be added to a parent container and the level must be lower than the parent container.
 
 
 
<br> '''Note:''' If the container is not full, a message is displayed to alert the user. Click on '''YES''' to continue. If the'''Log '''option was set in the container configuration, the user needs to enter a log to continue.
 
 
 
<br> The Multi-Level Containerization screen is displayed and the user can see the container data and only a few fields can be edited:
 
 
 
<br> '''Figure 49: Multi-Level Containerization'''
 
 
 
[[Image:MLC049.png]]
 
 
 
<br> The user is able to add or remove serial/container by typing or scanning the serial/container in the '''Add Serial/Container '''or'''Remove Serial/Container '''field and hitting '''Enter'''.
 
 
 
Any attribute data related to the container can be entered in the'''String One '''and/or '''String Two '''fields.
 
 
 
Click on '''Save''' to save the data.
 
 
 
<br> Every time that a container is closed, the print label dialog displays unless the option “Disable printing when…” in the Container Configuration was selected.
 
 
 
<br> '''Figure 50: Print container Label'''
 
 
 
[[Image:MLC050.png]]
 
 
 
<br> The user needs to select the Print Mode, the Label Type (it must be assigned to the containers’ part number) and the Print Queue and click on Print. If the user clicks on Cancel, to print a label for this container, it must be opened and closed again.
 
 
 
<br>
 
 
 
==== Print Export Filtered Containers  ====
 
 
 
1) To print or Export filtered containers, go to'''Multi-Level Containerization Browser''', click on "'''Print/Export Filtered Container'''" task on panel;
 
 
 
<br> '''Figure 51: Print/Export Filtered Containers'''
 
 
 
[[Image:MLC051.png]]
 
 
 
<br> The report is generated according the filter:
 
 
 
<br> '''Figure 52: Print/Export Filtered Containers Report '''
 
 
 
[[Image:MLC052.png|700px|MLC052.png]]
 
 
 
<br> Click on "'''Save'''" button to save the result;
 
 
 
A CSV file with the Containers report is saved in the selected path.
 
 
 
<br>
 
 
 
==== Export Filtered Containers  ====
 
 
 
1) To Export filtered containers, go to'''Multi-Level Containerization Browser''', click on '''Export Filtered Container'''" in the task on panel;
 
 
 
<br> '''Figure 53: Print/Export Filtered Containers'''
 
 
 
[[Image:MLC053.png|700px|MLC053.png]]
 
 
 
==== Multi-Level Container Pack  ====
 
 
 
The '''Multi-Level Container Pack '''was developed to help users that work with data collector and use the bar code commands.
 
 
 
<br> If a user A is working on any container and a B user tries to update the same one, it is displayed a warning message to alert that this container is locked for editing by "A" user.
 
 
 
<br> The container will be available for a new editing when user A complete the updates and close it.
 
 
 
<br>
 
 
 
==== Accessing the Multi-Level Container Pack  ====
 
 
 
To access the Multi-Level Container Pack, go to '''MDS Client &gt; Multi-Level Containerization &gt; Multi-Level Container Pack'''.
 
 
 
<br> '''Figure 54: Multi-Level Container Pack'''
 
 
 
[[Image:MLC054.png]]
 
 
 
<br> The main Multi-Level Container Pack window displays:
 
 
 
<br> '''Figure 55: Multi-Level Container Pack main window '''
 
 
 
[[Image:MLC055.png|700px|MLC055.png]]
 
 
 
<br> This screen is used to execute the same operations of Container Browser screen with the addition that the users can use an optical reader (data collector) to read barcodes to containerize. The Container Pack screen allows to manage (Create, Open, Add Elements, Remove Elements, Close) parent containers by commands that can be typed or scanned from bar-codes. The screen displays container details with big font size and colors.
 
 
 
<br> The following commands can be executes from the Command Console:
 
 
 
*'''<nowiki>#ClearConsole</nowiki>''': this command will clear all data entered in the command console;
 
*'''<nowiki>#RemElement</nowiki>''': type this command to remove elements from container;
 
*'''<nowiki>#RemoveAll</nowiki>''': it will remove All elements from container;
 
*'''<nowiki>#Cancel</nowiki>''': this command will cancel all information entered;
 
*'''<nowiki>#Save</nowiki>''': it will save all data from container;
 
*'''<nowiki>#CloseContainer</nowiki>''': close the container;
 
*'''<nowiki>#CreateParentContainer</nowiki>''': create a parent container for the actual container;
 
 
 
In addition, to represent some information are used colors and sounds:
 
 
 
*'''Black''': Closed.
 
*'''Green''': Opened with 80% of capacity free.
 
*'''Yellow''': Opened with 80% of capacity full.
 
*'''Orange''': Opened with 100% of capacity full.
 
*'''Red''': Error message.
 
 
 
'''Sounds:'''
 
 
 
*1 beep: Error message.
 
*2 beep: with 80% of capacity full.
 
*3 beep: with 100% of capacity full.
 
 
 
==== Open/Containerize  ====
 
 
 
To Open/Containerize, click on '''Open/Containerize''' in the Tasks Panel.
 
 
 
'''NOTE''': The first time that the users open or create a container, must be by clicking on the link.
 
 
 
<br> '''Figure 56: Open/ Containerize'''
 
 
 
[[Image:MLC056.png|700px|MLC056.png]]
 
 
 
<br> '''Figure 57: Add Elements'''
 
 
 
[[Image:MLC057.png|700px|MLC057.png]]
 
 
 
Now the user can include elements till reach the capacity.
 
 
 
<br>
 
 
 
==== Close/Print Container  ====
 
 
 
This function is exactly like Close/Print Container in the Container Browser module. For more information, go to [#_d)_Close/Print_container Close/Print Container].
 
 
 
<br>
 
 
 
==== Create Parent Container  ====
 
 
 
This function is exactly like Create Parent Container in the Container Browser module. For more information, go to [#_2.2.2c_Create_Parent Create Parent Container].
 
 
 
<br>
 
 
 
==== Cancel Containers  ====
 
 
 
This functionality just cancels all data entered for the active session, from the last opened container.
 
 
 
<br>
 
 
 
==== Dimensions  ====
 
 
 
The Dimensions must be filled using the same rules for Multi Container Browser.:
 
 
 
*The user can define the Container dimension filling the weight (kg), height (m), length (m), volume (m3) and width (m). Selecting the Dimension per Unit flag, it is possible to fill for each configuration container. If the dimension is in different measure, the data will be converted.
 
 
 
'''Note: '''
 
 
 
The dimensions icon will be enabled if the '''Dim. Per Unit''' flag is set.
 
 
 
== Employee Validation  ==
 
 
 
== SQC Configuration  ==
 
 
 
== Labor Tracking Maintenance  ==
 
 
 
== Algorithm Tool  ==
 
 
 
== MDS&nbsp;Labels ==
 

Latest revision as of 22:05, 26 September 2024

42Q Home > Shop Floor Control > Configuration
 

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).
 


Kit Verify Layout

42Q-MES0078 Kit Verify Layout 

The Kit Verify Layout module allows users to validate all components in a kit and provides a visual layout mapping to aid in component placement.

 

Multi-level Containerization Configuration

42Q-MES0018 Multi-Level Containerization Configuration

The Multilevel Containerization Configuration module described here is used for registering and storing serial numbers placed in a container, box, or packaging that will be sent to customers at the end of production.

 

Employee Validation

42Q-MES0019 Employee Validation

The module is responsible for creating training that the operator should complete working in certain manufacturing processes. All operator control (registration and maintenance of information) and required training and certificates for the operator's work on the shop floor (especially in medical locations) will be administered by this feature.

 

SQC Configuration

42Q-MES0023 SQC Configuration

Module developed for storing data imported from a manually entered spreadsheet. SQC Configuration then compares this data with real data collected by the SFDC / MES application. This module is important because it calculates/measures the required time to produce a unit (HPU - Hour Per Unit).

 

Labor Maintenance 

42Q-MES0182-A  Labor Maintenance

Labor Maintenance is an Administrative portlet, that allows to change and modify the time registered by the operators tracked in Production Workbench and OEE Workbench. 

 

Algorithm Maintenance

42Q-MES0021 Algorithm Maintenance 

The Algorithm Tool provides the ability to create and modify serial number algorithms. It adheres to the format used by customers and engineers when writing specifications for serial number algorithms, integrated with Shop Floor Configuration, and generates serial numbers (shop order and containerization modules) and MAC addresses.

 

MDS Labels

42Q-MES0022 MDS Labels

This Web application gives plants the ability to create, update, print, and share labels without the need for IT resources. It enables plants to easily define and access various different data sources like MDS, and MESR, along with a variety of other database types. It allows users to map label fields to these data sources in order to create dynamic labels. It also enables plants to extract statistical information about the labels that are managed in MDS Labels as well as monitor the audit information.

 

CMMS Admin

42Q-MES0073 CMMS Admin

42Q’s CMMS (Computerized Maintenance Management System) tools are designed to manage a plant’s assets. The administration module of CMMS (CMMS Admin) is designed for administrators (manufacturing engineers) to perform pre-configuration tasks so that plant machinery and equipment are properly maintained. Within the CMMS Admin portal, plant administrators define groups responsible for repair and maintenance, set notification alerts, and add plants, departments, and projects to the CMMS system. There are seven sub-modules available to local system administrators. 

 

CMMS Asset

42Q-MES0074 CMMS Asset

Within CMMS Asset, administrators and engineers configure maintenance details related to a plant's assets. There are 12 sub-modules available to local system administrators. 

 

Tooling Control

42Q-MES0142 Tooling Control

CMMS Tooling Control is the sister companion to CMMS Asset, 42Q’s definitive solution for asset maintenance. Tooling Control manages machine tooling equipment such as jigs, stencils, and test fixtures, according to their usage (cycle/hit count) and/or expiration date. The Tooling Mapping module creates an association between the product’s Part Number (associated with the Shop Floor ID and configured in MES 101) and the Asset Type defined in CMMS Asset. This connection allows the system to identify tooling usage counts via scan activity on the Product’s Part Number. Tooling Mapping sends tooling requirements to conduit, 42Q’s Production Scanning portal.


OEE Configuration

42Q-MES0136 OEE Configuration

The OEE Configuration modules allow users to define the following: Shift, Plant Calendar, Work Center, Root Cause Category, and Root Cause. Users complete the following tasks within OEE Configuration: Map Tag IDs to Assets (Tag Mapping), Define Up/Down Thresholds for Asset Types, Import Tag Mapping, Import Up/Down Thresholds, SetTarget UPH for Mfg Line, Process Part Number, and Shop Order.

 

Target Maintenance

42Q-MES0084 Target Maintenance

Targets are meant to be used as a source of any custom data. This work instruction is intended to guide users on how to manage and maintain targets faster and more efficiently. It also helps any MES Application customization. This user guide will show how to create data, add columns (attributes), and define the data type.

 

MES-Fuji Configuration

42Q-MES0146 MES Fuji Configuration

Per manufacturing industry best practice, a typical production line in 42Q’s MES consists of an  SFDC (Shop Floor Data Collector) station and a PTS (Parts Traceability System) workstation configured for advanced traceability.

 

Configuration Publish

42Q-MES0112 Configuration Publish

42Q’s Configuration Publish portlet is used to publish configuration changes for Conduit. For example, when a Part x Route association is configured or a Route is changed, users can publish the configuration for use with Production Scanning. Configuration Publish has the ability to automatically publish these configurations, or users can manually publish them within the portlet.

 

Command Register

42Q-MES0143 Command Register

The Command Register provides the users the ability to customize and manage Auto Commands, Macros, and Process Control that are available for a given shop floor ID.

 

QCP Configuration

42Q-MES0150 QCP Configuration Portlet

The QCP Configuration Portlet provides the users with administrator's profiles, the ability to create checklists with pre-configured questions for specific stations.

 

Shop Floor Configuration - Assembly Maintenance

42Q-MES0002 Assembly Maintenance

This Assembly Maintenance module described in this document defines the procedures for assembling a product, along with the steps for each component’s integration. When the user enters information into the workstation, the description of how to perform specific labor will display. This description is available on the scanner, located at the station display, and may also inform the user on the exact location of where the component should be placed in the part.

 

Shop Floor Configuration - Attribute Def Maintenance

42Q-MES0003 Attribute Def Maintenance

The Attribute Definition Maintenance module described in this documentation creates attributes that are tied to specific products during the manufacturing process. It also creates the steps that should occur at the attribute check/validation.

 

Shop Floor Configuration - Data Collector Maintenance

42Q-MES0004 Data Collector Maintenance

The Data Collector Maintenance module described here defines the equipment reading (data collector) that will be used at a particular workstation.

 

Shop Floor Configuration - Data Editor Maintenance

42Q-MES0005 Data Editor Maintenance

The Setup Data Editor is a text, tab-delimited mechanism used for defining various pieces for Shop Floor configuration. Various parts of configuration can be defined, but generally, it is used for the configuration that is text string-based and does not lend itself well to a table structure. Examples are defining scan macros, auto command lines, and serial input masking lines for product numbers.

 

Shop Floor Configuration - Defect Codes Maintenance

42Q-MES0006 Defect Codes Maintenance

The Defect Codes Maintenance moduled described here allows for the recording of defects found after a component is manufactured. According to the number of records, the operator will be able to identify a defect for a specific component and reference that defect in the future.

 

Shop Floor Configuration - Location Maintenance

42Q-MES0007 Location Maintenance

The Location Maintenance module described here is used to register workstations and define the specific process that should be available at each workstation.

 

 

Shop Floor Configuration - Mfg Hold Maintenance

42Q-MES0008 Mfg Hold Maintenance

The Manufacturing Hold Maintenance module described here allows the operator to place a particular component on hold, either for lack of material or if it requires an unavailable process. The component will bypass the process and continue on the production line.

 

Shop Floor Configuration - Mfg Line Maintenance

42Q-MES0009 Mfg Line Maintenance

The Manufacturing Line Maintenance module described here allows users to map a point on a production line where information must be collected, such as the error rate. This helps measure the efficiency of the manufacturing process by Data Collectors located at a workstation (Locations). If the rate is higher than acceptable, the system sends a message requesting action to alleviate the problem.

 

Shop Floor Configuration - Misc Configuration Maintenance

42Q-MES0010 Misc Configuration Maintenance

The Misc Configuration Maintenance module described here inserts the data that was created in the Shop Floor ID functionality into the configuration. This data is necessary because it indicates a shift in the schedules on which the lines will be working, and it also informs the system of data collection that will be used in the database at those times.

 

Shop Floor Configuration - Part Maintenance

42Q-MES0011 Part Maintenance

The Part Maintenance module described here allows you to create a code (part number) and description for a particular product/component produced.

 

Shop Floor Configuration - Product Route Maintenance

42Q-MES0012 Product Route Maintenance

The Product Route Maintenance module described here can be used for enabling the creation of the path (route) the product should follow in the production line.

 

Shop Floor Configuration - Record Components Maintenance

42Q-MES0013 Record Components Maintenance

The Record Components Maintenance module described here notifies the process of a particular component that its serial number is connecting with the serial number of the final product.

 

Shop Floor Configuration - Revision Change Maintenance

42Q-MES0014 Revision Change Maintenance

The Revision Change Maintenance module described here is used to update the specification (revision) of a product. When the user needs to change any feature or component of a product, this feature is used to apply changes and the product is manufactured with the new specification (new revision).

 

Shop Floor Configuration - Shop Floor ID Maintenance

42Q-MES0015 Shop Floor ID Maintenance

The Shop Floor ID Maintenance module described here is used to create a configuration that joins the SFDC with the database that will be used by MES applications. The configuration has the same name as the Data Collector system.

 

Shop Floor Configuration - Sampling Plan Configuration

42Q-MES0016 Sampling Plan Configuration

This module registers the percentage of products that deviated from their respective routes and analyzes the data for quality.

 

Shop Floor Configuration - Traveler Maintenance

42Q-MES0017 Traveler Maintenance

The Traveler Maintenance module described here is used for creating an information list that contains the components a product needs for assembly. It is used to track components that have been inserted in the product on the production line.

 

Quick Action Configuration

MES0188-A-Quick Action Configuration

Quick Action Configuration is a tool designed to allow authorized users with administrator or engineering access to trigger macros and commands with a simple click, to connect actions with equipment, by creating buttons or quick actions.

 

Event Link

42Q-MES0189-A  Event Link

Event Link acts as a bridge between the quick action button and the equipment, making communication available and ensuring the button reflects real-time equipment status.