E01.02 W913E520C0003 Signed.pdf

CODE

(Hour)

PAGE(S)

until local time

X

A X B X C

D

EX

X G F

H

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

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

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

1 35

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

BEVERLY RYMER / EXECUTIVE DIRECTOR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE

(713) 743-5773

15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

UNIVERSITY OF HOUSTON SYSTEM

BEVERLY RYMER

4800 W CALHOUN ST STE 316

HOUSTON TX 77004

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

W913E520C0003

W913E5 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 3

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT

PACKAGING AND MARKING

4 - 21 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 24 - 27

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

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

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

Net 30 Days

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

9B955 FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

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

PART I - THE SCHEDULE

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

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

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

$1,896,433.00 See Schedule

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

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

PR W1J5 USACE FIN CTR

5722 INTEGRITY DRIVE

BUILDING 787

MILLINGTON TN 38054-5005

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

28 - 35

PART II - CONTRACT CLAUSES

ERDC CONTRACTING OFFICE

HANOVER OFFICE

72 LYME ROAD

HANOVER NH 03755-1290 (217) 373-7297

(217) 373-6773FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.

W81EWF00165112

5. DATE ISSUED4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

3. SOLICITATION NO.

See Item 7

04-09-2020

601-634-4687 Melodie.Y.Fisher@usace.army.mil

Melodie Fisher 9-Apr-2020

9 April 2020

W913E520C0003

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Job $1,896,433.00 $1,896,433.00 Research and Development Services

FFP

BAA Proposal 18-0107 titled, "Registration and Confidence Assessment of Multi- Temporal Point Clouds for 3D Change Detection" FOB: Destination

NET AMT $1,896,433.00

000101 $0.00 Funding for CLIN 0001

FFP

Task 1

PURCHASE REQUEST NUMBER: W81EWF00165112

NET AMT $0.00

ACRN AA

CIN: W81EWF001651120001

$135,749.00

000102 $0.00 Funding for CLIN 0001

FFP

Task 2

CIN: W81EWF001651120002

$248,047.00

000103 $0.00 Funding for CLIN 0001

FFP

Task 3

CIN: W81EWF001651120003

$143,659.00

0002 1 Job NSP Contractor Manpower Reporting

FFP

The Contractor shall perform CMR in accordance with Section C, PWS, Paragraph C.11.r.

NET AMT

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

Title: “Registration and Confidence Assessment of Multi-Temporal Point Clouds for 3D Change Detection”

C.1. INTRODUCTION: This contract is the result of a successful proposal received under the ERDC Broad Agency Announcement W912HZ18BAA01 addressing the Water Resources Geospatial Applications technical area (CRREL-9). The proposal BAA 18-0107 submitted by the University of Houston (UH), entitled “Registration and Confidence Assessment of Multi- Temporal Point Clouds for 3D Change Detection ”, proposes to alleviate two fundamental deficiencies in 3D point cloud models using a four-pronged approach: (1) examination of both rigorous, non-rigorous and bootstrapping methods for quantifying uncertainty in 3D point cloud models derived from both lidar and SfM-MVS, (2) analysis of automated methods to register different point cloud models to common foundational reference datasets with error propagation and estimation of registration accuracy, (3) use of estimated errors in commonly registered datasets to infer detection limits and associated uncertainties for derived spatial change detection products using rigorous error propagation through a variety of change detection algorithms, and

(4) examining methods for making change detection more agile on large point cloud datasets.

The results and methodology will be validated by the collection and analysis of focused data acquisitions using both lidar and SfM-MVS. The tools and methodology developed will be transferred into open source algorithms and integrated into the open source Point Data Abstraction Library to support potential integration into the Geospatial Repository and Data Management System as well as implementation into other software packages via uptake of open source software.

C.2 Period of Performance. 36 months from date of contract award.

