TRADOC PROGRAM INTEGRATION OFFICE FOR TERRAIN DATA

1
TRADOC PROGRAM INTEGRATION OFFICE FOR TERRAIN
DATA

• Campaign Plan
• March 1999

2
Purpose of Briefing

• Describe the current state of the topographic
  world.
• Outline the actions TPIO-TD is taking to ensure
  the digital terrain data piece of the digital
  force is synchronized across the Army.

3
Agenda

• Situation - NIMAs Foundation Data Concept
• Task Organization (Agencies Affected)
• Mission
• Intent
• Execution
• Major Issues
• DTLOMS Implications
• Summary

4
Agencies Involved in Terrain Data Requirement
Processes
TRADOC TEC DISA TPIOs/TSMs NIMA PEOs/PMs DCSINT
STRICOM WES DFCC CAC ADO SIGCEN
CECOM DCSOPS SARD CTCs MACOMs TRADOC
Schools FORSCOM Joint Venture Battle Labs INTEL
School DLA III Corps CINCs Corps of Engrs
ASPO DISC4 JCS ICTs/IPTs DMSO/AMSO
List Continues to Grow
Bottom Line Nothing is Simple or Easy
5
Mission
TPIO-TD will coordinate and synchronize all
generic Army digital topographic data (DTD)
requirements and DTD for digital force
development and training experimentation combat
developments training and live, virtual and
constructive modeling and simulation in order to
provide a Common Topographic Operating
Environment (CTOE) essential for implementation
of a digital force.
6
Directors Intent

• Advocate for implementation of GII MP
• Define DTD through various exercises and
  experiments such as the Division Capstone
  Exercise (DCX) and Joint Contingency Force -
  Advanced Warfighting Experiment (JCF-AWE)
• requirements generation process
• requirements requests process
• dissemination methods to the force
• use in modeling and simulation
• End State A CTOE with requirements policies,
  doctrine, TTPs and dissemination means tested and
  validated

7
Concept of Operations
NIMA
MS Data Builders
Establish Requirements Collect Process Store
Manage Disseminate Manipulate
Corps/Div
ABCS
JMTK
BDE
TMTK
BN
CTOE
CO
FBCB2
Platform/Soldier
8
Defining DTD Requirements

• Three parts to the requirements issue
• How is DTD requested - the doctrine
• What are the generic Army requirements
• What does a DTD request consist of

9
Terrain Requirements Documents
Operations Training System Development Experimenta
tion
NIMA
Data Factory
Service Needs
CJCSI 3901.01
AR 115-11
TP 71-9
10
Army (Generic) Requirements

• Terrain data requirements to NIMA Feb 98
• Foundation Data
• Elevation, imagery (5 M), features
• Worldwide except snow covered areas
• MSDS
• Higher resolution elevation, imagery and features
  - to 150K map standard
• Areas defined by impending or in-progress
  operations

11
Production Timelines

• Timelines for production defined (Just in time,
  for planning, as well as execution)
• 20X20 Km area in 18 hours
• 90X90 Km area in 72 hours
• 300X300 Km area in 12 days
• NIMA developing production metrics from MAPEX 2010

12
NIMAs Position

• NIMAs response to Armys requirements
• FD Will meet most of the Armys needs
• MSDS Wanted to move soils from FD
• Cannot provide high resolution HSI (Technology)
• All levels of command and services can provide
  qualified data

13
One Mans Opinion
If you ask the planners what they want on their
map, they will probably slap you.
LTC Fred Brosk ACOM SME on Joint Planning MSDS
Conference, Oct 98
14
MSDS - Features and Attributes

• Features - A geographic entity or object
  characterized by its location
• Objects like bridges, airfields, forests, roads,
  wells
• There are over 200 possible features on a
  150,000 map
• Attributes - Typically linked to a feature in
  tabular form
• Characteristics of features
• Width of bridge, length of airfield, tree spacing
  in forests

15
MSDS Dilemma

• Precise selection of features
• Excessive planning time
• Faster production by NIMA

• Easy for the Warfighter
• Wasted Production Time
• Delayed Response from NIMA

16
Defining MSDS

• NIMA has asked for Army MSDS
• Conference held _at_ Ft Leonard Wood - Oct 98
• Primarily producers
• Built consensus on
• Administration of request
• Imagery and elevation data
• Proposal for features - the difficult area

17
MSDS Approach

• MSDS can not be easily defined by
• Force Size
• Force Type
• Mission
• Five packages of varying levels of features and
  attribution proposed
• Packages designed for large units, crisis action
  planning
• Units retain option of requesting specific
  features and attributes

18
MSDS Features Example
19
MSDS Plan

• MG Flowers letter to NIMA, 12 Jan 99
• Article
• Two sets of customers to satisfy
• Commanders and planners hard copy products
• Terrain teams digital products
• We are requesting hard copy and digital products
  of
• All components of Foundation Data (DPPDB,
  Features, DTED, Imagery)
• Each level of MSDS (5)
• Examples of fused products (Features over DTED,
  etc)
• Standard 150,000 map as a baseline for
  comparison
• Required delivery date 10 Mar 99

20
NIMA Prototypes

• 23 March Brief TRADOC DCD
• 23-29 March
• Get GEN Abrams signature on memorandum
• Package products at TEC
• Mail to commanders
• Response back NLT 31 Aug 99
• Define specific requirements NLT 30 Oct 99

21
Products to be Mailed

