Document: NUREG-0800
Document ID: 7916b088-fb90-4163-84fe-027bd315bcc5
Document Type: srp
Title: REVIEW OF RISK INFORMATION USED TO SUPPORT PERMANENT PLANT-
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML0717/ML071700658.pdf
Revision Date: 2023-06
Chapter: 19
Section ID: 19.2
CFR Part: 
CFR Title: 

Content:
eather), the licensee should consider the effects of the change and provide the rationale for why additional PRA analyses are not necessary. This rationale could be addressed by assessing the level of redundancy and diversity provided by the plant systems, system trains, human actions, etc., for responding to these unanalyzed initiating events. The licensee should also show that the proposed change does not introduce unanalyzed vulnerabilities and that redundancy and diversity will still exist in the plant response capability after the changes are implemented. This issue is addressed acceptably if the proposal fulfills any one of the following criteria: • The licensee addresses all modes and all initiator types using PRA. 19.2-14 June 2007 • The licensee demonstrates that the application does not unacceptably degrade plant capability and does not introduce risk vulnerabilities or remove elements of the plant response capability from programmatic activities aimed at ensuring satisfactory safety performance for plant modes and initiator types not included in the PRA. • If the proposed change impacts unanalyzed plant modes or initiator types, the licensee demonstrates that a bounding analysis of the change in plant risk from the application (e.g., by qualitative arguments, or by use of sensitivity studies) meets guidelines that are equivalent to the acceptance guidelines specified in Regulatory Guide 1.174, Section 2.2.4. III.2.2.3 Level of Detail The level of detail in a PRA required to support an application should be such that the proposed changes to the plant can be adequately characterized in the PRA model elements, as discussed in Subsection III.2.2.1 of this SRP section. In addition, the PRA should be detailed enough to account for important system and operator dependencies (functional, operational, and procedural), especially for those components affected by the application. A review of the licensee's failure modes and effects analysis and a review of