RFP-NRC-04-10-127 FINAL.pdf

Jeffrey R. Mitchell /s/

1. THIS CONTRACT IS A RATED ORDER RATING PAGE OF PAGES

UNDER DPAS (15 CFR 700)

2. CONTRACT NUMBER 3. SOLICITATION NUMBER 4. TYPE OF SOLICITATION 5. DATE ISSUED 6. REQUISITION/PURCHASE NUMBER

SEALED BID (IFB)

NEGOTIATED (RFP)

7. ISSUED BY CODE 8. ADDRESS OFFER TO (If other than Item 7)

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

9. Sealed offers in original and _____________________________ copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in until local time _______________________ (Hour) (Date)

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.

A. NAME B. TELEPHONE (NO COLLECT CALLS) C. E-MAIL ADDRESS

AREA CODE NUMBER EXT.

(X) SEC. DESCRIPTION PAGE(S) (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

A SOLICITATION/CONTRACT FORM I CONTRACT CLAUSES

B SUPPLIES OR SERVICES AND PRICES/COSTS PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

C DESCRIPTION/SPECS./WORK STATEMENT J LIST OF ATTACHMENTS

D PACKAGING AND MARKING PART IV - REPRESENTATIONS AND INSTRUCTIONS

E INSPECTION AND ACCEPTANCE

F DELIVERIES OR PERFORMANCE

G CONTRACT ADMINISTRATION DATA L INSTR., CONDS., AND NOTICES TO OFFERORS

H SPECIAL CONTRACT REQUIREMENTS M EVALUATION FACTORS FOR AWARD

K

REPRESENTATIONS, CERTIFICATIONS AND OTHER

STATEMENTS OF OFFERORS

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within ________ calendar days (60 calendar days unless a different period is inserted 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 designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT 10 CALENDAR DAYS (%) 20 CALENDAR DAYS (%) 30 CALENDAR DAYS (%) CALENDAR DAYS (%)

(See Section I, Clause No. 52-232-8)

14. ACKNOWLEDGEMENT OF AMENDMENTS AMENDMENT NO. DATE AMENDMENT NO. DATE

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated:

CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER 15A. NAME AND

ADDRESS

OF OFFEROR

(Type or print)

15B. TELEPHONE NUMBER 17. SIGNATURE 18. OFFER DATE

AREA CODE NUMBER EXT.

15C. CHECK IF REMITTANCE ADDRESS IS DIFFERENT FROM

ABOVE - ENTER SUCH ADDRESS IN SCHEDULE

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION: 23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM (4 copies unless otherwise specified)

10 U.S.C. 2304(a) ( ) 41 U.S.C. 253(c) ( )

24. ADMINISTERED BY (If other than Item 7) 25. PAYMENT WILL BE MADE BY CODE CODE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

(Signature of Contracting Officer)

(REV. 9-97)

10. FOR INFORMATION CALL:

11. TABLE OF CONTENTS

AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 33

Previous edition is unusable Prescribed by GSA-FAR (48 CFR) 53.214(c)

SOLICITATION, OFFER AND AWARD

SOLICITATION

OFFER (Must be fully completed by offeror)

AWARD (To be completed by Government)

1 N/A 71

RFP-NRC-04-10-127

X

U.S. Nuclear Regulatory Commission Div. of Contracts Attn: Jeffrey R. Mitchell, 301-492-3639 Mail Stop: TWB-01-B10M Washington, DC 20555

Item 7 4:00 PM EST October 12, 2010

Jeffrey R. Mitchell 301-492-3639 jeffrey.mitchell@nrc.gov

See Attached Table of Contents

U.S. Nuclear Regulatory Commission Div. of Contracts Mail Stop: TWB-01-B10M

Washington, DC 20555

Department of Interior / NBC NRCPayments@nbc.gov Attn: Fiscal Services Branch - D2770 7301 W. Mansfield Avenue Denver CO 80235-2230

Table of Contents

PART I - THE SCHEDULE ............................................................................................................... A-1

SECTION A - SOLICITATION/CONTRACT FORM ......................................................................... A-1

SF 33 SOLICITATION, OFFER AND AWARD .....................................................................A-1

PART I - THE SCHEDULE ............................................................................................................... B-1

SECTION B - SUPPLIES OR SERVICES AND PRICE/COSTS ...................................................... B-1

B.1 PROJECT TITLE ...............................................................................................................B-1 B.2 BRIEF DESCRIPTION OF WORK (MAR 1987) ALTERNATE 1 (JUN 1988) ...................B-1

B.3 CONSIDERATION AND OBLIGATION--TASK ORDERS (AUG 1989) ALTERNATE 1

(JUN 1991) ........................................................................................................................B-1

B.4 SCHEDULE OF COST………………………………………………………………………….B-1

SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK .............................. C-- 2 -

C.1 STATEMENT OF WORK ............................................................................................. C-- 2 -

SECTION D - PACKAGING AND MARKING .................................................................................. D-1

D.1 PACKAGING AND MARKING (MAR 1987) ..................................................................... D-1

SECTION E - INSPECTION AND ACCEPTANCE ............................................................................E-1

E.1 NOTICE LISTING CONTRACT CLAUSES INCORPORATED BY REFERENCE ............E-1

E.2 PLACE OF INSPECTION AND ACCEPTANCE (MAR 1987) ...........................................E-1

SECTION F - DELIVERIES OR PERFORMANCE ............................................................................ F-1

F.1 NOTICE LISTING CONTRACT CLAUSES INCORPORATED BY REFERENCE ............ F-1

F.2 2052.211-70 PREPARATION OF TECHNICAL REPORTS (JAN 1993) ........................ F-1 F.3 2052.211-71 TECHNICAL PROGRESS REPORT (JAN 1993) ...................................... F-1 F.4 2052.211-72 FINANCIAL STATUS REPORT (OCT 1999) ............................................. F-2 F.5 PLACE OF DELIVERY--REPORTS (JUN 1988) ............................................................... F-3 F.6 DURATION OF CONTRACT PERIOD (MAR 1987) ALTERNATE 1 (JUN 1988) ............. F-3

SECTION G - CONTRACT ADMINISTRATION DATA .................................................................... G-1

G.1 2052.215-71 PROJECT OFFICER AUTHORITY (NOVEMBER 2006) .............................. G-1 G.2 2052.215-77 TRAVEL APPROVALS AND REIMBURSEMENT (OCT 1999) ................ G-2 G.3 2052.216-71 INDIRECT COST RATES (JAN 1993) ..................................................... G-3 G.4 2052.216-72 TASK ORDER PROCEDURES (OCT 1999) ............................................ G-3 G.5 2052.216-73 ACCELERATED TASK ORDER PROCEDURES (JAN 1993) ................. G-4 G.6 ORDERING PROCEDURES (MAY 1991) ....................................................................... G-4

SECTION H - SPECIAL CONTRACT REQUIREMENTS ................................................................. H-1

H.1 CONTRACTOR RESPONSIBILITY……………………………………………………...……H-1

H.2 PROPRIETARY DATA AND SENSITIVE UNCLASSIFIED INFORMATION…….….…..H-1

H.3 COPYRIGHT OF CODES – SPECIAL NUCLEAR PURPOSE LICENSE…………………H.1

H.4 2052.204-71 BADGE REQUIREMENTS FOR UNESCORTED BUILDING ACCESS TO

NRC FACILITIES (MAR 2006) ......................................................................................... H-1

H.5 2052.209-72 CONTRACTOR ORGANIZATIONAL CONFLICTS OF INTEREST (JAN

1993) ................................................................................................................................ H-2

H.6 2052.215-70 KEY PERSONNEL (JAN 1993) ................................................................ H-4 H.7 2052.235-70 PUBLICATION OF RESEARCH RESULTS (OCT 1999) ......................... H-5

H.8 2052.242-70 RESOLVING NRC CONTRACTOR DIFFERING PROFESSIONAL

OPINIONS (AUG 2007) ................................................................................................... H-5

H.9 2052.242-71 PROCEDURES FOR RESOLVING NRC CONTRACTOR DIFFERING

PROFESSIONAL OPINIONS (OCT 1999) .................................................................... H-6

H.10 2052.204.70 SECURITY (MAR 2004) ............................................................................ H-7

H.11 SECURITY REQUIREMENTS FOR INFORMATION TECHNOLOGY LEVEL I OR LEVEL

II ACCESS APPROVAL (JUL 2007) ................................................................................ H-9

H.12 GOVERNMENT FURNISHED EQUIPMENT/PROPERTY - NONE PROVIDED (JUN

1988) .............................................................................................................................. H-11 H.13 SEAT BELTS ............................................................................................................... H-11 H.14 Annual and Final Contractor Performance Evaluations ............................................... H-12 H.15 Compliance with U.S. Immigration Laws and Regulations ........................................... H-12

H.16 NRC INFORMATION TECHNOLOGY SECURITY TRAINING (AUG 2003) ............. H-12

H.17 SECURITY REQUIREMENTS RELATING TO THE PRODUCTION OF REPORT(S) OR

THE PUBLICATION OF RESULTS UNDER CONTRACTS, AGREEMENTS, AND

GRANTS ........................................................................................................................ H-13

H.18 WHISTLEBLOWER PROTECTION FOR NRC CONTRACTOR AND SUBCONTRACTOR

EMPLOYEES (JULY 2006) ............................................................................................ H-14

PART II - CONTRACT CLAUSES ................................................................................................... I-1

SECTION I - CONTRACT CLAUSES ............................................................................................ I-1

I.1 NOTICE LISTING CONTRACT CLAUSES INCORPORATED BY REFERENCE .............. I-1

I.2 52.215-23 LIMITATIONS ON PASS-THROUGH CHARGES (OCT 2009) .......................... I-3 I.3 52.216-7 ALLOWABLE COST AND PAYMENT (DEC 2002) ......................................... I-4 I.4 52.216-18 ORDERING (OCT 1995) ................................................................................ I-7 I.5 52.216-19 ORDER LIMITATIONS (OCT 1995) ............................................................... I-7 I.6 52.216-22 INDEFINITE QUANTITY (OCT 1995) ............................................................ I-8

I.7 52.219-28 POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION (APR

2009) .................................................................................................................................. I-8 I.8 52.222-54 EMPLOYMENT ELIGIBILITY VERIFICATION (JAN 2009) ................................ I-9 I.9 52.249-14 EXCUSABLE DELAYS (APR 1984) ............................................................. I-12 I.10 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998) ...................... I-12

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS ............................... J-1

SECTION J - LIST OF ATTACHMENTS ........................................................................................... J-1

PART IV - REPRESENTATIONS AND INSTRUCTIONS ............................................................ K-1

SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF

OFFERORS ............................................................................................................................. K-1

K.1 52.204-8 ANNUAL REPRESENTATIONS AND CERTIFICATIONS (FEB 2009) ...........K-1

K.2 52.227-15 REPRESENTATION OF LIMITED RIGHTS DATA AND RESTRICTED

COMPUTER SOFTWARE (DEC 2007) ..........................................................................K-4

K.3 52.230-1 COST ACCOUNTING STANDARDS NOTICES AND CERTIFICATION (OCT

2008) .................................................................................................................................K-4

K.4 52.230-7 PROPOSAL DISCLOSURE--COST ACCOUNTING PRACTICE CHANGES

(APR 2005) .......................................................................................................................K-7

K.5 2052.209-70 CURRENT/FORMER AGENCY EMPLOYEE INVOLVEMENT (OCT 1999)K-7

K.6 2052.209-71 CONTRACTOR ORGANIZATIONAL CONFLICTS OF INTEREST

(REPRESENTATION) (OCT 1999) ...................................................................................K-7

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS ........................... L-1

L.1 NOTICE LISTING SOLICITATION PROVISIONS INCORPORATED BY REFERENCE .. L-1

L.2 52.215-20 REQUIREMENTS FOR COST OR PRICING DATA OR INFORMATION

OTHER THAN COST OR PRICING DATA (OCT 1997) ................................................... L-1

L.3 52.215-22 LIMITATIONS ON PASS-THROUGH CHARGES--IDENTIFICATION OF

SUBCONTRACT EFFORT (OCT 2009) ........................................................................... L-2 L.4 52.216-1 TYPE OF CONTRACT (APR 1984) ............................................................... L-2 L.5 52.233-2 SERVICE OF PROTEST (SEP 2006) ............................................................ L-2

L.6 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB

1998) ................................................................................................................................. L-3 L.7 2052.215-72 TIMELY RECEIPT OF PROPOSALS (OCT 1999) ..................................... L-3

