Mission Delta 2
Connecting Space Domain Awareness Challenges With Emerging Capabilities Through Technical Evaluation & Engineering Integration.
Combat Development Team (CDT)
What CDT Supports
Operator-informed capability discovery and assessment. Demonstrations, test evidence and technical SME engagement. Mission-system data, interoperability and integration feasibility, Coordination of viable capability transition pathways.
Purpose
MD2 mission-driven discovery and engineering assessment of relevant materiel and non-materiel capabilities.How CDT Works
Connects operators, technical specialists, system stakeholders and partners to examine value, constraints and applicability.Scope / Authorities
CDT supports evaluation and integration planning; formal acquisition, security, integration & fielding decisions remain with authorized owners.Primary Contact
What CDT Supports
Operator-informed capability discovery and assessment. Demonstrations, test evidence and technical SME engagement. Mission-system data, interoperability and integration feasibility, Coordination of viable capability transition pathways.
MD2 mission-driven discovery and engineering assessment of relevant materiel and non-materiel capabilities.
Purpose
Connects operators, technical specialists, system stakeholders and partners to examine value, constraints and applicability.
How CDT Works
CDT supports evaluation and integration planning; formal acquisition, security, integration & fielding decisions remain with authorized owners.
Scope / Authorities
Primary Contact
Capability Discovery Guidance
The MD2 Mission Challenges describe operational outcomes MD2 seeks to improve. They are intended to help industry organizations determine where existing or demonstrable capabilities may provide relevant mission value.
Organizations should identify only those Mission Challenges for which an existing or demonstrable capability has credible relevance. A narrow, evidence-backed fit is stronger than a broad generic claim.
Identify Relevance
Across all Mission Challenges, MD2 seeks to understand:
Organizations should be prepared to demonstrate what works today and clearly distinguish demonstrated functionality from developmental, prototype, or future-roadmap capability.
Demonstrate Current Capability
Provide Supporting Evidence
Supporting information should address demonstrated performance, current maturity, relevant use or testing, known limitations, and known dependencies. Representative or analogous operational environments are appropriate for initial engagement.
Current Capabilities
Available and demonstrable functionality
Evidence
Users, testing, deployment, outcomes
Operational Effects
Measurable outcome produced or intended
Integration Requirements
Data, interfaces, hosting, dependencies
Maturity & Scale
Readiness, volume, operational limits
Adoption Considerations
Training, licensing, support, sustainment
How to Engage with CDT
Industry Engagement Sequence
Review MD2 Mission Challenges
Identify a Mission Challenge your capability/offering resolves.Mission Relevance
Operator use case, expected benefit, existing use & comparison.Prepare Capability & Engineering Evidence
Summarize Technology, Maturity and Demonstrated results.
Performance Evidence
Demonstrations, test results, maturity, known limitations.Submit Unsolicited Capability & Request Form
MD2 Meeting Request.What To Prepare For Technical Discussion
Interoperability
Data inputs/outputs, formats, interfaces & dependencies.CDT Review & Response
CDT will advise on next steps.(Technical discussion, request for more information, etc.Integration Considerations
Hosting, security posture, workflow effect & sustainment.