Difference between revisions of "SOP-42Q-MES0009 Mfg Line Maintenance"
(Created page with "130px <center>'''SFDC Configuration''' </center> <center>'''Mfg Line Maintenance''' </center> <center>'''Version MDS Portal xx-x''' </center> <cent...") |
|||
Line 6: | Line 6: | ||
<center>'''Mfg Line Maintenance''' </center> | <center>'''Mfg Line Maintenance''' </center> | ||
− | <center>'''Version MDS Portal | + | <center>'''Version MDS Portal 1.0''' </center> |
<center>'''Work Instruction''' </center> | <center>'''Work Instruction''' </center> | ||
Line 19: | Line 19: | ||
<center>Contact the IT Global Education and Training Department to submit suggested alterations and or updates.</center> | <center>Contact the IT Global Education and Training Department to submit suggested alterations and or updates.</center> | ||
− | ''This edition applies to MDS Portal | + | ''This edition applies to MDS Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.'' |
Line 29: | Line 29: | ||
SFDC provides real-time information used by SPC/SQC and MESWeb to create quality control reports. The data configuration for SFDC PC is handled within the Manufacturing Data System (MDS), which is a complete factory automation system. The SFDC System uses barcode scanning, both manual and automated, to monitor and control a single product line or an entire plant. SFDC Configuration collects data, provides analysis, maintains unit histories, and controls product movement on the manufacturing floor. | SFDC provides real-time information used by SPC/SQC and MESWeb to create quality control reports. The data configuration for SFDC PC is handled within the Manufacturing Data System (MDS), which is a complete factory automation system. The SFDC System uses barcode scanning, both manual and automated, to monitor and control a single product line or an entire plant. SFDC Configuration collects data, provides analysis, maintains unit histories, and controls product movement on the manufacturing floor. | ||
+ | |||
− | + | ===Mfg Line Maintenance=== | |
− | + | This functionality enables the user associate Data Collector Locations to a Manufacturing Line for use with the SOMS system. | |
− | |||
− | == Mfg Line Maintenance == | ||
− | This functionality enables the user associate Data Collector Locations to a Manufacturing Line for use with the SOMS system | ||
− | |||
− | |||
− | |||
+ | To access the Mfg Line list, click on '''Mfg Line '''module in the main SFDC Configuration menu. | ||
'''Figure 1: Mfg Line List''' | '''Figure 1: Mfg Line List''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_01.png|thumb|none|624px]] |
− | + | ====Add Mfg Lines==== | |
− | === Add Mfg Lines | ||
This functionality enables the user to add Mfg Lines configurations into database. | This functionality enables the user to add Mfg Lines configurations into database. | ||
− | |||
To add Mfg Lines, click the '''Add''' icon. | To add Mfg Lines, click the '''Add''' icon. | ||
− | |||
'''Figure 2: Mfg Line - Add''' | '''Figure 2: Mfg Line - Add''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_02.png|thumb|none|624px]] |
− | |||
The Mfg Line form is displayed: | The Mfg Line form is displayed: | ||
Line 62: | Line 54: | ||
'''Figure 3: Mfg Line Form''' | '''Figure 3: Mfg Line Form''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_03.png|thumb|none|623px]] |
+ | To add or edit a Manufacturing Line fill the name and the site id fields. If it is a Wip Location Line, at least one location must be assigned; if not the pixel X and the pixel Y, and at least one scanner must be assigned. | ||
− | + | The name must be created according the following rules: | |
+ | * 2 chars for Level or Modules (areas of interests) - Ex: L1; M2 | ||
+ | * 2 chars to group Process Lines - Ex: L110; M250 | ||
+ | * 1 char with "_" <nowiki>+</nowiki> Process Name <nowiki>+</nowiki> 1 char with "_" - Ex: L110_SMT_; M250_PTH_ | ||
+ | * Line name - Ex: L110_SMT_Line1; M250_PTH_Line2. | ||
+ | '''Note''': If the Mfg Line is Wip Location Line, the name must ends with "WIP". | ||
− | + | The Site Id can be changed if in Miscellaneous Configuration all Site Id references were updated. If it is a Wip Location Line, it will not possible to create Escalation for this Mfg Line. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | The Site Id can be changed if in Miscellaneous Configuration all Site Id references were updated. If it is a Wip Location Line, it will not possible to create Escalation for this Mfg Line. | ||
− | |||
'''Man Power''', '''Work Hour''', '''Min Sample Size''', fields are going to be enabled only after the user select the Mfg Line field. | '''Man Power''', '''Work Hour''', '''Min Sample Size''', fields are going to be enabled only after the user select the Mfg Line field. | ||
− | |||
'''Note''': The '''Man Power '''and '''Work Hour''' fields will be used in the MES Web reports. | '''Note''': The '''Man Power '''and '''Work Hour''' fields will be used in the MES Web reports. | ||
+ | '''Adding Escalation E-mails:''' | ||
− | + | Escalation e-mails will be added by the full e-mail address and clicking on '''Add''' button. The Escalation Emails allow adding 4 levels of send emails, the level tab will just be enabled if the previous one has at least one email added. | |
− | |||
− | Escalation e-mails will be added by the full e-mail address and clicking on '''Add''' button. The Escalation Emails allow adding 4 levels of send emails, the level tab will just be enabled if the previous one has at least one email added. | ||
− | |||
'''Figure 4: Escalation''' | '''Figure 4: Escalation''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_04.png|thumb|none|624px]] |
+ | <font color="#0000FF">'''Using the available filters:''' | ||
− | + | To use the filter, follow the rules below: | |
− | + | * To filter by Location in the Location list, enter the Location name. Ex: 1FCT. | |
− | + | * To filter by Line in the Location list put the word line: before the Line name. Ex: 1FCT line:p99dcl. | |
− | * To filter by Location in the Location list, enter the Location name. Ex: 1FCT. | + | * To filter by Device in the Data Collector list, enter the Device number. Ex: 10. |
− | * To filter by Line in the Location list put the word line: before the Line name. Ex: 1FCT line:p99dcl. | ||
− | * To filter by Device in the Data Collector list, enter the Device number. Ex: 10. | ||
* To filter by NetUser in the Data Collector list put the word netuser: before the NetUser name. Ex: 10 netuser:p51dc3. | * To filter by NetUser in the Data Collector list put the word netuser: before the NetUser name. Ex: 10 netuser:p51dc3. | ||
+ | </font> | ||
'''Adding or Removing scanners:''' | '''Adding or Removing scanners:''' | ||
− | |||
'''Figure 5: Add/Remove Scanners''' | '''Figure 5: Add/Remove Scanners''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_05.png|thumb|none|624px]] |
− | |||
To add scanners, select it from Available Scanners in the drop-down list. | To add scanners, select it from Available Scanners in the drop-down list. | ||
Line 118: | Line 100: | ||
To remove a specific one, select the desired scanner, click on Remove selected iem. | To remove a specific one, select the desired scanner, click on Remove selected iem. | ||
− | To remove all items, just click on '''Remove all items''' button. | + | To remove all items, just click on '''Remove all items''' button. |
Click '''Ok''' to save, or '''Cancel '''to cancel the operation. | Click '''Ok''' to save, or '''Cancel '''to cancel the operation. | ||
− | |||
'''NOTE''': The '''Location Tab''' allow to setup MFG lines by Locations, instead of scanners. (SOMS). | '''NOTE''': The '''Location Tab''' allow to setup MFG lines by Locations, instead of scanners. (SOMS). | ||
− | + | ====Edit Mfg Lines==== | |
− | === Edit Mfg Lines | ||
This functionality enables the user to modify Mfg Line configuration. The rules for editing are the same rules for adding. For further information, see the ''Add Mfg Line'' section. | This functionality enables the user to modify Mfg Line configuration. The rules for editing are the same rules for adding. For further information, see the ''Add Mfg Line'' section. | ||
− | + | To edit Mfg Lines, select the desired line, and then click the '''Edit''' button in the list. | |
− | To edit Mfg Lines, select the desired line, and then click the '''Edit''' button in the list. | ||
− | |||
'''Figure 6: Mfg Line List – Edit''' | '''Figure 6: Mfg Line List – Edit''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_06.png|thumb|none|624px]] |
− | |||
− | Perform the desired updates in the Mfg Line Form. | + | Perform the desired updates in the Mfg Line Form. |
− | The rules to edit, are the same for add. For more information, | + | The rules to edit, are the same for add. For more information, see '''Add Mfg Line '''topic. |
Click '''Ok''' to confirm, or click '''No''' to cancel the update action. | Click '''Ok''' to confirm, or click '''No''' to cancel the update action. | ||
− | === Delete Mfg Lines | + | ====Delete Mfg Lines==== |
− | This functionality enables the user to delete a existing Mfg Line configuration. It is only possible to delete a mfg Line if it doesn | + | This functionality enables the user to delete a existing Mfg Line configuration. It is only possible to delete a mfg Line if it doesn<nowiki>’</nowiki>t have any Data Collector Locations associated to it. The user must first remove all associated Data Collector Locations from the Mfg Line configuration prior to deleting. |
− | |||
To delete a Mfg Line, select the desired Mfg Line, then click the '''Delete''' button. | To delete a Mfg Line, select the desired Mfg Line, then click the '''Delete''' button. | ||
− | |||
'''Figure 7: Mfg Line List - Delete''' | '''Figure 7: Mfg Line List - Delete''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_07.png|thumb|none|624px]] |
− | |||
A confirmation message is displayed: | A confirmation message is displayed: | ||
Line 160: | Line 134: | ||
Click '''Yes''' to confirm, or '''No''' to cancel the action. | Click '''Yes''' to confirm, or '''No''' to cancel the action. | ||
+ | ====Print/Export Filtered Mfg Lines==== | ||
+ | This functionality enables the user to print/export filtered Mfg Lines. | ||
− | + | To print filtered Mfg Lines, click the '''Print/Export Filtered Mfg Lines''' button. | |
− | |||
− | |||
− | |||
− | To print filtered Mfg Lines, click the '''Print Filtered Mfg Lines''' button. | ||
− | |||
− | |||
− | |||
− | + | '''Figure 8: Print/Export Filtered Mfg Line''' | |
+ | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_08.png|thumb|none|624px]] | ||
A report is generated and the user is able to save the file or print it. | A report is generated and the user is able to save the file or print it. | ||
+ | '''Figure 9: Print/Export Filtered Mfg Lines Result''' | ||
− | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_09.png|thumb|none|624px]] | |
− | |||
− | |||
− | |||
+ | A report is generated and the user is able to save the file or print it | ||
− | === Import Escalation Data === | + | ====Import Escalation Data==== |
To import escalation data, click on '''Import Escalation Data''' button. | To import escalation data, click on '''Import Escalation Data''' button. | ||
− | |||
'''Figure 10: Import Escalation Data''' | '''Figure 10: Import Escalation Data''' | ||
− | [[ | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_10.png|thumb|none|624px]] |
− | |||
Choose the .CVS file and save it. | Choose the .CVS file and save it. | ||
− | + | The CVS file has the following format: | |
− | The CVS file has the following format: | ||
SITE (String), LINE (Mfg Line name defined on precondition 2), x (Always empty), y (Always empty), x Pixels (Integer), y Pixels (Integer), Escalation 1, Escalation 2, Escalation 3 and Escalation 4 - see example bellow: | SITE (String), LINE (Mfg Line name defined on precondition 2), x (Always empty), y (Always empty), x Pixels (Integer), y Pixels (Integer), Escalation 1, Escalation 2, Escalation 3 and Escalation 4 - see example bellow: | ||
+ | E43_HO,M110_SMT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30 | ||
− | E43_HO, | + | E43_HO,M200_ICT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30 |
− | + | '''NOTE:''' CSV file format is the same currently in use by plants to maintaining SOMS Escalation and map coordinates. | |
+ | ====Export Escalation Data==== | ||
− | + | This functionality will export all escalation Data and save it in a zip file. | |
+ | '''Figure 11: Export Escalation Data''' | ||
− | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_11.png|thumb|none|624px]] | |
− | |||
+ | '''Figure 12: CSV file generated.''' | ||
− | + | [[Image:SOP-5-I-MDS0037-C_RA1_MDS_Mfg_Line_Maintenance_12.png|thumb|none|624px]] | |
− | + | Choose the local directory and click on''' Save''' button. The .zip file with the csv file will be saved locally. | |
+ | ==Appendix A== | ||
− | + | {|cellspacing="0" cellpadding = "10" style="border-style:solid; border-color:black; border-width:1px;" | |
+ | |COPS<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> | ||
+ | <br> | ||
+ | |} | ||
− | + | {|border="0" cellspacing="2" width="100%" | |
− | + | | | |
− | {| | + | | |
− | + | | | |
− | | | + | | |
+ | | | ||
+ | | | ||
|- | |- | ||
− | | | + | |colspan = "4"| |
− | + | | | |
− | + | | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | | | ||
− | |||
− | | | ||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
+ | ==Appendix B== | ||
− | |||
− | |||
'''Glossary''' | '''Glossary''' | ||
− | |||
'''''Access Control''''' | '''''Access Control''''' | ||
it is a module that will set the permissions for users and external customers of Sanmina | it is a module that will set the permissions for users and external customers of Sanmina | ||
− | |||
'''''administrator''''' | '''''administrator''''' | ||
the System Administration has full access - all plants, all reports, all users. | the System Administration 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 Sanmina'' | ''Universal login of Sanmina'' | ||
− | |||
'''''username''''' | '''''username''''' | ||
Line 310: | Line 273: | ||
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" cellspacing="0" cellpadding="4" width="100%" |
− | | | + | |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">Title</font> |
− | | | + | |align = "center" bgcolor = "#00FFFF"|<font color="#FFFFFF">Version</font> |
− | | | + | |align = "center" bgcolor = "#00FFFF"|<font color="#FFFFFF">Change Reference</font> |
|- | |- | ||
− | | | + | |08/16/13 |
− | + | |Elaine Fonaro | |
− | + | |Technical Writer | |
− | + | |v 1.0 | |
− | + | |This is the first revision of MDS User<nowiki>’</nowiki>s Guide | |
|} | |} |
Revision as of 19:22, 16 August 2013
This edition applies to MDS Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.
Contents
Introduction
The Shop Floor Data Collection System (SFDC) communicates interactively with the Customer Order Processing System (COPS), and Statistical Process Control/Statistical Quality Control (SPC/SQC). The Manufacturing Data System (MDS) makes the communication between these systems possible.
SFDC provides real-time information used by SPC/SQC and MESWeb to create quality control reports. The data configuration for SFDC PC is handled within the Manufacturing Data System (MDS), which is a complete factory automation system. The SFDC System uses barcode scanning, both manual and automated, to monitor and control a single product line or an entire plant. SFDC Configuration collects data, provides analysis, maintains unit histories, and controls product movement on the manufacturing floor.
Mfg Line Maintenance
This functionality enables the user associate Data Collector Locations to a Manufacturing Line for use with the SOMS system.
To access the Mfg Line list, click on Mfg Line module in the main SFDC Configuration menu.
Figure 1: Mfg Line List
Add Mfg Lines
This functionality enables the user to add Mfg Lines configurations into database.
To add Mfg Lines, click the Add icon.
Figure 2: Mfg Line - Add
The Mfg Line form is displayed:
Figure 3: Mfg Line Form
To add or edit a Manufacturing Line fill the name and the site id fields. If it is a Wip Location Line, at least one location must be assigned; if not the pixel X and the pixel Y, and at least one scanner must be assigned.
The name must be created according the following rules:
- 2 chars for Level or Modules (areas of interests) - Ex: L1; M2
- 2 chars to group Process Lines - Ex: L110; M250
- 1 char with "_" + Process Name + 1 char with "_" - Ex: L110_SMT_; M250_PTH_
- Line name - Ex: L110_SMT_Line1; M250_PTH_Line2.
Note: If the Mfg Line is Wip Location Line, the name must ends with "WIP".
The Site Id can be changed if in Miscellaneous Configuration all Site Id references were updated. If it is a Wip Location Line, it will not possible to create Escalation for this Mfg Line.
Man Power, Work Hour, Min Sample Size, fields are going to be enabled only after the user select the Mfg Line field.
Note: The Man Power and Work Hour fields will be used in the MES Web reports.
Adding Escalation E-mails:
Escalation e-mails will be added by the full e-mail address and clicking on Add button. The Escalation Emails allow adding 4 levels of send emails, the level tab will just be enabled if the previous one has at least one email added.
Figure 4: Escalation
Using the available filters:
To use the filter, follow the rules below:
- To filter by Location in the Location list, enter the Location name. Ex: 1FCT.
- To filter by Line in the Location list put the word line: before the Line name. Ex: 1FCT line:p99dcl.
- To filter by Device in the Data Collector list, enter the Device number. Ex: 10.
- To filter by NetUser in the Data Collector list put the word netuser: before the NetUser name. Ex: 10 netuser:p51dc3.
Adding or Removing scanners:
Figure 5: Add/Remove Scanners
To add scanners, select it from Available Scanners in the drop-down list.
To remove a specific one, select the desired scanner, click on Remove selected iem.
To remove all items, just click on Remove all items button.
Click Ok to save, or Cancel to cancel the operation.
NOTE: The Location Tab allow to setup MFG lines by Locations, instead of scanners. (SOMS).
Edit Mfg Lines
This functionality enables the user to modify Mfg Line configuration. The rules for editing are the same rules for adding. For further information, see the Add Mfg Line section.
To edit Mfg Lines, select the desired line, and then click the Edit button in the list.
Figure 6: Mfg Line List – Edit
Perform the desired updates in the Mfg Line Form.
The rules to edit, are the same for add. For more information, see Add Mfg Line topic.
Click Ok to confirm, or click No to cancel the update action.
Delete Mfg Lines
This functionality enables the user to delete a existing Mfg Line configuration. It is only possible to delete a mfg Line if it doesn’t have any Data Collector Locations associated to it. The user must first remove all associated Data Collector Locations from the Mfg Line configuration prior to deleting.
To delete a Mfg Line, select the desired Mfg Line, then click the Delete button.
Figure 7: Mfg Line List - Delete
A confirmation message is displayed:
Click Yes to confirm, or No to cancel the action.
Print/Export Filtered Mfg Lines
This functionality enables the user to print/export filtered Mfg Lines.
To print filtered Mfg Lines, click the Print/Export Filtered Mfg Lines button.
Figure 8: Print/Export Filtered Mfg Line
A report is generated and the user is able to save the file or print it.
Figure 9: Print/Export Filtered Mfg Lines Result
A report is generated and the user is able to save the file or print it
Import Escalation Data
To import escalation data, click on Import Escalation Data button.
Figure 10: Import Escalation Data
Choose the .CVS file and save it.
The CVS file has the following format:
SITE (String), LINE (Mfg Line name defined on precondition 2), x (Always empty), y (Always empty), x Pixels (Integer), y Pixels (Integer), Escalation 1, Escalation 2, Escalation 3 and Escalation 4 - see example bellow:
E43_HO,M110_SMT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30
E43_HO,M200_ICT_Line_1,,,100,200,e-mail;email;-1-3-30,e-mail;-4-5-30,e-mail;-6-10-30,e-mail;-10-15-30
NOTE: CSV file format is the same currently in use by plants to maintaining SOMS Escalation and map coordinates.
Export Escalation Data
This functionality will export all escalation Data and save it in a zip file.
Figure 11: Export Escalation Data
Figure 12: CSV file generated.
Choose the local directory and click on Save button. The .zip file with the csv file will be saved locally.
Appendix A
COPS Customer Order Processing System |
Appendix B
Glossary
Access Control
it is a module that will set the permissions for users and external customers of Sanmina
administrator
the System Administration 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 Sanmina
username
the username is the siteminder username (or a partial string)
Document Revision History
Date | Author | Title | Version | Change Reference |
08/16/13 | Elaine Fonaro | Technical Writer | v 1.0 | This is the first revision of MDS User’s Guide |