1. DoD CIO/DISA/GSA Day
4/19/2017
Transforming the Way DoD Shares Information by Establishing Communities of Interest
An Army Officer recently observed, “The Global Information Grid (GIG) exists to connect people with information”
Mike Krieger
Director, Information Policy
OASD(NII)/DoD CIO
July 13, 2006

2. We can't solve problems by using the same kind of thinking we used when we created them.
Albert Einstein

3. In a Net-Centric Environment
Data is separate from Applications, AND
Data, Value-Added Services, and Applications are:
Visible – must be discoverable by a person (or machine) who is searching for it
Accessible – available to someone (or machine) for use
Understandable – so that it can be acted upon
Smart Pull

4. B A R R I E R B A R R I E R B A R R I E R B A R R I E R
Barriers to Identifying, Accessing and Understanding Data Defining The Data Problem
4/19/2017
End-User Consumer
End-User Producer
“What data exists?“
“How do I access the data?”
“How do I know this data is what I need?”
“How can I tell someone what data I need?”
“How do I share my data with others?”
“How do I describe my data so others can understand it?” ?
User knows this data exists but cannot access it because of organizational and/or technical barriers
User knows data exists and can access it but may not know how to make use of it due to lack of under standing of what data represents
User needs it but is unaware this data exists
Organization “A”
Organization “B”
Organization “C”
Data Strategy Approach:
Discovery
Metadata
Data Strategy Approach:
Web Enabling, Web-service Enabling
Data Strategy Approach:
COIs,
Metadata Registry

5. Where is the Requirement?
What Tells Us to do It?
4/19/2017
The Net-Centric Data Strategy (signed May 9, 2003) is a key enabler of the Department’s transformation.
DoDD (signed Dec 2, 2004) directs implementation of the Net-Centric Data Strategy.
DoD – G (signed April 12, 2006) provides guidance for implementing the DoD Net-Centric Data Strategy.
The Strategy provides the foundation for managing the Department’s data in a net-centric environment, including:
Ensuring data are visible, accessible, and understandable when needed and where needed to accelerate decision making
“Tagging” of all data (intelligence, non-intelligence, raw, and processed) with metadata to enable discovery by known and unanticipated users in the Enterprise
Posting of all data to shared spaces for users to access except when limited by security, policy, or regulations
Organizing around Communities of Interest (COIs)
The Net-Centric Enterprise Services (NCES) Program aims to establish a set of Core Enterprise Services (CESs) to provide users on the GIG with a suite of common computing capabilities and service-oriented framework. The CESs will consist of common capabilities that are useful or required by most users
in the DoD Enterprise. To support a global DOD net-centric environment, enterprise users will integrate NCES capabilities into their daily mission operations. This includes the
integration of CES capabilities into applications and systems as well as architecting data systems to build upon the CES to create additional enterprise capabilities.
The goal of the NCES Program is to provide a set of core enterprise services and the framework to enable the widespread deployment of high-value enterprise services that allow data and services to be discovered and securely accessed throughout the DoD and mission partners. This increased use of networked data capabilities requires a ubiquitous, high-speed, dependable communications infrastructure. Accordingly, the NCES CESs will be deployed on the GIG and will leverage the expanded bandwidth and network availability provided by TCS, JTRS, and GIG-BE activities.

6. DDMS: Leverages Industry Standard
Make Data Visible
4/19/2017
DoD Discovery Metadata Specification (DDMS) * * *
Data Catalog
(historical) * *
U=Military Science *
DDMS endorsed by
Executive Order 13388
“Further Strengthening The Sharing Of Terrorism Information To Protect Americans”
* mandatory
DDMS: Leverages Industry Standard

7. BFT C2 COI – Content Provider Advertisement (DDMS)
4/19/2017
BFT C2 COI – Content Provider Advertisement (DDMS)
BFT Content Provider Advertisements
“ Army 3rd Infantry Division
Unclassified
Ground Tracks in
AOI1 …”
XML is readable.

8. Make Data Accessible Documents Systems Use common formats
Store in shared spaces accessible via URL
Systems
For applications: Expose data via web services
Web services = “API for the web”
For end-user: Web-enable via browser or application

