31310019R0005_Attachment_No._1_Task_Order_No._1_Statement_of_Work.pdf

31310019R0008

ATTACHMENT NO. 1

TASK ORDER NO. 1

STATEMENT OF WORK

TITLE: Thermal Hydraulic Code Development and User Support

BACKGROUND

The Division of Safety Analysis (DSA), Office of Nuclear Regulatory Research (RES) has responsibility for the development, testing, assessment, maintenance, and user support of the NRC's thermal-hydraulic (T/H) computer codes. These codes include

• TRACE (TRAC/RELAP Advanced Computational Engine) is NRC's flagship thermal-hydraulics analysis tool. It is a modernized thermal-hydraulics code designed to consolidate the capabilities of NRC's 4 legacy safety codes - TRAC-P, TRAC-B, RELAP, and RAMONA. It is able to analyze large/small break LOCAs and system transients in PWRs, BWRs, SMRs, and non-LWR advanced reactor designs. The capability also exists to model thermal hydraulic phenomena in both 1-D and 3-D space. It also includes the ability to model 3-D kinetics through integration with the Purdue Advanced Reactor Core Simulator (PARCS) code. The combined integrated product of these two tools is called TRACE/PARCS throughout the remained of this contract.

• PARCS (Purdue Advanced Reactor Core Simulator) is a computer code that solves the time-dependent two-group neutron diffusion equation in three-dimensional Cartesian geometry using nodal methods to obtain the steady-state and transient neutron flux distribution. The code may be used in the analysis of reactivity-initiated accidents in light-water reactors where spatial effects may be important. It exists both as a stand-alone program and as a separate computational module coupled to other thermal-hydraulic codes. In this latter context, the source code for PARCS is tightly integrated with TRACE. PARCS may also be run in a coupled mode with RELAP5 using a looser coupling technology called the Generic Interface (GI). Associated with PARCS is the GENPMAXS tool which is used for converting macroscopic cross-sections generated by lattice physics codes like SCALE/TRITON/POLARIS, CASMO, or HELIOS into a form readable by PARCS.

• RELAP5 (Reactor Excursion and Leak Analysis Program) is a one dimensional (1-D) best-estimate T/H code that is primarily used for small-break loss of coolant accidents (SBLOCAs) and other transients.

• SNAP (Symbolic Nuclear Analysis Package) is a graphical user interface with pre-processor and post-processor capabilities which assists users in developing TRACE and RELAP5 input decks and running the codes.

• AVScript (Automated Validation Script) is a script written in the PERL language designed to allow code users to automate the process of running T/H codes and generating figures that are used to analyze the simulation of interest. The current TRACE assessment framework (over 500 separate and integral effects tests) makes extensive use of this tool. The functionality provided by this tool has been captured in an SNAP plugin called AVF. It is expected that over time, the entire TRACE assessment framework will be migrated to this new plugin.

• ACAP (Automated Code Assessment Program) is a graphical program designed to allow code users to easily generate quantitative figures of merit regarding the goodness of fit between code predictions and experimental data or other code predictions. This tool is written in C/C++ and runs as a GUI on Windows or in batch mode on Windows or Linux. The batch functionality of this tool has been captured in a SNAP plugin written in Java.

These codes are used to support independent regulatory decision-making in support of design reviews, power uprates, license extensions, generic safety issues, and the review of vendor evaluation models.

Additional responsibility of the Division includes maintenance of a thermal-hydraulic databank which contains the results of T/H experiments, tests, and assessments used to demonstrate applicability of T/H codes for their intended uses.

When requested by the NRC, the contractor makes the codes available to NRC-approved domestic users via a User Support Group, and foreign users participating in the international Code Applications and Maintenance Program (CAMP). The use of the codes by these organizations provides calculations and assessments needed to validate and improve the codes. Semi-annual international workshops are conducted by the NRC to discuss code results and related issues.

Codes are currently provided to approved users for a nominal fee that covers shipping, handling, and assistance in installation of the codes. Some users opt to join the User Support Group and pay an annual membership fee. For the additional fee, members receive consultation over email or the telephone on possible problems encountered in use of the codes, including new versions of the codes, and may send a representative to annual code training conducted by the NRC. Both domestic users and CAMP members continue to assess the codes against reactor operational and/or experimental data. As a result of these comparisons and through use of the codes for plant safety assessment, many changes to the codes are suggested each year.

