ML20276A148

Modification No. 001 to Task Order No. 31310020F0101 Under Contract No. 31310020D0003

ML20276A148
Person / Time
Issue date:	09/29/2020
From:	Mike Williams Acquisition Management Division
To:	Hattery G Engineering Mechanics Corp of Columbus
References
31310020D0003
Download: ML20276A148 (27)

Text

31310020D0003/31310020F0101 Page 4 coolant system pipe ruptures to fully address and quantify uncertainties and directly demonstrate compliance with the probabilistic requirements of 10 CFR Part 50, Appendix A, Criterion 4.

To develop the capability to perform the necessary probabilistic analyses, RES worked in collaboration with the Electric Power Research Institute to develop a new computer code called Extremely Low Probability of Rupture (xLPR). xLPR is a state-of-the-art probabilistic fracture mechanics code for piping applications. Code development was a multi-year effort that built on the results of a successful pilot study. The code was designed, built, and tested under a rigorous software quality assurance program and provides regulators, industry, researchers, and the public with new quantitative capabilities to analyze the risks associated with nuclear power plant piping systems subject to degradation mechanisms. Core capabilities of the code include modeling fatigue, stress-corrosion cracking, inservice inspection, chemical and mechanical mitigation, leak rates, and seismic effects.

As the initial regulatory application of xLPR Version 2.0 (V2.0), RES has used the code to study the impacts of PWSCC in systems that have been granted prior NRC leak-before-break approval under 10 CFR Part 50, Appendix A, Criterion 4. These activities included sensitivity studies to identify which models, sub-models, and types of input variables contribute most significantly to uncertainty in the results from the code. RES also used xLPR V2.0 to re-evaluate previous leak-before-break analyses for a subset of the current fleet of plants. The re-evaluations considered the impacts of PWSCC, fatigue, inservice inspection, and mitigation to determine the trend in rupture frequencies and other metrics. With the completion of these activities, RES needs to complete re-evaluations of previous of leak-before-break analyses for the remaining plants in the fleet. In addition, RES needs to consider the results and assess current leak-before-break regulations and guidance and, if applicable, make recommendations for enhancement.

Beyond leak-before-break studies, the xLPR code supports broader NRC efforts to further the use of probabilistic fracture mechanics analyses using state-of-the-art computational tools. To this end, RES has begun publicly distributing the xLPR code with the goal of establishing a user group. Public availability of xLPR V2.1 was announced in [2] and details about the code have been presented in various NRC public meetings [3] and [4]. Public distribution and user group participation benefits the NRC in several respects. For example, the broader user base: (a) exercises the code more thoroughly than would be possible if use were limited to only NRC applications, (b) increases confidence in the codes capability to accurately model individual phenomena and system behavior over the required range of conditions, (c) reduces the level of effort required by RES to ensure the validity of the codes results, and (d) leverages expertise of the users as they identify code deficiencies and errors and propose fixes. Public distribution is further expected to increase use of the xLPR code to support licensing actions and codes and standards development, and RES needs to maintain the necessary capabilities to support the related regulatory reviews. In concert with these activities, support for continued maintenance and development of the xLPR code is necessary to ensure its long-term usability.

List of

References:

[1] NUREG-0800, Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power Plants: LWR Edition, Section 3.6.3, Leak-Before-Break Evaluation Procedures, Revision 1, March 2007, NRC Agency wide Documents Access and Management System

31310020D0003/31310020F0101 Page 5 (ADAMS) Accession No. ML063600396

[2] Extremely Low Probability of Rupture (xLPR) Probabilistic Fracture Mechanics Code Version 2.1 Public Release Announcement, NRC ADAMS Accession No. ML20157A120

[3] Summary of the April 23, 2020, RES Category 3 Public Meeting with EPRI and Stakeholders to Discuss Public Release of the xLPR Probabilistic Fracture Mechanics Code, NRC ADAMS Accession No. ML20142A303

[4] Summary of the June 3, 2020, RES Category 3 Public Meeting with EPRI and Stakeholders to Discuss Models in the xLPR Probabilistic Fracture Mechanics Code, NRC ADAMS Accession No. ML20182A086

3. OBJECTIVE(S)

The objective of this task order is to obtain expert technical assistance services from the Contractor to support component integrity assessments. Support is needed in areas such as the application, maintenance, and development of computational tools and methodologies for performing component integrity assessments. Support is also needed to analyze emerging issues and evaluate and develop codes and standards and other aspects of NRCs regulatory framework related to component integrity.

This requirement falls under Technical Support Service Area (TSSA) 3.4, entitled Component Integrity and Materials Performance.

4. STATEMENT OF WORK TASKS Task 1: Generalization Study The Contractor shall use the xLPR code to study the impacts of PWSCC for the entire fleet of U.S. pressurized-water reactors (PWRs) to determine whether any changes are needed to current regulatory requirements and guidance related to leak-before-break. The use of other computational tools may be needed to develop inputs for or otherwise support the analyses performed using the xLPR code. Specific activities include, but are not limited to, the following:

A. The Contractor shall review and categorize all PWR piping systems previously approved for leak-before break. The goal of this review and categorization is to reduce, to the extent practical, the number of analyses that will need to be performed.

B. The Contractor shall define the specific analyses necessary to bound each category of piping system. Factors present in the PWR fleet, such as PWSCC mitigation techniques and inservice inspection, shall be considered. Definition of the analyses may be an iterative process, and the results from prior studies should be used to inform this effort.

C. The Contractor shall determine and develop the inputs necessary to perform each of the analyses. Sources for inputs could include the open literature, xLPR-related documentation, prior studies and analyses, and docketed correspondence available from both internal and external NRC ADAMS. The Contractor may also need to perform finite element analyses to develop weld residual stress profile inputs. The Contractor shall promptly communicate any input gaps that it cannot fill to the COR.

