SKIWeb – Pathfinder Transition from Local to Enterprise Capability COI FORUM 12 January 2010

1. SKIWeb – Pathfinder Transition from Local to Enterprise CapabilityCOI FORUM12 January 2010 Mr. Dennis Popiela, USJFCOM J8 DRAFT Document Unclassified FOUO

2. Purpose & Intent PURPOSE: Refine the templates for the transition of locally developed applications and services to an enterprise capability INTENT: Use USSTRATCOM Strategic Knowledge Integration Web (SKIWeb) ongoing transition to DISA's DECC as a pathfinder to mature ES DTM and Enterprise Solutions Designation and Governance (ESDG) processes AMPS and TIS lead the way SKIWeb enter the process at Decision Point - DP III. Receive feedback on alternative SKIWeb solutions currently existing or planned Unclassified 2

3. SKIWeb Background Problem:Transition COCOM developed C2 application to an enterprise capability • (2005-2009) USSTRATCOM developed/matured situational awareness event reporting web based capability • (2009) Joint Staff J3 directed COCOM watch centers use SKIWeb for event reporting • (2009) VCJCS identified SKIWeb as key service for National Senior Leaders Decision Support System (NSLDSS) Tool set • (2009) USSTRATCOM submitted P/BR11 issue paper for transition of SKIWeb to a DoD enterprise capability • (2009) CAPE RMD 700 funding guidance: “Transition SKIWeb from STRATCOM to DISA’s DECC..recover cost from COCOMs thru DWCF..FY 11 ($7.2M) FY 12 (4.0M)” Unclassified FOUO 3

4. Rapid Operational Solutions:Meeting COI 2010 Strategic Objectives 2010 and beyond Fix the Hand-Offs 2010 SKIWeb Pathfinder Project • Locally developed operational model • Transition planning to DECC underway • Template developed for PM and COI training • Forming strategic partnerships with COCOMs, DoD CIO, DISA, JS, Services • Promote models of success • Improve transition from COI pilots to operational solutions • Revise COI training • Encourage strategic partnerships Unclassified Source: DoD CIO ES&I “COI Enabling Net-Centric Data Sharing & ES Integration

5. SKIWeb Operational Overview • Event Management and Collaboration Tool • Open forum for information owner to share situational awareness • Real-time reporting on SIPR and JWICS networks • Self Correcting – users post corrected information • SMEs can interact directly with decision makers • USSTRATCOM hosted application • Used as an event reporting tool by Joint Staff, NMCC, COCOMs, Service Components and Agencies • User population • 27, 954 registered users • 2, 333 average daily users USSTRATCOM Brief 28 Dec 2009 Unclassified FOUO

6. SKIWeb: Operational Concept Flattens an organization through concept of need to share vice need to know. Enables decentralized planning, decision-making, and execution of mission areas without abdicating responsible control. Provides event entry and threaded discussions Decision Makers OPs Intel Event SME Support Watch Floor Based on USSTRATCOM Brief June 2009 Unclassified FOUO

7. System Overview Diagram USSTRATCOM Brief June 2009 Unclassified FOUO

8. Hardware Architecture • SKIWeb Architecture •   Production SKIWeb operates on 8 servers • 4 Application servers, 2 load balancers and 2 database servers USSTRATCOM Brief June 2009 Unclassified FOUO

9. Software Architecture USSTRATCOM Brief June 2009 Unclassified FOUO

10. Communications Architecture USSTRATCOM Brief June 2009 Unclassified FOUO

11. COI Process Goals and SKIWeb Unclassified Source: DoD CIO ES&I “COI Enabling Net-Centric Data Sharing & ES Integration

12. DoD Enterprise Service Designation and Governance Process • Phase I: Is there an opportunity to deliver capability as an enterprise solution? • Transitioning to DISA hosting • Global (COCOM) Community of Interest (COI) • Phase II: What is the “best: solution? • COCOM locally developed, tested, and deployed • Determine if there are alternative capabilities planned or existing • Phase III: What is the Implementation Strategy? • DECC implementation strategy under development • Enterprise capability transition strategy • Phase IV: How do we fund? • RMD 700 funding for FY 2011 • Funding Strategy beyond FY 2011 • Reduce funding burden on COCOMS for “mandate” services • Phase V: Is the Department “better” off? • SKIWeb has demonstrated reduction of DoD worldwide event reporting delays SKIWeb has met some criteria in each phase Derived from draft DTM-Enterprise Service Designation, Sustainment, Devolution and Termination • Completed actions

13. Discussion for COI • Are there alternatives to SKIWeb? • Current or planned • What is the best implementation for SKIWeb? • DECC hosting, enterprise capability, shared capability, enterprise service • How do you transition an operational capability? • Do no harm to the warfighter • What is the criteria to determine the decision point where mature capabilities enter the ES process? • Avoid starting over or loosing momentum • What is the proper funding model for SKIWeb like capabilities? • Least amount of burden on COCOMs and Services • What are other testing and training requirements for other type of applications going through transition.

14. Summary Request COI: Support pathfinder working group efforts to standardize the transition process for locally developed applications to an enterprise capability using the SKIWeb as the pathfinder project Following AMPS and TIS in EGB/ESRG transition process Deliver capability as an enterprise solution when applicable Determine the “best” solution Develop the implementation strategy Develop the funding strategy Identify the ES process entry points for mature operational capabilities Provide awareness of alternative solutions currently existing or planned Fundamental Step in Process of Delivering Slices of Capability Unclassified 14