FCS Training IPT Environmental Representation

1
FCS Training IPTEnvironmental Representation

• Simulation Interoperability Workshop
• presented by
• Rob Cox
• Dan Stevens
• FCS Training Systems
• coxr_at_saic.com
• stevensd_at_peostri.army.mil
• 22 September 2004

2
Agenda

• Network Centric Warfare
• What is Geospatial Data
• FCS Embedded Training
• A Common Environment
• Background
• FCS ORD Environmental Requirements
• Support to Lead Data Architect
• Support to FCS Geospatial Working Group
• Summary

This presentation is only the Training IPTs
efforts and work in establishing a common
environment. While the Training IPT supports
the FCS effort to develop a common environment,
this presentation is only the Training IPT
position and does not contain other FCS IPTs or
Working Groups position.
3
DoD Policy for Network Centric Warfare
4
FCS AROC ORD KPP 1

• KPP 1 - Network Ready
• FCS FoS activity interfaces, services,
  policy-enforcement controls, and data sharing of
  the NCOW-RM and GIG-KIPs will be satisfied to the
  requirements of the specific Joint integrated
  architecture products (including data
  correctness, data availability and data
  processing), and information assurance
  accreditation.

5
DoD DirectionProducer-centric transitioning to
Consumer-centric

• The new paradigm (http//ges.dod.mil/about/tppu.ht
  m)
• Moving from centralized thinking and planning to
  net-centric planning - Major Paradigm Shift
• Current Task, Process, Exploit, Disseminate
  (TPED) concept used in many services to provide
  information from the producer to the consumer is
  giving way to a new paradigm, Task, Post,
  Process, Use (TPPU)
• Improves the speed and quality of DoD decision
  making
• The net-centric environment must
• Support posting data to shared spaces as early as
  possible
• Provide users with the capability to pull
  whatever data they need, whenever they need it,
  from wherever they are
• Users post even raw data on the network for use
  before it is ingested into the conventional
  processing
• In TPED, processing normally refers to the data
  handling required to convert raw sensor data to a
  useful format
• In TPPU, there is fusion of data and information
  is posted directly

6
GIG Policy The New TPPU Paradigm

• to implement TPPU producer standards/technologies
  may need to differ from consumer
  standards/technologies
• The current TPED concept used in many services
  to provide information from the producer to the
  consumer is giving way to a new paradigm, TPPU...
  in TPPU, tasking is network centric, readily
  accessible to all authorized users, and fully
  integrated with user plans and operations.

(diagram obtained from http//ges.dod.mil/about/t
ppu.htm)
7
Army Transformation The Operational Environment
EM Spectrum
Weather
Space
Cyber
Atmospheric
Enemy seeks to leverage their home-court
advantage while collecting, denying, impeding,
contaminating, and cluttering friendly use.
We seek to enable our understanding, mobility,
and protection while neutralizing home court
advantages of an adaptive learning threat.
Terrestrial
Subterranean
Aspects of the Environment

• Resources

• Infrastructure

• Terrain

• Human

• Hazards

• Activities of
• Populations
• Refugees
• Criminals
• Terrorists
• Local Means to Control

• Industrial
• CBRN
• Diseases/Health
• Mines/Obstacles

• Water
• Power
• Crops
• Minerals
• Construction
• EM Spectrum

• Airfields
• Seaports
• LOCs
• Power
• Comms
• Media

• Weather

• Information

• Enemy

Dynamic Interactive !
The environment plays no favorites
Environmental factors can deny access and
mobility as readily as threat actions.
8
FCS Logical Data Distribution Flow
Traditional Process
Traditional Producers
MGV
Map
FCS UA
UAV
3D MODELS
Data Integration Tools
ADDITIONAL TYPES OF DATA
WEATHER
Continuous updates
Post to network Then process
Common FCS COP DB
ENHANCED FEATURE DATA
HIGH RES ELEVATION MODEL INSETS
ATTRIBUTED FEATURE DATA
Add attribution
ELEVATION MODEL
IMAGERY
UGV
CAD
PDA

• The process is based on the NCW principle of TPPU
  and is moving from TPED to support Future Force
  consumers
• Traditional DB processes are needed to create the
  baseline
