M-QIS

Proven as an efficient management tool, M-QIS processes quality information and increases the transparency of workflows, processes and business operations. The knowledge gained forms the basis for decisions and measures that lead to continuous process improvement. Reliable statistics create confidence and minimise the risk of producing defective parts.

The reporting system, the main component of the M-QIS module, is used to automate the evaluation and distribution of information to the employees involved. The basis for a successful application is a data flow concept, the ability to handle advanced filters and queries, and the use of the Q-FD form designer to create the reports to be sent. But it is not "just" an automation of the evaluation and the report creation according to the defined "reason for the report".

The reporting system offers many more possibilities, which are described in the FAQ and in the case studies. One possible training concept to get familiar with M-QIS is a workshop. In an M-QIS workshop, the Q-DAS project team plans the use of the reporting system together with the customer. In the workshop itself, the reporting matrix is discussed. In addition to the standard training courses, the following topics can be used to prepare for the M-QIS workshop:

​M-QIS Modules

The product M-QIS also includes the modules "Sample Analysis" and "Process Capability Analysis". The product M-QIS also includes the modules "Sample Analysis" and "Process Capability Analysis". These are the same modules as in the qs-STAT product. For more information on these modules, please refer to qs-STAT. The modules that are only available in the M-QIS are described below.

M-QIS Reporting System Basic handling of the M-QIS reporting system.	English:PDF	German:PDF
Long Term Analysis based on compressed data The Long Term Analysis module of the M-QIS Engine application provides a quick overview of production and process data. For this purpose, the results of the previously compressed measured values are displayed in special graphics, mainly in the so called “benchmark” graphics. In order to monitor the development of quality data over a longer period of time ("Long Term Analysis"), it is necessary to regularly perform data compression and result calculation with the Q-DAS M-QIS Engine Reporting application. This document describes the procedure for a long term data analysis, the interaction of the required Q-DAS applications and offers suggestions for the planning and configuration of data compressions.	English:PDF	German:PDF
Archiving Food for thought and a first start with archiving.	English:PDF	German:PDF
Installation as a service The following document briefly explains how to install M-QIS Reporting or Q-DM Upload as a service.	English:PDF	German:PDF

CAS Reporting System

The reporting system, the main component of the M-QIS product, is to be explained to the customer in a few case studies. The case studies serve as orientation about the possibilities and are not detailed click instructions. A basic knowledge of the handling of M-QIS must be assumed here in order to ensure the readability of the documents.

​

CAS 0101 Report for Nonconformity  A classic report that loads only the previous day's data and for variable characteristics reports only those characteristics that had measured values outside the specification limits.	English:PDF
CAS 0102 Report for bad characteristics only A classic report that is produced weekly to report only those characteristics produced in the previous week that were not capable with the measured values of the previous 12 weeks.	English:PDF
CAS 0103 Report for bad characteristics, filtered through the Report A sub-variant of CAS 0102. The report is always sent, the reduction of the characteristics to those that are not capable is not done via the alarm conditions of the reporting system but is realised via the form designer in the report. ZIP file with report template: CAS_0103_Reporting_Weekly_Report.zip	English:PDF
CAS 0104 Report for tolerance violations taking into account historical alarms A sub-variant of CAS 0101. This case study describes a special case: A daily report should list all characteristics which had violations of 80% of the limits on the previous day. However, the characteristics shown then should contain the data of a whole week. But historically already reported alarms from before the previous day should not be reported again. For this purpose, the option of "historical alarms" was created, which will be explained here. It is also described in the FAQ of the reporting system, Chapter 6.2.6.11.	English:PDF
CAS 0105 Combining reports and report-recipients in e-mails  A case study that does not show "what" is presented in the reports, but “how”, when sending reports of several parts, they can be summarised by mail or for recipients.	English:PDF
CAS 0120 Data Aggregation for "Long Term Analysis" In this example, the data aggregation for the module "long term analysis" will be briefly explained.	English:PDF