ML24257A187
| ML24257A187 | |
| Person / Time | |
|---|---|
| Issue date: | 09/11/2024 |
| From: | Rasmey Robinson Acquisition Management Division |
| To: | Maldonado P Southwest Research Institute |
| References | |
| 31310023D0005 | |
| Download: ML24257A187 (1) | |
Text
DATE OF ORDER 3
ORDER FOR SUPPLIES OR SERVICES SCHEDULE - CONTINUATION CONTRACT NO.
AMOUNT UNIT PRICE UNIT QUANTITY ORDERED SUPPLIES/SERVICES ITEM NO.
IMPORTANT: Mark all packages and papers with contract and/or order numbers.
ORDER NO.
QUANTITY ACCEPTED 09/11/2024 31310024F0136 PAGE NO (a)
(b)
(c)
(d)
(e)
(f)
(g) 31310023D0005 Period of Performance: 09/16/2024 to 03/29/2025 Prescribed by GSA FAR (48 CFR) 53.213(f)
OPTIONAL FORM 348 (Rev. 4/2006)
AUTHORIZED FOR LOCAL REPODUCTION PREVIOUS EDITION NOT USABLE TOTAL CARRIED FORWARD TO 1ST PAGE (ITEM 17(H))
$0.00
31310023D0005/31310024F0136 Page 4 B - Supplies or Services/Prices.....................................................................................................5 B.1 BRIEF PROJECT TITLE AND WORK DESCRIPTION (AUG 2011)..................................5 B.2 CONSIDERATION AND OBLIGATIONCOST-PLUS-FIXED-FEE ALTERNATE I (AUG 2023).........................................................................................................................................5 B.3 PRICE/COST SCHEDULE..................................................................................................6 C - Description/Specifications.......................................................................................................7 C.1 STATEMENT OF WORK....................................................................................................7 D - Packaging and Marking.........................................................................................................20 D.1 PACKAGING AND MARKING..........................................................................................20 D.2 BRANDING.......................................................................................................................20 E - Inspection and Acceptance....................................................................................................21 E.1 INSPECTION AND ACCEPTANCE BY THE NRC (SEP 2013)........................................21 F - Deliveries or Performance.....................................................................................................22 F.1 PLACE OF DELIVERY-REPORTS...................................................................................22 F.2 TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013)...........................22 H - Special Contract Requirements.............................................................................................23 H.1 ANNUAL AND FINAL CONTRACTOR PERFORMANCE EVALUATIONS (AUG 2023)..23 H.2 2052.215-70 KEY PERSONNEL. (JAN 1993)..................................................................23 H.3 2052.215-71 CONTRACTING OFFICER REPRESENTATIVE AUTHORITY. (OCT 1999)
.................................................................................................................................................24 I - Contract Clauses.....................................................................................................................27 I.1 2052.209-72 CONTRACTOR ORGANIZATIONAL CONFLICTS OF INTEREST. (JAN 1993).......................................................................................................................................27 I.2 52.217-7 OPTION FOR INCREASED QUANTITY - SEPARATELY PRICED LINE ITEM.
(MAR 1989).............................................................................................................................30 I.3 52.217-8 OPTION TO EXTEND SERVICES. (NOV 1999).................................................30
31310023D0005/31310024F0136 Page 6 B.3 PRICE/COST SCHEDULE Total Estimated Cost and Fixed-Fee Breakdown by CLIN is presented below.
TOTAL$317,388
31310023D0005/31310024F0136 Page 7 C - Description/Specifications C.1 STATEMENT OF WORK
- 1. PROJECT TITLE MELCOR Consequence Analyses Code System (MACCS) Code Assessment: Testing, Benchmarking, Verification, Validation, and Confirmatory Analyses
- 2. BACKGROUND The U.S. Nuclear Regulatory Commission (NRC), Office of Nuclear Regulatory Research, Division of System Analysis, Accident Analysis Branch (RES/DSA/AAB) plans, develops, and manages analytical and experimental research projects on the progression, response, and offsite consequences of postulated severe accidents; and performs safety analyses of nuclear power plant systems. This work includes safety and security analyses, including postulated severe accident analyses of accident progression in reactor vessel, containment, and postulated accidents from spent fuel storage and transportation. State-of-the-art analytical techniques are used to develop realistic best estimates of the potential effects (consequences) to the public of low-likelihood nuclear power plant and spent fuel storage and transportation accidents which could release radioactive material into the environment. AAB models accident progression in order to estimate the magnitude and timing of radioactive release into the environment to estimate site-specific consequences (e.g. health effects). The experimental research projects support NRC's knowledge and understanding of severe accidents, and they support NRC's models with experimental data. AAB provides consultation to other NRC offices regarding safety or licensing decisions, development of guidance, or other regulatory needs, and partners with the U.S. Department of Energy (DOE), universities, laboratories, and other national and international research centers. AAB also manages the Agency long-term research program and research for advanced reactor designs.
To accomplish regulatory research tasks, AAB use various computer codes including MELCOR Consequence Analyses Code System (MACCS). MACCS suite of computer codes is used to evaluate the impacts of atmospheric releases of radioactive aerosols and vapors on human health and the environment. MACCS model include radionuclide release, atmospheric transport and dispersion, site data, weather data, emergency response and protective actions, exposure pathways, health effects, and offsite costs.
- 3. OBJECTIVE The main objective of this task order is to document a user oriented MACCS, and associated pre-processors such as MEL-MACCS, SECPOP, or COMIDA, assessment using test cases and perform confirmatory analyses. This work includes reviewing the existing test cases and improving the reviewed test cases, if required, and developing new test cases.
This task order also includes optional work of providing technical support in the area of emerging work related to reviewing reports or documents in the areas of MACCS codes including benchmarking and confirmatory analysis using MACCS code where needed.
- 4. SCOPE OF WORK
31310023D0005/31310024F0136 Page 8 The scope of this task order involves researching areas related to MACCS consequence analyses, performing tests, and documenting analyses. Deliverables of this task order include draft reports, review and approval of draft reports by the Contracting Officers Representative (COR), and compilations of draft reports into final reports.
The Contractor shall perform the following tasks:
Task 1: Kick-off Meeting The Contractor shall participate in a virtual kick-off meeting via Microsoft Teams with the COR and other NRC technical staff to discuss the task order performance expectations. The kick-off meeting shall be held within 10 business days after task order award or as directed by COR to accommodate participants schedule.
The Contractor shall prepare a written summary of the meeting that includes, at a minimum, the following information: (1) identification of meeting participants from the NRC and Contractor, (2) minutes of the meeting that clearly describe the substance of the meeting, and (3) any action items and decisions from the meeting.
Task 2: Developing MACCS Cases of Analyses.
The Contractor shall review existing test cases for adequacy, perform state of practice literature review related to MACCS consequence analyses areas as needed to verify information supported by old documentation. When prior tests have not been documented properly, the Contractor shall perform MACCS Code assessment, verification, and validation testing. This can be accomplished by the contractor updating or enhancing these test cases as needed or developing new test cases and comparing MACCS output results with data obtained from various methods, such as:
(1) Analytic results using calculators or software like spreadsheets, and engineering equation solvers etc.
(2) Results of other comparable proven computer programs (3) Empirical data and information from real-life events published in technical literature.
The Contractor shall develop a draft report containing test plans and test cases. The draft report shall be reviewed and approved by the COR before the execution of the test cases. The Contractor shall propose in the test plan, which of the above 3 methods will be used in verification and validation testing. The Contractor shall develop additional test cases if existing test cases are insufficient to adequately cover the software functional requirements as described in theory and users manuals. The Contractor shall seek approval from the COR if additional cases, are needed, prior to developing the final input deck and making MACCS runs to generate output. If additional test cases are needed, the Contractor shall develop additional tests using the latest released version of MACCS or a version as confirmed by the COR. Prior to starting work on the test plan for the additional tests, the Contractor shall develop descriptions of test cases and schedule for additional tests and document this information in the draft report.
This information shall be presented and discussed at a meeting with the COR.
31310023D0005/31310024F0136 Page 9 The Contractor shall document the results of verification of a test case in a formal Verification Report in accordance with written technical direction provided by the COR. The verification method applied to the computer program results shall be shown to produce correct solutions for the applied mathematical model within defined limits for each parameter employed by the verifier. The applied mathematical model shall be shown to produce a valid solution to the physical problem associated with the application, by the verifier.
(a) The test plans shall specify the following, as applicable and agreed upon with the COR:
(1) planned testing activities and progression (2) identification of the stages at which testing is required (3) requirements for testing logic branches (4) requirements for hardware and system integration (5) requirements for input simulation (6) criteria for accepting the software (7) reports, records, standard formatting, and conventions (b) The test cases shall specify the following, as applicable and agreed upon with the COR:
(1) prerequisites for performing the test case (2) steps to be performed including the steps to restore the system or data to its original before to the test case (3) required ranges of input parameters (4) expected results (5) acceptance criteria for the test case (6) reports, records, standard formatting, and conventions The test problems may check figures of merits often used in NRC licensing and regulatory activities such as:
- Early Fatalities
- Latent Cancers Fatalities
- Dose and Dose rates
- Impact of shielding factor for protective actions/evacuation modeling.
- Long term contamination, economic consequences, and cost models When applicable the Contractor shall compare the results of the recently completed draft Level 3 PRA project to support code assessment.
31310023D0005/31310024F0136 Page 10 The Contractor shall continue to leverage the work already done by the Contractor in food chain modeling that was started under Task Order No. 31310020F0081 under 31310018D0002. The Contractor shall identify important parameters in the COMIDA2 model, recommend continued use of the current parameters or recommend new values, and evaluate and recommend new model development for MACCS / COMIDA2. The evaluation may consider FDA Protective Actions Guidelines (PAG), ingestions annual thresholds as compared to lifetime ingestion dose, ingestions dose start time, individual versus collective dose modeling in MACCS, and ingestion pathways. The Contractor shall include in the draft report the technical bases for ingestion input parameters, identify modeling limitations, and document modeling recommendations and guidance for MACCS users on appropriately handling uncertainty.
Another area of work may involve analyzing initial inventories and release fractions of radionuclides due to severe failures or accidents and evaluating associated consequences. This may or may not require running MACCS code because these items are related to the pre-processing and development of MACCS input files. Such cases may require an independent technical report rather than being part of a test report in accordance with written technical direction provided by the COR. This work is related to advance reactor design considered for licensing in the near future. This work will be documented in a report.
Additionally, certain MACCS-related post-processing work may involve improving the presentation of results using advanced graphics and updating complex figures in guidance documents. The work may also support rule making activities related to regulatory analyses, cost benefit analyses, and rulemaking. This work shall be documented in a report.
The Contractor may suggest additional areas of benchmarking, testing, and confirmatory analyses not listed above to the COR.
The Contractor shall ensure that all electronic content delivered under this task conforms to the accessibility requirements in Section 7 of this Statement of Work (SOW).
Task 3: Reporting Results and Continue with New Test Cases The Contract shall prepare a draft report that document each test case and associated code assessment and evaluation of results. The report shall be written for MACCS users, who are technical staff with diverse science and engineering background. When testing and analysis is performed to support MACCS formal verification, the Contractor shall document results in a Verification Report in accordance with 10 CFR Part 50. The report is expected to become a living document to be periodically updated and maintained as new test cases are identified to support MACCS maintenance, version upgrades, and users needs for new applications.
Observations of unexpected or unintended results shall be documented and dispositioned before the test result final approval by the COR. Test results shall be reviewed to ensure that test requirements have been satisfied.
The test section of the report shall include:
(1) computer program tested including system software used
31310023D0005/31310024F0136 Page 11 (2) computer hardware used (3) test equipment and calibrations, where applicable (4) date of test performed (5) name of the tester or data recorder (6) simulation models used, where applicable (7) test problems and traceability to requirements (8) results (9) action to be taken in connection with any deviations noted (10) name of the person evaluating test results (11) acceptability Computer program test reports shall be controlled and maintained as records of software documentation and turned over to NRC. Test records shall be established and maintained to indicate that the computer program adequately and correctly implemented the approved software requirements.
The Contractor shall prepare two separate final reports to include a Revision to the Verification Report prepared under 31310020F0081 under 31310018D0002 and a Technical Report after all testing and analysis has been performed under the task order. The contractor shall prepare a final draft Revised Verification and Technical Report The contractor shall prepare a final Verification and Technical Report that address NRC Comments.
The Contractor shall ensure that all electronic content delivered under this task conforms to the accessibility requirements in Section 7 of this SOW.
Task 4: Additional Benchmarking, Testing, Technical Assessment, & Review (OPTION)
The NRC may require additional support related to MACCS for benchmarking, testing, technical assessment, and review of MACCS related documents as needed to support, rulemaking, licensing, and regulatory research and analyses. This includes testing MACCS for new reactors application, reviewing MACCS related licensing or regulatory analyses reports and documents, or resolving issues identified by NRC staff or intervener, in accordance with written technical direction provided by the COR, related to MACCS areas of analyses. Also, the discrepancies identified in the draft report under Task 3 are expected to be resolved in the new release of MACCS (Version 4.X or 5.X). The Contractor shall update the results of the draft report completed in Task 3 using the new version of the MACCS code and issue MACCS Code Assessment Report (Verification Report) for public and the MACCS users, upon approval from the COR. This includes repeating all tests of the current MACCS Verification Report for MACCS Version 4.0 (assuming previous inputs file can be efficiently re-used), discussing results of retesting with NRC staff, initiating a revision of the MACCS Verification Report to apply to the
31310023D0005/31310024F0136 Page 12 newest MACCS version. Final deliverables of this option may include a Verification Report and Technical Report depending on the required support, similar to Task 3.
The Contractor shall ensure that all electronic content delivered under this task conforms to the accessibility requirements in Section 7 of this SOW.
- 5. REPORTING REQUIREMENTS Monthly Letter Status Report (MLSR)
The contractor shall provide a Monthly Letter Status Report (MLSR). If no work was performed during the prior month, the contractor shall not prepare and submit an MLSR. The MLSR shall be provided electronically to the COR and the Contracting Officer (CO) by the 20th calendar day of the following month.
The technical progress report and financial status report must clearly distinguish work associated with Advanced Reactors versus all other work performed under the task order.
- 6. DELIVERABLES AND DELIVERY SCHEDULE Deliverables of this task order include draft reports and compilations of draft reports into final reports. Electronic input output data for MACCS runs shall be delivered as secured electronics media transfer such as, official box or approved secured media via registered mail.
A summary of the deliverables and anticipated delivery schedule is shown in the table below.
Deliverable Format Due Date Kickoff Meeting Summary MS Word One week after the kickoff meeting Draft Report containing Initial Test Plans and Test Cases MS Word Oct 10, 2024 Draft Formal Verification Report MS Word Oct 30, 2024 Draft Report with COMIDA Analyses MS Word Nov 30, 2024 Draft Report with Advanced Reactor MS Word Dec 30, 2024 Draft Report with Regulatory Analyses MS Word Jan 30, 2025 Final Draft Technical Report (Final collection of draft report)
MS Word Feb 15, 2025 Final Draft Revised MS Word Feb 15, 2025
31310023D0005/31310024F0136 Page 13 Verification Report Final Technical Report (Final collection of draft report)
MS Word and Adobe PDF March 30, 2025 Final Technical Report (Final collection of draft report)
MS Word and Adobe PDF March 30, 2025 Optional Task Reports Draft Reports Final Report(s) (Revised Verification Report and Technical Report)
MS Word and Adobe PDF Electronics Media TBD upon exercise of Option Monthly Letter Status Report MS Word or Adobe PDF No later than the 20thof the following month The deliverables shall be submitted electronically to the COR.
- 7. SECTION 508 - INFOMRATION AND COMMUNICATION TECHNOLOGY ACCESSIBLITY 7.1 Introduction In December 2000, the Architectural and Transportation Barriers Compliance Board (Access Board) pursuant to Section 508(2)(A) of the Rehabilitation Act Amendments of 1998, established electronic and information technology (EIT) accessibility standards for the federal government.
The Standards for Section 508 of the Rehabilitation Act (codified at 36 CFR § 1194) were revised by the Access Board, published on January 18, 2017 and minor corrections were made on January 22, 2018, effective March 23, 2018.
The revised 508 standards have replaced the term EIT with ICT (Information and Communication Technology). ICT is information technology (as defined in 40 U.S.C. 11101(6))
and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include, but are not limited to:
Computers and peripheral equipment; information kiosks and transaction machines; telecommunications equipment; customer premises equipment; multifunction office machines; software; applications; Web sites; videos; and, electronic content.
The text of the Standards for Section 508 of the Rehabilitation Act can be found in 36 CFR § 1194.1 and in Appendices A, C and D to Part 1194 (https://www.ecfr.gov/current/title-36/chapter-XI/part-1194?toc=1).
7.2 General Requirements To help the NRC comply with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. § 794d) (Section 508), the Contractor shall ensure that its deliverables (both products and services) within the scope of this contract/order are
31310023D0005/31310024F0136 Page 14
- 1. in conformance with, and
- 2. support the requirements of the Standards for Section 508 of the Rehabilitation Act, as set forth in 36 CFR § 1194.1 and in Appendices A, C and D to Part 1194.
The Standards for Section 508 of the Rehabilitation Act reference the Web Content Accessibility Guidelines (WCAG) version 2.0, Level A and Level AA Success Criteria and Conformance Requirements. However, it is desirable that the contractor support the latest WCAG version (currently 2.2), when possible.
7.3. Applicable Provisions of the Standards for Section 508 of the Rehabilitation Act The following is an outline of the standards that identifies what provisions are always applicable and which ones may be applicable.
Applicable to the Contract/Order?
Provision of 36 CFR Part 1194 Yes 1)Revised 508 Standards Yes a)Appendix A to Part 1194 - Section 508 of the Rehabilitation Act: Application and Scoping Requirements Yes i)508 Chapter 1: Application and Administration-sets forth general application and administration provisions Yes ii)508 Chapter 2: Scoping Requirements - containing scoping requirements (which, in turn, prescribe which ICT - and, in some cases, how many - must comply with the technical specifications)
Yes (see the Exceptions to the Standards section below)
(1)E202 General Exceptions No (2)E203.2 User Needs Yes (see the Accessibility of Electronic Content section below)
(3)E205 Electronic Content See below b)Appendix C to Part 1194 - Functional Performance Criteria and Technical Requirements Yes i)Chapter 3: Functional Performance Criteria-applies to ICT where required by 508 Chapter 2 (Scoping Requirements) and where otherwise referenced in any other chapter of the Revised 508 Standards No ii)Chapter 4: Hardware No iii)Chapter 5: Software No iv)Chapter 6: Support Documentation and Services (applicable to, but not limited to, help desks, call centers, training services, and automated self-service technical support)
Yes v)Chapter 7: Referenced Standards - the standards referenced here apply to ICT where required by Section 508 Chapter 2 (Scoping Requirements) and where referenced in any other chapter of the Revised 508 Standards
31310023D0005/31310024F0136 Page 15 No 2)Appendix D to Part 1194 - Electronic and Information Technology Accessibility Standards as Originally Published on December 21, 2000 Refer to 508 Chapter 2 (Scoping Requirements) first to confirm what provisions in Appendix C apply in a particular case.
7.4. Exceptions to the Standards 7.4.1. Legacy ICT N/A 7.4.2. National Security Systems Based on the definition at 40 U.S.C. 11103(a), the National Security Systems general exception (section E202.3 of 36 CFR § 1194) is not applicable to this contract/order.
7.4.3 Incidental ICT ICT acquired by the Contractor incidental to this contract/order shall not be required to conform to the revised 508 standards.
Note: This only applies when the Contractor is procuring the ICT, only the Contractor personnel will access or use the ICT, and ownership of the ICT will remain with the Contractor upon completion of the contract/order.
7.4.4 ICT Functions Located in Maintenance or Monitoring Spaces The Contractor shall confirm with the COR that an ICT deliverable of this contract/order will be located in maintenance or monitoring spaces before assuming that the ICT Functions Located in Maintenance or Monitoring Spaces general exception (section E202.5 of 36 CFR § 1194) applies.
Note that this exception does not apply to features of the ICT (such as Web interfaces) that can be accessed remotely, outside the maintenance or monitoring space where the ICT is located.
7.4.5 Undue Burden The Undue Burden general exception (section E202.6 of 36 CFR § 1194) is not expected to be applicable to work performed by the Contractor. If there are questions about potential application of this exception please discuss with the CO.
7.4.6 Fundamental Alteration or Best Meets If the Contractor wishes to use the Fundamental Alteration (section E202.6 of 36 CFR § 1194) or Best Meets (section E202.7 of 36 CFR § 1194) general exceptions the Contractor shall do the following:
31310023D0005/31310024F0136 Page 16
- 1. provide the COR with information necessary to support the agencys documentation requirements, as identified in sections E202.6.2 and E202.7.1 of 36 CFR § 1194, respectively
- 2. request and obtain written approval from the COR for development and/or use, as applicable to the scope of the contract/order, of an alternative means for providing individuals with disabilities access to and use of the information and data, as specified in sections E202.6.3 and E202.7.2 of 36 CFR § 1194, respectively.
7.5 Additional Accessibility Requirements 7.5.1 Notification Due to Impact from NRC Policies, Procedures, Tools and/or ICT Infrastructure If and when 1) the Contractor is dependent upon NRC policies, procedures, tools and/or ICT infrastructure for standards-conformant delivery of any of the products or services under this acquisition, and 2) the Contractor is aware that conformance of products or services will be negatively impacted by capability gaps in NRC policies, procedures, tools and/or ICT infrastructure, the Contractor shall inform the COR so that the NRC can both be aware and take corrective action.
7.5.2 Accessibility of Electronic Content At a minimum, the standards require electronic content that is Public Facing or Agency Official Communication (as defined in sections E103 and E205.3 of 36 CFR § 1194, respectively) to be conformant with section E205.4 of 36 CFR § 1194.
- Public Facing content: Content made available by an agency to members of the general public.
- Agency Official Communication. Electronic content that is not public facing, when such content constitutes official business and is communicated through one or more of the following:
- a. An emergency notification;
- b. An initial or final decision adjudicating an administrative claim or proceeding;
- c. An internal or external program or policy announcement;
- d. A notice of benefits, program eligibility, employment opportunity, or personnel action;
- e. A formal acknowledgement of receipt;
- f. A survey questionnaire;
- g. A template or form;
- h. Educational or training materials; or
- i. Intranet content designed as a Web page.
However, if not Public Facing nor Agency Official Communication the NRC may still have a requirement that the electronic content deliverable be conformant with section E205.4 of 36 CFR § 1194, but only if the deliverable is identified in this contract/order as having the requirement to be accessible.
31310023D0005/31310024F0136 Page 17 The NRC may choose, for its own reasons, to take responsibility for the final conformance of an electronic content deliverable or a class of electronic content deliverables by explicitly identifying the deliverable or class of deliverables through one of the following means:
- 1. Identified in this contract/order, or
- 2. Identified in writing to the Contractor by the COR, with a copy to the CO.
- 8. KEY PERSONNEL QUALIFICATION REQUIREMENTS Key personnel will be the Project Manager, if they contribute substantively to the task order, and the Principal Investigator(s).
Project Manager The Contractor shall provide a Project Manager who shall be responsible for the performance of the work. The Project Manager shall have full authority to act for the Contractor on all order matters relating to daily operation of this order. The Project Manager shall have at a minimum, a bachelors degree in science or engineering. The Project Manager shall also have significant experience with program or project management and NRC regulatory requirements. The Project Manager will support all of the tasks.
Principal Investigator(s)
The Principal Investigator(s) shall have background and experience in the following areas:
Nuclear Engineering Radiation Protection and Health Physics Dose assessment Radioecology Radiological Engineering Consequence Analysis MACCS computer code Principal Investigator(s) shall have an understanding of MACCS as well as offsite consequence analysis phenomenology. Knowledge in in all technical elements of offsite consequence modeling including radionuclide release, atmospheric transport and dispersion, site data, weather data, emergency response and protective actions, exposure pathways, health effects, and offsite costs are required to perform analyses with MACCS code.
- 9. APPLICABLE DOCUMENTS AND STANDARDS Additional guidance on technical computer code testing may be found in:
(1) NRC NUREG/BR-0167 defines three levels of software used by the NRC. Level 1 software represents technical application software used in a safety decision by the NRC and Level 2 software is technical or non-technical software not used in safety decision. The guidelines in NUREG/BR-0167 apply to Level 1 and Level 2 software only.
(2) NRC Office of Regulatory Research (RES), Office Instruction OI-PRN-012 Software Quality Assurance.
(3) Institute of Electrical and Electronics Engineers (IEEE) Std 1012, IEEE Standard for
31310023D0005/31310024F0136 Page 18 Software Verification and Validation.
(4) Electric Power Research Institute (EPRI) Technical Report 1025243, Guideline for the Acceptance of Commercial-Grade Design and Analysis Computer Programs Listing of MACCS document that may be used to support this work include:
Please note older version of same of similar report may be needed if newer version has missing information.
(1) MACCS User Manual, Theory manuals, and verification reports, and other documents available on MACCS web site: https://maccs.sandia.gov/
(2) MACCS output error notification (FORTRAN code), ML17174A930, 2016 (3) MACCS Best Practices as Applied in the State-of-the-Art Reactor Consequence Analyses (SOARCA) Project, NUREG/CR-7009, MLl4234A148, 2014 (4) MACCS2 Consequence Code Set Version Control Matrix DRAFT, ML17047A457, 2013 (5) Benchmarking Upgraded HotSpot Dose Calculations Against MACCS2 Results, ML17047A449, 2009 (6) Draft WinMACCS User's Manual (superseded set above), ML072350221, 2007 (7) Comparison of Average Transport and Dispersion Among a Gaussian, a Two-Dimensional, and a Three-Dimensional Model NUREG/CR-6853, ML043240034, 2004 (8) Code Manual for MACCS2: Users Guide NUREG/CR-6613, Vol.1 SAND97-0594, ML17047A443, 1998 (9) Code Manual for MACCS2: preprocessor codes COMIDA2, FGRDCF, IDCF2 NUREG/CR-6613, Vol. 2 SAND97-0594, ML17047A444, 1998 (10) MELCOR Accident Consequence Code System (MACCS): Model Description NUREG/CR-4691 SAND86-1562 Vol. 2, ML063560409, 1990 (11) MELCOR Accident Consequence Code System (MACCS): Model Description NUREG/CR-4691 SAND86-1562 Vol. 2. ML063560409, 1990 (12) NUREG/CR-5376, TI90 007219 Quality Assurance and Verification of the MACCS Code, Version 1.5 (13) SANDIA REPORT SAND2021-11703 Preliminary Radioisotope Screening for Off-site Consequence Assessment of Advanced Non-LWR Systems (14) Reviewing MACCS Capabilities for Modeling Variable Physiochemical Forms, ML22270A049
31310023D0005/31310024F0136 Page 19 (15) Reviewing MACCS Capabilities for Assessing Tritium Releases to the Environment, ML22270A054 (16) Quantitative Assessment for Advanced Reactor Radioisotope Screening Utilizing a Heat Pipe Reactor Inventory, ML22270A046
- 10. GOVERNMENT-FURNISHED PROPERTY/MATERIALS It is understood that SWRI has access to MACCS computer code. A copy of the code and associated documentation will be provided by the COR if requested.
- 11. PLACE OF PERFORMANCE The work to be performed under this task order shall be performed at the Contractors site.
- 12. SPECIAL CONSIDERATIONS 12.1 TRAVEL No travel is anticipated for this requirement.
12.2 SECURITY The work expected under this task order is unclassified and not sensitive.
12.3 LICENSE FEE RECOVERABLE Work under this task order is not license fee recoverable.
31310023D0005/31310024F0136 Page 20 D - Packaging and Marking D.1 PACKAGING AND MARKING (a) The Contractor shall package material for shipment to the NRC in such a manner that will ensure acceptance by common carrier and safe delivery at destination. Containers and closures shall comply with the Surface Transportation Board, Uniform Freight Classification Rules, or regulations of other carriers as applicable to the mode of transportation.
(b) On the front of the package, the Contractor shall clearly identify the contract number under which the product is being provided.
(c) Additional packaging and/or marking requirements are as follows: N/A.
D.2 BRANDING The Contractor is required to use the statement below in any publications, presentations, articles, products, or materials funded under this contract/order, to the extent practical, in order to provide NRC with recognition for its involvement in and contribution to the project. If the work performed is funded entirely with NRC funds, then the contractor must acknowledge that information in its documentation/presentation.
Work Supported by the U.S. Nuclear Regulatory Commission (NRC), Office of Nuclear Regulatory Research, under Contract/order number 31310023D0005/31310024F0136.
31310023D0005/31310024F0136 Page 21 E - Inspection and Acceptance E.1 INSPECTION AND ACCEPTANCE BY THE NRC (SEP 2013)
Inspection and acceptance of the deliverable items to be furnished hereunder shall be made by the NRC Contracting Officers Representative (COR) at the destination, accordance with FAR 52.247 F.o.b. Destination.
31310023D0005/31310024F0136 Page 22 F - Deliveries or Performance F.1 PLACE OF DELIVERY-REPORTS The items to be furnished hereunder shall be delivered, with all charges paid by the Contractor, to:
- a. Contracting Officers Representative (COR)
Refer to Section H.3 2052.215-71 CONTRACTING OFFICER REPRESENTATIVE AUTHORITY. (OCT 1999)
- b. Contracting Officer (CO) (1 electronic copy)
(End of Clause)
F.2 TASK/DELIVERY ORDER PERIOD OF PERFORMANCE (SEP 2013)
This order shall commence on September 16, 2024 and will expire on March 29, 2026.
31310023D0005/31310024F0136 Page 23 H - Special Contract Requirements H.1 ANNUAL AND FINAL CONTRACTOR PERFORMANCE EVALUATIONS (AUG 2023)
Annual and final evaluations of contractor performance under this contract will be prepared in accordance with FAR Subpart 42.15, "Contractor Performance Information," normally at or near the time the contractor is notified of the NRC's intent to exercise the contract option. If the multi-year contract does not have option years, then an annual evaluation will be prepared. Final evaluations of contractor performance will be prepared at the expiration of the contract during the contract closeout process.
The Contracting Officer will transmit the NRC Contracting Officers Representatives (COR) annual and final contractor performance evaluations to the contractor's Project Manager, unless otherwise instructed by the contractor. The contractor will be permitted thirty (30) calendar days to review the document and submit comments, rebutting statements, or additional information.
Where a contractor concurs with, or takes no exception to an annual performance evaluation, the Contracting Officer will consider such evaluation final and releasable for source selection purposes. Disagreements between the parties regarding a performance evaluation will be referred to an individual one level above the Contracting Officer, whose decision will be final.
The Contracting Officer will send a copy of the completed evaluation report, marked "Source Selection Information, to the contractor's Project Manager for their records as soon as practicable after it has been finalized. The completed evaluation report also will be used as a tool to improve communications between the NRC and the contractor and to improve contract performance.
The completed annual performance evaluation will be used to support future award decisions in accordance with FAR 42.1502 and 42.1503. During the period the information is being used to provide source selection information, the completed annual performance evaluation will be released to only two parties - the Federal government personnel performing the source selection evaluation and the contractor under evaluation if the contractor does not have a copy of the report already.
H.2 2052.215-70 KEY PERSONNEL. (JAN 1993)
(a) The following individuals are considered to be essential to the successful performance of the work hereunder:
- The contractor agrees that personnel may not be removed from the contract work or replaced without compliance with paragraphs (b) and (c) of this section.
(b) If one or more of the key personnel, for whatever reason, becomes, or is expected to become, unavailable for work under this contract for a continuous period exceeding 30 work days, or is expected to devote substantially less effort to the work than indicated in the proposal or initially anticipated, the contractor shall immediately notify the contracting officer and shall, subject to the concurrence of the contracting officer, promptly replace the personnel with personnel of at least substantially equal ability and qualifications.
31310023D0005/31310024F0136 Page 24 (c) Each request for approval of substitutions must be in writing and contain a detailed explanation of the circumstances necessitating the proposed substitutions. The request must also contain a complete resume for the proposed substitute and other information requested or needed by the contracting officer to evaluate the proposed substitution.
The contracting officer and the project officer shall evaluate the contractor's request and the contracting officer shall promptly notify the contractor of his or her decision in writing.
(d) If the contracting officer determines that suitable and timely replacement of key personnel who have been reassigned, terminated, or have otherwise become unavailable for the contract work is not reasonably forthcoming, or that the resultant reduction of productive effort would be so substantial as to impair the successful completion of the contract or the service order, the contract may be terminated by the contracting officer for default or for the convenience of the Government, as appropriate.
If the contracting officer finds the contractor at fault for the condition, the contract price or fixed fee may be equitably adjusted downward to compensate the Government for any resultant delay, loss, or damage.
(End of Clause)
- To be incorporated into any resultant contract H.3 2052.215-71 CONTRACTING OFFICER REPRESENTATIVE AUTHORITY. (OCT 1999)
(a) The contracting officer's authorized representative (hereinafter referred to as the COR) for this contract is:
Primary COR:
Name: Salman Haq Address: U.S. Nuclear Regulatory Commission Office of Nuclear Regulatory Research Washington, DC 20555 Phone: 301-415-1799 E-mail: Salman.Haq@nrc.gov Alternate COR:
Name: Nazila Tehrani Address: U.S. Nuclear Regulatory Commission Office of Nuclear Regulatory Research Washington, DC 20555 Phone: (301) 415-3684 E-mail: Nazila.Tehrani@nrc.gov (b) Performance of the work under this contract is subject to the technical direction of the NRC COR. The term "technical direction" is defined to include the following:
(1) Technical direction to the contractor which shifts work emphasis between areas of work or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work (SOW) or changes to specific travel identified in the SOW), fills in details, or otherwise serves to accomplish the contractual SOW.
31310023D0005/31310024F0136 Page 25 (2) Provide advice and guidance to the contractor in the preparation of drawings, specifications, or technical portions of the work description.
(3) Review and, where required by the contract, approval of technical reports, drawings, specifications, and technical information to be delivered by the contractor to the Government under the contract.
(c) Technical direction must be within the general statement of work stated in the contract. The COR does not have the authority to and may not issue any technical direction which:
(1) Constitutes an assignment of work outside the general scope of the contract.
(2) Constitutes a change as defined in the "Changes" clause of this contract.
(3) In any way causes an increase or decrease in the total estimated contract cost, the fixed fee, if any, or the time required for contract performance.
(4) Changes any of the expressed terms, conditions, or specifications of the contract.
(5) Terminates the contract, settles any claim or dispute arising under the contract, or issues any unilateral directive whatever.
(d) All technical directions must be issued in writing by the COR or must be confirmed by the COR in writing within ten (10) working days after verbal issuance. A copy of the written direction must be furnished to the contracting officer. A copy of NRC Form 445, Request for Approval of Official Foreign Travel, which has received final approval from the NRC must be furnished to the contracting officer.
(e) The contractor shall proceed promptly with the performance of technical directions duly issued by the COR in the manner prescribed by this clause and within the COR's authority under the provisions of this clause.
(f) If, in the opinion of the contractor, any instruction or direction issued by the COR is within one of the categories as defined in paragraph (c) of this section, the contractor may not proceed but shall notify the contracting officer in writing within five (5) working days after the receipt of any instruction or direction and shall request the contracting officer to modify the contract accordingly. Upon receiving the notification from the contractor, the contracting officer shall issue an appropriate contract modification or advise the contractor in writing that, in the contracting officer's opinion, the technical direction is within the scope of this article and does not constitute a change under the "Changes" clause.
(g) Any unauthorized commitment or direction issued by the COR may result in an unnecessary delay in the contractor's performance and may even result in the contractor expending funds for unallowable costs under the contract.
(h) A failure of the parties to agree upon the nature of the instruction or direction or upon the contract action to be taken with respect thereto is subject to 52.233 Disputes.
31310023D0005/31310024F0136 Page 26 (i) In addition to providing technical direction as defined in paragraph (b) of the section, the COR shall:
(1) Monitor the contractor's technical progress, including surveillance and assessment of performance, and recommend to the contracting officer changes in requirements.
(2) Assist the contractor in the resolution of technical problems encountered during performance.
(3) Review all costs requested for reimbursement by the contractor and submit to the contracting officer recommendations for approval, disapproval, or suspension of payment for supplies and services required under this contract.
(4) Assist the contractor in obtaining the badges for the contractor personnel.
(5) Immediately notify the Security Branch, Division of Facilities and Security (SB/DFS) (via e-mail) when a contractor employee no longer requires access authorization and return of any NRC issued badge to SB/DFS within three days after their termination.
(6) Ensure that all contractor employees that require access to classified Restricted Data or National Security Information or matter, access to sensitive unclassified information (Safeguards, Official Use Only, and Proprietary information) access to sensitive IT systems or data, unescorted access to NRC controlled buildings/space, or unescorted access to protected and vital areas of nuclear power plants receive approval of SB/DFS prior to access in accordance with Management Directive and Handbook 12.3.
(7) For contracts for the design, development, maintenance or operation of Privacy Act Systems of Records, obtain from the contractor as part of closeout procedures, written certification that the contractor has returned to NRC, transferred to the successor contractor, or destroyed at the end of the contract in accordance with instructions provided by the NRC Systems Manager for Privacy Act Systems of Records, all records (electronic or paper) which were created, compiled, obtained or maintained under the contract.
(End of Clause)
31310023D0005/31310024F0136 Page 27 I - Contract Clauses I.1 2052.209-72 CONTRACTOR ORGANIZATIONAL CONFLICTS OF INTEREST. (JAN 1993)
(a) Purpose. The primary purpose of this clause is to aid in ensuring that the contractor:
(1) Is not placed in a conflicting role because of current or planned interests (financial, contractual, organizational, or otherwise) which relate to the work under this contract; and (2) Does not obtain an unfair competitive advantage over other parties by virtue of its performance of this contract.
(b) Scope. The restrictions described apply to performance or participation by the contractor, as defined in 48 CFR 2009.570-2 in the activities covered by this clause.
(c) Work for others.
(1) Notwithstanding any other provision of this contract, during the term of this contract, the contractor agrees to forego entering into consulting or other contractual arrangements with any firm or organization the result of which may give rise to a conflict of interest with respect to the work being performed under this contract. The contractor shall ensure that all employees under this contract abide by the provision of this clause. If the contractor has reason to believe, with respect to itself or any employee, that any proposed consultant or other contractual arrangement with any firm or organization may involve a potential conflict of interest, the contractor shall obtain the written approval of the contracting officer before the execution of such contractual arrangement.
(2) The contractor may not represent, assist, or otherwise support an NRC licensee or applicant undergoing an NRC audit, inspection, or review where the activities that are the subject of the audit, inspection, or review are the same as or substantially similar to the services within the scope of this contract (or task order as appropriate) except where the NRC licensee or applicant requires the contractor's support to explain or defend the contractor's prior work for the utility or other entity which NRC questions.
(3) When the contractor performs work for the NRC under this contract at any NRC licensee or applicant site, the contractor shall neither solicit nor perform work in the same or similar technical area for that licensee or applicant organization for a period commencing with the award of the task order or beginning of work on the site (if not a task order contract) and ending one year after completion of all work under the associated task order, or last time at the site (if not a task order contract).
(4) When the contractor performs work for the NRC under this contract at any NRC licensee or applicant site, (i) The contractor may not solicit work at that site for that licensee or applicant during the period of performance of the task order or the contract, as appropriate.
31310023D0005/31310024F0136 Page 28 (ii) The contractor may not perform work at that site for that licensee or applicant during the period of performance of the task order or the contract, as appropriate, and for one year thereafter.
(iii) Notwithstanding the foregoing, the contracting officer may authorize the contractor to solicit or perform this type of work (except work in the same or similar technical area) if the contracting officer determines that the situation will not pose a potential for technical bias or unfair competitive advantage.
(d) Disclosure after award.
(1) The contractor warrants that to the best of its knowledge and belief, and except as otherwise set forth in this contract, that it does not have any organizational conflicts of interest as defined in 48 CFR 2009.570-2.
(2) The contractor agrees that if, after award, it discovers organizational conflicts of interest with respect to this contract, it shall make an immediate and full disclosure in writing to the contracting officer. This statement must include a description of the action which the contractor has taken or proposes to take to avoid or mitigate such conflicts. The NRC may, however, terminate the contract if termination is in the best interest of the Government.
(3) It is recognized that the scope of work of a task-order-type contract necessarily encompasses a broad spectrum of activities. Consequently, if this is a task-order-type contract, the contractor agrees that it will disclose all proposed new work involving NRC licensees or applicants which comes within the scope of work of the underlying contract. Further, if this contract involves work at a licensee or applicant site, the contractor agrees to exercise diligence to discover and disclose any new work at that licensee or applicant site. This disclosure must be made before the submission of a bid or proposal to the utility or other regulated entity and must be received by the NRC at least 15 days before the proposed award date in any event, unless a written justification demonstrating urgency and due diligence to discover and disclose is provided by the contractor and approved by the contracting officer. The disclosure must include the statement of work, the dollar value of the proposed contract, and any other documents that are needed to fully describe the proposed work for the regulated utility or other regulated entity. NRC may deny approval of the disclosed work only when the NRC has issued a task order which includes the technical area and, if site-specific, the site, or has plans to issue a task order which includes the technical area and, if site-specific, the site, or when the work violates paragraphs (c)(2), (c)(3) or (c)(4) of this section.
(e) Access to and use of information.
(1) If, in the performance of this contract, the contractor obtains access to information, such as NRC plans, policies, reports, studies, financial plans, internal data protected by the Privacy Act of 1974 (5 U.S.C. Section 552a (1988)), or the Freedom of Information Act (5 U.S.C. Section 552 (1986)), the contractor agrees not to:
31310023D0005/31310024F0136 Page 29 (i) Use this information for any private purpose until the information has been released to the public; (ii) Compete for work for the Commission based on the information for a period of six months after either the completion of this contract or the release of the information to the public, whichever is first; (iii) Submit an unsolicited proposal to the Government based on the information until one year after the release of the information to the public; or (iv) Release the information without prior written approval by the contracting officer unless the information has previously been released to the public by the NRC.
(2) In addition, the contractor agrees that, to the extent it receives or is given access to proprietary data, data protected by the Privacy Act of 1974 (5 U.S.C.
Section 552a (1988)), or the Freedom of Information Act (5 U.S.C. Section 552 (1986)), or other confidential or privileged technical, business, or financial information under this contract, the contractor shall treat the information in accordance with restrictions placed on use of the information.
(3) Subject to patent and security provisions of this contract, the contractor shall have the right to use technical data it produces under this contract for private purposes provided that all requirements of this contract have been met.
(f) Subcontracts. Except as provided in 48 CFR 2009.570-2, the contractor shall include this clause, including this paragraph, in subcontracts of any tier. The terms contract, contractor, and contracting officer, must be appropriately modified to preserve the Government's rights.
(g) Remedies. For breach of any of the above restrictions, or for intentional nondisclosure or misrepresentation of any relevant interest required to be disclosed concerning this contract or for such erroneous representations that necessarily imply bad faith, the Government may terminate the contract for default, disqualify the contractor from subsequent contractual efforts, and pursue other remedies permitted by law or this contract.
(h) Waiver. A request for waiver under this clause must be directed in writing to the contracting officer in accordance with the procedures outlined in 48 CFR 2009.570-9.
(i) Follow-on effort. The contractor shall be ineligible to participate in NRC contracts, subcontracts, or proposals therefor (solicited or unsolicited) which stem directly from the contractor's performance of work under this contract. Furthermore, unless so directed in writing by the contracting officer, the contractor may not perform any technical consulting or management support services work or evaluation activities under this contract on any of its products or services or the products or services of another firm if the contractor has been substantially involved in the development or marketing of the products or services.
(1) If the contractor under this contract, prepares a complete or essentially complete statement of work or specifications, the contractor is not eligible to
31310023D0005/31310024F0136 Page 30 perform or participate in the initial contractual effort which is based on the statement of work or specifications. The contractor may not incorporate its products or services in the statement of work or specifications unless so directed in writing by the contracting officer, in which case the restrictions in this paragraph do not apply.
(2) Nothing in this paragraph precludes the contractor from offering or selling its standard commercial items to the Government.
(End of Clause)
I.2 52.217-7 OPTION FOR INCREASED QUANTITY - SEPARATELY PRICED LINE ITEM.
(MAR 1989)
The Government may require the delivery of the numbered line item, identified in the Schedule as an option item, in the quantity and at the price stated in the Schedule. The Contracting Officer may exercise the option by written notice to the Contractor within the period of performance. Delivery of added items shall continue at the same rate that like items are called for under the contract, unless the parties otherwise agree.
(End of clause)
I.3 52.217-8 OPTION TO EXTEND SERVICES. (NOV 1999)
The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the Contractor within 3 days before the Task Order expires.
(End of clause)