C.3. CONTRACTOR’S TECHNICAL PROPOSAL: The Contractor’s technical proposal entitled “Registration and Confidence Assessment of Multi-Temporal Point Clouds for 3D Change Detection” is incorporated herein by reference and made a part thereof. In the event of any discrepancies between the Contractor’s proposal and this Performance Work Statement, this Performance Work Statement shall govern.

C.4. NON-PERSONAL SERVICES: The Government and the Contractor hereby understand and agree that the services to be delivered under this contract by the Contractor to the Government are non-personal services, and the parties recognize and agree that no employer-employee or master-servant relationships exist or will exist under this contract between the Government and the Contractor's employees.

C.5. GOVERNMENT-FURNISHED EQUIPMENT AND INFORMATION:

C.5.a. Laptops: The Government does not anticipate that government computers or IT equipment are needed for this work.

C.5.b. CAC Cards: The Government does not anticipate CAC cards are needed for this work.

C.5.c. Access to ERDC IT Systems: The Government does not anticipate access to ERDC IT will be required for this work.

C.5.d. Other GFE: The Government does not anticipate any GFE.

C.6. CONTRACTING OFFICER'S REPRESENTATIVE (COR): The identification of duties and limitations of the COR are specified in the COR appointment letter, which will be provided to the contractor at or shortly after the time of award. No Government personnel, other than the Contracting Officer, shall have the authority to do other than clarify technical points or supply relevant information to the Contractor regarding this contract. Specifically, no requirement in these specifications may be altered through verbal clarification. Only a warranted Contracting Officer, acting within their delegated limits, has the authority to issue modifications or otherwise change the terms and conditions of this contract. If an individual other than the Contracting Officer attempts to make changes to the terms and conditions of this contract you shall not proceed with the change and shall immediately notify the Contracting Officer.

C.6.a. Contracting Officer’s Representative (COR): The COR for this contract is Bryan Baker: Bryan.E.Baker@usace.army.mil, (603) 738-1633.

C.6.b. Invoice Acceptor: When submitting invoices via WAWF, the contractor shall enter the COR’s email address in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system. The contractor shall also enter Jackie Walker who serves as a second acceptor: Jacqueline.A.Walker@usace.army.mil

C.7. TECHNICAL POINTS OF CONTACT (TPOCs): TPOCs coordinate with the contractor to facilitate execution of the work, ensure access to necessary government data, hardware, or supplies, review monthly progress reports, review deliverables, and assist the vendor to engage with other government agencies to transition the products developed (e.g., end-user communities, Program of Record Offices, etc.). TPOCs provide feedback to the COR regarding their perception of contract progress and risks. TPOCs must include the COR on written correspondences, telecons, and other communications so that the COR can properly monitor and document contract progress. Likewise, the vendor must include the COR on written correspondences, telecons, and other communications with the TPOCs. TPOC’s are selected based on interest in the contract topic and technical or governmental backgrounds making them subject matter experts (SMEs) in areas relevant to the contract. Other Technical POCs from ERDC may be engaged by the COR as the work evolves and will be formally introduced to the vendor as a TPOC. The vendor should consult with the COR regarding engagements by other government employees seeking to interact technically on the contract being executed. TPOCs for this contract include:

Adam LeWinter: Adam.L.Lewinter@usace.army.mil, (603) 646-4877 Bryan Baker: Bryan.E.Baker@usace.army.mil, (603) 738-1633

C.8 SCHEDULE AND TASKS: The vendor’s proposal discusses ten (10) tasks. These task assignments are required to ensure clarity through the lifecycle of the contract for tracking of contract deliverables and progress between the Government and Contractor. Tasks are assigned to the contractor’s activities per the proposal. In subsequent parts of the Government’s contract, these tasks are also aligned to deliverables and the PRS. The vendor is instructed to use the below listed task labels in their section headings when discussing work in each Monthly Progress Report.