• Need tools and processes to rapidly integrate
  new data into the NCW baseline to assist in the
  fusion of organic and indigenous data for
  incremental, instantaneous deltas (at UA, sent
  back to producers after the fact)

9
Logical Data Distribution Flow
Current producer DEDs have gaps meeting FCS
ORD requirements. CBRN and Urban are examples

• Why two DED formats
• Current forces use different formats
  dictionaries
• -FCS requires common environment (may require
• converters to prepare for UA)

UE Cache Theatre Command Post
Producers
Repository Store data w/ Multiple Native DEDs
FCS Common DED
NGA (FACC)
WX (GRIB/ JMCDM)
Multiple Native Format/DEDs
Converter to interoperate with Future Force
Ocean (GRIB JMCDM)
FCS Common Format/DED
UA Cache
CONUS
Local repository in FCS common format cached
at individual unit
Space (GRIB JMCDM)
Repository Store data w/ Multiple Native DEDs
FCS Common DED
Incremental Indigenous Updates
CBRN
Will require converters to merge all the data
from various sources to fulfill FCS ORD
common environment requirement
Other?
May collect local updates in FCS common format
from FCS sensors
Majority of data processing is before
deployment. Only doing updates in field
FCS Applications Mission Execution
Planning, Mission Rehearsal, Battle
Simulation, (requiring COP DB) Embedded
Training, Manned Unmanned Vehicle Navigation,
CROP,
10
What is Geospatial Data
11
Definition of Geospatial

• Traditional definition found in JTA
• Mapping, Charting, and Geodesy
• Does not include multiple domains that are
  required for the Future Force (CBRN, urban,
  space, atmosphere, etc)
• Others have tried to redefine Geospatial to
  include other parts of the environment (e.g.
  J-GES and AGDIMP)
• While a worthwhile attempt, many view the term as
  still terrain centric
• Need to use another term such as environmental
  representation

12
The Environmental Data Facts

• FCS requirements is more complex, costly, and
  time consuming than current and other Future
  Force requirements
• Future Force will NOT be able to See First,
  Understand First without timely, accurate,
  tactical-level environmental data
• Current holdings of environmental data are out of
  date, cover small portions of the earth, largely
  analog source
• NGA service and capabilities is inadequate to
  support current and Future Force environmental
  data requirements
• Cannot currently meet required geographic
  mapping tasks in a timely manner
• Integration of Modeling and Simulation tools
  (Embedded training, EMPLRS, and predictive
  analysis planning tools) will require Joint, DoD
  common data element format

13
FCS Embedded Training
14
Embedded Training..
a DoD plan an Army Commitment
Build an Integrated Live, Virtual, and
Constructive Training Environment. The ultimate
goal is to develop a transformed training
capability that provides accurate, timely,
relevant, and affordable training and mission
rehearsal in support of specific operational
needs. Training must be a living process with the
ability to adapt and respond quickly to the
dynamic challenges of the national security
environment. This will require the ability to
identify potential crisis situations in real
time conduct course-of-action analyses utilize
continuously available networks for mission
rehearsal, simulation and just-in-time training
and measure performance systematically to improve
operational effectiveness.
Strategic Plan for Transforming DoD Training, 1
Mar 02
15
UA/FCS Training Concept
Training is THE factor in determining the
victor. - DSB Task Force on Training Superiority
and Training Surprise

• Expanded training availability using organic,
  integrated, embedded systems - Training,
  Operations, and Mission Planning/ Rehearsal for
  full spectrum training including JIM
• Full range of training task representation -
  individual, crew, collective, and leaders
  embedded or reach via C4ISR system
• Reduced training burden cost resulting from
  product line design approach - maximum
  commonality between operational and training
  systems.

Non-organic assets
Stand-alone Simulations Simulators
Part task Trainers
Crew
Stimulators
CTCs
Integrated
and
Embedded Systems
Units Leader teams
Home Station Institution
organic
C4ISR drivers
Individual
Knowledge Repositories
16
Training Systems Capabilities
Embedded Task Training (Crews Soldier)
Distributed, Collective Training (Virtual
Constructive) ( Leaders Units )
Platform Workstation
Synthetic Operational Environment
Synthetic Operational Environment
Distributed, Collective Training (Live) (Embedded
MILES CTC Instrumentation Interface)
CTCs / JNTC
Reach
UE Subunit
HS
UA
17
FCS ORD Training Requirements
Objective Requirements
KPP-Critical Requirements
Training Requirements are spread across the FCS
program
Training Requirements are spread across the FCS
program
18
Training Products

