ML20269A182

Modification No. 001 to Task Order No. 31310020F0103 Under Contract No. 31310020D0005

ML20269A182
Person / Time
Issue date:	09/25/2020
From:	Jeffrey Mitchell Acquisition Management Division
To:	Numark N Numark Associates
References
31310020D0005
Download: ML20269A182 (23)

Text

___________

(x) 31310020F0103 x 31310020D0005 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FA LURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

See Schedule WASHINGTON DC 200362444 788247377 NUMARK ASSOCIATES INC NRCHQ WASHINGTON DC 20555-0001 MAIL STOP TWFN-07B20M ACQUISITION MANAGEMENT DIVISION US NRC - HQ RES-20-0208 See Block 16C P00001 23 1

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNT NG AND APPROPRIATION DATA (If required) is not extended.

is extended tems 8 and 15, and returning Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods: (a) By completing The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS FAC LITY CODE CODE 10B. DATED (SEE ITEM 13) 10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11) 9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)

CODE

6. ISSUED BY PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.

3. EFFECTIVE DATE

2. AMENDMENT/MODIFICATION NO.

5. PROJECT NO. (If applicable)

1. CONTRACT D CODE AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 08/10/2020 ATTN NEIL NUMARK 1220 19TH ST NW SUITE 500 Net Increase:

$300,000.00 CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIF ED TO REFLECT THE ADM NISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation date, etc.) SET FORTH N ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT Contractor is not, is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

Bilateral; Acceptance of Task Order 31310020F0103 x

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

X 1

The purpose of this modification is utilize the minimum guarantee and award the first task order to Numark Associates.

The NRC hereby awards task order 31310020D0005 / 31310020F0103 entitled FAVOR, REAP, and RPV Analysis.

Total Obligated Amount: $310,000.00 Total Contract Ceiling: $1,413,657.02 Period of Performance: 09/28/2020 to 01/31/2024 16A. NAME AND TITLE OF CONTRACT NG OFFICER (Type or print) 15A. NAME AND TITLE OF SIGNER (Type or print) 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED (Signature of person authorized to sign)

(Signature of Contracting Officer)

JEFFREY R. MITCHELL STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243 NSN 7540-01-152-8070 Previous edition unusable Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect.

09/25/2020 TEL:

EMAIL:

301-415-5074 Jeffrey.Mitchell@nrc.gov

31310020D0005/31310020F0103 Page 2 B - Supplies or Services/Prices B.1 BRIEF PROJECT TITLE AND WORK DESCRIPTION (a) The title of this project is: FAVOR, REAP, and RPV Analysis (b) Summary work description: The objective of this task order is to provide technical support to NRC staff with the following:

• The enhancement of the SQA and V&V for the FAVOR code.

• The development of SQA and V&V documentation for the FAVOR code.

• Maintenance, user support, data entry, and development of the REAP database.

• Creation and management of the FAVOR User Group.

B.2 CONSIDERATION AND OBLIGATIONCOST-PLUS-FIXED-FEE ALTERNATE I (a) The total estimated cost to the Government for full performance of this contract is of which the sum of represents the estimated reimbursable costs, and of which $

represents the fixed-fee.

(b) There shall be no adjustment in the amount of the Contractor's fixed fee.

(c) The amount currently obligated by the Government with respect to this contract is

, of which the sum of represents the estimated reimbursable costs, and of which $

represents the fixed-fee.

(d) It is estimated that the amount currently obligated will cover performance through 03/01/2021.

(e) This is an incrementally-funded contract and FAR 52.232 Limitation of Funds applies.

(f) In accordance with FAR 52.216 Fixed Fee, it is the policy of the NRC to withhold payment of fee after payment of 85 percent of the fee has been paid in order to protect the Governments interest. The amount of fixed-fee withheld from the contractor will not exceed 15 percent of the total fee or $100,000, whichever is less. Accordingly, the maximum amount of fixed-fee that may be held in reserve is $

B.4 PRICE/COST SCHEDULE Base Task Order CLIN DESCRIPTION OF SERVICE/SUPPLY ESTIMATED COST 0001 Labor 0002 Subcontractor Costs 0003 Travel 0004 ODC SUBTOTAL 0005 Indirect Cost Pool (includes G&A, Fringe, Overhead and Subcontractor Handling)

SUBTOTAL

31310020D0005/31310020F0103 Page 3 0006 Fixed Fee TOTAL

$1,413,657.02 Optional Task 1.6 CLIN DESCRIPTION OF SERVICE/SUPPLY ESTIMATED COST 1001 Labor 1002 Subcontractor Costs 1003 Travel 1004 ODC SUBTOTAL 1005 Indirect Cost Pool (includes G&A, Fringe, Overhead and Subcontractor Handling)

