USCG_MDA_SOW_v9_20240408.docx

UNCLASSIFIED

NATIONAL GEOSPATIAL-INTELLIGENCE AGENCY

AUTOMATED ANALYTICS

FOR

MARITIME LAW ENFORCEMENT & SECURITY

STATEMENT OF WORK

3 April 2024

Table of Contents

1. BACKGROUND

Most seagoing vessels are required to broadcast their location, speed, and heading using a transponder system called Automatic Identification System (AIS). Although AIS was originally developed to supplement radar for ship-on-ship collision avoidance, the system is broadly utilized by owners, insurers, governments, and port authorities to track vessels' locations and activities globally. Vessels engaging in illegal activities, such as sanction breaching, dumping, illegal fishing, or trafficking, regularly switch the system off (e.g. grey vessels) or spoof its location in an attempt to mask these activities (e.g. dark vessels).

NGA requires a commercial capability to detect and classify surface vessels through an automated algorithm via Electro-Optical (EO) and Synthetic Aperture Radar (SAR) imagery to determine their identity, location, speed, and heading across open ocean, despite their AIS activity. Furthermore, NGA requires the ability to maintain near-real time custody and high confidence positive ID of vessels to support interdiction operations.

Frequently Used Acronyms:

· Automatic Identification System (AIS)

· Common Operating Platform (COP)

· International Maritime Organization (IMO)

· Maritime Mobile Service Identity (MMSI)

· Marine Information for Safety and Law Enforcement (MISLE)

· Ship Arrival Notification System (SANS)

· Vessel of Interest (VOI)

2. SCOPE

The Contractor shall use existing capabilities to automatically identify, classify, and geo-locate surface vessels from commercial EO and SAR imagery across open ocean, and receive those observations in a timeframe and format that enables interdiction as deemed necessary.

3. REQUIREMENTS

3.1. Identification and Classification

The Contractor shall:

3.1.1. Identify and classify common vessel types (military, passenger, tanker, and cargo) derived from EO/SAR imagery.

3.1.2. Associate vessels detected from EO/SAR imagery with matching AIS transmissions.

3.1.3. Automatically detect and alert meetings with other vessels, including ship-to-ship (STS) transfer activities derived from EO/SAR imagery.

3.1.4. Provide rule-based risk assessments, specifically the ability to identify and alert on a vessel’s changes in activity over time, to include economic implications. This includes deviations from normal POL and shipping standards, including turning off AIS, use of false identities, and any activities that otherwise appear illicit or illegal in nature vs legitimate economic activity.

3.1.5. Identify vessels with incorrect/invalid metadata (invalid MMSI, flag mismatch, expired permits (fishing).

3.1.6. Determine the identity of vessels detected from EO/SAR imagery with identifiers like IMO and MMSI even when a nearby AIS transmission is not detected. When identity cannot be determined with high confidence, a list of likely identities shall be provided.

3.1.7. Determine the length and width of all vessels detected from EO/SAR imagery.

3.1.8. Identify when a vessel is spoofing its location via AIS and identify the vessels true location with EO/SAR imagery.

3.1.9. Provide instructor-led (virtually or in-person) training to end user on system functionality and capabilities, including when new functions and capabilities are introduced.

3.2. Coverage

The Contractor shall:

3.2.1. Provide broad area search across up to 10 million km2 of open ocean, i.e., any area from the coastline outward, at least once per day in AOIs specified by the Government.

3.2.2. Prioritize the Red Sea and the South China Sea geographic AOIs but be flexible to include other AOIs.

3.2.3. Track vessels (30m or larger) over time as they are observed from multiple EO/SAR imagery.

3.3. Delivery

The Contractor shall:

3.3.1. Provide near real-time delivery of detections including image chip-out to unclassified government systems to support interdiction operations.

3.3.2. Provide the ability for the Government to have access to Application Programming Interface (API) for integration into a COP.

3.3.3. Automatically detect and alert the USG operator, the COP applicable mission system(s) or COPs on the change vessel particulars to include vessel name, flag, IMO, owner, operator, charterer, change in AIS destination, etc.

3.3.4. Provide the government the ability to create virtual geographic boundaries (“geo-fencing”) also known as specific areas of interest (AOIs).

3.3.4.1. Provide the ability to specify a VOI in a particular timeframe within a specified geographically “fenced” area (watch box) and alert the USG operators or COPs in near real-time.

3.3.4.2. Provide the ability for the Government to set up alerts based on dynamic sorting criteria and receive automatic notifications when criteria is met. This includes identifying a VOI entering or exiting an AOI, identifying a VOI at a specific location during a specific time period, identifying a VOI transiting between two points (ports, countries, AOIs) at any point in time (alerts, previous port validation), etc.

3.3.5. Provide the ability for the Government to import and export data in commonly used formats (.csv, .xls, .xml, Oth-G, .shp, .lyr) to support data fusion [correlating arrival data (SANS) with location data (AIS) and MISLE data].

3.3.6. Provide the Government the ability to conduct simple and complex searches by name of vessel, IMO, MMSI, vessel type, vessel size, vessel course/speed or in combination.

3.3.6.1. Provide the Government the ability to create reusable and predefined filters by any combination of metadata (e.g. display all Iranian flag, tanker vessels, >300GT).

4. DELIVERY

4.1. Delivery Dates

4.1.1. Hosted software: One week (7 calendar days) after award.

4.1.2. API integration into the Government’s chosen COP: One week (7 calendar days) after award.

4.2. Delivery Format

4.2.1. Hosted software: Through a commercially hosted user interface (UI)

4.2.2. Analytics feed: Through an API to the COP of choice from the Government.

5. DATA RIGHTS

5.1. Government Purpose Rights

5.1.1. Notwithstanding any contrary language in a standard commercial license, NGA shall have “government purpose rights,” (GPR) as that term is defined in 48 C.F.R. 252.227-7013.

6. QUALITY ASSURANCE AND ACCEPTANCE CRITERIA

6.1. The required performance standards and/or quality levels are included in the table below.

Performance Requirements Summary Table

7. REPORTING and MEETINGS

7.1. Kickoff

A local kick-off meeting or teleconference shall take place within the first month of contract award. The Government Program Manager (GPM) and Contractor will determine the most appropriate location to have this meeting.

7.2. Technical Exchange Meetings (TEMs)

The Contractor shall support a technical exchange meeting (TEM) via teleconference at least once a month.

8. PERIODS OF PERFORMANCE

The Base Period of Performance (POP) is four months after award.

The Option Period of Performance (POP) is two months after exercise.

9. TRAVEL

Travel is not required for this effort and will not be compensated.

10. SECURITY

All work under this delivery order is UNCLASSIFIED, and there are no additional security requirements for processing or delivering the final deliverables.

11. CONTRACTING OFFICER REPRESENTATIVE (COR)

The Contractor shall make all deliveries to the COR unless otherwise directed:

Heather A. Moser 3838 Vogel Road Arnold, MO 63010

(314) 676-0881

UNCLASSIFIED

image1.jpeg