Attachment 1 - AMVER Data Services SOW.pdf
PDF 161 KB Posted
- Attached to
- AMVER Consolidated Vessel Data
- Solicitation number
- 70Z0G326QAMVER001
About this file
This is a Statement of Work (SOW) for AMVER Subscription Data Services provided to the U.S. Coast Guard Command, Control, Communications, Computers, Cyber, and Intelligence Service Center (C5ISC) located in Kearneysville, West Virginia.
The contractor shall provide biweekly updates of ship characteristic data, including owner information and pre-maiden voyage data, to the Automated Mutual Vessel Rescue (AMVER) system via secure FTP server. The contractor must notify the AMVER Technical team via email when data is available for download into the AMVER database to support search and rescue missions. Additionally, the contractor must provide ten (10) user licenses for Coast Guard personnel to access data via FTP and five (5) user licenses to access the contractor's maritime data and tracking platform. The contract includes a 12-month base period with four optional 12-month renewal periods, for a total potential five-year performance period. No onsite personnel are required; this is a data delivery service only. The contractor must furnish all software upgrades, licenses, investment protection support services, and necessary equipment. Initial data and licenses must be delivered upon contract award, with subsequent deliverables as specified in the final contract.
The contractor must comply with security and CUI (Controlled Unclassified Information) protection requirements under DHS MD 11042.1, DHS MD 4300.1, and the DHS Sensitive Systems Handbook. All hardware and software interfaces must meet FIPS 140-2 and FIPS 197 (AES-256) encryption compliance. Solutions and services must comply with DHS and USCG Enterprise Architecture policies, standards, and the HLS EA Technical Reference Model. The contractor must provide Section 508 Accessibility Conformance Reports for each ICT item offered and comply with geospatial data standards under the Geospatial Data Act of 2018, including FGDC-endorsed standards and metadata requirements. The Contracting Officer's Representative (COR) will review deliverables within mutually agreed business days and provide acceptance notification or non-acceptance explanations via email. The Information System Security Officer contact is Mr. John Denny at John.J.Denny@uscg.mil.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFQ 70Z0G326QAMVER001 - AMEND 1 KO.pdf | ||
| RFQ Letter_70Z0G326QAMVER0001 SAM.gov.pdf | ||
| Attachment 4 - AMVER Price Matrix.xlsx | XLSX spreadsheet | |
| Attachment 2-TABLES-COLUMNS.pdf | ||
| Attachment 3-DHS_form_11000-6.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment 1
LAST UPDATED: 11/21/2025 PAGE 1/4
STATEMENT OF WORK (SOW)
FOR
AMVER SUBSCRIPTION DATA SERVICES FOR THE U.S. COAST GUARD
Command, Control, Communications, Computers, Cyber, and Intelligence Service
Center (C5ISC)
1.0 GENERAL
Background In the performance of this contract, the contractor shall provide data files with Ship Characteristic data to include owner information and “pre-maiden” voyage data to the Automated Mutual Vessel Rescue (AMVER) system. The contractor must upload the data files included in the Tables and Columns file onto the contractor’s FTP Server every two weeks. The US Coast Guard Command, Control, Communications, Computer, Cyber and Intelligence Service Center located in Kearneysville, WV will download the data files via secure file transport protocol (FTP) into the AMVER database.
1.2 Scope
The contractor must provide the required data every two weeks and will notify the AMVER Technical team when it is available via email. Using manual intervention by the AMVER Team, the data is downloaded into the AMVER system to support search and rescue missions.
Additionally, the Government will also need to purchase ten (10) user licenses to share the data and five (5) user licenses to access the contractor’s maritime data and tracking platform. This contract includes a Base Period of 12 months and four (4) 12-months Option Periods, for a total of five (5) years, if all options are exercised.
2.0 SPECIFIC REQUIREMENTS/TASKS
The Contractor must provide software licenses and vessel data as outlined below and must perform updates for the term of the license.
2.1 Task One: AMVER Data Delivery
• Provide updates on all the data described in the Tables and Columns file every two weeks and send the AMVER Team confirmation via email, when data is available.
2.2 Task Two: User Licenses
• Provide ten (10) user licenses for the CG users to access the data via FTP.
• Provide five (5) user licenses to the contractor’s maritime data and tracking platform.
3.0 CONTRACTOR PERSONNEL
3.1 Qualified Personnel
This contract is for the delivery of data only and no onsite personnel are required to support associated tasks.
4.0 OTHER APPLICABLE CONDITIONS
4.1 Security and Protection of Information Access to Classified Information:
LAST UPDATED: 11/21/2025 PAGE 2/4
No access to classified information is required. Contractor access to Controlled Unclassified Information (CUI) is required under this SOW. Contractor employees must safeguard CUI against unauthorized disclosure or dissemination in accordance with law, policy, and regulation.
Contractors must comply with DHS MD 11042.1, DHS MD 4300.1, and the DHS Sensitive Systems Handbook, and must not use or redistribute DHS information except as specified in this SOW. Information System Security Officer (ISSO) Contact: Mr. John Denny John.J.Denny@uscg.mil
Encryption Compliance: All hardware and software interfaces used in performance must meet FIPS 140-2 and FIPS 197 (AES-256) compliance.
Interconnection Security Agreements: Interconnections between DHS and non-DHS IT systems must be established only through controlled interfaces and via approved service providers, and documented as required.
Remote Access Contractor access to DHS networks from a remote location is a temporary privilege for mutual convenience while the Contractor performs business for the DHS Component. Access may be terminated for unauthorized use. The Contractor agrees to hold and save DHS harmless from any unauthorized use and agrees not to request additional time or money under the ID/IQ Contract for any delays resulting from unauthorized use or access.
4.2 Period of Performance
The period of performance is one base year and 4 option years.
4.3 Section 508 Compliance and Deliverables
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.
Section 508 Requirements for Technology Products
Section 508 applicability to Information and Communications Technology (ICT): AMVER Subscription Data Services Applicable Exception: N/A Authorization #: N/A Applicable Functional Performance Criteria: Does not apply 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: 11/21/2025 PAGE 3/4
Applicable 508 requirements for electronic content features and components (including but not limited to Electronic reports): Does not apply Applicable 508 requirements for software features and components: Does not apply Applicable 508 requirements for hardware features and components: Does not apply Applicable 508 requirements for support services and documentation: All requirements in Chapter 6 apply
Section 508 Deliverables
1. 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.4 Geospatial Compliance In accordance with the Geospatial Data Act of 2018, vendors must:
• Ensure geospatial data complies with FGDC-endorsed standards and DHS Geospatial Management Office policies and best practices for metadata, records retention, and privacy.
• Ensure interoperability of geospatial data and allocate resources for effective data management.
• Support DHS in reducing duplicative data acquisition, as appropriate, by searching available data from DHS enterprise partners and public sources.
• Ensure that geospatial data is made available to the public, as appropriate.
4.5 DHS-USCG Enterprise Architecture Compliance All solutions and services must comply with DHS and USCG Enterprise Architecture policies, standards, and procedures:
• Solutions and requirements must be compliant with the HLS and USCG Enterprise Architectures.
• IT hardware and software must 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 data assets, information exchanges, and data standards must be submitted to USCG EAD and DHS EAD for review, approval, and insertion into the USCG and DHS Data Reference Models.
• Development of data assets, information exchanges, and data standards must comply with DHS Data Management Policy MD 103-01 and applicable data management architectural guidelines.
• Applicability of IPv6 must be in accordance with the DHS Enterprise Architecture and USGv6 Profile, including declarations of conformance defined in the USGv6 Test Program.
5.0 GOVERNMENT FURNISHED RESOURCES
https://www.itic.org/policy/accessibility/vpat
LAST UPDATED: 11/21/2025 PAGE 4/4
The Government will not furnish any facilities, property, equipment, supplies, services, information, data, or documents to the Contractor for this requirement unless otherwise stated in individual contracts/orders.
6.0 CONTRACTOR FURNISHED PROPERTY
The Contractor must furnish all software upgrades, licenses, Investment Protection (IP) support services, and other material and equipment necessary to perform this contract.
7.0 GOVERNMENT ACCEPTANCE PERIOD
The COR will review deliverables prior to acceptance and provide the Contractor with an e-mail explaining any reasons for non-acceptance. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying that the deliverable has been accepted.
• The COR will have mutually agreed business days to review deliverables and make comments per contract.
• The Contractor must make corrections and redeliver within mutually agreed business days.
• Review times and schedules for deliverables must be agreed upon by the parties based on the final approved project or task plan.
8.0 DELIVERABLES
SOW Reference Deliverable/Event Due By Distribution
2.1 Task One: AMVER
Data Delivery
As specified in contract; initial data delivered upon award
ESD-APP, COR,
Contracting Officer
2.2 Task Two: User
Licenses
As specified in contract; initial licenses upon award
ESD-APP, COR,
Contracting Officer
File details come from the government source that posted it. Updated .