• Mission Task Analyses
• Embedded Training system
• - Driver Trainer
• - Weapons Trainer
• - RSTA Trainer
• - Battle Command Trainer
• Stand-Alone Training Systems (reconfigurable)
  for
• those tasks which are unsafe, unaffordable or
  
• impractical for embedded training expected
  primary
• support for institutions.
• - High fidelity
• - Desk-top
• Maintenance Trainers
• Training Support Packages (TSPs) Individual
  Collective
• - Level V IETMs
• - Simulation-based TSPs
• - Interactive Multimedia Instruction (IMI)

Each contains a progressive performance matrix
(a la UCOFT)
Each Stand-alone trainer reuses ET code
19
Training KPP
The FCS FoS must have an embedded individual and
collective training capability that supports
live, virtual and constructive training
environments.
Rationale Embedded full task and tactical
engagement simulation systems provide leaders
with a readily available system for training and
assessing Combat Critical Skills of soldiers and
provide the capability to train and assess
crew/sections, dismounted soldiers, and
multi-echelon combined arms skills in operational
environments.
20
Critical Enabling KPP Requirements
Embedded Training - Virtual / Constructive (ORD
1093)
Embedded Training - Live (ORD 1089)
CTC / JNTC
Interoperability Reach (ORD 3784)
Dismounted Training (ORD 1078)
HS
EXERCISE FUNCTIONS
Plan Exercise
Execute Exercise
Assess Exercise
Initialize Simulation
Scenario Generation
ENABLERS
Datalogger
OTW View
After Action Review (AAR)
Embedded TESS
Exercise Management
Computer
Generated Forces (CGF)
Synthetic
Operational Environments

• MGV Reqt

Inter-Vehicle Connectivity
C4ISR

• Common
• Training
• Components

Interoperability Reach
21
A Common Environment
22
Common Environment

• The complete environment is also the view held by
  the SoSCOE
• This view important because it shows need at
  implementation
• Terrain and environment are in the Common Domain
  Services

23
Common Environment

• FCS ORD requires environmental data from all
  domains terrain, atmosphere, ocean, space,
  urban, CBRN, etc. (e.g. ORD 1020, 2392, and
  2467)
• FCS ORD requires a common environmental
  representation (e.g. ORD 3131 and 1079)
• PM FCS through the C4ISR and SSEI IPT
  established the Terrain Working Group (TWG) to
  address theses issues (May 2003)
• Now called the Geospatial Working Group (GWG)

24
Geospatial Working Group Charter

• What does the Geospatial Working Group Charter
  say
• Conduct trade studies across IPTs to include
• Geospatial Data Model of application features and
  attributes for a full range of FCS applications
  including C2, Training, and Logistics
  applications
• Analysis of existing and potential land, sea,
  air (weather) and space data sources to determine
  if and how FCS could implement a common land,
  sea, air (weather) and space model of the Natural
  Operating Environment

Take Away Must do analysis to implement common
environment
25
Geospatial Working Group Charter

• What does the Geospatial Working Group Charter
  say
• The GWG will be responsible for production of the
  following products
• Provide rationale concerning Geospatial Data
  content (land, sea, air/weather and space) to the
  FCS SSEI Lead Data Architect for the SSEI OV7 SoS
  Logical Data Model, and upon approval of the
  rationale or other direction by the FCS SSEI Lead
  Data Architect,
• Provide rationale concerning the SoS OV7 Data
  Element Dictionary for Geospatial Data content
  (land, sea, air/weather and space) to the FCS
  SSEI Lead Data Architect for the SSEI OV7 SoS
  Logical Data Model, and upon approval of the
  rationale or other direction by the FCS SSEI Lead
  Data Architect, then supply and coordinate an
  integrated set of modifications into the SoS Data
  Element Dictionary. This product will select and
  utilize a common, standards-based, environmental
  dictionary for the encoding and communication of
  qualitative and quantitative information
  associated with the physical environment
  (including but not limited to vegetation,
  topography, oceanographic phenomena and
  conditions, hydrology, atmosphere and atmospheric
  conditions, space phenomena, and man-made
  objects), or else will provide detailed rationale
  and recommendations for alternatives