Tasks Description Task 1 Error Propagation into GDAL Task 2 Error Propagation using Structure for Motion Task 3 3D Point Cloud Error Task 4 Accuracy Estimation Task 5 Automated Tie Points Task 6 Robust Error Estimation Task 7 Vertical Change Uncertainty Estimation Task 8 Image Correlation Algorithms Task 9 Adaptive 3D Change Detection

Task 10 Data Acquisition

C.9. MEETINGS AND REVIEWS:

C.9.a. [A001] Government’s Contract Kick-off Meeting. The purpose of this meeting is for the Government to review the contract and associated documentation with the vendor, TPOCs, and any other relevant personnel to ensure all parties understand the contract and the processes necessary to follow the proper execution of the contract IAW policies, procedures, and laws. In this meeting, the COR and Contractor will attend a joint contract kick-off meeting at the start of the contract, scheduled as early after award as possible (before substantial technical work starts). The Government may hold the meeting at CRREL and/or via WebEx Telecon. The COR will deliver a briefing of the contract, processes, and Government’s performance expectations; the COR will open the floor to questions to ensure clear understanding by both the Government and Contractor on these matters. The Contractor will present a brief overview of their project to include: team members with roles, technical approach, schedule – milestone – deliverable chart covering the full contract period of performance (POP), discussion of risks (schedule, cost, performance/product), and any other topics the Contractor wishes to discuss.

C.9.b. [A003] Technical Meeting with CRREL – Task 1. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon to discuss findings associated with links between observed turbulence attributes and sand fluxes. Execution and delivery schedule is established in Paragraph C.10.

C.9.c. [A004] Technical Meeting with CRREL – Task 2. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon to discuss findings associated with the conceptual sand flux model. Execution and delivery schedule is established in Paragraph C.10.

C.9.d. [A005] Technical Meeting with CRREL – Task 3. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss results from the sand flux validation assessment. Execution and delivery schedule is established in Paragraph C.10.

C.9.e. [A006] Technical Meeting with CRREL – Task 4. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss findings associated with links between observed turbulence attributes and LES model parameters. Execution and delivery schedule is established in Paragraph C.10.

C.9.f. [A007] Technical Meeting with CRREL – Task 5. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in Paragraph C.10.

C.9.g [A008] Technical Meeting with CRREL – Task 6. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in Paragraph C.10.

C.9.h [A009] Technical Meeting with CRREL – Task 7. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in Paragraph C.10.

C.9.i [A010] Technical Meeting with CRREL – Task 8. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in Paragraph C.10.

C.9.j [A011] Technical Meeting with CRREL – Task 9. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in Paragraph C.10.

C.9.k [A012] Technical Meeting with CRREL – Task 10. A technical meeting will take place with CRREL at UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in Paragraph C.10.

C.9.l. [A013] Final Project Meeting with Government (Contract Close Out). The purpose of this meeting is to close out the contract for this effort between the Government and the Contractor. The meeting may be held at CRREL, the ERDC Vicksburg campus, UH, or via WebEx/Telecon with government representatives, TPOCs, and other official stakeholders as appropriate. The vendor and the government may review final deliverables, review the products developed, and discuss any other aspects of the contract as appropriate.

The final close out meeting will be scheduled to occur after the draft-Final report is received.

Execution and delivery schedule is established in Paragraph C.10.

C.10. REPORTS AND DELIVERABLES: In addition to the reports and deliverables listed in the Contractor’s proposal, the Contractor shall submit the following to the COR. A detailed description of each deliverable and associated performance standard is provided in Paragraph C.11.

Deliverable Description Period A001 Government’s Contract Kick-off Meeting and Brief Task 1 A002 Monthly Progress Reports and Invoices Monthly A003 Technical Meeting with CRREL – Task 1; Updated PDAL software Task 1

A004 Technical Meeting with CRREL – LOE 2; algorithms for tie point accuracy; updated bundle adjustment of SIFT points code

Task 2

A005 Technical Meeting with CRREL – Task 3; updated module developed in Task 1

Task 3

A006 Technical Meeting with CRREL – Task 4; module for automated point cloud registration

