By Topic

Blue Force Tracking Network Modeling and Simulation

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

7 Author(s)
Chevli, K.R. ; Appl. Phys. Lab., Johns Hopkins Univ., Laurel, MD ; Kim, P.Y. ; Kagel, A.A. ; Moy, D.W.
more authors

Blue force tracking (BFT) has become a critical capability for the military. It involves communicating situational awareness (SA) and command & control (C2) information among highly dispersed battlefield units in a dynamic environment BFT was used during operation Iraqi freedom (OIF) for coordinating operations within the joint services and with allies and resulted in reduced causalities due to enhanced SA. The Army's current BFT system is a program of record C2/SA system known as Force XXI Battle Command Brigade and Below (FBCB2). It consists of a terrestrial line-of-sight (LOS) system and a commercial L-band satellite- based beyond-line-of-sight (BLOS) system known as FBCB2-BFT. About 6000 BLOS BFT devices were fielded during OIF. The Army is projecting its worldwide FBCB2-BFT fielding needs to exceed 100,000 devices over the next 5 years. The information exchange requirements per user are also expected to increase. At issue is the ability of the current FBCB2 architecture to support the projected BFT needs. This paper will discuss an Army G-3/G-6 sponsored study to investigate the BFT communications and coverage needs in the 2015 timeframe. It will focus on the network modeling and simulation aspects of the study using OPNET

Published in:

Military Communications Conference, 2006. MILCOM 2006. IEEE

Date of Conference:

23-25 Oct. 2006