The only change is that Q1 received its first answer. Previously it was unanswered; now the government states that vendors may propose trade studies or other objective, multi-variable analyses to compare alternative approaches and show how each addresses the mission need.

Why it matters for applicants:

• Submitting multiple avenues of approach in one technical proposal is effectively answered as acceptable, but only in the form of comparative trade studies or objective multi-variable analyses, not as several unrelated full proposals.
• Teams considering multiple approaches should frame them as a tradespace comparison that maps each option to the mission need, which also aligns with the CONOPS trade-study expectation noted in Q13 and Q7.

• Added a question asking whether applicants may submit multiple approaches in one technical proposal. No answer is shown, so applicants do not yet have confirmation that multiple approaches are allowed.
• Updated the Phase I deliverables and transition answer: it now begins by saying deliverables will be determined at the start of Phase I based on the vendor’s proposal. The answer is truncated in the supplied version, so its remaining guidance is unclear.

• Q1’s answer now states directly that Phase I deliverables require CMMC Level 2 (Self) protections. The prior answer also said this, while explicitly describing the deliverables as CUI; applicants should still plan for Level 2 protections.
• Q22 is now shown as asking about personnel, information-handling, and system-access prerequisites for Tap Lab participation. Its answer is truncated to “A...” in the provided update, so no guidance on those prerequisites is visible.

Description information changed.

Description information changed.

Added 1 Q&A on proposal formatting (submission rules):

• New Q1 addresses conflicting guidance on Technical Volume page limits. The answer clarifies that proposals must follow the "Space FY26 SBIR Phase I Proposal Template" with no independent page limit outside the template itself—resolving prior confusion about 10 vs. 13 pages.

Removed/Renumbered 3 Q&As: Questions on baseline datasets, mod/sim environments, and on-site Boulder Lab requirements were consolidated or removed, shifting subsequent question numbers down by 3.

Key impact: Applicants should use only the official FY26 SBIR Phase I template and disregard earlier page-limit guidance. This simplifies compliance but requires reviewing the template directly for format rules.

Major Changes to Q&A:

• Phase I on-site requirement removed (Q4): Previously unstated; now clarified vendors are NOT required to be on-site at Boulder OPIR TAP Lab during Phase I.

• Phase I deliverables flexibility (Q5): Simulation results are optional; CONOPs with trade studies and analytical findings alone are sufficient.

• Government less prescriptive (Q6): Topic now explicitly open to any OODA-loop solution maintaining mission assurance—not limited to fusion/tracking algorithms specifically.

• No preferred baseline dataset (Q2): Government does not provide reference baseline; vendors choose their own data approach.

• Phase I data access broadened (Q21, Q24): Performers may use "whatever data they choose" to represent concepts; not limited to government-furnished data.

• TAP Lab technical specs deferred (Q17): Software interfaces, data schemas, and packaging requirements will be discussed during Phase II, not before proposal submission.

• Performance criteria vendor-defined (Q19): Accuracy, false alerts, latency evaluated using "vendor-defined criteria" with government discussion during Phase I.

• Removed 12 prior Q&As: Questions 1-14 from previous version deleted entirely, replaced with 26 new questions.

Key implications: Phase I is now lower-barrier (no on-site requirement, flexible deliverables, vendor-defined metrics), but Phase II requires TAP Lab integration with physical presence.

Q&A Changes Summary

Major reorganization: The 14 Q&As were restructured and renumbered, with 6 new questions added at the beginning addressing Phase I data access and deliverables.

Key new guidance:

• Phase I data: Vendors may use unclassified/synthetic OPIR-representative data, ASSET synthetic data, or generate their own—government will not provide data (Q1, Q4)
• Government-furnished algorithms: If Phase I succeeds, the government will make tracking and fusion algorithms available in Phase II (Q2)
• In-space edge-compute scope: Confirmed responsive—approaches for orchestration layers to host algorithms (not developing new algorithms) are in scope (Q3)
• Track/tasking standards: Government seeks vendor innovation; no preferred standard mandated (Q6)
• TAP Lab access timing: Clearly stated access and onboarding occur in Phase II only, not Phase I (Q5)

Why it matters: These additions reduce ambiguity on Phase I feasibility and data strategy. Vendors can now confidently propose using synthetic datasets without requesting government data. The confirmation that edge-compute architecture proposals are acceptable expands eligible solution types beyond algorithm development.

Q2 (Technical Volume Page Limit) — Updated Answer

The page limit clarification now specifies two sequential requirements:

• Initially: 10 pages (pending topic change request processing)
• After change request approval: 13 pages maximum, following the SBIR/STTR PHASE I PROPOSAL TEMPLATE

Why it matters: Applicants should expect the final limit to be 13 pages, not the previously stated 10 pages. Monitor for the Component Instructions update confirming the change request approval before finalizing proposals.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Status changed from status: Pre-Release to status: Open.

Description information changed.

Description information changed.

Both Q1 and Q2 received answers clarifying scope responsiveness. Q1 now confirms in-space edge compute architecture is eligible and recommends DoDAF 2.0 documentation for integration pathways. Q2 confirms mission-aware orchestration and AI-assisted decision management (without new algorithms) are appropriate for submission.

Added new Q1 clarifying in-space edge compute architecture scope: infrastructure for hosting/executing algorithms on-orbit is responsive, with guidance requested on demonstrating integration/testing paths in OPIR Tap Lab. Original mission-orchestration question moved to Q2.

This Q&A clarifies that applicants can pursue Phase I projects emphasizing AI-driven orchestration and resource optimization rather than novel algorithms, expanding eligible research approaches within the OODA Loop focus area to include dynamic sensing and processing allocation strategies.