Task 4

A007 Technical Meeting with CRREL – Task 5; Module for co-registration feature extraction

Task 5

A008 Final Software Deliverable – Task 6; Module for estimation of co-registration of uncertainty

Task 6

A009 Technical Meeting with CRREL Task 7; Command line tool/software

Task 7

A010 Technical Meeting with CRREL – Task 8; Command lines tools/software

Task 8

A011 Final Technical Report Task 9; command line tool extension software

Task 9

A012 Data Products – Task 10 – 3D point cloud files and metadata;

survey notes; trip reports

Task 10

A013 Final Project Meeting with Government (Contract Close Out) N/A A014 Accounting for Contractor Services (ECMRA) N/A A015 DD Form 882 Patents – Reporting of Subject Inventions N/A A016 Mandatory Training and Security Procedures Initiation

C.11. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP) AND PERFORMANCE

REQUIREMENTS SUMMARY (PRS): The Government will track and monitor progress using a Quality Assurance Surveillance Plan (QASP) developed by the Government (the vendor’s proposal offered a draft of a QASP with recommended input which was taken into consideration, but not adopted by the government in entirety). The vendor is responsible for developing its own tools and processes for internal monitoring of quality and progress consistent with standard project management. The Government’s QASP is the tool used by the

Government to determine if the Contractor's performance meets the performance standards contained in the contract. The QASP establishes procedures for how assessment/inspection process will be conducted. The COR may share the QASP with the vendor if the COR feels it is appropriate and helpful. However, the critical element of the QASP that needs to be understood by the vendor is the Performance Requirements Summary (PRS) which is outlined below in Paragraph C.11. The Performance Requirements Summary is the list of performance objectives and surveillance standards for each of the elaborated contract deliverables. This PRS explains the surveillance approach the COR will use to validate and inspect elements of the contract for COR file documentation. The QASP is a living document that may be revised by the Government, as needed, to ensure highest standards of contract oversight. The COR will utilize the performance standards outlined in the PRS, as well as any other critical contractual requirements the COR determines to be of high risk and requiring oversight.

C.11.a. Surveillance Standards. Threshold and Objective Standards are provided.

Threshold is the minimum acceptable standard that must be met, and is considered achievable within the available cost, schedule, and scope of the contract, assuming a low risk approach by the vendor. Objective is the desired goal or end state that may be met by the contractor, and is achievable within the available cost, schedule, and scope of the contract, assuming a higher risk approach by the vendor. Objective standards are optional / not required to meet contract requirements.

C.11.b. Performance Ratings. In evaluating the quality of contractor’s performance, the following performance ratings may be used by the COR. Excellent: Performance meets contractual requirements and exceeds some requirements to the Government’s benefit.

Satisfactory: Performance meets contractual requirements. Marginal: Performance meets some requirements, but some problems have been identified. Corrective action has been taken by the contractor and monitored by the COR for evidence of correction or progress toward correction. Unsatisfactory: Contractual performance contains problem(s), and the contractor has not yet identified corrective actions, or the contractor’s proposed actions appear marginally effective or were not fully implemented.

PERFORMANCE REQUIREMENTS SUMMARY (PRS)

C.11.c. [A001] Government’s Contract Kick-off Meeting. The purpose of this meeting is for the Government to review the contract and associated documentation with the vendor, TPOCs, and any other relevant personnel to ensure all parties understand the contract and the processes necessary to follow the proper execution of the contract IAW policies, procedures, and laws. In this meeting, the COR and Contractor will attend a joint contract kick-off meeting at the start of the contract, scheduled as early after award as possible (before substantial technical work starts). The Government may hold the meeting at CRREL and/or via WebEx Telecon. The COR will deliver a briefing of the contract, processes, and Government’s performance expectations; the COR will open the floor to questions to ensure clear understanding by both the Government and Contractor on these matters. The Contractor will present a brief overview of their project to include: team members with roles, technical approach, schedule – milestone – deliverable chart covering the full contract period of performance (POP), discussion of risks (schedule, cost, performance/product), and any other topics the Contractor wishes to discuss.

