Collaborative IAMD Planning Program RFI_NAVWAR.pdf

NAVWAR HQCA-2024-A-160 Distribution Statement A. Approved for public release: distribution is unlimited. (25 NOV 2024)

REQUEST FOR INFORMATION

PMW 150 Collaborative Integrated Air and Missile Defense (IAMD)

Planning Program (CIPP)

1.0 Description

1.1 Overview

The Naval Information Warfare Systems Command (NAVWAR) in support of the Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO C4I) Program Manager, Warfare (PMW) 150, Command and Control Systems Program Office, is releasing this Request For Information (RFI) to facilitate the development, prototyping, production, support and sustainment of software solutions to satisfy Collaborative Integrated Air and Missile Defense requirements.

1.2 Request for Information Limitations

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes and does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to contract for any supply or service. Respondents are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued.

2.0 Background

CIPP provides Integrated Air and Missile Defense (IAMD) planning capabilities to U.S. Navy (USN) commanders and their staffs, via the delivery of a suite of software applications. CIPP’s software enables commanders to dynamically develop and assess force-level AMD plans.

Overarching capabilities provide collaborative planning across ship, strike group, and higher headquarters afloat and ashore. Following initial delivery of the CIPP Minimum Viable Capability Release (MVCR), the program office will deliver capability-focused updates that are rapidly developed and fielded through a Development, Security, and Operations (DEVSECOPS) pipeline. CIPP is a suite of AMD planning tools that will leverage and interface with a wide range of authoritative data sources and tactical communications networks that connect those data sources. As a software-only program, CIPP will rely on compute, memory, network, and storage resources from USN enterprise Infrastructure as a Service (IaaS)/Platform as a Service (PaaS) programs (e.g., Consolidated Afloat Network and Enterprise Services (CANES), Agile Core Services (ACS), and other approved infrastructure ashore). CIPP software is integrated and fielded with the Navy’s premier operational to tactical level planning system, the Maritime Tactical Command and Control (MTC2) Tactical Planning Tool (TPT).

NAVWAR HQCA-2024-A-160 Distribution Statement A. Approved for public release: distribution is unlimited. (25 NOV 2024)

2.1 Technical Requirements/Performance Specifications

The program is interested in applying Artificial Intelligence (AI) technology solutions to both increase the effectiveness of and reduce the time required to conduct IAMD planning in the Fleet and to war-game friendly Courses of Action (COA) and Enemy Courses of Actions (ECOA).

This emergent requirement is driven by a national strategic initiative to ensure the Fleet’s readiness in the tactical edge of warfighting.

In support of this mission, the program seeks solutions from Industry that meet the following performance requirements either through mature technologies, existing technologies that can be modified or redesigned to meet requirements, or the development of a new product.

The primary performance specifications for the AI based system to support and automate the phases of the Navy’s IAMD Mission Planning Process at both the unit and force levels. Desired capabilities include:

A. Mission Analysis Capture and display intelligence estimates and data associated with predictions of enemy air and missile threats. Automated ingestion of data from relevant DoD/Intelligence Community (IC) websites, planning systems, and third-party analytical tools is preferred where available, but manual entry of data must be provided.

Capture blue (Friendly) force IAMD asset availability, capability, readiness, positioning, and tasking data related to the mission. Automated ingestion of data from relevant DoD/IC websites, planning systems, and third-party analytical tools where available, but manual entry of data must be provided.

Develop and establish a wide range of meaningful customized commander’s intent & guidance, rules of engagement (ROE), and metrics to be used in the COA analysis, comparison, and selection process.

o Establish and/or select a set of orders/tasks associated with IAMD and within the ROE to drive wargaming scenarios.

o Establish and/or select a set of metrics against which the system would measure blue force performance in wargaming scenarios.

B. COA Development Allow operators to develop and simulate realistic red force ECOAs, including various aspects of force employment, coordination, and attack profiles.

Allow operators to develop and simulate realistic blue force COAs, including various aspects of asset deployment, coordination, and engagement tactics, covering the full spectrum of Navy Air Defense (AD) and Ballistic Missile Defense (BMD) task types.

Allow the IAMD planner to replicate blue and red force COAs (i.e., forces involved, asset positioning and tasking, asset configuration, tactics, etc.) in order to rapidly develop alternate COAs and conduct replanning.

C. COA Analysis Seamlessly integrate with and leverage existing and future third-party custom models of blue force IAMD platforms, combat systems, sensors, and effectors to model blue IAMD COA performance against anticipated red force COAs in support of

NAVWAR HQCA-2024-A-160 Distribution Statement A. Approved for public release: distribution is unlimited. (25 NOV 2024) simulation, and analysis. Where required, the proposed solution should also support the development and integration of new models.

