Attachment 2 - Performance Work Statement EDS - Refinements TO1 w Attachments 9 30 2025.pdf

PERFORMANCE WORK STATEMENT

LAST UPDATED: 07 AUG 2025 PAGE 1/11

PERFORMANCE WORK STATEMENT (PWS)

FOR

ENVIRONMENTAL DATA SERVER (EDS) REFINEMENT SERVICES EXTENSION

1.0 GENERAL

1.1 BACKGROUND

The Coast Guard’s Command, Control, Communications, Computers, Cyber and Intelligence (C5I) Service Center (C5ISC) develops, builds, fields, trains, and supports advanced electronic command, control, and navigation systems. C5ISC develops Government Off-The-Shelf (GOTS) system components using contracted services to fulfill the mission requirements for Command, Control, Communications, Computers, Intelligence, Surveillance, & Reconnaissance (C4ISR) capabilities. The purpose of Search and Rescue Optimal Planning System (SAROPS) is the creation of Search and Rescue plans in direct support of the core US Coast Guard mission of Search and Rescue (SAR). SAROPS is used 24/7 in every US Coast Guard Sector and District Command Center. C5ISC uses a technical approach of leveraging existing GOTS and Commercial-Off-The Shelf (COTS) products with standard technologies and environments (e.g., ArcGIS) to create families of interoperable and compatible systems. C5ISC products adhere to enterprise level direction provided by the United States Coast Guard (USCG), Department of Homeland Security (DHS) and Defense Information Systems Agency (DISA).

The SAROPS application is written as series of extensions to the ArcGIS geographical information system (GIS) from Environmental Systems Research Institute (ESRI). SAROPS is deployed on a pool of servers positioned throughout the Coast Guard Area of Responsibility (AOR). Operators access SAROPS by use of the remote desktop capability of the standard workstation. Current commercial Environmental Data Server (EDS) subscription provides SAROPS with web services technology to obtain the current and wind data which is required to optimally run search object drift simulations. The Search and Rescue (SAR) Controller identifies the Area Of Interest (AOI) and the EDS then provides a set of candidate wind and current data products for that AOI. SAROPS then transmits AOI and product parameters to the EDS provider and receives resultant wind and current data sufficient to run the drift simulation. The EDS provider collects datasets from various providers, verifies the integrity of those datasets and formats the data properly for SAROPS ingestion. These communications are temporary, initiated by SAROPS and terminated by SAROPS after receipt of requested information.

1.2 SCOPE

The purpose of this task order is to enhance current subscription services for environmental data services to optimally run search object drift simulations, including but not limited to new data elements/products, data analytics, additional data aggregation, smart Area of Interest processing, status monitoring web site for EDS health status information, and Web Mapping Services for alternate methods of product viewing.

1.3 OBJECTIVE

1.4 The objective of this solicitation is to provide enhancements to the current EDS subscription services for SAROPS.

1.5 APPLICABLE DOCUMENTS

file://hqnas/SHARED/G-A/G-ACS/CAAT%20Team/TOOLBOX/SCOPE%20PARAGRAPHS.doc

LAST UPDATED: 07 AUG 2025 PAGE 2/11

The following documents may be helpful to the Contractor in performing the work described in this document.

Operations Security (OPSEC) Program, COMDTINST M5510.24 (Series) U.S. Coast Guard Cybersecurity Manual, COMDTINST M5500.13 (Series)

2.0 SPECIFIC REQUIREMENTS/TASKS

The general nature of the work for data service refinements under this contract consists of adapting the available web services of the EDS to maintain currency with state-of-the-market data sources & environmental models. Technology & academia regularly advance in their methodologies & modeling techniques for the environmental & oceanographic data upon which SAROPS relies for accurate search planning. As these technological advances occur, their incorporation into the environmental data services is crucial in order to maintain the best quality search planning capability within SAROPS, which is consistent with existing system requirements.

2.1 TASK ONE. EDS Data Service Refinements

2.1.1 The contractor must deliver the following data enhancements (see Appendix A - EDS Current Guide and Appendix B - EDS Wind Guide):

2.1.1.1 OSCAT Oceansat-2 Scatterometer Winds

2.1.1.2 NECDIS Synthetic Aperture Radar Winds

2.1.1.3 NOAA/AOML Near Real Time Geostrophic Currents

2.1.1.4 NASA/SPoRT Sea Surface Temperature

2.1.1.5 NWS Real Time Met Station Data

2.1.1.6 TBCOM2 Model Winds And Currents

2.1.1.7 EFCOM Model Winds And Currents

2.1.1.8 HFR: Isla Contoy, Mexico and Puerto Morelos, Mexico

2.1.1.9 Fathom Relocatable Model

2.1.1.10 OSMC: NOAA Observing System Monitoring Center Drifting Buoys

2.1.1.11 NOAA/NCEP HWRF winds, SST

2.1.1.12 NOAA/NCEI Blended Seawinds Product

2.1.1.13 Global Model Downscaling

2.2 TASK TWO. Data Assurance/Quality

2.2.1 The contractor must develop and deliver Operator Guidance documentation for each item in 2.1.1.

2.2.2 The contractor must perform data assurance/quality checks to ensure data delivered to SAROPS is consistent with the original data (see Appendix C – Web Service Details).

