Surface Combat Systems Engineering and Integration
Open — responses due 4 Dec 2026 (20 days left) · No Set aside used · Department of the Navy, DoD · NAICS 541330 · Solicitation N6175027R1201
Get the AI read before you spend a day on this package. FedSift pulls out the deal-breakers and key risks, each quoted from the document. Free, no account.
Before you spend a day on this package: FedSift reads every document and pulls out what is being bought, the deal-breakers and the key risks — each quoted from the page it came from. Free, no account needed. The result is shared, so the next reader gets it instantly. With a free account it also builds the full compliance matrix.
Track this solicitation
We'll email you if the response deadline moves, an amendment posts, or new documents are added. It closes 04 December 2026. No account needed — one email, unsubscribe in a click.
Description
REQUEST FOR INFORMATION (RFI) / SOURCES SOUGHT ANNOUNCEMENT DEPARTMENT OF THE NAVY Program Acquisition Executive Mission Systems (PAE MS) Capability Portfolio Executive Combat Systems & Fires (CPE CS&F) Integrated Combat System (ICS), PMW 630 SECTION 1: GENERAL INFORMATION Document Type: Request for Information (RFI) / Sources Sought Notice Solicitation / Reference Number: N6175027R1201 Contracting Activity: Navy PAE Mission Systems, Washington Navy Yard, DC Program Title: Surface Ship ICS Engineering and Integration North American Industry Classification System (NAICS) Code: 541330 – Engineering Services (Military and Aerospace Equipment and Military Weapons) Product Service Code (PSC): AC13 – R&D: Defense Systems: Weapons / R425 – Support - Professional: Engineering/Technical Response Due Date: 04 December 2026, 15:00 EST Classification Level: Primary document UNCLASSIFIED. Classified responses or annexes up to SECRET / NOFORN handled by separate coordination (see Section 7). SECTION 2: STATUTORY DISCLAIMER & SPECIAL NOTICE This RFI is issued solely for information and planning purposes in accordance with FAR 15.101(c). This notice does not constitute a Request for Proposal (RFP), Invitation for Bid (IFB), or an announcement of a forthcoming solicitation. Issuance of this notice does not obligate the Government to issue a formal solicitation or award a contract. The Government will not pay or reimburse any costs incurred by respondents in preparing, submitting, or demonstrating information in response to this notice. All submissions become Government property and will not be returned. Participation in this RFI is voluntary. Failure to respond will not preclude a vendor from participating in any future competitive acquisition, should one be released. Respondents may submit capability statements addressing any subset or all of the focus areas detailed herein. SECTION 3: BACKGROUND & PROGRAM CONTEXT 3.1 Background & Context Modern surface warfare requires rapid, modular capability delivery across the Navy's surface fleet. The Navy’s ICS program is making this vision a reality through use of virtualization, Kubernetes orchestration, and development of a common suite of mission applications enabling a "build once and deploy across the fleet" methodology for delivery of capability to frigates, destroyers, amphibious ships, aircraft carriers, future manned and unmanned vessels, and future foreign military sales vessels. The ICS program is conducting market research to identify industry partners capable of executing comprehensive systems engineering and software integration for U.S. Navy surface combat systems. This scope is currently being executed under the N00024-23-C-5117 contract awarded to Lockheed Martin Rotary & Mission Systems in September 2023. 3.2 Technical Scope & Baselines The technical scope spans current and next-generation baseline configurations running incremental deliveries of the Integrated Combat System (ICS) software stack (infrastructure services and tactical platform services) and common mission applications. Applicable ship deliveries include the following: ICS-Enabled AEGIS Combat System Baselines 9.C3+ and Baseline 10.1+ running on Mk6 Mod0/1 hardware with IaaS ORDALT or on Mk6 ModX hardware ICS-Enabled Ship Self-Defense System (SSDS) platforms FF(X) 3 and follow DDG 1000 class in line with delivery of the Zumwalt Enterprise Upgrade Solution (ZEUS) Future USN and FMS platforms SECTION 4: TECHNICAL REQUIREMENTS & CAPABILITY AREAS SOUGHT The Navy seeks detailed technical capabilities, corporate competencies, and innovative methodologies across eleven (11) functional areas. Vendors may respond to any or all of the following scope areas: Focus Area 1: Programmatic Engineering, Configuration Management & Governance Configuration Management (CM): Formulating, baselining, and executing Configuration Management Plans (CMP), software build/release planning, Configuration Control Boards (CCBs), and tracking and adjudicating Software Change Requests (SWCRs). Programmatic & Systems Planning: Developing, maintaining, and synchronizing project-level Roadmaps, Integrated Master Schedules (IMS), and capability delivery cadences. Focus Area 2: Systems Engineering & Requirements Architecture Technical Baseline Artifacts: Developing, updating, and managing formal engineering artifacts: Systems Engineering Plans (SEP). Software Development Plans (SDP) utilizing modern Agile/DevSecOps frameworks. System / Subsystem Definition Documents (SSDD). System / Subsystem Specifications (SSS). Software Product Specifications (SPS). Interface Requirements Specifications (IRS). Requirements Traceability Verification Matrices (RTVM) maintaining end-to-end bidirectional requirement-to-test traceability. System Safety Plans (SSP) conforming to MIL-STD-882E and naval weapon safety requirements. Requirements Allocation: Decomposing ICS, AEGIS, SSDS, and future combat system Top Level Requirements (TLR) into modular capability building blocks and subsystem specifications across surface ship classes (DDG 51, CG 47, FF(X), DDG 1000, L-Class, CVN, unmanned surface vessels, FMS variants, future platforms). Technical Leadership: Serving as lead technical authorities in Integrated Product Teams (IPTs), Working Groups (WGs), formal milestone reviews (SRR, PDR, CDR), and leading Technical Interchange Meetings (TIMs) to define and allocate interface requirements. Force-Level Mission Thread Analysis: Evaluating complex, distributed kill-chain mission threads, establishing functional allocations, and resolving tactical latency challenges. ICS Re-Architecture & Model-Based Systems Engineering (MBSE): Authoring SysML/UML MBSE models and leading modular product development across the ICS Domain Architecture. Sensor Management. Vehicle Management. Information Management. Training Management. Tactical Decision Management. External Communications Management. Weapon Management. Display Management. Infrastructure Services. Focus Area 3: Fleet Data Analysis, Feasibility Studies & Gap Assessment Conducting engineering feasibility studies, system performance assessments, and trade studies for capability insertion across diverse ship classes and configurations. Extracting, parsing, and analyzing live fleet exercise data, weapon telemetry, and real-world tactical events to identify performance anomalies and drive capability enhancement. Assessing combat system shortfalls, bottlenecks, and operational gaps, and designing/evaluating candidate architectural and software modifications to close these gaps. Focus Area 4: Tactical Software Design, Coding, Testing, and Integration Combat System Design activities including analysis and algorithm development Mission software development, unit testing, and component integration. Cloud-based and Hardware-in-the-Loop (HWIL)-based testing to include element integration, subsystem testing, and system testing System Integration: Engineering and integrating software interfaces for specific sensor, weapon, and C2 programs and capabilities, including but not limited to: Patriot Advanced Capability-3 Missile Segment Enhancement (PAC-3 MSE) The Standard Missile (SM) Family of weapons (including all Air Defense, Ballistic Missile Defense, and Extended Range Active Missile variants) MK-41 VLS-compatible canister-launched weapons (including Evolved SeaSparrow Missile (ESSM), Tomahawk Land Attack Missile (TLAM), and Vertical Launch ASROC (VLA) Rolling Airframe Missile (RAM) Electronic Warfare (EW) systems Phased array and rotating radar systems Evolving to common track management solution across AEGIS and SSDS configurations Containerized payloads Tactical Virtualization Configurations: Designing, provisioning, benchmarking, and troubleshooting virtualized tactical hardware/software configurations and hypervisor-to-bare-metal runtime environments. Focus Area 5: Hardware/Software Tech Stack, Microservices & System-of-Systems Integration Third-Party Software & Microservices: Evaluating commercial and third-party software products, conducting compliance refactoring, and defining standardized, ICS-compliant APIs to support microservices orchestrated via Kubernetes. Hypervisor Integration: Integrating and tuning alternate hypervisors (e.g., VMware ESXi, KVM, bare-metal container engines) to meet strict real-time deterministic performance requirements. Full-Stack System-of-Systems (SoS): Ensuring the integrated tech stack (hardware compute blades, switching fabric, hypervisors, orchestrators, microservices, and tactical applications) fulfills holistic combat system operational requirements. Leading technical forums to establish cross-contractor deliverable interfaces, lead-ship integration agreements, and deployment schedules. Focus Area 6: Modeling & Simulation (M&S) Developing, maintaining, validating, and updating high-fidelity simulations and functional simulators. Conducting system-level, ship-level, and force-level performance simulations…
Go deeper on this solicitation
FedSift reads the full solicitation package — every attachment — and pre-extracts the compliance matrix, evaluation factors, key risks, win themes and deal-breakers, each with a verbatim quote and the exact PDF page it came from. It scores the opportunity against your company profile, tells you whether to bid as prime or sub, and ranks teaming partners who could close your gaps.
Source: this notice on SAM.gov. FedSift republishes public federal procurement data and is not affiliated with the U.S. Government. Always confirm dates and requirements against SAM.gov before responding.
