C4ISR and Networked Fires

1

• C4ISR and Networked Fires
• Precision Strike Association Annual
  SymposiumApril 21, 2004
• MAJ (P) Dave Bassett
• PM Software Integration (Provisional)
• Fort Monmouth, NJ

Program Managers Intent Field FCS-equipped
Units of Action with Threshold Future Force
Capability by the End of the Decade
2
Outline

• Program Introduction
• C4ISR capabilities
• Networked Fires

3
FCS Unit of Action ElementsOne Team Partner
Responsibilities
Manned Ground Vehicles
Network / Software / C4ISR
Unmanned Air Vehicles
Logistics Training
LDSS Northrop Grumman PSMRS
Honeywell Training Support Northrop Grumman
Dynamics Research Corp Computer Science
Corp
Unmanned Ground Vehicles
Unattended Munitions
Non-FCS Elements
4
FCS Program Master Schedule
FY2002
FY2003
FY2004
FY2005
FY2006
FY2007
FY2008
FY2009
FY2010
FY2011
FY2012
FY2013
CY2002
CY2003
CY2004
CY2005
CY2007
CY2008
CY2009
CY2010
CY2011
CY2012
CY2013
CY2006
MS B
MS B Update
OIPT
PDR
NMMDR
FRP
FOC
IOC
DRR
DCR
SRR
SFR
IPD 2
IPD 1
IOT
LUT/OE
IBR II
IBR I
System Development and Demonstration
Concept and Technology Development
Production and Deployment
Science and Technology and CTD leading to future
technology insertions and Increments
MS B - Milestone B IOT Initial Operational
Test OIPT - Overarching Integrating Process
Team FOC Full Operating Capability IBR -
Integrated Baseline Review SRR System
Readiness Review PDR - Preliminary Design
Review DCR Design Concept Review DRR Design
Readiness Review IPD Initial Production
Decision IOC Initial Operating Capability SFR
System of Systems Functional Review LUT/OE
Limited User Test / Operational Evaluation NMMDR
Network Maturity Milestone Decision Review
Network Maturity Milestone Decision Review
(NMMDR) 7/11/2008 Initial Production Decision
1 (IPD 1) 11/14/2008 Initial Production
Decision 2 (IPD 2) 8/14/2009
5
Outline

• Program Introduction
• C4ISR capabilities
• Networked Fires

6
C4ISR Overview
Information Domain
Joint Common Database
Information Layer UA Infosphere
Open Software Architecture
Logical Database
Interoperable export
RT Synchronization
Planning Fires Effects Information
Ops RSTA C4ISR Mgmt Sustainment Situation
Awareness Execution Intelligence Airspace
C2 Training Rehearsal Nontactical Support
FIOP
Interoperability Domain
JTRS
Reachback
Warfighter Interface
HHQ
XX
Battle Command
UE/HQ
WIN-T
Hierarchical Ad-Hoc Network
stubnet
Data Images Voice Video
Vetronics
UGS
Common Vehicle Subsystems
Platform Systems Domain
EO/IR
EO/IR SAR/MTI
Network-Centric Warfighting Domain
OO V1.0
7
System of Systems Common Operating Environment
(SOSCOE)
"Approved for Public Release, Distribution
Unlimited TACOM 9 Sept 2003"
8
Domain Application Interfaces with SOSCOE
Family of APIs
SoS Common Operating Environment API
Services to be exposed to the Domain Applications
Common Services
Distributed
Services
Inter-Service Communication Not exposed To
Domain Applications
OS Abstraction layer
Basic
Services
OS Services
9
Outline

• Program Introduction
• C4ISR capabilities
• Networked Fires

10
See First/Persistent ISR

• Distributed/Networked Sensors
• Provides unequaled Situational Awareness down to
  the Soldier System
• Enhances survivability through knowing and
  avoiding enemy fires
• Enables precision engagement beyond the effective
  range of the opponent
• Maintain contact and engagement in detail
  throughout the mission