L.8 2052.215-73 AWARD NOTIFICATION AND COMMITMENT OF PUBLIC FUNDS (OCT

1999) ................................................................................................................................. L-3 L.9 2052.215-74 DISPOSITION OF PROPOSALS (JAN 1993) ............................................ L-4 L.10 2052.216-70 LEVEL OF EFFORT (JAN 1993) .............................................................. L-4 L.11 2052.222-70 NONDISCRIMINATION BECAUSE OF AGE (JAN 1993) ........................ L-4 L.12 ESTIMATED DURATION (JUN 1988) ............................................................................. L-5

L.13 USE OF AUTOMATED CLEARING HOUSE (ACH) ELECTRONIC

PAYMENT/REMITTANCE ADDRESS .............................................................................. L-5 L.14 2052.215-78 PROPOSAL PRESENTATION AND FORMAT-ALTERNATE 1 (Language for Negotiated Task Order Contracts) ............................................................................... L-5

SECTION M - EVALUATION FACTORS FOR AWARD .................................................................. M-1

M.1 2052.215-79 CONTRACT AWARD AND EVALUATION OF PROPOSALS (OCT 1999)M-1

M.2 EVALUATION CRITERIA…………………………………………………………………….M-2

RFP-NRC-04-10-127 Section B

B-1

