• Q2 now clarifies there is no standard Phase II template for this topic; the referenced Direct-to-Phase-II instructions are the topic’s Component Instructions.
• The answer adds that CMMC Level 2 (Self) is required and corrects the Solicitation Instructions cross-reference: Section 5.2 should point to Section 2.6, not 2.13. It also says the annual affirmation of compliance with NIST’s 110 security requirements must be satisfied by contract award if it was not satisfied for a 2026 past award. Applicants should check their CMMC status and use the Component Instructions when preparing the submission.
• The Customer Memorandum remains not required.

• Added five Focus Area 2 questions about priority software artifacts and platforms, security and data handling, demo success criteria, machine-readable results, and identifying foreign or adversarial contributions. No answers are shown for these questions.
• Added a D2P2 submission question covering templates, Customer Memorandum requirements, CMMC Level 2, and whether a posted NIST 800-171 self-assessment score is sufficient. The answer clarifies that a Customer Memorandum is not required for this Specific Topic solicitation; the other parts do not have a complete answer in the update.
• Added three questions on disconnected Focus Areas 3 and 8 operations: preserving audit links between evidence, decisions, and response actions; recording operator authorization details; and enforcing and reconciling operator roles and mission authority. No answers are shown.
• Existing Q&As are renumbered; the prior Focus Area 8 integration question is retained as Q6. These additions flag unanswered points applicants may need to clarify, while the Customer Memorandum answer confirms it is not a required submission item.

Description information changed.

Key Q&A Updates for DV512:

• New Q1 (Technical Volume & Data Access): Technical Volume (Volume 2) capped at 20 pages. Government clarified that Elastic data specifics—which indices, ECS field sets, environment, and timing—will be provided (answer text incomplete in update).

• New Q2 (ITAR & Solicitation Version): DD Form 2345 application in progress is acceptable at submission if certification pending, but early filing encouraged to avoid award delays. Applicants must follow the newest solicitation release version for Direct-to-Phase-II feasibility documentation.

• Removed Q12 (Focus Area #5 Phase I Feasibility): Question about acceptable Phase I evidence for demonstrating feasibility was removed—likely to be addressed separately or in component instructions.

Why it Matters: The 20-page technical volume limit is a hard constraint for proposal planning. ITAR compliance timing is critical for award—start DD Form 2345 immediately. Use the current solicitation release for all compliance documentation.

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.

Q&A Changes Summary

New Question Added:

• Q1 (Focus Area #5): Clarifies whether Phase II should support defined Space Force formats or an extensible, source-agnostic transformation layer. Government will accept Phase I demonstration using heterogeneous representative formats with measured normalization performance, provenance tracking, and queryability, with mission-specific adapters integrated in Phase II.

Reorganization:

• Previous Q1 (Focus area #7 rationale) moved to Q2
• Previous Q2 (character-limit pending response) moved to Q3 with answer provided
• All subsequent questions renumbered (Q3→Q4, Q4→Q5, etc.)

Key Clarification in New Q1: Offerors may propose extensible approaches without Government-provided Space Force-specific interfaces pre-award, using representative data to demonstrate feasibility.

Q&A Changes Summary

New Question Added:

• Q1: Rationale for pursuing Focus Area #7 (AI-Driven Digital Supply Chain Illumination) through SBIR vs. alternative acquisition paths

Restructured Content:

• Previous Q1-Q6 renumbered to Q2-Q7 (all other questions remain substantively unchanged)
• Q6 answer regarding Focus Area #5 Phase I feasibility evidence appears truncated in updated version (ends mid-sentence at "validation...")

No Material Answer Changes: Responses to questions about multi-focus-area submissions, service-branch validation equivalency, CUI dataset availability, product-mission fit validation, and Focus Area #5 data model/performance requirements remain consistent with previous version.

Summary of Q&A Changes

New Q&A Added:

• Q1: Clarified Phase I feasibility evidence for Focus Area #5, including acceptable forms of documentation (technical feasibility, test results, performance metrics, stakeholder feedback, integration plans) without prescribing specific minimums.

Updated Answers (Previously Pending):

• Q4 (CUI Dataset): Government will NOT release hackathon dataset during proposal period; data may be provided to selected awardees post-award.
• Q5 (Product-Mission Validation): Prior USAF/USSF demonstration NOT required; validation acceptable via documented feasibility, use-case mapping, integration planning, and test evidence.
• Q6 (Focus Area #5 Technical Details): Added comprehensive guidance on data models (offerors propose their own), Government dataset availability (not guaranteed; synthetic data acceptable), "adaptive" engine criteria (diverse format onboarding with minimal core modifications), and performance thresholds (not prescribed; will be coordinated with awardees).

Key Clarifications: Offerors have flexibility in technical approach; validation doesn't require prior Government testing; Phase II details will be coordinated post-award.

Q&A Changes Summary

New/Updated Answers:

• Q7 (Focus Area 3): Added detailed answer clarifying that solutions need not independently provide full monitoring-detection-response lifecycle; complementary/modular capabilities addressing authorization, decision logic, or execution control are acceptable if they integrate with existing systems and clearly define scope, interfaces, dependencies, and autonomous-operation safeguards.

• Q8 (Test Environment): Added answer stating Government cannot guarantee forward-site network or DIL environment access; proposers must furnish their own representative test environment capable of operating under isolated/disconnected/bandwidth-constrained conditions. Government pursuing integration capabilities and may coordinate access with selected performers if available.

• Q9 (Focus Area 8): Added comprehensive answer clarifying Focus Area 8 seeks portable defensive cyber operations/hunt capability (not inline enforcement appliance); must support rapid network discovery, characterization, security posture assessment in disconnected environments. Clarified that integrated Focus Area 6+8 proposals will be scored per solicitation criteria.

Previously Unanswered Questions Remaining: Q3, Q4, Q5, Q11 still pending responses.

Q&A Changes Summary

New questions added (3):

• Q1: Evaluation of multi-focus-area solutions
• Q2: Cross-service validation acceptance (Army vs. USAF/USSF)
• Q10: Evidence types satisfying DAF stakeholder validation for Phase I feasibility

Key clarifications in new answers:

• Multi-focus-area proposals evaluated independently; cross-cutting impact should be clearly communicated
• No preferential weighting for USAF/USSF validation; any service branch validation equally valid
• Feasibility can be demonstrated through logical proof of technical and contractual feasibility without prior DAF engagement (flexibility noted)

Questions reordered: Previous Q2-Q8 renumbered to Q3-Q11; no content changes to existing answers.

Added 4 new Q&As: (1) CUI dataset availability from AFRL hackathon; (2) D2P2 product-mission validation evidence requirements; (3) Focus Area #5 data model standards, performance thresholds, Phase I feasibility criteria, and adaptive engine evaluation; (4) On-Orbit Space Logistics Challenge topic number clarification (DAF26BX06-DV513). Previous Focus Areas 3, 8, and 6 questions retained.

These Q&A clarifications allow applicants to understand flexibility in solution scope (complementary vs. standalone capabilities), identify what resources the Government will vs. won't provide (test environments), and seek specificity on end-user context and evaluation criteria to better tailor their proposals to actual requirements.

New opportunity: Cyberspace Warfare for Space