C2 SSA COI Pilot Working Group Outbrief

1. C2 SSA COI Pilot Working Group Outbrief Maj Mark Schmidt, mark.c.schmidt@peterson.af.mil 719-556-9469 Ms. Mary Pulvermacher, pulver@mitre.org 719-572-8241 DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. USAF/AFMC//ESC/PA clearance # ESC 07-0233

2. Overview • The C2 Space Situational Awareness COI • The Pilot Itself • Lessons Learned • Concluding Comments

3. New Net-Centric DSCS Capability IRIDIUM Cell 4 Old: Alert via Phone Previously Closed DSCS Network 2 GSSC Plan: Automated near real time message SOF 1 SATCOM GIG Node On SIPR Firewall SISP Server ∆t INMARSAT Eyes On 3 SISP Client Enemy Forces OC Old Enemy Arrives Little warning SIPRNet Plan SOF Alerted & counters 1. Normal communication with SOF 2. Communication link failure. SOF and OC alerted 3. Reconnaissance unit sends SITREP of enemy force movement 4. Communications reestablished. SOF alerted to enemy force

4. New Net-Centric NavAcc Capability Army TOC - ?Unanticipated user using Web Browser SIPRNET 3 Target located. Coordinates sent. SBMCS Interface 4 SISP NAVACC Processed Data Reconnaissance unit sends SITREP of Enemy Force Movement • GPS accuracy assessed. • Mission planned. • GPS changes. • Wing alerted. • A/C launch delayed. • Collateral damage averted. 1,2 GPS Notice Advisory to Navstar Users (NANU) 3 AOC Enemy Forces 4,5 GPS Network Bomber unit has the most accurate coordinates Raw Data 6

5. Pilot Accomplishments • Demonstrated both pilot threads at USSTRATCOM Global Lightning 2007 exercise in Dec. 2006 • Exposed data on the GIG that was never before accessible via machine to machine accessible services • Performed work in approx 12 months, from FY06 budget available to demonstration in an exercise (budget cut at T+1 month) • Created “Coalition of the Willing” after the budget cut • Everyone pitched in, “out of hide” • Significant risk reduction to the program of record (CCIC2S and the Single Integrated Space Picture, SISP) • First to implement C2 SSA COI XML data schema (vocabulary) • First COI to pilot NCES core services using DISA’s Early Capabilities Baseline • First COI to use PKI user certificates on SIPRNet • First to deploy to the AF ESC Rapid Operational Capabilities Development Environment

6. Net-Centric Shifting: Mostly Vertical to the Horizontal Lessons Learned – COI #1 • Successful COIs need powerful champions • AFSPC/CV (3-star) started the COI • OSD/NII and AFSPC/A5 helped overcome many hurdles • Pilots are an effective means to reduce risk • Allows programs to tackle HIGH risk items • Pilots have leadership’s attention • Focus on interoperability • Use pilots to reduce risk, pave the way • Define expectations up front Truly is a paradigm shift!

7. Lessons Learned – Programmatics #2 • Different views on data requirements • Is the requirement to expose data or the resulting capability? YES. • Data must be made available--think data enable enterprise • Different views on priority of the requirement • Net-Centric requirements process is needed • Prioritize cross-cutting requirements at a lower level • Across MAJCOMs, COCOMs, services and agencies • Jointly optimize and synchronize net-centric priorities • Different views on funding priorities • How fund? DoD process? COI authority? • Who funds? Organizationally? Data producers? Consumers? Hinders Delivery of Joint, Horizontal Net-Centric Capability COIs Can Make DECISIONS

8. Final Conclusions & Recommendations • Conclusions • Successfully met pilot objectives • Pathfinder for Space C2 • Pathfinder for COI paradigm for information sharing • Recommendations • COIs set community priorities and funding • Make decisions, direct member organizations and programs • Create incentives to deliver net-centric capabilities • Broaden interoperability requirements, elevate the priority • Joint interoperability—across MAJCOMs, services, agencies • Establish system integrators within community domains • Responsible for common domain level services • Sets/implements interoperability standards • Implement enterprise Information Assurance processes

9. Questions?