Navigation Modeling for Force XXI

1
Navigation Modeling for Force XXI

• Raymond L. Filler
• filler_at_mail1.monmouth.army.mil
• Phone [phone]
• Van Tran
• Mr. John Peace
• peacej_at_mail1.monmouth.army.mil
• Phone [phone]
• US Army CECOM

Joe McGowan jmgowa1_at_csc.com Phone
732-460-3184 James Adametz Mark
Berry mberry_at_csc.com Phone [phone]
Eric Gretzinger Consultant
Computer Sciences Corporation
2
New Role of Navigation

• The accuracy and availability of position and
  motion information directly affects the future
  Army C2 and Operational effectiveness.
• Traditional Role of position information is for
  own platform pilotage.
• Evolving Role of position information is as a
  shared resource

• Supports
• Maneuver
• Logistics
• Intel Data Fusion
• Air Defense
• Fire Support
• Munitions Emplacement

3
Why Navigation System Modeling?

• MOEs of maneuver, engagement and C2 are
  sensitive to navigation system MOPs.
• There is no such thing as Perfect Pos/Nav
• Global Positioning System (GPS) is pervasive but
  NOT guaranteed.
• Susceptible to
• Terrain/Foliage/Urban Canyon Blockage
• RF Interference
• Most Platforms with GPS do not have backup
  navigation systems.

4
MOPs and MOEs

• Relationships between Nav System Measures of
  Performance (MOPs) and military worth (MOEs)
  resist functional characterization - the
  representation of human performance is
  challenging
• Empirical relationships must be obtained through
  controlled experimentation.

5
Requirements of the Nav Model

• Able to accommodate Force or Community Level
  scenarios while maintaining single entity
  resolution.
• Able to stimulate live data interfaces.
• The model becomes the surrogate for individual
  platform navigation performance
• Faithfully represent navigation component
  algorithms, hardware and integrations.

6
CECOM Integrated GPS Navigation Model
(CIGNM)

• Comprehensive Monte-Carlo simulation of
  Integrated Navigation Systems
• Errors modeled at the sensor level
• RF/Terrain environmental effects modeled
• Navigation processing emulates or duplicates
  actual system being modeled.
• Easily reconfigured to model a wide-range of
  systems, sensors and technologies.
• PC/Windows compatible

7
The CIGNM Environment
GPS Constellation model includes satellites and
pseudolites

• Entity State Position Data includes Errors Due to
  Jamming, Noise, Iono/Tropo, RCVR Behavior, SV
  LOS Blockage, Backup Nav

8
CIGNM Communications

• CIGNM Supports Flexible I/O
• Network
• Point to point (e.g. serial, parallel interfaces)
• Data File
• Readily Adaptable to Support Other Interface
  Requirements

High Level Architecture Compliance Planned for
Next CIGNM Revision
Realistic
9
User Configurable Parameters
GPS Parameters
INS Parameters

• External To Receiver
• Ephemeris Along-Track, Cross Track, Radial
  Errors
• SV Clock Errors
• Maximum Mid-Day Ionospheric Delay
• Tropospheric Refractivity Variance
• SV Signal Power

• Gimbaled Or Strapdown Switch
• Gyro Bias, SF, Noise PSD, Noise Bandwidth
• Accelerometer Bias, SF, Noise PSD, Noise
  Bandwidth
• Baro Loop Gains
• Baro Bias, Scale Factor, Noise PSD, Noise
  Bandwidth, Time Constant

• Each Receiver
• Antenna Type/ Configuration
• Number Of Channels/Number of Nav Channels
• Acquisition/State 5/State 3 J/S Thresholds
• Acquisition Model Parmaters Pre-, Post-detection
  Integration Intervals, P(fa), Correlators per
  Channel
• Code And Carrier Tracking Loop Bandwidths
• Single/Dual Frequency Iono Switch
• State 3 Iono Model Switch
• Nav Constellation Selection Criteria

Doppler/AHRS Parameters

• Carrier Frequency
• Beam Orientation
• 3 dB Beam Width
• Frequency Tracker Time Constant
• Beam Alignment Error
• Gyro Bias, SF, Noise PSD, Noise Bandwidth

10
CIGNM Applicability

• Concepts and Initiatives
• Concept Identification and Validation
• Exploration of the Dependence of C2 Systems on
  Pos/Nav
