1. DoD Transformation for Data and Information Sharing
DoD Net-Centric Data Strategy (DS) and
Community of Interest (COI) Training
Executive Overview
DoD Transformation for Data and Information Sharing
Version 1.2

2. Purpose Describe key enablers for DoD transformation
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 Net- Centric approach

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

4. POTUS: “DoD Will Be Agile”
“The United States is going to maintain our military superiority with armed forces that are agile, flexible and ready for the full range of contingencies and threats.”
- President Obama
“The US joint force will be smaller and leaner.  But its great strength will be that it will be more agile, more flexible, ready to deploy quickly, innovative, and technologically advanced.  That is the force for the future.” 
- Secretary Panetta
President Obama’s remarks:
Defense Strategic Guidance:
SECDEF remarks:
The Budget Control Act to reduce defense spending by what we have now as the number of $487 billion over 10 years
DSG Conclusion: The United States faces profound challenges that require strong, agile, and capable military forces whose actions are harmonized with other elements of U.S. national power.
Defense Security Review, 5 Jan 12

5. DoD Net-Centric Data Strategy (9 May 2003)
“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)
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 Instruction (signed Aug 5, 2013) directs the implementation of the DoD Net- Centric Data and Services Strategies

6. DoD Net-Centric Services Strategy (4 May 2007)
“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)
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

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

8. DoD Data Strategy Vision
Today
Future
Pre-determined “point to point” connections within systems and applications on disparate networks
Producer “pushes” information to pre-defined consumers
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
Information Not Easily Shared
Information Ubiquitous on DoD “Web”

9. Net-Centric Data Sharing Benefits
Information
Manual
Electronic
Net-Centric
Net-Centric
Data +
Interpretation
and Context
Effective
Military
and
Government
Operations
Where we are today
Value Added
Services
Where DoD Net-Centric Strategies Get Us
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

10. Need for DoD Transformation
Outline
Need for DoD Transformation
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. What is a COI?
“COIs … come together to address a specific information sharing mission or challenge that the COI can solve by exposing and sharing data.”—DoD G, April 12, 2006
Cross-Component
Cross-Service
Cross-Agency
Multi-National
CNSSI – Committee on National Security Systems Instruction No. 4009: National Information Assurance (IA) Glossary, 26 Apr 2010
“A collaborative group of users who exchange information in pursuit of their shared goals, interests, missions, or business processes, and who therefore must have a shared vocabulary for the information they exchange. The group exchanges information within and between systems to include security domains.”
“A collaborative group of users who exchange information in pursuit of their shared goals, interests, missions, or business processes, and who therefore must have shared vocabulary for the information they exchange.”—CNSSI 4009, 26 Apr 2010

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
Visible
Accessible
Net-Centric Data Sharing
Trusted
Governable
Source authority (from who, how old, etc.) known and available
Governed with sustained leadership; Institutionalize data approaches
Understandable
Syntax (structure) and Semantics (meaning) are well documented

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

14. DoD Instruction 5000.02 Calls for Pilots
DoDI , Operation of the Defense Acquisition System, states:
5.d.(4)(b)2.a. …Risk reduction prototypes will be included …
5.d.(4)(c) … Multiple technology development demonstrations may be necessary …
DoDI is the “Acquisition Bible”.
DoDI Interim, 25 Nov 2013, Para 5.d.(4)(b)2.a.: “Risk reduction prototypes will be included if they will materially reduce engineering and manufacturing development risk at an acceptable cost.”
DoDI Interim, 25 Nov 2013, Para 5.d.(4)(c): “Multiple technology development demonstrations, defined in the acquisition strategy, may be necessary before the operational user and material developer can substantiate that a preferred solution is feasible, affordable, and supportable; satisfies validated capability requirements; and has acceptable technical risk.”
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, DoD CIO IESP

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 DoD Information Network (DoDIN)
The only “COI funding” is administrative overhead
KEY POINT !

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
KEY POINT !

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
Service
Data
Info Sharing
Vocab &
Implementations
Drives
Vocabulary = Agreements on terms and definitions common to the COI, including data dictionaries

18. A Sampling of COI Metrics
C2 SSA
MDA
Strike
SIGACT
Started
Spring 2005
Feb 2006
June 2006
July 2007
Led By
AFSPC/A5
Coast 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 1st pilot
20 elements
56 attributes
10 elements
40 attributes
3 elements
31 attributes
Not Applicable
Vocab - # implementations 6 4 3
Time to 1st pilot
12 months
8 months
16 months
Biggest Benefit
Many firsts built upon by subsequent COIs
Exemplar for SOA imple-mentation
Lead to improved
DoD & IC
collaboration
AFSPC = Air Force Space Command
JIEDDO = Joint Improvised Explosive Device Defeat Organization (US DoD)
JFCC GSI = Joint Functional Component Command for Global Strike and Integration
USSTRATCOM = United States Strategic Command
C2 SSA implementations: Pilot DSCS Thread, Pilot NavAcc thread, SISP, ESSA ACTD, GPS (believe GPSIS), Space Intel Prep of the Battlefield (SIPB)
Sample MDA elements/attributes: elements (e.g., vessel, conveyance, time, location) and attributes (e.g., vessel name, call sign, vessel id number)
SIGACT: Lead is VADM Edwards, OPNAV N6; POC is CAPT(s) Stu Wharton

19. 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
DHS= Department of Homeland Security
DoD = Department of Defense
DoT = Department of Transportation
IC = Intelligence Community
COIs expose Net-Centric barriers so they may be taken on as something to be changed

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

21. COI Strategic Rhythm – The Big Picture
COI B
COI C
Capability Delivery
Capability Delivery
DoD
Information
Network
COI A
Kickoff
Analagous to the World Wide Web
Exponential growth in capability (a “network effect”) is possible
Metcalf’s Law: The usefulness of a network equals the square of the number of users.
Your capability deliveries lead to exponential growth in Enterprise Capability
Positive Operational Effect
# Net-Centric Services

22. COIs Enable DoD Transformation
TIME
Deliver Systems
Deliver Services
Program
Program
COI
COI
Program
Program
Program
Program
COI
Data & Services tightly coupled to applications
System specific vocabularies
Services start to emerge
N2 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
Organization & processes tied to IT
COIs cut across organizations using existing processes
Organization & processes independent of IT
Service
Data

23. Conclusions Widely recognized need for Net-Centric Operations
DoD Net-Centric Data and Services Strategies are key enablers for Enterprise transformation
COIs facilitate 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

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

25. Backup Charts

26. Tenets of Net-Centric Operations
COIs Exercise
& Evolve
DoD
Net-Centric
Data Strategy
Information
Assurance
Strategy
Training Focus
DoD Net-Centric
Services Strategy
Global Connectivity
(Transformational
Communications)
Global connectivity, real-time collaboration, and rapid and continuous information exchange 26

27. 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

28. Cultures coming together
Key Challenges
Identifying a technical solution is not the biggest challenge…
Trust
Cultures coming together
Optimize for enterprise, not organization
No winners and losers

29. SESGG Vision and Purpose
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