SUBTOTAL 1006 Fixed Fee TOTAL

$55,162.07 Optional Task 6 CLIN DESCRIPTION OF SERVICE/SUPPLY ESTIMATED COST 2001 Labor 2002 Subcontractor Costs 2003 Travel 2004 ODC SUBTOTAL 2005 Indirect Cost Pool (includes G&A, Fringe, Overhead and Subcontractor Handling)

SUBTOTAL 2006 Fixed Fee TOTAL

$56,612.34 TOTAL ORDER COST (Inclusive of options)

TOTAL ORDER FIXED FEE TOTAL ORDER CEILING (Inclusive of options)

$1,525,431.43

31310020D0005/31310020F0103 Page 4 C - Description/Specifications C.1 STATEMENT OF WORK PROJECT TITLE FAVOR, REAP, and RPV Analysis BACKGROUND The operational integrity of nuclear reactor pressure vessel (RPV) and piping systems relies on sound knowledge of nuclear power plants and their applied loadings, their materials of construction, and of how these materials degrade over time (e.g., changes to properties, development of cracks, changes of dimension, etc.). Over the preceding decades the U.S. Nuclear Regulatory Commission (NRC), its contractors, and the national and international nuclear community in general have done considerable work on these topics.

As the pressure-retaining systems (i.e., piping, vessels) of nuclear power plants age, there is a continued need to evaluate these systems for the continued operating safety of these systems. Realistic assessment of operating safety requires the development of advanced probabilistic assessment tools and the gathering of empirical evidence of the processes underlying the age related material damage.

