Platform-Agnostic, Open Architecture, Advanced Automated Search & Track and Target Recognition Enhancement for Airborne, Fixed-Wing Special Operations Applications

**Q&A Changes Summary:** Only one substantive change: **Q5 received a new answer** clarifying that MX-20D and MX-25D are the only video sources for this effort. **Q6 received a detailed new answer** specifying that AC-130J integration and flight evaluation are required during D2P2, with prototype roll-on/roll-off capability and defined SWaP constraints (Threshold: 6U, Objective: 2U air-cooled computers).

# Q&A Changes Summary **Key change:** Answer to Q7 moved from unanswered to answered. The government clarified that focusing only on air-to-air detection/classification is non-responsive—a complete end-to-end solution across all modes (ground, maritime, air-to-air) is required. This answer duplicates the guidance already provided in A8, reinforcing the comprehensive solution requirement.

Q8 received a new answer clarifying that bidders must propose a complete end-to-end solution addressing all requirements, not just partial solutions. Partial proposals will be considered non-responsive.

Added 6 new Q&As: retraining vs. inference-only capability, alternative aerial platforms for testing, specific model architecture requirements, video data availability/extent, sensor sources beyond MX-20/MX-25, and AC-130J integration timeline/form factor during Phase II.

Two new questions added: Q1 asks about air-to-air detection/classification focus (previously unanswered), and Q2 repeats the earlier partial-solution question (now numbered differently). All other Q&As renumbered accordingly with no answer changes.

Added 1 new Q&A on solution scope: partial innovative solutions may be responsive. Existing answers on LLM roles, aircraft focus (AC-130J), and post-demonstration risk management specifications were renumbered but unchanged.

Q1 received a new answer clarifying that LLM optimization of ATR is optional—vendors can choose their own ATR-optimization paths to reduce operator workload and accelerate the kill chain. Q2 and Q3 answers remain unchanged.

Added Q1 asking Government to clarify the intended role of large language/foundation models in the search & track pipeline. Previous Q&A on ISTAR/AC-130J integration and post-demonstration risk management specifications remain unchanged.

Status changed from Pre-Release to Open

Added answers to 2 existing Q&As: Q1 clarifies the topic focuses on AC-130J Ghostrider aircraft integration; Q2 confirms risk management and audit trail specifications will be developed post-demonstration rather than pre-defined.

Added new Q1 about ISTAR advancements in Group 1 & 2 fixed wing aircraft. Original AI RMF/DoDI 8510.01 compliance question moved to Q2 (answer status unchanged).

This Q&A addresses ATO compliance requirements for AI systems, asking whether risk management must cross-reference both the NIST AI RMF and DoD RMF frameworks, and whether continuous monitoring/automated auditing is needed for model drift and data provenance at tactical edge deployments.

New opportunity: Platform-Agnostic, Open Architecture, Advanced Automated Search & Track and Target Recognition Enhancement for Airborne, Fixed-Wing Special Operations Applications