DRAFT Attachment 1 - Performance Work Statement REQUIREMENTS-26-2413.docx

Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

Weather Program Office (WPO)

PERFORMANCE WORK STATEMENT (PWS)

SBES Data Discovery and Interoperability Awards

1. BACKGROUND

NOAA’s Weather Ready Nation (WRN) initiative helps to ensure the Nation becomes more resilient to increasing extreme weather and water events by advancing understanding of how to effectively prepare for and communicate these events. This initiative encourages organizations to partner with first responders, emergency managers, local government agencies, businesses, the media, and the public to prepare for potential weather disasters. One way of facilitating this partnership is by leveraging existing discoverable and interoperable data that can be utilized to make informed decisions and ultimately accelerate NOAA’s capability to transition research outputs to operationally relevant assets.

2. OBJECTIVES

The Government requires a contractor to deliver an existing data-rich social, behavioral, and economic science (SBES) framework optimized for data discovery and interoperability studies. This unique SBES framework and database will be used as a mechanism to administer competitive subcontracts for discrete interoperability activities among the academic SBES community following final selection and approval of subcontractors by the COR. Specifically, the subcontract administration of activities shall fulfill the following objectives to deliver a single, indivisible program. The Government receives no independent value from partial performance or individual subcontract cycles prior to the delivery of the final cumulative program report:

· Execute metadata documentation and alignment work that demonstrably improves the discoverability of SBES datasets.

· Execute dataset integration proofs-of-concept that successfully demonstrate SBES data interoperability with meteorological or hydrological systems.

· Deliver open-source tooling (e.g., Python packages or equivalent) that enables non-developers to access and use SBES datasets easily.

· Conduct data interoperability readiness assessments that clearly identify gaps and actionable pathways for NOAA operational integration of SBES data.

3. SCOPE

This contract requires a contractor to solicit, review, and administer targeted subcontracts to academic researchers that advance SBES data assets toward operational readiness within the weather and water enterprise following final COR selection and approval. The contractor’s subcontractors will undertake concrete interoperability activities — including metadata alignment, open-source tooling development, dataset integration proofs-of-concept, and interoperability readiness assessments — that directly improve the discoverability and usability of SBES datasets for integration with meteorological and hydrological systems.

The core activities executed under this contract will directly improve the discoverability and usability of SBES datasets for seamless integration with meteorological and hydrological systems, leveraging a well-established SBES framework and data. This program aligns with NOAA’s Weather Ready Nation initiative, which prepares communities for extreme weather, water, and climate events. Taking advanced action to prepare people and places for extreme events can reduce the most devastating impacts from tornadoes, hurricanes, flooding, wildfires, and blizzards.

4. TASKS

The contractor and, as applicable, subcontractors, shall perform the following tasks:

4.1 Design and execute a competitive subcontract solicitation process that meets the objectives outlined herein, subject to final COR approval of the solicitation framework.

4.2 Develop draft subcontract review criteria for COR approval that align with NOAA’s data interoperability and operational goals.

4.3 Provide technical evaluations of subcontract proposals to inform final selection by the COR.

4.4 Monitor subcontractor progress and verify technical deliverable alignment against approved performance timelines.

4.5 Synthesize outputs across all subcontractors to identify patterns, gaps, and lessons learned.

4.6 Produce summary reports suitable for NOAA program review and future investment planning.

4.7 Conduct phased rounds of subcontract solicitation and administration over the period of performance, incorporating lessons learned from prior cycles.

5. DELIVERABLES

The following key deliverables are required for the contract:

5.1. Program Administration: The contractor shall provide all draft subcontractor solicitation materials and a formal proposed administrative review framework to the COR for approval. These documents shall establish the administrative requirements and process to:

5.1.1. Establish an administrative review framework to track metadata documentation alignment work that demonstrates improvements in the discoverability of SBES datasets.

5.1.2. Establish an administrative review framework to track proof-of-concept integration studies that successfully demonstrate SBES data interoperability with meteorological or hydrological systems.

5.1.3. Establish an administrative review framework to track the development of open-source tools that enable non-developers to access and use SBES datasets easily.

5.1.4. Establish an administrative review framework to track data interoperability readiness assessments that clearly identify gaps and actionable pathways for NOAA operational integration of SBES data.

5.1.5. Ensure the draft subcontract review criteria align with NOAA’s data interoperability and operational goals prior to final COR approval.

5.2. Documentation: The contractor shall provide documentation of all proposed funded subcontracts, including scope, recipients, and expected outputs.

