Difference between revisions of "SOP-42Q-MES0005 Data Editor Maintenance"
Line 1: | Line 1: | ||
− | <small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Shop_Floor_Control|Shop Floor Control]] > [[Configuration|Configuration]] > Data Editor Maintenance</small><br/> | + | <small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Shop_Floor_Control|Shop Floor Control]] > [[Configuration|Configuration]] > Data Editor Maintenance</small><br/> |
| | ||
Line 7: | Line 7: | ||
| | ||
− | <center>'''Shop Floor | + | <center>'''Shop Floor Control'''</center> <center>'''Configuration'''</center> <center>'''Data Editor'''</center> <center>'''Version MES15 1.0'''</center> <center> </center> |
| | ||
− | <center>This | + | <center>This SOP is 42Q's corporate standard.</center> <center> This document is under revision control. The latest revision is located on Intranet.</center> <center> Once printed it is an uncontrolled copy. All alterations to this SOP require approval.</center> <center> Contact the IT Global Education and Training Department to submit suggested alterations and or updates.</center> |
''This edition applies to MES15 portal V1.0 and all subsequent releases and modifications until otherwise indicated in new revisions.'' | ''This edition applies to MES15 portal V1.0 and all subsequent releases and modifications until otherwise indicated in new revisions.'' | ||
| | ||
− | == <span class="mw-headline" id="Shop_Floor_Configuration.5Bedit.5D"><span class="mw-headline" id="Shop_Floor_Configuration">Shop Floor Configuration</span></span> == | + | == <span class="mw-headline" id="Shop_Floor_Configuration"><span class="mw-headline" id="Shop_Floor_Configuration.5Bedit.5D"><span class="mw-headline" id="Shop_Floor_Configuration">Shop Floor Configuration</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). | 42Q’s powerful data collection system collects critical information from a plant’s shop floor, utilizing shop floor data collector, an intuitive tool developed by 42Q’s experienced manufacturing team. The aggregate information is stored in a cloud database, and available to MESWeb, where quality reports are generated. The 42Q system uses manual and automated barcode scanning to collect data for a product line or plant. Thus, 42Q plays an important role in maintaining unit histories and directing product movement on the manufacturing floor. The current version of 42Q includes configuration capabilities, which provide access to all sub-modules pages and their functionalities (view, add, edit, print/generate output files). | ||
Line 20: | Line 20: | ||
| | ||
− | == <span class="mw-headline" id="Data_Editor_Maintenance.5Bedit.5D"><span class="mw-headline" id="Data_Editor_Maintenance">Data Editor Maintenance</span></span> == | + | == <span class="mw-headline" id="Data_Editor_Maintenance"><span class="mw-headline" id="Data_Editor_Maintenance.5Bedit.5D"><span class="mw-headline" id="Data_Editor_Maintenance">Data Editor Maintenance</span></span></span> == |
Data Editor Maintenance provides access to the Shop Floor configuration file that defines (but is not limited to) PCC ports, Options Lines, Auto Commands, Macros, Serial Input Masking, Passwords, and Device Numbers. | Data Editor Maintenance provides access to the Shop Floor configuration file that defines (but is not limited to) PCC ports, Options Lines, Auto Commands, Macros, Serial Input Masking, Passwords, and Device Numbers. | ||
− | To access the Data Editor, select '''Shop Floor Control'''>'''Configuration'''>'''Shop Floor Configuration'''>'''Data Editor ''' | + | To access the Data Editor, select '''Shop Floor Control'''>'''Configuration'''>'''Shop Floor Configuration'''>'''Data Editor''' |
'''Figure 1: MES Data Editor Maintenance''' | '''Figure 1: MES Data Editor Maintenance''' | ||
Line 32: | Line 32: | ||
| | ||
− | '''<u> | + | '''<u>Note</u>''': A user only has access to the modules assigned to his/her profile. |
| | ||
Line 46: | Line 46: | ||
| | ||
− | The user can edit, clear Data Editor, Publish History and Print/Export the data. | + | The user can edit, clear Data Editor, Publish History, and Print/Export the data. |
| | ||
− | === <span class="mw-headline" id="Filter_Setup_Data_Editor_by_Shop_Floor_ID.5Bedit.5D"><span class="mw-headline" id="Filter_Setup_Data_Editor_by_Shop_Floor_ID">Filter Setup Data Editor by Shop Floor ID</span></span> === | + | === <span class="mw-headline" id="Filter_Setup_Data_Editor_by_Shop_Floor_ID"><span class="mw-headline" id="Filter_Setup_Data_Editor_by_Shop_Floor_ID.5Bedit.5D"><span class="mw-headline" id="Filter_Setup_Data_Editor_by_Shop_Floor_ID">Filter Setup Data Editor by Shop Floor ID</span></span></span> === |
This module enables the user to filter by Shop Floor ID. | This module enables the user to filter by Shop Floor ID. | ||
Line 66: | Line 66: | ||
| | ||
− | === <span class="mw-headline" id="Editing_with_the_Setup_Data_Editor.5Bedit.5D"><span class="mw-headline" id="Editing_with_the_Setup_Data_Editor">Editing with the Setup Data Editor</span></span> === | + | === <span class="mw-headline" id="Editing_with_the_Setup_Data_Editor"><span class="mw-headline" id="Editing_with_the_Setup_Data_Editor.5Bedit.5D"><span class="mw-headline" id="Editing_with_the_Setup_Data_Editor">Editing with the Setup Data Editor</span></span></span> === |
This module enables the user to edit using the Setup Data Editor. | This module enables the user to edit using the Setup Data Editor. | ||
Line 80: | Line 80: | ||
[[File:Figure 5 Setup Data Editor Form.jpg|700px|Figure 5 Setup Data Editor Form.jpg]] | [[File:Figure 5 Setup Data Editor Form.jpg|700px|Figure 5 Setup Data Editor Form.jpg]] | ||
− | <br/> '''<u> | + | <br/> '''<u>Note:</u>''' To add a new tab, create an entry line by entering "# SECTION" <nowiki>+ </nowiki>section name. |
− | <nowiki>+ </nowiki> | ||
− | |||
− | section name. | ||
For example: # SECTION MULTIPASS | For example: # SECTION MULTIPASS | ||
Line 89: | Line 86: | ||
2. Enter the desired modifications to the Setup Data Editor Form. | 2. Enter the desired modifications to the Setup Data Editor Form. | ||
− | '''<u> | + | '''<u>Note:</u>''' If multiple users have opened the Setup Data Editor for the same SFDC PC line, only the first user to open the file has to write access. Other users are notified that the SDE is locked for editing by another user and that read-only access is allowed. |
| | ||
Line 97: | Line 94: | ||
| | ||
− | ==== <span class="mw-headline" id="Copy_Setup_Data_Editor_from_Other_Shop_Floor_ID.5Bedit.5D"><span class="mw-headline" id="Copy_Setup_Data_Editor_from_Other_Shop_Floor_ID">Copy Setup Data Editor from Other Shop Floor ID</span></span> ==== | + | ==== <span class="mw-headline" id="Copy_Setup_Data_Editor_from_Other_Shop_Floor_ID"><span class="mw-headline" id="Copy_Setup_Data_Editor_from_Other_Shop_Floor_ID.5Bedit.5D"><span class="mw-headline" id="Copy_Setup_Data_Editor_from_Other_Shop_Floor_ID">Copy Setup Data Editor from Other Shop Floor ID</span></span></span> ==== |
This module replaces the contents of the current Setup Data Editor Form with data copied from another Shop Floor ID. | This module replaces the contents of the current Setup Data Editor Form with data copied from another Shop Floor ID. | ||
Line 123: | Line 120: | ||
3. Select '''Yes''' to confirm the install, or select '''No''' to cancel. | 3. Select '''Yes''' to confirm the install, or select '''No''' to cancel. | ||
− | <br/> '''<u> | + | <br/> '''<u>Note:</u>''' The application saves a backup file on the MES server every time the user installs a Setup Data Editor. |
| | ||
− | ==== <span class="mw-headline" id="Publish_History.5Bedit.5D"><span class="mw-headline" id="Publish_History">Publish History</span></span> ==== | + | ==== <span class="mw-headline" id="Publish_History"><span class="mw-headline" id="Publish_History.5Bedit.5D"><span class="mw-headline" id="Publish_History">Publish History</span></span></span> ==== |
The Publish History functionality is used by permitted users to show and publish the action history of a Route. To use this functionality | The Publish History functionality is used by permitted users to show and publish the action history of a Route. To use this functionality | ||
Line 141: | Line 138: | ||
[[File:42Q Publish History.png|SFID Publish History Function.png]]<br/> | [[File:42Q Publish History.png|SFID Publish History Function.png]]<br/> | ||
− | ==== <span class="mw-headline" id="Print.2FExport_Current_Setup_Data_Editor.5Bedit.5D"><span class="mw-headline" id="Print.2FExport_Current_Setup_Data_Editor">Print/Export Current Setup Data Editor</span></span> ==== | + | ==== <span class="mw-headline" id="Print.2FExport_Current_Setup_Data_Editor"><span class="mw-headline" id="Print.2FExport_Current_Setup_Data_Editor.5Bedit.5D"><span class="mw-headline" id="Print.2FExport_Current_Setup_Data_Editor">Print/Export Current Setup Data Editor</span></span></span> ==== |
This module enables the user to print or export the current Setup Data Editor. | This module enables the user to print or export the current Setup Data Editor. | ||
− | 1. To print or export current Setup Data Editor Form, select '''Print/Export'''. A report PDF will be generated that the user may save or print. | + | 1. To print or export the current Setup Data Editor Form, select '''Print/Export'''. A report PDF will be generated that the user may save or print. |
| | ||
Line 165: | Line 162: | ||
| | ||
− | ==== <span class="mw-headline" id="Show_History.5Bedit.5D"><span class="mw-headline" id="Show_History">Show History</span></span> ==== | + | ==== <span class="mw-headline" id="Show_History"><span class="mw-headline" id="Show_History.5Bedit.5D"><span class="mw-headline" id="Show_History">Show History</span></span></span> ==== |
This module displays the Setup Data Editor history updates. | This module displays the Setup Data Editor history updates. | ||
Line 183: | Line 180: | ||
| | ||
− | === <span class="mw-headline" id="Save.2FPublish.5Bedit.5D"><span class="mw-headline" id="Save.2FPublish">Save/Publish</span></span> === | + | === <span class="mw-headline" id="Save.2FPublish"><span class="mw-headline" id="Save.2FPublish.5Bedit.5D"><span class="mw-headline" id="Save.2FPublish">Save/Publish</span></span></span> === |
The Save/Publish Conduit-based function at the bottom of the Attribute Step List screen is available to users with the appropriate permissions and can be used by selecting the down arrow adjacent to the Save button. Whereas Save gives the record a pending status relative to Conduit, Save/Publish saves the record and publishes it to Conduit. | The Save/Publish Conduit-based function at the bottom of the Attribute Step List screen is available to users with the appropriate permissions and can be used by selecting the down arrow adjacent to the Save button. Whereas Save gives the record a pending status relative to Conduit, Save/Publish saves the record and publishes it to Conduit. | ||
Line 195: | Line 192: | ||
| | ||
− | == <span class="mw-headline" id="Appendix_A.5Bedit.5D"><span class="mw-headline" id="Appendix_A">Appendix A</span></span> == | + | == <span class="mw-headline" id="Appendix_A"><span class="mw-headline" id="Appendix_A.5Bedit.5D"><span class="mw-headline" id="Appendix_A">Appendix A</span></span></span> == |
<br/> <br/> '''FES'''<br/> Factory Execution Systems<br/> <br/> '''LDAP'''<br/> Lightweight Directory Access Protocol<br/> <br/> '''Mfg'''<br/> Manufacturing<br/> <br/> '''MES'''<br/> Manufacturing Execution Systems<br/> <br/> '''PRAC'''<br/> Process Access<br/> <br/> '''SFDC'''<br/> Shop Floor Data Collection<br/> <br/> '''SPC'''<br/> Statistical Process Control<br/> <br/> '''SQC'''<br/> Statistical Quality Control<br/> | <br/> <br/> '''FES'''<br/> Factory Execution Systems<br/> <br/> '''LDAP'''<br/> Lightweight Directory Access Protocol<br/> <br/> '''Mfg'''<br/> Manufacturing<br/> <br/> '''MES'''<br/> Manufacturing Execution Systems<br/> <br/> '''PRAC'''<br/> Process Access<br/> <br/> '''SFDC'''<br/> Shop Floor Data Collection<br/> <br/> '''SPC'''<br/> Statistical Process Control<br/> <br/> '''SQC'''<br/> Statistical Quality Control<br/> | ||
− | == <span class="mw-headline" id="Appendix_B.5Bedit.5D"><span class="mw-headline" id="Appendix_B">Appendix B</span></span> == | + | == <span class="mw-headline" id="Appendix_B"><span class="mw-headline" id="Appendix_B.5Bedit.5D"><span class="mw-headline" id="Appendix_B">Appendix B</span></span></span> == |
'''Glossary''' | '''Glossary''' | ||
Line 221: | Line 218: | ||
'''''Shop Floor Configuration''''' | '''''Shop Floor Configuration''''' | ||
− | The rules used to define how Shop Floor collects data provides analysis, controls the processing and maintains unit histories | + | The rules used to define how Shop Floor collects data provides analysis, controls the processing, and maintains unit histories |
'''''Site Minder''''' | '''''Site Minder''''' | ||
Line 231: | Line 228: | ||
The username is the SiteMinder username (or a partial string) | The username is the SiteMinder username (or a partial string) | ||
− | + | ---- | |
− | |||
− | |||
| | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 18:01, 18 August 2021
42Q Home > Shop Floor Control > Configuration > Data Editor Maintenance
This edition applies to MES15 portal V1.0 and all subsequent releases and modifications until otherwise indicated in new revisions.
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).
Data Editor Maintenance
Data Editor Maintenance provides access to the Shop Floor configuration file that defines (but is not limited to) PCC ports, Options Lines, Auto Commands, Macros, Serial Input Masking, Passwords, and Device Numbers.
To access the Data Editor, select Shop Floor Control>Configuration>Shop Floor Configuration>Data Editor
Figure 1: MES Data Editor Maintenance
Note: A user only has access to the modules assigned to his/her profile.
The Setup Data Editor screen is displayed.
Figure 2: Setup Data Editor Shop Floor ID List
Setup Data Editor Shop Floor ID List.jpg
The user can edit, clear Data Editor, Publish History, and Print/Export the data.
Filter Setup Data Editor by Shop Floor ID
This module enables the user to filter by Shop Floor ID.
1. Enter the desired Shop Floor ID into the appropriate field, and then select Filter. The filtered Shop Floor ID is now displayed.
Figure 3: Shop Floor ID List - Find
Editing with the Setup Data Editor
This module enables the user to edit using the Setup Data Editor.
1. To edit using Setup Data Editor, select the data editor to be edited and select Edit. The Setup Data Editor Form for the selected Shop Floor ID is now displayed.
Figure 4: Shop Floor ID List – Edit Setup Data Editor
Shop Floor ID List – Edit Setup Data Editor
Figure 5: Setup Data Editor Form
Note: To add a new tab, create an entry line by entering "# SECTION" + section name.
For example: # SECTION MULTIPASS
2. Enter the desired modifications to the Setup Data Editor Form.
Note: If multiple users have opened the Setup Data Editor for the same SFDC PC line, only the first user to open the file has to write access. Other users are notified that the SDE is locked for editing by another user and that read-only access is allowed.
Copy Setup Data Editor from Other Shop Floor ID
This module replaces the contents of the current Setup Data Editor Form with data copied from another Shop Floor ID.
1. To copy data from another Shop Floor ID, open the target Shop Floor IDs Setup Data Editor and select Copy Data from Other Shop Floor ID in the Tasks window. The Choose a Shop Floor ID window is now displayed.
Figure 7: Copy Data from Other Shop Floor ID
Figure 7 Copy Data from Other Shop Floor ID.jpg
2. Select the Shop Floor ID to copy and select Save to install the Setup Data Editor. The Setup Data Editor is now updated with the data from the selected Shop Floor ID.
Figure 8: Install
DE_Install
3. Select Yes to confirm the install, or select No to cancel.
Note: The application saves a backup file on the MES server every time the user installs a Setup Data Editor.
Publish History
The Publish History functionality is used by permitted users to show and publish the action history of a Route. To use this functionality
- Select a route from the list. The Publish History function becomes available for selection.
- Select Publish History. The Publish History window pops up for the given route. This history shows the Action, Status, Time/Date, and User for each item.
- Select Publish, to publish the history to the Conduit. Select Close to end or abort.
Figure 9: Publish History
SFID Publish History Function.png
Print/Export Current Setup Data Editor
This module enables the user to print or export the current Setup Data Editor.
1. To print or export the current Setup Data Editor Form, select Print/Export. A report PDF will be generated that the user may save or print.
Figure 10: Print/Export Current Editor
Figure 11: Print/Export Report
Show History
This module displays the Setup Data Editor history updates.
1. To show the history, select Show History. The Setup Data Backup Files pop-up is now displayed.
Figure 12: Show History
FIgure 11 Show History.jpg
2. Select the Restore Setup Data icon to restore the data or to save it locally, then select the Download Setup Data icon.
Save/Publish
The Save/Publish Conduit-based function at the bottom of the Attribute Step List screen is available to users with the appropriate permissions and can be used by selecting the down arrow adjacent to the Save button. Whereas Save gives the record a pending status relative to Conduit, Save/Publish saves the record and publishes it to Conduit.
Figure 13: Save/Publish - Conduit Function
Appendix A
FES
Factory Execution Systems
LDAP
Lightweight Directory Access Protocol
Mfg
Manufacturing
MES
Manufacturing Execution Systems
PRAC
Process Access
SFDC
Shop Floor Data Collection
SPC
Statistical Process Control
SQC
Statistical Quality Control
Appendix B
Glossary
Access Control
A module that will set the permissions for users and external customers of 42Q
Administrator
the System Administrator has full access - all plants, all reports, all users.
Component
A component is a specific piece of data that appears on a label, for example, barcode, part numbers, graphic images, line, or text. Hence, label components are broken down into several different types: text, graphic images, MES database values, or a combination of text and database values.
Framework
In software development, a framework is a defined support structure in which another software project can be organized and developed. A framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project.
Shop Floor Configuration
The rules used to define how Shop Floor collects data provides analysis, controls the processing, and maintains unit histories
Site Minder
Universal login of 42Q
Username
The username is the SiteMinder username (or a partial string)