• Experiments, Exercises, Training
• Explore and Teach Issues Relating to Pos/Nav,
  Situation Awareness and C2
• Investigate/explore C3 system alternatives
• Simulation
• Navigation and RF Propagation
• Analysis
• What-If Reproducibility

11
CIGNMs Presence in the MS Community

• Installed Presence
• GPS JPO Navwar Program
• Fort Monmouth C2D Systems Lab
• Fort Monmouth C2D Modeling and Simulation Lab
• Fort Monmouth Digital Integration Lab (DIL)
• Used to Support GPS-DIS Experiment at Fort Knox
  Mounted Warfare Test Bed Fort Rucker Aviation
  Test Bed, October/November 1997
• STORM (FBCB2 Testing) EPG - Ft. Huachucha and Ft.
  Hood

12
The GPS-DIS Experiment

• Assess the Impact of GPS Jamming on C2 and
  Maneuver Operations
• Assessment Focused on Loss of Effectiveness
• NAIC-approved GPS Jammer Threats Were Placed in
  the Battlespace to Observe and Record their
  Impact on
• GPS-based Situation Awareness
• Command and Control, in Particular Coordinated
  Operations
• Rendezvous for Refuel/Rearm
• Massing of Force Capabilities
• Air/Ground Coordinated Strikes
• Operational Tempo
• Tactical Internet Voice/Data Loading

13
GPS-DIS Configuration
14
CIGNM Role in GPS-DIS
SIM
SIM
SIM
SIM
SIM
SIM
1
5
6
4
3
2
M1AX
M1AX
M1AX
M1AX
TOC
1
2
3
4
APPLQ
APPLQ
APPLQ
APPLQ
APPLQ
APPLQ
1
6
5
4
3
2
CIGNM
MASTER
INC
INC
INC
INC
INC
INC
CIGNM
SLAVE
TIM
TIM
TIM
TIM
TIM
TIM
CIGNM/SA SERVER LAN
NET ADMIN
KNOX DIS 2.03 LAN
SA
PATHLOSS
TIM
MODSAF
MODSAF
MODSAF
TIME
DATA
1
2
SERVER 1
PROXY
MODSAF
SERVER
STAMP
ANALYSIS
MODSAF
FRONT END/OPERATORS
MODSAF
TIM
DATA
DATABASE
MODSAF
MODSAF
MODSAF
SIMULYZER
MAINT
3
4
LOGGER
CORREL
(UTILITY)
BACK END/ENTITY GEN.
SIMNET
RUCKER DIS 2.03 LAN
DEFENSE SIMULATION INTERNET (DSI)
INES
INES
XCAIU
LONG-HAUL NETWORK
AH64
AH64
1
2
HIGHLIGHTING CIGNM IN THE GPS-DIS EXPERIMENT
ARCHITECTURE
APPLQ
APPLQ
SERIAL
CONNECTIONS
CIGNM
INC
INC
TIM
TIM
15
S3 FBCB2 Screen SA Quality

• SA errors shown are the differences between the
  SA message position received at the TOC and the
  truth.
• SA Problem driven by GPS only (no INS) on scouts
  trucks.

Note INS on Tanks assumed linked to the Tactical
Internet (2006 capability).
16
Simulation,Test, Operations, Rehearsal Model
STORM

• The Army is developing C4I systems such as FBCB2
  that interface with multiple echelons.
• A great amount of resources are being saved
  through the use of a synthetic environment for
  live testing Force XXI - all data flow for a BDE
  represented in a real-world battlefield
  environment.
• Requires realistic digital communications and
  navigation models to seamlessly integrate
  constructive and live entities.

17
STORM Configuration
18
TIM Suite
19
Summary

• Navigation Modeling for Force XXI (and beyond)
  Experimentation Needs to
• Represent
• Many Players in a Force Level Experiment
• Multitude of Nav Technologies, Qualities
  Configurations
• Sensitivities to Environment and Counter Measures
• Support Real Time Operations
• Interoperate with Other Models, Facilities
• Emulates Interfaces to Combat and C2 Systems
• CIGNM is a Modeling Environment that Fills These
  Needs With Great Flexibility
• Successful application to Navigation Warfare AoA
  for individual platforms and a multi-entity
  manned experiment.
• CIGNM integration for STORM proceeding with all
  objectives met.