Even though the U.S. Department of Defense budget is shrinking and the country's military footprint worldwide is receding the need for the warfighter to have accurate and actionable intelligence has never been more critical. Data from Intelligence, Surveillance, and Reconnaissance (C4ISR) systems such as radar, image processing payloads on Unmanned Aerial Vehicles, and more will be used and fused together to provide commanders with real-time situational awareness. Each system will also need to embrace open architectures and the latest commercial standards to meet the DoD's performance, size, and cost requirements. This e-cast will discuss how embedded defense suppliers are meeting these challenges.
11. Why Distribution Middleware?
DIA
DIA
FIL
FIL
Each module talks to many
other modules
NAV
NAV
TDM
TDM
3.0 Fusion
CEC
RIP
CEC
RIP
MUX
MUX
MCP
IPCC
MCP
IPCC
aADNS
TRK
TRK
5.0 Communications
L4
L11
L16
L4
L11
L16
7.0 Visualization
ACIS
HMI
ACIS
HMI
TIS
MSI
MSI
IPv6
Distributed Data Framework
Hawkeye has functionally
oriented software modules
Adding new
functionality cascades
integration re-work
across many other
modules
2.0 Sensors
IFF
RDR
IFF
RDR
1.0 Common Services
ESM
ESM
DWC
4.0 BMC2
WAC
WAC
SAFE
SAFE
TDA
TDA
RAIDER CHAT
6.0 Sensor Control
SEN
DSC
SEN
DSC
8.0 Training
T4O
Grouping the modules into functional clusters does nothing to change that reality and
ease software integration
Changing the communication between the modules can ease integration, when the new
‘Publish Subscribe’ approach is used – each module publishes its output w/o regard to
who is receiving it, in contrast to the point-to-point approach of traditional inter-process
communication
It’s about an architecture that can assimilate evolving functionality, rather than remaining set in time
UNCLASSIFIED