2.2.3 The contractor must perform any necessary data conversion to ensure data delivered to SAROPS is consistent with the original data.

2.2.4 The contractor must host the data on the EDS.

2.2.5 The contractor must output velocities and models’ velocities from the skill assessment to a csv file for download.

2.2.6 The contractor must explore the possibility of incorporating and, if feasible, include other Self-Locating Datum Marker Bouy (SLDMB)-type bouy data into the EDS (similarly as current SLDMBs)

LAST UPDATED: 07 AUG 2025 PAGE 3/11

2.2.7 The contractor must Implement process of aggregation of HYCOM Navy global model with the smaller low-res model domains (or with the same model type when it is available in a larger domain ie. UHI EDS products)

2.2.8 The contractor must develop an interface to download the models' surface current speeds at the SLDMB fixes and SLDMB speed used in skill assessment.

2.2.9 The contractor must provide skill assessment data shortly after the SLDMB is deployed

2.2.10 The contractor must protect proprietary model forecast data and observe and implement data distribution roles as defined by the USCG for the following:

2.2.10.1 CAPGIS

2.2.10.2 WoodsHole Group

2.2.10.3 WHG-TOPS

2.2.10.4 Fathom Relocatable Model

2.2.10.5 Any other private company not mentioned in 2.2.10.1 – 2.2.10.4

2.2.11 The contractor must restrict access to the data listed in 2.1.10 to only those contractors that need to work on that data set.

3.0 CONTRACTOR PERSONNEL

3.1 Qualified Personnel

The Contractor must provide qualified personnel to perform all requirements specified in this

PWS.

4.0 OTHER APPLICABLE CONDITIONS

4.1 PERIOD OF PERFORMANCE

The period of performance for this contract extension is 12/29/2025 – 12/28/2026.

4.2 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor’s facilities.

4.3 TRAVEL

Contractor travel will not be required for this requirement.

4.4 PROGRESS REPORTS (A001)

The Contractor must provide a monthly progress report to the Contracting Officer, COR and Product Line Project Manager (PL PM) via electronic mail for Contract Data Requirements List (CDRL) A001. This report must include a summary of all Contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any Contractor concerns or recommendations for the previous reporting period.

4.5 GENERAL REPORT REQUIREMENTS

LAST UPDATED: 07 AUG 2025 PAGE 4/11

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Microsoft Office Applications).

4.6 INTELLECTUAL PROPERTY

All Contractor developed processes and procedures first developed under this work statement and not otherwise covered by 5 52.227-14 Rights in Data – General (June 1987) shall be considered Government property.

All documentation, executable software and source code generated specifically for all tasks issued under this contract shall be delivered with Unlimited Rights in accordance with Federal Acquisition Regulation 52.227-14 Rights in Data – General (June 1987). Any disposal or destruction of such material must be pre-approved by the COR.

4.7 SECTION 508 COMPLIANCE

Section 508 Requirements (include in the SOW, PWS, or SOO) Section 508 of the Rehabilitation Act (classified to 29 U.S.C. § 794d) requires that when Federal agencies develop, procure, maintain, or use information and communications technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public with disabilities must be afforded access to and use of information and data comparable to that of Federal employees and members of the public without disabilities.

All products, platforms and services delivered as part of this work statement that, by definition, are deemed ICT shall conform to the revised regulatory implementation of Section 508 Standards, which are located at 36 C.F.R. § 1194.1 & Appendixes A, C & D, and available at https://www.ecfr.gov/cgi-bin/text-idx?SID=e1c6735e25593339a9db63534259d8ec&mc=true&node=pt36.3.1194&rgn=div5. In the revised regulation, ICT replaced the term electronic and information technology (EIT) used in the original 508 standards. ICT includes IT and other equipment.

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the Contracting Officer and a determination will be made according to DHS Directive 139-05, Office of Accessible Systems and Technology, dated November 12, 2018 and DHS Instruction 139-05- 001, Managing the Accessible Systems and Technology Program, dated November 20, 2018, or any successor publication.

1. 1.1 Section 508 Requirements for Technology Services (include in the SOW, PWS, or SOO)

2. When developing or modifying ICT, the Contractor is required to validate ICT deliverables for conformance to the applicable Section 508 requirements. Validation shall occur on a frequency that ensures Section 508 requirements is evaluated within each iteration and release that contains user interface functionality.

3. When modifying, installing, configuring or integrating commercially available or government-owned ICT, the Contractor shall not reduce the original ICT Item’s level of Section 508 conformance.

4. When developing or modifying web based and electronic content components, except for electronic documents and non-fillable forms provided in a Microsoft Office or Adobe PDF format, the Contractor shall demonstrate conformance to the applicable Section 508 standards (including WCAG 2.0 Level A and AA Success Criteria) by conducting testing using the DHS Trusted Tester for Web Methodology Version 5.0 or successor versions, and shall ensure testing is conducted by individuals who are certified by DHS on version 5.0 or successor versions (e.g. “DHS Certified Trusted Testers”). The Contractor shall provide the Trusted Tester Certification IDs to DHS upon request.