03-22
11
Understand First/Act First/Finish Decisively
CONUS / Higher HQs En Route Planning Rehearsal
SATCOM
Legend
Interfaces
Intra
-
FCS
Interoperable
National ISR
Joint ISR
Joint Coalition Assets
UAV
FCS
Other Objective Force Coalition Forces
Dismounted Combat Team A
NLOS
NGO
Command
FCS
C2 Subsystem
Networked Fires Using Cooperative Engagements
"Approved for Public Release, Distribution
Unlimited TACOM 9 Sept 2003"
12
Networked Fires Process
This integrated process consists of the following
steps Step 1 Define/update Attack Guidance.
Step 2 Perform ISR Integration Step 3 Detect
and locate surface/air targets. Step 4 Provide
Intelligence Support to Target Development Step
5 Assign effectors to target. Step 6 Track
Targets for Engagement. Step 7 Establish
sensor-to-shooter linkages. Step 8 Deconflict
mission with air/ground and UE /JIM forces. Step
9 Engage targets Step 10 Conduct Battle Damage
Assessment Step 11 Provide re-attack
recommendation
Networked Fires are comprised of BLOS and NLOS
and some LOS (Cooperative Engagement) fires
focused to achieve an effect. While the principal
applications of Networked Fires will come from
NLOS units employing FCS Cannon and NLOS LS
systems, BLOS and LOS weapons may be tasked to
support Networked Fires.
Conduct Networked Fires-Process consists of a
sequence of operational tasks and their
associated information exchanges that must be
performed to achieve the commanders intent
through the synergistic application of all
available lethal and non-lethal effects.
13
UNCLASSIFIED
NLOS-LS Elements
LAM
PAM
Container/Launch Unit
CLU
Loiter Attack Munition (LAM)
NLOS-LS TO BE ONE OF THE UNATTENDED MUNITIONS
WITHIN THE FCS FAMILY OF SYSTEMS
Precision Attack Munition (PAM)
14
NLOS-LS System Description

• System Capabilities
• Networked, extended range targeting and
  precision attack of a variety of targets
  including fleeting high value and both moving and
  stationary armor
• Platform independent vertically launched
  missile system with self contained fire control
  and communications
• Automatic/Aided Target Recognition
• Two-way networked data link

• Characteristics/Description
• FCS UA Core System
• Transitions Army/DARPA NetFires Demo Program
  into Development and Production

Precision Attack Munition (PAM)
Loiter Attack Munition (LAM)
03-35
NLOS-03-057
15
Networked Fires NLOS/BLOS
(3,5,7,9)
Class III/IV UAV JTRS/WNW
(4,8)
(2)
(1,6,10)
16
Battle Command Software Services
17
Networked Fires for Deliver Effects
A Fires and Effects Thread is primarily comprised
of Services within BCME and PPS with input from
SU.These Services are linked by the Task
Integration Networks (TINs).Services are
executed IAW Policies. These are rules for
automated processing. They control who shoots
what, when, on under on specific authority
SoS COE provides data and services via
publish/subscribe
Conflict Control
Next WTP
Adjust Fires
New Weapon/Target Pairing
4.3.1
Prioritize Targets
Deconfliction Successful
BDA Not Required
4.3.3
4.3.4
4.3.6
4.3.9
Release Sensor /Effector
Perform Weapon /Target Pairing
Deconflict Mission
Prosecute Target
R
R
A
A
R
R
O
O
R
R
X
X
4.3.2
4.3.5
4.3.7
4.3.8
Build Effectors List
Command Maneuver
Assess Effect
Determine Next Action
Sensor
FEC
Mnvr S3
NLOS Bn
Sensor
FEC
FEC
FEC
FEC
The execution of the logic of the Services
comprising the TIN can occur throughout the
network based on the behavior described by the
rules set by the POLICY EDITOR. Gain is less
message traffic across the network, faster
response, and greater mission throughput vice
current the model of serial mission processing
18
Summary