Since the mid-1990s, the NRC contracted with Oak Ridge National Laboratory (ORNL) to develop the FORTRAN-based computer code FAVOR (Fracture Analysis of Vessels, Oak Ridge). ORNL developed the FAVOR code pursuant to NUREG/BR-0167 ("Software Quality Assurance Program and Guidelines). The software quality assurance (SQA) guidance in NUREG/BR-0167 applies to technical applications software used in a safety decision by the NRC. FAVOR enables users to estimate the frequency with which a crack can be expected to propagate through the wall of an RPV as a result of thermal-hydraulic loading events. Since 1999, this code has been a key component of the NRCs assessment methodology.

FAVOR Since the mid-1990s, the NRC contracted with Oak Ridge National Laboratory (ORNL) to develop the FORTRAN-based computer code FAVOR (Fracture Analysis of Vessels, Oak Ridge). ORNL developed the FAVOR code pursuant to NUREG/BR-0167 ("Software Quality Assurance Program and Guidelines). The software quality assurance (SQA) guidance in NUREG/BR-0167 applies to technical applications software used in a safety decision by the NRC. FAVOR enables users to estimate the frequency with which a crack can be expected to propagate through the wall of an RPV as a result of thermal-hydraulic loading events. Since 1999, this code has been a key component of the NRCs assessment methodology.

Due to its development spanning 3 decades, FAVOR is a legacy code written with many obsolete programing features (by todays standards). FAVOR is written in fixed-format Fortran 77, with some constructs from Fortran 90/95. This legacy source code is prone to causing software errors as changes are made, and the source code needs major modernization.

A recent effort to assess the software quality assurance (SQA) and verification and validation (V&V) pedigree and practices for the FAVOR code has led to the development of a new Software Quality Assurance Plan (SQAP) for FAVOR, and the NRC is also in the process of establishing new software development QA and V&V practices, with an increased focus on automation and collaborative development. The NRC needs assistance in further developing, documenting, and implementing SQA and V&V processes for FAVOR. In addition, NRC needs assistance in preforming independent SQA and V&V activities, developing FAVOR Test cases, and managing a FAVOR users group.

It is envisioned that for the duration of this task order, a FAVOR development team will be collaboratively working to modernize the FAVOR code. This team will consist of the contractor, the NRC COR, potentially other NRC staff, and

31310020D0005/31310020F0103 Page 5 another contractor that specializes in Fortran code development.

REAP Both the NRC and the nuclear power industry have, over the years, generated significant amounts of data that characterize the properties of materials used in power plant construction, as well as the effect of the power plant environment on these properties. This data was generally found in individual reports or letters and had not been catalogued and archived in a sustainable way, nor had the ample data from these documents been stored in a matter that enables their efficient retrieval and use. Therefore, under a previous contract, ORNL developed a material database and archive for the NRC called REAP (Radiation Embrittlement Archive Project). REAP consists of two major parts: (1) a document archive, and (2) a relational database. REAP is currently focused on data that quantify the effects of irradiation embrittlement on RPV steels. The REAP users consist of domestic and international members of the nuclear industry (utilities, vendors, and other industry research entities), as well as international regulatory and government technical support organizations (national laboratories and public research institutes). REAP is in need of regular updating and maintenance to remain a useful tool for NRC and other outside users.

RPV Analysis In past NRC-sponsored efforts, modelling work demonstrated that a shallow surface breaking flaw having a depth just slightly more than the thickness of the austenitic stainless steel cladding on the RPV ID exhibit an unexpectedly large impact on the structural integrity of the RPV. This past work identified the added driving force for fracture generated by the mismatch in the coefficient of thermal expansion between the austenitic stainless steel cladding and the ferritic steel base metal as the primary cause of this effect.

OBJECTIVE(S)

The objective of this task order is to provide technical support to NRC staff with the following:

The enhancement of the SQA and V&V for the FAVOR code.

The development of SQA and V&V documentation for the FAVOR code.

Maintenance, user support, data entry, and development of the REAP database.

Creation and management of the FAVOR User Group.

STATEMENT OF WORK TASKS Task 1: FAVOR Software Quality Assurance and Verification and Validation Subtask 1.1: Configuration Management and Maintenance Plan (CMMP)

The contractor shall develop a Configuration Management and Maintenance Plan (CMMP) for the FAVOR code maintenance and development. The CMMP shall adopt the intent of modern best practices for SQA and V&V, as described in contemporary software SQA and V&V standards such as ASME V&V10 or the IEEE standards.

Subtask 1.1 Deliverables

Draft CMMP for the FAVOR code

Final CMMP that incorporates NRC comments on the draft CMMP (note that two or three iterations on the CMMP might be needed to converge on a final document)

Subtask 1.2: Software Requirements and Design Documents The contractor shall develop Software Requirement Documents and Software Design Documents for the various parts of the FAVOR code. Specifically, as the FAVOR source code is modernized by the FAVOR development team, the contractor shall create SRDs and SDDs for the parts of the code that have undergone modernization. The contractor shall write the SRDs and SDDs to reflect the modernized FAVOR code. The contractor shall be responsible for creating and tracking the STPs and STRRs, and shall either write the SRDs and SDDs in their entirety, or request and integrate content from other members of the FAVOR development team, or a combination of both, as needed and as directed in writing by the COR.

Each major partition of the FAVOR code (either subroutine, module, or group of subroutines performing a major function of the code) shall have its own SRD and SDD. Since the FAVOR code will undergo a major modernization during the course of this task order, the contractor shall develop SRDs and SDDs little by little, as each major partition of the code is

31310020D0005/31310020F0103 Page 6 modernized. The SRDs and SDDs shall reflect the new modernized FAVOR code.

Subtask 1.2 Deliverables For each major partition of the FAVOR code:

Draft SRD

Final SRD that incorporates NRC comments on the draft SRD (note that two or three iterations on the SRD might be needed to converge on a final document)

Draft SDD

Final SDD that incorporates NRC comments on the draft SDD (note that two or three iterations on the SDD might be needed to converge on a final document)

Subtask 1.3: Software Test Plans and Software Test Results Reports The contractor shall develop Software Test Plans (STPs) and Software Test Result Reports (STRRs). Specifically, as the FAVOR source code is modernized by the FAVOR development team, the contractor shall create STPs for the parts of the code that have undergone modernization. The STPs shall describe the testing to be performed, to include unit testing and integration testing for the verification of FAVOR. Once the tests have been performed, the contractor shall then create STRRs that describe the test results. The contractor shall be responsible for creating and tracking the STPs and STRRs, and shall either write the STPs and STRRs in their entirety, or request and integrate content from other members of the FAVOR development team, or a combination of both, as needed and as directed in writing by the COR.

Subtask 1.3 Deliverables For each part of the FAVOR code that has been modernized:

Draft STP

Final STP that incorporates NRC comments on the draft STP (note that two or three iterations on the STP might be needed to converge on a final document)

Draft STRR

Final STRR that incorporates NRC comments on the draft STRR (note that two or three iterations on the STRR might be needed to converge on a final document)

Subtask 1.4: Execution of FAVOR Software Tests The contractor shall follow the STPs and execute new verification tests to show that the numerical solutions from the newly implemented code are producing correct results. The contractor shall also execute the tests for the existing version 16.1 of FAVOR to have a basis for comparison.

Subtask 1.4 Deliverables

Input files and other supporting files for software tests, for both FAVOR v16.1 and the new version of FAVOR.

Results files for software tests, for both FAVOR v16.1 and the new version of FAVOR.

Subtask 1.5: Software V&V Plan and Software V&V Report The contractor shall develop a Software Verification and Validation Plan (SVVP) and a corresponding Software Verification and Validation Report (SVVR). These reports shall summarize plans for verification and validation of FAVOR and the results of FAVOR verification and validation, respectively. These reports shall NOT provide all the details described in the STPs and STRRs, but instead provide a high level description of the FAVOR V&V. The contractor shall be responsible for creating and tracking the SVVP and SVVR, and shall either write the SVVP and SVVR in their entirety, or request and integrate content from other members of the FAVOR development team, or a combination of both, as needed and as directed in writing by the COR.

Subtask 1.5 Deliverables

Draft SVVP

Final SVVP that incorporates NRC comments on the draft SVVP (note that two or three iterations on the SVVP might be needed to converge on a final document)

Draft SVVR

Final SVVR that incorporates NRC comments on the draft SVVR (note that two or three iterations on the SVVR might be needed to converge on a final document)

OPTIONAL Task - Subtask 1.6: Support of Independent V&V (IV&V) Effort Should the NRC decide to perform additional independent V&V of FAVOR, the NRC staff will constitute the FAVOR Independent V&V Group, whose membership will be defined if and when needed. This group will develop an Independent V&V plan, and subsequently execute this plan.

31310020D0005/31310020F0103 Page 7 The contractor shall review the IV&V plan produced by the FAVOR IV&V Group for completeness and accuracy and provide comments to the COR.

The contractor shall be available to respond to any inquiries from the FAVOR IV&V Group related to the performance of the IV&V effort.

OPTION Task - Subtask 1.6 Deliverables

1) Comments on the IV&V plan, with tracked changes and comments in MSWord

2) Written answers to written inquiries generated by the FAVOR IV&V Group, relating to the IV&V effort, that are transmitted to the contractor by the COR Task 2: FAVOR User Group Subtask 2.1: FAVOR User Group Management The contractor shall assist the NRC COR in managing the FAVOR User Group. Activities shall include preparing and distributing quarterly newsletters to the User Group, keeping a registry of members, and adding and removing members per the NRC CORs direction.