31310020D0003/31310020F0101 Page 6 D. The Contractor shall execute the analyses using the xLPR code. The Contractor shall compare the results of these analyses against acceptance criteria identified by the COR.

E. Based on the results of the analyses, the Contractor shall prepare an assessment of current regulatory requirements and guidance related to leak-before-break. Recommendations for enhancing these regulations and guidance shall be provided as appropriate.

Task 1 Completion Date: The task shall be completed by August 31, 2021.

Task 1 Anticipated Travel: One trip for up to 3 Contactor personnel of up to 3 days duration to NRC Headquarters from the Contractors office(s). (Total of 1 Trip)

Task 1 Deliverables: The Contractor shall prepare an Analysis Plan for completion of this task.

The Analysis Plan shall, at minimum, include the categories of piping systems, analyses that will be performed to bound each category, completion schedule and status of each analysis, and any potential input gaps. The Contractor shall submit the Initial Analysis Plan to the COR no later than 30 days after award of the task order. Thereafter, the Contractor shall maintain and update the Analysis Plan as needed until the task is complete. The Analysis Plan Updates shall be provided to the COR biweekly until the analyses are complete and incorporate any comments provided by the COR.

The Contractor shall submit information (e.g., code input and output files) from the analyses executed per the Analysis Plan (as updated) as they are completed.

In addition, the Contractor shall prepare a Technical Letter Report (TLR) covering all work performed under this task. The Contractor shall prepare the TLR in parallel with performing the analyses executed per the Analysis Plan (as updated). In-progress drafts of the TLR shall be submitted to the COR monthly. The in-progress TLR drafts shall incorporate any comments provided by the COR on the previous submission. The Contractor shall complete the TLR after executing all the analyses in the Analysis Plan (as updated). The Contractors completed TLR shall be submitted by March 01, 2021.

Thereafter, the Contractor shall support the NRC staffs review of the TLR. The review will be completed in several stages and may take up 5 months to complete. The COR will communicate comments generated as a result of this review process to the Contractor. The Contractor shall address all comments and prepare interim updates to the TLR as necessary.

Some comments may require the Contractor to perform additional analyses to address. Interim updates to the TLR shall be provided to the COR biweekly during the review process through July 31, 2021. The Contractor shall finalize and submit the TLR in a form ready for NRC publication by August 31, 2021.

Task 2: xLPR Code Maintenance, Development, and Technical Support Task 2a - xLPR Code Maintenance and Development As directed by the COR, the Contractor shall provide technical assistance to support xLPR code maintenance and development needs. Maintenance activities include, but are not limited to:

developing modifications to code-related products, such as the source and executable code,

31310020D0003/31310020F0101 Page 7 user manual, data libraries, configuration control documents, and other reference files and documents, to correct identified problems, improve performance or maintainability, keep the products usable in a changed or changing environment, and detect and correct latent faults.

Maintenance activities also include, but are not limited to: (a) configuration management, (b) documenting, tracking, and processing maintenance requests, (d) performing testing necessary to ensure proper functionality of the code following maintenance-related changes, and (e) electronic storage of files. Development activities include modifications that significantly expand the functional capabilities of the xLPR code.

All maintenance and development activities shall be performed in accordance with the xLPR Software Maintenance Plan, as may be revised from time-to-time, and any implementing procedures as directed by the COR. In addition, all Contractor personnel involved in maintaining or developing the xLPR code shall receive training as specified in the xLPR Software Maintenance Plan and participate in any other supplemental training as directed by the COR. The Contractor shall coordinate its maintenance and development activities with other code maintainers as directed by the COR. It also may be necessary or advantageous for the Contractor to prepare, deliver, and maintain electronic systems to support the effective and efficient performance of the maintenance and development activities. Such systems shall be implemented as approved by the COR.

Task 2b - xLPR Code Technical Support Under this task, the Contractor shall provide a broad range of technical assistance support related to the xLPR code and its various applications. It includes support for the NRC staff, general analysis and technical support, and support to build the community of public xLPR code users.

Upon request, the Contractor shall assist users from the NRC staff with proper use of the code.

Support may include, but is not limited to, areas such as:

assisting with code installation preparing, optimizing, and troubleshooting issues with inputs investigating, interpreting, and resolving code errors and warnings extracting, aggregating, and interpreting results responding to questions about operation of the code and the models contained therein The Contractor shall respond to all NRC staff user support requests within 2 business days.

Support shall be provided via phone, email, or both as appropriate to facilitate the most expeditious resolution. When the total time required to respond to a request is anticipated to or exceeds 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the Contractor shall notify the COR. Thereafter, any further technical assistance related to the request shall be limited to the time authorized by the COR.

In addition, as directed by the COR, the contractor shall provide general analysis and technical support, including but not limited to:

developing inputs performing analyses using the code and analyzing and interpreting the results conducting sensitivity studies and other statistical analyses investigating and implementing custom changes to the code to accommodate analysis needs assisting with resolution of technical review comments on documents

31310020D0003/31310020F0101 Page 8 developing and delivering training providing support for resolution of emergent issues The Contractor shall also assist with activities to support and build the community of public users of the code. This will primarily include support for holding up to 3 meetings or workshops per year. These events will generally serve as a venue for sharing information about the code and to provide a means for code users to interface with each other. Contractor support could include, but is not limited to, preparing and delivering guidance and training, conducting studies pertaining to the code and presenting the results, and other engagement activities, The events may be held either in-person or virtually; however, only one event per year may be held in-person.

Task 2 Completion Date: Expiration date of the Task Order.

Task 2 Anticipated Travel: One trip per year for up to 2 Contactor personnel of up to 3 days duration to locations at distances similar to NRC Headquarters from the Contractors office(s)

(Total of 4 Trips)

