31310019R0008_Solicitation_CO.pdf
PDF 646 KB Posted
- Solicitation number
- 31310019R0008
- Issued by
-
Nuclear Regulatory Commission
About this file
31310019R0008 Solicitation CO
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
31310019R0008
SOLICITATION, OFFER AND AWARD
4. TYPE OF SOLICITATION2. CONTRACT NUMBER 3. SOLICITATION NUMBER
7. ISSUED BY CODE 8. ADDRESS OFFER TO (If other than Item 7)
ORDER UNDER DPAS (15 CFR 700)
6. REQUISITION/PURCHASE NUMBER
NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".
NEGOTIATED (RFP)
SEALED BID (IFB)
5. DATE ISSUED
1. THIS CONTRACT IS A RATED RATING PAGE OF PAGES
1 99
C. E-MAIL ADDRESS
EXT.NUMBERAREA CODE
B. TELEPHONE (NO COLLECT CALLS)A. NAME
10. FOR
INFORMATION
CALL:
CAUTION: LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.
(Date)(Hour) local timeuntildepository located in copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if hand carried, in the
SOLICITATION
9. Sealed offers in original and
PART IV - REPRESENTATIONS AND INSTRUCTIONS
OTHER STATEMENTS OF OFFERORS
EVALUATION FACTORS FOR AWARD
INSTRS., CONDS., AND NOTICES TO OFFERORS
REPRESENTATIONS, CERTIFICATIONS AND
LIST OF ATTACHMENTS
CONTRACT CLAUSES
PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.
I
J
K
L
M SPECIAL CONTRACT REQUIREMENTS
CONTRACT ADMINISTRATION DATA
DELIVERIES OR PERFORMANCE
INSPECTION AND ACCEPTANCE
PACKAGING AND MARKING
DESCRIPTION/SPECS./WORK STATEMENT
SUPPLIES OR SERVICES AND PRICES/COSTS
SOLICITATION/CONTRACT FORM
PART II - CONTRACT CLAUSESPART I - THE SCHEDULE
H
G
F
E
D
C
B
A
SEC. DESCRIPTION PAGE(S) (X) DESCRIPTION SEC. (X)
11. TABLE OF CONTENTS
18. OFFER DATE17. SIGNATURE
SUCH ADDRESS IN SCHEDULE.
IS DIFFERENT FROM ABOVE - ENTER
15C. CHECK IF REMITTANCE ADDRESS
EXT.NUMBERAREA CODE
15B. TELEPHONE NUMBER
(Type or print)AND
ADDRESS
OF
OFFEROR
CODE FACILITY
16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER15A. NAME
DATEAMENDMENT NO.DATEAMENDMENT NO.
and related documents numbered and dated):
amendments to the SOLICITATION for offerors
(The offeror acknowledges receipt of
14. ACKNOWLEDGEMENT OF AMENDMENTS
CALENDAR DAYS (%)30 CALENDAR DAYS (%)20 CALENDAR DAYS (%)10 CALENDAR DAYS (%)
(See Section I, Clause No. 52.232.8)
13. DISCOUNT FOR PROMPT PAYMENT
designated point(s), within the time specified in the schedule.
by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the
NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.
OFFER (Must be fully completed by offeror)
IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.
28. AWARD DATE
(Signature of Contracting Officer)
27. UNITED STATES OF AMERICA
25. PAYMENT WILL BE MADE BY
26. NAME OF CONTRACTING OFFICER (Type or print)
CODE 24. ADMINISTERED BY (If other than Item 7)
ITEM
(4 copies unless otherwise specified)
23. SUBMIT INVOICES TO ADDRESS SHOWN IN
41 U.S.C. 253 (c) ( 10 U.S.C. 2304 (c) (
22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:
21. ACCOUNTING AND APPROPRIATION20. AMOUNT19. ACCEPTED AS TO ITEMS NUMBERED
AWARD (To be completed by government)
CODE
03/08/2019 X
NRCHQ
US NRC - HQ
ACQUISITION MANAGEMENT DIVISION
MAIL STOP TWFN-07B20M
WASHINGTON DC 20555-0001
Jeffrey.Mitchell@NRC.GOV
1200 ET 04/09/2019
JEFFREY R. MITCHELL 301
Jeffrey.Mitchell@nrc.gov
415-5074
PAGE(S)
JEFFREY R. MITCHELL
AUTHORIZED FOR LOCAL REPRODUCTION
Previous edition is unusable
STANDARD FORM 33 (Rev. 9-97)
Prescribed by GSA - FAR (48 CFR) 53.214(c)
12. In compliance with the above, the undersigned agrees, if this offer is accepted within _____0_________ calendar days (60 calendar days unless a different period is inserted
SECTION A - Solicitation/Contract Form SECTION B - Supplies or Services/Prices
B.1 BRIEF DESCRIPTION OF WORK ALTERNATE I
B.2 CONSIDERATION AND OBLIGATION—INDEFINITE-QUANTITY CONTRACT
B.3 SCHEDULE OF ESTIMATED COST…………………………………………………..
SECTION C – Statement of Work SECTION D - Packaging and Marking
D.1 BRANDING
D.2 PACKAGING AND MARKING
SECTION E - Inspection and Acceptance E.1 Clauses Incorporated by reference.…………………………………………………… E.2 Quality Assurance………………………………………………………………………..
E.3 Research Quality…………………………………………………………………………
SECTION F - DELIVERIES OR PERFORMANCE
F.1 CLAUSES INCORPORATED BY REFERENCE…………………………………….
F.2 PREPARATION OF TECHNICAL REPORTS (JAN 1993)…………………………..
F.3 PERIOD OF PERFORMANCE ALTERNATE IV
F.4 PLACE OF DELIVERY-REPORTS
SECTION G - Contract Administration Data
G.1 2052.215-71 CONTRACTING OFFICER REPRESENTATIVE (COR) (NOVEMBER
2006)
G.2 2052.215-77 TRAVEL APPROVALS AND REIMBURSEMENT. (OCT 1999)
G.3 2052.216-71 INDIRECT COST RATES. (JAN 1993)
G.4 2052.216-72 TASK ORDER PROCEDURES. (OCT 1999)
G.5 2052.216-73 ACCELERATED TASK ORDER PROCEDURES. (JAN 1993)
G.6 ORDERING PROCEDURES FOR MULTIPLE-AWARD INDEFINITE-
DELIVERY/INDEFINITE-QUANTITY CONTRACTS (MAR 2014)
G.7 REGISTRATION IN FEDCONNECT® (JULY 2014)
G.8 ELECTRONIC PAYMENT (DEC 2017)
SECTION H - Special Contract Requirements
H.1 2052.204-70 SECURITY. (OCT 1999)
H.2 2052.204-71 SITE ACCESS BADGE REQUIREMENTS. (JAN 1993)
H.3 2052.209-72 CONTRACTOR ORGANIZATIONAL CONFLICTS OF INTEREST.
(JAN 1993)
H.4 2052.215-70 KEY PERSONNEL. (JAN 1993)
H.5 2052.235-70 PUBLICATION OF RESEARCH RESULTS (OCT 1999)
H.6 2052.242-70 RESOLVING DIFFERING PROFESSIONAL VIEWS. (OCT 1999)
H.7 2052.242-71 PROCEDURES FOR RESOLVING DIFFERING PROFESSIONAL
VIEWS. (OCT 1999)
H.8 AWARD NOTIFICATION AND COMMITMENT OF PUBLIC FUNDS
H.9 USE OF AUTOMATED CLEARING HOUSE (ACH) ELECTRONIC
PAYMENT/REMITTANCE ADDRESS
H.10 DRUG FREE WORKPLACE TESTING: UNESCORTED ACCESS TO NUCLEAR
FACILITIES, ACCESS TO CLASSIFIED INFORMATION OR SAFEGUARDS
INFORMATION, OR PERFORMING IN SPECIALLY SENSITIVE POSITIONS (OCT
2014)
H.11 SECURITY REQUIREMENTS RELATING TO THE PRODUCTION OF REPORTS
OR THE PUBLICATION OF RESULTS UNDER CONTRACTS, AGREEMENTS, AND
GRANTS (JUL 2016)
H.12 NRC INFORMATION TECHNOLOGY SECURITY TRAINING (MAY 2016)
H.13 NRCH030 SECURITY REQUIREMENTS FOR INFORMATION TECHNOLOGY
LEVEL I OR LEVEL II ACCESS APPROVAL (JUL 2016)
H.14 ANNUAL AND FINAL CONTRACTOR PERFORMANCE EVALUATIONS
H.15 INFORMATION TECHNOLOGY (IT) SECURITY REQUIREMENTS – GENERAL
(JUL 2016)
H.16 NRCH036 IT SECURITY REQUIREMENTS - DEVELOPMENT AND
OPERATIONS AND MAINTENANCE REQUIREMENTS (APR 2014)
H.17 CONTRACTOR RESPONSIBILITY FOR PROTECTING PERSONALLY
IDENTIFIABLE INFORMATION (PII) (AUG 2011)
H.18 UPDATED STANDARDS FOR CONTRACTORS WHO PREPARE NUREG-
SERIES MANUSCRIPTS
H.19 COPYRIGHT OF CODES - SPECIAL NUCLEAR PURPOSE LICENSE
SECTION I - Contract Clauses
I.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE. (FEB 1998)
I.2 52.204-23 Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab and Other Covered Entities.
I.3 52.216-7 ALLOWABLE COST AND PAYMENT. (AUG 2018)
I.4 52.216-18 ORDERING. (OCT 1995)
I.5 52.216-19 ORDER LIMITATIONS. (OCT 1995)
I.6 52.216-22 INDEFINITE QUANTITY. (OCT 1995)
I.7 52.217-8 OPTION TO EXTEND SERVICES. (NOV 1999)
I.8 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT. (MAR 2000)I.8
I.9 52.219-4 NOTICE OF PRICE EVALUATION PREFERENCE FOR HUBZONE
SMALL BUSINESS CONCERNS. (OCT 2014)
I.10 52.232-20 LIMITATION OF COST (APR 1984)
I.11 52.232-22 LIMITATION OF FUNDS. (APR 1984)
I.12 52.244-2 SUBCONTRACTS. (OCT 2010) - ALTERNATE I (JUN 2007)
I.13 COMPLIANCE WITH SECTION 508 OF THE REHABILITATION ACT OF 1973,
AS AMENDED (SEP 2013)
SECTION J - List of Documents, Exhibits and Other Attachments SECTION K - Representations, Certifications, and Other Statements of Bidders K.1 Clauses
K.2 52.204-17 OWNERSHIP OR CONTROL OF OFFEROR. (JUL 2016)
K.3 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS. (JUL 2013)
K.4 52.209-11 REPRESENTATION BY CORPORATIONS REGARDING
DELINQUENT TAX LIABILITY OR A FELONY CONVICTION UNDER ANY FEDERAL
LAW. (FEB 2016)
K.5 52.215-6 PLACE OF PERFORMANCE. (OCT 1997)
K.6 52.219-1 SMALL BUSINESS PROGRAM REPRESENTATIONS. (OCT 2014)
K.7 52.222-22 PREVIOUS CONTRACTS AND COMPLIANCE REPORTS. (FEB 1999)
K.8 52.222-25 AFFIRMATIVE ACTION COMPLIANCE. (APR 1984)
K.9 52.225-20 PROHIBITION ON CONDUCTING RESTRICTED BUSINESS
OPERATIONS IN SUDAN--CERTIFICATION. (AUG 2009)
K.10 2052.209-70 CURRENT/FORMER AGENCY EMPLOYEE INVOLVEMENT.
(OCT 1999)
K.11 2052.209-71 CONTRACTOR ORGANIZATIONAL CONFLICTS OF INTEREST
(REPRESENTATION). (OCT 1999)
SECTION L - Instructions,Conditions, and Notices to Bidders
L.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE.
(FEB 1998)
L.2 52.216-1 TYPE OF CONTRACT. (APR 1984)
L.3 52.233-2 SERVICE OF PROTEST. (SEP 2006)
L.4 2052.215-72 TIMELY RECEIPT OF PROPOSALS. (OCT 1999)
L.5 2052.215-73 AWARD NOTIFICATION AND COMMITMENT OF PUBLIC FUNDS
(OCT 1999)
L.6 2052.215-74 DISPOSITION OF PROPOSALS. (JAN 1993)
L.7 2052.216-70 LEVEL OF EFFORT. (JAN 1993)
L.8 PROPOSAL PRESENTATION AND FORMAT (SEP 2012) ALTERNATE I (FOR
NEGOTIATED COST TYPE TASK ORDER CONTRACTS AND INDIVIDUAL COST-
REIMBURSEMENT TASK ORDERS) (SEP 2012)
L.9 GREEN PURCHASING (JUL 2016)
L.10 REFERENCED DOCUMENTS AVAILABLE FROM THE NRC (AUG 2011)
SECTION M - Evaluation Factors for Award M.1 Clauses
M.2 2052.215-79 CONTRACT AWARD AND EVALUATION OF PROPOSALS. (OCT
1999)
SECTION B - Supplies or Services/Prices
B.1 BRIEF DESCRIPTION OF WORK ALTERNATE I
(a) The title of this project is: MAINTENANCE OF NUCLEAR REGULATORY
COMMISSION (NRC) COMPUTER CODES III (MONC-3)
(b) Summary work description: The contractor shall provide thermal-hydraulic (T/H) code and model development and improvements, as well as configuration control, correction of code errors, documentation updates, and user support to the NRC, its contractors, and members of CAMP and the domestic user community.
(c) Orders will be issued for work in accordance with FAR 52.216-18 – Ordering.
(End of Clause)
B.2 CONSIDERATION AND OBLIGATION—INDEFINITE-QUANTITY CONTRACT
(a) The estimated total quantity of this contract for the products/services under this contract is incorporated into resultant contract.
(b) The Contracting Officer will obligate funds on each task order issued.
(c) The minimum guarantee under this contract is $30,000.00 [Obligated under Task Order No. 1.
(d) The obligated amount for this contract at award shall result in the fulfilment of the $30,000.00 guaranteed minimum obligation under this IDIQ contract.
(e) A total estimated cost and fee, if any, will be negotiated for each task order and will be incorporated as a ceiling in the resultant task order. The Contractor shall comply with the provisions of FAR 52.232-20 - Limitation of Cost for fully-funded task orders and FAR 52.232-22 - Limitation of Funds for incrementally-funded task orders, issued hereunder.
(End of Clause)
B.3 SCHEDULE OF ESTIMATED COST
SCHEDULE OF ESTIMATED COST
CLIN NO. DESCRIPTION OF
SUPPLIES/SERVICES
ESTIMATED
COST
FIXED FEE TOTAL
ESTIMATED
COST PLUS
FIXED FEE
FIVE YEARS FROM EFFECTIVE DATE
(INCLUSIVE OF FOUR ONE-YEAR OPTION
PERIODS)
00001 Base Year
CLIN NO. SCHEDULE OF PERIOD OF PERFORMANCE
00001 Base Year (12 months)
10001 Option Period 1 (12 months)
20001 Option Period 2 (12 months)
30001 Option Period 3 (12 months)
40001 Option Period 4 (12 months)
SECTION C - Description/Specifications
STATEMENT OF WORK
BACKGROUND
The Division of Safety Analysis (DSA), Office of Nuclear Regulatory Research (RES) has responsibility for the development, testing, assessment, maintenance, and user support of the NRC's thermal-hydraulic (T/H) computer codes. These codes include
TRACE (TRAC/RELAP Advanced Computational Engine) is NRC's flagship thermal-hydraulics analysis tool. It is a modernized thermal-hydraulics code designed to consolidate the capabilities of NRC's 4 legacy safety codes - TRAC- P, TRAC-B, RELAP, and RAMONA. It is able to analyze large/small break LOCAs and system transients in PWRs, BWRs, SMRs, and other advanced reactor designs. The capability also exists to model thermal hydraulic phenomena in both 1-D and 3-D space. It also includes the ability to model 3-D kinetics through integration with the Purdue Advanced Reactor Core Simulator (PARCS) code. The combined integrated product of these two tools is called TRACE/PARCS throughout the remainder of this contract.
PARCS (Purdue Advanced Reactor Core Simulator) is a computer code that solves the time-dependent two-group neutron diffusion equation in three-dimensional Cartesian geometry using nodal methods to obtain the steady-state and transient neutron flux distribution. The code may be used in the analysis of reactivity-initiated accidents in light-water reactors where spatial effects may be important. It exists both as a stand-alone program and as a separate computational module coupled to other thermal-hydraulic codes. In this latter context, the source code for PARCS is tightly integrated with TRACE. PARCS may also be run in a coupled mode with RELAP5 using a looser coupling technology called the Generic Interface (GI). Associated with PARCS is the GENPMAXS tool which is used for converting macroscopic cross-sections generated by lattice physics codes like SCALE/TRITON/POLARIS, CASMO, or HELIOS into a form readable by PARCS.
RELAP5 (Reactor Excursion and Leak Analysis Program) is a one dimensional (1-D) best-estimate T/H code that is primarily used for small-break loss of coolant accidents (SBLOCAs) and other transients.
SNAP (Symbolic Nuclear Analysis Package) is a graphical user interface with pre-processor and post-processor capabilities which assists users in developing TRACE and RELAP5 input decks and running the codes.
AVScript (Automated Validation Script) is a script written in the PERL language designed to allow code users to automate the process of running T/H codes and generating figures that are used to analyze the simulation of interest. The current TRACE assessment framework (over 500 separate and integral effects tests) makes extensive use of this tool. The functionality provided by this tool has been captured in an SNAP plugin called AVF. It is expected that over time, the entire TRACE assessment framework will be migrated to this new plugin.
ACAP (Automated Code Assessment Program) is a graphical program designed to allow code users to easily generate quantitative figures of merit regarding the goodness of fit between code predictions and experimental data or other code predictions. This tool is written in C/C++ and runs as a GUI on Windows or in batch mode on Windows or Linux. The batch functionality of this tool has been captured in a SNAP plugin written in Java.
REQUIREMENTS
These codes are used to support independent regulatory decision-making in support of design reviews, power uprates, license extensions, generic safety issues, and the review of vendor evaluation models.
Additional responsibility of the Division includes maintenance of a thermal-hydraulic databank which contains the results of T/H experiments, tests, and assessments used to demonstrate applicability of T/H codes for their intended uses.
When requested by the NRC, the contractor makes the codes available to NRC-approved domestic users via a User Support Group, and foreign users participating in the international Code Applications and Maintenance Program (CAMP). The use of the codes by these organizations provides calculations and assessments needed to validate and improve the codes. Semi-annual international workshops are conducted by the NRC to discuss code results and related issues.
Codes are currently provided to approved users for a nominal fee that covers shipping, handling, and assistance in installation of the codes. Some users opt to join the User Support Group and pay an annual membership fee. For the additional fee, members receive consultation over email or the telephone on possible problems encountered in use of the codes, including new versions of the codes, and may send a representative to annual code training conducted by the NRC. Both domestic users and CAMP members continue to assess the codes against reactor operational and/or experimental data. As a result of these comparisons and through use of the codes for plant safety assessment, many changes to the codes are suggested each year. When sufficient changes have been made to the codes, assessments are made by the contractor and new versions of the codes are released to the users.
The contractor may, at the request of NRC, assert copyright to these codes, subject to a special nuclear purpose license [Section H.19 entitled “Copyright of Codes – Special Nuclear Purpose License] that gives NRC the right to distribute the code in the nuclear arena and transfer the copyright to new contractors as new contract vehicles are awarded.
FAR 52.227-17 “Rights in Data -- Special Works (DEC 2007)” applies to all special works data identified below in DELIVERABLES, while FAR 52.227-14 applies to data other than special works data generate under this contract.
The contractor provides a single point of contact to assist code users, performs code and model development for the TRACE code, provides maintenance in the form of version control, error corrections and code debugging, and provides support for CAMP activities for the TRACE and RELAP5 codes. As noted above, it is expected that code modifications will be required as a result of code usage/assessment. The contractor is also expected to develop and conduct training courses at the beginning, intermediate, and advanced levels for NRC staff as well as domestic and international code users.
The NRC has transitioned from RELAP5 to TRACE as its primary thermal-hydraulic analysis tool. As such, RELAP5 code development activities are expected to be at a very low level, limited to bug fixes and porting features from RELAP5 into TRACE, as needed. Support for RELAP5 code maintenance will continue to address CAMP member needs as required by active international agreements.
OBJECTIVE
The contractor shall provide the necessary personnel, management, materials, equipment, administrative and technical services as outlined in this Statement of Work.
The work performed will support the Agency's safety mission by providing high-quality and timely regulatory research, tools, expertise and other technical products that facilitate regulatory decision making and system safety.
SCOPE OF WORK
Tasks under this contract will be accomplished through the issuance of task orders.
Each task order will provide specific levels of effort, deliverables, and a schedule.
Unless otherwise stated, these task areas may apply to any of the following codes:
TRACE, PARCS (both standalone and coupled versions), RELAP5, AVScript, and ACAP, SCALE, TRITON, AGREE, and GENPMAXS. It should be understood that PARCS- related application and development work may involve the development and testing of cross-section libraries and SCALE sequences necessary to support project objectives, as well as the use of commercially available lattice physics codes like HELIOS or CASMO.
The NRC may, at its discretion, issue task orders for work in any of the following areas:
1. Engineering analyses related to code errors, modeling gaps, or deficiencies and document those analyses and their safety significance.
2. Code and/or model development to add new modeling capabilities or features to the codes. This may include the integration of changes developed by others into official code update submittals (including all necessary SQA). All development will be performed according to accepted SQA practices.
3. Code and/or model development to change existing modeling capabilities or features in the codes. This may include the integration of changes developed by others into official code update submittals (including all necessary SQA). All development will be performed according to accepted SQA practices.
4. Typical code maintenance activities, such as (but not necessarily limited to) tracking & fixing bugs, version control and configuration management, developing and maintaining installation packages across multiple platforms, and maintaining documentation.
5. Evaluation of new experimental and/or assessment results and make recommendations to the NRC concerning their implementation.
6. Developmental assessment and documentation of (i.e. V&V) the codes against new or existing experimental data. This may involve assessing codes against a wide range of pre-existing test cases in an automated framework and documenting the results in an assessment addendum prior to code release. This may also include reviewing the assessment data base and expanding it with applicable test cases and automated validation frameworks, as appropriate.
7. Have new versions of codes tested or peer reviewed by independent organizations.
8. Maintenance and updates of code documentation, as appropriate. This may include converting documentation to different formats.
9. Specific technical studies and technical support related to the codes as requested by the NRC.
10. Development of input models to address issues that may arise from the NRC review of new or existing reactor designs and generic or safety issues related to operating reactors.
11. Maintenance and improvement of the NRC Data Bank. This may include (but is not limited to) such tasks as
a. Converting raw data to the NRC PIB binary format and arranging for placement into the NRC’s Agency-wide Documentation And Management System (ADAMS)
b. Identifying and acquiring relevant technical reports and reference material for inclusion in the Data Bank
c. Reorganizing electronic files already in the Data Bank to new hierarchical structures
d. Migration of the Data Bank to a version control system
e. Development of a queuing system to allow tracking of the file conversion process
f. Changes to the conversion process or storage format
12. CAMP and Domestic User Group program management. Typical activities would include maintaining a current list of approved users/organizations, organizing and participating in bi-annual CAMP conferences, taking meeting minutes, maintaining a user support site, reviewing in-kind contributions, providing telephone and email assistance to code users, developing and distributing bi-annual newsletters, distributing codes to approved users, establishing CAMP licensing agreements with foreign commercial organizations on NRC’s behalf, and handling invoicing and fee collection for domestic and international organizations.
13. Special development projects designed to improve the capabilities or maintenance of electronic tools used to support code users and the CAMP program.
14. Develop and/or conduct training courses for NRC T/H codes as well as general thermal-hydraulics and reactor safety topics (i.e. LBLOCA, SBLOCA, transients, stability analysis, two-phase flow fundamentals, etc). Training materials may take the form of on-line web-based training videos as opposed to traditional classroom-based learning.
TECHNICAL AND OTHER SPECIAL QUALIFICATIONS REQUIRED
This project requires engineers who have experience (minimal of 5 years) and knowledge (enough to train others) of (a) various versions of TRACE, RELAP5, PARCS, SNAP, TRITON, PATHS, AGREE, GENPMAXS, APTPlot, AVScript, ACAP and the NRC Data Bank, (b) thermal-hydraulic and reactor physics principles, (c) numerical methods,
(d) code uncertainty analysis, and (e) modeling for both transient and accident analyses of both operating and advanced PWRs and BWRs, as well as non-LWR designs. Since analysis using PARCS may involve the generation of cross section libraries, the project will also require engineers skilled in the use of lattice physics codes like SCALE, POLARIS, CASMO and HELIOS. Individuals must also possess strong programming skills in Fortran 90/95/2003/2008/2018, C/C++, and Python. In addition, computer capabilities to perform code development and validation are required. Finally, there must also be diversity in computer hardware availability (specifically, SUN, IBM, Intel (32 & 64 bit), AMD (32 & 64 bit), Linux, Windows, Apple Mac/OSX) and compiler technologies (Compaq Visual Fortran, Intel Visual Fortran, NAG, Lahey. Salford, gfortran, & Absoft) used for compiling and running TRACE by most of the users. Code documentation is generally maintained in variety of formats. Knowledge of software tools such as Word, Framemaker and Latex, as well as skills for efficiently converting between these formats, is required.
The contractor is responsible for assigning technical staff, employees, subcontractors, or specialists who have the required educational background, experience, or combination thereof to meet the technical objectives of the work specified in this statement of work. In addition, the contractor and personnel assigned to this work must be approved for handling and working with proprietary information.
DELIVERABLES
In general, deliverables under this contract may take the form of the following:
1) Code distribution packages appropriate for external dissemination
2) Code update transmittal packages (includes updated source code, executables, patch files, associated scripts, README files, html content, code input and output files, AVScript files, code documentation, reference material, calculation notebooks and any other files necessary for NRC to reproduce the work and reach the same (or similar) conclusions as the contractor.
3) Code assessment transmittal packages (includes code input and output files, patch files, executables, associated scripts, README files, html content, experimental data files, AVScript files, code documentation, analysis reports, reference material, calculation notebooks and any other files necessary for NRC to reproduce the work and reach the same (or similar) conclusions as the contractor.
4) Code versions in source and executable form
5) Software quality assurance documentation
6) Version control files
7) Code input models and associated code outputs
8) Website content
9) License management data
10) Training workshop content (presentations, inputs & outputs, exercises, instructions, executables & scripts, agendas)
11) Periodic bug report status updates and database files
12) Experimental data files in binary or ASCII form
13) Meeting minutes
14) Periodic newsletters
15) Summary reports of independent assessments performed by CAMP participants
16) Presentation materials (other than for training workshops)
17) Letter reports describing any work performed
18) Technical progress reports
19) Financial status reports
The above list is not all-inclusive. Specific deliverables, schedules, and/or milestones appropriate to the task will be developed at the time the task orders are developed.
Unless otherwise stated in the SOW for a task order, categories 1-12 are to be considered special works and are subject to FAR 52.227-17 “Rights in Data – Special Works (DEC 2007)”. FAR 52.227-14 shall apply to data other than special works data generated under this contract.
MEETINGS AND TRAVEL
Meetings and travel requirements will be determined and specified in individual task orders
NRC-FURNISHED MATERIAL
Materials to be furnished by NRC will be determined and specified in individual task orders
CONTRACTOR ACQUIRED EQUIPMENT/PROPERTY
The contractor may purchase, upon the NRC Contracting Officer's approval, high performance workstations, and/or upgrade or replace existing computer hardware as needed during the period of the contract to assure that the codes properly utilize state-of-the-art workstation capabilities and to maintain compatibility with the workstations used by NRC, its contractors and CAMP members. Identification of upgrade and/or replacement hardware shall be presented to the NRC Contracting Officer and Project Manager and purchases made only after prior written approval of the NRC Contracting Officer. The contractor shall provide a written request each year to the NRC Contracting Officer and Project Manager as to the equipment and/or any upgrades required for the performance of this contract.
(To be specified in each Task Order.)
SECTION D - Packaging and Marking
D.1 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 Regulation, under Contract/order number incorporated into resultant contract.
(End of Clause)
D.2 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.
(End of Clause)
SECTION E - Inspection and Acceptance
E.1 Clauses
The following contract clauses pertinent to this section are hereby incorporated by reference (by Citation Number, Title, and Date) in accordance with the clause at FAR "52.252-2 CLAUSES INCORPORATED BY REFERENCE" in Section I of this contract.
See FAR 52.252-2 for an internet address (if specified) for electronic access to the full text of a clause.
NUMBER TITLE DATE
FEDERAL ACQUISITION REGULATION (48 CFR Chapter1)
52.246-5 INSPECTION OF SERVICES--COST-REIMBURSEMENT
(APR 1984)
E.2 QUALITY ASSURANCE
Section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001 (Public Law 106-554) directs the Office of Management and Budget (OMB) to issue government-wide guidelines (FR Vol. 67, No. 36, pp. 8452-8460) that “provide policy and procedural guidance to federal agencies for ensuring and maximizing the quality, objectivity, utility, and integrity of information (including statistical information) disseminated by federal agencies.” NRC Information Quality Guidelines are provided in FR Vol. 67, No. 190, pp. 61695-61699.
The Contractor shall cite contractor quality assurance procedures to be used in the conduct of this work that provide for compliance with OMB and NRC. With regard to the code development and maintenance activities outlined above, this should, at a minimum, include accepted software quality assurance (QA) procedures, as set forth in NUREG/BR-0167 “Software Quality Assurance Program and Guidelines”, and NUREG- 1737, "Software Quality Assurance Procedures for NRC Thermal Hydraulic Codes" (See Section L.11).
E.3 RESEARCH QUALITY
The quality of NRC research programs are assessed each year by the Advisory Committee on Reactor Safeguards. Within the context of their reviews of RES programs, the definition of quality research is based upon several major characteristics:
Results meet the objectives (75% of overall score) Justification of major assumptions (12%) Soundness of technical approach and results (52%) Uncertainties and sensitivities addressed (11%)
Documentation of research results and methods is adequate (25% of overall score) Clarity of presentation (16%) Identification of major assumptions (9%)
It is the responsibility of the contractor to ensure that these quality criteria are adequately addressed throughout the course of the research that is performed. The NRC COR will review all research products with these criteria in mind.
SECTION F - Deliveries or Performance
F.1 NOTICE LISTING CONTRACT CLAUSES INCORPORATED BY REFERENCE
The following contract clauses pertinent to this section are hereby incorporated by reference (by Citation Number, Title, and Date) in accordance with the clause at FAR "52.252-2 CLAUSES INCORPORATED BY REFERENCE" in Section I of this contract.
NUMBER TITLE DATE
52.242-15 STOP-WORK ORDER AUG 1989
ALTERNATE I (APR 1984)
52.247-34 F.O.B. DESTINATION NOV 1991
F.2 2052.211-70 PREPARATION OF TECHNICAL REPORTS (JAN 1993)
All technical reports required by Section C and all Technical Progress Reports required by Section F are to be prepared in accordance with the Management Directive 3.7, “NUREG-Series Publications.” Management Directive 3.7 is not applicable to any Contractor Spending Plan (CSP) and any Financial Status Report that may be included in this contract.
F.3 PERIOD OF PERFORMANCE ALTERNATE IV
The ordering period for this contract shall commence on Day of Award and will expire on one year thereafter. Any orders issued during this period shall be completed within the time specified in the order, unless otherwise specified herein. (See 52.216-18 - Ordering.) The term of this contract may be extended at the option of the Government for an additional four 1-year options.
Base Period: 12 Months
Option Period 1: 12 Months
Option Period 2: 12 Months
Option Period 3: 12 Months
Option Period 4: 12 Months
(End of Clause)
F.4 PLACE OF DELIVERY-REPORTS
The items to be furnished hereunder shall be delivered, with all charges paid by the Contractor, to:
a. Name: Incorporated into resultant contract (1 hard copy)
b. Contracting Officer’s Representative (COR)
c. U.S. Nuclear Regulatory Commission
d. Address:
e. Electronic copies to: NRC Contracting Officer
NRC Contracting Officer’s Representative
SECTION G - Contract Administration Data
G.1 2052.215-71 CONTRACTING OFFICER REPRESENTATIVE (COR) (NOVEMBER
2006)
(a) The contracting officer's authorized representative (hereinafter referred to as the COR) for this contract is:
Name: Incorporated into resultant contract
(b) Performance of the work under this contract is subject to the technical direction of the NRC COR. The term "technical direction" is defined to include the following:
(1) Technical direction to the contractor which shifts work emphasis between areas of work or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work (SOW) or changes to specific travel identified in the SOW), fills in details, or otherwise serves to accomplish the contractual SOW.
(2) Provide advice and guidance to the contractor in the preparation of drawings, specifications, or technical portions of the work description.
(3) Review and, where required by the contract, approval of technical reports, drawings, specifications, and technical information to be delivered by the contractor to the Government under the contract.
(c) Technical direction must be within the general statement of work stated in the contract. The COR does not have the authority to and may not issue any technical direction which:
(1) Constitutes an assignment of work outside the general scope of the contract.
(2) Constitutes a change as defined in the "Changes" clause of this contract.
(3) In any way causes an increase or decrease in the total estimated contract cost, the fixed fee, if any, or the time required for contract performance.
(4) Changes any of the expressed terms, conditions, or specifications of the contract.
(5) Terminates the contract, settles any claim or dispute arising under the contract, or issues any unilateral directive whatever.
(d) All technical directions must be issued in writing by the COR or must be confirmed by the COR in writing within ten (10) working days after verbal issuance. A copy of the written direction must be furnished to the contracting officer. A copy of NRC Form 445, Request for Approval of Official Foreign Travel, which has received final approval from the NRC must be furnished to the contracting officer.
(e) The contractor shall proceed promptly with the performance of technical directions duly issued by the COR in the manner prescribed by this clause and within the COR's authority under the provisions of this clause.
(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-1 - Disputes.
(i) In addition to providing technical direction as defined in paragraph (b) of the section, the COR shall:
(1) Monitor the contractor's technical progress, including surveillance and assessment of performance, and recommend to the contracting officer changes in requirements.
(2) Assist the contractor in the resolution of technical problems encountered during performance.
(3) Review all costs requested for reimbursement by the contractor and submit to the contracting officer recommendations for approval, disapproval, or suspension of payment for supplies and services required under this contract.
(4) Assist the contractor in obtaining the badges for the contractor personnel.
(5) Immediately notify the Security Branch, Division of Facilities and Security (SB/DFS) (via e-mail) when a contractor employee no longer requires access authorization and return of any NRC issued badge to SB/DFS within three days after their termination.
(6) Ensure that all contractor employees that require access to classified Restricted Data or National Security Information or matter, access to sensitive unclassified information (Safeguards, Official Use Only, and Proprietary information) access to sensitive IT systems or data, unescorted access to NRC controlled buildings/space, or unescorted access to protected and vital areas of nuclear power plants receive approval of SB/DFS prior to access in accordance with Management Directive and Handbook 12.3.
(7) For contracts for the design, development, maintenance or operation of Privacy Act Systems of Records, obtain from the contractor as part of closeout procedures, written certification that the contractor has returned to NRC, transferred to the successor contractor, or destroyed at the end of the contract in accordance with instructions provided by the NRC Systems Manager for Privacy Act Systems of Records, all records (electronic or paper) which were created, compiled, obtained or maintained under the contract.
(End of Clause)
G.2 2052.215-77 TRAVEL APPROVALS AND REIMBURSEMENT. (OCT 1999)
(a) All foreign travel must be approved in advance by the NRC on NRC Form 445, Request for Approval of Official Foreign Travel, and must be in compliance with FAR 52.247-63 Preference for U.S. Flag Air Carriers. The contractor shall submit NRC Form 445 to the NRC no later than 30 days before beginning travel.
(b) The contractor must receive written approval from the NRC Project Officer before taking travel that was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work, or changes to specific travel identified in the Statement of Work).
(c) The contractor will be reimbursed only for travel costs incurred that are directly related to this contract and are allowable subject to the limitations prescribed in FAR 31.205-46.
(d) It is the responsibility of the contractor to notify the contracting officer in accordance with the Limitations of Cost clause of this contract when, at any time, the contractor learns that travel expenses will cause the contractor to exceed the estimated costs specified in the Schedule.
(e) Reasonable travel costs for research and related activities performed at State and nonprofit institutions, in accordance with Section 12 of Pub. L. 100-679, must be charged in accordance with the contractor's institutional policy to the degree that the limitations of Office of Management and Budget (OMB) guidance are not exceeded. Applicable guidance documents include OMB Circular A-87, Cost Principles for State and Local Governments; OMB Circular A-122, Cost Principles for Nonprofit Organizations; and OMB Circular A-21, Cost Principles for Educational Institutions.
(End of Clause)
G.3 2052.216-71 INDIRECT COST RATES. (JAN 1993)
(a) Pending the establishment of final indirect rates which must be negotiated based on audit of actual costs, the contractor shall be reimbursed for allowable indirect costs as follows:
Incorporated into resultant contract.
[FAR 31.201-2 Determining allowability and FAR 31.203 Indirect Costs apply to costs incurred by the contractor during the performance of the resultant contract and task orders issued thereunder.]
(b) The contracting officer may adjust these rates as appropriate during the term of the contract upon acceptance of any revisions proposed by the contractor. It is the contractor's responsibility to notify the contracting officer in accordance with FAR
52.232-20, Limitation of Cost, or FAR 52.232-22, Limitation of Funds, as applicable, if these changes affect performance of work within the established cost or funding limitations.
*To be incorporated into any resultant contract.
(End of Clause)
G.4 2052.216-72 TASK ORDER PROCEDURES. (OCT 1999)
(a) Task order request for proposal. When a requirement within the scope of work for this contract is identified, the contracting officer shall transmit to the contractor a Task Order Request for Proposal (TORFP) which may include the following, as appropriate:
(1) Scope of work/meetings/travel and deliverables;
(2) Reporting requirements;
(3) Period of performance - place of performance;
(4) Applicable special provisions;
(5) Technical skills required; and
(6) Estimated level of effort.
(b) Task order technical proposal. By the date specified in the TORFP, the contractor shall deliver to the contracting officer a written or verbal (as specified in the TORFP technical proposal submittal instructions) technical proposal that provides the technical information required by the TORFP.
(c) Cost proposal. The contractor's cost proposal for each task order must be fully supported by cost and pricing data adequate to establish the reasonableness of the proposed amounts. When the contractor's estimated cost for the proposed task order exceeds $100,000 and the period of performance exceeds six months, the contractor may be required to submit a Contractor Spending Plan (CSP) as part of its cost proposal. The TORP indicates if a CSP is required.
(d) Task order award. The contractor shall perform all work described in definitized task orders issued by the contracting officer. Definitized task orders include the following:
(1) Statement of work/meetings/travel and deliverables;
(2) Reporting requirements;
(3) Period of performance;
(4) Key personnel;
(5) Applicable special provisions; and
(6) Total task order amount including any fixed fee.
G.5 2052.216-73 ACCELERATED TASK ORDER PROCEDURES. (JAN 1993)
(a) The NRC may require the contractor to begin work before receiving a definitized task order from the contracting officer. Accordingly, when the contracting officer verbally authorizes the work, the contractor shall proceed with performance of the task order subject to the monetary limitation established for the task order by the contracting officer.
(b) When this accelerated procedure is employed by the NRC, the contractor agrees to begin promptly negotiating with the contracting officer the terms of the definitive task order and agrees to submit a cost proposal with supporting cost or pricing data. If agreement on a definitized task order is not reached by the target date mutually agreed upon by the contractor and contracting officer, the contracting officer may determine a reasonable price and/or fee in accordance with Subpart 15.8 and Part 31 of the FAR, subject to contractor appeal as provided in 52.233-1, Disputes. In any event, the contractor shall proceed with completion of the task order subject only to the monetary limitation established by the contracting officer and the terms and conditions of the basic contract.
(End of Clause)
G.6 ORDERING PROCEDURES FOR MULTIPLE-AWARD INDEFINITE-
DELIVERY/INDEFINITE-QUANTITY CONTRACTS (MAR 2014)
[The contracting officer is responsible for providing further specificity to supplement the standard information contained in the ordering procedures set forth below to address the specific requirements of each contract.]
General.
This clause applies to solicitations and contracts for multiple-award Indefinite-Delivery contracts. For the work specified in the SOW, PWS or SOO, the CO may issue an order to one of the IDC contractors. The contractor agrees that issuance of an order in accordance with any of the procedures described below is deemed to have provided the contractor a “fair opportunity to be considered” as that phrase is used at FAR 16.505(b)(1).
Ordering Process.
Under this RFTOP this agency will follow the procedures set forth in FAR 16.505.
To the extent that the RFTOP requirements or aspects of the proposal that deviate from the government’s requirements and are not within established scope or pricing of the IDC the contractor shall immediately contact the CO for appropriate guidance.
Task/Delivery Order Ombudsman.
To further ensure that all contractors are afforded a fair opportunity to be considered to task or delivery orders pursuant to FAR 16.505, the NRC has an Ombudsman. The purpose of the Ombudsman is not to diminish the authority of the CO, but to receive on behalf of and to communicate to the appropriate Government personnel concerns and disagreements of contractors not receiving a specific order and to work to resolve the matter. When requested, the Ombudsman will maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the original selection of contractors or in the evaluation or determination of the issuance of task or delivery orders under the applicable IDC contract. He/She does not act in the capacity of a CO and does not participate in the adjudication of contract disputes in regard to multiple award task or delivery order contracts awarded pursuant to FAR Subpart 16.5.
Interested parties may contact the Ombudsman with concerns or disagreements. Issues or concerns to the NRC task/delivery order Ombudsman may be forwarded to:
U.S. Nuclear Regulatory Commission
Acquisition Management Division
Attn: Ombudsman
Washington, DC 20555
G.7 REGISTRATION IN FEDCONNECT® (JULY 2014)
The Nuclear Regulatory Commission (NRC) uses Compusearch Software Systems’ secure and auditable two-way web portal, FedConnect®, to communicate with vendors and contractors. FedConnect® provides bi-directional communication between the vendor/contractor and the NRC throughout pre-award, award, and post-award acquisition phases. Therefore, in order to do business with the NRC, vendors and contractors must register to use FedConnect® at https://www.fedconnect.net/FedConnect. The individual registering in FedConnect® must have authority to bind the vendor/contractor. There is no charge for using FedConnect®. Assistance with FedConnect® is provided by Compusearch Software Systems, not the NRC. FedConnect® contact and assistance information is provided on the FedConnect® web site at https://www.fedconnect.net/FedConnect.
G.8 ELECTRONIC PAYMENT (DEC 2017)
The Debt Collection Improvement Act of 1996 requires that all payments except IRS tax refunds be made by Electronic Funds Transfer. Payment shall be made in accordance with FAR 52.232-33, entitled “Payment by Electronic Funds Transfer-System for Award Management.”
To receive payment, the contractor shall prepare invoices in accordance with NRC’s Billing Instructions. Claims shall be submitted through the Invoice Processing Platform (IPP) (https://www.ipp.gov/). Back up documentation shall be included as required by the NRC’s Billing Instructions.
SECTION H - Special Contract Requirements
H.1 2052.204-70 SECURITY. (OCT 1999)
As prescribed at 2004.404(a), the contracting officer shall insert the following clause in solicitations and contracts during which the contractor may have access to, or contact with classified information, including National Security information, restricted data, formerly restricted data, and other classified data:
SECURITY (OCT 1999)
(a) Security/Classification Requirements Form. The attached NRC Form 187 (See List of Attachments) furnishes the basis for providing security and classification requirements to prime contractors, subcontractors, or others (e.g., bidders) who have or may have an NRC contractual relationship that requires access to classified information or matter, access on a continuing basis (in excess of 90 or more days) to NRC Headquarters controlled buildings, or otherwise requires NRC photo identification or card-key badges.
(b) It is the contractor's duty to safeguard National Security Information, Restricted Data, and Formerly Restricted Data. The contractor shall, in accordance with the Commission's security regulations and requirements, be responsible for safeguarding National Security Information, Restricted Data, and Formerly Restricted Data, and for protecting against sabotage, espionage, loss, and theft, the classified documents and material in the contractor's possession in connection with the performance of work under this contract. Except as otherwise expressly provided in this contract, the contractor shall transmit to the Commission any classified matter in the possession of the contractor or any person under the contractor's control in connection with performance of this contract upon completion or termination of this contract.
(1) The contractor shall complete a certificate of possession to be furnished to the Commission…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.