CG-RAPTOR_Coastal_Sentinel_Industry_Day__RFI.docx

UNITED STATES COAST GUARD

REQUEST FOR INFORMATION (RFI) AND INDUSTRY DAY ANNOUNCEMENT

CG-RAPTOR COASTAL SENTINEL INDUSTRY DAY

Maritime Tracks, Distributed Sensing, TAK Integration, and AI-Enabled Video Analytics

San Diego, California | Tuesday, 29 September 2026

Marc.A.Massey@uscg.mil, Mr. Marc Massey

IMPORTANT - THIS IS NOT A SOLICITATION

This RFI is issued solely for market research, planning, and selection of participants for the 29 September 2026 industry engagement. The Government does not intend to award a contract on the basis of this RFI or otherwise pay for the information requested. Responses are information only, are not proposals or offers, and cannot be accepted to form a binding contract.

1. Purpose The United States Coast Guard Office of Rapid Response and Prototyping (CG-RAPTOR) invites industry to submit information on mature, operationally relevant technologies that could strengthen the Coastal Sentinel capability portfolio. Based on the responses, the Coast Guard intends to down-select to no more than ten companies to participate in an invitation-only Coastal Sentinel Industry Day the afternoon of 29 September 2026 in San Diego, California. The Government may select fewer than ten companies at its discretion.

The objective is to identify technologies that can be evaluated rapidly with operators, integrated with existing or emerging maritime data and command-and-control workflows, and transitioned at a pace consistent with urgent operational needs.

A response may address one technology area or an integrated solution spanning multiple areas. The Government is especially interested in solutions that are already demonstrated in relevant environments, can show measurable operational value, and can be presented or demonstrated on the event date without significant Government-funded development.

2. Background CG-RAPTOR is the Coast Guard's Office of Rapid Response and Prototyping. It brings operators, industry, and Government stakeholders together to test proven innovative concepts, evaluate real-world effectiveness, and close urgent operational gaps through rapid learning and prototyping.

Coastal Sentinel is the Coast Guard's next-generation maritime surveillance, command-and-control, and communications capability. It is intended to help operators sense maritime activity, make sense of diverse data, and act through a data-rich common operating picture. This RFI focuses on technologies that can improve the quality, persistence, integration, and operational usefulness of maritime sensing and analytics.

3. Industry Day Overview

3.1 Date and Location

Date: Tuesday, 29 September 2026. Location: San Diego, California. The exact venue, access procedures, parking information, and any facility restrictions will be provided to invited participants. The venue is anticipated to be at a site near Imperial Beach, CA. Attendance will be limited and controlled by the Government.

3.2 Planned Format

The event is expected to be unclassified. The Government will not accept classified information, Controlled Unclassified Information (CUI), or export-controlled technical data in response to this notice. Additional handling restrictions for the event will be provided to selected participants.

4. Technology Areas of Interest The Coast Guard seeks mature technologies in the following four areas. The examples are illustrative and are not intended to exclude other approaches that directly address the stated operational objective.

4.1 Mature Integration with the Team Awareness Kit Ecosystem

Technologies should demonstrate functioning, mature integration with the Team Awareness Kit (TAK) ecosystem rather than an integration roadmap alone. Relevant integrations may include ATAK, WinTAK, TAK Server, Cursor-on-Target data exchange, TAK plugins, or other applicable TAK components and services. Responses should describe the integration that exists today, the environment in which it has been tested or deployed, and the operational functions enabled.

Bidirectional exchange of tracks, detections, alerts, imagery, tasking, or other mission data, as applicable.

Demonstrated interoperability with relevant TAK clients, servers, plugins, application programming interfaces, and data standards.

Operation in disconnected, intermittent, limited-bandwidth, or degraded-network conditions.

Identity, access control, data-sharing, federation, audit, and cybersecurity features appropriate to operational use.

Evidence of operational deployment, user testing, integration testing, or repeatable laboratory demonstration.

4.2 Improved Maritime Tracks and Detections

Technologies should improve the quality and operational usefulness of maritime tracks and detections beyond basic position reporting. Areas of interest include:

Multi-source track correlation;

Sensor fusion;

Confidence scoring;

Identity resolution;

Track history and behavior;

Kinematic analysis;

Anomaly detection;

Sensor provenance;

Alert generation; and Data enrichment for operational decision-making.

4.3 Alternatives or Complements to Traditional Long-Range Electro-Optical/Infrared Sensing The Government is interested in technologies that expand maritime awareness, persistence, or coverage while reducing cost, manpower, or operational burden. Areas of interest include:

High-altitude balloons;

