mobility aircraft interoperability in a multi-domain …€¦ · mobility aircraft interoperability...

(A/TA SEMINAR BRIEF)

Daniel Malloy

LM Aero SoSITE Program ManagerLM Aero ADP

[email protected]

MOBILITY AIRCRAFT INTEROPERABILITY IN A MULTI-DOMAIN ENVIRONMENT

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


MULTI-DOMAIN OPERATIONS (MDO) VISION

To Produce High-velocity, operationally agile ops that present multiple dilemmas for an adversary at an operational tempo they cannot match

• Interoperability across various mission systems

• Fast-track ability to develop, deploy and field capabilities

• Accelerate sharing of information and decision making

Resilient - Distributed - Multi Domain -Open Architecture - Platform Agnostic - Affordable

Every Node Connects – Shares – Learns

Involves Multi-Domain Planning…and Execution

Multi-Domain Operations:Warfare that operates using the integrated capabilities of:• Space• Air• Land• Surface• Cyber


OODA LOOP: DECISION SUPERIORITY

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

Observe, Orient, Decide, Act (OODA) Loop – Developed by Col. John Boyd USAF

OODA Loop

• 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

• What needs to be done about threat• What are ways to mitigate threat• Select mitigation• Enable mitigation


VISION: RETHINKING PLATFORMS AS PART OF A MULTI-DOMAIN SYSTEM OF SYSTEMS

Platform

Mission Systems• Platforms• Pilot/Operators• Communications

System of Systems(SoS)

Mission Systems• Weapons• Battle Manager• Communications

Mission Systems• Electronic Warfare• Communications

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

Rethinking Current & Future Military

Systems

Enablers• Open System Architectures• Autonomous Applications• System Interoperability

Mission Systems• Pilot/Operator• Mission SA / C2• Communications

Mission Systems• Sensor• Communications

Mission Systems• Weapons• Battle Manager• Communications

Combat Cloud

AOC Node

Mission Systems• Sensor• Communications

Mission Systems• Mission SA / C2• Communications

Mission Systems• Mission SA / C2• Communications


CROSS-DOMAIN APPLICATIONS

Naval Integrated Fire Control – Counter-air (NIFC-CA)

• Elevated, Forward Sensors Data-Linked to Shooters

• Shortens Kill Chain…Moves Engagement Earlier


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


HUMAN AUGMENTATION, MACHINE AUTONOMY

Decision aids and Flexible autonomy to deal with complexity

“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

ManualControl

FullAutonomy


SOS INTEGRATION

Allows forces to rapidly reconfigure and prevail over any threat

• 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

• Demonstrating rapid and affordable integration of mission systems into existing and new architectures

Tactical / Strategic System of Systems


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


DEVSECOPS SOFTWARE BASELINE APPROACH TO ENABLE AFFORDABLE AND RAPID SOLUTIONS

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

• Plugin-based, Operator Verified HMI

• Proven Modular architecture to support centralized or distributed solutions

• Algorithm agnostic, supports third party business logic

OPEN ARCHITECTURE COMPLIANT

INTUITIVE HUMAN MACHINE INTERFACE

DEPLOYABLE ON

COTS H/W

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


FLEXIBLE AUTONOMY PROVEN AND ESSENTIAL FOR MDO

Flexible, Autonomous Framework Ready to Transition Across All Multi-Domain Operations

• 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 to ops & to all services /agencies

• Warfighter Impact

- Provides decreases in warfighter cognitive workload and reduces operational manning requirements by building trust in autonomous system operations


DARPA SoSITE PROGRAM & STITCHESSystem 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/

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

Accomplishments

• 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

automated cooperative jamming via datalink

• Gauntlet-4: real-time ATO kill chain: reduced task time of a

new mission to <10 minutes

• Gauntlet-5: automated & distributed EW protection

• Gauntlet-6: integrated key threat & no-fly data between

several Command & Control (C2) systems

• Gauntlet-7: integrated naval EW systems to enable

shared detections

System of Systems Integration Technology and Experimentation (SoSITE)

Hypothesis: System of Systems Approach Provides Increased Mission Utility, Cost Leverage, and Adaptability

ATO: Air Tasking OrderEW: Electronic Warfare

SoS: System of SystemsSTITCHES: SoS Technology Integration Tool Chain for Heterogeneous Electronic Systems

Distribution Statement A: Approved for Public Release, Distribution Unlimited

Objective: Integrate new & existing systems faster than

the measure-countermeasure cycle (nominally 90 days)

Approach: Use automated toolchain to integrate

multiple stand-alone subsystems into a new SoS

• SoS defined by needed capability, not limited by standards

• Global interoperability without global standards; use database

to automatically translate messages between subsystems

• Use rapid integration events to reduce risk of adopting new

architectures

SoSITE integrates via a new toolchain called STITCHES

STITCHES Example:

Integrate a Radar and Targeting Pod

SubsystemsExisting physical

connections or

datalinks

Subsystem

Core2. SS interfaces are written

to separate STITCHES from

the SS core software &

handle message (M) traffic

4. SoS message (M) translation

software is automatically

generated by searching the

FTG for existing message pairs

Note: Translations are

optimized and at least as fast

and precise as those created

by hand

17Distribution Statement A: Approved for Public Release, Distribution Unlimited

1. Both subsystems (SS) are

modeled in the FTG

The STITCHES toolchain:• automatically creates

translations between any two

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

to optimize the translations

FTG: Field and Transform Graph. A set of XML files used to

model subsystems and their connections.

Message (M): data passed between subsystems; logically

represented as “Fields” in FTG files. Visually depicted as

“nodes” in a graph

Transform: a conversion between two or more Messages (M)

or “Fields”. Visually depicted as “edges” in a graph

SS: Subsystem, the individual components of a SoS

SoS: System of Systems

STITCHES: SoS Technology Integration Tool Chain for

Heterogeneous Electronic Systems

3. Transforms are written to

connect each new SS into

the existing FTG

FTG Repository

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:

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

SOSITE RAPID INTEGRATION EXPERIMENT SUCCESS STORIES

[Jan 2018] FE-2: MUMT Flight Experiment

[Dec 2018] Gauntlet-6: Integrated Airborne and Distributed C2 Lab Test

[June 2018] Gauntlet-4: Real-Time ATO & Automated Kill Chain Flight Test

[Sept 2018] Gauntlet-5: Distributed EW Command & Control

[Feb 2019] Gauntlet-7: Navy Integrated Fires Lab Test Flight

Lab

SOSITE HAS PERFORMED 9 FLIGHT AND LAB EXPERIMENTS INTEGRATING 73 UNIQUE SYSTEMSDistribution Statement “A” (Approved for Public Release, Distribution Unlimited)Distribution Statement “A” (Approved for Public Release, Distribution Unlimited)

SUMMARY

MDO capability is closer than some think…

Close collaboration with DOD is critical

• 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

- Advancing enabling technologies to make MDO a reality

• To be most effective, close industry-military relationships are essential- Tie materiel designs and operating concepts

(CONOPS, user feedback, testing / certification issues, etc)


mobility aircraft interoperability in a multi-domain …€¦ · mobility aircraft interoperability...

Documents