Threshold: Attend meeting, present on the topics as appropriate, deliver briefing materials as specified

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Reschedule missed meeting at no additional cost to the government; invoices will not be paid until the Government’s kickoff meeting has taken place Standard(s): Inspection applies to all standards.

C.11.d. [A002] Monthly Progress Reports and Invoices: Reports describing progress on the project shall be submitted to the COR and TPOCs via email no later than the 10th calendar day following the reporting period in the format and content specified by CRREL.

The report shall summarize work executed during the reporting month for each of the lines of effort (LOEs) clearly and distinctly labeled in subject headings. The vendor shall discuss any current or anticipated risk to schedule, cost, or performance. Additional data that should be included in the Progress Reports are the number of employees working on the contract and the total cost of the invoice for the subject period of reporting. Invoices for partial (monthly) payment shall be accompanied by a current progress report. Invoices revived without progress report will be rejected. Invoices must clearly state the period of reporting for which payment is requested or they will be rejected.

Threshold: Error free and complete progress reports and invoices delivered on time

Objective: COR observes evidence that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Rework/replacement required due to negligent mistakes will be accomplished at no additional cost to the government; invoices will not be paid unless progress reports and invoices are submitted IAW the contract

C.11.e. [A003] Technical Meeting with CRREL – Task 1. Technical meetings will take place in-person at CRREL or UH and/or via WebEx Telecon to discuss findings associated with links between observed turbulence attributes and sand fluxes. Execution and delivery schedule is established in Paragraph C.10.

Threshold: Attend meeting, present on the topics as appropriate, deliver briefing and other technical materials as required such as PDAL software and source code and subsequent Quality Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Reschedule missed meeting at no additional cost to the government. Fix critical software errors

C.11.f. [A004] Technical Meeting with CRREL – Task 2. A technical meeting will take place in-person at CRREL or UH and/or via WebEx Telecon to discuss findings associated with the conceptual sand flux model. Execution and delivery schedule is established in Paragraph C.10.

other technical materials as required. Software, source code, and subsequent Quality Control checks when assessing the software/algorithm performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Reschedule missed meeting at no additional cost to the government Standard(s): Inspection applies to all standards. Fix critical software/algorithm errors.

C.11.g. [A005] Technical Meeting with CRREL – Task 3. A technical meeting will take place in-person at CRREL or UH and/or via WebEx Telecon that will discuss results from the sand flux validation assessment. Execution and delivery schedule is established in other technical materials as required. such as PDAL software and source code and subsequent Quality Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.h. [A006] Technical Meeting with CRREL – Task 4. A technical meeting will take place in-person at CRREL or UH and/or via WebEx Telecon that will discuss findings associated with links between observed turbulence attributes and LES model parameters.

subsequent Quality Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.i. [A007] Technical Meeting with CRREL – Task 5. A technical meeting will take place in-person at CRREL or UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in subsequent Quality Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.j. [A008] Technical Meeting with CRREL – Task 6. A technical meeting will take subsequent Quality Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.k. [A009] Technical Meeting with CRREL – Task 7. A technical meeting will take

Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.l. [A010] Technical Meeting with CRREL – Task 8. A technical meeting will take

Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.m. [A011] Technical Meeting with CRREL – Task 9. A technical meeting will take subsequent Quality Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.n. [A012] Data Collection – Task 10. A technical meeting will take place in-person at CRREL or UH and/or via WebEx Telecon that will discuss preliminary results from the dust model assessment. Execution and delivery schedule is established in Paragraph C.10.

other technical materials as required. Data and metadata collected in the field. Any field notes taken during data collection. All data belongs to the government. The government will determine appropriate classification of data such as open, or For Official Use Only.

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

