1. Connecting People With Information DoD Transformation to Net-Centric Operations via Net-Centric Strategies For further information email OSD at: COI_HelpDesk@osd.mil DoD Net-Centric Data Strategy (DS) and Community of Interest (COI) Training Executive Overview Version 1.1 – February 16, 2008

2. 2 Purpose Describe key enablers for DoD transformation to Network Centric Operations –DoD Net-Centric Data and Services Strategies –Community of Interest (COI) Approach Illustrate how use of these enablers can lead to DoD Transformation Solicit your help to achieve effective military and government operations through a Network-Centric approach

3. 3 Outline Call for Enterprise Transformation & Net-Centric Operations DoD Net-Centric Data and Services Strategies Community of Interest (COI) –Definition –The COI’s Relationship to the Enterprise –What COIs do OASD(NII)/DoD CIO Facilitated COIs & their Lessons COI Strategic Rhythm COIs Enable DoD Transformation Conclusions

4. 4 National Strategies Call For Enterprise Transformation & Network-Centric Operations NATIONAL SECURITY STRATEGY Transform America’s national security institutions to meet the challenges and opportunities of the twenty-first century. NATIONAL DEFENSE STRATEGY We will conduct network-centric operations with compatible information and communications systems, usable data, and flexible operational constructs. Beyond battlefield applications, a network-centric force can increase efficiency and effectiveness across defense operations, intelligence functions, and business processes... Transforming to a network-centric force requires fundamental changes in process, policy, and culture. President George W. Bush Secretary of Defense Robert M. Gates

5. 5 DoD Net-Centric Data Strategy (9 May 2003) Purpose –Describes a vision for a net-centric environment and the data goals for achieving that vision –Defines approaches and actions that DoD personnel will have to take as users—whether in a role as consumers and producers of data or as system and application developers DoD Directive 8320.2 (signed Dec 2, 2004) directs the implementation of the DoD Net­Centric Data Strategy “The…DoD Net-Centric Data Strategy provides a key enabler of the Department’s Transformation by establishing the foundation for managing the Department’s data in a net-centric environment…. The strategy also introduces management of data within communities of interest (COIs) rather than standardizing data elements across the Department.” - John P. Stenbit (former DoD CIO)

6. 6 DoD Net-Centric Services Strategy (May 2007) Purpose –Describes the DoD’s vision for establishing a Net-Centric Environment that increasingly leverages shared services and Service Oriented Architecture (SOA) –Expands upon the DoD Net-Centric Data Strategy by connecting services to the Data Strategy goals DoD and Intelligence Community (IC) are partnering to create a DoD and IC Net­Centric Services Strategy “The Department of Defense (DoD) Net-Centric Services Strategy (NCSS) reflects the recognition by the DoD that this services oriented approach can result in an explosion of capabilities for our warfighters and decision makers, thereby increasing operational effectiveness.” - John G. Grimes (DOD CIO)

7. 7 The Situation and Proposed Solution CURRENT INFORMATION SHARING CHALLENGES Accessible Web Enable Sources Provide assured access Remove Impediments — “Need to Share” Visible Advertise Information Holdings (“Tag” Data) NET-CENTRIC DATA STRATEGY TENETS (DoD Directive 8320.2) IMPLEMENTATION APPROACHES Understandable Communities of Interest (COIs) — Shared Vocabularies User UNAWARE information exists User knows it exists, but CANNOT ACCESS IT “#$^@!” User can access information, but cannot exploit it due to LACK OF UNDERSTANDING

8. 8 DoD Data Strategy Vision Pre-determined “point to point” connections within systems and applications on disparate networks Producer “pushes” information to pre-defined consumers TodayFuture Systems and applications are web- enabled to expose their information Authorized known & unanticipated consumers “pull” or “subscribe to” what they need regardless of who produced the information 3 8 Information Not Easily Shared Information Ubiquitous on DoD “Web” Source: Mr. Mike Krieger, OASD(NII)I/DoD CIO

9. 9 Net-Centric Data Sharing Benefits Manual Data + Interpretation and Context Data SharingInformation Effective Military and Government Operations Where we are today Value Added Services Operational Perspective: Increased accuracy, effectiveness and agility to respond to dynamic information sharing needs and changing enemy tactics Acquisition Perspective: Faster delivery, built-in interoperability, increased flexibility and lower costs Where DoD Net-Centric Strategies Get Us Net-CentricElectronic Net-Centric

10. 10 Outline Call for Enterprise Transformation & Net-Centric Operations DoD Net-Centric Data and Services Strategies Community of Interest (COI) –Definition –The COI’s Relationship to the Enterprise –What COIs do OASD(NII)/DoD CIO Facilitated COIs & their Lessons COI Strategic Rhythm COIs Enable DoD Transformation Conclusions