Subtask 2.1 Deliverables

Up-to-date list of FAVOR User Group members

Quarterly newsletter to User Group members informing them of latest FAVOR related news.

Subtask 2.2: FAVOR User Group Meetings The contractor shall assist the NRC COR in organizing annual FAVOR User Group meetings. The FAVOR User Group meetings shall last 1 or 2 days. Circumstances permitting, the User Group meeting may take place either at the NRC HQ, or virtually, or at a convenient location where a relevant conference is already taking place (for example a meeting of the International Group for Radiation Damage Mechanisms - IGRDM, or ASME Code meeting, or ASM PVP, for example).

This includes communications and announcements for the FAVOR User Group Meeting, the collection of Users papers or presentations ahead of the meeting, and keeping minutes of the meetings.

Subtask 2.2 Deliverables

Announcements for the FAVOR User Group meetings

Registry of attendees to the FAVOR User Group meetings

Compilation of papers of presentations from Users at the FAVOR User Group meeting

Meeting minutes Task 3: Technical Support to Radiation Embrittlement Archive Project (REAP)

Subtask 3.1: REAP Migration The contractor shall assist with the migration of the REAP database and website to the NRCs Azure cloud based web servers. Specifically, the contractor shall provide the NRC with all the files required to host the REAP database, web application, and website on NRCs Azure cloud. The contractor shall deploy the REAP application in the NRCs Azure cloud and maintain it such that it remains functional, accessible to NRC staff and the public, and remains in compliance with the REAP Authorization to Operate (ATO) conditions.

Subtask 3.1 Deliverables

All digital files associated with the REAP database, web application, and website.

REAP application deployed on the NRCs Azure cloud.

REAP application that complies with the REAP ATO conditions.

Subtask 3.2: REAP User Support The contractor shall host the REAP database on a publicly accessible website, shall process new user requests, shall service the needs of existing users having problems with their accounts, and shall correct any data errors identified by users. At the beginning of the project the COR will provide a list of already approved users to the contractor. The contractor shall consult with the COR prior to approving any user request, and prior to resolving any significant issues (significant means taking more than 1 workday to resolve). For cost estimation purposes the contractor should assume that these activities should be limited to one full working day per month.

The contractor shall also have a version of REAP that is accessible only to NRC staff, for access to the non-public data in

31310020D0005/31310020F0103 Page 8 REAP, is applicable.

The website shall be linked to the NRC infrastructure and kept in good standings with regards to NRC requirements to maintain NRCs Authority to Operate (ATO) for REAP.

