MOBILITY AIRCRAFT INTEROPERABILITY IN A MULTI-DOMAIN ENVIRONMENT (A/TA SEMINAR BRIEF) Daniel Malloy LM Aero SoSITE Program Manager LM Aero ADP [email protected]

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) REALIZING MULTI-DOMAIN DISTRIBUTED ARCHITECTURE

• Multi-Domain Operations (MDO) require increased warfighter speed in DATA TO DECISION - Platforms need to be interoperable in a dynamic Command & Control (C2) architecture - Operations based on heterogenous distributed platforms, sensors, weapons, and applications - Decision making is distributed across the battlespace • Datalink communications, machine-to-machine information exchange, and automated/autonomous decision aids are key enablers for realizing this MDO architecture • USAF is developing and maturing foundational technology through flight test demonstrations to realize MDO sooner than thought possible • Two key MDO enabling technologies: - FLEXIBLE AUTONOMY FRAMEWORK to enable enhanced Situational Awareness (SA) and mission management (C2) with minimum impact on Pilot/Operator workload - “STITCHES” technology developed under DARPA's SoSITE Program to enable interoperability

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) MULTI-DOMAIN OPERATIONS (MDO) VISION

Involves Multi-Domain Every Node Connects To Produce High-velocity, Planning…and Execution – Shares – Learns operationally agile ops that present multiple dilemmas for an adversary at an operational tempo they cannot match

Multi-Domain Operations: Warfare that operates using the integrated capabilities of: • Space Resilient - Distributed - Multi Domain - • Air Open Architecture - Platform Agnostic - Affordable • Land • Surface • Interoperability across various mission systems • Cyber • Fast-track ability to develop, deploy and field capabilities • Accelerate sharing of information and decision making

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) OODA LOOP: DECISION SUPERIORITY

• What is the threat • Where is the threat • How am I oriented to the threat • Where are other mission assets • Who can respond • What capability do they have

Need to shrink our OODA decision loop and Loop keep it inside the adversary’s decision loop

• What needs to be done about threat • What are ways to mitigate threat • Select mitigation • Enable mitigation Observe, Orient, Decide, Act (OODA) Loop – Developed by Col. John Boyd USAF Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) VISION: RETHINKING PLATFORMS AS PART OF A MULTI-DOMAIN SYSTEM OF SYSTEMS

Mission Systems • Sensor Mission Systems • Communications • Electronic Warfare • Communications Mission Systems Combat • Sensor Platform Cloud AOC Node • Communications

Mission Systems • Mission SA / C2 Mission Systems • Communications Mission Systems System of Systems • Weapons • Mission SA / C2 • Battle Manager • Communications (SoS) • Communications Mission Systems Rethinking Current • Platforms & Future Military • Pilot/Operators Systems • Communications Enablers Mission Systems Mission Systems • Open System Architectures • Pilot/Operator • Weapons • Autonomous Applications • Mission SA / C2 • Battle Manager • System Interoperability • Communications • Communications

System-of-Systems Architecture (SoS) = Platforms + mission systems + distribution of mission systems information and C2 across platforms

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) CROSS-DOMAIN APPLICATIONS Naval Integrated Fire Control – Counter-air (NIFC-CA)

• Elevated, Forward Sensors Data-Linked to Shooters • Shortens Kill Chain…Moves Engagement Earlier

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) FLIGHT DEMONSTRATIONS

• Demo'ing building blocks for future MDO • 5th to 5th and 5th to 4th Comms • Multi-Level Security, Open Sys Arch. • High Assurance computing (where needed) • Common Mission C2, EW, Weapons Integration • Multi-Domain: Air-Space Integration • SoS Engineering

Enterprise-OSA Mission Computer

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) HUMAN AUGMENTATION, MACHINE AUTONOMY

“The complexity of integrating forces has eclipsed the human’s ability to make timely decisions, synchronize fires, and optimize allocation of resources.”

- Navy Fleet Forces Command N8/N9

Acquisition and Trust Timeline Data Analytics Decision Aids Full Autonomy Decision aids and Flexible autonomy to deal with complexity Manual Full Control Autonomy

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) SOS INTEGRATION

• System of Systems Integration Technology Experimentation (SoSITE) - Goal: Seamless and rapid integration across air, space, land, sea and cyber in contested environments - STITCHES: Novel integration technology - EMC2 Box: Open computing environment and security protections between systems Tactical / Strategic System of Systems

• Demonstrating rapid and affordable integration of mission systems into Allows forces to rapidly existing and new architectures reconfigure and prevail over any threat

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) FLEXIBLE AUTONOMY SCALABLE & FLEXIBLE AUTONOMY FRAMEWORK

Building Trust In Autonomy, With The Warfighter “On The Loop” vs. “In The Loop” For Faster Data To Decision

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) DEVSECOPS SOFTWARE BASELINE APPROACH TO ENABLE AFFORDABLE AND RAPID SOLUTIONS

• USG-Owned H/W & S/W Standards (OMS/UCI)

• Plugin-based, Operator Verified HMI DEPLOYABLE ON COTS H/W • Proven Modular architecture to OPEN ARCHITECTURE COMPLIANT support centralized or distributed solutions INTUITIVE HUMAN MACHINE INTERFACE

• Algorithm agnostic, supports third party business logic

DEVSECOPS: integrating security practices within the DevOps process. DevSecOps involves creating a 'Security as Code' culture with ongoing, flexible collaboration between release engineers and security teams

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) FLEXIBLE AUTONOMY PROVEN AND ESSENTIAL FOR MDO • MDO Applicability - Provides domain agnostic automation tools • Feasibility - Proven, High-Technology Readiness Level - Open System Architecture systems already in USAF operations • Scalability - Intuitive automation easily able to scale from tactical Flexible, Autonomous to ops & to all services /agencies Framework Ready to • Warfighter Impact Transition Across All - Provides decreases in warfighter cognitive workload and reduces operational manning requirements by Multi-Domain building trust in autonomous system operations Operations

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) DARPA SoSITE PROGRAM & STITCHES

