PROCESS : SEPARATION ASSURANCE 30/05/2014 Context Introduction - - PowerPoint PPT Presentation

process separation
SMART_READER_LITE
LIVE PREVIEW

PROCESS : SEPARATION ASSURANCE 30/05/2014 Context Introduction - - PowerPoint PPT Presentation

HYBRID MODELING AND AUTOMATION OF AIR TRAFFIC CONTROLLER DECISION PROCESS : SEPARATION ASSURANCE 30/05/2014 Context Introduction Dynamic Modeling of the ATC Process Aircraft Dynamic Model for Flight Management System


slide-1
SLIDE 1

HYBRID MODELING AND AUTOMATION OF AIR TRAFFIC CONTROLLER DECISION PROCESS : SEPARATION ASSURANCE

30/05/2014

slide-2
SLIDE 2

Context

  • Introduction
  • Dynamic Modeling of the ATC Process
  • Aircraft Dynamic
  • Model for Flight Management System
  • Flight Plan
  • Decision Process of ATCO
  • Decision Mechanism of Enroute Controller
  • Decision Mechanism of Approach Controller
  • Hybrid System Modeling of Air Traffic Controller
  • ACC Finite State Automaton
  • APP Finite State Automaton
  • Algorithm for Automated Safety Assurance
  • ACC Algorithm
  • APP Algorithm
  • Implementation and Results
  • Conclusions
  • Future Works
slide-3
SLIDE 3

I. Introduction

slide-4
SLIDE 4

Air Traffic Growth

  • The system is still reliable but air transport goes on to grow.

[Source: ICAO, Airbus]

slide-5
SLIDE 5

Air Traffic Growth From The View of ATCO How do you handle this?

2014 2030

slide-6
SLIDE 6

Human Decision Making

  • Human decision making:
  • complex
  • Innovative

but only for smaller problem size!

slide-7
SLIDE 7

Automation tools for APP and ACC

  • Goal : Automation tools which perform routine separation

provision tasks of controller for two different types of flight modes.

  • Arrival/Departure (APP)
  • En-route (ACC) operations
  • We utilize hybrid automata formalism for both of these flight

modes.

slide-8
SLIDE 8

Air Traffic Management Structure

[Taken from Overview of ATC Systems and Processes , Prof. Hamsa Balakrishnan]

slide-9
SLIDE 9

Our Focus

The main subject of this study:

Detailed model for

  • ne aircraft (> 5 min)

ACC APP

slide-10
SLIDE 10

II. Dynamic Model of the ATC Process

slide-11
SLIDE 11

II. Dynamic Model of the ATC Process

  • We use an aircraft and flight management model to simulate of Air

Traffic Control (ATC) actions.

  • based on Lygeros and Glover’s model [Lygeros,2007]
  • We revise the model in some aspects as seen in figure:
slide-12
SLIDE 12
  • A. Aircraft Dynamic
  • Point Mass Model (PMM)
  • The state variables of the aircraft are:
  • the horizontal position (x1 and x2)
  • altitude (x3)
  • the true airspeed (x4)
  • the heading angle (x5)
  • the mass of the aircraft (x6)
  • The control inputs of the aircraft are:
  • the engine thrust (u1)
  • the bank angle (u2)
  • the flight path angle (u3)

                 

4 5 3 1 4 5 3 2 4 3 3 2 3 4 1 3 6 6 3 4 2 6 1

cos cos sin cos sin sin 2 sin 2

D L

x x u w x x u w x u w C S x x u x g u x x C S x x u x u           

                         

slide-13
SLIDE 13
  • B. Model for Flight Management System
  • The FMS works like a controller.
  • FMS model has 8 discrete modes. These discrete modes are:
  • flight level (FL)
  • way-point index (WP)
  • acceleration mode (AM)
  • climb mode (CM)
  • speed hold mode (SHM)
  • flight phase (FP)
  • reduced power mode (RPM)
  • troposphere mode (TrM)

u = f(x, flight plan, ATC actions)

slide-14
SLIDE 14

Finite State Machines for Flight Manegement System

Finite state machine for AM Finite state machine for FL

These modes are defined relative to BADA for determination of control inputs. Detailed information about these modes can be reached at [Lygeros, 2007]

slide-15
SLIDE 15

FMS Controller

  • FMS controller can be divided into two components:
  • First one is vertical and along track motion control with u1

(thrust) and u3 (flight path angle)

  • The second one is horizontal motion control with u2 (bank angle)
slide-16
SLIDE 16
  • C. Flight Plan
  • We use a flight plan data set which includes sequence of way-

points, in three dimensions.

  • Way-point data come from point profile of ALLFT+ data set [PRISME

Data]

  • ALLFT+ :
slide-17
SLIDE 17

point profile of ALLFT+ data set:

slide-18
SLIDE 18

Progression to FMS Model

  • Flight plan is captured from ALLFT+ data
  • The speed profile is evaluated from BADA model