Uncrewed aircraft systems (UAS) deployed from or integrated with uncrewed surface vessels (USVs);

Maritime buoys;

Distributed sensing architectures;

Lower-cost wide-area sensing approaches;

Persistent or semi-persistent maritime coverage; and Systems that increase coverage while reducing cost or operational burden.

4.4 Mature Full-Motion Video and Computer Vision for Maritime Operations Technologies should apply mature full-motion video (FMV), computer vision, or related machine-learning models to maritime operational needs. Areas of interest include:

Maritime object detection;

Vessel classification;

Activity recognition;

Pattern-of-life analysis;

Anomaly detection;

Automated cueing;

AI-assisted watch standing;

Model outputs integrated into the common operating picture;

Confidence scoring; and Operator feedback loops for validation, correction, and model improvement.

5. Desired Maturity and Cross-Cutting Attributes The Coast Guard is seeking demonstration-ready capabilities, not basic research or marketing-only concepts. Respondents should state the Technology Readiness Level (TRL), commercial maturity, or equivalent evidence of readiness. Preference may be given to technologies that have been tested in a relevant environment, have current users or customers, or can provide repeatable performance evidence.

Across all technology areas, the Government values the following attributes:

Clear operational utility and a measurable improvement over current practice;

Modular architecture, documented interfaces, and practical integration pathways;

Operation at the edge and under constrained communications conditions;

Transparent confidence measures, data provenance, explainability, and operator control;

Cybersecurity, identity, access-control, logging, and data-governance features appropriate to the intended environment;

Human-centered design that reduces workload and supports rapid operator comprehension;

Scalability, affordability, maintainability, and reduced training or sustainment burden; and A credible path to rapid operator evaluation and, if warranted through a separate action, transition or procurement.

6. Response Instructions

6.1 Response Package

A complete response consists of the required quad chart and the information requested in the submission email. An optional white paper is strongly encouraged. The Government will evaluate and down-select based solely on the information submitted by the response deadline.

6.2 Required Quad Chart Content

The quad chart shall be suitable for distribution to U.S. Government reviewers and registered event participants. It shall not contain proprietary, classified, CUI, or export-controlled information. Use Attachment A or a materially equivalent layout. At a minimum, include:

Company legal name, solution name, website, point of contact, business size, and all teaming partners;

Primary and secondary technology area(s) addressed;

Operational problem, intended users, and the specific Coastal Sentinel contribution;

Technology description, architecture or image, principal data inputs and outputs, and differentiators;

Current maturity, deployments or tests, performance evidence, and known limitations;

Existing TAK and common-operating-picture integrations, as applicable;

Proposed 29 September demonstration, what the audience will observe, and proposed success measures; and Major logistics, network, power, spectrum, airspace, water-access, safety, cybersecurity, or data dependencies.

6.3 Encouraged White Paper Content

The optional white paper may contain properly marked proprietary information. The three-page limit includes all text, figures, tables, footnotes, and references. The white paper should address the following, to the extent applicable:

Executive summary and operational use case;

Technical approach, system architecture, interfaces, data standards, hosting or edge-compute model, and cybersecurity posture;

Evidence of maturity, including customers, relevant deployments, test results, model performance, latency, accuracy, false-alarm performance, confidence calibration, or other appropriate measures;

Integration details, especially mature TAK integration, common-operating-picture integration, and data ingest or export methods;

Proposed demonstration plan and objective success criteria;

Equipment footprint, personnel, setup time, network and power needs, radio frequencies, UAS/USV/balloon/buoy activity, safety considerations, and required Government support;

Scalability, sustainment, training burden, licensing approach, and rough-order-of-magnitude acquisition and recurring cost ranges, if available; and Risks, limitations, export-control status, and any conditions that could prevent demonstration on 29 September 2026.

6.4 Submission Email and File Naming

Submit responses electronically to kenneth.s.boyer@uscg.mil and marc.a.massey@uscg.mil no later than Friday, 14 August 2026, 2:00PM EST. Late responses may not be considered for event participation.

Use the email subject line: CG-RAPTOR Coastal Sentinel RFI - [Company Name] - [Technology Name].

Use the following file naming convention:

[Company]_[Technology]_CG-RAPTOR_QuadChart.pptx [Company]_[Technology]_CG-RAPTOR_QuadChart.pdf [Company]_[Technology]_CG-RAPTOR_WhitePaper.pdf, if submitted

The submission email shall include:

Company legal name, address, website, and business size or socioeconomic category;

Unique Entity ID and CAGE Code, if available (not required for submission);

Primary point of contact name, title, email, and telephone number;