• FCS subset of UA subset of UE subset of Joint
  Forces subset of Multinational Forces (FCS -gt UA
  -gt UE -gt Joint -gt Multinational)
• FCS Family of Systems defined in ORD
• Multidimensional System of Systems Integration
• KPP axis 7 KPPs
• Systems axis MGV, UGV, UAV, NLOS-LS, IMS
• Components
• C4ISR C2 CC ISR SOSCOE
• SOSCOE
• Software layer in all FCS Family of Systems
• Eases integration of distributed capabilities
• C2 4 areas WMI, SU, BC PP
• SOSCOE and C2 software packages enable Networked
  Lethality
• Networked Fires key to the employment of FCS

19
Backups
20
FCS ISR Philosophy

• Be flexible and adaptable
• Use modular payloads
• Upgrade easily
• Locate human interface anywhere
• Decentralize
• Collection of small sensors
• Fuse data locally before hierarchically
• Analysts can be centralized or distributed
• Tailor sensors
• Local area and MOUT sensors for platoons
• Wide-area coverage for Brigade
• Deploy SIGINT/ESM widely to detect hidden targets
• Tailor presentation
• Reconfigure display to consumer
• Sensor data types published for subscription

• Focus organic ISR coverage
• Exploit UE assets for wide-area coverage
• Deploy organic ISR forward
• Provide timely sensing
• Update close, critical regions most often
• Use local resources for fast response
• Provide quality sensing
• Correlate to reduce false tracks due to false,
  redundant detects
• Match sensor (and system of sensor) accuracy to
  weapons
• Blocked approach
• Block 1 is strongly capability based but guided
  by Block 2 directions
• Block 2 will be more top-down

21
Integrator Roles

• System Engineering
• Translate top-down requirements to sensors
• Refine internal interfaces
• Develop platform-to-sensor interfaces
• Commonality Growth
• Ensure commonality of parts
• Define standard, public interfaces for modularity
• Develop design principles to reduce upgrade
  cost/schedule
• Test
• Develop VV plan
• Integrate SW and HW
• Support LSI C4ISR SIL

(Approved for Public Release, Distribution
Unlimited)
22
The Infosphere Is Our Domain forInformation
Management

• Worldwide information source access
• Shared and managed information
• Controlled access to sensitive information
• Tools and services for info manipulation
• Tailored information to each user

Affordable Data Structures That Use Available
Worldwide Databases and Information Fusion In
Near Real Time
23
FCS Interfaces and Interoperability
Maneuver
C2
JSF
MCTIS
C2PC
TAOM/MCE
JDP
JWARN
AWACS
SIAP
FIOP
SIMACET
EC-3B
AH-64D
AMPS/ JMPS
TCO
GCCS
FIA
DTSS
DCTS
SECOMP-I
GIG
TCS
FBCB2
SJFHQ
TAIS
GPS
Mounted Warrior
Teleport
MCS
CAP Vehicle
JNMS
IBS/GBS
A2C2S
UAH
Armed Robotic Vehicle
Mounted Combat System
JTRS
SISP
TBMCS
Land Warrior I/II
JTAGS
Infantry Carrier Vehicle
MILSATCOM
C2 Vehicle
IMS
WIN-T
TES
Profiler
Soldier
Network
CBRNRS
JDISS
BLT
Recon Surv Vehicle
Paladin AFCS
Mule
JSOF C2
JSIPS
Networked Battle Command
Multi- Mission Radar
GMLRS
Small Unmanned Ground Vehicle
Homeland Defense
ATACMS
Intelligent Munitions System
HIMARS
DOE
DIA
MLRS
Firefinder
FORCEnet
NSA
NGIC
DCGS
Unattended Ground Sensors
CIA
NIMA
DCGS-A - ASAS
AFATDS
NLOS Launch System
THAAD
PAM
National Databases
Patriot
MEADS
NLOS Cannon
UAV Class I
Prophet
JTAGS
Sentinel
AMDWS FAADC2 ADSI
JWICS
IMETS
LSDIS
NLOS Mortar
UAV Class II
Networked Fires
AFWA
BATES
ISR
FED
Maint Vehicle
UAV Class III
Comanche
ADOCS
JLENS
Medical Vehicle
UAV Class IV
M-109A6
PFED
TLAM
Shadow 200
Hunter
LFED/FOS
WARSIM
Predator
GCSS-A
FTTS
CSSCS
Aerial Common Sensor
Chinook
NFCS
C2 Constellation
MFCS
Blackhawk
CATT
TESS
TSV
TMIP/MC4
DMLSS
Rivet Joint
ADLER
CCTT
TSV
DLS
DIMHRS
LAMD
FMTV
Netwars
OneSAF
JSTARS
LMSR
Global Hawk
JSIMS
IAS
GTN
Version 3/31/03
Sustainment
24
Role of the LSI

