Mission Planning Tool Software

1.0 INTRODUCTION & PURPOSE

JIATF-401 (Joint Interagency Task Force) is seeking information on modern, web-accessible software solutions to support tactical mission planning, electromagnetic spectrum management, and Counter-UAS threat modeling.

1.1 FAR 52.215-3 Request for Information or Solicitation for Planning Purposes (Oct 1997)

The Government does not intend to award a contract on the basis of this solicitation or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the Federal Acquisition Regulation.

Although "proposal" and "offeror" are used in this Request for Information, your response will be treated as information only. It shall not be used as a proposal.

This solicitation is issued for the purpose of: Market Research and Acquisition Planning.

1.2 Administrative Disclaimers

• No Obligation: This RFI 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 whatsoever.


• Cost of Preparation: Responders 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.


• Proprietary Information: 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.

2.0 TECHNICAL REQUIREMENTS

The Government is conducting market research to identify software platforms capable of meeting the following Mission Planning Tool features:

1. Sensor & Effector catalog: Built-in library of current/commercial sensors & effectors; editable parameters (Tx/Rx band, power, elevation, antenna pattern/orientation, sensitivity); user-defined sensor creation.


2. Threat Catalog: Library of commercial UAS, state and non-state actors UAS, and configurable (user defined) threats (size, speed, elevation, modality).


3. AOI + Defended Zone tools: Draw/manage zones, standoff rings, and constraints directly on map.


4. Terrain: DTED L2/L3 support; Configurable Sea state (i.e., Beaufort Scale).


5. Files ingest capable: KMZ/KML ingest for infrastructure and reference layers.


6. Collateral Damage Estimation: Non-kinetic effects on environment, kinetic hazard areas.


7. MSS Ingestion: Can ingest threat locations / geometries from MSS.


8. EMS/RF modeling: Multi-band detection modeling against the environment and systems in the environment; illuminators of opportunity ingest/modeling for passive sensors.


9. Environmental effects: Band-dependent performance impacts for active/passive sensors; multiple sea states supported.


10. Automated sensor siting: Auto-placement within AOI to meet Defended Zone coverage (layered/overlapping/mutually supporting).


11. Spectrum planning: Frequency assignment recommendations; interference/conflict alerts (co-/adjacent-channel, overlap, jamming); civilian band constraints.


12. Optimization metrics: Optimizes plans using Pd (Probability of Detection) and Pk (Probability of Kill/defeat) informed by modeling and historical/empirical data.


13. Visualization: 2D/3D coverage and viewsheds; compare alternative plans.


14. Export + COP integration: CSV export of the sensor plan (locations, configs, frequencies, metrics); outputs formatted for Maven COP ingest.


15. Web-access + support: Web-based, accessible from government or civilian computers with token login; contractor support available.

3.0 QUESTIONS FOR INDUSTRY

Interested parties are requested to submit a capability statement addressing their ability to meet the technical requirements in Section 2.0. Additionally, please provide responses to the following questions:

1. Commercial Availability: Is your solution a Commercial-Off-The-Shelf (COTS) product, or does it require custom development?


2. Security & Cloud Compliance: What DoD Impact Level (e.g., IL4, IL5, IL6) is your software currently authorized for? Do you have an active Authority to Operate (ATO)?


3. Licensing Model: How is your software priced (e.g., per user seat, enterprise license, or annual subscription)?


4. Integration Timeline: What is your estimated timeline to achieve data export/ingest with government systems?


5. Company Profile & Socio-Economic Status: Please provide your CAGE Code, UEI number, and state your socio-economic status (e.g., Small Business, 8(a), SDVOSB, WOSB) under NAICS 513210. If you believe a different NAICS code is more appropriate for this requirement, please identify it and provide a brief rationale.

4.0 SUBMISSION INSTRUCTIONS

Responses shall be submitted via email to the primary point of contact listed below.

• Format: Submissions must be in Adobe PDF format.


• Page Limit: Responses shall not exceed 10 pages, excluding the cover page.


• Due Date: All responses must be received no later than 30 June 2026 at 1:00 PM EDT.

Points of Contact:

• Point of Contact: Louis E. Hernandez, CPT, EN, louis.e.hernandez14.mil@army.mil


• Contract Specialist: Julie Jenkins, julie.a.jenkins27.civ@army.mil


• Contracting Officer: David J. DiRoma, david.j.diroma.civ@army.mil