Tower CTSD

Document Sample
Tower CTSD Powered By Docstoc
					                                                              f7919ee3-d7fb-4de6-9213-
                                                                     1719658e70fc.doc

                                                                                 Page : i

                                                                                                      EUROCONTROL




                                  EUROCONTROL EXPERIMENTAL CENTRE
                                        Brétigny-sur-Orge, FRANCE




                                                                 eDEP
                                                Technical Document
                                     Tower Component Test Scripts

                 Document Ref: TEC/<Activity/<No>/<Release><Draft>/<Author>
                                Issue date: 17 September 2007




         <Preface>




 The information contained in this document is the property of the EUROCONTROL Agency and no part should be reproduced in any form without the
                                                                  Agency’s permission.
                            The views expressed herein do not necessarily reflect the official views or policy of the Agency.




STATUS                                                                                                                                  TITLE
Company Ref.                                                                                                         Template : Normal.dotm
                                          f7919ee3-d7fb-4de6-9213-
                                                 1719658e70fc.doc

                                                        Page : ii

                                                                       EUROCONTROL




                                     Document Change Log
Rel.     Author   Date of the release   Description of the release        Modifications (sections
                                                                           affected and relevant
                                                                                information)
1.0    Graffica   30 July 2004        Created Document
2.0    Graffica   30 July 2004        Issued to EEC
3.0    Graffica   10 Dec 2004         Issued to EEC                  Added TCS, TCWP, TFM,
                                                                     TFPM and uTCWP sections
4.0    Graffica   7 Jan 2005          Post iteration 2 delivery      Response to EEC comments
5.0    Graffica   14 April 2005       2005 Quarter 1 delivery        Modify taxipoint delay points.
                                                                     Remove observation column.
6.0    Graffica   06 June 2005        Tower05 Activation 1 Tasks     10.3 TCWP Symbols
                                                                     10.4 TCWP Air/Grd/Hybrid
                                                                     12 TSN Component Tests
                                                                     13 TAAM Traffic Converter
7.0    Graffica   1 July 2005         Modifications after 27/06/05 12 TSN Component tests.
                                      meeting at EEC.
8.0    Graffica   14 Feb 2006         Modifications after APT tasks 5 TPM
                                      2005                           6 TCS
                                                                     10 TCWP
9.0    Graffica   22 Mar 2006         2006 Q1 delivery modifications 3 Automated tests
10.0   Graffica   21 Jun 2006         2006 Q2 delivery modifications 6 and onwards. Mainly
                                                                     GroundUnit          functionality
                                                                     moved to callsign field.
11.0   Graffica   30 Oct 2006         PRF482 m/s to Knots.           Throughout for correction of
                                      WP5.3 Tower Pilot.             m/s to knots.
                                                                     Sections 5.8 Pilot functions.
                                                                     Section 10 renamed to
                                                                     Graphical Components and
                                                                     now encompasses TCWP,
                                                                     TPWP and TCWP(Hybrid).
12     Graffica   21 Dec 2006                                        Added Route editor tests to
                                                                     section 10.3.4.
13     Graffica   22 Mar 2007                                        Added manoeuvre prompts to
                                                                     label tests, and orders section
                                                                     for speed, stop-ahead and
                                                                     conditional orders to TPWP
                                                                     section 10.2.
                  22 Mar 2007                                        4.3.3, 4.4.3, 5.1.4 Replace
                                                                     references to the airport
                                                                     arrival     flight  plan    flag
                                                                     ALLOW_FAST_RUNWAY_E
                                                                     XIT,
                                                                     5.1.6 insert tests for new
                                                                     runway fast exit requirements.
                  10 Apr 2007                                        Updated stop-slow-go (5.4.1)
                                                                     test to include reaction times.
                  11 Apr 2007                                        TCS section updated for new
                                                                     label and arrival/departure list
                                                                     formats
                  20 Apr 2007         2007 Q1 delivery modifications Changes thoughout for work
                                                                     packages WPE5.3d and
                                                                     WPE6.2


STATUS                                                                                           TITLE
Company Ref.                                                                      Template : Normal.dotm
                                       f7919ee3-d7fb-4de6-9213-
                                              1719658e70fc.doc

                                                    Page : iii

                                                                      EUROCONTROL




14     Graffica   12 June 2007      Updated TPWP Label Test           Section 10.2.1.1.
                  22 May 2007                                         Additional TFPM test added –
                                                                      CT_TFPM_02
                  18 June 2007                                        10.2.6, 10.2.7 - Added freq.
                                                                      tests for TPWP / PWP
                                                                      interactions.
                                                                      13 - Go Around tests.
                   nd
                  2 July 2007       Acceleration / deceleration,      5 - General update to tests
                                    queuing      and       junction   5.1 - update to runway fast
                                    congestion radius changes.        exit test.
                                                                      5.7 - addition of GMS accel.
                                                                      test.
                    th
                  17 July 2007      Added Runway SID Menu test        10.1.3.2 – TCWP test
                                    cases for TCWP and TPWP.          10.2.4.2 – TPWP test
                    th
                  20 July 2007      Updated STP references            Throughout
                    th
15.0   Graffica   14 Aug 2007       Version number change to          N/A
       (Thom)                       common Graffica standard
                   th
                  4 Sept 2007       Added TSN clearance alert         12.4 – TSN Clearance alerts
                                    tests
                    th
                  11 Sept 2007      Q2 Testing                        Minor updates for testing
                    th
16.0              11 Sept 2007      2007 Q2 Delivery
                    th
       Graffica   25 Sept 2007      Updated       following    TCR    12.4 – TSN Clearance alerts
       (Cooper)                     comments on Alert Checks and
                                    Route Clearance tasks.
                    th
       Graffica   16 Oct 2007       Added                             12.4 – TSN Clearance alerts
       (Martin)                     CT_TSN_CLEARANCE_08
                    th
       Graffica   18 Oct. 2007      Deviation alert test added        12.5 – TSN Devaition Alerts
                    th
       Graffica   19 Oct 2007       Added                             12.4 – TSN Clearance Alerts
       (Martin)                     CT_TSN_CLEARANCE_09/10
                    th
       Graffica   20 Oct 2007       Minor Updates                     12.4 – TSN Clearance Alerts
       (Martin)
                    rd
       Graffica   23 Oct 2007       Added                             12.4 – TSN Clearance Alerts
       (Martin)                     CT_TSN_CLEARANCE_11
                    th
       Graffica   07 Nov 2007       Added                             12.4 – TSN Clearance Alerts
       (Martin)                     CT_TSN_CLEARANCE_12
                    th
       Graffica   15 Nov 2007       Added                             12.4 – TSN Clearance Alerts
       (Martin)                     CT_TSN_CLEARANCE_13
                        nd
       Graffica   22 Nov 2007       Updated CT_TIFPL_001              4.3 - TIFPL
       (Martin)
                   th
       Graffica   6 December 2007   2007 Q4 delivery modifications    Minor changes throughout
       (Martin)
                    th
       Graffica   14 December 2007 Updated                            12.4 – TSN Clearance Alerts
       (Martin)                    CT_TSN_CLEARANCE_01/04/            Airborne DEPs no longer
                                   05/07/09/10/12                     trigger alerts.
                    th
17     Graffica   14 December 2007 Added                              12.4 – TSN Clearance Alerts
       (Martin)                    CT_TSN_CLEARANCE_14
                    th
       Graffica   29 January 2008  Added                              12.4 – TSN Clearance Alerts
       (Martin)                    CT_TSN_CLEARANCE_15
                    th
       Graffica   04 February 2008 Added                              12.4 – TSN Clearance Alerts
       (Martin)                    CT_TSN_CLEARANCE_16
                    th
       Graffica   06 February 2008 Added                              12.4 – TSN Clearance Alerts
       (Martin)                    CT_TSN_CLEARANCE_17
                    th
       Graffica   15 February 2008 Updated clearance alerts.          12.4 – TSN Clearance Alerts
       (Martin)
STATUS                                                                                             TITLE
Company Ref.                                                                        Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                          Page : iv

                                                                        EUROCONTROL


                          th
         Graffica     14 March 2008      Remove TPM to TFPM “cheat”     9 TFPM Component tests.
         (Eveleigh)                      interface.
                          st
         Graffica     31 March 2008      Add cross reference between    Section 18 replaced, and
         (Fletcher)                      SRD requirements and test      requirement field added to
                                         scenarios.                     each test.
                          rd
         Graffica     23 April 2008      Minor updates throughout for   Throughout.
                                         8.1 delivery testing.

                                Acceptance and Reviewing Procedures
               Name (s)                    Date of acceptance/ review              Date of approval



                                       Document distribution
 to/cc                         Name                                         Role




STATUS                                                                                             TITLE
Company Ref.                                                                        Template : Normal.dotm
                                                                         f7919ee3-d7fb-4de6-9213-
                                                                                1719658e70fc.doc

                                                                                             Page : v

                                                                                                                      EUROCONTROL




                                 TABLE OF CONTENTS

TABLE OF CONTENTS .................................................................................................................................... V

1      INTRODUCTION ........................................................................................................................................ 1
1.1     Purpose................................................................................................................................................... 1
1.2     Intended audience .................................................................................................................................. 1
1.3     Responsibilities ....................................................................................................................................... 1
1.4     Associated documentation...................................................................................................................... 1
   1.4.1     Internal project documentation ....................................................................................................... 1
   1.4.2     General documentation .................................................................................................................. 1
1.5     Glossary & Abbreviations ....................................................................................................................... 1
1.6     Colour Definitions ................................................................................................................................... 2
   1.6.1     Flight Labels.................................................................................................................................... 2
2      TEST SCENARIO ....................................................................................................................................... 2
2.1     Intended purpose .................................................................................................................................... 2
2.2     Airspace .................................................................................................................................................. 2
   2.2.1     R27X Airspace ................................................................................................................................ 3
   2.2.2     LFPG (TAAM) Airport ..................................................................................................................... 3
   2.2.3     French Airspace .............................................................................................................................. 4
3      AUTOMATED TEST SCRIPTS .................................................................................................................. 7
3.1        Introduction ............................................................................................................................................. 7
3.2        Running the Automated Test Scripts ...................................................................................................... 7
4      AUTOMATED COMPONENT TESTS ........................................................................................................ 8
4.1     TACR ...................................................................................................................................................... 8
   4.1.1    Running the TACR Test .................................................................................................................. 8
   4.1.2    Tests Performed ............................................................................................................................. 8
4.2     TASP....................................................................................................................................................... 9
   4.2.1    Running the TASP Test .................................................................................................................. 9
   4.2.2    Tests Performed ............................................................................................................................. 9
     4.2.2.1 TestCounts.................................................................................................................................. 9
     4.2.2.2 TestTaxiwayHierarchy ................................................................................................................ 9
     4.2.2.3 TestRunwayEntryExitPoints ....................................................................................................... 9
     4.2.2.4 TestDistances ............................................................................................................................. 9
     4.2.2.5 TestRunwayPerimeter ..............................................................................................................10
     4.2.2.6 TestStatusData .........................................................................................................................10
     4.2.2.7 TestGroundSectors ...................................................................................................................11
     4.2.2.8 TestAirportElevation .................................................................................................................11
     4.2.2.9 TestPushback ...........................................................................................................................11
     4.2.2.10      TestExclusionAreas ..............................................................................................................11
4.3     TIFPL ....................................................................................................................................................12
   4.3.1    Running the TIFPL ........................................................................................................................12
   4.3.2    Response Key...............................................................................................................................12
   4.3.3    TIFPL Testset Details ...................................................................................................................12
4.4     DNS ......................................................................................................................................................15
   4.4.1    Running the DNS Test ..................................................................................................................15
   4.4.2    Response Key...............................................................................................................................15
   4.4.3    DNS Testset Details .....................................................................................................................15
5      TPM COMPONENT TESTS .....................................................................................................................21

STATUS                                                                                                                                                       TITLE
Company Ref.                                                                                                                            Template : Normal.dotm
                                                                        f7919ee3-d7fb-4de6-9213-
                                                                               1719658e70fc.doc

                                                                                            Page : 6

                                                                                                                     EUROCONTROL



5.1     Arrivals ..................................................................................................................................................21
   5.1.1      CT_TPM_ARR_01 – Standard Arrival Test ..................................................................................21
   5.1.2      CT_TPM_ARR_02 – Specified Exit Arrival Test ...........................................................................21
   5.1.3      CT_TPM_ARR_03 – Failed Deceleration Arrival Test .................................................................22
   5.1.4      CT_TPM_ARR_04 – Arrival Fast Runway Exit Test ....................................................................23
   5.1.5      CT_TPM_ARR_05 – Arrival No Route Test .................................................................................23
   5.1.6      CT_TPM_ARRXASAP_01 – Arrivals Leave Runway By First Available Exit Point. ....................24
   5.1.7      CT_TPM_ARRXASAP_02 – Arrival Fast Runway Exits. .............................................................25
   5.1.8      CT_TPM_ARRXASAP_03 – Arrival Fast Runway Exits With Tolerance. ....................................26
5.2     Departures ............................................................................................................................................27
   5.2.1      CT_TPM_DEP_01 – Standard Departure Test ............................................................................27
   5.2.2      CT_TPM_DEP_02 – Specified Runway Entry Departure Test ....................................................28
   5.2.3      CT_TPM_DEP_03 – Failed Acceleration Departure Test ............................................................28
   5.2.4      CT_TPM_DEP_04 – Departure No Route Test ............................................................................29
5.3     Traffic Rules ..........................................................................................................................................29
   5.3.1      CT_TPM_TRA_01 – Speed Test ..................................................................................................29
   5.3.2      CT_TPM_TRA_02 – Priority Test .................................................................................................30
   5.3.3      CT_TPM_TRA_03 – Vehicle Test ................................................................................................31
   5.3.4      CT_TPM_TRA_04 – Flight Plan Speed GMS ..............................................................................32
5.4     Queuing Tests ......................................................................................................................................32
   5.4.1      CT_TPM_QUE_01 – Stopped Traffic Test ...................................................................................32
   5.4.2      CT_TPM_QUE_02 – Slowed Traffic Test .....................................................................................33
5.5     Give Way Tests ....................................................................................................................................34
   5.5.1      CT_TPM_GIV_01 – Give way to right test ...................................................................................34
   5.5.2      CT_TPM_GIV_02 – Give way to departures test .........................................................................34
   5.5.3      CT_TPM_GIV_03 – Give way to aircraft test ...............................................................................35
5.6     Traffic Resources ..................................................................................................................................35
   5.6.1      CT_TPM_RES_01 – Crossing Time Factor Test .........................................................................35
   5.6.2      CT_TPM_RES_02 – Occupancy Time Test .................................................................................36
   5.6.3      CT_TPM_RES_03 – Junction Congestion Distance Test ............................................................37
5.7     GMS ......................................................................................................................................................38
   5.7.1      CT_TPM_GMS_01 – Pluggable GMS ..........................................................................................38
   5.7.2      CT_TPM_GMS_02 – Acceleration and Deceleration ...................................................................39
5.8     PM Piloted Flights .................................................................................................................................40
   5.8.1      CT_TPM_PM_01 – Integrate ATC and TWR tracks on TCWP ....................................................40
5.9     TPM Tower Piloted Flights....................................................................................................................41
   5.9.1      CT_TPM_TPF_01 – Integrate ATC and TWR tracks on TPWP ...................................................41
   5.9.2      CT_TPM_TPF_02 – Pilot Frequencies .........................................................................................42
   5.9.3      CT_TPM_TPF_03 – Pilot Orders..................................................................................................44
     5.9.3.1 CT_TPM_TPF_03_1 – Arrival Orders ......................................................................................45
     5.9.3.2 CT_TPM_TPF_03_2 – Departure Orders ................................................................................46
     5.9.3.3 CT_TPM_TPF_03_3 – Vehicle Orders .....................................................................................48
   5.9.4      CT_TPM_TPF_04 – Air Derived Data ..........................................................................................49
6      TCS COMPONENT TESTS......................................................................................................................51
6.1     Controller Roles ....................................................................................................................................51
   6.1.1     General Description ......................................................................................................................51
   6.1.2     CT_TCS_ROL_01 – TCS Arrival Roles ........................................................................................51
   6.1.3     CT_TCS_ROL_02 – TCS Arrival Roles Merged ..........................................................................54
   6.1.4     CT_TCS_ROL_03 – TCS Arrival All Roles Merged .....................................................................55
   6.1.5     CT_TCS_ROL_04 – TCS Departure Roles ..................................................................................56
   6.1.6     CT_TCS_ROL_05 – TCS Departure Roles Merge .......................................................................59
   6.1.7     CT_TCS_ROL_06 – TCS Departure All Roles Merged................................................................61
6.2     Controller Orders ..................................................................................................................................62
   6.2.1     Changing Taxi Route ....................................................................................................................62
6.3     Integrated ..............................................................................................................................................64

STATUS                                                                                                                                                     TITLE
Company Ref.                                                                                                                          Template : Normal.dotm
                                                                        f7919ee3-d7fb-4de6-9213-
                                                                               1719658e70fc.doc

                                                                                            Page : 7

                                                                                                                    EUROCONTROL



   6.3.1    General Description ......................................................................................................................64
   6.3.2    CT_TCS_INT_01 - TCS Arrival Integrated Mode .........................................................................65
   6.3.3    CT_TCS_INT_02 – TCS Departure Integrated Mode ..................................................................66
   6.3.4    CT_TCS_INT_03 – TCS Arrival and Departure Integrated Mode ................................................68
6.4     Advance Boundary Information ............................................................................................................70
   6.4.1    ABI For Arrival...............................................................................................................................70
7      TIAS COMPONENT TESTS.....................................................................................................................72
7.1     Update Rates ........................................................................................................................................72
   7.1.1    CT_TIAS_UPD_01 Track – Track Update Rates .........................................................................72
8      TFM COMPONENT TESTS .....................................................................................................................73
8.1     Orders ...................................................................................................................................................73
   8.1.1    CT_TFM_ORDERS_01 – Changing Arrival Gate Test.................................................................73
   8.1.2    CT_TFM_ORDERS_02 – Changing Departure Runway Test .....................................................74
   8.1.3    CT_TFM_ORDERS_03 – Changing Standard Instrument Departure (SID) Test ........................76
   8.1.4    CT_TFM_ORDERS_04 – Abort Take-off .....................................................................................77
8.2     Clearances ............................................................................................................................................78
   8.2.1    CT_TFM_CLR_01 – Pushback, Taxi, Lineup and Takeoff Clearances Test ...............................78
   8.2.2    CT_TFM_CLR_02 – Clearance To Gate For Arrival Test ............................................................79
   8.2.3    CT_TFM_CLR_03 – Cleared To Cross Runway For Departure Test ..........................................80
9      TFPM COMPONENT TESTS ...................................................................................................................82
9.1     Turnaround With Progress Events .......................................................................................................82
   9.1.1    CT_TFPM_01 – Progress Events Test .........................................................................................82
   9.1.2    CT_TFPM_02 – Progress Events Test .........................................................................................84
10         GRAPHICAL COMPONENT TESTS ...................................................................................................85
10.1 TCWP ...................................................................................................................................................85
  10.1.1   Labels ...........................................................................................................................................85
    10.1.1.1    CT_TCWP_LABEL_01 – Track Labels ................................................................................85
  10.1.2   Arrival Departure Lists ..................................................................................................................87
    10.1.2.1    CT_TCWP_LIST_01 – Arrival Departure Lists .....................................................................87
    10.1.2.2    CT_TCWP_LIST_02 – Navigation Times .............................................................................89
    10.1.2.3    CT_TCWP_LIST_03 – Changing Navigation Times ............................................................91
  10.1.3   Menus ...........................................................................................................................................92
    10.1.3.1    CT_TCWP_MENUS_01 – Menu Default Selection ..............................................................92
    10.1.3.2    CT_TCWP_MENUS_02 – Runway SID Menu .....................................................................96
  10.1.4   ShortCuts ......................................................................................................................................97
    10.1.4.1    CT_TCWP_SHORTCUTS_01 – Air and Ground Shortcuts .................................................97
    10.1.4.2    CT_TCWP_SHORTCUTS_02 – Hybrid Shortcuts ...............................................................99
10.2 TPWP..................................................................................................................................................100
  10.2.1   Labels .........................................................................................................................................100
    10.2.1.1    CT_TPWP_LABEL_01 – Pilot Track Labels .......................................................................100
    10.2.1.2    CT_TPWP_LABEL_02 – Manoeuvre Prompts ...................................................................104
  10.2.2   Orders .........................................................................................................................................106
    10.2.2.1    CT_TPWP_ORDERS_01 – Conditional Line-up and Take-off...........................................106
    10.2.2.2    CT_TPWP_ORDERS_02 – Conditional Line-up and Take-off...........................................108
    10.2.2.3    CT_TPWP_ORDERS_03 – Stop-Ahead Order ..................................................................109
    10.2.2.4    CT_TPWP_ORDERS_04 – Speed Order ..........................................................................112
  10.2.3   Arrival Departure Vehicle Lists ...................................................................................................113
    10.2.3.1    CT_TPWP_LIST_01 – Arrival Departure Vehicle Lists ......................................................113
  10.2.4   Menus .........................................................................................................................................115
    10.2.4.1    CT_TPWP_MENUS_01 – Menu Default Selection ............................................................115
    10.2.4.2    CT_TPWP_MENUS_02 – Runway SID Menu ...................................................................116
  10.2.5   ShortCuts ....................................................................................................................................117

STATUS                                                                                                                                                    TITLE
Company Ref.                                                                                                                          Template : Normal.dotm
                                                                     f7919ee3-d7fb-4de6-9213-
                                                                            1719658e70fc.doc

                                                                                        Page : 8

                                                                                                                EUROCONTROL



    10.2.5.1     CT_TPWP_SHORTCUTS_01 – Pilot Shortcuts .................................................................117
  10.2.6   Pilot Configurations .....................................................................................................................117
    10.2.6.1     CT_TPWP_CNFG_01 – Tower Pilot ..................................................................................117
    10.2.6.2     CT_TPWP_CNFG_02 – ATC Pilot .....................................................................................118
    10.2.6.3     CT_TPWP_CNFG_03 – Tower and ATC Pilot ...................................................................118
  10.2.7   Flight Control Transfer ................................................................................................................119
    10.2.7.1     CT_TPWP_TRNS_01 – Transfer on Landing ....................................................................119
    10.2.7.2     CT_TPWP_TRNS_02 – Transfer on Takeoff .....................................................................120
    10.2.7.3     CT_TPWP_FRQ_01 – Frequency Management ................................................................120
10.3 Common Graphical Elements .............................................................................................................121
  10.3.1   Symbols ......................................................................................................................................121
    10.3.1.1     CT_TWP_SYMBOL_01 – Symbol Orientation ...................................................................121
    10.3.1.2     CT_TWP_SYMBOL_02 – Symbol Shape and Size ...........................................................122
    10.3.1.3     CT_TWP_SYMBOL_03 – Symbol Shape and Size ...........................................................123
    10.3.1.4     CT_TWP_SYMBOL_04 – Mark Symbol .............................................................................125
  10.3.2   Toolbar ........................................................................................................................................125
    10.3.2.1     CT_TWP_TOOLBAR_01 – Toolbar ...................................................................................125
  10.3.3   Companion Windows ..................................................................................................................126
    10.3.3.1     CT_TWP_CMPN_01 – Adjacent Companion Window .......................................................126
    10.3.3.2     CT_TWP_CMPN_02 – Independent Window ....................................................................128
    10.3.3.3     CT_TWP_CMPN_03 – Mix Use of Independent and Adjacent Companions .....................129
  10.3.4   Route ..........................................................................................................................................131
    10.3.4.1     Route Editor – TPWP .........................................................................................................131
    10.3.4.2     Route Editor - TCWP ..........................................................................................................134
10.4 Mixed Working Positions ....................................................................................................................137
  10.4.1   Mixed TCWP, TPWP and Hybrid TCWP ....................................................................................137
    10.4.1.1     CT_TWP_AIRGRD_01 – Air/Ground Positions Changing Runway and Gate ...................137
    10.4.1.2     CT_TWP_AIRGRD_02 – Air/Ground Positions Issuing Arrival Clearances .......................139
    10.4.1.3     CT_TWP_AIRGRD_03 – Air/Ground Positions Issuing Departure Clearances .................139
    10.4.1.4     CT_TWP_HYBRID_01 – Air/Ground/Hybrid Working Positions ........................................140
11        UTCWP COMPONENT TESTS..........................................................................................................144
11.1 Automate Controller Positions ............................................................................................................144
  11.1.1 CT_uTCWP_01 – Automatic Orders and Clearances Test ........................................................144
12        TSN COMPONENT TESTS................................................................................................................145
12.1 Exclusion Area Closed Runway..........................................................................................................145
  12.1.1  CT_TSN_CLOSED_01 – Closed Runway Incursion ..................................................................145
12.2 Exclusion Area Open Runway ............................................................................................................147
  12.2.1  CT_TSN_OPEN_01 – Arriving On Wrong Runway ....................................................................147
  12.2.2  CT_TSN_OPEN_02 – Lineup/Takeoff In Wrong Direction .........................................................148
  12.2.3  CT_TSN_OPEN_03 – Arrival With Mobile on Runway ..............................................................149
  12.2.4  CT_TSN_OPEN_04 – Arrival with Departure On Runway .........................................................150
  12.2.5  CT_TSN_OPEN_05 – Arrival With Arrival On Runway ..............................................................152
  12.2.6  CT_TSN_OPEN_06 – Departure With Mobile On Runway ........................................................154
  12.2.7  CT_TSN_OPEN_07 – Departure With Multiple Lineups ............................................................156
12.3 Performance .......................................................................................................................................157
  12.3.1  CT_TSN_PERFORMANCE_01 – Efficient intrusion detection algorithm...................................157
  12.3.2  CT_TSN_PERFORMANCE_02 – Intrusion detection during system loading ............................158
12.4 Clearance Alerts .................................................................................................................................158
  12.4.1  CT_TSN_CLEARANCE_01 – Landing-Takeoff Alert .................................................................158
  12.4.2  CT_TSN_CLEARANCE_02 – Landing-Landing Alert ................................................................159
  12.4.3  CT_TSN_CLEARANCE_03 – Lineup-Landing Alert ..................................................................160
  12.4.4  CT_TSN_CLEARANCE_04 – Takeoff-Takeoff Alert ..................................................................162
  12.4.5  CT_TSN_CLEARANCE_05 – Takeoff-Lineup Alert ...................................................................163
  12.4.6  CT_TSN_CLEARANCE_06 – EnterCross-Landing Alert ...........................................................164

STATUS                                                                                                                                               TITLE
Company Ref.                                                                                                                     Template : Normal.dotm
                                                                     f7919ee3-d7fb-4de6-9213-
                                                                            1719658e70fc.doc

                                                                                         Page : 9

                                                                                                                 EUROCONTROL



  12.4.7  CT_TSN_CLEARANCE_07 – EnterCross-Takeoff Alert ............................................................165
  12.4.8  CT_TSN_CLEARANCE_08 – EnterCross Mobile Alert .............................................................166
  12.4.9  CT_TSN_CLEARANCE_09 – Runway Closed Alert ..................................................................167
  12.4.10   CT_TSN_CLEARANCE_10 – Runway Too Short Alert .........................................................168
  12.4.11   CT_TSN_CLEARANCE_11 – Fast Taxi Alert ........................................................................168
  12.4.12   CT_TSN_CLEARANCE_12 – Taxiway Sector Closed Alert ..................................................170
  12.4.13   CT_TSN_CLEARANCE_13 – Takeoff Without Clearance Alert ............................................170
  12.4.14   CT_TSN_CLEARANCE_14 – Lineup/Lineup Alert.................................................................172
  12.4.15   CT_TSN_CLEARANCE_15 – Cleared Up To Alert ................................................................172
  12.4.16   CT_TSN_CLEARANCE_16 – LND Alert ................................................................................174
  12.4.17   CT_TSN_CLEARANCE_17 – Stationary Alert .......................................................................175
12.5 Deviation Alerts ...................................................................................................................................176
  12.5.1  CT_TSN_DEVIATION_01 – Route Deviation Alert ....................................................................176
13        TOWER ATC INTERACTION ............................................................................................................178
13.1      CT_TAI_GORD_01 – Go-Around .......................................................................................................178
13.2      CT_TAI_GORD_02 – Go-Around .......................................................................................................178
14        TAAM TRAFFIC CONVERTER TESTS.............................................................................................179
14.1 EEC Supplied TAAM Test Data ..........................................................................................................179
  14.1.1  CT_TAAM_TRAFFIC_01 – Convert Traffic for Standalone Mode .............................................179
  14.1.2  CT_TAAM_TRAFFIC_02 – Convert Traffic for Truncate Mode .................................................181
  14.1.3  CT_TAAM_TRAFFIC_03 – Convert Traffic for Connected Mode ..............................................182
14.2 Graffica Test Data ...............................................................................................................................184
  14.2.1  CT_TAAM_TRAFFIC_04 – Convert Traffic Using Derived Routes ............................................184
  14.2.2  CT_TAAM_TRAFFIC_05 – Convert Traffic Using Derived Routes ............................................185
15        DISTRIBUTED SYSTEM TESTS .......................................................................................................186
15.1 Distributed ...........................................................................................................................................186
  15.1.1   CT_DIS_01 – Distributed Test ....................................................................................................186
16        BACKWARDS COMPATIBILTY ........................................................................................................188
16.1 Supporting ATC Components .............................................................................................................188
  16.1.1 CT_INT_BC_01 – Tower Provides Backwards Compatibility for ATC .......................................188
17        CAPACITY TEST ...............................................................................................................................188
17.1 Rush Hour ...........................................................................................................................................188
  17.1.1 CT_INT_CAP_01 – Automated Many Arrivals and Departures .................................................188
18        COMPLIANCE MATRIX .....................................................................................................................190
18.1      SRD Requirement To Test Case Mapping ........................................................................................190
18.2      Test Cases not linked to SRD Requirement .......................................................................................197



                                                                Index of figures
FIGURE 1: TEST R27X AIRSPACE ..................................................................................................................3

FIGURE 2: LFPG (TAAM) AIRPORT ................................................................................................................4

FIGURE 3: LFPG ATC SECTOR .......................................................................................................................5

FIGURE 4: ATC SECTORS ...............................................................................................................................5

FIGURE 5: ELEVATION VIEW OF ATC SECTORS .........................................................................................6
STATUS                                                                                                                                                TITLE
Company Ref.                                                                                                                     Template : Normal.dotm
                 f7919ee3-d7fb-4de6-9213-
                        1719658e70fc.doc

                              Page : 10

                                            EUROCONTROL




               Index of tables




STATUS                                                              TITLE
Company Ref.                                         Template : Normal.dotm
                                                     f7919ee3-d7fb-4de6-9213-
                                                            1719658e70fc.doc

                                                           Page : 1 of 197

                                                                                EUROCONTROL




    1     INTRODUCTION

    1.1    Purpose
This document contains component level tests for the Tower subsystem of the eDEP system.

    1.2    Intended audience
This document is of interest to all developers and managers of the Tower project.

    1.3    Responsibilities
The eDEP EEC and Graffica project managers are responsible for updating this document.



    1.4    Associated documentation

    1.4.1 Internal project documentation
                       Title                                     Reference                    Date
 Software Requirements Document (SRD)                                                29th Feb 2008 (V16.0)




    1.4.2 General documentation
                       Title                                      Authors                     Date




    1.5    Glossary & Abbreviations
        Abbreviation                                               Meaning
TWR                            Tower Subsystem
eDEP                           Early Development and Evaluation Platform
GSDK                           Graffica Software Development Kit
ATC                            Air Traffic Control
TACR                           Tower Aircraft Performance component
TASP                           Tower Airspace component
TIFPL                          Tower Initial Flight Plan component
DNS                            Detailed Navigation Script component
TPM                            Tower Pilot Manager component
TSN                            Tower Safety Network




STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                   f7919ee3-d7fb-4de6-9213-
                                                          1719658e70fc.doc

                                                         Page : 2 of 197

                                                                                  EUROCONTROL



    1.6     Colour Definitions

    1.6.1 Flight Labels
Each aircraft and vehicle that is displayed on a controller position will have an associated label. The colours
used to display the label indicate the state of a particular aircraft or vehicle to a controller. Where test scripts
refer to the appearance of the label a logical state will be used. The following table sets our the colour
schemes used for each logical state.
    State                        Label Colour Scheme
    Advance                      Callsign either blue (departure) or brown (arrival)
                                 Label fields and border in black.
    Advance Transferred          Callsign either blue (departure) or brown (arrival) with a white
                                 background.
                                 The remaining label fields and borders in black.
    Assumed                      Callsign and label either all blue (departure) or brown (arrival).
    Assumed Transferred          Callsign either blue (departure) or brown (arrival).
                                 Label fields and border in grey.
    Not Concerned                Callsign and label all in grey.
    Concerned                    Not used within the current tower system, however the colour scheme
                                 would be the same as for the Not Concerned state.




    2     TEST SCENARIO

    2.1     Intended purpose
Because of the size of the data provided in the TAAM data, it would be inordinately difficult to validate all
functionality for certain components. For this reason, a small scenario (R27X) has been created with a wide
range of features in a simple, well-defined space. Using this scenario, full validation can be performed by the
user.
The TAAM data will be used for acceptance tests of certain components, e.g. TPM, TCWP and TSN.
To support testing integrated functions between the Tower System and th eDEP ATC system the TAAM data
will be supplemented with French airspace definitions.

    2.2     Airspace




STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                           f7919ee3-d7fb-4de6-9213-
                                                                  1719658e70fc.doc

                                                                    Page : 3 of 197

                                                                                                          EUROCONTROL



    2.2.1 R27X Airspace
The following diagram describes the test airspace used in tests for the TASP, TIFPL and DNS components.




                                                                                                                                                                START
                                                                                                                                                                START
    END




           P1
          R_                            P2
                                       R_                         P3
                                                                 R_                        u wy 2
                                                                                          Rn a R7          P4
                                                                                                          R_                                            P5
                                                                                                                                                       R_




           00
          16       25
                   18                   05
                                       16                        17
                                                                  06                                       00
                                                                                                          16                            32
                                                                                                                                       14




           P0
          T _      1
                  82                   T _
                                        P1                        P2
                                                                 T _                                       P3
                                                                                                          T _

                                                                                                                                                   e
                                                                                                                                                  Ky
                                             25
                                             10            19
                                                          19                         39
                                                                                    12               34
                                                                                                    11


                                                                                                                                          n a r rriva
                                                                                                                                         O e w y fo A ls
                                                                       Not Medium
                                                                       Not Medium




                                                                                                                Not Heavy
                           Not Light




                                       10
                                        18                        07
                                                                 19                                        18
                                                                                                          10



                                                                                                                                              pe      it 0 /s
                                                                                                                                             S e d lim 1 m



                                                                  P5
                                                                 T _
                                        P4
                                       T _                                                                 P6
                                                                                                          T _
                                                                                                                                                   1
                                                                                                                                                  82
                                                                 s e y
                                                                1 d la
                                                                                                                                             a 1m n
                                                                                                                                           P th 8 2 lo g
                                                                                                                                         (a p x –ro n e to
                                                                                                                                           p ro     udd
                                                                                                                                             e re t e r)
                                                                                                                                            n a s m te




                                                                                                                            Pushback
                                        16
                                       16           12
                                                     32                                   14
                                                                                           33              16
                                                                                                          10

                                                                                                                                              n a r ig t
                                                                                                                                             O e w y fo L h
                                                                                                                                                  irc ft
                                                                                                                                                 A ra




                                       A
                                                                                                          B



                                                  Figure 1: Test R27X Airspace

This diagram describes a single runway, two gates, and seven taxipoints; there are eighteen possible paths
between the various taxipoints. Constraints on these paths which can be used to test DNS functionality
include paths of variable lengths, differing speed limits on paths, restrictions on travel direction (based on the
type of flight involved), and weight restrictions, limiting aircraft by the weights allowed. Note that the
distances listed are rounded to the nearest integer for display purposes; values generated may be slightly
higher due to rounding errors.
Additionally, there is a single delay on taxipoint 5. This delay can be used to alter the optimal path, and to
confirm that it is listed in the resulting navigation script.



    2.2.2 LFPG (TAAM) Airport
The following diagram illustrates the TAAM converted test airport data used within these tests. It represents
Charles De Gaulle airport (LFPG). The data consists of:
         TaxiPoints (2702)
         Taxiways (197)
         Taxiway Segments(2273)
         Aprons (407)
         Gates (393)
         Runways (4 pairs). Although only the northern most two pairs (R09L, R09R, R27L, R27R) are used
          specifically in the tests.

STATUS                                                                                                                                                                  TITLE
Company Ref.                                                                                                                             Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                      Page : 4 of 197

                                                                             EUROCONTROL




                                      Figure 2: LFPG (TAAM) Airport

In addition, overlaid on top of the airport are ground sectors. These consist of airport, runway, taxiway and
apron ground sectors. The airport ground sector LFPG encompasses all other ground sectors. There are two
taxiway ground sectors, namely TWY_N and TWY_S. These divide the LFPG ground sector (above and
below the dashed blue line). There are also two runway ground sectors RWY_N and RWY_S and four apron
ground sectors APRON_N, APRON_S, CARGO_N and CARGO_S.
The tests described within this document predominately use the northern side of the airport. That is the area
above the blue dashed line.



    2.2.3 French Airspace
When running tests where the Tower system interfaces with the eDEP ATC system further enroute airspace
definitions are utilised. These include fixes, airports, airlanes and sectors. To connect the two systems an
ATC sector corresponding to the LFPG ground sector must be defined. The ATC LFPG sector for
consistency must match the ground sector area and extend to a flight level (FL10) that encompasses the
airport‟s elevation (387ft).




STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                      Page : 5 of 197

                                                                           EUROCONTROL




                                        Figure 3: LFPG ATC Sector

Around the ATC LFPG sector are four other sectors FS, FN, UR and LU.




                                           Figure 4: ATC Sectors

This gives the following elevation view of the ATC sectors.




STATUS                                                                                             TITLE
Company Ref.                                                                        Template : Normal.dotm
                            f7919ee3-d7fb-4de6-9213-
                                   1719658e70fc.doc

                                  Page : 6 of 197

                                                         EUROCONTROL




               Figure 5: Elevation View of ATC Sectors




STATUS                                                                           TITLE
Company Ref.                                                      Template : Normal.dotm
                                                    f7919ee3-d7fb-4de6-9213-
                                                           1719658e70fc.doc

                                                           Page : 7 of 197

                                                                                     EUROCONTROL




    3     AUTOMATED TEST SCRIPTS

    3.1    Introduction
By performing certain tests automatically, it is possible to check a much larger range of functionality
(including possible interactions between features), in a considerably reduced time period, and minimising
human error. In addition to this, the debugging output makes it a lot faster to isolate and fix errors – and
retain a thorough record of exactly which tests succeeded and failed for each test run.


Upon running, each test will automatically deliver a series of queries to the tested component, and compare
each generated output to the expected results. Each query can be used to demonstrate a specific response
to a particular parameter (or conjunction of parameters). As such, a successful run will prove that the
component performs as specified by each query-response pair. The query-response pairs may additionally
be verified externally against desired behaviour, if desired. The primary purpose of this document (with
regard to the automatically tested components) is to list these query-response pairs, thus aiding this
verification process.



    3.2    Running the Automated Test Scripts
In order to perform automated testing, simply start the test scenario by launching it through the Tower
launcher, and examine the console log. The GSDK will load up as normal, printing the standard initialisation
lines. At this point, it will begin testing – there may be a pause here as it runs its queries. Once tested, the
script will print out a summary.


A successful run of the test will result in the following message being printed to the log:

                        ***
                        * test.twr.tests.DNSTEST passed all tests (22 tests total)
                        ***


If there are any errors within the test, the summary will contain a listing of each error generated. Noting these
errors will isolate which aspect of functionality is in error, and help in the debugging process:

                        ***
                        * test.twr.tests.TASPTEST failed test count: 4/7
                        * >testCounts error count: 1/8
                        * >testRunwayEntryExitPoints error count: 1/9
                        * >testDistances error count: 1/5
                        * >testRunwayPerimeter error count: 2/11
                        ***


The first line specifies which test set failed, and a ratio of failed tests to total tests – this is the number of „test
groups‟ that contain at least one error. Within the automated tests, a test group is generally a series of 5-10
atomic checks on a certain event, or piece of functionality; and an error is a mismatch between an expected
value and a generated value.
After this single-line summary, there is a summary of each failed test, with the ratio of errors to total checks.
These summaries can be expanded by setting the resource TEST.VERBOSE to true; however this action
should be part of the debugging process, once errors are found.




STATUS                                                                                                           TITLE
Company Ref.                                                                                      Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                        Page : 8 of 197

                                                                                 EUROCONTROL




    4     AUTOMATED COMPONENT TESTS

    4.1     TACR

    4.1.1 Running the TACR Test
Scenario ID                 CT_TACR_001
SRD Requirement             70
Objective                   This test comprises a full test suite for the TACR component
Dependencies                None
Resource File               <component test home>/tacr/tacr.gsdk
                            This test references the following scenario files:
                            TACR performance: resources/common/performance/r27x.dat



    4.1.2 Tests Performed
TACR is entirely an entity parsing/distribution component. Full functionality can be verified by confirming that
it produces and distributes entities equivalent to those declared in the resource file. As such, the testing
component will create a TACRService object, and load the performance data (using the normal component
distribution method).
There is only one test performed within the TACR test suite - once the performance data is loaded, the
testing component will query the entity managers for the correct number of objects, and then compare
sample entities against the values actually present in the resource file:
Field                                              Expected Value
Number of AircraftPerformance objects:             2
B737 dry runway acceleration                       12 (m/s/s)
B737 dry runway deceleration                       10 (m/s/s)
B737 final approach speed                          200 (m/s)
B737 queue distance                                15 (m)
B737 takeoff speed                                 300 (m/s)
B737 default taxi speed                            25 (m/s)
B737 touchdown speed                               200 (m/s)
B737 wet runway acceleration                       8 (m/s/s)
B737 wet runway deceleration                       6 (m/s/s)


Number of VehiclePerformance objects:              4
TaxiTruck1 queue distance                          9 (m)
TaxiTruck1 default taxi speed                      15 (m/s)



STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                        Page : 9 of 197

                                                                                 EUROCONTROL



    4.2     TASP

    4.2.1 Running the TASP Test
Scenario ID                CT_TASP_001
SRD Reference              80, 90, 100, 230, 260, 270
Objective                  This test comprises a full test suite for the TASP component
Dependencies               None
Resource File              <component test home>/tasp/tasp.gsdk
                           This test references the following scenario files:
                           TASP airspace: resources/common/airports/r27x/r27x_airport.dat
                           ASP airspace: resources/common/airports/r27x/r27x_airspace.dat



    4.2.2 Tests Performed
TASP is entirely an entity parsing/distribution component. Full functionality can be verified by confirming that
it produces and distributes entities equivalent to those declared in the resource file. As such, the testing
component will create a TASPService object, and load the airspace data (using the normal component
distribution method). Once the airspace data is loaded, the testing component will perform the following tests
on the entities in the manager:



    4.2.2.1 TestCounts
This will check that the number of entities in the databases correspond to the number of entities in the
scenario file. If there are any problems in the parsing, distribution or resolution of the entities, an incorrect
number of entities will be present, and this will report an error.



    4.2.2.2 TestTaxiwayHierarchy
This will check that the entities successfully resolve references to each other. Taxiways are defined to
contain a number of Taxiway segments, each of which is constituted by a number of Taxipoints. The checks
performed in this test will confirm that it is possible to reference the taxipoints from the taxiways. This method
also checks that associated data on the taxipoint was successfully detected, for instance whether the point
was a junction, a cul de sac or a delay point.



    4.2.2.3 TestRunwayEntryExitPoints
This will check that all (and only) taxipoints listed as part of a runway (i.e. specifically mentioned in the
runway perimeter definition‟s “CONNECT_TO_RUNWAY_AT” section) will have the isRunwayEntryExit flag set
to true.



    4.2.2.4 TestDistances
This test is largely used as a reference – it documents the exact distance between any adjacent nodes. As
the values are listed in lat-long coordinates, but used by the eDEP system as X-Y, the values listed cannot


STATUS                                                                                                      TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                                   f7919ee3-d7fb-4de6-9213-
                                                          1719658e70fc.doc

                                                        Page : 10 of 197

                                                                                 EUROCONTROL



easily be confirmed. These values are, however, important benchmarks for future tests (e.g. in the DNS
component), and so it is useful to have any deviations in these values easily noticeable.

    4.2.2.5 TestRunwayPerimeter
This tests the following functionality of a runway perimeter:
        Correct number of hold points (0)
        Correct number of entry/exit points (5)
        Reference to the associated runway object correctly parsed
        Correctly parsed touchdown distance (50m)
        Touchdown position correctly calculated from start threshold, end threshold and touchdown distance
In addition, the method documents and confirms the following values for future reference:
       Start threshold location
       End threshold location
       Distance from start threshold to end threshold
       Distance from start threshold to each runway entry/exit point



    4.2.2.6 TestStatusData
This tests that status values as listed in the TASP airspace file (r27x_airport.dat) are accurately reflected in
the entities:
Check ID and test description                 Expected Value
Check #1: rp1status                           Status=3,      Allowed     weights=[true,true,true,false],      Max
                                              Speed=15.0
Taxipoints: RP1, TP0, TP1
Default status: All aircraft allowed to
move in either direction, maximum speed
15 m/s
Check #2: runway3statusToHead                 Status=3,      Allowed     weights=[true,true,true,false],      Max
                                              Speed=15.0
Taxipoints: RP2, TP1
Confirms that moving from TP1 to RP2,
the status is the default status
Check #3: runway3statusToTail                 Status=2,      Allowed     weights=[true,true,true,false],      Max
                                              Speed=15.0
Taxipoints: RP2, TP1
When moving in the reverse direction
(RP2 to TP1), the status is 2, i.e.
departures only
Check #4: midsection1status                   Status=3,      Allowed    weights=[true,true,false,false],      Max
                                              Speed=15.0
Taxipoints: TP1, TP4
This taxiway is not allowed for LIGHT
aircraft.
Check #5: midsection3status                   Status=3,      Allowed     weights=[true,true,true,false],      Max
                                              Speed=10.0


STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 11 of 197

                                                                             EUROCONTROL



Taxipoints: TP4, TP2, TP6
This taxiway has a max speed of 10m/s

    4.2.2.7 TestGroundSectors
This tests that Ground Sectors contain the information with respect to the airport they belong to, the
frequency associated with them, and they correctly determine whether particular points are located within the
sector or not.



    4.2.2.8 TestAirportElevation
This tests that airports have elevation values added to them, and these values are as specified in the
resource file.



    4.2.2.9 TestPushback
This tests that a gate specified as a pushback gate has a pushback point. Conversely if the gate is not a
pushback gate then it has no pushback point.



    4.2.2.10 TestExclusionAreas
This tests that exclusion areas are defined with an associated runway, multiple lineup option, long and short
final approach times with an additional optional reduced spacing criteria.




STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                       Page : 12 of 197

                                                                                  EUROCONTROL




    4.3     TIFPL

    4.3.1 Running the TIFPL
Scenario ID                CT_TIFPL_001
SRD Reference              240, 280
Objective                  This test comprises a full test suite for the TIFPL component
Dependencies               None
Resource File              <component test home>/tifpl/tifpl.gsdk
                           This test references the following scenario files:
                           TASP airspace: resources/common/airports/r27x/r27x_defaults.dat
                           TACR performance: resources/common/performance/r27x.dat
                           TIFPL flight plans: resources/scenarios/tifpl/tifpl_traffic.dat

    4.3.2 Response Key
These tests are run when the TIFPL processes and distributes tower flight plans. These tower flight plans
are converted into a string to enable easy confirmation of their contents. These string descriptions of the
tower flight plans are checked against the expected values to enable automatic verification. There is a
common format throughout test outputs, designed to make it easy to read the important information at a
glance:
    1. A marker, “VEH”, “ARR” or “DEP”, referring to the type of tower flight plan in question – i.e. whether
       the plan is for a vehicle (non-aircraft), an arriving aircraft or a departing aircraft.
    2. An optional “Speed” parameter, which (if present) will override the aircraft‟s speed for this journey.
    3. After the optional speed parameter, there is a set of „flight plan type‟ specific parameters:
             a. For a departure, the string will indicate whether a pushback is required
             b. For a vehicle plan, there will be the weight category (Size) and the vehicle model.
    4. The start time (note that with arrivals and departures, this figure is extracted from the corresponding
       IFPL flight plan, not listed here. All flights begin at 8:00:00, with the clock start time 7:59:59)
    5. The list of constraints. Each constraint is listed as a single unit in parentheses, and there is an arrow
       (=>)indicating the journey from one constraint to the next. Each constraint consists of the name of
       the constraint point (the taxipoint or runway constraining the flight at this step), followed by the
       following optional parameters (each separated in the test by colons for visibility):
             a. “W” – the pause at this location as specified by the flight plan (this will override any pauses
                specified by airspace)
             b. “S” – the maximum speed for the aircraft to move at (this will override all previous
                performance or flight-plan based speeds, and set the speed for the rest of the plan)
“AVOID” – this specifies that the constraint is NOT to go via this point – the route from the last non-AVOID
constraint to the next non-AVOID constraint will not go through any AVOID constraints.

    4.3.3 TIFPL Testset Details
Test ID      Scenario-based flight plan       eDEP-based flight plan                   Demonstrated Behaviour
TIFPL_1      AIRPORTARRIVAL TIFPL_1           ARR,                                     Basic arrival (used as reference point
             TAXIROUTE                        Start time = 1.0,

STATUS                                                                                                         TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                          f7919ee3-d7fb-4de6-9213-
                                                 1719658e70fc.doc

                                               Page : 13 of 197

                                                                      EUROCONTROL



              RUNWAY R27               ETA = 0,                           for further tests).
              GATE A                   Constraints = (R27)=>(A)
           END
TIFPL_2    AIRPORTARRIVAL TIFPL_2      ARR,                               Optional taxi speed present
           TAXI_SPEED 10               Speed=10.0,
           TAXIROUTE                   Start time = 1.0,
              RUNWAY R27               ETA = 0,
              GATE A                   Constraints = (R27)=>(A)
           END
TIFPL_3    AIRPORTARRIVAL TIFPL_3      ARR,                               Intermediate constraint with a wait
           TAXIROUTE                   Start time = 1.0,                  parameter
              RUNWAY R27               ETA = 0,
              TAXIPOINT RP_4 WAIT 1    Constraints =
              GATE A                   (R27)=>(RP_4:W=1.0)=>(A)
           END
TIFPL_4    AIRPORTARRIVAL TIFPL_4      ARR,                               Intermediate constraint with a speed
           TAXIROUTE                   Start time = 1.0,                  parameter
              RUNWAY R27               ETA = 0,
              TAXIPOINT TP_3 SPEED 2   Constraints =
              GATE A                   (R27)=>(TP_3:S=2.0)=>(A)
           END
TIFPL_5    AIRPORTARRIVAL TIFPL_5      ARR,                               Intermediate constraint (gates are valid
           TAXIROUTE                   Start time = 1.0,                  intermediate steps) with wait and
              RUNWAY R27               ETA = 0,                           speed parameters
              GATE B WAIT 3 SPEED 4    Constraints =
              GATE A                   (R27)=>(B:W=3.0:S=4.0)=>(A)
           END
TIFPL_6    AIRPORTARRIVAL TIFPL_6      ARR,                               Intermediate not-via constraint
           TAXIROUTE                   Start time = 1.0,
              RUNWAY R27               ETA = 0,
              NOT_VIA TP_2             Constraints =
              GATE A                   (R27)=>(TP_2:AVOID)=>(A)
           END
TIFPL_7    AIRPORTDEPARTURE TIFPL_7    DEP,                               Basic departure (used as reference
           TAXIROUTE                   Start time = 1.0,                  point for further tests)
              GATE B                   Constraints = (B)=>(R27)
              RUNWAY R27
           END
TIFPL_8    AIRPORTDEPARTURE TIFPL_8    DEP,                               Optional speed parameter present
           TAXI_SPEED 10               Speed=10.0,
           TAXIROUTE                   Start time = 1.0,
              GATE B                   Constraints = (B)=>(R27)
              RUNWAY R27
           END
TIFPL_9    VEHICLEPLAN TIFPL_9         VEH,                               Basic vehicle plan (used as reference
           ACTIVATION "08:00:00"       Origin = EHAM,                     point for further tests)
           ORIGIN      EHAM            Size = LIGHT,
           SIZE        LIGHT           Planned = false,
           TYPE        ambulance       ManoeuvreType = 0,
           TAXIROUTE                   OBT = 0.0,
              TAXIPOINT TP_4           Model = ambulance,
              TAXIPOINT TP_3           Start time = 1.0,
           END                         Constraints = (TP_4)=>(TP_3)
TIFPL_10   VEHICLEPLAN TIFPL_10        VEH,                               Single point flight plans are acceptable
           ACTIVATION "08:00:00"       Origin = EHAM,                     for vehicle plans
           ORIGIN      EHAM            Size = LIGHT,
           SIZE        LIGHT           Planned = false,
           TYPE        ambulance       ManoeuvreType = 0,
           TAXIROUTE                   OBT = 0.0,
              TAXIPOINT TP_4           Model = ambulance,
           END                         Start time = 1.0,
                                       Constraints = (TP_4)
TIFPL_11   VEHICLEPLAN TIFPL_11        VEH,                               Size information changed
           ACTIVATION "08:00:00"       Origin = EHAM,
           ORIGIN      EHAM            Size = MEDIUM,
           SIZE        MEDIUM          Planned = false,
           TYPE        ambulance       ManoeuvreType = 0,
           TAXIROUTE                   OBT = 0.0,
              TAXIPOINT TP_4           Model = ambulance,
              TAXIPOINT TP_3           Start time = 1.0,

STATUS                                                                                             TITLE
Company Ref.                                                                       Template : Normal.dotm
                                        f7919ee3-d7fb-4de6-9213-
                                               1719658e70fc.doc

                                             Page : 14 of 197

                                                                   EUROCONTROL



           END                       Constraints = (TP_4)=>(TP_3)
TIFPL_12   VEHICLEPLAN TIFPL_12      VEH,                                Airport origin information changed.
           ACTIVATION "08:00:00"     Origin = LHHR,                      There is currently no effect on
           ORIGIN      LHHR          Size = LIGHT,                       behaviour as a result of this.
           SIZE        LIGHT         Planned = false,
           TYPE        ambulance     ManoeuvreType = 0,
           TAXIROUTE                 OBT = 0.0,
              TAXIPOINT TP_4         Model = ambulance,
              TAXIPOINT TP_3         Start time = 1.0,
           END                       Constraints = (TP_4)=>(TP_3)
TIFPL_13   VEHICLEPLAN TIFPL_13      VEH,                                Vehicle model information changed.
           ACTIVATION "08:00:00"     Origin = LHHR,
           ORIGIN      LHHR          Size = LIGHT,
           SIZE        LIGHT         Planned = false,
           TYPE        taxiTruck1    ManoeuvreType = 0,
           TAXIROUTE                 OBT = 0.0,
              TAXIPOINT TP_4         Model = taxiTruck1,
              TAXIPOINT TP_3         Start time = 1.0,
           END                       Constraints = (TP_4)=>(TP_3)
TIFPL_14   VEHICLEPLAN TIFPL_14      VEH,                                Start time changed
           ACTIVATION "08:00:01"     Origin = LHHR,
           ORIGIN      EHAM          Size = LIGHT,
           SIZE        LIGHT         Planned = false,
           TYPE        ambulance     ManoeuvreType = 0,
           TAXIROUTE                 OBT = 0.0,
              TAXIPOINT TP_4         Model = ambulance,
              TAXIPOINT TP_3         Start time = 2.0,
           END                       Constraints = (TP_4)=>(TP_3)
TIFPL_15   VEHICLEPLAN TIFPL_15      VEH,                                No limit to length or amount of
           ACTIVATION "08:00:00"     Origin = EHAM,                      repetition within plans
           ORIGIN      EHAM          Size = LIGHT,
           SIZE        LIGHT         Planned = false,
           TYPE        ambulance     ManoeuvreType = 0,
           TAXIROUTE                 OBT = 0.0,
              TAXIPOINT TP_0         Model = ambulance,
              TAXIPOINT TP_1         Start time = 1.0,
              TAXIPOINT RP_1         Constraints =
              TAXIPOINT TP_0         (TP_0)=>(TP_1)=>(RP_1)=>(TP_0)=>
              TAXIPOINT TP_1         (TP_1)=>(RP_1)=>(TP_0)=>(TP_1)=>
              TAXIPOINT RP_1         (TP_0)=>(TP_1)=>(TP_0)=>(TP_1)=>
              TAXIPOINT TP_0         (RP_1)=>(TP_0)=>(TP_1)=>(TP_0)=>
              TAXIPOINT TP_1         (TP_1)
              TAXIPOINT TP_0
              TAXIPOINT TP_1
              TAXIPOINT TP_0
              TAXIPOINT TP_1
              TAXIPOINT RP_1
              TAXIPOINT TP_0
              TAXIPOINT TP_1
              TAXIPOINT TP_0
              TAXIPOINT TP_1
           END
TIFPL_16   AIRPORTARRIVAL TIFPL_16   ARR,                                An arrival may have a turnaround – i.e.
           TURNAROUND TIFPL_17       Turnaround = TIFPL_17,              a departure which gets automatically
           TAXIROUTE                 Start time = 1.0,                   triggered when the arrival parks at a
              RUNWAY R27             ETA = 0,                            gate.
              GATE A                 Constraints = (R27)=>(A)
           END
TIFPL_18   VEHICLEPLAN TIFPL_18      TIFPL_18,                           A vehicle performing an unplanned
           ACTIVATION "08:00:00"     VEH, Origin = EHAM, Size = LIGHT,   TOW manoeuvre
           ORIGIN      EHAM          Planned = false, ManoeuvreType =
           SIZE        LIGHT         1, OBT = 0.0, Model = ambulance,
           TYPE        ambulance     Start time = 1.0, Constraints =
           PLANNED     FALSE         (TP_4)=>(TP_3)
           MANOEUVRE   TOW
           TAXIROUTE
              TAXIPOINT TP_4
              TAXIPOINT TP_3
           END
TIFPL_19   VEHICLEPLAN TIFPL_19      TIFPL_18,                           A vehicle performing a planned TOW
           ACTIVATION "08:00:00"     VEH, Origin = EHAM, Size = LIGHT,

STATUS                                                                                           TITLE
Company Ref.                                                                    Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                       Page : 15 of 197

                                                                                 EUROCONTROL



             ORIGIN      EHAM                 Planned = true, ManoeuvreType =        manoeuvre
             SIZE        LIGHT                1, OBT = 0.0, Model = ambulance,
             TYPE        ambulance            Start time = 1.0, Constraints =
             PLANNED     TRUE                 (TP_4)=>(TP_3)
             MANOEUVRE   TOW
             TAXIROUTE
                TAXIPOINT TP_4
                TAXIPOINT TP_3
             END
TIFPL_20     VEHICLEPLAN TIFPL_20             TIFPL_18,                              Off-block time (OBT) changed
             ACTIVATION "08:00:00"            VEH, Origin = EHAM, Size = LIGHT,
             ORIGIN      EHAM                 Planned = false, ManoeuvreType =
             SIZE        LIGHT                0, OBT = 3.0, Model = ambulance,
             TYPE        ambulance            Start time = 1.0, Constraints =
             OBT            "08:00:02"        (TP_4)=>(TP_3)
             TAXIROUTE
                TAXIPOINT TP_4
                TAXIPOINT TP_3
             END



    4.4     DNS

    4.4.1 Running the DNS Test
Scenario ID                 CT_DNS_001
SRD Reference               210, 220, 230, 260
Objective                   This test comprises a full test suite for the DNS component
Dependencies                None
Resource File               <component test home>/dns/dns.gsdk
                            This test references the following scenario files:
                            TASP airspace: resources/common/airports/r27x/r27x_defaults.gsdk
                            TACR performance: resources/common/performance/r27x.dat
                            TIFPL flight plans: resources/scenarios/dns/dns_traffic.dat



    4.4.2 Response Key
These tests are run by requesting navigation scripts for a number of flight plans. The returned navigation
scripts are converted into a string to enable easy confirmation of their contents. These string descriptions of
the scripts are checked against the expected values to enable automatic verification. Each script is listed as
a series of steps, each of the format
          (RP_3, T=174, S=15, W=2)
In each case, the first argument (RP_3) is the name of the taxipoint to be visited. The second argument
(T=174) establishes the total time which the aircraft should take to reach this point from the start of the plan.
This value is rounded to the nearest integer for the description only (in the interests of clarity); the actual
script retains the value as a double. The third argument (S=15) is the speed which the aircraft is due to travel
from this point to the next point at. The fourth optional argument (W=2) is present if there is a delay on this
taxipoint.

    4.4.3 DNS Testset Details
Test ID       Flight Plan                        Resulting DNS Script                  Demonstrated Behaviour
              (Query)                            (Response)

STATUS                                                                                                      TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                      f7919ee3-d7fb-4de6-9213-
                                                             1719658e70fc.doc

                                                           Page : 16 of 197

                                                                                  EUROCONTROL



DNS_1      AIRPORTARRIVAL DNS_1                      (RP_3, T=0.0, S=15.0)->            DNS successfully searches by time -
           TAXIROUTE                                 (TP_2, T=71.7, S=15.0)->           route through TP_4 is shorter, but
              RUNWAY R27                             (TP_5, T=144.8, S=15.0, W=1.0)->   has a speed limit on path TP_2-
              GATE A                                 (A, T=234.0, S=0.0)                >TP_4
           END
                                                                                        For an arrival with no intermediate
           (Note also that the associated                                               points, the flight will decelerate to taxi
           primary flight plan lists the aircraft                                       speed, and then leave at next exit.
           type of this aircraft as MFTR, which
           has a default taxi speed of 15m/s).                                          Without a flight-plan defined speed,
                                                                                        DNS will extract aircraft performance
                                                                                        speed for flight plan.
                                                                                        DNS successfully detects and
                                                                                        includes any delay on taxipoints



DNS_2      AIRPORTARRIVAL DNS_2                      (RP_3, T=0.0, S=10.0)->            When a flight plan defines a speed,
           TAXI_SPEED 10                             (TP_2, T=107.6, S=10.0)->          this    overrides    the     aircraft
           TAXIROUTE                                 (TP_4, T=227.5, S=10.0)->          performance speed.
              RUNWAY R27                             (A, T=344.1, S=0.0)
              GATE A                                                                    The maximum speed limit can affect
           END                                                                          the resulting flight plan – indicating
                                                                                        that the DNS successfully searches
                                                                                        by time



DNS _3     AIRPORTARRIVAL DNS_3                      (RP_4, T=0.0, S=10.0, W=10.0)->    When a flight plan defines a runway
           TAXI_SPEED 10                             (TP_3, T=116.0, S=10.0)->          exit point, the resulting script will
           TAXIROUTE                                 (TP_6, T=226.8, S=10.0)->          honour that point, even if reaching
              RUNWAY R27                             (TP_2, T=359.8, S=10.0)->          the taxispeed is unattainable
              TAXIPOINT RP_4 WAIT 10                 (TP_4, T=479.7, S=10.0)->
              GATE A                                 (A, T=596.3, S=0.0)                If the flight plan marks a designated
           END                                                                          wait on a taxipoint (even an exit
                                                                                        point), this will be included on the
                                                                                        script, and the pause will be counted
                                                                                        on the cumulative time.

DNS_4      AIRPORTARRIVAL DNS_4                      (RP_3, T=0.0, S=10.0)->            When a flight script specifies an
           TAXI_SPEED 10                             (TP_2, T=107.6, S=10.0)->          intermediate taxipoint on an arrival
           TAXIROUTE                                 (TP_5, T=217.3, S=10.0, W=1.0)->   (which is not an exit point), the DNS
              RUNWAY R27                             (TP_3, T=349.6, S=10.0)->          will calculate the exit point based on
              TAXIPOINT TP_3                         (TP_6, T=460.4, S=10.0)->          deceleration distance (as with no
              GATE A                                 (TP_2, T=593.4, S=10.0)->          intermediate points).
           END                                       (TP_4, T=713.3, S=10.0)->
                                                     (A, T=829.9, S=0.0)                The DNS will construct a route from
           (Note also that the associated                                               the exit point to the intermediate
           primary flight plan lists the weight of                                      point, and then to the gate.
           this aircraft as LIGHT).
                                                                                        The navigation script will check to
                                                                                        make sure that the various directions
                                                                                        are allowed for each leg – the step
                                                                                        TP5->TP3 is allowed for arrivals, but
                                                                                        the reverse journey TP3->TP5 is not.

DNS_5      AIRPORTARRIVAL DNS_5                      (RP_1, T=0.0, S=10.0)->            The DNS obtains the weight of the
           TAXI_SPEED 10                             (TP_1, T=128.5, S=10.0)->          aircraft from the primary flight plan,
           TAXIROUTE                                 (TP_5, T=249.0, S=10.0, W=1.0)->   and uses this information to
              RUNWAY R27                             (TP_3, T=381.4, S=10.0)->          determine if the aircraft can travel
              TAXIPOINT TP_3                         (TP_6, T=492.2, S=10.0)->          over each taxiway.
              GATE A                                 (TP_2, T=625.1, S=10.0)->
           END                                       (TP_4, T=745.0, S=10.0)->          Note that the flight plans for this test
                                                     (A, T=861.6, S=0.0)                and DNS_6 are almost the same
           (Note also that the associated                                               here as DNS_4, but as the weight
           primary flight plan lists the weight of                                      changes in each test, the appropriate
           this aircraft as MEDIUM).                                                    taxiway from the test scenario
                                                                                        becomes disallowed.
                                                                                        This also confirms that when there is
                                                                                        no valid route from the first runway
                                                                                        exit point, it will use the next possible
                                                                                        runway exit point (R27).


STATUS                                                                                                           TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                      f7919ee3-d7fb-4de6-9213-
                                                             1719658e70fc.doc

                                                           Page : 17 of 197

                                                                                  EUROCONTROL



DNS_6      AIRPORTARRIVAL DNS_6                      No route found,                     The DNS obtains the weight as
           TAXI_SPEED 10                             start point = RP_5                  heavy, and uses this to deduce there
           TAXIROUTE                                                                     is no possible route.
              RUNWAY R27
              TAXIPOINT TP_3 WAIT 5                                                      This is because, when leaving
                             SPEED 6                                                     specified point TP_3, the journey to
              GATE A                                                                     TP_5 is barred as this direction is not
           END                                                                           allowed for arrivals, and the journey
                                                                                         to TP_6 is barred, as this path is not
           (Note also that the associated                                                allowed for heavy aircraft. As such,
           primary flight plan lists the weight of                                       there is no valid route from TP_3 to
           this aircraft as HEAVY).                                                      gate A.
                                                                                         When there is no possible route, the
                                                                                         navigation      script   returns    this
                                                                                         information, and notes a default point
                                                                                         (the first point on the flight plan) for
                                                                                         the aircraft to wait at.

DNS_7      AIRPORTDEPARTURE DNS_7                    (B, T=0.0, S=9.0)->                 DNS correctly calculates the route for
           TAXI_SPEED 10                             (TP_5, T=149.2, S=9.0, W=1.0)->     a simple departure.
           TAXIROUTE                                 (TP_3, T=296.1, S=9.0)->
              GATE B SPEED 9                         (RP_5, T=445.3, S=0.0)              In the absence of intermediate
              RUNWAY R27                                                                 constraints, the aircraft will move to
           END                                                                           the start of the runway, in order to
                                                                                         maximise takeoff distance.
           (Note also that the associated
           primary flight plan lists the weight of                                       As the DNS obtains the weight as
           this aircraft as HEAVY).                                                      heavy, it cannot travel from TP_6 to
                                                                                         TP_3. Instead, it goes via TP_5.

                                                                                         Also checks that a speed on the gate
                                                                                         will override the flight plan speed for
                                                                                         the route.
DNS _8     AIRPORTDEPARTURE DNS_8                    (B, T=0.0, S=10.0)->                When processing departures, if there
           TAXI_SPEED 10                             (TP_6, T=110.6, S=10.0)->           are intermediate constraints, and the
           TAXIROUTE                                 (TP_2, T=243.6, S=10.0)->           last one is a runway entry point, the
              GATE B                                 (RP_3, T=351.1, S=0.0, W=10.0)      DNS will connect the gate to this
              TAXIPOINT RP_3 WAIT 10                                                     point.
                             SPEED 16
              RUNWAY R27                                                                 Note there is a pause on this point,
           END                                                                           so even though it is on the runway, it
                                                                                         will wait for 10s.
DNS_9      AIRPORTDEPARTURE DNS_9                    P>                                  When processing departures, if there
           TAXI_SPEED 10                             (B, T=0.0, S=10.0)->                are intermediate constraints, but the
           PUSHBACK                                  (TP_5, T=134.3, S=10.0, W=1.0)->    last constraint is not an entry point for
           TAXIROUTE                                 (TP_3, T=266.6, S=10.0, W=15.0)->   this runway, the DNS will use the first
              GATE B                                 (RP_4, T=387.6, S=0.0)              runway entry point, to give the aircraft
              TAXIPOINT TP_3 WAIT 15                                                     the maximum possible takeoff
              RUNWAY R27                                                                 distance.
           END
                                                                                         The DNS successfully adds pauses
                                                                                         to intermediate constraints where
                                                                                         specified.

                                                                                         Note also that when the departure
                                                                                         gate has a pushback listed, it will
                                                                                         respect (and mention) that pushback
                                                                                         in the navigation script (indicated as
                                                                                         “P>”)
DNS_10     AIRPORTDEPARTURE DNS_10                   (A, T=0.0, S=10.0)->                Where there is a delay listed on the
           TAXI_SPEED 10                             (TP_5, T=132.2, S=10.0, W=2.0)->    airspace for a point, and also a delay
           TAXIROUTE                                 (TP_3, T=265.6, S=10.0)->           listed in the flight plan, the flight plan
              GATE A                                 (RP_5, T=399.8, S=0.0)              delay overrides the airspace delay.
              TAXIPOINT TP_5 WAIT 2
              RUNWAY R27
           END
DNS_11     VEHICLEPLAN DNS_11                        (TP_4, T=0.0, S=0.0)                The DNS will successfully handle
           ACTIVATION "08:06:40"                                                         single-point flight plans for vehicles.
           ORIGIN      EHAM
           SIZE        LIGHT

STATUS                                                                                                             TITLE
Company Ref.                                                                                   Template : Normal.dotm
                                                               f7919ee3-d7fb-4de6-9213-
                                                                      1719658e70fc.doc

                                                                     Page : 18 of 197

                                                                                                      EUROCONTROL



                  TYPE        ambulance
                  TAXIROUTE
                     TAXIPOINT TP_4
                  END
DNS_12            VEHICLEPLAN DNS_12                        (TP_4,    T=0.0, S=10.0, W=5.0)->                 Simple vehicle plan traveling from
                  ACTIVATION "08:07:20"                     (TP_2,    T=124.9, S=10.0)->                      TP_4 to TP_3. In this case, the three
                  ORIGIN      EHAM                          (TP_5,    T=234.6, S=10.0, W=1.0)->               most efficient routes are:
                  SIZE        LIGHT                         (TP_3,    T=366.9, S=0.0)
                  TYPE        ambulance                                                                       TP_4, TP_2, TP_5, TP_3 (3608m)
                  TAXI_SPEED 10                                                                               TP_4, TP_2, TP_6, TP_3 (3636m)
                  TAXIROUTE                                                                                   TP_4, A, TP_5, TP_3 (3799m)
                     TAXIPOINT TP_4 WAIT 5
                     TAXIPOINT TP_3                                                                           Although the second possible plan
                  END                                                                                         avoids TP_5, the inherent delay is
                                                                                                              only 1s (equivalent to an extra 10m
                                                                                                              on each other plan). This means that
                                                                                                              this order is maintained whether
                                                                                                              searching by distance or by time. The
                                                                                                              DNS successfully finds the best path.
DNS_13             VEHICLEPLAN DNS_13                        (TP_4, T=0.0, S=10.0)->                          Where a NOT_VIA constraint is listed
                   ACTIVATION "08:08:00"                     (A, T=116.6, S=10.0)->                           between two taxipoints in a flight
                   ORIGIN           EHAM                     (TP_5, T=248.8, S=10.0, W=1.0)->                 plan, the resulting script will not pass
                   SIZE             LIGHT                    (TP_3, T=381.1, S=0.0)                           through this point.
                   TYPE             ambulance
                   TAXI_SPEED 10                                                                              This has the same start and end
                   TAXIROUTE                                                                                  point as TEST_12, but it specifies
                       TAXIPOINT TP_4                                                                         that you can't visit TP_2. As a result,
                       NOT_VIA        TP_2                                                                    it goes via gate A instead.
                       TAXIPOINT TP_3
                   END
Tests 14-20 are used to confirm correct usage of NOT_VIA constraints, with specific respect to obtaining runway entry/exit points. The normal
calculation for these points is to search for a constraint adjacent to the runway, and use this point to determine which runway entry/exit point is
optimal. However, if the adjacent point is a NOT_VIA point, it should not be used at this point of the calculation.

When actually determining the route, the NOT_VIA constraint does have its normal effect, however – once the runway entry/exit point is
determined, the DNS will not return a route, which goes through a NOT_VIA point. It is because of this relationship that there are a number of
tests to confirm that all aspects are working correctly.
DNS_14             AIRPORTDEPARTURE DNS_14                (A, T=0.0, S=10.0)->                            Correct departure behaviour with a
                   TAXI_SPEED 10                          (TP_4, T=116.6, S=10.0)->                       NOT_VIA constraint, but no other
                   TAXIROUTE                              (TP_2, T=236.5, S=10.0)->                       intermediate constraints (DNS
                       GATE A                             (TP_6, T=369.4, S=10.0)->                       ignores NOT_VIA constraint) and
                       NOT_VIA TP_5                       (TP_3, T=480.2, S=10.0)->                       moves aircraft to the start of the
                       RUNWAY R27                         (RP_5, T=614.5, S=0.0)                          runway
                   END
DNS_15             AIRPORTARRIVAL DNS_15                  (RP_3, T=0.0, S=10.0)->                         Correct arrival behaviour with a
                   TAXI_SPEED 10                          (TP_2, T=107.6, S=10.0)->                       NOT_VIA constraint, but no other
                   TAXIROUTE                              (TP_5, T=217.3, S=10.0, W=1.0)->                intermediate constraints (DNS
                       RUNWAY R27                         (A, T=350.5, S=0.0)                             ignores the NOT_VIA point and
                       NOT_VIA TP_4                                                                       moves aircraft to the first runway exit
                       GATE A                                                                             point after decelerating)
                   END

DNS_16            AIRPORTARRIVAL DNS_16                     (RP_4, T=0.0, S=10.0)->                           Correct arrival behaviour with a
                  TAXI_SPEED 10                             (TP_3, T=106.0, S=10.0)->                         NOT_VIA constraint immediately
                  TAXIROUTE                                 (TP_6, T=216.8, S=10.0)->                         before a non-runway intermediate
                     RUNWAY R27                             (TP_2, T=349.8, S=10.0)->                         constraint (DNS avoids the NOT_VIA
                     TAXIPOINT RP_4                         (TP_4, T=469.7, S=10.0)->                         point and , then directs the aircraft to
                     NOT_VIA TP_5 WAIT 3                    (A, T=586.3, S=0.0)                               the intermediate constraints)
                                  SPEED 8
                     TAXIPOINT TP_3                                                                           .
                     GATE A
                  END                                                                                         Speed and Wait constraints on
                                                                                                              NOT_VIA points are ignored.


DNS_17            AIRPORTARRIVAL DNS_17                     (RP_3, T=0.0, S=10.0)->                           Correct arrival behaviour with a
                  TAXI_SPEED 10                             (TP_2, T=107.6, S=10.0)->                         NOT_VIA constraint immediately
                  TAXIROUTE                                 (TP_5, T=217.3, S=10.0, W=1.0)->                  after a non-runway intermediate
                     RUNWAY R27                             (TP_3, T=349.6, S=9.0, W=3.0)->                   constraint (NOT_VIA constraint has
                     TAXIPOINT TP_3 WAIT 3                  (TP_6, T=475.8, S=9.0)->                          no relevance to determining runway
                                    SPEED 9                 (B, T=598.7, S=9.0)->                             exit point, DNS moves aircraft to the
STATUS                                                                                                                                 TITLE
Company Ref.                                                                                                         Template : Normal.dotm
                                                      f7919ee3-d7fb-4de6-9213-
                                                             1719658e70fc.doc

                                                           Page : 19 of 197

                                                                                  EUROCONTROL



               NOT_VIA TP_2           WAIT 2         (TP_5, T=747.9, S=9.0, W=1.0)->    first valid runway exit point after
                                      SPEED 8        (A, T=895.8, S=0.0)                decelerating)
              GATE A
           END                                                                          After leaving the runway at the most
                                                                                        convenient point (after deceleration),
                                                                                        the aircraft will go via any
                                                                                        TAXIPOINTS, while avoiding the
                                                                                        NOT_VIA points, until it reaches its
                                                                                        gate.
DNS_18     AIRPORTARRIVAL DNS_18                     (RP_3, T=0.0, S=10.0)->            Correct arrival behaviour with a
           ORIGIN      LHHR                          (TP_2, T=107.6, S=10.0)->          NOT_VIA runway-based constraint
           TAXI_SPEED 10                             (TP_6, T=240.5, S=10.0)->          immediately before a non-runway
           TAXIROUTE                                 (B, T=351.1, S=10.0)->             intermediate constraint (DNS ignores
              RUNWAY R27                             (TP_5, T=485.4, S=10.0, W=1.0)->   the NOT_VIA point and moves
              NOT_VIA RP_2                           (A, T=618.6, S=0.0)                aircraft to the first runway exit point
              TAXIPOINT TP_6                                                            after deceleration, then directs it to
              GATE A                                                                    the intermediate constraint)
           END

DNS_19     AIRPORTARRIVAL DNS_19                     (RP_4, T=0.0, S=10.0)->            Correct arrival behaviour with a
           ORIGIN      LHHR                          (TP_3, T=106.0, S=10.0)->          NOT_VIA runway-based constraint
           TAXI_SPEED 10                             (TP_6, T=216.8, S=10.0)->          immediately before a runway-based
           TAXIROUTE                                 (TP_2, T=349.8, S=10.0)->          intermediate constraint (DNS ignores
              RUNWAY R27                             (TP_4, T=469.7, S=10.0)->          the NOT_VIA exit point and moves
              NOT_VIA RP_2                           (A, T=586.3, S=0.0)                aircraft to the actual exit point)
              TAXIPOINT RP_4
              GATE A
           END
DNS_20     AIRPORTARRIVAL DNS_20                     (RP_1, T=0.0, S=10.0)->            When determining the runway exit
           ORIGIN      LHHR                          (TP_1, T=128.5, S=10.0)->          point, the DNS will use performance
           TAXI_SPEED 10                             (TP_4, T=239.4, S=10.0)->          data of the aircraft to calculate how
           TAXIROUTE                                 (A, T=355.9, S=0.0)                long the aircraft will take to
              RUNWAY R27                                                                decelerate.
              GATE A
           END
                                                                                        This calculation is performed using
           (Note also that this flight is listed
                                                                                                      v2
                                                                                                      2
                                                                                                        u
           with a different performance profile
           to other aircraft – all aircraft so far                                               s 
                                                                                                   td
           are listed as MFTR type, but this is                                                        2a
           B737)                                                                        With the following values:
                                                                                        td: Runway-based threshold distance
                                                                                        v: Route taxi speed
                                                                                        u: Touch down speed
                                                                                        a: Dry runway deceleration


                                                                                        For a MFTR aircraft (all aircraft-
                                                                                        based tests up to this one), this
                                                                                        equation becomes
                                                                                                   2
                                                                                                     2
                                                                                                  10350
                                                                                                
                                                                                              s 50
                                                                                                   2
                                                                                                    *50
                                                                                        Thus, the deceleration distance is
                                                                                        1274m. The first runway exit point
                                                                                        after 1274m is RP_3 (1558m) –
                                                                                        which is why arrivals have typically
                                                                                        left the runway at RP_3.


                                                                                        However, this arrival is a B737
                                                                                        aircraft. For this aircraft, the
                                                                                        deceleration distance is:
                                                                                                   2
                                                                                                     2
                                                                                                  10200
                                                                                                
                                                                                              s 50
                                                                                                   2
                                                                                                    *10
                                                                                        This value is 2045m. The first runway
                                                                                        exit point located after 2045m is
                                                                                        RP_2, however this point has no
                                                                                        acceptable paths out of it – the path
STATUS                                                                                                           TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                      f7919ee3-d7fb-4de6-9213-
                                                             1719658e70fc.doc

                                                              Page : 20 of 197

                                                                                   EUROCONTROL



                                                                                        to TP_1 is barred for arrivals.
                                                                                        Because of this, the DNS makes the
                                                                                        aircraft leave the runway at RP_1
DNS_21     VEHICLEPLAN DNS_21                        (TP_0,   T=0.0, S=10.0)->          If specified in the flight plan, the
           ACTIVATION "08:14:00"                     (TP_1,   T=81.2, S=10.0)->         resulting route will repeat, but not
           ORIGIN      EHAM                          (RP_1,   T=209.7, S=10.0)->        double back.
           SIZE        LIGHT                         (TP_0,   T=315.7, S=10.0)->
           TYPE        ambulance                     (TP_1,   T=396.9, S=10.0)->
           TAXI_SPEED 10                             (RP_1,   T=525.5, S=10.0)->
           TAXIROUTE                                 (TP_0,   T=631.4, S=10.0)->
              TAXIPOINT TP_0                         (TP_1,   T=712.6, S=10.0)->
              TAXIPOINT TP_1                         (RP_1,   T=841.2, S=10.0)->
              TAXIPOINT RP_1                         (TP_0,   T=947.1, S=10.0)->
              TAXIPOINT TP_0                         (TP_1,   T=1,028.4, S=0.0)
              TAXIPOINT TP_1
              TAXIPOINT RP_1
              TAXIPOINT TP_0
              TAXIPOINT TP_1
              TAXIPOINT TP_0
              TAXIPOINT TP_1
           END
DNS_22     AIRPORTDEPARTURE DNS_22                   (A, T=0.0, S=10.0)->               The DNS will search for the first valid
           TAXI_SPEED 10                             (TP_5, T=132.2, S=10.0, W=1.0)->   entry point – if there is no valid route
           TAXIROUTE                                 (TP_3, T=264.6, S=10.0)->          to the first runway entry point, it will
              GATE A                                 (RP_4, T=370.6, S=0.0)             try the second runway entry point,
              RUNWAY R27                                                                and so on.
           END

           (Note also that the associated
           primary flight plan lists the weight of
           this aircraft as LIGHT).




STATUS                                                                                                          TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                     Page : 21 of 197

                                                                               EUROCONTROL




     5     TPM COMPONENT TESTS

     5.1    Arrivals

     5.1.1 CT_TPM_ARR_01 – Standard Arrival Test
Scenario ID               CT_TPM_ARR_01
SRD Reference             G170, 110, 490, 500, 510, 2006TWR220, 150, 370, 380
Objective                 Demonstrate correct standard behaviour for an arrival – that the aircraft will
                          decelerate in a sensible manner, and leave the runway at an appropriate point,
                          then travel the best route possible to the designated gate.
Dependencies              None
Resource File             <component test home>/tpm/arrival/arrival.gsdk


ID   Time       Actions                Expectations
1    16:12:00   Launch CWP.            AVD appears with map of LFPG
                Commence          at
                normal speed.
2                                      Aircraft LFPG_ARR appears on runway R27L, travelling in westerly
                                       direction.
                                       Aircraft decelerates
3                                      Aircraft leaves runway at TP_85 at a constant speed.
4                                      Aircraft follows the following route to the apron:
                                       TP_85, TP_80, TP_58, TP_360, TP_1130, TP_488, TP_305,
                                       TP_1202, TP_1198, TP_1003, TP_1459
5                                      Aircraft reaches apron (TP_1459), and travels along it at a
                                       significantly slower pace. Moves towards gate EN_20
6                                      Aircraft arrives at gate EN_20, and pauses
7    16:17:16                          Aircraft disappears

     5.1.2 CT_TPM_ARR_02 – Specified Exit Arrival Test
Scenario ID               CT_TPM_ARR_02
SRD Reference             G170, 110, 490, 500, 510, 520, 2006TWR220, 150, 370, 380
Objective                 Demonstrate that where requested, the aircraft will leave the runway at a specified
                          point.
Dependencies              None
Resource File             <component test home>/tpm/arrival/arrival_exit_at.gsdk


ID   Time       Actions                Expectations
1    16:12:00   Launch CWP.            AVD appears with map of LFPG

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                     Page : 22 of 197

                                                                               EUROCONTROL



                Commence          at
                normal speed.
2                                      Aircraft LFPG_ARR appears on runway R27L, travelling in westerly
                                       direction.
                                       Aircraft decelerates
3                                      Aircraft leaves runway at TP_1338.
4                                      Aircraft follows the following route to the apron:
                                       TP_1338, TP_1330, TP_1082, TP_309, TP_303, TP_308, TP_1202,
                                       TP_1198, TP_1003, TP_1459
5                                      Aircraft reaches apron (TP_1459), and travels along it at a
                                       significantly slower pace. Moves towards gate EN_20
6                                      Aircraft arrives at gate EN_20, and pauses
7    16:16:13                          Aircraft disappears




     5.1.3 CT_TPM_ARR_03 – Failed Deceleration Arrival Test
Scenario ID               CT_TPM_ARR_03
SRD Reference             G170, 110, 490, 500, 510, 2006TWR220, 150, 370, 380
Objective                 Demonstrate that where the aircraft is not able to decelerate in time for any point
                          on the runway, the TPM will raise an error to notify the user, and use the last
                          possible point on the runway as a starting point for the route.
Dependencies              None
Resource File             <component test home>/tpm/arrival/arrival_fail.gsdk


ID   Time       Actions                Expectations
1    16:12:00   Launch CWP.            AVD appears with map of LFPG
                Commence          at
                normal speed.
2                                      Aircraft LFPG_ARR appears on runway R27L, travelling in westerly
                                       direction.
                                       Aircraft decelerates slowly
3                                      Aircraft leaves runway at TP_15.
                                       Error message appears on console window: “LFPG_ARR exits too
                                       fast (119.8m/s) from runway at TP_15”
4                                      Aircraft follows the following route to the apron:
                                       TP_15, TP_20, TP_309, TP_303, TP_308, TP_1202, TP_1198,
                                       TP_1003, TP_1459
5                                      Aircraft reaches apron (TP_1459), and travels along it at a
                                       significantly slower pace. Moves towards gate EN_20
6                                      Aircraft arrives at gate EN_20, and pauses

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                          f7919ee3-d7fb-4de6-9213-
                                                 1719658e70fc.doc

                                               Page : 23 of 197

                                                                         EUROCONTROL



7    16:14:49                    Aircraft disappears




     5.1.4 CT_TPM_ARR_04 – Arrival Fast Runway Exit Test
Scenario ID          CT_TPM_ARR_04
SRD Reference        G170, 110, 490, 500, 510, 2006TWR220, 150, 370, 380
Objective            Demonstrate that where the aircraft has not decelerated to its taxi speed, but the
                     DNS.FAST_EXIT flag is set to true, the TPM will not raise an error.
Dependencies         None
Resource File        <component test home>/tpm/arrival/arrival_fast_exit.gsdk


ID    Time       Actions            Expectations
1.    16:12:00   Launch CWP.        AVD appears with map of LFPG
                 Commence      at
                 normal speed.
2.                                  Aircraft LFPG_ARR appears on runway R27, travelling in westerly
                                    direction.
                                    Aircraft decelerates
3.                                  Aircraft leaves runway at TP_220.
                                    TPM message (not error) appears on console                    window:
                                    “LFPG_ARR fast (30.9m/s) runway exit at TP_220”
4.                                  Aircraft follows the following route to the apron:
                                    TP_220, TP_219, TP_213, TP_217, TP_615, TP_616, TP_337,
                                    TP_338, TP_339, TP_584, TP_585, TP_200, TP_199, TP_1002,
                                    TP_1003, TP_1459
5.                                  Aircraft decelerates maintains 60 knots while taxiing before
                                    decelerating down to normal taxi speeds of 15, 19 or 20 knots.
6.                                  Aircraft reaches apron (TP_1459), and travels along it at a
                                    significantly slower pace. Moves towards gate EN_20
7.                                  Aircraft arrives at gate EN_20, and pauses
8.    16:18:14                      Aircraft disappears




     5.1.5 CT_TPM_ARR_05 – Arrival No Route Test
Scenario ID          CT_TPM_ARR_05
SRD Reference
Objective            Demonstrate that where there is no possible route for an arrival, TPM will raise an

STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 24 of 197

                                                                             EUROCONTROL



                          error, and no flights will appear on the AVD.
Dependencies              None
Resource File             <component test home>/tpm/arrival/arrival_no_route.gsdk


ID   Time       Actions                  Expectations
1    16:12:00   Launch CWP.              AVD appears with map of LFPG
                Commence at normal
                speed.
2    16:12:00                            Message appears on console window: “No route found starting
                                         from TP_220 for LFPG_ARR”


3    16:19:00                            No flights have appeared



     5.1.6 CT_TPM_ARRXASAP_01 – Arrivals Leave Runway By First Available Exit
           Point.
Scenario ID               CT_TPM_ARRXASAP_01
SRD Reference             2005APT90
Objective                 Scenario demonstrates that an arrival will leave the designated runway by the first
                          available runway exit point, unless it has been instructed to leave by a specified
                          exit point.
Dependencies              None
Resource File             <component test home>/tpm/arrival/leaveRwyASAP.gsdk


ID   Time       Actions          Expectations
                                 Note leaveRwyASAP_traffic.dat specifies five arrivals.
                                 ARR1 will take the default runway exit.
                                 ARR2 will exit at TP_764.
                                 ARR3 will exit at TP_27.
                                 ARR4 will exit at TP_32.
                                 ARR5 will exit at TP_35.
                                 All are destined for stand EN21.
1    16:12:00   Launch and run   One AVD RWY_N and one PVD LFPG appear.
                scenario.
                ARR1 lands.      Check planned route leaves runway at TP_27 to taxi to EN21.
                ARR2 lands.      Check planned route leaves runway at TP_764 to taxi to EN21.
                ARR3 lands.      Check planned route leaves runway at TP_27 to taxi to EN21.
                ARR4 lands.      Check planned route leaves runway at TP_32 to taxi to EN21.


STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                       Page : 25 of 197

                                                                                 EUROCONTROL



                ARR5 lands.         Check planned route leaves runway at TP_35 to taxi to EN21.
                ARR2    leaves      Log states that ARR2 has left the runway but speed was greater than
                runway.             required taxi.
                Check console
                log.
                                    Conclusion:
                                    Due to aircraft performance deceleration rate ARR1 can not exit runway at
                                    first exit point TP_764 but has left at first available exit point TP_27.
                                    The route leaving this exit point is longer than the other available exit point
                                    routes.




     5.1.7 CT_TPM_ARRXASAP_02 – Arrival Fast Runway Exits.
Scenario ID                CT_TPM_ARRXASAP_02
SRD Reference              2005APT90
Objective                  Scenario demonstrates that the use of the FAST_EXIT flag changes the optimal
                           runway exit for an aircraft. This flag indicates that an aircraft can leave the runway
                           at a faster speed than its preferred taxi speed so long as it can meet the maximum
                           speed limit for the exit taxiway.
Dependencies               None
Resource File              <component test home>/tpm/arrival/fast_exit_false.gsdk
                           <component test home>/tpm/arrival/fast_exit_true.gsdk


ID   Time       Actions             Expectations
                Inspect the         Note the following parameters specified in the resource file:
                resource file
                                    DNS.FAST_EXIT FALSE
                fast_exit_false.g
                                    DNS.FAST_EXIT_TOLERANCE 1.0
                sdk
                                    Note that the leaveRWY_fast_exit_traffic.dat specifies one arrival which
                                    leaves the runway at its default exit point.
1    16:12:00   Launch and run      One AVD RWY_N and one PVD LFPG appear.
                scenario.
                ARR1 lands and      Check planned route leaves runway at TP_27 (the second available exit)
                leaves the          to taxi to EN21.
                runway.
                End scenario
                Inspect the         Note the following parameters specified in the resource file:
                resource file
                                    DNS.FAST_EXIT TRUE
                fast_exit_true.g
                                    DNS.FAST_EXIT_TOLERANCE 1.0
                sdk
2    16:12:00   Launch and run      One AVD RWY_N and one PVD LFPG appear.
                scenario.


STATUS                                                                                                      TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 26 of 197

                                                                                EUROCONTROL



                ARR1 lands and     Check planned route leaves runway at TP_764 (the first available exit) to
                leaves the         taxi to EN21.
                runway.
                                   Message appears in the console log: “ARR1 fast (30.9m/s) runway exit at
                                   TP_764”
                End scenario
                                   Conclusion:
                                   Due to aircraft performance deceleration rate, ARR1 can not exit the
                                   runway at the first exit point TP_764 as it will not have decelerated to its
                                   preferred taxi speed, it therefore leaves at the next available exit point
                                   TP_27. However with fast exits enabled, the aircraft is able to decelerate
                                   to a speed within the first exit taxiway‟s speed limit.



     5.1.8 CT_TPM_ARRXASAP_03 – Arrival Fast Runway Exits With Tolerance.
Scenario ID                CT_TPM_ARRXASAP_03
SRD Reference              2005APT90
Objective                  Scenario demonstrates that with the use of the FAST_EXIT flag and the
                           FAST_EXIT_TOLERANCE, an aircraft may leave the runway at a higher speed
                           than the maximum speed limit for that taxiway.
                           This test uses a resource file with a modified speed limit to create the required test
                           criteria.
Dependencies               None
Resource File              <component test home>/tpm/arrival/fast_exit_notolerance.gsdk
                           <component test home>/tpm/arrival/fast_exit_withtolerance.gsdk


ID   Time       Actions            Expectations
                Inspect the        Note 1: the following parameters are specified in the resource file:
                resource file
                                   DNS.FAST_EXIT TRUE
                fast_exit_notole
                                   DNS.FAST_EXIT_TOLERANCE 1.0
                rance.gsdk
                                   Note 2: the resource file specifies the modified taam data resource file
                                   /twr/resources/scenarios/tpm/arrival/lfpg_taam_airport_fastexit.dat. This
                                   has set the maximum speed limit for taxiway twy_clz4_1 to be 35.0 kts.
                                   Note 3: leaveRwy_fast_exit_traffic.dat specifies one arrival leaving at the
                                   default exit point.
1    16:12:00   Launch and run     One AVD RWY_N and one PVD LFPG appear.
                scenario.
                ARR1 lands and     Check planned route leaves runway at TP_27 (the second available exit)
                leaves the         to taxi to EN21.
                runway
                                   Message appears in the console log: “ARR1 fast (30.9m/s) runway exit at
                                   TP_27”
                End scenario
                Inspect the        Note 1: the following parameters are specified in the resource file:
                resource file
                                   DNS.FAST_EXIT TRUE
STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                        Page : 27 of 197

                                                                                 EUROCONTROL



                fast_exit_withtol   DNS.FAST_EXIT_TOLERANCE 1.05
                erance.gsdk
                                    Note 2: the resource file specifies the modified taam data resource file
                                    /twr/resources/scenarios/tpm/arrival/lfpg_taam_airport_fastexit.dat. This
                                    has set the maximum speed limit for taxiway twy_clz4_1 to be 35.0 kts.
                                    Note 3: leaveRwy_fast_exit_traffic.dat specifies one arrival leaving at the
                                    default exit point.
2    16:12:00   Launch and run      One AVD RWY_N and one PVD LFPG appear.
                scenario.
                ARR1 lands and      Check planned route leaves runway at TP_764 (the first available exit) to
                leaves the          taxi to EN21.
                runway
                                    Message appears in the console log: “ARR1 fast (18.1m/s) runway exit at
                                    TP_764”
                End scenario
                                    Conclusion:
                                    The aircraft is unable to decelerate to a speed of 35 kts (i.e. the speed
                                    limit for the first exit) so therefore takes the second (longer) route, however
                                    with a 5% tolerance set on the speed limit, the aircraft can reach that
                                    speed and hence take the first exit.



     5.2    Departures

     5.2.1 CT_TPM_DEP_01 – Standard Departure Test
Scenario ID                CT_TPM_DEP_01
SRD Reference              G30, G50, G60, 130, 360, 2006TWR220, G70, 390, 120, 440, 450, 460, 470, 480
Objective                  Demonstrate correct standard behaviour for a departure – that the aircraft will
                           travel the best possible route from the designated gate to the start of the runway,
                           then accelerate along the runway until it reaches takeoff speed, at which point it
                           leaves the TWR system.
Dependencies               None
Resource File              <component test home>/tpm/departure/departure.gsdk


ID   Time       Actions             Expectations
1    16:12:00   Launch CWP.         AVD appears with map of LFPG
                Commence at
                normal speed.
2                                   Aircraft LFPG_DEP appears at gate V4.
3                                   Aircraft begins to taxi.
                                    Aircraft follows the following route to the runway:
                                    TP_2137, TP_2140, TP_1215, TP_1214, TP_1212, TP_333, TP_334,
                                    TP_561, TP_562, TP_935, TP_1442, TP_673, TP_70, TP_71, TP_74,
                                    TP_314, TP_313, TP_312, TP_311, TP_310, TP_302, TP_239, TP_233,
                                    TP_232, TP_1185

STATUS                                                                                                      TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                      Page : 28 of 197

                                                                               EUROCONTROL



4    16:20:32                     Aircraft accelerates in direction of runway and disappears.




     5.2.2 CT_TPM_DEP_02 – Specified Runway Entry Departure Test
Scenario ID               CT_TPM_DEP_02
SRD Reference             G30, G50, G60, 130, 360, 2006TWR220, G70, 390, 120, 440, 450, 460, 470, 480
Objective                 Demonstrate that where specified, the aircraft will enter the runway at a specified
                          point.
Dependencies              None
Resource File             <component test home>/tpm/departure/departure_enter_at.gsdk


ID   Time       Actions           Expectations
1    16:12:00   Launch CWP.       AVD appears with map of LFPG
                Commence at
                normal speed.
2                                 Aircraft LFPG_DEP appears at gate V4.
3                                 Aircraft begins to taxi.
                                  Aircraft follows the following route to the runway:
                                  TP_2137, TP_2140, TP_1215, TP_1214, TP_1212, TP_333, TP_334,
                                  TP_561, TP_562, TP_935, TP_1442, TP_673, TP_1127, TP_1257,
                                  TP_1107, TP_466, TP_464, TP_1314, TP_915, TP_801, TP_447,
                                  TP_450, TP_456, TP_461
4    16:19:06                     Aircraft accelerates in direction of runway and disappears.



     5.2.3 CT_TPM_DEP_03 – Failed Acceleration Departure Test
Scenario ID               CT_TPM_DEP_03
SRD Reference             G30, G50, G60, 130, 360, 2006TWR220, G70, 390, 120, 440, 450, 460, 470, 480
Objective                 Demonstrate that where the aircraft is not able to accelerate in time to take off, the
                          TPM will notify the user, and take off anyway.
Dependencies              None
Resource File             <component test home>/tpm/departure/departure_fail.gsdk


ID   Time       Actions           Expectations
1    16:12:00   Launch CWP.       AVD appears with map of LFPG
                Commence at
                normal speed.
2                                 Aircraft LFPG_DEP appears at gate V4, and begins to taxi.


STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                      Page : 29 of 197

                                                                              EUROCONTROL



3                                Aircraft starts to taxi.
                                 Aircraft follows the following route to the runway:
                                 TP_2137, TP_2140, TP_1215, TP_1214, TP_1212, TP_333, TP_334,
                                 TP_561, TP_562, TP_935, TP_1442, TP_673, TP_70, TP_71, TP_74,
                                 TP_314, TP_313, TP_312, TP_311, TP_310, TP_302, TP_239, TP_233,
                                 TP_232, TP_1185
4    16:21:57                    Aircraft accelerates very slightly.
                                 Console log prints “ERROR - LFPG_DEP will not attain take-off speed by
                                 end of runway R27”
                                 Aircraft disappears at end of runway.



     5.2.4 CT_TPM_DEP_04 – Departure No Route Test
Scenario ID               CT_TPM_DEP_04
SRD Reference
Objective                 Demonstrate that where there is no possible route for a departure, TPM will raise
                          an error, and no flights will appear on the AVD.
Dependencies              None
Resource File             <component test home>/tpm/departure/departure_no_route.gsdk


ID   Time       Actions                   Expectations
1    16:12:00   Launch CWP.               AVD appears with map of LFPG
                Commence at normal
                speed.
2    16:12:00                             Message appears on console window: “No route found starting
                                          from V4 for LFPG_DEP”
3    16:20:00                             No flights have appeared.




     5.3    Traffic Rules

     5.3.1 CT_TPM_TRA_01 – Speed Test
Scenario ID               CT_TPM_TRA_01
SRD Reference             G40, 290, 310
Objective                 Demonstrate correct speed handling for ground vehicles, and any vehicles
                          following them.
Dependencies              None
Resource File             <component test home>/tpm/trafficrules/speed.gsdk


STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 30 of 197

                                                                               EUROCONTROL



ID   Time       Actions                 Expectations
1    16:12:00   Launch CWP.             AVD appears with map of LFPG
                Commence at normal
                speed.
2                                       Vehicle VAN_SLOW appears at taxipoint TP_978, and begins to taxi
                                        slowly.
3                                       Vehicle VAN_FAST appears at taxipoint TP_978 but does not move.
4                                       VAN_FAST begins to taxi.
5                                       VAN_SLOW reaches taxipoint TP_977, continues to taxi at a faster
                                        rate. VAN_FAST continues slowly.
6                                       VAN_SLOW reaches taxipoint TP_979, and pauses.
7                                       VAN_FAST reaches taxipoint TP_977, speeds up (for a short time)
                                        and queues behind VAN_SLOW.
8                                       VAN_SLOW restarts taxiing at an average rate.
                                        VAN_FAST restarts 2 seconds later, keeping a fixed distance
                                        between it and VAN_SLOW
9                                       VAN_SLOW reaches TP_980 and slows down. VAN_FAST also
                                        slows down to match speed.
10                                      VAN_SLOW reaches TP_507, and pauses. VAN_FAST also
                                        pauses.
11                                      VAN_SLOW restarts, heading north, slowly.
                                        VAN_FAST restarts 2 seconds after VAN_SLOW, also travels
                                        slowly.
12                                      VAN_FAST suddenly speeds up (as VAN_SLOW has cleared the
                                        junction)
13                                      VAN_OPP appears at TP_987, and begins to travel towards
                                        VAN_FAST
14   16:15:33                           VAN_OPP and VAN_FAST stop, VAN_FAST and VAN_OPP close
                                        to TP_981



     5.3.2 CT_TPM_TRA_02 – Priority Test
Scenario ID               CT_TPM_TRA_02
SRD Reference             G110, 330, 290
Objective                 Demonstrate correct priority handling for departing and arriving aircraft.
Dependencies              None
Resource File             <component test home>/tpm/trafficrules/priority.gsdk


ID   Time       Actions                     Expectations
1    07:59:59   Launch CWP.                 AVD appears with map of R27x
                Commence      at   normal
STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                     Page : 31 of 197

                                                                              EUROCONTROL



                speed.
2                                          Flights DEP_1 and DEP_2 appear at the gates A and B
                                           respectively.
3                                          DEP_1 starts to move and taxi to runway.
                                           DEP_2 starts to pushback and then taxis to runway.
5                                          Flight ARR_1 appears, decelerating on runway.
6                                          ARR_1 leaves runway at RP_3, and heads towards TP_2.
                                           DEP_1 and DEP_2 are also heading toward TP_2.
7                                          DEP_1 and DEP_2 wait for ARR_1 to move past TP_2 towards
                                           TP_4.
                                           DEP_1 and DEP_2 restart with DEP_2 in front (DEP_1 gives
                                           way to Right).



     5.3.3 CT_TPM_TRA_03 – Vehicle Test
Scenario ID               CT_TPM_TRA_03
SRD Reference             G110, 330, G40, 340, 290, 310
Objective                 Demonstrate correct priority handling for priority between aircraft and vehicles.
Dependencies              None
Resource File             <component test home>/tpm/trafficrules/vehicle.gsdk


ID   Time       Actions               Expectations
1    07:59:59   Launch CWP.           AVD appears with map of R27x
                Commence         at
                normal speed.
2    08:00:01                         Vehicle VEH_1 appears at TP_6, and starts to taxi towards TP_2.
3    08:01:01                         Flight DEP_1 appears at gate A.
4                                     Flight DEP_1 starts to taxi towards TP_5.
5                                     VEH_1 reaches TP_2, and starts to head towards TP_5.
6                                     DEP_1 waits a short distance from TP_5 to allow VEH_1 to pass.
7    08:04:01                         Flight DEP_2 appears at gate A
8                                     VEH_1 starts moving towards TP_1.
9                                     DEP_2 starts moving towards TP_5.
10                                    DEP_1 restarts movement towards TP_2.
11   08:05:01                         Vehicle VEH_2 appears at TP_6 and starts movement towards TP_2.
12                                    DEP_2 reaches TP_5, pauses for a second, then begins to travel
                                      towards TP_2.
13                                    VEH_2 pauses a short distance from TP_2, and waits for DEP_2 to
                                      pass.

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 32 of 197

                                                                               EUROCONTROL



14                                   DEP_2 passes TP_2.
15                                   VEH_2 restarts moving.
16   08:10:00                        Vehicles VEH_3 and VEH_4 appear and start moving towards TP_5.
                                     Vehicles VEH_5, VEH_6, VEH_7, VEH_8 appear behind VEH_4.
17                                   Vehicle VEH_3 pauses to allow the other 5 vehicles through (they are
                                     coming from the right).
                                     Note VEH_8 pauses for 15s at TP_5.
18                                   When all aircraft have moved off TP_5, VEH_3 restarts



     5.3.4 CT_TPM_TRA_04 – Flight Plan Speed GMS
Scenario ID               CT_TPM_TRA_04
SRD Reference             280
Objective                 Demonstrate that, where specified, the flight plan speed overrides all other speeds
                          (including taxiway speed limits)
Dependencies              None
Resource File             <component test home>/tpm/trafficrules/very_fast.gsdk


ID   Time       Actions                           Expectations
1    16:12:00   Launch    CWP     and    start    AVD window appears, with a view of the tower system.
                Console
                                                  A console window appears.

2                                                 Aircraft pushes back at a significantly faster rate than
                                                  normal


3                                                 Aircraft doubles its speed
4                                                 Aircraft crosses TP_70, decelerates to half its original
                                                  speed.
5                                                 Aircraft accelerates down runway
5    16:17:46                                     Aircraft takes off




     5.4    Queuing Tests

     5.4.1 CT_TPM_QUE_01 – Stopped Traffic Test
Scenario ID               CT_TPM_QUE_01
SRD Reference             G120, 290, 310, 320, 2006TWR230
Objective                 Demonstrate correct behaviour for queuing behind stopped traffic.
Dependencies              None

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 33 of 197

                                                                            EUROCONTROL



Resource File             <component test home>/tpm/trafficrules/queue/stopslowgo.gsdk


ID   Time       Actions                          Expectations
1    16:12:00   Launch CWP.                      AVD appears with map of LFPG
                Commence at normal speed.
2               Open the resources window        Vehicle: 2 seconds
                and       observe      the
                                                 Light: 4 seconds
                TPM.REACTION_TIME
                parameters:                      Medium: 6 seconds
                                                 Heavy: 8 seconds
3    16:12:01                                    Vehicles VAN1, VAN2, and aircraft                DEP_LIGHT,
                                                 DEP_MEDIUM and DEP_HEAVY appear.
4                                                VAN2 begins to move in direction of runway.
5                                                DEP_LIGHT, DEP_MEDIUM and DEP_HEAVY begin to
                                                 move in direction of runway.
6    16:13:45                                    VAN2 and the three aircraft pause behind VAN1.
7    16:14:05                                    VAN1 begins to move.
8                                                VAN2 resumes its course behind VAN1, approximately 2
                                                 seconds after VAN1 started moving.
9                                                DEP_LIGHT resumes its course behind VAN2,
                                                 approximately 4 seconds after VAN2 started moving.
10                                               DEP_MEDIUM resumes its course behind DEP_LIGHT,
                                                 approximately 6 seconds after DEP_LIGHT started moving.
11                                               DEP_HEAVY resumes its course behind DEP_MEDIUM,
                                                 approximately 8 seconds after DEP_MEDIUM started
                                                 moving.
12                                               VAN1 and VAN2 have both turned off the taxiway, onto a
                                                 side road
13                                               The three aircraft speed up, as VAN1 and VAN2 are no
                                                 longer obstructing its path.



     5.4.2 CT_TPM_QUE_02 – Slowed Traffic Test
Scenario ID               CT_TPM_QUE_02
SRD Reference             G120, 290, 310, 320
Objective                 Demonstrate correct behaviour for queuing behind slow traffic.
Dependencies              None
Resource File             <component test home>/tpm/trafficrules/queue/slowdown.gsdk


ID   Time       Actions                       Expectations
1    16:12:00   Launch CWP.                   AVD appears with map of LFPG

STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 34 of 197

                                                                             EUROCONTROL



                Commence at normal speed.
2    16:12:01                                  Vehicle VAN, and aircraft LFPG_DEP appear
3    16:12:04                                  VAN begins to move
3    16:12:13   Issue taxi clearance to        LFPG_DEP begins to move in direction of runway
                LFPG_DEP
4    16:12:54                                  LFPG_DEP slows down behind VAN, remaining a fixed
                                               distance behind VAN.
5    16:13:42                                  VAN turns off the taxiway, onto a side road.
6    16:13:48                                  LFPG_DEP speeds up, as VAN is no longer obstructing its
                                               path.



     5.5    Give Way Tests

     5.5.1 CT_TPM_GIV_01 – Give way to right test
Scenario ID                CT_TPM_ GIV_01
SRD Reference              G110, 330
Objective                  Demonstrate that vehicles will give way to the right when there are two vehicles
                           headed for the same junction.
Dependencies               None
Resource File              <component test home>/tpm/trafficrules/giveway/to_right.gsdk


ID   Time       Actions                       Expectations
1    16:12:00   Launch CWP.                   AVD appears with map of LFPG
                Commence       at    normal
                speed.
2    16:12:01                                 Vehicles VAN_1 and VAN_2 appear
3    16:12:02                                 Both vehicles begin moving towards each other
4    16:12:50                                 VAN_1 pauses to allow VAN_2 to pass. VAN_2 continues
                                              moving.
5    16:12:58                                 VAN_1 restarts, as VAN_2 is no longer obstructing its path.



     5.5.2 CT_TPM_GIV_02 – Give way to departures test
Scenario ID                CT_TPM_ GIV_02
SRD Reference              G110, 330
Objective                  Demonstrate that when an arrival and a departure are approaching the same
                           junction, the arrival will give way to the departure.
Dependencies               None
Resource File              <component test home>/tpm/trafficrules/giveway/to_departure.gsdk

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                   Page : 35 of 197

                                                                           EUROCONTROL




ID   Time       Actions                           Expectations
1    16:12:00   Launch CWP.                       AVD appears with map of LFPG
                Fast forward to 16:14:45, then
                proceed in normal time.
2                                                 Aircraft LFPG_DEP and LFPG_ARR appear, heading in
                                                  the general direction of each other.
3                                                 LFPG_DEP passes TP_481.
4                                                 LFPG_ARR passes TP_359.           Both    aircraft   begin
                                                  travelling towards TP_360.
5                                                 LFPG_ARR pauses to allow LFPG_DEP to pass
                                                  TP_360.
6                                                 LFPG_ARR restarts its journey as LFPG_DEP is no
                                                  longer obstructing its journey.




     5.5.3 CT_TPM_GIV_03 – Give way to aircraft test
Scenario ID               CT_TPM_GIV_03
SRD Reference             G40, 340, 2006TWR230
Objective                 Demonstrate that when an aircraft and a ground vehicle are approaching the
                          same junction, the vehicle will give way to the aircraft.
Dependencies              None
Resource File             <component test home>/tpm/trafficrules/giveway/to_aircraft.gsdk


ID   Time       Actions                     Expectations
1    16:12:00   Launch CWP.                 AVD appears with map of LFPG
                Commence      at   normal
                speed.
2    16:12:03                               Vehicle AMBULANCE appears and starts moving
3    16:14:45                               Aircraft LFPG_DEP appears.
4    16:15:00                               LFPG_DEP begins to move in the direction of the runway
5    16:15:38                               AMBULANCE stops, pausing to allow LFPG_DEP to proceed
6    16:16:17                               AMBULANCE restarts, as LFPG_DEP no longer obstructs its
                                            journey.



     5.6    Traffic Resources

     5.6.1 CT_TPM_RES_01 – Crossing Time Factor Test


STATUS                                                                                                 TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 36 of 197

                                                                              EUROCONTROL



Scenario ID               CT_TPM_RES_01
SRD Reference             G30, G50, G60, 360, 2006TWR220
Objective                 Demonstrate the effect of changing the CROSSING_TIME_FACTOR resource
                          variable from its default value of 2 to 0.
Dependencies              None
Resource File             <component test home>/tpm/resources/crossing_time_factor.gsdk
                          <component test home>/tpm/resources/crossing_time_factor_def.gsdk




ID   Time       Actions                         Expectations
1    07:59:59   Launch                          AVD appears with map of R27x
                crossing_time_factor
                Commence      at       normal
                speed.
2    08:00:01                                   Vehicles VEH_4 and VEH_5 appear and start moving towards
                                                TP_5. Vehicles VEH_6, VEH_7, VEH_8 and VEH_9 appear
                                                behind VEH_5.
3    08:02:13                                   Vehicle VEH_4 crosses TP_5, between the queue of vehicles
                                                (VEH_5,…,VEH_9) and continues towards TP_3.
                                                Vehicles VEH_5, VEH_6, VEH_7, VEH_8 and VEH_9 cross
                                                TP_5 when junction is clear.


1    08:00:00   Launch                          Vehicles VEH_4 and VEH_5 appear and start moving towards
                crossing_time_facter_def        TP_5. Vehicles VEH_6, VEH_7, VEH_8 and VEH_9 appear
                                                behind VEH_5.
2    08:02:11                                   Vehicle VEH_4 pauses to allow the other 5 aircraft through
                                                (they are coming from the right).
3    08:02:39                                   When all aircraft have moved off TP_5, VEH_4 restarts



     5.6.2 CT_TPM_RES_02 – Occupancy Time Test
Scenario ID               CT_TPM_RES_02
SRD Reference             G30, G50, G60, 360, 2006TWR220
Objective                 Demonstrate the effect of changing the DEPARTURE_OCCUPANCY_TIME and
                          ARRIVAL_OCCUPANCY_TIME resource variables from the default value of 12 to
                          60 (seconds).
Dependencies              None
Resource File             <component test home>/tpm/resources/times.gsdk
                          <component test home>/tpm/resources/times_def.gsdk


ID   Time       Actions                     Expectations

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                       Page : 37 of 197

                                                                            EUROCONTROL



1    07:59:59   Launch times.gsdk          AVD appears with map of R27x
                Commence     at   normal
                speed.
2    08:00:02                              Flight DEP appears at gate A,
                                           Flight ARR appears on runway R27
3    08:00:10                              ARR leaves runway at RP_3, takes following route to gate A:
                                           RP_3, TP_2, TP_4, A
4    08:01:03                              DEP leaves gate A, takes following route to runway R27: A,
                                           TP_5, TP_3, RP_5
5    08:04:40                              ARR arrives at gate A
6    08:05:40                              ARR disappears from system.


1    07:59:59   Launch times_def.gsdk      AVD appears with map of R27x
                Commence     at   normal
                speed.
2    08:00:02                              Flight DEP appears at gate A,
                                           Flight ARR appears on runway R27
3    08:00:10                              ARR leaves runway at RP_3, takes following route to gate A:
                                           RP_3, TP_2, TP_4, A
4    08:00:13                              DEP leaves gate A, takes following route to runway R27: A,
                                           TP_5, TP_3, RP_5
5    08:04:39                              ARR arrives at gate A
6    08:04:52                              ARR disappears from system.



     5.6.3 CT_TPM_RES_03 – Junction Congestion Distance Test
Scenario ID               CT_TPM_RES_03
SRD Reference             G30, G50, G60, 360, 2006TWR220
Objective                 Demonstrate the effect of changing the JUNCTION_CONGESTION_DISTANCE
                          resource variable from the default value of 10 to 50m.
                          Note the queuing distance for LFPG_DEP is also 50m.
Dependencies              None
Resource File             <component test home>/tpm/resources/junction_congestion_radius.gsdk
                          <component test home>/tpm/resources/junction_congestion_radius_def.gsdk


ID   Time       Actions                                  Expectations
1    16:12:00   Run       junction_congestion_radius     AVD appears with map of LFPG
                scenario.
2    16:12:01                                            LFPG_DEP appears on AVD at gate EN20
                                                         AMBULANCE appears at TP_305 and starts to taxi
STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                    Page : 38 of 197

                                                                            EUROCONTROL



                                                      (very slowly) to TP_308
3   16:13:03                                          LFPG_DEP starts to taxi to R09R and will pass
                                                      through junction TP_308.
4                                                     Both LFPG_DEP and AMBULANCE converge on
                                                      TP_308.
5                                                     As LFPG_DEP approaches TP_308 it checks for
                                                      traffic congestion within 50m of TP_308.
                                                      As AMBULANCE is within 50m of TP_308
                                                      LFPG_DEP stops as junction is considered to be
                                                      congested.
6                                                     LFPG_DEP remains stationary to the end of the
                                                      scenario while AMBULANCE continues to travel very
                                                      slowly across junction.


1   16:12:00   Run junction_congestion_radius_def     AVD appears with map of LFPG
               scenario.
2   16:12:01                                          LFPG_DEP appears on AVD at gate EN20
                                                      AMBULANCE appears at TP_305 and starts to taxi
                                                      (very slowly) to TP_308
3   16:13:03                                          LFPG_DEP starts to taxi to R09R and will pass
                                                      through junction TP_308.
4                                                     Both LFPG_DEP and AMBULANCE converge on
                                                      TP_308
5                                                     As LFPG_DEP approaches TP_308 it checks for
                                                      traffic congestion within 10m of TP_308
                                                      Although AMBULANCE is within 50m of TP_308 it is
                                                      further than 10m away from TP_308.
                                                      LFPG_DEP passes TP_308 and continues on its
                                                      route to R09R and takes off.
6                                                     After LFPG_DEP has passed TP_308, AMBULANCE
                                                      continues very slowly on its taxi route.



    5.7     GMS

    5.7.1 CT_TPM_GMS_01 – Pluggable GMS
Scenario ID              CT_TPM_GMS_01
SRD Reference            G101
Objective                Demonstrates that different manoeuvres and movement characteristics can be
                         plugged into the GMS model.
                         The current aircraft and vehicle GMS models have been implemented such that
                         the aircraft model extends the vehicle model. To demonstrate the flexible nature of
                         the GMS model the aircraft model is replaced with the vehicle model. Any aircraft
                         in the scenario will then interpret and process its navigation script as if it was a

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 39 of 197

                                                                             EUROCONTROL



                          ground vehicle e.g. no take off orders will be processed.
Dependencies              None
Resource File             <component test home>/tpm/gms/gms_default.gsdk
                          <component test home>/tpm/gms/gms_pluggable.gsdk


ID   Time       Actions                    Expectations
1               Run gms_default.gsdk       AVD appears with map of LFPG
2    16:12:00   Commence     at   normal
                speed.
3                                          LFPG_DEP and VAN appear on AVD.
4                                          LFPG_DEP travels towards R09R but is delayed by stationary
                                           VAN.
5                                          VAN starts to move forward. LFPG_DEP follows at reduced
                                           speed.
6                                          VAN eventually turns off taxiway. LFPG_DEP is then able to
                                           continue to R09R at preferred faster taxi speed.
7                                          LFPG_DEP lines up on R09R and takes-off


9               Run                        AVD appears with map of LFPG
                gms_pluggable.gsdk
10   16:12:00   Commence     at   normal
                speed.
11                                         LFPG_DEP and VAN appear on AVD.
12                                         LFPG_DEP travels towards R09R but is delayed by stationary
                                           VAN.
13                                         VAN starts to move forward. LFPG_DEP follows at reduced
                                           speed.
14                                         VAN eventually turns off taxiway. LFPG_DEP is then able to
                                           continue to R09R at preferred faster taxi speed.
15                                         LFPG_DEP reaches R09R but does not take-off.



     5.7.2 CT_TPM_GMS_02 – Acceleration and Deceleration
Scenario ID               CT_TPM_GMS_02
SRD Reference             2006TWR220
Objective                 Demonstrate that departures, arrivals and vehicles accelerate and decelerate to
                          meet requested speed changes.
Dependencies              None
Resource File             <component test home>/tpm/gms/acceleration.gsdk



STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 40 of 197

                                                                               EUROCONTROL



ID    Time       Actions                     Expectations
1.                                           AVD appears with map of LFPG
2.    16:12:00   Commence     at   normal
                 speed.
3.    16:12:10                               DEP1, ARR1 and VAN1 appear.
4.               Issue taxi clearance to     DEP1 starts to taxi, accelerating up to a taxi speed of 3 knots.
                 DEP1.
5.               Issue speed order     40    The speed field in the extended label for DEP1 slowly increases
                 knots  to  DEP1        in   until it reaches 40.
                 RWY_N/PILOT.
6.               Issue  speed order          The speed field in the extended label for DEP1 decreases at a
                 Resume to DEP1 in           faster rate than it increased, until it reaches the normal taxi
                 RWY_N/PILOT.                speed (15, 19 or 20 knots).
7.                                           ARR1 stops, waiting for Taxi clearance.
8.               Issue taxi clearance to     ARR1 starts to taxi, accelerating up to a taxi speed of 15 knots.
                 ARR1 in RWY_N/PILOT.
9.               Issue speed order     40    The speed field in the extended label for ARR1 increases until it
                 knots  to  ARR1        in   reaches 40 knots.
                 RWY_N/PILOT.
10.              Issue  speed order          The speed field in the extended label for ARR1 decreases at a
                 Resume to ARR1 in           faster rate than it increased, until it reaches the normal taxiway
                 RWY_N/PILOT.                speed (15, 19 or 20 knots).
11.              Issue speed order     40    The speed field in the extended label for VAN1 increases until it
                 knots  to  VAN1        in   reaches 40 knots.
                 RWY_N/PILOT.
12.              Issue  speed order          The speed field in the extended label for VAN1 decreases until it
                 Resume to VAN1 in           reaches the normal vehicle taxiway speed of 8 knots.
                 RWY_N/PILOT.



      5.8    PM Piloted Flights

      5.8.1 CT_TPM_PM_01 – Integrate ATC and TWR tracks on TCWP


Scenario ID                CT_TPM_PM_01
SRD Reference              2005APT10
Objective                  Demonstrates that PM Piloted flights can be resolved into TPM Piloted Flights.
                           These flights are then detected by TIAS when within a specified range and height
                           of the airport.
                           This is observed as arrivals are seen as they approach prior to landing and
                           departures are seen after the takeoff.
Dependencies               None
Resource File              <component test home>/tpm/pm/merge.gsdk


STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 41 of 197

                                                                              EUROCONTROL




ID   Time       Actions                      Expectations
1    16:12:00   Launch scenario.             One AVD (RWY_N) and two PVDs (LFPG, FS) displayed.
2               Select Tools Resources       Observe:
                                             TIAS.MAX_HEIGHT_ABOVE_AIRPORT_FT            is 1500 (FL1500).
                                             TIAS.MAX_RANGE_NM       is 10.
3               Zoom RWY_N AVD out           RWY_N AVD at approximate same zoom as FS PVD.
                200%.
                Repeat.
4               Commence      at   normal
                speed.
5    After                                   Departures start to appear on RWY AVD.
     16:12:10                                Arrivals start to appear on PVDs and begin to descend.
                                             As arrivals descend through FL16 they appear on RWY AVD.
                                             Note FL16 = 1500ft + 387ft(airport elevation)
                                             Note update is every 1s on AVD and every 6s on PVD.
6               When first arrival appears   Observe departures takeoff. As departures takeoff they appear
                on AVD reset zoom.           on PVDs.
                                             Observe arrivals land. As arrivals land they disappear from
                                             PVDs.
7               When second departure        Observe departures remain below FL15 but disappear from RWY
                appears on PVDs:             AVD as they approach 10nm.
                Centre RWY_N AVD at
                centre of airport.
                Zoom RWY_N AVD out
                200%. Repeat.
                Turn range rings on.




     5.9     TPM Tower Piloted Flights

     5.9.1 CT_TPM_TPF_01 – Integrate ATC and TWR tracks on TPWP
Scenario ID                CT_TPM_TPF_01
SRD Reference              2006TWR20, 2006TWR30, 2006TWR40, 2006TWR50, 2006TWR60
Objective                  Demonstrates that PM Piloted flights can be resolved into TPM Piloted Flights.
                           These flights are then displayed by a TPWP.
                           This is observed as arrivals are seen as they approach prior to landing and
                           departures are seen after takeoff.
                           Observe no TFM, TFPM, TCS or TIAS are included in the component list.

STATUS                                                                                                      TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 42 of 197

                                                                             EUROCONTROL



Dependencies              None
Resource File             <component test home>/tpm/pm/merge_air.gsdk


ID    Time             Actions                              Expectations
1.    16:12:00         Launch scenario.                     One Pilot AVD (RWY_N) and two PVDs (LFPG,
                                                            FS) displayed.
2.                     Open:<component test       home>     Observe the component list does not contain the
                       /tpm/pm/merge_air.gsdk               following entries:
                                                            (   twr.tfm.TFM,               TFM              )
                                                            (   twr.tfpm.TFPM,             TFPM             )
                                                            (   twr.tias.TIAS,             TIAS             )
                                                            (   twr.ts.TCS,                TCS              )

3.                     Zoom RWY_N AVD out 200%.             RWY_N AVD at approximate same zoom as FS
                                                            PVD.
                       Repeat twice.
4.                     Commence at normal speed.

5.    After                                                 Arrivals start to appear on PVDs and begin to
                                                            descend.
      16:12:10
                                                            Note update is every 1s on AVD and every 6s on
                                                            PVD.
6.    After 16:18:30                                        Departures start to appear on RWY AVD.
7.                     In RWY_N issue Departures with       Departures start their taxi to the runway and take
                       Taxi,   Lineup  and    Takeoff       off.
                       clearances.
8.                     When first arrival appears on        Observe departures takeoff. As departures
                       RWY_N reset zoom.                    takeoff they appear on PVDs.
                                                            Observe arrivals land. As arrivals land they
                                                            disappear from PVDs.

     5.9.2 CT_TPM_TPF_02 – Pilot Frequencies
Scenario ID               CT_TPM_TPF_02
SRD Reference             2006TWR70, 2006TWR80, 2006TWR90
Objective                 Observe TPWPs operating on one and more frequencies.
                          Observe two TPWPs operating on same frequency.
                          Traffic allocated to default TPWP.
                          TPWP transferring control of arrivals, departures and vehicles via frequency and
                          by named TPWP with traffic lists updated accordingly.
                          The above observed in Stand-alone and Integrated mode.
Dependencies              None
Resource File             <component test home>/tpwp/control/control.gsdk
                          <component test home>/tpwp/control/control_standalone.gsdk



STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                           f7919ee3-d7fb-4de6-9213-
                                                  1719658e70fc.doc

                                                Page : 43 of 197

                                                                          EUROCONTROL



ID   Time       Actions                    Expectations
1.   16:12:00   Launch scenario.           Three Pilot AVDs (RWY_N, TWY_N, APR_N) and two PVDs
                                           (LFPG, FS) are displayed.
                                           Note the PVDs will not be displayed in standalone mode.
2.              Select             Tools   Observe the AVD controlled frequencies:
                Resources
                                           APR_N_AIR.FREQUENCY        is ( 120.25 121.25 )
                                           RWY_N_AIR.FREQUENCY        is ( 119.25 )
                                           TWY_N_AIR.FREQUENCY        is ( 120.25 )
                                           Observe the following Resource:
                                           TPWP.DEFAULTS RWY_N_AIR

3.              Commence at normal
                speed.
4.   After                                 Departure DEP1 appears controlled by APRON_N and shown
                                           as uncontrolled in RWY_N and TWY_N. APRON_N contains
     16:12:10
                                           flightstrip information for DEP1 in the flightstrip bays while
                                           RWY_N and TWY_N do not.
                                           The departure flightstrip list the initial frequency as 121.25,
                                           matching the APRON_N frequency.
                                           Arrival ARR1 appears on PVD FS and begins its descent.
                                           The flightstrip for ARR1 is displayed in the flightstrip bay for
                                           RWY_N only.
                                           The arrival flightstrip lists the initial frequency as 119.25,
                                           matching the RWY_N frequency.
                                           Vehicle VAN1 appears controlled by RWY_N and shown as
                                           uncontrolled in TWY_N and APRON_N. Flightstrip
                                           information for VAN1 is displayed in the flightstrip bays of
                                           RWY_N only.
                                           The vehicle flightstrip lists the initial frequency as 122.25. As
                                           no pilot AVD is present for that frequency VAN1 has been
                                           controlled by the default position, RWY_N.
                                           Note the default Pilot AVD is defined in the resources as
                                           RWY_N. If the default Pilot AVD is not defined in this manner
                                           then it will be the first AVD to register a frequency with the
                                           TPM.
                                           Note that when a flight couldbe initially controlled by either of
                                           two Pilot AVDs responsible for the same frequency, the first
                                           AVD discovered will be used.
                                           Note update is every 1s on AVD and every 6s on PVD.
5.              DEP1 commences taxi        DEP1 is now controlled by TWY_N and uncontrolled by
                to runway „09R‟.           APRON_N.
                In APRON_N, transfer       The flightstrip information has been transferred from the
                the flight to 120.25 –     flightstrip bay of APRON_N to TWY_N.
                TWY_N_AIR.
6.              VAN1 departs EN20.         VAN1 is now controlled by TWY_N and uncontrolled by

STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 44 of 197

                                                                             EUROCONTROL



                  In RWY_N, transfer           RWY_N.
                  VAN1 to frequency
                                               The flightstrip information has been transferred from the
                  120.25.
                                               flightstrip bay of RWY_N to TWY_N.
                                               Note that when a flight is transferred by frequency only and
                                               two AVDs are controlling that frequency, the flight is assigned
                                               to the first AVD returned.
7.     After      In TWY_N transfer            DEP1 is now controlled by RWY_N and uncontrolled by
       16:20:00   DEP1 to frequency            TWY_N.
                  119.25.
                                               The flightstrip information has been transferred from the
                                               flightstrip bay of TWY_N to RWY_N.
8.                DEP1 has taken-off.          DEP1 is now controlled by TWY_N and uncontrolled by
                                               RWY_N.
                  In RWY_N transfer
                  DEP1 to 120.25 –             The flightstrip information has been transferred from the
                  TWY_N_AIR                    flightstrip bay of TWY_N to RWY_N.
9.                ARR1 lands.                  ARR1 is now controlled by TWY_N and uncontrolled by
                                               RWY_N.
                  In RWY_N transfer
                  ARR1 to 120.25 –             The flightstrip information has been transferred from the
                  TWY_N_AIR.                   flightstrip bay of RWY_N to TWY_N.
10.    16:39:30   ARR1 has left the            ARR1 is now controlled by APR_N and uncontrolled by
                  runway and                   RWY_N.
                  commenced taxiing to
                                               The flightstrip information has been transferred from the
                  X1.
                                               flightstrip bay of TRY_N to APRON_N.
                  In TWY_N transfer
                                               Note when running standalone, ARR1 will commence landing
                  ARR1 to 120.25 –
                                               when it activates at 16:12:12 instead of at this time.
                  APR_N_AIR (by
                  selecting the controller
                  in the Arrivals list and
                  then 120.25 –
                  APR_N_AIR from the
                  resulting popup menu).
                  Note: if the controller is
                  not displayed in the
                  arrivals list, then it can
                  be switched on by
                  selecting the TPWP
                  option in the EFS tool,



      5.9.3 CT_TPM_TPF_03 – Pilot Orders
Scenario ID            CT_TPM_TPF_03
SRD Reference          2006TWR100, 2006TWR110
Objective              TPWP controlling traffic with the following commands:




STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 45 of 197

                                                                                EUROCONTROL



                           Command             Arrival   Departure    Vehicle
                           Pushback                      Yes
                           Stop                Yes       Yes          Yes
                           Taxi                Yes       Yes          Yes
                           Re-route            Yes       Yes
                           Change stand        Yes
                           Change runway                 Yes
                           Change SID                    Yes
                           Delete              Yes       Yes          Yes
                           Line-up                       Yes
                           Takeoff                       Yes
                           Transfer            Yes       Yes          Yes
                                                                                  Where Re-route is possible
                          before landing/pushback.
                          Note the Transfer control is covered in 5.9.2.
Dependencies              None
Resource File             <component test home>/tpwp/control/arrival.gsdk
                          <component test home>/tpwp/control/departure.gsdk
                          <component test home>/tpwp/control/vehicle.gsdk

     5.9.3.1 CT_TPM_TPF_03_1 – Arrival Orders
ID    Time           Actions                    Expectations
1.    16:12:00       Launch arrival             Two Pilot AVDs (RWY_N/PILOT, APRON_N), one Controller
                     scenario                   AVD (RWY_N/RWY), and one PVD (LFPG) are displayed.
2.                   Commence at normal
                     speed.
3.    After                                     Arrival ARR1 appears on RWY_N/PILOT landing on runway
                                                „27R‟. The flightstrip for ARR1 is displayed in the flightstrip
      16:12:10
                                                bay on RWY_N/PILOT only.
4.    Fast forward   ARR1 exits the runway      In RWY_N/PILOT, a „Taxi Due‟ prompt is displayed on the
      until ARR1     and stops, waits for       label
      has landed.    taxi clearance.
5.                   In RWY_N/PILOT             The control menu for ARR1 displays the following options:
                     open the flight control    TAXI, MARK, STOPAT, DELETE and CANCEL.
                     menu for ARR1.
6.                   Issue a Taxi clearance.    ARR1 continues to taxi to „X1‟.
7.                   In RWY_N/PILOT             The control menu for ARR1 displays the following options:
                     open the flight control    HOLD, MARK, STOPAT, DELETE and CANCEL.
                     menu for ARR1.
8.                   Issue a Hold               ARR1 stops, a „Taxi Due‟ prompt is displayed on the label
                     clearance.


STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                   Page : 46 of 197

                                                                             EUROCONTROL



9.                In RWY_N/PILOT              The stand listed in the flightstrip entry and label for ARR1
                  open the stand menu         now shows „A36‟
                  from the aircraft label.
                  Select stand „A36‟.
10.               In RWY_N/PILOT right        The current planned route is displayed, with a solid line
                  click on the aircraft       showing the forward route to the stand and a broken line
                  symbol to bring up the      showing the route already travelled.
                  route display.
11.               In RWY_N/PILOT,             The TPWP route editor is opened, showing a line leading to
                  close the route view by     the next taxi point on the vehicle route, which is also circled,
                  right clicking on the       to show it has been selected as a constraint point. A line joins
                  aircraft symbol, then       that circle to the mouse cursor.
                  left click on the
                  symbol to bring up the
                  route edit tool.
12.               Select a taxi point         Selecting the stand closes the tool display. There are no
                  close to the current        changes to the display to indicate a change of route.
                  route, then double click
                  on stand A36. Note
                  that not all routes will
                  be valid.
13.               In RWY_N/PILOT right        The route is different from the one previously shown in step
                  click on the aircraft       10, and includes the taxi point selected.
                  symbol to bring up the
                  route display.
14.               Open the flight control     The symbol, label and associated flightstrip display for ARR1
                  menu for ARR1.              are removed from both the Pilot AVDs and the Controller
                                              AVD.
                  Select DELETE, and
                  then confirm the
                  deletion by selecting
                  „Delete‟ in the following
                  popup..



      5.9.3.2 CT_TPM_TPF_03_2 – Departure Orders
ID     Time       Actions                      Expectations
1.     16:12:00   Launch departure             Two Pilot AVDs (RWY_N/PILOT, APRON_N) and one
                  scenario.                    Controller AVD (RWY_N/RWY) are displayed along with one
                                               PVD (LFPG).
2.                Commence at normal
                  speed.
3.     After                                   Departure DEP1 appears at „T3‟ and is under the control of
       16:12:10                                the APRON_N AVD. The flightstrip for DEP1 is displayed in
                                               the flightstrip bay for APRON_N only.
4.                In APRON_N open the          The control menu for DEP1 displays the following options:
                  flight control menu for      TAXI, LINEUP, TAKEOFF, MARK, CLUP, CTOF, STOPAT,
                  DEP1.                        DELETE and CANCEL.
5.                Issue a Taxi clearance.      DEP1 starts to taxi.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                           f7919ee3-d7fb-4de6-9213-
                                                  1719658e70fc.doc

                                                Page : 47 of 197

                                                                         EUROCONTROL



6.             In APRON_N open the         The control menu for DEP1 displays the following options:
               flight control menu for     HOLD, LINEUP, TAKEOFF, MARK, CLUP, CTOF,
               DEP1.                       STOPAT, DELETE and CANCEL.
7.             Issue a Hold clearance.     DEP1 stops, a „Taxi Due‟ prompt is displayed on the label.
8.             In APRON_N right click      The current planned route is displayed, with a solid line
               on the aircraft symbol to   showing the forward route to the runway and a broken line
               bring up the route          showing the route already travelled.
               display.
9.             Close the route display     The SID listed in the flightstrip entry and ELW for DEP1 now
               by right clicking on the    shows „SID‟.
               aircraft symbol.
                                           Note the Airport (LFPG) and Runway (R09R) pre-fixes are
               In APRON_N open the         removed from the SID name display.
               SID menu for DEP1.
               Change the SID to
               „LFPG R09R SID‟.
10.            In APRON_N open the         The runway listed in the flightstrip entry and label for DEP1
               runway menu for DEP1.       now shows „R09L‟.
               Change the runway to        The SID now shows „SID‟. Opening the SID menu confirms
               „R09L‟.                     that the only SID available is „LFPG R09L SID‟, which is also
                                           abbreviated to „SID‟ in the display.
11.            In APRON_N right click      The route is different from the one previously shown in step
               on the aircraft symbol to   8, and leads to runway R09L.
               bring up the route
               display.
12.            Close the route display     The TPWP route editor is opened, showing a line leading to
               by right clicking on the    the next taxi point on the vehicle route, which is also circled,
               aircraft symbol.            to show it has been selected as a constraint point. A line
                                           joins that circle to the mouse cursor.
               In APRON_N left click
               on the aircraft symbol
               for DEP1 to bring up the
               route edit tool.
13.            Select a taxi point close   Selecting the entry point closes the route and tool display.
               to the current route,       There are no changes to the display to indicate a change of
               then double click on the    route.
               entry point to runway
               R09L . Note that not all
               routes will be valid.
14.            In APRON_N right click      The route is different from the one previously shown in step
               on the aircraft symbol to   11, and includes the taxi point selected.
               bring up the route
               display.
15.            In APRON_N open the         The control menu for DEP1 displays the following options:
               flight control menu for     TAXI, LINEUP, TAKEOFF, MARK, CLUP, CTOF, STOPAT,
               DEP1.                       DELETE and CANCEL.
16.            Issue a Taxi clearance.     DEP1 starts to taxi.
17.            DEP1 stops, waiting for     DEP1 taxi‟s onto the runway and stops waiting for takeoff
               lineup clearance.           clearance.
               In APRON_N issue
STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                   Page : 48 of 197

                                                                           EUROCONTROL



                  DEP1 with a Lineup
                  clearance.
18.               In APRON_N open the          DEP1 takes off.
                  flight control menu for
                                               Note the error message in the console: “DEP1 will not attain
                  DEP1.
                                               take-off speed by end of runway R09L”
                  Issue Takeoff
                  clearance.
19.               Observe the route taken      DEP1 flies over fixes R09LSID and LFPGE.
                  by DEP1 in the PVD
                  (LFPG).
20.                                            Departure DEP2 appears at „U6‟. The flightstrips for DEP2 is
                                               displayed in the flightstrip bay for APRON_N.
21.               In APRON_N open the          The control menu for DEP2 displays the following options:
                  flight control menu for      PUSHBACK, MARK, STOPAT, DELETE and CANCEL.
                  DEP2.
22.               Issue a Pushback             DEP2 commences a pushback.
                  clearance.
23.               DEP2 executes a
                  pushback and stops,
                  waiting for a taxi
                  clearance.
24.               In APRON_N open the          The control menu for DEP2 displays the following options:
                  flight control menu for      TAXI, LINEUP, TAKEOFF, MARK, CLUP, CTOF, STOPAT,
                  DEP2.                        DELETE and CANCEL.
25.               Issue a Taxi clearance.      DEP2 starts to taxi.
26.               In APRON_N open the          The symbol, label and associated flightstrip display for
                  flight control menu for      DEP2 are removed from both the Pilot AVDs and the
                  DEP2.                        Controller AVD.
                  Select DELETE, and
                  then confirm the
                  deletion by selecting
                  „Delete‟ in the following
                  popup..



      5.9.3.3 CT_TPM_TPF_03_3 – Vehicle Orders
ID     Time       Actions                     Expectations
1.     16:12:00   Launch vehicle              Two Pilot AVDs (RWY_N/PILOT, APRON_N) and one
                  scenario                    Controller AVD (RWY_N/RWY) are displayed along with one
                                              PVD (LFPG).
2.                Commence at normal
                  speed.
3.     After                                  Vehicle VAN1 appears on APRON_N at „EN20‟. The
                                              flightstrip for VAN1 is displayed in the flightstrip bay for
       16:12:10
                                              APRON_N only.
4.                In APRON_N open the         The control menu for VAN1 displays the following options:

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 49 of 197

                                                                          EUROCONTROL



                 flight control menu for     HOLD, MARK, STOPAT, DELETE and CANCEL.
                 VAN1.
5.               Issue a Hold                VAN1 stops, and a „Taxi Due‟ prompt is displayed
                 clearance.
6.               In APRON_N open the         The control menu for ARR1 displays the following options:
                 flight control menu for     TAXI, MARK, STOPAT, DELETE and CANCEL.
                 VAN1.
7.               Issue a Taxi clearance.     VAN1 starts to taxi.
8.               In APRON_N open the         The symbol, label and associated flightstrip display for VAN1
                 flight control menu for     are removed from both the Pilot AVDs and the Controller
                 VAN1.                       AVD.
                 Select DELETE, and
                 then confirm the
                 deletion by selecting
                 „Delete‟ in the following
                 popup..



     5.9.4 CT_TPM_TPF_04 – Air Derived Data
Scenario ID           CT_TPM_TPF_04
SRD Reference         2006TWR150
Objective             Run scenario with TPWPs and TCWPs.
                      TPWP re-routes traffic.
                      Observe TPWP displays new actual traffic route while TCWP displays original
                      planned route.
                      Observe TPWP not controlling the traffic also sees actual traffic route.
Dependencies          None
Resource File         <component test home>/tpwp/control/control_tcwp.gsdk


ID    Time       Actions                      Expectations
1.    16:12:00   Launch scenario.             Three AVDs are displayed, one controller TCWP
                                              (RWY_N/RWY) and two pilot TPWPs (RWY_N/PILOT and
                                              TWY_N).
2.               Commence at normal
                 speed.
3.    After                                   Departure DEP1 appears at „T3‟.
      16:12:10
4.               In RWY_N, transfer the       DEP1 is now controlled by TWY_N and uncontrolled by
                 flight to frequency          RWY_N.
                 120.25
5.               In TWY_N open the            DEP1 starts to taxi.
                 flight control menu for
                 DEP1.


STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 50 of 197

                                                                           EUROCONTROL



               Issue a Taxi clearance.
6.             In TWY_N open the              The runway listed in the flightstrip entry and label for DEP1
               runway menu for DEP1.          now shows „R09L‟.
               Change the runway to
               „R09L‟.
7.             Right click on the aircraft    The route display on the TCWP shows the flight going to a
               symbols for DEP1 in the        different runway than the TPWP displays.
               RWY_N/RWY and both
                                              Both TPWPs show the same route for DEP1.
               TPWP displays
               (RWY_N/PILOT and
               TWY_N).
8.             Advance time and               DEP1 follows the path specified by the TPWP position.
               observe the path taken
               by DEP1, issueing
               further taxi clearances
               as required.




STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 51 of 197

                                                                               EUROCONTROL




     6     TCS COMPONENT TESTS

     6.1    Controller Roles

     6.1.1 General Description
Scenario ID               CT_TCS_ROL_01
                          CT_TCS_ROL_02
                          CT_TCS_ROL_03
                          CT_TCS_ROL_04
                          CT_TCS_ROL_05
                          CT_TCS_ROL_06
Objective                 Using different combinations of controller roles the scenarios will demonstrate and
                          confirm that:
                                  Labels are coloured (advance, advance transferred, assumed, assumed
                                   transferred, not concerned) accordingly as aircraft jurisdiction is
                                   transferred and assumed by callsigns. (see the Colour Definitions section
                                   above for a definition of the colour schemes used for each logical state.)
                                  Transfer and Assume actions for arrivals and departures.
                                  Correct organisation of Arrival / Departure Lists
Dependencies              None



     6.1.2 CT_TCS_ROL_01 – TCS Arrival Roles
Scenario ID               CT_TCS_ROL_01
SRD Reference             830, 870, G80, G140, G150, 780, 790, 800, 820, 850, 930, 810, 890, 910, 930
Objective                 To use four AVDs to control the progress of an arriving aircraft. The four AVDs will
                          represent one runway controller (RWY_N), one taxiway controller (TWY_N) and
                          two apron controllers (CARGO_N and APRON_N).
Resource File             <component test home>/tcs/roles/arrival.gsdk


ID   Time       Actions                     Expectations
1    16:12:00   Launch scenario.            AVDs for TWY_N, RWY_N, APR_N and CARGO_N appear with
                                            map of LFPG.

                                            On RWY_N AVD:
                                            Arrival list shows:
                                            FINAL, RUNWAY, TAXIWAY

                                            On TWY_N AVD:
                                            Arrival list shows:
                                            RUNWAY, TAXIWAY, APRON

                                            On APR_N and CARGO_N AVD:
STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                    Page : 52 of 197

                                                                              EUROCONTROL



                                           Arrival list shows:
                                           TAXIWAY, APRON, GATE
2              Commence scenario at
               normal speed.
3   16:12:08                               ARRIVAL touches down on runway.
4                                          On RWY_N AVD:
                                           Label state - Advance Transferred
                                           Entry in Arrival list FINAL section.

                                           On TWY_N AVD:
                                           Label state - Not Concerned.
                                           No entry in Arrival list.

                                           On CARGO_N AVD:
                                           Label state - Not Concerned.
                                           No entry in Arrival list.

                                           On APR_N AVD:
                                           Label state - Not Concerned.
                                           No entry in Arrival list.

5              RWY _N clicks(L)       on   On RWY_N AVD:
               callsign field.             Label state - Assumed
                                           Entry in Arrival list RUNWAY section.
               Select assume.
                                           On TWY_N AVD:
                                           Label state - Advance.
                                           Entry in Arrival list RUNWAY section.

                                           On CARGO_N AVD:
                                           Label state - Not Concerned.
                                           No entry in Arrival list.

                                           On APR_N AVD:
                                           Label state - Not Concerned.
                                           No entry in Arrival list.

6              RWY_N: After issuing        On RWY_N AVD:
               VACate clearance select     Label state – Assumed Transferred.
               transfer.                   Entry in Arrival list TAXIWAY section.

                                           On TWY_N AVD:
                                           Label state – Advance Transferred.
                                           Entry in Arrival list TAXIWAY section.

                                           On CARGO_N AVD:
                                           Label state – Advance
                                           Entry in Arrival list TAXIWAY section.

                                           On APR_N AVD:
                                           Label state - Not Concerned.
                                           Entry in Arrival list TAXIWAY section.

7              TWY   _N   clicks(L)   on   On RWY_N AVD:
                                           Label state - Not Concerned.
STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 53 of 197

                                                                             EUROCONTROL



                callsign field.           Entry in Arrival list TAXIWAY section.
                Select assume.
                                          On TWY_N AVD:
                                          Label state - Assumed.
                                          Entry in Arrival list TAXIWAY section.

                                          On CARGO_N AVD:
                                          Label state – Advance.
                                          Entry in Arrival list TAXIWAY section.

                                          On APR_N AVD:
                                          Label state - Not Concerned.
                                          Entry in Arrival list TAXIWAY section.

8               Let scenario progress
                until ARRIVAL reaches
                TP_86 and give taxi
                clearance
9               TWY _N clicks(L)    on    On RWY_N AVD:
                callsign field.           Label state - Not Concerned.
                                          Entry removed from Arrival list.
                Select transfer.
                                          On TWY_N AVD:
                                          Label state – Assumed Transferred.
                                          Entry in Arrival list APRON section.

                                          On CARGO_N AVD:
                                          Label state – Advance Transferred.
                                          Entry in Arrival list APRON section.

                                          On APR_N AVD:
                                          Label state - Not Concerned.
                                          Entry in Arrival list APRON section.

10              CARGO _N clicks(L) on     On RWY_N AVD:
                callsign field.           Label state - Not Concerned.
                                          No entry in Arrival list.
                Select assume.
                                          On TWY_N AVD:
                                          Label state - Not Concerned.
                                          Entry in Arrival list APRON section.

                                          On CARGO_N AVD:
                                          Label state – Assumed.
                                          Entry in Arrival list APRON section.

                                          On APR_N AVD:
                                          Label state - Not Concerned.
                                          Entry in Arrival list APRON section.

11                                        ARRIVAL reaches gate.
12   approx     Parameterised Resource    ARRIVAL symbol and label and entries in Arrival list removed
                time                      from all AVDs
     16:22:26
                (TOWER.ARRIVAL_OCC
                UPANCY_TIME)      after
STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 54 of 197

                                                                              EUROCONTROL



                 occupying gate (Default
                 300s)



     6.1.3 CT_TCS_ROL_02 – TCS Arrival Roles Merged
Scenario ID               CT_TCS_ROL_02
SRD Reference             830, 870, G80, G140, G150, 780, 790, 800, 820, 850, 930, 810, 890, 910, 930
Objective                 To use two AVDs to control the progress of an arriving aircraft. The two AVDs will
                          represent one runway controller (RWY_N), one merged taxiway and apron
                          controller (TWY_N).
Resource File             <component test home>/tcs/roles/arrivalMerged.gsdk


ID    Time          Actions                       Expectations
1     16:12:00      Launch scenario.              AVDs for TWY_N and RWY_N appear with map of LFPG.

                                                  On RWY_N AVD:
                                                  Arrival list shows:
                                                  FINAL, RUNWAY, TAXIWAY

                                                  On TWY_N AVD:
                                                  Arrival list shows:
                                                  RUNWAY, TAXIWAY/APRON, GATE

2                   Commence scenario       at
                    normal speed.
3     16:12:08                                    ARRIVAL touches down on runway.
4                                                 On RWY_N AVD:
                                                  Label state – Advanced Transferred.
                                                  Entry in Arrival list FINAL section.

                                                  On TWY_N AVD:
                                                  Label state – Not Concerned.
                                                  No entry in Arrival list.

5                   RWY _N clicks(L)       on     On RWY_N AVD:
                    callsign field.               Label state – Assumed
                                                  Entry in Arrival list RUNWAY section.
                    Select assume.
                                                  On TWY_N AVD:
                                                  Label state – Advance.
                                                  Entry in Arrival list RUNWAY section.

6                   RWY_N: After issuing          On RWY_N AVD:
                    VACate select transfer.       Label state – Assumed Transferred.
                                                  Entry in Arrival list TAXIWAY section.

                                                  On TWY_N AVD:
                                                  Label state – Advance Transferred.
                                                  Entry in Arrival list TAXIWAY/APRON section.


STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 55 of 197

                                                                            EUROCONTROL



7                TWY _N clicks(L)        on     On RWY_N AVD:
                 callsign field.                Label state – Not Concerned
                                                Entry in Arrival list TAXIWAY section.
                 Select assume.
                                                On TWY_N AVD:
                                                Label state – Assumed.
                                                Entry in Arrival list TAXIWAY/APRON section.

8                Let scenario progress until
                 ARRIVAL reaches TP_86
                 and give taxi clearance
9     16:22:26   Parameterised Resource         ARRIVAL symbol and label and entries in Arrival list
                 time                           removed from all AVDs
                 (TOWER.ARRIVAL_OCC
                 UPANCY_TIME)      after
                 occupying gate (Default
                 300s)



     6.1.4 CT_TCS_ROL_03 – TCS Arrival All Roles Merged
Scenario ID            CT_TCS_ROL_03
SRD Reference          830, 870, G80, G140, G150, 780, 790, 800, 820, 850, 930, 810, 890, 910, 930
Objective              To use one AVD to control the progress of an arriving aircraft. The AVD will
                       represent one merged runway, taxiway and apron controller (RWY_N).
Resource File          <component test home>/tcs/roles/arrivalAllMerged.gsdk


ID    Time       Actions                        Expectations
1     16:12:00   Launch scenario.               AVD for RWY_N appears with map of LFPG.

                                                On RWY_N AVD:
                                                Arrival list shows:
                                                FINAL, RUNWAY/TAXIWAY/APRON, GATE

2                Commence scenario        at
                 normal speed.
3     16:12:08                                  ARRIVAL touches down on runway.
4                                               On RWY_N AVD:
                                                Label state – Advance Transferred.
                                                Entry in Arrival list FINAL section.

5                RWY _N clicks(L)        on     On RWY_N AVD:
                 callsign field.                Label state – Assumed.
                                                Entry in Arrival list RUNWAY/TAXIWAY/APRON section.
                 Select assume.
6                Let scenario progress until
                 ARRIVAL reaches TP_86
                 and give VACate ane Taxi
                 clearances
7     16:22:26   Parameterised    Resource      ARRIVAL symbol and label and entries in Arrival list

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 56 of 197

                                                                            EUROCONTROL



                 time                         removed from all AVDs
                 (TOWER.ARRIVAL_OCC
                 UPANCY_TIME)      after
                 occupying gate (Default
                 300s)



     6.1.5 CT_TCS_ROL_04 – TCS Departure Roles
Scenario ID            CT_TCS_ROL_04
SRD Reference          860, G80, G140, G150, 780, 790, 800, 820, 840, 850, 930, 890, 910
Objective              To use four AVDs to control the progress of a departing aircraft. The four AVDs
                       will represent one runway controller (RWY_N), one taxiway controller (TWY_N)
                       and two apron controllers (CARGO_N and APRON_N).
Resource File          <component test home>/tcs/roles/departure.gsdk


ID    Time       Actions                      Expectations
1     16:12:00   Launch scenario.             AVDs for TWY_N, RWY_N, APR_N and CARGO_N
                                              appear with map of LFPG.

                                              On RWY_N AVD:
                                              Departure list shows:
                                              TAXIWAY, RUNWAY, CTR

                                              On TWY_N AVD:
                                              Departure list shows:
                                              APRON, TAXIWAY, RUNWAY

                                              On APR_N and CARGO_N AVD:
                                              Departure list shows:
                                              GATE, APRON, TAXIWAY

2                Commence scenario      at
                 normal speed.
3     16:12:16                                DEPARTURE appears at EN20.
4                                             On RWY_N AVD:
                                              Label state –Not Concerned.
                                              No entry in Departure list.

                                              On TWY_N AVD:
                                              Label state – Advance.
                                              No entry in Departure list.

                                              On CARGO_N AVD:
                                              Label state – Advance Transferred.
                                              Entry in Departure list GATE section.

                                              On APR_N AVD:
                                              Label state – Not Concerned.
                                              Entry in Departure list GATE section.


STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                        f7919ee3-d7fb-4de6-9213-
                                               1719658e70fc.doc

                                             Page : 57 of 197

                                                                       EUROCONTROL



5              CARGO_N clicks(L)   on    On RWY_N AVD:
               callsign field.           Label state – Not Concerned.
                                         No entry in Departure list.
               Select assume.
                                         On TWY_N AVD:
                                         Label state – Advance.
                                         No entry in Departure list.

                                         On CARGO_N AVD:
                                         Label state – Assumed.
                                         Entry in Departure list GATE section.

                                         On APR_N AVD:
                                         Label state – Not Concerned.
                                         Entry in Departure list GATE section.

6              CARGO_N clicks(L)   on    On RWY_N AVD:
               callsign field.           Label state – Not Concerned.
                                         No entry in Departure list.
               Select taxi.
                                         On TWY_N AVD:
                                         Label state – Advance.
                                         Entry in Departure list APRON section.

                                         On CARGO_N AVD:
                                         Label state – Assumed.
                                         Entry in Departure list APRON section.

                                         On APR_N AVD:
                                         Label state – Not Concerned.
                                         Entry in Departure list APRON section.

7              CARGO _N clicks(L) on     On RWY_N AVD:
               callsign field.           Label state – Advance.
                                         Entry in Departure list TAXIWAY section.
               Select transfer.
                                         On TWY_N AVD:
                                         Label state – Advance Transferred.
                                         Entry in Departure list TAXIWAY section.

                                         On CARGO_N AVD:
                                         Label state – Assumed Transferred.
                                         Entry in Departure list TAXIWAY section.

                                         On APR_N AVD:
                                         Label state – Not Concerned.
                                         Entry in Departure list TAXIWAY section.

8              TWY _N clicks(L)    on    On RWY_N AVD:
               callsign field.           Label state – Advance.
                                         Entry in Departure list TAXIWAY section.
               Select assume.
                                         On TWY_N AVD:
                                         Label state – Assumed.
                                         Entry in Departure list TAXIWAY section.


STATUS                                                                                           TITLE
Company Ref.                                                                      Template : Normal.dotm
                                       f7919ee3-d7fb-4de6-9213-
                                              1719658e70fc.doc

                                            Page : 58 of 197

                                                                    EUROCONTROL



                                        On CARGO_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list TAXIWAY section.

                                        On APR_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list TAXIWAY section.

9              TWY _N clicks(L)   on    On RWY_N AVD:
               callsign field.          Label state – Advance Transferred.
                                        Entry in Departure list TAXIWAY section.
               Select transfer.
                                        On TWY_N AVD:
                                        Label state – Assumed Transferred.
                                        Entry in Departure list TAXIWAY section.

                                        On CARGO_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list TAXIWAY section.

                                        On APR_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list TAXIWAY section.

10             RWY _N clicks(L)   on    On RWY_N AVD:
               callsign field.          Label state – Assumed.
                                        Entry in Departure list TAXIWAY section.
               Select assume.
                                        On TWY_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list TAXIWAY section.

                                        On CARGO_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list TAXIWAY section.

                                        On APR_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list TAXIWAY section.

11             RWY _N clicks(L)   on    On RWY_N AVD:
               callsign field.          Label state – Assumed.
                                        Entry in Departure list RUNWAY section.
               Select line-up.
                                        On TWY_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list RUNWAY section.

                                        On CARGO_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list removed.

                                        On APR_N AVD:
                                        Label state – Not Concerned.
                                        Entry in Departure list removed.


STATUS                                                                                       TITLE
Company Ref.                                                                  Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 59 of 197

                                                                              EUROCONTROL



12                                              DEPARTURE continues to runway.
13               RWY _N clicks(L)        on     DEPARTURE accelerates down runway and takes-off.
                 callsign field.
                 Select take-off.
                 Note time of takeoff.
14               Parameterised Resource         On RWY_N AVD:
                 time after takeoff (Default    Entry in Departure list CTR section.
                 60s) implies automatic         The Departure List entry is initially coloured with the
                 assume by surrounding          Assumed     Transferred     colours,  then   after  the
                 ATC Approach sector.           parameterised time the entry changes to the Not
                                                Concerned colour scheme.

                                                On TWY_N AVD:
                                                No entry in Departure list.

                                                On CARGO_N AVD:
                                                No entry in Departure list.

                                                On APR_N AVD:
                                                No entry in Departure list.

16               Parameterised Resource         Entries in Departure list removed from all AVDs
                 time   after    automatic
                 assume (Default 60s)



     6.1.6 CT_TCS_ROL_05 – TCS Departure Roles Merge
Scenario ID             CT_TCS_ROL_05
SRD Reference           860, G80, G140, G150, 780, 790, 800, 820, 840, 850, 930, 890, 910
Objective               To use two AVDs to control the progress of a departing aircraft. The two AVDs will
                        represent one runway controller (RWY_N), one merged taxiway and apron
                        controller (TWY_N).
Resource File           <component test home>/tcs/roles/departureMerged.gsdk


ID    Time       Actions                        Expectations
1     16:12:00   Launch scenario.               AVDs for TWY_N and RWY_N appear with map of LFPG.

                                                On RWY_N AVD:
                                                Departure list shows:
                                                TAXIWAY, RUNWAY, CTR

                                                On TWY_N AVD:
                                                Departure list shows:
                                                GATE, APRON/TAXIWAY, RUNWAY

2                Commence scenario        at
                 normal speed.
3     16:12:16                                  DEPARTURE appears at EN20.

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                   Page : 60 of 197

                                                                             EUROCONTROL



4                                              On RWY_N AVD:
                                               Label state - Advance
                                               No entry in Departure list.

                                               On TWY_N AVD:
                                               Label state – Advance Transferred
                                               Entry in Departure list GATE section.

5              TWY_N         clicks(L)   on    On RWY_N AVD:
               callsign field.                 Label state – Advance.
                                               No entry in Departure list.
               Select assume.
                                               On TWY_N AVD:
                                               Label state – Assumed.
                                               Entry in Departure list GATE section.

6              TWY_N         clicks(L)   on    On RWY_N AVD:
               callsign field.                 Label state – Advance.
                                               Entry in Departure list TAXIWAY section.
               Select taxi.
                                               On TWY_N AVD:
                                               Label state – Assumed.
                                               Entry in Departure list APRON/TAXIWAY section.

7              TWY _N clicks(L)          on    On RWY_N AVD:
               callsign field.                 Label state – Advance Transferred.
                                               Entry in Departure list TAXIWAY section.
               Select transfer.
                                               On TWY_N AVD:
                                               Label state – Assumed Transferred.
                                               Entry in Departure list APRON/TAXIWAY section.

8              RWY _N clicks(L)          on    On RWY_N AVD:
               callsign field.                 Label state – Assumed.
                                               Entry in Departure list TAXIWAY section.
               Select assume.
                                               On TWY_N AVD:
                                               Label state – Not Concerned.
                                               Entry in Departure list APRON/TAXIWAY section.

9              Let scenario continue until
               DEPARTURE          reaches
               hold point i.e. approaches
               runway.
10             RWY _N clicks(L)          on    On RWY_N AVD:
               callsign field.                 Label state – Assumed.
                                               Entry in Departure list RUNWAY section.
               Select line-up.
                                               On TWY_N AVD:
                                               Label state – Not Concerned.
                                               Entry in Departure list RUNWAY section.

11             Let scenario continue until
               DEPARTURE lines-up on
               runway.

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 61 of 197

                                                                             EUROCONTROL



12               RWY _N clicks(L)          on    DEPARTURE accelerates down runway and takes-off.
                 callsign field.
                 Select take-off.
13               Parameterised Resource          On RWY_N AVD:
                 time after takeoff (Default     Entry in Departure list CTR section.
                 60s) implies automatic          The Departure List entry is initially coloured with the
                 assume by surrounding           Assumed     Transferred     colours,  then   after  the
                 ATC Approach sector.            parameterised time the entry changes to the Not
                                                 Concerned colour scheme.



                                                 On TWY_N AVD:
                                                 In All label coloured not-concerned.
                                                 No entry in Departure list.

14               Parameterised Resource          Entries in Departure list removed from all AVDs.
                 time   after    automatic
                 assume (Default 60s)



     6.1.7 CT_TCS_ROL_06 – TCS Departure All Roles Merged
Scenario ID             CT_TCS_ROL_06
SRD Reference           860, G80, G140, G150, 780, 790, 800, 820, 840, 850, 930, 890, 910
Objective               To use one AVD to control the progress of a departing aircraft. The AVD will
                        represent one merged runway, taxiway and apron controller (RWY_N).
Resource File           <component test home>/tcs/roles/departureAllMerged.gsdk


ID    Time       Actions                         Expectations
1     16:12:00   Launch scenario.                AVD for RWY_N appears with map of LFPG.

                                                 On RWY_N AVD:
                                                 Departure list shows:
                                                 GATE, APRON/TAXIWAY/RUNWAY, CTR

2                Commence scenario         at
                 normal speed.
3     16:12:16                                   DEPARTURE appears at EN20.
                                                 On RWY_N AVD:
                                                 Label State – Advance Transferred.
                                                 Entry in Departure list GATE section.

4                RWY_N         clicks(L)   on    On RWY_N AVD:
                 callsign field.                 Label State – Assumed.
                                                 Entry in Departure list GATE section.
                 Select assume.
5                RWY_N         clicks(L)   on    On RWY_N AVD:
                 callsign field.                 Label State – Assumed.
                                                 Entry in Departure list      APRON/TAXIWAY/RUNWAY

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 62 of 197

                                                                             EUROCONTROL



                   Select taxi.                   section.

6                  Let scenario continue until
                   DEPARTURE          reaches
                   hold point i.e. approaches
                   runway.
7                  RWY _N clicks(L)         on    DEPARTURE continues to runway.
                   callsign field.
                   Select line-up.
8                  Let scenario continue until
                   DEPARTURE lines-up on
                   runway.
9                  RWY _N clicks(L)         on    DEPARTURE accelerates down runway and takes off.
                   callsign field.
                   Select take-off.
10                 Parameterised Resource         On RWY_N AVD:
                   time after takeoff (Default    Entry in Departure list CTR section.
                   60s) implies automatic         The Departure List entry is initially coloured with the
                   assume by surrounding          Assumed     Transferred     colours,  then   after  the
                   ATC Approach sector.           parameterised time the entry changes to the Not
                                                  Concerned colour scheme.


11                 Parameterised Resource         Entry removed from Departure list.
                   time   after    automatic
                   assume (Default 60s)



     6.2    Controller Orders

     6.2.1 Changing Taxi Route
Scenario ID                CT_TCS_ORD_01
SRD Reference
Objective                  The scenario will demonstrate and confirm that changing the taxi route will change
                           the planned jurisdiction of control for an aircraft.
Dependencies               None
Resource File              <component test home>/tcs/orders/taxiroute.gsdk


ID    Time       Actions                    Expectations
1     16:12:00   Launch scenario.           AVDs for TWY_N, RWY_N, APR_N and CARGO_N appear
                                            with map of LFPG.

                                            On RWY_N AVD:
                                            Arrival list shows:
                                            FINAL, RUNWAY, TAXIWAY

                                            On TWY_N AVD:

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                 Page : 63 of 197

                                                                           EUROCONTROL



                                         Arrival list shows:
                                         RUNWAY, TAXIWAY, APRON

                                         On APR_N and CARGO_N AVD:
                                         Arrival list shows:
                                         TAXIWAY, APRON, GATE
2              Commence scenario at
               normal speed.
3   16:12:08                             ARRIVAL touches down on runway.
4                                        On RWY_N AVD:
                                         Label state – Advance Transferred.
                                         Entry in Arrival list FINAL section.

                                         On TWY_N AVD:
                                         Label state – Not Concerned.
                                         No entry in Arrival list.

                                         On CARGO_N AVD:
                                         Label state – Not Concerned.
                                         No entry in Arrival list.

                                         On APR_N AVD:
                                         Label state – Not Concerned.
                                         No entry in Arrival list.

5              RWY _N clicks(L) on       On RWY_N AVD:
               callsign field.           Label state – Assumed.
                                         Entry in Arrival list RUNWAY section.
               Select assume.
                                         On TWY_N AVD:
                                         Label state – Advance.
                                         Entry in Arrival list RUNWAY section.

                                         On CARGO_N AVD:
                                         Label state – Not Concerned.
                                         No entry in Arrival list.

                                         On APR_N AVD:
                                         Label state – Not Concerned.
                                         No entry in Arrival list.

6              RWY_N: After issuing      On RWY_N AVD:
               VACate select transfer.   Label state – Assumed Transferred.
                                         Entry in Arrival list TAXIWAY section.

                                         On TWY_N AVD:
                                         Label state – Advance Transferred.
                                         Entry in Arrival list TAXIWAY section.

                                         On CARGO_N AVD:
                                         Label state – Advance.
                                         Entry in Arrival list TAXIWAY section.

                                         On APR_N AVD:
                                         Label state – Not Concerned .
STATUS                                                                                             TITLE
Company Ref.                                                                        Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                   Page : 64 of 197

                                                                            EUROCONTROL



                                          Entry in Arrival list TAXIWAY section.

7                TWY _N clicks(L) on      On RWY_N AVD:
                 callsign field.          Label state – Not Concerned.
                                          Entry in Arrival list TAXIWAY section.
                 Select assume.
                                          On TWY_N AVD:
                                          Label state – Assumed..
                                          Entry in Arrival list TAXIWAY section.

                                          On CARGO_N AVD:
                                          Label state – Advance.
                                          Entry in Arrival list TAXIWAY section.

                                          On APR_N AVD:
                                          Label state – Not Concerned.
                                          Entry in Arrival list TAXIWAY section.

8                From          TWY_N      On RWY_N AVD:
                 clicking(L) on type      Label state – Not Concerned.
                 designator use elastic   Entry in Arrival list TAXIWAY section.
                 vector to change gate
                 to one within APR_N      On TWY_N AVD:
                 ground sector            Label state – Assumed.
                                          Entry in Arrival list TAXIWAY section.

                                          On CARGO_N AVD:
                                          Label state – Not Concerned.
                                          Entry in Arrival list TAXIWAY section.

                                          On APR_N AVD:
                                          Label state – Advance.
                                          Entry in Arrival list TAXIWAY section.




    6.3     Integrated

    6.3.1 General Description
Scenario ID              CT_TCS_INT_01
                         CT_TCS_INT_02
                         CT_TCS_INT_03
Objective                The scenarios will demonstrate and confirm that:
                                 Labels are coloured (advance, assumed, concerned, not concerned)
                                  accordingly as aircraft jurisdiction is transferred and assumed by
                                  callsigns.
                                 The callsign field on the AVD aircraft label is coloured according to
                                  transfer/assume transition.
                                 The unit field on the PVD aircraft label is coloured according to
                                  transfer/assume transition.


STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 65 of 197

                                                                             EUROCONTROL



                               Transfer and Assume actions for arrivals and departures.
                               Correct organisation of Arrival Lists
                               Communication between the Tower and ATC systems
                               Tower Controller can also view Airport ATC sector
                               Traffic rules are not enforced on runways.
Dependencies           None



     6.3.2 CT_TCS_INT_01 - TCS Arrival Integrated Mode
Scenario ID            CT_TCS_INT_01
SRD Reference          G160, 20, 250, 620, 630, 640, 670, 680, 650, 760, 770
Objective              To use one AVD and one PVD to control the progress of arriving aircraft. The AVD
                       will represent one merged runway, taxiway and apron controller (RWY_N). The
                       PVD will represent the ATC sector surrounding the airport.
Resource File          <component test home>/tcs/integrated/arrival.gsdk


ID    Time       Actions                         Expectations
1     16:12:00   Launch scenario.                AVD for RWY_N appears with map of LFPG.

                                                 On RWY_N AVD:
                                                 Arrival list shows:
                                                 FINAL, RUNWAY/TAXIWAY/APRON, GATE

                                                 PVDs for LFPG and FS appear displaying airspace
                                                 surrounding the airport

                                                 PVD LFPG is used for viewing only. It does allow
                                                 inputs but these are not reflected in The Tower system
2                Commence scenario         at
                 normal speed.
3     16:12:25   As scenario progresses.         ARR1, ARR2 and ARR3 appear on PVD.
                                                 Flights enter the Arrival list in FINAL section.
                                                 As flights approach the airport and after passing fix REM
                                                 they begin to descend with the labels displaying LFPG.
                                                 The entries in the Arrival list are coloured in the Advance
                                                 colour scheme.
                                                 The SILs on the LFPG PVD show ARR1, ARR2 and ARR3
                                                 as inbound.

4                For ARR1 and ARR2               On AVD the ARR1 and ARR2 entries in the Arrival list
                 using PVD click(L) on           update to the Advance Transferred colour but the ground
                 LFPG label and select           sector fields display FINAL and are shown in Assumed
                 transfer.                       colour.
5                For ARR1 using AVD              On AVD the ARR1 entry in the Arrival list now displays
                 Arrival list, click(L) on       RWY_N and the whole line is coloured Assumed.
                 callsign     and     select     Entry shown in Arrival list RUNWAY/TAXIWAY/APRON
                 assume.                         section.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 66 of 197

                                                                              EUROCONTROL



                                                 On PVD ARR1 label coloured concerned.
                                                 On LFPG PVD ARR1 removed from SIL.
6                As scenario progresses.         ARR1, ARR2 and ARR3 descend to FL4 (airport elevation
                                                 387ft) removed from PVDs, touch down.
7                                                On RWY_N AVD:

                                                 In ARR1 label:
                                                 Label state – Assumed.
                                                 Entry in Arrival list RUNWAY/TAXIWAY/APRON section.

                                                 In ARR2 label:
                                                 Label state – Advance Transferred.
                                                 Entry in Arrival list FINAL section.

                                                 In ARR3 label:
                                                 Label state – Advance Transferred.
                                                 Entry in Arrival list FINAL section.

8                For ARR2 and ARR3               On RWY_N AVD:
                 clicks(L) on callsign field.    All labels show Assumed state.
                                                 Entries in Arrival list RUNWAY/TAXIWAY/APRON section.
                 Select assume.
9                Let scenario progress until
                 arrivals reach TP_86 and
                 give Vacate and Taxi
                 clearance.
11               Parameterised Resource          All symbols, labels and entries in Arrival list removed from
                 time                            all AVDs
                 (TOWER.ARRIVAL_OCC
                 UPANCY_TIME     default
                 300s) after occupying
                 gate.



     6.3.3 CT_TCS_INT_02 – TCS Departure Integrated Mode
Scenario ID             CT_TCS_INT_02
SRD Reference           G160, 20, 250, 620, 630, 640, 670, 680, 650, 760, 770
Objective               To use one AVD and one PVD to control the progress of departing aircraft. The
                        AVD will represent one merged runway, taxiway and apron controller (RWY_N).
                        The PVD will represent the ATC sector surrounding the airport.
Resource File           <component test home>/tcs/integrated/departure.gsdk


ID    Time       Actions                         Expectations
1     16:12:00   Launch scenario.                AVD for RWY_N appears with map of LFPG.

                                                 On RWY_N AVD:
                                                 Departure list shows:
                                                 GATE, RUNWAY/TAXIWAY/APRON, CTR

                                                 PVD for FS appears displaying ATC air routes surrounding
                                                 the airport.
STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 67 of 197

                                                                            EUROCONTROL




                                                PVD for LFPG appears displaying airspace surrounding
                                                airport.

                                                PVD LFPG is used for viewing only. It does allow
                                                inputs but these are not reflected in The Tower system
2               Commence scenario         at
                normal speed.
3    16:12:17                                   DEP1 appears at gate U6.
                                                DEP2 appears at gate V2.
                                                DEP3 appears at gate V4.

                                                Callsign coloured assumed.
                                                Labels coloured advance.
                                                Entries in Departure list GATE section.
4               For each flight in turn         All label coloured assumed.
                click(L) on callsign and
                select assume.
5               For DEP1 click(L) on            Departure list entry moves to
                callsign  and   select          RUNWAY/TAXIWAY/APRON section.
                pushback.                       DEP1 begins to pushback.
6               Wait until DEP1 reaches
                TP_1215.
7               For DEP2 click(L) on            Departure       list     entry              moves           to
                callsign  and   select          RUNWAY/TAXIWAY/APRON section.
                pushback.                       DEP2 begins to pushback.
8               Wait     until   DEP2           DEP2 queues behind DEP1.
                approaches TP_1215.
9               For DEP3 click(L) on            Departure       list     entry              moves           to
                callsign  and   select          RUNWAY/TAXIWAY/APRON section.
                pushback.                       DEP3 begins to pushback.
10              Wait     until   DEP3           DEP3 queues behind DEP2.
                approaches TP_1215.
11              For DEP1 click(L) on            DEP1 begins to taxi.
                callsign and select taxi.       DEP2 reaches TP_1215 and waits.
                                                DEP3 queues behind DEP2.
12              For DEP2 click(L) on            DEP2 begins to taxi.
                callsign and select taxi.       DEP3 reaches TP_1215.
13              For DEP3 click(L) on            DEP3 begins to taxi.
                callsign and select taxi.
14              Let scenario progress until     DEP1 reaches runway hold point.
                flights reach hold point        DEP2 queues behind DEP1.
                near runway.                    DEP3 queues behind DEP2.
15              For DEP1 click(L) on            DEP1 lines-up on runway.
                callsign and select lineup.     DEP2 moves to hold point.
                                                DEP3 queues behind DEP2.
16              For DEP1 click(L) on            DEP1 accelerates down runway and takes-off.
                callsign and select takeoff.    DEP1 appears on PVDs.



STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 68 of 197

                                                                            EUROCONTROL



17               For DEP2 click(L) on            DEP2 lines-up on runway.
                 callsign and select lineup.     DEP3 moves to runway hold point.
18               For DEP2 click(L) on            DEP2 accelerates down runway and takes-off.
                 callsign and select takeoff.    DEP2 appears on PVD.
19               For DEP3 click(L) on            DEP3 lines-up on runway.
                 callsign and select lineup.
20               For DEP3 click(L) on            DEP2 accelerates down runway and takes-off.
                 callsign and select takeoff.    Entry moves to Arrival list CTR section.
                                                 DEP3 appears on PVD.
21                                               On LFPG PVD labels coloured assumed with next unit
                                                 coloured concerned indicating that they have been
                                                 transferred.
                                                 On FS PVD DEP1 and DEP2 labels will show FS in
                                                 assumed colour with label coloured advance.
                                                 This is also the case for DEP3 label even though it was
                                                 not transferred while displayed on the AVD.
22               On PVD, for each of the         On PVD DEP1, DEP2 and DEP3 labels show flights as
                 flights, click(L), note time    assumed.
                 and select assume.
                                                 On AVD entries in the Departure list CTR section are
                                                 shown in not-concerned colour.
                                                 Track labels on LFPG indicate not concerned.
23               Parameterised Resource          All entries in Departure list removed from all AVDs
                 time after assuming flights
                 (Default 60s)



     6.3.4 CT_TCS_INT_03 – TCS Arrival and Departure Integrated Mode
Scenario ID             CT_TCS_INT_03
SRD Reference           G160, 20, 250, 620, 630, 640, 670, 680, 650, 760, 770
Objective               To use one AVD, one unmanned AVD and one PVD to control the progress of
                        arriving and departing aircraft. The AVD will represent one apron controller
                        (CARGO_N) while the unmanned controller will represent one merged runway,
                        taxiway and apron controller (LFPG = RWY_N + TWY_N + APRON_N). The PVD
                        will represent the ATC sector surrounding the airport.
Resource File           <component test home>/tcs/integrated/lfpgUnmannedRWY.gsdk
                        <component test home>/tcs/integrated/lfpg.gsdk


ID    Time       Actions                         Expectations
1     16:12:00   Launch        scenario          AVD for CARGO_N appears with map of LFPG.
                 lfpgUnmannedRWY.gsdk.
                                                 On CARGO_N AVD:
                                                 Arrival list shows:
                                                 FINAL, RUNWAY/TAXIWAY, APRON, GATE
                                                 Departure list shows:
                                                 GATE, APRON, TAXIWAY/RUNWAY, CTR.

                                                 PVD for FS appears displaying ATC air routes surrounding
                                                 the airport.

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                   Page : 69 of 197

                                                                           EUROCONTROL




                                               No LFPG PVD is required as runway controller role is
                                               automated.
2               Commence scenario        at
                normal speed.
3    16:12:00                                  On AVD
                                             DEP1 appears at gate EN20.
                                               DEP2 appears at gate EN21.
     16:13:20
                                               DEP3 appears at gate EN22.

                                               Callsign coloured assumed.
                                               Label state – Advance Transferred.
                                               Entries in Departure list GATE section.

                                               In Arrival list ARR1,..,ARR9 appear FINAL section
                                               coloured not-concerned.

                                               On PVD
                                               ARR1,..,ARR9 appear.

4               On CARGO_N AVD for             All label coloured in the Assumed state.
                DEP1,..,DEP3     in  turn
                click(L) on callsign and
                select assume.
5               For DEP1 click(L) on           Departure list entry moves to APRON section.
                callsign and select taxi.      DEP1 begins to taxi.
6               For DEP2 click(L) on           Departure list entry moves to APRON section.
                callsign and select taxi.      DEP2 begins to taxi.
7               For DEP3 click(L) on           Departure list entry moves to APRON section.
                callsign and select taxi.      DEP3 begins to taxi.


8               Let scenario progress until    DEP1 reaches hold point.
                departures reach hold          DEP2 queues behind DEP1.
                point near R09R.               DEP3 queues behind DEP2.
9               For DEP1 click(L) on           DEP1 is automatically assumed by unmanned AVD
                callsign  and   select         (RWY_N).
                transfer.                      Entry moves to Runway/Taxiway section in Departure list
                                               and label shown in Not Concerned colour scheme.
                                               It is then automatically given lineup and takeoff clearance
                                               and proceeds onto the runway and accelerates and takes
                                               off.
                                               Entry moved to CTR section on Departure list.
                                               DEP2 moves to runway hold point.
                                               DEP3 queues behind DEP2.
                                               On PVD DEP1 is shown in advance colour with sector
                                               coloured assumed.
10   16:28:00   The first of nine arrivals     First eight arrivals are coloured not-concerned. They are
                appear and land on R27R        coloured in the Not Concerned state as they are destined
                                               for gates in APRON_N.
                                               The last arrival is coloured in the Advance state. It is
                                               coloured advance as it is destined for a gate in
                                               CARGO_N.

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 70 of 197

                                                                             EUROCONTROL



                                                All entries appear in Runway/Taxiway section of Arrival
                                                list.
11                Just before ARR1 starts to    DEP2 and DEP3 are automatically assumed by unmanned
                  cross R09R, click(L) on       AVD (RWY_N).
                  callsign on DEP2 and          Entries move to Runway/Taxiway section in Departure list
                  select transfer. Similarly    and labels shown in concerned colour.
                  for DEP3                      They are then automatically given lineup and takeoff
                                                clearance and proceed onto the runway and accelerate
                                                and take off even though there is traffic crossing the
                                                runway.
                                                Entries removed form Departure list.
12                Follow arrivals as they       On leaving RWY_N ground sector ARR1,.., ARR8 proceed
                  cross runway.                 to APRON_N ground sector and park.
                                                Entries in the Arrival list for Arr1-ARR8 are eventually
                                                removed after arrival occupancy time (default 60s after
                                                parking).
                                                On leaving RWY_N ground sector ARR9 is coloured in the
                                                Advance Transferred state with the corresponding entry in
                                                the Arrival list moved to the APRON section
13                For ARR9 click(L) on          Label state updtated to Assumed.
                  callsign and    select        Entry in Arrival list APRON section.
                  assume.                       ARR9 continues to taxi to CARGO_N where it parks.
                                                Entry stays in Arrival list APRON section until it is removed
                                                after arrival occupancy time (default 300s after parking)
                  Terminate scenario


                  Launch and run scenario       Observe that same scenario is processed but RWY_N is
                  lfpg.gsdk.                    now a manned position
       16:24:30   Assume arrivals as they       Arrivals land and leave runway.
                  land.                         ARR1 proceeds to TP_33 and waits for clearance to taxi.
                                                Other arrivals queue behind ARR1
                                                TP_33 is marked as a taxipoint that requires taxi
                                                clearance to proceed. It is positioned so that clearance is
                                                required to cross runway.
                                                ARR5, … , ARR9 all occupy runway entry/exit point. i.e.
                                                no traffic rules on runway.
                  Give ARR1 taxi clearance.     ARR1 resumes to taxi.
                                                ARR2 moves to TP_33 and prompts for taxi clearance.
                                                Other arrivals queue behind ARR2.


     6.4    Advance Boundary Information

     6.4.1 ABI For Arrival
Scenario ID             CT_TCS_ABI_01
SRD Reference
Objective               Scenario demonstrates advance boundary and inbound information are reported
                        and affect the coordination jurisdiction of arrivals.
Dependencies            None
Resource File           <component test home>/tcs/abi/abi.gsdk


STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                       Page : 71 of 197

                                                                            EUROCONTROL



ID   Time       Actions       Expectations
1    16:12:00   Launch        One AVD RWY_N and one PVD LFPG appear.
                and     run
                scenario.
     16:12:47                 ABI message received for ARR1. (Check console output)
                              ARR1 enters RWY_N arrival list coloured in the Assumed Transferred state.
     16:13:47                 ABI message received for ARR2. (Check console output)
                              ARR2 enters RWY_N arrival list coloured in the Assumed Transferred state.
     16:30:47                 Inbound message received for ARR1. (Check console output)
                              ARR1 enters RWY_N arrival list coloured in the Advance state.
     16:31:47                 Inbound message received for ARR2. (Check console output)
                              ARR2 enters RWY_N arrival list coloured in the Advance state.
     16:41:47                 ARR1 enters RWY_N arrival list coloured in the Advance Transferred state.
     16:42:47                 ARR2 enters RWY_N arrival list coloured in the Advance Transferred state.
     16:42:47                 ARR1 enters airport sector.
     16:43:47                 ARR2 enters airport sector.
     16:43:34                 ARR1 lands at airport
     16:44:34                 ARR2 lands at airport.


                              ABI messages received 30 mins before entering sector (See Resource
                              COORDINATION.ADVANCE_BOUNDARY_INFORMATION_TIME).
                              Inbound messages received 12 mins before entering sector (See Resource
                              COORDINATION.ACTIVATION_TIME).
                              Arrivals transferred by approach sector 60 seconds before crossing airport
                              sector boundary (See Resource COORDINATION.ACTIVATION_TIME).




STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 72 of 197

                                                                           EUROCONTROL




     7     TIAS COMPONENT TESTS

     7.1    Update Rates

     7.1.1 CT_TIAS_UPD_01 Track – Track Update Rates


Scenario ID                CT_TIAS_UPD_01
SRD Reference              600
Objective                  Demonstrate that the TIAS component can provide track information at different
                           update rates.
Dependencies               None
Resource File              <component test home>/tias/update1.gsdk
                           <component test home>/tias/update6.gsdk


ID       Time    Actions                   Expectations
1                Run update1.gsdk          After departure gate occupancy track on AVD updates at 1
                                           second intervals
2                Run update6.gsdk          After departure gate occupancy track on AVD updates at 6
                                           second intervals
3                Compare update1.gsdk      TIAS.POSITION_UPDATE_INTERVAL = 1 in update1.gsdk
                 and update6.gsdk          (i.e. the default specified in TwrResources.java) and
                                           specifically set to 6 in update6.gsdk




STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                   f7919ee3-d7fb-4de6-9213-
                                                          1719658e70fc.doc

                                                        Page : 73 of 197

                                                                                  EUROCONTROL




     8     TFM COMPONENT TESTS

     8.1    Orders

     8.1.1 CT_TFM_ORDERS_01 – Changing Arrival Gate Test
Scenario ID                 CT_TFM_ORD_01
SRD Reference               2007TWR200
Objective                   Demonstrate that:
                                 1. It is possible to change the parking gate for an arrival.
                                 2. Changing to an invalid gate is reported correctly.
                                 3. It is possible to correct an invalid gate.
Dependencies                None
Resource File               <component test home>/tfm/gateorder.gsdk


ID       Time        Actions                        Expectations
1        16:12:00    Launch scenario.               AVD (for RWY_N) appears with map of LFPG.
                     Commence at normal
                     speed.
2        16:12:21                                   Aircraft LFPG_ARR appears on runway R27L, travelling in
                                                    westerly direction ready to be assumed by RWY_N.
                                                    The aircraft label state is Advance Transferred.
                                                    Aircraft decelerates on runway.
3        16:14:20                                   Aircraft leaves runway at TP_220. Trail dots are evenly
                                                    spaced.
5                                                   Label shows gate EN21. Same gate shown in Arrival list.
4                    Click(L) on Gate button        No menu appears.
5                    Click(L) on callsign button    Aircraft label becomes assumed colour.
                     and assume control of
                     aircraft.
6                    Click(L) on Gate button.       Gate menu appears.
7                    On menu choose                 Label shows “GATE AXAXAX” in warning colour. As does
                     AXAXAX (unreachable)           Arrival list.
8                    Click(L) on Gate button        Warning removed and label indicates gate EN21, as does
                     choose EN21                    Arrival list
9                    Click(L) on type               The route editor is opened, showing a line leading to the
                     designator.                    next taxi point on the vehicle route, which is also circled, to
                                                    show it has been selected as a constraint point. A line
                                                    joins that circle to the mouse cursor.
10                   Click( R)                      The route editor is closed.


STATUS                                                                                                         TITLE
Company Ref.                                                                                    Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                    Page : 74 of 197

                                                                              EUROCONTROL



11               Click(L) on type               The route editor is opened.
                 designator.
12               Using yellow circle to         When label highlighted label shows new gate.
                 capture gate choose gate
                                                New gate also shown in Arrival list.
                 EN24 by double
                 clicking(L) on gate symbol.
13               Using yellow circle to         When label highlighted label shows new gate.
                 capture gate and using
                                                New gate also shown in Arrival list.
                 kink to capture an
                 intermediate taxipoint,        (Note not all routes will be valid.
                 choose new route via
                 intermediate point by          When invalid route there is no indication of error on
                 clicking(L) on intermediate    AVD.)
                 point symbol.
14               Click(R) on type               View path to confirm intermediate point.
                 designator.
15    n/a        Scenario continues. When       Aircraft continues to taxi to new gate.
                 reaching TP_86 give
                 VACate and Taxi
                 clearances.




     8.1.2 CT_TFM_ORDERS_02 – Changing Departure Runway Test


Scenario ID            CT_TFM_ORD_02
SRD Reference          2007TWR200
Objective              Demonstrate that:
                            1. It is possible to change the runway for a departure.
                            2. Changing to an invalid runway is reported correctly.
                            3. It is possible to correct an invalid runway.
Dependencies           None
Resource File          <component test home>/tfm/runwayorder.gsdk


ID    Time       Actions                        Expectations
1     16:12:00   Launch scenario.               AVD (RWY_N) appears with map of LFPG
                 Commence at normal
                 speed.
2     16:12:16                                  Aircraft DEP1 appears at gate U6 ready to be assumed by
                                                RWY_N.
                                                Label shown in advance colour.
                                                Label shows callsign RWY_N in Advance state colours.
3                                               Label shows runway R09R. Departure list shows same

STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 75 of 197

                                                                             EUROCONTROL



                                              runway.
4              Click(L) on Runway button      No menu appears.
5              Click(L) on callsign button    Aircraft label shown in the Assumed state.
               and assume control of
               aircraft.
6              Click(L) on callsign button    Aircraft begins to taxi immediately if occupancy time has
               and issue Pushback             expired otherwise waits for occupancy time expiry.
               clearance.
7                                             Aircraft taxis to pushback point TP_1215 and stops.
8              Click(L) on Runway             Runway menu appears.
               button.
9              On menu choose                 Label shows “AXAXAX” in warning colour. Departure list
               AXAXAX (unreachable)           shows same warning.
10             Click(L) on Runway button      When highlighted label shows R09R. Departure list shows
               and select R09R                same runway.


11             Click(L) on type               The route editor is opened, showing a line leading to the
               designator.                    next taxi point on the vehicle route, which is also circled, to
                                              show it has been selected as a constraint point. A line
                                              joins that circle to the mouse cursor.
12             Click( R)                      Route editor disappears.
13             Click(L) on type               Route editor appears
               designator.
14             Using yellow circle to         When label highlighted label shows new runway.
               capture TP_32 on R09L
                                              New runway also shown in Departure list.
               (the second entry point
               from the left end of the
               runway)
15             Choose a new route via         When label highlighted label shows new runway.
               an intermediate point by
                                              New runway also shown in Departure list.
               clicking(L) on intermediate
               point symbol then double       (Note not all routes will be valid)
               clicking (L) on the runway
               entry/exit point
16             Click(R) on type               Route display appears. View path to confirm intermediate
               designator.                    point.
17             Click(R)                       Route display disappears
18   n/a       Click(L) on callsign button    Aircraft begins to taxi to new runway and takesoff
               and issue Taxi clearance.
               Click(L) on callsign button
               and issue Lineup
               clearance.
               Click(L) on callsign button
               and issue takeoff
               clearance.
               Also give any required taxi
STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 76 of 197

                                                                           EUROCONTROL



                 clearances as aircraft
                 travels to runway.



     8.1.3 CT_TFM_ORDERS_03 – Changing Standard Instrument Departure (SID) Test
Scenario ID            CT_TFM_ORD_03
SRD Reference
Objective              Demonstrate that when a Tower Controller changes the allocated SID, the
                       departure flies the new nominated SID in the ATC system.
                       Note: At present there is no way of changing the SID without changing the
                       runway. Also when the controller selects a new runway the system selects the first
                       SID found for that runway.
Dependencies           None
Resource File          <component test home>/tcs/integrated/departure.gsdk


ID    Time       Actions                      Expectations
1                Check
                 departure_traffic.dat and
                 confirm DEP1 and DEP2
                 are both planned to fly
                 R09RSID
2     16:12:00   Launch scenario.             RWY_N AVD appears with map of LFPG.
                                              LFPG and UNIT_FS PVDs appears with map of airspace
                                              surrounding LFPG.
3     16:12:16                                Aircraft DEP1, DEP2, DEP3 appear on RWY_N AVD.
                                              The label state is Advance Transferred.
4                Assume DEP1.                 Label state - Assumed.
5                Give DEP1 pushback           DEP1 starts to pushback.
                 clearance.
                                              At end of push back the aircraft stops.
                                              Note label indicates takeoff runway is R09R.
6                Give DEP1 taxi clearance     DEP1 starts to taxi to runway.
7                Give DEP1 takeoff            DEP1 taxis to runway and takesoff.
                 clearance.
8                                             On UNIT_FS PVD confirm aircraft flies SID R09R_SID1
                                              (i.e. fixes    R09RSID, LFPGE, CGZ, REM) before
                                              continuing to SEB.
9                Assume DEP2.                 Label coloured in assumed colour.
10               Give DEP2 pushback           DEP2 starts to pushback.
                 clearance.
                                              At end of push back the aircraft stops.
                                              Note label indicates takeoff runway is R09R.
11               Give DEP2 taxi clearance     DEP2 starts to taxi to runway.

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 77 of 197

                                                                               EUROCONTROL



12                  Change runway from            Runway updated in label.
                    R09R to R27R.
13                  Give DEP2 takeoff             DEP2 taxis to runway and takesoff
                    clearance.
                                                  Note the following error message appeaars in the console:
                    Also give any further taxi    “DEP2 will not attain take-off speed by end of runway
                    clearances required to        R27R”
                    reach runway.

14                                                On UNIT_FS PVD confirm aircraft flies SID R27R_SID1
                                                  (i.e. fixes R27RSID, PON, EVX) before continuing to SEB.



     8.1.4 CT_TFM_ORDERS_04 – Abort Take-off
Scenario ID                CT_TFM_ORD_04
SRD Reference
Objective                  To demonstrate that after aborting take-off departures return to their stand.
Dependencies               None
Resource File              <component test home>/tfm/abortDeparture/abortHybrid.gsdk


ID   Time       Actions                                    Expectations
1    16:12:00   Launch and run scenario.                   AVD for RWY_N and PVD for LFPG appear.
     16:12:16                                              DEP1 and DEP2 appear as advance transferred,
                                                           both requesting taxi clearance.
                RWY_N gives DEP1 then DEP Taxi             DEP1 and DEP2 become assumed and start to
                clearance.                                 taxi.
                Once DEP1 and DEP2 have turned left        TOT field in Departure list indicates ↑↑↑↑↑. DEP1
                off the apron, RWY_N gives both            and DEP2 continue to taxi to runway.
                departures clearance to takeoff
                Immediately after giving take-off          TOT field in Departure list indicates ABORT for
                clearance RWY_N aborts take-off for        DEP2. DEP1 continues to taxi to runway. DEP2‟s
                DEP2.                                      new route takes it back to its original stand.
                As DEP1 accelerates down runway            DEP1 immediately slows to taxi speed, taxis to the
                RWY_N aborts take-off                      end of the runway, and leaves runway to taxi back
                                                           to original stand.
                RWY_N issues taxi clearances when          DEP1 taxis to original stand.
                requested.




STATUS                                                                                                     TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 78 of 197

                                                                             EUROCONTROL



     8.2    Clearances

     8.2.1 CT_TFM_CLR_01 – Pushback, Taxi, Lineup and Takeoff Clearances Test
Scenario ID              CT_TFM_CLR_01
SRD Reference            560, 570, G130, 300
Objective                To demonstrate and confirm that:
                                Pushback, taxi, lineup and takeoff clearances control the movement of a
                                 departure.
                                Hold clearance can temporarily stop an aircraft
                                Takeoff clearance also gives lineup clearance.
Dependencies             None
Resource File            <component test home>/tfm/clearances.gsdk


ID    Time        Actions                        Expectations
1     16:12:00    Launch scenario.               AVD for RWY_N appears with map of LFPG.
2                 Commence scenario at
                  normal speed.
3     16:12:17                                   DEP1 appears at gate U6.
                                                 DEP2 appears at gate V2.
                                                 DEP3 appears at gate V4.
4                 For each flight in turn        All label coloured in the Assumed state.
                  click(L) on callsign and
                  select assume.
5                 For DEP1 click(L) on           DEP1 begins to pushback.
                  callsign and select
                  pushback.
6                 Wait until DEP1 reaches        DEP1 stops.
                  TP_1215.
7                 For DEP1 click(L) on           DEP1 begins to taxi to runway perimeter.
                  callsign and select taxi
8                 As DEP1 travels to             DEP1 stops moving, Hold sysmbol is displayed in the
                  runway click(L) on DEP1        label.
                  callsign and select hold
9                 For DEP1 click(L) on           DEP1 resumes journey.
                  callsign and select taxi
10                                               DEP1 reaches lineup.
11                For DEP1 click(L) on           DEP1 begins to taxi on to runway, LUP symbol is
                  callsign and select lineup     displayed in the label.
12                                               DEP1 reaches runway entry point.
13                For DEP1 click(L) on           Take off clearance symbol is displayed in the label and
                  callsign and select takeoff    DEP1 begins to accelerate down the runway and takes off.

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 79 of 197

                                                                              EUROCONTROL




14               For DEP2 click(L) on             DEP2 begins to pushback.
                 callsign and select
                 pushback.
15               Wait until DEP2 reaches          DEP2 stops.
                 TP_1215.
16               For DEP2 click(L) on             DEP2 starts to taxi.
                 callsign and select taxi
17               For DEP2 click(L) on             DEP2 continues to taxi to runway perimeter, then on to
                 callsign and select LUP          runway entry point.
                                                  The lineup clearance symbol is displayed in the label.
                                                  Reselect menu to check LUP option is not available.
18               For DEP2 click(L) on             DEP2 starts to accelerate down runway and takesoff.
                 callsign and select takeoff


19               For DEP3 click(L) on             DEP3 begins to pushback.
                 callsign and select
                 pushback.
20               Wait until DEP3 reaches          DEP3 stops.
                 TP_1215.
21               For DEP3 click(L) on             DEP3 begins to taxi to runway perimeter.
                 callsign and select taxi
22               As taxiing to runway             The takeoff clearance sysmbol is displayed in the label.
                 perimeter for DEP3
                                                  Reselect menu to check that lineup and takeoff options
                 click(L) on callsign and
                                                  not available.
                 select takeoff.
                                                  DEP3 continues to taxi to runway perimeter, then on to
                                                  runway, accelerates and takesoff



     8.2.2 CT_TFM_CLR_02 – Clearance To Gate For Arrival Test
Scenario ID             CT_TFM_CLR_02
SRD Reference           G131
Objective               To demonstrate and confirm for an arrival that by defining appropriate taxipoints
                        requiring “clearance to proceed” that clearance is required to start travelling to the
                        gate after leaving runway perimeter.
Dependencies            None
Resource File           <component test home>/tfm/clearedtogate.gsdk


ID    Time       Actions                          Expectations
1     16:12:00   Launch scenario.                 AVD for RWY_N appears with map of LFPG.
2                Commence scenario          at
                 normal speed.

STATUS                                                                                                     TITLE
Company Ref.                                                                              Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 80 of 197

                                                                            EUROCONTROL



3     16:12:17                                ARR appears on runway R27L.
4                For ARR click(L) on          Label shows GroundUnit=GATE.
                 callsign and   select
                                              All label coloured in the Assumed state.
                 assume.
5                                             ARR decelerates and leaves runway at TP_85.
                                              ARR stops at TP_86 waiting for clearance to taxi. (i.e.
                                              clearance to continue)
6                For ARR click(L) on          ARR continues to taxi to its gate where it parks.
                 callsign   and    select
                 VACate then Taxi.



     8.2.3 CT_TFM_CLR_03 – Cleared To Cross Runway For Departure Test
Scenario ID             CT_TFM_CLR_03
SRD Reference           530
Objective               To demonstrate and confirm for departures/arrivals that by defining appropriate
                        taxipoints requiring “clearance to proceed” that clearance is required to cross over
                        other runways on taxi route to the final runway/gate.
Dependencies            None
Resource File           <component test home>/tfm/clearedtocrossrwy.gsdk


ID    Time       Actions                      Expectations
1     16:12:00   Launch scenario.             AVD for RWY_N appears with map of LFPG.
2                Commence scenario at
                 normal speed.
3     16:12:17                                DEP appears at gate EN24.
                                              ARR appears on runway R27R.
4                For ARR click(L) on          All label coloured assumed.
                 callsign and select
                 assume.
                 When aircraft leaves
                 runway, click(L) on
                 callsign and select VAC.
5                                             ARR decelerates and leaves runway at TP_32.
                                              ARR stops at TP_28 waiting for clearance to taxi. (i.e.
                                              clearance to cross runway)
6                For ARR click(L) on          ARR continues on taxi route journey to cross runway
                 callsign and select taxi.    R27L.
                                              After crossing R27L and on reaching TP_86 ARR stops
                                              waiting for another taxi clearance. (i.e. clearance to taxi to
                                              gate)
7                For ARR click(L) on          ARR continues to taxi to its gate where it parks.
                 callsign and select taxi.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 81 of 197

                                                                            EUROCONTROL



8              For DEP click(L) on            Label state updated to Assumed.
               callsign and select
               assume.
9              For DEP click(L) on            DEP begins to taxi to R09L.
               callsign and select taxi.
10             Wait until DEP reaches         DEP stops for clearance to cross runway.
               TP_1467.
11             For DEP click(L) on            DEP begins to taxi across R09R.
               callsign and select taxi
12             Wait until DEP reaches         DEP stops at TP_33 for taxi clearance.
               TP_33.

13             For DEP click(L) on            DEP resumes journey.
               ground sector and select
               taxi
14                                            DEP reaches lineup point and stops.
15             For DEP click(L) on            Lineup clearance symbol is displayed in the label. DEP
               callsign and select lineup     begins to taxi on to R09L.
16                                            DEP reaches runway entry point and stops.
17             For DEP click(L) on            Takeoff clearance symbol is displayed in the label. DEP
               callsign and select takeoff    begins to accelerate down the runway and takes off.




STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 82 of 197

                                                                           EUROCONTROL




     9      TFPM COMPONENT TESTS

     9.1    Turnaround With Progress Events

     9.1.1 CT_TFPM_01 – Progress Events Test


Scenario ID             CT_TFPM_01
SRD Reference           G90, 400, 580
Objective               Demonstrate that the TFPM component can recognise the following events.
                                   TouchDownEvent
                                   GroundSectorEntryEvent
                                   GroundSectorExitEvent
                                   ParkedAtGateEvent
                                   TurnaroundEvent
                                   PushBackStartEvent
                                   TaxipointPassedEvent
                                   PushBackCompleted Event
                                   StartTaxiEvent
                                   LineUpStartEvent
                                   LineUpCompletedEvent
                                   TakeOffEvent
                                   RunwayExitEvent (not used)
                                   TerminatedEvent

                        The test is used for illustrative purposes only, as the events either trigger or are
                        triggered by those observations listed below.

Dependencies            None
Resource File           <component test home>/tfpm/turnaroundTEST.gsdk


ID   Time    Actions    Expectations
      n/a
     1.      Launch     TWY AVD window appears, with a view of the tower system.
             scenario
                        PVD window appears, with a view of French airspace.
                        A console window appears.
                        Unmanned uTCWPs present acting as runway and taxiway controllers.
     2.                 “ARR” appears in the PVD, traveling west, approaching airport.
                        Label indicates No clearance due.
                        “ARR” descends and lands on R27L.
                        Disappears from PVD.
                        Label colour indicates Advance state.
                        (GroundSectorEntryEvent, and TouchDownEvent)
     3.                 “ARR” leaves runway.

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                    f7919ee3-d7fb-4de6-9213-
                                           1719658e70fc.doc

                                           Page : 83 of 197

                                                                  EUROCONTROL



               “ARR” leaves runway sector and is automatically transferred to TWY_N.
               The label state changes to Assumed
               (GroundSectorExitEvent)
   4.          “ARR” stops, label indicates Taxi clearance due.
               Clearance automatically given.
               “ARR” continues to U6.
               “ARR” reaches gate U6, and parks there.
               (ParkedAtGateEvent and TerminatedEvent)
   5.          “ARR” disappears from the system.
   6.          “DEP” appears at gate U6.
               (TurnaroundEvent)
   7.          ”DEP” automatically assumed.
               Label indicates Pushback clearance due.
               Clearance automatically given.
               “DEP” begins to pushback to target TP_1215.
               (PushBackStartEvent)
   8.          “DEP” reaches TP_1215, and pauses for taxi clearance.
               (TaxipointPassedEvent and PushBackCompleted Event)
   9.          Taxi clearance automatically given.
               “DEP” begins to taxi towards runway R09R.
               (StartTaxiEvent)
   10.         Automatically transferred to RWY.
               DEP reaches TP_16 and stops.
               Label indicates Lineup clearance due.
               Clearance automatically given.
               (LineUpStartEvent)
   11.         “DEP” reaches TP_15 at start of runway R09R.
               Label indicates Takeoff clearance due.
               (LineUpCompletedEvent)
   12.         Clearance automatically given.
               “DEP” begins to take off.
               “DEP” takesoff from runway on AVD.
               (TakeOffEvent)
   13.         “DEP” appears on PVD, at takeoff position (i.e. some way between fixes R27L
               and R09R, FL4=airport elevation 387ft). It is travelling east and ascending.
   14.         Examine narrative and confirm all tests passed.



STATUS                                                                                    TITLE
Company Ref.                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 84 of 197

                                                                              EUROCONTROL



     9.1.2 CT_TFPM_02 – Progress Events Test
Scenario ID                CT_TFPM_02
SRD Reference
Objective                  Demonstrate that the TFPM component can recognise the following events.
                                      GateOccupied
                                      GateVacated

                           The test is used for illustrative purposes only, as the events either trigger or are
                           triggered by those observations listed below.

Dependencies               None
Resource File              <component test home>/tfpm/gateoccupiedTEST.gsdk


ID    Time       Actions                 Expectations
      16:12:00
     1.          Launch scenario.        AVD for RWY_N appears with map of LFPG.
     2.                                  DEP1 appears at gate EN20.
                                         ARR1 lands on R27R.
                                         ARR1 label indicates gate EN20 occupied.
     3.                                  DEP1 begins to taxi.
                                         ARR1 label indicates gate EN20 empty.
     4.                                  ARR2 lands on R27R.
                                         ARR1 continues to EN20 and parks.
                                         ARR2 label indicates EN20 occupied.
     5.                                  ARR1 terminates.
                                         ARR2 label indicates N20 empty.
     6.                                  ARR3 lands on R27R.
                                         ARR2 continues to EN20 and parks.
                                         ARR3 label indicates EN20 occupied.
                                         ARR2 turns-around as DEP2.
                                         ARR3 label remains indicating EN20 occupied.
     7.                                  DEP2 starts taxiing.
                                         ARR3 indicates EN20 empty.
     8.                                  Examine narrative and confirm all tests passed.




STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 85 of 197

                                                                              EUROCONTROL




     10 GRAPHICAL COMPONENT TESTS

     10.1 TCWP

     10.1.1 Labels

     10.1.1.1 CT_TCWP_LABEL_01 – Track Labels

Scenario ID                CT_TCWP_LABEL_01
SRD Reference              G20, 880, 2005APT60, 880
Objective                  Demonstrate that arrival/departing aircraft will have its details displayed in the
                           track label.
                           Confirm that runway, gate and callsign fields are active fields where controller
                           orders can be issued.
                           Confirm vehicle labels are insensitive.
Dependencies               None
Resource File              <component test home>/tcwp/labels/labels.gsdk


ID    Time       Actions                     Expectations
1     16:12:00   Launch scenario.
2     16:13:30   Stop scenario               ARR1 and DEP1 have entered in the scenario.
                                             Labels are in advance colour with callsign coloured assumed.
                                             Arrivals show callsign and gate in label. When cursor focused
                                             on label, label expands to show aircraft type suffixed with wake
                                             category.
                                             Departures show callsign and gate in label. When cursor
                                             focused on label, label expands to show CTOT, aircraft type
                                             suffixed with wake category.
3                Move cursor in labels       Expanded labels show aircraft type suffixed with wake
                 for    arrivals  and        category.
                 departures.
4                On ARR1 click(L) on         No menu, field inactive.
                 gate field.
5                On ARR1 click(L) on         Callsign menu displayed showing assume, mark and cancel
                 callsign field.
6                Select assume               Entry becomes assumed colour.
7                On ARR1 click(L) on         Gate menu displayed.
                 gate field.
8                Select EN24                 Gate field updated in label.


STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                 Page : 86 of 197

                                                                             EUROCONTROL




9              On DEP1 click(L) on       No menu, field inactive.
               runway field.
10             On DEP1 click(L) on       Callsign menu displayed showing:
               callsign field.
                                         Assume, Push, Mark, Cancel.
11             Select assume             Entry becomes assumed colour.
12             On DEP1 click(L) on       Runway menu displayed
               runway field.
13             Select R09L               Runway field updated in label.


14             On DEP1 click(L) on       Callsign menu displayed showing:
               callsign field.
                                         Push, Cross, Enter, Mark, Cancel.
15             Select pushback.          DEP1 completes pushback manoeuvre.
               Unfreeze scenario.
16             On DEP1 click(L) on       Callsign menu displayed showing:
               callsign field.
                                         Taxi, Cross, Enter, Mark, Cancel.
17             Select Taxi               DEP1 starts taxiing.
18             On DEP1 click(L) on       Callsign menu displayed showing:
               callsign field.
                                         Tof, Lup, Clu, Hold, Cross, Enter, Mark, Cancel
19             Select Hold               DEP1 stops, hold symbol is displayed in label.
20             On DEP1 click(L) on       Callsign menu displayed showing:
               callsign field.
                                         Tof, Lup, Clu, Taxi, Cross, Enter, Mark, Cancel
21             Select Taxi               DEP1 continues taxiing.
22             On DEP1 click(L) on       Callsign menu displayed showing:
               callsign field.
                                         Tof, Lup, Clu, Taxi, Cross, Enter, Mark, Cancel
23             Select LUP, then          Callsign menu displayed showing:
               click(L) on callsign
                                         TOF, Hold, Cross, Enter, Mark, Cancel.
               field.
19             Select Takeoff
20             On DEP1 click(L) on       Callsign menu displayed showing:
               callsign field.
                                         Cross, Enter, Mark, Abort, Cancel
21             Select CANCEL             Menu is removed, DEP1 is proceeds towards runway.
22             Click on vehicle label.   No menus appear.




STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                       Page : 87 of 197

                                                                                  EUROCONTROL



     10.1.2 Arrival Departure Lists

     10.1.2.1 CT_TCWP_LIST_01 – Arrival Departure Lists

Scenario ID                CT_TCWP_LIST_01
SRD Reference              G20, 880, 900, 920, 2005APT60, 880
Objective                  Demonstrate that arrival/departing aircraft will have its details displayed in the
                           Arrival/Departure List.
                           Confirm that runway, gate and callsign fields are active fields where controller
                           orders can be issued.
                           Confirm that highlighting an entry in the list highlights the track label.
Dependencies               None
Resource File              <component test home>/tcwp/lists/arrdep_list.gsdk


ID    Time       Actions                     Expectations
1     16:12:00   Launch scenario.            AVDs for TWY_N, RWY_N, APR_N and CARGO_N appear
                                             with map of LFPG.


                                             On RWY_N AVD:
                                             Arrival list shows:
                                             FINAL, RUNWAY/TAXIWAY/APRON, GATE
                                             Departure list shows:
                                             GATE, APRON/TAXIWAY/RUNWAY, CTR


                                             On TWY_N AVD:
                                             Arrival list shows:
                                             RUNWAY, TAXIWAY, APRON
                                             Departure list shows:
                                             APRON,TAXIWAY, RUNWAY


                                             On APR_N and CARGO_N AVD:
                                             Arrival list shows:
                                             TAXIWAY, APRON, GATE
                                             Departure list shows:
                                             GATE, APRON, TAXIWAY
2     16:13:30   Stop scenario               ARR1 and DEP have entered in the scenario.
                                             On RWY_N AVD:
                                             Arrival list shows:

STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                 Page : 88 of 197

                                                                           EUROCONTROL



                                        ARR1 in FINAL in advance transferred colours.
                                        Departure list shows:
                                        DEP1 in GATE in not concerned colour.


                                        On TWY_N AVD:
                                        Arrival list empty.
                                        Departure list empty.


                                        On APR_N AVD:
                                        Arrival list empty.
                                        Departure list:
                                        DEP1 in GATE in advance transferred colours.


                                        On CARGO_N AVD:
                                        Arrival list empty.
                                        Departure list:
                                        DEP1 in GATE in not concerned colour.


4              On RWY_N Arrival list    No menu, field inactive.
               click(L) on   ARR1
               stand field.
5              On RWY_N Arrival list    Callsign menu displayed allowing assume.
               click(L) on     ARR1
               callsign field.
6              Select assume            Entry becomes assumed colour and moves to Arrival list
                                        RUNWAY/TAXIWAY/APRON section.
8              On RWY_N Arrival list    Gate menu displayed.
               click(L) on   ARR1
               stand field.
9              Select EN24              Gate field updated in list and label.


10             On APR_N Departure       No menu, field inactive.
               list click(L) on DEP1
               runway field.
               If necessary filter on
               runway field.
12             On APR_N Departure       Callsign menu displayed allowing assume.
               list click(L) on DEP1
               callsign field.
13             Select assume            Entry becomes assumed colour.
15             On APR_N Departure       Runway menu displayed

STATUS                                                                                             TITLE
Company Ref.                                                                        Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 89 of 197

                                                                              EUROCONTROL



                 list click(L) on   DEP1
                 runway field.
16               Select R09L                Runway field updated in list and label.


17               On APR_N Departure         Entry line in list is highlighted and corresponding track label is
                 list move cursor over      highlighted.
                 DEP1 entry.
18               Move cursor off entry      Items no longer highlighted
19               On    APR_N      move      Track lable highlighted and corresponding entry in Departure
                 cursor over track label    list also highlighted.
                 for DEP1.
20               Move cursor off entry      Items no longer highlighted



     10.1.2.2 CT_TCWP_LIST_02 – Navigation Times
Scenario ID                CT_TCWP_LIST_02
SRD Reference
Objective                  The scenario demonstrates how for departures off block times (OBT) and take off
                           times (TOT) change from estimates to targets and finally to actual times. Similarly
                           for arrivals the scenario demonstrates how landing times (LDT) and in block times
                           (IBT) change from estimates to targets and then finally actuals.
                           The first run of the scenario the controller issues Clearance for Take-off on
                           request.
                           The second run of the scenario Clearance for Take-off and Clearance To Land
                           are given prior to request and landing respectively.
                           Note the estimate and target times for OBT, TOT, LDT and IBT are for guidance
                           only as delays in issuing clearance can cause deviations. Actual times should
                           match the time as given on the clock.
Dependencies               None
Resource File              <component test home>/tcwp/lists/navigationTimes.gsdk


ID    Time       Actions                    Expectations
1.    16:12:00   Launch       and     run   One AVD (RWY_N) and one PVD (LFPG) appear.
                 scenario.
2.    16:12:16                              DEP1 appears on AVD and in Departure list as advance
                                            transferred and requesting pushback clearance.
                                            OBT =E20:35. Estimated from flight plan ETD.
                                            TOT = E20:44. Estimated from OBT and calculated taxi time.
3.    16:12:30   Freeze scenario
4.    16:12:30   RWY_N gives DEP1           DEP1 becomes assumed.
                 pushback clearance.
5.    16:12:30   Unfreeze scenario

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 90 of 197

                                                                            EUROCONTROL



6.    16:12:30                            DEP1 starts pushback.
                                          OBT =A16:12. Actual off block time.
                                          TOT = T16:21. Target time derived from OBT and calculated
                                          taxi time.
7.    16:12:48   Note.                    ARR1 appears in Arrival list as unconcerned.
                                          LDT = E16:43. Estimated from received ATC ABI message.
                                          IBT = E16:49. Estimated from LDT and calculated taxi time.
8.               As DEP1 continues to     DEP1 continues on to runway and requests Take-off clearance
                 runway give necessary
                 Taxi    and    Lineup
                 clearances.
9.               RWY_N gives DEP1         DEP1 starts takeoff.
                 take-off clearance.
                                          OBT =A16:12. Actual off block time.
                                          TOT = ↑↑↑↑↑. Indicates cleared to takeoff
10.              Take-Off.                DEP1 takes-off, indicated by automatic transfer of jurisdiction.
                                          OBT =A16:12. Actual off block time.
                                          TOT = A16:21. Actual takeoff time.
11.   16:30:48   Inbound                  ARR1 appears in Arrival list as advance.
      (approx)                            LDT = E16:43. Estimated from received ATC Inbound
                                          message.
                                          IBT = E16:49. Estimated from LDT and calculated taxi time.
12.   16:41:50                            ARR1 appears in Arrival list as advance transferred.
      (approx)                            LDT and IBT remain unchanged.
13.              RWY_N         assumes    ARR1 coloured assumed in Arrival list.
                 ARR1
                                          LDT and IBT remain unchanged.
14.              RWY_N issues landing     LDT = ↓↓↓↓↓. Indicates cleared to land.
                 clearance
15.   16:43:45   ARR1 lands.              ARR1 coloured assumed in Arrival list.
                                          LDT = A16:43. Actual landing time.
                                          IBT = E16:49. Estimate time derived from LDT and calculated
                                          taxi time.
16.              Give ARR1 necessary      ARR1 taxis to its stand.
                 taxi clearances.
17.   16:49:25   ARR1 arrives at stand.   ARR1 coloured assumed in Arrival list.
                                          LDT = A16:43. Actual landing time.
                                          IBT = A16:49. Actual in block time.




STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                     Page : 91 of 197

                                                                             EUROCONTROL



      10.1.2.3 CT_TCWP_LIST_03 – Changing Navigation Times
Scenario ID                 CT_TCWP_LIST_03
SRD Reference               G20. 880, 900, 920, 2005APT60
Objective                   The scenario demonstrates that by changing the destination of the taxi route for
                            arrivals and departures the navigation times for Take-off Time (TOT) and Inblock
                            Time (IBT) are recalculated.
                            Note the estimate and target times for OBT, TOT, LDT and IBT are for guidance
                            only as delays in issuing clearance can cause deviations. Actual times should
                            match the time as given on the clock.
Dependencies                None
Resource File               <component test home>/tcwp/lists/navigationTimes.gsdk


ID     Time       Actions                    Expectations
1.     16:12:00   Launch       and     run   One AVD (RWY_N) and one PVD (LFPG) appear.
                  scenario.
2.     16:12:16                              DEP1 appears on AVD and in Departure list as advance
                                             transferred and requesting pushback clearance.
                                             OBT =E20:35. Estimated from flight plan ETD.
                                             TOT = E20:44. Estimated from OBT and calculated taxi time.
3.     16:12:30   Freeze scenario
4.     16:12:30   RWY_N gives DEP1           DEP1 becomes assumed.
                  pushback clearance.
5.     16:12:30   Unfreeze scenario
6.     16:12:30                              DEP1 starts pushback.
                                             OBT =A16:12. Actual off block time.
                                             TOT = T16:21. Target time derived from OBT and calculated
                                             taxi time.
7.     16:12:48   Note.                      ARR1 appears in Arrival list as unconcerned.
                                             LDT = E16:43. Estimated from received ATC ABI message.
                                             IBT = E16:49. Estimated from LDT and calculated taxi time.
8.
9.                RWY_N      changes         OBT =A16:12. Actual off block time.
                  runway to R27L for
                                             TOT = T16:21. Target time derived from OBT and calculated
                  DEP1
                                             taxi time.
10.               As DEP1 continues to       DEP1 continues on to runway and requests Take-off clearance
                  runway give necessary
                  Taxi    and    Lineup
                  clearances.
11.               RWY_N gives DEP1           DEP1 starts takeoff.
                  take-off clearance.
                                             OBT =A16:12. Actual off block time.


STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                       Page : 92 of 197

                                                                                EUROCONTROL



                                              TOT = ↑↑↑↑↑. Indicates cleared to takeoff
12.               Take-Off.                   DEP1 takes-off, indicated by automatic transfer of jurisdiction.
                                              OBT =A16:12. Actual off block time.
                                              TOT = A16:21. Actual takeoff time.
13.    16:30:48   Inbound                     ARR1 appears in Arrival list as advance.
       (approx)                               LDT = E16:43. Estimated from received ATC Inbound
                                              message.
                                              IBT = E16:49. Estimated from LDT and calculated taxi time.
14.    16:41:50                               ARR1 appears in Arrival list as advance transferred.
       (approx)                               LDT and IBT remain unchanged.
15.               RWY_N             assumes   ARR1 coloured assumed in Arrival list.
                  ARR1
                                              LDT and IBT remain unchanged.
16.    16:43:45   ARR1 lands.                 ARR1 coloured assumed in Arrival list.
                                              LDT = A16:43. Actual landing time.
                                              IBT = E16:49. Estimate time derived from LDT and calculated
                                              taxi time.
17.               RWY_N changes stand         LDT = A16:43. Actual landing time.
                  to I49 (i.e. further
                                              IBT = E16:49. Estimate time derived from LDT and calculated
                  West)
                                              taxi time.
                  Give ARR1 necessary         ARR1 taxis to its stand.
                  taxi clearances.
       16:49:25   ARR1 arrives at stand.      ARR1 coloured assumed in Arrival list.
                                              LDT = A16:43. Actual landing time.
                                              IBT = A16:49. Actual in block time.




      10.1.3 Menus

      10.1.3.1 CT_TCWP_MENUS_01 – Menu Default Selection
Scenario ID                 CT_TCWP_MENUS_01
SRD Reference
Objective                   Demonstrate that default positioning of cursor for menus will be based upon
                            current traffic state and selection type.
                            For the callsign menu, when coordination state is advance + transferred then
                            default position on opening menu will be at Assume otherwise it is Transfer unless
                            a clearance is required.
                            For arrivals
                                    The only clearance required is Taxi.

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                    f7919ee3-d7fb-4de6-9213-
                                                           1719658e70fc.doc

                                                         Page : 93 of 197

                                                                                   EUROCONTROL



                                     On the Stand menu the default position will be on the current stand
                                      selected.
                            For departures:
                                     When clearance required the order priority will be Startup, Pushback,
                                      Taxi, Lineup, Takeoff, Abort.
                                     On the Runway menu the default position will be on the current runway
                                      selected.
Dependencies                None
Resource File               <component test home>/tcwp/menus/menusAirGrd.gsdk
                            <component test home>/tcwp/menus/menusHybrid.gsdk


ID   Time       Actions                             Expectations
1    16:12:00   Launch       and       run          Two AVDs appear RWY_N and RWY_N(Pilot)
                menusAirGrd.gsdk scenario.
2    16:12:16                                       Arrivals and departures start to appear
ARRIVAL
                                                    ARR1 lands and decelerates to taxi speed and on leaving the
                                                    runway and reaching first junction stops and prompts for taxi
                                                    clearance.
                RWY_N(Pilot)         clicks   on    Callsign menu displayed with cursor position on taxi. (No
                ARR1 callsign.                      assume available to pilots).
                RWY_N(Pilot)              selects   Menu disappears
                cancels.
                RWY_N       clicks   on   ARR1      Callsign menu displayed with cursor position on assume.
                callsign.
                RWY_N selects assume.               RWY_N and RWY_N(Pilot) see ARR1 as assumed.
                RWY_N       clicks   on   ARR1      Callsign menu displayed with cursor position on VACate.
                callsign.
                RWY_N selects vacate.
                RWY_N       clicks   on   ARR1      Callsign menu displayed with cursor position on taxi.
                callsign.
                RWY_N selects taxi.                 Taxi clearance is removed and RWY_N(Pilot) is prompted to
                                                    taxi.
                RWY_N(Pilot) accepts taxi           ARR1 starts to taxi to gate.
                command.
                RWY_N       clicks   on   ARR1      Callsign menu displayed with cursor position on Hold.
                callsign.
                RWY_N selects hold.
                RWY_N(Pilot) selects hold           ARR1 stops.
                command.
                RWY_N       clicks   on   ARR1      Callsign menu displayed with cursor position on taxi.
                callsign.

STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                    f7919ee3-d7fb-4de6-9213-
                                                           1719658e70fc.doc

                                                         Page : 94 of 197

                                                                                  EUROCONTROL



               RWY_N selects taxi.                  RWY_N(Pilot) is prompted to taxi.
               RWY_N(Pilot) accepts taxi            ARR1 continues to taxi to stand.
               command.
                                                    Note stand is EN21.


               RWY_N(Pilot)     clicks         on   Stand menu displayed with cursor position on EN21.
               ARR1 stand field.
               RWY_N(Pilot) cancels menu            Menu disappears.
               by mouse click(R).
               RWY_N clicks         on   ARR1       Stand menu displayed with cursor position on EN21.
               stand field.
               RWY_N selects EN24.                  EN24 displayed in label.
               RWY_N(Pilot) clicks on               ARR1 continues to taxi but to EN24.
               ARR1 stand field and selects
               EN24.
               RWY_N clicks         on   ARR1       Stand menu displayed with cursor position on EN24.
               stand field.
               RWY_N selects cancel.                Menu disappears.
               RWY_N(Pilot)     clicks         on   Stand menu displayed with cursor position on EN24.
               ARR1 stand field.
               RWY_N(Pilot) cancels menu            Menu disappears.
               by mouse click(R).
                                                    ARR1 continues to taxi to EN24.
DEPARTURE
                                                    RWY_N and RWY_N(Pilot) see DEP1 as assumed and
                                                    transferred.
               RWY_N(Pilot)         clicks     on   Callsign menu displayed with cursor position on pushback
               DEP1 callsign.                       (No assume or startup available to pilots).
               RWY_N(Pilot)              selects    Menu disappears.
               cancels.
               RWY_N       clicks   on       DEP1   Callsign menu displayed with cursor position on assume.
               callsign.
               RWY_N assumes DEP1.                  RWY_N sees DEP1 as assumed.
               RWY_N       clicks   on       DEP1   Callsign menu displayed with cursor position on pushback.
               callsign.
               RWY_N selects pushback.
               RWY_N(Pilot) clicks on               DEP1 starts to move.
               DEP1 callsign and selects
               pushback command.
                                                    DEP1 continues to pushback point where it prompts for taxi
                                                    clearance.


               RWY_N       clicks   on       DEP1   Callsign menu displayed with cursor position on taxi.

STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                    f7919ee3-d7fb-4de6-9213-
                                                           1719658e70fc.doc

                                                         Page : 95 of 197

                                                                                  EUROCONTROL



               callsign.
               RWY_N selects taxi.
               RWY_N(Pilot) selects taxi            DEP1 starts to move.
               command.
               RWY_N(Pilot)    clicks          on   Runway menu displayed with cursor position on R09R.
               DEP1 runway field.
               RWY_N(Pilot)              selects    Menu disappears.
               cancel.
               RWY_N clicks         on       DEP1   Runway menu displayed with cursor position on R09R.
               runway field.
               RWY_N selects R27L.                  R27L displayed in label.
               RWY_N(Pilot) selects R27L            DEP1 continues to taxi but to R27L.
               from label runway button.
               RWY_N clicks         on       DEP1   Runway menu displayed with cursor position on R27L.
               runway field.
               RWY_N selects cancel.                Menu disappears.
               RWY_N(Pilot)    clicks          on   Runway menu displayed with cursor position on R27L.
               DEP1 runway field.
               RWY_N(Pilot)              selects    Menu disappears.
               cancel.
               RWY_N(Pilot)         clicks     on   Callsign menu displayed with cursor position on hold.
               DEP1 callsign.
               RWY_N(Pilot) selects hold.           DEP1 stops.
               RWY_N(Pilot)         clicks     on   Callsign menu displayed with cursor position on taxi.
               DEP1 callsign.
               RWY_N(Pilot) selects taxi.           DEP1 starts to taxi to runway and stops short of runway to
                                                    request lineup clearance.


               RWY_N       clicks   on       DEP1   Callsign menu displayed with cursor position on TOF.
               callsign.
               RWY_N selects lineup.                Lineup clearance displayed in label.
               RWY_N(Pilot)              accepts    DEP1 starts to lineup on runway.
               lineup prompt.
               RWY_N       clicks   on       DEP1   Callsign menu displayed with cursor position on takeoff.
               callsign.
               RWY_N selects takeoff.               Takeoff clearance displayed in label.
               RWY_N(Pilot) accepts                 DEP1 starts to accelerate down runway to takeoff.
               takeoff prompt.




ID   Time      Actions                                                                     Expectations


STATUS                                                                                                        TITLE
Company Ref.                                                                                   Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                        Page : 96 of 197

                                                                                 EUROCONTROL



1    16:12:00   Launch and run menusHybrid.gsdk scenario.                              One   AVD         appears
                                                                                       RWY_N
                As for menusAirGrd.gsdk          but    all   pilot   commands   are   As for menusAirGrd.gsdk
                automatically accepted.



     10.1.3.2 CT_TCWP_MENUS_02 – Runway SID Menu
Scenario ID                CT_TCWP_MENUS_02
SRD Reference
Objective                  Demonstrate that the TCWP runway menu also supports the selection of a
                           specific SID at the same time the runway is chosen.
Dependencies               None
Resource File              <component test home>/tcwp/menus/runwaySIDMenu.gsdk


ID   Time       Actions                                 Expectations
1    16:12:00   Launch and run runwayMenu.gsdk          One CWP appears.
                scenario.
                                                        Two AVDs appear: RWY_N/RWY and CARGO_N/APR.
2    16:12:16                                           DEP1 and DEP2 appear waiting to be assumed by
                                                        CARGO_N/APR.
                                                        Both flights are due to depart on Runway 09R using the
                                                        SID named “SID” (“LFPG_R09R_SID” in the SID
                                                        menu).
                In CARGO_N/APR, assume and              DEP1 and DEP2 start taxiing.
                give taxi clearances to both flights.
                In CARGO_N/APR, open the                A SID menu is shown alongside the runway menu,
                runway menu for DEP1 and point          containing a single SID (“LFPG_R27L_SID”).
                the mouse at R27L.
                Select the SID “LFPG_R27L_SID”          The runway selected for DEP1 is changed to R27L. The
                for DEP1.                               SID display remains the same (“SID”). The route for
                                                        DEP1 has been changed to lead to R27L.
                In CARGO_N/APR, open             the    The runway menu is displayed with a SID menu
                runway menu for DEP2.                   alongside showing the two available SIDS for runway
                                                        R09R.
                Select the runway R27L for DEP2.        The runway selected for DEP2 is changed to R27L. The
                                                        SID display remains the same (“SID”). The route for
                                                        DEP2 has been changed to lead to R27L.
                In CARGO_N/APR, transfer both
                flights to RWY_N/RWY.
                In RWY_N/RWY assume DEP1                Both flights in RWY_N/RWY display takeoff runway
                and DEP2.                               R27L with SID “SID.
                In RWY_N/RWY, open the runway           A SID menu is shown alongside the runway menu,
                menu for DEP1 and point the             containing two   SIDs  (“LFPG_R09R_SID”    and
                mouse at R09R.                          “R09R_SID_F10”).


STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                   Page : 97 of 197

                                                                             EUROCONTROL



                Select the SID “R09R_SID_F10”      The runway selected for DEP1 is changed to R09R.
                for DEP1.                          The SID selected for DEP1 is changed to “SID_F10”.
                                                   The route for DEP1 has been changed to lead to R09R.
                In RWY_N/RWY, open the runway      The runway selected for DEP2 is changed to R09R.
                menu for DEP2 and select runway    The SID display remains the same (“SID”). The route for
                R09R.                              DEP2 has been changed to lead to R09R.
                Give take-off clearance to both    Both flights proceed to runway R09R and takeoff.
                flights in RWY_N/RWY.
                                                   DEP1 heads south shortly after takeoff following the
                                                   SID “SID_F10” (“R09R_SID_F10” -> LFPGE, C4,
                                                   ORTIL).
                                                   DEP2 heads in a general easterly direction following the
                                                   SID “SID” (“LFPG_R09R_SID” -> LFPGE, CGZ, REM).



     10.1.4 ShortCuts

     10.1.4.1 CT_TCWP_SHORTCUTS_01 – Air and Ground Shortcuts
Scenario ID              CT_TCWP_SHORTCUTS_01
SRD Reference            2005APT70
Objective                To demonstrate that the following short cut commands imply other commands and
                         that the appropriate pilot command is also issued:
                                Pushback, Taxi, Hold, Lineup, Abort clearance orders imply Assume.
                                 (Note Abort can only be given when cleared to takeoff is given and
                                 this can only be given when the flight is assumed. So Abort can
                                 never be issued other than in an assumed state)
                                Take-Off clearance implies Lineup Clearance.
                                Cleared-To-Land implies Assume
Dependencies             None
Resource File            <component test home>/tcwp/shortcuts/shortcutsAirGrd.gsdk


ID   Time          Actions                               Expectations
1    16:12:00      Launch and run scenario.              Four AVDs appear.
                                                         Two controllers APN_N and RWY_N.
                                                         Two pilots APN_N(Pilot) and RWY_N(Pilot).
2    16:12:16                                            Aircraft begin to appear.
                                                         DEP1, DEP2, DEP3 ready to be assumed by
                                                         APN_N.
                                                         DEP1 requests taxi clearance.
                                                         DEP2 and DEP3 request pushback clearance.


3                  For DEP1, APR_N left clicks on        Flight assumed.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                  Page : 98 of 197

                                                                           EUROCONTROL



               callsign and selects taxi.               Taxi clearance is no longer displayed in the
                                                        callsign menu.
4              APR_N(Pilot) issues Taxi                 DEP1 begins to move.
               command.
5              For DEP1, APN_N right clicks on          DEP1 ready to be assumed by RWY_N.
               callsign and selects transfer.
6              Foe DEP1, RWY_N right clicks on          Flight assumed.
               callsign and selects hold.
                                                        Hold clearance symbol is displayed in the radar
                                                        label. Hold is replaced with Taxi in the callsign
                                                        menu.
7              RWY_N(Pilot) issues Hold                 DEP1 stops. Taxi Due is displayed in the label.
               command.


8              For DEP2, APR_N left clicks on           Flight assumed.
               callsign and selects pushback.
                                                        Pushback clearance is no longer displayed in the
                                                        callsign menu.
9              APR_N(Pilot)     issues      Pushback    DEP2 begins to move and continues to pushback
               command.                                 point where DEP2 requests taxi clearance.
10             For DEP2, APR_N left clicks on
               callsign and selects taxi.
11             RWY_N(Pilot) issues Taxi                 DEP2 continues to taxi to runway and just prior to
               command.                                 runway stops and requests lineup clearance.
12             For DEP2, APN_N left clicks on           DEP2 ready to be assumed by RWY_N.
               callsign and selects transfer.
13             For DEP2, RWY_N left clicks on           Flight assumed.
               callsign and selects lineup.
                                                        Lineup clearance is no longer displayed in the
                                                        callsign menu.
14             APR_N(Pilot) issues Lineup               DEP2 line-up on runway and requests takeoff
               command.                                 clearance.
15             For DEP2, RWY_N left clicks on           Takeoff clearance is no longer displayed in the
               callsign and selects takeoff.            callsign menu.
16             APR_N(Pilot) issues Takeoff              DEP2 accelerates down runway and takes-off.
               command.


17             For DEP3, APN_N left clicks on           Flight assumed.
               callsign and selects pushback.
                                                        Pushback clearance is no longer displayed in the
                                                        callsign menu.
18             APR_N(Pilot) issues pushback             DEP3 begins to move and continues to pushback
               command.                                 point where DEP3 requests taxi clearance.
19             For DEP3, APR_N left clicks on
               callsign and selects taxi.
20             RWY_N(Pilot) issues Taxi                 DEP3 starts to taxi to runway.
               command.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                           f7919ee3-d7fb-4de6-9213-
                                                  1719658e70fc.doc

                                                Page : 99 of 197

                                                                          EUROCONTROL



21              For DEP3, APN_N left clicks on        DEP3 ready to be assumed by RWY_N.
                callsign and selects transfer.
22              For DEP3, RWY_N left clicks on        Flight assumed.
                callsign and selects assume.
23              For DEP3, RWY_N left clicks on        Lineup and Takeoff options        are    no   longer
                callsign and selects takeoff.         displayed in the callsign menu.
24              RWY_N(Pilot) issues Takeoff           DEP3 continues to taxi to runway where it
                command.                              accelerates down runway and takes-off.


25   16:26:00                                         ARR1 is transferred from approach sector to
     (approx)                                         RWY_N.
                                                      ARR1 is seen as inbound and transferred in the
                                                      arrival list.




     10.1.4.2 CT_TCWP_SHORTCUTS_02 – Hybrid Shortcuts
Scenario ID           CT_TCWP_SHORTCUTS_02
SRD Reference         2005APT70
Objective             To demonstrate that a Hybrid TCWP can issue the following short cut commands:
                             Pushback, Taxi, Hold, Lineup, Abort clearance orders imply Assume.
                              (Note Abort can only be given when cleared to takeoff is given and
                              this can only be given when the flight is assumed. So Abort can
                              never be issued other than in an assumed state)
                             Take-Off clearance implies Lineup Clearance.
                             Cleared-To-Land implies Assume
Dependencies          None
Resource File         <component test home>/tcwp/shortcuts/shortcutsHybrid.gsdk


ID   Time       Actions                              Expectations
1    16:12:00   Launch and run scenario.             Two AVDs appear, APN_N and RWY_N.
2    16:12:16                                        Aircraft begin to appear.
                                                     DEP1, DEP2, DEP3 ready to be assumed by
                                                     APN_N.
                                                     DEP1 requires taxi clearance.
                                                     DEP2 and DEP3 require pushback clearance.


3               For DEP1, APR_N left clicks on       Flight assumed.
                callsign and selects taxi.
                                                     DEP1 begins to move.
4               For DEP1, APN_N left clicks on       DEP1 ready to be assumed by RWY_N.

STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 100 of 197

                                                                            EUROCONTROL



                 callsign and selects transfer.
5                Foe DEP1, RWY_N left clicks on         Flight assumed.
                 callsign and selects hold.
                                                        DEP1 stops.


6                For DEP2, APR_N left clicks on         Flight assumed.
                 callsign and selects pushback.
                                                        DEP2 begins to move and continues to the
                                                        pushback point.
7                For DEP2, APR_N left clicks on         DEP2 continues to taxi to runway and just prior to
                 callsign and selects taxi.             runway stops for lineup clearance.
8                For DEP2, APN_N left clicks on         DEP2 ready to be assumed by RWY_N.
                 callsign and selects transfer.
9                For DEP2, RWY_N left clicks on         Flight assumed.
                 callsign and selects lineup.
                                                        DEP2 line-up on runway and waits for takeoff
                                                        clearance.
10               For DEP2, RWY_N left clicks on         DEP2 accelerates down runway and takes-off.
                 callsign and selects takeoff.


11               For DEP3, APN_N left clicks on         Flight assumed.
                 callsign and selects pushback.
                                                        DEP3 begins to move and continues to pushback
                                                        point where it waits for taxi clearance.
12               For DEP3, APR_N left clicks on         DEP3 starts to taxi to runway.
                 callsign and selects taxi.
13               For DEP3, APN_N left clicks on         DEP3 ready to be assumed by RWY_N.
                 callsign and selects transfer.
14               For DEP3, RWY_N left clicks on         Flight assumed.
                 callsign and selects assume.
15               For DEP3, RWY_N left clicks on         DEP3 continues to taxi to runway where it
                 callsign and selects takeoff.          accelerates down runway and takes-off.


16   16:26:00                                           ARR1 is transferred from approach sector to
     (approx)                                           RWY_N.
                                                        ARR1 is seen as inbound and transferred in the
                                                        arrival list.



     10.2 TPWP

     10.2.1 Labels

     10.2.1.1 CT_TPWP_LABEL_01 – Pilot Track Labels
Scenario ID            CT_TPWP_LABEL_01
SRD Reference          2006TWR10, 2006TWR120, 2006TWR130, 2006TWR140, 2006TWR160,

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 101 of 197

                                                                                  EUROCONTROL



                          2006TWR170
Objective                 Demonstrate that piloted traffic have their details displayed in the piloted traffic
                          label.
                          Confirm controlled piloted traffic label text coloured according to traffic type i.e.
                          arrival, departure, and vehicle.
                          Confirm uncontrolled piloted traffic coloured unconcerned.
                          Confirm that from the label, controlling pilot can change:
                                 Frequency (departures/arrivals/vehicles)
                                 Runway for departures
                                 Stand for arrivals
                          Confirm extended label window can be displayed and reflects label and flight plan
                          data.
                          Confirm label fields are insensitive for traffic not controlled by pilot.
Dependencies              None
Resource File             <component test home>/tpwp/labels/labels.gsdk


ID   Time       Actions                      Expectations
1.   16:12:00   Launch scenario.             Two Pilot AVDs (RWY_N, APRON_N) are displayed.
2.   16:12:30   Stop scenario                ARR1, DEP1 and VAN1 have entered the scenario.
                                             ARR1 is shown in the controlled arrival colour by RWY_N and
                                             in the uncontrolled colour by APRON_N.
                                             DEP1 is shown in the controlled departure colour by APRON_N
                                             and in the uncontrolled colour by RWY_N.
                                             VAN1 is shown in the controlled vehicle colour by APRON_N
                                             and in the uncontrolled colour by RWY_N.
3.              Observe        arrival,      The label for ARR1 shows the callsign, runway and gate.
                departure and vehicle
                                             The label for DEP1 shows the callsign, runway and gate.
                labels without mouse
                focus.                       The label for VAN1 shows the callsign.
4.              Move cursor in labels        The expanded label for ARR1 shows the callsign, runway, gate,
                for arrival, departure       aircraft type suffixed with wake category and controlling
                and     vehicle   and        frequency.
                observe contents.
                                             The expanded label for DEP1 shows the callsign, runway, gate,
                                             aircraft type suffixed with wake category and controlling
                                             frequency.
                                             The expanded label for VAN1 shows the callsign, vehicle type
                                             suffixed with size and controlling frequency.
5.              On APRON_N, ARR1             The callsign field is inactive and the menu is not opened.
                (uncontrolled) click(L)
                on callsign field.
6.              On APRON_N, ARR1             The runway field is inactive and the menu is not opened.
                (uncontrolled) click(L)
                on runway field.

STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                Page : 102 of 197

                                                                           EUROCONTROL



7.             On APRON_N, ARR1          The gate field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on gate field.


8.             On APRON_N, ARR1          The frequency field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on frequency field.
9.             On RWY_N, DEP1            The callsign field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on callsign field.
10.            On RWY_N, DEP1            The runway field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on runway field.
11.            On RWY_N, DEP1            The gate field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on gate field.
12.            On RWY_N, DEP1            The frequency field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on frequency field.
13.            On RWY_N, VAN1            The callsign field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on callsign field.
14.            On RWY_N, VAN1            The frequency field is inactive and the menu is not opened.
               (uncontrolled) click(L)
               on frequency field.
15.            On RWY_N, ARR1            The callsign menu is displayed showing Taxi, Hold, Mark,
               click(L) on callsign      Stopat, Delete and Cancel.
               field.
16.            On RWY_N, ARR1            The runway field is inactive and the menu is not opened.
               click(L) on runway
               field.


17.            On RWY_N, ARR1            The gate menu is displayed.
               click(L) on gate field.


18.            Select Gate „A36‟         The label is updated to display the new gate „A36‟.
19.            On RWY_N, ARR1            The label is updated to display the gate „AXAXAX‟ in yellow,
               click(L) on gate field.   indicating that a route cannot be found to that gate.
               Select Gate „AXAXAX‟
20.            On RWY_N, ARR1            The route is shown for ARR1. If ARR1 is airborne or on the
               mouse-over the flight     runway then no route is shown. If ARR1 is taxiing then the
               symbol.                   route is shown up to the next waypoint on the route.
21.            On RWY_N, ARR1            The frequency menu is displayed.
               click(L) on frequency
               field.


STATUS                                                                                                TITLE
Company Ref.                                                                          Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                 Page : 103 of 197

                                                                            EUROCONTROL



22.            Select       frequency     The flight is transferred to APRON_N, where it is shown in the
               121.25.                    controlled arrival colour. The flight is displayed in the
                                          uncontrolled colour on RWY_N.
                                          The label is updated to display the frequency „121.25‟.
23.            On APRON_N, DEP1           The callsign menu is displayed showing Taxi, Lineup, Takeoff,
               click(L) on callsign       Mark, CLUP, CTOF, StopAt, Delete and Cancel.
               field.

24.            On APRON_N, DEP1           The runway menu is displayed.
               click(L) on runway
               field.
25.            Select Runway „R27R‟.      The label is updated to display the new runway „R27R‟.
26.            On APRON_N, DEP1           The label is updated to display the runway „AXAXAX‟ in yellow,
               click(L) on runway         indicating that a route cannot be found to that runway.
               field.
               Select         Runway
               „AXAXAX‟.
27.            On APRON_N, DEP1           The route is shown for DEP1 up to the next taxipoint.
               mouse-over the flight
               symbol.
28.            On APRON _N, DEP1          The gate field is inactive and the menu is not opened.
               click(L) on gate field.
29.            On APRON _N, DEP1          The frequency menu is displayed.
               (controlled) click(L) on
               frequency field.
30.            Select       frequency     The flight is transferred to RWY_N, where it is shown in the
               „119.25‟                   controlled departure colour. The flight is displayed in the
                                          uncontrolled colour on APRON_N.
                                          The label is updated to display the frequency „119.25‟.
31.            On APRON_N, VAN1           The callsign menu displayed showing Hold, Mark, StopAt,
               click(L) on callsign       Delete and Cancel.
               field.
32.            On APRON_N, VAN1           The frequency menu is displayed.
               click(L) on frequency
               field.
33.            Select       frequency     The vehicle is transferred to RWY_N, where it is shown in the
               „119.25‟                   controlled vehicle colour. The vehicle is displayed in the
                                          uncontrolled colour on APRON_N.
                                          The label is updated to display the frequency „119.25‟.
34.            On APRON_N and             The Extended Label Window (ELW) is opened for ARR1.
               RWY_N,       ARR1
                                          The colour of the contents of the ELW is the same as that of
               click(R) on callsign
                                          the label: concerned arrival on APRON_N and unconcerned on
               field.
                                          RWY_N.
                                          The ELW shows the callsign, runway, gate, frequency,
                                          controlling TPWP, aircraft type suffixed with wake category and
                                          airport.

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 104 of 197

                                                                              EUROCONTROL



                                              The Gate shown in the ELW matches the new gate „W6‟
                                              selected through the label gate menu.
35.               On APRON_N and              The Extended Label Window (ELW) is opened for DEP1.
                  RWY_N, DEP1 click(R)
                                              The colour of the contents of the ELW is the same as that of
                  on callsign field.
                                              the label: concerned departure on RWY_N and unconcerned
                                              on APRON_N.
                                              The ELW shows the callsign, runway, gate, SID, frequency,
                                              controlling TPWP, aircraft type suffixed with wake category and
                                              airport.
                                              The Runway shown in the ELW matches the new Runway
                                              „R27R‟ selected through the label runway menu.
36.               On APRON_N and              The Extended Label Window (ELW) is opened for VAN1.
                  RWY_N, VAN1 click(R)
                                              The colour of the contents of the ELW is the same as that of
                  on callsign field.
                                              the label: concerned vehicle in RWY_N and unconcerned on
                                              APRON_N.
                                              The ELW shows the callsign, frequency, controlling TPWP and
                                              vehicle type suffixed with size.



      10.2.1.2 CT_TPWP_LABEL_02 – Manoeuvre Prompts
Scenario ID                 CT_TPWP_LABEL_02
SRD Reference               2007TWR210
Objective                   Demonstrate that piloted traffic display manoeuvre prompts for pushback, taxi,
                            line-up and takeoff manoeuvres.
                            Demonstrate that the initial pushback or taxi prompts, as well as the line-up and
                            takeoff prompts, for a departure are displayed before the off-block time, line-up
                            point or takeoff point is reached.
Dependencies                None
Resource File               <component test home>/tpwp/labels/manoeurveprompts.gsdk


ID     Time       Actions                     Expectations
1.     16:12:00   Launch scenario.            One Pilot AVDs (RWY_N) is displayed.
2.                Check the following         The resources have the following values:
                  resource values with
                                              TOWER.MANOEUVERE_PROMPTS.TAXI_INTERVAL: 30s
                  the following prefix in
                  the resources window:       TOWER.MANOEUVERE_PROMPTS.PUSHBACK_INTERVAL: 30s

                  TOWER.MANOEUVERE            TOWER.MANOEUVERE_PROMPTS.LINEUP_INTERVAL: 10s
                  _PROMPTS                    TOWER.MANOEUVERE_PROMPTS.TAKEOFF_INTERVAL: 10s
3.                Open        the      file   The ETD for DEP1 and DEP2 are as follows:
                  “<component test home>
                  /tpwp/manoeuvreprompts/     DEP1 ETD: 16:14:10
                  manoeuvreprompts_traffi     DEP2 ETD: 16:14:30
                  c.dat”
4.                Start the scenario

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 105 of 197

                                                                            EUROCONTROL



5.    16:12:12                             ARR1, DEP1, DEP2 and VAN1 have entered the scenario.
6.               Open the control menu     VAN1 stops moving and a “Taxi Due” prompt is displayed in the
                 for VAN1 and select       label above the callsign.
                 HOLD.
7.               Left-click on the “Taxi   VAN1 starts to move and the “Taxi Due” prompt is removed.
                 Due” prompt in the
                 label for VAN1.
8.               Open the control menu     VAN1 stops moving and a “Taxi Due” prompt is displayed in the
                 for VAN1 and select       label above the callsign.
                 HOLD.
9.               Open the control menu     VAN1 starts to move and the “Taxi Due” prompt is removed.
                 for VAN1 and select
                 TAXI.
10.   16:13:41   Pause the scenario.       The label for DEP1 shows a “Taxi Due” prompt above the
                                           callsign. This is 30s before the ETD listed for DEP1.
11.              Restart the scenario.
12.              Open the control menu     DEP1 starts to move and the “Taxi Due” prompt is removed.
                 for DEP1 and select
                 TAXI.
13.   16:14:01   Pause the scenario.       The label for DEP2 shows a “Pushback Due” prompt above the
                                           callsign. This is 30s before the ETD listed for DEP2.
14.              Restart the scenario
15.              Open the control menu     DEP2 starts to move and the “Pushback Due” prompt is
                 for DEP2 and select       removed.
                 PUSHBACK.
16.              DEP2 stops, waiting for   The label for DEP2 shows a “Taxi Due” prompt above the
                 taxi clearance.           callsign.
17.              Left-click on the “Taxi   DEP2 starts to move and the “Taxi Due” prompt is removed.
                 Due” prompt in the
                 label for DEP2.
18.              Open the control menu     DEP2 stops moving and a “Taxi Due” prompt is displayed in the
                 for DEP2 and select       label above the callsign.
                 HOLD.
19.              Open the control menu     DEP2 starts to move and the “Taxi Due” prompt is removed.
                 for DEP2 and select
                 TAXI.
20.              DEP1 approaches the       The label for DEP1 shows a “Lineup Due” prompt. The prompt
                 line-up point.            is displayed approximately 10s before DEP1 stops at the line-
                                           up point.
21.              DEP2 approaches the       The label for DEP2 does not show a prompt.
                 line-up point and stops
                 behind DEP1.
22.              Open the control menu     DEP1 starts to line-up and the “Lineup Due” prompt is
                 for DEP1 and select       removed.
                 LINEUP.
                                           DEP2 starts to move a short interval after DEP1 starts to move.


STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 106 of 197

                                                                            EUROCONTROL



23.                                          The label for DEP2 shows a “Lineup Due” prompt. The prompt
                                             is displayed approximately 10s before DEP2 stops at the line-
                                             up point.
24.                                          DEP1 shows a “Takeoff Due” prompt. The prompt is displayed
                                             approximately 10s before DEP1 stops at the takeoff point
25.               Open the control menu      DEP1 starts to takeoff and the “Takeoff Due” prompt is
                  for DEP1 and select        removed.
                  TAKEOFF.
26.               Left-click     on   the    DEP2 starts to line-up and the “Lineup Due” prompt is
                  “Lineup Due” prompt in     removed.
                  the label for DEP2.
27.                                          The label for DEP2 shows a “Takeoff Due” prompt. The prompt
                                             is displayed approximately 10s before DEP2 stops at the
                                             takeoff point.
28.               Left-click     on    the   DEP2 starts to takeoff and the “Takeoff Due” prompt is
                  “Takeoff Due” prompt       removed.
                  in the label for DEP2.
29.               Increase time speed.
30.    16:28:00   Resume normal speed        ARR1 has landed and stopped off the runway waiting for taxi
                                             clearance. The label for ARR1 shows a “Taxi Due” prompt
                                             above the callsign.
31.               Open the control menu      ARR1 starts to move and the “Taxi Due” prompt is removed.
                  for ARR1 and select
                  TAXI.
32.               Open the control menu      ARR1 stops moving and a “Taxi Due” prompt is displayed in the
                  for ARR1 and select        label above the callsign.
                  HOLD.
33.               Left-click on the “Taxi    ARR1 starts to move and the “Taxi Due” prompt is removed.
                  Due” prompt in the
                  label for ARR1.



      10.2.2 Orders

      10.2.2.1 CT_TPWP_ORDERS_01 – Conditional Line-up and Take-off
Scenario ID               CT_TPWP_ORDERS_01
SRD Reference             2006TWR100, 2006TWR190
Objective                 Demonstrate that piloted departing traffic may be given clearances conditional to
                          another flight or vehicle leaving the runway area.
                          The conditional orders that should be supported are:
                                 Line-up – The departing flight lines-up and awaits take-off clearance once
                                  the selected flight or vehicle has departed the runway area.
                                 Take-off – The departing flight lines-up and takes-off once the selected
                                  flight or vehicle has departed the runway area.
Dependencies              None

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 107 of 197

                                                                             EUROCONTROL



Resource File              <component test home>/tpwp/conditional/conditional.gsdk


ID    Time       Actions                    Expectations
1.    16:12:00   Launch scenario.           One Pilot AVDs (RWY_N) is displayed.
2.    16:12:30   Stop scenario              ARR1, DEP1, DEP2, DEP3 and VAN1 have entered the
                                            scenario.
3.               Issue taxi clearances      DEP1 and DEP2 start to taxi.
                 to DEP1, DEP2 and
                                            DEP3 starts to taxi.
                 DEP3.
4.               Advance time until all 3   DEP1 is waiting for line-up clearance, with DEP2 stopping
                 flights are waiting for    behind waiting for DEP1 to taxi onto the runway.
                 line-up clearances.
                                            DEP3 is waiting for line-up clearance.
                 Issue     any     Taxi
                 clearances required for
                 DEP3.
5.               For DEP1, open the         The menu is removed and the conditional flight selection tool is
                 control  menu    and       displayed linking the DEP1 symbol to the cursor.
                 select CLUP from the
                 command menu.
6.               Left-click on VAN1 to      The flight selection tool display is removed. A conditional line-
                 select    it   as   the    up notification is displayed in the label for DEP1 above the
                 conditional subject for    callsign, with VAN1 as the target.
                 the line-up order.
7.               Left-click      on   the   The new route for VAN1 is created.
                 symbol      for    VAN1,
                 opening the trajectory
                 edition tool.
                 Create a root for VAN1
                 that moves it off the
                 runway.
8.               Open the control menu      VAN1 starts to move.
                 for VAN1 and select
                                            When VAN1 vacates the runway area, DEP1 starts to line-up.
                 TAXI.
                                            The conditional line-up notification is removed from the label
                                            display for DEP1.
9.               For DEP2, open the         A conditional line-up notification is displayed in the label for
                 control  menu   and        DEP2 above the callsign, with DEP1 as the target.
                 select CTOF from the
                 command menu.
                 Select DEP1 as the
                 conditional flight.
10.              Open the control menu      DEP1 commences to take off.
                 for DEP1 and select
                                            When DEP1 vacates the runway area, DEP2 lines up and takes
                 TAKEOFF.
                                            off. The conditional line-up notification is removed from the
                                            label display for DEP2.
11.              Accelerate time until
                 ARR1 is about to land.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 108 of 197

                                                                              EUROCONTROL



12.    16:27:00   FOR DEP3, open the         A conditional takeoff notification is displayed in the label for
       approx.    control  menu    and       DEP3 above the callsign, with ARR1 as the target.
                  select CTOF from the
                  command menu.
                  Select ARR1 as the
                  conditional flight.
13.               Observe ARR1 as it         When ARR1 exits the runway area, DEP3 lines up and takes
                  lands.                     off.
                                             Note that an error message is displayed in the console:
                                             ERROR - DEP3 will not attain take-off speed by
                                             end of runway R27R



      10.2.2.2 CT_TPWP_ORDERS_02 – Conditional Line-up and Take-off
Scenario ID                 CT_TPWP_ORDERS_02
SRD Reference               2006TWR190, 2006TWR210
Objective                   Demonstrate that piloted departing traffic may be given manoeuvres conditional to
                            another flight or vehicle crossing a runway, and that a conditional order is only
                            processed when the target leaves the runway associated with the subject flight.
Dependencies                None
Resource File               <component test home>/tpwp/conditional/conditional2.gsdk


ID     Time       Actions                    Expectations
1.     16:12:00   Launch scenario.           One Pilot AVDs (RWY_N) is displayed.
2.     16:12:30   Stop scenario              DEP1, DEP2 and VAN1 have entered the scenario.
3.                Issue taxi clearances      DEP1 and DEP2 start to taxi.
                  to DEP1 and DEP2.
4.                Issue a hold clearance     VAN1 stops waiting for taxi clearance.
                  to VAN1.
5.                Advance the scenario.
                  Resume normal speed
                  when DEP1 and DEP2
                  are waiting for line-up
                  orders.
                  Issue any taxi orders
                  required for DEP2 to
                  reach the line-up point.
6.                For DEP1, open the         The menu is removed and the conditional flight selection tool is
                  control  menu    and       displayed linking the DEP1 symbol to the cursor.
                  select CLUP from the
                  command menu.
7.                Left-click on VAN1 to      The flight selection tool display is removed. A conditional line-
                  select    it  as    the    up notification is displayed in the label for DEP1 above the
                  conditional subject for    callsign, with VAN1 as the target.


STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 109 of 197

                                                                             EUROCONTROL



                  the line-up order.
8.                For DEP1, open the        The menu is removed and the conditional flight selection tool is
                  control  menu    and      displayed linking the DEP1 symbol to the cursor.
                  select CTOF from the
                  command menu.
9.                Left-click on DEP2 to     The flight selection tool display is removed. The conditional
                  select    it   as   the   line-up notification remains in the label display for DEP1.
                  conditional subject for
                  the takeoff order.
10.               Issue a taxi clearance    VAN1 starts to move.
                  to VAN1.
11.                                         VAN1 exits runway R09R.
                                            DEP1 is given a line-up order and commences line-up.
                                            The conditional notification shown in the label for DEP1 is
                                            changed to be a take-off order with DEP2 as a target.
12.               Issue a take-off          DEP2 taxis onto the runway and takes off.
                  clearance to DEP2.
                                            Note that an error will be displayed in the console:
                                            ERROR - DEP2 will not attain take-off speed by
                                            end of runway R27R
13.                                         DEP1 is not given a take-off order. The notification remains in
                                            the label display.
14.               Issue    a     take-off   The conditional take-off notification is removed from the label
                  clearance to DEP1.        display for DEP1, which commences takeoff.



      10.2.2.3 CT_TPWP_ORDERS_03 – Stop-Ahead Order
Scenario ID                 CT_TPWP_ORDERS_03
SRD Reference               2006TWR200, 2006TWR210
Objective                   Demonstrate that piloted traffic may be given stop-ahead orders causing them to
                            stop at a specified point until taxi clearance is given.
Dependencies                None
Resource File               <component test home>/tpwp/stopahead/stopahead.gsdk


ID     Time       Actions                   Expectations
1.     16:12:00   Launch scenario and       One Pilot AVDs (RWY_N) is displayed.
                  start.
2.     16:12:30                             ARR1, DEP1 and VAN1 have entered the scenario.
3.                Open the control menu     The route to travel for VAN1 is displayed with a marker point
                  for VAN1 and select       under the cursor as it is moved along the route line.
                  STOPAT.
4.                Left-click on the stop-   The stop-ahead route is removed and a stop-ahead notification
                  ahead route to add a      is displayed in the label for VAN1, above the callsign.
                  stop-ahead point.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                 Page : 110 of 197

                                                                           EUROCONTROL



5.             Open the route display     The route for VAN1 is displayed with the stop-ahead marker at
               for VAN1 (right-click in   the point selected.
               the symbol for VAN1).
6.             Advance the simulation     VAN1 stops at the specified point waiting for taxi clearance. A
               time    until   VAN1       taxi prompt is displayed alongside the stop-ahead notification.
               reaches    the   stop-
               ahead point.
7.             Open the control menu      VAN1 resumes taxing. The taxi prompt and stop-ahead
               for VAN1 and select        notification are removed from VAN1‟s label display. The stop-
               TAXI.                      ahead marker is no longer displayed on the route display for
                                          VAN1.
8.             Open the control menu      The route to travel for DEP1 is displayed with a marker point
               for DEP1 and select        under the cursor as it is moved along the route line.
               STOPAT.
9.             Left-click on the stop-    The stop-ahead route is removed and a stop-ahead notification
               ahead route to add a       is displayed in the label for DEP1, above the callsign.
               stop-ahead point.
10.            Open the route display     The route for DEP1 is displayed with a stop-ahead marker at
               for DEP1 (right-click on   the point selected.
               symbol for DEP1).
11.            Issue taxi clearance for   DEP1 starts to taxi.
               DEP1.
12.            Close the route display    The route to travel for DEP1 is displayed with the existing stop-
               for DEP1 (right-click      ahead point marked and a different marker under the cursor as
               again on symbol for        it is moved along the route line.
               DEP1).
               Open the control menu
               for DEP1 and select
               STOPAT.
13.            Left-click on the stop-    The stop-ahead route is removed from the display. The stop-
               ahead route to add a       ahead notification is not changed.
               stop-ahead point.
14.            Open the route display     The route for DEP1 is shown with two stop-ahead markers
               for DEP1.                  displayed at the selected positions.
15.            Advance the simulation     DEP1 stops at the specified point waiting for taxi clearance. A
               time    until   DEP1       taxi prompt is displayed alongside the stop-ahead notification.
               reaches    the   stop-
               ahead point.
16.            Open the control menu      DEP1 resumes taxing. The taxi prompt is removed from
               for DEP1 and select        DEP1‟s label display, but the stop-ahead notification is still
               TAXI.                      present. The stop-ahead marker just passed is no longer
                                          displayed on the route display for DEP1, but the next stop-
                                          ahead marker is still displayed.
17.            Advance the simulation     DEP1 stops at the specified point waiting for taxi clearance. A
               time    until     DEP1     taxi prompt is displayed alongside the stop-ahead notification.
               reaches the second
               stop-ahead point.
18.            Open the control menu      DEP1 resumes taxing. The taxi prompt and stop-ahead

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 111 of 197

                                                                            EUROCONTROL



               for DEP1 and select         notification are removed from DEP1‟s label display. The stop-
               TAXI.                       ahead marker is no longer displayed on the route display for
                                           DEP1.
19.            Advance        simulation
               time until ARR1 has
               landed and is waiting
               for taxi clearance.
20.            Open the control menu       The route to travel for ARR1 is displayed with a marker point
               for ARR1 and select         under the cursor as it is moved along the route line.
               STOPAT.
21.            Left-click on the stop-     The stop-ahead route is removed and a stop-ahead notification
               ahead route to add a        is displayed in the label for ARR1, above the callsign.
               stop-ahead point.
22.            Open the route display      The route for ARR1 is displayed with a stop-ahead marker at
               for ARR1 (right-click on    the point selected.
               symbol for ARR1).
23.            Close the route display     The route to travel for ARR1 is displayed with the existing stop-
               for DEP1 (right-click       ahead point marked and a different marker under the cursor as
               again on symbol for         it is moved along the route line.
               DEP1).
               Open the control menu
               for DEP1 and select
               STOPAT.
24.            Left-click on the stop-     The stop-ahead route is removed from the display. The stop-
               ahead route to add a        ahead notification is not changed.
               stop-ahead point.
25.            Open the route display      The route for ARR1 is shown with two stop-ahead markers
               for ARR1.                   displayed at the selected positions.
26.            Select an existing stop-    The selected stop-ahead point is removed from the route-
               ahead point on the          display. The stop-ahead notification remains.
               route display and left-
               click on it.
27.            Select the other stop-      The selected stop-ahead point is removed from the route-
               ahead point on the          display and the stop-ahead notification is removed.
               route display and left-
               click on it.
28.            Open the control menu       The route to travel for ARR1 is displayed with a marker point
               for ARR1 and select         under the cursor as it is moved along the route line.
               STOPAT.
29.            Left-click on the stop-     The stop-ahead route is removed and a stop-ahead notification
               ahead route to add a        is displayed in the label for ARR1, above the callsign.
               stop-ahead point.
30.            Advance the simulation      ARR1 stops at the specified point waiting for taxi clearance. A
               time    until     ARR1      taxi prompt is displayed alongside the stop-ahead notification.
               reaches the second
               stop-ahead point.
31.            Open the control menu       ARR1 resumes taxing. The taxi prompt and stop-ahead
               for ARR1 and select         notification are removed from ARR1‟s label display. The stop-

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 112 of 197

                                                                              EUROCONTROL



                  TAXI.                      ahead marker is no longer displayed on the route display for
                                             ARR1.



      10.2.2.4 CT_TPWP_ORDERS_04 – Speed Order
Scenario ID                 CT_TPWP_ORDERS_04
SRD Reference               2006TWR200, 2006TWR210
Objective                   Demonstrate that piloted traffic may be given a taxi speed to override the default
                            speed for the route.
Dependencies                None
Resource File               <component test home>/tpwp/speed/speed.gsdk


ID     Time       Actions                    Expectations
1.     16:12:00   Launch scenario and        One Pilot AVDs (RWY_N) is displayed.
                  start.
2.     16:12:30                              ARR1, DEP1 and VAN1 have entered the scenario.
3.                In the label for VAN1,     The speed menu is opened for VAN1 with the cursor centred
                  left-click on the speed    on the current speed.
                  entry (last field in the
                  second row).
4.                Select a speed of 35       VAN1 moves at a faster rate than before. The new speed is
                  for VAN1.                  displayed in the speed field of the selected label view.
5.                Open the speed menu        VAN1 moves at a slower rate than before. The new speed is
                  for VAN1 and select a      displayed in the speed field of the selected label view.
                  speed of 5.
6.                Open the speed menu        The speed for VAN1 is the default value of 8, which is shown in
                  for VAN1 and select        the speed field of the selected label view.
                  RESUME.
7.                Issue taxi clearance for   DEP1 starts to taxi.
                  DEP1.
8.                In the label for DEP1,     The speed menu is opened for DEP1 with the cursor centred
                  left-click on the speed    on the current speed.
                  entry (last field in the
                  second row).
9.                Select a speed of 35       DEP1 moves at a faster rate than before. The new speed is
                  for DEP1.                  displayed in the speed field of the selected label view.
10.               Open the speed menu        DEP1 moves at a slower rate than before. The new speed is
                  for DEP1 and select a      displayed in the speed field of the selected label view.
                  speed of 5.
11.               Open the speed menu        The speed for DEP1 is the default value of 3 (if just leaving the
                  for DEP1 and select        gate) or 15 (on the taxiway), which is shown in the speed field
                  RESUME.                    of the selected label view.
12.               Accelerate time until
                  ARR1 has landed and
                  is waiting for taxi
STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 113 of 197

                                                                                  EUROCONTROL



                  clearance.
13.    16:30:00   Issue taxi clearance to     ARR1 starts to taxi.
                  ARR1.
14.               In the label for ARR1,      The speed menu is opened for ARR1 with the cursor centred
                  left-click on the speed     on the current speed.
                  entry (last field in the
                  second row).
15.               Select a speed of 35        ARR1 moves at a faster rate than before. The new speed is
                  for ARR1.                   displayed in the speed field of the selected label view.
16.               Open the speed menu         ARR1 moves at a slower rate than before. The new speed is
                  for ARR1 and select a       displayed in the speed field of the selected label view.
                  speed of 5.
17.               Open the speed menu         The speed for ARR1 is the default value of 15, which is shown
                  for ARR1 and select         in the speed field of the selected label view,
                  RESUME.



      10.2.3 Arrival Departure Vehicle Lists

      10.2.3.1 CT_TPWP_LIST_01 – Arrival Departure Vehicle Lists

Scenario ID                 CT_TPWP_LIST_01
SRD Reference               2006TWR170
Objective                   Demonstrate that piloted traffic have their details displayed in the piloted traffic
                            lists, in particular arrivals show predicted landing times and stand, departures
                            show predicted pushback time and runway.
                            Confirm controlled piloted traffic list text coloured according to traffic type i.e.
                            arrival, departure, and vehicle.
                            Confirm that from the list, controlling pilot can change:
                                   Frequency (departures/arrivals/vehicles)
                                   Runway for departures
                                   Stand for arrivals
                            Confirm uncontrolled piloted traffic not contained in list.
                            Confirm highlighting list entry highlights label and vice versa.
Dependencies                None
Resource File               <component test home>/tpwp/lists/lists.gsdk


ID     Time       Actions                     Expectations
1.     16:12:00   Launch scenario.            Two Pilot AVDs (RWY_N, APRON_N) are displayed.
2.     16:12:30   Stop scenario               ARR1, DEP1 and VAN1 have entered the scenario.
                                              Details for ARR1 are shown in the Arrivals list in the controlled
                                              arrival colour by RWY_N.

STATUS                                                                                                        TITLE
Company Ref.                                                                                   Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 114 of 197

                                                                              EUROCONTROL



                                            Details for DEP1 are shown in the Departures list in the
                                            controlled departure colour by APRON_N.
                                            Details for VAN1 are shown in the Vehicles list in the controlled
                                            vehicle colour by APRON_N.
                                            The lists for RWY_N only contain details for ARR1.
                                            The lists for APRON_N only contain details for DEP1 and
                                            VAN1.
3.                                          The details listed for ARR1 in RWY_N are the callsign,
                                            predicted landing time, runway, gate, frequency and controlling
                                            TPWP.
                                            The details listed for DEP1 in APRON_N are the callsign,
                                            runway, predicted pushback time, gate, SID, frequency and
                                            controlling TPWP.
                                            The details listed for VAN1 in APRON_N are the callsign,
                                            frequency and controlling TPWP.
4.             On RWY_N, ARR1 list          The callsign menu is displayed showing Taxi, Hold, Mark,
               click(L) on callsign         StopAt, Delete and Cancel.
               field.
5.             On RWY_N, ARR1 list          The predicted landing time field is inactive and no menu is
               click(L) on predicted        opened.
               landing time field.
6.             On RWY_N, ARR1 list          The runway field is inactive and the menu is not opened.
               click(L) on runway
               field.
7.             On RWY_N, ARR1 list          The gate menu is displayed.
               click(L) on gate field.

8.             Select Gate „W6‟             The list and label is updated to display the new gate „W6‟.
9.             On RWY_N, ARR1 list          The list and label is updated to display the gate „AXAXAX‟ in
               click(L) on gate field.      yellow, indicating that a route cannot be found to that gate.
               Select Gate „AXAXAX‟
10.            On RWY_N, ARR1 list          The frequency menu is displayed.
               click(L) on frequency
               field.
11.            Select         frequency     The flight is transferred to APRON_N, where the details are
               121.25.                      shown in the controlled arrival colour. The flight details have
                                            been removed from RWY_N.
12.            On           APRON_N         The flight symbol and label highlight when the mouse selects
               highlight the list details   the list entry.
               for ARR1.
                                            The list and label both display the new frequency „121.25‟.
13.            On APRON_N, DEP1             The callsign menu is displayed showing Taxi, Lineup, Takeoff,
               list click(L) on callsign    Mark, CLUP, CTOF, StopAt, Delete and Cancel.
               field.

14.            On APRON _N, DEP1            The runway menu is displayed.
               list click(L) on runway

STATUS                                                                                                    TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 115 of 197

                                                                              EUROCONTROL



                field.
15.             Select Runway „R27R‟.       The list and label is updated to display the new runway „R27R‟.
16.             On APRON _N, DEP1           The list and label is updated to display the runway „AXAXAX‟ in
                list click(L) on runway     yellow, indicating that a route cannot be found to that runway.
                field.
                Select            Runway
                „AXAXAX‟.
17.             On APRON _N, DEP1           The predicted pushback time field is inactive and no menu is
                list    click(L)    on      opened.
                predicted     pushback
                field.
18.             On APRON _N, DEP1           The gate field is inactive and the menu is not opened.
                list click(L) on gate
                field.
19.             On APRON _N, DEP1           The frequency menu is displayed.
                list    click(L) on
                frequency field.
20.             Select          frequency   The flight is transferred to RWY_N, where the details are
                „119.25‟                    shown in the controlled departure colour. The flight details have
                                            been removed from APRON_N.
21.             On RWY_N highlight          The flight symbol and label highlight when the mouse selects
                the list details for        the list entry.
                DEP1.
                                            The list and label both display the new frequency „119.25‟.
22.             On APRON_N, VAN1            The callsign menu displayed showing Hold, Mark, StopAt,
                list click(L) on callsign   Delete and Cancel.
                field.
23.             On APRON_N, VAN1            The frequency menu is displayed.
                list    click(L) on
                frequency field.
24.             Select          frequency   The vehicle is transferred to RWY_N, where the details are
                „119.25‟                    shown in the controlled vehicle colour. The flight details have
                                            been removed from APRON_N.
25.             On RWY_N highlight          The vehicle symbol and label highlight when the mouse selects
                the list details for        the list entry.
                VAN1.
                                            The list and label both display the new frequency „119.25‟.



      10.2.4 Menus

      10.2.4.1 CT_TPWP_MENUS_01 – Menu Default Selection
Scenario ID                CT_TPWP_MENUS_01
SRD Reference
Objective                  No pilot default selections have been specified.
Dependencies               None


STATUS                                                                                                    TITLE
Company Ref.                                                                             Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                     Page : 116 of 197

                                                                              EUROCONTROL



Resource File



     10.2.4.2 CT_TPWP_MENUS_02 – Runway SID Menu
Scenario ID               CT_TPWP_MENUS_02
SRD Reference             2006TWR100, 2006TWR210
Objective                 Demonstrate that the TPWP runway menu also supports the selection of a
                          specific SID at the same time the runway is chosen.
Dependencies              None
Resource File             <component test home>/tpwp/menus/runwaySIDMenu.gsdk


ID   Time       Actions                               Expectations
1    16:12:00   Launch and run runwayMenu.gsdk        One CWP appears.
                scenario.
                                                      Two Pilot AVDs        appear:   APRON_N/PILOT          and
                                                      RWY_N/PILOT.
                                                      One Controller AVD appears: RWY_N/RWY
2    16:12:16                                         DEP1 and DEP2            appear     under    control    of
                                                      APRON_N/PILOT.
                                                      Both flights are due to depart on Runway 09R using the
                                                      SID named “SID” (“LFPG_R09R_SID” in the SID
                                                      menu).
                In APRON_N/PILOT, give        taxi    DEP1 and DEP2 start taxiing.
                clearances to both flights.
                In APRON_N/PILOT, open the            A SID menu is shown alongside the runway menu,
                runway menu for DEP1 and point        containing a single SID (“LFPG_R27L_SID”).
                the mouse at R27L.
                Select the SID “LFPG_R27L_SID”        The runway selected for DEP1 is changed to R27L. The
                for DEP1.                             SID display remains the same (“SID”). The route for
                                                      DEP1 has been changed to lead to R27L.
                                                      The controlling position RWY_N/RWY still shows the
                                                      original runway, R09R.
                In APRON_N/PILOT, open the            The runway menu is displayed with a SID menu
                runway menu for DEP2.                 alongside showing the two available SIDS for runway
                                                      R09R.
                Select the runway R27L for DEP2.      The runway selected for DEP2 is changed to R27L. The
                                                      SID display remains the same (“SID”). The route for
                                                      DEP2 has been changed to lead to R27L.
                                                      The controlling position RWY_N/RWY still shows the
                                                      original runway, R09R.
                                                      Both flight follow the new route to the end of R27L.
                In APRON_N/PILOT, transfer both       Both flights in RWY_N/PILOT display takeoff runway
                flights    to       RWY_N/PILOT       R27L with SID “SID.
                (frequency 119.25).

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 117 of 197

                                                                              EUROCONTROL



                In RWY_N/PILOT, open the            A SID menu is shown alongside the runway menu,
                runway menu for DEP1 and point      containing two SIDs (“LFPG_R09R_SID” and
                the mouse at R09R.                  “R09R_SID_F10”).
                Select the SID “R09R_SID_F10”       The runway selected for DEP1 is changed to R09R.
                for DEP1.                           The SID selected for DEP1 is changed to “SID_F10”.
                                                    The route for DEP1 has been changed to lead to R09R.
                                                    The controlling position RWY_N/RWY still shows the
                                                    original runway, R09R with SID “SID”.
                In RWY_N/PILOT, open the            The runway selected for DEP2 is changed to R09R.
                runway menu for DEP2 and select     The SID display remains the same (“SID”). The route
                runway R09R.                        for DEP2 has been changed to lead to R09R.
                                                    The controlling position RWY_N/RWY still shows the
                                                    original runway, R09R.
                Give take-off clearance to both     Both flights proceed to runway R09R and takeoff.
                flights in RWY_N/PILOT.
                                                    DEP1 heads south shortly after takeoff following the
                                                    SID “SID_F10” (“R09R_SID_F10” -> LFPGE, C4,
                                                    ORTIL).
                                                    DEP2 heads in a general easterly direction following
                                                    the SID “SID” (“LFPG_R09R_SID” -> LFPGE, CGZ,
                                                    REM).



     10.2.5 ShortCuts

     10.2.5.1 CT_TPWP_SHORTCUTS_01 – Pilot Shortcuts
Scenario ID              CT_TPWP_SHORTCUTS_01
SRD Reference
Objective                No pilot short cuts have been specified.
Dependencies             None
Resource File



     10.2.6 Pilot Configurations

     10.2.6.1 CT_TPWP_CNFG_01 – Tower Pilot
Scenario ID              CT_TPWP_CNFG_01
SRD Reference            2007TWR100
Objective                Demonstrates pilot control of flights with a Tower Pilot only.
Dependencies             None
Resource File            <component test home>/tpwp/frequency/configTower.gsdk


ID    Time            Actions                               Expectations

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                           f7919ee3-d7fb-4de6-9213-
                                                  1719658e70fc.doc

                                               Page : 118 of 197

                                                                         EUROCONTROL



1.    16:12:00    Launch scenario.                      One controller AVD (RWY_N/RWY), one pilot
                                                        AVD (RWY_N/PILOT) and one PVD (FS).
2.    16:12:12                                          ARR1 track seen in RWY_N/PILOT and FS
                                                        positions. DEP1 seen in both RWY_N positions.


                                                        RWY_N/PILOT controls both flights.
3.                Give pilot clearances needed for
                  DEP1 to take-off.
4.                DEP1 takes off.                       DEP1 appears in FS. Control of DEP1 remains
                                                        with RWY_N/PILOT.
5.    16:24:26    ARR1 appears in RWY_N/RWY
                  position.
6.    16:27:50    ARR1 lands.                           ARR1 removed from FS display. Control of
                                                        ARR1 remains with RWY_N/PILOT.



     10.2.6.2 CT_TPWP_CNFG_02 – ATC Pilot
Scenario ID          CT_TPWP_CNFG_02
SRD Reference
Objective            Demonstrates pilot control of flights with an ATC Pilot only.
Dependencies         None
Resource File        <component test home>/tpwp/frequency/configATC.gsdk


ID    Time        Actions                               Expectations
1.    16:12:00    Launch scenario.                      One controller AVD (RWY_N/RWY), one PVD
                                                        (FS) and one PWP (PWP_FS) are displayed.
2.    16:12:12                                          ARR1 track seen in FS and PWP_FS positions.
                                                        PWP_FS controls ARR1.


                                                        DEP1 seen in RWY_N/RWY.
3.    16:23:41    DEP1 takes off.                       DEP1 appears in FS. Control of DEP1 is with
                                                        PWP_FS.
4.    16:24:26    ARR1 appears in RWY_N/RWY
                  position.
5.    16:27:55    ARR1 lands                            ARR1 removed from FS and PWP_FS.



     10.2.6.3 CT_TPWP_CNFG_03 – Tower and ATC Pilot
Scenario ID          CT_TPWP_CNFG_03
SRD Reference        2006TWR70, 2007TWR100
Objective            Demonstrates pilot control of flights with both a Tower and an ATC Pilot.

STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                 Page : 119 of 197

                                                                           EUROCONTROL



Dependencies            None
Resource File           <component test home>/tpwp/frequency/configTowerATC.gsdk


ID    Time           Actions                              Expectations
1.    16:12:00       Launch scenario.                     One controller AVD (RWY_N/RWY), one pilot
                                                          AVD (RWY_N/PILOT), one PVD (FS) and one
                                                          PWP (PWP_FS) are displayed.
2.    16:12:12                                            ARR1 track seen in RWY_N/PILOT, PWP_FS
                                                          and FS positions. PWP_FS controls ARR1.
                                                          DEP1 track seen in RWY_N/RWY and
                                                          RWY_N/PILOT. RWY_N/PILOT controls DEP1.
3.                   Give pilot clearances needed for
                     DEP1 to take-off.
4.                   DEP1 takes off.                      DEP1 appears in FS. Control of DEP1 remains
                                                          with RWY_N/PILOT.
5.                   In RWY_N/PILOT transfer DEP1         Control of   DEP1     is   removed  from
                     to frequency 126.7                   RWY_N/PILOT and received by PWP_FS.
6.    16:24:26       ARR1 appears in RWY_N/RWY
                     position.
7.    16:27:55       ARR1 lands                           ARR1 removed from FS and PWP_FS.
                                                          ARR1 controlled by Pilot AVD (RWY_N)



     10.2.7 Flight Control Transfer

     10.2.7.1 CT_TPWP_TRNS_01 – Transfer on Landing
Scenario ID             CT_TPWP_TRNS_01
SRD Reference
Objective               Demonstrates that control of PM piloted flights is automatically transferred to the
                        TPM when an arrival lands
Dependencies            None
Resource File           <component test home>/tpwp/frequency/transferArrival.gsdk


ID    Time           Actions                              Expectations
1.    16:12:00       Launch scenario.                     One Pilot AVD (RWY_N) and one PVD (FS) and
                                                          one PWP (PWP_FS) are displayed.
2.                                                        ARR1 track seen in all displays. PWP_FS
                                                          controls ARR1.
3.    16:27:55       ARR1 lands                           ARR1 removed from FS and PWP_FS.
                                                          ARR1 controlled by Pilot AVD (RWY_N)



STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                Page : 120 of 197

                                                                         EUROCONTROL



     10.2.7.2 CT_TPWP_TRNS_02 – Transfer on Takeoff
Scenario ID          CT_TPWP_TRNS_02
SRD Reference
Objective            Demonstrates that control of TPM Piloted flights can be transferred to the PM only
                     after a departure takes off.
Dependencies         None
Resource File        <component test home>/tpwp/frequency/transferDeparture.gsdk


ID    Time        Actions                                Expectations
1.    16:12:00    Launch scenario.                       One Pilot AVD (RWY_N) and one PVD (FS) and
                                                         one PWP (PWP_FS) are displayed.
2.                                                       DEP1 track seen in RWY_N.
3.                Open frequency transfer menu.          Only the runway frequency (119.25) is displayed
                                                         in the menu.
4.                Give DEP1 clearances required to       DEP1 takes off and remains under the control of
                  takeoff in RWY_N.                      RWY_N.
5.                Open frequency transfer menu for       The frequency menu contains several ATC
                  DEP1 in RWY_N.                         sector frequencies as well as the TWR
                                                         frequency (119.25).
6.                Select frequency 126.7.                Control of DEP1 is transferred from RWY_N to
                                                         PWP_FS.



     10.2.7.3 CT_TPWP_FRQ_01 – Frequency Management
Scenario ID          CT_TPWP_FRQ_01
SRD Reference
Objective            Demonstrates that arrivals and departures can only be controlled by ATC
                     frequencies while airborne.
                     Demonstrate that Vehicles cannot be controlled by ATC frequencies.
Dependencies         None
Resource File        <component test home>/tpwp/frequency/transferFrequencies.gsdk


ID    Time        Actions                                Expectations
1.    16:12:00    Launch scenario.                       One Pilot AVD (RWY_N) and one PVD (FS) and
                                                         one PWP (PWP_FS) are displayed.
2.                                                       Tracks for DEP1, ARR1 and VAN1 are seen in
                                                         RWY_N. The RWY_N has control of DEP1 and
                                                         VAN1.


                                                         ARR1 seen in FS and PWP_FS. PWP_FS has
                                                         control of ARR1.

STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                                   f7919ee3-d7fb-4de6-9213-
                                                          1719658e70fc.doc

                                                       Page : 121 of 197

                                                                                  EUROCONTROL



                       Departure
3.                     Open the frequency menu for              The frequency menu contains the RWY_N
                       DEP1 in RWY_N.                           frequency (119.25) only.
4.                     Close the frequency menu
5.                     Issue clearances        required   for   DEP1 takes off.
                       DEP1 to takeoff.
6.                     Open the frequency menu for              The frequency menu contains the RWY_N
                       DEP1 in RWY_N.                           frequency (119.25) as well as frequencies for the
                                                                ATC sectors.
7.                     Select the PWP_FS frequency              Control of DEP1 is removed from RWY_N and
                       (126.7).                                 received by PWP_FS.
8.                     In PWP_FS issue an order for             Control of DEP1 is removed from PWP_FS and
                       DEP1 to transfer frequency to the        received by RWY_N.
                       Airport frequency (119.25).
                       Arrival
9.                     In PWP_FS issue an order for             Control of ARR1 is removed from PWP_FS and
                       ARR1 to transfer frequency to the        received by RWY_N.
                       Airport frequency (119.25).
10.                    Open the frequency menu for              The frequency menu contains the frequencies
                       ARR1 in RWY_N.                           for the ATC sectors. The current frequency
                                                                (119.25) is excluded from the list.
11.                    Close the frequency menu.
12.                    ARR1 lands.                              ARR1 remains under the control of RWY_N.
13.                    Open the frequency menu for              The frequency menu is empty.
                       ARR1 in RWY_N
                       Vehicle
14.                    Open the frequency menu for              The frequency menu contains the RWY_N
                       VAN1 in RWY_N.                           frequency (119.25) only.



      10.3 Common Graphical Elements

      10.3.1 Symbols

      10.3.1.1 CT_TWP_SYMBOL_01 – Symbol Orientation

Scenario ID               CT_TWP_SYMBOL_01
SRD Reference             2005APT60, 2005G10
Objective                 Demonstrate that
                                    Vehicle symbol orientation implies direction of travel.
                                    Aircraft orientation implies direction of travel when taxiing.
                                    Aircraft orientation implies reverse direction of travel when pushing back.


STATUS                                                                                                        TITLE
Company Ref.                                                                                   Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 122 of 197

                                                                             EUROCONTROL



                                 Aircraft shape/size imply wake category
Dependencies              None
Resource File             <component test home>/graphics/common/symbols/symbols.gsdk


ID   Time       Actions                         Expectations
1    16:12:00   Launch and start scenario.      Three AVDs displayed:
                                                       TCWP (Hybrid) -TCWP_APR_N
                                                       TCWP - RWY_N_GRD
                                                       TPWP - RWY_N_AIR
2               On all displays zoom in on      Observe:
                symbols.
                                                AMBULANCE starts to travel across airport with triangular
                                                symbol implying direction of travel.
                                                DEP1, DEP2, DEP4 symbols drawn as aircraft.
                                                Symbols drawn to represent wake category (H, M, S, L).
                                                DEP1 H wake category. Largest symbol.
                                                DEP2 M wake category. DEP1 > DEP2 symbol > DEP4.
                                                (DEP3 S wake category. DEP2 > DEP3 symbol > DEP4.
                                                Note S wake categories are for UK and UK airports only.)
                                                DEP4 L wake category. Smallest symbol.
3               TCWP_APR_N       assumes        DEP1 aircraft symbol starts to travel in reverse.
                DEP1, DEP2 and DEP4.
                                                DEP2 aircraft symbol starts to travel in forward direction.
                TCWP_APR_N gives DEP1
                pushback clearance.
                TCWP_APR_N gives DEP2
                taxi clearance.




     10.3.1.2 CT_TWP_SYMBOL_02 – Symbol Shape and Size

Scenario ID               CT_TWP_SYMBOL_02
SRD Reference             2005APT100
Objective                 Demonstrate that
                                 Aircraft and Vehicle symbol shape can easily be changed.
                                 Aircraft and Vehicle symbol size can easily be changed.
                                 Aircraft and vehicle symbols vary in size according to zoom but limited to
                                  a minimum size. Note this minimum size is dependent on the pixel
                                  representation as described in the twr.common.graphics.symbols.
                                  VehiclePolygon.java and AircraftPolygon.java


STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                     f7919ee3-d7fb-4de6-9213-
                                                            1719658e70fc.doc

                                                         Page : 123 of 197

                                                                                 EUROCONTROL



Dependencies                   None
Resource File                  <component test home>/graphics/common/symbols/symbolShapeSize.gsdk


ID   Time       Actions               Expectations
1    16:12:00   Launch       and      Three AVDs displayed:
                start scenario.
                                             TCWP (Hybrid) -TCWP_APR_N
                                             TCWP - RWY_N_GRD
                                             TPWP - RWY_N_AIR
2                                     Scenario contains VAN, DEP1, DEP2 and DEP4 as in test
                                      CT_TWP_SYMBOL_02 but VAN is drawn as an aircraft and departures
                                      drawn as triangles.
                                      Symbols are drawn much larger.
3               Zoom      in     on   Symbols increase in size according to zoom.
                map
4               Zoom      out    on   Symbols decrease in size according to zoom but are limited to a minimum
                map                   size.




     10.3.1.3 CT_TWP_SYMBOL_03 – Symbol Shape and Size

Scenario ID                    CT_TWP_SYMBOL_03
SRD Reference                  2005APT100
Objective                      Demonstrate that
                                      Different symbols and size information can be assigned to a
                                       flight type / model overriding the default shapes and sizes
                                       based on category.
                                      Aircraft and vehicle symbols vary in size according to zoom but
                                       limited to a minimum size.
Dependencies                   None
Resource File                  <componenttest
                               home>/graphics/common/symbols/symbolSizeTest.gsdk


ID   Time       Actions               Expectations
1    16:12:00   Launch      and       Four AVDs displayed:
                start scenario.
                                             TPWP – GNDS (Pilot)
                                             TPWP – GNDN (Pilot)
                                             TPWP – RWY (Pilot)
                                             TCWP – RWY (Controller)

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 124 of 197

                                                                             EUROCONTROL



2   16:12:10                    Scenario contains aircraft named Heavy, Medium and Light.
                                Aircraft sizes and shapes match the name and the flightplan
                                wake category.
    16:12:20                    Aircraft Dep1, Dep2 and Dep3 have been added to the display.
                                All 3 aircraft use the Medium wake category symbol, but have
                                symbols descending in size from Dep1 to Dep3.
                                The flightplan confirms Dep1, Dep2 and Dep3 all use the
                                medium wake category, but use different aircraft types.
                                The aircraft types define different lengths for the aircraft but are
                                otherwise identical.
    16:12:30                    Aircraft Vehicle_Heavy Vehicle_Medium and Vehicle_Light have
                                been added to the display.
                                All 3 aircraft use the vehicle symbols.
                                The size of the symbols matches the name and the flightplan
                                wake category. The flightplan for each of the aircraft type B73E
                                The aircraft type B73E defines the vehicle symbol, but no length.
    16:12:40                    Aircraft Vehicle_Giant has been added to the display.
                                The aircraft uses the vehicle symbol and is very large.
                                The flightplan lists the wake category as medium and the vehicle
                                type as B73F.
                                The aircraft type B73F defines the vehicle symbol and length to
                                be used.
    16:12:50                    Vehicles Van1, Van2 and Ambulance have been added to the
                                display.
                                Van1 shows the medium van size and symbol. Checking the
                                flightplan and vehicle performance file shows the medium size,
                                and that the length and symbol are not modified.
                                Van2 shows the van symbol at a much larger size. Checking the
                                flightplan shows the medium size, and the vehicle performance
                                file shows that the length has been set.
                                Ambulance shows the vehicle using the heavy aircraft symbol at
                                approximately the same size as Van1. Checking the flightplan
                                shows the medium size, and the vehicle performance file shows
                                the symbol has been set.
    16:13:00                    Vehicle Ambulance_Giant has been added to the display.
                                The vehicle is shown using the heavy aircraft symbol at a much
                                larger size.
                                Checking the flightplan shows the medium size, and the vehicle
                                performance file shows both the length and symbol have been
                                set.
               Zoom   in   on   Symbols increase in size according to zoom.
               map
               Zoom out on      Symbols decrease in size according to zoom but are limited to a
               map              minimum size.

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 125 of 197

                                                                                EUROCONTROL




     10.3.1.4 CT_TWP_SYMBOL_04 – Mark Symbol

Scenario ID               CT_TWP_SYMBOL_04
SRD Reference
Objective                 Demonstrate that controllers can “locally” mark traffic for their later attention.
Dependencies              None
Resource File             <component test home>/graphics/common/symbols/mark.gsdk


ID   Time       Actions                                     Expectations
1    16:12:00   Launch and start scenario.                  Three AVDs displayed:
                                                                   TCWP (Hybrid) -TCWP_APR_N
                                                                   TCWP - RWY_N_GRD
                                                                   TPWP - RWY_N_AIR
                TCWP_APR_N marks DEP1                       Square marks DEP1           symbol     but   only     on
                                                            TCWP_APR_N.
                TCWP_APR_N unmarks DEP1                     Square removed.
                Repeat  for      RWY_N_GRD           and
                RWY_N_AIR
                TCWP_APR_N marks DEP1                       Square marks DEP1           symbol     but   only     on
                                                            TCWP_APR_N.
                RWY_N_GRD marks DEP1                        Square marks DEP1 symbol on RWY_N_GRD.
                RWY_N_GRD unmarks DEP1                      Square removed from RWY_N_GRD.




     10.3.2 Toolbar

     10.3.2.1 CT_TWP_TOOLBAR_01 – Toolbar
Scenario ID               CT_TWP_TOOLBAR_01
SRD Reference
Objective                 To demonstrate independent tailored toolbar for operational use.
Dependencies              None
Resource File             <component test home>/graphics/common/toolbox/toolbox.gsdk


ID   Time       Actions                   Expectations


STATUS                                                                                                         TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 126 of 197

                                                                                   EUROCONTROL



1   16:12:00   Launch      and      run   AVDs for RWY_N(Pilot), RWY_N(RWY) and TWY_N(RWY hybrid)
               scenario.                  appear containing Arrival and Departure Lists and Toolbar.
                                          Pilot Toolbar contains:
                                          PREF, VIEW, BAYS, MAP, ZOOM, LAB, EFS
                                          Controller and Hybrid toolbars contain:
                                          PREF, VIEW, MAP, ZOOM, LAB, ARR, DEP
    16:12:30                              FireEngine, ARR1 and DEP1 appear as tracks on the AVD.
                                          Arrival List contains ARR1 on RWY_N
               TWY_N Assumes              Departure List contains DEP1 on TWY_N
               DEP1 and issues Push
               clearance.
               RWY_N      assumes         ARR1 and DEP1 coloured assumed on RWY_N AVD.
               ARR1 and DEP1.
Repeat the following for each type of AVD
               Move     Toolbar     by    Toolbar repositioned.
               dragging clock button.
               Exercise PREF              Not fully implemented.
               Exercise VIEW              Show and hide sub views.
               Exercise Bays              Show and hide flight strip windows.
               Exercise MAP               Show and hide map elements
               Exercise ZOOM              Zoom in and out on map, re-centring and showing and hiding zoom
                                          tools.
               Exercise LAB               Filter on/off fields within Track labels.
               Exercise EFS               Filter on/off fields within Flight strips.
               Exercise ARR               Filter on/off fields within (DSI) Arrival list.
               Exercise DEP               Filter on/off fields within (DSI) Departure list.




    10.3.3 Companion Windows

    10.3.3.1 CT_TWP_CMPN_01 – Adjacent Companion Window

Scenario ID                CT_TWP_CMPN_01
SRD Reference              2005APT20, 2005APT30, 2005APT40, 2005APT50
Objective                  Demonstrates that a Tower AVD (parent view) can be configured such that it is
                           accompanied by a single adjacent companion view.
                           The views can be configured as “top and bottom” or “left and right”.
                           Each view can be configured with a toolbar either as a window decoration or as a

STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                    f7919ee3-d7fb-4de6-9213-
                                                           1719658e70fc.doc

                                                         Page : 127 of 197

                                                                                     EUROCONTROL



                           free moving autonomous toolbox.
                           For TCWPs the adjacent view can either display the Tower situation (AVD) or the
                           surrounding ATC situation (PVD).
                           For TPWPs the adjacent view can only display the Tower situation (AVD).
Dependencies               None
Resource File              <component test home>/graphics/common/companion/airgrd/adjacentAvd.gsdk
                           <component test home>/ graphics/common/companion/hybrid/adjacentAvd.gsdk


ID   Time       Actions                                  Expectations
1    16:12:00   Launch           airgrd/adjacentAvd      One  TCWP (RWY_N_GRD)                   and      one    TPWP
                scenario                                 (RWY_N_AIR) AVD.
                                                         Both are split into two. Left and right AVD panes.
                                                         Left pane has Tower toolbar.
                                                         Right pane has window decoration.
2               Commence at normal speed.                As scenario progresses observe three departures, three
                                                         arrivals and one vehicle.
3               Utilise Zoom tools                       Observer zoom tools affect only the pane it belongs to.
4               Select     and       move       pane     Panes are resized.
                separator.
5               Move mouse onto an arrival               Label highlights.
                track label.
                                                         Corresponding labels on companion/parent windows
                                                         highlight.
                                                         Associated entry in arrival list highlights.
6               Move mouse onto entry in arrival         Entry in list highlights.
                list.
                                                         Corresponding labels on companion/parent windows
                                                         highlight.
7               Move mouse onto a departure              Label highlights.
                track label.
                                                         Corresponding labels on companion/parent windows
                                                         highlight.
                                                         Associated entry in departure list highlights.
8               Move mouse         onto     entry   in   Entry in list highlights.
                departure list.
                                                         Corresponding labels on companion/parent windows
                                                         highlight.


                Launch        hybrid/adjacentAvd         Observe as above but no TPWP while TCWP is seen as
                scenario                                 TCWP_RWY_N


ID   Time       Actions                                  Expectations
1    16:12:00   Launch                                   One  TCWP (RWY_N_GRD)                   and      one    TPWP
                companion/airgrd/adjacentPvd             (RWY_N_AIR) AVD.

STATUS                                                                                                           TITLE
Company Ref.                                                                                      Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                       Page : 128 of 197

                                                                                   EUROCONTROL



                scenario.                              Only RWY_N_GRD AVD is split into two. Top AVD pane
                                                       and bottom PVD pane.
                                                       AVD has Tower toolbar and window decoration.
2               Commence at normal speed.              As scenario progresses observe three departures, three
                                                       arrivals and one vehicle.
3               Utilise Zoom tools.                    Observer zoom tools affect only the pane it belongs to.
4               Select     and     move       pane     Panes are resized.
                separator.
5               Move mouse onto an arrival             Label highlights.
                track label.
                                                       Corresponding labels on companion/parent windows
                                                       highlight.
                                                       Associated entry in arrival list highlights.
6               Move mouse onto entry in arrival       Entry in list highlights.
                list.
                                                       Corresponding labels on companion/parent windows
                                                       highlight.
7               Move mouse onto a departure            Label highlights.
                track label.
                                                       Corresponding labels on companion/parent windows
                                                       highlight.
                                                       Associated entry in departure list highlights.
8               Move mouse        onto    entry   in   Entry in list highlights.
                departure list.
                                                       Corresponding labels on companion/parent windows
                                                       highlight.


                Launch        hybrid/adjacentPvd       Observe as above but no TPWP while TCWP is seen as
                scenario                               TCWP_RWY_N



    10.3.3.2 CT_TWP_CMPN_02 – Independent Window

Scenario ID        CT_TWP_CMPN_02
SRD Reference      2005APT20, 2005APT30, 2005APT40, 2005APT50
Objective          Demonstrates that a Tower AVD (parent view) can be configured such that it is
                   accompanied by independent companion views.
                   Each view can be configured with a toolbar either as a window decoration or as a free
                   moving autonomous toolbox.
                   For TCWPs the adjacent view can either display the Tower situation (AVD) or the
                   surrounding ATC situation (PVD).
                   For TPWPs the adjacent view can only display the Tower situation (AVD).
Dependencies       None
Resource File      <component test home>/graphics/common/companion/airgrd/independentAvdPvd.gsdk
                   <component test home>/ graphics/common/companion/hybrid/independentAvdPvd.gsdk

STATUS                                                                                                         TITLE
Company Ref.                                                                                    Template : Normal.dotm
                                                    f7919ee3-d7fb-4de6-9213-
                                                           1719658e70fc.doc

                                                          Page : 129 of 197

                                                                                       EUROCONTROL




ID   Time       Actions                                    Expectations
1    16:12:00   Launch scenario                            One TCWP (RWY_N_GRD)                   and     one    TPWP
                                                           (RWY_N_AIR) AVD.
                                                           RWY_N_GRD AVD accompanied by one smaller
                                                           companion AVD (RWY/VIEW_1) and one smaller
                                                           companion PVD (RWY/VIEW_2).
                                                           RWY_N_AIR AVD (RWY_N) accompanied by one
                                                           smaller companion AVD (RWY/VIEW_1).
                                                           Companion views float on top of parent AVD.
                                                           Parent AVD has Tower toolbox.
                                                           Smaller companion AVD has window decoration.
2               Commence at normal speed.                  As scenario progresses observe three departures,
                                                           three arrivals and one vehicle.
3               Utilise Zoom tools                         Observer zoom tools affect only the view it belongs to.
4               Select and resize AVDs and PVDs.           Views are resized independently.
5               Move mouse onto an arrival track           Label highlights.
                label.
                                                           Corresponding labels on companion/parent windows
                                                           highlight.
                                                           Associated entry in arrival list highlights.
6               Move mouse onto entry in arrival           Entry in list highlights.
                list.
                                                           Corresponding labels on companion/parent windows
                                                           highlight.
7               Assume departures and issue taxi           Entries for each departure appear in the Departure list.
                clearances.
8               Move mouse onto a departure                Label highlights.
                track label.
                                                           Corresponding labels on companion/parent windows
                                                           highlight.
                                                           Associated entry in departure list highlights.
9               Move mouse           onto   entry    in    Entry in list highlights.
                departure list.
                                                           Corresponding labels on companion/parent windows
                                                           highlight.


                Launch                                     Observe as above but no TPWP while TCWP is seen
                                                           as TCWP_RWY_N
                hybrid/independentAvdPvd.gsdk
                scenario



     10.3.3.3 CT_TWP_CMPN_03 – Mix Use of Independent and Adjacent Companions

Scenario ID                CT_TWP_CMPN_03

STATUS                                                                                                           TITLE
Company Ref.                                                                                      Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 130 of 197

                                                                                 EUROCONTROL



SRD Reference              2005APT20, 2005APT30, 2005APT40, 2005APT50
Objective                  Demonstrates that a Tower AVD (parent view) can be configured such that it is
                           accompanied by independent and adjacent companion views.
                           Each view can be configured with a toolbar either as a window decoration or as a
                           free moving autonomous toolbox.
                           For TCWPs the adjacent view can either display the Tower situation (AVD) or the
                           surrounding ATC situation (PVD).
                           For TPWPs the adjacent view can only display the Tower situation (AVD).
Dependencies               None
Resource File              <component test home>/graphics/common/companion/airgrd/ mixAvdPvd.gsdk
                           <component test home>/ graphics/common/companion/hybrid/ mixAvdPvd.gsdk


ID   Time       Actions                        Expectations
1    16:12:00   Launch scenario                One TCWP (RWY_N_GRD) and one TPWP (RWY_N_AIR)
                                               AVD.
                                               Both are split into two. Top and bottom AVD panes.
                                               RWY_N_GRD AVD accompanied by one smaller companion
                                               AVD (RWY/VIEW_1) and one smaller companion PVD
                                               (RWY/VIEW_2).
                                               RWY_N_AIR AVD (RWY_N) accompanied by one smaller
                                               companion AVD (RWY/VIEW_1).
                                               Companion views float on top of parent AVD.
                                               Parent AVD has Tower toolbox.
                                               Smaller companion AVD has window decoration.
2               Commence       at    normal    As scenario progresses observe three departures, three
                speed.                         arrivals and one vehicle.
3               Utilise Zoom tools             Observer zoom tools affect only the view it belongs to.
4               Select and resize AVDs         Views are resized independently.
                and PVDs.
5               Move mouse onto an arrival     Label highlights.
                track label.
                                               Corresponding labels on companion/parent windows highlight.
                                               Associated entry in arrival list highlights.
6               Move mouse onto entry in       Entry in list highlights.
                arrival list.
                                               Corresponding labels on companion/parent windows highlight.
7               Assume departures        and   Entries for each departure appear in the Departure list.
                issue taxi clearances.
8               Move mouse onto            a   Label highlights.
                departure track label.
                                               Corresponding labels on companion/parent windows highlight.
                                               Associated entry in departure list highlights.
9               Move mouse onto entry in       Entry in list highlights.

STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 131 of 197

                                                                                 EUROCONTROL



                departure list.                Corresponding labels on companion/parent windows highlight.


                Launch hybrid/adjacentAvd      Observe as above but no TPWP while TCWP is seen as
                scenario                       TCWP_RWY_N



     10.3.4 Route

     10.3.4.1 Route Editor – TPWP
Scenario ID                 CT_TWP_RTE_01
SRD Reference               2006TWR100, 2006TWR110, 2006TWR190, 2006TWR200
Objective                   Demonstrate that the TPWP Route editor can be used to edit the route followed
                            by a flight or vehicle.
                            Show that multiple intermediate points can be made in the selection of a new
                            route.
                            The departure runway and / or runway entry point can be changed.
                            The arrival gate and runway exit point can be changed.
                            The route for flights or vehicles can end at a taxi point. Flights or vehicles at the
                            end of their route will follow a new route when selected.
                            The route editor updates the selected route while editing as the flight or vehicle
                            moves along it, indicating when the chosen route is no longer valid due to
                            deviation from the selection.
Dependencies                None
Resource File               <component test home>/graphics/common/route/ routeEditor.gsdk


ID   Time       Actions                                  Expectations
1.   16:12:00   Launch scenario                          One controller TCWP (RWY_N_GRD) and one pilot
                                                         TPWP (RWY_N_AIR) are displayed.
2.              Commence at normal speed.                As scenario progresses observe one departure, one
                                                         arrival and one vehicle appear.
3.              In the pilot position, left-click on     The TPWP route editor is opened, showing a line
                VAN1 symbol.                             leading to the next taxi point on the vehicle route,
                                                         which is also circled, to show it has been selected as a
                                                         constraint point. A line joins that circle to the mouse
                                                         cursor.
4.              Observe the vehicle travelling on its    As the vehicle passes the constraint point, the circle is
                route with the edit tool open.           removed and the next taxi point on the vehicle route is
                                                         selected.
5.              Select a taxi point on the vehicles      The path chosen is drawn, with the selected constraint
                route a short distance from the first,   points circled.
                and a second point leading away
                from the vehicles current route.
6.              Observe the vehicle travelling on its    The chosen path rolls up as the vehicle moves.
                route with the edit tool open.
                                                         The first selected constraint point is removed as the
STATUS                                                                                                  TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                       Page : 132 of 197

                                                                                EUROCONTROL



                                                         vehicle passes it.
                                                         The second selected constraint point is removed as
                                                         the vehicle passes it.
                                                         The chosen route is shown as invalid when the vehicle
                                                         deviates from the chosen path.
7.             In the pilot position, right-click to     The route edit tool is closed and the display removed.
               cancel the invalid path.
8.             In the pilot position, open the route     The route edit tool is opened and the new path
               edit tool (left-click on VAN1 symbol).    displayed as it is chosen.
               Select a path ending at a taxi point.     When accepted, the route edit tool is closed and the
                                                         display removed.
               Double left-click on the final point to
               accept the route.                         The route for the vehicle has been changed to match
                                                         the selected route (right-click on VAN1 symbol to view
                                                         the route).


9.             In the pilot position open the control    DEP1 starts to taxi to the runway.
               menu and issue a Taxi Clearance
               for DEP1.
10.            In the pilot position left-click on       The TPWP route editor is opened, showing a line
               DEP1 symbol.                              leading to the next taxi point on the departures route,
                                                         which is also circled, to show it has been selected as a
                                                         constraint point. A line joins that circle to the mouse
                                                         cursor.
11.            Observe the departure travelling on       As the departure passes the constraint point, the circle
               its route with the edit tool open.        is removed and the next taxi point on the departures
                                                         route is selected.
12.            Select a taxi point on the departures     The path chosen is drawn, with the selected constraint
               route a short distance from the first,    points circled.
               and a second point leading away
               from the departures current route.
13.            Observe the departure travelling on       The chosen path rolls up as the departure moves.
               its route with the edit tool open.
                                                         The first selected constraint point is removed as the
                                                         departure passes it.
                                                         The second selected constraint point is removed as
                                                         the departure passes it.
                                                         The chosen route is shown as invalid when the
                                                         departure deviates from the chosen path.
14.            In the pilot position, right-click to     The route edit tool is closed and the display removed.
               cancel the invalid path.
15.            In the pilot position, open the route     The route edit tool is opened and the new path
               edit tool (left-click on DEP1 symbol).    displayed as it is chosen.
               Select a path ending at a taxi point.     When accepted, the route edit tool is closed and the
                                                         display removed.
               Double left-click on the final point to
               accept the route.                         The route for the departure has been changed to
                                                         match the selected route (right-click on DEP1 symbol


STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 133 of 197

                                                                                EUROCONTROL



                                                         to view the route).


16.                                                      VAN1 has reached the end of its route.
17.            In the pilot position, left-click on      The TPWP route editor is opened showing a circle
               VAN1 symbol.                              around the current position of the vehicle and a line
                                                         connected to the cursor position.
18.            Select a new route for VAN1.              The route is displayed as it is drawn.
               Accept the new route (double left-        The route edit tool is closed and the display removed
               click on the final point).                when the route is accepted.
                                                         Opening the route display shows the route for VAN1
                                                         has been updated.
19.            In the pilot position, open the control   VAN1 continues along its route.
               menu for VAN1 and issue a Taxi
               clearance.


20.                                                      DEP1 has reached the end of its route.
21.            In the pilot position, left-click on      The TPWP route editor is opened showing a circle
               DEP1 symbol.                              around the current position of the departure and a line
                                                         connected to the cursor position.
22.            Select a new route for DEP1               The route is displayed as it is drawn.
               leading to the far left end of runway
                                                         The route edit tool is closed and the display removed
               09L.
                                                         when the route is accepted.
               Accept the new route (double left-
                                                         Opening the route display shows the route for DEP1
               click on the final point).
                                                         has been updated.
                                                         The label and flightstrip bays have been updated with
                                                         the new runway and SID information.
                                                         DEP1 continues to taxi along the new route.
23.            In the pilot position, open the route     The route is displayed as it is drawn.
               edit tool for DEP1 and select a new
                                       nd                The route edit tool is closed and the display removed
               route leading to the 2 entry point
                                                         when the route is accepted.
               on runway 09L.
                                                         Opening the route display shows the route for DEP1
                                                         has been updated.
                                                         The label and flightstrip bays show the same runway
                                                         information as before.
                                                         DEP1 continues to taxi along the new route.
24.            In the pilot position, issue Taxi,        DEP1 taxis onto the runway and takes off.
               Lineup and Takeoff clearances as
               required for DEP1.


25. 16:27:30   Freeze the scenario.                      ARR1 is airborne and approaching the end of runway
                                                         27R
26.            In the pilot position, open the route     The TPWP route editor is opened showing a circle
               edit tool for ARR1.                       around the current position of the arrival and a line

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 134 of 197

                                                                              EUROCONTROL



                                                       connected to the cursor position.
27.            Select a Taxi point for ARR1 to         The route is displayed from a runway exit point to the
               travel too.                             selected constraint point.
28.            Select a new Gate for ARR1.             The route is displayed as it is drawn.
               Accept the route.                       The route edit tool is closed and the display removed
                                                       when the route is accepted.
                                                       Opening the route display shows the route for ARR1
                                                       has been updated.
                                                       The label and flightstrip bays have been updated with
                                                       the new Gate information.
29.            Commence the scenario.                  ARR1 follows the new route specified.
               Observe ARR1 as it lands and
               commences along the selected
               route.
               Give any Taxi clearances required
30.            In the pilot position, open the route   The route is displayed as it is drawn.
               edit tool for ARR1.
                                                       The route edit tool is closed and the display removed
               Select a new route stopping at a        when the route is accepted.
               taxi point instead of a Gate.
                                                       Opening the route display shows the route for ARR1
               Accept the new route.                   has been updated.
31.            Run the scenario until          ARR1    ARR1 stops at the end of the route.
               reaches the end of its route.
32.            In the pilot position, open the route   The route is displayed as it is drawn.
               edit tool for ARR1.
                                                       The route edit tool is closed and the display removed
               Select a new route stopping at a        when the route is accepted.
               Gate.
                                                       Opening the route display shows the route for ARR1
               Accept the new route.                   has been updated.
                                                       The label and flightstrip bays have been updated with
                                                       the new Gate information.
                                                       ARR1 continues to taxi along the new route.
33.                                                    ARR1 arrives at the specified gate
34.                                                    ARR1 is removed from the display approximately 5
                                                       minutes after arriving at the gate.



      10.3.4.2 Route Editor - TCWP
Scenario ID               CT_TWP_RTE_02
SRD Reference             2006TWR100, 2006TWR110, 2006TWR190, 2006TWR200
Objective                 Demonstrate that the TCWP Route editor can be used to edit the ground route for
                          flights.
                          Show that multiple intermediate points can be made in the selection of a new
                          route.


STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                   f7919ee3-d7fb-4de6-9213-
                                                          1719658e70fc.doc

                                                          Page : 135 of 197

                                                                                    EUROCONTROL



                            The departure runway and / or runway entry point can be changed.
                            The arrival gate and runway exit point can be changed.
                            The route for flights can end at a taxi point. Flights at the end of their route can
                            have a new route selected.
                            The route editor updates the selected route while editing as the flight or vehicle
                            moves along it, indicating when the chosen route is no longer valid due to
                            deviation from the selection.
Dependencies                None
Resource File               <component test home>/graphics/common/route/ routeEditor.gsdk


ID   Time       Actions                                     Expectations
1.   16:12:00   Launch scenario                             One controller TCWP (RWY_N_GRD) and one pilot
                                                            TPWP (RWY_N_AIR) are displayed.
2.              Commence at normal speed.                   As scenario progresses observe one departure, one
                                                            arrival and one vehicle appear.
3.              In the pilot position open the control      DEP1 starts to taxi to the runway.
                menu and issue a Taxi Clearance
                for DEP1.
4.              In the controller position left-click       The TCWP route editor is opened showing a circle
                on DEP1 symbol.                             around the current position of the departure and a line
                                                            connected to the cursor position.
5.              Observe the departure travelling on         As the departure moves, the circle marking the start of
                its route with the edit tool open.          the route edit matches the departures position.
6.              Select a taxi point on the                  The path chosen is drawn, with the selected constraint
                departures route a short distance           points circled.
                from the first, and a second point
                leading away from the departures
                current route.
7.              Observe the departure travelling on         The chosen path rolls up as the departure moves.
                its route with the edit tool open.
                                                            The first selected constraint point is removed as the
                                                            departure passes it.
                                                            The second selected constraint point is removed as the
                                                            departure passes it.
                                                            The chosen route is shown as invalid when the
                                                            departure reaches a taxi point that is not on the chosen
                                                            path.
8.              In the controller position, right-click     The route edit tool is closed and the display removed.
                to cancel the invalid path.
9.              In the controller position, open the        The route edit tool is opened and the new path
                route edit tool (left-click on DEP1         displayed as it is chosen.
                symbol).
                                                            When accepted, the route edit tool is closed and the
                Select a path ending at a taxi point.       display removed.
                Double left-click on the final point to     The route for the departure has been changed to
                accept the route.                           match the selected route (right-click on DEP1 symbol

STATUS                                                                                                          TITLE
Company Ref.                                                                                     Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                        Page : 136 of 197

                                                                                  EUROCONTROL



                                                          to view the route).
10.            Compare the routes for DEP1 in             The controller position shows the new route for DEP1
               the controller and pilot positions.        while the pilot position shows the original route.
               Observe DEP1 as it taxis.                  DEP1 follows the route specified by the pilot position.
11.            In the controller position, left-click     The TCWP route editor is opened showing a circle
               on DEP1 symbol.                            around the current position of the departure and a line
                                                          connected to the cursor position.
12.            Select a new route for DEP1                The route is displayed as it is drawn.
               leading to the far left end of runway
                                                          The route edit tool is closed and the display removed
               09L.
                                                          when the route is accepted.
               Accept the new route (double left-
                                                          Opening the route display shows the route for DEP1
               click on the final point).
                                                          has been updated.
                                                          The label and flightstrip bays have been updated with
                                                          the new runway and SID information.
                                                          DEP1 continues to taxi along the original pilot specified
                                                          route.
13.            In the controller position, open the       The route is displayed as it is drawn.
               route edit tool for DEP1 and select
                                            nd            The route edit tool is closed and the display removed
               a new route leading to the 2 entry
                                                          when the route is accepted.
               point on runway 09L.
                                                          Opening the route display shows the route for DEP1
                                                          has been updated.
                                                          The label and flightstrip bays show the same runway
                                                          information as before.
                                                          DEP1 continues to taxi along the original pilot specified
                                                          route.
14.            In the pilot position, issue Taxi,         DEP1 taxis onto the original runway and takes off.
               Lineup and Takeoff clearances as
               required for DEP1.
15.
16. 16:27:30   Freeze the scenario.                       ARR1 is airborne and approaching the end of runway
                                                          27R
17.            In the controller position, open the       The TCWP route editor is opened showing a circle
               route edit tool for ARR1.                  around the current position of the arrival and a line
                                                          connected to the cursor position.
18.            Select a Taxi point for ARR1 to            The route is displayed from a runway exit point to the
               travel too.                                selected constraint point.
19.            Select a new Gate for ARR1.                The route is displayed as it is drawn.
               Accept the route.                          The route edit tool is closed and the display removed
                                                          when the route is accepted.
                                                          Opening the route display shows the route for ARR1
                                                          has been updated.
                                                          The label and flightstrip bays have been updated with
                                                          the new Gate information.


STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                        Page : 137 of 197

                                                                                   EUROCONTROL



20.              Commence the scenario.                   ARR1 follows the original pilot specified route.
                 Observe ARR1 as it lands and
                 taxis.
                 Give any Taxi clearances required
                 in the pilot position for ARR1.
21.              In the controller position, open the     The route is displayed as it is drawn.
                 route edit tool for ARR1.
                                                          The route edit tool is closed and the display removed
                 Select a new route stopping at a         when the route is accepted.
                 taxi point instead of a Gate.
                                                          Opening the route display shows the route for ARR1
                 Accept the new route.                    has been updated.
                                                          The label and flightstrip bays have been updated with
                                                          the new Gate information.
                                                          ARR1 follows the original pilot specified route.


22.                                                       ARR1 arrives at the original specified gate
23.                                                       ARR1 is removed from the display approximately 5
                                                          minutes after arriving at the gate.



      10.4 Mixed Working Positions

      10.4.1 Mixed TCWP, TPWP and Hybrid TCWP

      10.4.1.1 CT_TWP_AIRGRD_01 – Air/Ground Positions Changing Runway and Gate

Scenario ID                 CT_TWP_AIRGRD_01
SRD Reference               2005G60
Objective                   The test will demonstrate that Controller requests to:
                                   Change runway can be accepted by the Pilot.
                                   Change runway can be rejected by the Pilot.
                                   Change gate can be accepted by the Pilot.
                                   Change gate can be rejected by the Pilot.
                            The test will also demonstrate that pilots are able to deviate from the controller
                            planned taxi route.
Dependencies                None
Resource File               <component test home>/graphics/mixed/twpAirGrdRwyGate.gsdk


ID    Time       Actions                                         Expectations
1.    16:12:00   Launch scenario.                                One  ground            controller      AVD      appears.
                                                                 RWY_N(RWY).
                                                                 One    air   (pilot)    controller      AVD     appears.

STATUS                                                                                                              TITLE
Company Ref.                                                                                         Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 138 of 197

                                                                                 EUROCONTROL



                                                                 RWY_N(PILOT).
2.    16:13:00                                                   DEP1, DEP2, DEP3, ARR1, ARR2 and ARR3
                                                                 have all appeared on displays.
3.               Following actions on arrivals.
4.               On RWY_N(RWY) AVD and using callsign            Labels for ARR1, ARR2 and ARR3 are
                 button, assume ARR1, ARR2 and ARR3.             coloured assumed.
                                                                 Note stands required are W1, W2 and W3.
5.                                                               Arrivals reach TP_1340 and queue and wait for
                                                                 taxi clearance.
6.               RWY_N(Rwy) changes ARR1 stand from              Both AVDs show new stand as EN21.
                 W1 to EN21.
                 RWY_N(Pilot) changes ARR1 stand from
                 W1 to EN21.
7.               RWY_N(Rwy) changes ARR2 stand from              Only RWY_N(Rwy) AVD shows new stand as
                 W2 to EN22.                                     EN22.
8.               RWY_N(Pilot) changes ARR3 stand from            Only RWY_N(Pilot) AVD shows new stand as
                 W1 to EN23.                                     EN23.
9.               As each arrival stops at TP_1340                Observe ARR1 goes to stand EN21 as cleared.
                 RWY_N(Rwy) issues taxi clearance.
                                                                 ARR2 does not go to cleared stand EN22 but
                 Similarly RWY_N(Pilot)       issues      taxi   goes to original stand W2.
                 command.
                                                                 ARR3 does not go to original cleared stand W3
                                                                 but goes to stand EN23.
10.              Following actions on departures.
11.              RWY_N(Rwy) assumes DEP1, Dep2 and               Note departure runway is shown as R09R on
                 DEP3.                                           both AVDs.
12.              RWY_N(Rwy) changes          DEP1    cleared     DEP1 departure runway is shown as R27L on
                 runway to R27L.                                 both AVDs.
                 RWY_N(Pilot) changes DEP1 runway to
                 R27L.
13.              RWY_N(Rwy) changes          DEP2    cleared     DEP2 departure runway is shown as R27L only
                 runway to R27L.                                 RWY_N(Rwy) AVD.
14.              RWY_N(Pilot) changes DEP3 runway to             DEP3 departure runway is shown as R27L only
                 R27L.                                           RWY_N(Pilot) AVD.
15.              RWY_N(Rwy) issues pushback clearances           Departures start to push back to pushback point
                 for DEP1, DEP2 and DEP3.                        where they stop and wait for taxi clearance.
                 RWY_N(Pilot)       issues          pushback
                 commands.
16.              RWY_N(Rwy) issues taxi clearances for           Departures start to taxi to runways.
                 DEP1, DEP2 and DEP3.
                 RWY_N(Pilot) issues taxi commands.
17.              RWY_N(Rwy) issues takeoff clearances            Observe DEP1 takes off on cleared R27L.
                 for DEP1, DEP2 and DEP3.
                                                                 DEP2 does not take off on cleared R27L but on
                 RWY_N(Pilot) issues takeoff commands.           original R09R.

STATUS                                                                                                      TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 139 of 197

                                                                             EUROCONTROL



                                                             DEP3 does not take off on original cleared
                                                             R09L but on R27L.



     10.4.1.2 CT_TWP_AIRGRD_02 – Air/Ground Positions Issuing Arrival Clearances
Scenario ID               CT_TWP_AIRGRD_02
SRD Reference             2005G60
Objective                 The test will demonstrate that Pilots can accept and reject Controller arrival
                          clearance requests e.g. Taxi.
                          The test will also demonstrate that Pilots are able to deviate from the Controller
                          planned clearances.
Dependencies              None
Resource File             <component test home>/graphics/mixed/twpAirGrdArrClr.gsdk


ID   Time       Actions                                             Expectations
1.   16:12:00   Launch scenario.                                    One ground controller AVD appears.
                                                                    RWY_N(RWY).
                                                                    One air (pilot) controller AVD appears.
                                                                    RWY_N(PILOT).
2.   16:13:00                                                       ARR1, ARR2 and ARR3                have   all
                                                                    appeared on displays.
3.              RWY_N(RWY) AVD and using callsign button,           Labels for ARR1, ARR2 and ARR3 are
                assume ARR1, ARR2 and ARR3.                         coloured assumed
4.                                                                  Arrivals reach TP_1340 and queue and
                                                                    wait for taxi clearance.
5.              RWY_N(RWY) gives ARR1 taxi clearance.               ARR1 continues to stand.
                RWY_N(Pilot) issues ARR1 taxi command.
6.              RWY_N(Pilot) issues ARR2 taxi command.              ARR2 continues      to     stand    without
                                                                    clearance.
7.              RWY_N(RWY) gives ARR3 taxi clearance.               ARR3 remains at TP_1340 as pilot has
                                                                    not issued command.



     10.4.1.3 CT_TWP_AIRGRD_03 – Air/Ground Positions Issuing Departure Clearances

Scenario ID               CT_TWP_AIRGRD_03
SRD Reference             2005G60
Objective                 The test will demonstrate that Pilots can accept and reject Controller departure
                          clearance requests e.g Pushback, Taxi, Lineup, Takeoff.
                          The test will also demonstrate that Pilots are able to deviate from the Controller
                          planned clearances.


STATUS                                                                                                   TITLE
Company Ref.                                                                            Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 140 of 197

                                                                            EUROCONTROL



Dependencies               None
Resource File              <component test home>/graphics/mixed/twpAirGrdDepClr.gsdk


ID    Time       Actions                                 Expectations
1.    16:12:00   Launch scenario.
2.    16:13:00                                           DEP1, DEP2 and DEP3 have all appeared on
                                                         displays.
3.               RWY_N(Rwy) assumes DEP1, DEP2           Label coloured assumed for RWY_N(RWY).
                 and DEP3.
4.               DEP1
5.               RWY_N(Rwy)        issues   pushback     DEP1 pushes back to pushback point and waits
                 clearance for DEP1.                     for taxi clearance.
                 RWY_N(Pilot)    issues     pushback
                 command for DEP1.
6.               RWY_N(Rwy) issues taxi clearance for    DEP1 taxis to line-up point.
                 DEP1.
                 RWY_N(Pilot) issues taxi command for
                 DEP1.
7.               RWY_N(Rwy) issues line-up clearance     DEP1 lines-up on runway
                 for DEP1.
                 RWY_N(Pilot) issues line-up command
                 for DEP1.
8.               RWY_N(Rwy) issues take-off clearance    DEP1 takes-off on runway
                 for DEP1.
                 RWY_N(Pilot) issues take-off command
                 for DEP1.
9.               DEP2
10.              RWY_N(Pilot)    issues     pushback     DEP2 pushes back to pushback point and waits
                 command for DEP2.                       for taxi clearance.
11.              RWY_N(Pilot) issues taxi command for    DEP2 taxis to line-up point.
                 DEP2.
12.              RWY_N(Pilot) issues line-up command     DEP2 lines-up on runway
                 for DEP2.
13.              RWY_N(Pilot) issues take-off command    DEP2 takes-off on runway
                 for DEP2.
14.              DEP3
15.              RWY_N(Rwy)        issues   pushback     DEP3 remains on stand as pilot has not issued
                 clearance for DEP3.                     command.



      10.4.1.4 CT_TWP_HYBRID_01 – Air/Ground/Hybrid Working Positions
Scenario ID                CT_TWP_HYBRID_01

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 141 of 197

                                                                                  EUROCONTROL



SRD Reference             2005G70
Objective                 The test will demonstrate that a mix of working positions can provide a flexible
                          simulation environment.
                          The test will contain one Pilot position, one Controller position and one Hybrid
                          position feeding the Pilot and Controller positions.
                          Functions illustrated will include:
                                  Hybrid Transfer and Controller Assuming aircraft.
                                  Controller Transfer and Hybrid Assuming aircraft.
                                  Pilot controlling    aircraft    outside   Pilot‟s    corresponding       Controller
                                   jurisdiction.
Dependencies              None
Resource File             <component test home>/graphics/mixed/twpAirGrdHybrid.gsdk


ID   Time       Actions                                            Expectations
1.   16:12:00   Launch scenario.                                   One ground controller              AVD     appears.
                                                                   RWY_N(RWY).
                                                                   One air (pilot)       controller   AVD     appears.
                                                                   RWY_N(PILOT).
                                                                   One hybrid controller AVD appears. APR_N.
2.   16:13:00                                                      DEP1, DEP2, DEP3, ARR1, ARR2 and ARR3
                                                                   have all appeared on displays.
                                                                   On APR_N:
                                                                   DEP1, DEP2 and DEP3 are coloured
                                                                   advanced with callsign coloured assumed.
                                                                   ARR1, ARR2           and   ARR3     are    coloured
                                                                   advance.
                                                                   On RWY_N:
                                                                   ARR1, ARR2 and ARR3 are coloured
                                                                   advanced with callsign coloured assumed.
                                                                   DEP1, DEP2           and   DEP3     are    coloured
                                                                   advance.
3.              On APR_N(Hybrid) AVD and using callsign            On APR_N:
                button, assume DEP1, DEP2 and DEP3.
                                                                   DEP1, DEP2           and   DEP3     are    coloured
                                                                   assumed.
                                                                   On RWY_N:
                                                                   DEP1, DEP2           and   DEP3     are    coloured
                                                                   advance.
4.              On RWY_N(RWY) AVD and using callsign               On APR_N:
                button, assume ARR1, ARR2 and ARR3.
                                                                   ARR1, ARR2           and   ARR3     are    coloured
                                                                   advance.
                                                                   On RWY_N:

STATUS                                                                                                          TITLE
Company Ref.                                                                                    Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 142 of 197

                                                                              EUROCONTROL



                                                              ARR1, ARR2        and    ARR3     are   coloured
                                                              assumed.
5.                                                            Arrivals reach TP_1338 and queue and wait
                                                              for taxi clearance.
6.             ARR1.
7.             RWY_N(RWY) gives ARR1 taxi clearance.          ARR1 continues to stand.
               RWY_N(Pilot) issues ARR1 taxi command.
8.             RWY_N(Rwy) transfers ARR1.                     RWY_N(Rwy)        sees           ARR1          As
                                                              assumedTransferred.
                                                              APR_N(Hybrid)      sees           ARR1         as
                                                              advanceTransferred
9.             APR_N(Hybrid) assumes ARR1.                    RWY_N(Rwy) sees ARR1 As concerned.
                                                              APR_N(Hybrid) sees ARR1 as assumed.
                                                              ARR1 continues to stand.
10.            RWY_N(Pilot) holds then taxis ARR1             ARR1 stops and then continues.
11.            ARR2.
12.            RWY_N(Rwy) transfers ARR2.                     RWY_N(Rwy)        sees           ARR2          As
                                                              assumedTransferred.
                                                              APR_N(Hybrid)      sees           ARR2         as
                                                              advanceTransferred
13.            APR_N(Hybrid) assumes ARR2.                    RWY_N(Rwy) sees ARR2 As concerned.
                                                              APR_N(Hybrid) sees ARR2 as assumed.
14.            APR_N(Hybrid) issues taxi command for          ARR2 taxis to stand.
               ARR2.
15.            ARR3.
16.            RWY_N(Rwy) transfers ARR3.                     RWY_N(Rwy)        sees           ARR3          As
                                                              assumedTransferred.
                                                              APR_N(Hybrid)      sees           ARR3         as
                                                              advanceTransferred
17.            APR_N(Hybrid) issues taxi command for          RWY_N(Rwy) sees ARR1 As concerned.
               ARR3.
                                                              APR_N(Hybrid) sees ARR1 as assumed.
                                                              ARR1 continues to stand.
18.            DEP1.
19.            APR_N(Hybrid)   gives   DEP1      pushback     DEP1 pushes back to pushback point and
               clearance.                                     waits for taxi clearance.
20.            APR_N(Hybrid) gives DEP1 taxi clearance.       DEP1 starts to taxi to line-up point.
21.            APR_N(Hybrid) transfers DEP1.                  APR_N(Hybrid)       sees          DEP1         As
                                                              assumedTransferred.
                                                              RWY_N(Rwy)         sees          DEP1          as
                                                              advanceTransferred


STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 143 of 197

                                                                             EUROCONTROL



22.            RWY_N(Rwy) assumes DEP1.                       APR_N(Hybrid) sees DEP1 As concerned.
                                                              RWY_N(Rwy) sees DEP1 as assumed.
                                                              DEP1 continues to LUP point.
23.            RWY_N(RWY) gives take-off clearance.           DEP1 line-up and takes-off.
               RWY_N(Pilot)    gives    DEP1       take-off
               command.
24.            DEP2.
25.            APR_N(Hybrid)   gives    DEP2     pushback     DEP1 pushes back to pushback point and
               clearance.                                     waits for taxi clearance.
26.            APR_N(Hybrid) gives DEP2 taxi clearance.       DEP1 taxis to line-up point and waits for line-
                                                              up clearance
27.            APR_N(Hybrid) transfers DEP2.                  APR_N(Hybrid)       sees         DEP2         As
                                                              assumedTransferred.
                                                              RWY_N(Rwy)         sees         DEP2          as
                                                              advanceTransferred
28.            RWY_N(Rwy)      issues    DEP2       line-up   DEP1 is assumed by RWY_N.
               clearance.
                                                              APR_N(Hybrid) sees DEP2 As concerned.
                                                              RWY_N(Rwy) sees DEP2 as assumed.
29.            RWY_N(Pilot)    gives    DEP2        line-up   DEP1 lines-up on runway.
               command.
30.            RWY_N(RWY) gives take-off clearance.           DEP3 takes-off.
               RWY_N(Pilot)    gives    DEP2       take-off
               command.
31.            DEP3.
32.            APR_N(Hybrid)   gives    DEP3     pushback     DEP3 pushes back to pushback point and
               clearance.                                     waits for taxi clearance.
33.            APR_N(Hybrid) gives DEP3 taxi clearance.       DEP1 taxis to line-up point and waits for line-
                                                              up clearance
34.            APR_N(Hybrid) transfers DEP3.                  APR_N(Hybrid)       sees         DEP3         As
                                                              assumedTransferred.
                                                              RWY_N(Rwy)         sees         DEP3          as
                                                              advanceTransferred
35.            RWY_N(Rwy) assumes DEP3.                       APR_N(Hybrid) sees DEP3 As concerned.
                                                              RWY_N(Rwy) sees DEP3 as assumed.
36.            RWY_N(RWY) gives take-off clearance.           DEP3 lines-up and takes-off.
               RWY_N(Pilot)    gives    DEP3       take-off
               command.




STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 144 of 197

                                                                         EUROCONTROL




     11 UTCWP COMPONENT TESTS

     11.1 Automate Controller Positions

     11.1.1 CT_uTCWP_01 – Automatic Orders and Clearances Test


Scenario ID                CT_uTCWP_01
SRD Reference              940, 950, 960
Objective                  Demonstrate that a UTCWP can be used in place of a TCWP, and in this case no
                           graphics appear, and all orders and clearances are given automatically.
Dependencies               None
Resource File              <component test home>/utcwp/utcwp_all_there.gsdk
                           <component test home>/utcwp/utcwp_no_taxiway.gsdk
                           <component test home>/utcwp/utcwp_only_taxiway.gsdk


ID    Time       Actions                   Expectations
1                Launch                    3 AVD windows appear – “CARGO_N”, “TWY_N” and
                 “utcwp_all_there”   and   “RWY_N”.
                 start Console
                                           A console window appears.
2     16:12:10                             “DEPARTURE” appears at a gate, “ARRIVAL” appears,
                                           decelerating at the runway.
3                CARGO_N:   Assume         “DEPARTURE” becomes assumed by CARGO_N.
                 “DEPARTURE”

                 RWY_N:           Assume   “ARRIVAL” becomes assumed by RWY_N
                 “ARRIVAL”
4     16:12:20   CARGO_N:      Give        “DEPARTURE” starts to move
                 “DEPARTURE” a Taxi
                 Clearance
5     16:13:00                             “DEPARTURE” crosses boundary out of “CARGO_N”
6                CARGO_N: Transfer         “DEPARTURE” becomes transferred
                 “DEPARTURE”
                 TWY_N:     Assume         “DEPARTURE” becomes assumed by TWY_N
                 “DEPARTURE
7     16:14:00                             User TWY_N cannot give lineup clearance.
8                TWY_N:     Transfer       “DEPARTURE” becomes transferred
                 “DEPARTURE”
                 RWY_N:     Assume         “DEPARTURE” becomes assumed by RWY_N
                 “DEPARTURE”


STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 145 of 197

                                                                            EUROCONTROL



9                RWY_N:             Give    “DEPARTURE” begins to line up
                 “DEPARTURE”           a
                 lineup clearance
10    16:14:30                              “ARRIVAL” has left runway and is leaving RWY_N sector.
11               RWY_N:            Give     “DEPARTURE” begins to take off.
                 “DEPARTURE”          a
                                            “ARRIVAL” becomes transferred
                 takeoff     clearance.
                 Transfer “ARRIVAL”
                 TWY_N:        Assume       “ARRIVAL” becomes assumed by TWY_N
                 “ARRIVAL” and give
                 taxi   clearance   at
                 TP_86.
12    16:16:45                              “ARRIVAL” moves into the CARGO_N ground sector.
13               TWY_N:        Transfer     “ARRIVAL” becomes transferred
                 “ARRIVAL”
                 CARGO_N:      Assume       “ARRIVAL” becomes assumed by CARGO_N
                 “ARRIVAL”
14    16:17:30                              “ARRIVAL” stops at gate EN_21, and disappears after “arrival
                                            occupancy time” seconds.


15               Load                       Only two AVD windows appear – one for CARGO_N, and one
                 “utcwp_no_taxiway”         for RWY_N.
16               Repeat steps       1-14,   The same results occur, with the missing instructions being
                 omitting            any    performed by the UTCWP component for TWY_N.
                 instructions         for
                 “TWY_N”


17               Load                       Only two AVD windows appear – one for CARGO_N, and one
                 “utcwp_only_taxiway”       for RWY_N.
18               Repeat steps       1-14,   The same results occur, with the missing instructions being
                 omitting            any    performed by the UTCWP components for CARGO_N and
                 instructions         for   RWY_N.
                 “CARGO_N”             or
                 “RWY_N”




     12 TSN COMPONENT TESTS

     12.1 Exclusion Area Closed Runway

     12.1.1 CT_TSN_CLOSED_01 – Closed Runway Incursion
Scenario ID              CT_TSN_CLOSED_01
SRD Reference            2005G90, 2005G100, 2005G110
Objective                For a closed runway associated with an exclusion area the scenario will

STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 146 of 197

                                                                             EUROCONTROL



                          demonstrate that:
                                An arrival whose time to the area‟s runway threshold is less than the long
                                 final time will initiate an ALARM alert.
                                A departure lining-up or taking off from the area‟s runway will initiate
                                 ALARM alerts.
                                A mobile (vehicle/aircraft) in the exclusion area will initiate an
                                 INFORMATION alert.
Dependencies              None
Resource File             <component test home>/tsn/tsnClosedArea.gsdk
                          <component test home>/tsn/tsnClosedAreaPilot.gsdk




ID   Time       Actions                       Expectations
1    16:12:00   Launch and run scenario       RWY_N AVD and LFPG PVD appear.
                tsnClosedArea.                RWY_N AVD has Arrivals, Departures and Alert lists.
2                                             AMBULANCE appears on RWY_N travelling towards northern
                                              most runway.
3                                             AMBULANCE enters exclusion area EXCLUSION_R27R.
                                              Informational alert highlighted in Alert window.
                                              Callsign highlighted in “information” colour.
4                                             AMBULANCE leaves exclusion area EXCLUSION_R27R.
                                              Informational alert removed from Alert window.
                                              Callsign no longer highlighted in “information” colour.
5                                             DEP1 stops at runway hold point (outside exclusion area).
                                              DEP1 automatically given clearance and begins to lineup. On
                                              entering exclusion area EXCLUSION_R27R alarm alert raised.
                                              Alarm alert highlighted in Alert window.
                                              Callsign highlighted in “alarm” colour.
                                              DEP1 continues onto runway, completes lineup.
                                              After 20s automatically given takeoff clearance and begins to
                                              accelerate down runway.
                                              DEP1 takes-off.
                                              Alarm alert removed from Alert window.
                                              Callsign no longer highlighted.
7                                             DEP2 enters exclusion area EXCLUSION_R27R.
                                              Information alert highlighted in Alert window.
                                              Callsign highlighted in “information” colour.
                                              DEP2 stops to wait for lineup clearance.
                                              20s later automatically given lineup clearance.
                                              DEP2 lines-up.
                                              20s later automatically give takeoff clearance.
                                              DEP2 accelerates to take off speed.
8                                             DEP2 takes-off.
                                              Information alert removed from Alert window.
                                              Callsign no longer highlighted.
9                                             On LFPG PVD note that ARR1 approaches airport from the
                                              east.
                                              On RWY_N AVD note that ARR1 entry in Arrival list is not
                                              highlighted but is intending to use R27R.
10                                            ARR1 callsign in Arrival list is coloured “alarm”. (Note time)
STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 147 of 197

                                                                             EUROCONTROL



11                                          ARR1 lands on R27R and decelerates.
                                            Note: The time since the beginning of the alarm may differ
                                            slightly to the long final time (100s).
                                             The time discrepancy is due to arrival not flying a straight
                                            trajectory to the runway.
12                                          ARR1 leaves the runway and then the exclusion area.
                                            Alarm alert removed from Alert window.
                                            Callsign no longer highlighted.



ID   Time       Actions                                   Expectations
1    16:12:00   Launch      and       run     scenario    RWY_N RWY and Pilot AVDs and LFPG PVD
                tsnClosedAreaPilot.                       appear.
                                                          RWY_N(RWY) has Arrivals, Departures and Alert
                                                          lists.
2    16:12:17                                             DEP1 appears advance transferred.
                                                          DEP1 is cleared for runway of R09L.
3               RWY_N(RWY) assume DEP1                    DEP1 shown as assumed on AVDs.
4               RWY(PILOT)    issues   pushback           DEP1 starts to pushback and moves onto apron
                command.                                  where it stops
5               RWY(PILOT) issues taxi command.           DEP1 starts to taxi.
6               RWY(PILOT) changes runway to R27R         RWY_N air shows new runway.
                i.e. the closed runway.                   Note RWY_N ground labels and list show original
                                                          cleared runway.
                                                          DEP1 continues to taxi.
7               RWY(PILOT) issues taxi commands           DEP1 continues to taxi to start lineup point for
                whenever DEP1 stops at taxipoints with    runway R27R. On reaching start lineup point DEP1
                delays.                                   stops.
8               RWY(PILOT) issues lineup command.         DEP1 taxis into exclusion area raising an
                                                          information alert.
                                                          DEP1 continues onto runway to complete lineup
                                                          and stops.
9               RWY(PILOT) issues takeoff command         DEP1 begins to accelerate down runway.
                                                          Note alert does not become alarm straight away
                                                          but only when DEP1 has accelerated to a speed
                                                          considered as a takeoff speed.




     12.2 Exclusion Area Open Runway

     12.2.1 CT_TSN_OPEN_01 – Arriving On Wrong Runway
Scenario ID               CT_TSN_OPEN_01
SRD Reference             2005G120
Objective                 This scenario will test that an arrival landing on the opposite runway to the one it
                          has been cleared for will raise an alert only if there is an obstruction on the
                          runway.
Dependencies              None
Resource File             <component test home>/tsn/tsn_2005G120.gsdk

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 148 of 197

                                                                             EUROCONTROL



                          <component test home>/tsn/tsn_2005G120Obstruction.gsdk


ID   Time       Actions                                   Expectations
1    16:12:00   Launch    and        run      scenario    RWY_N ground and air AVDs and LFPG PVD
                tsn_2005G120.                             appear.
                                                          RWY_N ground AVD has Arrivals, Departures and
                                                          Alert lists.
2    16:12:10                                             ARR1 appears in Arrivals list.
3    16:12:12                                             ARR1 appears on PVD.
     16:16:50                                             Arrival      list shows  ARR1    assumable   by
                                                          RWY_N(RWY)
                RWY_N(RWY) assumes ARR1.                  ARR1 arrival entry shown as assumed.
                RWY_N(RWY)      changes   cleared         RWY_N(RWY) displays new cleared runway R27L.
                runway from R09R to R27L.                 RWY_N(Pilot) AVD sees actual runway to be used.
5    16:18:20                                             ARR1 lands on R09RL and decelerates.
                                                          No alerts are raised.



ID   Time       Actions                             Expectations
1    16:12:00   Launch   and  run     scenario      RWY_N RWY and Pilot AVDs and LFPG PVD appear.
                tsn_2005G120Obstruction.            RWY_N(RWY) has Arrivals, Departures and Alert lists.
2    16:12:06                                       Ambulance appears on AVDs.
3    16:12:10                                       ARR1 appears in Arrivals list.
4    16:12:12                                       ARR1 appears on PVD.
5    16:12:30                                       Ambulance blocks runways R09R and R27L.
6    16:16:50                                       Arrival list shows ARR1 assumable by RWY_N(RWY)
7               RWY_N(RWY) assumes ARR1.            ARR1 arrival entry shown as assumed.
8               RWY_N(RWY) changes cleared          RWY_N(RWY) displays new cleared runway R27L.
                runway from R09R to R27L.           RWY_N(Pilot) AVD sees actual runway to be used.
10   16:17:20                                       Information alert raised as ARR1 approaches within long
                                                    final time to threshold of R27L.
11   16:18:14                                       Alarm alert raised as ARR1 approaches within short
                                                    short time to threshold of R27L.
12   16:18:20                                       ARR1 lands on R09RL and decelerates.
                                                    Alarm alert still raised.
13   16:20:32                                       ARR1 travels beyond ambulance.
                                                    Alert removed.




     12.2.2 CT_TSN_OPEN_02 – Lineup/Takeoff In Wrong Direction
Scenario ID               CT_TSN_OPEN_02
SRD Reference             2005G130
Objective                 This scenario will test that a departure:
                                 Lining-up on the wrong runway will issue an information alert.
                                 Taking off on the wrong runway will issue an alarm alert.
Dependencies              None

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 149 of 197

                                                                               EUROCONTROL



Resource File             <component test home>/tsn/tsn_2005G130.gsdk


ID   Time       Actions                        Expectations
1    16:12:00   Launch and run scenario.       RWY_N RWY and Pilot AVDs and LFPG PVD appear.
                                               RWY_N RWY has Arrivals, Departures and Alert lists.
2    16:12:17                                  DEP1 appears on AVDs in advance transferred colour and
                                               assigned to R27L.
3               RWY_N(RWY) assume
                DEP1 and give pushback
                clearance.
4               RWY_N(Pilot) issues            On reaching end of pushback taxi prompt appears in label.
                pushback command.
5               RWY_N(RWY) gives DEP1
                taxi clearance.
6               RWY_N(Pilot) issues taxi       DEP1 starts to taxi forward.
                command.
7               RWY_N (Pilot) change           RWY_N(RWY) displays original/cleared runway R27L.
                runway to R09R.                RWY_N(Pilot) AVD sees actual runway to be used.
8               RWY_N (Pilot) gives DEP1       DEP1 travels on to R09R and lines up in R09R direction.
                lineup command from label.     Information alert shown in Alert list.
                                               Callsign highlighted in information colour.
                                               Note alert not raised when lineup command given but when
                                               flight orientation approximates to runway direction.
9               RWY_N (Pilot) gives DEP1       DEP1 accelerates on R09R.
                takeoff command.               On exceeding TSN.RUNWAY_MAX_TAXISPEED_KTS the
                                               alert is alarm coloured.
                                               After takeoff alert is removed from labels and lists.


     12.2.3 CT_TSN_OPEN_03 – Arrival With Mobile on Runway
Scenario ID               CT_TSN_OPEN_03
SRD Reference             2005G140
Objective                 This scenario will test that an arrival will cause an information alert when an
                          obstructing mobile is ahead of the arrivals track and the time to arrival is within the
                          long final time.
                          When the time to arrival is within the short final time the alert is promoted from
                          information to alarm.
                          When the obstructing mobile is behind the arrivals track heading the alert is
                          removed.
Dependencies              None
Resource File             <component test home>/tsn/tsn_2005G140.gsdk


ID   Time       Actions                Expectations
1    16:12:00   Launch and       run   RWY_N AVD and LFPG PVD appear.
                scenario.              RWY_N AVD has Arrivals, Departures and Alert lists.
2    16:12:07                          AMBULANCE appears on AVD and starts to travel to R27L.
                                       On reaching R27L AMBULANCE stops on runway.
3    16:13:01                          On AVD Arrival list an entry for ARR1 appears indicating that it will

STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 150 of 197

                                                                               EUROCONTROL



                                      land on R27L.
4    16:13:12                         On PVD ARR1 appears travelling towards airport.
5    16:14:46                         AVD Arrival list entry for ARR1 shows information alert.
                                      Alert list has information alert for ARR1 and AMBULANCE.
6    16:15:48                         AVD Arrival list entry for ARR1 shows alarm alert.
                                      Alert list has alarm alert for ARR1 and AMBULANCE.
7    16:16:38                         ARR1 lands on R27L. Alert still shown as alarm.
                                      After passing AMBULANCE on runway, alert is removed from labels
                                      and lists.
                                      Time between landing and first (information) alert is ~115s.
                                      Time between landing and alert becoming alarm coloured is ~55s
                                      Note long and short final times are 100 and 50.
                                      Note: The time discrepancy is due to arrival not flying a straight
                                      trajectory to the runway.




     12.2.4 CT_TSN_OPEN_04 – Arrival with Departure On Runway
Scenario ID               CT_TSN_OPEN_04
SRD Reference             2005G150
Objective                 This first scenario will test that an arrival will cause an information alert when an
                          obstructing departure is ahead of the arrivals track and the time to arrival is within
                          the long final time (100s).
                          When the time to arrival is within the short final time (50s) the alert is promoted
                          from information to alarm.
                          The second scenario will test that the short final time can be qualified with short
                          (2000m) and long (2500m) final approach distance criteria.
                          When separation is between short and long final distance alerts shown as alarm if
                          obstructing departure has not taken off. If the departure has taken off then the
                          alert is shown as information.
                          To aid scenario verification fixes R27L_3000, R27L_2500, R27L_2000 and
                          R27L_1000 have been defined to indicate (approx) distances to touchdown for
                          runway R27L. Also ATC sectors have been defined which match the geographic
                          areas of the runway exclusion areas. All of these can be seen on the PVD.
Dependencies              None
Resource File             <component test home>/tsn/tsn_2005G150.gsdk
                          <component test home>/tsn/tsn_2005G150_applyspacing.gsdk


ID   Time       Actions           Expectations
1    16:12:00   Launch            RWY_N AVD and LFPG PVD appear.
                tsn_2005G150      RWY_N AVD has Arrivals, Departures and Alert lists.
                and        run
                scenario.
2                                 DEP1 appears on AVD and starts to taxi to R27L
3    16:15:50                     On AVD Arrival list an entry for ARR1 appears.
                                  ARR1 appears on PVD.
4    16:17:08                     DEP1 reaches R27L and waits for takeoff clearance.
5    16:18:00                     On AVD:
STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                Page : 151 of 197

                                                                         EUROCONTROL



                                ARR1 shows information alert on label and in Arrival list.
                                DEP1 shows information alert on label and in Departure list.
                                Alert window shows information alert between ARR1 and DEP1.
6    16:18:54                   On AVD:
                                ARR1 shows alarm alert on label and in Arrival list.
                                DEP1 shows alarm alert on label and in Departure list.
                                Alert window shows alarm alert between ARR1 and DEP1.
7    16:19:24                   DEP1 takes-off. Note that DEP1 has been configured with a very low
                                takeoff speed.
                                All alerts are removed from labels and lists.
8    16:20:30                   ARR1 has landed at R27L. DEP1 has cleared runway R27L. No alerts are
                                shown.



ID   Time       Actions                     Expectations
1    16:12:00   Launch                      RWY_N AVD and LFPG PVD appear.
                tsn_2005G150_applyspacing   RWY_N AVD has Arrivals, Departures and Alert lists.
                and run scenario.
2                                           DEP1 appears on AVD and starts to taxi to R27L
3    16:16:00                               On AVD Arrival list an entry for ARR1 appears.
                                            ARR1 appears on PVD.
4    16:15:14                               DEP1 reaches R27L and waits for takeoff clearance.
5    16:18:00                               On AVD:
                                            ARR1 shows information alert on label and in Arrival list.
                                            DEP1 shows information alert on label and in Departure list.
                                            Alert window shows information alert between ARR1 and
                                            DEP1.
6    16:19:12                               On AVD:
                                            ARR1 shows alarm alert on label and in Arrival list.
                                            DEP1 shows alarm alert on label and in Departure list.
                                            Alert window shows alarm alert between ARR1 and DEP1.
                                            Note on PVD ARR1 has just passed R27L_2500 and lies
                                            between R27L_2500 and R27L_2000.
7    16:19:24                               DEP1 takes-off. Note that DEP1 has been configured with a
                                            very low takeoff speed.
8    16:19:29                               DEP1 appears on PVD.
                                            On AVD:
                                            ARR1 shows alarm alert in Arrival list.
                                            DEP1 shows alarm alert in Departure list.
                                            Alert window shows alarm alert between ARR1 and DEP1.
9    16:19:42                               ARR1 is removed from PVD. ARR1 appears on AVD. ARR1
                                            decelerates on R27L.
                                            Alerts are still shown as alarm.
10   16:20:03                               On AVD:
                                            ARR1 shows information alert on label and in Arrival list.
                                            DEP1 shows information alert in Departure list.
                                            Alert window shows information alert between ARR1 and
                                            DEP1.
                                            Note DEP1 still flying within exclusion area and on same
                                            heading as runway but separation has now exceeded short

STATUS                                                                                             TITLE
Company Ref.                                                                        Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 152 of 197

                                                                                EUROCONTROL



                                                final separation but within long final separation.
                                                Separation can be compared using runway lengths (R09L
                                                R27R = 2700M, R009R R27L = 4200M) to the track reported
                                                positions. DEP1 track reported on PVD, ARR1 track reported
                                                on AVD. ARR1 on R27L but adjacent to start of runway
                                                R27R. DEP1 approx 4/5 length (use trail dots to approximate)
                                                of R09L_R27R along R09R_R27L.
11   16:20:15                                   All alerts are removed as DEP1 leaves exclusion area.




     12.2.5 CT_TSN_OPEN_05 – Arrival With Arrival On Runway
Scenario ID               CT_TSN_OPEN_05
SRD Reference             2005G160
Objective                 This first scenario will test that an arrival will cause an information alert when an
                          obstructing arrival is ahead of the arrivals track and the time to arrival is within the
                          long final time (100s).
                          When the time to arrival is within the long final time (50s) the alert is promoted
                          from information to alarm.
                          The second scenario will test that the long final time can be qualified with the long
                          (2500m) final approach distance criteria.
                          When time to threshold is less than short final time and separation is greater than
                          long final distance alerts shown as information. When separation is less than long
                          final distance the alert is shown as alarm.
                          Applying the separation in the third scenario demonstrates two alerts for one
                          mobile with the higher priority alert taking precedence.
                          To aid scenario verification fixes R27L_3000, R27L_2500, R27L_2000 and
                          R27L_1000 have been defined to indicate (approx) distances to touchdown for
                          runway R27L. Also ATC sectors have been defined which match the geographic
                          areas of the runway exclusion areas. All of these can be seen on the PVD.
Dependencies              None
Resource File             <component test home>/tsn/tsn_2005G160.gsdk
                          <component test home>/tsn/tsn_2005G160_applyspacing.gsdk
                          <component test home>/tsn/tsn_2005G160_3arr_applyspacing.gsdk


ID   Time       Actions             Expectations
1    16:12:00   Launch              RWY_N AVD and LFPG PVD appear.
                tsn_2005G160        RWY_N AVD has Arrivals, Departures and Alert lists.
                and run scenario.
2    16:12:02                       On AVD Arrival list an entry for ARR1 appears.
3    16:12:12                       ARR1 appears on PVD.
4    16:14:01                       On AVD Arrival list an entry for ARR2 appears
5    16:14:12                       ARR2 appears on PVD.
6    16:15:54                       ARR1 lands on R27L.
7    16:16:11                       On AVD:
                                    ARR1 shows information alert on label and in Arrival list.
STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                 Page : 153 of 197

                                                                          EUROCONTROL



                                 ARR2 shows information alert in Arrival list.
                                 Alert window shows information alert between ARR1 and ARR2.
8    16:17:04                    On AVD:
                                 ARR1 shows alarm alert on label and in Arrival list.
                                 ARR2 shows alarm alert in Arrival list.
                                 Alert window shows alarm alert between ARR1 and ARR2.
9    16:17:54                    ARR2 lands on R27L.
10   16:18:59                    ARR1 leaves runway exclusion area. All alerts removed.



ID   Time       Actions                     Expectations
1    16:12:00   Launch                      RWY_N AVD and LFPG PVD appear.
                tsn_2005G160_applyspacing   RWY_N AVD has Arrivals, Departures and Alert lists.
                and run scenario.
2    16:12:02                               On AVD Arrival list an entry for ARR1 appears.
3    16:12:12                               ARR1 appears on PVD.
4    16:14:01                               On AVD Arrival list an entry for ARR2 appears
5    16:14:12                               ARR2 appears on PVD.
6    16:15:54                               ARR1 lands on R27L.
7    16:16:11                               On AVD:
                                            ARR1 shows information alert on label and in Arrival list.
                                            ARR2 shows information alert in Arrival list.
                                            Alert window shows information alert between ARR1 and
                                            ARR2.
8    16:17:55                               ARR2 lands on R27L.
                                            Using R09L R27R runway pair as a gauge, ARR1 and ARR2
                                            are separated by the same length (i.e. 2700m)
9    16:18:22                               On AVD:
                                            ARR1 shows alarm alert on label and in Arrival list.
                                            ARR2 shows alarm alert in Arrival list.
                                            Alert window shows alarm alert between ARR1 and ARR2.
                                            Using R09L R27R runway pair as a gauge, ARR1 and ARR2
                                            are now separated by less than long final separation (i.e. less
                                            than 2500m)
10   16:18:59                               ARR1 leaves runway exclusion area. All alerts removed.



ID   Time       Actions                           Expectations
1    16:12:00   Launch                            RWY_N AVD and LFPG PVD appear.
                tsn_2005G160_3arr_applyspacing    RWY_N AVD has Arrivals, Departures and Alert lists.
                and run scenario.
2    16:15:00                                     On AVD Arrival list entries for ARR1, ARR2 and ARR3
                                                  have appeared.
                                                  ARR1, ARR2 and ARR3 have appeared on PVD.
3    16:15:54                                     ARR1 lands on R27L.
                                                  AVD shows:
                                                  ARR2 – ARR1 information alert.
                                                  ARR3 – ARR1 information alert.
4    16:16:11                                     Note Tower radar updates every 1s while ATC radar
                                                  updates are every 6s.
                                                  ARR1-ARR2 alert becomes alarm as ATC track for
STATUS                                                                                               TITLE
Company Ref.                                                                          Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 154 of 197

                                                                               EUROCONTROL



                                                     ARR2 encroaches past long final separation distance
                                                     with ARR1 i.e. ARR2 nears runway quicker than ARR
                                                     travels along runway.
                                                     Note ARR1 is coloured alarm in the ARR3 information
                                                     alert as the ARR1 – ARR2 alarm alert takes
                                                     precedence.
5    16:16:30                                        ARR2 lands on R27L
                                                     AVD shows:
                                                     ARR1 – ARR2 alarm alert.
                                                     ARR3 – ARR1 information alert.
                                                     ARR3 – ARR2 information alert.
                                                     Note ARR1 and ARR2 are coloured alarm in the ARR3
                                                     information alerts as the ARR1 – ARR2 alarm alert
                                                     takes precedence.
6    16:17:39                                        ARR3 lands on R27L
7    16:17:49                                        ARR3 nears ARR2.
                                                     AVD shows:
                                                     ARR1 – ARR2 alarm alert.
                                                     ARR3 – ARR1 alarm alert.
                                                     ARR3 – ARR2 alarm alert.
                                                     Note ARR3 – ARR1 alert is really an information alert
                                                     but ARR3 and ARR1 are coloured alarm as they occur
                                                     in other alarm alerts.
8    16:17:56                                        Conflict between ARR2 and ARR1 no longer exists as
                                                     ARR2 has turned off runway, so ARR1 is no longer in
                                                     front of ARR2. As this conflict no longer exists the true
                                                     colour of the colour between ARR3 and ARR1 can be
                                                     seen on ARR1 as information.
9    16:18:00                                        ARR2 exits runway:
                                                     AVD shows:
                                                     ARR3 – ARR1 information alert.
10   16:18:05                                        ARR1 exits runway:
                                                     All alerts are removed.



     12.2.6 CT_TSN_OPEN_06 – Departure With Mobile On Runway
Scenario ID               CT_TSN_OPEN_06
SRD Reference             2005G170
Objective                 The scenario will verify that if an obstructing mobile is in front of a departure then
                          an information alert will be raised. This alert will be promoted to an alarm when
                          the departure starts to takeoff.
Dependencies              None
Resource File             <component test home>/tsn/tsn_2005G170.gsdk
                          <component test home>/tsn/tsn_2005G170Pilot.gsdk


ID   Time       Actions           Expectations
1    16:12:00   Launch            RWY_N AVD and LFPG PVD appear.
                tsn_2005G170      RWY_N AVD has Arrivals, Departures and Alert lists.
                and        run
                scenario.
STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                 Page : 155 of 197

                                                                            EUROCONTROL



2    16:12:07                   AMBULANCE appears on AVD
3    16:12:11                   DEP1 appears on AVD
4                               AMBULANCE moves on to R27L and stops.
                                DEP1 starts to pushback and taxi to R27L
5    16:14:11                   DEP2 appears on AVD destined for R27L
6                               DEP1 stops at runway hold point waiting for lineup clearance.
                                10s later DEP1 automatically given lineup clearance.
                                DEP1 enters exclusion area onto R27L further West than AMBULANCE.
                                DEP1 completes lineup and wairs for takeoff clearance.
                                10s later DEP1 automatically given take-off clearance.
                                DEP1 begins to accelerate to take-off.
                                No alert is raised, as AMBULANCE is not in front of departure DEP1.
7                               DEP2 stops at runway hold point waiting for lineup clearance.
                                10s later DEP2 automatically given lineup clearance.
                                DEP2 enters exclusion area with lineup clearance onto R27L further East
                                than AMBULANCE. Information alert raised.
                                DEP2 completes lineup and waits for takeoff clearance.
                                10s later DEP2 automatically given take-off clearance. Information alert
                                changes to alarm.
                                DEP2 begins to accelerate to take-off.
                                As DEP2 passes AMBULANCE conflict no longer exists and alert is
                                removed.



ID   Time       Actions                          Expectations
1    16:12:00   Launch                           RWY_N ground and air AVDs and LFPG PVD appear.
                tsn_2005G170Pilot                RWY_N AVDs have Arrivals, Departures and Alert lists.
                and run scenario.
2    16:12:07                                    AMBULANCE appears on AVD and starts to move to
                                                 R27L and stopping on runway at 16:12:48.
3    16:12:11                                    DEP1 appears on AVD
4               RWY_N (RWY) assumes DEP1         DEP1 coloured assumed on AVDs.
5               RWY_N (RWY) gives pushback
                clearance.
6               RWY_N(PILOT)         issues      DEP1 starts to pushback.
                pushback command.                On completion of pushback DEP1 prompts for taxi
                                                 clearance.
7               RWY_N (RWY) gives taxi
                clearance.
8               RWY_N(PILOT) issues taxi         DEP1 starts to taxi to start of runway hold point.
                command.                         On reaching point Lineup clreance prompt displayed.
9               RWY_N(PILOT) issues lineup       DEP1 lines up with ambulance behind DEP1.
                command.                         No alert raised.
10              RWY_N(PILOT) issues take off     DEP1 accelerates and takes off.
                command.                         No alert raised.
11              RWY_N (RWY) assumes DEP2         DEP2 coloured assumed on AVDs.
12              RWY_N (RWY) gives pushback
                clearance.
13              RWY_N(PILOT)          issues     DEP2 starts to pushback.
                pushback command.                On completion of pushback DEP2 prompts for taxi
                                                 clearance.
14              RWY_N (RWY) gives         taxi
                clearance.
15              RWY_N(PILOT) issues       taxi   DEP2 starts to taxi to runway hold point.
STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 156 of 197

                                                                              EUROCONTROL



                command.                           On reaching runway hold point Lineup cleareance prompt
                                                   displayed.
16              RWY_N(PILOT) issues lineup         DEP2 enters exclusion area with ambulance in front of
                command.                           DEP2.
                                                   Information alert raised.
17              RWY_N(PILOT) issues take off       DEP2 accelerates down runway.
                command.                           Information alert only becomes alarm as speed
                                                   recognised as a take-off speed (exceeds ).




     12.2.7 CT_TSN_OPEN_07 – Departure With Multiple Lineups
Scenario ID                CT_TSN_OPEN_07
SRD Reference              2005G180
Objective                  This scenario will demonstrate that the Tower system can be configured to allow
                           (or disallow) multiple departures lining up on the same runway. If not allowed than
                           an information alert is raised.
Dependencies               None
Resource File              <component test home>/tsn/tsn_2005G180.gsdk
                           <component test home>/tsn/tsn_2005G180_allowlineups.gsdk


ID   Time       Actions                              Expectations
1    16:12:00   Launch                               RWY_N ground and air AVDs and LFPG PVD appear.
                tsn_2005G180                         AVDs have Arrivals, Departures and Alert lists.
                and run scenario.
2    16:12:11                                        DEP1 and DEP2 appear on AVDs.
3               On TCWP assume DEP1 and              DEP1 and DEP2 become assumed coloured on AVDs .
                DEP2.
4               On TCWP give DEP1 pushback
                clearance.
5               On TPWP issue pushback               DEP1 starts to pushback.
                command.                             On reaching pushback point label shows prompt to taxi.
6               On TCWP give DEP1 taxi
                clearance.
7               On TPWP issue taxi command.          DEP1 starts to taxi to R27L.
8               On TCWP give DEP2 pushback
                clearance.
9               On TPWP issue pushback               DEP2 starts to pushback.
                command.                             On reaching pushback point label shows prompt to taxi.
10              On TCWP give DEP2 taxi
                clearance.
11              On TPWP issue taxi command.          DEP2 starts to taxi to R27L.
12                                                   DEP1 continues to taxi to R27L stopping at TP_456 for
                                                     lineup clearance.
                                                     DEP2 continues to taxi to R27L stopping at TP_1627 for
                                                     lineup clearance.
13              On TCWP give DEP2 clearance
                to lineup.

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 157 of 197

                                                                            EUROCONTROL



14              On TPWP issue lineup command.      DEP2 starts to lineup.
                                                   After lining up label shows prompt for takeoff.
15              On TCWP give DEP1 clearance
                to lineup.
16              On TPWP issue lineup command.      DEP1 starts to lineup.
                                                   After lining up label shows prompt for takeoff.
                                                   Information alert raised for DEP1 with DEP2
17              On TCWP give DEP1 clearance        Alert promoted to alarm.
                to takeoff.




ID   Time       Actions                      Expectations
1    16:12:00   Launch                       Following the same steps as for tsn_2005G180 the same
                tsn_2005G180_allowlineups    results are seen except that no information alarm is raised.
                and run scenario.




     12.3 Performance

     12.3.1 CT_TSN_PERFORMANCE_01 – Efficient intrusion detection algorithm
Scenario ID               CT_TSN_PERFORMANCE_01
SRD Reference             2005G190
Objective                 This scenario will demonstrate and verify that the intrusion detection algorithm
                          does not have a detrimental impact on the overall performance of the system.
Dependencies              None
Resource File             <component test home>/tsn/tsn_2005G190.gsdk


ID   Time       Actions                   Expectations
1    16:12:00   Launch                    RWY_N AVD and LFPG PVD appear.
                tsn_2005G190              RWY_N AVD has an Alert list.
                and run scenario     at
                normal speed.
                                          Arrivals raise alarm alerts as they approach R27L when there are
                                          other arrivals on the runway.
                                          Departures raise information alerts as they line up at a runway
                                          when other mobiles are ahead of them on the runway
                                          Departures raise alarm alerts as they take off at a runway when
                                          other mobiles are ahead of them on the runway
     16:36:00   Stop exercise.            Examine percentage time used by incursion algorithm as reported
                                          in message report log.
                                          Algorithm percentage time is negligible.
                                          Note some requests to perform the incursion algorithm were
                                          ignored as a previous request was still pending.




STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 158 of 197

                                                                                 EUROCONTROL



     12.3.2 CT_TSN_PERFORMANCE_02 – Intrusion detection during system loading
Scenario ID               CT_TSN_PERFORMANCE_02
SRD Reference             2005G200
Objective                 This scenario will demonstrate and verify that the intrusion detection algorithm will
                          operate efficiently in periods of obvious system overloading
Dependencies              None
Resource File             <component test home>/tsn/tsn_2005G190.gsdk


ID   Time       Actions                            Expectations
1    16:12:00   Launch                             RWY_N AVD and LFPG PVD appear.
                tsn_2005G190                       RWY_N AVD has an Alert list.
                and start scenario at normal
                speed then speed up.
                                                   Arrivals raise alarm alerts as they approach R27L when
                                                   there are other arrivals on the runway.
                                                   Departures raise information alerts as they line up at a
                                                   runway when other mobiles are ahead of them on the
                                                   runway
                                                   Departures raise alarm alerts as they take off at a runway
                                                   when other mobiles are ahead of them on the runway
     16:36:00   Stop exercise.                     Examine percentage time used by incursion algorithm as
                                                   reported in message report log.
                                                   Algorithm percentage time is negligible.
                                                   Note some requests to perform the incursion algorithm were
                                                   ignored as a previous request was still pending.




     12.4 Clearance Alerts

     12.4.1 CT_TSN_CLEARANCE_01 – Landing-Takeoff Alert
Scenario ID               CT_TSN_CLEARANCE_01
SRD Reference             2007APT120
Objective                 For a runway associated with an exclusion area the scenario will demonstrate
                          that:
                                    An alert will be raised if an arrival is given a landing clearance at the same
                                     time as a departure is given a takeoff clearance.
                                    The alert will be removed when the arrival landing clearance is removed
                                     (Go Around).
                                    The alert will be removed when the departure takeoff clearance is
                                     removed (Abort).
                                    The alert will be removed if the arrival lands and is given the Vacate order
                                     or Transfer order.
                                    The alert will be removed if the departure is given the Airborne order or
                                     the Transfer order.

STATUS                                                                                                      TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 159 of 197

                                                                             EUROCONTROL



Dependencies               None
Resource File              <component test home>/tsn/clearancealerts/lndTOFAlert.gsdk




ID    Time       Actions                              Expectations
1.    16:12:00   Launch and run scenario.             RWY_N and APR_N appears.
                                                      RWY_N AVD has Arrivals, Departures and Alert lists.
2.                                                    ARR1, DEP1, DEP2 and DEP3 appear.
                                                      ARR2 and ARR3 appear later in the scenario.
3.               Issue taxi, transfer and takeoff     TOF/LND alert shown in Alert window between ARR1
                 clearances to DEP1.                  and DEP1

                 Issue Assume and LND clearance       Arrival and Departure callsign displays are coloured to
                 to ARR1.                             show alert status in labels and lists.
4.               Issue taxi, transfer and assume      DEP2 and DEP1 start to taxi to runway.
                 clearances to DEP2.
5.               Issue Go clearance to ARR1.          The clearance alert is removed.
6.               Issue LND clearance to ARR1.         The clearance alert is displayed.
7.                                                    ARR1 lands
8.               Issue VAC clearance to ARR1.         The clearance alert is removed.
9.    16:16:30   Issue LND clearance to ARR2.         TOF/LND alert shown in Alert window between ARR2
                                                      and DEP1.

                                                      Arrival and Departure callsign displays are coloured to
                                                      show alert status in labels and lists.
10.                                                   DEP1 takes off.
11.                                                   The clearance alert between ARR2 and DEP1 is
                                                      removed.
12.                                                   ARR2 lands.
13.              Issue TOF clearance to DEP2.         A clearance alert is displayed between ARR2 and
                                                      DEP2.
14.              Transfer ARR2 /                      The clearance alert between ARR2 and DEP2 is
                 Issue VAC clearance to ARR2.         removed.

15.              Issue LND clearance to ARR3          A clearance alert is displayed between ARR3 and
                                                      DEP2
16.                                                   DEP2 takes off
17.                                                   The clearance alert between ARR3 and DEP2 is
                                                      removed.
18.              Issue taxi, transfer assume and      TOF/LND alert shown in Alert window between ARR3
                 TOF clearances to DEP3.              and DEP3.
19.              Issue ABORT clearance to DEP3.       The clearance alert is removed.



      12.4.2 CT_TSN_CLEARANCE_02 – Landing-Landing Alert
Scenario ID                CT_TSN_CLEARANCE_02
SRD Reference              2007APT110
Objective                  For a runway associated with an exclusion area the scenario will demonstrate

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 160 of 197

                                                                               EUROCONTROL



                           that:
                                  An alert will be raised if two arrivals are given landing clearance for the
                                   same runway at the same time.
                                  The alert will be removed when the arrival landing clearance is removed
                                   (Go Around) for either arrival.
                                  The alert will be removed if one of the arrivals land and is given the
                                   Vacate order.
Dependencies               None
Resource File              <component test home>/tsn/clearancealerts/lndLNDAlert.gsdk




ID    Time       Actions                           Expectations
1.    16:12:00   Launch and run scenario.          RWY_N and APR_N appears.
                                                   RWY_N AVD has Arrivals, Departures and Alert lists.
2.                                                 ARR1, ARR2, ARR3 appear
3.               Issue LND clearance to ARR1       LND/LND alert shown in Alert window between ARR1 and
                 and ARR2.                         ARR2

                                                   ARR1 and ARR2 callsigns are coloured to show alert
                                                   status in labels and lists.
4.               Issue Go clearance to ARR1.       The clearance alert is removed.
5.               Issue LND clearance to ARR1.      The clearance alert is displayed.
6.               Issue Go clearance to ARR2.       The clearance alert is removed.
7.               Issue LND clearance to ARR2.      The clearance alert is displayed.
8.                                                 ARR1 lands.
9.               Issue VAC clearance to ARR1.      The clearance alert is removed.
10.              Issue LND clearance to ARR3.      LND/LND alert shown in Alert window between ARR2 and
                                                   ARR3.

                                                   ARR2 and ARR3 callsigns are coloured to show alert
                                                   status in labels and lists.
11.                                                ARR2 lands.
12.              Issue VAC clearance to ARR2.      The clearance alert between ARR2 and ARR3 is removed.




      12.4.3 CT_TSN_CLEARANCE_03 – Lineup-Landing Alert
Scenario ID                CT_TSN_CLEARANCE_03
SRD Reference              2007APT130
Objective                  For a runway associated with an exclusion area the scenario will demonstrate
                           that:
                                  An alert will be raised if an arrival is given a landing clearance at the same
                                   time as a departure is given a lineup clearance.
                                  The alert will be removed when the arrival landing clearance is removed
                                   (Go Around).

STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                       Page : 161 of 197

                                                                                EUROCONTROL



                                   The alert will be removed when the departure lineup clearance is removed
                                    (Abort).
                                   The alert will be removed if the arrival lands passes the lineup point of the
                                    conflicting departure.
                                   The alert will be removed if the departure is given the Airborne order.
Dependencies                None
Resource File               <component test home>/tsn/clearancealerts/lupLNDAlert.gsdk




ID    Time       Actions                               Expectations
    16:12:00   Launch and run scenario.              RWY_N and APR_N appears.
                                                       RWY_N AVD has Arrivals, Departures and Alert lists.
                                                     ARR1, ARR2, ARR3, DEP1 and DEP2 appear.
               Issue taxi, transfer and lineup       LUP/LND alert shown in Alert window between ARR1
                 clearances to DEP1.                   and DEP1

                 Issue    Assume       and   LND       Arrival and Departure callsign displays are coloured to
                 clearance to ARR1.                    show alert status in labels and lists.
               Issue taxi, transfer and assume       DEP2 start to taxi to runway.
                 clearances to DEP2.
               Issue Go clearance to ARR1.           The clearance alert is removed.
               Issue LND clearance to ARR1.          The clearance alert is displayed.
                                                     ARR1 lands, the clearance alert is removed as ARR1
                                                       passes the Lineup point that DEP1 is heading for.
               Issue VAC clearance to ARR1.
               Using the route editor tool, select
                 a new runway entry point for
                 DEP1 that is further down the
                 runway than the original route.
              Issue    Assume       and      LND    LUP/LND alert shown in Alert window between ARR2
                 clearance to ARR2.                    and DEP1.

                                                       Arrival and Departure callsign displays are coloured to
                                                       show alert status in labels and lists.
                                                    ARR2 lands, the clearance alert is removed as ARR1
                                                       passes the Lineup point that DEP1 is heading for.
              Issue VAC clearance to ARR2.


              Issue    Assume    and        LND     LUP/LND alert shown in Alert window between ARR3
                 clearance to ARR3.                    and DEP1.

                                                       Arrival and Departure callsign displays are coloured to
                                                       show alert status in labels and lists.
              Issue TOF clearance to DEP1.          The clearance alert between ARR3 and DEP1 is
                                                       removed.
              Issue LUP clearance to DEP2.          LUP/LND alert shown in Alert window between ARR3
                                                       and DEP2.

                                                       Arrival and Departure callsign displays are coloured to

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 162 of 197

                                                                                 EUROCONTROL



                                                      show alert status in labels and lists.
              Rescind the LUP clearance for        The clearance alert is removed.
                 DEP2 using the -[LUP] option on
                 the callsign menu.


      12.4.4 CT_TSN_CLEARANCE_04 – Takeoff-Takeoff Alert
Scenario ID                CT_TSN_CLEARANCE_04
SRD Reference              2007APT140
Objective                  For a runway associated with an exclusion area the scenario will demonstrate
                           that:
                                  An alert will be raised if two departures are given takeoff clearance for the
                                   same runway at the same time.
                                  The alert will be removed when the takeoff clearance is removed (Abort)
                                   for either departure.
                                  The alert will be removed if one of the departures takes off and is given
                                   the Air order or Transfer order.
Dependencies               None
Resource File              <component test home>/tsn/clearances/tofTOFAlert.gsdk




ID    Time       Actions                                           Expectations
1.    16:12:00   Launch and run scenario.                          RWY_N appears.
                                                                   RWY_N AVD has Arrivals, Departures and
                                                                   Alert lists.
2.                                                                 DEP1, DEP2, DEP3 and DEP4 appear.
3.               Issue appropriate clearances to DEP1 and          TOF/TOF alert shown in Alert window
                 DEP2 such that both have TOF clearance            between DEP1 and DEP2

                                                                   DEP1 and DEP2 callsigns are coloured to
                                                                   show alert status in labels and lists.
4.                                                                 DEP1 takes off.
5.                                                                 The clearance alert is removed.
6.               Issue appropriate clearances to DEP3 such         TOF/TOF alert shown in Alert window
                 that it has TOF clearance.                        between DEP2 and DEP3.

                                                                   DEP2 and DEP3 callsigns are coloured to
                                                                   show alert status in labels and lists.
7.                                                                 DEP2 takes off.
8.                                                                 The clearance alert between DEP2 and
                                                                   DEP3 is removed.
9.               Issue appropriate clearances to DEP4 such         TOF/TOF alert shown in Alert window
                 that it has TOF clearance.                        between DEP3 and DEP4.

                                                                   DEP3 and DEP4 callsigns are coloured to
                                                                   show alert status in labels and lists.
10.              Issue Abort clearance to DEP3.                    The clearance alert is removed.
11.              Issue TOF clearance to DEP3.                      The clearance alert is displayed.

STATUS                                                                                                        TITLE
Company Ref.                                                                                   Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 163 of 197

                                                                                EUROCONTROL




      12.4.5 CT_TSN_CLEARANCE_05 – Takeoff-Lineup Alert
Scenario ID                CT_TSN_CLEARANCE_05
SRD Reference              2007APT150
Objective                  For a runway associated with an exclusion area the scenario will demonstrate
                           that:
                                  An alert will be raised if a departure is given a takeoff clearance at the
                                   same time as another departure is given a lineup clearance for a entry
                                   point ahead of the takeoff position on the runway.
                                  The alert will be removed when the lineup or takeoff clearance is removed
                                   (Abort).
                                  The alert will be removed if the departure is given the Airborne order or
                                   the Transfer order.
Dependencies               None
Resource File              <component test home>/tsn/clearances/tofLUPAlert.gsdk




ID    Time       Actions                                    Expectations
1.    16:12:00   Launch and run scenario.                   RWY_N appears.
                                                            RWY_N AVD has Arrivals, Departures and Alert
                                                            lists.
2.                                                          DEP1, DEP2 and DEP3 appear.
3.               Inspect the routes for DEP1, DEP2,         DEP1 is departing from the end of the runway, with
                 DEP3 and DEP4.                             DEP2 and DEP3 using entry points progressively
                                                            further down the runway.
                                                            DEP4 uses the same runway entry point as DEP3.
4.               Issue Assume, Taxi         and     TOF     TOF/LUP alert shown in Alert window between
                 clearances to DEP1.                        DEP1 and DEP2

                 Issue Assume, Taxi and LUP                 Departure callsigns are coloured to show alert
                 clearances to DEP2.                        status in labels and lists.
5.               Change the runway entry point for          The clearance alert is removed.
                 DEP1 to a point further down the
                 runway than DEP2 will enter.
6.               Change the runway entry point for          The clearance alert is displayed.
                 DEP1 back to the end of the runway.
7.                                                          DEP1 takes off.
8.                                                          The clearance alert between DEP1 and DEP2 is
                                                            removed.
9.               Issue Assume, Taxi         and      LUP    TOF/LUP alert shown in Alert window between
                 clearances to DEP3.                        DEP2 and DEP3.
                 Issue TOF clearance to DEP2.
                                                            Departure callsigns are coloured to show alert
                                                            status in labels and lists.
10.                                                         DEP2 takes off.
11.                                                         The clearance alert between DEP2 and DEP3 is
                                                            removed.

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 164 of 197

                                                                                EUROCONTROL



12.              Issue Assume, Taxi         and      LUP    TOF/LUP alert shown in Alert window between
                 clearances to DEP4.                        DEP3 and DEP4.

                 Issue TOF clearance to DEP3.               Departure callsigns are coloured to show alert
                                                            status in labels and lists.
13.              Issue Abort clearance to DEP3.             The clearance alert is removed.
14.              Issue TOF clearance to DEP3.               The clearance alert is displayed.



      12.4.6 CT_TSN_CLEARANCE_06 – EnterCross-Landing Alert
Scenario ID                CT_TSN_CLEARANCE_06
SRD Reference              2007APT160
Objective                  For a runway associated with an exclusion area the scenario will demonstrate
                           that:
                                  An alert will be raised if an arrival is given a landing clearance at the same
                                   time as a mobile is given either enter or cross clearance for that runway.
                                  The alert will be removed when the arrival landing clearance is removed
                                   (Go Around).
                                  The alert will be removed when the mobile cross or enter clearance is
                                   removed.
                                  The alert will be removed if the arrival lands and is given the Vacate
                                   order.
                                  The alert will be removed if the mobile is given the Vacate order.
Dependencies               None
Resource File              <component test home>/tsn/clearances/lndCrossEnterAlert.gsdk




ID    Time       Actions                           Expectations
    16:12:00   Launch and run scenario.          RWY_N and APR_N appears.
                                                   RWY_N AVD has Arrivals, Departures and Alert lists.
                                                 ARR1, ARR2, ARR3, DEP1 and VAN1 appear.
               Issue ENTER clearance to          ENTER/LND alert shown in Alert window between ARR1
                 DEP1.                             and DEP1

                 Issue Assume and LND              Arrival and Departure callsign displays are coloured to
                 clearance to ARR1.                show alert status in labels and lists.
               Issue Go clearance to ARR1.       The clearance alert is removed.
               Issue LND clearance to ARR1.      The clearance alert is displayed.
                                                 ARR1 lands.
               Issue VAC clearance to ARR1.      The clearance alert is removed.
               Issue Assume and LND              ENTER/LND alert shown in Alert window between ARR2
                 clearance to ARR2.                and DEP1.

                                                   Arrival and Departure callsign displays are coloured to
                                                   show alert status in labels and lists.
               Issue VAC clearance to DEP1.      The clearance alert between ARR2 and DEP1 is removed.
STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 165 of 197

                                                                                 EUROCONTROL



              Issue Assume and ENTER            ENTER/LND alert shown in alert window between ARR2
                 clearance to VAN1.                and VAN1.

                                                   Arrival and Departure callsign displays are coloured to
                                                   show alert status in labels and lists.
              Issue CROSS clearance to          Clearance alert changes to CROSS/LND in the alert
                 VAN1.                             window, still between ARR2 and VAN1.
                                                ARR2 lands.
              Issue VAC clearance to ARR2       The clearance alert between ARR2 and VAN1 is removed.
              Issue Assume and           LND    CROSS/LND alert shown in alert window between ARR3
                 clearance to ARR3.                and VAN1.

                                                   Arrival and Departure callsign displays are coloured to
                                                   show alert status in labels and lists.
              Issue VAC clearance to VAN1.      The clearance alert between ARR3 and VAN1 is removed.


      12.4.7 CT_TSN_CLEARANCE_07 – EnterCross-Takeoff Alert
Scenario ID                CT_TSN_CLEARANCE_07
SRD Reference              2007APT170
Objective                  For a runway associated with an exclusion area the scenario will demonstrate
                           that:
                                  An alert will be raised if a departure is given a takeoff clearance at the
                                   same time as a mobile is given either enter or cross clearance for that
                                   runway, and the enter or cross point is ahead of the takeoff point.
                                  The alert will be removed when the departure takeoff clearance is
                                   removed (Abort).
                                  The alert will be removed when the mobile cross or enter clearance is
                                   removed.
                                  The alert will be removed if the departure takes off and is given the
                                   Airborne order or the Transfer order.
                                  The alert will be removed if the mobile is given the Vacate order.
Dependencies               None
Resource File              <component test home>/tsn/clearances/tofCrossEnterAlert.gsdk




ID    Time       Actions                                              Expectations
1.    16:12:00   Launch and run scenario.                             RWY_N appears.
                                                                      RWY_N AVD has Arrivals, Departures and
                                                                      Alert lists.
2.                                                                    DEP1, DEP2, DEP3, DEP4 and DEP5
                                                                      appear.
3.               Issue Assume, Taxi and TOF clearances to             ENTER/TOF alert shown in Alert window
                 DEP1.                                                between DEP1 and DEP2.

                 Issue Assume, Taxi and ENTER clearance to            Arrival and Departure callsign displays are
                 DEP2.                                                coloured to show alert status in labels and
STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 166 of 197

                                                                               EUROCONTROL



                                                                    lists.
4.             Issue Assume and Taxi clearances to DEP4.
5.
6.             Issue CROSS clearance to DEP2.                       The    clearance     alert  changes to
                                                                    CROSS/TOF in the alert window.
7.             Issue VAC clearance to DEP2.                         The clearance alert is removed.
8.             Issue Assume, Taxi and Enter clearance to            ENTER/TOF alert shown in Alert window
               DEP3.                                                between DEP1 and DEP3.

                                                                    Arrival and Departure callsign displays are
                                                                    coloured to show alert status in labels and
                                                                    lists.
9.             Change the runway entry point for DEP1 to the        The clearance alert between DEP1 and
               entry point to the left of the point that DEP3       DEP3 is removed.
               crosses the runway.
10.            Change the runway entry point for DEP1 back          The clearance alert is displayed.
               to the end of the runway.
11.                                                                 DEP1 takes off.
12.                                                                 The clearance alert between DEP1 and
                                                                    DEP3 is removed.
13.            Issue TOF clearance to DEP4.                         ENTER/TOF alert shown in Alert window
                                                                    between DEP3 and DEP4.

                                                                    Arrival and Departure callsign displays are
                                                                    coloured to show alert status in labels and
                                                                    lists.
14.                                                                 DEP4 takes off
15.                                                                 The clearance alert between DEP3 and
                                                                    DEP4 is removed.
16.            Issue Assume, Taxi and TOF clearance to              ENTER/TOF alert shown in Alert window
               DEP5.                                                between DEP3 and DEP5.

                                                                    Arrival and Departure callsign displays are
                                                                    coloured to show alert status in labels and
                                                                    lists.
17.            Issue Abort clearance to DEP5.                       The clearance alert between DEP3 and
                                                                    DEP5 is removed.


      12.4.8 CT_TSN_CLEARANCE_08 – EnterCross Mobile Alert
Scenario ID              CT_TSN_CLEARANCE_08
SRD Reference            2007APT270
Objective                For a runway associated with an exclusion area the scenario will demonstrate
                         that:
                                An alert will be raised if a vehicle enters without enter/cross clearance.
                                An alert will be raised if an aircraft enters a runway it is not assigned to
                                 with cross/enter clearance.
                                An alert will be raised if an aircraft enters its assigned runway without a
                                 clearance.
                                The alert will be removed if the mobile is given clearance.

STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 167 of 197

                                                                                  EUROCONTROL



                                  The alert will be removed if the mobile leaves the exclusion area.
Dependencies               None
Resource File              <component test home>\tsn\clearancealerts\mobCrossEnterAlert.gsdk




ID   Time       Actions                                                    Expectations
1.   16:12:00   Launch and run scenario.                                   RWY_N appears.
                                                                           RWY_N AVD has Arrivals, Departures
                                                                           and Alert lists.
2.   16:12:05                                                              AMBULANCE appears.
3.   16:13:29                                                              CROSS/ENTER alert appears when
                                                                           AMBULANCE crosses protected area.
4.   16:14:10                                                              AMBULANCE leaves protected area,
                                                                           alert disappears.
5.              Select and ASSUME AMBULANCE and issue
                CROSS clearance before it enters the lower runway
                protected area.
6.   16:14:48                                                              No alert is generated as the
                                                                           AMBULANCE crosses the runway with
                                                                           clearance.
7.              Select AMBULANCE and issue ENTER clearance
                before it enters the lower runway protected area for
                the second time.
8.   16:15:57                                                              No alert is generated as the
                                                                           AMBULANCE crosses the runway with
                                                                           clearance.


     12.4.9 CT_TSN_CLEARANCE_09 – Runway Closed Alert
Scenario ID                CT_TSN_CLEARANCE_09
SRD Reference              2007APT180
Objective                  The scenario will demonstrate that:
                                  Alerts will be raised about all aircraft assigned to a runway when a runway
                                   is closed.
                                  An alert will be shown if an aircraft is assigned to a closed runway.
                                  Alerts will disappear if a runway is opened.
                                  The alert will disappear if a aircraft is an assigned to an open runway.
Dependencies               None
Resource File              <component test home>\tsn\clearancealerts\RunwayClosedAlert.gsdk


ID   Time       Actions                            Expectations
1.   16:12:00   Launch and run scenario.           RWY_N appears.
                                                   RWY_N AVD has Arrivals, Departures and Alert lists.
2.   16:12:05                                      DEP1 appears.
3.              Click on Runway R09L and           An INFORMATION alert appears listing R09L, DEP1 and

STATUS                                                                                                     TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 168 of 197

                                                                                EUROCONTROL



                select close.                     RUNWAY CLOSED
4.              Click on Runway R09L and          The alert disappears
                select open.
5.              Assume DEP1 and change            An INFORMATION alert appears listing RW27R, DEP1
                runway to R27R                    and RUNWAY CLOSED
6.              Change DEP1 runway to R27L        The alert disappears
7.              Click on runway R27L, and         2 alerts appear: DEP1, and ARR1 both listing R27L
                select close.
8.              Issue Taxi, and TOF to DEP1       Dep1 takes off. The alert for DEP1 disappears.
9.              Issue VAC to ARR1                 The alert for ARR1 disappears.


     12.4.10    CT_TSN_CLEARANCE_10 – Runway Too Short Alert
Scenario ID               CT_TSN_CLEARANCE_10
SRD Reference             2007APT190
Objective                 The scenario will demonstrate that:
                                 Alerts will be raised about all aircraft assigned to runways which are too
                                  short for take off.
                                 An aircraft‟s alert will disappear if it is reassigned to a long enough
                                  runway.
Dependencies              None
Resource File             <component test home>\tsn\clearancealerts\shortRunwayAlert.gsdk




ID   Time       Actions                                             Expectations
1.   16:12:00   Launch and run scenario.                            RWY_N appears.
                                                                    RWY_N AVD has Arrivals, Departures
                                                                    and Alert lists.
2.   16:12:05                                                       DEP1 appears
3.              ASSUME DEP1 and change the last point on            An INFORMATION alert appears listing
                the taxi route to TP_764 (middle of top runway).    RW09L, DEP1 and RWY TYPE
4.              Change DEP1‟s last taxipoint to TP_194 (far         The alert disappears
                right of the top runway).
5.              Change the last point on DEP1‟s taxi route to       An INFORMATION alert appears listing
                TP_764 (middle of top runway).                      RW09L, DEP1 and RWY TYPE
6.              Issue Assume, Taxi and TOF to DEP1
7.                                                                  Dep1 takes off. The alert disappears.


     12.4.11    CT_TSN_CLEARANCE_11 – Fast Taxi Alert
Scenario ID               CT_TSN_CLEARANCE_11
SRD Reference             2007APT250
Objective                 The scenario will demonstrate that:
                                 Alerts will be raised if an aircraft exceeds the taxi speed limit
                                 Alerts will disappear if the aircraft slows down to/below the taxi speed


STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                        Page : 169 of 197

                                                                                  EUROCONTROL



                                    limit.
                                   Alerts will not be raised for aircraft inside a runway exclusion area.
                                   Alerts will be raised for vehicles inside exclusion areas.
                                   The speed limit is set to a default limit (currently 36kts).
                                   The speed limit can be changed in resource files.
Dependencies                None
Resource File               <component test home>\tsn\clearancealerts\fastTaxiAlert.gsdk




ID    Time       Actions                                                 Expectations
1.    16:12:00   Launch and run scenario.                                RWY_N.
                 In the menu bar click LABEL, speed – min for            RWY_N AVD has Arrivals, Departures
                 vehicles, arrivals and departures.                      and Alert lists.
                 Position the windows so you can see both the            RWY_N/PILOT appears.
                 TCWP and TPWP at the same time.
2.    16:12:05                                                           DEP1 appears. ARR1 appears.
3.    16:12:35   ARR1 lands                                              No alert is displayed as ARR1
                                                                         decelerates from landing speed.
4.               In the TPWP, select the TAXI command and
                 change taxi speed to 40 kts for ARR1.
5.               ARR1 is travelling above 37 kts.                        No alert is displayed
6.               ARR1 leaves the fast exit taxiway.                      An INFORMATION alert appears listing
                                                                         a blank runway field, ARR1 and HIGH
                                                                         SPEED
7.               Change ARR1‟s speed to 0.                               The alert disappears when ARR1
                                                                         reaches 36 kts.
8.               In TPWP select TAXI and TOF, for DEP1. Then             DEP1 begins to taxi.
                 select the taxi speed menu and change the speed
                 to 40.
9.               DEP1 reaches a speed of 37 kts                          An INFORMATION alert appears listing
                                                                         a blank runway field, DEP1 and HIGH
                                                                         SPEED
10.              Change DEP1‟s speed to 0.                               The alert disappears when DEP1
                                                                         reaches 36 kts.
11.              In TPWP, change DEP1‟s taxi speed to 40 kts.
12.              DEP1 enters the runway exclusion area.                  The alert disappears.
13. 16:19:00     VEH1 appears.
14.              Change VEH1‟s taxi speed to 40 kts.
15.              VEH1‟s speed reaches 37 kts.                            The alert appears and stays there when
                                                                         VEH1 enters the runway exclusion
                                                                         area.
16.              In the TPWP change VEH1‟s speed to 0.                   The alert disappears when VEH1
                                                                         reaches 36 kts.
17.              Close the scenario
18.              Uncomment the line in the gsdk file:
                 TSN.MAX_TAXI_SPEED_KTS 10
19.              Re-run the scenario                                     The scenario works as before, but this
                                                                         time the alerts appear when at 11 kts
                                                                         and disappear at 10 kts.

STATUS                                                                                                       TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 170 of 197

                                                                                  EUROCONTROL



     12.4.12    CT_TSN_CLEARANCE_12 – Taxiway Sector Closed Alert
Scenario ID               CT_TSN_CLEARANCE_12
SRD Reference             2007APT340, 2007APT350
Objective                 The scenario will demonstrate that:
                                 An Information alert will be raised if a aircraft/vehicle has a route going
                                  through a closed taxiway sector.
                                 An alarm alert will be raised if an aircraft/vehicle is in a closed sector.
                                 The alert will disappear if the aircraft/vehicle leaves the closed sector
                                 Alerts will not be raised if a sector is open
Dependencies              None
Resource File             <component test home>\tsn\clearancealerts\closedSectorAlert.gsdk




ID   Time       Actions                                         Expectations
1.   05:50:00   Launch the scenario.                            RWY/RWY appears.
                                                                GND/PILOT appears.
2.              In the CWP open the map tool and select         The taxiway sector opens.
                view taxiway sectors.
                Click((R) on the sector labelled “PA”, and
                select open.
                Run the scenario.
3.   05:50:30                                                   DEP1 appears. DEP1‟s route goes through
                                                                sector PA.
4.              Give DEP1 ASSUME, PUSH and TAXI                 DEP1 begins to taxi.
                orders in the TCWP.
                Give DEP1 a TAXI order in the TPWP.
5.              Close the PA taxiway sector.                    An information alert appears listing DEP1 and
                                                                “TWY CLOSED”.
6.              DEP1 enters the sector PA                       The alert is changed to an alarm alert
7. 05:53:00     DEP1 leaves sector PA.                          The alert disappears.
8.              Open the sector PA before FIRE1 appears.
9. 05:53:30                                                     FIRE1 appears
10.             Close the PA sector                             An information alert is displayed
11.             Open the PA sector                              The information alert disappears.


     12.4.13    CT_TSN_CLEARANCE_13 – Takeoff Without Clearance Alert
Scenario ID               CT_TSN_CLEARANCE_13
SRD Reference
Objective                 The scenario will demonstrate that:
                                 An alarm alert will be raised if a aircraft starts to takeoff with TOF
                                  clearance
                                 The alert is not shown if the aircraft has TOF clearance
                                 The alert is not shown if the aircraft crosses the runway without TOF

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                  f7919ee3-d7fb-4de6-9213-
                                                         1719658e70fc.doc

                                                      Page : 171 of 197

                                                                                EUROCONTROL



                                     clearance.
Dependencies               None
Resource File              <component test home>\tsn\clearancealerts\TOFalert.gsdk




ID    Time       Actions                                  Expectations
1.    06:12:00   Launch the scenario.                     RWY/RWY appears – a TCWP
                                                          GND:PILOT appears – a TPWP.
2.    06:12:05                                            DEP1, DEP2 DEP3, DEP4 appear.
3.               In the TPWP give DEP1 TAXI and           DEP1 begins to taxi to the runway.
                 LUP commands.
                 In the TCWP give DEP1 ASSUME,
                 TAXI and LUP commands.
4.                                                        DEP1 enters runway and stops at the take off point.
                                                          No alert is shown.
5.               In TPWP      give    DEP1    a   TOF     DEP1 begins take off and moves past take off point.
                 command.                                 An alert is show in the TCWP displaying “R27R,
                                                          DEP1 and RWY CLR DEV”.
6.               In the TCWP give DEP2 ASSUME,            DEP2 begins to taxi to the runway.
                 TAXI and LUP orders.
                 In the TPWP give DEP2 TAXI and
                 LUP commands.
7.                                                        DEP2 enters the runway and stops at the take off
                                                          point. No alert is shown.
8.               In the TCWP give DEP2 a TOF              DEP2 takes off. No alert is shown.
                 order.
                 In the TPWP gibe DEP2 a TOF
                 command.
9.               Right click on DEP3‟s type
                 designator. Check that the taxi route
                 crosses runway R09L before taking
                 off from the same runway.
10.              In the TPWP give DEP3 ASSUME,            DEP3 begins its taxi route.
                 TAXI and TOF orders.
                 In the TCWP give DEP3 TAXI and
                 LUP commands.
11.              DEP3 crosses runway R09L.                No alert is shown.
12.              DEP3 crosses back over R09L              No alert is shown.
13.              DEP3 enters R09L and passes the          An alarm alert is shown listing RO9L, DEP3 and RWY
                 take off point.                          CLR DEV.
14.              Before DEP3 is airborne pause the        The alert disappears.
                 scenario.
                  In the TCWP give DEP3 TOF
                 clearance.
                 Play the scenario.
15.              In the TPWP give DEP4 TAXI, LUP          DEP4 takes off. No RWY CLR DEV alert is shown as
                 and TOF commands.                        a runway incursion alert should be shown if the
                                                          aircraft enters without LUP clearance.




STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 172 of 197

                                                                                EUROCONTROL



     12.4.14    CT_TSN_CLEARANCE_14 – Lineup/Lineup Alert
Scenario ID               CT_TSN_CLEARANCE_14
SRD Reference             2007APT155
Objective                 The scenario will demonstrate that:
                                 If 2 or more aircraft have clearance to line-up at the same point an alert
                                  will be displayed.
                                 If the aircraft are cleared to line-up at different points an alert won‟t be
                                  displayed.
                                 The alert will be removed if the line-up clearance is removed
                                 The alert will be removed if the aircraft is airborne.
Dependencies              None
Resource File             <component test home>\tsn\clearancealerts\lupLUPalert.gsdk


ID   Time       Actions                                 Expectations
1.   06:12:00   Launch the scenario.                    RWY/RWY appears – a TCWP
                                                        GND:PILOT appears – a TPWP
2.   16:12:05                                           DEP1, DEP2 and DEP3 appear.
3.              In the TCWP, Give DEP1 and DEP2         An alarm alert is shown listing DEP1, DEP2, runway
                ASSUME,       TAXI    and     LUP       R27L and LUP/LUP.
                commands.
4.              In the TCWP, change DEP1‟s last         The alert disappears.
                taxipoint to another taxipoint on
                runway R27L (e.g TP_1630).
5.              In the TCWP, change DEP1‟s last         The alert is displayed again.
                taxipoint back to the end of the
                runway.

6.              In the TPWP give DEP1 TAXI, LUP         DEP1 begins to taxi to runway.
                and TOF commands.
7.              DEP1 takes off.                         The alert disappears.
8.              In the TCWP give DEP3 ASSUME,           An alert appears listing DEP2 , DEP3, runway R27L
                TAXI, and LUP commands.                 and LUP/LUP
9.              In the TCWP give DEP2 a TOF             The alert disappears.
                command.


     12.4.15    CT_TSN_CLEARANCE_15 – Cleared Up To Alert
Scenario ID               CT_TSN_CLEARANCE_15
SRD Reference             2007APT210, 2007APT220
Objective                 The scenario will demonstrate that:
                                 An alert will be raised if a departure moves off its gate without
                                  taxi/pushback clearance.
                                 An alert will be raised if a depature moves past its pushback point without
                                  taxi clearance.
                                 An alert will be raised if a departure moves past its line-up point without

STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 173 of 197

                                                                                  EUROCONTROL



                                   LUP clearance.
                                  An alert will be raised if a departure moves along the runway without TOF
                                   clearance.
                                  An alert will be raised if an aircraft starts to taxi without taxi clearance.
Dependencies               None
Resource File              <component test home>\tsn\clearancealerts\clearedUpToAlert.gsdk




ID    Time       Actions                                Expectations
1.    16:12:00   Launch and run scenario.               RWY_N.
                 Position the windows so you can        RWY_N AVD has Arrivals, Departures and Alert lists.
                 see both the TCWP and TPWP at          RWY_N/PILOT appears.
                 the same time.
2.    16:12:05                                          DEP1 appears. ARR1 appears. DEP2 appears.
3.    16:12:35   ARR1 lands                             ARR1 stops at TP_219 waiting for TAXI clearance.
4.               In the TPWP, select the TAXI
                 command.
5.               ARR1 moves off the taxi point.         An INFORMATION alert appears listing a blank
                                                        runway field, ARR1 and NO TAXI CLR.
6.               In the TCWP left click on ARR1 and     The alert disappears.
                 select ASSUME, VACATE, TAXI.

7.               In the TPWP left click on DEP1 and     DEP1 begins to taxi.
                 select TAXI.
8.                                                      An INFORMATION alert appears listing a blank
                                                        runway field, DEP1 and NO TAXI CLR.
9.               In the TCWP click on DEP1 and          The alert disappears.
                 select TAXI.
10.              In the TCWP click on DEP1 and          After DEP1 has moved a some distance (140 metres),
                 select HOLD.                           an alert is displayed listing a blank runway field, DEP1
                                                        and NO TAXI CLR.
11.              In the TCWP click on DEP1 and          The alert disappears.
                 select TAXI.
12.              DEP1 stops at the line-up point        An alarm alert is shown listing runway RWR27L,
                 (TP_1187).                             DEP1 and NO LUP CLR.
                 In the TPWP click on DEP1 and
                 select LINEUP.
13.              In the TCWP click on DEP1 and          The alert disappears.
                 select LUP.
14.              In the TPWP click on DEP1 and          An alarm alert is shown listing runway RWR27L,
                 select TAKEOFF.                        DEP1 and NO TOF CLR.
15.              In the TCWP, click on DEP1 and         The alert disappears.
                 select TOF.
16.              In the TPWP, click on DEP2 and         An information alert appears listing a blank runway
                 select PUSHBACK                        field DEP2 and NO PUSH CLR.
17.              In the TCWP, click on DEP2 and         The alert disappears.
                 select PUSH.
18.                                                     DEP2 reaches the pushback point (TP_1214) and
                                                        stops.
19.              In the TPWP click on DEP2 and          An information alert is displayed listing a blank runway
                 select TAXI.                           field, DEP2 and NO TAXI CLR.
STATUS                                                                                                        TITLE
Company Ref.                                                                                  Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 174 of 197

                                                                                 EUROCONTROL



20.              In the TCWP, click on DEP2 and         The alert disappears.
                 select TAXI.
21.              In the TCWP, click on DEP2‟s           When DEP2 crosses runway R27L an alert appears
                 runway field and select a new          listing DEP2 and NO CROSS CLR.
                 runway of R09L.
                 In the TPWP, click on DEP2‟s
                 runway field and select a new
                 runway of R09L.
22.              In the TCWP, click on DEP2 and         The alert disappears.
                 select CROSS.                          DEP2 taxis and then stops at its new lineup point
                                                        (TP_34).
23.              In the TPWP, click on DEP2 and         An alarm alert is displayed listing runway R09L, DEP2
                 select LINEUP.                         and NO LUP CLR.
24.              In the TCWP click on DEP2, and         The alert disappears.
                 select CLUP.
25.              In the TPWP, click on DEP2 and         An alarm alert appears listing runway R09L, DEP2
                 select TAKEOFF.                        and NO TOF CLR.
26. 16:30:00     VEH1 appears.                          No alert appears as the vehicle moves around the
                                                        airport without taxi clearance from the controller.
27.              In the TCWP, click on VEH1 and         After the vehicle has moved a short distance an
                 select ASSUME and HOLD.                information alert is displayed listing a blank runway
                                                        field, VEH1, and NO TAXI CLR.
28.              In the TCWP, click on VEH1 and         The alert disappears.
                 select TAXI.


      12.4.16    CT_TSN_CLEARANCE_16 – LND Alert
Scenario ID                CT_TSN_CLEARANCE_16
SRD Reference              2007APT280
Objective                  The scenario will demonstrate that:
                                  An alert will be shown if an arrival is within short final distance and altitude
                                   of the exclusion area for its landing runway, without LND clearance.
                                  An alert will not be shown if a short final distance is not defined for the
                                   exclusion area.
                                  An alert will not be shown/will disappear if the arrival is given LND
                                   clearance.
Dependencies               None
Resource File              <component test home>\tsn\clearancealerts\LNDalert.gsdk


ID    Time       Actions                                 Expectations
1.    06:12:00   Launch the scenario.                    RWY:N/RWY appears – a TCWP.
2.               ARR1, ARR2, ARR3, and ARR4
                 appear.
3.    06:12:30   ARR1 comes with short final             An alert appears listing RWR27L, ARR1, and NO
                 distance of runway R27L (about half-    LND CLR.
                 way between LFPGE and runway
                 R27L).
4.               ARR1 lands.                             The alert disappears.
5.               Click on ARR2 and select ASSUME         No alert appears as ARR2 passes the short final

STATUS                                                                                                      TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 175 of 197

                                                                                EUROCONTROL



                and then LND.                           distance.
6.   16:13:30   ARR2 passes the short final distance    No alert is shown.
7.              Before ARR2 lands, click on ARR2        An alert appears listing RW27L, ARR2, and NO LND
                and select GO                           CLR.
8.   16:14:00   ARR2 lands.                             The alert disappears.
9.   16:15:00   ARR3 lands.                             No alert is shown as ARR3 comes into land because
                                                        the R27R exclusion area does not define a short final
                                                        boundary.
10. 16:15:30    ARR4 heads towards runway R09R          An alert is shown displaying RWR09R, ARR4, and
                                                        NO LND CLR.
                                                        The alert is shown a long distance from the runway
                                                        because R09R is defined to have a large boundary in
                                                        lndAlert_ea.dat.


     12.4.17    CT_TSN_CLEARANCE_17 – Stationary Alert
Scenario ID               CT_TSN_CLEARANCE_17
SRD Reference             2007APT230, 2007APT240, 2007APT260
Objective                     The scenario will demonstrate that:
                                      An alarm alert will be shown if an aircraft stays stationary for longer
                                       than parameter STATIONARY_ALERT_TOLERANCE seconds when
                                       it has takeoff or lineup clearance.
                                      An alarm alert will be shown if an aircraft stays stationary for longer
                                       than    parameter      STATIONARY_CROSS_ALERT_TOLERANCE
                                       seconds when it has cross or enter clearance.
                                      An alert will show if an aircraft stays stationary in the runway
                                       protection        area           for          longer         than
                                       STATIONARY_RWY_ALERT_TOLERANCE seconds.
                                      The alert will not be shown if the aircraft is given clearance to hold.
                                      The alert will not be shown if the aircraft is moving.
Dependencies              None
Resource File             <component test home>\tsn\clearancealerts\StationaryAlert.gsdk


ID   Time       Actions                                            Expectations
1.   06:12:00                                                      RWY:N/RWY appears – a TCWP.
                                                                   RWY:N/PILOT appears – a TPWP.
2.              In the eDep console click tools and then           Note the values of
                resources.                                         TSN.STATIONARY_ALERT_TOLERANCE
                                                                   (default 120 secs),
                                                                   TSN.CROSS_ALERT_TOLERANCE
                                                                   (default 120 secs),
                                                                   TSN.RWY_ALERT_TOLERANCE (default
                                                                   15 secs).
3.              Launch the scenario.
4.   06:12:05                                                      VEH1, DEP1 and ARR1 appear.
5.              In TPWP, click on VEH1 and select HOLD.            VEH1 stops.
6.              In TPWP click on ARR1 and select HOLD as           ARR1 stops on the runway inside the
                the flight leaves the runway.                      runway protection area.

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 176 of 197

                                                                              EUROCONTROL



7.                                                                After RWY_ALERT_TOLERANCE seconds
                                                                  an alert is displayed listing R27L, ARR1 and
                                                                  STATIONARY RPA.

                                                                  Note: if hold is issued before the aircraft
                                                                  reaches its exit point, then an error will be
                                                                  output to the console:
                                                                  ERROR - Hold command ignored as
                                                                  ARR1 is LANDING
8.              In the TCWP click on VEH1 and select
                ASSUME and CROSS.
9.              STATIONARY_CROSS_ALERT_TOLERANCE                  An alert is displayed listing runway R09R,
                seconds pass.                                     VEH1 and STATIONARY.
10.             In the TCWP, click on VEH1 and select             The alert disappears.
                ENTER.
11.             STATIONARY_CROSS_ALERT_TOLERANCE                  An alert is displayed listing runway R09R,
                seconds pass.                                     VEH1 and STATIONARY.
12.             In the TCWP click on VEH1 and select HOLD.        The alert disappears.
13.             In the TCWP click on DEP1 and select TAXI,
                and LUP.
14.             STATIONARY_ALERT_TOLERANCE seconds                An alarm alert is displayed listing runway
                pass.                                             R27L, DEP1 and STATIONARY.
15.             In the TPWP click on DEP1 and select TAXI.        The aircraft starts to move. The alert
                                                                  disappears.
16.             In the TPWP click on DEP1 and select HOLD
17.             STATIONARY_ALERT_TOLERANCE seconds                An alarm alert is displayed listing runway
                pass.                                             R27L, DEP1 and STATIONARY.
18.             In the TCWP click on DEP1 and select HOLD.        The alarm alert disappears.
19.             In the TCWP, click on DEP1 and select TAXI.
20.             STATIONARY_ALERT_TOLERANCE seconds                An alarm alert is displayed listing runway
                pass.                                             R27L, DEP1 and STATIONARY.
21.             In the TCWP, click on DEP1 and select TOF.        The alarm alert disappears.
22.             STATIONARY_ALERT_TOLERANCE seconds                An alarm alert is displayed listing runway
                pass.                                             R27L, DEP1 and STATIONARY.




      12.5 Deviation Alerts

      12.5.1 CT_TSN_DEVIATION_01 – Route Deviation Alert
Scenario ID               CT_TSN_DEVIATION_01
SRD Reference             2007APT200
Objective                 This scenario will demonstrate the detection of aircraft and vehicles deviating from
                          their cleared route as they travel around the airport.
Dependencies              None
Resource File             <component test home>\tsn\ tsnRouteDeviation.gsdk


ID    Time      Actions                                       Expectations
 16:12:00    Launch and run scenario.                      RWY_N, RWY_N(Pilot), and PVD displays
                                                              appear.

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                     Page : 177 of 197

                                                                                EUROCONTROL



                                                                RWY_N AVD has Arrivals, Departures and
                                                                Alert lists.
 16:12:17                                                    DEP1 appears.
            Pause the scenario.                              The planned route is displayed for DEP1
               Hover the mouse over the aircraft symbol,
               on both displays.
            On the RWY_N display:
               ASSUME DEP1.
               Click(L) on the DEP1 symbol and use the
               route editor utility to set a new route that
               extends only a short way along its original
               route.
               Hover the mouse over the aircraft symbol         The planned route on the RWY_N display
               on both displays.                                extends only a short way, the planned route on
                                                                the RWY_N(Pilot) position extends all the way
                                                                to the runway.
            Restart the scenario.                            DEP1 proceeds towards the runway.
               Issue Taxi clearance to DEP1 on the              As it goes beyond the end of the planned route
               RWY_N display and then on the                    that was set on the RWY_N display an
               RWY_N(Pilot) display.                            information alert is displayed.
               Observe the RWY_N display.
            On RWY_N, left click on the DEP1 symbol          The route deviation alert is removed.
               and reset the route to reach the runway.
            On the RWY_N(Pilot) display, click (L) on        As DEP1 deviates from the cleared route an
               the DEP1 symbol and change the route so          information alert is displayed on the RWY_N
               that it is differs from the cleared route set    display.
               on RWY_N.
                                                                As DEP1 continues towards the runway and
               Observe the RWY_N display.                       returns to the cleared route the alert is
                                                                removed.
 16:19:00                                                    VEH1 appears and starts moving.
            On the RWY_N(Pilot) display, hover the           Note that there is no alert displayed as the
               mouse over the vehicle symbol and                vehicle deviates from the cleared route.
               observe the planned route.
                                                                (Alert not shown as the vehicle is uncontrolled).
               Amend the route so that it reaches the
               same destination but via a different route.
               Observe the RWY_N display.
            On the RWY_N display, ASSUME VEH1.               An information alert appears on the RWY_N
                                                                display.
            Click the callsign button and select REL to      The information alert is removed.
               release control of VEH1
            On the RWY_N display, ASSUME VEH1                The information alert is re-displayed.
               again.                                           As VEH1 progresses and returns to the cleared
                                                                route, the alert is removed.




STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                         f7919ee3-d7fb-4de6-9213-
                                                1719658e70fc.doc

                                             Page : 178 of 197

                                                                      EUROCONTROL



     13 TOWER ATC INTERACTION

     13.1 CT_TAI_GORD_01 – Go-Around
Scenario ID         CT_TAI_GORD_01
SRD Reference
Objective           Demonstrates that a PM arrival can be taken off-plan by the PWP, vectored back
                    around to the runway approach, resume their approach and land correctly.
Dependencies        None
Resource File       <component test home>/tai/goAround.gsdk


ID    Time       Actions                              Expectations
1.    16:12:00   Launch scenario.                     One Pilot AVD (RWY_N) and one PVD (FS) and
                                                      one PWP (PWP_FS) are displayed.
2.                                                    ARR1 track seen in all displays. PWP_FS has
                                                      control of ARR1.
3.    16:27:30   Give ARR1 heading order to 360       ARR1 doesn‟t land, continuing on the assigned
                 in PWP_FS, taking ARR1 off-plan.     heading.
4.    16:28:00   Give ARR1 heading order to 90 in
                 PWP_FS.
5.    16:29:30   Give ARR1 direct to R27R in
                 PWP_FS.
6.    16:31:50                                        ARR1 lands and is removed from the FS and
      (approx)                                        PWP_FS displays. ARR1 is controlled by
                                                      RWY_N.



     13.2 CT_TAI_GORD_02 – Go-Around
Scenario ID         CT_TAI_GORD_02
SRD Reference
Objective           Demonstrates that a PM arrival can be taken off-plan by the PWP, vectored back
                    around to the runway approach, resume their approach and capture an ILS to land
                    on a runway.
                    Demonstrate that an arrival landing on an incorrect runway is correctly handled by
                    the Tower system.
Dependencies        None
Resource File       <component test home>/tai/goAround.gsdk


ID    Time       Actions                              Expectations
1.    16:12:00   Launch scenario.                     One Pilot AVD (RWY_N) and one PVD (FS) and
                                                      one PWP (PWP_FS) are displayed.
2.                                                    ARR1 track seen in all displays. PWP_FS has

STATUS                                                                                           TITLE
Company Ref.                                                                      Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                 Page : 179 of 197

                                                                              EUROCONTROL



                                                           control of ARR1.
3.    16:27:30        Give ARR1 heading order to 360       ARR1 doesn‟t land, continuing on the assigned
                      in PWP_FS, taking ARR1 off-plan.     heading.
4.                    Give ARR1     FL3000    order   in
                      PWP_FS.
5.    16:28:00        Give ARR1 heading order to 90 in
                      PWP_FS.
6.    16:33:00        Give ARR1 heading order to 270
                      in PWP_FS.
7.                    Give ARR1 intercept ILS order in
                      PWP_FS.
8.    16:39:06                                             ARR1 lands and is removed from the FS and
                                                           PWP_FS displays. ARR1 is controlled by
                                                           RWY_N.
                                                           ARR1 has landed on runway R27R instead of
                                                           R27L. A new route has been calculated from
                                                           R27R to the stand for ARR1.




     14 TAAM TRAFFIC CONVERTER TESTS

     14.1 EEC Supplied TAAM Test Data

     14.1.1 CT_TAAM_TRAFFIC_01 – Convert Traffic for Standalone Mode
Scenario ID              CT_TAAM_TRAFFIC_01
SRD Reference            2005G20
Objective                This test will demonstrate that TAAM Traffic data in CSV (comma separated
                         variables) text format can be converted and expanded into eDEP flight plans and
                         airport plans.
                         The traffic converter will assume that the Tower System will run in Standalone
                         mode and use the TAAM activation time as the actual off block time (AOBT) for
                         departures and actual time of arrival (ATA) for arrivals.
                         To verify the conversion the scenario will be launched and started noting the off
                         block times and arrival times of flights.
Dependencies             TAAM test data supplied in Excel Format. This test depends that the Excel data
                         has been saved in comma separated variable (csv) text form.
                         As files are auto generated for use within the ATC/Tower systems this test has
                         been written such that the tester must run the scenario from the development
                         environment rather than from a jar file.
Resource File            <component test home>/converter/traffic/taam/runStandalone.gsdk




ID   Time   Actions                                                 Expectations

STATUS                                                                                                TITLE
Company Ref.                                                                           Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 180 of 197

                                                                             EUROCONTROL



1           Launch TAAM Traffic Converter                             TAAM Traffic Converter appears with
                                                                      default airport LFPG and default mode
                                                                      STANDALONE.
2           Browse for TAAM data to load and select
            TAAM_TRAFFIC_SAMPLE.csv
3           Browse for location to save airport plans. Select         As in STANDALONE mode specifying
            converter,        traffic,   generated   and  enter       all three files enables the calculate
            traffic_aiportplans.dat.                                  button
            Browse for location to save flight plans. Select
            converter,        traffic,   generated   and  enter
            traffic_flightplans.dat.
            Browse for location to save airspace routes. Select
            converter,        traffic,   generated   and  enter
            traffic_routes.dat.
            Note if the test has previously been run then these
            three files will already exist.
            Click calculate button.                                   See Below
Converter completes reporting illegal fix name 1BRY.



ID   Time       Actions                                         Expectations
1               Start eDEP Tower Launcher.                      Tower RWY_N AVD appears
                Select
                converter/traffic/taam/runStandalone.gsdk
2               Start scenario
3    01:09:40                                                   Ten arrivals land and ten departures appear.
                                                                No activation times have changed.
     to
                                                                Activation times are as stated in original
     01:12:00                                                   TAAM traffic data. See below:
TAAM Traffic activation times:
    DLH4064: 01,09:40
    DLH4171: 01,10:40
    AFR1435: 01,09:45
    AFR2008: 01,10:45
    AFR5145: 01,09:50
    AFR5144: 01,10:50
    IBE3444: 01,09:55
    IBE3445: 01,10:55
    BAW306: 01,10:00
    BAW307: 01,11:00
    AFR318Y: 01,10:05
    AFR1318: 01,11:05
    AFR1205: 01,10:10
    AFR1648: 01,11:10
    SAS1579: 01,10:15
    SAS1580: 01,11:15
    AFR1777: 01,10:20
    AFR2076: 01,11:20
    RAM5568: 01,10:25
    RAM5569: 01,11:25




STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 181 of 197

                                                                            EUROCONTROL



     14.1.2 CT_TAAM_TRAFFIC_02 – Convert Traffic for Truncate Mode
Scenario ID              CT_TAAM_TRAFFIC_02
SRD Reference            2005G20
Objective                This test will demonstrate that TAAM Traffic data in CSV (comma separated
                         variables) text format can be converted and expanded into eDEP flight plans and
                         airport plans.
                         The traffic converter will assume that the Tower will run in Connected mode and
                         Truncate the ATC flight plans to fly only the associated STARs. The converter will
                         use the TAAM activation time as the actual off block time (AOBT) for departures
                         and actual time of arrival (ATA) for arrivals and determine new activation times for
                         arrivals such that the flights fly the appropriate STARs and land at the TAAM ATA.
                         To verify the conversion the scenario will be launched and started noting the
                         position and time of arrivals in the ATC system and the off block times and arrival
                         times of flights.
Dependencies             TAAM test data supplied in Excel Format. This test depends that the Excel data
                         has been saved in comma separated variable (csv) text form.
                         As files are auto generated for use within the ATC/Tower systems this test has
                         been written such that the tester must run the scenario from the development
                         environment rather than from a jar file.
Resource File            <component test home>/converter/traffic/taam/runTruncated.gsdk


ID   Time   Actions                                                  Expectations
1           Launch TAAM Traffic Converter                            TAAM Traffic Converter appears with
                                                                     default airport LFPG and default mode
                                                                     STANDALONE.
2           Select mode TRUNCATE                                     Mode now shows TRUNCATE
3           Browse for TAAM data to load and select
            TAAM_TRAFFIC_SAMPLE.csv
4           Browse for location to save airport plans. Select As in TRUNCATE mode only specifying
            converter,        traffic,   generated  and      enter all four files enables the calculate
            traffic_aiportplans.dat.                                  button
            Browse for location to save flight plans. Select
            converter,        traffic,   generated  and      enter
            traffic_flightplans.dat.
            Browse for location to save airspace routes. Select
            converter,        traffic,   generated  and      enter
            traffic_routes.dat.
            Note if the test has previously been run then these
            three files will already exist.
            Browse for location of resources. Select converter,
            traffic, taam and sampleResources.gsdk
            Click calculate button.                                   See Below
Converter completes reporting illegal fix name 1BRY and with the following reported activation times:
      AFR1777:   new   activation    time   is   01:07:48,    time   to   touchdown    is   00:02:31
      AFR1435:   new   activation    time   is   01:07:09,    time   to   touchdown    is   00:02:35
      AFR5145:   new   activation    time   is   01:07:18,    time   to   touchdown    is   00:02:31
      IBE3444:   new   activation    time   is   01:07:42,    time   to   touchdown    is   00:02:12
      AFR318Y:   new   activation    time   is   01:07:52,    time   to   touchdown    is   00:02:12
      SAS1579:   new   activation    time   is   01:07:39,    time   to   touchdown    is   00:02:35

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 182 of 197

                                                                             EUROCONTROL



      DLH4064: new activation time is 01:07:27, time to touchdown is 00:02:12
      BAW306: new activation time is 01:07:24, time to touchdown is 00:02:35
      RAM5568: new activation time is 01:08:12, time to touchdown is 00:02:12
      AFR1205: new activation time is 01:07:57, time to touchdown is 00:02:12



ID   Time       Actions                                           Expectations
1               Start eDEP Tower Launcher.                        Tower RWY_N AVD appears.
                Select                                            ATC LFPG PVD appears.
                converter/traffic/taam/runTruncated.gsdk
2               Start scenario
3    01:07:09                                                     Arrivals appear on PVD starting at CGZ
     to
     01:08:12
4    01:09:40                                                     Ten arrivals land and ten departures
     to                                                           appear.
     01:12:00




     14.1.3 CT_TAAM_TRAFFIC_03 – Convert Traffic for Connected Mode
Scenario ID               CT_TAAM_TRAFFIC_03
SRD Reference             2005G20
Objective                 This test will demonstrate that TAAM Traffic data in CSV (comma separated
                          variables) text format can be converted and expanded into eDEP flight plans and
                          airport plans.
                          The traffic converter will assume that the Tower will run in Connected mode and
                          use the complete defined route associated to the flight. The converter will use the
                          TAAM activation time as the actual off block time (AOBT) for departures and
                          actual time of arrival (ATA) for arrivals and determine new activation times for
                          arrivals such that the flights fly the appropriate routes and land at the TAAM ATA.
                          To verify the conversion the scenario will be launched and started noting the
                          position and time of arrivals in the ATC system and the off block times and arrival
                          times of flights.
                          Note the geographic location of the fixes referenced within the TAAM routes are
                          not known so substitute routes of the same names but with known fixes are used.
Dependencies              TAAM test data supplied in Excel Format. This test depends that the Excel data
                          has been saved in comma separated variable (csv) text form.
                          As files are auto generated for use within the ATC/Tower systems this test has
                          been written such that the tester must run the scenario from the development
                          environment rather than from a jar file.
Resource File             <component test home>/converter/traffic/taam/runConnected.gsdk


ID   Time   Actions                                                   Expectations
1           Launch TAAM Traffic Converter                             TAAM Traffic Converter appears with
                                                                      default airport LFPG and default mode
                                                                      STANDALONE.

STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                 Page : 183 of 197

                                                                            EUROCONTROL



2           Select mode CONNECTED                                     Mode now shows CONNECTED
3           Browse for TAAM data to load and select
            TAAM_TRAFFIC_SAMPLE.csv
4           Browse for location to save airport plans. Select As in CONNECTED mode only
            converter,        traffic,   generated  and      enter specifying all four files enables the
            traffic_aiportplans.dat.                                  calculate button
            Browse for location to save flight plans. Select
            converter,        traffic,   generated  and      enter
            traffic_flightplans.dat.
            Browse for location to save airspace routes. Select
            converter,        traffic,   generated  and      enter
            traffic_routes.dat.
            Note if the test has previously been run then these
            three files will already exist.
            Browse for location of resources. Select converter,
            traffic, taam and sampleResources.gsdk
5           Click calculate button.                                   See Below
Converter completes reporting illegal fix name 1BRY and with the following reported activation times:
      AFR1777: new activation time is 00:54:29, time to touchdown is 00:15:50
      AFR1435: new activation time is 00:54:31, time to touchdown is 00:15:13
      AFR5145: new activation time is 00:53:56, time to touchdown is 00:15:53
      IBE3444: new activation time is 00:54:55, time to touchdown is 00:14:59
      AFR318Y: new activation time is 00:55:03, time to touchdown is 00:15:01
      SAS1579: new activation time is 00:54:53, time to touchdown is 00:15:21
      DLH4064: new activation time is 00:54:40, time to touchdown is 00:14:59
      BAW306: new activation time is 00:54:39, time to touchdown is 00:15:20
      RAM5568: new activation time is 00:55:34, time to touchdown is 00:14:50
      AFR1205: new activation time is 00:55:10, time to touchdown is 00:14:59




I   Time        Actions                                     Expectations
D
1               Examine                                     Note the routes to be used are not those
                converter/traffic/taam/sampleResources.g    derived by the Converter but substitutes of the
                sdk                                         same names.
                                                            The file used by ASP.SCEANRIO is
                                                            converter/traffic/airspace/traffic_stub_routes.da
                                                            t
2               Start eDEP Tower Launcher.                  Tower RWY_N AVD appears.
                Select                                      ATC LFPG PVD appears.
                converter/traffic/taam/runConnected.gsdk
3               Start scenario
4   00:53:56                                                Arrivals appear on PVD starting at REM
    to
    00:55:34
5   01:09:40                                                Ten arrivals land and ten departures appear.
    to
    01:12:00




STATUS                                                                                                 TITLE
Company Ref.                                                                            Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 184 of 197

                                                                                 EUROCONTROL



     14.2 Graffica Test Data

     14.2.1 CT_TAAM_TRAFFIC_04 – Convert Traffic Using Derived Routes
Scenario ID               CT_TAAM_TRAFFIC_04
SRD Reference             2005G20
Objective                 This test will demonstrate that Traffic data in CSV (comma separated variables)
                          text format can be converted and expanded into eDEP flight plans and airport
                          plans.
                          The traffic converter will assume that the Tower will run in Connected mode and
                          use the complete defined route associated to the flight. Example routes defined in
                          the sample file will contain routes with 0, 1, 2 and 3 waypoints. When 0 waypoints
                          are defined no route will be generated but a route based on airport names will be
                          assumed to have been predefined by the user.
                          The converter will use the TAAM activation time as the actual off block time
                          (AOBT) for departures and actual time of arrival (ATA) for arrivals and determine
                          new activation times for arrivals such that the flights fly the appropriate routes and
                          land at the TAAM ATA.
                          To verify the conversion the scenario will be launched and started using the
                          derived routes and noting the position and time of arrivals in the ATC system and
                          the off block times and arrival times of flights.
Dependencies              Test data supplied in Excel Format. This test depends that the Excel data has
                          been saved in comma separated variable (csv) text form.
                          As files are auto generated for use within the ATC/Tower systems this test has
                          been written such that the tester must run the scenario from the development
                          environment rather than from a jar file.
Resource File             <component test home>/converter/traffic/tower/runConnected.gsdk


ID   Time   Actions                                                        Expectations
1           Launch TAAM Traffic Converter                                  TAAM Traffic Converter appears with
                                                                           default airport LFPG and default mode
                                                                           STANDALONE.
2           Select mode CONNECTED                                          Mode now shows CONNECTED
3           Browse for TAAM data to load and select
            TOWER_TRAFFIC_SAMPLE.csv
4           Browse for location to save airport plans. Select              As in CONNECTED mode only
            converter,        traffic,   generated    and      enter       specifying all four files enables the
            traffic_aiportplans.dat.                                       calculate button
            Browse for location to save flight plans. Select
            converter,        traffic,   generated    and      enter
            traffic_flightplans.dat.
            Browse for location to save airspace routes. Select
            converter,        traffic,   generated    and      enter
            traffic_routes.dat.
            Note if the test has previously been run then these
            three files will already exist.
            Browse for location of resources. Select converter,
            traffic, tower and sampleResources.gsdk
            Click calculate button.                                        See Below
Converter completes with the following reported activation times:
STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 185 of 197

                                                                                 EUROCONTROL



      ARR2: new activation time is 00:46:42, time to touchdown is 00:23:02
      ARR1: new activation time is 00:45:57, time to touchdown is 00:23:02



I    Time       Actions                                        Expectations
D
1               Examine                                        Note the routes to be used are those derived
                converter/traffic/tower/sampleResources.g      by the converter and the predefined user route.
                sdk
                                                               The files used by          ASP.SCEANRIO        are
                                                               converter/traffic/…
                                                               generated/traffic_routes.dat and
                                                               airspace/traffic_lfpg_lfpo_route.dat
2               Start eDEP Tower Launcher.                     Tower RWY_N AVD appears.
                Select                                         ATC LFPG PVD appears.
                converter/traffic/tower/runConnected.gsdk
3               Start scenario
4    00:45:57                                                  Arrivals appear on PVD starting at SEB
     to
     00:46:42
5    01:09:00                                                  Two arrivals land and three departures appear.
     to
     01:11:45




     14.2.2 CT_TAAM_TRAFFIC_05 – Convert Traffic Using Derived Routes
Scenario ID               CT_TAAM_TRAFFIC_05
SRD Reference             2005G20
Objective                 This test will demonstrate that Traffic data in CSV (comma separated variables)
                          text format can be converted and expanded into eDEP flight plans and airport
                          plans.
                          The traffic converter will report modified activation times that are earlier than the
                          scenario start time.
Dependencies              Test data supplied in Excel Format. This test depends that the Excel data has
                          been saved in comma separated variable (csv) text form.
                          As files are auto generated for use within the ATC/Tower systems this test has
                          been written such that the tester must run the scenario from the development
                          environment rather than from a jar file.
Resource File             <component test home>/converter/traffic/tower/runLateConnected.gsdk


ID   Time   Actions                                                        Expectations
1           Launch TAAM Traffic Converter                                  TAAM Traffic Converter appears with
                                                                           default airport LFPG and default mode
                                                                           STANDALONE.
2           Select mode CONNECTED                                          Mode now shows CONNECTED
3           Browse for TAAM data           to   load    and    select

STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 186 of 197

                                                                                 EUROCONTROL



            TOWER_TRAFFIC_SAMPLE.csv
4           Browse for location to save airport plans. Select              As in CONNECTED mode only
            converter,        traffic,   generated    and      enter       specifying all four files enables the
            traffic_aiportplans.dat.                                       calculate button
            Browse for location to save flight plans. Select
            converter,        traffic,   generated    and      enter
            traffic_flightplans.dat.
            Browse for location to save airspace routes. Select
            converter,        traffic,   generated    and      enter
            traffic_routes.dat.
            Note if the test has previously been run then these
            three files will already exist.
            Browse for location of resources. Select converter,
            traffic, tower and sampleBResources.gsdk
            Click calculate button.                                        See Below
Converter completes with the following reported activation times:
      WARNING - ARR2: new activation time 00:46:42 is before scenario start time 00:55:00!!!
      ARR2: new activation time is 00:46:42, time to touchdown is 00:23:02
      WARNING - ARR1: new activation time 00:45:57 is before scenario start time 00:55:00!!!
      ARR1: new activation time is 00:45:57, time to touchdown is 00:23:02



I   Time         Actions                                       Expectations
D
1                Start eDEP Tower Launcher.                    Tower RWY_N AVD appears.
                 Select                                        ATC LFPG PVD appears.
                 converter/traffic/tower/runLateConnected.
                 gsdk
2                Start scenario
3   00:55:00                                                   Arrivals appear on PVD starting at REM
4   01:09:00                                                   Two arrivals land and threedepartures appear.
    to
    01:11:45




    15 DISTRIBUTED SYSTEM TESTS

    15.1 Distributed

    15.1.1 CT_DIS_01 – Distributed Test
Scenario ID                CT_DIS_01
SRD Reference
Objective                  Demonstrate that the TWR system can be run distributed over a network of
                           computers.
Dependencies               None
Resource File              <component test home>/distributed/server.gsdk


STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                 f7919ee3-d7fb-4de6-9213-
                                                        1719658e70fc.doc

                                                      Page : 187 of 197

                                                                              EUROCONTROL



                           <component test home>/distributed/client.gsdk




ID   Time       Actions                               Expectations
1               Launch “server”                       RWY_N AVD appears with a view of the airport.
                                                      LFPG PVD window appears with a view of the “local”
                                                      surrounding airspace.
                                                      A console window appears.
2               On a different computer, check        The value of the resource is the name of the computer
                value of GSDK.MIDDLEWARE.             which “server” was launched on.
                DISCOVERY_HOST
3               Launch “client” on the second         CARGO_N AVD appears with a view of the airport.
                computer
                                                      FS PVD window appears with a view of the surrounding
                                                      airspace.
                                                      A console window appears.
4               Click „play‟ on       the    client   The timer on both computers start.
                computer‟s console
5               Click „pause‟ on      the   server    The timer on both computers pause.
                computer‟s console
6               Click „play‟ on the         server    The timer on both computers start
                computer‟s console
7    16:12:20                                         “DEPARTURE” appears on AVDs.
8               On “CARGO_N” display, assume          “DEPARTURE” becomes assumed by “CARGO_N”,
                aircraft and give it taxi clearance   starts taxiing and moves into the “APRON” list.
                                                      (Movement and ArrDep changes on all consoles,
                                                      assumed status on CARGO_N and RWY_N)
9               On “CARGO_N” display, transfer        “DEPARTURE” becomes assumed by “RWY_N”.
                aircraft. On “RWY_N” display,
                assume it.
10                                                    “DEPARTURE” reaches line-up point, stops.
11              On “RWY_N” display, give a            “DEPARTURE” lines up and takes off. Disappears from
                Line-up clearance, and a Take-        all AVD consoles.
                off clearance
12                                                    “DEPARTURE” appears on PVD displays.




STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 188 of 197

                                                                          EUROCONTROL



     16 BACKWARDS COMPATIBILTY

     16.1 Supporting ATC Components

     16.1.1 CT_INT_BC_01 – Tower Provides Backwards Compatibility for ATC
Scenario ID                CT_INT_BC_01
SRD Reference              30, 170, 200, 250
Objective                  To Demonstrate that the Tower system can interpret and provide airspace data
                           and flight plan information.
                           In particular TIFPL extends IFPL and TASP extends ASP to provide both airport
                           and ATC views.
Dependencies               None
Resource File              <component test home>/integration/backwards_compatibility.gsdk


ID    Time       Actions                   Expectations
1     16:12:00   Run scenario.             AVD appears displaying LFPG ground sectors, LFPG airport
                                           sector and fixes.
                                           FS PVD appears displaying airspace sectors and fixes around
                                           LFPG.
                                           LFPG PVD appears displaying (local) airspace sectors and
                                           fixes around LFPG.
2     16:12:00   Commence at normal
                 speed.
3     16:12:17                             DEP1 appears on AVD.
                                           DEP1 does not appear on PVDs (zoom out as necessary)
4     16:12:24                             ARR1 appears on PVDs.
                                           ARR1 does not appear on AVD (zoom out as necessary)
                                           ARR1 only appears on AVD when within TIAS limits.




     17 CAPACITY TEST

     17.1 Rush Hour

     17.1.1 CT_INT_CAP_01 – Automated Many Arrivals and Departures
Scenario ID                CT_INT_CAP_01
SRD Reference              670
Objective                  To Demonstrate many arrivals, departures at airport both in standalone and
                           integrated mode.

STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                             f7919ee3-d7fb-4de6-9213-
                                                    1719658e70fc.doc

                                                 Page : 189 of 197

                                                                           EUROCONTROL



Dependencies              None
Resource File             <component test home>/rushhour/standalone.gsdk
                          <component test home>/rushhour/integrated.gsdk


ID   Time       Actions                   Expectations
1    16:12:00   Launch      and    run    Confirm AVD RWY_N appears.
                scenario
                                          Confirm 22 departures takeoff.
                rushhour/standalone.g
                sdk                       Confirm 22 arrivals land
                                          Confirm one vehicle VAN travels around APRON_N.
2    16:34:00                             Confirm only VAN remains on AVD.


1    16:12:00   Launch      and     run   Confirm AVD RWY_N appears.
                scenario
                                          Confirm PVDs LFPG and FS appear
                rushhour/integrated.gs
                dk                        Confirm 22 departures takeoff and appear in PVDs.
                                          Confirm 22 arrivals appear in PVDs, which then disappear from
                                          PVD when they land at airport and appear on AVD.
                                          Confirm one vehicle VAN travels around APRON_N.
2    16:34:00                             Confirm only VAN remains on AVD.




STATUS                                                                                             TITLE
Company Ref.                                                                        Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 190 of 197

                                                                               EUROCONTROL




     18 COMPLIANCE MATRIX



     18.1 SRD Requirement To Test Case Mapping
SRD            Test Case Reference
Requirement
10             NO TEST: Architecture distinct components (mandatory)
20             CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
30             CT_INT_BC_01
40             NO TEST: Architecture built upon existing GSDK and eDEP (mandatory)
50             NO TEST: TIAS distinct air ground components (mandatory).
60             NO TEST: Architecture document (mandatory).
               The design documentation shall explicitly address the architectural concerns detailed in
               requirements 40 and 50 above.
70             CT_TACR_001
80             CT_TASP_001
90             CT_TASP_001
100            CT_TASP_001
110            CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
120            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
130            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
140            NO TEST: TASP apron entity (mandatory).
               An airport shall be partitioned into ground sectors which may cover all or part of the
               airport. Each apron shall be modelled using a ground sector where any gates within the
               geographic boundaries of the ground sector will be associated to that apron.
150            CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
160            NO TEST: TASP entity altitude (mandatory).
               The airport altitude shall be used to define the aircraft flight level when entering or
               leaving the eDEP ATC system.
170            CT_INT_BC_01
180            NO TEST: TASP import TAAM data (desireable).
               A TAAM –> eDEP file converter utility shall be required to import such data into eDEP.
190            NO TEST: TASP XML import utility (optional).
               A STORIA XML -> eDEP file converter utility may be required to import such data into
               eDEP.
200            CT_INT_BC_01
210            CT_DNS_001
220            CT_DNS_001
230            CT_TASP_001, CT_DNS_001

STATUS                                                                                                    TITLE
Company Ref.                                                                               Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 191 of 197

                                                                               EUROCONTROL




SRD            Test Case Reference
Requirement
240            CT_TIFPL_001
250            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
260            CT_TASP_001, CT_DNS_001
270            CT_TASP_001
280            CT_TIFPL_001, CT_TPM_TRA_04
290            CT_TPM_TRA_01, CT_TPM_TRA_02, CT_TPM_TRA_03, CT_TPM_QUE_01,
               CT_TPM_QUE_02
300            CT_TFM_CLR_01
310            CT_TPM_TRA_01, CT_TPM_TRA_03, CT_TPM_QUE_01, CT_TPM_QUE_02
320            CT_TPM_QUE_01, CT_TPM_QUE_02
330            CT_TPM_TRA_02, CT_TPM_GIV_01, CT_TPM_GIV_02
340            CT_TPM_TRA_03, CT_TPM_GIV_03
360            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03, CT_TPM_RES_01,
               CT_TPM_RES_02, CT_TPM_RES_03
370            CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
380            CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
390            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
400            CT_TFPM_01
410            NO TEST: TPM Apron pause for de-icing (optional)
               Certain departing aircraft shall be sent to de-icing points : these points shall have an
               associated PAUSE parameter. This will simulate the process of de-icing.
420            NO TEST: TPM Apron destination parking (optional)
               Certain arriving aircraft, after a period at the gate, shall be sent to the parking area.
430            NO TEST: TPM Apron departing from parking (optional)
               Certain departing aircraft shall begin their navigation at the parking area. They shall then
               proceed to the gate, where after a given delay (e.g. 30 minutes) they shall push-back for
               taxing to runway.
440            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
450            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
460            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
470            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
480            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
490            CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
500            CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
510            CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
520            CT_TPM_ARR_02
530            CT_TFM_CLR_03



STATUS                                                                                                     TITLE
Company Ref.                                                                                Template : Normal.dotm
                                                f7919ee3-d7fb-4de6-9213-
                                                       1719658e70fc.doc

                                                    Page : 192 of 197

                                                                                 EUROCONTROL




SRD            Test Case Reference
Requirement
540            NO TEST: TPM Runway dry weather (mandatory).
               The supplier shall assume dry-weather conditions (related to a/c acceleration &
               deceleration rates)
560            CT_TFM_CLR_01
570            CT_TFM_CLR_01
580            CT_TFPM_01
590            NO TEST: TCWP Ground radar true updates (mandatory)
               Radar updates (plots) shall be identical to ground movement state vectors
               (i.e. no error modelling and/or radar coverage modelling is required)
600            CT_TIAS_UPD_01
610            NO TEST: Approach autoland change SID/STAR (optional).
               Possible improvements to the eDEP ATC simulator (APP/En-route) include
                 Change SID/STAR (also change runway)
                 AutoLand (capture localizer/ILS/glide slope)
620            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
630            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
640            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
650            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
660            NO TEST: Approach standalone mode (mandatory).
               In standalone mode :
                  arrivals shall automatically land on the runway at the defined ‘AIFPL.ETA time
                  Departures shall leave the system after takeoff + ‘delta’ time.
670            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
680            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
690            NO TEST: TFM estimate trajectory (mandatory).
               In conjunction with the navigation script TFM shall maintain estimate off block (OBT) and
               take off (TOT) times for departures and estimate landing (LDT) and in block (IBT) times
               for arrivals. TFM shall manage these estimates and promote them to targets and finally
               to actual as the aircraft progress on their travels.
700            NO TEST: TFM trajectory airport point with time (mandatory).
               This ‘trajectory’ shall simply be a list of (Airport Point, Time) values (i.e. the supplier is
               not expected to provide a detailed trajectory with estimates every 5 seconds).
710            NO TEST: TFM determination of taxiing times (mandatory).
               This trajectory shall be used to determine approximate [in fact it will provide nominal taxi
               times] taxiing times
720            NO TEST: TCWP airport view display (mandatory).
               The HMI‟s principle element shall be the Airport view display
730            NO TEST: TCWP airport map (mandatory).
               The AVD shall contain a detailed 2D airport Map detailing taxiways, runways, buildings,
               aprons/gates etc
740            NO TEST: TCWP airport map in TAAM format (mandatory).
               The detailed map data shall be provided by the EEC in a TAAM format (polygon ASCII
               files). This will be converted by the supplier into eDEP file format.


STATUS                                                                                                          TITLE
Company Ref.                                                                                 Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 193 of 197

                                                                              EUROCONTROL




SRD            Test Case Reference
Requirement
750            NO TEST: TCWP airport plot movements (mandatory).
               The AVD shall display all airport traffic movements (plot position, vector line, data block)
760            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
770            CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
780            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
790            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
800            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
810            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03
820            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
830            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03
840            CT_TCS_ROL_04, CT_TCS_ROL_05, CT_TCS_ROL_06
850            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
860            CT_TCS_ROL_04, CT_TCS_ROL_05, CT_TCS_ROL_06
870            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03
880            CT_TCWP_LABEL_01, CT_TCWP_LIST_01,
890            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
900            CT_TCWP_LIST_01
910            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
920            CT_TCWP_LIST_01
930            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
940            CT_uTCWP_01
950            CT_uTCWP_01
960            CT_uTCWP_01
970            NO TEST: Data Preparation (optional).
               Improve the eDEP Traffic editor to allow:
                 visualisation of airport data
                 visualisation of airport map data
                 edition of AIFPL data.
                 visualisation of computed DNS (Detailed Navigation Script) & trajectory data
                  (available via TWR FDPS)
G10            NO TEST: Assumption TAAM data (mandatory).
               It will be assumed that EEC will supply TAAM data, which on tailored conversion to the
               appropriate eDEP format can be used in the Tower simulator.
G20            CT_TCWP_LABEL_01, CT_TCWP_LIST_01

STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                            f7919ee3-d7fb-4de6-9213-
                                                   1719658e70fc.doc

                                                Page : 194 of 197

                                                                         EUROCONTROL




SRD            Test Case Reference
Requirement
G30            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03, CT_TPM_RES_01,
               CT_TPM_RES_02, CT_TPM_RES_03
G40            CT_TPM_TRA_01, CT_TPM_TRA_03, CT_TPM_GIV_03
G50            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03, CT_TPM_RES_01,
               CT_TPM_RES_02, CT_TPM_RES_03
G60            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03, CT_TPM_RES_01,
               CT_TPM_RES_02, CT_TPM_RES_03
G70            CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03
G80            CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
G90            CT_TFPM_01
G100           CT_TPM_DEP_01
G101           CT_TPM_GMS_01
G110           CT_TPM_TRA_02, CT_TPM_TRA_03, CT_TPM_GIV_01, CT_TPM_GIV_02
G120           CT_TPM_QUE_01, CT_TPM_QUE_02
G130           CT_TFM_CLR_01
G131           CT_TFM_CLR_02
G140           CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
G150           CT_TCS_ROL_01, CT_TCS_ROL_02, CT_TCS_ROL_03, CT_TCS_ROL_04,
               CT_TCS_ROL_05, CT_TCS_ROL_06
G160           CT_TCS_INT_01, CT_TCS_INT_02, CT_TCS_INT_03
G170           CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04
G180           NO TEST: TWR eDEP ATC coordination (mandatory).
               The interface between the TWR simulator and the eDEP ATC system shall require the
               transfer of coordination status between TWR and the eDEP ATC. This shall be achieved
               through the TWR TCS and its eDEP ATC counterpart CS.
2005APT10      CT_TPM_PM_01
2005APT20      CT_TWP_CMPN_01, CT_TWP_CMPN_02, CT_TWP_CMPN_03
2005APT30      CT_TWP_CMPN_01, CT_TWP_CMPN_02, CT_TWP_CMPN_03
2005APT40      CT_TWP_CMPN_01, CT_TWP_CMPN_02, CT_TWP_CMPN_03
2005APT50      CT_TWP_CMPN_01, CT_TWP_CMPN_02, CT_TWP_CMPN_03
2005APT60      CT_TCWP_LABEL_01, CT_TCWP_LIST_01, CT_TWP_SYMBOL_01
2005APT70      CT_TCWP_SHORTCUTS_01, CT_TCWP_SHORTCUTS_02
2005APT80      NO TEST: DEMONSTRATION SCENARIOS (mandatory).
               The Tower project shall support the development of demonstration scenarios exhibiting
               different controller and pilot configurations.
2005APT90      CT_TPM_ARRXASAP_01, CT_TPM_ARRXASAP_02, CT_TPM_ARRXASAP_03
2005APT100     CT_CWP_SYMBOL_02, CT_CWP_SYMBOL_03
2005G10        CT_TWP_SYMBOL_01
STATUS                                                                                              TITLE
Company Ref.                                                                         Template : Normal.dotm
                                              f7919ee3-d7fb-4de6-9213-
                                                     1719658e70fc.doc

                                                  Page : 195 of 197

                                                                             EUROCONTROL




SRD            Test Case Reference
Requirement
2005G20        CT_TAAM_TRAFFIC_01, CT_TAAM_TRAFFIC_02, CT_TAAM_TRAFFIC_03,
               CT_TAAM_TRAFFIC_04, CT_TAAM_TRAFFIC_05
2005G60        CT_TWP_AIRGRD_01, CT_TWP_AIRGRD_02, CT_TWP_AIRGRD_03
2005G70        CT_TWP_HYBRID_01
2005G90        TWR_TSN_CLOSED_01
2005G100       TWR_TSN_CLOSED_01
2005G110       TWR_TSN_CLOSED_01
2005G120       TWR_TSN_OPEN_01
2005G130       TWR_TSN_OPEN_02
2005G140       TWR_TSN_OPEN_03
2005G150       TWR_TSN_OPEN_04
2005G160       TWR_TSN_OPEN_05
2005G170       TWR_TSN_OPEN_06
2005G180       TWR_TSN_OPEN_07
2005G190       TWR_TSN_PERFORMANCE_01
2005G200       TWR_TSN_PERFORMANCE_02
2006TWR10      NO TEST: TPWP Architecture TCWP-like (mandatory).
               The design and implementation of the Tower PWP (TPWP) shall be architecturally
               sound, offer similar functionality to what is available today (e.g. hybrid TCWP), and offer
               an HMI that is „TCWP-like‟
2006TWR20      CT_TPM_TPF_01
2006TWR30      CT_TPM_TPF_01
2006TWR40      CT_TPM_TPF_01
2006TWR50      CT_TPM_TPF_01
2006TWR60      CT_TPM_TPF_01
2006TWR70      CT_TPM_TPF_02
2006TWR80      CT_TPM_TPF_02
2006TWR90      CT_TPM_TPF_02
2006TWR100     CT_TPM_TPF_03, CT_TPWP_LABEL_01, CT_TPWP_ORDERS_01,
               CT_TPWP_MENUS_02, CT_TWP_RTE_01, CT_TWP_RTE_02
2006TWR110     CT_TPM_TPF_03, CT_TWP_RTE_01, CT_TWP_RTE_02
2006TWR120     CT_TPWP_LABEL_01
2006TWR130     CT_TPWP_LABEL_01
2006TWR140     CT_TPWP_LABEL_01
2006TWR150     CT_TPM_TPF_04
2006TWR160     CT_TPWP_LABEL_01
2006TWR170     CT_TPWP_LABEL_01, CT_TPWP_LIST_01

STATUS                                                                                                  TITLE
Company Ref.                                                                             Template : Normal.dotm
                                               f7919ee3-d7fb-4de6-9213-
                                                      1719658e70fc.doc

                                                   Page : 196 of 197

                                                                              EUROCONTROL




SRD            Test Case Reference
Requirement
2006TWR190     CT_TPWP_ORDERS_02, CT_TWP_RTE_01, CT_TWP_RTE_02,
               CT_TPWP_ORDERS_01
2006TWR200     CT_TPWP_ORDERS_03, CT_TPWP_ORDERS_04, CT_TWP_RTE_01,
               CT_TWP_RTE_02
2006TWR210     CT_TPM_TPF_03
2006TWR220     CT_TPM_ARR_01, CT_TPM_ARR_02, CT_TPM_ARR_03, CT_TPM_ARR_04,
               CT_TPM_DEP_01, CT_TPM_DEP_02, CT_TPM_DEP_03, CT_TPM_RES_01,
               CT_TPM_RES_02, CT_TPM_RES_03, CT_TPM_GMS_02
2006TWR230     CT_TPM_QUE_01, CT_TPM_GIV_03
2006TWR240     NO TEST: TPM GMS Speed Adjustment (mandatory).
               Aircraft taxi speed shall be adjusted with respect to the aircraft wake vortex category. (It
               is assumed that this requirement is already satisfied as speeds are per vehicle type.)
2007APT110     CT_TSN_CLEARANCE_02
2007APT120     CT_TSN_CLEARANCE_01
2007APT130     CT_TSN_CLEARANCE_03
2007APT140     CT_TSN_CLEARANCE_04
2007APT150     CT_TSN_CLEARANCE_05
2007APT155     CT_TSN_CLEARANCE_14
2007APT160     CT_TSN_CLEARANCE_06
2007APT170     CT_TSN_CLEARANCE_07
2007APT180     CT_TSN_CLEARANCE_09
2007APT190     CT_TSN_CLEARANCE_10
2007APT200     CT_TSN_DEVIATION_01
2007APT210     CT_TSN_CLEARANCE_15
2007APT220     CT_TSN_CLEARANCE_15
2007APT230     CT_TSN_CLEARANCE_17
2007APT240     CT_TSN_CLEARANCE_17
2007APT250     CT_TSN_CLEARANCE_11
2007APT260     CT_TSN_CLEARANCE_17
2007APT270     CT_TSN_CLEARANCE_08
2007APT280     CT_TSN_CLEARANCE_16
2007APT340     CT_TSN_CLEARANCE_12
2007APT350     CT_TSN_CLEARANCE_12
2007TWR100     CT_TPWP_CNFG_01, CT_TPWP_CNFG_03
2007TWR200     CT_TFM_ORD_01, CT_TFM_ORD_02
2007TWR210     CT_TPWP_LABEL_02




STATUS                                                                                                   TITLE
Company Ref.                                                                              Template : Normal.dotm
                                         f7919ee3-d7fb-4de6-9213-
                                                1719658e70fc.doc

                                             Page : 197 of 197

                                                                    EUROCONTROL



   18.2 Test Cases not linked to SRD Requirement
CT_TPM_ARR_05         Arrival No Route Test
CT_TPM_DEP_04         Departure No Route Test
CT_TCS_ORD_01         Changing Taxi Route
CT_TCS_ABI_01         ABI For Arrival
CT_TFM_ORD_03         Changing Standard Instrument Departure (SID) Test
CT_TFM_ORD_04         Abort Take-off
CT_TFPM_02            Progress Events Test (GateOccupied/GateVacated)
CT_TCWP_LIST_02       Navigation Times
CT_TCWP_MENUS_01      Menu Default Selection
CT_TCWP_MENUS_02      Runway SID Menu
CT_TPWP_CNFG_02       ATC Pilot
CT_TPWP_TRNS_01       Transfer on Landing
CT_TPWP_TRNS_02       Transfer on Takeoff
CT_TPWP_FRQ_01        Frequency Management
CT_TWP_SYMBOL_04      Mark Symbol
CT_TWP_TOOLBAR_01     Toolbar
CT_TSN_CLEARANCE_13   Takeoff Without Clearance Alert
CT_TAI_GORD_01        Go Around
CT_TAI_GORD_02        Go Around
CT_DIS_01             Distributed Test




STATUS                                                                                      TITLE
Company Ref.                                                                 Template : Normal.dotm

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:8
posted:6/11/2011
language:English
pages:207