Views:

As far as the not reporting anything less than your CMC goes –

 

One of the ILAC P14 requirements state in 5.4 “Contributions to the uncertainty stated on the calibration certificate shall include relevant short-term contributions during calibration and contributions that can reasonably be attributed to the customer’s device. Where applicable the uncertainty shall cover the same contributions to uncertainty that were included in evaluation of the CMC uncertainty component, except that uncertainty components evaluated for the best existing device shall be replaced with those of the customer’s device. Therefore, reported uncertainties tend to be larger than the uncertainty covered by the CMC. Contributions that cannot be known by the laboratory, such as transport uncertainties, should normally be excluded in the uncertainty statement. If, however, a laboratory anticipates that such contributions will have significant impact on the uncertainties attributed by the laboratory, the customer should be notified according to the general clauses regarding tenders and reviews of contracts in ISO/IEC 17025.”

 

Based on the information in this section, two things can be derived from it:

 

  • The contributions documented in the CMC are those normally found in the particular calibration process, except that the CMC uses a best existing device (a device that could possibly have no standard deviation, and the best resolution possible for a real device).
  • When real uncertainties are with the customer unit (DUT), then the real standard deviation and real resolution should be used.  NOT the best case one that we used in our CMC budget.

 

So if you calculate your CMC with Standard Deviation of 0 (zero) and DUT resolution of the best available real device (such as the 8 ½ digits of resolution associated with the Fluke 8588A) but still show them (as placeholders) in your uncertainty budget, then…when MET/CAL calculates it will always be will always be larger, when it takes into account the “real” standard deviation and “real” DUT resolution.  Which fully meets and supports the 5.4 section.

 

Let me know if you wish to discuss this, but this has been reviewed by our Chief Corporate Metrologist (Jeff Gust) and our former one (David Deaver) along with several customers during Audits.

 

The biggest issue is knowing what to state to an Auditor when they ask “why did you not put in a value for those uncertainty components in your budget?”.

As long as you explain the ““Calibration and Measurement Capability” as above then you can do it quite easily with the MET/CAL software.