Difference between revisions of "Configuration"

From 42Q
Jump to navigation Jump to search
Line 2: Line 2:
 
<small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Shop_Floor_Control|Shop Floor Control]] > Configuration</small><br/> __TOC__
 
<small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Shop_Floor_Control|Shop Floor Control]] > Configuration</small><br/> __TOC__
  
== <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 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> ==
  
 
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;
 
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;
  
== <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 Tool</span></span></span></span></span></span> ==
+
== <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">Multilevel Containerization Configuration</span></span></span></span></span></span></span> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-5-I-MES0021-C_RA1_Algorithm_Tool|SOP-5-I-42Q-MES0021-C RA1 Algorithm Tool]]'''  
+
| '''[[SOP-5-I-MES0018-C_RA1_Multi-Level_Containerization_Configuration|SOP-5-I-42Q-MES0018-C RA1 Multi-Level Containerization Configuration]]'''  
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 SFDC and generates serial numbers (shop order and containerization modules) and MAC addresses.
+
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.
 +
 
 +
|}
 +
 
 +
== &nbsp; ==
 +
 
 +
== <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> ==
 +
 
 +
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-MES0019-C_RA1_Employee_Validation|SOP-5-I-42Q-MES0019-C RA1 Employee Validation]]'''
 +
The module 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 operators work on the shop floor (especially in medical locations) will be administered by this feature.
  
 
|}
 
|}
Line 17: Line 28:
 
&nbsp;
 
&nbsp;
  
== <span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span style="font-size:large;"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Control">Bulk Tooling Mapping</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
+
== <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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[42Q-MES0142-C_Tooling_Control#Bulk_Tooling_Mapping|42Q-MES0142-C Tooling Control]]'''  
+
| '''[[SOP-5-I-MES0023-C_RA1_SQC_Configuration|SOP-5-I-42Q-MES0023-C RA1 SQC Configuration]]'''  
CMMS Tooling Control is the sister companion to CMMS Asset, 42Q’s definitive solution for asset maintenance. The Bulk Tooling Mapping module is used to import the tooling mapping list information. The operator downloads the Template (in CSV format) file, edits the tooling mapping data, then imports the CSV file into the CMMS system.
+
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).
  
 
|}
 
|}
  
== <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> ==
+
&nbsp;
 +
 
 +
== <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 Tool</span></span></span></span></span></span></span> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-5-I-MES0073-C_CMMS_Admin|SOP-5-I-42Q-MES0073-C CMMS Admin]]'''  
+
| '''[[SOP-5-I-MES0021-C_RA1_Algorithm_Tool|SOP-5-I-42Q-MES0021-C RA1 Algorithm Tool]]'''  
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;
+
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 SFDC, and generates serial numbers (shop order and containerization modules) and MAC addresses.
  
 
|}
 
|}
Line 37: Line 50:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-5-I-MES0074-C_CMMS_Asset|SOP-5-I-42Q-MES0074-C CMMS Asset]]'''  
+
| '''[[SOP-5-I-MES0022-C_RA1_MDS_Labels|SOP-5-I-42Q-MES0022-C RA1 MDS Labels]]'''  
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;
+
This Web application gives plants the ability to create, update, print, and share labels without the need of IT resources. It enables plants to easily define and access various different data sources like MDS, 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.
  
 
|}
 
|}
  
== <br/> <span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register"><span style="font-size:large;"><span class="mw-headline" id="Command_Register"><span class="mw-headline" id="Command_Register">Command Register</span></span></span></span></span></span> ==
+
&nbsp;
 +
 
 +
== <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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-5-I-42Q-MES0143-C_Command_Register|SOP-5-I-42Q-MES0143-C Command Register]]'''  
+
| '''[[SOP-5-I-MES0073-C_CMMS_Admin|SOP-5-I-42Q-MES0073-C CMMS Admin]]'''  
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.
+
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;
  
 
|}
 
|}
Line 57: Line 72:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[42Q-MES0112-C_RA1_Configuration_Publish|SOP-5-I-42Q-MES0112-C RA1 Configuration Publish]]'''  
+
| '''[[SOP-5-I-MES0074-C_CMMS_Asset|SOP-5-I-42Q-MES0074-C CMMS Asset]]'''  
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.
+
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;
  
 
|}
 
