0835 - Bond - Keynote Presentation

Air Force Evolution to Open
Avionics
- HPEC 2010 Workshop Robert Bond
16 September 2010
MIT Lincoln Laboratory

Avionics for HPEC 1
16 September 2010
Outline
Open Architecture Vision for the Air Force

Layered architecture
Technologies
Air Force Avionics Architectures
F22 Raptor case study
Architecture evolution
Open Avionics
Key open avionics concepts
Architectures and testbeds
Acquisition in an Open Architecture Context
Leverage and adapt
Open acquisition
Conclusion
Avionics for HPEC 2

16 September 2010
Air Force
Layered Open Systems Architecture (OSA)
Open Sensors
Open Avionics
Net-Centric Systems
VISION:
VISION: Air
Air Force
Force is
is developing
developing an
an integrated
integrated (but
(but loosely
loosely coupled)
coupled) open-systems
open-systems
architectures
spanning
Air
Force
layered
system-of-systems
architectures spanning Air Force layered system-of-systems
Avionics for HPEC 3
16 September 2010
Technology Drivers
- Embedded Systems Embedded System
Airborne Radar
Networked System-of-Systems
Distributed System
Avionics
Ground Station
GIG
Component
Attribute
Throughput
~ 1 TOPS
~ 10 GFLOPS
~1s GFLOPS
> 100 MFLOPS/W
10s MFLOPS/W
< 1 GFLOPS
Form-factor
10 GOPS/W
Data Rate
~500 GB/s
~ 100 GB/s
~ 10GB/s
< 10GB/s
Latency
~ mSecs
~ 100 mSecs
~ secs
> secs
10s MFLOPS/W
Note
Note that
that embedded
embedded military
military systems
systems have
have challenges
challenges that
that set
set them
them apart
apart
from
distributed
and
networked
systems,
but
from distributed and networked systems, but
Avionics for HPEC 4
16 September 2010
Technology Drivers
- System-of-systems Embedded System
Airborne Radar
Distributed System
Avionics
Ground Station
GIG
System
Attribute
Application
Complexity
~10s modes
~100s functions
100s modules
# Components
<10 subsys
10s subsys
100s subsys
redundancy
User select
1000s nodes
Dynamic
topologies,
users,
content/use
databases
databases
web content
(semantic)
Configurability Static (design)
Data
Complexity
arrays
structures
100s Programs
distributed
distributed and
and networked
networked military
military system
system have
have their
their own
own set
set of
of challenges
challenges that
that set
set
them
them apart
apart from
from embedded
embedded systems;
systems; and
and avionics
avionics have
have elements
elements of
of both
both domains.
domains.
Avionics for HPEC 5
16 September 2010
Open Systems Technologies

Embedded System
Airborne Radar
Distributed System
Avionics
Ground Station
GIG
Performance
(Low Latency)
Hardware
Computation
Hardware
VLSI, FPGA, DSP, multicomputers
workstations, servers, clusters
Computation
Middleware
SAL, VSIPL, PVTOL, RT-CORBA
Libraries, CORBA, SOA, NCES
Communication
Hardware
FPDP, VME, Myrinet, RapidIO
Communication
Middleware
SMM, (RT)-MPI, RT-CORBA,DDS
IP based: Infiniband, GigE, WWW
DDS, CORBA, JMS, HTTP, SOAP
Domain
Domain specific
specific technologies
technologies support
support open
open architectures
architectures in
in the
the two
two domains
domains
Avionics for HPEC 6
16 September 2010
SOA = Service Oriented Architecture

OSA = Open System Architecture
generality
Networked SOA
specialization
Embedded OSA
Open Architecture Thrusts

Open Avionics
Open Sensors
Ground
Ground
Station
Station
Open Ground Stations
MCE
MCE
Open Avionics
GIG
Compatible
Networks
CAOC
CAOC
GIG-connected C2ISR users/apps
Users/Apps
Users/Apps
(e.g.
(e.g. Exploitation)
Exploitation)
Sensors
Sensors
Embedded
Embedded OSA
OSA
Avionics
Leverage best of both
Avionics
OSA
OSA and
and SOA
SOA blend
blend
Ground
Ground Stations
Stations
Networked
Networked SOA
SOA
GIG
GIG Users/Apps
Users/Apps
Networked
Networked SOA
SOA
Avionics for HPEC 7
16 September 2010
SOA = Service Oriented Architecture

