NAS Infrastructure Management
Symposium
AMHS
Maryann King
Tom Flynn
13 Jun 2006
Copyright © 2006 Raytheon Company. All rights reserved.
The 20 Minute Roadmap to NGATS
(The first Half)
The first step to NGATS is succinctly defining the capability
needs for the stakeholders
Develop the Architecture…. But not too much Architecture!!
– First it is a 2025 thing (we don’t know everything!... This will allow smart
engineers to impress) Raytheon alone has over 40,000.
– See the future, turn around and bridge it to the present… not the other
way around! The technical obstacles that way are openings vs. locked
doors.
– Assume Moore and Metcalf laws (take bandwidth and processing
constraints off the table)
The solutions will be elegant and will solve the problem (not the problems
associated with the problem) and finally…. think grand …. no little thinkers in
world leadership
It is assumed NGATS will be Net-Enable and Service
Oriented based on FAA, JPDO, NASA language
– These assumptions are good, for now, they narrow scope
6/16/2006
Page 2
The NGATS Architecture Linkages
NGATS Capability Needs
Customer Operations’ Top
Objectives and operational
threads (OA)
Goals,
Major Task Objectives
Planning
Logistics
Transportation
Execution
NGATS Key Enabling Parts
Essential Mission Capabilities
• built on COTS/GOTS
• provide enterprise service bus
Infrastructure Service
Categories or
Enterprise Enablers
Command & Control
Mission Systems
Information
Mission Systems
Communications
Mission Systems
NGATS Elements
Correspond to
• Business
• Products
Sensors
Payloads
Command & Control
Platform
Domain or Mission
Specific Products
Communications which interact
6/16/2006
Page 3
The 20 Minute Roadmap to NGATS
(The second half)
NGATS requires the selection of standards (worldwide) i.e.
everything below the middleware
– Above the middleware you can be close but below you have to be “right
on”… i.e. a close security standard is a non-starter
These standards must address the three basic parts of a NetEnable architecture; Information, Communications, and
Command and Control
– Put logistics in the process not on it…now (pay now or pay latter)
Of the three (first among equals is Command and Control)
but establishing the communications network is the first step
to “Net” Centricity for NGATS
If scaled properly this communications architecture will not
only sustain NGATS but new business models as well
6/16/2006
Page 4
NGATS Architecture (next layer down)
Human Machine Interface Hardware
Cut line
Other Functional
Services
Information Client
Comm. Mgt
Service
Sense
Service
Logistics
Service
Information Mgt
Service
Platform
Service
Payload
Service
Other
Functional
Service
Applications
Planning
Service
Human Machine Interface Service
Legacy HMI Adapter
Legacy
Information
Applications
Info App Adapter
Core Information Infrastructure (SecurArchFrmwk, Internet/Infosphere, Database, Security Service)
Application Transport Protocols (IIOP, NTP, SMNP, FTP, DNS, MDP, HTTP, ...)
Network QoS Layer (RSVP…)
Transport Protocols (TCP, UDP, RTP, ...)
High Assurance IP Security
IPv6
Mobility Enhancements
IP Network Applique’
Native IP Mobile
Networks
Legacy Terminal
Equipment
Legacy/
IPv4
Non-IP
Comm
Equipment
OS
Platform/Hardware
6/16/2006
Page 5
The 20 Minute Roadmap to NGATS
(The third half) ☺
Consider all (aircraft and ground) systems now in an
elemental level (strive for interdependence)
– Sensors, Payloads/Passengers, C2, Platform and
Communications
– Then net-enable those legacy systems that can bridge to
the future then fill the gaps with new systems native to the
new architecture
Begin including more stakeholders (they are bill
payers too!)
– Roads, ships, trains, cars, homes, and ?
NGATS----- NGaTS ------- NGTS -------- ?
– US, Europe, Asia…..
This is why NGATS could become the second largest
integration job in the history of mankind!
6/16/2006
Page 6
Maryann King
Director, Advanced Programs
Raytheon Network Centric Systems
Maryann_S_King@raytheon.com
508.490.2877 (Office)
978.257.1419 (Cell)
Tom Flynn
Director
Raytheon Network Centric Systems
Thomas_J_Flynn@raytheon.com
972.344.3606 (Office)
972.670.1334 (Cell)
6/16/2006
Page 7