Leave Behind C2ISR

1. Headquarters U.S. Air Force Leave Behind C2ISR Maj Mike Lydon A5R-Q Irregular Warfare Requirements Michael.lydon@af.pentagon.smil.mil 703-697-1416 (DSN 227)

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 Partner Nation US Mil/Interagency Commercial SATCOM (part of fly-away-kit) Local WiMax (part of fly-away-kit) CONUS/Reach-back Support Connect via Internet, CCP or other CCP Servers Other Common Collaborative Picture and Multi-Lingual Portal (part of fly-away kit) Open Source Intel US Based NGOs (CDC, NIH, etc.)

5. Conceptual Architecture CONUS Support Local Ingest US MIL/Interagency Databases Connect via SATCOM Commercial Services (Imagery, Weather, etc.) Connect via Internet, CCP or other CCP Multi-Lingual Portal CCP JSR Compliant Portlets Connect via SATCOM Open Source US Based NGOs (CDC, NIH, etc.) Other CCP Servers Functions Data Applications USAF ISR Enterprise Language Processing Local GEOINT Search 3rd Party Metadata Mgt Pre-existing Wiki Infrastructure SOA Services Resource Task Mgr (semantic mediation) Data Access Layer (OCR, Extraction and Data Import)

6. Initial CCP Roadmap FY 2009 FY 2010 FY 2011 3Q 1Q 1Q 1Q 4Q 3Q 4Q 2Q 2Q 3Q 4Q 2Q Proof of Concept/Requirements Study Spiral 1: Initial Enterprise Connectivity Demonstrate a capable system • Visual Display Access Layer • SATCOM & Imagery Connection • Basic Wiki and collaboration tools • Wi-Max and Blue Force Tracking Demonstrate a capable system with expanded connectivity Spiral 2: Discovery/ Data Services • Additional Access Layer (MQ, APIs, Web Services) • Add Multi-Lingual portal (Arabic) • Semantic Discovery of Data Services • Alert Manager Demonstrate an enhanced automated and rapidly deployable system Spiral 3: Extraction and Recognition • Multiple Organic Sensor integration • OCR and Extraction Service Integration • Web Service Access to the Portal • Automated Map Generation Spiral 4: Automation Updates • Automation & Integration Updates

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