PART I - THE SCHEDULE

SECTION B - SUPPLIES OR SERVICES AND PRICE/COSTS

B.1 PROJECT TITLE

The title of this project is as follows:

CODE APPLICATIONS FOR REACTOR SYSTEMS (CARS)

B.2 BRIEF DESCRIPTION OF WORK (MAR 1987) ALTERNATE 1 (JUN 1988)

(a) Brief description of work:

The contractor shall perform code improvements/upgrading, perform code assessment, demonstrate code applicability for new designs, perform technical studies, and provide support related to maintained codes.

(b) Orders will be issued for work required by the NRC in accordance with 52.216-18 - Ordering. Only Contracting Officers of the NRC or other individuals specifically authorized under this contract may authorize the initiation of work under this contract. The provisions of this contract shall govern all orders issued hereunder.

B.3 CONSIDERATION AND OBLIGATION--TASK ORDERS (AUG 1989) ALTERNATE 1 (JUN 1991)

(a) The Maximum Ordering Limitation (MOL) for products and services ordered, delivered and accepted under this contract is 29,250 professional hours. The Contracting Officer may place orders with the contractor during the contract period provided the aggregate amount of such orders does not exceed the MOL.

(b) The guaranteed minimum obligated by the Government under this contract is 100 professional hours.

(c) A total estimated cost as well as any 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 52.232-20 - Limitation of Cost for fully funded task orders and 52.232-22 - Limitation of Funds for incrementally funded task orders, issued hereunder.

B.4 SCHEDULE OF COST

