Testnet is divided into three functions:- Analyse - Repair - Administration. These applications correspond to the actual user they are intended for.
Analyse incorporates several functions, which together enables you to make a concise analysis of a product:
Weekdata enables you to look at aggregated test information and to create weekly reports. Weekdata reports show the result as the percentage of faults found the first time the individual is tested, taken over a four-week average. Also shown is the distribution of error codes.
Infodata enables you to find information about how a product has been tested. The information is presented in an Excel sheet, which means that it is possible to use the information to create customised reports/graphs.
Measdata is used to analyse measurement data from tests. Here you can also see the distribution and trends for measurement points. The resulting report displays information on individuals contained in the relevant search criteria and the distribution for a measurement point. There is also build in auto generated Word reports available in this tool for e.g capability calculation. The information is presented in an Excel sheet, which means that it is possible to use the information to create customised reports/graphs.
With MachTime it is possible to search selected stations for information about test time usage. The results from these findings are presented in both graphical and numerical format. For example, it is possible to see exactly when every test-run has been started and when it is finished. From this you can go deeper and see just how long the tests have been active and how much of this active time was spent testing objects that passed or failed.
Reptile — Repair tool
This allows you to look at earlier repair data or to see previous test results. It is also possible to see the reason for repair, as well as what repairs have been made. Repair is used to input repair data into the database.
Admin is the administration program of Testnet. With Admin, you can correct test protocols that have been rejected before they are stored.
In Users, you define the user profile and user access.
One of the main benefits with the quality module, is that with the help of the standard reports and the analysis function you have continuous quality control and follow-up of production. At the same time, actual man hours needed to record, retrieve and utilise data is reduced.
You decide at what level you would like to follow-up the process; for example, it is possible to follow-up per:
The quality module is not trapped by the boundaries of the factory walls. It is possible to provide the module with a ‘map´ of the process you would like to follow-up. This map acts as a navigation system, so that when an operator, for example, inputs data, the system module knows exactly where the data comes from and what has been tested, or what report has been generated. The map gives you the freedom you need to customise your requirements. Because administration is uncomplicated, it is quick and easy to make any necessary changes (if, for example work processes change), or to copy a map and use it as a template.
The map should define the different stages of follow-up, for example, if you would like to following-up quality in a factory the natural flow would be:
An area corresponds to a certain clearly defined section of the production process. For example, the area can correspond to a section or to a surface where a specific product is manufactured. One or more production lines are linked to an area. This is the highest level of the hierarchy.
A line is a logical term that is used for linking together various production steps. Ordinarily, a line begins where production begins and ends where the product is combined with another product or is finished for delivery. A production line can coincide with a physical line, although this is not a requirement.
A test category indicates which type of test is to be carried out on the product regardless of whether the tests are performed manually or automatically. Examples of test categories are Optical Inspection and Function Test
It is possible to register all products and functions in the database. Products can be imported from other databases, for example from PRIM which is Ericsson´s global product information management database.
Reports Information output is presented in different types of reports. These reports can be in either table or graph format and can cover, for example, the last hour of production or a period of twelve months. These reports can be used for long-term follow-up of quality for production or functionality and for seeing that corrective actions taken in the production process have the desired effects.
Certain reports can be scheduled; that is, they will be printed (you determine which printer) in time intervals that you specify. This is useful if, for example, you want have regular quality checks on shifts.
Types of reports
Below are examples of the standard reports that are presently available.
Yield/Fault Outcome Reports (Products)
Yield reports present yield in production and the value is expressed as a percentage. Yield in this instance is defined as the number of individuals that were approved during the first tests relative to the total number of tested individuals. The Yield is presented in an ascending order, which makes it possible to compare various report locations both quickly and easily.
Fault Outcome shows the number of faulty units relative to the number of tested units.
This report provides information on the Defects Per Million Opportunities (DPMO) value of three selectable fault categories, such as Solder and Assemblage, per report group and test category. The DPMO values can be presented in three different ways. The report is based on the fault and inspection inputs that were made during the specified period.
There are eight types of Pareto reports; Fault Code, Position, Component, Product, Area, Line, Test Category, and Measurement Point. The results of each include both actual and percentage values. The results show, for example, the ten most frequently occurring fault codes for a specified product or function.
Cause of Fault Report
This report consists of two tables. Information on the fault codes and the faulty positions are presented in two separate tables. The information is presented per report location for the selected period and product or report group. If you choose a report group, the results of the products in the report group will not be combined. This makes it possible to obtain statistics on a given product in a report group.
Fault Report (Positions verses Fault Code)
This report displays the following information on each faulty product:
Depending on whether the report is sorted according to “positions per fault code" or “fault codes per position", the presentation contains:
How many times the product has been tested and how many times it was faulty or the sum of all faults and the sum of all fault points distributed among the reported positions of the faults.
Information is presented per report location, for the specified period and product or report group.
Quality Audit Report
This report is aimed at people who are involved with quality assurance. With this function it is possible to look at process reliability and generate a quality audit report.
Quality reports can be generated, in graph form, for the follow:
The results are presented for selected report locations, products and for a specified period.
Detailed Trend Diagram
A Trend Diagram report can be generated for the following areas: fault code, position, component and product. This report shows how often a fault occurs over a specified period of time.
Using the quality Analysis function you can query information directly from the tables in the database and so minimise the need for external tools for accessing the database. The analysis function is used for querying information that cannot otherwise be obtained through various standard reports. By setting search criteria you can enter a formula relevant to your needs. Data is presented in table format. You can combine two or more tables to produce a view.