Difference between revisions of "SOP-42Q-MES0005 Data Editor Maintenance"
Line 1: | Line 1: | ||
− | |||
− | <br> | + | <small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Shop_Floor_Control|Shop Floor Control]] > [[Configuration|Configuration]] > Data Editor Maintenance</small><br/> [[File:42Q Logo.jpg|RTENOTITLE]] |
− | <center>'''SFDC Configuration''' </center> <center>'''Data Editor''' </center> <center>'''Version MES15 Portal 1.0''' </center> <center>'''Work Instruction''' </center> | + | |
− | + | | |
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | <center>'''SFDC Configuration'''</center> <center>'''Data Editor'''</center> <center>'''Version MES15 Portal 1.0'''</center> <center>'''Work Instruction'''</center> | ||
+ | | ||
<center>This Work Instruction is 42Q's corporate standard.</center> <center>This document is under revision control. The latest revision is located on Intranet.</center> <center>Once printed it is an uncontrolled copy. All alterations to this work instruction require approval.</center> <center>Contact the IT Global Education and Training Department to submit suggested alterations and or updates.</center> | <center>This Work Instruction is 42Q's corporate standard.</center> <center>This document is under revision control. The latest revision is located on Intranet.</center> <center>Once printed it is an uncontrolled copy. All alterations to this work instruction require approval.</center> <center>Contact the IT Global Education and Training Department to submit suggested alterations and or updates.</center> | ||
− | ''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.'' |
− | + | | |
− | == SFDC Configuration | + | == SFDC 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). | + | 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). |
− | To access SFDC Configuration, navigate to '''Shop Floor Control <nowiki>></nowiki> | + | To access SFDC Configuration, navigate to '''Shop Floor Control''' |
+ | <nowiki>></nowiki> | ||
− | ''' | + | '''Configuration''' |
+ | <nowiki>></nowiki> | ||
− | + | '''SFDC Configuration'''. The main SFDC Configuration page is displayed: | |
− | + | '''Figure 1: MES Portal – SFDC Configuration Sub-modules''' | |
− | + | [[File:SOP-5-I-MDS0032-C RA1 MDS Data Editor 01.jpg|700px|SOP-5-I-MDS0032-C RA1 MDS Data Editor 01.jpg]] | |
− | + | | |
− | + | '''<u>NOTE</u>''': A user only has access to the modules assigned to his/her profile. | |
− | + | | |
− | + | == Data Editor Maintenance == | |
− | + | Data Editor Maintenance provides access to the SFDC 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 '''Data Editor '''in the SFDC Configuration main menu. | |
− | ''' | + | The '''Setup Data Editor '''screen is displayed. |
− | + | | |
− | + | '''Figure 2: Setup Data Editor Shop Floor ID List''' | |
− | + | [[File:Figure 2 Data Editor Shop Floor ID List.jpg|700px|Figure 2 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 SFDC ID === | |
− | + | This module enables the user to filter by SFDC ID. | |
− | ''' | + | 1. Enter the desired SFDC ID into appropriate field, and then select '''Filter'''. The filtered Shop Floor ID is now displayed. |
− | + | | |
− | <br> | + | '''Figure 3: Shop Floor ID List - Find'''<br/> |
− | + | [[File:Figure3 Data Editor Shop Floor IDFilter.jpg|700px|Figure3 Data Editor Shop Floor IDFilter.jpg]] | |
− | + | | |
− | + | | |
− | + | === 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. | |
− | + | <br/> '''Figure 4: Shop Floor ID List – Edit Setup Data Editor''' | |
− | + | [[File:Figure4 Data Editor Shop Floor ID Edit.jpg|700px|Figure4 Data Editor Shop Floor ID Edit.jpg]] | |
− | + | <br/> '''Figure 5: Setup Data Editor Form''' | |
− | + | [[File:Figure 5 Setup Data Editor Form.jpg|700px|Figure 5 Setup Data Editor Form.jpg]] | |
− | '''<u>NOTE:</u>''' | + | <br/> '''<u>NOTE:</u>''' To add a new tab, create an entry line by entering "# SECTION" |
+ | <nowiki>+</nowiki> | ||
− | + | section name. | |
− | + | For example: # SECTION MULTIPASS | |
− | + | 2. Enter the desired modifications to the Setup Data Editor Form. | |
− | + | '''<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 write access. Other users are notified that the SDE is locked for editing by another user and that read-only access is allowed. | |
− | + | | |
− | + | '''Figure 6: SDE Read-Only State'''<br/> [[File:Figure 6 SDE Read-Only State.jpg|700px|Figure 6 SDE Read-Only State.jpg]] | |
− | + | | |
− | + | ==== 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 ID |
+ | <nowiki>’</nowiki> | ||
− | + | s 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''' | |
− | + | [[File:Figure 7 Copy Data from Other Shop Floor ID.jpg|700px|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. | |
− | <br> | + | <br/> '''Figure 8: Install'''<br/> [[File:Figure 8 Install.jpg|700px|Figure 8 Install.jpg]] |
− | + | | |
− | The Publish History functionality is used by permitted users to show and publish the action history of a Route. To use this functionality | + | |
+ | |||
+ | 3. Select '''Yes''' to confirm the install, or select '''No''' to cancel. | ||
+ | |||
+ | <br/> '''<u>NOTE:</u>''' The application saves a backup file on the MES server every time 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 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 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 Conduit. Select '''Close''' to end or abort. | + | #Select '''Publish''', to publish the history to Conduit. Select '''Close''' to end or abort. |
− | + | | |
− | '''Figure 9: Publish History''' | + | '''Figure 9: Publish History''' |
− | [[ | + | [[File:42Q Publish History.png|SFID Publish History Function.png]]<br/> |
− | ==== Print/Export Current Setup Data Editor | + | ==== Print/Export Current Setup Data Editor ==== |
− | 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 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 10: Print/Export Current Editor''' |
− | [[ | + | [[File:Figure10 Data Editor Shop Floor ID Print Export.jpg|700px|Figure10 Data Editor Shop Floor ID Print Export.jpg]] |
− | + | | |
− | + | | |
− | '''Figure 11: Print/Export Report''' | + | '''Figure 11: Print/Export Report''' |
− | [[ | + | [[File:Figure 10 Print Export Report.jpg|700px|Figure 10 Print Export Report.jpg]] |
− | + | | |
− | + | | |
− | ==== Show History | + | ==== Show History ==== |
− | This module displays the Setup Data Editor history updates. | + | 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. | + | 1. To show the history, select '''Show History'''. The '''Setup Data Backup Files''' pop-up is now displayed. |
− | + | | |
− | '''Figure 12: Show History'''<br> [[ | + | '''Figure 12: Show History'''<br/> [[File:FIgure 11 Show History.jpg|700px|FIgure 11 Show History.jpg]] |
− | + | | |
− | + | | |
− | 2. Select the '''Restore Setup Data''' icon to restore the data or to save it locally, then select '''Download Setup Data''' icon. | + | 2. Select the '''Restore Setup Data''' icon to restore the data or to save it locally, then select '''Download Setup Data''' icon. |
− | + | | |
− | === Save/Publish | + | === 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. | + | 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''' | + | '''Figure 13: Save/Publish - Conduit Function''' |
− | [[ | + | [[File:Step List Save Publish.JPG|150px|Step List Save Publish.JPG]] |
− | + | | |
− | == Appendix A | + | == Appendix A == |
− | {| | + | {| cellpadding="10" cellspacing="0" style="border-style:solid; border-color:black; border-width:1px;" |
|- | |- | ||
− | | '''COPS''' | + | | '''COPS''' |
− | Customer Order Processing System<br> <br> '''FES'''<br> Factory Execution Systems<br> <br> '''MDS'''<br> New Manufacturing Data System (Java technology)<br> <br> '''GLAD'''<br> Global Administration<br> <br> '''LDAP'''<br> Lightweight Directory Access Protocol<br> <br> '''Mfg'''<br> Manufacturing<br> <br> '''MES'''<br> Manufacturing Execution Systems<br> <br> '''MDS'''<br> Manufacturing Data System<br> <br> '''PRAC'''<br> Process Access<br> <br> '''SFDC'''<br> Shop Data Floor Collection<br> <br> '''SPC'''<br> Statistical Process Control<br> <br> '''SQC'''<br> Statistical Quality Control<br> <br> | + | Customer Order Processing System<br/> <br/> '''FES'''<br/> Factory Execution Systems<br/> <br/> '''MDS'''<br/> New Manufacturing Data System (Java technology)<br/> <br/> '''GLAD'''<br/> Global Administration<br/> <br/> '''LDAP'''<br/> Lightweight Directory Access Protocol<br/> <br/> '''Mfg'''<br/> Manufacturing<br/> <br/> '''MES'''<br/> Manufacturing Execution Systems<br/> <br/> '''MDS'''<br/> Manufacturing Data System<br/> <br/> '''PRAC'''<br/> Process Access<br/> <br/> '''SFDC'''<br/> Shop Data Floor Collection<br/> <br/> '''SPC'''<br/> Statistical Process Control<br/> <br/> '''SQC'''<br/> Statistical Quality Control<br/> <br/> |
|} | |} | ||
− | + | | |
− | + | | |
− | == Appendix B | + | == Appendix B == |
− | '''Glossary''' | + | '''Glossary''' |
− | '''''Access Control''''' | + | '''''Access Control''''' |
− | A module that will set the permissions for users and external customers of 42Q | + | A module that will set the permissions for users and external customers of 42Q |
− | '''''Administrator''''' | + | '''''Administrator''''' |
− | the System Administrator has full access - all plants, all reports, all users. | + | the System Administrator has full access - all plants, all reports, all users. |
− | '''''Component''''' | + | '''''Component''''' |
− | A component is a specific piece of data that appears on a label, for example: bar code, part numbers, graphic images, line or text. Hence, label components are broken down into several different types: text, graphic images, MDS database values, or a combination of text and database values. | + | A component is a specific piece of data that appears on a label, for example: bar code, part numbers, graphic images, line or text. Hence, label components are broken down into several different types: text, graphic images, MDS database values, or a combination of text and database values. |
− | '''''Framework''''' | + | '''''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. | + | 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. |
− | '''''SFDC Configuration''''' | + | '''''SFDC Configuration''''' |
− | The rules used to define how SFDC collects data, provides analysis, controls processing and maintains unit histories | + | The rules used to define how SFDC collects data, provides analysis, controls processing and maintains unit histories |
− | '''''Site Minder''''' | + | '''''Site Minder''''' |
− | ''Universal login of 42Q'' | + | ''Universal login of 42Q'' |
− | '''''Username''''' | + | '''''Username''''' |
− | The username is the siteminder username (or a partial string) | + | The username is the siteminder username (or a partial string) |
− | + | | |
− | == Document Revision History | + | == Document Revision History == |
− | {| border="2" | + | {| border="2" cellpadding="4" cellspacing="0" width="100%" |
|- | |- | ||
− | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Date</font> | + | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Date</font> |
− | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Author</font> | + | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Author</font> |
− | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Title</font> | + | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Title</font> |
− | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Version</font> | + | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Version</font> |
− | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Change Reference</font> | + | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Change Reference</font> |
| align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Approved by</font> | | align="center" bgcolor="#00FFFF" | <font color="#FFFFFF">Approved by</font> | ||
|- | |- | ||
− | | 08/14/13 | + | | 08/14/13 |
− | | Elaine Fonaro | + | | Elaine Fonaro |
− | | Technical Writer | + | | Technical Writer |
− | | v 1.0 | + | | v 1.0 |
− | | This is the first revision of MDS User<nowiki>’</nowiki>s Guide | + | | This is the first revision of MDS User <nowiki>’</nowiki> |
+ | s Guide | ||
|- | |- | ||
− | | 03/17/14 | + | | 03/17/14 |
− | | Ashley Martin | + | | Ashley Martin |
− | | Technical Writer | + | | Technical Writer |
− | | v 1.0 | + | | v 1.0 |
| Review and added the new function Map Defect X Process | | Review and added the new function Map Defect X Process | ||
|- | |- | ||
− | | 03/17/14 | + | | 03/17/14 |
− | | Elaine Fonaro | + | | Elaine Fonaro |
− | | Technical Writer | + | | Technical Writer |
− | | v 1.0 | + | | v 1.0 |
| Review and format for WIKI | | Review and format for WIKI | ||
|- | |- | ||
− | | 04/3/17 | + | | 04/3/17 |
− | | Martha Jordan | + | | Martha Jordan |
− | | Technical Writer | + | | Technical Writer |
− | | v 1.0 | + | | v 1.0 |
− | | Rewrite SFDC introductory paragraph according to current 42Q functionality | + | | Rewrite SFDC introductory paragraph according to current 42Q functionality |
| Bob Moss | | Bob Moss | ||
+ | |- | ||
+ | | 02/06/2018 | ||
+ | | Elaine Fonaro | ||
+ | | Technical Writer | ||
+ | | v 1.0 | ||
+ | | Updated images 02,03,04,10 to reflect the Conduit icon and updated Introduction for 42-q. | ||
|} | |} | ||
[[Category:Uncategorized]] | [[Category:Uncategorized]] |
Revision as of 17:32, 6 February 2018
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.
Contents
SFDC 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).
To access SFDC Configuration, navigate to Shop Floor Control >
Configuration >
SFDC Configuration. The main SFDC Configuration page is displayed:
Figure 1: MES Portal – SFDC Configuration Sub-modules
NOTE: A user only has access to the modules assigned to his/her profile.
Data Editor Maintenance
Data Editor Maintenance provides access to the SFDC 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 Data Editor in the SFDC Configuration main menu.
The Setup Data Editor screen is displayed.
Figure 2: Setup Data Editor Shop Floor ID List
The user can edit, clear Data Editor, Publish History and Print/Export the data.
Filter Setup Data Editor by SFDC ID
This module enables the user to filter by SFDC ID.
1. Enter the desired SFDC ID into 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
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 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 ID ’
s 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.
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 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 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 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 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
COPS
Customer Order Processing System |
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: bar code, part numbers, graphic images, line or text. Hence, label components are broken down into several different types: text, graphic images, MDS 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.
SFDC Configuration
The rules used to define how SFDC collects data, provides analysis, controls processing and maintains unit histories
Site Minder
Universal login of 42Q
Username
The username is the siteminder username (or a partial string)
Document Revision History
Date | Author | Title | Version | Change Reference | Approved by |
08/14/13 | Elaine Fonaro | Technical Writer | v 1.0 | This is the first revision of MDS User ’
s Guide | |
03/17/14 | Ashley Martin | Technical Writer | v 1.0 | Review and added the new function Map Defect X Process | |
03/17/14 | Elaine Fonaro | Technical Writer | v 1.0 | Review and format for WIKI | |
04/3/17 | Martha Jordan | Technical Writer | v 1.0 | Rewrite SFDC introductory paragraph according to current 42Q functionality | Bob Moss |
02/06/2018 | Elaine Fonaro | Technical Writer | v 1.0 | Updated images 02,03,04,10 to reflect the Conduit icon and updated Introduction for 42-q. |