https://uscode.house.gov/view.xhtml?req=(title:29%20section:794d%20edition:prelim)%20OR%20(granuleid:USC-prelim-title29-section794d)&f=treesort&edition=prelim&num=0&jumpTo=true https://www.ecfr.gov/cgi-bin/text-idx?SID=e1c6735e25593339a9db63534259d8ec&mc=true&node=pt36.3.1194&rgn=div5 https://www.ecfr.gov/cgi-bin/text-idx?SID=e1c6735e25593339a9db63534259d8ec&mc=true&node=pt36.3.1194&rgn=div5

LAST UPDATED: 07 AUG 2025 PAGE 5/11

Information on the DHS Trusted Tester for Web Methodology Version 5.0, related test tools, test reporting, training, and tester certification requirements is published at https://www.dhs.gov/trusted-tester.

5. 1.2 Section 508 Deliverables (include in the SOW, PWS, or SOO)

1. Section 508 Test Plans: When developing or modifying ICT pursuant to this contract, the Contractor shall provide a detailed Section 508 Conformance Test Plan. The Test Plan shall describe the scope of components that will be tested, an explanation of the test process that will be used, when testing will be conducted during the project development life cycle, who will conduct the testing, how test results will be reported, and any key assumptions.

2. Section 508 Test Results: When developing or modifying ICT pursuant to this contract, the Contractor shall provide test results in accordance with the Section 508 Requirements for Technology Services provided in this solicitation.

3. Section 508 Accessibility Conformance Reports: For each ICT item offered through this contract (including commercially available products, and solutions consisting of ICT that are developed or modified pursuant to this contract), the Offeror shall provide an Accessibility Conformance Report (ACR) to document conformance claims against the applicable Section 508 standards. The ACR shall be based on the Voluntary Product Accessibility Template Version 2.0 508 (or successor versions). The template can be found at https://www.itic.org/policy/accessibility/vpat. Each ACR shall be completed by following all of the instructions provided in the template, including an explanation of the validation method used as a basis for the conformance claims in the report.

4.8 DHS-USCG ENTERPRISE ARCHITECTURE COMPLIANCE

All solutions and services shall meet DHS and USCG Enterprise Architecture policies, standards, and procedures. Specifically, the contractor shall comply with the following Homeland Security Enterprise Architecture (HLS EA) and USCG EA requirements:

• All developed solutions and requirements shall be compliant with the HLS and USCG EAs.

• All IT hardware and software shall be compliant with the HLS EA Technical Reference Model (TRM) Standards and Products Profile and with the USCG IT Products and Standards Inventory.

• Description information for all data assets, information exchanges and data standards, whether adopted or developed, shall be submitted to USCG Enterprise Architecture Division (EAD) and DHS Enterprise Architecture Division (EAD) for review, approval and insertion into the USCG and DHS Data Reference Model and Mobius.

• Development of data assets, information exchanges and data standards will comply with the DHS Data Management Policy MD 103-01 and all data-related artifacts will be developed and validated according to DHS data management architectural guidelines.

• Applicability of Internet Protocol Version 6 (IPv6) to DHS-related components (networks, infrastructure, and applications) specific to individual acquisitions shall be in accordance with the DHS Enterprise Architecture (per OMB Memorandum M-05-22, August 2, 2005) regardless of whether the acquisition is for modification, upgrade, or replacement. All EA-related component acquisitions shall be IPv6 compliant as defined in the U.S. Government Version 6 (USGv6) Profile (National Institute of Standards and https://www.dhs.gov/trusted-tester https://www.itic.org/policy/accessibility/vpat

LAST UPDATED: 07 AUG 2025 PAGE 6/11

Technology (NIST) Special Publication 500-267) and the corresponding declarations of conformance defined in the USGv6 Test Program.

4.9 SECURITY REVIEW

The Government may elect to conduct periodic reviews to ensure that the security requirements contained in the contract are being implemented and enforced. The Government, at its sole discretion, may obtain assistance from other Federal agencies and/or third-party firms to aid in security review activities. The Contractor shall afford DHS, the Office of the Inspector General, other government organizations, and Contractors working in support of the Government access to the Contractor’s facilities, installations, operations, documentation, databases, networks, systems, and personnel used in the performance of this contract. The Contractor shall, through the Contracting Officer and Contracting Officer's Representative (COR), contact the Component or Headquarters CIO, or designee, to coordinate and participate in review and inspection activity by government organizations external to DHS. Access shall be provided, to the extent necessary as determined by the Government (including providing all requested images), for the Government to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability, and confidentiality of government data or the function of computer systems used in performance of this contract and to preserve evidence of computer crime.

4.10 INTERCONNECTION SECURITY AGREEMENT (ISA)

Interconnections between DHS and non-DHS IT systems shall be established only through controlled interfaces and via approved service providers. Connections with other federal agencies shall be documented based on interagency agreements, memoranda of understanding, service level agreements or interconnect service agreements. The applicable network connectivity policy is located in the Access Control Section, for “Interconnection Security Agreements,” of the DHS 4300A, Attachment N.

4.11 REQUIRED PROTECTIONS FOR DHS SYSTEMS HOSTED IN NON-DHS DATA

CENTERS

