Unmanned Air Systems Issues and Challenges to C4I INCOSE San Diego - - PowerPoint PPT Presentation

Information Dominance Anytime, Anywhere…

PEOC4I.NAVY.MIL

30 Oct 2010 CAPT John Robey Air Sea Integration (PMW 750) 619-524-7560 John.l.robey@navy.mil

Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO C4I)

Unmanned Air Systems – Issues and Challenges to C4I INCOSE San Diego

Statement A: Approved for public release; Distribution is unlimited.

CNO's Unifying Vision and Guiding Principles

Vision - "Pioneer, field and employ game-changing capabilities to ensure Information Dominance over adversaries and Decision Superiority for commanders, operational forces and the nation"

• First Principles Include:

 Every platform is a sensor  Every sensor is networked  Build a little; test a lot  Spiral development/acquisition  Plug-n-play sensor payloads  Reduce afloat/airborne manning  Transition to remoted, automated  Collectors dynamically tasked  Emphasize UAS/RPV and autonomous platforms UAS's increasingly sea-based One operator controls multiple platforms Data discoverable and accessible Missions drive requirements Commonality in interfaces, data links and control stations Every shooter capable of using target data derived from any sensor

2

Statement A: Approved for public release; Distribution is unlimited.

UAS Family of Systems

DISTRIBUTION STATEMENT A: Approved for public release; Distribution is unlimited. #09-983

3

BAMS UAS OV-1

Narrowband SATCOM Wideband SATCOM Global Positioning System UA MOB MCS FOB MCS EO/IR Joint Navy HQ(MOC)/ Allied/Coalition Battle Management Nodes Maritime Forces Joint Allied/ Coalition Exploitation Sites Teleport Airspace Control Authority

BAMS Payload Data BAMS Air Vehicle C2 Defense Info System Network/Global Info Grid Airspace Communications Airborne Communications Relay

Maritime Forces Radar, ESM & AIS

BAMS UAS Nodes (UA, MOB/FOB MCS)

DISTRIBUTION STATEMENT A: Approved for public release; Distribution is unlimited. #09-983

4

Exploitation Sites

GIG

DISA POP Mission Control System (MCS)

Main Operating Base (MOB)

Sensor data to Exploitation Sites

BAMS UA Worldwide

CSG/ESG Sensor data from UA

SIPRNET

Sensor data from UA

GCCS-M, AIS, Chat, VoIP

Wideband SATCOM CDL / Link-16 MPRA

First Pass Analysis from MCS

(e.g. NMIC, MOC/MIOCs, NGA, DCGS FoS, FIOC) DCGS-N Afloat Nodes

Teleport

DCGS-N Enterprise Node

DCGS Family of Systems (Air Force, Army, Marines, SOF, DCGS-IC) DISTRIBUTION STATEMENT A: Approved for public release; Distribution is unlimited. #09-1061

Managing the Processing, Exploitation and Dissemination (PED) of Data

5

Exponential Data Growth: Enabler & Challenge!

(From MIEA Study) GIG Data Capacity (Services, Transport & Storage)

UUVs

2000 2005 2010 2015 & Beyond

Theater Data Stream (2006): ~270 TB of NTM data / year 1018 1012 1024 1015 1021

FIRESCOUT VTUAV DATA

Capability Gap

Current single mode fiber carries 960 Gpbs Max of 50 Mbps per channel

MIEA Review

6

Statement A: Approved for public release; Distribution is unlimited.

Collection Data Decisions

• Should we collect?
• Which sensors?
• When/where to collect?
• Where to process?
• When to transmit ?
• Where to store?

Tactical Data Decisions

• Analyze it? Is Expertise available?
• Store it? How long? Capacity?
• Transmit it? How? Capacity?
• Throw it out?
• How to “mark it up?”

Data Transmission Decisions

• Send all of it?
• Compress it?
• Stream it?
• Just send a metadata

synopsis?

• Adjust Quality of Service?

Enterprise/Cloud Data Decisions

• Data center

consolidation?

• Degree of distributed

processing?

• “Big Data” storage and

processing standards?

• Time to live?
• Data format

standardization? Systems Data Decisions

• Analyze it?
• “Mark it up” (i.e., metadata)?
• Store it? Where and for how long? Searchable?
• Distribute it? How and which systems need it?
• Which system becomes “authoritative?”
• How to aggregate different results?
• How to track provenance? Who has

touched it?

• Throw it out? Why collect it and send it to begin

with?

Each decision is an opportunity to improve the end-to-end mission capability and streamline the OODA* Loop

*Observe, Orient, Decide, Act (OODA)

Navy Data Strategy Challenge

(from PEO C4I ISR Data Study - MITRE)

7

Statement A: Approved for public release; Distribution is unlimited.

Summary

• Proliferation of UASs (and their data) pose a significant

challenge to Navy C4I architectures and TTPs

• Data Strategies and ISR CONOPS are immature
• Acquisition requirements and ownership of data processing,

exploitation and dissemination (PED) are unclear

– Getting the right data to the right customer at the right time – Manpower - who does what and where – Bandwidth – how much is enough, what needs to be sent and to whom – Automation / Data Fusion – turning data into information

• Disciplined Systems Engineering and requirements

derivation across SYSCOMs and acquisition programs is critical

8

Statement A: Approved for public release; Distribution is unlimited.