Dewey, who would have thought....as long as your process is documented and in compliance with any site specific requirements....
from ISO/IEC 17025 5.10.4.4 A calibration certificate (or calibration label) shall not contain any recommendation on the calibration interval except where this has been agreed with the customer. This requirement may be superseded by legal regulations. from NIST Recommended Calibration Interval Q. Does NIST require or recommend specific recalibration intervals for measuring instruments, devices or calibration standards? A. In general, NIST does not require or recommend any set recalibration interval for measuring instruments, devices, or standards. Specific recalibration intervals depend on a number of factors including: · Accuracy requirements set by customers · Requirements set by contract or regulation · Inherent stability of the specific instrument or device · Environmental factors that may affect the stability and for a really in-depth method for determining calibration interval (100+ pages) NCSL International document RP-1, Establishment and Adjustment of Calibration Intervals Benjy Bertossi Fermi2 - RP Supervisor 734-586-4935 [email protected] From: "Thompson, Dewey L" <[email protected]> To: "[email protected]" <[email protected]> Date: 04/07/2014 03:32 PM Subject: RE: Powernet: Benchmarking on instrument calibration due dates Sent by: [email protected] Good question Benjy. Callaway's answer is "That's the way we've always done it…….." (Yeah, I know). Another point would be vendors performing calibrations generally set the due date as the complete date plus one year. Not to "justify the practice", but our program allows a grace period, however it requires a conscious decision each time you invoke the grace period. The action has to be logged with the name of who provided the authorization. Most folks that use the end of the month rubric started doing so in order to reduce time and headaches. The idea being that you would pull everything once a month. I'm not convinced this saves all that much, however would welcome feedback from the folks actually doing it. Questions or comments, email or call Dewey at Callaway. Thanks Dewey : : : : : : : : : : : : : : : : : : : : : : : : : Dewey Thompson Staff HP Radiation Protection Department T 314.225.1061 F 573.676.4484 E [email protected] ......................... Ameren Missouri Junction CC & Highway O Fulton, MO 65251 Please consider the environment before printing this e-mail. From: [email protected] [mailto:[email protected]] On Behalf Of Benjy P Bertossi Sent: Monday, April 07, 2014 2:06 PM To: [email protected] Subject: Re: Powernet: Benchmarking on instrument calibration due dates Fermi - due date is end of the month. You could make the case for using the periodicity allowance in your TS / TRM for calibration / functional surveillance grace period, say +25% of calibration periodicity, thus semi annual / annual cals due at the end of month would be well within grace period. For those that use exact due date, what technical reference is used for basis? Benjy Bertossi Fermi2 - RP Supervisor 734-586-4935 [email protected] Inactive hide details for sglee---04/07/2014 11:39:17 AM---Presently Perry RP uses a cal due date for RP instrumentation that esglee---04/07/2014 11:39:17 AM---Presently Perry RP uses a cal due date for RP instrumentation that equals the cal frequency (semi a From: [email protected] To: <[email protected]> Date: 04/07/2014 11:39 AM Subject: Powernet: Benchmarking on instrument calibration due dates Sent by: [email protected] Presently Perry RP uses a cal due date for RP instrumentation that equals the cal frequency (semi annual, annual) plus the time to the end of the month. The other plants in the FENOC fleet use the exact cal date plus frequency as a due date. What does your organization use? A. Due date at the end of the month? B. Exact due date (cal date + frequency)? Additional followup can be forwarded to: Mark Andrei Radiation Protection Supervisor FirstEnergy Nuclear Operating Company x5490 440-280-5490 Thank you. ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. The information contained in this message may be privileged and/or confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. Note that any views or opinions presented in this message are solely those of the author and do not necessarily represent those of Ameren. All e-mails are subject to monitoring and archival. Finally, the recipient should check this message and any attachments for the presence of viruses. Ameren accepts no liability for any damage caused by any virus transmitted by this e-mail. If you have received this in error, please notify the sender immediately by replying to the message and deleting the material from any computer. Ameren Corporation
<<inline: graycol.gif>>
