ML22257A069: Difference between revisions

From kanterella
Jump to navigation Jump to search
(StriderTol Bot insert)
 
(StriderTol Bot change)
Line 16: Line 16:


=Text=
=Text=
{{#Wiki_filter:31310019D0002/31310021F0038 The purpose of this task order modification is to: (1) increase the task order ceiling by
{{#Wiki_filter:31310019D0002/31310021F0038
 
The purpose of this task order modification is to: (1) increase the task order ceiling by
$184,299.02, from $490,130.97 to $674,429.99; (2) provide incremental funding in the amount of $127,250.19, thereby increasing the obligated amount from $490,130.97 to $617,381.16; (3) revise the price schedule; (4) revise the Statement of Work to add in Task 5 entitled, Code Documentation for Generalized Expansion of TRACE/PARCS Interface to Accommodate Dynamic Control Rod Motion and In-Core Detector Response; and (5) extend the period of performance through December 31, 2022. Accordingly, the task order is hereby modified as follows:
$184,299.02, from $490,130.97 to $674,429.99; (2) provide incremental funding in the amount of $127,250.19, thereby increasing the obligated amount from $490,130.97 to $617,381.16; (3) revise the price schedule; (4) revise the Statement of Work to add in Task 5 entitled, Code Documentation for Generalized Expansion of TRACE/PARCS Interface to Accommodate Dynamic Control Rod Motion and In-Core Detector Response; and (5) extend the period of performance through December 31, 2022. Accordingly, the task order is hereby modified as follows:
Section B - Supplies or Services/Prices was revised as follows.
Section B - Supplies or Services/Prices was revised as follows.
Summary of Clause Changes:
Summary of Clause Changes:
Clause titled CONSIDERATION AND OBLIGATION-TASK ORDERS is incorporated as follows:
Clause titled CONSIDERATION AND OBLIGATION-TASK ORDERS is incorporated as follows:
CONSIDERATION AND OBLIGATION-TASK ORDERS (a) The ceiling of this order for services is $674,429.99 (Costs of               and Fee of
 
            ).
CONSIDERATION AND OBLIGATION-TASK ORDERS
 
(a) The ceiling of this order for services is $674,429.99 (Costs of and Fee of
).
 
(b) This order is subject to the minimum and maximum ordering requirements set forth in the contract.
(b) This order is subject to the minimum and maximum ordering requirements set forth in the contract.
(c) The amount presently obligated with respect to this order is $617,381.16 (Costs of and Fee of             ). The obligated amount shall, at no time, exceed the order ceiling as specified in paragraph (a) above. When and if the amount(s) paid and payable to the Contractor hereunder shall equal the obligated amount, the Contractor shall not be obligated to continue performance of the work unless and until the Contracting Officer shall increase the amount obligated with respect to this order, in accordance with FAR Part 43 - Modifications. Any work undertaken by the Contractor in excess of the obligated amount specified above is done so at the Contractor's sole risk and may not be reimbursed by the Government.
 
(c) The amount presently obligated with respect to this order is $617,381.16 (Costs of and Fee of ). The obligated amount shall, at no time, exceed the order ceiling as specified in paragraph (a) above. When and if the amount(s) paid and payable to the Contractor hereunder shall equal the obligated amount, the Contractor shall not be obligated to continue performance of the work unless and until the Contracting Officer shall increase the amount obligated with respect to this order, in accordance with FAR Part 43 - Modifications. Any work undertaken by the Contractor in excess of the obligated amount specified above is done so at the Contractor's sole risk and may not be reimbursed by the Government.
 
(d) The Contractor shall comply with the provisions of FAR 52.232 Limitation of Funds, for incrementally-funded delivery orders or task orders.
(d) The Contractor shall comply with the provisions of FAR 52.232 Limitation of Funds, for incrementally-funded delivery orders or task orders.
Summary of Clause Changes:
Summary of Clause Changes:
Clause titled PRICE/COST SCHEDULE is incorporated as follows:
Clause titled PRICE/COST SCHEDULE is incorporated as follows:
PRICE/COST SCHEDULE CLIN            Description            Amount 00001Estimated Cost 00002Fixed-Fee TOTAL        $674,429.99 Page 2


31310019D0002/31310021F0038 Section C - Description/Specifications was revised as follows.
PRICE/COST SCHEDULE
 
CLIN Description Amount 00001Estimated Cost 00002Fixed-Fee TOTAL $674,429.99
 
Page 2 31310019D0002/31310021F0038
 
Section C - Description/Specifications was revised as follows.
 
Summary of Clause Changes:
Summary of Clause Changes:
Clause titled STATEMENT OF WORK is incorporated as follows:
Clause titled STATEMENT OF WORK is incorporated as follows:
STATEMENT OF WORK PARCS Code Suite Maintenance, Development, and User Support Contents C.1    Background C.2    Objective C.3    Scope of Work C.4    Reporting Requirements - Monthly Letter Status Report (MLSR)
C.5    Deliverables and Delivery Schedule C.6    Required Labor Categories C.7    Data Rights C.8    Section 508 - Information and Communication Technology Accessibility C.9    Incremental Development for Software C.10    Place of Performance C.11    Contractor Travel C.12    Applicable Publications (Current Editions)
C.13    Security Requirements C.14    License Fee Recoverable C.1    Background The U.S. Nuclear Regulatory Commission (NRC), Office of Nuclear Regulatory Research (RES), Division of Safety Analysis (DSA) has responsibility for the development, testing, assessment, maintenance, and user support of the NRC's thermal-hydraulic (T/H) and neutronics computer codes (such as PARCS).
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 TRAC/RELAP Advanced Computational Engine (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 code which is used for converting macroscopic cross-sections generated by lattice physics codes like SCALE/TRITON, SCALE/Polaris, CASMO, or HELIOS into a form readable by PARCS, along with a generalized capability to construct a cross section case matrix with Page 3


31310019D0002/31310021F0038 consideration for nodal burnup history effects and nodal state parameterizations.
STATEMENT OF WORK
 
PARCS Code Suite Maintenance, Development, and User Support
 
Contents
 
C.1 Background C.2 Objective C.3 Scope of Work C.4 Reporting Requirements - Monthly Letter Status Report (MLSR)
C.5 Deliverables and Delivery Schedule C.6 Required Labor Categories C.7 Data Rights C.8 Section 508 - Information and Communication Technology Accessibility C.9 Incremental Development for Software C.10 Place of Performance C.11 Contractor Travel C.12 Applicable Publications (Current Editions)
C.13 Security Requirements C.14 License Fee Recoverable
 
C.1 Background
 
The U.S. Nuclear Regulatory Commission (NRC), Office of Nuclear Regulatory Research (RES), Division of Safety Analysis (DSA) has responsibility for the development, testing, assessment, maintenance, and user support of the NRC's thermal-hydraulic (T/H) and neutronics computer codes (such as PARCS).
 
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 TRAC/RELAP Advanced Computational Engine (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 code which is used for converting macroscopic cross-sections generated by lattice physics codes like SCALE/TRITON, SCALE/Polaris, CASMO, or HELIOS into a form readable by PARCS, along with a generalized capability to construct a cross section case matrix with
 
Page 3 31310019D0002/31310021F0038
 
consideration for nodal burnup history effects and nodal state parameterizations.
 
The PARCS code supports independent regulatory decision making in that it allows staff and contractors to develop core physics models to confirm that core behavior is within safety limits for general steady-state operation and for a range of plant transients. PARCS is specifically used as a tool in confirmatory safety reviews of power plant operator actions, core designs, power uprates, and license amendments. This is done for both design certifications and License Amendment Requests (LARs).
The PARCS code supports independent regulatory decision making in that it allows staff and contractors to develop core physics models to confirm that core behavior is within safety limits for general steady-state operation and for a range of plant transients. PARCS is specifically used as a tool in confirmatory safety reviews of power plant operator actions, core designs, power uprates, and license amendments. This is done for both design certifications and License Amendment Requests (LARs).
For the context of this work, and when not directly coupled to TRACE or RELAP, PARCS is maintained in a larger, standalone form for quasi-steady-state fuel cycle analysis, with consideration for fuel shuffle schemes over multiple fuel cycles. In standalone form, PARCS also maintains a basic T/H-to-neutronic feedback capability through its coupling with the PATHS (BWRs/PWRs) code, along with an even simpler mass-energy based T/H solver that is specific to PWRs. When maintained in this standalone configuration, PARCS has its own version control system, regression test suite, and set of assessments problems. GenPMAXS is also maintained in its own version control system with a test suite segmented by all of the lattice physics codes that it supports. There is also a corresponding Perl-based regression harness that is used to test and interrogate the conversion of SCALE/TRITON cross sections from t16 format to PMAXS format in a systematic and visual manner.
For the context of this work, and when not directly coupled to TRACE or RELAP, PARCS is maintained in a larger, standalone form for quasi-steady-state fuel cycle analysis, with consideration for fuel shuffle schemes over multiple fuel cycles. In standalone form, PARCS also maintains a basic T/H-to-neutronic feedback capability through its coupling with the PATHS (BWRs/PWRs) code, along with an even simpler mass-energy based T/H solver that is specific to PWRs. When maintained in this standalone configuration, PARCS has its own version control system, regression test suite, and set of assessments problems. GenPMAXS is also maintained in its own version control system with a test suite segmented by all of the lattice physics codes that it supports. There is also a corresponding Perl-based regression harness that is used to test and interrogate the conversion of SCALE/TRITON cross sections from t16 format to PMAXS format in a systematic and visual manner.
C.2   Objective The objective of this acquisition is to obtain regulatory technical support with the maintenance, code support, assessment, development, and user training of the PARCS and GenPMAXS codes and the interface of PARCS with SNAP. The contractor shall provide the necessary personnel, management, materials, equipment, administrative and technical services as outlined in this Statement of Work.
 
C.3     Scope of Work The contractor shall provide the following services for the PARCS code suite: configuration control, the correction of code errors, documentation updates, the development of test problems, and user support to the NRC, its contractors, and members of CAMP and the domestic user community.
C.2 Objective
 
The objective of this acquisition is to obtain regulatory technical support with the maintenance, code support, assessment, development, and user training of the PARCS and GenPMAXS codes and the interface of PARCS with SNAP. The contractor shall provide the necessary personnel, management, materials, equipment, administrative and technical services as outlined in this Statement of Work.
 
C.3 Scope of Work
 
The contractor shall provide the following services for the PARCS code suite: configuration control, the correction of code errors, documentation updates, the development of test problems, and user support to the NRC, its contractors, and members of CAMP and the domestic user community.
 
PARCS and GenPMAXS code changes shall be tested on a variety of compiler/operating system combinations. The following compilers shall be used during maintenance and development of both of the PARCS and GenPMAXS source codes:
PARCS and GenPMAXS code changes shall be tested on a variety of compiler/operating system combinations. The following compilers shall be used during maintenance and development of both of the PARCS and GenPMAXS source codes:
Windows (Microsoft Visual Studio/Intel Visual Fortran)
Windows (Microsoft Visual Studio/Intel Visual Fortran)
Linux (gfortran, Intel, NAG, Portland Group)
Linux (gfortran, Intel, NAG, Portland Group)
The contractor shall ensure that the above compilers and platforms are in place for the entire period of performance, and that these compilers are maintained at their most current release levels throughout the contract. The Contracting Officers Representative (COR) may require the contractor to extend support to other compiler/operating system combinations that are not listed as a result of changing priorities.
The contractor shall ensure that the above compilers and platforms are in place for the entire period of performance, and that these compilers are maintained at their most current release levels throughout the contract. The Contracting Officers Representative (COR) may require the contractor to extend support to other compiler/operating system combinations that are not listed as a result of changing priorities.
Page 4


31310019D0002/31310021F0038 SPECIFIC SUBTASKS:
Page 4 31310019D0002/31310021F0038
3.1: Task 1 - PARCS/PATHS Code Maintenance Subtask 1.1: Identify Code Bugs The contractor shall identify all code bugs and maintain them in a bug report document which, at a high level, summarizes code errors received from all PARCS/PATHS users (bugs, unexplained behavior, and documentation problems). This document shall include the following information for each bug: a summary description of the bug; the date the bug was reported; the user or organization who reported the bug; and the status of the bug (i.e. in what code version the bug was discovered).
 
Subtask 1.2: Perform Code Fixes Under COR technical direction, the contractor shall make changes to the collective PARCS/PATHS source code in response to bugs reported by the COR and all other PARCS/PATHS users, as captured in the bug report under Subtask 1.1.
SPECIFIC SUBTASKS:
 
3.1: Task 1 - PARCS/PATHS Code Maintenance
 
Subtask 1.1: Identify Code Bugs
 
The contractor shall identify all code bugs and maintain them in a bug report document which, at a high level, summarizes code errors received from all PARCS/PATHS users (bugs, unexplained behavior, and documentation problems). This document shall include the following information for each bug: a summary description of the bug; the date the bug was reported; the user or organization who reported the bug; and the status of the bug (i.e. in what code version the bug was discovered).
 
Subtask 1.2: Perform Code Fixes
 
Under COR technical direction, the contractor shall make changes to the collective PARCS/PATHS source code in response to bugs reported by the COR and all other PARCS/PATHS users, as captured in the bug report under Subtask 1.1.
 
Upon COR direction, the contractor shall also update the LaTeX(lua)/python-based code documentation (PARCS Input, Theory, User Guide, and MAPTAB manuals and PATHS Input and Theory manuals) as the result of the correction of typos, the elimination of features that are no longer supported in the code, or the desire of users to make the documentation more clear and relevant, which may be included in the bug report.
Upon COR direction, the contractor shall also update the LaTeX(lua)/python-based code documentation (PARCS Input, Theory, User Guide, and MAPTAB manuals and PATHS Input and Theory manuals) as the result of the correction of typos, the elimination of features that are no longer supported in the code, or the desire of users to make the documentation more clear and relevant, which may be included in the bug report.
Any PARCS/PATHS source code changes made as a result of code bugs shall be tested against the PARCS regression test suite before being checked into the code version control system. New test problems that are added to the PARCS or GenPMAXS test suites as a result of the correction of code bugs shall be documented in the HyperText Markup Language (HTML) summary file. The contractor shall modify the run scripts for the test suite as a result of any test problem additions, changes, or deletions, and shall modify the build scripts as a result of any additions, changes, or deletions to the source code.
Any PARCS/PATHS source code changes made as a result of code bugs shall be tested against the PARCS regression test suite before being checked into the code version control system. New test problems that are added to the PARCS or GenPMAXS test suites as a result of the correction of code bugs shall be documented in the HyperText Markup Language (HTML) summary file. The contractor shall modify the run scripts for the test suite as a result of any test problem additions, changes, or deletions, and shall modify the build scripts as a result of any additions, changes, or deletions to the source code.
The contractor shall create new versions of PARCS in response to code bug corrections. These different code versions shall be maintained using a version control system methodology, and this methodology shall have the ability to retrieve previously released code versions. Each retrieved code version shall contain enough information such that it can be a self-contained distribution (an archive).
The contractor shall create new versions of PARCS in response to code bug corrections. These different code versions shall be maintained using a version control system methodology, and this methodology shall have the ability to retrieve previously released code versions. Each retrieved code version shall contain enough information such that it can be a self-contained distribution (an archive).
Subtask 1.3: Prepare TRACE Updates At a frequency determined by the COR, the contractor shall prepare a TRACE update for submittal to the TRACE website. This update shall include the revised PARCS source code (and the revised TRACE source code, if necessary), a list of the differences between code versions embedded in text files, new test problems formulated to test the code update, revised code documentation, and the results of automated testing against the TRACE regression suite.
3.2: Task 2 - PARCS/PATHS Code Support As directed by the COR, the contractor shall provide analysis and consultation support related Page 5


31310019D0002/31310021F0038 to PARCS/PATHS and GenPMAXS. This support shall include, but is not limited to: guidance on PARCS use, GenPMAXS, explanations of the algorithms that are coded into PARCS/PATHS, develop PARCS/PATHS models or GenPMAXS models, interpret results, or explain underlying physics phenomena or algorithms, explanations of the input format, or guidance on best-practices (how to approach a problem), the interpretation of any associated lattice physics models or PMAXS cross section libraries that are affiliated with the core model, performing pre-analysis scoping studies, and responding to code user questions and comments provided to the contractor by the COR. Analysis and consultation support may require the preparation of summaries, emails, or revised input decks, as well as participation in NRC meetings.
Subtask 1.3: Prepare TRACE Updates
3.3: Task 3 - PARCS/PATHS Code Development Upon COR direction and prioritization, the contractor shall perform any PARCS/PATHS source code development that may be necessary as a result of user feedback, future RES program needs, regulatory user needs, and CAMP needs. This code development shall not be limited to code fixes, but shall be broadly applied to significant code changes that support user convenience (e.g., improved error checking and advanced editing options), code robustness and speed (e.g., linear solver upgrades and changes and advanced neutronic methods),
 
At a frequency determined by the COR, the contractor shall prepare a TRACE update for submittal to the TRACE website. This update shall include the revised PARCS source code (and the revised TRACE source code, if necessary), a list of the differences between code versions embedded in text files, new test problems formulated to test the code update, revised code documentation, and the results of automated testing against the TRACE regression suite.
 
3.2: Task 2 - PARCS/PATHS Code Support
 
As directed by the COR, the contractor shall provide analysis and consultation support related
 
Page 5 31310019D0002/31310021F0038
 
to PARCS/PATHS and GenPMAXS. This support shall include, but is not limited to: guidance on PARCS use, GenPMAXS, explanations of the algorithms that are coded into PARCS/PATHS, develop PARCS/PATHS models or GenPMAXS models, interpret results, or explain underlying physics phenomena or algorithms, explanations of the input format, or guidance on best-practices (how to approach a problem), the interpretation of any associated lattice physics models or PMAXS cross section libraries that are affiliated with the core model, performing pre-analysis scoping studies, and responding to code user questions and comments provided to the contractor by the COR. Analysis and consultation support may require the preparation of summaries, emails, or revised input decks, as well as participation in NRC meetings.
 
3.3: Task 3 - PARCS/PATHS Code Development
 
Upon COR direction and prioritization, the contractor shall perform any PARCS/PATHS source code development that may be necessary as a result of user feedback, future RES program needs, regulatory user needs, and CAMP needs. This code development shall not be limited to code fixes, but shall be broadly applied to significant code changes that support user convenience (e.g., improved error checking and advanced editing options), code robustness and speed (e.g., linear solver upgrades and changes and advanced neutronic methods),
significant modeling enhancements, or utility codes or scripts that support PARCS/PATHS code use.
significant modeling enhancements, or utility codes or scripts that support PARCS/PATHS code use.
Any PARCS/PATHS source code changes made as a result of code enhancements or modeling changes shall be tested against the PARCS regression test suite before being checked-in to the code version control system. The contractor shall modify the run scripts for the test suite as a result of any test problem additions, changes, or deletions, and shall modify the build scripts as a result of any additions, changes, or deletions to the source code. The contractor shall revise the LaTeX(lua)/python-based code documentation (PARCS Input, Theory, User Guide, and MAPTAB manuals and PATHS Input and Theory manuals), to reflect the code development activity.
Any PARCS/PATHS source code changes made as a result of code enhancements or modeling changes shall be tested against the PARCS regression test suite before being checked-in to the code version control system. The contractor shall modify the run scripts for the test suite as a result of any test problem additions, changes, or deletions, and shall modify the build scripts as a result of any additions, changes, or deletions to the source code. The contractor shall revise the LaTeX(lua)/python-based code documentation (PARCS Input, Theory, User Guide, and MAPTAB manuals and PATHS Input and Theory manuals), to reflect the code development activity.
Subtask 3.1: Pre-Code Documentation Requirements For each code development activity, the contractor shall develop the following documentation, per the guidance specified in NUREG-1737:
 
Subtask 3.1: Pre-Code Documentation Requirements
 
For each code development activity, the contractor shall develop the following documentation, per the guidance specified in NUREG-1737:
 
Software Requirements Specification (SRS)
Software Requirements Specification (SRS)
The SRS is a technical document that focuses on the underlying algorithms, technical specifications, and requirements of the software.
The SRS is a technical document that focuses on the underlying algorithms, technical specifications, and requirements of the software.
Software Design and Implementation Document (SDID)/Qualification Test Plan (QTP) (referred to as the test plan in NUREG-1737)
Software Design and Implementation Document (SDID)/Qualification Test Plan (QTP) (referred to as the test plan in NUREG-1737)
The SDID/QTP is a combined document that describes the implementation of the technical specifications and algorithms outlined in the SRS, i.e., how the software will be structured and designed, and also describes how the implemented capabilities are proposed to be tested, i.e.
The SDID/QTP is a combined document that describes the implementation of the technical specifications and algorithms outlined in the SRS, i.e., how the software will be structured and designed, and also describes how the implemented capabilities are proposed to be tested, i.e.
the test problems which will be used to demonstrate the new capability.
the test problems which will be used to demonstrate the new capability.
Subtask 3.2: Perform Code Development Page 6


31310019D0002/31310021F0038 The contractor shall implement code development features into the PARCS code distribution (i.e., source code, build scripts, test problems, and code documentation (as applicable), etc.) as directed by the COR.
Subtask 3.2: Perform Code Development
Subtask 3.3: Prepare Completion Report The contractor shall prepare a Completion Report (CR) that documents the programming effort.
 
Page 6 31310019D0002/31310021F0038
 
The contractor shall implement code development features into the PARCS code distribution (i.e., source code, build scripts, test problems, and code documentation (as applicable), etc.) as directed by the COR.
 
Subtask 3.3: Prepare Completion Report
 
The contractor shall prepare a Completion Report (CR) that documents the programming effort.
Specifically, the report shall summarize the methodology, software, and user changes, and shall include calculation results that demonstrate the changed coding.
Specifically, the report shall summarize the methodology, software, and user changes, and shall include calculation results that demonstrate the changed coding.
Subtask 3.4: Prepare TRACE Updates A matching TRACE update (that envelopes the PARCS code changes completed in Subtasks 3.1 through 3.3) shall be prepared by the contractor for submittal to the TRACE website. This update shall include the new PARCS source code (and new TRACE source code, if necessary),
 
Subtask 3.4: Prepare TRACE Updates
 
A matching TRACE update (that envelopes the PARCS code changes completed in Subtasks 3.1 through 3.3) shall be prepared by the contractor for submittal to the TRACE website. This update shall include the new PARCS source code (and new TRACE source code, if necessary),
the differences between code versions embedded in text files, new test problems formulated to test the code update, code documentation, and the results of automated testing against the TRACE regression suite.
the differences between code versions embedded in text files, new test problems formulated to test the code update, code documentation, and the results of automated testing against the TRACE regression suite.
3.4: Task 4 - GenPMAXS Code Support and Maintenance The contractor shall provide technical support and code maintenance for GenPMAXS to assure the consistency and accuracy of the cross section data that feeds PARCS.
Subtask 4.1: Maintain GenPMAXS in a Version Control System The contractor shall maintain GenPMAXS in a version control system, each version being retrievable as a self-contained unit. Along with each version the contractor shall store the build system (MSVS workspaces, Linux and windows make files, and source), the test suite (test problems and run scripts), and the code documentation. The GenPMAXS code documentation shall include a manual describing the use and methodology behind GenPMAXS, as well as a document describing known issues.
Subtask 4.2: Correct GenPMAXS Bugs The contractor shall correct bugs resulting from the use of GenPMAXS for reading in cross section data supplied by the lattice physics codes. Any new test problems that are added to the GenPMAXS test suite as a result of the correction of code bugs shall be documented in the GenPMAXS manual.
3.5: Task 5 - Code Documentation for Generalized Expansion of TRACE/PARCS Interface to Accommodate Dynamic Control Rod Motion and In-Core Detector Response Part A The contractor shall draft software planning documents (SRS and SDID/QTP) that plan the development and implementation of the capability for TRACE to manipulate PARCS control rod bank positions in response to nuclear power plant signals. During operational transients, these Page 7


31310019D0002/31310021F0038 (QTP)
3.4: Task 4 - GenPMAXS Code Support and Maintenance
 
The contractor shall provide technical support and code maintenance for GenPMAXS to assure the consistency and accuracy of the cross section data that feeds PARCS.
 
Subtask 4.1: Maintain GenPMAXS in a Version Control System
 
The contractor shall maintain GenPMAXS in a version control system, each version being retrievable as a self-contained unit. Along with each version the contractor shall store the build system (MSVS workspaces, Linux and windows make files, and source), the test suite (test problems and run scripts), and the code documentation. The GenPMAXS code documentation shall include a manual describing the use and methodology behind GenPMAXS, as well as a document describing known issues.
 
Subtask 4.2: Correct GenPMAXS Bugs
 
The contractor shall correct bugs resulting from the use of GenPMAXS for reading in cross section data supplied by the lattice physics codes. Any new test problems that are added to the GenPMAXS test suite as a result of the correction of code bugs shall be documented in the GenPMAXS manual.
 
3.5: Task 5 - Code Documentation for Generalized Expansion of TRACE/PARCS Interface to Accommodate Dynamic Control Rod Motion and In-Core Detector Response
 
Part A
 
The contractor shall draft software planning documents (SRS and SDID/QTP) that plan the development and implementation of the capability for TRACE to manipulate PARCS control rod bank positions in response to nuclear power plant signals. During operational transients, these
 
Page 7
 
31310019D0002/31310021F0038
 
(QTP)
 
For this code development activity, the contractor shall develop an SDID and a Qualification Test Plan, per the guidance specified in NUREG-1737.
For this code development activity, the contractor shall develop an SDID and a Qualification Test Plan, per the guidance specified in NUREG-1737.
The SDID/QTP is a combined document that describes the implementation of the technical specifications and algorithms outlined in the SRS, and also describes how the implemented capabilities will be tested. For this task, the SDID shall describe any planned changes to inputs (if any) in the form of additional fields, cards, and blocks in TRACE and PARCS (and GenPMAXS, if any). The QTP shall propose model test problems to demonstrate the functionality of the implementations.
The SDID/QTP is a combined document that describes the implementation of the technical specifications and algorithms outlined in the SRS, and also describes how the implemented capabilities will be tested. For this task, the SDID shall describe any planned changes to inputs (if any) in the form of additional fields, cards, and blocks in TRACE and PARCS (and GenPMAXS, if any). The QTP shall propose model test problems to demonstrate the functionality of the implementations.
There should be at least one BWR model proposed to test the capabilities described in Part B (interaction of PARCS detector signals with the TRACE control system), and at least one other LWR model proposed to test the capabilities described in Part A (TRACE control of PARCS control rod movement).
There should be at least one BWR model proposed to test the capabilities described in Part B (interaction of PARCS detector signals with the TRACE control system), and at least one other LWR model proposed to test the capabilities described in Part A (TRACE control of PARCS control rod movement).
C.4     Reporting Requirements - Monthly Letter Status Report (MLSR)
 
C.4 Reporting Requirements - Monthly Letter Status Report (MLSR)
 
The contractor shall provide a Monthly Letter Status Report which consists of a technical progress report and financial status report. This report will be used by the Government to assess the adequacy of the resources proposed by the contractor to accomplish the work contained in this SOW and provide status of contractor progress in achieving activities and producing deliverables. The report shall include order summary information, work completed during the specified period, milestone schedule information, problem resolution, travel plans, and staff hour summary.
The contractor shall provide a Monthly Letter Status Report which consists of a technical progress report and financial status report. This report will be used by the Government to assess the adequacy of the resources proposed by the contractor to accomplish the work contained in this SOW and provide status of contractor progress in achieving activities and producing deliverables. The report shall include order summary information, work completed during the specified period, milestone schedule information, problem resolution, travel plans, and staff hour summary.
C.5    Deliverables and Delivery Schedule The Contractor shall correct errors in contractor developed software and applicable documentation that are not commercial off-the-shelf which are discovered by the NRC or the contractor. Inability of the parties to determine the cause of software errors shall be resolved in accordance with the Disputes clause in Section I, FAR 52.233-1, incorporated by reference in the base contract.
Section                                                                                    Submit Deliverable                  Due Date                    Format
    #                                                                                        to 3.1, Subtask Bug Report                  20th of the following    MS Word Document          COR 1.1                            month Tarball or SecureZIP Archive Within 5 business days of 3.1, PARCS/PATHS Code the completion of code Subtask                                                        Transmitted via e-mail,  COR Distribution              checked-in PARCS code 1.2                                                      TRACE Website or other version mechanism specified by the COR Page 9


31310019D0002/31310021F0038 Tarball or SecureZIP Archive 3.1, TRACE Update           Within 15 business days Subtask                                                   Transmitted via e-mail, COR Distribution            of COR request 1.3                                                   TRACE Website or other mechanism specified by the COR Documentation follows Code Support           Within 10 business days guidance from COR (email 3.2                                                                            COR Documentation           of the COR request       or MS Word document or revised input deck) 3.3, Pre-Code                 Within 20 business days Subtask Documentation (SRS,     of technical direction by MS Word document       COR 3.1 SDID/QTP)               COR Tarball or SecureZIP Archive 3.3,                         Within 25 business days PARCS/PATHS Subtask                         of technical direction by Transmitted via e-mail, COR Distribution 3.2                         COR                       TRACE Website or other mechanism specified by the COR Within 20 business days MS Word Document 3.3, of completion of the Subtask Completion Report                                                          COR programming effort in     Document follows 3.3 Task 3.2                 guidance in NUREG-1737 Tarball or SecureZIP Archive 3.3,                         Within 15 business days Subtask TRACE Code Update       of the completion of Task Transmitted via e-mail, COR 3.4                         3.2                       TRACE Website or other mechanism specified by the COR Tarball or SecureZIP Archive 3.4,                         Within 5 business days GenPMAXS Subtask                         after checking in the     Transmitted via e-mail, COR Distribution to COR 4.2                         GenPMAXS version         TRACE Website or other mechanism specified by the COR Pre-Code 3.5,                         Within 30 business days Documentation (SRS)
C.5 Deliverables and Delivery Schedule
Subtask                          of Subtask 5.1             MS Word document       COR for Dynamic Control 5.1                          commencement Rod/Detector Capability Pre-Code 3.5, Documentation           Within 30 business days Subtask (SDID/QTP) for           of Subtask 5.2           MS Word document       COR 5.2 Dynamic Control         commencement Rod/Detector Capability Page 10
 
The Contractor shall correct errors in contractor developed software and applicable documentation that are not commercial off-the-shelf which are discovered by the NRC or the contractor. Inability of the parties to determine the cause of software errors shall be resolved in accordance with the Disputes clause in Section I, FAR 52.233-1, incorporated by reference in the base contract.
 
Section Deliverable Due Date Format Submit
# to 3.1, 20th of the following Subtask Bug Report month MS Word Document COR 1.1 Tarball or SecureZIP Within 5 business days of Archive 3.1, PARCS/PATHS Code the completion of code Subtask Distribution checked-in PARCS code Transmitted via e-mail, COR 1.2 version TRACE Website or other mechanism specified by the COR
 
Page 9 31310019D0002/31310021F0038
 
Tarball or SecureZIP Archive 3.1, TRACE Update Within 15 business days Subtask Distribution of COR request Transmitted via e-mail, COR 1.3 TRACE Website or other mechanism specified by the COR Documentation follows 3.2Code Support Within 10 business days guidance from COR (email COR Documentation of the COR request or MS Word document or revised input deck) 3.3, Pre-Code Within 20 business days Subtask Documentation (SRS, of technical direction by MS Word document COR 3.1 SDID/QTP) COR Tarball or SecureZIP Archive 3.3, PARCS/PATHS Within 25 business days Subtask Distribution of technical direction by Transmitted via e-mail, COR 3.2 COR TRACE Website or other mechanism specified by the COR 3.3, Within 20 business days MS Word Document Subtask Completion Report of completion of the COR 3.3 programming effort in Document follows Task 3.2 guidance in NUREG-1737 Tarball or SecureZIP Archive 3.3, Within 15 business days Subtask TRACE Code Update of the completion of Task Transmitted via e-mail, COR 3.4 3.2 TRACE Website or other mechanism specified by the COR Tarball or SecureZIP Archive 3.4, GenPMAXS Within 5 business days Subtask Distribution to COR after checking in the Transmitted via e-mail, COR 4.2 GenPMAXS version TRACE Website or other mechanism specified by the COR 3.5,Pre-Code Within 30 business days SubtaskDocumentation (SRS) of Subtask 5.1 MS Word document COR 5.1 for Dynamic Control commencement Rod/Detector Capability Pre-Code 3.5,Documentation Within 30 business days Subtask(SDID/QTP) for of Subtask 5.2 MS Word document COR 5.2 Dynamic Control commencement Rod/Detector Capability
 
Page 10 31310019D0002/31310021F0038
 
C.4 Monthly Report 20th of the following MS Word Document CO/COR MLSR month
 
C.6 Required Labor Categories
 
Labor Minimum Qualification Requirement Category Completion of graduate level courses in numerical methods, neutronic methods, reactor physics, and thermal-hydraulics
 
Knowledge of core nuclear analysis algorithms and application; nuclear analysis Principal methods development; numerical algorithms for the solution of systems of Engineer equations; and the numerical methods and algorithms which make up PARCS
 
Knowledge of FORTRAN, DOS, and Linux; knowledge of software engineering and software quality assurance (SQA)
 
Knowledge of using LaTeX (lualatex)/python to maintain PARCS documentation Completion of graduate level courses in numerical methods, neutronic methods, reactor physics, and thermal-hydraulics
 
Knowledge of core nuclear analysis algorithms and application; nuclear analysis methods development; numerical algorithms for the solution of systems of equations; and the numerical methods and algorithms which make up PARCS
 
Knowledge of the PARCS/PATHS source code and the GenPMAXS source code
 
Knowledge of nuclear analysis code structure, algorithms, and code compilation/build systems
 
Experience in coding with modern FORTRAN standards and in working with DOS, Engineer Linux, UNIX, and scripting languages such as Perl and Python; experience in software engineering and software quality assurance (SQA)
 
Experience with the following lattice physics packages: HELIOS, CASMO, SCALE/TRITON, SCALE/Polaris, SCALE/Shift, and Serpent


31310019D0002/31310021F0038 C.4 Monthly Report          20th of the following    MS Word Document        CO/COR MLSR                          month C.6  Required Labor Categories Labor Minimum Qualification Requirement Category Completion of graduate level courses in numerical methods, neutronic methods, reactor physics, and thermal-hydraulics Knowledge of core nuclear analysis algorithms and application; nuclear analysis methods development; numerical algorithms for the solution of systems of Principal equations; and the numerical methods and algorithms which make up PARCS Engineer Knowledge of FORTRAN, DOS, and Linux; knowledge of software engineering and software quality assurance (SQA)
Knowledge of using LaTeX (lualatex)/python to maintain PARCS documentation
Knowledge of using LaTeX (lualatex)/python to maintain PARCS documentation Completion of graduate level courses in numerical methods, neutronic methods, reactor physics, and thermal-hydraulics Knowledge of core nuclear analysis algorithms and application; nuclear analysis methods development; numerical algorithms for the solution of systems of equations; and the numerical methods and algorithms which make up PARCS Knowledge of the PARCS/PATHS source code and the GenPMAXS source code Knowledge of nuclear analysis code structure, algorithms, and code compilation/build systems Experience in coding with modern FORTRAN standards and in working with DOS, Linux, UNIX, and scripting languages such as Perl and Python; experience in Engineer software engineering and software quality assurance (SQA)
Experience with the following lattice physics packages: HELIOS, CASMO, SCALE/TRITON, SCALE/Polaris, SCALE/Shift, and Serpent Knowledge of using LaTeX (lualatex)/python to maintain PARCS documentation Experience performing quasi-steady state, fuel cycle calculations with PARCS/PATHS Experience in using PARCS/PATHS to model cores with advanced fuel forms (Accident Tolerant Fuel)
Experience in adding advanced fuel thermo-mechanical capabilities to Page 11


31310019D0002/31310021F0038 PARCS/PATHS Experience in testing GenPMAXS versions within the Perl-based regression testing harness Experience in mounting PARCS onto a version control system (such as CVS and SVN) and making changes and modifications to the version control system Experience developing and maintaining python scripts to compare PARCS/PATHS versions to measured detector power responses as part of PARCS/PATHS assessment Experience in developing/maintaining bash scripts to regression test PARCS/PATHS versions Experience in developing TRACE updates for changes to PARCS source Experience in developing input decks to test PARCS/PATHS features C.7     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 included in this contract/order.
Experience performing quasi-steady state, fuel cycle calculations with PARCS/PATHS
C.8     Section 508 - Information and Communication Technology Accessibility N/A C.9     Incremental Development for Software The Contractor shall use an incremental build model for software development. The Agency defines an incremental build model as a method of software development where the product is designed, implemented, and tested incrementally, with increasing functionality and/or capability added in each increment until the product is finished.
 
C.10 Place of Performance The work to be performed under this contract shall be primarily performed at the contractors site.
Experience in using PARCS/PATHS to model cores with advanced fuel forms (Accident Tolerant Fuel)
Page 12
 
Experience in adding advanced fuel thermo-mechanical capabilities to
 
Page 11 31310019D0002/31310021F0038
 
PARCS/PATHS
 
Experience in testing GenPMAXS versions within the Perl-based regression testing harness
 
Experience in mounting PARCS onto a version control system (such as CVS and SVN) and making changes and modifications to the version control system
 
Experience developing and maintaining python scripts to compare PARCS/PATHS versions to measured detector power responses as part of PARCS/PATHS assessment
 
Experience in developing/maintaining bash scripts to regression test PARCS/PATHS versions
 
Experience in developing TRACE updates for changes to PARCS source
 
Experience in developing input decks to test PARCS/PATHS features
 
C.7 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 included in this contract/order.
 
C.8 Section 508 - Information and Communication Technology Accessibility
 
N/A
 
C.9 Incremental Development for Software
 
The Contractor shall use an incremental build model for software development. The Agency defines an incremental build model as a method of software development where the product is designed, implemented, and tested incrementally, with increasing functionality and/or capability added in each increment until the product is finished.
 
C.10 Place of Performance
 
The work to be performed under this contract shall be primarily performed at the contractors site.
 
Page 12 31310019D0002/31310021F0038
 
C.11 Contractor Travel
 
None
 
C.12 Applicable Publications (Current Editions)


31310019D0002/31310021F0038 C.11 Contractor Travel None C.12    Applicable Publications (Current Editions)
The contractor shall comply with the following applicable regulations, publications, manuals, and local policies and procedures:
The contractor shall comply with the following applicable regulations, publications, manuals, and local policies and procedures:
* NUREG-1737: Software Quality Assurance Procedures for NRC Thermal Hydraulic Codes C.13 Security Requirements The following regulations/requirements are applicable to this task order:
* NUREG-1737: Software Quality Assurance Procedures for NRC Thermal Hydraulic Codes
 
C.13 Security Requirements
 
The following regulations/requirements are applicable to this task order:
* Management Directive 12.6 - MD 12.6 - NRC Sensitive Unclassified Information Security Program (SUNSI-Proprietary), IT Level II clearance
* Management Directive 12.6 - MD 12.6 - NRC Sensitive Unclassified Information Security Program (SUNSI-Proprietary), IT Level II clearance
* All work under this task order and all devices used to process NRC sensitive information shall comply with the National Institute of Standards and Technology (NIST), Special Publication (SP) 800-171r2, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations, and NRC guidance for the identification and documentation of minimum security controls. Upon request, the contractor shall participate with the NRC to review the contractors compliance with NIST 800-171r2 (i.e., provide requested documentation, participate in meetings, etc.).
* All work under this task order and all devices used to process NRC sensitive information shall comply with the National Institute of Standards and Technology (NIST), Special Publication (SP) 800-171r2, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations, and NRC guidance for the identification and documentation of minimum security controls. Upon request, the contractor shall participate with the NRC to review the contractors compliance with NIST 800-171r2 (i.e., provide requested documentation, participate in meetings, etc.).
* The contractor shall ensure that the software does not contain undocumented functions and undocumented methods for gaining access to the software or to the computer system on which it is installed. This includes, but is not limited to, master access keys, back doors, or trapdoors.
* The contractor shall ensure that the software does not contain undocumented functions and undocumented methods for gaining access to the software or to the computer system on which it is installed. This includes, but is not limited to, master access keys, back doors, or trapdoors.
C.14 License Fee Recoverable All the tasks listed in this SOW are NOT license fee recoverable.
C.14 License Fee Recoverable All the tasks listed in this SOW are NOT license fee recoverable.
Section F - Deliveries or Performance was revised as follows.
Section F - Deliveries or Performance was revised as follows.
Summary of Clause Changes:
Summary of Clause Changes:
Clause titled TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013) is incorporated as follows:
Clause titled TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013) is incorporated as follows:
TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013)
TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013)
This order shall commence on 09/03/2021 and will expire on 12/31/2022.
This order shall commence on 09/03/2021 and will expire on 12/31/2022.
All other terms and conditions of the task order remain the same.
All other terms and conditions of the task order remain the same.
Page 13}}
Page 13}}