|}
Line 68: Line 83:
 
&nbsp;
 
&nbsp;
  
== <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 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 Mapping</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
 +
 
 +
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[42Q-MES0142-C_Tooling_Control#Tooling_Mapping|42Q-MES0142-C 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.
 +
 
 +
|}
 +
 
 +
<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 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>
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-5-I-MES0019-C_RA1_Employee_Validation|SOP-5-I-42Q-MES0019-C RA1 Employee Validation]]'''  
+
| '''[[42Q-MES0136-C_OEE_Configuration|42Q-MES0136-C OEE Configuration]]'''  
The module 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 operators work on the shop floor (especially in medical locations) will be administered by this feature.
+
The OEE Configuration modules allow users to define the following: Shift, Plant Calendar, Work Center, Root Cause Category, 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.
  
 
|}
 
|}
Line 79: Line 103:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-5-I-MES0022-C_RA1_MDS_Labels|SOP-5-I-42Q-MES0022-C RA1 MDS Labels]]'''  
+
| '''[[SOP-5-I-MES0084-C_Target_Maintenance|SOP-5-I-42Q-MES0084-C Target Maintenance]]'''  
This Web application gives plants the ability to create, update, print, and share labels without the need of IT resources. It enables plants to easily define and access various different data sources like MDS, 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.
+
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.
  
 
|}
 
|}
Line 90: Line 114:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 103: Line 127:
 
&nbsp;
 
&nbsp;
  
== <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">Multilevel Containerization Configuration</span></span></span></span></span></span> ==
+
== <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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-5-I-MES0018-C_RA1_Multi-Level_Containerization_Configuration|SOP-5-I-42Q-MES0018-C RA1 Multi-Level Containerization Configuration]]'''  
+
| '''[[42Q-MES0112-C_RA1_Configuration_Publish|SOP-5-I-42Q-MES0112-C RA1 Configuration Publish]]'''  
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.
+
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.
  
 
|}
 
|}
Line 114: Line 138:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
 +
 
 +
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 +
|-
 +
| '''[[SOP-5-I-42Q-MES0143-C_Command_Register|SOP-5-I-42Q-MES0143-C 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.
 +
 
 +
|}
 +
 
 +
<br/> <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>
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[42Q-MES0136-C_OEE_Configuration|42Q-MES0136-C OEE Configuration]]'''  
+
| '''[[SOP-42Q-MES0150-C_QCP_Configuration_Portlet|SOP-42Q-MES0150-C QCP Configuration Portlet]]'''  
The OEE Configuration modules allow users to define the following: Shift, Plant Calendar, Work Center, Root Cause Category, 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.
+
The QCP Configuration Portlet provides the users with administrator's&nbsp;profiles, the ability to create checklists with pre-configured questions for specific stations.
  
 
|}
 
|}
Line 125: Line 158:
 
&nbsp;
 
&nbsp;
  
== <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 class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span style="font-size:large;"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Mapping"><span class="mw-headline" id="Bulk_Tooling_Control">Bulk Tooling Mapping</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
|-
| '''[[SOP-42Q-MES0150-C_QCP_Configuration_Portlet|SOP-42Q-MES0150-C QCP Configuration Portlet]]'''  
+
| '''[[42Q-MES0142-C_Tooling_Control#Bulk_Tooling_Mapping|42Q-MES0142-C Tooling Control]]'''  
The QCP Configuration Portlet provides the users with administrator's&nbsp;profiles, the ability to create checklists with pre-configured questions for specific stations.
+
CMMS Tooling Control is the sister companion to CMMS Asset, 42Q’s definitive solution for asset maintenance. The Bulk Tooling Mapping module is used to import the tooling mapping list information. The operator downloads the Template (in CSV format) file, edits the tooling mapping data, then imports the CSV file into the CMMS system.
  
 
|}
 
|}
Line 136: Line 169:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 147: Line 180:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 158: Line 191:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 169: Line 202:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 180: Line 213:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 191: Line 224:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 202: Line 235:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 213: Line 246:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 224: Line 257:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 235: Line 268:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 246: Line 279:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 257: Line 290:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 268: Line 301:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 279: Line 312:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 288: Line 321:
 