9. Enable Data To Be Understandable
One reason Government Agencies and Military Services have
trouble operating jointly is that they speak different languages.
“Secure the Building!” What does it mean?
Navy: “Turn off the lights and lock the doors.”
Army: “Surround the building, occupy, and control entry.”
Marines: “Call in close air support, assault with small team, neutralize occupants, fortify and hold at all costs until properly relieved. SEMPER FI!”
and…
Air Force: “Take out a three-year lease with option to buy.”
Register Terms, Definitions, & Relationships

10. DoD Metadata Registry (MDR) and Clearinghouse
4/19/2017
“One Stop” Publish, Subscribe and Manage capabilities for Reusable Structural Metadata Components
104K XML items (schema, stylesheet etc) registered as of Feb 2006
Includes translation logic for mediation & taxonomies
6500 Registered Users from DoD, IC, DHS, NASA and more
Unclassified, Secret and Top Secret instances operating
Run Time support available
Web Services
ebXML capabilities
User feedback driven
Online user-to-developer
DoD Metadata Working Group
V5 just released
The DoD Metadata Registry is the Department’s electronic marketplace for structural metadata components. It provides enterprise-wide visibility and access for developers, configuration controllers and program overseers to register, use, subscribe, and manage structural metadata. The purpose of the Registry is not to publish broadly applicable standards, but to provide visibility into the Department’s ongoing structural metadata investment, and to encourage reuse of existing metadata components that are both developmental and operational. While each registered component is identified with its status and distinguished by a namespace, the Registry’s purpose is to allow developers to pull whatever they need; not to try and mandate usage of any particular metadata collection. The benefits to the developer: reductions in cost, time savings and interoperability, have proven to be sufficient incentive. The public may access a portion of the DoD Metadata Registry via the Internet. To examine metadata artifacts, users must be sponsored by a government employee. The contents of the Metadata Registry are organized by governance namespaces within various metadata type “galleries.” Communities of Interest (COIs) should align with and leverage collections within one or more namespaces that intersect their concerns.

