Time-Based Tree Graphs for Stabilized Force Structure Representations *

Transcription

1 Time-Based Tree Graphs for Stabilized Fore Struture Representations * 8 th International Command & Control Researh & Tehnology Symposium National Defense University Ft. MNair, Washington, DC 19 June 2003 Sam Chamberlain, Ph.D. US rmy Researh Laboratory wildman@arl.army.mil (410) // DSN Chris Leeds Chief, Combat Servie Support MTOE Division U.S. rmy Fore Management Support geny leeds@hqda.army.mil (703) // DSN 655 * Sponsored and Funded by the US rmy G-8 G 8 / Diretor of Integration

2 ID Retention - Main Problem Fore struture is a (the) primary part of the initial onditions entered into battle ommand system databases. The system users add opious loal data to the initial data. Beause fore struture is at the heart of any battle ommand model, nearly all other user entities are linked to it. If the fore struture data is not stable and arefully managed, then it will be a diffiult task to maintain onsisteny in these databases. Data must not hanged unless the hanges are truly bona fide.

3 Primary Task - Change Management In the rmy, there are about 4900 MTOEs (Modifiation Tables of Organization & Equipment) [ 1550 tive Reserve/Guard ] They an hange every six months. Huge obstale to re-link systems deployed in the field, a ost that is muh bigger than the ost of hanging the MTOEs themselves. Fous: (1) Maintainability, (2) Interoperability, and (3) Generality. This led to the Org-ID Retention Projet. The fore struture representation proess must: (1) be automated and easily aessible (2) be usable by a diverse set of users and appliations (3) permeate the whole Fore Struture Development Proess (Requirements (TOE) uthorizations (MTOE) Real Units (Fores) (4) result in an openly available soure that is diretly downloadable into tatial systems (e.g., the rmy Battle Command System). (5) minimize hanges and be aompanied by a hange information to ensure onsisteny and integrity of the data after an update ours.

4 (M)TOE Struture Root Org (Mapped to Real Unit) RFL CO INF BN (MECH) (XXI) Ultimately ssigned a UIC Para: Single Clustering Level Company HQs Rifle Platoon HQS 3 Vehile Setions Rifle Squads Personnel & Equipment Data P Line # E Lin P Line # E Lin P Line # E Lin P Line # E Lin w/ Multipliers

5 Example MTOE - Personnel

6 Example MTOE - Equipment

7 LC2IEDM: 5 Basi Battlefield Entities (Land C2 Information Exhange Data Model) 1 Template Initial Fous Instane Organization-Type (Templates; (Templates; e.g., e.g., TO&Es) TO&Es) Fore Struture Organization (Real (Real Units; Units; e.g., e.g., w/ w/ UICs) UICs) 2 3 Materiel-Type Types Types of of Objets Objets w/ w/ NSNs,LINs NSNs,LINs Person-Type Cat. Cat. of of People; People; e.g., e.g., MOS s MOS s Logistis Personnel Materiel Real Real Objets Objets w/ w/ Serial Serial # s # s Person Real Real People People w/ w/ SSNs SSNs Faility-Type Cat. Cat. of of Buildings Buildings IS_ Links Faility Real Real Buildings Buildings w/ w/ ddresses ddresses Feature-Type Cat. Cat. Of Of Plaes Plaes Feature Real Real Plaes Plaes w/ w/ Numbers Numbers

8 Initial Subset of Interest Template Instane Organization-Type (Templates; (Templates; e.g., e.g., TO&Es) TO&Es) Materiel-Type Types Types of of Objets Objets w/ w/ NSNs NSNs Organization (Real (Real Units; Units; e.g., e.g., w/ w/ UICs) UICs) SORTS Person-Type Cat. Cat. of of People; People; e.g., e.g., MOS s MOS s MTOE

9 Org-Type Trees (Templates) vs Org Tree (Instanes) Org-Type Tree Rifle Co Inf Bn (Meh) Org Tree (Many) CO Co HQ nn IS- CO HQ nn nnn 3 1st Plt Rifle Platoon nnn 2nd Plt nnn nnn From the Land C2 Information Exhange Date Model, or LC2IEDM a NTO STNG. 3rd Plt

10 Possible Default Fore Struture for Tank Company 1-67 R BN CO HQ HQ CO Trains B B B HQ M1 WM M1 CP 113 1SG TK 1 M1 TK 2 M1 TK 4 M1 TK 3 M1 TK 1 M1 TK 2 M1 TK 4 M1 TK 3 M1 TK 1 M1 TK 2 M1 TK 4 M1 TK 3 M1 CO XO DVR NBC PL TC PSG TC PL TC PSG TC PL TC PSG TC GNR GNR MGR GNR GNR GNR GNR GNR GNR GNR GNR GNR GNR GNR CO 998 LDR LDR TC LDR LDR LDR LDR LDR LDR LDR LDR LDR LDR LDR TCM TCM XO 998 TCM TCM TCM TCM TCM TCM TCM TCM TCM TCM TCM GNR LDR TCM SPL SSG RM 1078 SPL TLR SPL M1 PL Dotrinal Organizations Crew Organizations Billet Organizations 1078 Materiel (e.g., Vehile) 94 OS Organizations 14 Dotrinal Organizations 15% 17 Crew Organizations 18% 63 Billets (5 OFF / 58 EN) 67% Node Legend

11 MTOE Identifiation - Overloaded Definitions DOCNO: [Series] CCNUM: WGL WGN WEZE 07245LFC FFC ug pr pr 03 WEZK Earliest E-Date Time 16 Ot 98 FY99 16 Ot 99 FY00 16 Ot 00 FY01 17 ug 01 FY01 17 Ot 01 FY02 16 De 01 FY02 19 ug 02 FY02 17 Jan 03 FY03 16 Ot 03 FY04 DOCNO/CCNUM or UIC/EDTE uniquely identifies an MTOE Question: re there 9 or 23 MTOEs Shown? Problem is Yes!

12 Tree Graphs Graph G: Parent B C D Child E F NODES (or verties): set V = {, B, C, D, E, F } LINKS (edges): set E = { (,B), (,C), (,D), (C,E), C,F) } GRPH: olletion of verties and edges: G(V,E) Tree struture is a onneted graph with no yles, i.e., every node has at least one link to another node and only one path exists between any two nodes. Via a link, a node an be a parent or a hild of another node. node without a hild is alled a terminal or leaf node (e.g., the nodes at the bottom of the tree: B, D, E, and F) node with hildren is a non-terminal or internal node (e.g., and C); The root node is a speial internal node with no parent (e.g., ). Organization Charts are Trees (w/ boxes instead of irles) ( Often the name of the tree is inherited from the name of the root node - e.g., ): B C D B C D B C D