11. 11 What is a COI? Cross-Component Cross-Service Cross-Agency Multi-National “A collaborative group of users that must exchange information in pursuit of its shared goals, interests, missions, or business processes and therefore must have shared vocabulary for the information exchanges.”— DoD 8320.2, December 2, 2004 “COIs … come together to address a specific information sharing mission or challenge that the COI can solve by exposing and sharing data. ”— DoD 8320.2G, April 12, 2006

12. 12 COIs Solve Information Sharing Problems by Making Data & Services … Connected to the network with tools to use & provide assured access Discoverable by most users Net-Centric Data Sharing Trusted Governable Syntax (structure) and Semantics (meaning) are well documented Visible Accessible Understandable Governed with sustained leadership; Institutionalize data approaches Source authority (from who, how old, etc.) known and available

13. 13 The COI’s Relationship to the Enterprise Extracted from DoD 8320.2G, “Guidance for Implementing Net-Centric Data Sharing,” April 1, 2006. servicedata service Information Sharing Capabilities JCIDSAcquisition PPBE DOD Components Business Mission Area Warfighting Mission Area Intelligence Mission Area (DoD portion) Enterprise Information Environment Mission Area Recommendations on implementation of COI agreements COI COIs provide recommendations for information sharing capabilities to DoD Components and Mission Area Leads Components use existing processes to plan, budget & manage resources PPBE: Planning, Programming, Budgeting, and Execution JCIDS: Joint Capabilities Integration and Development System Mission Area Leads look across Component plans & budgets in mission area to identify best value for the Enterprise Mission Areas are cross-DoD Component portfolios of related investments

14. 14 DoD Instruction 5000.2 Calls for Pilots DoDI 5000.2, Operation of the Defense Acquisition System, states: –3.3.2.1. …requirements are refined through demonstration and risk management…requirements for future increments depend on feedback from users … –3.6.5. … Multiple technology development demonstrations may be necessary … –3.6.6. … identification and development of the technologies necessary for follow- on increments continues in parallel with the acquisition of preceding increments… Post Milestone-B programs (Development & Demonstation Phase) can (and should) spend current-year funds on pilot demonstrations to define the next increment! Source: Mr. Dan Risacher, OASD-NII/DoD CIO

15. 15 More on Funding… COIs succeed through active engagement and commitment of members and leadership to solve a specific information sharing problem COIs don’t directly control resources but COI members and leadership do –COI Authority comes from its membership and leadership Data producers (i.e., programs) should pay to expose their data on the Global Information Grid The only “COI funding” is administrative overhead !

16. 16 What do COIs do? Solve mission-specific information sharing problems affecting their communities –Increase information sharing volume, speed, and reach to known and unanticipated users –Provide a user forum to drive the Net-Centric approach forward Provide information exchange vocabulary stewardship Foster collaboration within and across communities Build trust Identify and help resolve enterprise issues !

17. 17 The COI Process Identify information sharing problem Join existing COI or form new COI Identify and prioritize capabilities Address information sharing problem increment Obtain user feedback Make recommendations to Components and Mission Area Leads Disband when appropriate < 3 mo. 9-12 mo. Capability Needed Capability Needed Service Needed Service Needed Data Needed Data Needed Info Sharing Needed Info Sharing Needed Vocab & Implementations Vocab & Implementations Drives Vocabulary = Agreements on terms and definitions common to the COI, including data dictionaries (DoD 8320.02G)

18. 18 COI Activities Showing Promise… C2 Space Situational Awareness (SSA) — Enable operational and tactical command and control with information on status of space-related systems (red, blue, gray) Maritime Domain Awareness (MDA) (includes Federal partners) — Enable improved homeland security through maritime situational awareness Strike (includes coalition partners) — Enable accelerated strike planning by providing situational awareness information (blue, red, gray force) from now to 12 hours Significant Activities (SIGACT) Reporting (includes Intelligence Community) — Enable improved information sharing and agility to counter IED threat. …But More Successes are Needed to Motivate Delivery of Mission Capabilities through Improved Information Sharing

19. 19 A Sampling of COI Metrics C2 SSAMDAStrikeSIGACT StartedSpring 2005Feb 2006June 2006July 2007 Led ByAFSPC/A5Coast Guard Navy USSTRATCOM JFCC GSI/CDR OPNAV N6 Primary Organizations AFSPC, Army, USSTRATCOM Navy, Coast Guard, IC, DoT USSTRATCOM, USA, USN, USAF, USMC, Allies CENTCOM, JIEDDO, DIA, Services, DoJ, DHS, JFCOM Vocab – Size for 1 st pilot 20 elements 56 attributes 10 elements 40 attributes 3 elements 31 attributes Not Applicable Vocab - # implementations 6 43Not Applicable Time to 1 st pilot 12 months8 months16 months Not Applicable Biggest BenefitMany firsts built upon by subsequent COIs Exemplar for SOA imple- mentation Leading to DoD & IC Universal Core Not Applicable