Contractors are fully responsible and accountable for ensuring compliance with all Federal Information Security Management Act (FISMA), National Institute of Standards and Technology (NIST), Special Publication SP-800-47, DHS Management Directive 140-01, “Information Technology Security Program,” Revision 2, May 5, 2017, Federal Information Processing Standard (FIPS) and related DHS security control requirements (to include configuration guides, hardening guidance, DHS Security Policy, Procedures, and Architectural guidance). The contractor security procedures shall be the same or greater than those that are provided by DHS Enterprise Data Center(s). Please note that all the subsections from Security Authorization to Log Retention must be included in this requirement to comply with 4300A Information Security Systems Program 4300A version 13.4, December 6, 2024.

4.12 SECURITY AUTHORIZATION

A Security Authorization of any infrastructure directly in support of the DHS information system shall be performed as a general support system (GSS) prior to DHS occupancy to characterize the network, identify threats, identify vulnerabilities, analyze existing and planned security controls, determine likelihood of threat, analyze impact, determine risk, recommend controls, LAST UPDATED: 07 AUG 2025 PAGE 7/11 perform remediation on identified deficiencies, and document the results. The Security Authorization shall be performed in accordance with the DHS Security Policy and the controls provided by the hosting provider shall be equal to or stronger than the FIPS 199 security categorization of the DHS information system.

At the beginning of the contract, and annually thereafter, the contractor shall provide the results of an independent assessment and verification of security controls. The independent assessment and verification shall apply the same standards that DHS applies in the Security Authorization Process of its information systems. Any deficiencies noted during this assessment shall be provided to the COR for entry into the DHS’ Plan of Action and Milestone (POA&M) Management Process. The contractor shall use the DHS’ POA&M process to document planned remedial actions to address any deficiencies in information security policies, procedures, and practices, and the completion of those activities. Security deficiencies shall be corrected within the timeframes dictated by the DHS POA&M Management Process. Contractor procedures shall be subject to periodic, unannounced assessments by DHS officials. The physical aspects associated with contractor activities shall also be subject to such assessments.

The Government may elect to conduct periodic reviews to ensure that the security requirements contained in this contract are being implemented and enforced. The Government, at its sole discretion, may obtain assistance from other Federal agencies and/or third-party firms to aid in security review activities. Within ten working days’ notice, the Contractor shall afford DHS, the Office of the Inspector General, other government organizations, and Contractors working in support of the Government access to the Contractor’s facilities, installations, operations, documentation, databases, networks, systems, and personnel used in the performance of this contract. The Contractor shall, through the Contracting Officer and Contracting Officer’s Representative (COR), contact the Component or Headquarters Chief Information Officer, or designee, to coordinate and participate in the review and inspection activity of government organizations external to the DHS. Access shall be provided, to the extent necessary as determined by the Government (including providing all requested images), for the government to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of government data or the function of computer systems used in performance of this contract to preserve evidence of computer crime.

4.13 DHS SECURITY POLICY

All hardware, software, and services provided under this task order must be compliant with DHS Information Security System Program 4300A version 13.4, December 6, 2024.

Encryption Compliance Requirement

1. FIPS 197 (Advanced Encryption Standard (AES)) 256 algorithm and cryptographic modules that have been validated under FIPS 140-2 and / or FIPS 140-3.

2. National Security Agency (NSA) Type 2 or Type 1 encryption.

3. Public Key Infrastructure (PKI), key cards, biometrics, or in the case of multi-factor authentication, some combination therein (See Attachment U) Information Security Sensitive Systems Program Directive 4300A version 13.4, December 6, 2024.

LAST UPDATED: 07 AUG 2025 PAGE 8/11

4.14 ITAR SME CYBERSECURITY SUPPLY CHAIN RISK MANAGEMENT (C-

SCRM)

Cybersecurity C-SCRM language is applicable for requirements for the use of supplies and services to include the following:

a. Definitions:

i. Component: a unit defined by the supplier that connects to and functions as part of the product. For software products, a component is a unit of software defined by a supplier at the time the component is built, packaged, or delivered. For hardware, a component is one hardware unit designed to connect to and function as part of a larger product.