Revision as of 04:00, 16 November 2024

Modification No. 004 to Task Order No. 31310021F0038 Under Contract No. 31310019D0002
ML22257A069
Person / Time
Issue date: 09/12/2022
From: Jennifer Dudek
Acquisition Management Division
To: Williams J
Information Systems Labs
References
31310019D0002, 31310021F0038
Download: ML22257A069 (13)
v • d • e


Text

31310019D0002/31310021F0038

The purpose of this task order modification is to: (1) increase the task order ceiling by

$184,299.02, from $490,130.97 to $674,429.99; (2) provide incremental funding in the amount of $127,250.19, thereby increasing the obligated amount from $490,130.97 to $617,381.16; (3) revise the price schedule; (4) revise the Statement of Work to add in Task 5 entitled, Code Documentation for Generalized Expansion of TRACE/PARCS Interface to Accommodate Dynamic Control Rod Motion and In-Core Detector Response; and (5) extend the period of performance through December 31, 2022. Accordingly, the task order is hereby modified as follows:

Section B - Supplies or Services/Prices was revised as follows.

Summary of Clause Changes:

Clause titled CONSIDERATION AND OBLIGATION-TASK ORDERS is incorporated as follows:

CONSIDERATION AND OBLIGATION-TASK ORDERS

(a) The ceiling of this order for services is $674,429.99 (Costs of and Fee of

).