When sufficient changes have been made to the codes, assessments are made by the contractor and new versions of the codes are released to the users. The contractor may, at the request of NRC, assert copyright to these codes, subject to a special nuclear purpose license that gives NRC the right to distribute the code in the nuclear arena and transfer the copyright to new contractors as new contract vehicles are awarded.

The contractor provides a single point of contact to assist code users, performs code and model development for the TRACE code, provides maintenance in the form of version control, error corrections and code debugging, and provides support for CAMP activities for the TRACE and RELAP5 codes. As noted above, it is expected that code modifications will be required as a result of code usage/assessment. The contractor is also expected to develop and conduct training courses at the beginning, intermediate, and advanced levels for NRC staff as well as domestic and international code users.

The NRC has transitioned from RELAP5 to TRACE as its primary thermal-hydraulic analysis tool. As such, RELAP5 code development activities are expected to be at a very low level, limited to bug fixes and porting features from RELAP5 into TRACE, as needed. Support for RELAP5 code maintenance will continue to address CAMP member needs as required by active international agreements.

OBJECTIVE

The contractor shall provide the necessary personnel, management, materials, equipment, administrative and technical services as outlined in this Statement of Work. The work performed will support the Agency's safety mission by providing high-quality and timely regulatory research, tools, expertise and other technical products that facilitate regulatory decision making and system safety.

SCOPE OF WORK

The contractor shall provide T/H code and model development and improvements, as well as configuration control, correction of code errors, documentation updates, and user support to the NRC, its contractors, and members of CAMP and the domestic user community. The NRC will provide the contractor with the required codes.

SPECIFIC SUBTASKS:

Task 1 – TRACE/PARCS Code Development and Maintenance

The contractor shall:

1. Maintain and develop TRACE/PARCS as directed by the NRC and provide a single point of contact for satisfying code users' requests for documentation, code versions or updates, modeling changes, improved user convenience, assistance and diagnosis of user problems, correction of code bugs, code changes, and updating of code documentation. Unless authorized by NRC, modifications shall be backwardly compatible with plant input models that were developed for older versions of the code.

2. Support TRACE/PARCS on the following platforms: Windows PC - 32 bit*, Windows PC

- 64 bit*, Linux PC - 32 bit*, Linux PC - 64 bit*, and Mac/OSX (or later)* running the following Fortran compilers and tools: Intel Visual Fortran (for Linux and Windows)* and Microsoft Visual Studio*, Totalview Fortran debugger for Linux*, NAG Fortran compiler for Linux*, NAG Fortran compiler for Mac/OSX*, Lahey (Linux and Windows)*, Compaq Visual Fortran, IBM xlf compiler (for Apple), Portland Group compiler, and gfortran compiler.

3. Ensure that the above compilers and platforms with asterisks next to them are in place for the entire period of performance. Also ensure that these tools and platforms are maintained at their most current release levels throughout the contract (to the extent that the compilers will successfully compile NRC codes and the compilers and platforms reflect what is being used in the user community). Other tools and platforms can be acquired later on direct instruction from the NRC Contracting Officers Representative (COR). The contractor may be asked to extend support to other platforms and tools not listed (i.e., Sun Unix, HP Unix, etc.) to reflect changing user needs.

4. Develop and maintain user-friendly installation packages that are to be used when distributing TRACE/PARCS – one variant with source code, and one variant without source code (executable only). If an installation package does not exist, the contractor shall create one. Installation packages should include, at a minimum, a README file explaining how to install and run the code, sample inputs and outputs, all relevant code documentation, optimized and debug 32 and 64-bit executables for Linux and Windows.

Unless otherwise directed, installation packages shall be checked to ensure they do not contain proprietary information. Sample distribution CD’s shall be provided to the NRC COR before their first release.

5. Perform verification and validation (V&V) of new models and TRACE/PARCS code versions, as directed by NRC. This includes the preparation of existing assessment cases into an automated execution framework (i.e. AVScript or AVF plugin) and the preparation of assessment reports in a format specified by NRC (may be Word, Framemaker, or Latex, using templates provided by the NRC). When a new version of a code is created or new experimental data becomes available, and when requested, the contractor shall provide the NRC COR with a plan for developmentally assessing the code and an assessment matrix based on a review of the relevant models and correlations in the code and ranges of conditions over which they apply.

