The U.S. Air Force has formally designated two mission design series to guide future collaborative combat efforts, aligning platforms, data links, and tactics across joint forces. These designations establish a repeatable framework for rapid integration of crewed and uncrewed capabilities in high-threat environments.
This structured approach enables clearer requirements, standardized interfaces, and more predictable test and evaluation pathways as the services field larger autonomous fleets under the collaborative combat architecture model.
| Mission Design Series | Primary Role | Key Platforms | Data Architecture Emphasis |
|---|---|---|---|
| MDS-A | Attritable operations and massed effects | Loyal Wingman, optionally-manned platforms | Open mission architecture, rapid model deployment |
| MDS-B | High-end contested operations and resilient networking | Next-gen fighters, collaborative nodes, secure cloud edge | Multi-domain secure data links, joint all-domain command control |
Collaborative Combat Architecture Integration
The Air Force designates two mission design series to anchor collaborative combat architecture, ensuring that emerging autonomous capabilities can interoperate across domains. MDS-A emphasizes attrition-resistant mass, while MDS-B focuses on survivable, high-tempo engagements in denied environments. This alignment allows programs to converge on common standards for autonomy, sensing, and decision-sharing.
Test and Evaluation Pathways
Each mission design series defines explicit test and evaluation milestones, from component-level modeling to large-scale system demonstrations. Test events are structured around representative threat scenarios, data-sharing conformance checks, and human-machine teaming performance metrics. These pathways reduce risk by identifying interface mismatches before fielding.
Program Integration and Requirements Alignment
By assigning programs to one of the two mission design series, the Air Force can align requirements, standards, and milestone reviews across acquisition boundaries. This structure supports cross-service reuse of open architecture modules, common cybersecurity profiles, and reusable test assets. Program managers gain clearer expectations for interface documentation, model-based systems engineering artifacts, and verification evidence.
Operational Concepts and Campaign Planning
Operational planners leverage the two mission design series to shape campaign concepts that blend crewed platforms, loyal wingman, and tactical data networks. MDS-A enables distributed mass operations, while MDS-B supports time-sensitive contested access and multi-domain coordination. This operational lens ensures that design decisions favor real-world mission success in peer environments.
Implementation Roadmap and Key Takeaways
- Adopt open, service-defined data standards to ensure cross-platform compatibility across both mission design series.
- Establish joint test and evaluation campaigns that mirror realistic peer adversary tactics and sensors.
- Use requirements alignment to prevent duplicated development of autonomy, secure cloud, and edge computing capabilities.
- Plan incremental fielding with gateway and adaptation layers to integrate legacy systems into new collaborative architectures.
FAQ
Reader questions
How will the two mission design series affect open architecture adoption across programs?
The designation standardizes requirements for open mission architectures, ensuring that new capabilities plug into established data models and security policies, accelerating integration and reducing bespoke custom interfaces.
What role does the Air Force play in aligning services under these design series?
The Air Force leads cross-service governance, defining data standards, conformance tests, and interface baselines that allow Army, Navy, and joint partners to adopt the same mission design series for seamless interoperability.
Can legacy platforms participate in collaborative combat architectures mapped to these series?
Yes, legacy systems can participate through gateway nodes and adapters that translate data into the standardized formats defined by each mission design series, enabling gradual modernization without immediate wholesale replacement.
How are test and evaluation milestones structured differently between MDS-A and MDS-B?
MDS-A milestones focus on massed autonomous operations, rapid model updates, and attrition scenarios, whereas MDS-B milestones emphasize resilient networking, low-probability-of-intercept links, and high-end contested environment performance.