11. 4/19/2017
Blue Force Tracking (BFT) COI Service An Implementation of the DoD Net-Centric Data Strategy
BFT Service Consumers
Efficient
“on-demand”
info service
BFT Content Providers
BFT Service (
JointWebCOP
FBCB2/EPLRS
Tactical
Internet
FBCB2
JVMF
IP/MCG
BFT
SVC
XML
SOAP
BFT Service PI CI
User Interface
C2PC
Air Feed
BFT Service PI CI
BFT Service PI CI
TADIL-J
L-16
XML
SOAP
ADSI
BFT
SVC
BFT Service PI CI
FalconView
MDACT/USMC
Ad/Sub
Propagation
Info
Delivery
EPLRS/
CNR
VDX IP
XML
SOAP
BFT
SVC
IOW
BFT Service PI CI
Filtering
Query
QoS
Consolidation
MCS
MMC
XML
SOAP RM
MMC
BFT
SVC
Ground
Station
NCES
Service
Discovery
Security
Messaging
ESM
FBCB2/MTS/L-Band
NCES
Integration
Web Services Info Grid
XML
SOAP
JVMF
MTS RM
FBCB2
BFT
SVC
Ground
Station
F-15 WSO

12. Net-Centric Data Strategy Enables Unanticipated Users
4/19/2017
Focus of Existing Data Administration Policy is Pre-defined Point-to-Point Interfaces
Tactical
Internet
FBCB2-EPLRS
FBCB2
MCS
MCS-L
GCCS-A
JVMF
IP/MCG
DCE
API
JCDB
OTH-G
SMTP
UNITs
CST
Data exchanged across engineered, well-defined interfaces
System A
System B
Post data
Provide Discovery metadata
Register structural metadata
FBCB2/EPLRS
Tactical
Internet
FBCB2
JVMF
IP/MCG
BFT
SVC
XML
SOAP
Shared Space
DoD Metadata Registry
Structural Metadata
Data Content
Metadata Catalog
DDMS Compliant “Metacards”
Focus of
Net-Centric
Data Strategy
Data Producer
Data Consumer
System X
System X is an Unanticipated User of System A Data
“Pull” data
Apply “pulled’ data based on registered metadata structure
Query catalog

13. What is a COI? However, members of COIs do!
4/19/2017
A community formed to solve a data-sharing problem
Are described in the DoD Net-Centric Data Strategy
What does a COI do?
Work together to resolve the issues that affect their community
Establish community standards on how information will be exchanged within the COI
What can’t a COI do?
COIs do not operate systems or provide services
COIs do not submit POMs
COIs do not direct changes to ICDs, ORDs, CDDs, or CPDs
However, members of COIs do!

14. Maritime Domain Awareness COI Pilot High-Level Pilot Architecture
4/19/2017
Maritime Domain Awareness COI Pilot High-Level Pilot Architecture
USCG R&D Center
Infrastructure:
PEO C4I&Space
MDA DS CoI
NCES SOA Foundation
Other COIs
ONI
Content Discovery
Navy Afloat
TBD
NAIS
DHS Consumers
AMRS
DOD Consumers
Registration,
Publication
Interfaces:
NCES
DoD Net-Centricity
Enterprise Architecture FS
Federated Search Web Service
Security M
Messaging Service MP
Messaging Publisher
NCES Security Service
Discovery,
Subscription MS
Messaging Subscriber
I believe the most exciting aspect of the MDA COI is that the community spans both the military and civilian agencies of the federal government and also involves nonfederal port partners. The Department of Defense (DoD) is building the Net-Centric Enterprise Services (NCES) system for military users. The Department of Homeland Security (DHS) is building the Homeland Security Information Network (HSIN) for the 22 agencies in DHS.
Before this COI, neither the NCES nor the HSIN had considered sharing data outside their department. Now, as a result of this COI, both NCES and HSIN have changed their plans to allow interoperability and synergy between their two systems.
This diagram shows how both DHS and DoD users will be accommodated. Looking to the top in the clouds are the owners of unclas AIS information that have joined our COI as data providers. These providers have agreed to publish their data as a web-based consumable service leveraging the common vocabulary and schema developed together as members of the Data Management working group.
Shifting to the lower right of the diagram, you can see the military DoD users. These users subscribe and access this information using the Defense OnLine Portal. Looking to the lower center of the diagram, you can see the nonmilitary DHS users who subscribe to and access the AIS information from NCES using the HSIN as their portal.
DHS
DOD
Service
Registration
Fed Search WebPart
Fed Search WebPart
NCES Discovery Service
HSIN
Identity Store
(Portal Authentication)
Defense OnLine
DoD Portal
HSIN
Non-DoD Portal
DoD/DHS Cooperation – Unclassified AIS Information

15. iMapData – DHS User Defined Operating Picture (UDOP) Candidate
4/19/2017
iMapData – DHS User Defined Operating Picture (UDOP) Candidate
Only for HSIN Consumers….
I believe the most exciting aspect of the MDA COI is that the community spans both the military and civilian agencies of the federal government and also involves nonfederal port partners. The Department of Defense (DoD) is building the Net-Centric Enterprise Services (NCES) system for military users. The Department of Homeland Security (DHS) is building the Homeland Security Information Network (HSIN) for the 22 agencies in DHS.
Before this COI, neither the NCES nor the HSIN had considered sharing data outside their department. Now, as a result of this COI, both NCES and HSIN have changed their plans to allow interoperability and synergy between their two systems.
This diagram shows how both DHS and DoD users will be accommodated. Looking to the top in the clouds are the owners of unclas AIS information that have joined our COI as data providers. These providers have agreed to publish their data as a web-based consumable service leveraging the common vocabulary and schema developed together as members of the Data Management working group.
Shifting to the lower right of the diagram, you can see the military DoD users. These users subscribe and access this information using the Defense OnLine Portal. Looking to the lower center of the diagram, you can see the nonmilitary DHS users who subscribe to and access the AIS information from NCES using the HSIN as their portal.

16. Reference Links
The DoD Net-Centric Data Strategy Data Sharing in a Net-Centric DoD, DODD Guidance for Implementing Net-Centric Data Sharing, DOD G DoD Discovery Metadata Specification (DDMS) DDMS Schema information COI Resources