6. Maintain cognizance of national and international developments in the area of thermal-hydraulic codes/experiments. Based on this knowledge, as appropriate, propose modeling improvements to TRACE/PARCS and additions to the developmental assessment matrix to ensure that TRACE/PARCS retains a state-of-the-art thermal-hydraulic analysis capability.

7. Maintain a CD/DVD library (using archival quality media) of TRACE/PARCS code versions developed by the contractor. Include all files necessary to understand, reproduce, document and test these code versions, including ancillary data files and plotting routines. Restrict READ/WRITE access to supervised employees. While the NRC currently maintains configuration control of TRACE/PARCS using a version control system called Subversion, the NRC may, at its discretion, ask the contractor to assume this responsibility.

8. Maintain a Bugzilla-based (or similar) tool for user trouble reports and user change requests. The NRC COR shall be notified immediately if changes that need to be addressed urgently are identified.

9. Prior to the release of any revised versions of TRACE/PARCS, submit to the NRC COR, for review and approval, all documentation that reflects the changes made to the code(s), including assessment and user guidance. All NRC-approved released versions of TRACE/PARCS shall be provided to the NRC COR.

Task 2 – RELAP5 Code Maintenance

1. Maintain and develop RELAP5, as directed by the NRC, and provide a single point of contact for satisfying code users' requests for documentation, code versions or updates, modeling changes, improved user convenience, assistance and diagnosis of user problems, correction of code bugs, code changes, and updating of code documentation.

Unless authorized by NRC, modifications shall be backwardly compatible with plant input models that were developed for older versions of the code.

2. Support RELAP on the following platforms: Windows PC - 32 bit, Windows PC - 64 bit, Linux PC - 32 bit, Linux PC - 64 bit, and Mac/OSX (or later) running the following Fortran compilers and tools: Intel Visual Fortran (for Linux and Windows) and Microsoft Visual Studio, Totalview Fortran debugger for Linux, NAG Fortran compiler for Linux, NAG Fortran compiler for Mac/OSX, Lahey (Linux and Windows), Compaq Visual Fortran, IBM xlf compiler (for Apple), Portland Group compiler, and gfortran compiler. The contractor may be asked to extend support to other platforms and tools not listed (i.e., Sun Unix, HP Unix, etc.) to reflect changing user needs.

3. Develop and maintain user-friendly installation packages that are to be used when distributing RELAP – one variant with source code, and one variant without source code (executable only). If an installation package does not exist, the contractor shall create one.

4. Perform V&V of new models and RELAP5 code versions, as directed by NRC. When a new version of a code is created or new experimental data becomes available, and when requested, the contractor shall provide the NRC COR with a plan for developmentally assessing the code and an assessment matrix based on a review of the relevant models and correlations in the code and ranges of conditions over which they apply.

5. Maintain configuration control, and a CD/DVD library (using archival quality media) of RELAP5 code versions. Include all files necessary to understand, reproduce, document and test these code versions, including ancillary data files and plotting routines. Restrict READ/WRITE access to supervised employees.

6. Maintain a file of user trouble reports and user change requests. On a quarterly basis, provide to the NRC COR a report that describes how error corrections were/will be made with a proposed prioritization schedule, and estimated staff effort to meet these requests. The NRC COR shall be notified immediately if changes that need to be addressed urgently are identified. The report shall include a description of the procedures used for quality assurance for error corrections and code revisions.

7. Prior to the release of any revised versions of RELAP5, submit to the NRC COR, for review and approval, all documentation that reflects the changes made to the code(s), including assessment and user guidance. All NRC-approved released versions of RELAP5 shall be provided to the NRC COR.

Task 3 – Maintain the NRC Reactor Safety Data Bank

The contractor shall maintain the NRC Reactor Safety Data Bank. This may include any or all of the following:

1. Convert new (or other unconverted) experimental data to the platform independent binary (PIB) format as .bin files. All converted data shall be verified for completeness and correctness. Also, converted files shall be delivered to NRC in formats appropriate for both inclusion in the standard Data Bank hierarchy and archival into the NRC ADAMS system.

2. Update existing Data Bank files, as necessary, to ensure completeness and correctness

3. Locate references and documents associated with existing or pertinent experiments for inclusion in the Data Bank

Task 4 – CAMP Program Management

1. Provide user support to CAMP members as required by the CAMP agreements. This includes providing a single point of contact for answering general code related questions and satisfying requests for documentation, code versions or updates (with NRC approval), installation support, modeling changes, improved user convenience, assistance and diagnosis of user problems, correction of code bugs, code changes, and updating of code documentation.

