Abstract

The definition in the ‘‘International Vocabulary of Metrology—Basic and general concepts and associated uncertainties (VIM)’’ [1] of ‘measurement result’ [2] refers to a ‘‘set of quantity values being attributed to a measurand together with any other available information’’. Note 2 to that definition [3] adds: ‘‘A measurement result is generally expressed as a single measured quantity value and a measurement uncertainty. ...’’ (terms in bold mean that they refer to concepts that are themselves defined in VIM). In the VIM, ‘‘Notes’’ are explanatory to definitions and are considered part of them. We discussed the ‘‘quality’’ of a measurement result previously [4–6]. Let us here take a special look at that most important intention we have when we carry out a measurement: the intended use of the result. If the quality of a measurement result is guaranteed by using a ‘measuring system’ [7], which is calibrated by means of an appropriate ‘calibrator’ [8], we could all agree that that would enable to obtain an acceptable result. Just about, but not quite. In daily measurements performed because of specific needs, the ‘measurement uncertainty’ in the measurement result should be small enough for the intended use of the result. However, there is no need that it be much smaller (hence requiring unnecessarily sophisticated and expensive procedures), nor much larger (making the measurement superfluous because leading to an inappropriate result). After all, it is because of the need for some specified use of the result that a measurement is made. Hence, it is logical that it must be designed as such on beforehand. The result should be consistent with the definition of the concept measurement result, whilst at the same time, the expected measurement uncertainty should be fit-for-the-intended-use of that result. In other words, the achieved uncertainty in the result should fall within an approximate (and pre-set) ‘target measurement uncertainty’ [9], which is decided before the measurement. Could it be that in a number of cases, we make too many measurements? Maybe. What more do we wish—or even need—than a measurement result falling within a pre-set target measurement uncertainty? Normally, a complete measurement uncertainty is composed of a combined Type A and Type B evaluation [10, 11]. Carrying out a ‘Type A evaluation of measurement uncertainty’ is easy. It is obtained from calculating a repeatability standard deviation and is usually not critical in most chemical measurement results as it is not generating the biggest component of the full final uncertainty in the result. The ‘Type B evaluation of measurement uncertainty’ usually constitutes the largest component of that full uncertainty and must be ‘‘evaluated’’ by the analyst. It is sufficient to verify that it is expected to fall within the pre-set target measurement uncertainty. If it would be expected to be much larger, there would be no need to make the measurement at all as the Type B uncertainty component is expected to be too large, rendering the result useless. ‘‘Fitness-for-intendeduse’’ of the measurement result is important as it prevents making too many measurements, or requiring too sophisticated measuring systems, all of which bring associated cost. On the other hand, evaluation of the Type B component of the expected uncertainty enables to ascertain whether the measurement is worth to be made at all, as the P. De Bievre (&) Kasterlee, Belgium e-mail: paul.de.bievre@skynet.be

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.