Global Force Management and the Organization Unique Identifier OUID

1
Global Force Management and the Organization
Unique Identifier (OUID)
Johnny Lopez, Chief IT Division Johnny.lopez_at_osd.p
entagon.mil 703-696-0084
2
Purpose

• Provide an overview of the Global Force
  Management Data Initiative (GFM-DI)
• Discuss the creation and use of the Organization
  Unique Identifier (OUID)

3
Why Global Force Management?
NEED GFM

• Strategic Planning Guidance (SPG), Mar 04
• Joint Planning Guidance (JPG), Jun 04
• Quadrennial Defense Review (QDR), Feb 06
• Joint Planning Guidance (JPG) VII, Jun 06
  Provide the SecDef a plan to make force structure
  authorization data visible and accessible by Sep
  07 and address the resources to reach Full
  Operational Capability (FOC) by Oct 09
• DoD Instruction (DoDI) 8260.03 Aug 06,
  Organizational Force Structure Construct (OFSC)
  for GFM Directs documenting force structure in
  the GFM Information Exchange Data Model (GFMIEDM)
  format
• Program Decision Memorandum (PDM) III, Dec 06
• Services fund GFM DI implementation by the end of
  FY 08
• GFM DI Implementation Plan approved by Deputy
  Secretary of Defense (DepSecDef), 26 Mar 07
• Capability Development Document (CCD) for GFM DI
  Increment, 1 Sep 07

DOGFM DI
USEGFMIEDM
FUND GFM DI
IMPLEMENTGFM DI
4
GFM-DI Problem

• Answering seemingly simple questions regarding
  force structure, disposition, status,
  capabilities, and associated costs can take
  months
• 30 DoD force structure systems evolved
  separatelycannot easily exchange data
• Organization structure is not consistently
  portrayed by different functional areas nor is it
  represented by common identifiers
• Command relationships are seldom documented

5
Force Structure Pulls Everything Together
6
GFM Data Initiative (GFM DI) A Critical Enabler
of the Solution

• GFM DI provides the DoD enterprise solution for
  force structure
• Creates authoritative data sources (ADSs) for
  authorized force structure
• Makes force structure visible, accessible, and
  understandable across DoD for effective and
  efficient force management
• Uniquely identifies billets, crews, equipment
  authorization, and chain-of-command links
• Allows easy integration of data from disparate
  sources
• Provides the common reference for force structure
  across DoD personnel, readiness, planning, and
  finance systems

GFM DI Enables integration of data across
domains and systems
7
Global Force Management Data Initiative
Organization Servers and Unique Identifiers
Electronically documents Authorized force
structure data for integration across DoD
Feeder Systems
ORG Servers Shared Spaces
Net-Centric Enterprise Services

Raw Data

• eJMAPS
• TFSMS
• FMS

• DRRS-N
• GCSS-AF

All Organizations Uniquely Identified (OUIDs)
AIR FORCE
ORG Servers
ARMY
MARINE COPRS
NAVY
Intel Community

• Types of Data
• Billet
• Organization
• Command relationships

JOINT STAFF
OSD
Force Structure

• Billet Data
• Rank/Grade
• MOS/AFSC
• Skill Code
• Skill Level
• Service
• Effective Date
• Service Billet ID

• Elements tagged with unique identifiers
• Document hierarchies relationships
• Org Servers are the Authoritative Data Sources
  for force structure

ANG
ARNG
8
Development Timeline for GFM Component Org Servers

• Target Initial Operational Capability (IOC) No
  later than (NLT) Sep 08
• Authorization data for forces assignable
  (deployable) to Combatant Commanders
• Includes Active, Guard, Reserve, civilians and
  embedded contractors, and equipment
  authorizations (crew vehicles)
• Target Full Operational Capability (FOC) Oct 09
  
• Authorization data for all forces
• Includes Active, Guard, Reserve, civilians and
  embedded contractors, and equipment
  authorizations (crew vehicles and
  Component-specific level of detail)

9
Why is an OUID Needed?

• As information is exchanged between enterprise
  systems on the Global Information Grid (GIG),
  information must be unique to preclude collision
  of data from multiple sources
• An OUID will serve as a primary key to link
  organizational information to other functional
  systems
• An OUID will be generated for organizations
  within the Component Organization (Org) Servers
• Required by Department of Defense Directive
  (DoDD) 8320.03 (Unique Identification) and by
  DoDD 8260.03 (Organization Force Structure
  Construct)

10
OUID Concept

• Uniquely identify Organizations in an
  authoritative data system (ADS) so that Force
  Structure information can be provided for machine
  use in Enterprise systems on the GIG
