Attachment 1 - Draft Performance Work Statement (145027-24-0047).pdf

PACIFIC MARINE ENVIRONMENTAL LABORATORY (PMEL)

DATA MANAGEMENT DEVELOPMENT

145027-24-0047

PERFORMANCEWORK STATEMENT

02/29/2024

I. INTRODUCTION

The Science Data Integration Group (SDIG) with the Pacific Marine Environmental Laboratory (PMEL) applies innovative software concepts to develop software for scientific data integration tools. One of the in-house developed, and widely accepted tools developed by SDIG is the Live Access Server (LAS) application.

One of the in-house areas of specialized experience established in SDIG is the development and hosting of data discovery and data visualization platforms, like the Live Access Server (LAS) Application. LAS is a unique Web application for geo-science datasets that has been developed by and is supported by the SDIG at the National Oceanic & Atmospheric Administration’s (NOAA) PMEL (see https://ferret.pmel.noaa.gov/LAS/). LAS strives to blend data selection and sub-settings, with data analysis and visualization tool for environmental science and research purposes.

As with most software, improvement and enhancement is key. As LAS reached the end of its support lifecycle, its functionality is being redeveloped into a new application that will also use a new software development platform. This tool, temporarily branded as PyLAS, moves away from the JAVA programming language and is written in Python and JavaScript. Besides the PyLAS application, the contractor will act as the lab focal point for data visualization, develop quality control applications, and work on commercial cloud data storage.

II. PLACE OF PERFORMANCE

The primary place(s) of performance is/are as follows:

Pacific Marine Environmental Laboratory Building #3 7600 Sand Point Way NE Seattle, WA 98115

Some activities within this statement of objectives may be performed at other locations rather than the primary place of performance. The contractor must seek Contracting Officer’s Representative (COR) approval for any location not designated as the primary place of performance and for any remote work arrangements.

III. SCOPE OFWORK

Development of scientific data visualization software requires a foundational understanding of a LAS and the use cases that make software successful lead to both software and scientific research being adopted broadly.

DRAFT

https://ferret.pmel.noaa.gov/LAS/

In broad terms, ocean and climate research progress through a blend of observations, research, and modeling-based research. PMEL classifies different forms of data that emerge from these approaches as "feature types". For example: "profiles" that measure vertically into the oceans, "time series" that result from an instrument located at a point in space, and space-time "grids" that are output by models. It is within this context of scientific exploration and product development that scientific development takes place.

The contractor will work closely with PMEL scientists, developers, and data practitioners, as well as other NOAA offices, to advise and develop new data analysis and visualization tools. The PyLAS Application will be developed to a fully operational application. The contractor will work closely with PMEL colleagues to support the PMEL PLotly Dash Enterprise suite of tools.

The contractor will work closely with the Computing and Network Services Division (CNSD) to ensure the Dash Enterprise Application is configured for optimal utilization at PMEL. The contractor will be an information focal point on environmental data management, data visualization, ERDDAP application configuration, and for PMEL and NOAA data management and developer meetings.

IV. OBJECTIVES

NOAA’s objective is to award a scientific data integration vendor with a contract to work closely with the Computing and Network Services Division (CNSD) to ensure the Dash Enterprise Application is configured for optimal utilization at PMEL.

The contractor will use expert judgment to manage environmental data, execute data visualization software, run ERDDAP application configurations, and host NOAA Data Management Developer Meetings. The vendor will also regularly provide PMEL with regular weekly progress reports.

V. TASKS

The contractor will use expert judgment to execute the following task list.

All tasks listed will result in the completion of the products listed in Section 6 - Deliverables.

Task Deliverable Format

Develop and refine the PyLAS Application before full lab release, ready the application for iterative improvements.

PyLAS Application Software

Define optimal ERDDAP configuration against commercial cloud data storage.

ERDDAP configurations Method descriptions and functional code (Python)

Define optimal subsetting and data retrieval for commercial cloud hosted large volume gridded datasets.

Cloud solution for gridded data sets

Common practice descriptions, software resource libraries

Continues development and enhancement of quality control interfaces, Interactive software development

Software in Github

Provide PMEL with monthly progress reports.

Progress reports PDF

Present weekly updates during NOAA data management meetings.

SDIG meeting attendance Verbal

Provide PMEL with monthly progress report updates on the status of applications, meeting tasks, and interface developments.

Progress Reports PDF

Software development in support of Uncrewed platform and data buy support.

Iterative software deliveries

Software files in Github

Software in support of OceanSITES data upload dashboard

Iterative software deliveries

Software files in Github

Invoicing Requirements: Submit Microsoft Word, Adobe, or Google Doc attached with invoice in IPP.gov

VI. DELIVERABLES.

Deliverables Table

PWS

Paragraph

Title Format Required Date Frequency Distribution

4.1 PyLAS

Application

Software December 01, Once Total Payment Obligation to Claimant

TPOC

4.2 Data Retrieval

Optimization (AWS and GCP)

Ongoing, progress reports

August 1, 2027 Continuous TPOC

4.3 Cloud solution

for gridded data sets

August 1, 2025 Once TPOC

4.4 QC user

interfaces

Software August 1, 2025 Once TPOC

4.5 Data visualization

applications

Software -various

August 1, 2027 Annually TPOC

4.6 CEFI data

retrieval routines

Continuous development

Continuous development

Incremental improvemen ts based on user requests.

TPOC

4.7 SDIG meeting

attendance

Weekly N/A Weekly TPOC

4.8 Conference and

PMEL in-reach attendance

Monthly attendance.

N/A Monthly TPOC

4.9 Progress Reports Microsoft

Word, or Adobe, or Google Doc submitted by email or attached with invoice in IPP.gov

Initial: With each invoice

Monthly TPOC, COR

4.10 Quality Control

Plan

Microsoft Word, or Adobe, or Google Doc submitted by email

Initial: Within 2 weeks after contract award Subsequent: As needed for changes

Initial and as required for changes

TPOC, COR

VII. IT SECURITY REQUIREMENTS

The contractor(s) data visualization suite will interact with low risk Federal Information Security Management Act (FISMA) systems, and does not involve any PII related data.

The contractor(s) are also required to complete the annual NOAA On-line Security Awareness Training.

Suitability/Risk Level - The suitability or risk level for this work has been determined and confirmed to be: Low. As such, the contractor shall pre-screen their employees to eliminate anyone who does not meet the following criteria: The prospective employees must be U.S. Citizens.

48 CFR 1352.237-71 Security Processing Requirements—Low Risk Contracts (APR 2010)

(a) Investigative Requirements for Low Risk Contracts. All contractor (and subcontractor) personnel proposed to be employed under a Low Risk contract shall undergo security processing by the Department's Office of Security before being eligible to work on the premises of any Department of Commerce owned, leased, or controlled facility in the United States or overseas, or to obtain access to a Department of Commerce IT System. All Department of Commerce security processing pertinent to this contract will be conducted at no cost to the contractor.

(b) Investigative requirements for Non-IT Service Contracts are:

(1) Contracts more than 180 days—National Agency Check and Inquiries (NACI).

(2) Contracts less than 180 days—Special Agency Check (SAC).

(c) Investigative requirements for IT Service Contracts are:

(1) Contracts more than 180 days—National Agency Check and Inquiries (NACI).

(2) Contracts less than 180 days—National Agency Check and Inquiries (NACI).

(d) In addition to the investigations noted above, non-U.S. citizens must have a background check that includes an Immigration and Customs Enforcement agency check.

(e) Additional Requirements for Foreign Nationals (Non-U.S. Citizens). Non-U.S.

citizens (lawful permanent residents) to be employed under this contract within the United States must have:

(1) Official legal status in the United States;

(2) Continuously resided in the United States for the last two years; and

(3) Obtained advance approval from the servicing Security Officer in consultation with the Office of Security headquarters.

(f) DOC Security Processing Requirements for Low Risk Non-IT Service Contracts.

Processing requirements for Low Risk non-IT Service Contracts are as follows:

(1) Processing of a NACI is required for all contract employees employed in Low Risk non-IT service contracts for more than 180 days. The Contracting Officer's Representative (COR) will invite the prospective contractor into e-QIP to complete the SF-85. The contract employee must also complete fingerprinting.

(2) Contract employees employed in Low Risk non-IT service contracts for less than 180 days require processing of Form OFI-86C Special Agreement Check (SAC), to be processed. The Sponsor will forward a completed Form OFI-86C, FD-258, Fingerprint Chart, and Credit Release Authorization to the servicing Security Officer, who will send the investigative packet to the Office of Personnel Management for processing.

(3) Any contract employee with a favorable SAC who remains on the contract over 180 days will be required to have a NACI conducted to continue working on the job site.

(4) For Low Risk non-IT service contracts, the scope of the SAC will include checks of the Security/Suitability Investigations Index (SII), other agency files (INVA), Defense

Clearance Investigations Index (DCII), FBI Fingerprint (FBIF), and the FBI Information Management Division (FBIN).

(5) In addition, for those individuals who are not U.S. citizens (lawful permanent residents), the Sponsor may request a Customs Enforcement SAC on Form OFI-86C, by checking Block #7, Item I. In Block 13, the Sponsor should enter the employee's Alien Registration Receipt Card number to aid in verification.

(6) Copies of the appropriate forms can be obtained from the Sponsor or the Office of Security. Upon receipt of the required forms, the Sponsor will forward the forms to the servicing Security Officer. The Security Officer will process the forms and advise the Sponsor and the Contracting Officer whether the contract employee can commence work prior to completion of the suitability determination based on the type of work and risk to the facility (i.e., adequate controls and restrictions are in place). The Sponsor will notify the contractor of favorable or unfavorable findings of the suitability determinations. The Contracting Officer will notify the contractor of an approved contract start date.

(g) Security Processing Requirements for Low Risk IT Service Contracts. Processing of a NACI is required for all contract employees employed under Low Risk IT service contracts.

(1) Contract employees employed in all Low Risk IT service contracts will require a National Agency Check and Inquiries (NACI) to be processed. The Contracting Officer's Representative (COR) will invite the prospective contractor into e-QIP to complete the SF-85. Fingerprints and a Credit Release Authorization must be completed within three working days from start of work, and provided to the Servicing Security Officer, who will forward the investigative package to OPM.

(2) For Low Risk IT service contracts, individuals who are not U.S. citizens (lawful permanent residents) must undergo a NACI that includes an agency check conducted by the Immigration and Customs Enforcement Service. The Sponsor must request the ICE check as a part of the NAC.

(h) Notification of Disqualifying Information. If the Office of Security receives disqualifying information on a contract employee, the Sponsor and Contracting Officer will be notified. The Sponsor shall coordinate with the Contracting Officer for the immediate removal of the employee from duty requiring access to Departmental facilities or IT systems. Contract employees may be barred from working on the premises of a facility for any of the following reasons:

(1) Conviction of a felony crime of violence or of a misdemeanor involving moral turpitude.

(2) Falsification of information entered on security screening forms or of other documents submitted to the Department.

(3) Improper conduct once performing on the contract, including criminal, infamous, dishonest, immoral, or notoriously disgraceful conduct or other conduct prejudicial to the Government regardless of whether the conduct was directly related to the contract.

(4) Any behavior judged to pose a potential threat to Departmental information systems, personnel, property, or other assets.

(i) Failure to comply with security processing requirements may result in termination of the contract or removal of contract employees from Department of Commerce facilities or denial of access to IT systems.

(j) Access to National Security Information. Compliance with these requirements shall not be construed as providing a contract employee clearance to have access to national security information.

(k) The contractor shall include the substance of this clause, including this paragraph, in all subcontracts.

VIII. CONSTRAINTS AND RISKS

All software development should comply with the policies and IT infrastructure provided by DOC, NOAA and PMEL.

The three development operating systems (OS) supported by PMEL are Windows 10 and onwards, Apple OS-X, and Red Hat Linux Enterprise 7 and onwards.

Tasks listed on this contract will be developed mostly Red Hat platform.

If the contractor is not approved, the Pacific marine Environmental Laboratory will be unable to provide ocean and climate research progress and document observations, research, and modeling-based research using innovative software concepts.

PMEL will be unable to classify different forms of data that emerge as "feature types".

Examples of feature types are: "profiles" that measure vertically into the oceans, "time series" that result from an instrument located at a point in space, and space-time "grids" that are output by models.

PMEL will not be equipped with the software required to conduct scientific exploration and develop critical products for environmental data management.

IX. TECHNICAL POINT OF CONTACT

Technical Point(s) of Contact (TPOC)

One or more TPOCs will assist the COR as needed. 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, Contracting Officer’s Representative (COR). Only the contracting officer has the authority to direct, revise, or otherwise change the requirements of the subject contract.

The TPOC(s) will be identified via a separate letter and may be changed at any time by the Government via letter without prior notice to the contractor.

X. DELIVERABLES

The following list of deliverables will be provided by the contractor to DOC - NOAA -

PMEL.

Deliverables Distribution

PyLAS Application TPOC

Data Retrieval Optimization (AWS and GCP) TPOC

Cloud solution for gridded data sets TPOC

QC user interfaces TPOC

Data visualization applications TPOC

CEFI data retrieval routines TPOC

SDIG meeting attendance TPOC

Conference and PMEL in reach attendance TPOC

Progress Reports TPOC, COR

Quality Control Plan TPOC, COR

XI. GOVERNMENT FURNISHED PROPERTY/INFORMATION

The contractor will have a government furnish email account, and secure access to software development machines. To ensure secure access to PMEL IT infrastructure and Government laptop is provided for this access via a dedicated virtual private network (VPN) connection.

All interactions with PMEL infrastructure is to be done via this connection.

XII. PERFORMANCE REQUIREMENTS SUMMARY

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

Incentive: Timely payment and potential for superior performance rating.

Remedy: Withholding of invoice until rectified and/or negative performance rating.

PWS

Paragraph

Performance Objective Acceptable Quality Level

Review Frequency

V. Tasks The contractor shall develop an operational PyLAS application

95% Annually

IV. Objectives Dash Enterprise application configuration 95% Annually

XIII. TRAVEL

Domestic and international travel will be required for the contractor to attend scientific meetings.

Annually the following travel will be required, although not limited to:

1. A weeklong site visit (meeting) to PMEL.

The contractor will bill separately for the costs incurred with this travel.