Global Force Management Data Initiative

Transcription

1 Global Force Management Data Initiative Army GFM DI Prototype Briefing Joint Staff, J-8 21 July

2 Bottom Line: Force structure pulls everything together Personnel/Manpower Resources Materiel Plans/Readiness Capabilities Orders C2 Targeting Objectives 2 Uses Force Structure (FS) to integrate data Default FS PL GNR LDR TCM TC GNR LDR TCM LDR TCM TC GNR LDR TCM Hardcore computer science problem No silver bullet Must create the data Must document all organizations Administrative Combatant Operational Rigorously reported Starting point for any joint task organization Common identification (XML & FMIDS) Disseminate from a single authoritative data source

3 Timeline GFM-DI Long Term View w OSD GFM Data Initiative Long Term View / Related Efforts Calendar Year Policy GFM DI Proof of Concept SPG Org Servers Development All dates are estimates JPG CMP CONOPS Prototype USN USAF USMC FSC DODD FSC DODI OSD? USA JOS ~ OSD? USN USAF USA USMC JOS 2012 = IOC = FOC Applications 3 DRRS JFP FNA RP/UID DIMHRS A DIMHRS AF DIMHRS USMC DIMHRS N RP/UID GIG/NCES DIMHRS DRRS GIG/NCES

4 This is a graphical representation of the Cavalry Troop Document shows the functional alignments The Operational organizations are missing Document names are ambiguous CAV TRP Personnel data found in the (Army) D Troop, 9 th Cavalry MTOE Document 4

5 So What Is Missing? Semantics Ask 20 people to draw their org chart How many will be the same? An organization is a virtual entity - it doesn t physically exist There is nothing to ensure consistency Organizations are aggregation points for People & Equipment The OFSC provides the rules, semantics, and definitions to provide consistent Force Structure 5

6 Organizational & Force Structure Construct A 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.) DB1 XML Identify XML DB2 DB3 XML RECORD SETS EXCHANGED VIA XML FMIDS (unique data identifiers) to allow data integration Document Disseminate Org Servers are the Authoritative Data Source NIPRNET (mil) UNCLASS systems (e.g. DIMHRS) FORCE STRUCTURE OSD JOS AOS NOS MCO AFOS Guard OSD+ JOS+ AOS+ NOS+ MCO+ AFOS+ Web-service-enabled SIPRNET (mil) CLASS systems (e.g. DRRS) FORCE STRUCTURE 32 Bit (4 Byte) EID Seed 32 Bits (4 Bytes) Local Sequence Prefix Bit (8 Byte) EID Suffix DIMHRS Personnel Data by Billet USER (pull on demand) USER (pull on demand) Readiness Data by Unit DRRS

7 GFM DI Prototype Effort Preparing a Combat Slice from each of the Services and putting it into GFMIEDM format Navy 2 nd Expeditionary Strike Group (ESG) USMC 26 th Marine Expeditionary Unit (MEU) Army 1 st Brigade Combat Team, 1 st Cavalry Division Air Force CAF AEW / ISR AEG (AETF) Simultaneously preparing the Concept of the Operations (CONOPS) in three areas: Organization Server Operations Allocation, Assignment & Apportionment process GFM in a net-centric environment 7 Objectives: Define business rules, flush out GFMIEDM, and demonstrate capabilities of GFM DI prototype

8 This is what the organization looks like in the Organizational & Force Structure Construct Uses Authorization data as the basis Integrates People and Equipment into a the organizational structure Includes all organizational elements Based on fewest changes required by operators D Troop, 9 th Cavalry in the Organizational & Force Structure Construct (OFSC) 8

9 Look Closer This represents ~1/2% of the Army (~600Kb) 9