Primary technology area and any secondary areas addressed;

Names of teaming partners, subcontractors, or affiliated organizations included in the proposed demonstration;

Whether the response contains proprietary information and whether any aspect of the technology is subject to ITAR, EAR, or other export-control restrictions;

Confirmation that the respondent consents to review by authorized Government personnel and Government support contractors or FFRDC personnel who are subject to appropriate nondisclosure obligations; and Confirmation that the technology can be presented or demonstrated in San Diego on 29 September 2026 if selected.

Submit one response package for each distinctly different technology. A single integrated solution may address multiple technology areas in one package. Do not submit executable files, source code, classified material, CUI, or export-controlled technical data. Links requiring credentials or special software may not be reviewed.

7. Down-Selection for Industry Day Participation The Coast Guard intends to select no more than ten companies for demonstration and technical-exchange session. The Government may select fewer than ten, make no selections, or identify alternate participants. Selection is solely for participation in this industry engagement and is not a source-selection decision, competitive-range determination, product endorsement, qualification, or commitment to purchase.

A Government review team will assess complete, timely responses. Criteria are not listed in order of importance and may be considered holistically:

The Government may also consider portfolio balance across the four technology areas, avoidance of duplicative demonstrations, and the value of exposing operators to distinct technical approaches. The Government may contact respondents for brief clarifications; respondents should not assume that an opportunity to revise or supplement a response will be provided.

The Government intends to notify selected and non-selected respondents by email no later than Tuesday, 1 September 2026. Formal debriefings are not anticipated. Feedback may be provided at the Government's discretion and as resources permit.

8. Requirements for Selected Participants Selected companies will receive an invitation and a separate planning package. Acceptance of the invitation will require timely completion of event coordination actions. Selected respondents should expect to provide, at a minimum:

An attendee roster and all information required for facility access, badging, citizenship or foreign-national review, and security screening;

A detailed demonstration plan, equipment list, footprint, setup and teardown timeline, staffing plan, and objective success measures;

Power, network, data, display, spectrum, airspace, water-access, vessel, UAS, USV, balloon, buoy, hazardous-material, and other special requirements;

Safety documentation, operating instructions, risk controls, insurance or certifications if required, and proof of applicable regulatory authorizations;

Cybersecurity and data-handling information needed to approve any connection to a Government-provided network, data feed, or system; and A final non-proprietary presentation or quad chart suitable for the common industry-day session.

No radio-frequency transmission, Government-network connection, flight, autonomous or remotely operated water activity, over-water deployment, balloon release, buoy deployment, or other regulated activity may occur without prior written Government approval. Selection does not guarantee that any requested activity will be approved. The Government may require a static, simulated, recorded, or reduced-scope demonstration when safety, venue, spectrum, cybersecurity, environmental, or regulatory constraints prevent a live demonstration.

Selected participants shall be prepared to operate their own technology and to bring all equipment, cables, adapters, displays, tools, spares, consumables, and trained personnel necessary for the demonstration. Any Government data, interface, network, vessel, range, test asset, or technical support must be specifically requested and is not guaranteed.

9. Government Support and Respondent Costs The Government anticipates providing the event venue, a scheduled demonstration or presentation slot, and basic meeting or display space. Standard commercial power may be available if requested in advance. All other resources are subject to availability and written confirmation.

Each respondent is responsible for all costs associated with preparing and submitting its response and, if selected, participating in the event. This includes travel, lodging, meals, shipping, insurance, permits, regulatory approvals, equipment, integration, setup, operation, teardown, and restoration. The Government will not reimburse any respondent for these costs and assumes no liability for loss of or damage to respondent-owned equipment except as may be expressly provided in a separate written agreement.

10. Information Protection, Proprietary Data, and Review Support The required quad chart must be non-proprietary and suitable for distribution to Government reviewers and registered event participants. An optional white paper may contain proprietary information if each page and the specific protected material are clearly marked. Respondents should submit only the proprietary detail necessary for meaningful Government review.

The Government will safeguard properly marked information from unauthorized disclosure in accordance with applicable law and policy. The Government will not be responsible for protecting information that is not clearly marked. Submission grants the Government permission to reproduce the response for internal review and event-planning purposes; it does not transfer ownership of the respondent's intellectual property.

Government support contractors, consultants, or Federally Funded Research and Development Center personnel may assist with event planning, safety, cybersecurity, integration, or assessment. Such personnel will be subject to appropriate nondisclosure and conflict-of-interest obligations. Submission constitutes consent to release the response to those authorized reviewers. A respondent that cannot provide this consent shall state that limitation prominently in its submission; the limitation may prevent complete evaluation.