CLIN DESCRIPTION REIMBURSABLE

COST

FIXED FEE TOTAL COST

PLUS FIXED FEE

001 YEAR ONE (1)

DURATION: 12 MONTHS FROM

DAY OF AWARD **

002 YEAR TWO (2)

DURATION: 12 MONTHS

003 YEAR THREE (3)

DURATION: 12 MONTHS

TOTAL ESTIMATED COST PLUS FIXED

FEE

**An award is estimated to be made in November 2010.

B-- 2 -

SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

TITLE: Code Applications for Reactor Systems (CARS)

BACKGROUND

The U.S. Nuclear Regulatory Commission (NRC) uses computer codes and analytical methods to perform systems analyses of currently operating reactors, new reactors, and advanced reactor designs. The Office of Nuclear Regulatory Research (RES) uses these tools and methods to support the Office of Nuclear Reactor Regulation (NRR) and the Office of New Reactors (NRO) in identifying and resolving safety issues, making regulatory decisions, and promulgating regulations and guidance.

NRC’s tools and methods cover a range of technical fields including thermal-hydraulics, computational fluid dynamics (CFD), neutronics, severe accidents, and fuel behavior. The principal codes used for reactor system analyses in these technical areas are the TRAC/RELAP Advanced Computational Engine (TRACE) code, Reactor Excursion and Leak Analysis Program (RELAP5), Symbolic Nuclear Analysis Package (SNAP), Purdue Advanced Reactor Core Simulator (PARCS), Severe Core Damage Analysis Program (SCDAP), Radionuclide Transport and Removal and Dose Estimation (RADTRAD), Computer Code for Nuclear Reactor Containment Analysis (CONTAIN), FLUENT, FRAPCON, FRAPTRAN, and MELCOR.

These codes currently are used to support the licensing review of new and advanced reactor designs including the Economic Simplified Boiling-Water Reactor (ESBWR), U.S. EPR (EPR), Advanced Passive Reactor (AP1000), U.S. Advanced Pressurized Power Reactor (US-APWR), and the Advanced Boiling-Water Reactor (ABWR). These codes also are used to perform reviews of extended power uprate applications for operating reactors, resolve generic safety issues, evaluate emergency procedures and accident management strategies, and evaluate success criteria for probabilistic risk assessments.

An integral part of applying advanced computational methods is ensuring that the codes are applicable to each novel simulation. This is particularly important when codes are exercised for new operating conditions, geometries, and/or plant features. Therefore, code applications to plant transients are often accompanied by extensive code assessments against separate effect and integral test data. Moreover, as codes evolve because of new requirements and advancements in the state-of-the-art, simulations and assessments are maintained to ensure that analytical tools and models remain current.

OBJECTIVE

The objective of this contract is to obtain contractor technical assistance in:

Performing confirmatory and exploratory code simulations.

o Conducting scoping analyses, sensitivity and uncertainty studies. Assessing the codes against experimental data, including evaluating scaling considerations to determine the applicability of the codes to simulate the relevant phenomena.

RFP-NRC-04-10-127 Section C

C-2 o Recommending modifications to existing codes and methods.

o Organizing technical meetings and workshops.

The contractor shall provide competent, qualified, and fully-trained labor; supervision and project management support; materials including manuals and schematics; equipment; and transportation necessary to accomplish the tasks of the statement of work.

SCOPE OF WORK

This contract covers all currently operating reactor types as well as new and advanced reactor designs. Technical assistance is sought for simulations and analyses that include normal operations, anticipated operational occurrences, design basis accidents, and beyond-design basis accidents. Technical expertise is required in the following fields—thermal-hydraulics, CFD, neutronics, severe accidents, and fuel behavior. This contract includes, but is not limited to the following computer codes—TRACE, RELAP5, SNAP, PARCS, SCDAP, RADTRAD, CONTAIN, FLUENT, FRAPCON, FRAPTRAN, and MELCOR, hereafter referred to as the “codes.”

All functions of this contract will be accomplished through the issuance of task orders. Each task order will provide specific levels of effort, deliverables, and a schedule.

NRC may issue task orders for work in some or all of the following areas:

1. Confirmatory loss-of-coolant-accident (LOCA) simulations or transient analyses for extended power uprates in currently operating Westinghouse, Combustion Engineering, and Babcock and Wilcox pressurized-water reactors (PWRs) and General Electric boiling-water reactors (BWRs).

2. Confirmatory code simulations for the review of new and advanced reactor designs, such as ESBWR, EPR, AP1000, US-APWR, and the ABWR.

3. Exploratory code simulations to support rulemaking such as those done in support of revisions to 10 CFR 50.61

(pressurized thermal shock) or 10 CFR 50.46 (large-break LOCA).

4. Scoping analyses and preliminary calculations toward the identification and resolution of generic safety issues such as GSI-185: Control of Recriticality Following Small-Break LOCAs in PWRs and GSI-191: Assessment of Debris Accumulation on PWR Sump Performance.

5. Sensitivity and uncertainty studies to examine the response of plants and plant systems to variabilities in boundary conditions and key parameters such as time of operator action, fuel burnup, and the gap conductance model.