OSA = Open System Architecture
Outline

Technologies
Open Avionics
Leverage and adapt
Open acquisition
Conclusion
Avionics for HPEC 8

16 September 2010
F-22 Raptor
LO Stealth
Supercruise (the ability to attain
and sustain supersonic speeds
w/o afterburners)
Agility (maneuverability for shootto-kill)
Advanced Avionics (integrated 4pisteradian situation awareness)
Supportability (by means of higher
reliability and 2 level maintenance)
AN/APG-77
Radar
Source: http://www.f-22raptor.com/af_radar.php
Wing Area:
840 sq ft
Engine Thrust Class:
35,000 lb
Level Speed:
921 mph
Total Length:
62.08 ft
Wing Span:
44.5 ft
Horizontal Tail Span:
29ft
Tail Span:
18'10"
Total Height:
16.67ft
Track Width:
10.6ft
Engines:
Pratt & Whitney F-119
Max. Takeoff Weight:
60,000 lb (27,216 kg)
Max. External Stores:
5,000 lb (2,270 kg)
Weight Empty:
31,670 lb (14,365 kg)
Ceiling:
50,000 ft (15,240 m)
G Limit:
9+
The
The F-22
F-22 Raptor
Raptor is
is the
the worlds
worlds pre-eminent
pre-eminent air
air dominance
dominance fighter
fighter
Avionics for HPEC 9
16 September 2010
Source: http://www.f22fighter.com/
F-22 Avionics Architecture

AN/APG-77 RADAR
8-12.5 GHz
Active ESA
10W TR modules
Low Observability
ECCM
LPI modes
Highly
Highly sophisticated
sophisticated integrated
integrated avionics
avionics system
system architecture
architecture
Source: Military Avionics Systems, I. Moir and A. Seabridge

2006 John Wiley & Sons, Ltd

Avionics for HPEC 10
16 September 2010

AN/APG-77 RADAR
8-12.5 GHz
Active ESA
10W TR modules
Low Observability
ECCM
LPI modes
Highly
integrated avionics
avionics system
system architecture
architecture


16 September 2010

AN/APG-77 RADAR
8-12.5 GHz
Active ESA
10W TR modules
Low Observability
ECCM
LPI modes
Highly
integrated avionics
avionics system
system architecture
architecture


16 September 2010
F-22 Acquisition
Request for proposals
1985
1981
Requirements issued
Jul 1986
Design Submitted
Program Start
Oct 86
First flight,
preproduction
Sep 97
First flight,
production
Sep 03
Aug 01
Production go-ahead
Sep 1990
First Flight
Worlds
most
expensive
FOC
Dec 07
Dec 05
IOC
Jul 09
Production capped
at 187 Aircraft
Worlds
best
Cost
Cost needs
needs to
to be
be balanced
balanced with
with war
war fighting
fighting capability
capability
Acquisition,
maintenance,
and
upgrades
Acquisition, maintenance, and upgrades need
need to
to be
be cost
cost
competitive
competitive AND
AND timely
timely AND
AND high
high quality
quality
Open
Open avionics
avionics architecture
architecture are
are aa fundamental
fundamental enabler!
enabler!
Sources:
1. Jane's All the World's Aircraft
2. Defense Aerospace.com; Measuring the Real Cost of Modern Fighter Aircraft
16 September 2010
F-22 Supply-Chain Vendors

Source: Ending F-22A production: costs and industrial base implications of
alternative options / Obaid Younosss [et al]
Avionics
Avionics supplied
supplied by
by aa small
small set
set of
of vendors
vendors but
but are
are the
the major
major cost
cost
component
component in
in aa modern
modern fighter
fighter aircraft.
aircraft.
16 September 2010
Growth in Operational Flight Program (OFP)

Complexity
OFP Memory Utilization: K 16 bit words
Aging Avionics in Military Aircraft

http://www.nap.edu/catalog/10108.html
F-35
(estimated)
106
F-22
105
Estimated 1.7M SLOC OFP

