leave behind c2isr

Enterprise Integration Systems Group

Leave Behind C2ISR

Maj Mike LydonA5R-Q Irregular Warfare Requirements

[email protected]

703-697-1416 (DSN 227)

Headquarters U.S. Air Force


2

Mission Statement

• Provide an affordable and unclassified information

sharing and gathering infrastructure for Partner

Nation Building Partnership Capacity Operations and

Humanitarian Assistance/Disaster Relief missions

that enables US Military collaboration with Non

Government Organizations (NGOs), Foreign Nationals

and other Authorities including USG Interagency


3

CCP Key Functionality• Core Functionality

– Provide common operating picture collaboration environment

– Visual display of participating groups, data layers showing assets and capabilities, area imagery,

maps, real time tracking of assets/people, intelligence, weather, road conditions

– Collaboration software-multilingual chat, “Office-like” suite of tools, wiki, etc

– Pre-loaded Databases of commercial/unrestricted imagery, medical info, human terrain, local maps

• System Requiremnts

– Unclassified System, Non-ITAR Restricted, Open Source Software

– Some Information Assurance required

– Service Oriented Architecture (SOA)

– Interoperability with foreign heterogeneous data sources

• Users

– Open to any NGO, foreign national, US citizen, US Military, local police, local military,

– Access determined by PN and MTT

• System Functionality

– Blue Force Tracker

– Commercial Satellite Communications if in austere environment

• Internet access, video teleconferencing, remote network, image transmission

– Local Broadband Communications via wi-max

– Alert and Warning push capability


4

Notional Concept Of Operations

Connect via Internet, CCP or other

Open Source Intel

US Based NGOs (CDC, NIH, etc.)

US Mil/InteragencyPartner Nation

Other

Commercial SATCOM (part of fly-away-kit)

Common Collaborative Picture and Multi-Lingual Portal (part of fly-away kit)

CONUS/Reach-back Support

Local WiMax (part of fly-away-kit)

CCP Servers


5

CCP Servers

Conceptual Architecture

Connect via Internet, CCP or other

Open Source

US Based NGOs (CDC, NIH, etc.)

US MIL/InteragencyLocal Ingest

Other

CCP JSR Compliant Portlets

CCP Multi-Lingual Portal

Applications

GEOINT

Search

Wiki

SOA Services

Data

Local

3rd Party

Pre-existing

Functions

Language Processing

Metadata Mgt

Infrastructure

Resource Task Mgr (semantic mediation)

Data Access Layer (OCR, Extraction and Data Import)

CONUS Support

Databases

Connect via SATCOM

Commercial Services (Imagery, Weather, etc.)

Connect via SATCOM

USAF ISR Enterprise


6

Initial CCP Roadmap

1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4QFY 2009 FY 2010 FY 2011

Spiral 1: Initial Enterprise Connectivity

• Visual Display Access Layer• SATCOM & Imagery Connection• Basic Wiki and collaboration tools• Wi-Max and Blue Force Tracking

Spiral 2: Discovery/ Data Services

• Multiple Organic Sensor integration• OCR and Extraction Service Integration• Web Service Access to the Portal• Automated Map Generation

Proof of Concept/Requirements Study

Spiral 3: Extraction and Recognition

• Additional Access Layer (MQ, APIs, Web Services)• Add Multi-Lingual portal (Arabic)• Semantic Discovery of Data Services• Alert Manager

• Automation & Integration Updates

Spiral 4: Automation Updates

Demonstrate a capable system

Demonstrate a capable system with expanded connectivity

Demonstrate an enhanced automated and rapidly deployable system


7

Integration Elements

• Services

• Modern ISR systems have 300+ SOA services

• System will probably need 1/2 of these services

– User Services: Collaboration; Data Exploitation;

Presentation; Process & Workflow; Asset Mgt, etc..

– Domain Services: Information Fusion; GEOINT; Alerting;

Dissemination; Weather; etc..

– Infrastructure: Metadata; Network Mgt; Security; Systems

Mgt; etc..

• Integration involves more than just the user applications

– Most likely include 25-50 open source and COTS/GOTS

elements

leave behind c2isr

Documents