13 Labeled or Timed Tree Graphs T 1 T 2 T 3 a b T x T y T 1 T x < T 2 T y < T 3 T x T y a b a b a B D G a a a a B C E G b b b b C D E F a and b and Base C a b E F b

14 Stability with Time n interval is defined with a start_point (s_date) and an termination_point (t_date). Valid nodes/links are those whose assoiated time interval inlude a speified time. To ontinue to inlude a node or link in the tree, the t_date is simple extended to the urrent event horizon (the maximum value of any t_date in the graph). The default assumption is that all nodes and links ontinue to be part of the tree, whih is the usual ase. This results in stability as bona fide hanges must be expliitly entered. There is no need to delete obsolete values.

15 Org Tree with Times Org Tree: 2 nd -5 th Cav Bn (WGN) s_date: 1 Jan 1990 t_date: 31 De 2010 s_date: 1 Jan 1990 t_date: 16 ug 2001 HHC B C D Transition from L-Series to F-Series Struture on 17 ug 2001 Time is REL time it represents an Effetive Date (EDTE)

16 Org-Type Trees with Times Org-Type Tree: INF BN MECH (FXXI) s_date: 1 Jan 1990 t_date: 31 De 2010 s_date: 1 Jan 1990 t_date: 30 Sep 2001 X 3 X 4 HHC MECH INF (XXI) s_date: 1 Ot 2001 t_date: 31 De 2010 RFL CO INF BN (MECH) s_date: 1 Jan 1990 t_date: 31 De 2010 Modifiation from L-Series to F-Series Struture Time is RELTIVE time it represents a sequential state in the evolution of the tree (a monotoni inreasing funtion). I named it a Modifiation Date (MDTE).