5.3. Reporting: The contractor shall provide cumulative program reports on the status of the solicitation subcontracts leading to final project completion.

5.3.1. The reports shall include a compilation of the subcontractor interoperability outputs for metadata documentation, open-source tools, dataset integration proof-of-concepts, and interoperability readiness assessments.

5.3.2. A subcontract summary report for each funding cycle that documents funded activities, outputs, and recommendations for subsequent rounds.

5.3.3. A cross-subcontract synthesis report that summarizes progress, overall outputs, and recommendations for future cycles.

5.3.4. A final cumulative program report that is delivered in accordance with Government-approved criteria to inform continued investment and program replication, which represents the final, nonseverable end-product of this contract.

6. PLACE OF PERFORMANCE

Work will be performed at the contractor’s facility.

7. TECHNICAL POINT(S) OF CONTACT (TPOCs) One or more TPOCs may assist the COR as needed; while the government will provide technical guidance and, when applicable, establish technical priorities within the scope of the PWS, the contractor remains responsible for the technical accuracy and delivery of all services. All parties are reminded that this in no way detracts or changes the responsibilities and limitations described in the contract including, but not limited to, CAR 1352.201-70, Contracting Officer’s Authority, and CAR 1352.201-72, COR. Only the contracting officer has the authority to direct, revise, or otherwise change the requirements of the contract.

TPOC(s) if applicable will be identified via email or separate letter and may be changed at any time by the contracting officer without prior notice to the contractor.

8. MEETINGS

The contractor shall hold quarterly check-ins with the COR and/or TPOCs to track progress on activities and tasks.

9. Government-Furnished Property (GFP), Material (GFM), Equipment (GFE), or Information (GFI) Not applicable.

10. PERSONNEL

The contractor shall ensure that all personnel have the expertise, knowledge, training, and possess credentials needed to meet the requirements of this PWS. The contractor shall, when communicating with outside parties, NOAA personnel, and other NOAA contractors, identify themselves as contractors to ensure they are not mistaken as Government employees. Contractor employees shall identify themselves as contractors (in meetings, workshops, emails, reports, etc.) and display a badge in plain view above the waist when in person. Email messages and work products such as memos, presentations, and other documents from contractor employees shall contain a signature block identifying the individual as a contractor employee with the company’s name, and a reference to being a NOAA agency contractor.

11. QUALITY

Quality Control Quality control is the responsibility of the contractor. The contractor is responsible for the delivery of quality services to the Government.

Quality Assurance Quality assurance is a program for the systematic monitoring and evaluation of contract performance to ensure that standards of quality are being met. Quality assurance is the responsibility of the government. The government will evaluate the contractor’s performance in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is a government only document primarily focused on what the government will do to assure that the contractor has performed in accordance with the requirements of the contract.

Contract Discrepancy Meetings The government will issue a written Contract Discrepancy Report when the contractor’s performance is found to be unacceptable for any contract service. The COR will, within two work days of discovery of a discrepancy, call a meeting between the PM, and any others, as appropriate, to address the unacceptable performance. The government will, within two work days of the meeting, prepare a Discrepancy Report that explains the problem and documents the meeting discussion. This report will be sent to the PM and to the CO.

Within three work days of receipt of the Discrepancy Report, the contractor shall provide, to the COR and the CO, a written statement of the planned corrective action. The contractor shall take corrective action within two work days after providing the written statement of corrective action.

If the contractor disagrees with the Discrepancy Report, the contractor shall explain, in writing, areas of disagreement to the COR and CO within three work days of Discrepancy Report receipt. Upon receipt of the contractor’s written disagreement, the CO will recommend action.

12. PERFORMANCE REQUIREMENT SUMMARY (PRS)

The contractor shall be responsible to ensure all tasks are completed in accordance with the performance requirements. Failure to meet the performance requirements will be reported verbally to the contractor by the COR and reported on a Contract Discrepancy Report by the COR. The contractor shall correct substandard performance within the timeframe specified in the Contract Discrepancy Report.

The following incentives/remedies apply to all performance objectives listed below.

Incentive: Timely payment and potential for exercising option periods Remedy: Withholding of invoice until rectified and/or negative past performance rating

13. DELIVERABLES

Draft Subcontractor Solicitation Materials, including Review Criteria (Paragraph 5.1)

Subsequent: As needed for updates.

Administrative Review Framework (Paragraph 5.1)

Subsequent: As needed for updates.

Subsequent: As needed for updates.

Cumulative Program Reports (Paragraph 5.3)

Subsequent: Final 30 days prior to end of period of performance and as needed for updates.