|}
 
|}
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 299: Line 332:
 
&nbsp;
 
&nbsp;
  
== <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 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> ==
  
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
Line 309: Line 342:
  
 
&nbsp;
 
&nbsp;
 
== <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> ==
 
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
| '''[[SOP-5-I-MES0023-C_RA1_SQC_Configuration|SOP-5-I-42Q-MES0023-C RA1 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).
 
 
|}
 
 
&nbsp;
 
 
== <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> ==
 
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
| '''[[SOP-5-I-MES0084-C_Target_Maintenance|SOP-5-I-42Q-MES0084-C 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.
 
 
|}
 
 
== <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 Mapping</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==
 
 
{| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:blue; border-width:2px;"
 
|-
 
| '''[[42Q-MES0142-C_Tooling_Control#Tooling_Mapping|42Q-MES0142-C 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.
 
 
|}
 

Revision as of 16:18, 28 June 2021

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

Multilevel Containerization Configuration

SOP-5-I-42Q-MES0018-C RA1 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

SOP-5-I-42Q-MES0019-C RA1 Employee Validation

The module 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 operators work on the shop floor (especially in medical locations) will be administered by this feature.

 

SQC Configuration

SOP-5-I-42Q-MES0023-C RA1 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).

 

Algorithm Tool

SOP-5-I-42Q-MES0021-C RA1 Algorithm Tool

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 SFDC, and generates serial numbers (shop order and containerization modules) and MAC addresses.

 

MDS Labels

SOP-5-I-42Q-MES0022-C RA1 MDS Labels

This Web application gives plants the ability to create, update, print, and share labels without the need of IT resources. It enables plants to easily define and access various different data sources like MDS, 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

SOP-5-I-42Q-MES0073-C 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

SOP-5-I-42Q-MES0074-C 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 Mapping

42Q-MES0142-C 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-C OEE Configuration

The OEE Configuration modules allow users to define the following: Shift, Plant Calendar, Work Center, Root Cause Category, 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

SOP-5-I-42Q-MES0084-C 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

SOP-5-I-42Q-MES0146-C 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

SOP-5-I-42Q-MES0112-C RA1 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

SOP-5-I-42Q-MES0143-C 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

SOP-42Q-MES0150-C 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.

 

Bulk Tooling Mapping

42Q-MES0142-C Tooling Control

CMMS Tooling Control is the sister companion to CMMS Asset, 42Q’s definitive solution for asset maintenance. The Bulk Tooling Mapping module is used to import the tooling mapping list information. The operator downloads the Template (in CSV format) file, edits the tooling mapping data, then imports the CSV file into the CMMS system.

 

Shop Floor Configuration - Assembly Maintenance

SOP-5-I-42Q-MES0002-C RA1 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

SOP-5-I-42Q-MES0003-C RA1 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

SOP-5-I-42Q-MES0004-C RA1 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

SOP-5-I-42Q-MES0005-C RA1 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

SOP-5-I-42Q-MES0006-C RA1 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

SOP-5-I-42Q-MES0007-C RA1 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

SOP-5-I-42Q-MES0008-C RA1 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

SOP-5-I-42Q-MES0009-C RA1 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

SOP-5-I-42Q-MES0010-C RA1 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

SOP-5-I-42Q-MES0011-C RA1 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

SOP-5-I-42Q-MES0012-C RA1 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

SOP-5-I-42Q-MES0013-C RA1 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

SOP-5-I-42Q-MES0014-C RA1 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 - Sampling Plan Configuration

SOP-5-I-42Q-MES0016-C RA1 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 - Shop Floor ID Maintenance

SOP-5-I-42Q-MES0015-C RA1 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 - Traveler Maintenance

SOP-5-I-42Q-MES0017-C RA1 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.