LTC Jim Smith HQDA, G8

1
JFCOM Industry DayUSA-USMC BFT Convergence17
Mar 04

• LTC Jim Smith HQDA, G8
• Lt Col Mike Sweeney HQMC, C4

2
Purpose and Agenda

• Purpose Provide information on USA-USMC efforts
  to converge C2 and SA systems as directed by
  Secretary of Defense and Joint Staff
• Agenda
• Background and Facts
• Defining the battlespace
• Brigade and Above
• Brigade and Below
• Joint Blue Force Situational Awareness

3
Battle Space Awareness Guidance

• OIF/OEF Lessons Learned
• FBCB2-BFT and C2PC very successful provides
  foundation on which to build
• Joint Staff Direction, Subject Blue Force
  Tracking, 13 AUG 03
• VCSA and Assistant Commandant, USMC present an
  integrated briefing to JROC discussing way ahead
  for converging efforts to achieve a single joint
  capability OCT 03
• Joint Blue Force Situational Awareness (JBFSA)
• Initial strategy for JBFSA convergence

Converge Command and Control (C2) and Situational
Awareness (SA) capabilities for Ground Forces
soonest
4
Strategy to Achieve a Single Joint Capability

• Task USMC and Army converge to a single Blue
  Force Tracking (BFT) capability
• Implied Tasks
• Focus on ground forces for near term
• Facilitate interoperability with Air Force, Navy
  and Coalition by putting Army, Marines and SOF on
  one baseline
• Not just BFT C2 and SA
• Achieve capability soonest
• Not just Applications must consider hardware,
  policies and procedures
• Restated Task Develop an architecture capable of
  handling multiple systems and schema
  simultaneously to provide transparent C2 and SA
  capabilities to ground forces soonest

5
Combat Identification (CID) CAPABILITY

CID is The process of attaining an accurate
characterization of detected objects in the
joint battlespace to the extent that high
confidence, timely application of military
options and weapons resources can occur.

PLUS
Target Identification
Situational Awareness (Includes BFT)
Supports
Fratricide Reduction Increased Combat
Effectiveness Across Four Mission
Areas Air-Surface Surface-Surface Surface-Air
Air-Air
6
Blue Force Situational Awareness andBlue Force
Tracking Definitions
Why Friendly Intent What Friendly Status Where
Friendly Location Who Friendly Unit ID
BFSA
BFT
BFSA The collection and integration of
capabilities and systems employed to obtain and
report Blue force precision identification,
location, status, and intent information to
decision-makers. JBFSA includes both one-way and
two-way active reporting capabilities BFT
Employment of techniques to actively or passively
identify and track US, allied, or coalition
forces for the purpose of providing the combatant
commander enhanced battlespace situational
awareness and reducing fratricide DRAFT Joint
Blue Force Situational Awareness Operational
Concept, US JFCOM, 18 AUG 03
7
BFT/BFSA Systems Overview
Multiple systems, sharing SA and C2 message
information where possible, integrated together
to produce the blue pictures
MTS Movement Tracking System Provides Blue SAand
Very limited C2 messaging.Primarily used by
CSS/STAMIS
OmniTRACS Qualcomm Commercial Military Tracking
System Provides one way Blue SA Very limited C2
messaging Interfaces to GCCS Used by commercial
trucking industry gt 400,000
Radiant Blue Expeditionary Warfare Blue
Force Tracking Integrate LOS generated BFT tracks
with MMC and PACOM Top COP USN Concept
MDACT/C2PC Mounted Data Automated Communications
Terminal / Command and Control PC Displays Red
and Blue SA C2 messaging Interfaces to GCCS via
L- band 18,000
GRENADIER BRAT One way transmission
system,GCCS Interface through ground stationand
SIPRNET, ProvidesBlue Force SA data 3000
FBCB2 Force XXI Battle CommandBrigade and
Below Blue SA, Red SA, Georef SAfeatures-alerts,
Full map, C2 messaging,Tactical planning
features. Used by Army Brigade and below 59,622
planned
HF Tracker
8
BFSA Systems Characteristics
 
9
As-Is Systems/Shortfalls (Sep 03)
Shortfalls
Bottom Line no single, complete SA picture for
operating forces, nor common tools to enable
Joint Ops
10
Communications Architecture
Joint Corps Div Bde Bn Co Plt Sqd Team
11
Proposed Way Ahead
SOF
USMC
Army
GCCS-J
GCCS-J
Joint
Corps
GCCS-J/JTCW
GCCS-A/JTCW
Joint Tactical COP Workstation (JTCW) FBCB2/BFT
MCS
DIV
Brigade
NA
BN
CO
PLT/SQD/TM
Cobra Family
12
Convergence Drivers

• Brigade and Above
• Single capability based on the Joint Tactical COP
  Workstation
• USMCs C2PC is foundation
• Must meet Armys Good Enough requirement

• Brigade and Below
• Single capability based on the Armys FBCB2
• Must meet USMCs and SOCOMs key capabilities