(b) This order is subject to the minimum and maximum ordering requirements set forth in the contract.

(c) The amount presently obligated with respect to this order is $617,381.16 (Costs of and Fee of ). The obligated amount shall, at no time, exceed the order ceiling as specified in paragraph (a) above. When and if the amount(s) paid and payable to the Contractor hereunder shall equal the obligated amount, the Contractor shall not be obligated to continue performance of the work unless and until the Contracting Officer shall increase the amount obligated with respect to this order, in accordance with FAR Part 43 - Modifications. Any work undertaken by the Contractor in excess of the obligated amount specified above is done so at the Contractor's sole risk and may not be reimbursed by the Government.

(d) The Contractor shall comply with the provisions of FAR 52.232 Limitation of Funds, for incrementally-funded delivery orders or task orders.

Summary of Clause Changes:

Clause titled PRICE/COST SCHEDULE is incorporated as follows:

PRICE/COST SCHEDULE

CLIN Description Amount 00001Estimated Cost 00002Fixed-Fee TOTAL $674,429.99

Page 2 31310019D0002/31310021F0038

Section C - Description/Specifications was revised as follows.

Summary of Clause Changes:

Clause titled STATEMENT OF WORK is incorporated as follows:

STATEMENT OF WORK

PARCS Code Suite Maintenance, Development, and User Support

