1

Unclassified

Unclassified

Global Force Management (GFM) Data Initiative (DI)

Overview Briefing

Joint Staff, J-831 March 2005

2

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)

– The GFMIEDM provides common semantics and rules– Documented in an single authoritative data source call the

Organizational Server.

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

• FMIDS (unique data identifiers) to allow data integration

DB1

DB2

DB3XML

XML XML

RECORD SETS EXCHANGED VIA XML

DB1

DB2

DB3XML

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

Identify

Document

NIPRNET (mil) SIPRNET (mil)DOS+

JOS+

AOS+

NOS+

MCO+

GuardAFOS+

DOS

JOS

AOS

NOS

MCO

AFOS

UNCLASS systems (e.g. DIMHRS)

DIMHRS

FORCE STRUCTURE

Personnel Data by Billet

DRRS Readiness Data

by UnitUSER

(pull on demand) USER

(pull on demand)

CLASS systems (e.g. DRRS)

FORCE STRUCTURE

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

3

Unclassified

Unclassified

4

Unclassified

Unclassified

5

Unclassified

Unclassified

6

Unclassified

Unclassified

7

Unclassified

Unclassified

8

Unclassified

Unclassified

9

Unclassified

Unclassified

Property BookProperty Book

DIMHRSDIMHRS

TC

GNR

LDR

DVR

Connectivity

Org ServerOrg Server

A Tank Sect

M1WMM1HQ

TC

GNR

LDR

DVR

PL

GNR

LDR

DVR

Property BookProperty Book

UIDs

FMIDS

FMIDS

FMIDS

FMIDS

FMIDS

FMIDS

SSG JonesEDIPI

SGT SmithEDIPI

PFC MillerEDIPI

SPC LucasEDIPI

TC

GNR

LDR

DVR

PL

GNR

LDR

DVR

1st Plt/A/1-33 AR

User Application

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

10

Unclassified

Unclassified

Org Server Timelines

• Organization Server Development IOC FOC

– USAF (AF/XIWA) Jun 2005 Jan 2007– USA (G-3) Dec 2005 Nov 2006– USMC (MCCDC) Dec 2005 Dec 2006– USN (N43) Dec 2005 Dec 2007– Joint (J-8 MASO) Oct 2006 Oct 2007– DoD (P&R) TBD TBD

• Other Products Under Development– DoD Directive Org & FSC for GFM Apr 2005– Configuration Management Plan Mar 2005– CONOPS Jul 2005– Prototype Jul 2005– DoD Instruction Sep 2005– Overarching Capstone Identifier Directive

11

Unclassified

Unclassified

DoD Directive & Instructions

• The Directive was initially staffed under a different name in April 2004

• After combining the FSC Directive and the FSID Directive, it was re-staffed in November 2004– Several hundred comments were received

– Most comments were administrative in nature

– Most “Substantive/Critical” comments simply require clarification

• The DODD has been re-written to incorporate all relevant comments

• DODI is awaiting lessons learned from the prototype– Initial draft is complete

DoD Directive: Organizational and Force Structure Construct (FSC) for Global Force Management (GFM) at USD (P&R)

12

Unclassified

Unclassified

GFM DI Prototype Effort

• Preparing a “Combat Slice” from each of the Services and putting it into GFMIEDM format– Navy – 2nd Expeditionary Strike Group (ESG)– USMC – 26th Marine Expeditionary Unit (MEU)– Army – 1st Brigade Combat Team, 1st Cavalry Division– Air Force – 4404th Wing (Provisional) - AEW

• Simultaneously preparing the Concept of the Operations (CONOPS) in three areas:– Organization Server Operations– Allocation, Assignment & Apportionment process– GFM in a net-centric environment

Objectives: Define business rules, flush out GFMIEDM, and demonstrate capabilities of GFM DI prototype

13

Unclassified

Unclassified

Application Threads - Capability Based Planning Example

• Focus Area: Link forces to capabilities• Issue: Force structure capability is not defined• Systems affected: Command & Control, Readiness, Finance and Accounting,

Master Capabilities Library, Maintenance Management systems, and GFM Org Servers

• Concept:– Tie capability to the authorization data for an organization– Use the capabilities (e.g., UTCs) to determine force requirements

• Scenario: Augmented AEW at Prince Natlus Air Base• Discussion Points:

– What are the capabilities of this force?– What are the corresponding assets that relate to these capabilities and

their current availability?– How much does this capability cost for normal operations for a 90-day

period?– What is the current readiness status of his forces?

• GFM COI Applicability: Need to add “Capabilities” to GFMIEDM

14

Unclassified

Unclassified

GFM DI Prototype Timeline

• All FC complete• Final CONOPS & CMP

Draft FSC DODI

Draft CONOPS EXSUM & CMP Draft

Operational Architecture

I-ChartV 3.0

LEGEND:

Completed

On track for completion

Questionable

Problem area

I-ChartV 2.0

DraftCONOPS

JUL 05

StaffFSC DODI

TODAY

ESGESGSlice Slice

CompleteComplete

AEWAEW

SliceSliceStartStart

BCTBCT

SliceSliceStartStart

MEUMEU

SliceSliceStartStart

15

Unclassified

Unclassified

Long Term View / Related Efforts

2004 2005 2007 2008

GFM DIGFM DI CONOPsCONOPs

Org ServersOrg ServersDevelopment Development

Calendar Year

JPGJPG

ApplicationsApplications

All dates are estimatesAll dates are estimates

2012

GIG/NCESGIG/NCESGIG/GIG/

NCESNCES

JFP FNAJFP FNA

2006

DODDDODD

CMPCMPSPGSPG

PrototypePrototype

= FOC

= IOCDIMHRSDIMHRS

USAFUSAFUSNUSN

USAUSAUSMCUSMC

JOSJOS

DRRS

USAUSA

DRRS

JOSJOSUSMCUSMC

USNUSNUSAFUSAF

DIMHRS NDIMHRS N

DIMHRS AFDIMHRS AFDIMHRS ADIMHRS A

DIMHRS USMCDIMHRS USMC

~DODIDODI

16

Unclassified

Unclassified

Questions?