NEO (NextGen 4D TM) Federal Aviation

Administration
Provided by SWIM’s
Surveillance SOA
(SDN ASP for RNP 4D
Ops)

Presented to: 2007 ICNS Conference

By: Jim Dieudonne, FAA, Chief Engineer Data and
Communications Services
Date: May 3, 2007
Surveillance System for NextGen 4D Ops - Bottom Line

• A Surveillance Service Oriented Architecture (SOA) via SWIM will be

required
• Tighter Separation Standards will be required
• New Tools for the Traffic Management Team (TMT) will be required
– Conformance Monitoring Automation
– Displays
– Surveillance Information - Highly Accurate and Timely from Multi-Sensor
Trackers with inputs from all types of Surveillance Sensors
– Data Links of Aircraft State, Intent, and 4D Trajectories
– Real-Time System Certification
• GOOD NEWS - ALL REQUIRED ELEMENTS HAVE BEEN
DEMONSTRATED, REQUIREMENTS ANALYSIS CONDUCTED, AND
INITIAL NETWORKING AND INTEGRATION HAS YIELDED POSITIVE
RESULTS

2007 ICNS Conference Federal Aviation 2

May 3, 2007 Administration
4D Operations Required Navigation Performance (RNP)

• Over Decades the Aviation Community has defined RNP for many flight
operations
• Improvements in FMS and the use of GPS, WAAS, LAAS, etc. have enabled
very precise navigation
• RTCA has documented these requirements
• Future FMS will contain algorithms to calculate the aircraft’s current Actual
Navigation Performance (ANP)
• DL will be used to transfer this information to TM automation
• RNP for each 4D Operation must be defined
– reduced lateral separation requirements for operations to parallel runways
– merging and spacing
– reduced separations
– time-based ATM
– more efficient use of terminal airspace through dynamic routings
– improved surface traffic management
– high-density en route corridors
– oceanic pair-wise maneuvers, and
– certified sensor monitored airport surface movement

2007 ICNS Conference Federal Aviation 3

May 3, 2007 Administration
Required Surveillance Performance (RSP) for the 4D Ops
RNP

• RSP for 3 nmi and 5 nmi separation standards has been

expressed in an RNP metric of NAC position (see next chart)
– Enroute – NAC position – 5 (RNP-1)
– Terminal – NAC position – 4 (RNP-0.5)
• RSP for future reduced separation
– Terminal, 2 nmi separation requires a NAC position of 6 (RNP-0.3)
• RSP for 4D Ops
– Electronically monitored airport surface movement may required a
NAC position of 11 (LAAS, EPU of less than 3m, VEPU of less than
4m)

2007 ICNS Conference Federal Aviation 4

May 3, 2007 Administration
Comparison of Error Bounds for SWSSR, MSSR,
and Several NACp Values

95% Bound Accuracy (NM) 0.8

0.6

0.4

SWSSR
MSSR
0.2 NAC4x
NAC5x
NAC6x
NAC7x
0
0 50 100 150 200

Range from SSR (NM)

2007 ICNS Conference Federal Aviation 5

May 3, 2007 Administration
SWIM Functional Architecture
Users Users

NAS Application
Application Application System Functions
NAS System NAS System
ServiceInterface
Service Interface
Service Interface Service Interface

Messaging Messaging Interface

Management
Value-Added
SWIM Service Services
Functions Enterprise
Service
Service
Security
Boundary Management
Protection

Secure IP Network Naming &

Connectivity Intrusion Detection Identity & Certificate
Addressing
and Response Management

Information Technology Infrastructure Functions

2007 ICNS Conference Federal Aviation 6

May 3, 2007 Administration
SWIM Physical Architecture Mapped to NAS
Facilities
ESB Server
need not be in SWIM
same facility ESB
as System Server IT Infrastructure:
Adapters • SWIM LAN
equipment:
NAS SWIM • ethernet
Application System SWIM IP Wide Area
switches,
System Adapter Network Connectivity:
• cabling,
• Firewall (as FTI BD1 “Open” with
needed) ED11 Access Control
• IDS sensors List
SWIM
NAS System • DNS servers
Application Adapter
System
FTI Service
NAS Facility Delivery Point
(other NAS
To other NAS
system-specific
facilities
SDPs not shown)

System-specific LAN,
NAS WAN or point-to-point
Application connections
System

Remote NAS Facility

2007 ICNS Conference Federal Aviation 7

May 3, 2007 Administration
Notional SWIM-based Architecture for Weather
Systems

Publish Subscribe
ARTCCs
Product Imagery Product Imagery
System X SA and Encoded Data and Encoded Data ATCSCC

SA System Z
System Y SA
SWIM IP Network
(FTI WAN, Subscribe
Subscribe Facility LANs)
Product Imagery
Product Imagery
and Encoded Data DoD, DHS
and Encoded Data

Publication may be
implemented at either the Subscribe
System Adapters Airlines
or within SWIM Core SWIM NAS
Services Boundary
Registry Protection
Permits outside
SWIM Core Services subscribers with little
SA = System Adapter or no
additional costs

2007 ICNS Conference Federal Aviation 8

May 3, 2007 Administration
 Surveillance Data Network (SDN)
(Diagram provided courtesy of Lincoln Laboratory)
SM: Sensor Manager
Family of Interfaces to Manage Sensors
and Acquire Surveillance Data

SM
SM SM
Modem SM
Modem

Modem Modem
GW GW
ARTS/ HOST/
STARS ERAM
DSTs DSTs
Router Router
SDM: Surveillance Data Manager SDO: Surveillance
SDM SDO Uses Sensor Managers to Acquire, Organize, and SDM SDO
Data Objects
Disseminate Surveillance Data