Contents

C.1 Background C.2 Objective C.3 Scope of Work C.4 Reporting Requirements - Monthly Letter Status Report (MLSR)

C.5 Deliverables and Delivery Schedule C.6 Required Labor Categories C.7 Data Rights C.8 Section 508 - Information and Communication Technology Accessibility C.9 Incremental Development for Software C.10 Place of Performance C.11 Contractor Travel C.12 Applicable Publications (Current Editions)

C.13 Security Requirements C.14 License Fee Recoverable

C.1 Background

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

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 TRAC/RELAP Advanced Computational Engine (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 code which is used for converting macroscopic cross-sections generated by lattice physics codes like SCALE/TRITON, SCALE/Polaris, CASMO, or HELIOS into a form readable by PARCS, along with a generalized capability to construct a cross section case matrix with

Page 3 31310019D0002/31310021F0038

consideration for nodal burnup history effects and nodal state parameterizations.

The PARCS code supports independent regulatory decision making in that it allows staff and contractors to develop core physics models to confirm that core behavior is within safety limits for general steady-state operation and for a range of plant transients. PARCS is specifically used as a tool in confirmatory safety reviews of power plant operator actions, core designs, power uprates, and license amendments. This is done for both design certifications and License Amendment Requests (LARs).

For the context of this work, and when not directly coupled to TRACE or RELAP, PARCS is maintained in a larger, standalone form for quasi-steady-state fuel cycle analysis, with consideration for fuel shuffle schemes over multiple fuel cycles. In standalone form, PARCS also maintains a basic T/H-to-neutronic feedback capability through its coupling with the PATHS (BWRs/PWRs) code, along with an even simpler mass-energy based T/H solver that is specific to PWRs. When maintained in this standalone configuration, PARCS has its own version control system, regression test suite, and set of assessments problems. GenPMAXS is also maintained in its own version control system with a test suite segmented by all of the lattice physics codes that it supports. There is also a corresponding Perl-based regression harness that is used to test and interrogate the conversion of SCALE/TRITON cross sections from t16 format to PMAXS format in a systematic and visual manner.

C.2 Objective

The objective of this acquisition is to obtain regulatory technical support with the maintenance, code support, assessment, development, and user training of the PARCS and GenPMAXS codes and the interface of PARCS with SNAP. The contractor shall provide the necessary personnel, management, materials, equipment, administrative and technical services as outlined in this Statement of Work.

C.3 Scope of Work

The contractor shall provide the following services for the PARCS code suite: configuration control, the correction of code errors, documentation updates, the development of test problems, and user support to the NRC, its contractors, and members of CAMP and the domestic user community.

PARCS and GenPMAXS code changes shall be tested on a variety of compiler/operating system combinations. The following compilers shall be used during maintenance and development of both of the PARCS and GenPMAXS source codes:

Windows (Microsoft Visual Studio/Intel Visual Fortran)

Linux (gfortran, Intel, NAG, Portland Group)

The contractor shall ensure that the above compilers and platforms are in place for the entire period of performance, and that these compilers are maintained at their most current release levels throughout the contract. The Contracting Officers Representative (COR) may require the contractor to extend support to other compiler/operating system combinations that are not listed as a result of changing priorities.

Page 4 31310019D0002/31310021F0038

SPECIFIC SUBTASKS:

3.1: Task 1 - PARCS/PATHS Code Maintenance

Subtask 1.1: Identify Code Bugs

The contractor shall identify all code bugs and maintain them in a bug report document which, at a high level, summarizes code errors received from all PARCS/PATHS users (bugs, unexplained behavior, and documentation problems). This document shall include the following information for each bug: a summary description of the bug; the date the bug was reported; the user or organization who reported the bug; and the status of the bug (i.e. in what code version the bug was discovered).

Subtask 1.2: Perform Code Fixes

Under COR technical direction, the contractor shall make changes to the collective PARCS/PATHS source code in response to bugs reported by the COR and all other PARCS/PATHS users, as captured in the bug report under Subtask 1.1.

Upon COR direction, the contractor shall also update the LaTeX(lua)/python-based code documentation (PARCS Input, Theory, User Guide, and MAPTAB manuals and PATHS Input and Theory manuals) as the result of the correction of typos, the elimination of features that are no longer supported in the code, or the desire of users to make the documentation more clear and relevant, which may be included in the bug report.

Any PARCS/PATHS source code changes made as a result of code bugs shall be tested against the PARCS regression test suite before being checked into the code version control system. New test problems that are added to the PARCS or GenPMAXS test suites as a result of the correction of code bugs shall be documented in the HyperText Markup Language (HTML) summary file. The contractor shall modify the run scripts for the test suite as a result of any test problem additions, changes, or deletions, and shall modify the build scripts as a result of any additions, changes, or deletions to the source code.

The contractor shall create new versions of PARCS in response to code bug corrections. These different code versions shall be maintained using a version control system methodology, and this methodology shall have the ability to retrieve previously released code versions. Each retrieved code version shall contain enough information such that it can be a self-contained distribution (an archive).

Subtask 1.3: Prepare TRACE Updates

At a frequency determined by the COR, the contractor shall prepare a TRACE update for submittal to the TRACE website. This update shall include the revised PARCS source code (and the revised TRACE source code, if necessary), a list of the differences between code versions embedded in text files, new test problems formulated to test the code update, revised code documentation, and the results of automated testing against the TRACE regression suite.

3.2: Task 2 - PARCS/PATHS Code Support

As directed by the COR, the contractor shall provide analysis and consultation support related

Page 5 31310019D0002/31310021F0038

to PARCS/PATHS and GenPMAXS. This support shall include, but is not limited to: guidance on PARCS use, GenPMAXS, explanations of the algorithms that are coded into PARCS/PATHS, develop PARCS/PATHS models or GenPMAXS models, interpret results, or explain underlying physics phenomena or algorithms, explanations of the input format, or guidance on best-practices (how to approach a problem), the interpretation of any associated lattice physics models or PMAXS cross section libraries that are affiliated with the core model, performing pre-analysis scoping studies, and responding to code user questions and comments provided to the contractor by the COR. Analysis and consultation support may require the preparation of summaries, emails, or revised input decks, as well as participation in NRC meetings.

3.3: Task 3 - PARCS/PATHS Code Development

Upon COR direction and prioritization, the contractor shall perform any PARCS/PATHS source code development that may be necessary as a result of user feedback, future RES program needs, regulatory user needs, and CAMP needs. This code development shall not be limited to code fixes, but shall be broadly applied to significant code changes that support user convenience (e.g., improved error checking and advanced editing options), code robustness and speed (e.g., linear solver upgrades and changes and advanced neutronic methods),

significant modeling enhancements, or utility codes or scripts that support PARCS/PATHS code use.

Any PARCS/PATHS source code changes made as a result of code enhancements or modeling changes shall be tested against the PARCS regression test suite before being checked-in to the code version control system. The contractor shall modify the run scripts for the test suite as a result of any test problem additions, changes, or deletions, and shall modify the build scripts as a result of any additions, changes, or deletions to the source code. The contractor shall revise the LaTeX(lua)/python-based code documentation (PARCS Input, Theory, User Guide, and MAPTAB manuals and PATHS Input and Theory manuals), to reflect the code development activity.

Subtask 3.1: Pre-Code Documentation Requirements

For each code development activity, the contractor shall develop the following documentation, per the guidance specified in NUREG-1737:

Software Requirements Specification (SRS)

The SRS is a technical document that focuses on the underlying algorithms, technical specifications, and requirements of the software.

Software Design and Implementation Document (SDID)/Qualification Test Plan (QTP) (referred to as the test plan in NUREG-1737)

The SDID/QTP is a combined document that describes the implementation of the technical specifications and algorithms outlined in the SRS, i.e., how the software will be structured and designed, and also describes how the implemented capabilities are proposed to be tested, i.e.

the test problems which will be used to demonstrate the new capability.

Subtask 3.2: Perform Code Development

Page 6 31310019D0002/31310021F0038

The contractor shall implement code development features into the PARCS code distribution (i.e., source code, build scripts, test problems, and code documentation (as applicable), etc.) as directed by the COR.

Subtask 3.3: Prepare Completion Report

The contractor shall prepare a Completion Report (CR) that documents the programming effort.

Specifically, the report shall summarize the methodology, software, and user changes, and shall include calculation results that demonstrate the changed coding.

Subtask 3.4: Prepare TRACE Updates

A matching TRACE update (that envelopes the PARCS code changes completed in Subtasks 3.1 through 3.3) shall be prepared by the contractor for submittal to the TRACE website. This update shall include the new PARCS source code (and new TRACE source code, if necessary),

the differences between code versions embedded in text files, new test problems formulated to test the code update, code documentation, and the results of automated testing against the TRACE regression suite.

3.4: Task 4 - GenPMAXS Code Support and Maintenance

The contractor shall provide technical support and code maintenance for GenPMAXS to assure the consistency and accuracy of the cross section data that feeds PARCS.

Subtask 4.1: Maintain GenPMAXS in a Version Control System

The contractor shall maintain GenPMAXS in a version control system, each version being retrievable as a self-contained unit. Along with each version the contractor shall store the build system (MSVS workspaces, Linux and windows make files, and source), the test suite (test problems and run scripts), and the code documentation. The GenPMAXS code documentation shall include a manual describing the use and methodology behind GenPMAXS, as well as a document describing known issues.

Subtask 4.2: Correct GenPMAXS Bugs

The contractor shall correct bugs resulting from the use of GenPMAXS for reading in cross section data supplied by the lattice physics codes. Any new test problems that are added to the GenPMAXS test suite as a result of the correction of code bugs shall be documented in the GenPMAXS manual.

3.5: Task 5 - Code Documentation for Generalized Expansion of TRACE/PARCS Interface to Accommodate Dynamic Control Rod Motion and In-Core Detector Response

Part A

The contractor shall draft software planning documents (SRS and SDID/QTP) that plan the development and implementation of the capability for TRACE to manipulate PARCS control rod bank positions in response to nuclear power plant signals. During operational transients, these

Page 7

31310019D0002/31310021F0038

(QTP)

For this code development activity, the contractor shall develop an SDID and a Qualification Test Plan, per the guidance specified in NUREG-1737.

The SDID/QTP is a combined document that describes the implementation of the technical specifications and algorithms outlined in the SRS, and also describes how the implemented capabilities will be tested. For this task, the SDID shall describe any planned changes to inputs (if any) in the form of additional fields, cards, and blocks in TRACE and PARCS (and GenPMAXS, if any). The QTP shall propose model test problems to demonstrate the functionality of the implementations.

There should be at least one BWR model proposed to test the capabilities described in Part B (interaction of PARCS detector signals with the TRACE control system), and at least one other LWR model proposed to test the capabilities described in Part A (TRACE control of PARCS control rod movement).

C.4 Reporting Requirements - Monthly Letter Status Report (MLSR)

The contractor shall provide a Monthly Letter Status Report which consists of a technical progress report and financial status report. This report will be used by the Government to assess the adequacy of the resources proposed by the contractor to accomplish the work contained in this SOW and provide status of contractor progress in achieving activities and producing deliverables. The report shall include order summary information, work completed during the specified period, milestone schedule information, problem resolution, travel plans, and staff hour summary.

C.5 Deliverables and Delivery Schedule

The Contractor shall correct errors in contractor developed software and applicable documentation that are not commercial off-the-shelf which are discovered by the NRC or the contractor. Inability of the parties to determine the cause of software errors shall be resolved in accordance with the Disputes clause in Section I, FAR 52.233-1, incorporated by reference in the base contract.

Section Deliverable Due Date Format Submit

  1. to 3.1, 20th of the following Subtask Bug Report month MS Word Document COR 1.1 Tarball or SecureZIP Within 5 business days of Archive 3.1, PARCS/PATHS Code the completion of code Subtask Distribution checked-in PARCS code Transmitted via e-mail, COR 1.2 version TRACE Website or other mechanism specified by the COR

Page 9 31310019D0002/31310021F0038

Tarball or SecureZIP Archive 3.1, TRACE Update Within 15 business days Subtask Distribution of COR request Transmitted via e-mail, COR 1.3 TRACE Website or other mechanism specified by the COR Documentation follows 3.2Code Support Within 10 business days guidance from COR (email COR Documentation of the COR request or MS Word document or revised input deck) 3.3, Pre-Code Within 20 business days Subtask Documentation (SRS, of technical direction by MS Word document COR 3.1 SDID/QTP) COR Tarball or SecureZIP Archive 3.3, PARCS/PATHS Within 25 business days Subtask Distribution of technical direction by Transmitted via e-mail, COR 3.2 COR TRACE Website or other mechanism specified by the COR 3.3, Within 20 business days MS Word Document Subtask Completion Report of completion of the COR 3.3 programming effort in Document follows Task 3.2 guidance in NUREG-1737 Tarball or SecureZIP Archive 3.3, Within 15 business days Subtask TRACE Code Update of the completion of Task Transmitted via e-mail, COR 3.4 3.2 TRACE Website or other mechanism specified by the COR Tarball or SecureZIP Archive 3.4, GenPMAXS Within 5 business days Subtask Distribution to COR after checking in the Transmitted via e-mail, COR 4.2 GenPMAXS version TRACE Website or other mechanism specified by the COR 3.5,Pre-Code Within 30 business days SubtaskDocumentation (SRS) of Subtask 5.1 MS Word document COR 5.1 for Dynamic Control commencement Rod/Detector Capability Pre-Code 3.5,Documentation Within 30 business days Subtask(SDID/QTP) for of Subtask 5.2 MS Word document COR 5.2 Dynamic Control commencement Rod/Detector Capability

Page 10 31310019D0002/31310021F0038

C.4 Monthly Report 20th of the following MS Word Document CO/COR MLSR month

C.6 Required Labor Categories

Labor Minimum Qualification Requirement Category Completion of graduate level courses in numerical methods, neutronic methods, reactor physics, and thermal-hydraulics

Knowledge of core nuclear analysis algorithms and application; nuclear analysis Principal methods development; numerical algorithms for the solution of systems of Engineer equations; and the numerical methods and algorithms which make up PARCS

Knowledge of FORTRAN, DOS, and Linux; knowledge of software engineering and software quality assurance (SQA)

Knowledge of using LaTeX (lualatex)/python to maintain PARCS documentation Completion of graduate level courses in numerical methods, neutronic methods, reactor physics, and thermal-hydraulics

Knowledge of core nuclear analysis algorithms and application; nuclear analysis methods development; numerical algorithms for the solution of systems of equations; and the numerical methods and algorithms which make up PARCS

Knowledge of the PARCS/PATHS source code and the GenPMAXS source code

Knowledge of nuclear analysis code structure, algorithms, and code compilation/build systems

Experience in coding with modern FORTRAN standards and in working with DOS, Engineer Linux, UNIX, and scripting languages such as Perl and Python; experience in software engineering and software quality assurance (SQA)

Experience with the following lattice physics packages: HELIOS, CASMO, SCALE/TRITON, SCALE/Polaris, SCALE/Shift, and Serpent

Knowledge of using LaTeX (lualatex)/python to maintain PARCS documentation

Experience performing quasi-steady state, fuel cycle calculations with PARCS/PATHS

Experience in using PARCS/PATHS to model cores with advanced fuel forms (Accident Tolerant Fuel)

Experience in adding advanced fuel thermo-mechanical capabilities to

Page 11 31310019D0002/31310021F0038

PARCS/PATHS

Experience in testing GenPMAXS versions within the Perl-based regression testing harness

Experience in mounting PARCS onto a version control system (such as CVS and SVN) and making changes and modifications to the version control system

Experience developing and maintaining python scripts to compare PARCS/PATHS versions to measured detector power responses as part of PARCS/PATHS assessment

Experience in developing/maintaining bash scripts to regression test PARCS/PATHS versions

Experience in developing TRACE updates for changes to PARCS source

Experience in developing input decks to test PARCS/PATHS features

C.7 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 included in this contract/order.

C.8 Section 508 - Information and Communication Technology Accessibility

N/A

C.9 Incremental Development for Software

The Contractor shall use an incremental build model for software development. The Agency defines an incremental build model as a method of software development where the product is designed, implemented, and tested incrementally, with increasing functionality and/or capability added in each increment until the product is finished.

C.10 Place of Performance

The work to be performed under this contract shall be primarily performed at the contractors site.

Page 12 31310019D0002/31310021F0038

C.11 Contractor Travel

None

C.12 Applicable Publications (Current Editions)

The contractor shall comply with the following applicable regulations, publications, manuals, and local policies and procedures:

  • NUREG-1737: Software Quality Assurance Procedures for NRC Thermal Hydraulic Codes

C.13 Security Requirements

The following regulations/requirements are applicable to this task order:

  • All work under this task order and all devices used to process NRC sensitive information shall comply with the National Institute of Standards and Technology (NIST), Special Publication (SP) 800-171r2, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations, and NRC guidance for the identification and documentation of minimum security controls. Upon request, the contractor shall participate with the NRC to review the contractors compliance with NIST 800-171r2 (i.e., provide requested documentation, participate in meetings, etc.).
  • The contractor shall ensure that the software does not contain undocumented functions and undocumented methods for gaining access to the software or to the computer system on which it is installed. This includes, but is not limited to, master access keys, back doors, or trapdoors.

C.14 License Fee Recoverable All the tasks listed in this SOW are NOT license fee recoverable.

Section F - Deliveries or Performance was revised as follows.

Summary of Clause Changes:

Clause titled TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013) is incorporated as follows:

TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013)

This order shall commence on 09/03/2021 and will expire on 12/31/2022.

All other terms and conditions of the task order remain the same.

Page 13

Retrieved from "https://kanterella.com/w/index.php?title=ML22257A069&oldid=3721297"