This post discusses O/T reporting after a calibration. After other posts and re-reading the original post comments, I believe this post is not on topic, but on the chance that the original post description does in fact look for this information it is left.
.
The old MIL STD 45662A and forward wanted O/T reporting. In a strict Z540 calibration lab the item will be tested, and if found O/T the device will be placed on a hold shelf. The customer will recieve an O/T report. Upon recieving back from the customer an alignment go-ahead or return AS-IS the process continues. The O/T report can have many bits of information. All of the information can cause a question, so more information causes more questions. A full blown quote of repair or other defined report should be avoided.
An O/T report should report the O/T condition(s) for Z540.1 / 45662A
1. Description of test
2. Nominal value to be sourced/measured
3. Actual value sourced/measured
4. Tolorance limit
In the world of Z540.3 and ISO 17025 additionally you would add
1. Uncertainty of test
2. A description of degree of PASS* or FAIL* or Fail ("*" for in the uncertainty regions)
For a caliper, an example: All values in inches is reader simple versus a +/-tolorance spec.
This is a single O/T. The report line must be for each O/T-----(17025 only)
Description___Nominal____Actual____Spec low___Spec high__Uncertainty
Measure 1"___1.000,00"__1.005,00"__0.999,00"__1.001,00"___0.000,01"
(This is the AS-Found data only)
A 17025 test PASS* or FAIL* are classified as Unknown compliance, and 17025 test FAIL is an O/T with data.
Any measureable data is an O/T. If no data can be reported the test line becomes a Failure.
A test failure should generate a failure report without any O/T data. A minimal description of failure is listed.
.
The number of O/T can be great, to the point of limiting reporting to a
process system limit of 10 for example. (this is not defined in a standard, but a real world limitation)
Addition descriptions should be limited or absent at best for O/T reports.
Complete Failure reporting is another basket of issues to report.
It is an improper practice to claim a complete failure, when an O/T is present.
A failure is likely not to impact the process because the device could not be used.
An O/T can cause serious problems.
There is the condition/situation where both function/feature failures occur, and other parts of the DUT have O/T conditions.
This situation is a 1-of-100 in the O/T or Failure situation. It is many times not handled properly.
.
Another method of operation is a general O/T notice with limited description/reporting
The entire O/T can be applied to the calibration CERT in the remarks section.
The item was recieved/returned O/T or recieved O/T and adjusted, and returned In Tolorance.
In this case the O/T data can be reported for clarity. This is a highly recomended practice for the CERT.
O/T reporting seems to float about and get lost/misplaced.
The CERTs are protected by the customer and service lab, due to them being the prooof of service etc.
AN O/T report would be defined as having:
1. Customer info
2. Test Lab info
3. DUT info
4. Test date
5. O/T report lines, having one for each O/T
6. Asking for OK to repair/align or return AS-IS is a smart remark line.
(hold DUT until response is given, unless you have customer policy agreement)
Standards and method of testing is not required.
The format comes very close to the content of a Calibration Test CERT
Calibration evolution:
MIL-C-45662=>MIL-STD-45662=>MIL-STD=45662A=>ISO-10012&ANSI/NCSL-Z540.1=>ANSI/NCSL-Z540.3,ISO-17025
GUM from many places, but originating from @ JCGM, BIPM and others n France I believe.
.
.......I just realized the O/T report you are are asking about is not one issued after a calibration, but after finding a gage in an in-house process being O/T, and possibly causing O/T product being shipped. The O/T of a gage would cause an Impact analysis and report. If the O/T was believed to impact in-house product(s) or customer's product(s) as a result, then reporting of the event is required, and then also CAPA and other action(s). The following posts reflect those views
Hope this helps...............