• USMC and SOCOM Capabilities
• Must be NSA Type I Encrypted or capable of
  operating on the SIPRNet
• Must be a native GCCS-J / JC2 COP client and must
  be able to dynamically establish direct peer to
  peer communications with other JBFSA-capable
  units
• Must open its Application Program Interfaces
  (API) to third party developers
• Demonstrate low probability of detection
  (LPD)/low probability of intercept (LPI)
  capabilities (SOCOM unique)

• Army Commanders Needs Top 7 One
• Friendly Locations
• Current Enemy Situation
• Running Estimate
• Graphic Control Measures (GCMs,FSCM,Capability
  Overlays)
• FRAGOs
• Commanders SITREPs
• FS Coordination Measures/Capabilities Overlap
• Joint and Coalition Interoperability

13
Brigade and Above Downselect

• Joint Tactical COP Workstation provides superior
  Joint interoperability Bde or Regt can operate
  directly under CJTF through a GCCS-A or IOS
  Server
• Current version of JTCW requires capability
  upgrades to meet Army needs specified in Maneuver
  Control System (MCS) ORD
• Current version of JTCW does not support Army
  Battle Command System interoperability

• Air Tracks
• TACWEB Application
• Multi-National Interoperability Program (MIP)
• Planning Tools / Manager

• Military Decision Making Process (MDMP) Assistant
  with Wargaming/Rehearsal Capability
• MCS-Engineer
• JWARN NBC Capabilities