ii. End-of-Life (EOL): means that an ICT product has reached the final stage of the product life cycle in which that version of the ICT product will no longer be supported nor manufactured (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iii. End-of-Support (EOS): means that an ICT product will no longer be supported (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iv. Information and Communications Technology (ICT): encompasses the capture, storage, retrieval, processing, display, representation, presentation, organization, management, security, transfer, and interchange of data and information; includes all categories of ubiquitous technology used for the gathering, storing, transmitting, retrieving, or processing of information (e.g., microelectronics, printed circuit boards, computing systems, software, signal processors, mobile telephony, satellite communications, and networks).

v. Product: part of the equipment (hardware, software and materials) for which usability is to be specified or evaluated.

b. Original Equipment Manufacturer (OEM) End-use Information and Communications Technology (ICT) Product:

i. The contractor shall provide new equipment unless otherwise formally approved by the Government, in writing. The contractor shall provide only Original Manufacturer (OEM) end-use products to the Government. In the event that a shipped OEM product, or part or component of that product, fails, all replacements must be new (i.e., non-refurbished, not previously used) OEM.

ii. The contractor may provide previously used OEM products only with written Government approval. Such parts shall be procured from their original source and shipped only from the manufacturer's authorized shipment points.

c. Accounting of Components in ICT Products:

i. The contractor shall provide and maintain a list of components for each product used in performance of the contract, including through subcontracts or other arrangements. This list for each product shall provide the component manufacturer's name, address, state, and/or domain of registration, and, where applicable, the Unique Entity Identifier (UEI) number, for all components comprising the ICT products.

ii. The contractor shall notify the Government when a new contractor/subcontractor/service provider is introduced to the ICT provided on this contract, or when suppliers of components or products are changed. If a software component used in the performance of the contract is updated with a new build or release, the contractor must update the list provided in accordance with (i) above to reflect the new version of the software. This includes software builds to integrate an updated component or dependency.

LAST UPDATED: 07 AUG 2025 PAGE 9/11

iii. For software products, the contractor shall provide all OEM software updates, and patches to correct defects, for the life of the product [i.e., until the "End of Life" (EoL) or "End of Support" (EoS)]. Software updates and patches shall be made available to the government for all products procured under this Contract and replaced when End of Support (EoS) is reached.

iv. A contractor using team members in performance of the contract (e.g., subcontractors or other service providers) shall ensure that the standards for the accounting of components in this subsection are met by team members.

d. Supply-Chain Transport:

i. The contractor shall use formal, documented, and accountable transit, storage, and delivery procedures (i.e., the possession of the end-use product to be delivered is documented at all times from initial shipping point to final destination, and every transfer of the product from one custodian to another is fully documented and accountable) for all information and communication technology (ICT) shipments to fulfill this contract.

ii. The contractor shall maintain all records pertaining to the transit, storage, and delivery of ICT deliverables under this contract through at least 6 months after acceptance and make available for inspection upon request of the Government.

iii. The contractor shall make use of tamper-proof or tamper-evident packaging for all shipments.

iv. The contractor shall provide a packing slip for each container or package with the information identifying the contract or order number, a description of the hardware/software enclosed (Manufacturer name, model number, serial number), and the customer point of contact.

v. The contractor shall provide a shipping notification to the intended government recipient;

with a copy transmitted to the Contracting Officer, or other designated representative. This shipping notification shall be provided electronically and identify the contract or order number, a description of the hardware/software being shipped (manufacturer name, model number, serial number), initial shipper, shipping date and identifying (tracking) number.

e. Changes to Ownership and Control:

The Contractor shall immediately notify the Contracting Officer and Contracting Officer's Representative regarding any significant changes to corporate ownership or control from contract award through final delivery or the end of the period of performance. A significant change would be one in which a change occurs in the individuals or entities who, directly or indirectly, either (1) exercises substantial control over an entity, or (2) owns or controls at least 25 percent of the ownership interests of an entity.

5.0 GOVERNMENT FURNISHED RESOURCES

The Government will not furnish any resources to the Contractor in support of this contract.

6.0 CONTRACTOR FURNISHED PROPERTY

The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract.

7.0 GOVERNMENT ACCEPTANCE PERIOD

LAST UPDATED: 07 AUG 2025 PAGE 10/11

The COR will review deliverables prior to acceptance and provide the contractor with an e-mail that provides documented reasons for non-acceptance. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying it that the deliverable has been accepted.

7.1 The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions.

7.2 The COR will have 10 business days to review deliverables and make comments. The Contractor shall have 10 business days to make corrections and redeliver.

8.0 DELIVERABLES

The Contractor shall consider items in BOLD as having mandatory due dates. Items in italics are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or event in this PWS.

ITEM PWS

REFERENCE DELIVERABLE / EVENT DUE BY

DISTRIBUTION

1 4.4 Progress Reports (A001) 10th of each month

COR, Contracting Officer, PL PM

9.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS).

The PRS establishes key elements of Contractor performance that represent “mission essential” service requirements, which are identified in the table below in the “Service Output” column.

The “Performance Objective” column represents the standard against which Contractor performance will be measured in relation to accomplishment of the corresponding service output. The performance objective or “standard” describes the minimum acceptable level of service by the Contractor for satisfactory performance. The “Acceptable Quality Level (AQL)” column displays the maximum allowable deviation from the performance objective, which, if exceeded, evokes the negative incentive specified in the table below.

Service Output Performance Objective Acceptabl e Quality

Level

(AQL)

Positive Incentive

Negative incentive

LAST UPDATED: 07 AUG 2025 PAGE 11/11

Service Output Performance Objective Acceptabl e Quality

Level

(AQL)

Positive Incentive

Negative incentive

1. EDS Data Service Refinements

(PWS 2.1)

The contractor must deliver the data enhancements listed in section 2.1

+/- 99% Positive CPARS entry

Negative CPARS entry

2. The contractor must develop and deliver Operator Guidance documentation for each item in

2.1.(PWS 2.2.1)

The contractor must develop and deliver to USCG Operator Guidance documentation for each item listed in PWS 2.1

+/- 99% Positive CPARS entry

Negative CPARS entry

10. ATTACHMENTS and APPENDICIES

10.1 Attachment - CDRL A001 – Progress Reports

10.2 Attachment - Appendix A – EDS Current Guide

10.3 Attachment - Appendix B – EDS Wind Guide

10.4 Attachment - Appendix C – Web Service Details

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

A X

SAROPS

A001 Monthly Progress Report

See block 16 PWS Section 4.4 U.S. Coast Guard, C5ISC

No

N/A No

Monthly

Monthly

Block 16

Block 16

COR 1

KO 1

KS 1

OISPL PM 1

0 4 0

Block 4: The Project Manager must provide a monthly progress report to the Contracting Officer and COR via electronic mail in the contractor’s format. This report must include a summary of all Contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any Contractor concerns or recommendations for the previous reporting period.

Blocks 12&13: Due by the 10th of each month for the previous month's progress

Adobe Professional 7.0

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

A X

SAROPS

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoD 5010.12-M for detailed instructions.)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