Subtask 3.2 Deliverables

Functional REAP application served to the public and internally to NRC staff, with NRC ATO conditions met.

In the Monthly Letter Status Report (MLSR) for this task order, the contractor shall include: (1) a complete list of users (names, organizations, e-mail addresses); (2) a summary of REAP users identifying the number of users by country, number of sessions and minutes per session; (3) identifying any new users added in the reporting month; and (4) a description of any significant issues identified, and their resolution.

Subtask 3.3: REAP Data Review, Correction and Expansion The contractor shall formalize a process for data entry into the REAP database, including Quality Assurance checks to ensure the accuracy of the data.

The contractor shall perform a high-level review of the data in REAP for consistency both with the source documents and with ASTM definitions of terms and data field definitions. Where any inconsistencies or errors are identified, the contractor shall provide documentation of proposed data changes to correct the data to the COR. After approval of changes by the COR, the contractor shall correct any identified inconsistencies or errors in REAP data.

From time-to-time the operators of power reactors in the United States produce additional surveillance data. The contractor shall scan these reports, which will be provided to the contractor by the COR, for the document archive, and shall enter data from the reports into the relational database. For cost estimation purposes the contractor should assume that an initial data entry from six reports will be needed. After this data entry a rate of two new reports per year shall be assumed.

Subtask 3.3 Deliverables

White paper documenting the process to enter data in to the REAP database.

In the MLSR for this task order, the contactor shall include a summary of corrections to REAP data and any new reports received that month and documentation of their entry into REAP. The documentation shall demonstrate the data entry and how the data was stored, and shall include evidence of cross-checking the new data with previous reports from the same plant to ensure consistency with data already collected.

Subtask 3.4: REAP Development The contractor shall upgrade the data storage, retrieval, and analysis capabilities of REAP by regularly updating the source code of the REAP application, per the written direction of the NRC COR. This task shall include linking the REAP data and reports to ADAMS records whenever possible.

Subtask 3.4 Deliverables

Upgraded REAP web-application Subtask 3.5: REAP ATO Maintenance The contractor shall perform routine maintenance of REAP to ensure that the conditions in the REAP ATO continue to be met. The REAP ATO shall be shared with the contractor by the NRC COR at the start of this task order.

Subtask 3.5 Deliverables

REAP application that is fully compliant with the conditions in the NRC ATO.

Task 4: FAVOR Development Subtask 4.1: Technical Support for FAVOR Modernization The contractor shall assist the NRC COR and the FAVOR development team in the effort to modernize the FAVOR code.

This includes providing expertise on the historical FAVOR code, its structure and overall architecture, as well as expertise on the physics and technical bases for the code. The contractor shall provide this expertise by providing written responses to written inquiries from the FAVOR development team, by being an integral part of development team, by helping write source code as needed and directed by the COR, and by sharing knowledge with other developers via meetings and discussions.

Subtask 4.1 Deliverables

Written responses to written inquiries from the FAVOR development team

31310020D0005/31310020F0103 Page 9

Modernized FAVOR source code (when directed in writing by the COR)

Meetings and discussion to share knowledge with the FAVOR development team, as needed.

Subtask 4.2: Technical Support for FAVOR Development The contractor shall assist the NRC COR and the FAVOR development team in the effort to further the development of the FAVOR code, if applicable. This includes providing expertise on the detailed structure and inner workings of the FAVOR code, as well as expertise on the physics and technical bases for the code. The contractor shall provide this expertise by providing written responses to written inquiries from the FAVOR development team, by being an integral part of development team, by helping write source code as needed and directed by the COR, and by sharing knowledge with other developers via meetings and discussions.

Subtask 4.2 Deliverables

Written responses to written inquiries from the FAVOR development team

FAVOR source code developments (when directed in writing by the COR)

Meetings and discussion to share knowledge with the FAVOR development team, as needed.

Task 5: Related Technical Support Subtask 5.1: Kickoff Meeting and Annual Program Review Meetings Shortly after award, the contractor shall participate in a kickoff meeting either at the NRC Headquarters in Rockville Maryland (Circumstances permitting), or virtually. Each year of the contract, the contractor shall participate in an annual program review meeting with the COR and other NRC technical staff to discuss work performed during the year. The meetings are expected to be held at NRC Headquarters, in Rockville Maryland, or virtually, dependent on the circumstances.