2. Coordinate, participate in, and make presentations at CAMP semi-annual meetings.

This includes such details as 1) acquiring and reserving an appropriate meeting location,

2) arranging for appropriate audio-visual support, 3) preparing meeting announcements, registration materials, a meeting agenda, and assisting foreign non-NRC participants with identifying possible travel & meal options, 4) handling participant registrations, and

5) taking and preparing CAMP and Technical Program Committee (TPC) meeting minutes. These minutes shall be made available to all CAMP representatives no less than 2 months in advance of the next CAMP meeting.

3. Prepare annual summary reports (commencing one year from the effective date of the contract) of independent assessments performed by CAMP participants (i.e. in-kind contributions).

4. Assist NRC in maintaining an up-to-date list of official CAMP representatives and CAMP code users.

5. Provide telephone assistance to NRC staff and domestic code users during regular business hours, i.e., 8:00 AM to 5:00 PM local time, Monday through Friday, to diagnose their difficulties with the code and offer solutions to code problems. Code problems that are discovered shall be tracked using the tracking tools discussed in Tasks 1 & 2.

6. Distribute code versions to approved foreign code users in a form compatible with the user's computer system (workstation). The NRC may, at its discretion, direct the contractor, on behalf of NRC, to enter into formal CAMP cooperative agreements and licensing arrangements with foreign commercial organizations to exchange NRC codes in exchange for in-kind contributions and a monetary fee, as well as exchange of reactor safety information. This shall include handling all invoicing and fee collection responsibilities. The appropriate CAMP-specific templates will be provided by NRC.

The NRC may also, at its discretion, direct the contractor to manage the disbursement and collection of signed non-disclosure agreements with potential code users (the NRC currently handles this function itself). When all supporting documentation has been filed and fees have been paid, the NRC will provide authorization via e-mail to the contractor to distribute the code. This e-mail will include relevant information on the approved users.

Any monies received by the contractor from CAMP members or other authorized code users for services required under this contract, which the contractor has billed the NRC for re-imbursement, shall be credited to this contract and such credit deducted from the next invoice submitted to the NRC for payment. Invoices shall clearly track these credits as a separate item, including current and cumulative totals.

Task 5 – Domestic User Support

1. Provide user support to NRC staff and authorized domestic code users. This includes providing a single point of contact for answering general code-related questions and satisfying requests for documentation, code versions or updates (with NRC approval), installation support, modeling changes, improved user convenience, assistance and diagnosis of user problems, correction of code bugs, code changes, and updating of code documentation.

2. Assist NRC in maintaining an up-to-date list of authorized domestic code users.

3. Provide telephone assistance to NRC staff and domestic code users during regular business hours, i.e., 8:00 AM to 5:00 PM local time, Monday through Friday, to diagnose their difficulties with the code and offer solutions to code problems. Code problems that are discovered shall be tracked using the tracking tools discussed in Tasks 1 & 2.

4. Distribute code versions to approved users in a form compatible with the user's computer system (workstation). This shall include handling all invoicing and fee collection according the standard fee structure used by NRC (see http://www.nrc.gov/about-nrc/regulatory/research/obtainingcodes.html) for obtaining access to its codes. The NRC may, at its discretion, also direct the contractor to manage the disbursement and collection of signed non-disclosure agreements with potential code users (the NRC currently handles this function itself). When all supporting documentation has been filed and fees have been paid, the NRC will provide authorization via e-mail to the contractor to distribute the code. This e-mail will include relevant information on the approved users.

http://www.nrc.gov/about-nrc/regulatory/research/obtainingcodes.html

Any monies received by the contractor from domestic code users for services required under this contract, which the contractor has billed the NRC for re-imbursement shall be credited to this contract and such credit deducted from the next invoice submitted to the NRC for payment. Invoices shall clearly track these credits as a separate item, including current and cumulative totals.

Task 5 - Training

1. Conduct TRACE and/or RELAP5 training workshops for up to 5 days on a yearly basis unless otherwise instructed by the NRC COR. The workshops shall be for 20-40 users of the code (from beginners to advanced). The contractor shall acquire and reserve an appropriate facility to conduct the workshop. The location of the workshop shall, in general, be in the Washington, DC area but may also be located in closer proximity to the contractor’s location if travel to/from is convenient for code users and costs are no higher than the DC area. Decisions regarding the workshop location shall be made in consultation with (and approved by) the NRC COR..