Item I. Signature of CDRL approval authority.

Item J. Date CDRL was approved.

Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.

Item 2. Enter title as it appears on data acquisition document cited in Item 4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.

DD FORM 1423-1 (BACK), FEB 2001

APPENDIX A

Environmental Data System (EDS)

(Currents)

(Updated 21 November 2024)

Highlights and Notes

This is an overview of the surface current products and data available in the Environmental Data System (EDS version 2.0) as of 15 August 2018. Below are relevant highlights and notes on EDS and its products.

The products listed here are available to USCG users of SAROPS. The products are listed by order of preference from highest to lowest in the flow charts for that particular end point. However, the primary choice, if available, should always be evaluated. The EDS choice should first be evaluated for coverage of the AOI in time and space; then for coverage in the immediate area of the scenario(s). And then finally the EDS choice should be evaluated against data sources, the secondary choices, on scene reports and local or expert knowledge. If the primary choice does not satisfy the above evaluations; secondary and tertiary sources should be considered and evaluated for use. Many of the EDS sources are equivalent or nearly equivalent, so consideration and use of secondary and tertiary sources is encouraged. Data sources of winds (NDBC buoys) and currents (SLDMBs and HF radar data) are listed last.

Global HYCOM (Navy) currents are forced with winds from Navy’s NAVGEM, and therefore pair NAVGEM winds with Global HYCOM (Navy) currents.

Global HYCOM (NCEP) currents are forced with winds from NCEP’s GFS, and therefore pair GFS winds with Global HYCOM (NCEP) currents.

The European Copernicus currents are forced with winds from ECMWF atmospheric numerical prediction model, and therefore pair ECMWF winds with Copernicus currents.

The Australian Bluelink currents (BLUELINK_V3_C) are forced with winds from ACCESS G3 (ACCESS_G3_W) atmospheric numerical prediction model, and therefore pair ACCESS G3 winds with Bluelink currents.

No_GoMex_FVCOM_NOS2_C currents are forces with winds from NOS No_GoMex_NOS2_W model, and therefore No_GoMex_FVCOM_NOS2_C currents should be paired with No_GoMex_NOS2_W winds.

Names now contain the product, (source) and if necessary the type or short descriptor and ends with ‘_C’ to indicate that it’s a surface current product. After a current product is downloaded, the DTG of the download request is also appended to specific file name. Thus the current file name in the TOC or cached products will have the format: ‘name_descriptor_(source)_C: DTG’.

The FVCOM models are identified by the descriptor ‘_FVCOM_’ in their name tag. CAUTION: these models are very high resolution and therefore can generate excessive download and run times. Limit the AOI to only what is needed for the simulation

The vertical extent of the surface layer is now reported in the Tables 1-4. There is wide variation among the oceanographic models and even within the models on the thickness of the surface layer that is reported to the EDS/SAROPS. Surface currents are influenced from below by deep currents (e.g. tidal currents, mean, seasonal, and several day (i.e. geostrophic) currents) and from above by the local winds. The thinner the surface layer modeled, the quicker and faster that modeled layer will respond to its local modeled winds; and vice versa, thicker layers mean slower response and slower currents. Since the operational definition of leeway relates the motion of the SAR object to the upper 1.0 meter of the ocean and SLDMBs are drogued at between 0.3 and 1.0 meters depth, the closer the model’s surface layer is to 1.0 meter the closer it can be expected to represent the surface layer as defined in SAROPS’s equations and tracked by the SLDMBs.

The confidence parameters used to determine the dispersion or spread of the particles due to uncertainty in the current vectors are now provided for each EDS current product and are provided in the background to SAROPS Simulator. Also provided is the internal Time Step within the SAROPS Simulator. High resolution models require a shorter Time Step to prevent particles from skipping over grid cells during a single Time Step. Caution: this may result in longer Simulator run times.

The Skill of each model at predicting the drift of SLDMBs has now been measured. For each model, SLDMB tracks, at 6-hour intervals, are compared to simulated tracks from the models where model and SLDMB data were available and co-located. These SLDMB - model comparisons and skill scores are available to CG SME.

The Doppio_Rutgers_C EDS product has been added as of 15 August 2018

The Espresso_Rutgers_C EDS product has been dropped as of 15 August 2018

The CA_3km_UCLA_C was discontinued in October 2022 and replaced by WCOFS

The Currents Sketch Tool has been removed in SAROPS 2.0; so this guidance reflects that change here and in the flow charts. Selection of SLDMB in the EDS menu is meant to replace the Sketch Tool for use of SLDMB data.