Take Away Must provide rationale for a common
standards based Dictionary for approval
26
Geospatial Working Group Charter

• Accountability
• The Geospatial Working Group will be supported by
  the following IPTs SSEI, C4ISR, Training
  Systems, MGV, UGV, UAV, Soldier Systems, Force
  Development, Integrated Sim Test.
• The Geospatial Working Group will work closely
  with the following IPTs SSEI, C4ISR, Training
  Systems, MGV, UGV, UAV, Soldier Systems, Force
  Development, Integrated Sim Test.
• The Geospatial Working Group will be accountable
  to the FCS SSEI Lead Data Architect.

Take Away The GWG responds to its customers the
FCS IPTs and is accountable to the FCS SSEI Lead
Data Architect
27
Direction to Training IPT

• Baseline environmental (land, air, sea, weather)
  features and attributes that we know or expect to
  exists in the FCS embedded training applications
• Use the SEDRIS EDCS as the coding standard to
  identify the features and attributes
• Provide this to the ongoing FCS system of system
  architecture work and the FCS data modeling from
  a training perspective (Training requirements)
• Support the FCS Geospatial trade study and will
  work to define the criteria for that trade study
• Results of that trade study will guide the FCS
  implementation which is a future event

• FCS is about the future and not about the past
• Work toward a common environmental representation
  for all FCS applications (a common and consistent
  representation and standards)
• Concerned with the apparent emergence of the
  stovepipes of the past
• Working the system engineering effort for FCS
  training
• A review of the requirements

Take Away Training IPT has its direction and is
supporting the FCS GWG effort
28
FCS ORDEnvironment Requirements
29
FCS ORDEnvironment Requirements

• Reviewed the 14 April 2003 JROC approved ORD
• What does ORD require for the environment
• The following slides will show
• Key points by ORD paragraph number and ORD number
• Reason why important

Take Away Current direction has been traced to
ORD requirements
30
FCS ORD Environmental Requirements

• Approximately 420 were identified
• Not all 420 had actual ORD numbers
• Initial review did not distinguish between
  environmental database requirement and a testing
  requirements
• Need to know soil type for maneuver vs must be
  able to operate between 20 and 100 degrees
• Requirements stratified by four environment
  domains (terrain, atmosphere, ocean, space)

31
FCS ORD Environmental Requirements

• Below is an extraction from the spreadsheet
• Description column is the actual ORD words
• Geospatial requirement column is for the domain
  of the requirement
• Comments column is the rationale used
• Last two columns are whether we thought the
  requirement was an operational or test
  requirements and if the requirement was an
  architecture, timing, or database requirement

32
FCS ORDEnvironment Requirements

• Annex A 2.0.9.1 ORD 2355 Technology insertion
  to ensure plug and play states that we can select
  technology now, and change later if other
  technology is developed that better meets FCS
  requirements.
• Annex A 2.0.7.4 ORD 3266 States need for
  common representation.
• Annex A 2.0.7.5 ORD 2323 Battle Command
  systems must meet the requirements for garrison
  operations, training, field exercises, and actual
  operations.
• Main 4.1.1.1.1.1 ORD 1020 Must be capable of
  conducting distributed, simultaneous, multiple,
  and continuous fully integrated CA full spectrum
  operations (a common system).
• Annex B 2.0.2.1.1 ORD 3131 Must have a common
  data base.
• Annex B 2.0.7.1.4 ORD 3125 Need for data that
  is accessible/retrievable from knowledge
  repositories.
• Annex A 2.0.6.2 ORD 1064 Data comes from
  multiple sources and needs to be integrated into
  a common representation.
• Main 4.1.1.7.2.1 ORD 1093 Need a common
  database of the total environment

33
FCS ORDEnvironment Requirements

• Annex A 2.0.5.2 ORD 2392 C4ISR systems rely
  on the networkover operational distances, in all
  environments.