• Leverage the use of GFM Organization Server Force
  Management Identifiers (FMIDS) as the
  Organization Unique Identifiers for all DoD
  organizations
• GFM Org Servers use FMIDS as a primary key to
  identify all information in the Org Server
• The subset of FMIDS that identify organization
  nodes are OUIDS
• Expose OUIDs to the web in a central registry or
  phone book
• Provide pointers to the source system for the
  OUID
• Provide a map to other alias organization
  identifiers
• Mirror the OUID Registry in the classified
  environment

11
FMIDS/OUID Relationships
FMIDS are the collection of identifiers and
indexes used to identify each piece of data
within the Org Servers
Service Major
Command
Top Level Unit
Subordinate Unit
Subordinate Unit
Crew Vehicle
Subordinate Unit
FMIDS/OUIDS (In Registry)
OUIDs are the subset of Org Server FMIDS
associated with the Organization Name
Billet
Billet
Billet
Billet
12
Users and applications use the OUID Registry to
identify organizations, then can go directly to
the Org Servers as required for details
Org Servers provide OUIDS to the Registry
Authoritative Data Sources (ADS) provide and
maintain alias identifiers in the registry
13
OUID Registry Structure
ADS Authoritative Data Source POC Point of
Contact PK Primary Key is a value that can be
used to identify a unique row in a table in a
database. FK Foreign Key is a field or group
of fields in a table that point to a key field(s)
of another table in a database. Usually a foreign
key in one table refers to the primary key (PK)
of another table.
14
OUID Registry Scope
15
What Does an OUID Look Like?

• An OUID is a 64-bit binary data element
• The OUID is built upon an Enterprise-wide
  Identifier Allocation Scheme
• An identifier that is unique across the
  enterprise (e.g., DoD)
• Fundamental characteristics
• Includes no information about the entity it
  identifies
• It is a fixed size (ease of software development
  and interoperability) of 64 bits (the smallest
  size that will do the job - bandwidth is a
  consideration)
• Allocation Scheme Global Prefix, Local Suffix
  for simplicity
• A central seed server provides the global
  prefix 4.3 Billion Seeds
• When any data is created, it is tagged with an
  identifier that remains associated with it for
  its life

16
OSD Org Server Example of an FMIDS/OUID
OUID
17
When will OUIDs be Available?

• Initial availability of OUIDs was Sep 07 for
  bridge data (DoD umbrella Organizations e.g.,
  DoD, Army, Navy)
• Initial Org Server population is only Assignable
  Forces (Sep 08)
• Full set of OUIDs available at FOC scheduled for
  Oct 09
• The prototype OUID Registry is planned for the
  summer of 08
• OUID creation and testing is being done with the
  Org Servers
• The OUID Registry will pull OUIDs from the Org
  Servers and become the phone book for
  organizations

18

• Questions?
• For additional information, visit the PR IM
  Website https//www.mpm.osd.mil or the J8/Joint
  Data Support Website http//jds.pae.osd.mil/

19

• Back Up

20
Enterprise-wide Identifier Allocation
HierarchyGFM Org Server Example
Up to 4.3 BillionServers possible
NOTE This entire process will be transparent to
the user, who will see only the OUID
Virtually UnlimitedOUIDs
Org Servers
VirtualFMIDS EwID Seed Server (ESS)w/ 4.3
Billion Seeds
30A9F5DD00000001,30A9F5DD00000002, 30A9F5DD000000
03, 30A9F5DD00000004, . .
.
EwIDSEED
https//ess.arl.army.mil
Each Org ServerCan Provide 4.3 Billion FMIDS
per seed
Note This is all transparent to the user who
will only see the resulting FMIDS associated with
the Force Structure Information
30A9F5DD
21
OUID Formulation Scheme
An enterprise-wide identifier (EwID) to uniquely
identify any item in any database can be composed
by combining unique identifiers.

• A globally unique, four byte (32 bit) EwID Seed
  is obtained from an EwID Seed Server by the Org
  Server.

Suffix
Prefix

• The Org Server generates eight byte (64 bit)
  FMIDS by appending the EwID seed prefix with a
  locally controlled, unique, four byte (32 bit)
  suffix.

• The common, eight byte (64-bit) enterprise-wide
  identifier format allows264 bit patterns 18.45
  X 1018, or 18.45 Exa-identifiers, or 18 Billion
  Billion Unique Entities to be tracked. In other
  words . . . 4.3 billion EwIDs can be produced
  from each of the 4.3 billion EwID Seeds.

22
Organization Unique Identifier (OUID)
FMIDS generated in the Org Servers are the key
to the OUID Registry
All organizational identifiers will be linked to
the OUID Registry
Org Server
Alias Identifiers
23
(No Transcript)