bassett.67):88€(;)));::()&&@@@€(;:/34568.ppt

Bassett

1. 1
10/17/24 02:05 PM
C4ISR and Networked Fires
Precision Strike Association Annual Symposium
April 21, 2004
MAJ (P) Dave Bassett
PM Software Integration (Provisional)
Fort Monmouth, NJ
Program Manager’s Intent: Field FCS-equipped Units of Action with
Threshold Future Force Capability by the End of the Decade

2. 2
10/17/24 02:05 PM
Outline
•Program Introduction
•C4ISR capabilities
•Networked Fires

3. 3
10/17/24 02:05 PM
FCS Unit of Action Elements
One Team Partner Responsibilities
Unmanned Air Vehicles
Manned Ground Vehicles
Class IV - 2
Northrop
Grumman

Class III - 12
Class II - 36
Class I - 54
Logistics & Training
LDSS – Northrop Grumman
PSMRS – Honeywell
Training Support
– Northrop Grumman
– Dynamics Research Corp
– Computer Science Corp
Unattended Munitions
Network / Software / C4ISR
Non-FCS Elements
Battle Command & Mission Execution –
Raytheon
SOSCOE / Warfighter Machine Interface – Boeing
Level 1 Fusion – Lockheed Martin
Sensor Data Mgmt / Planning & Prep – GDDS
Situation Understanding – Austin Info Systems
Network Management – Northrop Grumman
Integrated Computer System – General Dynamics
Unattended Ground Sensors – Textron
Ground Sensor Integration – Raytheon
Air Sensor Integration – Northrop Grumman
Ground Comm & Air Comm – BAE Systems
Command & ControlInfantry Carrier
Medical
Mounted Combat Sys Recon & Surveil.
NLOS mortarNLOS Cannon
Maint. & Recovery
102

49

60

30

18

24

10

29

General Dynamics / United Defense
Unmanned Ground Vehicles
Armed
Robotic Vehicle
United Defense Mule
Lockheed Martin
Small UGV
iRobot
45

81
78
Auto. Navigation - GDRS
NLOS LS (LAM, PAM) 60
Intelligent Munition System
Trucks 376
81 mm Mortar 12
RAH-66 Comanche 12
AAFARS 2 , HTARS 2

4. 4
10/17/24 02:05 PM
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
FCS Program Master Schedule
FY2002FY2003FY2004FY2005FY2006FY2007FY2008FY2009FY2010
MS B
Production and
Deployment
Concept and
Technology
Development
LUT/OE
FY2011
CY2002CY2003CY2004CY2005CY2006CY2007CY2008CY2009CY2010CY2011
MS B
Update
IBR IIBR II
SFR
OIPT
SRR
DCR IOC
FY2012
CY2012
IOT
FOC
FY2013
CY2013
FRP
NMMDR
IPD
#1
IPD
#2
Science and Technology and CTD leading to future technology insertions and Increments
PDR
DRR
System
Development and
Demonstration
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

5. 5
10/17/24 02:05 PM
Outline
•Program Introduction
•C4ISR capabilities
•Networked Fires

6. 6
10/17/24 02:05 PM
C4ISR Overview
CROP
Logical Database
Information Layer
“UA Infosphere”
Interoperable
export
WIN-T
UE/HQESO
Open Software Architecture
CROP CROP CROP CROP
Common Operating
Picture
HQ
ESO
JTRS
EPLRS
SINCGARS
VHF
Link 4A
Link 11
Link 16
Hierarchical Ad-Hoc Network
Data
Images
Voice
Video
Planning
Fires & Effects
Information Ops
RSTA
C4ISR Mgmt
Sustainment
Situation
Awareness
Execution
Intelligence
Airspace C2
Training &
Rehearsal
Nontactical Support
C
o
m
m
o
n

S
e
r
v
i
c
e
s
I
n
f
o
r
m
a
t
i
o
n

M
a
n
a
g
e
m
e
n
t
C
o
m
p
u
t
i
n
g

a
n
d

N
e
t
w
o
r
k
i
n
g
W
a
r
f
i
g
h
t
e
r

I
n
t
e
r
f
a
c
e
Vetronics
Common Vehicle
Subsystems
HQ
Battle
Command
EO/IR EO/IR
SAR/MTI
UGS
MOSAIC
Reachback
HHQ
MOSAIC
Joint Common
Database
XX
stubnet
O&O V1.0
RT Synchronization
Information Domain
Platform Systems Domain
Network-Centric Warfighting Domain
Interoperability Domain
FIOP

7. 7
10/17/24 02:05 PM"Approved for Public Release, Distribution Unlimited TACOM 9 Sept 2003"
System of Systems Common Operating
Environment (SOSCOE)

8. 8
10/17/24 02:05 PM
Domain Application Interfaces with
SOSCOE “Family” of APIs
Distributed
Services
SoS Common Operating Environment API
Basic
Services
Common
Services
OS Services
Services to be
exposed to the
Domain
Applications
FCS MGV
Systems
FCS UMV
Systems
FCS Training
Systems
FCS
Sustainment
Systems
Inter-Service
Communication
Not exposed
To Domain
Applications
OS Abstraction
layer

9. 9
10/17/24 02:05 PM
Outline
•Program Introduction
•C4ISR capabilities
•Networked Fires

10. 10
10/17/24 02:05 PM
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. 11
10/17/24 02:05 PM
Legend: Interfaces
Intra-FCS
Interoperable
Joint &
Coalition
Assets
CONUS / Higher HQs
En Route Planning
Rehearsal
National ISR
NGO
FCS
C2 Subsystem
SATCOM
Dismounted
Combat Team A
NLOS
Command
Joint ISR
UAV
Other Objective Force &
Coalition Forces
FCSFCS
Networked Fires Using Cooperative Engagements
"Approved for Public Release, Distribution Unlimited TACOM 9 Sept 2003"
Understand First/Act First/Finish Decisively

12. 12
10/17/24 02:05 PM
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 commander’s intent through
the synergistic application of all available
lethal and non-lethal effects.
Networked Fires Process

13. 13
10/17/24 02:05 PM
NLOS-LS Elements
UNCLASSIFIED
Precision Attack Munition (PAM)
Loiter Attack Munition (LAM)
Container/Launch Unit
CLU
PAM
LAM
NLOS-LS TO BE ONE OF THE
“UNATTENDED MUNITIONS” WITHIN
THE FCS FAMILY OF SYSTEMS

14. 14
10/17/24 02:05 PM
Precision Attack Munition (PAM)
Loiter Attack Munition (LAM)
NLOS-LS System Description
Container/Launch Unit
Missile
Computer &
Commo
System
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
NLOS-03-057
03-35

15. 15
10/17/24 02:05 PM
Networked Fires NLOS/BLOS
Class III/IV UAV + JTRS/WNW
(1,6,10)
(3,5,7,9)
(2)
(4,8)
(1) R&SV detects potential target
- Acquires target data & geolocates (Mast Sensors)
- Performs Combat ID
- Prepares Spot report, Updates NCIE
- Reports Target via JTRS WNW
(2) C2V
- BCS (TIN/SoSCOE ICS)Wpn Tgt pairing/de-confliction
- Calls for fire via JTRS/WNW
(3) CLIII/IV Comm Relay
- Relays Call for fire via JTRS/WNW
(4) NLOS Cannon/Mortar/MCS
- Receives/accepts fire mission
- Calls for Target update via JTRS/WNW
(5) CLIII/IV Comm Relay
-Relays target update request
(6) R&SV
- Updates Target data
(7) CLIII/IV Comm Relay
-Relay target update
(8) NLOS Cannon/Mortar/MCS
- Updates gun data & fire
- Publish fires data, R&SV designate timeline
- Munition TOF (MRM)
(9) CLIII/IV Comm Relay
- Relays fire mission designation requirements
(10) R&SV
- Designates per fire mission
- Observes strike, prepares BDA report
- Reports mission (SADB) via JTRS/WNW
Comm Priority
Routine
Immediate
Flash
Flash Override

16. 16
10/17/24 02:05 PM
Battle Command Software Services
GREEN shading:
code procured
here
But resident in
SoSCOE
(common service)
BLUE shading:
code procured
elsewhere
or developed in-
house
But resident here
Level 1 Fusion
Resource
Constrained
Prioritization
Manager
Fusion
Information
Broker
Fusion
Element
Manager
Multi INT
Fusion
Engine
Single INT
Fusion
Engine
Battle Command
& Mission Execution
Order, Report
& Authorizer
Incoming
Order
Processor
Action
Requester
Task
Organization
Policy Editor
Airspace
Control
UGV
Control
UAV
Control
Manned
Ground
Vehicle
Remote
Operation
UGS
Control
Unmanned
Payloads
Control
Unattended
Munitions
Control
Ground
Space
Control
Fires &
Effects
Control
Notification
Conflict
Control
WMI Services
Report
Generator
Role
Manager
Agent
Authorizer
Collaborator
Intelligent
Operator
Monitor
Presentation
Tailor
Visualizer
Presentation
Builder
Presentation
Manager
Task Integration
Network Editor
Translation
Interface
(Text-Voice,
etc.)
WMI
Primitives
Core APIs
Window
Control
O/S Interface
Terminal
Emulators
Logon
Manager
Operator
Account
Manager
Situation Understanding
Object
Refinement
Weather
Service
Situation
Refinement
SU
Toolset
Threat
Refinement
Fusion
Process
Refinement
Readiness
Monitor
Battlespace
Object
Priority
Manager
SU
Presentation
Battle State
Assessor
Planning & Preparation
Rehearsal
Services
Simulation
AAR
Services
Terrain
Analyzer
Objective
Planner
Sensor
Planner
Air Defense
Planner
Fires&Effects
Planner
Survivability
Planner
Airspace
Planner
Security
Planner
Maneuver
Planner
Plan
Assessor
COA
Planner
Services
Comms
Network
Planner
Ground Space
Planner
Ver3.01 20030428
Sensor Data Manager
SDM Kernel (External Control
and Sensor Arbitration)
Unit of Action
Sensor
Plug-Ins
SDM Sensor Framework
(Plug-in control and monitoring)
SDM Utilities
Non-Organic
Sensor
Plug-Ins

17. 17
10/17/24 02:05 PM
Networked Fires for “Deliver Effects”
Next WTP
R RA A
4.3.1
Prioritize
Targets
4.3.2
Build
Effectors
List
New Weapon/Target Pairing
R R
4.3.3
Perform
Weapon
/Target
Pairing
4.3.4
Deconflict
Mission
O O
Deconfliction
Successful
4.3.5
Command
Maneuver
Adjust Fires
R R
4.3.6
Prosecute
Target
X X
BDA Not Required
4.3.7
Assess
Effect
4.3.8
Determine
Next Action
4.3.9
Release
Sensor
/Effector
Conflict
Control
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
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
Sensor FEC Mnvr S3 NLOS Bn SensorFEC FECFECFEC
SoS COE provides data
and services via
publish/subscribe

18. 18
10/17/24 02:05 PM
Summary
•FCS subset of UA subset of UE subset of Joint Forces subset of
Multinational Forces (FCS -> UA -> UE -> Joint -> 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. 19
10/17/24 02:05 PM
Backups

20. 20
10/17/24 02:05 PM
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. 21
10/17/24 02:05 PM
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 V&V plan
–Integrate SW and HW
–Support LSI C4ISR SIL
(Approved for Public Release, Distribution Unlimited)

22. 22
10/17/24 02:05 PM
The Infosphere Is Our Domain for
Information Management
•Worldwide information Worldwide information
source accesssource access
•Shared and managed Shared and managed
informationinformation
•Controlled access to Controlled access to
sensitive informationsensitive information
•Tools and services for Tools and services for
info manipulationinfo manipulation
•Tailored information to Tailored information to
each usereach user
Affordable Data Structures That Use Available Affordable Data Structures That Use Available
Worldwide Databases and Information Fusion In Near Worldwide Databases and Information Fusion In Near
Real TimeReal Time
XXXX

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

24. 24
10/17/24 02:05 PM
Role of the LSI
•Why a Lead Systems Integrator (LSI)…
–The Army’s 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. 25
10/17/24 02:05 PM
Key Enabler: Electronic Integration for Geographically
Dispersed Team with Site-Specific Systems
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
Trusted PartnersTrusted Partners
Best of Industry
Army/DARPA The Army’s LSI
03-18

26. 26
10/17/24 02:05 PM
What does “Network Centric”
Buy Us?
With Planned Synchronization
With Empowered Self-Synchronization
E
x
e
c
u
t
i
o
n
Time
New Sciences and Warfare
VADM A.K. Cebrowski 9/21/98
Lost Combat Power
Approved for Public Release, Distribution Unlimited TACOM 8 Oct 2003

27. 27
10/17/24 02:05 PM
United Defense
ASD & GSD
Bloomington, Minnesota
Santa Clara, California
MGV
ARV – PKG 5
Northrop Grumman
Mission Systems
Carson, California
Network Management –
PKG 17
LDSS – PKG 10
General Dynamics Decision Systems
Scottsdale, Arizona
Sensor Data Management – PKG 16
Planning and Preparation – PKG 19
Raytheon Company
Ft. Wayne, Indiana
Battle Command and
Mission Execution – PKG 18
Northrop Grumman - ESD
Linthicum, Maryland
Air Sensor Integrators- PKG 14
Textron Systems
Wilmington,
Massachusetts
Unattended Ground
Sensors – PKG 15
General Dynamics
Bloomington, Minnesota
Integrated Computer System
PKG 26
BAE Systems / CNIR

Wayne,
New Jersey
Ground Comm.– PKG 24
Air Comm.-PKG 25
Raytheon Company
Plano, Texas
Ground Sensor Integrators

PKG 12
Austin Info Systems
Austin, Texas
Situation Understanding
PKG 20
Lockheed Martin
(Orincon) Defense Corp
San Diego, California
Level 1 Fusion – PKG 16
Honeywell Defense &
Electronics Systems
Albuquerque, New Mexico
PSMRS – PKG 11
Northrop Grumman InfoTech
McLean, Virginia
Training Support Package- PKG 27
Computer Science Corp
Hampton, Virginia
Training Support Package- PKG 27
Dynamic Research Corp
Andover, Massachusetts
Training Support Package – PKG 27
Lockheed Martin
Missiles
& Fire Control
Grand Prairie, Texas
MULE – PKG 7
iRobot Corp
Burlington,
Massachusetts
SUGV – PKG 8
General Dynamics
Robotics Systems
Westminster, Maryland
ANS – PKG 9
General Dynamics
Land Systems
Sterling Heights,
Michigan
MGV
C4ISR UGV Logistics MGVTraining Support UAV
Northrop Grumman
Systems Corporation
San Diego, California
Class !V UAV
PKG 1
Boeing – McDonnell
Douglas Helicopter Co.
Mesa, Arizona
Warfigther Machine interface
Situation Understanding
PKG 23
Building the “Best of Industry” Team
03-19

28. 28
10/17/24 02:05 PM
Interoperability
WIN-T
UE/HQFSB
Hierarchical
Ad-Hoc Network
Data
Images
Voice
Video
HQ
Battle Command
HHQ XX
HQ
JTRS
FCS Unit of Action / Unit of Employment
WNW WNW
FSB
SOSCOE
Joint Common
Database
1.Joint Interoperability
2.Networked Battle Command
3.Networked Lethality
4.Transportability
5.Sustainability/Reliability
6.Training
7.Survivability
Key Performance
Parameters
FCS Advantage:
- Conflict duration: 50-60%
- Survivability: 60-80%
- Logistics footprint: 30-70%
FCS Network Centric Architecture
“Approved for Public Release, Distribution Unlimited”

29. 29
10/17/24 02:05 PM
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 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.
UE & Above Complementary:
Those systems needed to operate or
support a system of systems outside
the UA.
UA Battlespace
Future Increments Technology Base
* Family of Interoperable Operational Pictures
UA SoS
UA Complementary
Systems
UE & Above Complementary
Systems
LW
Block III
Javelin
C130
JTA
FIOP*
RAH-66
ACS
DCGS-A
JCAD
C17
TSV
New/
Proposed
Systems
Core
Systems
I
n
t
e
r
o
p
e
r
a
b
i
l
i
t
y
F
u
t
u
r
e

F
o
r
c
e

C
a
p
a
b
i
l
i
t
y
F
u
t
u
r
e

F
o
r
c
e

C
a
p
a
b
i
l
i
t
y
Defining Program Relationships:
Complementary Programs
“Approved for Public Release, Distribution Unlimited”

30. 30
10/17/24 02:05 PM
6%
5%
7%
29%
27%
9%
9%
8%
FCS IPTs by % Work Share
* Software distributed throughout IPTs
C4ISR
MGV
Supportability
Training
Systems Engineering, ACE
Program, Business, and
Supplier Management
Unmanned Systems
Integrated Simulation & Test

31. 31
10/17/24 02:05 PM
FCS Increment I
FCS Increment I

32. 32
10/17/24 02:05 PM
General Dynamics Decision Systems – Scottsdale, Arizona
Sensor Data Management – PKG 16
Planning and Preparation – PKG 19
Raytheon Company – Ft. Wayne, Indiana
Battle Command and Mission Execution – PKG 18
Northrop Grumman Sys Corp –
Linthicum, Maryland
Air Sensor Integrators- PKG 14
Textron Systems - Wilmington, Massachusetts
Unattended Ground Sensors – PKG 15
General Dynamics – Bloomington, Minnesota
Integrated Computer System – PKG 26
BAE Systems/CNIR – Wayne,
New Jersey
Ground Comm.– PKG 24
Air Comm.-PKG 25
Austin Info Systems - Austin, Texas
Situation Understanding – PKG 20
Northrop Grumman
Mission
Systems - Carson,
California
Network Management –
PKG 17
Lockheed Martin (Orincon)
Defense Corp - San Diego,
California
Level 1 Fusion – PKG 16
Boeing, Mesa, AZ
Warfighter Machine
Interface-PKG 23
C4ISR Work Packages
Raytheon Network Systems - Plano, TX
Ground Sensor Integrators- PKG 12

33. 33
10/17/24 02:05 PM
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