Subtask 5.1 Deliverables The contractor shall prepare viewgraphs and other support materials, e.g. handouts, for the kickoff meeting and for each annual program review. In the viewgraphs for the kickoff meeting, the contractor shall go over the scope of the work for all awarded tasks, and provide any insights and suggestions to ensure a successful project. In the viewgraphs for the annual program reviews, the contactor shall summarize the work performed to date under this task order, highlight important test results, provide a snapshot of the projects financial status, highlight any potential problem areas and propose potential solutions, and outline the work to be performed during the following contract year.

Subtask 5.2: Shallow Flaw Survey of US Nuclear Reactor Fleet The contractor shall survey the US reactor fleet for actual practices and limitation on reactor heatup and cooldown, as well as leak tests (for BWRs). Specifically the contractor shall search in the public ADAMS for Pressure-Temperature Limits Reports and other relevant licensing documents hat describe actual operational limits for the transients listed above. The results of the survey shall be compared for the recommendations from previous NRC and EPRI work on the shallow flaw issue resolution. The NRC COR shall provide all necessary documentation at the start of the task order.

The contractor shall prepare a draft of the report, submit it to the NRC Cor for review, and incorporate the NRC CORs comments into a final report.

Subtask 5.2 Deliverables

Draft technical letter report documenting the references surveyed for the US fleet, the relevant information from the survey, its comparison with recommendations from past NRC and EPRI work on the shallow flaw, and an assessment of whether the shallow flaw may still represent a safety issue for the US reactor fleet.

Final technical report of US fleet survey that incorporates the NRC CORs comments.

Subtask 5.3: Peer-Reviewed Technical Paper For each year of this task order, the contractor shall prepare a technical paper to be presented at a peer reviewed conference, technical meeting, or to be published in a technical journal. In this technical paper, the contractor shall describe one or more important aspects of the research performed during the year related to this research project. The contractor shall obtain COR written approval of the topics to be addressed in the technical paper prior to starting work on preparing the technical paper. If directed by the COR, the contractor shall present the paper.

Subtask 5.3 Deliverables

Draft technical paper

Final technical paper that incorporates COR comments received on the draft technical paper.

31310020D0005/31310020F0103 Page 10 OPTIONAL Task - Task 6: Related Technical and Regulatory Analysis Support The contractor shall perform technical and regulatory analysis on emerging issues related to RPV integrity in support of NRC licensing regulatory reviews. The contractor shall also provide technical expertise to address emerging issues associated with probabilistic modeling. The contractor shall provide support on an as-needed basis upon the written direction of the COR. Specifically, the contractor shall perform, as needed, probabilistic fracture mechanics analyses, finite element analyses, peer review of technical work, P-T limits calculations, code development and maintenance, and data retrieval and analysis. Such analyses shall be in support of RPV integrity licensing regulatory reviews.

OPTION - Task 6 Deliverables For each technical or regulatory analysis support request, the contractor shall prepare and submit a short (e.g.

anticipated to be no more than 10 pages) draft TLR that includes analysis results and/or other information as requested by the COR commensurate with the issue being addressed and the needs of the COR. The contractor shall prepare a final TLR incorporating any comments from the COR on the draft TLR.

APPLICABLE DOCUMENTS AND STANDARDS None.

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 contractor specifically agree on another format, such as PDF for example. 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 deliverables below shall be submitted to the task order COR. 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 (as necessary), maintain, and control data, files, information, and deliverables pursuant to this task order.

Subtask Deliverable Estimated Due Date 1.1 Draft CMMP for FAVOR 6 months from award 1.1 Final CMMP for FAVOR 1 month after receiving final comments from NRC COR 1.2 Draft SRD for each major partition of FAVOR 18 months from award 1.2 Final SRD for each major partition of FAVOR 1 month after receiving final comments from NRC COR 1.2 Draft SDD for each major partition of FAVOR 24 months from award 1.2 Final SDD for each major partition of FAVOR 1 month after receiving final comments from NRC COR 1.3 Draft STP for each part of FAVOR that has been modernized 1 month after modernization effort 1.3 Final STP for each part of FAVOR that has been modernized 1 month after receiving

31310020D0005/31310020F0103 Page 11 Subtask Deliverable Estimated Due Date final comments from NRC COR 1.3 Draft STRR for each part of FAVOR that has been modernized 1 month after software testing has been completed 1.3 Final STRR for each part of FAVOR that has been modernized 1 month after receiving final comments from NRC COR 1.4 Input and supporting files for software tests 1 month after software testing has been completed 1.4 Results files for software tests 1 month after software testing has been completed 1.5 Draft SVVP for FAVOR 18 months from award 1.5 Final SVVP for FAVOR 1 month after receiving final comments from NRC COR 1.5 Draft SVVR for FAVOR 30 months from award 1.5 Final SVVR for FAVOR 1 month after receiving final comments from NRC COR 1.6 (OPTION)