• Package one (large envelope)
• GEN Abrams memorandum (TRADOC has draft)
• Draft Army Requirements memorandum
• Letter Of Instruction (LOI)
• Suspense
• Instructions
• VTC Times (4)
• Web-site address with briefing and background
  sites
• CD-ROM introducing concept
• (2) CD-ROMs with Digital Topographic Examples

22
Products to be Mailed

• Package two (tube)
• Letter of Instruction (LOI)
• Hardcopy map products
• Package three (if required)
• Digital point position database
• Secret - handled separately
• Mailed to topographic battalions/detachment only

23
Who Will Receive Package

• Army Component Cdrs 8
• 1st, 5th, 8th Army 3
• Corps 4
• Division (active/reserve) 18
• Topographic Battalions 3
• TRADOC Schools 15
• CTCs 4
• MS Domain Managers 3
• CAC
• TPIO-ABCS
• TPIO-SE
• TEC
• STRICOM
• TRAC

• TSM (selected) 24
• DMS
• MOUT ACTD
• WES
• AMSO
• National Sim Center
• PEO C3S
• PEO GCSS
• Chief, Reserve Affairs
• NG Bureau
• TECOM
• RTV ACTD
• BG Arnold
• Eagle Vision

• ATMD
• ADO
• CECOM

• Copy Furnished
• TRADOC DCSCD, DCST, DCSSA
• DCSOPS, DCSINT
• Chief of Engineers
• Navy
• Marine Corps
• Air Force
• Joint Staff (MCG)

24
Digital Terrain Data Dissemination

• IPT generated operational concept - 10 months
• Key aspects
• Initial background dissemination via magnetic
  media (Foundation Data)
• Storage device requirements identified
• GBS critical for updates/MSDS
• Experimentation of concepts ongoing
• PEO C3S at Ft Hood
• Battle Command Battle Lab - Ft Leavenworth
• NIMA MAPEX 2010 - generating metrics

25
Dissemination Issues

• Updated Data - Mission Specific Data Sets(MSDS)
• Filtering - GBS/RBM segmentation by geographic
  area/ area of interest - data overload
• Defining and providing DTD for weapon platforms
  and Land Warrior
• Who duplicates the data, on what device, and to
  what type of media?
• How is data distributed to the platforms?
• TPIO-TD coordinating solution among developers

26
Modeling and Simulation

• Objective
• Develop reusable, interactive SE databases for
  MS applications across all domains.
• Technical Challenges
• Different system capabilities of MS systems.
  Objective systems developed around legacy data
  paradigms.
• MS and C4I databases are not congruent.

27
MS in Transition
OBJECTIVE

• Affordable, timely, verified/validated data
• Reuse and sharing of data
• Interoperability of MS
• Dynamic representative of natural terrain

LEGACY
28
NIMA Data Users
NIMA DATA
CINC - Present Hardcopy-Raster
C4I - Future ABCS-Vector
VALUE ADDED Processing
WARSIM Janus CBS CCTT BBS etc.
Different Processing for each Database
DOD 5000.59-P outlines corrective action.
29
MS Direction

• Data call to MS community - Jun/Oct 98
• Catalog requirements
• Division Capstone Exercise Joint Contingency
  Force AWE
• Initial requirements identified
• Continued scenario development will drive final
  requirements
• Army requirements memorandum

30
TPIO-TD Autobahn to CTOE
SEP 04
SEP 02
SEP 00
SEP 00
JAN-MAR 01
JCFAWE
WARSIMIOTE
2008
DCX
AUG 00
JMTK v5.0
APR 04
CTOE
RTV-ACTD
SE 00-2
NOV 00
OCT 00
JUL 01
JMTK v4.2
JAN 00
SEP 99
Prototype Object Oriented dBase
AUG 99
MAY 00
SEDRISOperational
OCT 99
SE 00-1
SE 99-2
JMTK v4.1
FEB 00
JAN 00
NOV 98
DEC 98
OCT 98
APR 99
MSAdvisoryBoard
MSInitial dBase
SE 99-1
MSAdvisoryBoard
JMTK v4.0
DisseminationImplementation
JMTK v3.4
OCT 98
NIMAMAPEX
APR 99
AR 115-11Revision
MSDSIPT
SEP 98
NOV 98
JAN 99
OCT 98
31
Review of Major Issues

• Requirements
• MSDS need NIMA products
• Dissemination
• Duplicating station in ABCS
• Removable medium for transfer to platforms/land
  warrior
• Area filters
• Modeling and Simulation

32
DTLOMS Implications

• Doctrine/Training
• Digital Terrain Data training (TPIO-TD, MANSCEN
  DOT, CAC)
• MSDS Information Management (TPIO-TD, MANSCEN
  DOT, CAC)
• Use of MS in mission planning and rehearsal
  (TPIO-SE, TPIO-TD, TPIO-ABCS)
• Leadership
• Cultural transition from maps to digital
  information (TRADOC)

33
DTLOMS Implications

• Organization
• Terrain teams at BDE level (MANSCEN DCD, TVC)
• Materiel
• DTSS distribution (PM CTIS, MANSCEN DCD)
• Requirements for ABCS/comms to support digital
  force (TPIO-ABCS, TPIO-TD, PEO C3S)
• Soldier
• Cultural transition from maps to digital
  information (TRADOC)

34
Summary

• Complicated, highly technical business with many
  agencies involved
• Transition of DoD/Intel community from production
  based to information generation presents many
  DTLOMS challenges
• TPIO-TD has laid the foundation for movement to a
  CTOE