# Department Of Defense

## Directive


USD(AT&L)/USD(P&R)

SUBJECT:  Unique Identification (UID) Standards for a Net-Centric Department of Defense
References: (a) Strategic Planning Guidance (SPG) FY 2006-2011, March 20041

(b) Deputy Secretary of Defense Memorandum, "Actions from the Senior


Readiness Oversight Council of December 10, 2003," January 20, 2004

(c) Department of Defense Chief Information Officer (CIO) Memorandum, "DoD


Net-Centric Data Strategy," May 9, 20032

(d) DoD Directive 1000.25, "DoD Personnel Identity Protection (PIP) Program,"


July 19, 2004

(e) through (h), see Enclosure 1
1.  PURPOSE This Directive:
1.1.  Implements Reference (a) to establish policy and prescribe the criteria and
responsibilities for creation, maintenance, and dissemination of UID data standards for discrete
entities.  UID standards will enable on-demand information in a net-centric environment, which is an essential element in the accountability, control, and management of DoD assets and resources.
1.2.  Establishes policy and assigns responsibilities, per Reference (b), for the establishment
of the Department's integrated enterprise-wide UID strategy and for the development, management, and use of unique identifiers and their associated authoritative data sources in a manner that precludes redundancy.
2.  APPLICABILITY This Directive applies to the Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of 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 in the Department of Defense (hereafter referred to collectively as the "DoD Components").

3.  DEFINITIONS Terms used in this Directive are defined in Enclosure 2.


4.  POLICY It is DoD policy that:
4.1.  All relevant business, warfighter, intelligence, and enterprise information environment mission area transactions, among the Department of Defense, Federal and State Agencies,
non-governmental organizations, and domestic and foreign persons and organizations will use UID standards for discrete entities.

4.2.  UID be used as an enabler of DoD business transformation.  Management of business, warfighter, intelligence, and information environment mission area transactions will be achieved by the DoD Components' information technology applications through the use of unique identifiers.

4.3.  UID be used to enhance the capability to gather, organize, and assess information on organizations, materiel assets, people, and places to enable the DoD Components to perform their functions.

4.4.  DoD UID standards will be based on the specific data, its associated attributes, the relationships of the data, and common enterprise-wide capabilities.

4.5.  The following criteria shall apply to all UID data standards:

4.5.1.  Unique identifiers for discrete entities, their associated attributes, and relationships, shall be explicit throughout the DoD enterprise and shall enable data discovery, correlation, and sharing of information between users in a net-centric environment.


4.5.2.  A common vocabulary and definitions shall be adopted for all uniquely identified entities, their associated attributes, and relationships.


4.5.3.  International interoperability data exchange standards shall be used when appropriate.  If not available, DoD data exchange standards shall be used.


4.5.4.  Authoritative data sources, stewards, and accessibility requirements shall be designated by all DoD Components with responsibility for unique identifiers in this Directive. 5.  RESPONSIBILITIES
5.1.  The Under Secretary of Defense for Acquisition, Technology, and Logistics
(USD(AT&L)) shall:

5.1.1.  Review this Directive within 2 years to determine if it should remain current and make improvements to content, clarity, and brevity, as necessary, in coordination with the Under Secretary of Defense for Personnel and Readiness (USD(P&R)).



5.1.2.  Publish a DoD issuance for defining, implementing, and maintaining the UID
standards for DoD personal property in coordination with the DoD Components.


5.1.3.  Develop and promulgate policy guidance for defining, implementing, and maintaining location UID standards to include the real property site, real property asset, and environmental site identifiers for all real property in which the Department of Defense has a legal interest, in coordination with the DoD Components.


5.1.4.  Establish and maintain compatible data standards for the association of personal property, real property, and radio frequency identification, where applicable.


5.1.5.  Develop and issue policy guidance for defining, implementing, and maintaining the UID standards for acquisition programs, in coordination with the DoD Components.