• Annex A 2.0.6.1 ORD 2467 FoS must acquire,
  access, and disseminate relevant and accurate
  environmental information from multiple sources.
• Main 4.1.1.8.2.2 ORD 3790 Must develop an
  authoritative representation of the environment.
• Annex D 2.0.7.2.1 ORD 1079 Must have the
  total environment for display and its format.

34
What is Needed?

• We now know that FCS requires a common
  environment
• We have identified key organizations to work the
  environment
• We now know what the requirements are as outlined
  in the FCS ORD
• What are the key pieces that must be accomplished
  now to set the stage for a common environment?
• A common logical data model leading to a common
  physical data model for persistent storage of
  common environment content
• A common data dictionary
• Tools, especially to allow applications to read
  the common persisted format and convert to
  application-specific formats at runtime

35
Training Support Provided to SSEI Lead Data
Architecture Team
36
Support to SSEILead Data Architecture Team

• FCS working group chartered for SSEI
  Architecture Team to address data modeling issues
• Asked IPTs to submit requirements in April 2003
• Started having telecons in May/June of 2003
• Asked all IPTs for participation and support
• Laid out challenge and schedule
• Challenge similar to that of the GWG for
  identifying a common Data Element Dictionary
  (DED) and Data Model (DM)
• Training IPT offered support to Architecture Team
• Supplied Training IPT requirements in September
• Supplied environment report in November
• Lead Data Architect (LDA) selected the C2IEDM as
  the baseline for the FCS Common Data Model (FCDM)

Take Away Architecture working group must
create the FCDM using a DED. It must meet
schedules set by program office.
37
Support to SSEILead Data Architecture Team

• Before any support was given to the LDA efforts
  the following path was discussed and agreed to in
  April 2003 (before chartering of GWG and in
  support of the FCS data modeling activities)
• What is needed (what are the geospatial
  parameters that are needed each user (IPT)
  requirements for geospatial data)
• This is user requirement centric. Producers need
  to produce what the users require, not what the
  users do not use/require
• How is it represented (once the parameters are
  known and fully defined, then represent them in a
  logical DM)
• How is it transmitted in FCS (after the
  parameters are defined by a DED and represented
  in the DM, then discussion of how the geospatial
  data is formatted for transport will be discussed)

38
Support to SSEILead Data Architecture Team

• What has been provided
• Initial briefing was presented on how the
  training/simulation community has approached this
  problem over the years
• Detailed briefings were presented on various
  technologies that could be used to help solve the
  problem to include
• Common Data Model Framework (CDMF)
• Environmental Data Coding Specification (EDCS)
• Projects sponsored by the Topographic Engineering
  Center and PEO STRI

Take Away Earliest work by the LDA wanted to
consider multiple IPTs needs and queried for
existing technologies
39
Support to SSEILead Data Architecture Team

• What has been provided
• CDMF captured, using EDCS, features and
  attributes of the following systems DTSS, IMETS,
  OOS terrain, OOS AOS, MM5, MSDS 1-5, Littoral
  1-5, JCDM, JMTK, and DNC
• Union of these systems produced the initial
  Training IPT requirements of the environment
  features and attributes that SSEI needed for DM
  asked all IPTs to provide their requirements and
  compare to this list
• Used EDCS to convey these features and attributes
  to SSEI
• Recognizing that the provided material was
  preliminary with
• Urban not included
• Impoverished in some domains (e.g. ocean)
• Need to have individual program managers (e.g.
  DTSS, OOS, IMETS, etc) to review to ensure the
  CDMF characterized the system capability
  correctly
• Ask other IPTs to review the input to determine
  if their requirements were met by the submission,
  too
• Even with that, SSEI was given a first order
  solution of the features and attributes for the
  total environment (complete geospatial
  definition)
• Training IPT has now begun updating the
  submission to include urban

Take Away Work completed to date include many
C4I and Training systems Recommendations for
review by C4I and all IPTs
40
Support to SSEILead Data Architecture Team

• What has been provided
• A list of the features (approximately 800)
• A list of the attribute (approximately 1000)
• A combined list of features and attributes
  (26,182)
• The EDCS label and authoritative definition for
  each feature and attribute