6. Evaluation of experimental data including scaling adequacy and the applicability of the data to specific reactor designs and transients, such as the use of data from the Rig-of-Safety Assessment facility to assess TRACE for the AP1000.

7. Scoping studies to assess specific code model improvements to enhance applicability for specific models such as using the CONTAIN component of the TRACE code in simulating BWRs.

8. Code assessments against data collected in separate effect and integral effect test facilities such as experimental data to establish code accuracy, limitations, and range of applicability such as those conducted for the developmental assessment of TRACE 5.0.

9. Demonstration of code applicability to scenarios involving novel geometries or operating characteristics such as the passive systems of the ESBWR or the reflux-condensation operation of EPR steam generators.

C-3

10. Development of phenomena identification and ranking tables for simulations of reactor systems and transients that extend beyond the validated range of conditions.

11. Targeted technical studies for new systems such as the CFD studies on flow rate and cavitation in the advanced accumulators of the US-APWR or the boron injection system of the ESBWR.

12. Multidisciplinary investigations such as those involving integration of thermal-hydraulic, severe accident, fuel response, and CFD analyses, such as those used to support resolution of the steam generator thermally-induced rupture containment bypass scenario.

13. Organization of technical meetings and workshops to bring together experts for multidisciplinary research or the conduct of peer reviews such as the evaluation of global safety margins and the review of TRACE 5.0.

RESEARCH QUALITY

The Advisory Committee on Reactor Safeguards (ACRS) assesses the quality of NRC research programs each year.

Within the context of its reviews of RES programs, the definition of quality research is based upon several major characteristics:

Results meet the objectives (75 percent of overall score).

o Justification of major assumptions (12 percent).

o Soundness of technical approach and results (52 percent).

o Uncertainties and sensitivities addressed (11 percent).

Documentation of research results and methods is adequate (25 percent of overall score).

o Clarity of presentation (16 percent).

o Identification of major assumptions (9 percent).

The contractor is responsible for ensuring that these quality criteria are adequately addressed throughout the course of the research that is performed. The NRC project manager and technical monitor will review all research products with these criteria in mind.

TECHNICAL AND OTHER SPECIAL QUALIFICATIONS REQUIRED

This project requires analysts who have experience and knowledge of the applicable versions of the codes including fuel behavior, thermal-hydraulic and reactor physics principles, CFD, severe accident tools and methods, numerical methods, neutronics, and modeling for both transient and accident analyses of operating new and advanced reactors including PWRs and BWRs. In addition, the project requires computer capabilities to perform code development and validation. Finally, experience and knowledge of computer hardware and the compiler technologies used for compiling and running the codes also are 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. NRC will rely on the contractor to verify the qualifications of the personnel assigned to this contract including assurance that all information contained in the technical and cost proposals (including resumes) is accurate and truthful.

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

For any work to be subcontracted or performed by consultants, the contractor shall obtain the NRC project manager’s written approval of the subcontractor or consultant prior to initiation of the subcontract effort. Conflict-of-interest considerations shall apply to any subcontracted effort.

C-4

REPORTING REQUIREMENTS LOCATION

Resource Name: RESDSAMLSR.Resource@nrc.gov

PUBLICATIONS NOTE

RES encourages the publication of the scientific results from RES-sponsored programs in refereed scientific and engineering journals as appropriate. If the contractor proposes to publish in the open literature or to present the information at meetings in addition to submitting the required technical reports, prior approval of the proposed article or presentation shall be obtained from the NRC project manager. The NRC project manager shall approve the material as submitted, approve it subject to NRC-suggested revisions, or disapprove it. In any event, the NRC project manager may disapprove or delay presentation or publication of papers on information that is subject to Commission approval that has not been ruled upon or which has been disapproved. Additional information regarding the publication of NRC-sponsored research is contained in NRC Management Directives 3.7, “NUREG Series Publications,” and 3.9, “NRC Staff and Contractor Speeches, Papers, and Journal Articles on Regulatory and Technical Subjects.”

If the presentation or paper is in addition to the required technical reports and the RES project manager determines that it will benefit the RES project, the project manager may authorize payment of travel and publishing costs, if any, from the project funds. If the project manager determines that the article or presentation would not benefit the RES project, the costs associated with the preparation, presentation, or publication shall be borne by the contractor. For any publication or presentations falling into this category, NRC reserves the right to require that such presentation or publication shall not identify NRC’s sponsorship of the work.

NEW STANDARDS FOR CONTRACTORS WHO PREPARE NUREG-SERIES MANUSCRIPTS

NRC began to capture most of its official records electronically on January 1, 2000. NRC will capture each final NUREG-series publication in its native application; therefore, the Contractor shall submit final manuscripts that have been approved by the NRC project manager in both electronic and camera-ready copy.

All format guidance, as specified in NUREG-0650, Revision 2, will remain the same with one exception. The Contractor shall no longer be required to include the NUREG-series designator on the bottom of each page of the manuscript. NRC will assign this designator when we send the camera-ready copy to the printer and will place the designator on the cover, title page, and spine. The designator for each report will no longer be assigned when the decision to prepare a publication is made. NRC's Publishing Services Branch will inform the NRC project manager for the publication of the assigned designator when the final manuscript is sent to the printer.

