Implementing the Sharing of Data, Information, and Information Technology (IT) Services in the Department of Defense1. PURPOSE. In accordance with the authority in DoD Instruction (DoDI) 8320.02 (Reference
(a)) and DoD Directive (DoDD) 5144.02 (Reference (b)), this instruction:
a. Establishes policy, assigns responsibilities, and prescribes procedures to implement
Reference (a) and to enable a secure sharing environment in the DoD that supports the
warfighting, business, DoD intelligence, and enterprise information environment mission areas.
b. Describes or references key enablers necessary for sharing data, information, and IT
services and ensuring data, information, and IT services are visible, accessible, understandable,
trustworthy, and interoperable. Key enablers include, but are not limited to, concepts, processes,
governance forums, standards, models, and shared vocabularies.For the purposes of the instruction, data sharing and information sharing are equivalent terms. Service and IT service,
are used interchangeably throughout this instruction. IT services include DoD Enterprise
Services; however, not all IT services are DoD Enterprise Services.
c. Guides the use of resources for implementing the sharing of data, information, and IT
services within the DoD Information Enterprise (IE) and with mission partners.
d. Incorporates and cancels DoD 8320.02-G (Reference (c)).U.S. Department of DefenseDOD_5e8dcfdc-5d6a-11df-839d-400e7a64ea2aTerry A. HalvorsenChief Information OfficerDoD Components2. APPLICABILITY
a. This instruction applies to:
(1) OSD, the Military Departments, the Office of the Chairman of the Joint Chiefs of
Staff (CJCS) and the Joint Staff, the Combatant Commands, the Office of the Inspector General
of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other
organizational entities within the DoD (referred to collectively in this instruction as the “DoD
Components”).OSDMilitary DepartmentsOffice of the Chairman of the Joint Chiefs of Staff (CJCS)Joint StaffCombatant CommandsOffice of the Inspector General of the Department of DefenseDefense AgenciesDoD Field ActivitiesUnited States Coast Guard(2) The United States Coast Guard. The U.S. Coast Guard will adhere to DoD
requirements, standards, and policies in this instruction in accordance with the direction in
Paragraph 4a of the Memorandum of Agreement between the Department of Defense and the
Department of Homeland Security (Reference (ay)).Communities of Interest(3) All new data assets, information, IT services, IT systems, and capabilities, as well as
existing data assets, information, IT services, IT systems, and capabilities when investment funds
are received for modernization, to include those managed as part of a community of interest
(COI).
(a) DoD Chief Information Officer (CIO) Memorandum (Reference (d)), key
principles, rules, constraints, and best practices apply within the Internet Protocol Boundary of
the DoD Information Network (DoDIN), including those devices that are often disconnected if
they are used to receive and share data.
(b) Outside of these boundaries, key principles still should be considered, but the
rules of the DoD IE Architecture must yield to the state of technology and the needs and
imperatives of DoD missions.Electronic Information Services(4) Data, information, and IT services in electronic form.Forward Deployed Systemsb. This instruction does not apply to data, information, and IT services supporting existing
forward deployed systems, or those systems in use in combat operations, except to the extent that
they receive investment dollars for modernization. Mandatory retrofitting of existing systems,
services, or capabilities is not required.Director of National Intelligencec. This instruction will not alter or supersede:
(1) The existing authorities and policies of the Director of National Intelligence (DNI)
regarding the protection of sensitive compartmented information (SCI) and special access
programs (SAP) for intelligence pursuant to Executive Order 12333 (Reference (e)) and other
applicable laws and regulations. The application of the provisions and procedures of this
instruction to SCI or other SAP for intelligence information systems is encouraged where they
may complement or discuss topics not otherwise specifically addressed.Business Information Exchange Partnersc. This instruction will not alter or supersede:
(2) Existing laws and policies regarding the use of existing business information
exchange standards to record the initiation of and responses to business events among the DoD,
Federal, State, local government, foreign government, and commercial trading partners that
comprise the DoD acquisition, logistics, and finance communities.The warfighting, business, DoD intelligence, and enterprise information environment mission areas are supported._cefc8eec-21e7-11ea-9da4-2753f382ea00To enable a secure sharing environment in the DoD._cefc8ffa-21e7-11ea-9da4-2753f382ea00Information ExchangeImprove information exchange across the DoD and with its mission partners._cefc90ae-21e7-11ea-9da4-2753f382ea00aa. The DoD will effectively improve information exchange across the DoD and with its
mission partners to defend the United States and enhance global stability in accordance with
DoDD 8000.01 (Reference (f)), the DoD CIO Memorandum (Reference (g)), and Executive
Order 13526 (Reference (h))._cefc9162-21e7-11ea-9da4-2753f382ea00NIEM & XMLConsider use of National Information Exchange Model (NIEM)-based exchanges for all new Extensible Markup Language (XML) information exchanges._cefc920c-21e7-11ea-9da4-2753f382ea00bb. In accordance with DoD CIO Memorandum (Reference (i)), and except as required
otherwise by law or DoD policy, the use of National Information Exchange Model (NIEM)-
based exchanges must be considered for all new Extensible Markup Language (XML)
information exchanges created and for all XML information exchanges being modernized as part
of the normal lifecycle management for these information exchanges._cefc92b6-21e7-11ea-9da4-2753f382ea00Standards & SpecificationsImplement applicable standards and specifications._cefc93a6-21e7-11ea-9da4-2753f382ea00cc. All DoD activities will implement applicable standards and specifications as cited in the
DoD IT Standards Registry (DISR) or successor registry, pursuant to DoDI 8330.01
(Reference (j)).
_cefc945a-21e7-11ea-9da4-2753f382ea00Data SourcesDesignate, register, and use authoritative data sources (ADSs) to the maximum extent possible._cefc9504-21e7-11ea-9da4-2753f382ea00dd. In accordance with Reference (a), authoritative data sources (ADSs) will be designated,
registered, and used to the maximum extent possible to improve mission effectiveness by
enabling the reuse of visible, accessible, understandable, trustworthy, and interoperable data.
Criteria to designate and register an ADS is outlined in the DoD Data Services Environment
(DSE) Concept of Operations (CONOPS) (Reference (k)) and DoD DSE User Manual
(Reference (l)). _cefc95b8-21e7-11ea-9da4-2753f382ea00MetadataCreate and associate metadata with data, information, and IT services._cefc966c-21e7-11ea-9da4-2753f382ea00ee. Data, information, and IT services will be visible to authorized users by creating and
associating metadata (“tagging”), including discovery metadata, for each asset. In accordance
with Reference (a), DoD metadata standards will comply with applicable national and
international consensus standards for metadata exchange when possible. _cefc9720-21e7-11ea-9da4-2753f382ea00Education, Training & ProcessesInclude data, information, and IT services-sharing concepts and practices in
education and awareness training and the appropriate DoD processes._cefc97de-21e7-11ea-9da4-2753f382ea00ff. Data, information, and IT services-sharing concepts and practices will be included in
education and awareness training and the appropriate DoD processes._cefc9892-21e7-11ea-9da4-2753f382ea00ComplianceComply with this instruction during planning, approval, budgeting, funding, development, purchase, implementation, certification, and operation phases._cefc9946-21e7-11ea-9da4-2753f382ea00gg. Data, information, or IT services will comply with this instruction, DoDI 5000.02
(Reference (m)), The Planning, Programming, Budgeting, and Execution (PPBE) Process
(Reference (am)), and the Data and Services Deployment Principles and Business Rules as
specified in Reference (d) during planning, approval, budgeting, funding, development,
purchase, implementation, certification, or operation phases._cefc9a04-21e7-11ea-9da4-2753f382ea00Standards, Protocols & InterfacesUse a common set of standards, protocols, and interfaces._cefc9ac2-21e7-11ea-9da4-2753f382ea00hh. A common set of standards, protocols, and interfaces will be used to enable the sharing of
DoD data, information, and IT services pursuant to Reference (d), Office of Management and
Budget Memo M-13-13 (Reference (n)) and DoDI 8551.01 (Reference (o)). A common
information-sharing technical framework will be used at all levels throughout the DoD in
accordance with Reference (d). All new IT systems must be designed for openness, expose highvalue data and content through implementation of neutral hosted services, and publish public
data sets in the list at www.defense.gov/data. For existing systems, high-value data and content
will be made available through Web application programming interfaces (APIs) and apply
metadata tagging, as appropriate. To the greatest extent possible, the DoD’s common
information sharing standards, protocols, and interfaces will be compatible and interoperable
with those of other federal departments, agencies, and mission partners._cefc9b80-21e7-11ea-9da4-2753f382ea00Identity & AccessMake data and information accessible via identity and access management
(IdAM) mechanisms._cefc9c48-21e7-11ea-9da4-2753f382ea00ii. Data and information will be accessible via appropriate identity and access management
(IdAM) mechanisms in accordance with DoD IdAM guidance. _cefc9d10-21e7-11ea-9da4-2753f382ea00Security MetadataInclude security metadata with electronic data and information intended to be shared._cefc9dce-21e7-11ea-9da4-2753f382ea00jj. Electronic data and information intended to be shared should, at a minimum, include
associated security metadata identifying its classification determination, markings, disclosure,
and handling rules in order to support access control. _cefc9ea0-21e7-11ea-9da4-2753f382ea00RecordsManage records in accordance with DoDI 5015.02._cefc9f68-21e7-11ea-9da4-2753f382ea00kk. Data and information that meets the definition of a federal record will be managed in
accordance with records management policies outlined in DoDI 5015.02 (Reference (p)). _cefca030-21e7-11ea-9da4-2753f382ea00Personally Identifiable InformationComply with DoDD 5400.11 and DoD 5400.11-R with regard to personally identifiable information and sharing of information. _cefca10c-21e7-11ea-9da4-2753f382ea00ll. All DoD activities will comply with DoDD 5400.11 (Reference (q)) and DoD 5400.11-R
(Reference (r)) with regard to personally identifiable information and sharing of information. _cefca1de-21e7-11ea-9da4-2753f382ea00Procurement & Supply ChainComply with the Federal Acquisition Regulation, Defense Federal Acquisition Regulation Supplement, and DoDI 4140.01 for sharing of data and information regarding DoD procurement and supply chain management._cefca2a6-21e7-11ea-9da4-2753f382ea00mm. All DoD activities will comply with the Federal Acquisition Regulation (Reference (s)),
Defense Federal Acquisition Regulation Supplement (Reference (t)), and DoDI 4140.01
(Reference (u)) for sharing of data and information regarding DoD procurement and supply
chain management, respectively. _cefca382-21e7-11ea-9da4-2753f382ea00AccessibilityEnable persons with disabilities to access and use information and data._cefca454-21e7-11ea-9da4-2753f382ea00nn. Individuals who are federal employees with disabilities or members of the public with
disabilities seeking information or services from the DoD will have access to, and use of,
information and data comparable to the access and use available to federal or public individuals
without disabilities, subject to appropriate access considerations and in accordance with section
794d of Title 29, United States Code (Reference (v)). For exceptions to compliance with
Reference (v), refer to DoD Manual (DoDM) 8400.01-M (Reference (w)).
_cefca526-21e7-11ea-9da4-2753f382ea002015-08-032019-12-18OwenAmburOwen.Ambur@verizon.net