5.1.6.  In coordination with USD(P&R), the Under Secretary of Defense
(Comptroller)/Chief Financial Officer (USD(C)), and the Federal eGov program3, establish, implement, and maintain the requirements for organization unique identification for organizations external to DoD organizations that support DoD business processes.  International interoperable data exchange standards for globally-unique identification of organizations shall be followed wherever possible.

5.2.  The USD(P&R) shall:

5.2.1.  Establish, implement, and maintain the capability to uniquely identify all organizations that must be uniquely identified to support the Chief Information Officer Memorandum (Reference (c)) in collaboration with the Chairman of the Joint Chiefs of Staff, USD(AT&L), USD(C), Assistant Secretary of Defense (Networks and Information Integration/DoD Chief Information Office (ASD(NII)/DoD CIO)), and in coordination with the

other DoD Components.  International interoperable data exchange standards for globally-unique identification of organizations shall be followed wherever possible.


5.2.2.  Publish a DoD issuance documenting and defining the process and requirements necessary to support DoD implementation and maintenance of organization UID for all organizations in collaboration with the Chairman of the Joint Chiefs of Staff, USD(AT&L), USD(C), ASD(NII)/DoD CIO, and in coordination with other DoD Components.


5.2.3.  Publish applicable DoD issuances for personnel that will uniquely identify personnel with specific associations with the Department of Defense and maintain the integrity of the unique personnel identifier in coordination with DoD Components.


5.2.4.  Determine UID standards for manpower planning, programming, and accounting, in collaboration with the USD(C), and the Director, Program Analysis and Evaluation, and in coordination with other DoD Components.


5.2.5.  Establish, implement, and maintain the capability for unique identification of personnel within the Defense Manpower Data Center (DMDC) to include active, reserve, dependent, government civilian, and appropriate contractor personnel in support of DoD
Directive 1000.25 (Reference (d)).  DMDC, under the DoD Human Resources Activity, shall create and centrally manage an unambiguous identifier to facilitate UID of each person affiliated with the Department of Defense in accordance with Reference (d).


5.2.6.  DMDC will reconcile with legacy identification codes and ensure the UID is attached to the right person in all applicable systems.


5.2.7.  DMDC will maintain a central site delivery system for providing and maintaining the person UID code throughout the DoD systems.

5.3.  The Under Secretary of Defense for Intelligence shall publish a DoD issuance for defining, implementing, and managing the UID standards for use within the DoD portion of the Intelligence Mission Area, in coordination with the DoD Components.

5.4.  The ASD(NII)/DoD CIO shall review UID strategies and implementation plans to ensure consistency with the net-centric data strategy as directed by DoD Directive 8320.2
(Reference (e)) and standards mandated in DoD IT Standards Registry (DISR)4, in accordance with DoD Directive 5101.7 (Reference (f)).

5.5.  The Heads of the DoD Components shall:

5.5.1.  Ensure the policies set forth in this Directive are effectively implemented within their respective areas of responsibility.


5.5.2.  Implement UID and develop Component UID transition plans and roadmaps.



5.5.3.  Ensure future data systems will use UID as the basis for DoD and non-DoD
integrated business transaction management based on specific data and common enterprise data capabilities.



5.5.4.  Report progress against UID transition plans and roadmaps.

5.6.  The Chairman of the Joint Chiefs of Staff shall coordinate with the other DoD
Components regarding policy for defining, implementing, and managing UID standards required to support the warfighting mission area.

5.7.  The Combatant Commands shall:

5.7.1.  Utilize UID as an enabler for identifying, tracking, and reporting of the theater battle through net-centric visibility of organizations, materiel assets, people, and places.


5.7.2.  Utilize UID to enhance the capability to gather, organize, and assess information so that Combatant Commands and Combat Support Teams can train, equip, and organize more efficiently.

5.8.  The Principal Staff Assistant(s) (PSAs) for each functional requirements area shall:

5.8.1.  Provide leadership, determine the functional requirements for, and ensure implementation of the unique identifiers in this Directive.