Seamlessly integrate with and leverage existing and future third-party custom models of red force platforms, combat systems, sensors, and weapons to model red force attack ECOAs. Where required, the proposed solution should also support the development and integration of new models.

Provide realistic simulation of both blue and red forces in the IAMD mission area, incorporating sophisticated AI agents that can learn, adapt, and respond to evolving situations within the simulation.

Allow IAMD planners to create constraints and restraints within a war gaming scenario to simulate blue force COAs against the anticipated ECOAs over a customized time period, to include but not limited to: evaluation of potential effectiveness against operator tailored metrics, identify potential weaknesses in the blue force COAs vs. Rules of Engagement (ROE), and Commander’s intent, etc.

Allow IAMD planners to simulate and visualize complex missile raids and assess blue force performance using a range of relevant metrics.

Collect and analyze incremental COA metrics data throughout the war gaming scenario runs and compile and analyze final COA metrics data at the end of war gaming scenario runs.

Provide mechanism for user-controlled “playback” of the war gaming simulation, including adjustable time scales (slow/fast speed), stop/start controls, forward/rewind controls, etc.

Provide alerts to planners which highlight critical events, decision points, metrics boundaries, potential risks, and recommended responses or adjustments within the war gaming scenario.

Provide recommendations to planners for unit-level and force-level sensor placement/configuration and effector selection/employment to provide optimal defense against the red force ECOAs.

D. COA Comparison and Selection Provide the IAMD planner with meaningful, intuitive display of metrics and analysis results data collected from war gaming scenarios to assist in evaluating the effectiveness of blue force COAs.

Provide side-by-side display of COA metrics and analysis results data collected from war gaming scenarios to support COA comparison and for presentation to senior leadership to support COA selection.

Provide simultaneous, side-by-side “playback” of war gaming scenarios to highlight differences between COAs in simulation time in support of COA comparison and selection.

Automatically develop, display, and export worksheets and other required products required from the settings used to drive the wargaming scenario to support IAMD planner preparation for and execution of local Doctrine Review Boards (DRB).

E. Transition to Execution Provide for export of COA/planning data (i.e., organization, asset positioning and tasking, asset configuration and doctrine, etc.) in customizable electronic formats (i.e.

.json format) for ingestion by external combat and C2 systems to support transition to execution.

NAVWAR HQCA-2024-A-160 Distribution Statement A. Approved for public release: distribution is unlimited. (25 NOV 2024)

Provide for export of COA war gaming results data for electronic sharing with external commands and for ingestion into briefs and documents.

3.0 Requested Information

The program is interested in whether industry can apply AI technology solutions to both increase the effectiveness of and reduce the time required to conduct IAMD planning that meets the requirements in Section 2 of this RFI to support the urgent need to ready the Fleet. Please submit information regarding existing corporate capabilities, Commercial Off-The-Shelf (COTS) or Non-Developmental Item (NDI) solutions, services, experience, and recommendations related to the delivery of a partial or full solution to the requirements described in Section 2 of this RFI.

Additionally, the proposed solution will need to be accessed/timeshared by more than one terminal or central processing unit. The integration of the software will be completed across multiple DevSecOps environments with multiple commands.

In white paper format, please address each of the following.

A. Provide the name and description of your solution’s item(s) (if already developed).

B. Describe how you would implement innovative technical solutions to meet the requirements in Section 2.

C. Provide examples demonstrating experience in developing, integrating, fielding, and sustaining complex software systems.

D. Provide examples demonstrating past performance in meeting government schedules.

E. Provide examples demonstrating experience developing AI systems.

F. Provide examples demonstrating successful government/contractor collaboration on DoD programs using Agile software development processes.

G. Describe any prior experience developing software that integrates with an established software baseline.

H. Describe any prior experience developing systems fielded in the operational environments described in Section 2.1.

I. Describe any successful experience you have had in working with and/or incorporating capabilities that transition from the Science and Technology (S&T) environment such as Future Naval Capability (FNC), Small Business Innovative Research (SBIR), and Rapid Innovation Fund (RIF) into systems you have developed, if applicable.

J. Describe any potential COTS solutions that may support the requirements as described in Section 2.

K. Provide any relevant developmental and operational test data for existing solutions along with its description (if applicable).

L. List all other entities and DoD components that are using the item(s) (if any).

3.1 Data Rights

The Government’s objective is to have the ability to maintain and advance contract solutions for the least total ownership cost over the anticipated 30+ year life of the system. Data rights are an important part of that ownership cost, as such, an interested party should describe what technical data/computer software they are willing to deliver to the Government as part of its solution.

NAVWAR HQCA-2024-A-160 Distribution Statement A. Approved for public release: distribution is unlimited. (25 NOV 2024)