20. 20 Key COI Lessons To Date Cultural change is hard, technology is easy –Willingness to share; TRUST; Optimize for the enterprise Cross-organization participation is essential –Strike COI: UK/Coalition involvement has enhanced community –MDA COI: Active collaboration among DoD, DHS, IC, and DoT Pilots are an effective means to reduce risk –Clearly define scope, expectations, and resource commitments up front; Document information sharing agreements early –Must engage Resource Sponsors for year of execution funds Scoping is vital –Clearly defined so COI members have clarity of mission and unity of effort; Tackle in achievable increments Incentivizing Net-Centric delivery is needed –Consider entire enterprise including unanticipated users COIs expose Net-Centric barriers so they may be taken on as something to be changed

21. 21 Service Registry Metadata Registry COI Strategic Rhythm Vocabularies Services Evolve Vocab Transition Vocab Evolve Vocab ID Risks Risk Reduction; Transition Capabilities Program of Record (POR) Program of Record (POR) Data Management Working Group Data Management Working Group Develop Each COI is unique. After addressing an information sharing problem increment a COI may: Disband Address the next Roadmap increment Each COI is unique. After addressing an information sharing problem increment a COI may: Disband Address the next Roadmap increment Register Pilot Working Group (optional) Pilot Working Group (optional) Community of Interest (COI) Information Sharing Need Information Sharing Need Capability Delivery Capability Delivery

22. 22 COI Strategic Rhythm – The Big Picture Analagous to the World Wide Web Positive Operational Effect # Net-Centric Services COI A Global Information Grid Kickoff Capability Delivery Your capability deliveries lead to exponential growth in Enterprise Capability COI B COI C Capability Delivery

23. 23 COIs Enable DoD Transformation TIME Program COI Data & Services tightly coupled to applications System specific vocabularies Services start to emerge N 2 integration problem Decouple data from applications Service enable data Create standards-based vocabularies (community & core) to enable interoperability Data and Services available on the GIG Composable services Programs provide services or value-added services Program Service Data Organization & processes tied to ITCOIs cut across organizations using existing processes Organization & processes independent of IT Deliver ServicesDeliver Systems

24. 24 Conclusions Widely recognized need for Net-Centric Operations DoD Net-Centric Data and Services Strategies are key enablers for Enterprise transformation –COIs enable DoD Transformation –COIs provide an opportunity to address Joint, inter-agency, and coalition information sharing challenges But challenges remain – we are pioneering Net-Centric transformation and need your help to: –Implement the things we know how to do –Address the remaining challenges –Continue to innovate as technology changes and needs evolve Progress is being made but your help is needed to achieve effective military and government operations

25. Connecting People With Information AOC Achieve net-centric operations where anything on the network can be dynamically integrated to support any mission. Get Connected Share Information Achieve Netcentric Ops No Warrior Fights Alone Courtesy of Fred Stein (COL, USA. ret), Net-Centric Warfare Senior Principal Engineer, MITRE

26. 26 Backup Charts

27. 27 Tenets of Net-Centric Operations DoDNet-Centric Data Strategy InformationAssuranceStrategy Global Connectivity (TransformationalCommunications) Core Enterprise Services(NCES) Global connectivity, real-time collaboration, and rapid and continuous information exchange 27 Modified From: NCES Overview, Dec 2006 – available at: http://www.disa.mil/nces/ COIs Exercise & Evolve Training Focus Today

28. 28 COIs Support Portfolio Management QDR 2006 moved DoD toward the use of “joint capability portfolios” to change how the department does business DoD Deputy’s Advisory Working Group (DAWG) –A body of the Department’s senior civilian and military leaders co- chaired by the Vice Chairman of the Joint Chiefs of Staff (CJCS) and the Deputy Secretary of Defense (DSD) –Established four pilot portfolios to evolve the Department’s business practices and methodologies COIs and COI pilots address information sharing problems and –Continuously refine the Department’s business processes –Inform acquisition programs to make them more effective “The goal is better effectiveness and, through it, better efficiency – we have to do the right things, and we have to do them right. I can tell you that our work is still not finished. The DAWG is continuing to debate and refine our approach.” - Gordon England, DSD