Task 2 Deliverables: Task 2a deliverables are as required by the xLPR Software Maintenance Plan depending on the scope of the particular maintenance activities assigned by the COR.

Task 2b deliverables are the draft materials presented at the user group meetings, which shall be submitted no later than 15 days before the meeting is scheduled to be held. The Contractor shall incorporate any comments on the draft presentation materials from the COR. The contractor shall provide the final presentation materials no later than 5 days before the meeting is scheduled to be held.

Task 3: Codes and Standards Technical Support This task requires the contractor to participate in American Society of Mechanical Engineers (ASME) Boiler and Pressure Vessel (B&PV) Code committees within Section XI,Section III, and other appropriate code groups, as instructed by the COR. Some of the issues of importance presented at the committee meetings pertain to aging effects and component integrity issues.

In addition, it is anticipated that new developments and results obtained using the xLPR code (e.g., new code cases) will be introduced to the ASME B&PV committees. Technical support is needed so that the NRC staff may adequately understand the technical and regulatory issues associated with related code actions so that it may vote appropriately. Accordingly, the Contractor shall prepare for, attend, and prepare a summary of the topics, discussions, and any presentations given at the regular ASME B&PV code meetings. As directed by the COR, the Contractor shall also provide support outside of the regular code meetings. This may include assisting the NRC staff with preparing its own code actions or with reviewing code cases or other proposed code actions.

Task 3 Completion Date: Expiration date of the Task Order.

Task 3 Anticipated Travel: Four trips per year for up to 2 Contactor personnel of up to 3 days duration to locations at distances similar to NRC Headquarters from the Contractors office(s)

(Total of 4 Trips)

31310020D0003/31310020F0101 Page 9 Task 3 Deliverables: For any Contractor presentations given at the ASME B&PV Code meetings, the draft presentation materials shall be submitted no later than 2 weeks before each meeting. The final presentation materials incorporating any comments from the COR shall be submitted no later than 1 week before each meeting. The Contractor shall prepare and submit a letter report summarizing the meeting minutes and the presentations made at the ASME meetings no later than 2 weeks after each meeting.

Task 4: Ad-Hoc Technical Support The Contractor shall provide ad-hoc technical assistance to the NRC as directed by the COR.

This technical assistance may include, but is not limited to, the following topics:

I. Benchmarking studies.

II. Providing training to NRC staff on component integrity topics.

III. Support for emerging needs on component integrity issues.

IV. Severe accident considerations on piping issues. Severe accidents, such as seismic damage or high temperature faulted conditions may occur that require help from the contractor to investigate.

V. Confirmatory analyses on an as-needed basis.

VI. Emergency needs for rapid assistance on piping related technical issues as they arise.

VII. Testing to enhance computational tool models and databases. This may include:

a. material testing, such as fracture testing, cyclic testing for mixed hardening WRS fields, creep test update for post-weld heat treatment improvements

b. leakage rate testing Task 4 Completion Date: Expiration date of the Task Order.

Task 4 Anticipated Travel: None.

Task 4 Deliverables: For each technical assistance request from the COR, the contractor shall prepare and submit a Draft TLR covering all work performed no later than 30 days of completion of the work. Each Draft TLR shall summarize the efforts completed, propose conclusions, and identify recommendations for any issues identified. If the contractor performs material testing, the Draft TLR shall also include thorough descriptions of any material testing performed under this task, including test procedures and matrices, and all test results. The contractor shall also provide any test results in their raw data form and in Excel. The contractor shall prepare a Final TLR incorporating any comments on the Draft TLR from the COR. The contractor shall provide the Final TLR no later than 30 days after the receipt of comments from the COR.

5. APPLICABLE DOCUMENTS AND STANDARDS The following documents and standards are applicable to the Task Order:

ASME BPV Code, Sections III and XI xLPR Software Maintenance Plan

6. DELIVERABLES/MILESTONE SCHEDULE AND REPORTING REQUIREMENTS The contractor shall provide the deliverables stated in the table below in electronic format unless otherwise directed by the COR. The electronic format shall be provided using a Microsoft-based product, (e.g., Outlook, Word, Excel, PowerPoint) unless the COR and the

31310020D0003/31310020F0101 Page 10 contractor specifically agree on another format. All deliverables, with the exception of the Monthly Letter Status Report (MLSR) shall be in the format of draft version, revision version with redline/strikeout with a change-control appendix, and a revised version which shall become the final version. The contractor shall maintain appropriate version control in an electronic format.

The contractor shall explicitly state in its submittal(s) that the product provided is the deliverable for Task/Subtask XX, as further described below.

The Contractor shall submit the following deliverables to the Task Order COR. Unless otherwise directed by the COR or the Contracting Officer (CO), the Contractor must provide all deliverables except the MLSR as draft products. The COR will review all draft deliverables (and coordinate any internal NRC staff review, if needed) and provide comments back to the contractor. The Contractor shall revise the draft deliverable based on the comments provided by the COR and then deliver a revised version of the deliverable, which will then be considered the Final Version. When mutually-agreed upon between the Contractor and the COR, the Contractor may submit preliminary or partial drafts to help gauge the Contractors understanding of the particular work requirement. More than one round of drafts may be needed if the Contractor does not successfully incorporate the CORs comments on the previous draft.

The Contractor shall develop, maintain, and control data, files, information, and deliverables pursuant to this Task Order.

DELIVERABLE/MILESTONE SCHEDULE Task No.

Description Due Date 1

Initial Analysis Plan 30 days after award of the task order 1

Analysis Plan Updates Biweekly until the Contractor completes all the analyses 1

Analysis information (e.g., code input and output files)

Submitted as the analyses are completed 1

In-progress TLR drafts Submitted monthly 1

Completed TLR March 01, 2021 1

Interim TLR updates in response to NRC staff review comments Submitted biweekly during the review process through July 31, 2021 1