Respondents are responsible for compliance with the International Traffic in Arms Regulations (ITAR), Export Administration Regulations (EAR), and all other applicable export-control requirements. Do not include export-controlled technical data in the response. Identify any export or access restrictions that could affect event attendance, Government review, photography, discussion, or demonstration. Facility and attendee access rules will be provided to selected respondents.

The Government may use non-proprietary observations, performance data, lessons learned, and aggregated findings from the event for internal planning, requirements development, and future market research. The Government will not intentionally disclose properly marked proprietary information outside authorized review channels.

Any Government support contractors and/or Coast Guard personnel assisting with the development, review, evaluation, administrative processing of these submissions and/or participation in the Industry Day are bound by strict Non-Disclosure Agreements (NDAs) and/or Organizational Conflict of Interest (OCI) clauses that prohibit them, or their affiliated companies, from competing on future Coastal Sentinel solicitations.

11. Questions and Communications Submit administrative and technical questions by email to kenneth.s.boyer@uscg.mil and marc.a.massey@uscg.mil no later than Thursday, 6 August 2026, 11:00AM EST. Use the subject line: CG-RAPTOR Coastal Sentinel RFI Question - [Company Name].

The Government may post answers or an amended notice when a response would benefit all potential respondents. Questions and answers may be paraphrased and posted without company attribution. Do not include proprietary information in questions. Telephone inquiries are not authorized unless expressly invited by the Government point of contact.

Only the designated Government point of contact may provide official information regarding this RFI. Communications with other Government personnel do not change the terms of this notice and shall not be relied upon as authorization to incur costs or conduct event activities.

12. Schedule

All dates are subject to change. Changes will be communicated through an amendment to the public notice or directly to selected participants, as appropriate.

13. Reservation of Rights and RFI Limitations This notice is not a solicitation or commitment to issue a future acquisition. The Government does not intend to award a contract on the basis of this RFI or otherwise pay for the information requested; responses are information only and not proposals or offers.

The Government may use information received for market understanding, operational concepts, evaluation planning, requirements development, or future acquisition strategy, subject to protection of properly marked information.

The Government may cancel, postpone, relocate, or modify the event; select fewer than ten companies; make no selections; discontinue discussions; or decline to acknowledge responses, provide feedback, return materials, or answer every question.

Responding, being selected, attending, or declining to participate will not provide an advantage or disadvantage in any future procurement. Any future solicitation will be announced separately and governed solely by its own terms.

ATTACHMENT A - REQUIRED QUAD CHART CONTENT GUIDE

Submit as a one-page, 16:9 landscape PowerPoint and PDF. Use clear, non-proprietary content and readable graphics.

COMPANY

[Legal name / website]

SOLUTION

[Technology Name]

TECHNOLOGY AREA(S)

[1, 2, 3, and/or 4]

POINT OF CONTACT

[Name / email / phone]

MATURITY

[TRL / deployment]

1. OPERATIONAL NEED AND USE CASE

Operational problem and intended user Representative maritime vignette or mission use case Specific Coastal Sentinel contribution Expected operational benefit and measurable outcome [Use concise text, visuals, and quantified evidence. Do not include proprietary or export-controlled information.]

2. TECHNOLOGY AND DIFFERENTIATORS

Diagram, image, or architecture overview Principal sensors, data inputs, outputs, and interfaces How the solution works and why it is different Relevant TAK / COP integration and interoperability [Use concise text, visuals, and quantified evidence. Do not include proprietary or export-controlled information.]

3. MATURITY, INTEGRATION, AND EVIDENCE

TRL or commercial maturity and deployment history Test results, performance measures, users, and references Cybersecurity, hosting / edge model, confidence, provenance Known limitations, dependencies, and integration burden [Use concise text, visuals, and quantified evidence. Do not include proprietary or export-controlled information.]

4. PROPOSED 29 SEPTEMBER DEMONSTRATION

What Coast Guard operators will see and do Objective success criteria and expected outputs Equipment, setup time, personnel, power, network, data needs RF, UAS / USV, airspace, water, safety, and regulatory needs [Use concise text, visuals, and quantified evidence. Do not include proprietary or export-controlled information.]

Footer information: business size / socioeconomic category; teaming partners; UEI and CAGE if available; file name; and the statement "NON-PROPRIETARY - SUITABLE FOR EVENT DISTRIBUTION."

Recommended PowerPoint body text: at least 18 points. Use charts, diagrams, screenshots, or photographs only when they improve understanding. Avoid sales slogans, unsupported claims, dense paragraphs, and unreadable footnotes.