10 1 st Brigade Combat Team, 1st Cavalry Division w/ symbols ( 10

11 Behind the Org Chart MOS/Rank 19B 19K 19K 19K ORGANIZATION A M1A2 PL GNR LDR DVR Contains: People authorizations Military Civilians (GS, NAF, part-time) Contract work years Equipment authorizations Home station Relationships Names Definitions Force Developers maintain the data! 11

12 12

13 13

14 14

15 15

16 Using Links ORGANIZATION A M1 PL GNR LDR M1 TC GNR LDR SSG Jones SGT Smith SP4 Clarke PFC Snuffy DVR DVR CHANNELS Battalion Command Channel; X A/2-22 Company Command Channel; X 1/A/2-22 Platoon Command Channel; X 2/A/2-22 Platoon Command Channel; X 3/B/2-92 Platoon Command Channel; X

17 Examples: Org Tree with Times Org Tree: 2 nd - 5 th Cav Bn (WAGNAA) s_date: 1 Jan 1990 t_date: 31 Dec 2010 s_date: 1 Jan 1990 t_date: 16 Aug 2001 HHC A B C D Transition from L-Series to F-Series Structure on 17 Aug 2001 Time is REAL time it represents an Effective Date (EDATE) 17

18 18

19 19

20 Reconfiguring a Default Force Structure: A CO I nnn nnn nnn CO HQ Stable Nodes - Dynamic Links.

21 Reconfiguring a Default Force Structure: Temporary Temporary Alias: Alias: Team Team Alpha Alpha Team Alpha A CO I Temporary Temporary Parent Parent t 1 : t 2 nnn nnn nnn CO HQ 1 2 3/B3 21 No No new new nodes nodes were were required only only existing organizations were were re-linked. A new new graph graph (Unit) (Unit) was was created with with existing organizations. If If the the Default Force Force Structure is is Carefully and and Richly Richly Populated, Then Then Task Task Organizing Does Does Not Not Require Creating any any New New Organizations Stable Nodes - Dynamic Links.

22 Stable Nodes - Dynamic Links I A CO 2-11 Armor B CO t 1 : t 2 I 2-94 Infantry (Mech) CO HQ 1 nnn 2 nnn t 1 : t 2 3 nnn CO HQ 1 nnn 2 nnn 3 nnn A Company Company / / th th Armor Armor Bn Bn B Company Company / / th th Mechanized Mechanized Infantry Infantry Bn Bn Default Links ( Assigned / Organic / ADCON ) and New Temporary Links ( Attach / OPCON / TACON ) I TEAM ALPHA TF 2-11 TEAM BRAVO I TF 2-94 CO HQ 1 nnn 2 nnn t 1 : t 2 t 1 : t 2 nnn nnn nnn 3/B CO HQ 1 2 3/A nnn Team Alpha ( Tank Company Tm ) Team Bravo ( Mechanized Infantry Company Tm) 22 Simplified View of the TASK ORGANIZED Force

23 23

24 24

25 Connectivity A Tank Sect FMIDS FMIDS Property Book HQ M1 WM M1 PL TC FMIDS TC GNR GNR FMIDS GNR LDR LDR FMIDS LDR DVR DVR FMIDS DVR Org Server DIMHRS 25

26 Connectivity UIDs A 1 st Plt/A/1-33 AR FMIDS FMIDS Property Book HQ M1 PL WM M1 TC FMIDS SSG Jones TC EDIPI GNR GNR FMIDS SGT Smith GNR EDIPI LDR DVR User Org Database Server LDR DVR FMIDS FMIDS CPL Miller LDR EDIPI PFC Lucas DVR EDIPI DIMHRS 26

27 Readiness Reporting Via the Operational Links Is Dynamic, Flexible, and Continuous ESG-2 ESG HQ Wasp Strike Grp I I I 22 nd MEU (SOC) LHD-1 LPH-12 LSD-41 CG-48 Strike Grp HQ USS Wasp USS Shreveport USS Whidbey Island USS Yorktown Crew Crew Crew Crew LCU LCAC Crew D Det / ACU-2 D Det / ACU-4 BMU-2 FST-8 USS Avenger MCM-1 CE GCE ACE CSSE I I I I I I I I I 22 nd MEU CE BLT 1/6 HMM-266(Rein) MSSG-22 CG-55 USS Leyte Gulf Crew Crew USS Defender MCM-2 DDG-74 USS McFaul Crew Crew USS Robin MHC-54 SSN-22 SSN Connecticut Crew Crew USS Kingfisher MHC AOE-8 USS Arctic Crew Crew USS Blackhawk MHC-58

28 28

29 29

30 GFM DI Prototype Timeline Draft CONOPS & CMP USA 2a USN 2a TODAY USA 4a USA 4b USA 5 USMC 2a USAF 2a 2b Final CONOPS & CMP Staff FSC DODI 30 # V 3.0 LEGEND # IChart On track for completion Questionable Problem Area Completed All Services 3 USA USA 6 7 USA Slice Demos for Functional Cases Prototype USN USMC USA USAF Functional Cases ESG MEU BCT AETF 1: ID ADS G Y G Y 2a: Populate Org Servers G Y G Y 2b: Web-enable GFMIEDM Y Y Y Y 3: Test Scalability G 4a: Links Y Y Y Y 4b: Roles Y Y Y 5: Time Variables Y Y Y Y 6: Change Management Y Y 7: On-hand links Y Y Y Y 8: Assignment Y Y 9: Allocation 10: Apportionment SEP 05 8 USN 8 USA 9 10

31 Summary Force Structure is the central integrating theme (i.e., the foundation ) for Global Force Management The GFM Organizational & Force Structure Construct (OSFC) is used to electronically document force structure data Document a fully-articulated, joint, hierarchal, force structure in a single Authoritative Data Source (i.e. the Organization Servers ) for use by all systems within the DoD enterprise Identify (using Force Management Identifiers) each piece of force structure authorization data using FMIDS in the GFMIEDM format and an integrated XML schema Disseminate force structure data in a net-centric environment (Web Service enabling) POC is Mike Boller (SAIC ISO Joint Staff, J-8, MASO) (703) , Michael.Boller@js.pentagon.mil 31

32 Questions? 32