Attachment 1 - GMIXVIS_SOW.pdf

Attachment 1: Statement of Work 70Z0G324QOIPL0006 Description: Data Feed for Vessel

Identification System Page 1 of 7

Last Updated: 5 August 2024 Page 1/7

STATEMENT OF WORK (SOW)

FOR

Vessel Information System (VIS)

1.0 GENERAL

1.1 BACKGROUND

Per Congressional legislation, the U.S. Coast Guard was given the task to develop and maintain a Vessel Identification System (VIS) in order to share state vessel registration and federal vessel documentation information with local, state and federal law enforcement officials and state vessel registration and titling authorities. In 1988, Congress passed legislation that required the United States Coast Guard to develop a vessel identification system (VIS) to acquire and share individual states’ vessel information as well as information on federally documented vessels. With the implementation of VIS, the Coast Guard, state law enforcement officials, and state registration and titling officials, could more effectively identify information on vessels in our nation’s ports and waterways and to fill a major Marine Awareness gap. Most large commercial vessels and many large recreational vessels obtain federal documentation.

Smaller vessels are registered only in the state where they are principally operated. VIS would allow the Coast Guard, local law enforcement officials, and registration and titling agencies to identify critical information more effectively and efficiently for CG Documented vessels and participating States’ and Territories numbered vessels; information including the owner’s name, vessel identification, and any prior law enforcement activities associated with the vessel. Other information was to include information on any liens associated with the vessel, and information to assist law enforcement officials, such as the date a vessel was stolen or abandoned.

The entire set of regulations for vessel titling and VIS participation can be found at:

