contract no. nrc-hq-60-15-c-0012. · 503 thompson st ann arbor mi 481091340 code 073133571 facility...
TRANSCRIPT
AWARDICONTRACT UNDER DPAS (15 CFR 700) ...o 1 NCz2. CONTRACT (Proc. Inst. I/ent.) NO: 3. EFFECTIVE DATE 4. REOUISITIONIPURCHASE REQUEST/PROJECT NO.
NRC-HQ-60-15-C-0012 See Block 2OCRES-15-0158
5. ISSUED BY CODE NRCHQ S. ADMINISTERED BY (If other than item 5) CODE NRCHQ
US NRC - HQ ,US NRC - HQACQUISITION MANAGEMENT DIVISION ACQUISITION MANAGEMENT DIVISION
MAIL STOP TWFN-5E03 MAIL STOP TWFN-5E03ATTN MARK THOMPSON 301-415-0689 ,WASHINGTON DC 20555-0001WASHINGTON DC 20555-0001
7. NAME AND ADDRESS OF CONTRACTOR (No., Street, City, Country, State and ZIP Code) B. DELIVERY
H] FOE ORIGIN []OTHER (See below)UNIVERSITY OF MICHIGAN 9. DISCOUNT FOR PROMPT PAYMENT503 THOMPSON ST
ANN ARBOR MI 481091340
10. SUBMIT INVOICES ITEM(4 copies unless otherwise specified)
TO THE ADDRESS SHOWN IN
CODE 073133571 FACILITY CODE
11. SHIP TD/MARK FDR "CODE NRCHQ . 12. PAYMENT WILL BE MADE BY CODE NRC PAYMENT S
US NUCLEAR REGULATORY COMMISSION- US NUCLEAR REGULATORY COMMISSIONMAIL PROCESSING CENTER ONE WHITE FLINT NORTH"4930 BOILING BROOK PARKWAY 11555 ROCEVILLE PIKEROCKVILLE MD 20852 MAILSTOP O3-E17A
NRC PAYMENT S NRCGO VROCKVILLE MD 20852-2738
13. AUTHORITY FOR USING OTHER THAN FULLAND OPEN COMPETITION: 14. ACCOUNTING AND APPROPRIATION DATA
f710U.S.€.23o4c()( ) fl41 U.S.C. 253(c)( )See Schedule
15A. ITEM NO f15B. SUPPLIES/SERVICES 15C. i5D. 155. UNIT PRICE 1SF. AMOUNTQUANTITY UNIT
k tned.15G. TOTAL AMOUNT OF CONTRACT •[ $1,583,545.00
16. TABLE OF CONTENTS(x) IsEc. IDESCRIPTION PFAGE(S) CX) IsEc. IDESCRIPTION PAGE(S)
PART I -THE SCHEDULD PART II - CONTRACT CLAUSES
A SOLICITATION1CONTRACT FORM II CONTRACT CLAUSES
B SUPPLIES OR SERVICES AND PRICES/COSTS PART II]1- LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.
C D ESCRIPTIONISPECS./WORK STATEMENT J LIST OFATT-ACHMENTS
D PACKAGING AND MARKING PART IV - REPRESENTATIONS AND INSTRUCTIONS
E INSPECTION AND ACCEPTANCE K REPRESENTATIONS, CERTIFICATIONS AND
F DELIVERIES OR PERFORMANCE OTHER STATEMENTS OF OFFERORS
G CONTRACTADMINISTRATION DATA L ]NSTRS., CONDS., AND NOTICES TO OFFERORS
H SPECIAL CONTRACT REQUIREMENTS M EVALUATION FACTORS FOR AWARD
CONTRACTING OFFICER WILL COMPLETE ITEM 17 (SEALED-BID OR NEGOTIATED PROCUREMENT) OR 18 (SEALED-BID PROCUREMENT) AS APPLICABLE17. []jCONTRACTOR' S NEGOTIATED AGREEMENT (Contractor is required to sign this 18. D EBALED-BID AWARD (Contra ctor is not required to sign this document.) Your bid ondocument and return 1 copies to issuing office.) Contractor agrees to Solicitation Number NRC-HQ- 601- 15-R-00 0 9furnish and deliver all items or perform all the services set forth or otherwise identified including the additions or changes made by you which additions or changes are set torth
above and on any continuation sheets for the consideration slated herein. The rights and in full above, is hereby accepted as to the items listed above and on any continuation
obligations ot the parties to this contract shall be subject to and governed by the following sheets. This award consummates the contract which consiats ot the tollowingdocuments: (a) this award/contract, (5) the solicitation, if any, and (0) such provisiona, documents: (a) the Government's solicitation and your bid, and (b) this awardlcontract.
representations, certifications, and specifications, as are attached or incorporated by No further contractual document is necessary. (Block 18 should be checked only whenreference herein. (Attachments are listed herein.) awarding a sealed-bid contract.)19A. NAME AND TITLE OF SIGNER (Type orpdnf) 20A. NAME OF CONTRACTING OFFICER
MARK THOMPSON19B. NAME OF CONTRACTOR l9C. DATE SIGNED 209. UNITED STATES OF AMERICA 120C. DATE SIGNED
BY BY •' _-/.•I 09 /28 /2015
(Signature of person authoriyed to sign) (Signature of the Contracting Officer)..............
AUTHORIZED FOR LOCAL REPRODUCTIONPrevious edition is NOT usable
F'
SUNSI REVIEW COMPLEILDEC 2 3 2015
AR
AWARDICONTRACT " 1.;THS CONTRACT.IS A-RATEDOORDER -U~RDA 15CR7m. . RATING, PAGE1OF.PAGES,72.. CONTRACT (Proc. Inst. tdea.) NO. 3. EFFECTIVE DATE 4- REQUISITIONPURCHASE REQUEST/PROJECT NO.
NRC-HQ- 60-1 5-C- 0012 See Block 20C
5. ISSUED BY CODE NRCHQ 6 ADMINISTERED BY" (If other than 11em 5) CODE I ... NRCHQ
US NRC - HQ US NRC - HQACQUISITION MANAGEMENT DIVISION AhCQUISITION MANAGEMENT DIVISION
NAIL STOP TWE'N-5E03 MAhIL STOP TWFN-5E03ATTN MARK THOMPSON 301-415-0689 ,WASHINGTON DC 20555-0001WASHINGTON DC 20555-0001
7. NAMEANOADORESS OF CONTRACTOR (No.. Street, City. Countr,, State anctZtf'Code) B DELIVERY
E. FOB ORIGIN •] OTHER (See below)
UNIVERS ITY OF MICHIGAN B. DISCOUNTFOR PROMPT PAYMENT
503 THOMPSON STANN ARBOR MI 481091340
CODE 073133571 FACILITY CODE
11. SHIP TO/MAi•RK FOR "CODE NRCHQ 12, PAYMENT WtLL BE MADE BY C•ODE NRC PAYMENTS
US NUCLEAR REGULATORY COMMISSION- US NUCLEAR REGULATORY COMMISSIONMAIL PROCESSING CENTER ONE WHITE FLINT NORTH4930 BOILING BROOK PARKWAY 11555 ROCKVILLE PIKEROCKVILLE MD 20852 MAILSTOP O3-EI7A
NRC PAYMENTSNRC GOVROCKVILLE MD 20852-2738
13 AUTHORITY FOR USING OTHER THAN FULLAND OPEN COMPETITION: 14. ACCOUNTING AND APPROPRIATION DATA
Et0u.s.c. 2304(o)( ) L_•4 u.S.C.253(oel I See Schedule
A SOLICITATION!CONTRACT FoRM !II CONTRACT CLAUSES
B SUPPLIES OR SERVICES AND PRICES/COSTS _____J____ PART IIl - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.___ C DESCRIPTI ONIS PECS.AV•ORK STATEMENT 1. LIST OF ATTACHMENTS
___ PACKAGING AND MARRING PART IV -REPRESENTATIONS AND INSTRUCTIONS
___ INSPECTION AND ACCEPTANCE K REPRESENTATIONS, CERTIFICATIONS AND
___ F DELIVERIES OR PERFORMANCE OTHER STATEMENTS OF OFFERORS
G__ CONTRACT ADMINISTRATION DATA ____ L INSTRS., DONDS,, AND NOTICES TO OFFERORS
H SPECIAL CONTRACT REQUIREMENTS M EVALUATION FACTORS FOR AWARD
CONTRACTING OFFICER EIILL COMPLETE ITEM 17 (SEALED-BID OR NEGOTIATED PRODUREMENT) OR II8 (SEALED-BID PROCUREMENT AS APPLICABLE17. •_j]CONTRACTOR' S NEGOTIATED AGREEMENT (Contractor is required to sign tIrs 1B. LJ SeALED-BID AWARD (Contracrorrsa not required IcO sign this docaurent.) Your bid ondocument and eturn 1 -copies olissuinrgodice.) Contractor agrees to Solnetlalions Number __ _ N RC -HQ- 6 0- 5 - R-0 00 9
furnish and deliver all items or perform all the servIces Sal forth or otherilse idernttfed including the additions or changes made by you whIch additions or changes are set forthabove and on any continuation sheets for die consideration stated herein. The rights andt in full above, is hereby accepted as to the items listed above and on any continaatiren
obligations of tev partIes 10 Ihis contract shall be snbject to and governed by thle followlng sheats. This saverd consummates the contract which consists of the follcsvtingdocuments: (a) tries wardlcontcoct. (b) the solicitation, it any, and (c) 55u11 provisIons, documents: (a) the Gooerrnments soitoitatsen and your bid, mid (b) this asvar"d/contracLrepresentations, certittcations, and specifiations, as are attached or incorporated by No further contractual document Is necessary. (Block 18 srtould be checked only when
reeenehren(ttcmet r-!sedbrtn. r÷ . CI ar awarding a sealed-bid contracL)19A. NAME AND TITLE DE SIGNER (
Type orpritI)*'-o' ,a %al••d20A NAME OF CONTRACTING OFFICER
Associate'Director MAR THOMPSON19E. NAME OF CONTRACTOR Grants and Qor ts SIGNED 20B. UNITED STATES OF AMERICA 0.DTESND
(Sgatr o ero aE edtn atureof teContracting Oi'cer ..............
AUTHORIZED FOR LOCAL REPRODUCTIONPrevious edition is NOT usable
Prenonibed by GSA- FAR 148 OFR) 53.214(aI
SECTION A - Solicitation/Contract Form ................................................... 2SECTION B - Supplies or Services/Prices.................................................. 3NRCB010 BRIEF PROJECT TITLE AND WORK DESCRIPTION ......................... 3SECTION C - DescriptionlSpecifications.................................................... 4SECTION D - Packaging and Marking....................................................... 5NRCD020 BRANDING ........................................................................... 5NRCDOt0 PACKAGING AND MARKING ................... "......... .......................... 5SECTION E - Inspection and Acceptance ............. ................................... .. 6NRCE010 INSPECTION AND ACCEPTANCE BY THE NRC (SEP 2013) ............€.....6SECTION F - Deliveries or Performance .. ................................................. 7NRCFO30 PERIOD OF PERFORMANCE..................................................... 7NRCF010 PLACE OF DELIVERY-REPORTS ....... •.......:.................................. 7SECTION G, Contract Administration Data................................................. 8NRCG20 REGISTRATION IN FEDCONNECT® (JULY 2014) ..................... ........ 8NRCG030 ELECTRONIC PAYMENT (SEP 2014) ........................................... 8SECTION H - Special Contract Requirements .................. ... "......................... 92052.21 5-71 PROJECT OFFICER AUTHORITY. (OCT 1999) ............................ 122052.215-77 TRAVEL APPROVALS AND REIMBURSEMENT. (OCT 1999) ........... 142052.235-70 PUBLICATION OF RESEARCH RESULTS. (OCT 1999) ................ 152052.215-70 KEY PERSONNEL. (JAN 1993) ............................................... 15NRCH490 AWARD NOTIFICATION AND COMMITMENT OF PUBLIC FUNDS .... Error!Bookmark not defined.NRCH480 USE OF AUTOMATED CLEARING HOUSE (ACH) ELECTRONICPAYMENT/REMITTANCE ADDRESS....................................................... 16NRCH47O GREEN PURCHASING (SEP 2013)............................................. 16NRCH410 WHISTLEBLOWER PROTECTION FOR NRC CONTRACTOR ANDSUBCONTRACTOR EMPLOYEES.......................................................... 17NRCH400 SECURITY REQUIREMENTS RELATING TO THE PRODUCTION OFREPORT(S) OR THE PUBLICATION OF RESULTS UNDER CONTRACTS,AGREEMENTS, AND GRANTS.............................................................. 17NRCH340 COMPLIANCE WiTH U.S. IMMIGRATION LAWS AND REGULATIONS ... 19NRCH31 0 ANNUAL AND FINAL CONTRACTOR PERFORMANCE EVALUATIONS. 19SECTION I - Contract Clauses............................................................. .. 2152.202-1 DEFINITIONS. (NOV 2013) ........................................................ 2152.203-5 COVENANT AGAINST CONTINGENT FEES. (MAY 2014) .............. 2152.203-6 RESTRICTIONS ON SUBCONTRACTOR SALES TO THE GOVERNMENT.(SEP 2006) ..................................................................................... 2152.203-7 ANTI-KICKBACK PROCEDURES. (MAY 2014) ................................ 2152.217-8 OPTION TO EXTEND SERVICES. (NOV 1999) ................................. 2252.217-9 OPTION TO EXTEND THE TERM-~OF THE CONTRACT. (MAR 2000)......2252.21 9-28 POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION.(JUL 2013)..................................................... Error! Bookmark not defined.52.222-2 PAYMENT FOR OVERTIME PREMIUMS. (JUL 1990) .......................... 2352.222-36 EQUAL OPPORTUNITY FOR WORKERS WITH DISABILITIES. (JUL 2014)........... ................................................................................2 452.232-25 PROMPT PAYMENT. (JUL 2013) ............................................... 2452.242-4 CERTIFICATION OF FINAL INDIRECT COSTS. (JAN 1997)Error! Bookmarknot defined.52.252-2 CLAUSES INCORPORATED BY REFERENCE. (FEB 1998).................. 25NRCI010 NRC ACQUISTION REGULATION (NRCAR) PROVISIONS AND CLAUSES
Page 1 of 26
NAME OF OFFEROR OR CONTRACTOR
UNIVERSITY OF MICHIGAN
ITEM NO. 1SUPPLIESISERVICES IQUANTITY UNIT UNIT PRICE 1AMOUNT(A) J(B) (C) (D) (E) (F)
00001
Contractor Support for the PARCS Code Suite
Total Contract Ceiling: $1,583,545.00.Total Contract Funding: $65,000.00.Period of Performance: 10/01/2015 to 09/30/2020
Labor and MaterialsTotal Obligated AmrountS1,583,545.00Incrementally Funded Amount: $66,000.00
Accounting Info:2015-C0200-FEEBASED-60-60D003-11l-6-213--1045-252AFunded: $22,505.00Accounting Info:2015-X0200-REIM--60-600003-11-R-729-1302-252AFunded: $23,495.00Accounting Info:2015-X0200-REIM-60-60D003-11--R-729-1302-252AFunded: $20,000.00
The obligated amount of award: $66,000.00. Thetotal for this award is shown in box 15G.
1,583,545.00
AUTHORIZED FOR LOCAL REPRC OPTIONAL FORM 336 (4-861Sponsored by GSAFAR (48 CFR) 53.110
SECTION B - Supplies or Services/Prices
NRCB010 BRIEF PROJECT TITLE AND WORK DESCRIPTION
(a) The title of this project is: Contractor Support for the Purdue Advanced Reactor CoreSimulator (PARCS) Code Suite.
(b) Summary work description: The objective of this contract is to obtain regulatorytechnical support with the maintenance, code support, assessment, development, anduser training of the PARCS and GenPMAXS codes and the interface of PARCS withRELAP, TRACE, and SNAP as well as maintaining TRIPEN/AGREE support for theOECD-NEA-LOFC benchmark. The PARCS code supports independent regulatorydecision making through its employment as a tool in confirmatory safety reviews ofpower plant operator actions, core designs, power uprates, and licenseamendments.NRCHQ
(End of Clause)
CONSIDERATION AND OBLIGATION - COST REIMBURSEMENT-NO FEE (AUG2011) ALTERNATE I (AUG 2011)
(a) The total estimated cost to the Government for full performance under this contract is$1,583,545.00.
(b) The amount presently obligated by the Government with respect to this contract is$22,505.00.
(d) This is an incrementally-funded contract and FAR 52.232-22 - "Limitation of Funds"applies.
PRICE SCHEDULE
Enhancing Guidance for00001 Evacuation Time Estimate $153450
Studies$1534.0
Total Estimated Cost $1,583,545.00
*AlI travel must receive prior approval from the Contracting Officer's Representative(COR)
Page 3 of 26
(AUG 2011)................................................................................... 25SECTION J - List of Documents, Exhibits and Other Attachments................... 26
SECTION A - SolicitationlContract Form
Page 2 of 26
SECTION C - Description/Specifications
See Section J, Attachment A - PAROS SOW
Page 4 of 26
SECTION D - Packaging and Marking
NRCD02O 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, inorder to provide NRC with recognition for its involvement in and contribution to theproject.. If the work performed is funded entirely with NRC funds, then the contractormust acknowledge that information in its documentation/presentation.
Work Supported by the U.S. Nuclear Regulatory Commission (NRC), Office of Office ofNuclear Research, under Contract/order number TBD.
(End of Clause)
NRCD010 PACKAGING AND MARKING
(a) The Contractor shall package material for shipment to the NRC in such a mannerthat will ensure acceptance by common carrier and safe delivery at destination.Containers and closures shall comply with the Surface Transportation Board, UniformFreight Classification Rules, or regulations of other carriers as applicable to the mode oftransportation.
(b) On the front of the package, the Contractor shall clearly identify the contract numberunder which the product is being provided.
(c) Additional packaging and/or marking requirements are as follows: [Insert packagingand/or marking requirements herel.
(End of Clause)
Page 5 of 26
SECTION E - Inspection and Acceptance
52.246-9 INSPECTION OF RESEARCH AND DEVELOPMENT (SHORT FORM)APR 1984
NRCEO10 INSPECTION AND ACCEPTANCE BY THE NRC (SEP 2013)
Inspection and acceptance of the deliverable items to be furnished hereunder shall bemade by the NRC Contracting Officer's Representative (COR) at the destination,accordance with FAR 52.247-34 - F.o.b. Destination.
(End of Clause)
Page 6 of 26
SECTION F - Deliveries or Performance
NOTICE LISTING CONTRACT CLAUSES INCORPORATED BY REFERENCE
The following contract clauses pertinent to this section are hereby incorporated byreference (byCitation Number, Title, and Date) in accordance with the clause at FAR "52.252-2CLAUSESINCORPORATED BY REFERENCE" in Section 1 of this contract. See FAR 52.252-2 foran internet address (if specified) for electronic access to the full text of a clause.
52.242-15 STOP-WORK ORDER. (AUG 1989) - ALTERNATE I (APR 1984)
NRCF03O PERIOD OF PERFORMANCE
This contract shall commence on October 1, 2015 and will expire on September 30,
2020.
(End of Clause)
NRCFOI 0 PLACE OF DELIVERY-REPORTS
The items to be furnished hereunder shall be delivered, with all charges paid by theContractor, to:
The Contracting Officer's Representative, as stated in Section H, 2052.21 5-71PROJECT OFFICER AUTHORITY. (OCT 1999).
a. Name: Nathaneal Hudson (1 Electronic Copy)b. Contracting Officer's Representative (COR)c. Address: Nathaneal.Hudson~nrc.Qov(1 Electronic Copy)
d. Name: Joseph Staudenmeier (1 Electronic Copy)e. Alternate Contracting Officer's Representative (AItCOR)f. Address: John .Staudenmeier~2nrc..gov(1 Electronic Copy)
(End of Clause)
Page 7 of 26
SECTION G - Contract Administration Data
NRCG20 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 vendorsand contractors. FedConnect® provides bi-directional communication between thevendor/contractor and the NRC throughout pre-award, award, and post-awardacquisition phases. Therefore, in order to do business with the NRC-, vendors andcontractors must register to use FedConnect® athttps:llwww.fedconnect.netlFedConnect. The individual registering in FedConnect®must have authority to bind the vendor/contractor. There is no charge for usingFedConnect®. Assistance with FedConnect® is provided by Compusearch SoftwareSystems, not the NRC. FedConnect® contact and assistance information is providedon the FedConnect® web site at https://www.fedconnect.net/FedConnect.
NRCG030 ELECTRONIC PAYMENT (SEP 2014)
The Debt Collection Improvement Act of 1996 requires that all payments except IRS taxrefunds be made by Electronic Funds Transfer. Payment shall be made in accordancewith FAR 52.232-33, entitled "Payment by Electronic Funds-Central ContractorRegistration"'.
To receive payment, the contractor shall prepare invoices in accordance with NRC'sBilling Instructions. Claims shall be submitted on the payee's letterhead, invoice, or onthe Government's Standard Form 1034, "Public Voucher for Purchases and ServicesOther than Personal," and Standard Form 1035, "Public Voucher for Purchases Otherthan Personal - Continuation Sheet." The preferred method of submitting invoices iselectronically to: N RCPayments(~nrc.,gov
(End of Clause)
52.216-15 PREDETERMINED INDIRECT COST RATES (APR 1998)
Page 8 of 26
SECTION H - Special Contract Requirements
2052.209-71 Contractor organizational conflicts of interest (representation). (OCT1999)
As prescribed in 2009.570-4(b) and 2009.570-8, the contracting officer must insert thefollowing provision in applicable solicitations and in contracts resulting from unsolicitedproposals. The contracting officer must also include the following in task orders andcontract modifications for new work.
2052.209-72 CONTRACTOR ORGANIZATIONAL CONFLICTS OF INTEREST (JAN
1993)
(a) Purpose. The primary purpose of this clause is to aid in ensuring that the contractor:
(1) Is not placed in a conflicting role because of current or planned interests(financial, contractual, organizational, or otherwise) which relate to the work underthis contract; and
(2) Does not obtain an unfair competitive advantage over other parties by virtue of itsperformance of this contract.
(b) Scope. The restrictions described apply to performance or participation by thecontractor, as defined in 48 CFR 2009.570-2 in the activities covered by this clause.
(c) Work for others.
(1) Notwithstanding any other provision of this contract, during the term of thiscontract, the .contractor agrees to forego entering into consulting or other contractualarrangements with any firm or organization the result of which may give rise to aconflict of interest with respect to the work being performed under this contract. Thecontractor shall ensure that all employees under this contract abide by the provisionof this clause. If the contractor has reason to-believe, with respect to itself or anyemployee, that any proposed consultant or other contractual arrangement with anyfirm or organization may involve a potential conflict of interest, the contractor shallobtain the written approval of the contracting officer before the execution of suchcontractual arrangement.
(2) The contractor may not represent, assist, or otherwise support an NRC licenseeor applicant undergoing an NRC audit, inspection, or review where the activities thatare the subject of the audit, inspection, or review are the same as or substantiallysimilar to the services within the scope of this contract (or task order as appropriate)except where theNRC licensee or applicant requires the contractor's support to explain or defend thecontractor's prior work for the utility or other entity which NRC questions.
(3) When the contractor performs work for the NRC under this contract at any NRClicensee or applicant site, the contractor shall neither solicit nor perform work in thesame or similar technical area for that licensee or applicant organization for a period
Page 9 of 26
commencing with theaward of the task order or beginning of work on the site (if not a task order contract)and ending one year after completion of all work under the associated task order, orlast time at the site (if not a task order contract).
(4) When the contractor performs work for the NRC under this contract at any NRClicensee or applicant site,
(i) The contractor may not solicit work at that site for that licensee or applicantduring the period of performance of the task order or the contract, as appropriate.
(ii) The-contractor may not perform work at that site for that licensee or applicantduring the period of performance of the task order or the contract, as appropriate,and for one year thereafter.
(iii) Notwithstanding the foregoing, the contracting officer may authorize thecontractor to solicit or perform this type of work (except work in the same orsimilar technical area) if the contracting officer determines that the situation willnot pose a potential for technical bias or unfair competitive advantage.
(d) Disclosure after award.
(1)The contractor warrants that to the best of its knowledge andbelief, and except as otherwise set forth in this contract, that it doesnot have any organizational conflicts' of interest as defined in 48CFR 2009 .570-2.
(2) The contractor agrees that if, after award, it discovers organizationalconflicts of interest with respect to this contract, it shall make animmediate and full disclosure in writing to the contracting officer. Thisstatement must include a description of the action which the contractorhas taken or proposes to take to avoid or mitigate such conflicts. TheNRC may, however, terminate the contract if termination is in the bestinterest of the Government.
(3) It is recognized that the scope of work of a task-order-type contractnecessarily encompasses a broad spectrum of activities. Consequently, ifthis is a task-order-type contract, the contractor agrees that it will discloseall proposed new work involving NRC licensees or applicants which comeswithin the scope of work of the underlying contract. Further, if this contractinvolves work at a licensee or applicant site, the contractor agrees to 'exercise diligence to discover and disclose any new work at that licensee orapplicant site. This disclosure must be made before the submission of a bidor proposal to the utility or other regulated entity and must be received bythe NRC at least 15 days before the proposed award date in any event,unless a written justification demonstrating urgency and due diligence todiscover and disclose is provided by the contractor and approved by thecontracting officer. The disclosure must include the statement of work, thedollar value of the proposed contract, and any other documents that areneeded to fully describe the proposed work for the regulated utility or otherregulated entity. NRC may deny approval of the disclosed work only whenthe NRC has issued a task order which includes the technical area and, if
Page 10 of 26
site-specific, the site, or has plans to issue a task order which includes thetechnical area and, if site-specific, the site, or when the work violatesparagraphs (c)(2), (c)(3) or (c)(4) of this section.
(e) Access to and use of information.
(1) If, in the performance of this contract, the contractor obtains access toinformation, such as NRC plans, policies, reports, studies, financial plans,internal data protected by the Privacy Act of 1974 (5 U.S.C. Section,552a(1988)), or the Freedom of Information Act (5
U.S.C. Section 552 (1986)), the contractor" agrees not to:
(i) Use this information for any private purpose until the information has beenreleased to the public;
(ii) Compete for work for the Commission based on the information for a periodof six months after either the completion of this contract or the release of theinformation to the public, whichever is first;
(iii)Submit an unsolicited proposal to the Government based on theinformation until one year after the release of the information to the public; or
(iv) Release the information without prior written approval by the contractingofficer unless
the information has previously been released to the public by the NRC.
(2) In addition, the contractor agrees that, to the extent it receives or is given accessto proprietary data, data protected by the Privacy Act of 1974 (5 U.S.C. Section 552a(1988)), or the Freedom of Information Act (5 U.S.C. Section 552 (1986)), or otherconfidential or privileged technical, business, or financial information under thiscontract, the contractor shall treat the information in accordance with restrictionsplaced on use of the information.
(3) Subject to patent and security provisions of this contract, the contractor shallhave the right to use technical data it produces under this contract for privatepurposes provided that all requirements of this contract have been met.
(f) Subcontracts. Except as provided in 48 CFR 2009.570-2, the contractor shallinclude this clause, including this paragraph, in subcontracts of any tier. The termscontract, contractor, and contracting officer, must be appropriately modified to preservethe Government's rights.
(g) Remedies. For breach of any of the above restrictions, or for intentionalnondisclosure or misrepresentation of any relevant interest required to be disclosedconcerning this contract or for such erroneous representations that necessarily implybad faith, the Government may terminate the contract for default, disqualify thecontractor from subsequent contractual efforts, and pursue other remedies permittedby law or this contract.
(h) Waiver. A request for waiver under this clause must be directed in writing to thecontracting officer in accordance with the procedures outlined in 48 CFR 2009.570-9.
Page 11 of 26
(i) Follow-on effort. The contractor shall be ineligible to participate in NRC contracts,subcontracts, or proposals therefor (solicited or unsolicited) which stem directly fromthe contractor's performance of work under this contract. Furthermore, unless so-directed in writing by the contracting officer, the contractor may not perform anytechnical consulting or management support services work or evaluation activitiesunder this contract on any of its products or services or the products or services ofanother firm if the contractor has been substantially involved in the development ormarketing of the products or services.
(1) If the contractor under this contract prepares a complete or essentiallycomplete statement of work or specifications, the contractor is not eligibleto perform or participate in the initial contractual effort which is based onthe statement of work or specifications. The contractor may notincorporate its products or services in the statement of work orspecifications unless so directed in writhing by the contracting officer, inwhich case the restrictions in this paragraph do not apply.
(2) Nothing in this paragraph precludes the contractor from offering or sellingits standard commercial items to the Government.
2052.211-71 TECHNICAL PROGRESS REPORT. (JAN 1993)
2052.211-72 FINANCIAL STATUS REPORT. (OCT 1999)
2052.21 5-71 PROJECT OFFICER'S AUTHORITY. (OCT 1999)
(a) The contracting officer's authorized representative hereinafter referred to as theproject officer for this contract is:
COR Name: Nathanael HudsonAddress: Agency: US NRCOffice: Office of Nuclear Regulatory ResearchMail Stop: TIW.FN/1 0 B58Street Address (Include Office Symbol): RES/DSAIRSCB, 21 Church StreetCity, State and Zip code: Rockville, MD 20850E-Mail: [email protected] Number: 301-251-7534
Alt COR Name: Joseph StaudenmeierAddress: Agency: US NRCOffice: Office of Nuclear Regulatory ResearchMail Stop: TWFN/ 10 B58Street Address (Include Office Symbol): RES/DSA/RSCB, 21 Church StreetCity, State and Zip code: Rockville, MD 20850E-Mail: Nathanael. [email protected] Number: 301-415-1138
(b) Performance of the work Under this contract is Subject to the technical direction of theNRC project officer. The term technical direction is defined to include the following:
Page 12 of 26
(1) Technical direction to the contractor which shifts work emphasis between areas ofwork or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel notcontemplated in the Statement of Work or changes to specific travel identified in theStatement of Work), fills in details, or otherwise serves to accomplish the contractualstatement of work.
(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, approve technical reports, drawings,specifications, and technical information to be delivered by the contractor to theGovernment under the contract.
(c) Technical direction must be within the general statement of work stated in thecontract. The project officer does not have the authority to and may not issue anytechnical 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, thefixed fee, if an~y, 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, orissues any unilateral directive whatever.
(d) All technical directions must be issued in writing by the project officer or must beconfirmed by the project officer in writing within ten (10) working days after verbalissuance. A copy of the written direction must be furnished to the contracting officer. Acopy of NRC Form 445, Request for Approval of Official Foreign Travel, which hasreceived final approval from the NRC must be furnished to the contracting officer.
(e) The contractor shall proceed promptly with the performance of technical directionsduly issued by the project officer in the manner prescribed by this clause and within theproject officer's authority under the provisions of this clause.
(f) If, in the opinion of the contractor, any instruction or direction issued by the projectofficer is within one of the categories defined in paragraph (c) of this section, thecontractor 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 thatcontracting officer to modify the contract accordingly., Upon receiving the notificationfrom the contractor, the contracting officer shall issue an appropriate contractmodification 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 changeunder the "Changes" clause.
(g) Any unauthorized commitment or direction issued by the project officer may result in
Page 13 of 26
an unnecessary delay in the contractor's performance and may even result in thecontractor 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 uponthe contract action to be taklen with respect to the instruction or direction is subject to52.233-1 - Disputes.
(i) In addition to providing technical direction as defined in paragraph (b) of the section,the project officer shall:
(1) Monitor the contractor's technical progress, including surveillance and assessment ofperformance, and recommend to the contracting officer changes in requirements.
(2) Assist the contractor in the resolution of technical problems encountered duringperformance.
(3) Review all costs requested for reimbursement by the contractor and submit to thecontracting officer recommendations for approval, disapproval, or suspension ofpayment for supplies and services required under this contract.
(End of Clause)
2052.21 5-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 FAR52.247-63 Preference for U.S. Flag Air Carriers. The contractor shall submit NRC Form445 to the NRC no later than 30 days before beginning travel.
(b) The contractor must receive written approval from the NRC Project Officer beforetaking travel that was unanticipated in the Schedule (i.e., travel not contemplated in theStatement 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 directlyrelated to this contract and are allowable subject to the limitations prescribed in FAR31.205-46.
(d) It is the responsibility of the contractor to notify the contracting officer in accordancewith the Limitations of Cost clause of this contract when, at any time, the contractorlearns that travel expenses will cause the contractor to exceed the estimated costsspecified in the Schedule.
(e) Reasonable travel costs for research and related activities performed at State andnonprofit institutions, in accordance with Section 12 of Pub. L. 100-679, must becharged in accordance with the contractor's institutional policy to the degree that thelimitations of Office of Management and Budget (0MB) guidance are not exceeded.Applicable guidance documents include 0MB Circular A-87, Cost Principles for Stateand Local Governments; 0MB Circular A-122, Cost Principles for NonprofitOrganizations; and 0MB Circular A-21, Cost Principles for Educational Institutions.
Page 14 of 26
(End of Clause)
2052.235-70 PUBLICATION OF RESEARCH RESULTS. (OCT 1999)
(a) The principal investigator(s)/contractor shall comply with the provisions of NRCManagement Directive 3.8 (Vol. 3, Part 1) and NRC Handbook 3.8 (Parts l-IV) regardingpublication in refereed scientific and engineering journals or dissemination to the publicof any information, oral or written, concerning the work performed under this contract.Failure to comply with this clause shall be grounds for termination of this contract.
(b) The principal investigator(s)/contractor may publish the results of this work inrefereed scientific and engineering journals or in open literature and present papers atpublic or association meetings at interim stages of work, in addition to submitting to NRCthe final reports and other deliverables required under this contract. However, suchpublication and papers shall focus on advances in science and technology and minimizeconclusions and/or recommendations which mfay have regulatory implications.
(c) The principal investigator(s) shall coordinate all such publications with, and transmit acopy of the proposed article or paper to, the NRC Contracting Officer or Project Officer,prior to publication. The NRC agrees to review and provide comments within thirty (30)days after receipt of a proposed publication. However, in those cases where theinformation to be published addresses and/or discusses NRC policy, the NRC reservesthe right to have the contractor add the following disclaimer that states "Any opinions,findings, and conclusions or recommendations expressed in this publication are those ofthe author(s) and do not necessarily reflect the views of the NRC".
(End of Clause)
2052.215-70 KEY PERSONNEL. (JAN 1993)
2052.21 5-70 Key personnel. (JAN 1993)
As prescribed at 2015.209-70(a)(1), the contracting officer shall insert in solicitations andcontracts the following clause as applicable to the requirement:
KEY PERSONNEL (JAN 1993)
Principal Manager Thomas DownerSenior Engineer Yunlin XuResearch Associate Andrew WardResearch Associate Volkan Seker
(a) The following individuals are considered to be essential to the successful
Page 15 of 26
performance of the work hereunder:
To be determined at Contract Award
The contractor agrees that personnel may not be removed from the contract work or
replaced without compliance with paragraphs (b) and (c) of this section.
(b) If one or more of the key personnel, for whatever reason, becomes, or is expected tobecome, unavailable for work under this contract for a continuous period exceeding 30work days, or is expected to devote substantially less effort to the .work than indicated inthe proposal or initially anticipated, the contractor shall immediately notify the contractingofficer and shall, su~bject to the concurrence of the contracting officer, promptly replacethe personnel with personnel of at least substantially equal ability and qualifications.
(c) Each request for approval of substitutions must be in writing and contain a detailedexplanation of the circumstances necessitating the proposed substitutions. The requestmust also contain a complete resume for the proposed substitute and Other informationrequested or needed by the contracting officer to evaluate the proposed substitution.The contracting officer and the project officer shall evaluate the contractor's request andthe contracting officer shall promptly notify the contractor of his or her decision in writing.
(d) If the contracting officer determines that suitable and timely replacement of keypersonnel who have been reassigned, terminated, or have otherwise becomeunavailable for the contract work is not reasonably forthcoming, or that the resultantreduction of productive effort would be so substantial as to impair the successfulcompletion of the contract or the service order, the contract may be terminated by thecontracting officer for default or for the convenience of the Government, as appropriate.If the contracting officer finds the contractor at fault for the condition, the contract price orfixed fee may be equitably adjusted downward to compensate the Government for anyresultant delay, loss, or damage.
(End of Clause)
NRCH480 USE OF AUTOMATED CLEARING HOUSE, (ACH) ELECTRONICPAYMENT/REMITTANCE ADDRESS
The Debt Collection Improvement Act of 1996 requires that all Federal payments exceptIRS tax refunds be made by Electronic Funds'Transfer. It is the policy of the NuclearRegulatory CommisSion to pay government vendors by the Automated Clearing House(ACH) electronic funds transfer payment system. Item 1 5C of the Standard Form 33may be disregarded.
(End of Clause)
NRCH47O GREEN PURCHASING (SEP 2013)
Page 16 of 26
(a) In furtherance of the sustainable acquisition goals included in E;•ecutive Order13514, "Federal Leadership in Environmental, Energy, and Economic Performance,"products and services acquired under this contract/order shall be energy-efficient(Energy Star or Federal Energy Management Program (FEMP) designated),water-efficient, biobased, environmentally preferable (e.g., Electronic ProductEnvironmental Assessment Tool (EPEAT) certified), non-ozone depleting, recycledcontent, and non-toxic or less toxic alternatives, to the maximum extent practicable inmeeting NRC contractual requirements.
(b) See NRC's Green Purchasing Plan (GPP) at:http://pbadu pws. nrc.gov/docs/M L1219//ML12191Al30. pdf and the General ServiceAdministration's (GSA) Green Procurement Compilation at:http:/lwww.gsa.govlportal/content/1 98257.
'(c) The contractor shall flow down this clause into all subcontracts and other agreementsthat relate to performance of this contract/order.
(End of Clause)
NRCH410 WHISTLEBLOWER PROTECTION FOR NRC CONTRACTOR ANDSUBCONTRACTOR EMPLOYEES
(a) The U.S. Nuclear Regulatory Commission (NRC) contractor'and its subcontractor aresubject to the Whistleblower Employee Protection public law provisions as codified at 42U.S.C. 5851. NRC contractor(s) and subcontractor(s) shall comply with therequirements of this Whistleblower Employee Protection law, and the implementingregulations of the NRC and the Department of Labor (DOL). See, for example, DCLProcedures on Handling Complaints at 29 C.F.R. Part 24 concerning the employerobligations, prohibited acts, DOL procedures and the requirement for prominent postingof notice of Employee Rights at Appendix A to Part 24 entitled: "Your Rights Under theEnergy Reorganization Act".
(b) Under this Whistleblower Employee Protection law, as implemented by regulations,NRC contractor and subcontractor employees are protected from discharge, reprisal,threats, intimidation, coercion, blacklisting or other employment discrimination practiceswith respect to compensation, terms, conditions or privileges of their employmentbecause the contractor or subcontractor employee(s) has provided notice to theemployer, refused to engage in unlawful practices, assisted in proceedings or testifiedon activities concerning alleged violations of the Atomic Energy Act of 1954 (asamended1) and the Energy Reorganization Act of 1974 (as amended).
(c) The contractor shall insert this or the substance of this clause in any subcontractsinvolving work performed under this contract.
(End of Clause)
NRCH400 SECURITY REQUIREMENTS RELATING TO THE PRODUCTION OFREPORT(S) OR THE PUBLICATION OF RESULTS UNDER CONTRACTS,AGREEMENTS, AND GRANTS
Page 17 of 26
Review and Approval of Reports
(a) Reporting Requirements. The contractor/grantee shall comply with the terms andconditions of the contract/grant regarding the contents of the draft and final report,summaries, data, and related documents, to include correcting, deleting, editing,revising, modifying, formatting, and supplementing any of the information containedtherein, at no additional cost to the NRC. Performance under the contract/grant will notbe deemed accepted or completed until it complies with the NRC's directions. Thereports, summaries, data, and related documents will be considered draft until approvedby the NRC. The contractor/grantee agrees that the direction, determinations, anddecisions on approval or disapproval of reports, summaries, data, and relateddocuments created under this contract/grant remain solely within the discretion of theNRC.
(b) Publication of Results. Prior to any dissemination, display, publication, or release ofarticles, reports, summaries, data, or related documents developed under thecontract/grant, the contractor/grantee shall submit them to the NRC for review andapproval. The contractor/ grantee shall not release, disseminate, display or publisharticles, reports, summaries, data, and related documents, or the contents therein, thathave not been reviewed and approved by the NRC for release, display, dissemination orpublication. The contractor/grantee agrees to conspicuously place any disclaimers,markings or notices, directed by the NRC, on any articles, reports, summaries, data, andrelated documents that the contractor/grantee intends to release, display, disseminate orpublish to other persons, the public, or any other entities. The contractor/grantee agrees,and grants, a royalty-free, nonexclusive, irrevocable worldwide license to thegovernment, to use, reproduce, modify, distribute, prepare derivative works, release,display or disclose the articles, reports, summaries, data, and related documentsdeveloped under the contract/grant, for any governmental purpose and to have orauthorize others to do so.
(c) Identification/Marking of Sensitive Unclassified Non-Safeguards Information (SUNSI)and Safeguards Information (SGI). The decision, determination, or direction by the NRCthat information possessed, formulated or produced by the contractor/granteeconstitutes SUNSI or SGI is solely within .the authority and discretion of the NRC. Inperforming the contract/grant, the contractor/grantee shall clearly mark SUNSI and SGI,to include for example, QUO-Allegation Information or QUO-Security RelatedInformation on any reports, documents, designs, data, materials, and written information,as directed by the NRC. In addition to marking the information as directed by the NRC,the contractor shall use the applicable NRC cover sheet (e.g., NRC Form 461Safeguards Information) in maintaining these records and documents. Thecontractor/grantee shall ensure that SUNSI and SGI is handled, maintained andprotected from unauthorized disclosure, consistent with NRC policies and directions. Thecontractor/grantee shall comply with the requirements to mark, maintain, and protect allinformation, including documents, summaries, reports, data, designs, and materials inaccordance with the provisions of Section 147 of the Atomic Energy Act of 1954 asamended, its implementing regulations (10 CFR 73.21), Sensitive UnclassifiedNon-Safeguards and Safeguards Information policies, and NRC Management Directivesand Handbooks 12.5, 12.6 and 12.7.
(d) Remedies. In addition to any civil, criminal, and contractual remedies available underthe applicable laws and regulations, failure to comply with the above provisions, and/or
Page 18 of 26
NRC directions, may result in suspension, withholding, or offsetting of any paymentsinvoiced or claimed by the contractor/grantee.
(e) Flowdown. If the contractor/grantee intends to enter into any subcontracts or otheragreements to perform this contract/grant, the contractor/grantee shall include all of theabove provisions in any subcontracts or agreements.
(End of Clause)
NRCH340 COMPLIANCE WITH U.S. IMMIGRATION LAWS AND REGULATIONS
NRC contractors are responsible to ensure that their alien personnel are not in violationof United States immigration laws and regulations, including employment authorizationdocuments and visa requirements. Each alien employee of the Contractor must belawfully admitted for permanent residence as evidenced by Permanent Resident Form1-551 (Green Card), or must present other evidence from the U.S. Department ofHomeland Security/U.S. Citizenship and Immigration Services that employment will notaffect his/her immigration status. The U.S. Citizenship and Immigration Servicesprovides information to contractors to help them understand the employment eligibilityverification process for non-US citizens. This information can be found on their website,http:Ilwww, uscis.gov/porta[/site/uscis.
The NRC reserves the right to deny or withdraw Contractor use or access to NRCfacilities or its equipment/services, and/or take any number of contract administrativeactions (e.g., disallow costs, terminate for cause) should the Contractor violate theContractor's responsibility under this clause.
(End of Clause)
NRCH31O ANNUAL AND FINAL CONTRACTOR PERFORMANCE EVALUATIONS
Annual and final evaluations of contractor performance under this contract will beprepared in accordance with FAR Subpart 42.15, "Contractor Performance Information,"normally at or near the time the contractor is notified of the NRC's intent to exercise thecontract option. If the multi-year contract does not have option years, then an annualevaluation will be prepared [insert time for annual evaluation here]. Final evaluations ofcontractor performance will be prepared at the exPiration of the contract during thecontract closeout process.
The Contracting Officer will transmit the NRC Contracting Officer's Representative's(COR) annual and final contractor performance evaluations to the contractor's ProjectManager, unless otherwise instructed by the contractor. The contractor will be permittedthirty days to review the document and submit comments, rebutting statements, oradditional information.
Where a contractor concurs with, or takes no exception to an annual performanceevaluation, the Contracting Officer will consider such evaluation final and releasable forsource selection purposes. Disagreements between the parties regarding a performanceevaluation will be referred to an individual one level above the Contracting Officer,whose decision will be final.
Page 19 of 26
The Contracting Officer will send a copy of the completed evaluation report, marked"Source Selection Information", to the contractor's Project Manager for their records assoon as practicable after it has been finalized. The completed evaluation report alsowill be used as a tool to improve communications between the NRC and the contractorand to improve contract performance.
The completed annual performance evaluation will be used to support future awarddecisions in accordance with FAR 42.1502 and 42.1503. During the period theinformation is being used to provide source selection information, the completed annualperformance evaluation will be released to only two parties - the Federal governmentpersonnel performing the source selection evaluation and the contractor underevaluation if the contractor does not have a copy of the report already.
(End of Clause)
Page 20 of 26
SECTION I - Contract Clauses
NOTICE LISTING CONTRACT CLAUSES INCORPORATED BY REFERENCE
The following contract clauses pertinent to this section are hereby incorporated byreference (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 fulltext of a clause.
52.202-1 DEFINITIONS. (NOV 2013)
When a solicitation provision or contract clause uses a word or term that isdefined in the Federal Acquisition Regulation (FAR), the word or term has thesame meaning as the definition in FAR 2.101 in effect at the time the solicitationwas issued, unless-
(a) The solicitation, or amended solicitation, provides a different definition;
(b) The contracting parties agree to a different definition;
(c) The part, subpart, or section of the, FAR where the provision or clauseis prescribed provides a different meaning; or
(d) The word or term is defined in FAR Part 31, for use in the costprinciples and procedures.
52.203-3 GRATUITIES. (APR 1984)
52.203-5 COVENANT AGAINST CONTINGENT FEES. (MAY 2014)
52.203-6 RESTRICTIONS ON SUBCONTRACTOR SALES TO THE GOVERNMENT.(SEP 2006)
52.203-7 ANTI-KICKBACK PROCEDURES. (MAY 2014)
52.203-8 CANCELLATION, RESCISSION, AND RECOVERY OF FUNDS FORILLEGAL OR IMPROPER ACTIVITY. (MAY 2014)
52.203-10 PRICE OR FEE ADJUSTMENT FOR ILLEGAL OR IMPROPER ACTIVITY.(MAY 2014)
52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERALTRANSACTIONS. (OCT 2010)
52.203-17 CONTRACTOR EMPLOYEE WHISTLEBLOWER RIGHTS ANDREQUIREMENT TO INFORM EMPLOYEES OF WHISTLEBLOWER RIGHTS. (APR2014)
52.204-4 PRINTED OR COPIED DOUBLE-SIDED ON POSTCONSUMER FIBER
Page 21 of 26
CONTENT PAPER. (MAY 2011)
52.204-10 REPORTING EXECUTIVE COMPENSATION AND FIRST-TIERSUBCONTRACT AWARDS. (JUL 2013)
52.209-6 PROTECTING THE GOVERNMENT'S INTEREST WHENSUBCONTRACTING WITH CONTRACTORS DEBARRED, SUSPENDED, ORPROPOSED FOR DEBARMENT. (AUG 2013)
52.209-9 UPDATES OF PUBLICLY AVAILABLE INFORMATION REGARDINGRESPONSIBILITY MATTERS. (JUL 2013)
52.215-2 AUDIT AND RECORDS - NEGOTIATION. ALTERNATE II (OCT 2010)
52.215-8 ORDER OF PRECEDENCE - UNIFORM CONTRACT FORMAT. (OCT 1997)
52.215-23 LIMITATIONS oN PASS-THROUGH CHARGES. (OCT 2009)
52.216-7 ALLOWABLE COST AND PAYMENT. (JUN 2013)
52.216-11 COST CONTRACT - NO FEE. ALTERNATE 1 (APR 1984)
52.219-8 UTILIZATION OF SMALL BUSINESS CONCERNS. (OCT 2014)
52.217-8 OPTION TO EXTEND SERVICES. (NOV 1999)
The Government may require continued performance of any services within the limitsand at the rates specified in the contract. These rates may be adjusted only as a resultof revisions to prevailing labor rates provided by the Secretary of Labor. The optionprovision may be exercised more than once, but the total extension of performancehereunder shall not exceed 6 months. The Contracting Officer may exercise the optionby written notice to the Contractor within [insert the period of time within which theContracting Officer may exercise the option].
52.21 7-9 OPTION TO EXTEND THE TERM OF THE CONTRACT. (MAR 2000)
(a) The Government may extend the term of this contract by written notice to theContractor within [insert the period of time within which the Contracting Officermay exercise the option]; provided that the Government gives the Contractor apreliminary written notice of its intent to extend at least 60 days (60 days unless adifferent number of days is inserted) before the contract expires. The preliminarynotice does not commit the Government to an extension.
(b) If the Government exercises this option, the extended contract shall beconsidered to include this option clause.
(c) The total duration of this contract, including the exercise of any options underthis clause, shall not exceed [](months)(years).
Page 22 of 26
52.222-2 PAYMENT FOR OVERTIME PREMIUMS. (JUL 1990)
(a) The use of overtime is authorized under this contract if the overtime premiumdoes not exceedS0.00 or the overtime premium is paid for work-
(1) Necessary to cope with emergencies such as those resulting fromaccidents, natural disasters, breakdowns of production equipment, oroccasional production bottlenecks of a sporadic nature;
(2) By indirect-labor employees such as those performing duties inconnection with administration, protection, transportation, maintenance,standby plant protection, operation of utilities, or accounting;
(3) To perform tests, industrial processes, laboratory procedures, loadingor unloading of transportation conveyances, and operations in flight orafloat that are continuous in nature and cannot reasonably be interruptedor completed otherwise; or
(4) That will result in lower overall costs to the Government.
(b) Any request for estimated overtime premiums that exceeds the amountspecified above shall include all estimated overtime for contract completion andshall-
(1) Identify the work unit; e.g., department or section in which therequested overtime will be used, together with present workload, staffing,and other data of the affected unit sufficient to permit the ContractingOfficer to evaluate the necessity' for the overtime;
(2) Demonstrate the effect that denial of the request will have on thecontract delivery or performance schedule;
(3) Identify the extent to which approval of overtime would affect theperformance or payments in connection with other Government contracts,together with identification of each affected contract; and
(4) Provide reasons why the required work cannot be performed by using
multishift operations or by employing additional personnel.
* insert either "zero" or the dollar amount agreed to during negotiations. The insertedfigure does not apply to the exceptions in subparagraph (a)(1) through (a)(4) of theclause.
52.222-3 CONVICT LABOR. (JUN 2003)
Page 23 of 26
52.222-21 PROHIBITION OF SEGREGATED FACILITIES. (APR 2015)
52.222-26 EQUAL OPPORTUNITY. (APR 2015)
52.222-35 EQUAL OPPORTUNITY FOR VETERANS. (JUL 2014)
52.222-36 EQUAL OPPORTUNITY FOR WORKERS WITH DISABILITIES. (JUL 2014)
52.222-37 EMPLOYMENT REPORTS ON VETERANS. (JUL 2014)
52.222-40 NOTIFICATION OF EMPLOYEE RIGHTS UNDER THE NATIONAL LABORRELATIONS ACT. (DEC 2010)
52.222-50 COMBATING TRAFFICKING IN PERSONS. (MAR 2015)
52.223-6 DRUG-FREE WORKPLACE. (MAY 2001) '
52.223-18 ENCOURAGING CONTRACTOR POLICIES TO BAN TEXT MESSAGINGWHILE DRIVING. (AUG 2011)
52.225-13 RESTRICTIONS ON CERTAIN FOREIGN PURCHASES. (JUN 2008)
52.227-1 AUTHORIZATION AND CONSENT. (DEC 2007) -- ALTERNATE I (APR1984)
52.227-2 NOTICE AND ASSISTANCE REGARDING PATENT AND COPYRIGHTINFRINGEMENT. (DEC 2007)
52.227-14 RIGHTS IN DATA-GENERAL. (MAY 2014)
52.228-7 INSURANCE - LIABILITY TO THIRD PERSONS. (MAR 1996)
52.230-6 ADMINISTRATION OF COST ACCOUNTING STANDARDS. (JUN 2010)
52.232-22 LIMITATION OF FUNDS. (APR 1984)
52.232-23 ASSIGNMENT OF CLAIMS. (MAY 2014)
52.232-25 PROMPT PAYMENT. (JUL 2013)
52.232-39 UNENFORCEABILITY OF UNAUTHORIZED OBLIGATIONS. (JUN 2013)
52.232-40 PROVIDING ACCELERATED PAYMENTS TO SMALL BUSINESSSUBCONTRACTORS. (DEC 2013)
Page 24 of 26
52.233-1 DISPUTES. (MAY 2014)
52.233-3 PROTEST AFTER AWARD. (AUG 1996) - ALTERNATE I (JUN 1985)
52.233-4 APPLICABLE LAW FOR BREACH OF CONTRACT CLAIM. (OCT 2004)
52.242-1 NOTICE OF INTENT TO DISALLOW COSTS. (APR 1984)
52.242-3 PENALTIES FOR UNALLOWABLE COSTS. (MAY 2014)
52.242-13 BANKRUPTCY. (JUL 1995)
52.243-2 CHANGES - COST-REIMBURSEMENT. (AUG 1987) - ALTERNATE V (APR
1984)
52.244-2 SUBCONTRACTS. (OCT 2010)
52.244-5 COMPETITION IN SUBCONTRACTING. (DEC 1996)
52.244-6 SUBCONTRACTS FOR COMMERCIAL ITEMS. (APR 2015)
52.245-1 GOVERNMENT PROPERTY- ALTERNATE II. (APR 2012)
52.249-5 TERMINATION FOR CONVENIENCE OF THE GOVERNMENT (SEP 1996)
52.249-14 EXCUSABLE DELAYS. (APR 1984)
52.252-2 CLAUSES INCORPORATED BY REFERENCE. (FEB 1998)
This contract incorporates one or more clauses by reference, with the same force andeffect as if they were given in full text. Upon request, the Contracting Officer will maketheir full text available. Also, the full text of a clause 'may be accessed electronically atthis/these address(es): [Insert one or more Internet addresses]
52.253-1 COMPUTER GENERATED FORMS. (JAN 1991)
NRCI0I0 NRC ACQUISTION REGULATION (NRCAR) PROVISIONS AND CLAUSES(AUG 2011)
Applicable NRCAR provisions and clauses located in 48 CFR Chapter 20 are herebyincorporated by reference into this contract/order.
(End of Clause)
Page 25 of 26
SECTION J - List of Documents, Exhibits and Other Attachments
Attachments:A -PARCS SOWB - Special RequirementsC - Trace Code Update ProcessD -Trace Standard F90E - MLSR Instructions
Page 26 of 26
DESCRIPTIONISPECIFICATIONS/WORK STATEM~ENT
Contents
0.1 Title of Project0.2 Introduction0.3 Background0.4 Objective0.5 Scope of Work*C.6 List Services/Deliverables0.7 Estimated Level-of-Effort (LOE)0.8 Estimated Materials Required0.9 Reporting Requirements0.10 Publications0.11 Government-Furnished Property0.12 Access to Government Property and Facilities0.13 Place of Performance0.14 Security Requirements0.15 Post-award Orientation (kickoff) or Periodic Progress Meetings0.16 Contracting Officer's Representative (CO R)0.17 Key Personnel0.18 General - Contractor Personnel0.19 Contractor Travel
1
DESCRIPTIONISPECIFICATIONS/WORK STATEMENT
C.1 Title of Project
Contractor Support for the Purdue Advanced Reactor Core Simulator (PARCS) CodeSuite.
C.2 Introduction
As part of the review of a nuclear power plant design undertaken under 10 CFR Part 50and 52, the staff customarily conduct confirmatory calculations with independent codesand methods which the U.S. Nuclear Regulatory Commission (NRC) developed andassessed without nuclear industry guidance. The NRC suite of confirmatory codes isStandardized Computer Analyses for Licensing Evaluation (SCALE), PARCS, andTRACE 1. These confirmatory calculations are important for two reasons: they requirethe NRC to develop and maintain a suite of codes for confirmatory nuclear and systemsengineering analyses, and performance of these exercises by NRC staff allows staff todevelop a deeper understanding of the underlying algorithms and phenomena of thesystems that are being analyzed. The NRC staff then use these confirmatory codes("software") to independently demonstrate the safety of a licensee action with a safety-related calculation. Specifically, the confirmatory codes are used to complement thestaff review of the power plant design to ensure that it meets the guidance described inChapter 15 of the Standard Review Plan (SRP) for Light Water Reactors (LWRs)(NUREG-0800).
This suite of confirmatory codes is collectively grouped into an Evaluation Model (EM) inwhich the different phenomena may be modeled via the use of different codes. GeneralEM development has been documented in a process that is described in bothNUREG/CR-5249, "Quantifying Reactor Safety Margins" and Regulatory Guide (RG)1 .203, 'Transient and Accident Analysis Methods."
The support for the NRC's EM development from the Office of Nuclear RegulatoryResearch (RES), Division of Systems Analysis (OSA) is ongoing. The Office of NuclearRegulation (NRR) and the Office of New Reactors (NRO) continue to need EM codesupport in the form of modifying TRACE/PARCS and PARCS models anddocumentation in ways that support NRC staff regulatory decision making with regardsto the safety of license amendments, advanced plant designs, and power uprates. ThePARCS predictions are usually compared to measured data from past industry initiatives.and against common code benchmarks that have been employed by nuclear plantdesigners.
The PARCS source code consists of the coding residing within the contractor-maintained, standalone PARCS distribution, the PARCS coding residing within the
' TRACE is an-acronym for TRAC (Transient Reactor Analysis Code) RELAP (Reactor Excursionand Leak Analysis Program) Advanced Computational Engine.
2
TRACE/PARCS distribution, and the PARCS coding residing within the RELAP/PARCSdistribution.
The contractor shall provide all personnel, equipment, supplies, facilities, transportation,tools, materials, supervision, and other items and non-personal services necessary toperform PARCS code suite (PARCS, GenPMAXS and TRIPEN/AGREE) maintenance,user support, assessment, development, and user training as defined in this Statementof Work (SOW), except for those items specified as Government-furnished property andservices.
C.3 Background
Fundamental to reactor safety analysis is the ability to predict the fission power anddecay heat sources that arise under normal, off-normal, and accident conditions. Quasi-steady-state calculations of spatial core~power and burn-up distributions over coreoperating cycles are used to analyze (a) peak pin powers in relation to fuel thermallimits, (b) reactivity and power control, (c) safe shutdown margins, (d) slow spatial xenontransients and oscillations, and (e) the initial conditions of spatial reactivity feedbackcharacteristics, fission power, stored heat, and decay power. Dynamically coupledtransient calculations are especially important in analyzing the spatial kinetics ofreactivity insertion transients (e.g., rod bank withdrawal, rod drop, rod ejection) and thecore power surges and oscillations associated with transient over-cooling events (e.g.,turbine trip), flow and boiling instabilities, and anticipated transients without scram(ATWS).
This predictive ability entails the use of three-dimensional (3-D) reactor physics codessuch as PARCS, which has been continuously developed by RES since 1998. PARCShas been dynamically coupled to the system thermal hydraulic code TRACE and isavailable as both an embedded module within TRACE and as a standalone code. Thedynamically coupled TRACE/PARCS is used for the analyses of normal operations andtransients in operating reactors (control and power maneuvers), analyses to supportresolution of generic issues, evaluation of emergency procedures and accidentmanagement strategies, confirmation of licensee's analyses, training exercises for NRCstaff, and supporting analyses for the certification review of current reactor designs,advanced reactor designs, and research and test reactors.
PARCS is a nodal reactor analysis code that calculates the transient and steady statecore power (and other safety significant reactor parameters) through the numericsolution to a discretized formulation for the neutron diffusion equation. In standalone-maintained form, PARCS is coupled to PATHS 2 for steady-state BWR and PWRanalysis, and coupled also to a simple mass-energy balance solver for steady-statePWR analysis. SNAP (Symbolic Nuclear Analysis Package) provides a graphicalinterface to PARCS.
GenPMAXS 3 provides the key interface between PARCS and the following latticephysics codes: CASMO, HELlOS, TRITON, POLARIS, WlMS, CONDOR, and
2 PATHS is an acronym for PARCS Advanced Thermal Hydraulic Solver.
3 GenPMAXS is the code for Generating the cross section interface file PMAXS.
3
SERPENT. GenPMAXS also provides the cross section processing interface forconversion into the PARCS format from lattice physics data and the TRIPEN 4/AGREE5
code. In addition to converting lattice physics-averaged cross sections, GenPMAXSanalytically solves for the flux discontinuity along the fuel reflector interface.
TRIPEN/AGREE is used for the analysis of prismatic gas cooled reactor designs.Similar to the PARCS code, TRIP EN is a nodal reactor analysis code, but it has beenformulated specifically for~triangular meshes. The AGREE code that has been coupledto TRIPEN solves for the heat transfer within the triangular portion of a hexagonal blockwith a system of 1-D flow channels for fluid flow, and a thermal-circuit conductionapproach for the heat transfer. As in PATHS, AGREE provides thermal-hydraulicfeedback for cross section interpolation.
PAROS code suite users include all users that have received the PAROS code suite orportions thereof through NRC licensing rights (e.g. Code Applications and MaintenanceProgram (CAMP)), international bilateral cooperative agreements, Thermal HydraulicsCodes Users Group, NRC contractors, and NRC staff).
C.4 Objective
The objective of this contract is to obtain maintenance, code support, assessment,development, and user training of the PARCS and GenPMAXS codes and the interfaceof PARCS with RELAP, TRACE, and SNAP as well as maintaining TRIPEN/AGREEsupport for the OECD-NEA-LOFC benchmark. The PARCS code supports independentregulatory decision making through its employment as a tool in confirmatory safetyreviews of power plant operator actions, core designs, power uprates, and licenseamendments.
C.5 Scope of Work
The contractor shall provide all resources necessary to accomplish the tasks anddeliverables described in this SOW. The contractor shall provide ongoing maintenance,code support, assessment, development and user training for the PARCS code suite(PARCS including the interface of PARCS with TRACE, RELAP, and SNAP, as well asthe GenPMAXS and TRIPEN/AGREE codes).
The~contractor shall maintain each portion of the PARCS code suite within its' ownconfiguration control system, perform model development, and PARCS standalone andcoupled code (TRACE/PAROS) assessment.
The work under this contract shall apply to, but not be limited to, the operating fleet ofLWRs, as well as more advanced Generation Ill (ABWR and APWR), Generation 1I1+(ESBWR and EPR), and small modular reactor LWR designs; High Temperature Gas-Cooled Reactors (HTGRs); research and training reactors; Aqueous Homogeneous
4 TRIPEN is an acronym for TRiangular Polynomial Expansion Nodal method.
S GE (Advanced Gas REactor Evaluation) is a 3-D gas dynamics and heat transfer code.
4
Reactors; fast reactors; and VVERs (water water energy reactors). During the course ofthis contract, the contractor may be required to apply PARCS expertise to otheradvanced reactor designs, as directed by the Contracting Officer's Representative(COR).
All PARCS and GenPMAXS code changes shall be consistent with Attachment A(Special Requirements) and Attachment B (TRACE Standard F90 ProgrammingPractices and General Design Philosophies).
The contractor shall test PAROS and GenPMAXS code changes a variety ofcompiler/operating system combinations. The contractor shall use the followingcompilers during maintenance and development of the PARCS source code:
Windows (Intel Visual Fortran)Linux (g95, Lahey, gfortran, Intel, NAG, Portland Group)
The contractor shall ensure that the above compilers and plafforms are in place for theentire period of performance, and that these compilers are maintained at their mostcurrent release levels throughout the contract. The contractor be required to extendsupport to other compiler/operating system combinations that are not listed as a result ofchanging priorities.
C.6 List of Services/Deliverables
C.6.1 Specific Tasks
The contractor shall perform the tasks listed below. All activities under these tasks shallbe prioritized by the COR through technical direction.
Task 1 - Code Maintenance
Subtask 1.1: Identify Code Bugs
The contractor shall identify all code bugs and maintain them in a "bug report" documentwhich summarizes code errors (bugs, unexplained behavior, and documentationproblems). This document shall list code bugs in tabular form and shall include thefollowing information for each bug: a summary description of the bug; the date the bugwas reported; the person who reported the bug; the status of the bug (i.e. in what codeversion the bug was addressed or will be addressed); the estimated level of effort interms of hours to correct the bug; and the recommended priority level. Priority ordershall be identified using a numerical scheme with number one (1) being the highestpriority. The contractor shall list code bugs in descending priority order in the report.
The contractor shall populate the bug report based on information received from theCOR and all authorized PARCS users per the COR provided user list. The final versionof the monthly bug report shall be maintained by the contractor.
The most current PARCS bug report in prioritized format will be provided to the.contractor upon contract award, along with the current PARCS user list. The COR willprovide the contractor updated PARCS user list(s) as necessary throughout the contractperiod of performance.
5
Deliverable for Subtask 1.1: Bug Report
The contractor shall deliver a bug report with a recommended work priority for each bugelectronically with the monthly letter status rePort (MLSR). The COR will review thereport and provide any comments including changes to the proposed work priority within5 business days of report receipt. The contractor shall reflect the COR comments in thefollowing month's report.
Subtask 1.2: Perform Code Fixes
Undler COR technical direction, the contractor shall make changes to the collectivePARCS source code in response to bugs reported by the COR and all other PARCSusers,, as captured in the bug-report under Subtask 1.1. The contractor shall perform allwork in accordance with priorities indicated in the Bug Report, as approved by the COR.
PARCS bugs may include bugs identified wit'h the PARCS plug-in with SNAP 6, bugsidentified due to the use of TRACE/PARCS or RELAP/PARCS in coupled form, bugsidentified due to the use of PARCS in standalone form, or bugs identified due toinconsistenc~ies in cross section methodology or formatting between PARCS and any ofthe several lattice physics codes (SCALE, HELlOS, CASMO 7, etc.) that are readable byGenPMAXS. -
Upon COR direction, the contractor shall also update code documentation as the resultof the correction of typos, the elimination of features that are no longer supported in thecode, or the desire of users to make the documentation more clear and relevant, whichmay be included in the bug report.
The contractor shall test any PARCS source code changes made as a result of codebugs against the PARCS regression test suite before being checked into the codeversion control system. New test problems that are added to the PARCS or GenPMAXStest suites as a result of the correction of code bugs shall be documented in theHyperText Markup Language (HTML) summary file. The contractor shall modify the runscripts for the test suite as a result of any test problem additions, changes, or deletions,and shall modify the build scripts as a result of any additions, changes, or deletions tothe source code.
The contractor shall create new versions of PARCS in response to code bug corrections.The contractor shall maintain these different code versions using a version controlsystem methodology, and this methodology shall have the ability to retrieve previouslyreleased code versions. Each retrieved code version shall contain enough informationsuch that it can be a self-contained distribution (an archive). Previous code distributionswill be provided to the contractor by the COR at tirmie of contract award.
The root name (upper-most directory) of the code distribution shall include the codeversion name. Each code distribution (i.e., in directories below the upper-most root
6 SNAP is an acronym for Symbolic Nuclear Analysis Package
7 Although written in capital letters, the names HELlOS and CASMO are not acronyms.
6
directory) shall contain the following: the source code and associated libraries; operatingsystem specific build scripts and MSVS (Microsoft Visual Studio) project workspaces forre-building the executable from the source code; code documentation, including aprogrammer's manual, a theory manual, and a user manual; and code versiondocumentation, which shall include directories that contain code differences by version(Fortran source code differences with respect to the previous version); the PARCS testsuite; and an HTML summary file that describes the changes that were incorporated into.that specific code version.
The following information shall be included in the HTML summary file: the code version;the developer responsible for the code version; the code peer reviewer; the date thecode version is submitted or checked-in; the base version over which the code version isdeveloped; a code summary that verbally describes the changes within the code version;new modules or files that have been added to the code version; modules or files thathave been deleted from the code version; the differences of the changed files;summaries of the code differences for each Changed module; changes to thedocumentation (e.g. user, theory, and programmer manuals as applicable) as a result ofthis code version change; changes that effect input, SNAP, or output; and regressiontest results. New test problems that are added to the regression/assessment suites asthe result of this code version shall also be listed.
Deliverable for Subtask 1.2: PARCS Code Distribution to COR
The contractor shall send each checked-in code version as a PARCS distribution to theCOR. The distribution shall be archived with SecureZIP and transmitted either throughemail, an NRC website, or another mechanism specified by the COR..The contractorshall provide the PARCS distribution to the COR within 5 business days of thecompletion of a checked-in PARCS code version.
Subtask 1.3: Prepare TRACE Updates
At a frequency determined by the COR (i.e., after a number of PARCS versions havebeen checked-in to the PARCS, version control system), the contractor shall prepare aTRACE update for submittal to the NRC website. This update shall include the revisedPARCS source code (and the revised TRACE source code, if necessary), a list of thedifferences between code versions embedded in text files, new test problemsformulated to test the code update, revised code documentation, and the results ofautomated testing against the TRACE regression suite. This update process isdescribed in detail in Attachments A and C.
Deliverable for Subtask 1.3: TRACE Update File
The contractor shall upload the TRACE Update file to the NRC website or submit theTRACE" Update file directly to the COR within 10 business days of COR request. Afterthe file is uploaded, the contractor shall provide an email confirmation to the COR within,1 business day of the upload.
Task 2 - Code Support
As directed by the COR, the contractor shall provide analysis and consultation supportrelated to PARCS. This support shall include, but is not limited to: guidance on PARCS
7.
use, explanations of the algorithms that are coded into PARCS, develop PAROS,TRACE/PARCS, RELAP/PAROS models, interpret results, or explain underlying physicsphenomena or algorithms, explanations of the input format, guidance on best-practices("how to approach a problem"), the interpretation of any associated lattice physicsmodels or PMA)XS cross section libraries that are affiliated with the core or nuclearpower plant model, performing pre-analysis scoping studies, performing phenomenaidentification and ranking table (PIRT) processes in accordance with NUREG/CR-5249,peer review analysis, and responding to code user questions and comments provided tothe contractor by the COR. Analysis and consultation support may require preparationof briefing materials, technical presentations, documents, tutorial sessions, emails, orany other written correspondence necessary, as well as participation in NRC meetings,ACRS (Advisory Committee on Reactor Safeguards) reviews, and CAMP meetings.
Deliverable for Task 2: Code Support Documentation
Upon request of the.COR, the contractor shall provide written code support documents(i.e. explanatory document) to the COR via email within 10 business days of the CORrequest.
Task 3 - Code Development
Upon COR direction and prioritization, the contractor shall perform any PARCS sourcecode development that may be necessary as a result of user feedback, future RESprogram needs, regulatory user needs, and CAMP needs. This code development shallnot be limited to code fixes, but shall be broadly applied to significant code changes thatsupport user convenience (e.g., improved error checking and advanced editing options),code robustness and speed e~g., linear solver upgrades and changes and advancedneutronic methods), significant modeling enhancements, or utility codes or scripts thatsupport PARCS code use.
Any PARCS source code changes made as a result of code enhancements or modelingchanges shall be tested against the PARCS regression test suite before being checked-in to the code version control system. The contractor shall modify the run scripts for thetest suite as a result of any test prol~lem additions, changes, or deletions, and shallmodify the build scripts as a result of any additions, changes, or deletions to the sourcecode. The contractor shall revise the User, Theory, and Programmer's manuals toreflect the~code development activity.
Subtask 3.1: Pre-Code Documentation Requirements
For each code development activity, the contractor shall develop the following
documentation, per the guidance specified in NUREG-1 737:
Software Requirements Specification (SRS)
The SRS is a technical document that focuses on the underlying algorithms, technicalspecifications, and requirements of the software.
Software Design and Implementation Document (SDID)
8
The SDlD describes the implementation of the technical specifications and algorithmsoutlined in the SRS, i.e., how the software will be structured and designed.
Qualification Test Plan (QTP) (also referred to as the "test plan" in NUREG-1737)
The Qualification Test Plan is a document which describes how the implementedcapability will be tested, i.e. the test problems which will be used to demonstrate the newcapability.
The contractor shall provide these documents to the COR prior to commencement ofany code development. The contractor shall not proceed with code development untilprior written approval has been received from the coR. For each code developmentactivity the contractor shall include the development name as part of the deliverable title.
Deliverable One for Subtask 3.1: Software Requirements Specification (SRS)
The contractor shall deliver the SRS within 20 business days after Subtask 3.1commencement.
Deliverable Two for Subtask 3.1: Software Design and Implementation Document(SDID)
The contractor shall deliver the SDID within 30 business days after Subtask 3.1
commencement.
Deliverable Three for Subtask 3.1: Qualification Test Plan (QTP)
The contractor shall deliver the QTP within 40 business days after Subtask 3.1commencement.
Subtask 3.2: Develop Resource Estimate for Code Development Activity
After COR approval of the pre-code documents developed in Subtask 3.1, the contractorshall develop a resource estimate of the effort required to implement a stable and testedcode version that is capable of meeting the requirements specified in the SRS. Thisresource estimate will not be binding, but will enable the OcRn to closely monitor theeffort being expended during the development task.
Deliverable for Subtask 3.2: Resource Estimate
The contractor shall provide the resource estimate via email and included as a notewithin the financial status section of the MLSR. The resource estimate shall be emailedto the OcR within 3 business days of OcR approval of pre-code documentation.
Subtask 3.3: Perform Code Development
The contractor shall implement the method outlined in the SRS and SDID into the lateststable PAROS version. During development, the contractor shall test the beta codeversion against a test problem(s) that was developed for the QTP. It is expected that theOcR and other NRC staff will peer review and test this draft distribution, and that thecontractor shall make continual changes to the draft code distribution (i.e., source code,
9
build scripts, test problems, code manuals (as applicable), etc.) as a result of this peerreview. This process may result in numerous submissions of Deliverable One forSubtask 3.3
Deliverable One for Subtask 3.3: Draft PARCS Distribution
The contractor shall provide the first PARCS test version to the COR, along with betasource code and draft documentation, within 40 business days of Subtask 3.3commencement. Each subsequent draft distribution shall be provided to the COR within20 business days of receipt of comments from COR.
Deliverable Two for Subtask 3.3: Final PARCS Distribution
The contractor shall provide to the COR the final PAROS distribution with theimplemented coding. This distribution shall be organized as described in Subtask 1.2,with the addition of test problems to the PARCS test suite that test this functionality andshall be provided to the COR within 20 business days of the receipt of COR commentson the last draft distribution.
Subtask 3.4: Prepare Completion Report
The contractor shall prepare a Completion Report (CR) that documents theprogramming effort. Specifically, the report shall summarize the methodology, software,and user changes, and shall include calculation results that demonstrate the changedcoding.
Deliverable for Subtask 3.4: Completion Report
The contractor shall deliver a completion report to the COR within 30 business days ofthe completion of each programming effort.
Subtask 3.5:. Prepare TRACE Updates
At a frequency to be determined by the COR, the contractor shall prepare a TRACEupdate for submittal to the NRC website. This update shall include the new PARCSsource code (and new TRACE source code, if necessary), the differences between codeversions embedded in text files, new test problems formulated to test the code update,code documentation, and the results of automated testing against the TRACE regressionsuite. This update process is described in detail in Attachments A and C.
Deliverable for Subtask 3.5: TRACE Update File
The contractor shall upload the TRACE Update file to the NRC website or submit theTRACE Update file directly to the COR within 10 business days of COR request. If thefile is uploaded, the contractor shall provide an email confirmation to the COR within 1business day of the upload..
Task 4 - GenPMAXS Code Support and Maintenance
The contractor shall provide technical support and code maintenance for GenPMAXS toassure the consistency and accuracy of the cross section data that feeds PARCS.
10
Subtask 4.1: Maintain GenPMAXS in a Version Control System
The contractor shall maintain GenPMAXS in a version control system, each versionbeing retrievable as a self-contained unit.. Along with each version the contractor~shallstore the build system (MSVS workspaces, Linux and windows make files, and Source),the test suite (test problems and run scripts), and the code documentation. TheGenPMAXS code documentation shall include a manual describing the use andmethodology behind GenPMAXS, as well as documents describing known issues,planned features, and supported features. Previous code distributions will be providedto the contractor by the COR at time of contract award.
Subtask 4.2: Correct GenPMAXS Bugs
The contractor shall correct bugs resulting from the use of GenPMAXS for reading incross section data supplied by the lattice physics codes. These bugs shall be prioritizedby the COR. Any new test problems that are added to the GenPMAXS test suite as aresult of the correction of code bugs shall be documented in the GenPMAXS manual.
Subtask 4.3: Update GenPMAXS Source Code
To support PARCS code development in Task 3, the contractor shall perform majorupdates to the GenPMAXS source as a result of changes to underlying physics methodsor cross section methodology within PARCS. These updates shall be prioritized by theCOR. The contractor shall modify the run scripts for the test suite as a result of any testproblem additions, changes, or deletions, and shall modify the build scripts as a result ofany additions, changes, or deletions to the source code. Before checking in eachGenPMAXS version to the version control system, each code version shall be testedagainst the common SCALE/GenPMAXS regression testing system. This testing systemwill be provided to the contractor at time of contract award.'
Deliverable for Subtask 4.3: GenPMAXS Distribution to COR
The contractor shall send each checked-in code version as a GenPMAXS distribution tothe COR and shall include a SCALE/GenPMAXS regression testing report, which willinclude an HTML testing summary. The GenPMAXS distribution shall be provided to theCOR via the mechanism specified by the COR, within 5 business days of the completionof the SCALE/GenPMAXS regression test.
Subtask 4.4: Analysis Support for GenPMAXS
The contractor shall provide analysis support for the use of GenPMAXS. This supportshall include, but not be limited to: guidance on GenPMAXS use, explanations ofunderlying GenPMAXS algorithms, interpretation of lattice physics or PMAXS crosssection libraries or models, interpretation of PARCS and TRACE/PARCS results,explanations of the input format, and guidance on best-practices. This support may alsoinclude the development of briefing materials, documents, or emails that provide writtenexplanations or interpretations of cross section libraries or methodology, and supportprogram and ACRS reviews.
Deliverable for Subtask 4.4: GenPMAX(S Code Support Documentation
11
Upon request of the COR, the contractor shall provide written Code support documents(i.e. explanatory document) to the COR via email within 10 business days of the CORrequest.
Task 5 - PARCS and GenPMAXS User Training
The contractor shall provide two training sessions that each encompass training on bothPARCS and GenPMAXS. The training sessions shall each be 8 hours in length andshall be provided to NRC staff and contractors, at NRC Headquarters, Rockville, MD.The exact dates and times of these training sessions will be determined by the COR.
The contractor shall update training materials for the GenPMAXS and PARCS trainingsessions, as provided and directed by the COR. The contractor shall provide trainingsessions based upon the most current stable code manuals in effect at .the time of thetraining.
As part of this task, the contractor shall revise example/model instructional slidesprovided by the COR to supplement the current GenPMAXS and PARCS stable codemanuals. This training shall include instruction on PARCS and GenPMAXS theory anduse, including example problems and instruction on code execution, and shall beprovided as instructor led training to audiences of no more than 30 participants in eachsession.
Deliverable One for Task 5: Draft PARCS/GenPMAXS Training Materials
The deliverable shall be the revised PARCS/GenPMAXS training materials. This shallinclude Power point slides, starter problem sets, and worked problem sets that illustratethe theory and use of PARCS/GenPMAXS. This shall be delivered to the COR 30business days prior to training.
Deliverable Two for Task 5: Final PARCS/GenPMAXS Training Materials
The contractor shall provide a final version of the training materials within 5 businessdays of receipt of COR comments on draft.
Task 6 - Support for OECD-NEA LOFC HTTR (High-Temperature Engineering TestReactor) Benchmark
The contractor shall support the participation of the NRC within the Organization forEconomic Cooperation and Development/Nuclear Energy Agency (OECD/NEA) HTTRbenchmark by performing the tasks stated below. The JAEA (Japanese Atomic EnergyAgency) had originally planned three separate LOFC (Loss of Forced Cooling) testsunder different conditions as part of the OECD/NEA LOFC benchmark. The first test,Run 1, was completed, and a post-test TRIPEN/AGREE model for Run 1 data isavailable. The second and third tests (Runs 2 and 3) are to be completed pendingHTTR restart in FY 2015, and pre-test TRIPEN/AGREE models for Runs 2 and 3 havebeen developed.
Subtask 6.1: TRIPEN/AGREE Analysis of OECD-NEA LOFC Tests
12
As directed by the COR, the contractor shall review the models that have beendeveloped for Runs 2-3, develop calculational notebooks for the models, and documentmodel revisions, if necessary. The contractor shall also perform post-test analysis ofRun 2 and Run 3 of the LOFO tests. When the experimental data becomes available,the contractor shall compare the models against the experimental data and makerevisions to the models, if necessary. The contractor shall provide interpretation of theresults presented in the briefing materials, explain the underlying physics phenomena oralgorithms, if necessary, or explain input/modeling choices via conference calls or anemail to the COR.
Deliverable One for Subtask 6.1: Draft TRIPEN/AGREE Models and CalculationalNotebooks
The contractor shall deliver the draft models and draft calculational notebooks to theCOR within 50 business days of receipt of the Run 2 and Run 3 digitized test data fromthe COR.
Deliverable Two for Subtask 6.1: Draft Briefing Materials to Support the Fourth ProgramReview Group/Management Board OECD LOFO Meeting
The contractor shall deliver post-test analysis of Run 2 and Run 3 of the LOFC tests inthe form of draft presentation(s). The contractor shall, deliver these materials to the CORwithin 70 business days of receipt of the Run 2 and Run 3 digitized test data from theCOR. It is anticipated that these materials shall be revised by the contractor as a resultof feedback from the COR.
Deliverable Three for Subtask 6.1: Final Briefing Materials, Models, and CalculationalNotebooks to Support the Fourth Program Review Group/Management Board OECDLOFO Meeting
The contractor shall deliver post-test analysis of Run 2 and Run 3 of the LOFC tests inthe form of final presentation(s), final models for Runs 2 'and 3, and final calculationalnotebooks for Runs 2 and 3. The contractor shall deliver these materials to the CORwithin 90 business days of receipt of the Run 2 and Run 3 digitized test data from theCOR.
Subtask 6.2: TRIPEN/AGREE Version Control
The contractor shall support the code maintenance, version control, and documentationof the TRIPEN/AGREE code. The contractor shall create new versions ofTRIPEN/AGREE in response to code bug corrections. The contractor shall maintainthese different code versions using a version control system methodology, and thismethodology shall have the ability to retrieve previously released code versions. Alongwith each code version the following items shall be stored: the build system including theassociated SCons scripts; the test suite (test problems and run scripts); and the codedocumentation (user and theory manuals). Each checked-out and retrieved codeversion shall have been tested against the TRIPEN/AGREE test suite (5 models), andshall contain enough information such that it can be a self-contained distribution (anarchive). The latest stable TRIPEN/AGREE code distribution will be provided to thecontractor by the COR at time of contract award.
13
Deliverable for Subtask 6.2: TRIPEN/AGREE Code Distribution to COR
The contractor shall send each checked-in code version as a TRIPEN/AGREEdistribution to the COR within 5 business days of COR request. The contractor shallarchive the distribution with SecureZIP and transmitted via a mechanism specified by theCOR.
Task 7 - Peuform PARCS Assessment against Watts Bar VERA
The contractor shall perform an assessment of SCALE/GenPMAXS/PARCS against theVERA benchmark that has been developed for the Watts Bar Unit 1 (WBN1) startup core(CASL-U-2012-0131-002). Throughout the assessment, the contractor shall participatein monthly conference calls with the COR and other NRC staff to discuss the progress ofthe assessment.
Deliverable One for Task 7: Draft PARCS / Watts BarNERA Models and Monthly StatusDocumentation
/,
The contractor shall provide draft slides and models summarizing monthly progress.The draft slides shall discuss results, model inputs, and interpretations of results. Thecontractor-shall provide these items to the COR 1 business day prior to each monthlyconference call.
Deliverable Two for Task 7: Final PARCS / Watts BarNERA Models andDocumentation
The contractor shall provide the following: final models, calculational notebook (s), andfinal assessment report. These items shall be provided to the COR within 50 businessdays of receipt of COR comments on draft materials after the final monthly conference•call.
Task 8 - Exponentially Varying Control Rod History Model
Currently, the PARCS methodology relies on linear interpolation of lattice physicscalculations performed at various control rod histories (i.e., between fully controlled andfully un-controlled nodes). This linear weighting of the cross section data between thecontrol rod states occurs regardless of the amount of time spent in each of the previousstates, or the order of control-bank sequence. To account for the fact that the spectrumof the current nodal state should be more heavily weighted by its most recent state, it willbe necessary for the contractor to implement an exponential weighting of control rodhistory interpolation.
Subtask 8.1: Pre-Code Documentation Requirements
Prior to implementation of this methodology, the contractor shall develop the followingdocumentation, per the guidance specified in NUREG-1 737:
Software Requirements Specification (SRS)
The SRS is a technical document that focuses on the underlying algorithms, technicalspecifications, and requirements of the software.
14
SoftwareDesiqn and Implementation Document (SDID)
The SDID describes the impiementation of the technicai specifications and algorithmsoutlined in the SRS, i.e., how the software will be structured and designed.
Qualification Test Plan (QTP) (also referred to as the "test plan" in NUREG-1737)
The Qualification Test Plan is a document which describes how the implementedcapability will be tested, i.e. the test problems which will be used to demonstrate the newcapability. The contractor shall provide these documents to the COR prior tocommencement of any code development. The contractor shall not proceed with codedevelopment until prior written approval has been received from the COR. For eachcode development activity the contractor shall include the development name as part ofthe deliverable title.
Deliverable One for Subtask 8.1: Software Requirements Specification (SRS)
The contractor shall deliver the SRS within 20 business days after Subtask 8.1
commencement.
Deliverable Two for Subtask 8.1: Software Design and Implementation Document
(SDID)
The contractor shall deliver the SDID ,within 30 business days after Subtask 8.1commencement.
Deliverable Three for Subtask 8.1: Qualification Test Plan (QTP)
The contractor shall deliver the QTP within 40 business days after Subtask 8.1commencement.
Subtask 8.2: Perform Code Development
The contractor shall implement the method outlined in the SRS and SDID into the lateststable PARCS version. An edit with descriptive information regarding the weightingscheme shall be produced in the PARCS *.out file, in addition to the modified control rodhistory that shall be written to the *.dep file. The format of the *.dep file shall not bechanged with this new methodology. During development, the contractor shall test thisnew weighting scheme against Three Mile Island Cycles 1-2 (TMI C1-C2). The modelsand documentation for TMI C1-C2 have already been developed by NRC staff. TheCOR and other NRC staff will peer review this task, and that the contractor shall makecontinual changes to the draft code distribution (i.e., source code, build scripts, testproblems, code manuals (as applicable), etc.) as a result of this peer review. Thecontractor shall modify existing depletion test problems within the PARCS test suite inorder to test this functionality, and the testing scripts shall be modified to accommodatethese additional, modified test problems. This process may result in numeroussubmissions of Deliverable One for Subtask 8.2.
Deliverable One for Subtask 8.2: Draft PARCS Distribution'
15
The contractor shall provide the PARCS test version to the COR, along with beta sourcecode and draft documentation within 55 business days of start of Subtask 8.2.
Deliverable Two for Subtask 8.2: Final PARCS Distribution
The contractor shall provide to the COR the final PARCS distribution with theimplemented exponential control rod history scheme. This distribution shall beorganized as described in Subtask 1 .2 and shall be provided to the COR within 10business days of receipt of final COR comments on the last draft PARCS distribution.
Subtask 8.3: Prepare Completion Report
The contractor shall prepare a Completion Report (CR) that documents theimplementation of the exponentially varying control rod history model. Specifically, thereport shall summarize the methodology, software, and user changes, and shall includecalculation results that demonstrate the. changed coding.
Deliverable for Subtask 8.3: Completion Report
A completion report shall be delivered to the COR within 30 business days of thecompletion of the exponentially varying control rod history model.
Task 9 - Micro-depletion Algorithm Development and Implementation withinPAROS
PAROS currently employs a macroscopic depletion method, in which the assembly-homogenized, macroscopic cross sections are functionalized by thermal-hydraulic stateand node history. The nodal burnup within a node is found from a relation between thenodal burnup and the nodal power and heavy metal density, and the core-averagedpower, burnup, and heavy metal density. This nodal burnup is obtained incrementallyduring the cycle.
The change in nuclide concentration with respect to time is expressed as a function ofthe parent nuclides, the disintegration constants per nuclide, the one-group scalar fluxesand absorption cross sections. The solution of equations can be expressed in terms ofan exponential, or transition (transmutation) matrix, in which the matrix terms expressthe reaction rates and fractions and decay rates and fractions. This system of equationsis solved for the nuclide field within every reactor node.
The objective of this task is for the contractor to develop and implement a microscopicdepletion method within PARCS that is capable of reading in data from SCALE. In amicroscopic depletion method, the number densities and microscopic cross sections offuel assemblies are used separately to construct the macroscopic cross sections at agiven state point in the reactor.
Subtask 9.1: Pre-Code Documentation Requirements
Prior to implementation of this methodology, the contractor shall develop the following
documentation, per the guidance specified in NUREG-1737:
Software Requirements Specification (SRS)
16
The SRS is a technical document that focuses on the underlying algorithms, technicalspecifications, and requirements of the software.
Software Desiqn and Implementation Document (SDID)
The SDlD describes the implementation of the technical specificationsand algorithms
outlined in the SRS, i.e., how the software will be structured and designed.
Qualification Test Plan (QTP) (also referred to as the "test plan" in NUREG-1 737)
The Qualification Test Plan is a document which describes how the implementedcapability will be tested, i.e. the test problems which will be used to demonstrate the newcapability. The contractor shall provide these documents to the COR prior tocommencement of any code development. The contractor shall not proceed with codedevelopment until prior written approval has been received from the COR. For eachcode development activity, the contractor shall include the development name as part ofthe deliverable title.
Deliverable One for Subtask 9.1: Software Requirements Specification (SRS)
The contractor shall deliver the SRS within 20 business days after Subtask 9.1commencement.
Deliverable Two for Subtask 9.1: Software Design and Implementation Document(SDID)
The contractor shall deliver the SDID within 30 business days after Subtask 9.1commencement.
Deliverable Three for Subtask 9.1: Qualification Test Plan (QTP)
The contractor shall deliver the QTP within 40 business days after Subtask 9.1
commencement.
Subtask 9.2: GenPMAXS to Support for Micro-depletion
The contractor shall develop a microscopic cross section-oriented variant of the PMAXSfile (Purdue Macroscopic Cross Section). This file shall contain enough information suchthat it is capable of tracking either the macroscopic or microscopic cross sections of allexplicitly tracked nuclides and lumped nuclides. Cross sections evaluated at a referencecondition shall be incorporated, along with cross sections evaluated at "branched"conditions, either in explicit or derivative form. The methodology shall be organized intoseveral different types of blocks, depending upon the availability of cross section dataper nuclide.
The contractor shall also develop a variant of the GenPMAXS code that is capable ofreading in microscopic cross section data that has been processed by the ORlGIN-SBsequence of SCALE.
8 ORIGIN is an acronym for Oak Ridge Isotope GENeration and Depl~tion Code.
17
Deliverable for Subtask 9.2: Draft GenPMAXS Distribution
The contractor shall deliver a draft GenPMAXS distribution to the COR (as described inSubtask 4.1) that is capable of both reading in ORIGIN-S data and writing a microscopicPMAXS file, within 40 business days after Subtask 9.2 commencement.
Subtask 9.3: PAROS Binning Feature Input
The contractor shall generalize the input format such that the user has the option toinput, expand, or deprecate the number of considered nuclides in the depletion chain.The result will be some user choice over the number of nuclides tracked in the chain,with the depletion calculation ranging from coarse but quick running (a few hundrednuclides), to the most accurate but expensive (1946 nuclides). The methodology shallbin the number of nuclides, with categories determined by the number of nuclides. Thebinning of the nuclide groups shall take into account the "lumping" of nuclides for ease oftracking.
Deliverable for Subtask 9.3: First Draft PARCS Distribution with Binning Input
The contractor shall provide a PARCS test version to the COR, along with beta sourcecode and draft documentation. This test version shall be capable of processingadditional input cards that define user choice in the number and type of nuclides to track.The contractor shall deliver this draft code version to the COR within 40 business daysafter commencement of Subtask 9.3.
Subtask 9.4: Construction of Transmutation Matrix
The contractor shall implement programming changes over the draft PARCS distributiondelivered in Subtask 9.3 to include the construction of a transition matrix (which is amatrix Constructed from neutron reaction rates, fractions, nuclide decay, etc., and relatesthe rate of change of a nuclide to all of the nuclide sources and sinks).
Deliverable for Subtask 9.4: Second Draft PAROS Distribution with Transition MatrixConstruction
The contractor shall provide a PAROS test version to the COR, along with beta sourcecode and draft documentation. This test version shall be capable of building a transitionmatrix within PAROS that expresses the balance equations for the tracked nuclidesspecified in Subtask 9.2. This draft code version shall be delivered to the COR within 80business days after commencement of Subtask 9.4.
Subtask 9.5: Solution of Transmutation Matrix
The contractor shall implement a solution algorithm within the draft PARCS distributionthat was delivered in Subtask 9.3 that solves the transmutation matrix at an exposurestep by looping through the user-specified nuclides (Subtask 9.2), classifying nuclides aslong or short-lived, lumping short lived nuclides together and solving iteratively, andsolving for long-lived nuclides with a series solution.
18
Deliverable for Subtask 9.5: Third Draft Micro-depletion PARCS Distribution withTransmutation Matrix Solution
The contractor shall provide a PARCS test version to the COR, aiong with beta sourcecode and draft documentation. This code version shall be capable of calculating thenuclide distribution within each region of the core for a particular exposure step. Thisdraft code version shall be delivered to the COR within 80 business days aftercommencement of Subtask 9.5.
Subtask 9.6: Exposure Record Capability for Micro-depletion
The contractor shall update the draft PARCS distribution delivered in Subtask 9.5 to
include the following capabilities:
* PAROS shall be updated to re-construct and store macroscopic cross sectionsthat are functionalized with user specified histories and state variables, and thesemacroscopic cross sections shall be stored in PMAXS format as a function ofexposure and state.
* PARCS shall be updated such that it writes the microscopic cross section data tothe restart file during calculation, and the format of the restart file shall beupdated to accommodate this additional information.
* PARCS shall maintain the capability to compute and store the currentlycomputed history and thermal-hydraulic parameters. These variables shall bewritten to the "dep" (burnup) file during marching through burnup.
Deliverable One for Subtask 9.6: Fourth Draft Micro-depletion PARCS Distribution withImplementation of Restart Capability
The contractor shall provide a PAROS draft distribution to the COR, along with betasource code and draft documentation. This draft distribution shall be delivered to theCOR within 20 business days after commencement of Subtask 9.6.,
Deliverable Two for Subtask 9.6: Final PARCS Distribution
The contractor shall provide to the COR the final PARCS distribution with theimplemented coding. This distribution shall be organized as described in Subtask 1.2,with the addition of micro-depletion and macro-depletion test problems to the PARCStest suite that test the functionality. The contractor shall test the final code versionagainst TMI 01-02 and shall deliver it to the COR within 50 business days of receipt ofCOR comments on Deliverable One for Subtask 9.6.
Subtask 9.7: Prepare Completion Report
The contractor shall prepare a Completion Report (CR) that documents theprogramming effort. Specifically, the report shall summarize the methodology, software,and user changes, and shall include calculation results that demonstrate the changedcoding.
Deliverable for Subtask 9.7: Completion Report
19
The contractor shall deliver a completion report to the coR within 40 business days ofthe completion of Subtask 9.6.
C.6.2 Table of Deliverables
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
1.1 - Bug Report By the 20th Report MS Wordday of the containsfollowing required Transmittedmonth content and via e-mail
incorporates allcoRcommentsfrom the priormonth
1.2 - PAROS Code Within 5 Distribution ArchivedDistribution to business days contains withcoR of the required SecureZip
completion of a contentchecked-in Transmitted'PARCS code via e-mail,version NRC
website, orothermechanismspecified bythe coR
1.3 - TRACE Update Within 10 Update TarballFile "-business days contains
of coR required Transmittedrequest content and via NRC
*follows website, orguidance in e-mailAttachment C directly to
____ the con2.0 - Code Support Within 10 Documentation MS Word
Documentation business days followsof the coR guidance from Transmitted
____request COR via e-mail3.1 One Software Within 20 Document FrameMaker
.Requirements business days followsSpecification after Subtask guidance in Transmitted(SRS) 3.1 NUREG-1737 via e-mail
commence-ment
3.1 Two Software Within 30 Document FrameMakerDesign and business days followsImplementation after Subtask guidance in Transmitted
20
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
Document 3.1 NUREG-1 737 via e-mail(SDlD) commence-
ment3.1 Three Qualification Within 40 Document FrameMaker
Test Plan business days follows(QTP) after Subtask guidance in Transmitted
3.1 NUREG-1 737 via e-mailcommence-ment
3.2 - Resource Within 3 Estimate MS WordEstimate business days contains effort
of coR to meet Transmittedapproval of requirements via e-mailpre-code specified in thedocumentation Software
RequirementsSpecification
3.3 One Draft PAROS First Distribution ArchivedDistribution Distribution contains with
within 40 required SecureZipbusiness days contentof Subtask 3.3 TransmittedCommence- via e-mail,ment NRC
website, orSubsequent otherDraft mechanismDistribution specified bywithin 20 the CORbusiness daysof receipt ofcommentsfrom COR
3.3 Two Final PARCS Within 20 All COR ArchivedDistribution business days comments are with
of the receipt reflected in the SecureZlPof COR distributioncomments on Transmittedthe last draft via e-mail,distribution NRC
website, orothermechanismspecified bythe COR
3.4 - Completion Within 30 Report FrameMakerReport business days contains the
21
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
of completion required Transmittedof each content via e-mailprog rammingeffort
3.5 - Trace Update Within 10 Update TarballFile business days contains
of COR required Transmittedrequest. content and via NRC
follows website, orguidance in e-mailAttachments A directly toand C the COR
4.3 - GenPMAXS Within 5 Distribution ArchivedDistribution to business days contains withCOR of the required SecureZIP
completion of contentthe SCALE/ TransmittedGenPMAXS viaregression test mechanism
specified byCOR
4.4 - GenPMAXS Within 10 Documentation MS WordCode Support business days followsDocumentation of the COR guidance Transmitted
request provided by via e-mailCOR
5.0 One Draft PARCS/ Delivered to Materials MS OfficeGenPMAXS the COR 30 containTraining business days required TransmittedMaterials prior to training information via e-mail
5.0 Two Final PARCS/ Within 5 All COR MS OfficeGenPMAXS business days comments areTraining of receipt of reflected in the TranSmittedMaterials COR training via e-mail
comments on materialsdraft
6.1 One Draft TRIPEN/ Within 50 Documentation MS WordAGREE Models business days followsand of receipt of guidance from TransmittedCalculational the Run 2 and COR via e-mailNotebooks Run 3 digitized
test data from____ ____ ___ _ ____ ____ the COR _ _ _ _ _ _ _ _ _
22
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
6.1 Two Draft Briefing Within 70 Documentation MS WordMaterials to business days foilowsSupport the of receipt of guidance from TransmittedFourth Program the Run 2 and COR via e-mailReview Group/ Run 3 digitizedManagement test data fromBoard EOCD CORLOFC Meeting
6.1 Three Final Briefing Within 90 Documentation MS WordMaterials, business days follows.Models and of receipt of guidance from Transmitted
Calculational Run 2 and Run COR via e-mailNotebooks to 3 digitized testSupport the . data from CORFourth ProgramReview Group/ManagementBoard OECDLOFO Meeting
6.2 - TRIPEN/ Within 5 Distribution ArchivedAGREE Code business days contains with SecureDistribution to of COR required ZIPCOR request information
Transmittedvia amechanismspecified bythe COR
7.0 One Draft Provided to the Documentation MS OfficePARCS/Watts COR 1 containsBarNERA business day required TransmittedModels and prior to each information via e-mailMonthly Status monthlyDocumentation conference call
7.0 Two Final Within 50 All COR FrameMakerPARCS/Watts business days comments areBarNERA of receipt of reflected in TransmittedModels and COR models and via e-mailDocumentation comments on documentation
draft materialsafter the finalmonthlyconference call
8.1 One Software Within 20 Document FrameMakerRequirements business days follows
23
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
Specification after Subtask guidance in Transmitted(SRS) 8.1 NUREG-1 737 via e-mail
commence-ment
8.1 Two Software Within 30 Document FrameMakerDesign and business days followsImplementation after Subtask guidance in TransmittedDocument 8.1 NUREG-1 737 via e-mail(SDlD) commence-
ment8.1 Three Qualification Within 40 Document FrameMaker
Test Plan business days follows(QTP) after Subtask guidance in Transmitted
8.1 NUREG-1 737 via e-mailcommence-ment
8.2 One Draft PAROS Within 55 Distribution ArchivedDistribution business days contains with
of start of required SecureZipSubtask 8.2 content
Transmittedvia e-mail,NRCwebsite, orothermechanismspecified bythe coR
8.2 Two Final PARCS Within 10 All coR ArchivedDistribution business days comments are with
of receipt of reflected in SecureZipfinal COR distributioncomments on Transmittedlast draft via e-mail,PARCS NRCdistribution website, or
othermechanismspecified bythe coR
8.3 - Completion Within 30 Report FrameMakerReport business days contains
of the required .Transmit viacompletion of content e-mailtheexponentiallyvarying control
24
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
rod history.model
9.1 One Software Within 20 Document- FrameMakerRequirements business days followsSpecification after Subtask guidance in Transmitted(SRS) 9.1 NUREG-1 737 via e-mail
commence-:ment
9.1 Two Software Within 30 Document FrameMakerDesign and business days followsImplementation after Subtask guidance in TransmittedDocument 9.1 NUREG-1737 via e-mail(SDID) commence-
ment9.1 Three Qualification Within 40 Document FrameMaker
Test Plan business days follows(QTP) after Subtask guidance in Transmitted
9.1 NUREG-1737 via e-mailcommence-ment
9.2 - Draft Within 40 Distribution ArchivedGen/PMAXS business days contains withDistribution after Subtask required SecureZIP
9.2 contentcommence- Transmittedment via
mechanismspecified byCOR
9.3 - First Draft Within 40 Distribution ArchivedPARCS business days contains withDistribution with after required SecureZipBinning Input commence- content
ment of TransmittedSubtask 9.3 ,via e-mail,
NRCwebsite, orothermechanismspecified by
___________the COR9.4 - Second Draft Within 80 Distribution Archived
PARCS business days contains withDistribution with after required SecureZipTransition Commence- contentMatrix ment of TransmittedConstruction Subtask 9.4 via e-mail,
25
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
NRCwebsite, orothermechanismspecified bythe COR
9.5 - Third Draft Within 80 Distribution ArchivedMicro-depletion business days contains withPARCS after required SecureZipDistribution with commence- contentTransmutation ment of TransmittedMatrix Solution Subtask 9.5 via e-mail,
NRC'website, orothermechanismspecified bythe COR
9.6 One Fourth Draft 'Within 20 Distribution ArchivedMicro-depletion business days contains withPARCS after required SecureZipDistribution with commence- contentImplementation ment of Transmittedof Restart Subtask 9.6 via e-mail,Capability NRC
website, orothermechanismspecified bythe COR
9.6 Two Final PARCS Within 50 Distribution ArchivedDistribution business days contains with
of receipt of required SecureZipCOR contentcomments on TransmittedDeliverable via e-mail,One for NRCSubtask 9.6 website, or
othermechanismspecified bythe COR
9.7 - Completion Within 40 Report FrameMakerReport business days contains.
of the required Transmittedcompletion of content via e-mail
_____ _________Subtask 9.6
26
Task Deliverable Deliverable Deliverable Acceptance Deliverable##Due Date Criteria Format
-- Monthly Letter By the 20th Report MS OfficeStatus Report day of the contains(Per SOW following required
___________Section 0. 12) month content______
C.7 Estimated Level-of-Effort (LOE)
This estimate is advisory only and not to be considered as the sole basis fordevelopment of a staffing plan.
The total estimated level of effort for this project over the five-year period of performanceis 12,717 staff hours. The estimated distribution of the effort for this task over the fivebase years is described in the following table.
LEVEL OF EFFORT TABLE
LABOR CATEGORY LEVEL OF EFFORTSum mary (All Five Years)Project Manager 1,274Senior Engineer 5,576Research Associate PARCS/GenPMAXS 4,136Research Associate TRIPEN/AGREE 1,731Total Level of Effort, 12,717
LABOR CATEGORY LEVEL OF EFFORTBase Year 1 ____________
Project Manager 265Senior Engineer 1018Research Associate PARCS/GenPMAXS 740Research Associate TRI PEN/AG REE 625Total Level of Effort 2648
LABOR CATEGORY LEVEL OF EFFORTBase Year 2Project Manager 291Senior Engineer 1192Research Associate PARCS/GenPMAXS 810Research Associate TRIPEN/AGREE 616Total Level of Effort 2909
LABOR CATEGORY LEVEL OF 'EFFORTBase Year 3 ____________
Project Manager 222Senior Engineer 844Research Associate PARCS/GenPMAXS 958Research Associate TRI PEN/AGREE 190
27
STotal Level of Effort 2214
LABOR CATEGORY LEVEL OF EFFORTBase Year 4Project Manager 248Senior Engineer 1261Research Associate PARCS/GenPMAXS 814Research Associate TRI PEN/AGREE 150Total Level of Effort 2473
LABOR CATEGORY LEVEL OF EFFORTBase Year 5Project Manager 248Senior Engineer 1261Research Associate PARCS/GenPMAXS 814Research Associate TRIPEN/AGREE 150Total Level of Effort 2473
Please note that the Level of Effort information presented in the tables above is. advisoryand is not to be considered as the definitive/sole basis for the development of theOfferor's staffing plan/proposal. Offerors are permitted to make revisions to theproposed hours, and labor categories, based upon their own professional judgment andproposed technical approach to the requirement described in the SOW.
Labor Category Minimum EducationallProfessional Experience RequirementProject Manager: Education: See Note 1, below.
Clearance: See Note 2, below.Experience: See Note 3, below.
Senior Manager Education: See Note 1, below.Clearance: See Note 2, below.Experience: See Note 3, below.
Research Associate Education: See Note 1, below.PARCS/GenPMAXS Clearance: See Note 2, below.
Experience: See Note 3, below.Research Associate Education: See Note 1, below.TRIPEN/AGREE Clearance: See Note 2, below.
Experience: See Note 3, below.
Minimum Educational and Professional Experience Requirements:
*Note 1. Minimum Education qualifications: Each of the personnel shall have atminimum one post-graduate degree in nuclear engineering, with demonstratedexperience in developing algorithms that solve for the neutron flux and powerwithin a nuclear reactor core.
*Note 2. IT Level II Access clearance: All of the Contractor's proposed personnelhold an IT Level II Access clearance, or demonstrate that he or she is capable ofreceiving an IT Level II Access clearance after contract award and shall maintainthis level of security clearance for the life of the contract.
28
*Note 3. Minimum Professional qualifications: Collectively, the personnelproposed shall have expert knowledge of and experience with (minimum of 2years): core nuclear analysis, nuclear analysis methods development, numericalalgorithms for the solution of systems of equations, software engineering, andsoftware quality assurance. These skill sets shall be demonstrated through ahistory of peer-reviewed publications and technical reports in these areas, andadditionally, Graduate school experience would count towards this requirement.The proposed personnel shall also have an understanding of nuclear corethermal-hydraulic analysis and experience in developing algorithms and codingfor existing core nuclear thermal-hydraulic concepts. In addition, the individualsproposed as a group shall demonstrate these additional skillsets:
o Expert knowledge (minimum of 2 years) of the classes of codes to whichPARCS, GenPMAXS, TRIPEN, AGREE and/or equivalent (In thetechnical evaluation, expert knowledge of PARCS is preferred and will begiven more weight than expert knowledge of the other codes). Expertknowledge of nuclear analysis code structure, algorithms, and codecompilation/build systems.
o Knowledge of (minimum of 2 years) modern FORTRAN standards and aworking knowledge of MS-DOS, Linux, UNIX, and scripting languagessuch as Perl and Python is also required.
o Proficiency (minimum of 1 year) in the use of the following lattice physicspackages: HELlOS, CASMO, and TRITON. (In the technicalevaluation, proficiency in the other lattice physics packages of WIMS,CONDOR, POLARIS, and SERPENT will be given additional weight.)
C.8 Estimated Materials Required
The following information technology is required during the life of the contract:
Commercial FORTRAN compilers including:
Intel® Fortran Studio XE for Windows (3 users)LF 64 Linux PRO v8.1 (3 users)NAG Fortran Compiler for Linux (1 user)PGI Fortran/C/C++ Workstation for Linux (1 user)
3 Engineering Workstations [Minimum Requirements: Multicore Processor, 2.40GHz,12GB RAM, 1 TB hard drive]
SecureZip and Adobe FrameMaker Software Packages
C.9 Reporting Requirements
The contractor shall provide a Monthly Letter Status Report (MLSR) by the 2 0 th day ofthe month which encompasses the prior month's effort. The MLSR shall be submittedelectronically to the following:
Contracting OfficerCOR.
29
Alternate CORNRC Administrative Management Division at: ContractsPOT. Resource~nrc.QlOV
The contractor shall follow the MLSR instructions and template provided in Attachment0. The staff hours shall be recorded at the task level. The deliverables schedule shall betracked by subtask.
C.10 Publications
See Section I.
C.1 I Government-Furnished Property
The following GFP will be provided to the contractor following contract award:
• yu-t• Date Method of
GFP temQuanity provided to Shipmentcontractor
PAROS Bug Report 1Upon ElectronicContractAward
PARCS User List IInitial List ElectronicuponContractAward
UpdatedList(s)throughoutcontractperiod ofperformanceas necessary
Prior PARCS Distributions 1Upon CD(source code, build scripts, manuals, Contracttest problems, etc.) AwardPrior GenPMAXS Distributions 1Upon CD(source code, build scripts, manuals, Contracttest problems, known bugs Awarddocument, regression testingsummary, summary slides, etc.)Prior PARCS and GenPMAXS IUpon ElectronicTraining Materials Contract
AwardSCALE/GenPMAXS Regression I Upon ElectronicTesting Framework Contract
_____ _____ ____ _____ _ ___ ____ Award _ _ _ _
TRIPEN/AGREE Code Distribution 1 Upon Electronic(source code, build scripts, manuals, ______Contract ______
30
Date Method ofGFP Item Quantity provided to Shipment
contractor
test problems, etc.) AwardJAEA LOEC Reports 1-1, 1-3, and Upon Electronic1-4 and JAEA Responses to US 1 each ContractNRC comments on Reports 1-1, 1-2, Awardand 1-4LOFC Run 1 Experimental Data I Upon Electronic
ContractAward
JAEA LOFC Report 1-2 1 Upon PaperContract
______Award
LOFC Run 2 and Run 3 1 each As soon as ElectronicExperimental Data available
from JAEA,AfterContractAward;
LOEC Runs 1-3 TRIPEN/AGREE 1 each Upon ElectronicModels Contract
AwardTMI Cycles 1-2 PARCS Models 1 each Upon Electronic
ContractAward
NUREG-1737 1 Upon Obtain viaContract publicAward website
(nrc.gov)
C.12 Access to Government Property and Facilities
Upon arrival at NRC Headquarters, contractor personnel are required to check-in at thesecurity desk to obtain a visitor's badge. Contractors are required to be escorted by anNRC employee at all times while in an NRC facility.
C.13, Place of Performance
The work to be performed under this contract shall be primarily performed at thecontractor'.s site.
Location of Training Sessions: The NRC is planning on a maximum of two separate 8hour user training sessions to be held at NRC Headquarters in Rockville, Maryland. Thekick-off meeting and annual program review meetings may occur at NRC Headquartersin Rockville, Maryland, as required by the COR.
O.14 Security Requirements
31
The NRC requires that all of the Contractor's proposed personnel hold an IT Level IIAccess clearance, or demonstrate in the proposal that this individual is capable ofreceivinq and IT Level II Access clearance after contract~award and shall maintain thislevel of security for the life of the contract.
C.15 Post-award Orientation (kick-off) and Periodic Proqress Meetinqs
The contractor shall attend a one-time kick-off meeting (either in person or viaconference call) to discuss the tasks, deliverables and performance requirements of thecontract. The kick-off meeting shall be held within five (5) working days of contractaward.
Annual program review meetings will be scheduled as needed. Program reviewmeetings shall include two members of the contractor's team, and will be for one day'sduration each.
C.16 Contracting Officer's Representative (COR)
See 2052.215-71 CONTRACTING OFFICER'S REPRESENTATIVE AUTHORITY.
(OCT 1999).
C.17 Key Personnel
See Section H, 2052.21 5-70 KEY PERSONNEL. (JAN 1993)
C.18 General - Contractor Personnel
The contractor shall not employ persons for work on this contract if such employee isconsidered by the contracting officer to be a potential threat to the health, safety,security, general well-being or operational mission of the installation and its population.
Contractor personnel shall present a neat appearance and be easily recognized ascontractor employees. Contractor personnel attending meetings, answering phones,and working in other situations where their status is not obvious are required to identifythemselves as such to avoid creating the impression that they are Government officials.
The contractor shall not employ any person who is an employee of the U.S. Governmentif employing that person would create a conflict of interest. Additionally, the contractorshall not employ any person who is an employee of the NRC, unless such person seeksand receives approval in accordance with NRC regulations.
C.19 Contractor Travel
The contractor shall be authorized travel expenses consistent with the provisions of theFederal Travel Regulation (FTR) and the limitation of funds specified in this contract. Alltravel requires prior written approval from the COR.
The NRC estimates that the following travel will be required, with each trip beingassumed to last for three days including travel time:
32
*One, 2-person, 1-day contract kick-off meeting, to be held at the beginning of thecontract at NRC Headquarters in Rockville, Maryland.
*One, 2-person, 1-day program review meeting, each year of the contract, to beheld at NRC Headquarters in Rockville, Maryland.
*Two, 2-person, 1-day training sessions for PAROS Users to be held at NRCHeadquarters in Rockville, Maryland. Two total training sessions throughout thelife of the contract-expected to occur during the first and third year of thecontract.
*One, 1-person, 1-day participation in the annual fall CAMP meetings, to be heldwithin commuting distance of NRC Headquarters in Rockville, Maryland.
*At the discretion of the COR, meetings may be conducted via telephone or videoconference.
Travel will be reimbursed in accordance with FAR 31 .205-46, 'Travel costs" and theGeneral Services Administration's Federal Travel Regulations at:http ://www.gsa.gov/portallcontentl1 04 790.
Note: Contractor's expenses for travel shall not be fee-bearing.
See Section H - 2052.215-77 TRAVEL APPROVALS AND REIMBURSEMENT. (OCT1999)
33
Attachment B
Special Requirements
All code development activities must follow principles described in NUREG-1 737 andadhere to the Programming Guidelines and Design Philosophies as outlined inAttachment D.
All code transmittal packages shall be generated using the buildTransmittal.pl perl scriptand shall include the following:
* SQA documentation*Patch files to the TRACE source in duff format• Modified source files* HTML summary file explaining the nature of the changes and testing* Modified test input files (if any)* Newly added test input decks (if any)* HTML results of the testSummary.pl script (generated for the regression test set)* AVScript input files (if applicable)* Scripts or programming tools that might have been used/generated in the course of
completing the update
If changes to the code manuals are required in conjunction with a particular update, thecontractor may be asked by NRC to make those modifications in addition to the SQAdocumentation outlined in the SOW. Regarding this issue, it is NRC's expectation thatthe contractor shall become familiar with the content of each chapter in each manual sothat manual changes are applied comprehensively and at a level of detail similar to thecontent that surrounds the modified or added text. The contractor shall ensure thatinconsistencies between various sections of content (either in thought or innomenclature) are not introduced.
Changes to manuals shall generally be made to the on-line, official electronic filesdirectly. In cases where this practice is either not prudent or not possible, the contractorshall use Framemaker's built-in change bar feature to call out modifications to make iteasier for NRC staff to integrate those changes into the official electronic files at theappropriate time.
The NRC will not consider it acceptable to submit graduate theses as the final productof research. All final assessment reports shall use NRC-supplied Framemakertemplates and shall be in accordance with the specifications provided in the Statementof Work.
The development of all assessment input problems shall be accompanied by the
Attachment B
development of a calculation notebook that justifies the use of every value provided inthe model. For every value, the calculation notebook shall answer the followingquestions:
* What is it?* Whywas it chosen?* What was assumed?* How was it calculated? and/or. Where did it come from?
2
Attachment C
TRACE CODE UPDATE PROCESS
1. Download current TRACE version and create a separate TRACE_mod version fordevelopment. Make applicable code changes.
2. Download current TRACE Automated Testing Framework (ATF) tarball from the ViewCVSsection of the Developer's Website to a Test directory. Run Test/config.pl to configure your ATFenvironment per the ATF-README.htm installation instructions.
3. Copy the base code version and the code version of interest to .the executable directorycreated during installation of the ATF (e.g., /Test/Exe).
4. Execute ./runTests.pl [--help] [--force] [--numProcs] [--all] [--noTime] --vers=VERSIONLISTOFSUITES from the /Test/Regression directory. The purpose of the runTests script is todrive execution of the TRACE verification test set.
5. Execute ./testSummary.pl [--help] [--sI--suite=NAME] [--ri--reverse] [--onlyStats] [--vi--versi--version=.VERSIONS] [--noSigDiff] [--noDiffs] from the /Test/Regression directory. The purposeof the testSummary script is to sweep through all TRACE output files for a given test suite (orsuites) for a given pair of code versions) and report: 1) whether the run was successful, 2) asummary of all the run time statistics for all runs, and 3) the differences in output with respect tothe previous code version. It creates two directories under the Regression directory: diffs andrunStats..
6. Execute ./traceDiff.pl [--help] [--ignoreWhiteSpace] DIR1 DIR2 from the /trace/executablesdirectory. The purpose of the traceDiff script is to compare two versions of the trace builddirectory structure and generate the necessary patch files to be able to update yet a thirdversion. DIR1 shall be the unmodified base TRACE distribution and DIR2 shall be the modifiedTRACE distribution directory.
7. Execute ./buildTransmittal.pl [--help] [--force] [--incTests] [--verbose] --nameTRANSMITTAL_NAME --duff DIFF_DIR --mods MOD_SRC from the /trace/executablesdirectory. The purpose of the buildTransmittal script is to create a TRACE update packagecalled TRANSMITTAL_NAME in the current directory. It will copy the duff files from DIFF_DIRinto Diffs_AsSubmitted and the corresponding modified source files from MOD_SRC into Mod-Src_AsSubmitted. It will also create a template Summary.html file and place it in the Docssubdirectory.
8. Copy the runStats directory from the /TestlRegression directory into the/trace/executables/TRANSMITTALNAME directory to be part of the TRACE update package.
1
Attachment C
9. If as part of the verification testing performed, new test problems were created, then create anew subdir called Newlnput and copy inputs to that subdir. The file names shall reflect theirpurpose, and comments shall be added to the top in the input model that the comments indicatewhat the test problem is supposed to test, what the expected result should be or should becompared to, and Whether the model is a permutation of some other test problem already in the
ATE.
10. If, as part of verification testing, existing test problems were modified in the ATF in order forthem to run correctly, create a new directory called Modlnput and copy into it both the modifiedfiles themselves, as well as the patch/diff files of that test problems that show only what inputparameters were changed.
11. Open the Summary.html file in the/ITRANSMITTAL_NAME/Docs directory with "Mozilla WebBrowser" and use FilelEdit Page to edit the Code Change Summary file.
12. Include any documentation changes and test input files in the TRACE update package
directory. When modifying any of the Framemaker documents, be sure to first turn on thechange bar feature. Add any modified Framemaker documents to the Docs directory. Also
include any other pertinent documents/reports/plots that are deemed important for someoneelse not intimately knowledgeable with the changes in order for them to be able to figure out thechanges that were made.
13. Execute ./tar -cvzf TRANSMITTAL_NAME.tgz TRANSMITTAL_NAME from the(trace/executables directory. This will create the TRACE update package tarball.
14. Upload the TRACE update package tarball to the Transmittals section of the Developer'sWebsite. Select File Type "code-update". Click "Upload File!" Done.
2
Attachment 0
TRACE Standard F90Programming Practices andGeneral Design Philosophies
Developers shall adhere to these practices for all new coding. Please send feedback toChristopher.Murray~nrc..Qov. Improper style in old coding will be corrected asresources permit:'
* Write GOOD req uirements - see
http://wvww.incose.org/workgrps/rwg/writing.html for some online guidelines
* All code SQA reports and code documentation shall be prepared and submitted toNRC in Framemaker format. Equations shall be generated using Framemaker's built-inequation tools. Line and vector-based diagrams shall be generated usingFramemaker's built-in drawing tools. In cases where this is not possible, the originalpicture files shall accompany the document and be in a format editable by commondrawing tools (eps, svg, mif, pdf, cdr). Use encapsulated postscript (eps) only as a verylast resort - we expect developers to employ modern drawing tools that will not lead tothis limitation. For engineering plots, AptPlot is the preferred program for generatingsuch plots. Save them to mif format for importing into a Framemaker document. Plotsshall NOT be imported as bitmap images (use vector formats instead. For raster/bitmappictures, the image may be inserted directly into the document, but the transmittal shallinclude the image in its own file in a standard format (gif, png, or jpg).
* All new variables will be explicitly typed, and all new routines shall include IMPLICITNONE statements.
* Implement a standard KIND representation for Integers and Reals
+ Always insert the line "USE lntrType" after the MODULE statement, or for anysubprograms that are not module procedures, after the SUBROUTINE or FUNCTIONstatement. If IntrType is declared at the module level, there is no need to include itwithin the CONTAINed subroutines.
+ Begin all definitions of real variables with "REAL(sdk)"
+ Begin all definitions of integer variables with "INTEGER(sik)"
!
Attachment D
* All use of real and integer constants should be implemented with the _sdk and _sikkind type parameters
+ For example, use 2_sik instead of just 2, or 1.Oe+10_sdk instead of 1.0d+10, etc.
* Do not use continuation lines inside of variable declaration statements
* When declaring a variable of TYPE POINTER, ALWAYS initialize it withthe => NULL() syntax.
* Get in the habit of using default initialization whenever variables are declared, butkeep in mind that use of this syntax implies the SAVE attribute for any variable for whichthis is done.
Developers shall use the ONLY syntax in their USE statements. This preventsunintended variables from coming into scope and preventing the compiler fromdetecting instances where a local variable is undeclared or an unintended globalvariable is used mistakenly (as can happen with variables like cco when cutting andpasting code).
, Developers shall use object-oriented designs. What does this imply? It means thatcoding shall be data-centric. In other words, design the data structure first. Make itflexible enough to handle all possible situations for which you could ever envisionneeding it. Once an effective data structure is fleshed out, on paper, begin to thinkabout methods that operate on that data structure. As a minimum, there ought to beconstructor/initialization and destructor methods for the data Structure as a whole andany substructure pointer or allocatable arrays that might exist. Make the data structurePRIVATE to the module of interest. Access to the data structure shall only be throughsubroutines or functions. The contractor shall factor these ideas into proposals andpredictions about time and cost. The penalty with these sorts of designs is in run-timespeed, so there may be situations where such designs do not make sense but adeveloper's priorities shall be object-oriented first, run-time second. Speed can alwaysbe recaptured in the next generation of processors or by optimizing other aspects of thecode.
* All dummy arguments and important local variables shall be declared within their ownTYPE declaration statements.
* The INTENT of all dummy arguments shall be declared in all new coding
* Do not use bare END statements
2
Attachment D* All Fortran statements, attributes, intrinsic subprograms, and logical operators in new
coding shall be in all upper case.
REAL(sdk), POINTER, DIMENSION(:,:):: a, aa
IF ( i.GT.j ) THEN
* Leading and trailing underscores shall not be used in any names (due to the potentialfor name mangling issues during linking), but underscores in the middle of names areallowed.
* Variable, file, and procedure names shall be long enough to be self-documenting,within reason, with a suggested limit of 15-20 characters
* All new variable names shall have the first letter of each sub-element capitalizedexcept the first, as in pipeData.
* All derived type names shall end in "T", as in pipeDataT.
* Module and subprogram names shall begin with a capitalized letter, but don't changeold subprogram names.
* All new coding shall be structured with an indentation level of three spaces.
DO i= 1,n
DOj = 1,n
IF (i~gt.j) THEN
a(i,j) = - aa(j,i)
ELSE
a(i,j) = aa(i,j)
ENDIF
ENDDO
ENDDO
* Use IF-THEN-ENDIF instead of IF (condition) statement
3
Attachment 0
* "GOTO" statements shall be used sparingly, if at all. Instead, programmers shall useIF-THEN-ELSE, SELECT CASE, CYCLE, EXIT, and internal subprograms asappropriate
* Use standard F90 free format code style with the following exceptions:
+ A limit of 110 columns per line
+ Source code shall start in column 7. Columns 1-6 are to be reserved for statementlabels. This does not apply to comments and MODULE statements.
* Comments lines shall be indicated with a 'T" in column 1.
* Comments that serve to delineate, summarize, and/or clarify larger multi-stepalgorithms shall be indented one or two spaces.
* Comments that serve to clarify the intent of and/or summarize small blocks of codeshall be given the same indentation level as that code.
* Comments shall be offset by at least one blank line from the previous F90 statement.
* Comment shall not be placed at the end of a continued line (illegal Fortran).
Try not to ever use multi-line statements. It makes writing scripts to parse FORTRANmore difficult and invalidates line coverage profiling studies.
* End-of-line comments shall not be used except in context of data type declaration
statements or where a brief comment on the same line as the statement clearlyaccentuates and improves the readability and intent of the IF statement or block thatfollows, ala
INTEGER(sik):: height = 0.0 sdk !height of the cell
or
IF (fillTab(cco)%flowin .GE. 0.0d0) THEN IDetermine donor cell mixture.
* Comment blocks shall generally not be longer than a dozen lines (additionalinformation can go in the programmer's manual, and/or the SDlD subroutine report).
* Authorship information shall be included for each new subroutine that a developer
creates or rewrites from scratch. When well defined blocks of changes (on the order of
4
Attachment D
100 lines or more) are made to an existing subroutine, a note shall be placed directlybeneath the existing authorship info (or below the subroutine purpose if it does not)denoting the name, organization, date and quick description of the modifications.Authorship info shall not be provided when the changes are spread out (i.e. not in welldefined blocks) - even if they significantly modify some behavior of the algorithmcontained therein - although the subroutine description shall be checked for accuracyand modified when appropriate.
* The following standard template shall be used for each new subroutine that is-,
developed (a plug-in to Visual Fortran has been created which can create thisautomatically):
SUBROUTINE SampleSub0
USE lntrTypeIMPLICIT NONE
SThe purpose of this routine is to <<Insert Description here»>
I Programmed by Name, Organization, Date (Month/Year)
!Subroutine Argument Descriptions:
I Variable Declarations:
RETURN
END SUBROUTINE SampleSub
When making a change, do not comment out the old coding but instead delete it.
* Do not surround your coding with your initials - it just uglifies the code.
* Never use COMMON. Use a MODULE and corresponding USE instead.
* Never use EQUIVALENCE. Use POINTERs if you must, but better practice is toredesign so pointers are not necessary.
* All code shall be standard F90 - use of non-standard compiler extensions or
preprocessor definitions shall not be allowed.
* If available in the compiler, all code shall be developed with strict F90 standardschecking and array bounds checking turned on. Also, compiler flags shall be engaged
Attachment 0
which check for any unused variables and uninitialized variables. If any unusedvariables are located in a routine that a developer touches, then he or she shall removethem.
* If a new subroutine is added to the code outside the scope of a MODULE statement,then an explicit interface to that routine shall be created. This allows the compiler tohandle checking of the argument lists at compile time.
* Developers shall remove any unused subroutines which are created as a result oftheir efforts.
* When incorporating legacy code from other computer codes into TRACE, every effortshall be made to clean that code up and to ensure that it conforms to the stylistic rulesand design philosophies outlined in this document.
When preParing an SRD for a particular develoPment project, the requirements shall
take into account the planned update's effect on or interaction with such areas as:
+ restart processing
+ CSS controllers
+ control system
+ exterior component and other parallel programming interfaces
+ timestep backup flow logic
+ SNAP and/or VEDA+ English units
* Any modification or enhancement of intercomponent transfer of information shallnever involve direct modification of bd array elements. All transfers shall be arrangedduring the initialization phase of the calculation (module SysService) through the systemservice transfer tables.
6