• Why a Lead Systems Integrator (LSI)
• The Armys first large scale system of systems
  development, integration across many disciplines
  and platforms, requires a robust / dedicated
  organization experienced in large scale systems
  integration
• What the LSI does
• Trusted Industry member of the FCS Team (ARMY
  /Defense/ Best of Industry) that has total
  systems integration responsibility (top down
  development)
• Provides the Team a general contractor focused
  on integration for resource allocation,
  subcontract implementation and coordination, and
  programmatic responsibilities
• Provides the vital link to the Best of Industry
  including domestic / foreign contractors,
  Government programs / Labs, and educational
  institutions
• What the LSI does not
• Does NOT provide hardware solutions to subsystem
  / element requirements

Synchronize and influence the piece parts which
will become the network Dependent on players
within and outside the Army
03-40
25
What Is One Team

• Army, LSI and Industrial Partners
  Organizationally Integrated
• All Executing to the Same Plan
• All Using the Same Processes and Best Practices
• All Sharing the Same Timely Data for Control and
  Corrective Action
• All Incentivized to Share the Same Destiny

Army/DARPA
The Armys LSI
Best of Industry
Trusted Partners
Trusted Partners
Key Enabler Electronic Integration for
GeographicallyDispersed Team with Site-Specific
Systems
03-18
26
What does Network Centric Buy Us?
Execution
Time
New Sciences and Warfare VADM A.K. Cebrowski
9/21/98
Approved for Public Release, Distribution
Unlimited TACOM 8 Oct 2003
27
Building the Best of Industry Team
UAV
Raytheon Company Ft. Wayne, Indiana Battle
Command and Mission Execution PKG 18
General Dynamics Bloomington, Minnesota Integrate
d Computer System PKG 26
Dynamic Research Corp Andover,
Massachusetts Training Support Package PKG 27
United Defense ASD GSD Bloomington,
Minnesota Santa Clara, California MGV ARV PKG 5
Textron Systems Wilmington, Massachusetts Unatten
ded Ground Sensors PKG 15
General Dynamics Robotics Systems Westminster,
Maryland ANS PKG 9
General Dynamics Land Systems Sterling Heights,
Michigan MGV
Boeing McDonnell Douglas Helicopter Co. Mesa,
Arizona Warfigther Machine interface Situation
Understanding PKG 23
Northrop Grumman Mission Systems Carson,
California Network Management PKG 17 LDSS
PKG 10
iRobot Corp Burlington, Massachusetts SUGV PKG 8
Honeywell Defense Electronics Systems
Albuquerque, New Mexico PSMRS PKG 11
BAE Systems / CNIR Wayne, New Jersey Ground
Comm. PKG 24 Air Comm.-PKG 25
Lockheed Martin Missiles Fire Control Grand
Prairie, Texas MULE PKG 7
Lockheed Martin (Orincon) Defense Corp San
Diego, California Level 1 Fusion PKG 16
Northrop Grumman - ESD Linthicum, Maryland Air
Sensor Integrators- PKG 14
Northrop Grumman Systems Corporation San Diego,
California Class !V UAV PKG 1
Computer Science Corp Hampton, Virginia
Training Support Package- PKG 27
General Dynamics Decision Systems Scottsdale,
Arizona Sensor Data Management PKG 16 Planning
and Preparation PKG 19
Raytheon Company Plano, Texas Ground Sensor
Integrators PKG 12
Austin Info Systems Austin, Texas Situation
Understanding PKG 20
Northrop Grumman InfoTech McLean, Virginia
Training Support Package- PKG 27
03-19
28
FCS Network Centric Architecture
Joint Common Database
Interoperability
Key Performance Parameters
FSB