Code of Federal Regulations - State Vessel Titling Systems (https://www.ecfr.gov/current/title- 33/chapter-I/subchapter-S/part-187/subpart-D)

The Coast Guard’s early efforts to acquire VIS were unsuccessful. Several attempts were made to create an in-house solution. In 2002 the General Accounting Office did a review of the VIS project and recommended that the Coast Guard consider working with a commercial vendor.

The Coast Guard solicited bids to acquire the states’ data. For additional information on the GAO report, visit Coast Guard: Vessel Identification System Development Needs to Be Reassessed | U.S. GAO (https://www.gao.gov/products/gao-02-477) Receipt of the data provides a single database to look for ownership information even if the state of registration is unknown. State registration and titling personnel will have access to VIS and VIS data will be available to authorized law enforcement personnel from participating States.

VIS has been a fully functional, stable and highly available system since it was fully implemented in September 2007.

1.2 SCOPE

VIS contains vessel descriptive information and ownership data for CG Documented vessels and participating States’ and Territories numbered vessels. A list of participating States and Territories is provided in Section 2.

https://www.ecfr.gov/current/title-33/chapter-I/subchapter-S/part-187/subpart-D https://www.gao.gov/products/gao-02-477 https://www.gao.gov/products/gao-02-477 https://uscg.sharepoint-mil.us/sites/VesselInformationSystemVIS/Shared%20Documents/SCOPE%20PARAGRAPHS.doc

Identification System Page 2 of 7

Last Updated: 5 August 2024 Page 2/7

Section 101 of H.R. 3105, as amended, adds a new chapter 125 to title 46, United States Code, to establish a vessel identification system for all vessels of the United States. This would include vessels documented under chapter 121 of title 46, numbered under chapter 123 of that title, or titled under the law of a State. The specifics required for VIS are documented in: 46 U.S. Code Chapter 125 - Vessel Identification System (https://www.law.cornell.edu/uscode/text/46/subtitle- II/part-H/chapter-125). Vendor must have a firm understanding of the complete content of this publication.

The current web site with VIS information can be found at: Coast Guard VIS Web Site (https://cgmix.uscg.mil/VISInformation.aspx?VISOption=)

1.3 OBJECTIVE

The primary purpose of this system is to serve as a centralized source of vessel registration and ownership information from participating States and the USCG National Vessel Documentation Center that can be accessed for search and rescue and various law enforcement purposes ranging from homeland security to serving as a means to help deter vessel theft, particularly where vessels are crossing state lines.

1.4 APPLICABLE DOCUMENTS

1.4.1 Compliance Documents

The following document provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract: Applicable 508 Compliance Statements (Section 4.4)

2.0 Data Feed Requirements

1. The requirements for Must Be and May Be data collected data items from the state are found in in 33CFR187. This must be utilized as a primary reference for data feed requirements.

2. Each week a file will be delivered via secure file transfer protocol (FTP) and will include updated vessel registration data from every state that has formally agreed to participate in VIS and is able to provide updated data.

3. Each week’s file will include data from different states as data is available.

4. If data errors or omissions are noted in the file submitted by the states, the vendor shall contact the Contracting Officer Representative (COR) or the USCG CG-68 Business Relationship Manager assigned to VIS within one (1) working day.

5. If states go offline periodically, every effort will be made to get the states back online without compromising the data already in VIS.

6. When sending data, each states’ data must have the two-digit state abbreviation.

7. The data shall be sent in the following format with attributes as noted:

Data Element Name Reg_ID] [int] IDENTITY(1,1) NOT NULL, [Reg_State] [char](2) NOT NULL, [Reg_Num] [varchar](15) NOT NULL, [Reg_Standard] [varchar](15) NULL, [Hull_ID] [varchar](20) NULL, [Make] [varchar](25) NULL, https://www.law.cornell.edu/uscode/text/46/subtitle-II/part-H/chapter-125 https://www.law.cornell.edu/uscode/text/46/subtitle-II/part-H/chapter-125 https://cgmix.uscg.mil/VISInformation.aspx?VISOption=

Identification System Page 3 of 7

Last Updated: 5 August 2024 Page 3/7

[Model_Year] [int] NULL, [Length_IN] [int] NULL, [Drive_Type] [varchar](20) NULL, [Hull_Type] [char](1) NULL, [Fuel_Type] [varchar](1) NULL, [Sboat_Type] [varchar](20) NULL, [Use_Type] [varchar](1) NULL, [Boat_Name] [varchar](20) NULL, [Reg_Date] [datetime] NULL, [Title_Date] [datetime] NULL, [Title_Num] [varchar](20) NULL, [Expired] [bit] NULL, [CG_Num] [varchar](15) NULL, [Last_Updated] [datetime] NULL, [Orig_Hull_ID] [varchar](15) NULL, [Orig_Make] [varchar](25) NULL, [Orig_Model] [varchar](25) NULL, [Orig_Year] [smallint] NULL, [Orig_Prop] [varchar](20) NULL, [Orig_Hull_Type] [char](20) NULL, [Stol_Date] [datetime] NULL, [Recov_Date] [datetime] NULL, [Lien_Holder] [varchar](75) NULL, [Lien_Date] [datetime] NULL, [Full_Name] [varchar](50) NULL, [First_Name] [varchar](25) NULL, [Last_Name] [varchar](35) NULL, [Address] [varchar](35) NULL, [City] [varchar](30) NULL, [State] [char](2) NULL, [Zip] [char](5) NULL, [Zip4] [char](4) NULL, [County] [varchar](50) NULL, [Reg_County] [varchar](50) NULL, [Phone] [varchar](15) NULL, [DOB] [datetime] NULL, [Orig_Name] [varchar](75) NULL, [Orig_Address] [varchar](50) NULL, [Reg_Name2] [varchar](75) NULL, [Reg_Name3] [varchar](75) NULL, [Engine_Mak] [varchar](20) NULL, [Engine_Ser] [varchar](20) NULL, [Engine_Yea] [int] NULL, [HP] [int] NULL, [SSN] [varbinary](128) NULL, [DL_NUM] [varchar](50) NULL, [PIN] [varchar](50) NULL, [Party_Type] [char](1) NULL, [SecondaryAddress] [varchar](35) NULL, Identification System Page 4 of 7

Last Updated: 5 August 2024 Page 4/7

[SecondaryCity] [varchar](30) NULL, [SecondaryState] [char](2) NULL, [Secondaryzip] [char](5) NULL, [Secondaryzip4] [char](4) NULL, [Prop_Type] [varchar](20) NULL, [Last_Mod_Individual] [varchar](50) NULL, [Last_Mod_DtTm] [datetime] NULL, [CODStatus] [varchar](30) NULL, [CODExpire] [datetime] NULL, [DuplicateHullID] [bit] NOT NULL, [Deleted_Ind] [bit] NOT NULL, [Deleted_DtTm] [datetime] NULL

Participating States Given that the VIS is dependent upon the voluntary participation of the States as according to statute, the Coast Guard developed a Memorandum of Agreements (MOA) for the States and the Coast Guard to sign to assure the States’ participation, to direct details of their participation, to provide participating States with access to the VIS data, and to protect the required privacy of the States’ data. The MOAs further explain that the state agrees that they are providing their data to the Coast Guard, and to a vendor who provides the data to the Coast Guard.

If a State is considered a Titling State, there is a requirement that all the data listed previously must be provided. The vendor must track this moving forward and update their provided data files accordingly.

An MOA is required between the vendor and each State to acquire the data that will be sent to the Coast Guard. As part of the MOAs, the data feed between the States and the vendor must be agreed to without any intervention with the Coast Guard. It is expected that the vendor will have the MOAs in place with a minimum of 35 participating States prior to award of contract. If the status is unsigned MOA, there is no access for that state to see State vessels from the inherent query within VIS for other States. An additional 6 participating States MOAs are required within six (6) months of award. There is a potential of up to a maximum of 56 MOAs during the period of performance as more States participate

Currently, the following states and territories have signed an MOA:

Alaska, Alabama, American Samoa, Arizona, Connecticut, District of Columbia, Delaware, Florida, Georgia, Guam, Hawaii, Iowa, Kansas, Louisiana, Massachusetts, Maryland, Maine, Missouri, Northern Mariana Islands, Mississippi, North Carolina, North Dakota, New Mexico, Nevada, Ohio, Oklahoma, Oregon, Pennsylvania, Puerto Rico, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Virginia, Virgin Islands, Washington, Wisconsin, Wyoming

3.0 CONTINUITY OF SUPPORT

The Contractor shall ensure that USCG is provided with a primary and secondary point of contact in case of an issue or question. Response time will be 4 hours or less, and the process for contacting support shall be provided.

Identification System Page 5 of 7

Last Updated: 5 August 2024 Page 5/7

4.1 SECURITY

The requirements office anticipates the following:

Contractor access to personal identifiable information (PII) and unclassified, but Security Sensitive Information may be required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination.

4.2 INDUSTRY PARTICIPATION

The contract awardee shall attend annual National Association of State Boating Law Administrators (NASBLA) conferences and pay annual membership fee ($750). Attendance will be required at up to 2 annual in person meetings and all monthly Vessel Identification Registration and Titling (VIRT) virtual subcommittee meetings (approximately 12 per year).

4.2 PERIOD OF PERFORMANCE

The period of performance for this contract is a one-year base year with four option years as follows:

Base Period - January 2, 2025, through January 1, 2026 Option Yr 1 - January 2, 2026, through January 1, 2027 Option Yr 2 - January 2, 2027, through January 1, 2028 Option Yr 3 - January 2, 2028, through January 1, 2029 Option Yr 4 - January 2, 2029, through January 1, 2030

4.3 PROTECTION OF INFORMATION

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (For Official Use Only) Information. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6).

4.4 SECTION 508 COMPLIANCE

4.4.1 Section 508 Requirements

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 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

Identification System Page 6 of 7

Last Updated: 5 August 2024 Page 6/7

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.

4.4.1.1 Section 508 Requirements for Technology Services (include in the SOW, PWS, or

SOO)

1. 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.

2. 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.

3. When developing or modifying ICT deliverables that contain the ability to automatically generate electronic documents and forms in Microsoft Office and Adobe formats, or when the capability is provided to enable end users to design and author web based electronic content (i.e. surveys, dashboards, charts, data visualizations, etc.), the Contractor shall demonstrate the ability to ensure these outputs conform to the applicable Section 508 standards (including WCAG 2.0 Level A and AA Success Criteria). The Contractor shall demonstrate conformance by conducting testing and reporting test results based on representative sample outputs. For outputs produced as Microsoft Office and Adobe PDF file formats, the Contractor shall use the test methods published under “Accessibility Tests for Documents”, which are published at https://www.dhs.gov/compliance-test-processes.

For outputs produced as web based electronic content, the Contractor shall use the DHS Trusted Tester for Web Methodology Version 5.0, or successor versions. This methodology is published at https://www.dhs.gov/trusted-tester

4. Contractor personnel shall possess the knowledge, skills and abilities necessary to address the accessibility requirements in this work statement

4.4.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 https://www.itic.org/policy/accessibility/vpat

Identification System Page 7 of 7

Last Updated: 5 August 2024 Page 7/7 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. Other Section 508 Documentation: The following documentation shall be provided upon request for ICT items offered through this contract:

o Documentation of features provided to help achieve accessibility and usability for people with disabilities.

o Documentation on how to configure and install the ICT Item to support accessibility.

o Documentation of core functions that cannot be accessed by persons with disabilities.

Documentation of remediation plans to address non-conformance to the Section 508 standards.

4.5 DELIVERABLES

Upon award contractor will provide a weekly, standardized dataset.