1

Unclassified

Unclassified

Global Force ManagementData Initiative

Joint Staff, J-8

14 December 2004

2

Unclassified

Unclassified

Global Force ManagementPurpose

To provide a high level overview of the Global Force Management (GFM) and the Force Structure Construct (FSC), specifically:

–Documentation of the DoD Force Structure

–The unique identification of force structure elements across the GIG, and

–The data dissemination processes

3

Unclassified

Unclassified

GFM Bottom Line

• Force structure pulls everything together– Readiness reporting

– Resources (including personnel & equipment)

– Capabilities

• Devil’s in the details– Need commonality between Services

– Need common naming (Enterprise-Wide Identifiers)

– Default operational force structures• Starting point for any joint task organization

• Readiness– Reporting is based on force structure

– Personnel & Materiel are tied in below the UIC level

– Reporting must be rigorous for any task organization

4

Unclassified

Unclassified

Global Force ManagementDirection

• Document the “Authorized” force structure in a single, authoritative data source (ADS)

• Improve the SecDef's ability to manage risk across current worldwide operations, warfighting capabilities, and future force capability needs(i.e., Assignment, Allocation, and Apportionment)

• Make net-centric GFM data transparent, easily accessible to all users, and shared using common standards and resources

• GFM is referred to two distinct ways:– The GFM Process– GFM Data

5

Unclassified

Unclassified

Data is not visible, accessible, or usable

Directives1. Per SecDef’s Memo, JS to integrate assignment, allocation and apportionment processes2. Per SROC Guidance, the JS will implement enterprise-wide unit identifiers 3. Per SPG FY06-11, CJCS to develop/organize force structure data across Service lines

Today’s Processes

Ass

ign

men

t

SECDEF DecisionsA

lloca

tio

n

Ap

po

rtio

nm

ent

WargameArbitration

GFM ProcessProblem Statement

Where are the forces today?What operations are we

committed to?What residual capability exists?

What happens if…?

6

Unclassified

Unclassified

GFM Data Problem Statement

DoD needs Global Force Management Data• Force Structure Data

– Current Unit Locations– “Event” data – Operational Availability– Total US Inventory– Joint hierarchically

organized• Historical archive• Timely, reliable, and

authoritative

What is the readiness of the available forces?

Who has recently deployed?How accurate/timely is my

information?

Need to make the data available in a Net-

Centric environment!

DoD cannot anticipate all of the Global Force Management questions that will need to be addressed for senior DoD leadership…the enterprise must have access and visibility to GFM data in a net-centric environment.

7

Unclassified

Unclassified

61 el. Theater

8GHz MBR

169 el. 7GHz MBT

44

/20

256 element

TPA484 element

RPA

“The two truly transforming things, conceivably, might be in information technology and information operation and networking and connecting things in ways that they function totally differently than they had previously. And if that's possible, what I just said, that possibly the single-most transforming thing in our force will not be a weapon system, but a set of interconnections and a substantially enhanced capability because of that awareness.”

Secretary Rumsfeld - Aug 9, 2001

Net-Centric Vision

Platform-Centric Information Advantage

Net-Centric Information Advantage

InformationQuality

Content Accuracy Completeness Timeliness Relevance

Local Global Regional

Net-Centric OperationsThe Way Ahead

Goals of Net-Centricity• Make information available on a network that people depend on and trust• Populate the network with new, dynamic sources of information to defeat the enemy• Deny the enemy comparable advantage and exploit weaknesses

InformationApplicability

8

Unclassified

Unclassified

Cross Domain COI’s (e.g. Global Force Management, M&S)

DoD (Title 10) IC (Title 50)

UsersUsers

Business Domains Warfighter Domains

Force Application

COI’s

Protection

Command & Control

FinancialManagement

Logistics

Domain/ COI

capabilities

Levels of services

above core level

ICOrg Spaces

National Intelligence Domain

Core Enterprise Services (CES)Transformational Communications (TC) & Computing Infrastructure

ApplicationUser

AssistantStorage Messaging

Acquisition Expedient COI’s

Installation & Environment

COI’s

COI’s

COI’s

Focused Logistics

Human Resource Management