C.11.o. [A013] Final Software Deliverable. The Contractor shall provide a copy the code generated to perform the contracted analyses, as well as the code used. All software, affiliated user guides or readme files, and example input/output data will be delivered to CRREL electronically on an external storage device or via email if size permits. The Contractor shall also deliver any supporting material needed to understand or work with the final product. Execution and delivery schedule is established in Paragraph C.10. All software developed is deemed government owned and the government can at its discretion release the software as open source.

Threshold: Product delivered error-free, on time, and addressing the requirements IAW the contract and the intent of the product. Software, source code, and subsequent Quality Control checks when assessing the software performance – to be used by the government as a starting point to perform Quality Assurance. The Quality Control should include any testing scripts if used in the Quality Control effort.

Objective: COR observes evidence that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Rework/replacement required due to negligent mistakes will be accomplished at no additional cost to the government

C.11.p. [A014] Final Technical Report. The Contractor shall deliver a final report of achievement summarizing the results of the research performed under this contract submitted in the format and content specified by CRREL that reports on findings and success toward meeting goals, any problems encountered with solutions, and discussions recommending next stages of development to mature the System Architecture, Algorithms, and other elements.

An electronic version of the Draft-Final Report shall be provided to the COR and TPOC(s) for review/feedback at least one (1) month prior to the end of POP. The Government will review and provide comments within fifteen (15) days of receipt. A final version, incorporating Government review comments, shall be submitted no later than the last day of the POP. The Contractor shall include a completed Standard Form 298, Report Documentation Page, with each copy of its final report as required by DFARS 252.235-7011.

Threshold: Documentation delivered error-free, on time, and addressing the requirements of the product IAW the contract and the intent of the product.

Objective: COR observes evidence that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Rework/replacement required due to negligent mistakes will be accomplished at no additional cost to the government

C.11.q. [A015] Final Project Meeting with Government (Contract Close Out). The purpose of this meeting is to close out the contract for this effort between the Government and the Contractor. The meeting may be held at CRREL, the ERDC Vicksburg campus, UH, or via WebEx/Telecon with government representatives, TPOCs, and other official stakeholders as appropriate. The vendor and the government may review final deliverables, review the products developed, and discuss any other aspects of the contract as appropriate.

The final close out meeting will be scheduled to occur after the draft-Final report is received.

Threshold: Attend meeting, present on the topics as appropriate, deliver materials as specified

Objective: COR notes that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Reschedule missed meeting at no additional cost to the government Standard(s): Inspection applies to all standards.

C.11.r. [A016] Accounting for Contractor Services (ECMRA): The Office of the Assistant Secretary of the Army (Manpower & Reserved Affairs) operates and maintains a secure Army data collection site where the contractor will report ALL contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address: https://ecmra.army.mil/. The required information includes: (1)

Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5) Estimated direct labor hours (including sub-contractors); (6) Estimated direct labor dollars paid this reporting period (including sub-contractors); (7) Total payments (including sub-contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information); (11) Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language: and (13) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country). As part of its submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor’s systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web site.

NDAA DATA

UIC W2R2AA – Military Appropriation

FSC AZ12

Contract Number W913E520C0003 Contract Fiscal Year 2020 Form of Contract Action Definitive Contract Contract Type Firm-fixed-price PBSA Yes Non-DoD Purchasing Agency (leave blank) Competed Action Full and Open Competition If Competed, number of offerors

Small Business No Small Disadvantaged Business No Women-owned Small Business No DoD Administering Component USA- USACE CRREL, Hanover Contracting Organization USA- USACE CRREL, Hanover

Threshold: enter manpower data IAW the contract requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Rework/replacement required due to negligent mistakes will be accomplished at no additional cost to the government; failure to enter data will be reflected in the Contractor Performance Assessment Reporting System (CPARS)

C.11.n. [A012] DD Form 882: The Contractor shall submit DD Form 882(s) in accordance with Section I, Clause No. 252.227-7039, “Patents – Reporting of Subject Inventions”. If the period of service of this contract is not in excess of eighteen (18) months, an interim DD Form 882 is not required

