Difference between revisions of "SOP-42Q-MES0055 MESWeb Reports"
Line 10: | Line 10: | ||
''This edition applies to MES15 Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.'' | ''This edition applies to MES15 Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.'' | ||
− | = <br/> <font size="4">'''Introduction'''</font> = | + | = <br/> <span class="mw-headline" id="Introduction"><font size="4">'''Introduction'''</font></span> = |
MESWeb is a powerful business intelligence application designed from the ground up to simplify reporting from manufacturing execution systems and to empower end users with a streamlined and full-featured web interface. The application includes an "ad hoc report" design tool that allows users to create basic, customized reports from heterogeneous data sources. | MESWeb is a powerful business intelligence application designed from the ground up to simplify reporting from manufacturing execution systems and to empower end users with a streamlined and full-featured web interface. The application includes an "ad hoc report" design tool that allows users to create basic, customized reports from heterogeneous data sources. | ||
Line 38: | Line 38: | ||
*ODBC | *ODBC | ||
− | == Access Level == | + | == <span class="mw-headline" id="Access_Level">Access Level</span> == |
MESWeb has five distinct access levels: | MESWeb has five distinct access levels: | ||
Line 48: | Line 48: | ||
*User (Execution Module only) Section Name | *User (Execution Module only) Section Name | ||
− | === Administrator (System Administrator) === | + | === <span class="mw-headline" id="Administrator_.28System_Administrator.29">Administrator (System Administrator)</span> === |
The System Administrator has full access to MESWeb Central and Execution – all plants, all reports, all customers. Basically, Administrator access includes the capabilities of all of the levels (Security Manager, Report Manager, and Data Source Manager). This access will be given to BSAs and global support personnel. An administrator can perform the following functions: | The System Administrator has full access to MESWeb Central and Execution – all plants, all reports, all customers. Basically, Administrator access includes the capabilities of all of the levels (Security Manager, Report Manager, and Data Source Manager). This access will be given to BSAs and global support personnel. An administrator can perform the following functions: | ||
Line 61: | Line 61: | ||
*Manage permissions for all MESWeb locations | *Manage permissions for all MESWeb locations | ||
− | === Security Manager (Local Administrator) === | + | === <span class="mw-headline" id="Security_Manager_.28Local_Administrator.29">Security Manager (Local Administrator)</span> === |
The Security Manager has full access to the plant(s) where he/she has been designated as local Administrator for the MESWeb tool. The main responsibilities of this role are to organize permissions and manage customers. A Security Manager is able to: | The Security Manager has full access to the plant(s) where he/she has been designated as local Administrator for the MESWeb tool. The main responsibilities of this role are to organize permissions and manage customers. A Security Manager is able to: | ||
Line 70: | Line 70: | ||
*Manage customers (add customers and map part numbers to them) | *Manage customers (add customers and map part numbers to them) | ||
− | === Report Manager === | + | === <span class="mw-headline" id="Report_Manager">Report Manager</span> === |
The Report Manager has access to "Reports" and "Report Groups" modules in the specific location(s) where he/she was designed as Report Manager. Inside those modules, a Report Manager is able to: | The Report Manager has access to "Reports" and "Report Groups" modules in the specific location(s) where he/she was designed as Report Manager. Inside those modules, a Report Manager is able to: | ||
Line 82: | Line 82: | ||
*Add Reports to Report Groups | *Add Reports to Report Groups | ||
− | === Data Source Manager === | + | === <span class="mw-headline" id="Data_Source_Manager">Data Source Manager</span> === |
The Data Source Manager is responsible for creating and updating Data Sources and Data Source types. | The Data Source Manager is responsible for creating and updating Data Sources and Data Source types. | ||
Line 91: | Line 91: | ||
*Create, Edit, and Delete Data Source types | *Create, Edit, and Delete Data Source types | ||
− | === User (Execution Module only) Section Name === | + | === <span class="mw-headline" id="User_.28Execution_Module_only.29_Section_Name">User (Execution Module only) Section Name</span> === |
The User role is able to execute only those reports specifically granted access to him/her, and may not create new reports or modify existing reports. Administrators may restrict user access only to data belonging to specific customers and data sources. | The User role is able to execute only those reports specifically granted access to him/her, and may not create new reports or modify existing reports. Administrators may restrict user access only to data belonging to specific customers and data sources. | ||
− | = Getting Started with MESWeb Reports = | + | = <span class="mw-headline" id="Getting_Started_with_MESWeb_Reports">Getting Started with MESWeb Reports</span> = |
{| border="0" cellpadding="0" cellspacing="0" width="100%" | {| border="0" cellpadding="0" cellspacing="0" width="100%" | ||
Line 109: | Line 109: | ||
| | ||
− | = Accessing MESWeb Reports = | + | = <span class="mw-headline" id="Accessing_MESWeb_Reports">Accessing MESWeb Reports</span> = |
{| border="0" cellpadding="0" cellspacing="0" width="100%" | {| border="0" cellpadding="0" cellspacing="0" width="100%" | ||
Line 140: | Line 140: | ||
| | ||
− | = Parameters = | + | = <span class="mw-headline" id="Parameters">Parameters</span> = |
MESWeb has a collection of parameters highly configurable by the user to help filter the information. | MESWeb has a collection of parameters highly configurable by the user to help filter the information. | ||
− | == Dropdown list == | + | == <span class="mw-headline" id="Dropdown_list">Dropdown list</span> == |
This manages a list where only one single option is selected (see Figure 5 for an example). | This manages a list where only one single option is selected (see Figure 5 for an example). | ||
Line 152: | Line 152: | ||
[[File:MESWebExec05.png|800px|MESWebExec05.png]] | [[File:MESWebExec05.png|800px|MESWebExec05.png]] | ||
− | == Checkbox == | + | == <span class="mw-headline" id="Checkbox">Checkbox</span> == |
A checkbox is used for true/false parameters (see Figure 6 for an example). | A checkbox is used for true/false parameters (see Figure 6 for an example). | ||
Line 160: | Line 160: | ||
[[File:MESWebExec06.png|RTENOTITLE]] | [[File:MESWebExec06.png|RTENOTITLE]] | ||
− | == Radio Buttons == | + | == <span class="mw-headline" id="Radio_Buttons">Radio Buttons</span> == |
Radio buttons allow the user to select one (1) option from the list (see Figure 7). Every selectable option is mutually exclusive. This also can be used for showing different parameters. | Radio buttons allow the user to select one (1) option from the list (see Figure 7). Every selectable option is mutually exclusive. This also can be used for showing different parameters. | ||
Line 168: | Line 168: | ||
[[File:MESWebExec07.png|RTENOTITLE]] | [[File:MESWebExec07.png|RTENOTITLE]] | ||
− | == Date == | + | == <span class="mw-headline" id="Date">Date</span> == |
A date parameter is used to select a specific date. There is a variant that also allows the user to select a time. | A date parameter is used to select a specific date. There is a variant that also allows the user to select a time. | ||
Line 176: | Line 176: | ||
[[File:MESWebExec08.png|800px|MESWebExec08.png]] | [[File:MESWebExec08.png|800px|MESWebExec08.png]] | ||
− | == Date Range == | + | == <span class="mw-headline" id="Date_Range">Date Range</span> == |
Date range is a parameter that allows the user to select a range between two dates. There is a variant that also allows the user to select a time. | Date range is a parameter that allows the user to select a range between two dates. There is a variant that also allows the user to select a time. | ||
Line 184: | Line 184: | ||
[[File:DateRange1.png|RTENOTITLE]] | [[File:DateRange1.png|RTENOTITLE]] | ||
− | == Listbox == | + | == <span class="mw-headline" id="Listbox">Listbox</span> == |
In a listbox, multiple options can be selected (i.e., users can select every option in the "Available" list). Users can filter options by using the radio buttons "Starts With", "Contains", and "Ends With". After the user selects the necessary option, he/she enters text into the text box and then must select the [[File:Refresh.PNG|RTENOTITLE]] icon to refresh the list. | In a listbox, multiple options can be selected (i.e., users can select every option in the "Available" list). Users can filter options by using the radio buttons "Starts With", "Contains", and "Ends With". After the user selects the necessary option, he/she enters text into the text box and then must select the [[File:Refresh.PNG|RTENOTITLE]] icon to refresh the list. | ||
Line 200: | Line 200: | ||
[[File:MESWebExec10.png|RTENOTITLE]] | [[File:MESWebExec10.png|RTENOTITLE]] | ||
− | == Multi-Line Text Box == | + | == <span class="mw-headline" id="Multi-Line_Text_Box">Multi-Line Text Box</span> == |
The multi-line text box allows the user to add lines as necessary. | The multi-line text box allows the user to add lines as necessary. | ||
Line 208: | Line 208: | ||
[[File:MESWebExec11.png|800px|MESWebExec11.png]] | [[File:MESWebExec11.png|800px|MESWebExec11.png]] | ||
− | = Steps = | + | = <span class="mw-headline" id="Steps">Steps</span> = |
Steps mainly work as filters that are used to execute reports. A step contains x parameters and it may or may not be the parent of another subsequent step. For example, after the user selects a Customer, the Part Numbers related to the selected Customer are shown. | Steps mainly work as filters that are used to execute reports. A step contains x parameters and it may or may not be the parent of another subsequent step. For example, after the user selects a Customer, the Part Numbers related to the selected Customer are shown. | ||
− | = Results = | + | = <span class="mw-headline" id="Results">Results</span> = |
− | == Grids == | + | == <span class="mw-headline" id="Grids">Grids</span> == |
Once a report is executed, a grid with the results will appear on the right side. | Once a report is executed, a grid with the results will appear on the right side. | ||
Line 222: | Line 222: | ||
[[File:MESWebExec12.png|RTENOTITLE]] | [[File:MESWebExec12.png|RTENOTITLE]] | ||
− | == Selected Parameters == | + | == <span class="mw-headline" id="Selected_Parameters">Selected Parameters</span> == |
Selected parameters also appear down the side. These results contain other useful information such as the Application, the Execution Date, and the Execution Time. | Selected parameters also appear down the side. These results contain other useful information such as the Application, the Execution Date, and the Execution Time. | ||
Line 230: | Line 230: | ||
[[File:MESWebExec13.png|RTENOTITLE]] | [[File:MESWebExec13.png|RTENOTITLE]] | ||
− | == Actions == | + | == <span class="mw-headline" id="Actions">Actions</span> == |
There are three principal actions that can be done with the report s results: Print, Export, and Share. | There are three principal actions that can be done with the report s results: Print, Export, and Share. | ||
Line 236: | Line 236: | ||
| | ||
− | === Print === | + | === <span class="mw-headline" id="Print">Print</span> === |
This option allows the user to print the report. | This option allows the user to print the report. | ||
Line 258: | Line 258: | ||
| | ||
+ | | ||
− | === Export === | + | === <span class="mw-headline" id="Export">Export</span> === |
The Export button downloads a file to the user's PC. | The Export button downloads a file to the user's PC. | ||
Line 309: | Line 310: | ||
| | ||
− | === Share === | + | === <span class="mw-headline" id="Share">Share</span> === |
This option is used to share the report's results. The user can share the report via Email or as a Link. | This option is used to share the report's results. The user can share the report via Email or as a Link. | ||
Line 319: | Line 320: | ||
| | ||
− | == Drilldowns == | + | == <span class="mw-headline" id="Drilldowns">Drilldowns</span> == |
Drilldowns occur when a link is selected by the user in order to drill down or further expand the data. To access Drilldown reports, select the parent link. This report will generate another report using a parameter passed by the selected link from the first report. This second report will use the default configuration (i.e., WEB format and pagination) to generate the data. WIP serials, a default report that shows the serial numbers and other information, has a Drilldown to Unit History. Drilldowns can be identified by their format; they are all underscored. | Drilldowns occur when a link is selected by the user in order to drill down or further expand the data. To access Drilldown reports, select the parent link. This report will generate another report using a parameter passed by the selected link from the first report. This second report will use the default configuration (i.e., WEB format and pagination) to generate the data. WIP serials, a default report that shows the serial numbers and other information, has a Drilldown to Unit History. Drilldowns can be identified by their format; they are all underscored. | ||
Line 329: | Line 330: | ||
| | ||
− | = Tools = | + | = <span class="mw-headline" id="Tools">Tools</span> = |
− | == Snap Shots == | + | == <span class="mw-headline" id="Snap_Shots">Snap Shots</span> == |
This tool allows the user to create Snap Shots of a report with the Selected Parameters displaying a certain time. These Snap Shots can be configured to run on a schedule. | This tool allows the user to create Snap Shots of a report with the Selected Parameters displaying a certain time. These Snap Shots can be configured to run on a schedule. | ||
Line 341: | Line 342: | ||
| | ||
− | === Schedules === | + | === <span class="mw-headline" id="Schedules">Schedules</span> === |
Schedules allow the user to create a task that will execute the report with the saved parameters from a Snap Shot. | Schedules allow the user to create a task that will execute the report with the saved parameters from a Snap Shot. | ||
Line 395: | Line 396: | ||
Once the FTP information has been entered and setup, the user can Save, Cancel, or Delete the scheduled report. | Once the FTP information has been entered and setup, the user can Save, Cancel, or Delete the scheduled report. | ||
− | == Most Viewed == | + | == <span class="mw-headline" id="Most_Viewed">Most Viewed</span> == |
MESWeb automatically saves the most viewed reports. These reports can be found within the '''Most Viewed''' group. | MESWeb automatically saves the most viewed reports. These reports can be found within the '''Most Viewed''' group. | ||
Line 405: | Line 406: | ||
| | ||
− | == Favorites == | + | == <span class="mw-headline" id="Favorites">Favorites</span> == |
Every report has a star on the header that allows to user to save reports on '''Favorites''' group. | Every report has a star on the header that allows to user to save reports on '''Favorites''' group. | ||
Line 415: | Line 416: | ||
| | ||
− | = Predefined Reports = | + | = <span class="mw-headline" id="Predefined_Reports">Predefined Reports</span> = |
Predefined Reports are reports that cannot be changed in the Report Builder. These reports have more complex functions and are more complete. They can also be viewed graphically. | Predefined Reports are reports that cannot be changed in the Report Builder. These reports have more complex functions and are more complete. They can also be viewed graphically. | ||
Line 421: | Line 422: | ||
Sometimes, the user can see sub-reports in a Predefined Report. The most common Predefined Report is the '''Unit History''' '''Report''', which allows the user to query data from multiple tables. | Sometimes, the user can see sub-reports in a Predefined Report. The most common Predefined Report is the '''Unit History''' '''Report''', which allows the user to query data from multiple tables. | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | == <span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports"><span class="mw-headline" id="Default_Reports">Default Reports</span></span></span></span></span></span></span></span></span> == | ||
− | + | === <span class="mw-headline" id="Custom_Reports"><span class="mw-headline" id="Custom_Reports"><span class="mw-headline" id="Custom_Reports"><span class="mw-headline" id="Custom_Reports"><span class="mw-headline" id="Custom_Reports"><span class="mw-headline" id="Custom_Reports"><span class="mw-headline" id="Custom_Reports"><span class="mw-headline" id="Custom_Reports">'''Custom Reports'''</span></span></span></span></span></span></span></span> === | |
− | |||
− | |||
− | == | ||
− | |||
− | |||
Custom Reports is a categorization of report types that users can create. Custom reports perform that function of default reports and allow users to be more specific and narrow in their searches within the application. | Custom Reports is a categorization of report types that users can create. Custom reports perform that function of default reports and allow users to be more specific and narrow in their searches within the application. | ||
Line 483: | Line 484: | ||
| | ||
− | === <span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report">Shop Order Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report"><span class="mw-headline" id="Shop_Order_Report">Shop Order Report</span></span></span></span></span></span></span></span></span> === |
The Shop Order Report presents details for one or more shop orders along with all serials associated with them. It is important for users to track shop orders, and in order to do so, a user needs to be able to see the details of the units that comprise the shop order. | The Shop Order Report presents details for one or more shop orders along with all serials associated with them. It is important for users to track shop orders, and in order to do so, a user needs to be able to see the details of the units that comprise the shop order. | ||
Line 503: | Line 504: | ||
[[File:MESWebExec28.png|900px|MESWebExec28.png]] | [[File:MESWebExec28.png|900px|MESWebExec28.png]] | ||
− | === <span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report">Shop Order Summary Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report"><span class="mw-headline" id="Shop_Order_Summary_Report">Shop Order Summary Report</span></span></span></span></span></span></span></span></span> === |
The Shop Order Summary Report displays information about the part numbers, the order status, and the quantity of units in each status of a shop order. | The Shop Order Summary Report displays information about the part numbers, the order status, and the quantity of units in each status of a shop order. | ||
Line 529: | Line 530: | ||
| | ||
− | === <span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report">Top Defect Evolution Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report"><span class="mw-headline" id="Top_Defect_Evolution_Report">Top Defect Evolution Report</span></span></span></span></span></span></span></span></span> === |
The Top Defect Evolution Report allows users to have a better view of defects registered in MESR for one or more products. Those defects are classified by defect name, which produces a sum (number of defects and percent defect from total) of defects found in a given range for the specific defect. This report also lists the defect total based on a range of time. | The Top Defect Evolution Report allows users to have a better view of defects registered in MESR for one or more products. Those defects are classified by defect name, which produces a sum (number of defects and percent defect from total) of defects found in a given range for the specific defect. This report also lists the defect total based on a range of time. | ||
Line 575: | Line 576: | ||
| | ||
− | === <span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report">WIP Distribution Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report"><span class="mw-headline" id="WIP_Distribution_Report">WIP Distribution Report</span></span></span></span></span></span></span></span></span> === |
The WIP Distribution Report is designed to take the parameters specified by the user and return the number of units that are currently in WIP based on those parameters. The WIP Distribution Report can group results in several ways, depending on the user's preferences. The top level of the results offers the ability to drill down to the unit details. The WIP Distribution Report aims to give users the ability to get a snapshot of where their plant s workload is distributed. | The WIP Distribution Report is designed to take the parameters specified by the user and return the number of units that are currently in WIP based on those parameters. The WIP Distribution Report can group results in several ways, depending on the user's preferences. The top level of the results offers the ability to drill down to the unit details. The WIP Distribution Report aims to give users the ability to get a snapshot of where their plant s workload is distributed. | ||
Line 605: | Line 606: | ||
[[File:MESWebExec31.png|1000px|MESWebExec31.png]] | [[File:MESWebExec31.png|1000px|MESWebExec31.png]] | ||
− | === <span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report">Yield & Defect Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report"><span class="mw-headline" id="Yield_.26_Defect_Report">Yield & Defect Report</span></span></span></span></span></span></span></span></span> === |
The purpose of the Yield & Defect Report is to give users a high-level overview of progress. It lists the total number of units with activity, pass/fail quantity, and the yield for each process that is selected (filtered by other parameters as well). From there users can see details about the most common defects for a given process as well as details about each unit. | The purpose of the Yield & Defect Report is to give users a high-level overview of progress. It lists the total number of units with activity, pass/fail quantity, and the yield for each process that is selected (filtered by other parameters as well). From there users can see details about the most common defects for a given process as well as details about each unit. | ||
Line 651: | Line 652: | ||
[[File:MESWebExec32.png|RTENOTITLE]] | [[File:MESWebExec32.png|RTENOTITLE]] | ||
− | === <span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report">Yield Evolution Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report"><span class="mw-headline" id="Yield_Evolution_Report">Yield Evolution Report</span></span></span></span></span></span></span></span></span> === |
This report displays the percentage of success of the product for a determined period (Hour/Day/Week/Month). Users can view charts of this data and have tabular data presenting the hour/date/unit/passed/yield of a product. This data is presented via "All Products". | This report displays the percentage of success of the product for a determined period (Hour/Day/Week/Month). Users can view charts of this data and have tabular data presenting the hour/date/unit/passed/yield of a product. This data is presented via "All Products". | ||
Line 697: | Line 698: | ||
| | ||
− | === <span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report">Yield Serials Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report"><span class="mw-headline" id="Yield_Serials_Report">Yield Serials Report</span></span></span></span></span></span></span></span></span> === |
The Yield Serials Report displays the following information: Serial Number, Product, Workstation where the action occurred, Serial Quantity, Date of Action, and the Action. | The Yield Serials Report displays the following information: Serial Number, Product, Workstation where the action occurred, Serial Quantity, Date of Action, and the Action. | ||
Line 741: | Line 742: | ||
| | ||
− | === <span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report">Unit History Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report"><span class="mw-headline" id="Unit_History_Report">Unit History Report</span></span></span></span></span></span></span></span></span> === |
The Unit History Report gives detailed information about a specific unit and all its activity throughout its lifecycle. This allows users to see information about a specific unit and its activity. | The Unit History Report gives detailed information about a specific unit and all its activity throughout its lifecycle. This allows users to see information about a specific unit and its activity. | ||
Line 789: | Line 790: | ||
| | ||
− | ==== <span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File">Unit History With Multimedia File </span></span></span></span></span></span></span></span> ==== | + | ==== <span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File"><span class="mw-headline" id="Unit_History_With_Multimedia_File">Unit History With Multimedia File </span></span></span></span></span></span></span></span></span> ==== |
Production Workbench supports Multimedia Data Collection (PDF, Imagen, and Video) and users can take photos using their computer or tablet camera and upload any multimedia file. | Production Workbench supports Multimedia Data Collection (PDF, Imagen, and Video) and users can take photos using their computer or tablet camera and upload any multimedia file. | ||
Line 823: | Line 824: | ||
| | ||
− | === <span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report">Part Order Summary Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report"><span class="mw-headline" id="Part_Order_Summary_Report">Part Order Summary Report</span></span></span></span></span></span></span></span></span> === |
This report displays the following information about works orders: Part Number, Status, Quantity, and Serial Quantity. It also shows the due date, last activity, and how many days have passed before the due date. | This report displays the following information about works orders: Part Number, Status, Quantity, and Serial Quantity. It also shows the due date, last activity, and how many days have passed before the due date. | ||
Line 847: | Line 848: | ||
| | ||
− | === <span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report">RTY Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report"><span class="mw-headline" id="RTY_Report">RTY Report</span></span></span></span></span></span></span></span></span> === |
RTY shows how many activities were created by a Global Process. The report can display the results by month, week, or day. | RTY shows how many activities were created by a Global Process. The report can display the results by month, week, or day. | ||
Line 871: | Line 872: | ||
| | ||
− | === <span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report">Workstation Monitor Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report"><span class="mw-headline" id="Workstation_Monitor_Report">Workstation Monitor Report</span></span></span></span></span></span></span></span></span> === |
The Workstation Monitor Report shows how many units have been processed on a particular station. | The Workstation Monitor Report shows how many units have been processed on a particular station. | ||
Line 915: | Line 916: | ||
| | ||
− | === <span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report">WIP Serials Report</span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report"><span class="mw-headline" id="WIP_Serials_Report">WIP Serials Report</span></span></span></span></span></span></span></span></span> === |
The WIP (Work in Process) Serials Report displays all the serial numbers that are in production. | The WIP (Work in Process) Serials Report displays all the serial numbers that are in production. | ||
Line 953: | Line 954: | ||
| | ||
− | === <span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report">Solder Paste Status Report </span></span></span></span></span></span></span></span> === | + | === <span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report"><span class="mw-headline" id="Solder_Paste_Status_Report">Solder Paste Status Report </span></span></span></span></span></span></span></span></span> === |
| | ||
Line 974: | Line 975: | ||
'''[[File:Solder Paste Status Report Result.png|700px|Solder Paste Status Report Result.png]]''' | '''[[File:Solder Paste Status Report Result.png|700px|Solder Paste Status Report Result.png]]''' | ||
− | |||
− | = SOMS Reports = | + | = <span class="mw-headline" id="SOMS_Reports">SOMS Reports</span> = |
The SOMS Global Status Report is designed to start with a high-level overview of a plant's current operating status. The user can see the current number of units that are in the WIP, the yield for the current and previous days, and the throughput for the current and previous days for each of the plant's levels. Users also have the ability to drill down into a single level to see the same information broken out by line and process. The report is designed to give a quick snap shot of the health of a plant operation. | The SOMS Global Status Report is designed to start with a high-level overview of a plant's current operating status. The user can see the current number of units that are in the WIP, the yield for the current and previous days, and the throughput for the current and previous days for each of the plant's levels. Users also have the ability to drill down into a single level to see the same information broken out by line and process. The report is designed to give a quick snap shot of the health of a plant operation. | ||
Line 994: | Line 994: | ||
6. (Optional) Select the interval to refresh the report as needed | 6. (Optional) Select the interval to refresh the report as needed | ||
− | '''Figure | + | '''Figure 53: SOMS Setup''' |
'''[[File:SOP-5-I-MES0055-C RA1 SOMS Setup.jpg|RTENOTITLE]]''' | '''[[File:SOP-5-I-MES0055-C RA1 SOMS Setup.jpg|RTENOTITLE]]''' | ||
Line 1,002: | Line 1,002: | ||
| | ||
+ | | ||
+ | | ||
− | + | = <span class="mw-headline" id="QCP_Checklist">QCP Checklist</span> = | |
− | = QCP Checklist = | ||
The '''QCP Checklist '''is a new functionality that allows the MESWeb users to access a set of questions and answers done previously in '''Production Workbench.''' | The '''QCP Checklist '''is a new functionality that allows the MESWeb users to access a set of questions and answers done previously in '''Production Workbench.''' | ||
Line 1,013: | Line 1,014: | ||
| | ||
− | '''Figure | + | '''Figure 54: QCP Default Reports''' |
[[File:MESWebExecQCP48.png|800px|MESWebExecQCP48.png]] | [[File:MESWebExecQCP48.png|800px|MESWebExecQCP48.png]] | ||
Line 1,021: | Line 1,022: | ||
| | ||
+ | | ||
− | + | == <span class="mw-headline" id="QCP_History">QCP History</span> == | |
− | == QCP History == | ||
'''QCP History''' is divided into four steps which allow the user to see the following parameters: | '''QCP History''' is divided into four steps which allow the user to see the following parameters: | ||
Line 1,036: | Line 1,037: | ||
| | ||
− | '''Figure | + | '''Figure 55: QCP History Steps''' |
'''[[File:MESWebExecQCP49.png|700px|MESWebExecQCP49.png]]''' | '''[[File:MESWebExecQCP49.png|700px|MESWebExecQCP49.png]]''' | ||
Line 1,046: | Line 1,047: | ||
The '''Data Range '''allows the user to search the previously filled/answered '''QCP checklists '''in the selected dates ranges; once the user fills in the dates and time, they can click the '''Go''' '''button'''. | The '''Data Range '''allows the user to search the previously filled/answered '''QCP checklists '''in the selected dates ranges; once the user fills in the dates and time, they can click the '''Go''' '''button'''. | ||
− | '''Figure | + | '''Figure 56: Data Range''' |
'''[[File:MESWebExecQCP50.png|RTENOTITLE]]''' | '''[[File:MESWebExecQCP50.png|RTENOTITLE]]''' | ||
Line 1,054: | Line 1,055: | ||
| | ||
− | '''Figure | + | '''Figure 57: Data Range List''' |
[[File:MESWebExecQCP51.png|700px|MESWebExecQCP51.png]] | [[File:MESWebExecQCP51.png|700px|MESWebExecQCP51.png]] | ||
Line 1,064: | Line 1,065: | ||
| | ||
+ | | ||
− | == QCP Details == | + | == <span class="mw-headline" id="QCP_Details">QCP Details</span> == |
'''QCP''' '''Details''' allows the user to see and customize the information placed into the '''QCP checklis'''t; Name, Status, Employees Id, etc. It also allows the user to see the questions and their respective answers. | '''QCP''' '''Details''' allows the user to see and customize the information placed into the '''QCP checklis'''t; Name, Status, Employees Id, etc. It also allows the user to see the questions and their respective answers. | ||
Line 1,075: | Line 1,077: | ||
| | ||
− | '''Figure | + | '''Figure 58: QCP Details''' |
'''[[File:MESWebExecQCP52.png|700px|MESWebExecQCP52.png]]''' | '''[[File:MESWebExecQCP52.png|700px|MESWebExecQCP52.png]]''' | ||
Line 1,083: | Line 1,085: | ||
| | ||
− | == QCP Serials == | + | == <span class="mw-headline" id="QCP_Serials">QCP Serials</span> == |
To access to the QCP Serials, the user can select the option from the QCP Details page, as displayed in the following image: | To access to the QCP Serials, the user can select the option from the QCP Details page, as displayed in the following image: | ||
− | '''Figure | + | '''Figure 59: QCP Serials''' |
'''[[File:MESWebExecQCP53.png|700px|MESWebExecQCP53.png]]''' | '''[[File:MESWebExecQCP53.png|700px|MESWebExecQCP53.png]]''' | ||
Line 1,095: | Line 1,097: | ||
Once this option is selected, the screen will display the '''QCP Serials,''' allowing the users to see the list of serials and their respective information, Serial Number, Part Number, Process, Location QCP name, and the QCP version. | Once this option is selected, the screen will display the '''QCP Serials,''' allowing the users to see the list of serials and their respective information, Serial Number, Part Number, Process, Location QCP name, and the QCP version. | ||
− | '''Figure | + | '''Figure 60: QCP Serials''' |
[[File:MESWebExecQCP54.png|700px|MESWebExecQCP54.png]] | [[File:MESWebExecQCP54.png|700px|MESWebExecQCP54.png]] | ||
Line 1,105: | Line 1,107: | ||
This allows the user to see the detailed information about the Serial Numbers and all its activity throughout its lifecycle. | This allows the user to see the detailed information about the Serial Numbers and all its activity throughout its lifecycle. | ||
− | '''Figure | + | '''Figure 61: Unit History''' |
'''[[File:MESWebExecQCP55.png|700px|MESWebExecQCP55.png]]''' | '''[[File:MESWebExecQCP55.png|700px|MESWebExecQCP55.png]]''' | ||
Line 1,111: | Line 1,113: | ||
---- | ---- | ||
+ | | ||
− | = Document Revision History = | + | = <span class="mw-headline" id="Document_Revision_History">Document Revision History</span> = |
{| border="1" class="wikitable" | {| border="1" class="wikitable" | ||
Line 1,214: | Line 1,217: | ||
| | | | ||
|} | |} | ||
+ | [[Category:Pages with broken file links]] |
Revision as of 21:14, 15 January 2021
42Q Home > Reporting > MESWeb Reports
This edition applies to MES15 Portal 1.0 Application and all subsequent releases and modifications until otherwise indicated in new revisions.
Contents
- 1 Introduction
- 2 Getting Started with MESWeb Reports
- 3 Accessing MESWeb Reports
- 4 Parameters
- 5 Steps
- 6 Results
- 7 Tools
- 8 Predefined Reports
- 8.1 Default Reports
- 8.1.1 Custom Reports
- 8.1.2 Shop Order Report
- 8.1.3 Shop Order Summary Report
- 8.1.4 Top Defect Evolution Report
- 8.1.5 WIP Distribution Report
- 8.1.6 Yield & Defect Report
- 8.1.7 Yield Evolution Report
- 8.1.8 Yield Serials Report
- 8.1.9 Unit History Report
- 8.1.10 Part Order Summary Report
- 8.1.11 RTY Report
- 8.1.12 Workstation Monitor Report
- 8.1.13 WIP Serials Report
- 8.1.14 Solder Paste Status Report
- 8.1 Default Reports
- 9 SOMS Reports
- 10 QCP Checklist
- 11 Document Revision History
Introduction
MESWeb is a powerful business intelligence application designed from the ground up to simplify reporting from manufacturing execution systems and to empower end users with a streamlined and full-featured web interface. The application includes an "ad hoc report" design tool that allows users to create basic, customized reports from heterogeneous data sources.
Decentralized custom reports, redundant data, lack of formal security controls, and convoluted development requirements are problems faced by all plants, and MESWeb has been designed to resolve these issues while maximizing usability and performance.
Business Benefits:
MESWeb provides access to technical information about MES through a real-time reporting database to avoid negatively-impacting production system performance by eliminating the need for an ODBC connection. In its standard configuration, some of the reports based on MES include the following, while new reports continue to be created:
- Work in Process (WIP Distribution)
- Yield, Defect, and Repair analysis
- Serial Number historical details (Unit History)
- Evolution Reports (including moving averages) – Top Defect Evolution and Yield Evolution
- Throughput information
These reports have the ability to filter and search data for common attributes such as Customer, Part Number, Process, Date and Time range, Shifts, Evolution Intervals, etc. These default reports provide a significant level of visibility to manufacturing processes.
Extensibility:
MESWeb is also the strategic platform for all MES reporting needs and it can be used with any system since the following databases are available:
- ERP
- Postgres
- MySQL
- SQL Server 2000-2005
- ODBC
Access Level
MESWeb has five distinct access levels:
- Administrator (System Administrator)
- Security Manager (Local Administrator)
- Report Manager
- Data Source Manager
- User (Execution Module only) Section Name
Administrator (System Administrator)
The System Administrator has full access to MESWeb Central and Execution – all plants, all reports, all customers. Basically, Administrator access includes the capabilities of all of the levels (Security Manager, Report Manager, and Data Source Manager). This access will be given to BSAs and global support personnel. An administrator can perform the following functions:
- Access the "Access Control" module
- Create, Edit, and Delete Locations
- Create, Edit, and Delete Data Sources
- Create, Edit, and Delete Data Source types
- Create new custom reports globally
- Copy, Edit, and Delete existing custom reports globally
- Publish custom reports globally
- Manage permissions for all MESWeb locations
Security Manager (Local Administrator)
The Security Manager has full access to the plant(s) where he/she has been designated as local Administrator for the MESWeb tool. The main responsibilities of this role are to organize permissions and manage customers. A Security Manager is able to:
- Visualize the Central MESWeb module in the MES Portal
- Access the "Access Control" module
- Grant permissions to him/herself and others from the Security Manager level to all lower levels
- Manage customers (add customers and map part numbers to them)
Report Manager
The Report Manager has access to "Reports" and "Report Groups" modules in the specific location(s) where he/she was designed as Report Manager. Inside those modules, a Report Manager is able to:
- Create custom reports and publish them only in his/her location
- Edit or Delete existing customer reports in his/her location
Note: Deleting is not possible if the report is published elsewhere
- Create Report Groups
- Add Reports to Report Groups
Data Source Manager
The Data Source Manager is responsible for creating and updating Data Sources and Data Source types.
A Data Source Manager is able to:
- Create, Edit, and Delete Data Sources
- Create, Edit, and Delete Data Source types
User (Execution Module only) Section Name
The User role is able to execute only those reports specifically granted access to him/her, and may not create new reports or modify existing reports. Administrators may restrict user access only to data belonging to specific customers and data sources.
Getting Started with MESWeb Reports
MESWeb has been designed to be easy to use. The process of executing a MESWeb Report involves following only a few simple steps. Instructions for these steps may currently be found in two locations: (1) the MES Wiki (navigate to Reporting >
MESWeb) on the respective pages for each report; and (2) the MESWeb Report page (accessible via the MES Portal). Users who wish to read instructions for one or more specific reports are referred to the two aforementioned locations. Items that are important to the general use of MESWeb Reports are reviewed here. |
Accessing MESWeb Reports
To access the MESWeb Reports page, users must have access to the 42Q Portal. Once logged in, users must navigate to Reporting > MESWeb. The user is directed to the MESWeb Reports page. At this point the user's web browser should be displaying content similar to that seen in Figure 1. |
Figure 1: Accessing MESWeb Reports
Users can access MESWeb Reports from this page by selecting Reports and navigating either to Default Reports or to SOMS. Figures 2 and 3 show a listing of the pages where users can generate the respective reports.
Figure 2: Default Reports
Figure 3: SOMS Reports
Figure 4 shows the appearance of a typical Report page in MESWeb. (Note that the instructions are provided in the window on the right-hand side of the page, whereas all user actions are performed in the window on the left-hand side of the page).
Figure 4: Report Page
Parameters
MESWeb has a collection of parameters highly configurable by the user to help filter the information.
Dropdown list
This manages a list where only one single option is selected (see Figure 5 for an example).
Figure 5: Dropdown List
Checkbox
A checkbox is used for true/false parameters (see Figure 6 for an example).
Figure 6: Checkbox
Radio Buttons
Radio buttons allow the user to select one (1) option from the list (see Figure 7). Every selectable option is mutually exclusive. This also can be used for showing different parameters.
Figure 7: Radio Button
Date
A date parameter is used to select a specific date. There is a variant that also allows the user to select a time.
Figure 8: Date
Date Range
Date range is a parameter that allows the user to select a range between two dates. There is a variant that also allows the user to select a time.
Figure 9: Date Range
Listbox
In a listbox, multiple options can be selected (i.e., users can select every option in the "Available" list). Users can filter options by using the radio buttons "Starts With", "Contains", and "Ends With". After the user selects the necessary option, he/she enters text into the text box and then must select the icon to refresh the list.
The (highlighted down-arrow) icon moves all of the options in the "Available" list to the "Selected" list.
The (down-arrow) icon moves only the selected option in the "Available" list to the "Selected" list.
The (up-arrow) icon moves only the selected option in the "Selected" list back into the "Available" list, thus removing it from the "Selected" list.
The (highlighted up-arrow) icon moves all of the options in the "Selected" list back to the "Available" list, thus removing all options from the "Selected" list.
Figure 10: Listbox
Multi-Line Text Box
The multi-line text box allows the user to add lines as necessary.
Figure 11: Multi-Line Text Box
Steps
Steps mainly work as filters that are used to execute reports. A step contains x parameters and it may or may not be the parent of another subsequent step. For example, after the user selects a Customer, the Part Numbers related to the selected Customer are shown.
Results
Grids
Once a report is executed, a grid with the results will appear on the right side.
Figure 12: Grids
Selected Parameters
Selected parameters also appear down the side. These results contain other useful information such as the Application, the Execution Date, and the Execution Time.
Figure 13: Selected Parameters
Actions
There are three principal actions that can be done with the report s results: Print, Export, and Share.
This option allows the user to print the report.
Figure 14: Print Reports
After selecting Print, a dialog box appears. Select Print to display the report’s results.
Figure 15: Print Result
Export
The Export button downloads a file to the user's PC.
Figure 16: Export Report
The report can be saved in several formats, according to the user needs Excel, XML, CSV, text and now it can also be saved in Google Sheet.
Flow the steps below to export to google sheet:
Step 1: Select the Google Sheet option in the drop-down menu:
Figure 17: Export Report
Step 2: Configure the Google permissions selecting the correct option:
Figure 18: Export Report
Step 3: A message will be displayed when the configuration is done:
Figure 19: Export Report
Step 4: See the report exported in the selected format:
Figure 20: Export Report
This option is used to share the report's results. The user can share the report via Email or as a Link.
Figure 21: Share Report Result
Drilldowns
Drilldowns occur when a link is selected by the user in order to drill down or further expand the data. To access Drilldown reports, select the parent link. This report will generate another report using a parameter passed by the selected link from the first report. This second report will use the default configuration (i.e., WEB format and pagination) to generate the data. WIP serials, a default report that shows the serial numbers and other information, has a Drilldown to Unit History. Drilldowns can be identified by their format; they are all underscored.
Figure 22: Drilldown Reports
Tools
Snap Shots
This tool allows the user to create Snap Shots of a report with the Selected Parameters displaying a certain time. These Snap Shots can be configured to run on a schedule.
Figure 23: Snapshot
Schedules
Schedules allow the user to create a task that will execute the report with the saved parameters from a Snap Shot.
Follow the steps below to create a Schedule:
1. Select the configuration icon in the top right corner of the page
2. Select Snap Shots within the list menu to open the Snap Shots window
Figure 24: SnapShot Schedule
3. Select the plus-sign icon to the left of the SnapShot to expand.
4. Select the plus-sign icon to the far right on the schedule bar to open the General Information form.
Figure 25: Snap Shot Additional Information
The General Information form appears where the user can enter specific information, such as Name, Time Zone, and Frequency, about the schedule (see Figure 22).
The Frequency section allows the user to establish the timing settings for running a report. |
Figure 26: General Information
The Duration section allows the user to set a date range for execution. The user can also select how he/she would like the report to be delivered by choosing from the available options within the Delivery options section.
Figure 27: Duration and Delivery Options
In the example above, the report will be delivered via email in Excel format.
Figure 28: Sending
This form is shown when users select Email onDelivery Options.
Figure 29: Sending via FTP Server
Once the FTP information has been entered and setup, the user can Save, Cancel, or Delete the scheduled report.
Most Viewed
MESWeb automatically saves the most viewed reports. These reports can be found within the Most Viewed group.
Figure 30: Most Viewed
Favorites
Every report has a star on the header that allows to user to save reports on Favorites group.
Figure 31: Favorites
Predefined Reports
Predefined Reports are reports that cannot be changed in the Report Builder. These reports have more complex functions and are more complete. They can also be viewed graphically.
Sometimes, the user can see sub-reports in a Predefined Report. The most common Predefined Report is the Unit History Report, which allows the user to query data from multiple tables.
Default Reports
Custom Reports
Custom Reports is a categorization of report types that users can create. Custom reports perform that function of default reports and allow users to be more specific and narrow in their searches within the application.
See the steps below the steps to generate a Custom Report by Serial Number:
- Select a data source.
- Insert a serial number.
- (Optional) Select a plant.
- (Optional) Select a year.
- (Optional) Select a month.
- Select whether or not parameters should be hidden when the report is executed.
- (Optional) Select the interval to refresh the report as needed.
The report result is:
Figure 32: Report 1 - Material on Board S3
Note: This report will be able to use the serial number for finding its use in all of the materials from PTSR and Fujitrax databases, and show its scan board data and material information.
See the steps below the steps to generate a Custom Report by Date Period:
- Select a data source.
- Insert a serial number.
- (Optional) Select a plant.
- (Optional) Select a year.
- (Optional) Select a month.
- Select whether or not parameters should be hidden when the report is executed.
- (Optional) Select the interval to refresh the report as needed.
The report result is:
Figure 33: Report 2 - Material Where Used S3
Note: This report will be able to use a scanning date period to retrieve its serial number.
Shop Order Report
The Shop Order Report presents details for one or more shop orders along with all serials associated with them. It is important for users to track shop orders, and in order to do so, a user needs to be able to see the details of the units that comprise the shop order.
Follow the steps below to generate a Shop Order Report:
1. Select a Data Source
2. Enter up to 1000 Shop Order Numbers
3. Select whether or not parameters should be hidden when the report is executed
4. (Optional) Select the interval to refresh the report as needed
The report result is:
Figure 34: Shop Order Report
Shop Order Summary Report
The Shop Order Summary Report displays information about the part numbers, the order status, and the quantity of units in each status of a shop order.
Follow the steps below to execute the Shop Order Summary Report:
1. Select a Data Source
2. Enter up to 100 Shop Orders (only one per line)
3. Select whether or not parameters should be hidden when the report is executed
4. (Optional) Select the interval to refresh the report as needed
The report result is:
Figure 35: Shop Order Summary Report
By entering one or several Shop orders this report will display information about, their part numbers, order status, and the quantity of units in each status.
Top Defect Evolution Report
The Top Defect Evolution Report allows users to have a better view of defects registered in MESR for one or more products. Those defects are classified by defect name, which produces a sum (number of defects and percent defect from total) of defects found in a given range for the specific defect. This report also lists the defect total based on a range of time.
Follow the steps below to generate a Top Defect Evolution Report:
1. Select a Data Source
2. Select one or more Customers
3. Select one or more Products
4. Select one or more Processes
5. Select one or more Lines
6. Select a Pass to view
7. Select one or more Shifts
8. Set the values for the Evolution Parameter
9. Select Start Date
10. Select which field to group by first
11. (Optional) Select which field to group by the second
12. Select the type of report you want to run
13. Indicate if you would like to view graphs, and, if so, select the type
14. Select whether or not parameters should be hidden when the report is executed
15. (Optional) Select the interval to refresh the report as needed
The report result is:
Figure 36: Top Defect Evolution Report
WIP Distribution Report
The WIP Distribution Report is designed to take the parameters specified by the user and return the number of units that are currently in WIP based on those parameters. The WIP Distribution Report can group results in several ways, depending on the user's preferences. The top level of the results offers the ability to drill down to the unit details. The WIP Distribution Report aims to give users the ability to get a snapshot of where their plant s workload is distributed.
Follow the steps below to generate a WIP Distribution Report:
1. Select a Data Source
2. Select one or more Customers
3. Select one or more Products
4. (Optional) null
5. Select one or more Departments
6. Select one or more Unit Statuses
7. (Optional) Select one or more Processes
8. Select one or more Workstations
9. Select whether or not parameters should be hidden when the report is executed
10. (Optional) Select the interval to refresh the report as needed
Figure 37: WIP Distribution Report
Yield & Defect Report
The purpose of the Yield & Defect Report is to give users a high-level overview of progress. It lists the total number of units with activity, pass/fail quantity, and the yield for each process that is selected (filtered by other parameters as well). From there users can see details about the most common defects for a given process as well as details about each unit.
Managers can use this information to pinpoint the areas on the floor that require their attention and discover why. To execute this report, the user must be in Execution Module, where he/she should select the Reports menu and navigate to Default Reports Yield & Defect Report.
Follow the steps below to generate a Yield & Defect Report:
1. Select a Data Source
2. Select one or more Customers
3. Select one or more Products
4. Select one or more Processes
5. Select one or more Lines
6. Select a Pass to view
7. Select one or more Shifts
8. Select one or more Workstations
9. Enter a Date Range or select one or more Orders
10. Select a field to group by
11. (Optional) Select a second field to group by
12. Choose whether to include moving units
13. Indicate if you would like to consider "No Fault Found" as passes
14. Indicate if you would like to view graphs
15. Select whether or not parameters should be hidden when the report is executed
16. (Optional) Select the interval to refresh the report as needed
The report result is:
Figure 38: Yield & Defect Report
Yield Evolution Report
This report displays the percentage of success of the product for a determined period (Hour/Day/Week/Month). Users can view charts of this data and have tabular data presenting the hour/date/unit/passed/yield of a product. This data is presented via "All Products".
A Drilldown report, which offers more details about the product, is available for unit/passed/failed. To execute this report, the user must be in Execution Module, where he/she should select the Reports menu and navigate to Default Reports Yield Evolution Report.
Follow the steps below to generate a Yield Evolution Report:
1. Select a Data Source
2. Select one or more Customers
3. Select one or more Products
4. Select one or more Processes
5. Select one or more Lines
6. Select a pass to view
7. Select one or more Shifts
8. Set the values for the Evolution Parameter
9. Select Start Date
10. Select which field to group by first
11. (Optional) Select which field to group by the second
12. Choose whether to include moving units
13. Indicate if you would like to display charts
14. Select whether or not parameters should be hidden when the report is executed
15. (Optional) Select the interval to refresh the report as needed
The report result is:
Figure 39: Yield Evolution Report
Yield Serials Report
The Yield Serials Report displays the following information: Serial Number, Product, Workstation where the action occurred, Serial Quantity, Date of Action, and the Action.
Follow the steps below to generate a Yield Serials Report:
1. Select a Data Source
2. Select one or more Customers
3. Select one or more Products
4. Select one or more Processes
5. (Optional) Select one or more Lines
6. Select a pass to view
7. (Optional) Select one or more Shifts
8. (Optional) Select one or more Global Processes
9. (Optional) Select one or more Workstations
10. (Optional) Filter data by a Date Range
11. (Optional) Select number of Shop Orders
12. Select one or more Actions
13. Select whether or not parameters should be hidden when the report is executed
14. (Optional) Select the interval to refresh the report as needed
The report result is:
Figure 40: Yield Serials Report
Unit History Report
The Unit History Report gives detailed information about a specific unit and all its activity throughout its lifecycle. This allows users to see information about a specific unit and its activity.
Follow the steps below to generate a Unit History Report:
1. Enter up to 1000 Serials
2. Select whether or not parameters should be hidden when the report is executed
3. (Optional) Select the interval to refresh the report as needed
Figure 41: Unit History
Unit History Report now has the capability to query data from MES Archive integrated into the report. A new parameter was added to the report which allows the user to decide whether to query Archive data or only be notified when searched serials have already been archived.
New includes Archive Parameter.
Figure 42: Unit History
When the report is executed with the Include Archive parameter selected, it will query Archive data for all searched serials that have been archived. Archived serials will be labeled as such, and data will be presented in the same format as regular serials. Both archived and regular serials can be searched at the same time.
A Report executed with Include Archive selected
Figure 43: Unit History
When the report is executed with the Include Archive parameter unselected, serials that have been archived will be labeled as such, and the user will be given the option to click the link in order to get the data from Archive. This is to prevent a longer execution time in case the user is unaware serials have been already archived.
Report executed with Include Archive unselected
Figure 44: Unit History
Unit History With Multimedia File
Production Workbench supports Multimedia Data Collection (PDF, Imagen, and Video) and users can take photos using their computer or tablet camera and upload any multimedia file.
This will reflect in the Unit History report, where the user is able to see the image upload for the SN.
For more information about Multimedia files, refer to Production Workbench SOP.
Figure 45: Unit History with Multimedia File Attached
Clicking on the image icon, the attached file will be displayed:
Figure 46: Expanded Image
Select the expand icon to see just the image.
Figure 47: Uploaded Image Details
Part Order Summary Report
This report displays the following information about works orders: Part Number, Status, Quantity, and Serial Quantity. It also shows the due date, last activity, and how many days have passed before the due date.
Follow the steps below to generate a Part Order Report:
1. Select a Data Source
2. Enter up to 500 Part Numbers (one per line)
3. Select whether or not parameters should be hidden when the report is executed
4. (Optional) Select the interval to refresh the report as needed
Figure 48: Part Order Summary
RTY Report
RTY shows how many activities were created by a Global Process. The report can display the results by month, week, or day.
Follow the steps below to generate an RTY Report:
1. Select a Data Source
2. Select one or more Customers
3. Select the Data Range (Start and End Dates)
4. Select whether or not parameters should be hidden when the report is executed
5. (Optional) Select the interval to refresh the report as needed
Figure 49: RTY Report
Workstation Monitor Report
The Workstation Monitor Report shows how many units have been processed on a particular station.
Follow the steps below to generate a Workstation Monitor Report: |
1. Select a Data Source
2. Select a Customer
3. Select a Product
4. Select a Workstation
5. Select the Date and Time Range for the Shift
6. Enter the start time for the first break (format: HH:mm)
7. Enter the end time for the first break (HH:mm)
8. (Optional) Enter the start time for the second break (HH:mm)
9. (Optional) Enter the end time for the second break (HH:mm)
10. (Optional) Enter the start time for the third break (HH:mm)
11. (Optional) Enter the end time for the third break (HH:mm)
12. Enter UPH target.
13. Select whether or not parameters should be hidden when report is executed
14. (Optional) Select the interval to refresh the report as needed
Figure 50: Workstation Monitor
WIP Serials Report
The WIP (Work in Process) Serials Report displays all the serial numbers that are in production.
Follow the steps below to generate a WIP Serial Report:
1. Select a Data Source
2. Select one or more Customers
3. Select one or more Products
4. Select the order that should be used to filter the results
5. Select one or more Departments
6. Select one or more Unit Status
7. Select one or more ways to group the information
8. (Optional) Select a field to group by
9. Indicate if you would like to display charts or not
10. Select whether or not parameters should be hidden when the report is executed
11. (Optional) Select the interval to refresh the report as needed
The report result is:
Figure 51: WIP Serials
Solder Paste Status Report
The Solder Paste Status Report details the status of any items with the Solder Paste inventory, specified by part and serial numbers. It shows the current status, with timestamp data.
See the steps below the steps to generate a Solder Paste Status Report
- Select a data source
- (Optional) Select a Solder Paste P/N
- (Optional) Select a Solder Paste S/N
- (Optional) Select a Solder Paste Status
- Select a date range
- Select whether or not parameters should be hidden when the report is executed.
- (Optional) Select the interval to refresh the report as needed.
The report result is:
Figure 52: Solder Paste Status Report Result
SOMS Reports
The SOMS Global Status Report is designed to start with a high-level overview of a plant's current operating status. The user can see the current number of units that are in the WIP, the yield for the current and previous days, and the throughput for the current and previous days for each of the plant's levels. Users also have the ability to drill down into a single level to see the same information broken out by line and process. The report is designed to give a quick snap shot of the health of a plant operation.
Follow the steps below to generate a SOMS Report:
1. Select a Data Source
2. (Optional) Enter the Mfg Line Name
3. (Optional) Enter the Scanner ID
4. (Optional) Enter the Multi-Pass Location Name
5. Select whether or not parameters should be hidden when the report is executed
6. (Optional) Select the interval to refresh the report as needed
Figure 53: SOMS Setup
QCP Checklist
The QCP Checklist is a new functionality that allows the MESWeb users to access a set of questions and answers done previously in Production Workbench.
To enter the QCP Checklist the user must go to MESWeb>Reports>Default Reports, there, three different reports are available:QCP History, QCP Details, and QCP Serials.
Figure 54: QCP Default Reports
Note: The user can access QCP History, QCP Details, and QCP Serials by selecting them.
QCP History
QCP History is divided into four steps which allow the user to see the following parameters:
- Step 1: Data Source
- Step 2:QCP Name
- Step 3: Part Number, Process, Location, Employee, Obsoletes
- Step 4: Data range.
Note: These configurations are showing on the left side of the screen, as displayed in the following image:
Figure 55: QCP History Steps
The parameters mentioned above allow the user to have a customized search of the QCP Checklists, all of them are optional, except for Step 1: Source andStep 4: Data Range; as shown in the image below.
The Data Range allows the user to search the previously filled/answered QCP checklists in the selected dates ranges; once the user fills in the dates and time, they can click the Go button.
Figure 56: Data Range
The QCP information will be displayed on the screen, with their respective configuration; name, version, part number, etc.
Figure 57: Data Range List
This list shows the Effective Date and the Expiration Date, it also shows the State of the QCP; this can be either Active or Expired, and the Employee ID from the user who filled the QCP checklist.
Note: The Effective Date and the Expiration Date information is associated with every Serial Number, scanned between the active period of the checklist and before it expires.
QCP Details
QCP Details allows the user to see and customize the information placed into the QCP checklist; Name, Status, Employees Id, etc. It also allows the user to see the questions and their respective answers.
The user can drill down from QCP History to QCP Details, by selecting the QCP Name in the list.
Note: The QCP Details have the same steps and the same parameters as QCP History (only the format is different).
Figure 58: QCP Details
Note: The color on the sidebar, changes according to the status; Red= Expired, Green= Active
QCP Serials
To access to the QCP Serials, the user can select the option from the QCP Details page, as displayed in the following image:
Figure 59: QCP Serials
Once this option is selected, the screen will display the QCP Serials, allowing the users to see the list of serials and their respective information, Serial Number, Part Number, Process, Location QCP name, and the QCP version.
Figure 60: QCP Serials
By selecting the Serial Number, shown on the image above; the user is able to see the Unit history.
This allows the user to see the detailed information about the Serial Numbers and all its activity throughout its lifecycle.
Figure 61: Unit History
Document Revision History
Date | Author | Title | Version | Change Reference | Approved by |
---|---|---|---|---|---|
28/10/15 | Elaine Fonaro | Technical Writer | V1.0 | Initial Version | |
12/01/16 | Claudia Urenda | Product Owner | V1.0 | General Review and especially for business rules. | |
13/01/16 | Elaine Fonaro | Technical Writer | V1.0 | Small changes required and new images added. Format to WIKI format. | |
15/01/16 | Kala Burson | Technical Writer | V1.0 | Grammatical edits. | |
03/04/16 | Elaine Fonaro | Technical Writer | v 1.0 | Updated Oracle occurrences to ERP | |
28/04/16 | Dane Parker | Technical Writer | v 1.0 | Formatted to 42Q | |
04/04/18 | Elaine Fonaro | Technical Writer | v 1.0 | Applied a new template for the format. | |
08/11/18 | Marisol Vargas | Technical Writer | v.1.0 | Small changes required and new images added to the Unit History Report and Export. | |
24/04/20 | Marisol Vargas | Technical Writer | v.1.0 | Adding QCP configuration for reports | Elizabeth Armenta |
03/05/20 | Fredy Serrano | Product Owner | v.1.0 | General Review for QCP Reports added | |
07/10/20 | Elaine Fonaro | Technical Writer | v.1.0 | Added the Multimedia File information for the Unit History report. | Elizabeth Armenta |
28/08/20 | Elaine Fonaro | Technical Writer | v.1.0 | Added the Default Report Solder Paste Status. | Kyle Wagner |
01/09/20 | Marisol Vargas | Technical Writer | V.1.0 | Peer review on Default Report Solder Paste Status |