2. Develop an agenda for each workshop in consultation with (and approved by) the NRC COR. Consistent with the agenda, revise the current materials and develop new training manuals and materials for the TRACE and RELAP5 training workshop, as appropriate All training manuals and materials shall be approved by the NRC COR and are considered property of the NRC.

Task 6 - General

1. Confer regularly with the NRC COR to discuss the progress of the contract and any other technical details.

2. Maintain and develop a T/H User Support website. The website is intended to be used by the NRC staff as well as approved CAMP and domestic code users. This website will host a Bugzilla bug tracking system.

3. On a biannual basis, commencing on the effective date of the contract, publish a newsletter for the NRC and code users that includes users' experiences not otherwise reported, and advises them of code updates, documentation changes, workshops, and other items of interest to the users. Distribute this newsletter to an approved list of recipients and publish it to the T/H User Support website.

4. Provide technical assistance to NRC. Examples include technical presentations and tutorial sessions, conference calls, meetings, and written correspondence to help the NRC staff gain adequate expertise to perform code development and maintenance functions.

TECHNICAL AND OTHER SPECIAL QUALIFICATIONS REQUIRED

This project requires engineers who have experience and knowledge (enough to train others) of

(a) various versions of TRACE, RELAP5, PARCS, SNAP, TRITON, GENPMAXS, APTPlot, AVScript, ACAP and the NRC Data Bank, (b) thermal-hydraulic and reactor physics principles,

(c) numerical methods, (d) code uncertainty analysis, and (e) modeling for both transient and accident analyses of both operating and advanced PWRs and BWRs. Since analysis using PARCS may involve the generation of cross section libraries, the project will also require engineers skilled in the use of lattice physics codes like SCALE, CASMO and HELIOS.

Individuals must also possess strong programming skills in Fortran 90/95/2003. In addition, computer capabilities to perform code development and validation are required. Finally, there must also be diversity in computer hardware availability (specifically, SUN, IBM, Intel (32 & 64 bit), AMD (32 & 64 bit), Linux, Windows, Apple Mac/OSX) and compiler technologies (Compaq Visual Fortran, Intel Visual Fortran, NAG, Lahey. Salford, g95, PathScale, & Absoft) used for compiling and running TRACE by most of the users.

The contractor is responsible for assigning technical staff, employees, subcontractors, or specialists who have the required educational background, experience, or combination thereof to meet the technical objectives of the work specified in this statement of work. The NRC will rely on representations made by the contractor concerning the qualifications of the personnel assigned to this contract including assurance that all information contained in the technical and cost proposal, including resumes, is accurate and truthful. In addition, the contractor and personnel assigned to this work must be approved for handling and working with proprietary information. One or more of the key personnel should have acquired in the past, or be capable of acquiring in the future, an NRC IT level 2 security clearance. Unescorted access to NRC Headquarters is not required.

The use of key personnel and any proposed change to key personnel on this contract is subject to the NRC COR approval. This includes proposed use of principal persons (i.e., key contributors) during the life of the contract.

For any work to be subcontracted or performed by consultants the contractor shall obtain the NRC Contracting Officer's written approval of the subcontractor or consultant prior to initiation of the subcontract effort. Conflict of interest considerations shall apply to any subcontracted effort.

LEVEL OF EFFORT

The level of effort for this task is estimated at 4,360 professional hours each year throughout the 5-year period of performance for a total of 21,800 professional hours.

Year 1 Year 2 Year 3 Year 4 Year 5 Total Est.

Hours Labor Category Estimated

Hours Estimated Hours

Estimated Hours

Estimated Hours

Estimated Hours

Principal Engineer 2490 2490 2490 2490 2490 12,450 Senior Engineer 380 380 380 380 380 1,900 Engineer 1220 1220 1220 1220 1220 6,100 Admin 270 270 270 270 270 1,350

This information is advisory and is not to be considered as the sole basis for the development of the staffing plan. For the purposes of the Government estimate, 2080 hours constitute a staff year.

PERIOD OF PERFORMANCE

The period of performance of this Task Order is 5 years.

DELIVERABLES/SCHEDULES AND/OR MILESTONES

Special Works:

1. Code versions (and associated installation packages) to be distributed to NRC-approved users in a form compatible with the user's computer system.

