Request for Information: United States Coast Guard Core Navigation Software

Description & Purpose of Request 1.1 Objective The United States Coast Guard (USCG) is conducting market research in accordance with Federal Acquisition Regulation (FAR) Part 10 to identify commercially available off-the-shelf (COTS) and Non-Developmental Item (NDI) core maritime navigation software solutions that have the capability of being enhanced to meet USCG requirements (e.g. EAIS IDD). The primary objective is to survey industry capabilities to inform the prospective modernization and eventual replacement of the legacy USCG “Vega” navigation software suite (currently derived from commercial core navigation architectures) across the cutter and boat fleet. 1.2 Purpose & Scope of Market Inquiry The Coast Guard seeks insight into the current commercial and naval navigation software, including cutting-edge display engines, autonomous voyage planning, sensor fusion, resilient Positioning, Navigation, and Timing (PNT), and modern software architectures (e.g., modular open systems, containerized microservices, cross-platform runtimes). The Government intends to assess software suites that can match or exceed the complete operational baseline of current USCG E-NAV capabilities while remaining flexible, open, and capable of integrating seamlessly into existing USCG shipboard hardware configurations without requiring complete bridge refits. 1.3 Disclaimer This is a Request for Information (RFI) and is issued solely for informational, market research, and planning purposes. This is not a Request for Proposals or a Request for Quotations, and it is not considered to be a commitment by the Government to award a contract/order nor is the Government responsible for any costs incurred in furnishing information provided under this RFI. No basis for claim against the Government shall arise as a result of a response to this RFI or Government use of any information provided. Further, the Government is not seeking proposals and will not accept unsolicited proposals at this time. No classified, confidential, or sensitive information should be included in your response to this RFI. Proprietary information must be clearly marked if included. The Government reserves the right to use any information provided by respondents for any purpose deemed necessary and legally appropriate, including using technical information provided by respondents in any resultant solicitation. Responses will assist the Government in determining the availability of potential solutions and commercial products in the market. At this time, no solicitation exists; therefore, please do not request a copy of the solicitation. The information and requirements in this RFI, and any attachments, is subject to change at the sole discretion of the Government. 2. Operational Environment & Hardware Baseline Constraints To ensure candidate software solutions can integrate into active cutter classes without widespread structural or electrical bridge overhauls, respondents must demonstrate compatibility with the following operational constraints: 2.1 Installed Hardware Baseline (E-NAV) The USCG fleet operates on a variety of IEC 60945 compliant hardware baselines consisting of: rack mounted industrial computers, rack mounted servers, ruggedized small factor computers, marine-grade All-in-One (AIO) Computer/Displays, system displays ranging from 15-19 inches, KVM matrix, ruggedized mouse and keyboard. 2.2 Operating System (OS) Gatekeeper Requirements Software architecture must natively support modern enterprise operating system standards: Microsoft Windows 11 Enterprise (including Long-Term Servicing Channel [LTSC] builds). Enterprise Linux Distributions (e.g., Latest version of Red Hat Enterprise Linux [RHEL]). Vendors must state whether their software executes natively on Windows 11, Linux, or maintains a dual-OS cross-platform compiled codebase. 2.3 System Availability and Deterministic State Recovery Deterministic State Recovery: In the event of ungraceful bridge power interruption or system reset, the software must reboot and restore its previous operational state, active route, safety parameters, and sensor assignments without manual database rebuilding. 3. Core Functional Capability Matrix See Attachment. 3.1 Sensor Ingestion & Data Distribution Protocol Support: Native ingestion, parsing, translation, and broadcast of NMEA 0183, NMEA 2000 (IEC 61162-3), NMEA OneNet, and Lightweight Ethernet (LWE)(IEC 61162-450) protocols. Sensor Interfacing: Interfacing with gyrocompasses, Doppler velocity logs (DVL), magnetic compasses, wind sensors, depth sounders, GPS/DGPS/Galileo receivers, Inertial Navigation Systems (INS), and radar targets (ARPA). Integrity & Checksum: Cryptographic and checksum integrity verification for all data streams; automated detection and notification of malformed or invalid sentences. Decoupled Time Distribution: Network time distribution via UDP/TCP; ability to assign an authoritative UTC time source independent of the primary positioning source. 3.2 Data Recording, Playback, and Forensics Comprehensive Logging: Continuous background recording of ownship dynamics, sensor inputs, target tracking data, alert histories, and operator interactions. Storage Flexibility: Ability to write logs and telemetry to internal storage, external mission media (USB/NAS), or enterprise shipboard repositories. Visual Playback: Integrated forensic playback mode providing time-synchronized replay of chart presentation, radar overlay, and sensor states for accident investigation and tactical debrief. 3.3 Chart Management & Next-Gen Hydrographic Standards Legacy Format Support: Seamless handling of S-57 ENC, S-63 encrypted charts, and DNC (Digital Nautical Chart) formats. S-100 Transition Framework: Implementation roadmap and readiness for the IHO S-100 Universal Hydrographic Data Model, specifically: S-101 Electronic Navigational Charts (ENC) S-102 High-Resolution Bathymetric Surfaces S-104 Water Level Information S-111 Surface Currents S-124 Navigational Warnings Manual Corrections: Ability to create, save, import, and visually verify manual notice-to-mariners chart corrections and local marine hazards. 3.4 Operational Display Area (ODA) & Ownship Dynamics Ownship Dynamics: Multi-source position fixing utilizing GNSS (GGA/GNS), INS, Radar Chart Matching, manual visual/radar Lines of Position (LOPs), and Dead Reckoning (DR). Dynamic Calculations: Automated computation of real-time Set and Drift, Course Over Ground (COG), Speed Over Ground (SOG), Speed Through Water (STW), and Rate of Turn (ROT). Tactical Plotting: Rapid generation of Danger Bearings/Ranges, Clearing Lines, Variable Range Markers (VRM), Electronic Bearing Lines (EBL), and instant Man Overboard (MOB) emergency markers. RADAR Overlay: Software must be compatible with Furuno SDK and SSR COMRIC for RADAR overlay capability. 3.5 Human-System Interface (HSI) & Publications Visual Standards: Full conformance with IHO S-52 Presentation Library colors, symbology, and display modes (Day, Dusk, Night). Coordinate Precision: Coordinate calculation and display capabilities resolving latitude and longitude to one thousandth of a second (0.001”). Nautical Nomenclature: Standardization using Pub. 9 (Bowditch) and Chart No. 1 nautical symbology and abbreviations. Electronic Publications: Native viewer for hydrographic reference materials, Standard Bearing Books, and Adobe PDF navigation documentation. 3.6 Cybersecurity, Information Assurance & System Management DoD/DHS Compliance: Architecture capable of being hardened to DISA Security Technical Implementation Guides (STIGs), meeting NIST SP 800-53 Rev 5 security controls, and aligning with Federal Information Security Modernization Act (FISMA) parameters. Role-Based Access Control (RBAC): Distinct cryptographic user/administrator profiles, group policies, and role permissions preserved across software patches and upgrades. Configuration Auditing: Secure text-searchable configuration repositories, system event logging, and controlled patch deployment. 4. Specialized Coast Guard Mission Functions The legacy Vega suite incorporates specialized operational modules tailored to unique USCG mission sets. Prospective solutions must identify whether these capabilities exist natively, can be integrated via plug-in/APIs, or require custom development. 4.1 Western Rivers (WR) Navigation & ATON Management The software must provide the capability to: Database Management: Dedicated database maintaining Western Rivers Aids to Navigation (WR ATON) and dynamic river segments. Buoy Tending Workflow: Specialized user interface designed for USCG river tenders to track, position, edit, drop, and inspect buoys directly within the ODA. Depth Survey Mode: Ingestion and visualization of single-beam and multi-beam bathymetric survey depth data in real-time. Enterprise Synchronization: Capability to export, import, archive, and synchronize ATON position reports, worklists, and discrepancy logs with Coast Guard enterprise ashore systems. 4.2 STEDS / Sensitive Tactical Asset Tracking & Encrypted AIS The software must provide the capability to: Encrypted AIS (EAIS) Interfacing: Two-way transactional command, status, and messaging interface between the navigation engine and EAIS transponders. Software must have a transactional process between an EAIS transponder and be able to act as a Presentation Interface with a STEDS capable transponder. Blue Force Tracking (BFT): Ingestion and presentation of Sensitive but Unclassified (SBU) tactical data, Situation Reports (SITREPs), and friendly force positions. Tactical Target of Interest (TOI): Management of specialized tactical identifiers, target classification, and Intercept / Closest Point of Approach (CPA) calculations. SAR Integration: Automated generation, overlay, and management of standard Search and Rescue (SAR) patterns (e.g., Expanding Square, Parallel Search, Sector Search, Creeping Line) and tracklines. Tactical Messaging: Transmission and reception of Geographic Notice messages, tactical text bulletins, and Linkage ID route information. 5. Vendor Survey & Technology Discovery Questions 5.1 Architecture, Operating Systems & Hardware Modularity Describe your software's underlying architecture. Is it built upon a monolithic codebase, modular libraries, or containerized microservices? Detail your native OS support across Windows 11 Enterprise (64-bit) and Enterprise Linux [RHEL] 8/9/10 etc.). Do you maintain parity across both operating systems with a single unified codebase? What are the minimum and recommended compute specifications (CPU, RAM, GPU, storage throughput) to operate your software efficiently on Marine AIO panel computers? What are some unique features or characteristics that your software provides? In the event of an uncontrolled system shutdown or power loss, what failover, fallback, or rapid-reboot behaviors does your software execute to minimize Time to First Fix and restore safety to navigation displays? Can your software be manipulated to include a widget within the ODA to remotely control KVM switch if provided the KVM’s SDK? Is your software capable of allowing pre-loaded, programmed configurations, as well as selecting individualized configurations using a graphical user interface matrix? 5.2 Next-Generation Hydrographic Standards (IHO S-100) What is the current maturity and operational status of your software regarding the IHO S-100 framework? Specifically, what is your production timeline or current support for S-101 (ENC), S-102 (Bathymetry), and S-111 (Surface Currents)? How does your display engine handle dynamic layering and visual priority when multi-source datasets (e.g., bathymetry + vector chart + radar overlay) are active simultaneously? 5.3 Resilient PNT, Sensor Fusion & EW Mitigation How does your navigation engine detect, alert, and mitigate Global Navigation Satellite System (GNSS) anomalies, such as jamming, spoofing, or multipath drift? Does your system support automated sensor fusion and Kalman filtering across heterogeneous inputs (e.g., GPS, INS, Doppler Log, Compass, Radar Matching)? What is the system's failover behavior when primary PNT data is lost or declared untrusted? 5.4 Specialized Mission Module Adaptation (Western Rivers & STEDS) Does your platform currently possess native capabilities comparable to the Western Rivers ATON and STEDS/EAIS requirements detailed in Section 4? If not natively present, what mechanism does your software offer for government or third-party developers to integrate custom mission logic (e.g., Open APIs, Software Development Kits [SDKs], gRPC/REST endpoints, C++ / Python plugins)? What is the intellectual property (IP) and licensing model for custom plugins developed on your platform? 5.5 Modern Human-System Interface (HSI) & Usability How is your graphical user interface optimized for high-stress bridge operations, night-vision adaptation (red/low-light), and rapid touch/trackball interaction? 5.6 Cybersecurity, Patching & Lifecycle Support What is your experience in deploying software that meets DISA STIG requirements and undergoes DoD/DHS Risk Management Framework (RMF) assessment? How are vulnerability security patches delivered, validated, and applied without disrupting marine type approvals or custom operational configurations? What is your commercial licensing structure (e.g., perpetual node license, enterprise subscription, per-seat maintenance)? How does your company provide/handle continued product support and warranty contracts? 5.7 Core Navigation Engine and Data Lifecycle Describe how your software ingests, validates (via checksums/cryptography), and processes raw sensor data (e.g., GPS, INS, Gyro, DVL) Explain your system’s internal and networked data distribution architecture for sharing telemetry across bridge workstations. Detail your chart management workflow, including how the system updates, overlays, and prioritizes multi-format charts (ENC, DNC, S-100) Explain the technical architecture of your data logging system and how the forensic visual playback mode is executed without impacting active navigation performance. 6. Response Submission Instructions 6.1 Content & Format Guidelines Executive Summary: Maximum 2 pages highlighting corporate overview, maritime navigation experience, and core product offerings. Vendors are encouraged to provide links to publicly available marketing materials, spec sheets, or other applicable materials. Technical Capability Statement: Maximum 15 pages addressing the Functional Baseline (Section 3), Mission Modules (Section 4), and Vendor Discovery Questions (Section 5). Format: Submissions must be delivered electronically in Adobe PDF format (searchable, 11-point font minimum). 6.2 Company Information Cover Sheet All submissions must include a cover sheet detailing: Company Name, Address, and Website Point of Contact (Name, Title, Email, Phone Number) Commercial and Government Entity (CAGE) Code and Unique Entity Identifier (UEI) Business Size Standard under NAICS 513210 Existing Government-Wide Acquisition Contracts (GWAC), GSA Multiple Award Schedules (MAS), or DoD Enterprise Software Initiative (ESI) vehicles held. 6.3 Submission Logistics Submission Deadline: October 23rd, 2026, no later than 5:00pm Eastern Time. Submission Delivery: Responses must be submitted via email to the USCG Contracting Personnel Listed Below: Contract Specialist: Roberta.F.Pluim@uscg.mil Contract Specialist: Eric.R.St.Pierre@uscg.mil Contracting Officer: Jessica.L.Coltz@uscg.mil Proprietary Data: If a respondent wishes to submit proprietary information, it must be clearly marked on each page containing proprietary data. The Government will handle proprietary material in accordance with applicable Federal statutes and FAR requirements.