90% ADA
104
F-15E
103
F-15A
102
F-16A
F-111A
10
F-106
1
1955
1965
1975
1985
1995
2005
Year
Modern
Modern software
software architectures,
architectures, technologies,
technologies, and
and practices
practices are
are crucial
crucial as
as the
the
complexity
complexity of
of military
military aircraft
aircraft software
software systems
systems continues
continues to
to grow
grow exponentially
exponentially
16 September 2010
Outline

Technologies
Open Avionics and Ground Segments
Leverage and adapt
Open acquisition
Conclusion

16 September 2010
Early Avionics Architectures

Distributed Analog Architecture
Circa 1960s
Distributed Digital Architecture

Circa 1970s
F-4 Phantom
F-14A Tomcat
Federated Digital Architecture

Circa 1980s
F/A-18 Hornet


16 September 2010
Current Operational Systems

1970s to 1990s
Radar
Cockpit Displays
EO / IR
Weapons
Integrated
Aircraft
System
Computer
Flight Controls &

Flight
Management
Recording
Communications

16 September 2010

AN/APG-77 RADAR
8-12.5 GHz
Active ESA
10W TR modules
Low Observability
ECCM
LPI modes
Highly
sophisticated capability
capability based
based on
on
integrated
integrated avionics
avionics system
system architecture
architecture

16 September 2010
Evolving
1990s to 200X
Radar
Cockpit Displays
EO / IR
Weapons
Payload
Management Unit
Integrated
Aircraft
System
Computer
Flight Controls &

Flight
Management
Recording
Communications

16 September 2010
PAVE PACE Avionics Architecture
Extension
Extension of
of F22
F22 integrated
integrated avionics
avionics system
system architecture
architecture
Integrates
Integrates RF
RF sensing
sensing // management
management
Unified
Unified avionics
avionics digital
digital network
network based
based on
on commercial
commercial technologies
technologies

16 September 2010
Open Architecture
201X - future
Radar
EO / IR
Weapons
Processor
Cockpit Displays
Processor
Flight Controls &

Flight
Management
Processor
Recording
Processor
Communications
Processor
Processor
Processor
Server

16 September 2010
Outline

Technologies
Open Avionics
Leverage and adapt
Open acquisition
Conclusion

16 September 2010
Open Avionics
- Key Technologies -
Concept
Composable Open Reference Architectures
Plug-and-Play Hardware Infrastructure
Service-oriented Subsystems
Service-oriented Middleware
Service and Client Factorization
Avionics Metadata

16 September 2010
Open Avionics Architecture Elements

- Reference Functional Architecture -
Open Reference Architectures

Plug-and-Play Hardware
Service & Client Factorization
Avionics Metadata
Radar
Radar
AMRAAM
AMRAAM
System
System
Mission
Mission
Computer
Computer
E
Interface Control Documents

(ICD) define
data items and messages
protocols observed
timing & event sequences
EW
EW
Display
Display
Subsystem
Subsystem
Mass Storage
Mass Storage
F
CNI
CNI
I
Network
Network
Adapter/
Adapter/
DataLink
DataLink
To/from GIG
(virtual Ground Station)

16 September 2010

- Standard Plug and Play Hardware -

Avionics Metadata
Radar
Radar
A
AMRAAM
AMRAAM
System
System
EWS
EWS
Switched fabric
Mil Std 1394B

(or Mil Std 1553)
Mission
Mission
Computer
Computer
E
ATR
Chassis
Display
Display
Subsystem
Subsystem
Mass Storage
Mass Storage
F
CNI
CNI
I
Network
Network
Adapter/
Adapter/
DataLink
DataLink
Self-describing components
for self-organization (crucial
for composable architecture).
To/from GIG
SEM-E Module
16 September 2010

- Service Oriented Subsystem Interfaces -

Reference
Reference Interfaces
Interfaces
Executable
Executable Service
Service Interfaces
Interfaces
Avionics Metadata
Radar
Radar
A
A
Mission
Mission
Computer
Computer
EE
AMRAAM
AMRAAM
System
System
EWS
EWS
DD
C
C
Display
Display
Subsystem
Subsystem
Mass Storage
Mass Storage
F
F
G
G
CNI
CNI
H
H
II
Avionics
Avionics performance
performance
constraints
require
constraints require domaindomainspecific
specific service
service // client
client
technologies
technologies
Network
Network
Adapter/
Adapter/
DataLink
DataLink
JJ
To/from GIG