RFI responses which include solutions incorporating commercial computer software (including open-source software) shall also include, as part of the response, all Commercial or Open-Source License Agreements applicable to the described capability. Such license information will not be included in the response submittal page limit.

3.2 Technical Support

The Contractor shall perform work at the unclassified and at the Secret classified level. The Contractor must have access to classified facilities and networks to be able to conduct the classified portions of work. The Contractor may be tasked to conduct independent development, integration, and testing of classified systems that will be delivered as independent products. The Contractor shall adhere to Government-directed agile development and system engineering processes.

4.0 Responses

4.1 Submission

Interested parties are requested to respond to this RFI with a white paper. White papers are due no later than 30 JAN 2026 at 2:00 PM Pacific Daylight Time (PDT) and will only be accepted via email or DoDSafe to Rachel Jimenez (rachel.r.jimenez5.civ@us.navy.mil) and Christopher Auen (christopher.d.auen.civ@us.navy.mil). Only responses at the unclassified level will be accepted. Proprietary information and proprietary components shall be clearly identified and marked. Components that are marked proprietary must be accompanied by a reason for the markings. Responses shall not include any CLASSIFIED information. Please be advised that all submissions become Government property and will not be returned.

4.2 Format

White papers shall be in Microsoft Word for Office format, comprised of two sections (detailed below) that total no more than 10 single-sided pages, not including enclosures, with 12 pt. Times New Roman font, normal 1” margins on 8.5” x 11” paper.

4.2.1. Section 1

Respondents shall provide administrative information and shall include the following, at minimum in Section 1 of the white paper:

Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail address of designated point of contact.

Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, Historically Underutilized Business Zone (HUBZone) small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 334511 Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing and PSC Code 7E20 (It And Telecom – End User: Help Desk; Tier 1-2, Workspace, Print, Productivity Tool (Hardware/Perpetual Software)). Please refer to 13 Code of

NAVWAR HQCA-2024-A-160 Distribution Statement A. Approved for public release: distribution is unlimited. (25 NOV 2024)

Federal Regulations Part 121 and Federal Acquisition Regulation Part 19 for additional detailed information on Small Business Size Standards.

Company size and head count.

Experience and expertise in carrying out similar efforts for the Government.

Describe current contractor Facility Security Clearance access, status, and classification level.

If the product has been delivered to a federal customer, please provide the contract number, Contracting Officer’s Representative’s (COR) name, and contract information.

4.2.2. Section 2

Section 2 of the white paper shall include the requested information outlined in Section 3 Requested Information (above) of this RFI.

4.2.3. Proprietary Data Protection Agreements (PDPA)

Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. If any respondent does not currently have a Proprietary Data Protection Agreement (PDPA) that would permit the NAVWAR support contractors listed below to review white papers submitted in response to this RFI, the respondent is requested to sign PDPAs with these NAVWAR/NIWC support contractors for this purpose. The following is a list of support contractor Points of Contacts who will review the responses.

Company Name Telephone

Number Email Address

General Dynamics Information Technology

Jessica Tirado (619) 988-9427 Jessica.c.tirado.ctr@us.navy.mil

Highbury Defense Group

(HDG)

James Timothy Pierce

(703) 559-5983 james.t.pierce4.ctr@us.navy.mil

Highbury Defense Group

(HDG)

Shawn Davis (619) 818-6434 shawn.r.davis.ctr@us.navy.mil

Highbury Defense Group

Beth Denys (206) 992-2848 beth.l.denys.ctr@us.navy.mil

32 North Solutions

Gunjan Pagan (706) 358-3105 gunjan.pagan.ctr@us.navy.mil

5.0 Industry Exchanges

NAVWAR HQCA-2024-A-160 Distribution Statement A. Approved for public release: distribution is unlimited. (25 NOV 2024)

Government representatives may or may not choose to meet with respondents. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks.

If you are interested in offering a demonstration of potential solutions that appear to be viable, please include this in your white paper response. Companies choosing to offer a demonstration will do so at their own expense. No compensation will be provided for demonstrations.

Demonstrations will be scheduled at the convenience of the Government. Depending on responses, the Government may or may not allow for demonstrations. A demonstration is not required for a company’s solution to be considered.

6.0 Questions

Questions regarding this announcement shall be submitted via email to Rachel Jimenez (rachel.r.jimenez5.civ@us.navy.mil) and Christopher Auen (christopher.d.auen.civ@us.navy.mil). Accordingly, questions shall NOT contain proprietary or classified information. Verbal questions will NOT be accepted. Questions will be answered on the Government public website via RFI Amendment. The Government does not guarantee that any questions received within 15 calendar days of the RFI closing date will be answered.