• Import mechanism into Rational Rose
• If decision is made to use a different DED, then
  SSEI Lead Data Architect mapping exist between
  EDCS and other DEDs

Take Away Provide support to SSEI in
developing the FCS environmental data model and
meet their milestones. Considered Training needs
and recommend broad review
41
Training Support Provided to the FCS Geospatial
Working Group
42
FCS GWG

• A common environment needs a common logical and
  physical data model which in turn implies a
  common dictionary
• FCS needs a standard dictionary of environmental
  terms for the encoding and communication of
  qualitative and quantitative information
• FCS ORD does require a common environmental
  representation (e.g. ORD 3131 and 1079)
• Terms must be unambiguously defined
• Terms must have a precise definition that states
  the nature, properties, scope and quantities of
  each term

43
FCS GWG

• Support to the GWG Trade Studies
• Data Element Dictionary
• Data Model
• Common applications, tools, APIs

44
FCS Environment Data Dictionary

• Several types of data must be found in the
  environmental data dictionary
• vegetation (forests, trees, grass, etc.),
• topography (mountains, valleys, islands, etc),
• oceanographic phenomena and conditions (littoral
  regions with surf,
• wave information, salinity, turbidity, water body
  type, ice, and floor, etc),
• hydrology (lakes, rivers, etc),
• atmosphere and atmospheric conditions (rain rate,
  humidity,
• soil moisture effects, aerosol particles, etc),
• space phenomena (solar activity, EMP, charged
  particles, effects on spacecraft and satellites,
  etc),
• man-made objects (bridges, vehicles, buildings,
  interiors, the building material, etc)

45
FCS Environment Data Dictionary

• Several candidate data dictionaries are available
• Some include
• Digital Geographic Information Exchange Standard
  (DIGEST) Part 4 of DIGEST is the Feature and
  Attribute Coding Catalogue (FACC), which is a
  coding schema for terrain-related features,
  attributes, and their values
• Environmental Data Coding Specification (EDCS)
  An emerging international standard (ISO/IEC
  18025) that supports the encoding and
  communication of information associated with all
  domains of the environment. The standard has an
  Application Program Interface (API) and nine
  separate dictionaries that specify the
  environmental concepts. EDCS takes advantage of
  FACC, IHO S-57, WMO, ICAO, and several other
  environmental dictionaries of concepts and terms
• International Hydrographic Organization (IHO)
  The IHO S-57 is a standard for transfer of
  digital hydrological data. It has a dictionary,
  data model, and exchange format. It specializes
  in transfer of only hydrological data
• Joint METOC Conceptual Data Model (JMCDM) The
  JMCDM has four sections for observational,
  derived, climatological, and astronomical data.
  It is an encyclopedia of meteorological,
  oceanographic, and space related features and is
  part of the US DOD Data Model (being replaced by
  the Joint METOC Broker Language (JMBL)

46
FCS Environment Data Dictionary

• Viable Candidate Options
• COA 1 EDCS
• COA 2 COI Trumps / FCS Unique(DFDDJMBLOthers
  by precedence)
• COA 3 NFDD Registry space etc.
• COA 4 ABE FDD
• Trade Study
• All candidates have briefed their DEDs
• Criteria for selection have been determined
• Responses due by end of September
• Trade study report will be finalized in October

47
FCS Data Model and Tools/Applications Trade Study

• FCS Common Data Model (FCDM)
• Lead Data Architect selected C2IEDM as FCDM
• Needs extensions for modeling complete
  environment
• DMSO funding work to extend
• Tools/Applications
• Once DED trade study complete, will begin this
  trade study
• Expected to start in October/November
• Will leverage work done by organizations like RD3
• Working with TPIO-TD on separate but linked issue
  of CONOPS

48
Summary

• Network Centric Warfare
• What is Geospatial Data
• FCS Embedded Training
• A Common Environment
• Background
• FCS ORD Environmental Requirements
• Support to Lead Data Architect
• Support to FCS Geospatial Working Group

This presentation is only the Training IPTs
efforts and work in establishing a common
environment. While the Training IPT supports
the FCS effort to develop a common environment,
this presentation is only the Training IPT
position and does not contain other FCS IPTs or
Working Groups position.