16 September 2010

- Middleware -

SOA
SOA middleware
middleware is:
is:
1.
Communication
1. Communication middleware
middleware
(e.g.
(e.g. DDS
DDS pub/sub)
pub/sub)
2.
2.Registry/Broker
Registry/Broker
3.
3.Interface
Interface description
description language
language
Common services
services
4.4.Common
Avioincs Metadata
Radar
Radar
AMRAAM
AMRAAM
System
System
EWS
EWS
DD
C
C
A
A
Avionics SOA Middleware
Mission
Mission
Computer
Computer
EE
Display
Display
Subsystem
Subsystem
Mass Storage
Mass Storage
F
F
G
G
CNI
CNI
H
H
II
SOA
SOA middleware
middleware supports:
supports:
1.
1.Position
Position independent
independent services
services
and
clients
and clients
2.
2.Real-time
Real-time communication
communication**

16 September 2010
Network
Network
Adapter/
Adapter/
DataLink
DataLink
JJ
To/from GIG
* Domain optimized (not SOAP; maybe DDS)

- Service/Client Decomposition -

1.
1.Define
Define standard
standard behavior
behavior of
of
subsystem
subsystem services
services
2.
Subsystem
implementations
2. Subsystem implementations
hidden
hidden from
from outside
outside world
world
1.
1. Wrapper
Wrapper for
for legacy
legacy systems
systems
2.
2. Embedded
Embedded OSA
OSA details
details hidden
hidden
Avionics Metadata
Radar
Radar
A
A
AMRAAM
AMRAAM
System
System
EWS
EWS
DD
C
C
Mission
Mission
Computer
Computer
Display
Display
Subsystem
Subsystem
Mass Storage
Mass Storage
EE
Mission
Mission Computer
Computer Software
Software
1.Factored
1.Factored into
into services
services and
and clients
clients
2.Services
2.Services mappable
mappable anywhere
anywhere in
in
system
system
3.Service
3.Service internals
internals are
are legacy
legacy codes
codes
of
of new
new variants
variants
F
F
G
G
CNI
CNI
H
H
I
Network
Network
Adapter/
Adapter/
DataLink
DataLink
JJ
To/from GIG

16 September 2010

- Metadata Definition -

1.
1.Metadata
Metadata specifications
specifications describe
describe
1.
1. Message
Message contents
contents
2.
Data
products
2. Data products
3.
3. Avionics
Avionics system
system configuration
configuration
Avionics Metadata
Radar
Radar
AMRAAM
AMRAAM
System
System
EWS
EWS
DD
C
C
A
A
Mission
Mission
Computer
Computer
EE
Avionics
Avionics Metadata
Metadata Stores
Stores
Physical
Physical configuration/status
configuration/status
descriptions
descriptions
Metadata
Metadata catalogs
catalogs for
for all
all data
data
product
product stores
stores
Display
Display
Subsystem
Subsystem
Mass Storage
Mass Storage
F
F
G
G
CNI
CNI
H
H
I
Network
Network
Adapter/
Adapter/
DataLink
DataLink
JJ
To/from GIG

16 September 2010
Open Architecture Testbed

- OA Testing Service Nodes
Shared
network
storage
Radar
Environment
Simulation
AMRAAM
System
EWS
DD
C
C
A
A

resource
manager
Mission
Computer
Mass Storage
EE
F
F
Display
Subsystem
G
G
CNI
H
H
Web Server
I
I
Network
Adapter/
DataLink
To LAN
Control and Display

Simulate subsystem interfaces
Uses open avionics standards
Key:
Simulation
Actual
Cluster
Cluster

16 September 2010

- OA Testing Service Nodes
Shared
network
storage
Environment
Simulations
Radar
AMRAAM
System
EWS
DD
C
C
A
A
AMRAAM
resource
manager
Radar
Environment
Simulation
EWS
Mission
Computer
Mass Storage
Web Server
Display
Subsystem
CNI
To LAN
Network
Adapter
Mission
Computer
Mass Storage
EE
F
F
Display
Subsystem
G
G
CNI
H
H
I
Network
Adapter/
DataLink
Control and Display
Control/
Display
Simulate subsystem interfaces

