Document: NUREG-0800
Document ID: 4e1d86bd-74a5-4678-8bc0-ffce3ba28ea0
Document Type: srp
Title: RISK-INFORMED INSERVICE TESTING
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML0428/ML042880272.pdf
Revision Date: 2023-06
Chapter: 3
Section ID: 3.9.7
CFR Part: 
CFR Title: 

Content:
st, the performance monitoring should help confirm that no unexpected failure mechanisms that are related to the revised test strategy become important enough to alter the failure rates assumed in the justification of proposed changes. Second, performance monitoring should, to the extent practicable, ensure that adequate component capability margin exists, above that required during design-basis conditions, so that component operating characteristics over time do not 3.9.7-5 Rev. 0-August 1998 result in reaching a point of insufficient margin before the next scheduled test activity. Regulatory Guide 1.175 provides guidance on performance monitoring when testing under design-basis conditions is impracticable. In most cases, component-level monitoring will be expected. Two important aspects of performance monitoring are whether the test frequency is sufficient to provide meaningful data and whether the testing methods, procedures, and analysis are adequately developed to ensure that performance degradation is detected. Component failure rates should not be allowed to rise to unacceptable levels (e.g., significantly higher than the failure rates used to support the change) before they are detected and corrected. 3. Feedback and Corrective Action Program A performance-based corrective action program should be a part of the licensee's proposed implementation and monitoring plan. 4. Periodic Reassessment The reviewer should examine the licensee's RI-IST program to ensure that it contains provisions whereby the overall program is periodically evaluated and component performance data gets fed back into both the component categorization and component test strategy determination (i.e., test frequency and methods) process. These assessments should also take into consideration corrective actions that have been taken on past IST program components. [This periodic reassessment should not be confused with the 120-month program updates required by 10 CFR 50.55a(f)(5)(i), whereby