Battlespace Awareness

Info Assurance/Security

IA/Security

ESM

IA/Security

ESM

IA/Security

ESMDiscovery

IA/Security

ESM

Collaboration

IA/Security

ESMEnterprise

Service Management

(ESM)

Mediation

IA/Security

ESM

IA/Security

ESM

Technical Infrastructure

Domain

ICSIS Community Space

Global Information Grid (GIG) Enterprise Services is way to common capabilities

9

Unclassified

Unclassified

A joint hierarchical way to organize (document) force structure data for integration across Service-lines

– Top to bottom (billet level) organizations with operational organizational aspects (Tactics, Techniques, and Procedures)

– Provides common semantics and rules for documenting FSC– Documented in an organizational server for use by multiple

enterprise programs (DRRS, DIMHRS, C2, etc.)

• XML tagging for web services (e.g., discovery, collaboration, mediation, etc.)

• FMIDs (unique EWID data identifiers) to allow data integration

DB1

DB2

DB3

XML

XML XML

RECORD SETS EXCHANGED VIA XML

DB1

DB2

DB3

XML

XML XML

RECORD SETS EXCHANGED VIA XML

. . .. . .1 32

64 Bit (8 Byte) EID

32 Bits (4 Bytes) Local Sequence

32. . .. . .1

32 Bit (4 Byte) EID Seed

Prefix Suffix

. . .. . .1 32

64 Bit (8 Byte) EID64 Bit (8 Byte) EID

32 Bits (4 Bytes) Local Sequence32 Bits (4 Bytes) Local Sequence

32. . .. . .1

32 Bit (4 Byte) EID Seed

Prefix Suffix

Force Structure Construct

Disseminate• Org Servers are the Authoritative Data Source • Web-service-enabledIdentify

Document

GIG / NCES Core Enterprise Services

GFM Graphical USER Interface

(pull on demand)

Default Force Structure“Empty Shell”Authorization

ADSLocation

ADSEquipment

ADSActivity/

Event

ADSActivity/

EventADS

Equipment

ADSPersonnel

ADSPersonnel

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

GIG

ADSActual

Unit

NIPRNET SIPRNET

GFM Graphical USER Interface

(pull on demand)

Default Force Structure“Empty Shell”Authorization

ADSLocation

ADSLocation

ADSEquipment

ADSEquipment

ADSActivity/

Event

ADSActivity/

Event

ADSActivity/

Event

ADSActivity/

EventADS

EquipmentADS

Equipment

ADSPersonnel

ADSPersonnel

ADSPersonnel

ADSPersonnel

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

OrgServer

GIG

ADSActual

Unit

ADSActual

Unit

GIG / NCES Core Enterprise Services

10

Unclassified

Unclassified

A

1 2

H

3 4

I

5 6

J

7 8

K

D E

B

9 10

L

11 12

M

13 14

N

15 16

O

F G

C

Why Put A Node (Aggregation Point) in an Org Chart?

is_composed_of

• Billet: Leaf node with a (designed) 1:1 correspondence with a person

BILLETS1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

• Crew: Internal node with a 1:1 correspondence with a platform designed for operation by one or more persons and transportthose persons.

A

H I

F

J K N O

• Doctrinal: Internal node that serves as an arbitrary aggregationpoint due to doctrine, tactics, techniques, or procedures

Regiment B

Company D

Squadron C

D

B C

E

L M

G

11

Unclassified

Unclassified

Force Structure Construct (FSC)

|

CO HQ

1SG

NBC

|

A

DVR

998CO

998XO

113CP

1078 SPL

PL

GNR

LDR

TCM

TC

GNR

LDR

TCM

PSG

GNR

LDR

TCM

TC

GNR

LDR

TCM

3

A B

M1TK 2

M1TK 4

M1TK 3

M1TK 1

PL

GNR

LDR

TCM

TC

GNR

LDR

TCM

PSG

GNR

LDR

TCM

TC

GNR

LDR

TCM

2

A B

M1TK 2

M1TK 4

M1TK 3

M1TK 1

PL

GNR

LDR

TCM

TC

GNR

LDR

TCM

PSG

GNR

LDR

TCM

TC

GNR