Final TLR August 31, 2021 2a Deliverables are as required by the xLPR Software Maintenance Plan depending on the scope of the particular maintenance activities assigned by the COR.

As directed by the COR 2b Draft xLPR User Group presentation materials No later than 15 days before the meeting is scheduled to be held 2b Final xLPR User Group presentation materials incorporating any comments from the COR No later than 5 days before the meeting is scheduled to be held 3

Draft ASME B&PV Code meeting presentation materials No later than 2 weeks before each meeting 3

Final ASME B&PV Code meeting No later than 1 week before each

31310020D0003/31310020F0101 Page 11 presentation materials incorporating any comments from the COR meeting 3

Letter report summarizing the topics, discussions, and any presentations given at the ASME B&PV code meetings No later than 2 weeks after each of the meetings 4

Draft TLR covering all work performed in response to each technical assistance request from the COR. Each draft TLR shall summarize the efforts completed, propose conclusions, and identify recommendations for any issues identified.

Duration for support in response to each technical assistance request is to be agreed-upon with the COR. Draft TLRs are due no later than 30 days after of completion of the work.

4 Final TLR incorporating any comments from the COR.

30 days after contractor receipt of COR comments. If applicable, revisions are due 30 days after COR request for a revision.

All MLSRs of the IDIQ contract. The MLSRs shall include detailed summary of the work effort carried out and the labor hours expended on each labor category for the tasks.

20th calendar day of the following month The contractor shall submit the raw and processed data and worksheet and/or input files used in analyses with the Draft TLRs, upon request by the COR and with the Final TLRs, in a tabulated Excel format or other format as directed by the COR.

7. REQUIRED LABOR CATEGORIES Labor Category Minimum Qualification Requirement

31310020D0003/31310020F0101 Page 12 Project Manager (PM)

1) B.S. in Engineering, Science, or similar technical

field, And,

2) Minimum 10 years of regulatory research project management and oversight experience Education and Skillsets that are not Required, but Desired for this Task Order Requirement:

M.S. in Engineering, Science, or similar technical field, or equivalent research and/or academic experience Demonstrated experience in working with/ managing with NRC regulatory research projects Demonstrated experience in materials science research Demonstrated experience managing computer code maintenance and development activities Knowledge of piping fracture issues in light-water reactor nuclear power plants Knowledge of NRC regulations and guidance as they pertain to leak-before-break Knowledge of nuclear power plant component integrity issues, such as corrosion, fatigue, stress-corrosion cracking, thermal and mechanical loadings and resulting stresses Knowledge of American Society of Mechanical Engineers (ASME) codes and standards pertinent to nuclear power plant design and inservice inspection

31310020D0003/31310020F0101 Page 13 Subject Matter Expert (SME)

1. Ph.D. in Engineering, Science, or similar technical

field, And,

2. Minimum combined 20 years experience covering all the following key technical areas:

Expertise in probabilistic fracture mechanics computer code maintenance, development, and applications Expertise in the use of finite element methods with specialized knowledge of user defined subroutines using the ABAQUS computer code (https://www.3ds.com/products-services/simulia/products/abaqus/)

Detailed knowledge of probabilistic risk assessment methods Expertise performing sensitivity analyses, sensitivity studies, stability analyses, uncertainty analyses, and other statistical analyses Detailed knowledge of piping fracture issues in light-water reactor nuclear power plants Detailed knowledge of NRC regulations and guidance as they pertain to leak-before-break Detailed knowledge of nuclear power plant component integrity issues, such as corrosion, fatigue, stress-corrosion cracking, thermal and mechanical loadings and resulting stresses Detailed knowledge of ASME codes and standards pertinent to nuclear power plant design and inservice inspection

31310020D0003/31310020F0101 Page 14 Senior Technical Reviewer/

Researcher

1. Ph.D. in Engineering, Science or similar technical

field, And,

2. Minimum combined 10 years experience covering all the following key technical areas:

Expertise in probabilistic fracture mechanics computer code maintenance, development, and applications Expertise in the use of the GoldSim (http://www/goldsim.com) Monte Carlo simulation software Expertise in the development and use of the Extremely Low Probability of Rupture (xLPR) probabilistic fracture mechanics code, Version 2.0 or later (https://www.nrc.gov/about-nrc/regulatory/research/safetycodes.html)

Expertise performing sensitivity analyses, sensitivity studies, stability analyses, uncertainty analyses, and other statistical analyses Detailed knowledge of piping fracture issues in light-water reactor nuclear power plants Detailed knowledge of NRC regulations and guidance as they pertain to leak-before-break Detailed knowledge of nuclear power plant component integrity issues, such as corrosion, fatigue, stress-corrosion cracking, thermal and mechanical loadings and resulting stresses Detailed knowledge of ASME codes and standards pertinent to nuclear power plant design and inservice inspection

31310020D0003/31310020F0101 Page 15 Technical Reviewer

1. M.S. in Engineering, Science or similar technical

field, And,

2. Minimum combine 10 years experience covering all of the following key technical areas:

Expertise in probabilistic fracture mechanics computer code maintenance, development, and applications Expertise in the use of finite element methods with specialized knowledge of user defined subroutines using the ABAQUS computer code (https://www.3ds.com/products-services/simulia/products/abaqus/)

Expertise in the use of the GoldSim (http://www/goldsim.com) Monte Carlo simulation software Expertise in the development and use of the Extremely Low Probability of Rupture (xLPR) probabilistic fracture mechanics code, Version 2.0 or later (https://www.nrc.gov/about-nrc/regulatory/research/safetycodes.html)

Knowledge of piping fracture issues in light-water reactor nuclear power plants Knowledge of NRC regulations and guidance as they pertain to leak-before-break Knowledge of nuclear power plant component integrity issues, such as corrosion, fatigue, stress-corrosion cracking, thermal and mechanical loadings and resulting stresses Knowledge of ASME codes and standards pertinent to nuclear power plant design and inservice inspection

8. GOVERNMENT-FURNISHED PROPERTY The NRC shall furnish to the following property for the performance of this task order:

Access to all results from previous NRC task orders, as needed for this project per the CORs determination, including all past data, analyses, and reports.

Access to NRCs internal ADAMS shall be provided to the Contractors personnel for the search and retrieval of proprietary information.

Access to EPRI technical reports and data obtained through applicable NRC-EPRI Memoranda of Understanding, as needed for this project per the CORs determination.

Access to xLPR source and executable code, user manual, data libraries, configuration control documents, and other reference files and documents pertinent to development and maintenance of the xLPR code, as needed for this project per the CORs determination.

9. PERIOD OF PERFORMANCE

31310020D0003/31310020F0101 Page 16 Refer to Section F.2 TASK/DELIVERY ORDER PERIOD OF PERFORMANCE

10. PLACE OF PERFORMANCE The work to be performed under this task order shall be performed at the Contractors facility except for the travel described in Section 11.1 of this statement of work.

11. SPECIAL CONSIDERATIONS 11.1 TRAVEL/MEETINGS The following travel* may occur under this Task Order:

• Attendance at meeting may be in person or virtually, as approved by the COR.

Travel Description Task(s)

Location Date Days Attendees Months 1 -12 Program Review at NRC Various Rockville, MD TBD 2

Up to 3 Task Planning or Results Presentation 1

Rockville, MD TBD 3

Up to 3 xLPR Code Maintenance, Development and Support 2

TBD TBD 3

Up to 2 ASME B&PV Code Meeting 3

TBD 11/2020 3

Up to 2 ASME B&PV Code Meeting 3

TBD 02/2021 3

Up to 2 ASME B&PV Code Meeting 3

TBD 05/2021 3

Up to 2 ASME B&PV Code Meeting 3

TBD 08/2021 3

Up to 2 Months 13-24 Program Review at NRC Various Rockville, MD TBD 2

Up to 3 xLPR Code Maintenance, Development and Support 2

TBD TBD 3

Up to 2 ASME B&PV Code Meeting 3

TBD 11/2021 3

Up to 2 ASME B&PV Code Meeting 3

TBD 02/2022 3

Up to 2

31310020D0003/31310020F0101 Page 17 ASME B&PV Code Meeting 3

TBD 05/2022 3

Up to 2 ASME B&PV Code Meeting 3

TBD 08/2022 3

Up to 2 Months 25-36 Program Review at NRC Various Rockville, MD TBD 2

Up to 3 xLPR Code Maintenance, Development and Support 2

TBD TBD 3

Up to 2 ASME B&PV Code Meeting 3

TBD 11/2022 3

Up to 2 ASME B&PV Code Meeting 3

TBD 02/2023 3

Up to 2 ASME B&PV Code Meeting 3

TBD 05/2023 3

Up to 2 ASME B&PV Code Meeting 3

TBD 08/2023 3

Up to 2 Months 37-48 Program Review at NRC Various Rockville, MD TBD 2

Up to 3 xLPR Code Maintenance, Development and Support 2

TBD TBD 3

Up to 2 ASME B&PV Code Meeting 3

TBD 11/2023 3

Up to 2 ASME B&PV Code Meeting 3

TBD 02/2024 3

Up to 2 ASME B&PV Code Meeting 3

TBD 05/2024 3

Up to 2 ASME B&PV Code Meeting 3

TBD 08/2024 3

Up to 2 Travel Notes -

a. All Contractor travel requires prior written approval from the COR.

b. The number of trips, number of contractor personnel, duration, location, may be modified based on meeting circumstances and COR's need for contractor support. Contractor shall implement travel cost-sharing measures (e.g., sharing rental car) if possible.

c. At the discretion of the COR, meetings may be conducted via telephone, video conference, or at the Contractors office(s).

d. All travel conducted pursuant to this task order is billable at Federal per diem rates, in accordance with Federal Travel Regulations.

31310020D0003/31310020F0101 Page 18 11.2 SECURITY The work will be UNCLASSIFIED; but requires an IT Security Level II Access.

Work on this task order may involve the handling of documents that contain proprietary information. The contractor shall safeguard documents containing proprietary information against unauthorized disclosure. After completion of work, the contractor shall either destroy the documents or return them to the NRC. If they are destroyed, please confirm this in an e-mail to the COR with a copy to the CO and include the date and manner in which the documents were destroyed.

11.3 KEY PERSONNEL Refer to Section H.5 KEY PERSONNEL for Name and Labor Category/ Position of Key Personnel.

Contractor personnel performing this work shall have experience and/or education -- at a minimum a bachelors degree in engineering/science or equivalent experience and at least 20 years of related experience (combined of all staff) in one or more of the following key technical areas:

Expertise in probabilistic fracture mechanics computer code maintenance and development Expertise in finite element method with specialized knowledge of user defined subroutines using ABAQUS computer code (https://www.3ds.com/products-services/simulia/products/abaqus/)

Expertise in the use of GoldSim (http://www/goldsim.com) probabilistic risk assessment suite of software Expertise in the use of the xLPR probabilistic fracture mechanics code, Version 2.0 or later (https://www.nrc.gov/about-nrc/regulatory/research/safetycodes.html)

Detailed knowledge of probabilistic risk assessment Detailed knowledge of uncertainty characterization methodologies Detailed knowledge of primary system piping fracture issues in light-water reactor nuclear power plants Detailed knowledge of NRC regulations and guidance as they pertain to leak-before-break in primary system piping in PWRs Detailed knowledge of corrosion, PWSCC, thermal and mechanical loadings and resulting stresses Detailed knowledge of ASME codes and standards pertinent to nuclear power plant design and inservice inspection 11.4 KEY EQUIPEMENT, CERTIFICATIONS, and ANALYSIS TOOLS The following analysis tools shall be required to perform the research described in this statement of work:

Finite element analysis capabilities with specialized user-defined subroutines using the ABAQUS commercial off-the-shelf software.

Commercial off-the-shelf software required in order to run the xLPR code, including, but not

31310020D0003/31310020F0101 Page 19 limited to, Microsoft Windows, Microsoft Excel, and GoldSim. Specific versions to be identified by the COR.

11.5 SPEECHES, PRESENTATIONS, PAPERS, AND JOURNAL ARTICLES The Contractors investigator(s) may publish the results of this work in the open literature or may present papers at public or association meetings at interim stages of the work if the article or paper has been reviewed by the COR in draft form and agreement has been reached on the content. Submit the work in final form to the COR, accompanied by NRC Form 390A, Release to Publish Unclassified NRC Contractor Speeches, Presentations, Papers, and Journal Articles.

If agreement on the content has not been reached, NRC may also require that the paper include, in addition to the standard statement Work Supported by the U.S. Nuclear Regulatory Commission, any caveats necessary to cover NRC objections. If NRC objections cannot be covered in this manner, NRC can refuse to authorize publication in the open literature and/or presentation of papers.

The Contractor shall place the following disclaimer on all published papers and articles:

This report was prepared as an account of work sponsored by an agency of the U.S.

Government. Neither the U.S. Government nor any agency thereof, nor any of their employees, makes any warranty, expressed or implied, or assumes any legal liability or responsibility for any third partys use, or the results of such use, of any information, apparatus, product, or process disclosed in this report, or represents that its use by such third party would not infringe privately owned rights. The views expressed in this paper are not necessarily those of the U.S.

Nuclear Regulatory Commission.

For additional information, see NRC Management Directive 3.9, NRC Staff and Contractor Speeches, Presentations, Papers, and Journal Articles on Regulatory and Technical Subjects.

Section D - Packaging and Marking was added and reads as follows.

D - Packaging and Marking D.1 PACKAGING AND MARKING (a) The Contractor shall package material for shipment to the NRC in such a manner that will ensure acceptance by common carrier and safe delivery at destination. Containers and closures shall comply with the Surface Transportation Board, Uniform Freight Classification Rules, or regulations of other carriers as applicable to the mode of transportation.

(b) On the front of the package, the Contractor shall clearly identify the contract number under which the product is being provided.

(c) Additional packaging and/or marking requirements are as follows: Identify Task Order COR.

D.2 BRANDING

31310020D0003/31310020F0101 Page 20 The Contractor is required to use the statement below in any publications, presentations, articles, products, or materials funded under this contract/order, to the extent practical, in order to provide NRC with recognition for its involvement in and contribution to the project. If the work performed is funded entirely with NRC funds, then the contractor must acknowledge that information in its documentation/presentation.

Work Supported by the U.S. Nuclear Regulatory Commission (NRC), Office of Office of Nuclear Regulatory Research, under Contract/order number 31310020D0003_31310020F0101.

Section F - Deliveries or Performance was added and reads as follows.

F - Deliveries or Performance F.1 PLACE OF DELIVERY-REPORTS The items to be furnished hereunder shall be delivered, with all charges paid by the Contractor, to:

Electronic copies to:

Contracting Officer's Representative (Refer to Section H.6 2052.215-71 CONTRACTING OFFICER REPRESENTATIVE AUTHORITY)

Contracting Officer, Monthly Letter Status Report (MLSR) and other reports as required F.2 TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013)

This order shall commence on 09/29/2020 and will expire on 09/30/2024.

F.3 2052.215-78 TRAVEL APPROVALS AND REIMBURSEMENT (OCT 1999) - ALTERNATE I (OCT 1999)

(a) Total expenditure for travel may not exceed without the prior approval of the contracting officer.

(b) All foreign travel must be approved in advance by the NRC on NRC Form 445, Request for Approval of Official Foreign Travel, and must be in compliance with FAR 52.247-63 Preference for U.S. Flag Air Carriers. The contractor shall submit NRC Form 445 to the NRC no later than 30 days prior to the commencement of travel.

(c) The contractor will be reimbursed only for travel costs incurred that are directly related to this contract and are allowable subject to the limitations prescribed in FAR 31.205-46.

(d) It is the responsibility of the contractor to notify the contracting officer in accordance with the FAR Limitations of Cost clause of this contract when, at any time, the contractor learns that travel expenses will cause the contractor to exceed the travel ceiling amount identified in paragraph (a) of this clause.

31310020D0003/31310020F0101 Page 21 (e) Reasonable travel costs for research and related activities performed at State and nonprofit institutions, in accordance with Section 12 of Pub. L. 100-679, must be charged in accordance with the contractor's institutional policy to the degree that the limitations of Office of Management and Budget (OMB) guidance are not exceeded. Applicable guidance documents include OMB Circular A-87, Cost Principles for State and Local Governments; OMB Circular A-122, Cost Principles for Nonprofit Organizations; and OMB Circular A-21, Cost Principles for Educational Institutions.

• To be incorporated into any resultant contract (End of Clause)

Section G - Contract Administration Data was added and reads as follows.

G - Contract Administration Data G.1 ELECTRONIC PAYMENTS (DEC 2017) - ALTERNATE 1 The Debt Collection Improvement Act of 1996 requires that all payments except IRS tax refunds be made by Electronic Funds Transfer. Payment shall be made in accordance with FAR 52.232-33, entitled Payment by Electronic Funds Transfer-System for Award Management.

To receive payment, the contractor shall prepare invoices in accordance with NRCs Billing Instructions. Claims shall be submitted on the payees letterhead, invoice, or on the Governments Standard Form 1034, Public Voucher for Purchases and Services Other than Personal, and Standard Form 1035, Public Voucher for Purchases Other than Personal -

Continuation Sheet. The preferred method of submitting invoices is electronically to:

NRC@fiscal.treasury.gov.

Section H - Special Contract Requirements was added and reads as follows.

H - Special Contract Requirements H.1 CONTRACTOR CONDUCT (APRIL 2020)

The contractor will ensure that all contractor staff receive anti-harassment training before being granted facility access. The Government reserves the right to deny or restrict facility access for any Contractor employee who engages in any conduct that the agency believes adversely affects the work place. The imposition of a restriction or prohibition shall not excuse the Contractor from performance of obligations under the contract.

H.2 SECURITY REQUIREMENTS RELATING TO THE PRODUCTION OF REPORTS OR THE PUBLICATION OF RESULTS UNDER CONTRACTS, AGREEMENTS, AND GRANTS (JUL 2016)

Review and Approval of Reports

31310020D0003/31310020F0101 Page 22 (a) Reporting Requirements. The contractor/grantee shall comply with the terms and conditions of the contract/grant regarding the contents of the draft and final report, summaries, data, and related documents, to include correcting, deleting, editing, revising, modifying, formatting, and supplementing any of the information contained therein, at no additional cost to the NRC.

Performance under the contract/grant will not be deemed accepted or completed until it complies with the NRCs directions, as applicable. The reports, summaries, data, and related documents will be considered draft until approved by the NRC. The contractor/grantee agrees that the direction, determinations, and decisions on approval or disapproval of reports, summaries, data, and related documents created under this contract/grant remain solely within the discretion of the NRC.

(b) Publication of Results. Prior to any dissemination, display, publication, or release of articles, reports, summaries, data, or related documents developed under the contract/grant, the contractor/grantee shall submit them to the NRC for review and approval. The contractor/

grantee shall not release, disseminate, display or publish articles, reports, summaries, data, and related documents, or the contents therein, that have not been reviewed and approved by the NRC for release, display, dissemination or publication. The contractor/grantee agrees to conspicuously place any disclaimers, markings or notices, directed by the NRC, on any articles, reports, summaries, data, and related documents that the contractor/grantee intends to release, display, disseminate or publish to other persons, the public, or any other entities. The contractor/grantee agrees, and grants, a royalty-free, nonexclusive, irrevocable worldwide license to the government, to use, reproduce, modify, distribute, prepare derivative works, release, display or disclose the articles, reports, summaries, data, and related documents developed under the contract/grant, for any governmental purpose and to have or authorize others to do so.

(c) Identification/Marking of Sensitive Unclassified Non-Safeguards Information (SUNSI) and Safeguards Information (SGI). The decision, determination, or direction by the NRC that information possessed, formulated or produced by the contractor/grantee constitutes SUNSI or SGI is solely within the authority and discretion of the NRC. In performing the contract/grant, the contractor/grantee shall clearly mark SUNSI and SGI, to include for example, OUO-Allegation Information or OUO-Security Related Information on any reports, documents, designs, data, materials, and written information, as directed by the NRC. In addition to marking the information as directed by the NRC, the contractor shall use the applicable NRC cover sheet (e.g., NRC Form 461 Safeguards Information) in maintaining these records and documents. The contractor/grantee shall ensure that SUNSI and SGI is handled, maintained and protected from unauthorized disclosure, consistent with NRC policies and directions. The contractor/grantee shall comply with the requirements to mark, maintain, and protect all information, including documents, summaries, reports, data, designs, and materials in accordance with the provisions of Section 147 of the Atomic Energy Act of 1954 as amended, its implementing regulations (10 CFR 73.21), Sensitive Unclassified Non-Safeguards and Safeguards Information policies, and NRC Management Directives and Handbooks 12.5, 12.6 and 12.7.

(d) Remedies. In addition to any civil, criminal, and contractual remedies available under the applicable laws and regulations, failure to comply with the above provisions, and/or NRC directions, may result in suspension, withholding, or offsetting of any payments invoiced or claimed by the contractor/grantee.

31310020D0003/31310020F0101 Page 23 (e) Flowdown. If the contractor/grantee intends to enter into any subcontracts or other agreements to perform this contract/grant, the contractor/grantee shall include all of the above provisions in any subcontracts or agreements.

H.3 WHISTLEBLOWER PROTECTION FOR NRC CONTRACTOR AND SUBCONTRACTOR EMPLOYEES (a) The U.S. Nuclear Regulatory Commission (NRC) contractor and its subcontractor are subject to the Whistleblower Employee Protection public law provisions as codified at 42 U.S.C.

5851. NRC contractor(s) and subcontractor(s) shall comply with the requirements of this Whistleblower Employee Protection law, and the implementing regulations of the NRC and the Department of Labor (DOL). See, for example, DOL Procedures on Handling Complaints at 29 C.F.R. Part 24 concerning the employer obligations, prohibited acts, DOL procedures and the requirement for prominent posting of notice of Employee Rights at Appendix A to Part 24 entitled: Your Rights Under the Energy Reorganization Act.

(b) Under this Whistleblower Employee Protection law, as implemented by regulations, NRC contractor and subcontractor employees are protected from discharge, reprisal, threats, intimidation, coercion, blacklisting or other employment discrimination practices with respect to compensation, terms, conditions or privileges of their employment because the contractor or subcontractor employee(s) has provided notice to the employer, refused to engage in unlawful practices, assisted in proceedings or testified on activities concerning alleged violations of the Atomic Energy Act of 1954 (as amended) and the Energy Reorganization Act of 1974 (as amended).

(c) The contractor shall insert this or the substance of this clause in any subcontracts involving work performed under this contract.

H.4 GREEN PURCHASING (SEP 2015 )

(a) In furtherance of the sustainable acquisition goals of Executive Order (EO) 13693, "Planning for Federal Sustainability in the Next Decade," products and services provided under this contract/order shall be energy efficient (EnergyStar or Federal Energy Management Program -

FEMP-designated products), water efficient, biobased, environmentally preferable (excluding EPEAT-registered products), non-ozone depleting, contain recycled content, or are non-or low toxic alternatives or hazardous constituents (e.g., non-VOC paint), where such products and services meet agency performance requirements. See: Executive Order (EO) 13693, "Planning for Federal Sustainability in the Next Decade."

(b) The NRC and contractor may negotiate during the contract term to permit the substitution or addition of designated recycled content products (i.e., Comprehensive Procurement Guidelines

- CPG), EPEAT-registered products, EnergyStar-and FEMP designated energy efficient products and appliances, USDA designated biobased products (Biopreferred program),

environmentally preferable products, WaterSense and other water efficient products, products containing non-or lower-ozone depleting substances (i.e., SNAP), and products containing non-or low-toxic or hazardous constituents (e.g., non-VOC paint), when such products and services are readily available at a competitive cost and satisfy the NRCs performance needs.

(c) The contractor shall flow down this clause into all subcontracts and other agreements that relate to performance of this contract/order.

31310020D0003/31310020F0101 Page 25 Address: U.S. Nuclear Regulatory Commission Office of Nuclear Regulatory Research Washington, DC 20555 Mail Stop: TWFN-10-A36 Phone: 301-415-2427 E-mail: Matthew.Homiack@nrc.gov (b) Performance of the work under this contract is subject to the technical direction of the NRC COR. The term "technical direction" is defined to include the following:

(1) Technical direction to the contractor which shifts work emphasis between areas of work or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work (SOW) or changes to specific travel identified in the SOW), fills in details, or otherwise serves to accomplish the contractual SOW.

(2) Provide advice and guidance to the contractor in the preparation of drawings, specifications, or technical portions of the work description.

(3) Review and, where required by the contract, approval of technical reports, drawings, specifications, and technical information to be delivered by the contractor to the Government under the contract.

(c) Technical direction must be within the general statement of work stated in the contract. The COR does not have the authority to and may not issue any technical direction which:

(1) Constitutes an assignment of work outside the general scope of the contract.

(2) Constitutes a change as defined in the "Changes" clause of this contract.

(3) In any way causes an increase or decrease in the total estimated contract cost, the fixed fee, if any, or the time required for contract performance.

(4) Changes any of the expressed terms, conditions, or specifications of the contract.

(5) Terminates the contract, settles any claim or dispute arising under the contract, or issues any unilateral directive whatever.

(d) All technical directions must be issued in writing by the COR or must be confirmed by the COR in writing within ten (10) working days after verbal issuance. A copy of the written direction must be furnished to the contracting officer. A copy of NRC Form 445, Request for Approval of Official Foreign Travel, which has received final approval from the NRC must be furnished to the contracting officer.

(e) The contractor shall proceed promptly with the performance of technical directions duly issued by the COR in the manner prescribed by this clause and within the COR's authority under the provisions of this clause.

31310020D0003/31310020F0101 Page 26 (f) If, in the opinion of the contractor, any instruction or direction issued by the COR is within one of the categories as defined in paragraph (c) of this section, the contractor may not proceed but shall notify the contracting officer in writing within five (5) working days after the receipt of any instruction or direction and shall request the contracting officer to modify the contract accordingly. Upon receiving the notification from the contractor, the contracting officer shall issue an appropriate contract modification or advise the contractor in writing that, in the contracting officer's opinion, the technical direction is within the scope of this article and does not constitute a change under the "Changes" clause.

(g) Any unauthorized commitment or direction issued by the COR may result in an unnecessary delay in the contractor's performance and may even result in the contractor expending funds for unallowable costs under the contract.

(h) A failure of the parties to agree upon the nature of the instruction or direction or upon the contract action to be taken with respect thereto is subject to 52.233 Disputes.

(i) In addition to providing technical direction as defined in paragraph (b) of the section, the COR shall:

(1) Monitor the contractor's technical progress, including surveillance and assessment of performance, and recommend to the contracting officer changes in requirements.

(2) Assist the contractor in the resolution of technical problems encountered during performance.

(3) Review all costs requested for reimbursement by the contractor and submit to the contracting officer recommendations for approval, disapproval, or suspension of payment for supplies and services required under this contract.

(4) Assist the contractor in obtaining the badges for the contractor personnel.

(5) Immediately notify the Security Branch, Division of Facilities and Security (SB/DFS) (via e-mail) when a contractor employee no longer requires access authorization and return of any NRC issued badge to SB/DFS within three days after their termination.

(6) Ensure that all contractor employees that require access to classified Restricted Data or National Security Information or matter, access to sensitive unclassified information (Safeguards, Official Use Only, and Proprietary information) access to sensitive IT systems or data, unescorted access to NRC controlled buildings/space, or unescorted access to protected and vital areas of nuclear power plants receive approval of SB/DFS prior to access in accordance with Management Directive and Handbook 12.3.

(7) For contracts for the design, development, maintenance or operation of Privacy Act Systems of Records, obtain from the contractor as part of closeout procedures, written certification that the contractor has returned to NRC, transferred to the successor contractor, or destroyed at the end of the contract in accordance with instructions provided by the NRC Systems Manager for Privacy

31310020D0003/31310020F0101 Page 27 Act Systems of Records, all records (electronic or paper) which were created, compiled, obtained or maintained under the contract.

(End of Clause)

Section I - Contract Clauses was added and reads as follows.

I - Contract Clauses I.1 52.217-8 OPTION TO EXTEND SERVICES. (NOV 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the Contractor within 15 days.

(End of clause)