Review of the IV&V plan, with tracked changes and comments in MSWord TBD 1.6 (OPTION)

Written answers to written inquiries generated by the FAVOR IV&V Group, relating to the IV&V effort TBD 2.1 Up-to-date list of FAVOR Users Group in MLSR Monthly in MLSR 2.1 Quarterly newsletter to FAVOR User Group members Once User Group is established, quarterly for remainder of TO period 2.2 Announcements of FAVOR User Group meetings Annually, 6 months before meeting 2.2 Registry of attendees to the FAVOR User Group meetings Annually, 1 week prior to meeting 2.2 Compilation of papers and presentations from Users at the FAVOR User Group meeting 2 weeks after each meeting 2.2 FAVOR User group meeting minutes 2 weeks after each meeting 3.1 All digital files associated with the REAP database, web application, and website 6 months from award 3.1 REAP application deployed on the NRCs Azure cloud 6 months from award 3.1 REAP application that complies with the REAP ATO conditions 6 months from award 3.2 Functional REAP application served to the public and internally to NRC staff, with NRC ATO conditions met Continuous throughout TO 3.2 In the MLSR: reporting on REAP users and usage statistics Monthly in MLSR 3.3 White paper on REAP data entry process 3 months from award 3.3 In the MLSR: reporting on REAP corrections, new data entries, and data consistency checks Monthly in MLSR 3.4 Upgraded REAP application, fully deployed in NRCs Azure and fully compliant with ATO Continuous throughout TO 3.5 REAP application that is fully compliant with the conditions in the NRC ATO Continuous throughout TO 4.1 Written responses to written inquiries from the FAVOR development team 1 week from initial inquiry transmittal by NRC COR 4.1 Modernized FAVOR source code TBD for each request from NRC COR 4.1 Meetings and discussion with the FAVOR development team Continuous throughout TO 4.2 Written responses to written inquiries from the FAVOR development team 1 week from initial inquiry transmittal by NRC COR

31310020D0005/31310020F0103 Page 12 Subtask Deliverable Estimated Due Date 4.2 Modernized FAVOR source code TBD for each request from NRC COR 4.2 Meetings and discussion with the FAVOR development team Continuous throughout TO 5.1 Meeting slides 1 week before meeting 5.2 Draft technical letter report on US fleet survey for shallow flaw issue 6 months from award 5.2 Final technical letter report on US fleet survey for shallow flaw issue 1 month after receiving final comments from NRC COR 5.3 Draft technical paper for peer reviewed journal or conference Annually, 2 months before journal /

conference deadline 5.3 Final technical paper for peer reviewed journal or conference 1 month after receiving final comments from NRC COR 6 (OPTION)

Draft TLR that includes analysis results and/or other information as requested by the COR commensurate with the issue being addressed and the needs of the COR TBD 6 (OPTION)

Final TLR 1 month after receiving final comments from NRC COR The contractor shall submit all raw and processed data and worksheet and/or input files used in testing and analyses with the corresponding Draft TLR, and with the Final TLR, in a tabulated Excel format or other format as directed by the COR.

LABOR QUALIFICATIONS Labor Type Qualification Requirements Key Personnel*

(yes or no)

Project Manager (PM)

Minimum Qualifications Requirement

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

2) Minimum 5 years of regulatory research project management and oversight experience Yes

31310020D0005/31310020F0103 Page 13 Labor Type Qualification Requirements Key Personnel*

(yes or no)

Senior Key Staff Minimum Qualifications Requirement

1) M.S. in Engineering, Science or similar technical field and

2) Individual Technical Staff, or team of Technical Staff as a whole performing work described herein must have a combined minimum 15 years knowledge and specialized experience in the following key technical areas:

Probabilistic fracture mechanics computer code development

Uncertainty characterization methodologies and sensitivity studies

Reactor pressure vessel fracture issues in light-water nuclear power plants

NRC regulation and guidance pertaining to reactor pressure vessel integrity

Use of the FAVOR code for regulatory purposes

Development of the FAVOR code

Experience in performing software quality assurance activities, including verification and validation Education and Skillsets that are not Required, but Desired for this Task Order Requirement:

In-depth technical experience and/or knowledge in the following areas:

Knowledge of, and practical experience in, NRC standards for software quality assurance Yes GOVERNMENT-FURNISHED PROPERTY Access to all deliverables from previous NRC research and development on the FAVOR code, as needed for this project per the CORs determination, including all past test data, analyses, and letter reports.

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.

SPECIAL CONSIDERATIONS 11.1 TRAVEL/MEETINGS The following travel may occur under this task order:

Travel Description Task Location Date Days Attendees FY 2021 Kickoff meeting at NRC 5

Rockville, MD Q4 CY2020 2

3 FAVOR User Group Meeting 2

TBD TBD 4

3

31310020D0005/31310020F0103 Page 14 FY 2022 Program Review at NRC 2

Rockville, MD Q4 CY2021 2

3 FAVOR User Group Meeting 5

TBD TBD 4

3 FY 2023 Program Review at NRC 2

Rockville, MD Q4 CY2022 2

3 FAVOR User Group Meeting 5

TBD TBD 4

3 FY2024 Program Review at NRC 2

Rockville, MD Q4 CY2023 2

3 FAVOR User Group Meeting 5

TBD TBD 4

3 Travel Notes a.

All contractor travel requires prior written approval from the COR.

b.

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

c.

At the discretion of the COR, meetings may be conducted via telephone, video conference, or at the contractor site.

d.

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

11.2 SECURITY The work will be UNCLASSIFIED.

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 LICENSE FEE RECOVERY All work under this task order is/is not license fee recoverable.

11.4 DATA RIGHTS The NRC shall have unlimited rights to and ownership of all deliverables provided under this contract/order, including reports, recommendations, briefings, work plans and all other deliverables. All documents and materials, to include the source codes of any software, produced under this contract/order are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written authorization from the CO. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights. The definition of unlimited rights is contained in Federal Acquisition Regulation (FAR) 27.401, Definitions. FAR clause at FAR 52.227-14, Rights in Data-General, is hereby incorporated by reference and made a part of this contract/order.

31310020D0005/31310020F0103 Page 15 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:

31310020D0005_31310020F0103.

D.2 BRANDING 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 Nuclear Regulatory Research, under Contract/order number 31310020D0005_31310020F0103.

31310020D0005/31310020F0103 Page 16 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:

Name:

a.

b. Contracting Officers Representative (COR)

c. Name: Jeffrey.Mitchell@nrc.gov

d. Contracting Officer (CO)

F.2 TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013)

This order shall commence on 09/28/2020 and will expire on 01/31/2024.

31310020D0005/31310020F0103 Page 17 G - Contract Administration Data G.1 ELECTRONIC PAYMENT (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.

31310020D0005/31310020F0103 Page 18 H - Special Contract Requirements H.1 USE OF PERMANENT AND LOANER DEVICE SOLUTIONS DURING INTERNATIONAL TRAVEL (FEB 2020)

In order to ensure the secure use of mobile devices by contractors while on official international travel, the NRC has implemented the following requirements. These policies establish best practices in accordance with Management Directive 12.5, "NRC Cybersecurity Program.

NRC-assigned Permanent Laptops Due to security risks, NRC-assigned permanent laptops shall not be used for international travel by contractors for any reason.

NRC-assigned Loaner Laptops NRC loaner laptops specifically configured for international travel, if provided, are the only NRC-provided mobile equipment that may be used by contractors while on official agency international travel. Under the NRC's Agency-Wide Mobility Policy, loaner tablets and mobile phones are not provided to contractors. All NRC loaner devices will be wiped of all data upon returning from each international trip.

Personal Devices The use of personal laptops, tablets and mobile phones while on official international travel is not prohibited. However, if a contractor is using a personal device to perform work for the NRC while on international travel, the contractor must leverage an NRC authorized solution (Citrix Remote Desktop, IBM MaaS360, Microsoft Office 365 (O365)) to access NRC information.

Personal International Travel The NRC does not support requests for loaner laptops, tablets or mobile phones while contractor employees are on personal international travel.

H.2 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.

31310020D0005/31310020F0103 Page 19 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.

H.5 KEY PERSONNEL. (JAN 1993)

(a) The following individuals are considered to be essential to the successful performance of the work hereunder:

31310020D0005/31310020F0103 Page 21 specifications, or technical portions of the work description.

(3) Review and, where required by the contract, approve 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 project officer 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 project officer in the manner prescribed by this clause and within the CORs authority under the provisions of this clause.

(f) If, in the opinion of the contractor, any instruction or direction issued by the COR is within one of the categories 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 that 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 to the instruction or direction is subject to 52.233 Disputes.

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

(1) Monitor the contractor's technical progress, including surveillance and assessment of

31310020D0005/31310020F0103 Page 22 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.

(End of Clause)

31310020D0005/31310020F0103 Page 23 SECTION J - List of Documents, Exhibits and Other Attachments J.1 List of Documents, Exhibits, and Other Attachments Attachments:

1.

Monthly Letter Status Report Template (Furnished Upon Request) 2.

Cost Reimbursement Billing Instructions (Furnished Upon Request)