If SLDMB data is not available, then Manual Input of currents in the EDS Current GUI is the last remaining option for surface currents.

If no data on currents is available for Manual Input; then use zero speed, 090 direction as inputs. This will result in SAROPS using only leeway to compute particle drift trajectories.

Inquiries: Dr. Cristina Forbes (Oceanographer for CG-SAR-1)

The objective is to SELECT the most appropriate EDS current source.

Job Aids

East Coast D1 East Coast D5 East Coast D7 Gulf of Mexico D8 Great Lakes D9 West Coast D11 West Coast D13 West Coast D14 West Coast D17

Table 1.

EDS SURFACE CURRENTS PRODUCTS

(Real-time Data-assimilating Numerical Models)

EDS LISTING

PRODUCT

OWNER COVERAGE

DATA CELL

HORIZONT

AL SIZE

(Horizontal Resolution)

SURFACE CELL

VERTICAL SIZE

FORECAST

FREQUEN

CY

(Temporal Resolution)

FORECAS

T

LENGTH

MODEL

RUN

Global_ HYCOM_ NCEP_C*1 NCEP *2 Global 8 km 0.17 - 1.0 m Hourly 144 Hrs Daily Global_ HYCOM_ Navy_C *3 Navy Global 8 km 0.17 - 1.0 m Every 3 Hrs 144 Hrs Daily

AGG_ADCIRC_GHycom_C*4

NCEP &

ADCIRC

Developme nt Group

Global/ Regional

3-14 km 0.17 - 1.0 m Every 3 Hrs 72/84 Hrs Daily

BLUELINK_V3_C

BoM*17

GLOBAL

[-75 to 75°]N, [-180 to 180]°E

0.1°x 0.1° (~10km x 10km)

2.5m

Every 3 Hrs

168 hours (7 days)

Daily

CARICOOS_C CARICOOS

*24

Puerto Rico & Virgin Islands [16.5°N - 20°N, 68.5°W - 63.5°W]

0.081 - 3 km 5 m Hourly 72 hours Daily

ChesBay_NOS_C DelBay_NOS_C

NOS

Chesapeake/ Delaware

Bay

0.1 - 3 km

0.1 - 2.75 m

0.2 - 13.0 m

Hourly 48 Hrs 4 Times Daily

Cook_Inlet_NOS_C NOS*5 Cook Inlet 50 m- 8 km 0.04 – 1.15 m Every 6 Hrs 48 Hours 4 Times Daily

COPERNICUS_GLOBAL_C CMEMS

Global

[-90° to 90°Lon -180° to 180°]

0.83°x0.83° (9kmx9km)

0.5 m Hourly 10 days Daily

Doppio_Rutgers_C Rutgers

Univ Nova Scotia to Cape

Hatteras 7 km 0.12 - 6.2 m 3 Hourly 60 Hrs Daily

GIOPS_C ECCC*25 Global

0.25° Equator: 27 km, Artic

Ocen 12 km

1 m Every 3 Hrs 10 days Daily

Guam_UHI_C U

Hawaii*14 Guam and Northern

Mariana Islands 2 km 1 m Every 3 Hrs 6 Days Daily

Hawaii_UHI_C U

Hawaii*14 Main Hawaiian Islands 4 km 1 m Every 3 Hrs 24 Hrs Daily

Kaneohe_UHI_C U Oahu - Kaneohe 100 m 0-1 m Hourly 3 Days Daily

Hawaii*14 L_Champlain_GLERL_C GLERL*6 Lake Champlain 50-400 m 0.5 cm – 6 m Hourly 120 hours Daily

L_Ontario_NOS_FVCOM_C NOS*5 Regional

(Great Lakes)

0.2 – 2.5 km 0.0125 – 5.69 m Hourly 120 Hrs 4 Times Daily

L_Superior_NOS_FVCOM_C NOS*5 Regional

(Great Lakes)

0.2 – 2.5 km 0.0125- 9.49 m Hourly 120 Hrs 4 Times Daily

L_Erie_NOS_FVCOM_C NOS*5 Lake Erie 0.03 - 2 km 0.0125 -1.57 m Hourly 120 Hrs 4 Times Daily

L_MichHuron_NOS_FVCOM_C NOS*5 Lakes Michigan &

Huron 0.05-2.5 km 0.0125 - 6.79 m Hourly 120 Hrs 4 Times Daily

L_Erie_GLERL_FVCOM_C L_MichHuron_GLERL_FVCOM _C

L_Ontario_GLERL_FVCOM _C L_Superior_GLERL_FVCOM _C

GLERL*6

Regional

(Great Lakes)

0.03 – 2 km

Erie: 0.0125 -1.57 m Michigan-Huron: 0.0125

- 6.79 m Ontario: 0.0125 - 5.69 m Superior: 0.0025 - 9.49 m

Hourly

72 Hrs (ice season)

120 Hrs (no ice season) finishing at

5:20 and

17:20 GMT

2 Times Daily

LIS_FVCOM_C UCONN*16 Long Island Sound 500 m in the sound

0.7 - 9.0 m Hourly 72 Hrs Daily

Maine_FVCOM_UMass_C UMass

Dartmouth DelMar to NE Nova

Scotia .2 - 20 km 0.5 - 5.0 m Hourly 48 Hrs Daily

