Immortal Jellyfish for Multi-Domain Command, Control, Communications and Situational Awareness (MDC3SA)

Technology has shifted from totally isolated, stove-piped monolithic systems to always-on, fully connected distributed systems that can be integrated dynamically with the push of a button. These monolithic systems still provide immense value across different military and intelligence organizations, holding domain-centric information that supports the very operational constructs of executing and planning different missions across the military. However, the Air Force and the larger Department of Defense cannot continue under this model if they are to compete with foreign nation-state actors who are embracing these technological evolutions. The DoD must rapidly shift to a Multi-Domain Command and Control (MDC2) ecosystem, where there is an ability to seamlessly analyze, fuse, and share this domain-centric information across disparate systems into a single C2 system that supports all domains and all levels of war. Further, communication, collaboration, and situational awareness must be integrated with the MDC2 ecosystem to provide real-time decision-making and analysis at the moment it is needed to successfully execute the mission across ground stations, ships, air assets, satellites, and mobile convoys of both manned and unmanned assets to form a tactical command, control, communication, and situational awareness (C3SA) environment. Air Force operations are inherently multi-domain, involving assets and weapons across air, space, and cyber domains, and supporting operations across global, regional, and unit levels.  To meet critical current and emerging C2 requirements, the Air Force has outlined a new MDC2 vision to transition from an environment in which requirements are met by developing whole systems over long periods of time to one characterized by “perpetual enhancement in operations.”  Achieving this vision requires the rapid design and prototyping of user-centered solutions with integration, security, test, deployment, and sustainment in mind from the onset – an approach referred to as “Design to Test”.  Further, software must be developed using an Agile approach with software deployed in weeks or months instead of years, and in a manner that facilitates sustainment.