System of Systems Integration Technology Experimentation (SoSITE) & System-of-systems Technology Integration Tool Chain For Heterogenous Electronic Systems (STITCHES) THE CHALLENGE OF INTEGRATING A SYSTEM OF SYSTEMS

Standards enable swift integration, but maintaining backwards- compatibility and “future- proofing” slows progress

Source: https://xkcd.com/927/

DistributionDistribution Statement Statement “A” (ApprovedA: Approved for for Public Public Release, Release, Distribution Distribution Unlimited) Unlimited System of Systems Integration Technology and Experimentation (SoSITE)

Hypothesis: System of Systems Approach Provides Increased Accomplishments Mission Utility, Cost Leverage, and Adaptability • Multiple SoS architectures were created during “Gauntlets”: rapid integration events lasting 1-2 weeks • Gauntlet workup 3-4 months, average < $500K, small teams of < 5 personnel per subsystem • SoS integration occurs < hours • The STITCHES tool chain was used by industry and government teams to integrate existing DoD systems during these SoSITE Gauntlets • Gauntlet-3: rapid SoS creation: 45 minutes to create Objective: Integrate new & existing systems faster than automated cooperative jamming via datalink the measure-countermeasure cycle (nominally 90 days) • Gauntlet-4: real-time ATO kill chain: reduced task time of a Approach: Use automated toolchain to integrate new mission to <10 minutes multiple stand-alone subsystems into a new SoS • Gauntlet-5: automated & distributed EW protection • SoS defined by needed capability, not limited by standards • Gauntlet-6: integrated key threat & no-fly data between • Global interoperability without global standards; use database several Command & Control (C2) systems to automatically translate messages between subsystems • Gauntlet-7: integrated naval EW systems to enable • Use rapid integration events to reduce risk of adopting new shared detections architectures ATO: Air Tasking Order SoS: System of Systems EW: Electronic Warfare STITCHES: SoS Technology Integration Tool Chain for Heterogeneous Electronic Systems Distribution Statement A: Approved for Public Release, Distribution Unlimited SoSITE integrates via a new toolchain called STITCHES

The STITCHES toolchain: STITCHES Example: • automatically creates Integrate a Radar and Targeting Pod FTG translations between any two Repository well-formed specifications • is independent of existing subsystem standards • combines a graph-based database with a custom computer language designed for integration • uses modern compiler theory Existing physical to optimize the translations Subsystems connections or datalinks 1. Both subsystems (SS) are 4. SoS message (M) translation FTG: Field and Transform Graph. A set of XML files used to modeled in the FTG model subsystems and their connections. software is automatically Subsystem Message (M): data passed between subsystems; logically Core generated by searching the represented as “Fields” in FTG files. Visually depicted as 2. SS interfaces are written “nodes” in a graph to separate STITCHES from FTG for existing message pairs Transform: a conversion between two or more Messages (M) the SS core software & or “Fields”. Visually depicted as “edges” in a graph handle message (M) traffic Note: Translations are SS: Subsystem, the individual components of a SoS optimized and at least as fast SoS: System of Systems 3. Transforms are written to and precise as those created

STITCHES: SoS Technology Integration Tool Chain for connect each new SS into by hand Heterogeneous Electronic Systems the existing FTG Distribution Statement A: Approved for Public Release, Distribution Unlimited 17 EXAMPLE: CONSENSUS NETWORK

• Organization A uses Geodetic coordinates in its systems to report Location • Organization B uses Earth-Centered-Inertial (ECI) to report Position • Organization C uses the Military Grid Reference System to report Place • A and B agree on precise rules to translate to and from Geodetic and ECI • B and C develop precise rules to translate to and from ECI and MGRS

• Use the pair-wise agreements (A-B & B-C) to achieve interoperability between A & C

• A Consensus Network!

• Organization D, a British company, uses British National Grid for Spot • D simply agrees on translations with one of the three, e.g. Organization A, to attain interoperability with all of the three:

DistributionDistribution Statement Statement “A” A: (ApprovedApproved for for Public Public Release, Release, DistributionDistribution Unlimited Unlimited) SOSITE RAPID INTEGRATION EXPERIMENT SUCCESS STORIES

[Jan 2018] FE-2: MUMT Flight Experiment [June 2018] Gauntlet-4: Real-Time ATO & [Sept 2018] Gauntlet-5: Distributed EW Command & Control Automated Kill Chain Flight Test

Flight Lab [Dec 2018] Gauntlet-6: Integrated Airborne and Distributed C2 Lab Test [Feb 2019] Gauntlet-7: Navy Integrated Fires Lab Test SOSITE HAS PERFORMED 9 FLIGHT AND LAB EXPERIMENTS INTEGRATING 73 UNIQUE SYSTEMS DistributionDistribution Statement Statement “A” “A” (Approved (Approved for for Public Public Release, Release, Distribution Distribution Unlimited) Unlimited) SUMMARY

• Fielding of distributed system-of-systems capability possible in near term

• MDO-related flight demos prove platforms can be modernized / connected together efficiently - Exploring CONOPs to allow rapid decision making MDO capability is closer - Advancing enabling technologies to make MDO a reality than some think… • To be most effective, close industry-military relationships are essential - Tie materiel designs and operating concepts Close collaboration with (CONOPS, user feedback, testing / certification issues, etc) DOD is critical

Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) Distribution Statement “A” (Approved for Public Release, Distribution Unlimited)