TheAxiomaticHamster
The hamster is undoubtably real.
A bit of premise: I worked in an ISO17205 commercial calibration lab for close to 10 years, and reporting of results was pretty straightforward. We always issued some report with data on all calibrations.
Recently I joined a company and am supporting their internal calibration program within an AS9100 framework. We have requirements to comply with ISO17025:2017, but not become accredited (yet). Our record retention is very good, and we keep all information about a calibration in a secure database.
My question is this: if we are calibrating our assets internally, and we retain all information set out in ISO17025:2017 Section 7.8.2 and 7.8.4 (for calibration reporting) within that database record, do we need to even create or issue a certificate? Or can we retain all of the information in the database record for that asset to be recalled as needed?
Additional information: we do report to the end users when assets are found out of tolerance, and disposition accordingly.
Recently I joined a company and am supporting their internal calibration program within an AS9100 framework. We have requirements to comply with ISO17025:2017, but not become accredited (yet). Our record retention is very good, and we keep all information about a calibration in a secure database.
My question is this: if we are calibrating our assets internally, and we retain all information set out in ISO17025:2017 Section 7.8.2 and 7.8.4 (for calibration reporting) within that database record, do we need to even create or issue a certificate? Or can we retain all of the information in the database record for that asset to be recalled as needed?
Additional information: we do report to the end users when assets are found out of tolerance, and disposition accordingly.