5.8.2.  Incorporate approved UID standards in DoD publications.


5.8.3.  Provide leadership and direct the development of cross-functional UID data standards, process roadmaps, and transition plans.


5.8.4.  Provide leadership to develop cross-functional strategies to support the implementation of the net-centric data strategy, per Reference (c).


5.8.5.  Consolidate integrated UID plans and facilitate the collaboration of UID across the Department of Defense to ensure a common approach addressing enterprise-wide interoperability.


5.8.6.  Escalate cross functional issues to the Defense Business Systems Management Committee (DBSMC).


5.8.7.  Ensure UID standards are developed in accordance with standards mandated in the DISR where applicable, per DoD Instruction 4630.8 (Reference (g)).


5.8.8.  Work with the other DoD Components, other entities, the International Organization for Standardization5, and other standards making bodies, as appropriate, to amend existing standards, or establish new standards where the available standards do not meet DoD needs.  New standards established will be proposed to the DoD Executive Agent for Information Technology Standards, per Reference (f).


5.9.  The Defense Business Transformation Agency shall:

5.9.1.  Execute the strategy of the PSAs, subject to resolution by the DBSMC.


5.9.2.  Integrate the strategy into the Enterprise Transition Plan (Reference (h)), business process reengineering, core business mission activities, and Investment Review Board matters.

6.  EFFECTIVE DATE

This Directive is effective immediately. Enclosures - 2
E1.  References, continued

E2.  Definitions


E1.  ENCLOSURE 1

REFERENCES, continued


(e) DoD Directive 8320.2, "Data Sharing in a Net-Centric Department of Defense,"
December 2, 2004
(f) DoD Directive 5101.7, "DoD Executive Agent for Information Technology Standards,"

May 21, 2004
(g) DoD Instruction 4630.8, "Procedures for Interoperability and Supportability

of Information Technology (IT) and National Security Systems (NSS),"

June 30, 2004
(h) Department of Defense, "2006 Enterprise Transition Plan," September 28, 20066

E2.  ENCLOSURE 2

DEFINITIONS


E2.1.  Attributes.  The properties or characteristics that describe, distinguish, measure, define, and identify entities.

E2.2.  Authoritative Data Source.  A recognized or official data production source with a designated mission statement or source/product to publish reliable and accurate data for subsequent use by customers.  An authoritative data source may be the functional combination of multiple, separate data sources.

E2.3.  Business Transaction.  A record of an event or a condition that creates, modifies, or deletes business data.  Each transaction represents a single business event of rightful or proper interest or concern for one or more persons, businesses, organizations, or government entities to perform, carry out, manage, or conduct its mission.

E2.4.  Enterprise.  The Department of Defense, including all of its organizational Components.

E2.5.  Entity.  An independent unit or distinguishable person, place, thing, event, or concept about which information is kept that has distinct features, objects, or attributes associated with it.

E2.6.  Personal Property.  All property (systems/equipment, materials, and supplies) except real property (facilities, structures, buildings), and records of the Federal Government.

E2.7.  Real Property.  Land, land rights, and improvements to land including all types of facilities (e.g., buildings and structures).  It includes equipment attached to and made part of facilities (such as heating systems).  It does not include separate foundations and other work necessary for installing special tooling, special test equipment, or other equipment. E2.8.  Steward.  A recognized, responsible agent of UID resources; the long-term responsibility for the care, control, and management of unique identifiers and authoritative data sources.  A steward can be responsible for one or more authoritative data sources. E2.9.  Unique Identification (UID).  A system of establishing globally ubiquitous unique identifiers within the Department of Defense, which serves to distinguish a discrete entity or relationship from other like and unlike entities or relationships. E2.10.  Unique Identifier.  A character string, number, or sequence of bits assigned to a discrete entity or its associated attribute which serves to uniquely distinguish it from other like and unlike entities.  Each unique identifier has only one occurrence within its defined scope of use.