LDR

TCM

1

A B

M1TK 2

M1TK 4

M1TK 3

M1TK 1

CO

GNR

LDR

TCM

XO

GNR

LDR

TCM

HQ CO

Trains

M1WM

M1HQ

ARM

SSG

SPL

MGR

TC

TLR SPL

1-67 AR BN

94 AOS Organizations14 Doctrinal Organizations

15%17 Crew Organizations

18%63 Billets (5 OFF / 58 EN)

67%

94 AOS Organizations14 Doctrinal Organizations

15%17 Crew Organizations

18%63 Billets (5 OFF / 58 EN)

67%

Node LegendNode Legend

Doctrinal Organizations

Crew Organizations

1078 Materiel (e.g., Vehicle)

PL

M1

Billet Organizations

12

Unclassified

Unclassified

Force Management Identifier Specification

• Force Management Identifiers:– Are the collection of identifiers used in the GFM Information Exchange Data

Model (GFMIEDM) (e.g., the “Organization-Identifier” and “Alias-Identifier” are FMIDs)

– Includes all GFMIEDM Identifiers and Indexes– Are of data type Enterprise-wide Identifier [EWID]– Can be used to uniquely identify any data across the GIG– All GFM data is tagged for ease of software development and interoperability

• An Enterprise-wide Identifier [EWID] data type is:– A non-intelligence bearing, 64-bit number that includes no information about

the entity it identifies, composed of a 32-bit prefix and a 32-bit suffix– Prefix is called an EWID Seed, is globally unique, and obtained via a

controlled server.– Suffix is local user controlled and maintained.– May be used as a primary or alternate identifier (or key)

• When any GFMIEDM data is created, it is tagged for life – this includes:– Organizations, Materiel Authorizations, Personnel Authorizations, and

Relationships and associations between these entities

13

Unclassified

Unclassified

Property BookProperty Book

DIMHRSDIMHRS

TC

GNR

LDR

DVR

Connectivity

Org ServerOrg Server

A Tank Sect

M1WMM1 HQ

TC

GNR

LDR

DVR

PL

GNR

LDR

DVR

Property BookProperty Book

UIDs

FMID

FMID

FMID

FMID

FMID

FMID

SSG JonesEDIPI

SGT SmithEDIPI

PFC MillerEDIPI

SPC LucasEDIPI

TC

GNR

LDR

DVR

PL

GNR

LDR

DVR

1st Plt/A/1-33 AR

User Database* This particular FMID is the “Organizational Identifier”, a 64-bit EWID used to ID a specific organization

14

Unclassified

Unclassified

“On-Hand” Data

AuthorizationData

GFM Org Servers

Force Development

Title 10

Authoritative Data Sources

Global Force Management FSC

C2 Systems

$.1B

$.5B

$.2B $.2B

Resources

DRRS

…

Users

OperationalData

WebServiceEnabled

FSC

WebServiceEnabled

15

Unclassified

Unclassified

GFM Data Prototype Effort

• Preparing a “Combat Slice” from each of the Services and putting it into GFMIEDM format

– Navy – Expeditionary Strike Group (ESG)

– USMC – Marine Expeditionary Unit (MEU)

– Army – Unit of Action (UA)

– Air Force – 4th Fighter Wing

• Simultaneously preparing the Concept of the Operations (CONOPS) in three areas:

– Organization Server Operations

– Allocation, Assignment & Apportionment process

– GFM in a net-centric environment

16

Unclassified

Unclassified

Summary

• Force Structure is the central integrating theme (i.e., the “foundation”) for Global Force Management

• The GFM Force Structure Construct is an organizational way to electronically document force structure data

– A fully-articulated, hierarchal, default force structure that will be the authoritative source for authorized force structure data for use by all systems within the DoD enterprise

– A net-centric means of accessing this information (XML & Web Service enabling)

– Enterprise-Wide Identifiers (EWID) for tagging data for organizations, manpower, and equipment authorizations within DoD

• POC is Mike Boller (SAIC, ISO Joint Staff, J-8, MASO) – (703) 614-6772 michael.boller@js.pentagon.mil

17

Unclassified

Unclassified

Back-Up Slides