For the electronic manuscript, the Contractor shall prepare the text in Microsoft Word, and use any of the following file types for charts, spreadsheets, and the like.

File Types to be Used for NUREG-Series Publications

File Type File Extension

Microsoft®Word® .doc

Microsoft®PowerPoint® .ppt

Microsoft®Excel .xls

Microsoft®Access .mdb

C-5

Portable Document Format .pdf

This list is subject to change if new software packages come into common use at NRC or by our licensees or other stakeholders that participate in the electronic submission process. If a portion of your manuscript is from another source and you cannot obtain an acceptable electronic file type for this portion (e.g., an appendix from an old publication), NRC can, if necessary, create a tagged image file format (file extension .tif) for that portion of your report.

Note that you should continue to submit original photographs that will be scanned because digitized photographs do not print well.

If you choose to publish a compact disk (CD) of your publication, place on the CD copies of the manuscript in both (1) a portable document format (PDF), (2) a Microsoft Word file format, and (3) an Adobe Acrobat Reader, or, alternatively, print instructions for obtaining a free copy of Adobe Acrobat Reader on the back cover insert of the jewel box.

DELIVERABLES/SCHEDULES AND/OR MILESTONES

Deliverables, schedules, and/or milestones will be developed in each task order. The deliverables specified in each task order may differ from other task orders in this contract but may include such items as follows:

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

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

3. Transmittal packages including the following items—input, restart and output files, plot files, AVSCRIPT files, documentation, and calculation notebooks in CD format.

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

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

Three CDs of all specified deliverables shall be sent to the NRC project manager. An electronic copy of Items (4) and

(5) above shall be emailed to the Contracting Officer.

MEETINGS AND TRAVEL

Meetings and travel requirements will be determined and specified in individual task orders.

NRC-FURNISHED MATERIAL

NRC will provide proprietary plant data, input decks and reports, if necessary and available, to the Contractor. All such data, input decks, and reports shall be clearly marked as “Proprietary” and securely stored in a place where they are not available to the general public.

APPROPRIATE USE OF GOVERNMENT FURNISHED INFORMATION TECHNOLOGY

EQUIPMENT AND/OR INFORMATION TECHNOLOGY SERVICES/ACCESS (APRIL 2003)

As part of contract performance, NRC may provide the contractor with information technology (IT) equipment and IT services or IT access as identified in the statement of work or subsequently as identified in the project.

Government-furnished IT equipment, or IT services, or IT access may include but is not limited to computers, copiers, facsimile machines, printers, pagers, software, phones, Internet access and use, and email access and use. The Contractor (including the Contractor's employees, consultants, and subcontractors) shall use the NRC-furnished IT equipment, and/or IT provided services, and/or IT access solely to perform the necessary efforts required under the contract. The Contractor (including the Contractor's employees, consultants, and subcontractors)

C-6 are prohibited from engaging or using the NRC IT equipment and government-provided IT services or IT access for any personal use, misuse, abuses, or any other unauthorized usage.

The Contractor is responsible for monitoring its employees, consultants, and subcontractors to ensure that NRC furnished IT equipment and/or IT services, and/or IT access are not being used for personal use, misused, or abused.