Threshold: Comply with Patents – Reporting of Subject Inventions requirements requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Rework/replacement required due to negligent mistakes will be accomplished at no additional cost to the government

C.11.o. [A013] Mandatory Training and Security Procedures: The Contractor shall complete all required training per Paragraph C.13 and provide proof of training to the COR per the schedules outlined in the training paragraphs.

Threshold: Comply with all training certifications and training procedures per the contract Paragraph C.13 and any other relevant clauses

Objective: COR observes evidence that the Contractor has exceeded threshold requirements.

Surveillance & Inspection:

How: 100% inspection Who: The COR will determine the final assessment of performance, with input from the TPOC(s) and other stakeholders as appropriate.

Incentive: Rework/replacement required due to negligent mistakes will be accomplished at no additional cost to the government; invoice payments may be withheld if the vendor fails to complete required training

C.12. VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS OF

ENGINEERS

CONTRACTS: In addition to complying with the requirements outlined in FAR Part 22.13, FAR Provision 52.222-38, FAR Clause 52.222-35, FAR Clause 52.222-37, DFARS 222.13 and Department of Labor regulations, U.S. Army Corps of Engineers (USACE) contractors and subcontractors at all tiers are encouraged to promote the training and employment of U.S.

veterans while performing under a USACE contract. While no set-aside, evaluation preference, or incentive applies to the solicitation or performance under the resultant contract, USACE contractors are encouraged to seek out highly qualified veterans to perform services under this contract. The following resources are available to assist USACE contractors in their outreach efforts:

Federal Veteran employment information at http://www.fedshirevets.gov/index.aspx Department of Labor Veterans Employment Assistance http://www.dol.gov/vets/ Department of Veterans Affairs–VOW to Hire Heroes Act http://benefits.va.gov/vow/ Army Wounded Warrior Program – http://wtc.army.mil/modules/employers/index.html U.S. Chamber of Commerce Foundation–Hiring Our Heroes http://www.hiringourheroes.org/ Guide to Hiring Veterans – Reference Material http://www.whitehouse.gov/sites/default/files/docs/white_house_business_council_- _guide_to_hiring_veterans_0.pdf

C.13. ANTI-TERRORISM AND OPERATIONAL SECURITY REQUIREMENTS

(AT/OPSEC):

C.13.a. AT Level 1 Training. All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, controlled access areas, or require network access, shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Upon request, the contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website:

http://jko.jten.mil/courses/atl1/launch.html; or it can be provided by the RA ATO in presentation form which will be documented via memorandum.

C.13.b. CRREL Site Access. Contractor personnel allowed on site shall follow all sign-in and security regulations as directed by the CRREL Security Office, COR, and TPOC, and as listed below:

i. U.S. Citizens – Only U. S. Citizens are allowed on site.

ii. Personnel List – Contractor shall supply the TPOC with a list of his employees who will be working on the CRREL site.

iii. Positive Picture ID – Contract personnel shall provide a positive picture ID prior to site access.

iv. Identification Badges – Contractor personnel are required to sign in with Security and to obtain and wear security identification badges while on government site.

v. Weapons – No weapons of any kind are allowed on site either in vehicles or on persons.

vi. Access/Deliveries – Contractor shall notify the TPOC the day before or as soon as possible when contractor or his subcontractors are to arrive or deliveries of equipment and/or supplies are to occur. Contractor must receive his or his subcontractor’s own deliveries. Government personnel are not allowed to receive deliveries for any contractor.

vii. General Disruption – General disruption by contractor is limited to the immediate work areas. Contractor products, tools, and/or equipment shall stay within the immediate work areas.

viii. Tools/Equipment – Contractor is strictly responsible for the security of all products, tools, and/or equipment used during the duration of this contract.

C.13.c. Contractors who do not require CAC, but require access to a DoD facility or installation). The Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05 / AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative, as NCIC and TSDB are available), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