[Sample for BADA performance file]

slide-19
SLIDE 19

III. Decision Process of ATCO

slide-20
SLIDE 20

III. Decision Process of ATCO

  • We determine the decision process of ATCOs speaking with real air

traffic controllers and convert these processes to hybrid models.

nlatim

Decision Process of Air Traffic Controller [Garcia-Avello, 1997]

slide-21
SLIDE 21

Decision Process of ATCO

  • Decision process of Air Traffic Controller:
  • evaluates information
  • analyses current situation
  • monitors flights
  • estimates routes
  • detects the problem
  • finds solution

Decision Process of Air Traffic Controller [Garcia-Avello, 1997]

slide-22
SLIDE 22
  • A. Decision Mechanism of En Route Controller
  • checks flight levels
  • Controller checks flight routes. If:
  • Controller checks horizontal separation (5 nm) at intersection point and

longitudinal separation (10 nm ) after intersection point. If any separation losses:

  • command direct routing, or
  • altitude change, or
  • delaying motions
  • If:
  • Controller checks horizontal separation (5 nm). If any separation losses:
  • command direct routing, or
  • heading angle change
slide-23
SLIDE 23
  • B. Decision Mechanism of Approach

Controller

  • Controller sequences arrival flights relative to the estimated

arrival time. If any separation losses are estimated between arrival flights:

  • delaying motions
  • If any separation losses are estimated between departure flights:
  • command direct routing, or
  • delaying motions
slide-24
SLIDE 24
  • B. Decision Mechanism of Approach Controller
  • If any separation losses are estimated between departure flight

and arrival flight:

  • command direct routing, or
  • delaying motion, or
  • horizontal motion at a defined altitude

Horizontal motion

slide-25
SLIDE 25

IV. Hybrid System Modeling of Air Traffic Controller

slide-26
SLIDE 26
  • A. ACC Finite State Automaton
  • ACC Finite State Automaton has eight discrete states which

symbolize defined controller actions:

  • q0 is initial state which refer to no action.
  • q1 denotes direct routing for first aircraft
  • q2 denotes altitude change for first flight
  • q3 denote delaying motion for second flight with reducing of speed
  • q4 denote delaying motion for second flight with vector for spacing
  • q5 denotes altitude change for second flight
  • q6 denotes direct routing for both of them
  • q7 denotes bank angle for both of them
slide-27
SLIDE 27
  • A. ACC Finite State Automaton
  • The logic definitions for transition functions and helper functions

are:

 

   

 

   

 

         

1 1 1 2 4 1 2 4 3 2 1 2 4 3 1 2 4 3 1 2 4 3 5 4 1 4 5 5 1 4 2 6 1 4 2 5 7 5 8 1 4 5

, , 1, and

  • r a

a is a not a a is e a a a a a a a a a a a a e a a a a a a a a a e a a a a a a e a a a a e a a a a e a a a a a e a a e a a a a                                                        

slide-28
SLIDE 28

B. APP Finite State Automaton

  • APP Finite State Automaton has seven

discrete states:

  • q0 is initial state which is defined as no

action

  • q1 denotes direct routing for second

flight (departure flight)

  • q2 denotes delaying motion for second

flight which is applied with reducing of speed (ROCD)

  • q3 denotes horizontal motion for

second flight at a defined altitude. In q3, departure flight are climbed to a defined altitude, moved along track and climbed to original route for separation with arrival flight

q3

slide-29
SLIDE 29
  • B. APP Finite State Automaton
  • q4 denotes delaying motion for first flight
  • q5 denote delaying motion for second flight with vector for spacing
  • q6 denote delaying motion for second flight with reducing of speed
slide-30
SLIDE 30
  • B. APP Finite State Automaton
  • The relation between transition functions and helper functions

are:

    

 

  

 

       

1 2 3 2 2 2 3 6 3 1 2 3 4 1 2 5 1 2 3 5 6 5 4 6 4 5 7 7 2 2 3 6 8 1 2 1 2 3 6 9 4 7

, , 1, and

  • r a

a is a not a a is e a a a e a a a a a a e a a a e a a a a a a a a e a e a a a e a a a a a a e a a a a a a e a a                                            

slide-31
SLIDE 31

V. Algorithm for Automated Safety Assurance

slide-32
SLIDE 32

A. ACC Algorithm

ACC Controller Algorithm Flight plans of all enroute flights and current state variables Controller actions and new flight routes of all enroute flights a new aircraft comes to sector Algorithm 1: input :

  • utput :

1 if then 2 Check separation of all flights in sector any unseparated flight exist all unseparated flights in sector flight1 to most old aircraft in unsepareted flights all unseparated flights with flight1 3 if then 4 for to | do 5 Set 6 for to | do flight2 to most close unseparated flight to flight1 controller action from ACC Automata for flight1 and flight2 new flight1 and new flight2routes to new flight routes 7 Set 8 Generate 9 Set

  • The algorithm generalizes ACC Automaton to multi-flight handling