FTI: FAA Telecommunications Infrastructure

Surface DoD/LEA Users New Decision Support Weather

Automation Tools (DSTs) Processors

2007 ICNS Conference Federal Aviation 9

May 3, 2007 Administration
NEO Project - All Systems Share Information

2007 ICNS Conference Federal Aviation 10

May 3, 2007 Administration
Industry standards achieving interoperability
 NEO Project Connectivity
En Route Terminal Terminal Military situation Civil interdiction and
air traffic control air traffic control air traffic control awareness and response apprehension

Microprocessor En-Route Standard Terminal Common Automated

Battle Control System – Fixed Air Marine Operations Center (DHS)
Automated Radar Automation Replacement Radar Terminal System
(DoD/NORAD)
Tracking System (FAA) System (FAA & DoD) (FAA)

DOD Global Information National Capital FAA System-Wide

Grid Monitoring and defense Information Management

Distributed Information Joint Air Defense Operations

Backbone (DoD) SWIM Testbed (FAA)
Center (DoD)
Real time Wireless Advanced Conformance Multi-Level Security
collaborative tools Connectivity Flight Monitoring Tools

Load Balancer
Content – Aware

rity
Ca
• ACL

ecu
ch
e

ic S
Se

t.
• Firewall

Dis
rv

Bas
er
• IDS

ia
rity ed
cu l M
Appl • DoS

S eigita
icat
ions
• VPN

D
(R EA
CT ) y
er
Deliv
ent
Cont
orks
CloudShield Netw
Label Edge CS -2000
Router (MLS) CA
Fo L E
re A
C a ns &
ptu ic D
re ata
oS
Q
re
cu P

Pe
Se SE

eri
Mg
t.

ng
gm

mt
t

.
N

Billing Mgm
AM
SL
Collaboration Workstation Mobile Devices REACT (NASA) Cloud Shield (COTS)
(Developed for NEO) (FAM PDA)

2007 ICNS Conference Federal Aviation 11

May 3, 2007 Administration
Service Oriented Architecture (SOA) Approach
to NEO 4D Trajectory Management

2007 ICNS Conference Federal Aviation 12

May 3, 2007 Administration
Required Characteristics of the Surveillance SOA
Elements

• System Wide Information Management (SWIM)

• Surveillance Data Network (SDN)
• Sensor Manager/Surveillance Performance Monitor (SM/SPM)
• Multi-Source Tracker (MST)
• Traffic Information Service – Broadcast (TIS-B)
• Kolona Mobile Objects
• Data Link for 4D Operations
• 4D Operations Required Navigation Performance (RNP)
• Required Surveillance Performance (RSP) for the 4D Ops RNP
• Surveillance Community of Interest (COI)

2007 ICNS Conference Federal Aviation 13

May 3, 2007 Administration
 Backup Slides

2007 ICNS Conference Federal Aviation 14

May 3, 2007 Administration
Navigation Integrity Categories (NIC)
Horizontal and Vertical
NIC Containment Bounds
Rc – Radius of
Rc ≥ 37.04 km (20NM) Containment
0
Unknown VPL – Vertical
Protection Limit

1 Rc < 37.04 km (20NM)

2 Rc < 14.816 km (8 NM)

3 Rc < 7.408 km (4 NM)

4 Rc < 3.704 km (2 NM)

5 Rc < 1852 m (1 NM)

6 Rc < 1111.2 m (0.6 NM)

7 Rc < 370.4 m (0.2 NM)

8 Rc < 185.2 m (0.1 NM)

9 Rc < 75 m and VPL < [112 m]

10 Rc < 25 m and VPL < [37.5 m]

11 Rc < 7.5 m and VPL < [11 m]

2007 ICNS Conference Federal Aviation 15

May 3, 2007 Administration
Navigation Accuracy Categories for Position
(NACP)
95% Horizontal and Vertical
NACP Accuracy Bounds (EPU and VEPU) Comment Notes

EPU – Estimated
0 EPU ≥18.52 km (10 NM) Unknown accuracy Position
Uncertainty

1 EPU < 18.52 km (10 NM) RNP-10 accuracy VEPU--

2 EPU < 7.408 km (4 NM) RNP-4 accuracy Vertical

3 EPU < 3.704 km (2 NM) RNP-2 accuracy Position

4 EPU < 1852 m (1NM) RNP-1 accuracy Uncertainty

5 EPU < 926 m (0.5 NM) RNP-0.5 accuracy SA--

6 EPU < 555.6 m ( 0.3 NM) RNP-0.3 accuracy Selective

7 EPU < 185.2 m (0.1 NM) RNP-0.1 accuracy Availability

8 EPU < 92.6 m (0.05 NM) e.g., GPS (with SA)

9 EPU < 30 m and VEPU < 45 m e.g., GPS (SA off)

10 EPU < 10 m and VEPU < 15 m e.g., WAAS

11 EPU < 3 m and VEPU < 4 m e.g., LAAS

2007 ICNS Conference Federal Aviation 16

May 3, 2007 Administration
Navigation Accuracy Categories for Velocity
(NACv)

Horizontal Velocity Vertical Geometric Velocity

NACP Accuracy (95%) Accuracy (95%)

Unknown or ≥ 50 feet
0 Unknown or ≥ 10 m/s
(15.24 m) per second

1 < 10 m/s < 50 feet (15.24 m) per second

2 < 3 m/s < 15 feet (4.57 m) per second

3 < 1 m/s < 5 feet (1.52 m) per second

4 < 0.3 m/s < 1.5 feet (0.46 m) per second

2007 ICNS Conference Federal Aviation 17

May 3, 2007 Administration