Modular Payloads for UAS

Opportunity ARM26BX01-NV002 no longer available

# Q&A Changes Summary **5 new questions added:** 1. **Software/AI payload safety assessment scope** - Clarifies no simplified template exists; awardees can work with government stakeholders under contract. 2. **UVC compatibility timing** - Confirms UVC is a desirable Phase II improvement, not a Phase I requirement; Phase I focuses on proof of concept. 3. **Soldier feedback documentation** - Army has no preference on methodology for capturing and integrating Soldier feedback. 4. **Software-only payload eligibility** - Confirms proposals with core software/AI/HMI innovation are acceptable if they offer offensive/defensive advantage. 5. **AI-augmented EO/IR payload eligibility** - Clarifies AI inference and interface design innovations are responsive under "novel payloads" if integrated with UAS and CLIK-compliant; standalone software not accepted. **Key clarification:** Software-heavy payloads are eligible provided physical CLIK integration is credible and the solution integrates onto a UAS.

# Q&A Changes Summary **New Questions Added (Q2-Q5):** - Q2: Clarifies "end-to-end solution" requires payload with compute and software capability integrated via Picatinny CLIK - Q3: Confirms no specific latency budget declared for communications relay payloads - Q4: States Army cannot provide feedback on EMCON/LPI/LPD prioritization approaches - Q5: Clarifies network discovery protocols (SSDP, Zeroconf, MQTT) are vendor-selected, not required **Renumbering:** Original Q2-Q8 renumbered to Q6-Q11 due to new questions inserted at top. **No Answer Changes:** All previously published answers (now Q6-Q11) remain identical to original Q2-Q8. **Key Clarification:** New Q2 explicitly requires payloads to integrate compute/software capability—not just transparent pass-through devices.

# Q&A Changes Summary **New additions:** - Q1: Added webinar recording link for AAL modular payloads UAS topic - Q8: New question added (incomplete in provided text) regarding Cyber Security/Supply Chain requirements and NDAA Section 884/889 compliance for Phase I **Reorganization:** - Previous Q2-Q7 renumbered to Q2-Q7 in updated version - All previous answers retained without modification **No substantive answer changes** to existing questions about kinetics, CLIK specifications, video encoding, cybersecurity requirements, prototype maturity, or payload compliance standards.

Status changed from Pre-Release to Open

**New Q&A Added (Q1-Q2):** Q1 clarifies payload scope: excludes kinetic/strike payloads and terrain shaping via explosives; confirms MOSA requirement per 10 USC 4401; states TRL 6 as Phase II endpoint; declines to provide feedback on specific approaches or funding estimates. Q2 addresses program context, video standards, and operational environment: states program context not publicly available; reiterates CLIK's 100mbps ethernet with no specified encoding standard; confirms no target operational environment envelope provided. **Reorganization:** Previous Q&A Q1-Q7 renumbered as Q3-Q9 with identical content preserved.

# Q&A Changes Summary **New Questions Added (3):** 1. **CLIK Manufacturing & Design for Manufacturing (Q1):** Clarifies that traditional CLIK is a functional specification, not a physical device. Only the Picatinny rail and connector are specified hardware. CLIK Lite (sUPI) variant does specify custom mount/electrical interface with potential manufacturing feedback opportunities. 2. **Video Compression & Network Architecture (Q2):** Clarifies that CLIK defines 100mbps ethernet at platform/payload interface but neither specifies nor limits video compression approach or offboard data transfer rates—proposers should consider bandwidth tradespace. 3. **Data Availability, Cybersecurity, & Prototype Maturity (Q3):** Government will not provide data for development/testing. CLIK does not specify cybersecurity requirements (external to standard). Phase II expected to achieve TRL 6; Phase I is planning/design focused. 4. **Standards Compliance & CLIK Connectivity (Q4):** Clarifies distinction between DoW Modular Payload Standard vs. Picatinny CLIK compliance. CLIK provides network interface to ground station (shared or dedicated radio). ATAK not required. Rail provides no direct inter-payload communication; IP-based backbone enables network communication. **Key Clarification:** Phase I emphasizes technical design and planning; prototyping/demonstration deferred to Phase II.

# Q&A Changes Summary **New Question Added:** - Q1 (New): Clarifies Phase I budget and timeline limits—firms must not exceed the 3-month base period or $150K cost limit. Also confirms that Army-specific proposal format instructions take precedence over general DoD format instructions. **No other substantive changes.** Questions Q2–Q5 and their answers remain identical to the previous version. All other Q&As (covering CLIK compliance emphasis, payload types, kinetic weapons eligibility, GFE platform details, travel budgeting, and use of COTS components) are unchanged.

**Summary of Q&A Changes:** Added 5 new Q&As clarifying Phase I scope, evaluation criteria, and logistics: - Phase I focuses on integration planning and design, not prototyping (Phase II activity) - No requirement to address multiple payload types; proposers should submit their best solution - Kinetic payloads/strike weapons remain ineligible - Government-furnished UAS and technical materials provided post-award - In-person final presentation in Austin, TX (May 6–June 3 submission window; budget one trip) - Commercially available components acceptable if Phase I deliverables met - SWaP-C reduction noted as desirable but not mandatory evaluation factor

**Changes to Q&A Section:** Added webinar registration details (29 APR 2026, 10:00 AM CT). Added new Q&A clarifying Phase I scope: focuses on payload integration planning and TRL improvements, with actual UAS integration deferred to Phase II (targeting TRL 6 by end of Phase II). Reordered existing Q&As for organization.

Added 4 new Q&As clarifying: C-UAS payloads are acceptable but kinetic/strike weapons excluded; Group 4/5 UAS platforms not considered; Phase I submission only (no Direct to Phase 2); Picatinny CLIK specification download links provided.

This Q&A clarifies that companies with existing payload systems must still submit Phase I proposals rather than proceeding directly to Phase II for this funding opportunity.

Content updated: description

Close Date changed from 2026-04-22 to 2026-06-03

Open Date changed from 2026-03-25 to 2026-05-06

Status changed from Removed to Pre-Release

Opportunity ARM26BX01-NV002 no longer available

New opportunity: Modular Payloads for UAS