within the sector.

slide-33
SLIDE 33

B. APP Algorithm

  • Sequencing of arrival flights
  • Separating arrival-arrival

conflict with APP Automaton

  • Separating arrival-departure

conflict with APP Automaton

  • Separating departure-

departure conflict with APP Automaton

slide-34
SLIDE 34
  • C. Computational Complexity of Algorithms
  • Algorithms have two parts:
  • conflict detection
  • separation assurance

time_conflict detection number of aircraft x number of way-points

  • f each aircraft

time_separation assurance number of aircrafts which have separation losses x number of way-points of each aircraft which have separation losses

 

slide-35
SLIDE 35

Time of conflict detection

20 40 60 80 100 120 140 2 4 6 8 10 12 14 16 Number of Flights in a Fixed Level Computation Time of Conflict Dedection (s) 6 way-points 10 way-points 14 way-points 18 way-points 10 20 30 40 50 60 0.2 0.4 0.6 0.8 1 1.2 1.4 Number of Flights in arrival Computation Time of Conflict Detection (s) 9 way-points 12 way-points 15 way-points

CD for Enroute CD for Approach

slide-36
SLIDE 36

Time of separation assurance

10 20 30 40 50 60 70 5 10 15 20 25 Number of Flight in a Fixed Level Computation Time of Separation Assurance (s) 5 10 15 20 25 30 35 40 0.5 1 1.5 2 2.5 3 3.5 4 Number of Flight in arrival (number of departures is same) Computational Time of Separation Assurance (s)

SA for Enroute SA for Approach

slide-37
SLIDE 37

VI. Implementations and Results

slide-38
SLIDE 38

A. Implementation for Enroute

  • We used real flight data from 1 March 2011 for implementations.

We use two different sets:

  • First data set includes all flight trajectories between 11:00 - 11:15 in

Istanbul ACC

  • Second data set includes all flight trajectories between 11:00 - 13:00
slide-39
SLIDE 39
  • A. Implementation for Enroute
  • In first set, 18 flights have been seen in 15 minutes within the

sector

  • Two of them have lost separation
  • ACC Controller Algorithm solved this separation lost by giving

vector command to an aircraft

slide-40
SLIDE 40
  • A. Implementation for Enroute
  • In second set, 102 flights have been seen in 120 minutes within

the sector

  • 13 of them have lost separation
  • ACC Controller Algorithm solved these separation lost by

intervening to 7 aircrafts:

  • 2 altitude changes
  • 1 direct routing
  • 1 reducing of speed
  • 3 VFS
slide-41
SLIDE 41

B. Implementation for Approach

  • We used real flight data from 1 March 2011 for implementations.

We use two different sets:

  • First data set includes all flight trajectories between 18:00 - 20:00 for

APP sector which including to Sabiha Gokcen Airport

  • Second data set includes all flight trajectories between 18:00 - 20:00

for APP sector which including to Ataturk Airport

slide-42
SLIDE 42
  • B. Implementation for Approach
  • In first set, 13 flights have been seen in arrival and 19 flights have been

seen in departure between 18:00 - 20:00 for Sabiha Gökçen Airport

  • 2 of arrival flights and 2 of departure flights have lost separation
  • APP Controller Algorithm solved these separation lost by

intervening to 2 aircrafts:

  • speed change for 1 arrival flight
  • VFS for 1 departure flight

Violet ----- departure flight Blue ----- arrival flight Yellow ----- intervened flight

slide-43
SLIDE 43
  • B. Implementation for Approach
  • In second set, 24 flights are appeared in arrival and 31 flights

appear in departure from 18:00 to 20:00. 2 of arrival flights and 6

  • f departure flights will have loss of separation.
  • In second set, 24 flights have been seen in arrival and 31 flights have

been seen in departure between 18:00 - 20:00 for Atatürk Airport

  • 2 of arrival flights and 6 of departure flights have lost separation
slide-44
SLIDE 44
  • B. Implementation for Approach
  • APP Controller Algorithm solved these separation lost by

intervening to 2 aircrafts:

  • speed change for 1 arrival flight
  • reducing of speed for 1 departure flight
  • VFS for 2 departure flight

Violet ----- departure flight Blue ----- arrival flight Yellow ----- intervened flight

slide-45
SLIDE 45

Conclusions

  • We have presented two different hybrid system models for the

decision process of Air Traffic Controller in en route and approach

  • peration.
  • By using these models, we have designed an automation algorithm

for achieving separation assurance.

  • By using real traffic data, we have shown that the algorithm can

detect conflicts and recommend solutions at seconds.

  • The workload of controllers can be reduced with proposed

automation tools and capacity of current system can be enhanced.

slide-46
SLIDE 46

Future Works: Integration to Flight Deck Testbed

slide-47
SLIDE 47

Future Works: Enhancing with flow management

  • Optimization algorithms for flow management
slide-48
SLIDE 48

Thank You !