MassBay_FVCOM_UMass_C UMass

Dartmouth*

Portsmouth, NH to Buzzards Bay

0.050 - 1 km 0.01 - 2.0 m Hourly 48 Hrs Daily

NCOM_AmSeas_C Navy Gulf of Mexico and Caribbean

[94°W-54°W, 5°N-33°N]

3.108-3.692 km

(1/30°)

1 m Every 3 Hrs

96 Hrs Daily

NCOM_Alaska_C Navy Alaska [170°W-119°W, 36°N-63°N]

1.683-2.998 km (1/30°)

NCOM_Hawaii_C Navy Hawaiian Islands [166°W-151°W, 15°N-30°N]

3.210-3.580 km

NCOM_SoCal_C Navy Southern California [125°W-110°W, 25°N-41°N]

2.797-3.359 km

NCOM_USec_C Navy US East Coast [82°W-63°W, 20°N-43°N]

2.710-3.483 km

No_GoMex_FVCOM_NOS2_C NOS*5 Mexico Border to

Panama City

0.045 - 10 km 0.5 - 5 m Every 3 Hrs 48 Hrs 4 Times Daily

NY_Hrbr_NOS_C

NOS*5

NY/NJ harbor

0.05 - 1 km 0.0 - 3.5 m Hourly 36 Hrs 4 Times Daily

Oahu_UHI_C U

Oahu 1 km 0-1 m Every 3 Hrs 7 Days Daily

Oahu_SouthShore_UHI_C U

Hawaii*14 Oahu 200 m 0-1 m Every 3 Hrs 3 Days Daily

RIOPS_C CCMEP*21 N. Atlantic & Pacific Oceans from Bering

Strait in Arctic Ocean to 44° N in the Pacific

& 26°N in Atlantic Oceans

3 km - 8 km (1/12°)

1 m Hourly 84 Hours 4 Times Daily

Samoa_UHI_C U

Hawaii*14 Islands of Samoa 3 km 1 m Every 3 Hrs 7 Days Daily

SalishSea_ColumbiaR_NOS_C*5 NOS Salish Sea, Columbia

River

Puget Sound:

100-500m Columbia

River: 100- 200m

Continental Shelf 10 km

72 hrs 4 Times Daily

SanFran_NOS_C NOS San Fran Bay 0.1 - 4 km 0.1 - 5.0 km Hourly 36 Hrs 4 Times Daily

StClair_FVCOM_GLERL_C*7

GLERL

Lake St Clair, St

Clair/Detroit Rivers .020 - 0.40 km

0.3 - 2.9 m Hourly 48 Hrs Daily

StJohnRiver_NOS_C NOS St. John River, FL 0.05 - 1 km 0.0 - 3.25 m Hourly 36 Hrs 4 Times Daily

STOFS_ATL_C NOAA

Western Atlantic W of

60W 2.5-6 km 0 m Hourly 96 hours

Daily (at 12

UTC)

STPS_MidAtl_ UConn_C

MARACO

OS/UCON

N*15

Coastal Cape Cod to Cape Hatteras

6 km 2.3 m

3 hourly averages updated every hour

From time of HF radar data to +24

HRS

Hourly

STPS_West_UConn_C UCONN*16 California, Oregon coasts 6 km 2.3 m

3 hourly averages updated every hour

From time of HF radar data to +24

Hrs

Hourly

TAMU_TX_LA_C TAMU*22 Texas and Lousiana 0.650-3.7 km 0.1 ~ 1m Hourly 96 hours Daily TWDB_CCI_C TWDB*23 Corpus Christi, Texas 0.053-

2.232km Local total depth Every 3 Hrs

522 Hours Daily

TWDB_CSA_C TWDB*23 San Antonio, Aransas and Copano Bays

0.060-2.518 km

TWDB_GAL_C TWDB*23 Galveston Bay, Texas 0.221-5.304

TWDB_MAG_C TWDB*23 Matagorda, Texas 0.137-2.398

TWDB_SAB_C TWDB*23 Sabine Lake, Texas/Lousiana Border

0.049-2.262

Waikiki_UHI_C U

Oahu 200 m 0-1 m Hourly 3 Days Daily

WCOFS_NOS_C

NOAA-CO-

OPS*19

US West Coast

[18.44°N -56.48°N] 4 km 0-2m Hourly 3 Days Daily

WFCOM_USF_C USF-OCL

Gulf of Mexico:

Louisiana, Mississippi, Alabama, FL West Coast and FL Keys

50-10000 m 0-4 m Hourly 3.5 Days Daily

WPAC_UHI_C

U

Hawaii*14

West Pacific 116 E - 148 E

2N - 27 N 8 km 1 m Every 3 Hrs 6 Days Daily

TampaBay_NOS_C NOS*5 Tampa Bay 0.1 - 1.2 km 0.2 - 2.8 m Hourly 48 Hrs 4 Times Daily

*1) Hybrid Coordinates Ocean Model (RTOFS - Real-time Operational Forecast System (Atlantic))

*2) National Centers for Environmental Prediction (NOAA - National Oceanic and Atmospheric Administration)

*3) Hybrid Coordinates Ocean Model

*4) Advanced Circulation Model

*5) National Ocean…