29. 29 History of the Universal Core Standards Principles Initial Strike COI Vocabulary Strike Pilot Decide to adopt as a starting point for Universal Core Form Working Groups: –Policy –Governance –Test & Eval –Description Goal: Increased info sharing Senior Enterprise Services Governance Group (SESGG) Implementations to solve operational needs SESGG Forms Intelligence Community DoD TODAYFUTURE Strike COI Business Transformation Air Force CoT JC3IEDM Army Air Ops COI Air Force JTM Navy CoT = Cursor on Target JC3IEDM = Joint C3 Information Exchange Data Model JTM = Joint Track Management Harmonization across organizations is HARD Lightweight interoperability standards and leadership are required Stakeholders need an Enterprise perspective DoD

30. 30 Key Challenges Identifying a technical solution is not the biggest challenge…

31. 31 Tools COIs (and Programs) May Use Net-Centric Core Enterprise Services (NCES) Universal Core –A universal core data schema that enables information sharing –Deliver capabilities that support and enable the Business, Warfighting, and Intelligence Mission Areas to achieve network-centric operations Task/Mission Universal Core

32. NCES Overview Macro Perspective NCES Capabilities Service Security Content Delivery Mediation Content Discovery Collaboration Service Discovery Enterprise Service Management People Discovery User Access via DKO (SIPR & NIPR) Service Oriented Architecture Foundation NCES is delivering capabilities to enable the Department’s Net-Centric Transformation! Metadata Registry Net-Enabled Command Capability Global Combat Support System Distributed Common Ground System National Geospatial-Intelligence Services Theater Battle Management Core System Integrated Strategic Planning & Analysis Network Defense Technical Information Center NCES Early Capabilities Baseline Users NCES Users Global Command & Control System Communities of Interest

33. 33 DoD and IC Universal Core Data Schema Universal core data schema to enable information sharing –Describes “when, where, what” –Includes minimal set of terms –Agreed to by DoD and Intel community –Uses appropriate open and Federal standards  Geography Markup Language (GML)  Intelligence Community – Information Security Markings (IC- ISM XML schema) –Extensible by COIs, services, and systems as needed Task/Mission COI Extensions Service/Organization Specific Extensions Domain Common Core Universal Core When Where What Increased Agility and Interoperability

34. 34 Strike COI Schema - Key Events JUN 14-15 – Strike COI Data Mgmt Working Group (DMWG) established JUN-JUL – Several contentious meetings on problem approach, scope, and proposed solutions –Different organizations, cultures and perspective; trust; –Each organization thinks they have the best (possibly only) solution AUG 4 – Draft Logical Data Models and Schemas Distributed –No consensus – voting was along service lines SEP 21 – Steering Committee (SC) Meeting –Directs re-focus on vocabulary and defining a common Strike implementation –Requests new support from “outside” technologists OCT 24-28 – Consensus reached on standards-based model partitioned into loosely-coupled core and Strike extensions NOV 6 – Steering Committee Meeting – Approach Approved DEC 8 – Final Draft Schema distributed for “official review” (after several iterations) JAN 8, 07 – Final Schema Delivered to USSTRATCOM JAN 07 – Senior Enterprise Services Governance Group formed

35. 35 Universal Core Background Senior Enterprise Services Governance Group (SESGG) formed in January 2007: –To increase collaboration on information sharing between DoD and the Intelligence Community (IC) –By the DoD CIO and the Associate Director of National Intelligence and Chief Information Officer (ADNI CIO) SESGG Chairs: –Mr. Mike Krieger, Office of the DoD CIO –Mr. Steve Selwyn, Office of the ADNI CIO SESGG Members: From each of the Services, USD(AT&L), DISA, and DIA First Undertaking: Review and adopt a DoD and IC Universal Core data schema Increased DoD & IC Info Sharing & Agility

36. 36 SESGG Vision and Purpose SESGG Vision –Ensure that the DoD and IC Net-Centric Environment (NCE) evolves to an enterprise services-based architecture that improves the joint community’s ability to respond to evolving operations and mission through increased information sharing and agility. SESGG Purpose –To drive a DoD and IC implementation of a joint Net-Centric Services and Data Strategy in support of mission requirements –Ensure that recommendations on data and enterprise services policies, implementation guidance, standards, and processes align with interoperability and information sharing objectives and are made in the best interests of the joint Enterprise –An advisory body to the  Director, Information Policy (IP),  Office of DoD Chief Information Officer (CIO), and the  Deputy Associate Director of National Intelligence for IC Enterprise Architecture, Office ADNI Chief Information Officer (CIO). Increased DoD & IC Info Sharing & Agility Reference: Senior Enterprise Service Governance Group Charter – January 2007