Document: NRC Regulatory Guide
Document ID: aa450282-f5b0-4dd2-b41a-917a7491deb2
Document Type: regulatory_guide
Title: Preparing Probabilistic Fracture Mechanics (Rev. 0)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML2133/ML21334A158.pdf
Revision Date: 2023-05
Chapter: 
Section ID: RG-1.245
CFR Part: 
CFR Title: 

Content:
rience (previous use in regulatory applications), and status RG 1.245 Revision 0, Page 12 of previous approval for the PFM software. The applicant should follow its SQA program and V&V procedures with these concepts in mind. The applicant should determine to which Table C-2 category its PFM software belongs. The applicant should consider discussing its choice of categorization with the NRC in pre-submittal meetings to ensure that an acceptable determination has been made. The applicant should perform and document SQA and V&V activities for the PFM software according to the guidelines in Table C-2. The NRC has approved applications using the following codes for a specific range of applications as of the publication of this RG: • the latest version of FAVOR, see FAVOR theory manual (Ref. 12) for validated application range • the latest version of xLPR, see xLPR documentation (Ref. 21) for validated application range • the version of the SRRA (Structural Reliability and Risk Assessment) code approved in Ref. 22, for the range approved in the referenced safety evaluation. There may be instances where a code was approved just for a specific application, and these are considered approved for the same exact type of application. RG 1.245 Revision 0, Page 13 Table C-2: SQA and V&V Code Categories Category Description Submittal Guidelines QV-1 Code used in NRC-approved application a QV-1A Exercised within previously validated range • Demonstrate code applicability within the validated range. • Describe features of the specific application where the code is validated and applicable (i.e., areas of known code capability). QV-1B Exercised outside of previously validated range • Provide evidence for the applicability of the code to the specific application with respect to the areas of unknown code capability. • Describe features of the specific application where the code has not been previously validated and applied (i.e., areas of unknown code capability). QV-1C