Uses open avionics standards
Key:
Simulation
Actual
Cluster
Cluster

16 September 2010

- Operational Code Development Service Nodes
Shared
network
storage
Environment
Simulations
Radar
EWS
DD
EWS
Mission
Computer
Mass Storage
Web Server
Display
Subsystem
CNI
To LAN
Network
Adapter
Control/
Display
Key:
AMRAAM
System
C
C
A
A
AMRAAM
resource
manager
Radar
Environment
Simulation
Simulation
Actual
Mission
Computer
Mass Storage
EE
F
F
Display
Subsystem
G
G
CNI
H
H
I
Network
Adapter/
DataLink
Control and Display

Factor Mission Computer Operation Flight Program
(OFP) into Services and Clients
Develop new OFP software
Test interface compliance
Cluster
Cluster

16 September 2010

- Selective Build Out Service Nodes
Shared
network
storage
Radar I/Fs
Radar Sim
Environment
Simulations
Bus Interfaces
Radar Sim
AMRAAM
System
Radar
EWS
DD
C
C
A
A
AMRAAM
resource
manager
Environment
Simulation
EWS
Bus Interfaces
Mass Storage
Web Server
Display
Subsystem
CNI
To LAN
Network
Adapter
Mission
Computer
Mass Storage
EE
F
F
Display
Subsystem
G
G
CNI
H
H
I
Network
Adapter/
DataLink
Control and Display
Control/
Display
Key:
Simulation
Actual
Cluster
Cluster

16 September 2010
Outline

Technologies
Open Avionics
Leverage and adapt
Open acquisition
Conclusion

16 September 2010
Historical Approach
Down select based on study, not demonstrated performance
Government
Government
PO
PO
No competitive incentive after prime contractor down select

Business model locks prime / sub for life of program
Prime
Prime
Contractor
Contractor
Government passes subsystem performance responsibility to prime

All interfaces proprietary to prime / sub
Business model locks improvements to initial prime / sub relationship
Expensive upgrades captive to prime subsystem contractors
Proposal
Proposal
A
A
Lack of competition deters contractor risk reduction / enhancement investment
Paper
Paper Down
Down
Select
Select
Proposal
Proposal
B
B
Prime
conducts
downselect
Prime
Prime
Production
Production
Decision
Decision
Single
Single Design
Design
Prime
Prime//Sub
Sub
System
System
Changes
Changes
Ops
OpsTest
Test
and
andOps
Ops
PDR
PDR
Upgrades
Upgrades
Flight
Flight
Test
Test
CDR
CDR
De-Mil
De-Mil

16 September 2010
Open Systems Support

Leverage Adapt Strategy
Design freeze
Deployment
10,000
s
e
r
oo
M
Processing Power
1000
100
Leverage & adapt
w
La
Technology
Refresh
COTS with
portable software
Custom Hardware
10
Freeze & build
10
15
Good for rapidly changing technology

Good for rapidly changing requirements
Built-in refresh and improvements
More difficult to manage
Freezes technology and builds to fixed design

Acceptable for slow moving technologies
Requires stable requirements throughout lifecycle
Easier to manage with current acquisition strategy
Years
Open
Open Systems
Systems support
support leverage
leverage and
and adapt
adapt strategy;
strategy; allows
allows DoD
DoD to
to leverage
leverage
commercial
industrys
investment
commercial industrys investment
Continuous
Continuous upgrade/refresh
upgrade/refresh possible
possible to
to meet
meet evolving
evolving threats
threats and
and obsolescence
obsolescence
16 September 2010
37
Need for Competitive Procurement

- E.G. F-22 Industrial Base Source: Ending F-22A production: costs and industrial base implications of
alternative options / Obaid Younosss [et al]
1. Competition
restricted to less
complex items
2. Little IP
competition
Need
Need to
to change
change competitive
competitive posture
posture of
of military
military aircraft
aircraft industrial
industrial base:
base:
Competitive
Competitive procurement
procurement and
and upgrade
upgrade of
of components
components with
with high
high
Intellectual
Property
content.
Intellectual Property content.
16 September 2010
Open Architecture Approach

Down select based on demonstrated performance (fly before buy)
Government
Government
PO
PO
Avionics
Avionics
Prime
Prime
Contractor
Contractor
Avionics
Avionics
Prime
Prime
Contractor
Contractor
Competitive incentive through flight test and production decision