C.13.d. iWATCH Training. The contractor and all associated subcontractors shall brief all employees on the USACE iWATCH program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 45 calendar days of contract award and within 45 days of new employees commencing performance on the contract.

The contractor shall provide certification of completion to the COR within 10 days of training completion. Training documents will be provided by the Security Office.

C.13.e. Pre-screen Candidates Using E-Verify Program. If the candidate does not have a Government completed background check or one as not been requested, the Contractor must pre-screen Candidates using the E-verify Program (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Vendor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible Candidates must be provided to the COR no later than 3 business days after the initial contract award."

*When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, with the designated Government representative. This Form will be provided to the Contracting Officer and shall become part of the official contract file.

C.14. INVOICING AND PAYMENT INSTRUCTIONS: Invoices shall be submitted monthly along with the vendor’s monthly progress report. Invoices shall cover the period of activity described in the accompanying progress report. Invoices received without a progress report will be rejected by the Government. Progress Reports are discussed above in the “REPORTS AND DELIVERABLES” section of this PWS. Payments for this contract will be made via Millington. The vendor is thus instructed to use the following approach for invoice submission.

C.14.a. Monthly Progress Report: The vendor must submit the progress report by the 10th of the month following the period of reporting. The progress report is submitted to the COR and TPOCs. The COR will review the report for tracking against the contract milestones, and also obtain concurrence from the TPOCs that the work is approved.

C.14.b. Monthly Invoice: The Contractor shall submit the invoice along with the accompanying progress report to the COR via email, copying the TPOCs each month per the schedule outlined above. The COR will submit invoices to Millington for payment after approval.

C.14.c. Contracting Officer’s Representative (COR): The COR for this contract is Bryan Baker: Bryan.E.Baker@usace.army.mil, (603) 738-1633.

C.14.d. Invoice Acceptor: The primary invoice acceptor for this contract is the COR, Bryan Baker, Bryan.E.Baker@usace.army.mil, (603) 738-1633. When submitting invoices, the contractor shall copy the COR on the email distribution. The contractor shall also copy Jackie Walker who serves as a second acceptor: Jacqueline.A.Walker@usace.army.mil, and 603-646-4717.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government 000101 N/A N/A N/A N/A 000102 N/A N/A N/A N/A 000103 N/A N/A N/A N/A 0002 Destination Government Destination Government

CLAUSES INCORPORATED BY REFERENCE

52.246-4 Inspection Of Services--Fixed Price AUG 1996 52.246-9 Inspection Of Research And Development (Short Form) APR 1984

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 POP 17-APR-2020 TO

16-APR-2023

N/A PR W2R2 COLD RGNS RSCH ENG LAB

REMOTE SENSING/GIS & WRB

72 LYME ROAD

HANOVER NH 03755-1290

603.646-4372

W14GQK

000101 N/A N/A N/A N/A

000102 N/A N/A N/A N/A

000103 N/A N/A N/A N/A

0002 POP 17-APR-2020 TO

16-APR-2023

N/A PR W2R2 COLD RGNS RSCH ENG LAB

REMOTE SENSING/GIS & WRB

72 LYME ROAD

HANOVER NH 03755-1290

603.646-4372

W14GQK

52.246-16 Responsibility For Supplies APR 1984 52.247-34 F.O.B. Destination NOV 1991

Section G - Contract Administration Data

INVOICING INSTRUCTIONS

G.1. METHOD OF PAYMENT: Invoices shall be submitted monthly along with the Contractor’s monthly progress report. Invoices will cover the period of activity described in the accompanying progress report. With reference to G Clause No. 252.232-7003, ELECTRONIC SUBMISSION OF PAYMENT REQUESTS, at the Contractor's Option he may, (a) upon completion of the work, submit one invoice for payment of the entire amount due under the contract in one lump sum, or (b) submit estimates of the amount and value of the work and services performed under the contract at any time during the period of performance, but not more frequently than once a month or for amounts…