17 Time Extends to ttribute Entities ssoiated with Org-Type Nodes E-3 11B10 s: 1 Jan 1990 t: 31 De 2010 s: 1 Jan 1990 t: 15 Nov 2001 M22 s: 1 Jan 1990 t: 31 ug 2008 s: 1 Jan 1990 t: 15 Ot 2003 Grenadier M2 IFV Crew s: 1 Jan 1990 t: 31 De 2010 E-4 11B10 s: 16 Nov 2001 t: 31 De 2010 s: 1 pr 2002 t: 31 De 2010 M23 s: 16 Ot 2003 t: 31 De 2010 Person-Type : Org-Type Materiel-Type : Org-Type

18 DOCNO: CCNUM: Time-Base MTOE 07245LFC FFC WGL WGN WEZE 16 Ot Ot Ot ug De ug pr pr pr pr 03 WEZK # RFL Co 17 Jan pr 03 X 4 X 3 Grenadier E-4 E-3 Equipment N/PVS-14 1 Ot 99 FY00 1 Ot 00 FY01 1 pr 01 FY01 1 Ot 01 FY02 1 Jan 02 FY02 1 Jul 02 FY02 1 Ot 03 FY04 MDTE

19 INF BN MECH (FXXI) Time Between Org and Org-Type Nodes s_date: 1 Jan 1990; t_date: 16 ug 2001; m_date: 30 Sep 2001; s_date: 17 ug 2001; t_date: 31 De 2010; m_date: 1 Ot 2001; 2 nd -5 th Cav Bn (WGN) RFL CO INF BN (MECH) N/ PVS-14 s_date: 1 Jan 2002; t_date: 31 De 2010; E-3 11B10 E-4 11B10 s_date: 1 Jan 1990; t_date: 31 De 2010; m_date: 1 Jan 2002; s_date: 1 Jan 1990; t_date: 17 ug 2002; m_date: 1 Jan 2002; -C Rifle Co (WGN/B/C0) D Rifle Co (WGND0) s_date: 1 pr 2001; t_date: 30 Sep 2001; s_date: 16 Ot 1999; t_date: 16 ug 2001; m_date: 1 Ot 1999; s_date: 1 Ot 2000; t_date: 30 Sep 2000; s_date: 1 Jan 1990; t_date: 30 Sep 2000; s_date: 1 Ot 2001; t_date: 21 De 2010; Grenadier s_date: 17 ug 2001; t_date: 15 De 2002; m_date: 1 Ot 2001; s_date: 16 De 2002; t_date: 16 pr 2003; m_date: 1 Jan 2002; s_date: 17 pr 2003; t_date: 31 De 2010; m_date: 1 Ot 2003; Grenadier 1 s_date: 1 Jan 1990; t_date: 16 ug 2001; 54 in 2-5 th Cav Bn

20 Summary Time-Based Tree Graphs an be used to provide a ontinuous, stable fore struture representation suitable for use in digital battle ommand systems. This hanges the way the rmy douments its fore struture a major undertaking that affets nearly every system in the rmy. It is an undergoing proess that urrently inludes the rmy G-3, G-8, G-6, PEO-C3T, and TRDOC with RL tehnial assistane.