NRC reserves the right to withdraw or suspend the use of its government-furnished IT equipment, IT services and/ or IT access arising from contractor personal usage, or misuse or abuse; and/or to disallow any payments associated with contractor (including the contractor's employees, consultants, and subcontractors) personal usage, misuses or abuses of IT equipment, IT services and/or IT access; and/or to terminate the project arising from violation of this provision.

IT SECURITY REQUIREMENTS

For unclassified information used for the effort, the contractor shall provide an information security categorization document indicating the sensitivity of the information processed as part of this contract if the information security categorization was not provided in the statement of work. The determination shall be made using NIST SP 800-60 and must be approved by CSO.

All work under this contract shall comply with the latest version of all applicable guidance and standards. Individual task orders will reference applicable versions of standards or exceptions as necessary. These standards include, but are not limited to, NRC Management Directive 12.5 Automated Information Security Program, and National Institute of Standards and Technology (NIST) guidance and Federal Information Processing Standards (FIPS), and Committee on National Security Systems (CNSS) policy, directives, instructions, and guidance. This information is available at the following links:

NRC Policies, Procedures and Standards (CSO internal website):

http://www.internal.nrc.gov/CSO/policies.html

All NRC Management Directives (public website):

http://www.nrc.gov/reading-rm/doc-collections/management-directives/

NIST SP and FIPS documentation is located at:

http://csrc.nist.gov/

CNSS documents are located at:

http://www.cnss.gov/

Contractor shall adhere to NRC policies, including but not limited to:

• Computer Security Policy for Encryption of Data at Rest When Outside of Agency Facilities

• Policy for Copying, Scanning, Printing, and Faxing SGI & Classified Information

• Computer Security Information Protection Policy

• Remote Access Policy

• Use of Commercial Wireless Devices, Services, and Technologies Policy

• Laptop Security Policy

• Computer Security Incident Response Policy

When e-mail is used, the Contractors shall only use NRC provided e-mail accounts to send and receive sensitive information (information that is not releasable to the public) or mechanisms to protect the information during transmission to NRC that have been approved by CSO.

C-7

All Contractor employees must sign the NRC Agency Rules of Behavior for Secure Computer Use prior to being granted access to NRC computing resources.

Contractor shall adhere to NRC’s prohibition of use of personal devices to process and store NRC sensitive information.

All work performed at non-NRC facilities shall be in facilities, networks, and computers that have been accredited by NRC for processing information at the sensitivity level of the information being processed.

The contractor shall ensure that the NRC data processed during the performance of this contract shall be purged from all data storage components of the contractor’s computer facility, and the contractor shall retain no NRC data within 30 calendar days after contract is completed. Until all data is purged, the contractor shall ensure that any NRC data remaining in any storage component shall be protected to prevent unauthorized disclosure.

When contractor employees no longer require access to an NRC system, the contractor shall notify the project officer within 24 hours.

Upon contract completion, the contractor shall provide a status list of all NRC system users and shall note if any users still require access to the system to perform work if a follow-on contract or task order has been approved by NRC.

The contractor shall not publish or disclose in any manner, without the Contracting Officer’s written consent, the details of any security controls or countermeasures either designed or developed by the contractor under this contract or otherwise provided by the NRC.

Any IT system used to process NRC sensitive information shall:

• Include a mechanism to require users to uniquely identify themselves to the system before beginning to perform any other actions that the system is expected to provide

• Be able to authenticate data that includes information for verifying the claimed identity of individual users (e.g., passwords)

• Protect authentication data so that it cannot be accessed by any unauthorized user

• Be able to enforce individual accountability by providing the capability to uniquely identify each individual computer system user

Report to appropriate security personnel when attempts are made to guess the authentication data whether inadvertently or deliberately

Any Contractor system being used to process NRC data shall be able to define and enforce access privileges for individual users. The discretionary access control mechanisms shall be configurable to protect objects (e.g., files, folders) from unauthorized access.

The Contractor system being used to process NRC data shall provide only essential capabilities and specifically prohibit and/or restrict the use of specified functions, ports, protocols, and/or services.

The Contractors shall only use NRC approved methods to send and receive information considered sensitive or classified. Specifically, Classified Information - All NRC Classified data being transmitted over a network shall use NSA approved encryption and adhere to guidance in MD 12.2 NRC Classified Information Security Program, MD 12.5 NRC Automated Information Security Program, and Committee on National Security Systems. Classified processing shall be only within facilities, computers, and spaces that have been specifically approved for classified processing.

SGI Information – All SGI being transmitted over a network shall adhere to guidance in MD 12.7 NRC Safeguards Information Security Program and MD 12.5 NRC Automated Information Security Program. SGI

C-8 processing shall be only within facilities, computers, and spaces that have been specifically approved for SGI processing. Cryptographic modules provided as part of the system shall be validated under the Cryptographic Module Validation Program to conform to NIST FIPS 140-2 overall level 2 and must be operated in FIPS mode.

The contractor shall provide the FIPS 140-2 cryptographic module certificate number and a brief description of the encryption module that includes the encryption algorithm(s) used, the key length, and the vendor of the product.

If the effort includes use or processing of classified information, the NRC Contracting Officer and Project Officer shall be notified prior to processing information at a more restrictive classification level.

All system modifications to classified systems shall comply with NRC security policies and procedures for classified systems, as well as federal laws, guidance, and standards to ensure Federal Information Security Management Act (FISMA) compliance.

The most restrictive set of rights/privileges or accesses needed by users (or processes acting on behalf of users) for the performance of specified tasks shall be enforced by the system through assigned access authorizations.

The mechanisms within the Contractor system or application that enforces access control and other security features shall be continuously protected against tampering and/or unauthorized changes.

Separation of duties for Contractor systems used to process NRC information shall be enforced by the system through assigned access authorizations.

All systems used to process NRC sensitive information shall meet NRC configuration standards available at:

http://www.internal.nrc.gov/CSO/standards.html.

All media used by the Contractor to store or process NRC information shall be controlled in accordance to the sensitivity level.

The Contractor shall not perform sanitization or destruction of media approved for processing NRC information designated as SGI or Classified. The Contractor shall provide the media to NRC for destruction.

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

The Contractor shall provide the system requirements traceability matrix at the end of the initiation phase, development/acquisition phase, implementation/assessment phase, operation & maintenance phase, and disposal phase that provides the security requirements in a separate section so that they can be traced through the development life cycle. The Contractor shall also provide the software and hardware designs and test plan documentation, and source code to the NRC for review, upon request.

All development and testing of the systems shall be protected at their assigned system sensitivity level and shall be performed on a network separate and isolated from the NRC operational network.

All system computers shall be properly configured and hardened according to NRC policies, guidance, and standards and shall comply with all NRC security policies and procedures as commensurate with the system security categorization.

All Contractor provided deliverables identified in the project plan shall be subject to the review and approval of NRC Management. The Contractor shall make the necessary modifications to project deliverables to resolve any identified issues. Project deliverables include but are not limited to: requirements, architectures, design documents, test plans, and test reports.

The Contractor shall not hardcode any passwords into the software unless the password only appears on the server side (e.g. using server-side technology such as ASP, PHP, or JSP).

C-9

The Contractor shall ensure that the software does not contain undocumented functions and undocumented methods for gaining access to the software or to the computer system on which it is installed. This includes, but is not limited to, master access keys, back doors, or trapdoors.

Cryptographic modules provided as part of the system shall be validated under the Cryptographic Module Validation Program to conform to NIST FIPS 140-2 and shall be operated in FIPS mode. The Contractor shall provide the FIPS 140-2 cryptographic module certificate number and a brief description of the encryption module that includes the encryption algorithm(s) used, the key length, and the vendor of the product.

The Contractor shall ensure that the system will be divided into configuration items (CIs). CIs are parts of a system that can be individually managed and versioned. The system shall be managed at the CI level.

The Contractor shall have a configuration management plan that includes all hardware and software that is part of the system and contains at minimum the following sections:

a. Introduction

i. Purpose & Scope

ii. Definitions

iii. References

b. Configuration Management

i. Organization

ii. Responsibilities

iii. Tools and Infrastructure

c. Configuration Management Activities

i. Specification Identification

ii. Change control form identification

iii. Project baselines

d. Configuration and Change Control

i. Change Request Processing and Approval

ii. Change Control Board

e. Milestones

i. Define baselines, reviews, audits

f. Training and Resources

The Information System Security Officer’s (ISSO's) role in the change management process must be described. The ISSO is responsible for the security posture of the system. Any changes to the system security posture shall have the prior approval of the ISSO. The Contractor shall not have the ability to make changes to the system's security posture without the appropriate involvement and approval of the ISSO.

The Contractor shall track and record information specific to proposed and approved changes that minimally includes:

a. Identification of the configuration change

b. Testing of the configuration change

c. Scheduled implementation of the configuration change

d. Tracking system impact of the configuration change

e. Tracking the implementation of the configuration change

f. Recording & reporting of the configuration change to the appropriate party

g. Back out/Fall back plan

h. Weekly Change Reports and meeting minutes

i. Emergency change procedures

j. List of team members from key functional areas

The Contractor shall provide a list of software and hardware changes in advance of placing them into operation within the following timeframes:

C-10

• 30 calendar days for a classified, SGI, or high sensitivity system

• 20 calendar days for a moderate sensitivity system

• 10 calendar days for a low sensitivity system

The contractor shall maintain all system documentation that is current to within:

• 10 calendar days for a classified, SGI, or high sensitivity system

• 30 calendar days for a low sensitivity system

Modified code, tests performed and test results, issue resolution documentation, and updated system documentation shall be deliverables under the contract.

Any proposed changes to the system shall have written approval from the NRC Project Officer.

The Contractor shall maintain a list of hardware, firmware, and software changes that is current to within:

• 15 calendar days for a classified, SGI or high sensitivity system

• 20 calendar days for a moderate sensitivity system

• 30 calendar days for a low sensitivity system

The Contractor shall analyze proposed hardware and software configurations and modification as well as addressed security vulnerabilities in advance of NRC accepted operational deployment dates within:

• 15 calendar days for a classified, SGI, or high sensitivity system

• 20 calendar days for a moderate sensitivity system

• 30 calendar days for a low sensitivity system

The Contractor shall provide the above analysis with the proposed hardware and software for NRC testing in advance of NRC accepted operational deployment dates within:

• 15 calendar days for a classified, SGI, or high sensitivity system

• 30 calendar days for a low sensitivity system

The Contractor shall demonstrate that all hardware and software meet security requirements prior to being placed into the NRC production environment.

The Contractor shall ensure that the development environment is separated from the operational environment using NRC CSO approved controls.

The Contractor shall ensure that its employees, in performance of the contract, receive Information Technology (IT) security training in their role at the contractor’s expense. The Contractor shall provide the NRC written certification that training has been completed, along with the title of the course and dates of training as a prerequisite to start of work on the contract. Contractors shall ensure that their employees, consultants, and subcontractors that have significant IT responsibilities (e.g. IT administrators, developers, project leads) receive in-depth IT security training in their area of responsibility. This training shall be at the Contractor’s expense.

C-11

The system shall be able to create, maintain, and protect from modification or unauthorized access or destruction an audit trail of accesses to the objects it protects. The audit data shall be protected so that read access to it is limited to those who are authorized.

The system shall be able to record the following types of events: use of identification and authentication mechanisms, introduction of objects into a user’s address space (e.g., file open, program initiation), deletion of objects, and actions taken by computer operators and system administrators or system security officers and other security relevant events.

The system shall be able to audit any override of security controls.

The Contractor shall ensure auditing is implemented on the following:

• Operating System

• Application

• Web Server

• Web Services

• Network Devices

• Database

• Wireless

The Contractor shall perform audit log reviews daily using automated analysis tools.

The Contractor shall log at least the following events on systems that process NRC information:

a. Audit all failures

b. Successful logon attempt

c. Failure of logon attempt

d. Permission changes

e. Unsuccessful file access

f. Creating users & objects

g. Deletion & modification of system files

h. Registry key/kernel changes

i. Startup & shutdown

j. Authentication

k. Authorization/permission granting

l. Actions by trusted users

m. Process invocation

n. Controlled access to data by individually authenticated user

o. Unsuccessful data access attempt

p.