Chapter 16: Difference between revisions
Jump to navigation
Jump to search
| (6 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
Several documents describe the need for software validation (or, as some documents describe it, first time verification). Both ISO17025 and ISO/IEC Guide 25 recognize the need for software validation. However neither document describe how this software validation should be performed. The document EA/GA(98)95 (version 4, May 1998) “Guidelines for the use of computers and computer systems in accredited laboratories” does describe guidelines for software validation. However this document is currently considered to be ‘informative only’. | Several documents describe the need for software validation (or, as some documents describe it, first time verification). Both ISO17025 and ISO/IEC Guide 25 recognize the need for software validation. However neither document describe how this software validation should be performed. The document EA/GA(98)95 (version 4, May 1998) “Guidelines for the use of computers and computer systems in accredited laboratories” does describe guidelines for software validation. However this document is currently considered to be ‘informative only’. | ||
{{CompanyName}} recognize the importance of software validation and has implemented special functionalities into the {{RadiMation}} EMC software package for this purpose. These functionalities make it possible to verify the performance of the test system as a whole and to reproduce specific tests at a later moment. | |||
In addition to the first software verification, every new version of {{RadiMation}} undergoes a software verification specified by a pre-defined test plan. This eliminates the need for test houses to perform a complete software validation process. | In addition to the first software verification, every new version of {{RadiMation}} undergoes a software verification specified by a pre-defined test plan. This eliminates the need for test houses to perform a complete software validation process. | ||
| Line 23: | Line 22: | ||
To make sure that the {{RadiMation}} Software is in compliance with ISO17025, ISO/IEC Guide 25 and relevant parts of EA/GA(98)95, several measures have been taken. An overview of these is listed below under '{{RadiMation}} Quality measures'. | To make sure that the {{RadiMation}} Software is in compliance with ISO17025, ISO/IEC Guide 25 and relevant parts of EA/GA(98)95, several measures have been taken. An overview of these is listed below (more information can be found under '{{RadiMation}} Quality measures'). | ||
== {{RadiMation}} Quality | # General measures | ||
# All relevant data is stored | |||
# System verification is performed prior to each test | |||
# Equipment verification is performed prior to each test | |||
# Software settings verification is performed prior to each test | |||
== {{RadiMation}} Quality measures == | |||
=== General measures === | === General measures === | ||
# The {{RadiMation}} Software package stores all test data | # The {{RadiMation}} Software package stores all test data. It is not possible to change the measurement data on a later moment, eliminating the possibility to temper with test results. It is possible however to append new test data to a EUT file at a later date. The test results can be viewed at any time. | ||
# Test data | # Test data stored in older versions of {{RadiMation}} can be viewed with newer versions, giving access to old test data at any time. | ||
=== Storage of all relevant data === | === Storage of all relevant data === | ||
All information that is relevant | All the information that is relevant and necessary to reproduce a test is stored. A summary of the items that are recorded during a test are visible below: | ||
# All the “RAW” measurement date is stored for later evaluation (e.g. all power meter(s), field sensor(s), receiver(s), A/D converter(s) readings, signal generator settings, etc.) | |||
# All the user configurable settings are stored with the measurement data (TSF file settings). | |||
# All the correction and calibration files used during the test are copied and stored with the test results. | |||
# All the test equipment used during the test is stored (Equipment list). | |||
# The date, time and test engineer name are stored with the measurement data. | |||
# Error messages (if any), that occurred during the test are stored with the measurement results. | |||
=== System verification prior to each test === | === System verification prior to each test === | ||
An EMC test set-up consists of a number of different test devices, computers and software packages. To maintain a high level of quality control, it is necessary to perform an overall system verification (including the complete test set-up) on a regular basis. | |||
Because of this {{RadiMation}} performs a number of hardware, software and system verifications at the beginning of each test. | |||
=== Radiated and conducted immunity tests === | === Radiated and conducted immunity tests === | ||
# Prior to each test, the software will perform a | # Prior to each test, the software will perform a power delivery test. During this power delivery test, the software increases the output power of the signal generator and measures the output power of the amplifier with the (forward) power meter. If the software measures a stable reading on the power meter, {{RadiMation}} assumes that all the cables between the signal generator, amplifier, coupler and the power meter are connected correctly. | ||
# Prior to each test, the software will perform a linearity check. The software generates a stable signal | # Prior to each test, the software will perform a linearity check. The software generates a stable signal generator output power, measures it on the power meter and then increases the signal generator level with 4 dB steps. If the power meter reading also increases with 4 dB steps, {{RadiMation}} assumes that the amplifier is linear. | ||
=== Radiated and conducted emission tests === | === Radiated and conducted emission tests === | ||
| Line 57: | Line 66: | ||
Equipment verification prior to each test: | Equipment verification prior to each test: | ||
# Prior to each test the {{RadiMation}} Software will check if all required test equipment can be found. If one or more | # Prior to each test the {{RadiMation}} Software will check if all the required test equipment can be found. If one or more devices are not found, the software will stop and display an error message. | ||
# Prior to each test the {{RadiMation}} Software will check if communication is possible with all required test equipment ( | # Prior to each test the {{RadiMation}} Software will check if communication is possible with all required test equipment (initialization). If one or more devices do not respond correctly, the software will stop and display an error message. | ||
Software settings verification prior to each test | Software settings verification prior to each test: | ||
# Prior to each test the {{RadiMation}} Software will check if all user configurable settings of the Technical Set-up File (TSF file) are within the limits of the selected test equipment in the equipment list ( | # Prior to each test the {{RadiMation}} Software will check if all the user configurable settings of the Technical Set-up File (TSF file) are within the limits of the selected test equipment in the equipment list (e.g. does the antenna cover the required frequency range, etc.). | ||
# If a test is started | # If a test is started that uses a calibration file, the software will verify if the currently selected test equipment (in the equipment list) is the same as the equipment used during the calibration. This is recommended for the accuracy of the test results. If different equipment was used, the software will display a warning, asking the operator to continue (despite the different equipment) or stop the test. | ||
[[Category:Manual]] | [[Category:Manual]] | ||
Latest revision as of 08:30, 11 March 2020
Quality assurance[edit]
Quality standards[edit]
The use of automatic test software can greatly affect the quality of tests performed in calibration and/or test laboratory. Depending on the software, the tests can be affected either in a positive and a negative way.
On one hand, good quality software can reduce the risks of human errors and increase the quality of work/tests performed. On the other hand, is the software contains errors (and no software validation has been performed), it is very likely that the measurements performed will be incorrect, reducing the quality of the tests performed.
Several documents describe the need for software validation (or, as some documents describe it, first time verification). Both ISO17025 and ISO/IEC Guide 25 recognize the need for software validation. However neither document describe how this software validation should be performed. The document EA/GA(98)95 (version 4, May 1998) “Guidelines for the use of computers and computer systems in accredited laboratories” does describe guidelines for software validation. However this document is currently considered to be ‘informative only’.
Raditeq recognize the importance of software validation and has implemented special functionalities into the RadiMation® EMC software package for this purpose. These functionalities make it possible to verify the performance of the test system as a whole and to reproduce specific tests at a later moment.
In addition to the first software verification, every new version of RadiMation® undergoes a software verification specified by a pre-defined test plan. This eliminates the need for test houses to perform a complete software validation process.
The use of the RadiMation® software (by the test houses) also influences the measurement quality and data security of the performed measurements. Because of this we strongly recommend test houses to adhere to the following advice:
- Make back up files of the measurements results.
- Install the RadiMation® Software on a local test computer and use a network drive location for the data storage. This network drive can be automatically backed up. (Alternatively, the measurement data can also be stored on a test computer. However, be advised that in this situation special attention should be paid to backing up the measurement data on a regular basis.)
- Set up access protection for both the computer system and the RadiMation® Software package.
- Appoint one or more individuals to be responsible for the configuration of the RadiMation® Software (i.e. equipment configuration, TSF file configurations, setting default directories, entering correction and calibration files and appointing new test engineers).
To make sure that the RadiMation® Software is in compliance with ISO17025, ISO/IEC Guide 25 and relevant parts of EA/GA(98)95, several measures have been taken. An overview of these is listed below (more information can be found under 'RadiMation® Quality measures').
- General measures
- All relevant data is stored
- System verification is performed prior to each test
- Equipment verification is performed prior to each test
- Software settings verification is performed prior to each test
RadiMation® Quality measures[edit]
General measures[edit]
- The RadiMation® Software package stores all test data. It is not possible to change the measurement data on a later moment, eliminating the possibility to temper with test results. It is possible however to append new test data to a EUT file at a later date. The test results can be viewed at any time.
- Test data stored in older versions of RadiMation® can be viewed with newer versions, giving access to old test data at any time.
Storage of all relevant data[edit]
All the information that is relevant and necessary to reproduce a test is stored. A summary of the items that are recorded during a test are visible below:
- All the “RAW” measurement date is stored for later evaluation (e.g. all power meter(s), field sensor(s), receiver(s), A/D converter(s) readings, signal generator settings, etc.)
- All the user configurable settings are stored with the measurement data (TSF file settings).
- All the correction and calibration files used during the test are copied and stored with the test results.
- All the test equipment used during the test is stored (Equipment list).
- The date, time and test engineer name are stored with the measurement data.
- Error messages (if any), that occurred during the test are stored with the measurement results.
System verification prior to each test[edit]
An EMC test set-up consists of a number of different test devices, computers and software packages. To maintain a high level of quality control, it is necessary to perform an overall system verification (including the complete test set-up) on a regular basis.
Because of this RadiMation® performs a number of hardware, software and system verifications at the beginning of each test.
Radiated and conducted immunity tests[edit]
- Prior to each test, the software will perform a power delivery test. During this power delivery test, the software increases the output power of the signal generator and measures the output power of the amplifier with the (forward) power meter. If the software measures a stable reading on the power meter, RadiMation® assumes that all the cables between the signal generator, amplifier, coupler and the power meter are connected correctly.
- Prior to each test, the software will perform a linearity check. The software generates a stable signal generator output power, measures it on the power meter and then increases the signal generator level with 4 dB steps. If the power meter reading also increases with 4 dB steps, RadiMation® assumes that the amplifier is linear.
Radiated and conducted emission tests[edit]
Equipment verification prior to each test:
- Prior to each test the RadiMation® Software will check if all the required test equipment can be found. If one or more devices are not found, the software will stop and display an error message.
- Prior to each test the RadiMation® Software will check if communication is possible with all required test equipment (initialization). If one or more devices do not respond correctly, the software will stop and display an error message.
Software settings verification prior to each test:
- Prior to each test the RadiMation® Software will check if all the user configurable settings of the Technical Set-up File (TSF file) are within the limits of the selected test equipment in the equipment list (e.g. does the antenna cover the required frequency range, etc.).
- If a test is started that uses a calibration file, the software will verify if the currently selected test equipment (in the equipment list) is the same as the equipment used during the calibration. This is recommended for the accuracy of the test results. If different equipment was used, the software will display a warning, asking the operator to continue (despite the different equipment) or stop the test.