Achieve interoperability by converging to one
system. Use JTCW baseline because of inherent
joint attributes. Develop Army-unique
injectors to meet MCS ORD requirements and
maintain ABCS interoperability
14
Brigade and Above Migration to Interoperability
Army and Marine Corps bde/regt can be seamlessly
cross- attached
INTSUM / OPSUM Logistics Information NBC
Warnings Reports TBMD and Air Defense
Warnings CCIRs Obstacle Information Combat
Power Air Tracks Plans and Orders Commander
Sitreps ATO / ACO Air Coordination
Measures Fires (Targets, FSCMs, Overlays
Battlefield Geometries Control
Measures Plans and Orders Commander
Sitreps Red Picture (Correlated and SPOT
Reports) Blue SA (Air/Ground at platform/unit
levels)
Army Bde can Operate Adjacent To Marine Corps
Regiment
Army Bde can work directly for JTF
JTCW pursuitof NR KPP
Key C2/SA Interoperability Metrics
Systems improving interoperability now
simultaneously to converging
USA MCS 6.3.2 MCS 6.3.D MCS 6.4 MCS 6.4 JTCW
7.0 USMC C2PC5.8 C2PC 5.9 C2PC 6.0 C2PC 6.1
Sep 03 Mar 04 Mar 05 Mar 06 Mar 07
15
Brigade And Below Bottom Line

• Convergence on an interoperable BFT capability is
  feasible. Services remain committed to FBCB2
  HW/SW as part of a potential solution
• Complexity at platform-to-battalion level
  requires further analysis to fully appreciate the
  adjustments required in communications hardware,
  software protocols, policies and Service-unique
  TTPs
• Additional work groups formed to drill further
  into the following key issues
• Differences in Engineering
• Different approaches to Policies such as
• Security
• Unit Reference Number (URN)
• Messaging
• Naming Standards
• Different capabilities/CONOPS required at
  platform level

16
Open System Interconnect Model
17
Functional Need/Operational Architecture Analysis
Guidance
Requirements Crosswalk
Doctrine Organization Training Materiel Leadership
Personnel Facilities
Vignettes (Mission Threads) Development
Capability Assessment
IER
Activity Modeling
18
Brigade and Below Way Ahead
Army (LTI)
USMC (TDN)
Capabilities
SA
Joint address Book and CONDOR-like capability
enables horizontal interoperability enables
multicast exchange FBCB2 and C2PC modify their
systems to be interoperable FBCB2 now integrated
onto existing USMC networks Digital Cross
service attachments not possible USMC manually
configures own network
C2 Any Size
C2 small
SA forwarding (VDX)
Theater OPS CTR Theater Comms TOP COP
III
X
C2PC
C2PC
IOS
PASS
II
II
Info Exchanges SA (Blue Pos, Geo-Ref,
uncorrelated Red) seen by all Direct C2 message
exchange to/from all except DACTs connected via
SINCGARS possible Small C2 messaging supported
to L-Band FBCB2
FBCB2
C2PC
C2PC
FBCB2
EPLRS
EPLRS
EPLRS
SINCGARS ASIP
SINCGARS ICOM
INC
MODEM
Common HH
Common HH
FBCB2
FBCB2
19
Challenges

• Policy
• Unit Reference Number (assignment and management)
• Security (classification of Position Location
  Indicator)
• Messaging (implementation of the standard)
• Naming Standards
• Engineering
• Encryption of L-band transceiver
• Non-Interoperable comms hardware at lower
  echelons
• Bandwidth and system constraints
• Leveraging terrestrial and space-based comms
• Latency
• Multi-level security
• Ubiquitous self-healing networks

20
Joint Blue Force Situational Awareness (JBFSA)
21
Progress On USA-USMC Convergence

• Two-way Radiant Mercury
• Two-way SA
• C2 On-the-move Network Digitized Over-the-horizon
  Relay (CoNDOR)
• Synchronization of Comm and C2 acquisition
  offices in both Services
• FBCB2-C2PC Interoperability
• USMC procurement of FBCB2 (317 OIF II)
• FBCB2 being applied to selected USMC airframes in
  support of OIF (9/149)
• Coalition Interoperability

22
JBFSA Capabilities
JBFSA Proposed Interoperability Enhancements
23
JBFSA Spiral 1

• One stage of capability development (Spiral 1)
  that provides
• Near-term interoperability of FBCB2 and C2PC as
  an interim capability
• An encrypted L-band solution for current BFT
  systems
• A bridge for isolated Line of Sight (LOS) BFT
  communities
• Data dissemination architecture for JBFSA

24
Spiral 1 Gap to Capability Crosswalk
FBCB2-C2PC INTEROPERABILITY ENCRYPTION CONDOR
DATA DISSEMINATION
Spiral 1 (FY-04)
Gaps
JBFSA MNS (April 2002) USA-USMC OIF Lessons
Learned (2003) AFSPC/XO (22 Oct 03)
Fully addressed Partially addressed
25
Improved Capability from FY04 Enhancements

• FBCB2-C2PC Interoperability
• Common method for shared USA/USMC battlefield
  SA and C2
• Reduced SA Latency. Circumvents communications
  path through GCCS Family of Systems
• Improved prospects for fratricide avoidance
• Encryption of JBFSA Communications Links
• Prevention of enemy exploitation with initial
  focus on FBCB2 L-Band encryption
• Reduced risk of divulging sensitive information
  on Blue Force location, status, and intent
• Optimized cryptographic mechanisms and key
  management approaches
• CONDOR (C2 On-the-Move Network Digitized
  Over-The-Horizon Relay)
• Provide OTM OTH capability for tactical units
  even in complex/urban terrain.
• Reduced potential for fratricide
• Enable SA reliable dissemination throughout
  battlefield among dis-similar data networks when
  extended Beyond Line Of Sight (BLOS)
• Data Dissemination
• Distributed BFSA access points.
• Normalized BFSA data formats for internet
  protocols and publish / subscribe regimes.
• Efficient Band Width utilization.
• Promotes Timeliness / Responsiveness.

26
JBFSA Spiral 2

• Two stages of capability development (Spiral 1
  and 2) that provide
• All capabilities of Spiral 1, plus the ones
  presented below
• Deconfliction of JBFSA and targeting locations
• Anti-jam position, timing, speed
• Responsive Joint Air Ground Situational
  Awareness Sharing
• Enhanced dismounted and unattended system
  capabilities (two-way communications for SOF
  survival radios, JTRS L-band for infantry)
• NSA Type 1 encryption with robust OPSEC
  characteristics where applicable

27
Spiral 2 Gap to Capability Crosswalk
Responsive Joint Air-Ground SA Sharing Anti
Jam GPS GPRS / SLICE L-Band (Phase
II) Battlefield Deconfliction NSA Type-1
Encryption With Robust OPSEC
Spiral 2 (FY-05)
Gaps
Fully addressed Partially addressed
JBFSA MNS (April 2002) USA-USMC OIF Lessons
Learned (2003) AFSPC/XO (22 Oct 03)
28
Improved Capability from FY05 Enhancements

• Responsive Joint Air - Ground SA Sharing
• Improved C2 architecture response to ground
  requirements for aerial fires
• Interoperability between AOC and TOC to
  alleviate bandwidth overload.
• Improved Timeliness / Responsiveness with
  increased potential for fratricide avoidance
• Anti Jam GPS
• To reduce impact of ECM employed against JBFSA
  GPS.
• Increased resistance to GPS jamming for the
  Precision Lightweight GPS Receiver (PLGR).
• Improved FBCB2 Blue Force SA picture via PLGR
  automated self-location feed under ECM.
• GPRS/SLICE L-Band (Phase II)
• Leverages SLICE L-Band waveform development.
• Upgraded AN/PRC-112G CSAR Software definable
  radio capabilities
• Provides 2-way L-Band (1-way S-Band) OTH
  LPI/LPD tagging and location data.
• Battlefield Deconfliction
• Effects Management Tool target analysis to
  perform complete spatial battlefield
  deconfliction.
• Improved timeline for engagement of time
  critical targets via management by exception.
• Improved critical Battlespace SA to decision
  makers for local or remote risk assessment.
• Increased Fratricide Avoidance/ Decrease Kill
  Time
• NSA Type 1 Encryption with Robust OPSEC
  Characteristics (Where Applicable)

29
Questions?
30
Backup
31
Converged Communications Architecture
USA
USMC
Joint Corps Div Bde Bn Co Plt Sqd Team
Bandwidth
Bandwidth
256 kb
256 kb