2. On a semi-annual basis, within one month following June and December, provide to the NRC COR a report that describes any outstanding errors or modeling deficiencies in RELAP5, how error corrections were/will be made with a proposed prioritization schedule, and estimated staff effort to meet these requests.

3. As requested by the NRC COR, the contractor shall provide CD/DVD’s containing converted electronic data as .bin files in PIB format, as well as any associated documentation, technical reports, and/or supporting material in electronic format for inclusion in the NRC Data Bank. The submittal will also include files in a format appropriate for archival into the NRC’s ADAMS document system.

4. Training workshops, conducted by contractor staff on a yearly basis unless otherwise instructed by the NRC. In addition to the training workshop itself, this deliverable shall include the training materials for the workshop, as requested by the NRC COR. Copies of past training workshops may be requested by the NRC at any time.

5. Code and/or assessment transmittal packages, as requested by the NRC COR. These packages shall include one or more of the following items — updated source code, patch files, associated scripts, README files, Summary.html files, input, restart and output files, plot files, AVScript files, documentation (in Framemaker and pdf formats), calculation notebooks, and any other files necessary for NRC to reproduce the work and reach the same (or similar) conclusions as the contractor.

6. Calculation notebooks used for developing input decks for nuclear reactor systems calculations.

7. As requested, but no less frequent than on an annual basis, provide the NRC COR with a list of currently distributed code versions and licensed code users for TRACE, RELAP, and PARCS. The NRC COR may also, at his/her discretion, request all license management information that would be necessary to appropriately manage individual license holders’ access to NRC codes.

8. Software quality assurance documentation, as requested by the NRC COR.

9. Website content, as requested by the NRC COR.

10. Version control database information, as requested by the NRC COR

Non-Special Works:

11. On a semi-annual basis, commencing on the effective date of the contract, publish a newsletter for the NRC and code users that includes users' experiences not otherwise reported, and advises them of code updates, documentation changes, workshops, and other items of interest to the users.

12. Presentations to be made at CAMP semi-annual meetings and ACRS meetings. For CAMP, these presentations will be delivered to the NRC COR no later than 2 weeks prior to the start of the CAMP conference. For ACRS, delivery dates will be in conformance with ACRS deadlines plus sufficient lead times for the NRC COR to review and approve the content.

13. CAMP and Technical Program Committee (TPC) meeting minutes. These minutes shall be made available to all CAMP representatives no less than 2 months in advance of the next CAMP meeting.

14. Periodic short status updates, as requested by NRC, posted to the T/H User Support website with regard to availability of new TRACE/RELAP5 releases, upcoming CAMP meetings, upcoming training opportunities, newly published NUREG/IA’s, and/or other items of interest to code users.

15. Prepare annual summary reports (commencing one year from the effective date of the contract) of Independent Assessments performed by CAMP participants.

16. Provide a written request each year to the NRC Contracting Officer and COR as to the equipment and/or any upgrades required for the performance of this contract. Keep a list of all equipment acquired through the NRC.

17. Letter reports describing the work performed submitted in accordance with each task order specification and schedule.

18. Technical Progress Reports – shall meet the requirements of Clause 2052.211-71 Technical Progress Reports (JAN 1993) of the contract.

19. Financial Status Reports – shall meet the requirements of Clause 2052.211-72 Financial Status Report (OCT 1999) of the contract.

MEETINGS AND TRAVEL

Two trips to Rockville MD per year for two staff for two days each to participate in ACRS meetings (dates to be determined).

Two trips to Rockville MD per year for two staff for 2 day(s) each for program review (dates to be determined).

One trip within the U.S. per year for two staff to attend the CAMP meeting for 3 days (dates to be determined).

One trip to the CAMP conference in a foreign country for one person for 3 days (dates and location to be determined).

One trip per year to the Rockville MD area for three staff to provide TRACE training workshop for up to 5 days (dates to be determined).

NRC-FURNISHED MATERIAL

1. Current versions of the TRACE, RELAP5, PARCS, and other related codes, PIRTs, code documentation, and relevant code assessment matrices within two weeks of contract startup.

2. A list of approved users for TRACE and related codes to whom the contractor shall supply services described above. As needed, the NRC will provide revised lists.

3. Current TRACE and RELAP5 training manuals and materials

4. Current source code for TRACE and RELAP5. Historical source versions of these codes as needed.

5. Experimental data in raw electronic format as well as any supporting documentation, as needed.