Business model keeps competitive second source for life of program
Government maintains responsibility for subsystem until directed sub-integration
All interfaces collaboratively designed, verified and published
Business model support competitive spiral improvements
Less Expensive competitive upgrades independent of prime
Proposal
Proposal
B
B
Proposal
Proposal
A
A
Competition inspires contractor risk reduction / enhancement investment
Design
Design A
A
PDR
PDR
CDR
CDR
Flight
Flight
Test
Test
ICD Development and Verification Process

Design
Design B
B
Performance
Performance
Down
Down Select
Select
Govt
Govt
Downselect
Downselect
Product
Product
Decision
Decision
Directed
Directed
Integration
Integration
((Sub
Sub))
PDR
PDR
System
System
Change
Change
CDR
CDR
Ops
Ops
Test
Test &
&
Ops
Ops
Best-ofBest-ofbreed
breed
Flight
Flight
Test
Test
Upgrades
Upgrades
De-Mil
De-Mil

16 September 2010
Outline

Technologies
Open Avionics
Leverage and adapt
Open acquisition
Conclusion

16 September 2010
Conclusion
The Air Force is pursuing a layered open-architecture

vision to improve system (of systems) capabilities in a cost
effective and rapid manner.
Open avionics are crucial to enabling the competitive, cost
effective, and timely introduction of new war-fighting
capabilities in platforms that will persist for decades.
Service oriented concepts judiciously combined with
embedded open system techniques will deliver the next
generation of open avionics technologies and
architectures.
Open architecture test beds based on executable
specifications will accelerate avioincs integration and
provide the mechanism to compete new avionics
technologies.

16 September 2010

0835 - Bond - Keynote Presentation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

0835 - Bond - Keynote Presentation

Uploaded by

Copyright:

Available Formats

Air Force Evolution to Open

MIT Lincoln Laboratory

Open Architecture Vision for the Air Force

Avionics for HPEC 2

> 100 MFLOPS/W

Configurability Static (design)

Open Systems Technologies

VLSI, FPGA, DSP, multicomputers

workstations, servers, clusters

SAL, VSIPL, PVTOL, RT-CORBA

Libraries, CORBA, SOA, NCES

FPDP, VME, Myrinet, RapidIO

SMM, (RT)-MPI, RT-CORBA,DDS

IP based: Infiniband, GigE, WWW

DDS, CORBA, JMS, HTTP, SOAP

SOA = Service Oriented Architecture

MIT Lincoln Laboratory

Open Architecture Thrusts

Open Ground Stations

GIG-connected C2ISR users/apps

SOA = Service Oriented Architecture

MIT Lincoln Laboratory

Open Architecture Vision for the Air Force

Avionics for HPEC 8

Engine Thrust Class:

Horizontal Tail Span:

Pratt & Whitney F-119

Max. Takeoff Weight:

60,000 lb (27,216 kg)

Max. External Stores:

5,000 lb (2,270 kg)

31,670 lb (14,365 kg)

F-22 Avionics Architecture

Source: Military Avionics Systems, I. Moir and A. Seabridge

MIT Lincoln Laboratory

F-22 Avionics Architecture

Source: Military Avionics Systems, I. Moir and A. Seabridge

MIT Lincoln Laboratory

F-22 Avionics Architecture

Source: Military Avionics Systems, I. Moir and A. Seabridge

MIT Lincoln Laboratory

MIT Lincoln Laboratory

F-22 Supply-Chain Vendors

Growth in Operational Flight Program (OFP)

OFP Memory Utilization: K 16 bit words

Aging Avionics in Military Aircraft

Estimated 1.7M SLOC OFP

Open Architecture Vision for the Air Force

Avionics for HPEC 16

Early Avionics Architectures

Distributed Digital Architecture

Federated Digital Architecture

Source: Military Avionics Systems, I. Moir and A. Seabridge

MIT Lincoln Laboratory

Current Operational Systems

Flight Controls &

MIT Lincoln Laboratory

F-22 Avionics Architecture

MIT Lincoln Laboratory

Flight Controls &

MIT Lincoln Laboratory

PAVE PACE Avionics Architecture

Avionics for HPEC 21