1. Joint Interoperability
2. Networked Battle Command
3. Networked Lethality
4. Transportability
5. Sustainability/Reliability
6. Training
7. Survivability

SOSCOE
HHQ
XX
Battle Command
UE/HQ
FSB
HierarchicalAd-Hoc Network
WIN-T
WNW
WNW
Data Images Voice Video

• FCS Advantage
• Conflict duration 50-60
• Survivability 60-80
• Logistics footprint 30-70

JTRS
FCS Unit of Action / Unit of Employment
Approved for Public Release, Distribution
Unlimited
29
Defining Program Relationships Complementary
Programs
FCS Core Defined as the 19 Systems
specifically called out in the FCS ORD, to
include current programs that will be integrated
directly into the 19 Systems. FCS is responsible
for the integration and procurement of these
systems into FCS platforms.
UA Battlespace
JTA
FIOP
UA SoS
JCAD
ACS
UA Complementary Those existing systems
essential to get the family of systems to work
together but are not part of the FCS Core
Systems, or to facilitate operation of an
individual core system. They will also have
applicability outside the FCS Core Systems. Those
systems needed to operate or support a system of
systems within the UA but not FCS core systems.
Unit set fielding implications.
DCGS-A
LW Block III
Core Systems
C130
Future Force Capability
Javelin
Interoperability
RAH-66
UA Complementary Systems
TSV
C17
UE Above Complementary Systems
UE Above Complementary Those systems needed
to operate or support a system of systems
outside the UA.
New/Proposed Systems
Future Increments Technology Base
Family of Interoperable Operational Pictures
Approved for Public Release, Distribution
Unlimited
30
FCS IPTs by Work Share
Systems Engineering, ACE
Unmanned Systems
Training
Integrated Simulation Test
Supportability
Program, Business, and Supplier Management
C4ISR
MGV
Software distributed throughout IPTs
31
FCS Increment I
FCS Increment I
32
C4ISR Work Packages
Textron Systems - Wilmington, Massachusetts Unatte
nded Ground Sensors PKG 15
General Dynamics Bloomington,
Minnesota Integrated Computer System PKG 26
Raytheon Company Ft. Wayne, Indiana Battle
Command and Mission Execution PKG 18
Boeing, Mesa, AZ Warfighter Machine Interface-PKG
23
Northrop Grumman Mission Systems - Carson,
California Network Management PKG 17
BAE Systems/CNIR Wayne, New Jersey Ground
Comm. PKG 24 Air Comm.-PKG 25
Lockheed Martin (Orincon) Defense Corp - San
Diego, California Level 1 Fusion PKG 16
Northrop Grumman Sys Corp Linthicum, Maryland
Air Sensor Integrators- PKG 14
General Dynamics Decision Systems Scottsdale,
Arizona Sensor Data Management PKG 16 Planning
and Preparation PKG 19
Raytheon Network Systems - Plano, TX Ground
Sensor Integrators- PKG 12
Austin Info Systems - Austin, Texas Situation
Understanding PKG 20
33
Sustainment

• Provides the functions and services to assess and
  maintain personnel and equipment readiness,
  support deployment and operations training
• Provides status on physical and functional
  availability on both platforms and soldiers from
  which readiness can be derived to support Command
  and Control and Logistics
• Collects observations on consumption, LRU repair
  and replacement, delivery and receipt

C4ISR is a Key Enabler for Sustainment