Docstoc

Test Scripts

Document Sample
Test Scripts Powered By Docstoc
					ACE / eDEP Gateway                             Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008




                              ACE / eDEP Gateway



                               Technical Document


                                    Test Scripts




Issue:        3.0 Draft 1


Author:       Mike Humphrey


Date:         21 Feb 2008


Company:      Graffica Ltd


                              Page 1 of 69
ACE / eDEP Gateway                                                                               Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


                                                                       Table of Contents
1      Introduction..................................................................................................................................................... 3
     1.1      Document purpose .................................................................................................................................. 3
     1.2      Document Change History...................................................................................................................... 3
     1.3      Document Structure ................................................................................................................................ 4
     1.4      Related Documents / References ............................................................................................................ 4
     1.5      Acronyms ................................................................................................................................................ 5
2      Test Details ..................................................................................................................................................... 6
3      Test Plan ......................................................................................................................................................... 7
     3.1      Strategy ................................................................................................................................................... 7
     3.2      Miscellaneous Testing ............................................................................................................................ 7
     3.3      TS Testing ............................................................................................................................................... 7
     3.4      IFPL Testing ........................................................................................................................................... 8
     3.5      FM Testing.............................................................................................................................................. 8
     3.6      IAS Testing ............................................................................................................................................. 9
     3.7      FPM Testing ......................................................................................................................................... 10
     3.8      PM Testing............................................................................................................................................ 10
     3.9      CS Testing ............................................................................................................................................ 11
4      Test Preparations........................................................................................................................................... 12
     4.1      Introduction........................................................................................................................................... 12
     4.2      OASIS Lightweight Platform ............................................................................................................... 12
     4.3      ACE Platform ....................................................................................................................................... 14
5      Test Scripts ................................................................................................................................................... 18
     5.1      Miscellaneous Tests .............................................................................................................................. 18
     5.2      Time Server (TS) .................................................................................................................................. 20
     5.3      Initial Flight Plan Server (IFPL) ........................................................................................................... 23
     5.4      Flight Manager (FM) ............................................................................................................................ 26
     5.5      Integrated Air Surveillance (IAS) ......................................................................................................... 38
     5.6      Flight Path Monitor (FPM) ................................................................................................................... 40
     5.7      Pilot Manager (PM) .............................................................................................................................. 46
     5.8      Coordination Server (CS) ..................................................................................................................... 49
A.         Annex 1 – Screen Captures ...................................................................................................................... 69




                                                              Page 2 of 69
ACE / eDEP Gateway                                               Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


1     INTRODUCTION

1.1 DOCUMENT PURPOSE
eDEP is a low-cost, lightweight, web-enabled ATM simulator platform, offering an ideal environment for
research and advanced concept projects to rapidly prototype applications. For a full description see the
Architecture Design Document (reference 1). More information is also available online at
http://www.eurocontrol.int/eec/projects/projects/355.htm.
ACE is the latest generation of ESCAPE, the EEC’s ATM platform for real-time simulation, training and pre-
operational validation. For a full description see the High Level Description document (reference 2). More
information is also available online at http://www.eurocontrol.int/eec/projects/projects/276.htm
eDEP is to be integrated with ACE so that eDEP can be run with high-fidelity trajectories. This is to be done
using a gateway, the ACE / eDEP Gateway (AEG), which will provide the connections with the ACE platform
and include proxy components to replace some of the standard eDEP components. Full details of this gateway
can be found in the ACE/eDEP Gateway Design Document (reference 3).
This document describes the tests used to verify the correct functioning of the AEG, and how to run them. It
lists the features to be tested, the expected results, and any comments on the observed behaviour.
This version of the document is concerned with the testing of the AEG for ACE8A, using the eDEP 2007 Q4
delivery. Full details of what was tested, and using what, are given in section 2.

1.2   DOCUMENT CHANGE HISTORY
Release       Author         Release Date        Release Description       Modifications (sections affected
                                                                             and relevant information)
0.1       M. Humphrey      September 2004      Initial Draft for FDPS
                                               testing.
1.0       M. Humphrey      28th September 2004 First release for FDPS     All.
                                               testing.
1.1       M. Humphrey      19th January 2005   All testing completed      2.6, 2.7, 3 updated.
                                               with ACE2004B bis.         4.4, 4.5, 4.6 completed.
1.2       M. Humphrey      2nd December 2005 CS testing added.            2.8, 4.7 added. 3.3 updated.
1.3       M. Humphrey      21st December 2005 4Bbis and 5A testing.
1.4       M. Humphrey      1st August 2006     5B testing.                Section 2, Test Details updated.
                                                                          ACE5B details added to section 4.
                                                                          Section 5, test scripts & results updated.
1.5       M. Humphrey      23rd January 2007     5B testing with Q4 ‘06   Section 5, minor updates to test scripts.
1.6       M. Humphrey      13th February 2007    7A testing.              Sections 4 & 5, test preparations &
                                                                          scripts updated throughout.
1.7       M. Humphrey      5th May 2007          Reference SCMP for       Section 4.2.2.
                                                 build instructions.
1.7       M. Humphrey      28th June 2007        7A coordination testing Section 2, Test Details updated.
                                                                         Section 3.9, Coordination tests updated.
                                                                         Section 5, test scripts & results updated.
2.0       Graffica(Thom)   14 Aug 2007           Version number change N/A
                                                 to Graffica standard
3.0       Graffica         21 February 2008      Updated for AEG 8A.     Sections 2, 4, 5, Test Details, Scripts &
Draft 1   (Humphrey)                                                     Results, all updated

                                     Table 1-1 Document Change History




                                          Page 3 of 69
ACE / eDEP Gateway                                                 Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008



1.3 DOCUMENT STRUCTURE
This document contains the following sections:
Section 1 outlines the purpose of the document, and its contents.
Section 2, Test Details, lists which tests were performed for the current version of this document.
Section 3 describes the test plans – the testing strategy, and the features of each AEG component to be tested
and how the testing will be performed.
Section 4 describes the test environment, how to build and prepare the systems ready for testing, and how to run
the tests.
Finally, section 5 has the full test scripts, with expected results and observations.

1.4   RELATED DOCUMENTS / REFERENCES
Ref                  Title                      Doc Reference               Authors            Date
 1     eDEP Architecture Design Doc.        GL/eDEP/ADD/1 V2.0           M. Vere          August 2007
 2     ESCAPE High Level Description                      -              Various          January 2003

 3     ACE/eDEP Gateway Design
                                               GL/AEG/TR/1, V3.0         Graffica         February 2008
       Document

 4                                                                       D.Smith,
       eDEP Acceptance Plan (STP)                     V0.4                                December 2003
                                                                         Graffica
 5     eDEP Component Test Scripts                    V2.2               Various          December 2007

 6     eDEP Software Configuration
                                              GL/eDEP/TN/1, V1.1         Graffica         January 2008
       Management Plan [SCMP]

                                                Table 1-2 References




                                           Page 4 of 69
ACE / eDEP Gateway                                    Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008



1.5   ACRONYMS
      Abbreviation                                     Meaning
ACE                  AVENUE Compliant ESCAPE
AEG                  ACE / eDEP Gateway
ATM                  Air Traffic Management
AVENUE               ATM Validation Environment for Use towards EATMS
CDB                  CORBA Data Browser
CDL                  Component Definition Language
CLI                  Command Line Interface
CORBA                Common Object Request Broker Architecture
CS                   Coordination Server
CWP                  Controller Working Position
EATMP                European Air Traffic Management Programme
EATMS                European Air Traffic Management System
eDEP                 Early Development and Evaluation Platform
EEC                  EUROCONTROL Experimental Centre
ERIS                 EATMP Reference Industry-Based Simulation Platform
ESCAPE               EUROCONTROL Simulation Capability And Platform for Experimentation
FDPS                 Flight Data Processing System
FM                   Flight Manager
FPM                  Flight Path Monitor
IAS                  Integrated Air Surveillance
IDL                  Interface Definition Language
IFPL                 Initial Flight Plan
IOR                  Interoperable Object Reference
OASIS                Open Architecture for Simulation Systems
ORB                  Object Request Broker
PM                   Pilot Manager
POA                  Portable Object Adapter
PVT                  Profile Validation Tool
RDPS                 Radar Data Processing System
RMI                  Remote Method Invocation
SIL                  Sector Inbound List
SIW                  SYSCO Interface Window
SYSCO                System Coordination
TS                   Time Server
                                     Table 1-3 Acronyns




                                Page 5 of 69
ACE / eDEP Gateway                                             Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


2   TEST DETAILS


The following table indicates which tests were run for which versions of ACE:
                   Test                  ACE 5B               ACE 7A                 ACE 8A
             AEGT_MISC_A                 Recorded              Recorded              Live
             AEGT_MISC_B                      -                  Live                Live
             AEGT_TS_A                        -                  Live                Live
             AEGT_IFPL_A                    Live                 Live                Live
             AEGT_FM_A                      Live                 Live                Live
             AEGT_FM_B                      Live                 Live                Live
             AEGT_FM_C                      Live                 Live                Live
             AEGT_IAS_A                     Live                 Live                Live
             AEGT_FPM_A                       -                    -                 Live
             AEGT_PM_A                        -                    -                 Live
             AEGT_CS_A                       n/a                 Live            Live Generic*
             AEGT_CS_B                       n/a                 Live                  -
             AEGT_CS_C                       n/a                 Live                  -
             AEGT_CS_D                       n/a                 Live                  -
*For the ACE 8A Coordination Server tests, some generic tests were run live to check basic functionality, but
the full tests could not be performed due to problems with the ACE scenario and SYSCO configuration.


Where tests were performed live, the following table gives the dates the tests were run and of the ACE
executables used, for each version of ACE tested against:
                                ACE 5B                   ACE 7A                         ACE 8A
Dates run                 23rd/24th January 2007    11th – 27th June 2007     11th – 20th February 2008
Date of Executables         17th January 2007        5th/25th June2007          th
                                                                            9 January / 20th February 2008

A copy of the ACE input files used for each version of ACE is held within the relevant AEG project under
“AEG_Component/implementation/src/test/data…” (previously “AEG_src/test/data/…”). The relevant files for
this testing are:
               ACE 2005B        - GRAFFICA5B_data.tar.gz.
               ACE 2007A        - BGDTL_data.tar.gz, EGSYSCO_data.tar.gz
               ACE 2008A        - BGDTL, EGSYSCO.




                                         Page 6 of 69
ACE / eDEP Gateway                                                 Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


3     TEST PLAN

3.1 STRATEGY
Several measures will be taken to reduce the effort required to test the proxy components and AEG while still
ensuring adequate test coverage. These include:
      -     re-using standard component test cases
      -     using standard ACE delivery airspace and traffic
      -     ‘static’ testing where possible
Where possible, test cases will be selected from the existing component test cases to provide a reasonable
coverage. This will save the effort required to devise tests from scratch. Not all the existing test cases will be
needed, just those that test the interfaces and translation between eDEP and ACE and those that test
functionality retained within the AEG proxy components – functionality now provided by ACE need not be
tested.
Using the standard ACE delivery data files will reduce the risk of encountering problems with the platform and
ACE components by only re-using a well tested scenario. While this will require the test scripts for the above
selected test cases to be adapted to this scenario for each component, rather than just converting the set of input
files once, it is likely to be worthwhile in the long run.
Where possible, testing will be performed ‘statically’, i.e. with sufficient of the ACE platform running to send
events, and the resulting eDEP information being examined in the PVT. This will reduce the effort needed to
conduct the tests. Where this is not possible, e.g. because the test requires an aircraft to fly along its trajectory,
testing will be performed with both ACE and eDEP running and at least one eDEP CWP. The number of
components running, however, will still be kept to the minimum necessary.
Testing will be carried out broadly in line with the philosophy set out in the eDEP System Test Plan (see ref 4).

3.2    MISCELLANEOUS TESTING

3.2.1 Method
The miscellaneous AEG tests are performed dynamically running both ACE and eDEP, and running eDEP with
the AEG in replay mode without ACE.

3.2.2 Test Cases
The following test cases will be used:
          1. AEGT_MISC_01         - CORBA Data Browser
          2. AEGT_MISC_02         - Replay
          3. AEGT_MISC_03         - MAFF data
          4. AEGT_MISC_04         - Trajectory editing
          5. AEGT_MISC_05         - Separate launching



3.3    TS TESTING

3.3.1 Method
The AEG proxy TS component will be tested using the OASIS light platform and time server, and by observing
results on the eDEP Console.

                                          Page 7 of 69
ACE / eDEP Gateway                                                Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


3.3.2 Test Cases
The following test cases will be used to test the time service:
         1. AEGT_TS_01           - Time updates
         2. AEGT_TS_02           - Time rates
         3. AEGT_TS_03           - Time pauses

3.4     IFPL TESTING

3.4.1 Method
The AEG proxy IFPL component will be tested statically, by examining the flight plan data in the PVT.

3.4.2 Test Cases
The set of test cases from the IFPL component tests will be used (see ref. 5). Specifically, for each flight plan
under test, the contents as displayed in the PVT will be verified against the original input data. The following
flight plan properties will be included:
         1. AEGT_IFPL_01         - Simple level en route plan
         2. AEGT_IFPL_02         - Plan with a descent
         3. AEGT_IFPL_03         - Plan with a climb
         4. AEGT_IFPL_04         - Plan with SID
         5. AEGT_IFPL_05         - Plan with STAR

3.5     FM TESTING

3.5.1 Method
The AEG proxy FM component will be tested in two phases. In the first phase the tests will be conducted
statically, by examining the initial trajectory information in the PVT. To complete the testing a second set of
tests will need to be performed dynamically, with both ACE and eDEP running. In this second phase orders for
aircraft will be entered at a CWP, and sent via the AEG proxy FM component to the ACE platform. The
subsequent flight of the relevant aircraft will then be followed to verify correct translation of the orders.

3.5.2    Test Cases
3.5.2.1 Phase 1
In the first phase, the following test cases from the FM component tests will be used (see ref. 5):
          1. AEGT_FM_01 (STC_GRD_FM_RTE_010)                       – Simple Route Segment Expansion
          2. AEGT_FM_02 (STC_GRD_FM_RTE_020)                       – SID / STAR Expansion
          3. AEGT_FM_03 (STC_GRD_FM_CON_020)                       – LoA Constraint
          4. AEGT_FM_04 (STC_GRD_FM_SEC_10)                        – Horizontal Sector Traversal*
          5. AEGT_FM_05 (STC_GRD_FM_SEC_20)                        – Vertical Sector Traversal*
          6. AEGT_FM_06 (STC_GRD_FM_UNT_030)                       – FM Derived COP Calculation
*Note again that since, in an integrated eDEP, a unit will always equal a sector, these test cases will test both
sector and unit traversal.



                                          Page 8 of 69
ACE / eDEP Gateway                                                Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


3.5.2.2 Phase 2
In this phase of testing, the following test cases from the FM component tests will be used (see ref. 5):
          1. AEGT_FM_11 (STC_GRD_FM_HDG_010)                       – Heading Order
          2. AEGT_FM_12 (STC_GRD_FM_CFL_010)                       – New Cleared Flight Level
          3. AEGT_FM_13 (STC_GRD_FM_DIR_010)                       – Simple Direct To Order
The following test cases will also be included:
          4. AEGT_FM_14                   - XFL Order
          5. AEGT_FM_15                   - Time Constraint*
          6. AEGT_FM_16                   - Speed Order
          7. AEGT_FM_20                   - General Flight Handling
          8. AEGT_FM_21                   - Flight Deletion
*Note that this cannot be tested with the current system.

3.6   IAS TESTING

3.6.1 Method
The AEG proxy IAS component will need to be tested dynamically, with both ACE and eDEP running. The
tracks of selected flights will be examined, and compared with their predicted trajectories (while allowing for
the usual variations).

3.6.2 Test Cases
Currently, there aren’t any standard IAS component tests that can be reused for testing the proxy IAS. The test
cases will comprise analysing flights with the following properties:
        1. AEGT_IAS_01           - Straight level flight at constant speed
        2. AEGT_IAS_02           - Turning level flight at constant speed
        3. AEGT_IAS_03           - Flight with speed change
        4. AEGT_IAS_04           - Straight climbing flight
        5. AEGT_IAS_05           - Straight descending flight
        6. AEGT_IAS_06           - Turning flight with climb or descent




                                          Page 9 of 69
ACE / eDEP Gateway                                               Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008



3.7   FPM TESTING

3.7.1 Method
The AEG proxy FPM component will need to be tested dynamically, with both ACE and eDEP running. For
testing deviation events, the MASS PWP on the ACE platform will be required, to send instructions to an
aircraft contrary to its planned trajectory in order to generate the required deviations. For testing the remaining
events no interaction is required.

3.7.2 Test Cases
The following cases will be tested:
        1. AEGT_FPM_01           - Sector/Unit crossing event*
        2. AEGT_FPM_02           - Waypoint Passed event
        3. AEGT_FPM_03           - Deviation event - vertical
        4. AEGT_FPM_04           - Deviation event – lateral
        5. AEGT_FPM_05           - Deviation event – longitudinal (time)
        6. AEGT_FPM_06           - Deviation event – combined
        7. AEGT_FPM_07           - End of deviation
*Note that since in an integrated eDEP, a unit will always equal a sector, these events will be equivalent.

3.8   PM TESTING.

3.8.1 Method
The AEG proxy PM component will need to be tested dynamically, with both ACE and eDEP running. The
eDEP configuration must include a hybrid CWP which will generate the aircraft orders that the proxy PM will
send to ACE. The subsequent flight of the relevant aircraft will then be followed to verify correct translation of
the orders.

3.8.2 Test Cases
The following test cases from the PM component tests will be used (see ref. 5):
        1. AEGT_PM_01 (STC_AIR_DIR_010)                   – Direct To (on plan, staying on plan)
        2. AEGT_PM_02 (STC_AIR_HDG_010)                   – Heading Order (Leaving Plan)
        3. AEGT_PM_03 (STC_AIR_CFL_010)                   – Change CFL (on Plan)
        4. AEGT_PM_05 (STC_AIR_SPD_010)                   – Mach Speed
        5. AEGT_PM_06 (STC_AIR_SPD_020)                   – IAS Speed
        6. AEGT_PM_08 (STC_AIR_CTL_010)                   – Transfer Flight
The following test cases will also be included:
        7. AEGT_PM_04                    - ROCD
        8. AEGT_PM_07                    - TAS Speed




                                         Page 10 of 69
ACE / eDEP Gateway                                             Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008



3.9   CS TESTING

3.9.1 Method
The AEG proxy CS component will need to be tested dynamically, with both ACE and eDEP running, and
multiple eDEP CWPs. The behaviour and information shown on the CWPs will be verified, both for
coordination events initiated by user interactions, such as requesting a crossing level, and for time/trajectory
based events initiated by the ACE SYSCO server, such as inbound messages. Where relevant, tests will be
performed for situations where standard coordination conditions are met (SC) and for where standard conditions
are not met (NSC). The tests are designed around the functionality of the ACE SYSCO server rather than being
based on the standard eDEP coordination test cases.

3.9.2 Test Cases
The following cases will be tested:
        1. AEGT_CS_01           - Initialisation
        2. AEGT_CS_02           - SC crossing: ABI – ACT – Transfer – Assume
        3. AEGT_CS_03           - NSC crossing: ABI – RAP – Accept – Transfer – Assume
        4. AEGT_CS_04           - Automatic (SC) coordination: ABI – ACT – Propose
        5. AEGT_CS_05           - NSC coordination: ABI – ACT – Propose – Accept
        6. AEGT_CS_06           - Counterpropose coordination: Propose – Counterpropose – Accept
        7. AEGT_CS_07           - Reject coordination: Propose – Reject
        8. AEGT_CS_08           - Parallel coordination: Propose PEL – Propose XFL – Accept – Accept
        9. AEGT_CS_09           - Coordination abrogation
        10. AEGT_CS_10          - Request on Frequency
        11. AEGT_CS_11          - Force Activation
        12. AEGT_CS_12          - Coordination timeout.
        13. AEGT_CS_13          - Re-entrant flight.
        14. AEGT_CS_14          - FM Direct To order – time shift
        15. AEGT_CS_15          - FM Direct To order – crossing point shift
        16. AEGT_CS_16          - FM Direct To order – abrogation
        17. AEGT_CS_17          - Commands via SYSCO Interface Window (SIW)
        18. AEGT_CS_18          - Route coordination – from downstream
        19. AEGT_CS_19          - Route coordination – from upstream




                                        Page 11 of 69
ACE / eDEP Gateway                                             Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


4   TEST PREPARATIONS

4.1 INTRODUCTION
This section describes everything needed to run the AEG tests – the machines and user accounts needed, file
locations, configuration, and finally how to launch the tests.
While eDEP itself can be run anywhere, it is normally run on the PC for convenience. The AEG can only be run
on a suitable platform with CORBA and OASIS installed. There are two platform types available – the OASIS
lightweight platform, and the full ACE platform. The full platform is currently available in the following
versions:
       ACE 5B (Linux)
       ACE 7A (Linux)
       ACE 8A (Linux)

4.2 OASIS LIGHTWEIGHT PLATFORM
The OASIS lightweight platform is a manually configured and operated platform with minimum components,
ideal for small scale and proof-of-concept integration. For our purposes it is only useful for testing the AEG
proxy TS component.

4.2.1 Test environment
An instance of the OASIS light platform for running/testing the AEG is installed alongside the AEG projects
themselves on the unix machine “tarkin” under the user account “mhumphre”.
Following the normal Synergy naming conventions the projects are located in the following directories:
        “/home/mhumphre/ccm_wa/ino/AEG-mhumphre_ACE5B/”,                for ACE 5B;
        “/home/mhumphre/ccm_wa/ino/AEG-mhumphre_ACE7A/”,                for ACE 7A;
        “/home/mhumphre/ccm_wa/ino/AEG-mhumphre_ACE8A/”,                for ACE 8A.

4.2.2 Building
The build process can be found in the ‘EEC Onsite Activities’ section of the eDEP Software Configuration
Management Plan [Ref 6].

4.2.3 Libraries (Jars)
There are 3 categories of jars required for testing the AEG:
              1. ACE-related jars
              2. eDEP-related jars
              3. AEG jar itself.
The following ACE-related jars are needed for building and running the AEG:
        OASIS_java.jar (in Oasis_Infrastructure_Delivery/Runtime/lib)
        libACE_API_Idl_java.jar
          (in Logical_architecture/ACE_IDL_COMPILATION/API_IDL_COMPILATION/orb_java)
        libACE_DD_Idl_java.jar
          (in Logical_architecture/ACE_IDL_COMPILATION/DD_IDL_COMPILATION/orb_java)



                                        Page 12 of 69
ACE / eDEP Gateway                                               Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


         libAVENUE_API_Idl_java.jar  (in   Logical_architecture/AVENUE_Logical_architecture/
           AVENUE_IDL_COMPILATION/API_IDL_COMPILATION/orb_java)
         libAVENUE_DD_Idl_java.jar  (in   Logical_architecture/AVENUE_Logical_architecture/
           AVENUE_IDL_COMPILATION/DD_IDL_COMPILATION/orb_java)
At runtime, the OASIS jar is provided automatically by the test platform; the remaining 4 must be included in
the classpath. For convenience, the contents of all 5 jars are available in the single merged jar
“AEG/lib/ace_libs.jar”.
The following eDEP-related jars are currently needed for building and running the AEG:
         gsdk.jar (normally obfuscated)
         edep.jar (core software)
         Chart2D.jar
         ersStoria.jar (runtime dependency due to the shared MAFF parsing code)
For convenience, the contents of all 4 jars are available in the single merged jar “AEG/lib/edep_libs.jar”.
The main AEG jar is “AEG/Executable/AEG_main/AEGServer.jar”.

4.2.4 Running
Within the project area the platform is run from the directory “AEG/run”.
There are three scripts for controlling the platform and AEG: “oaStart”, “oaStop”, and “launchAEG”.
The platform is launched as follows:
        1. Start the basic OASIS platform and time server: ‘. ./oaStart’
           Several windows appear including the Timer Command Line Interface (CLI).
        2. Start the AEG gateway and eDEP proxy time server: ‘. ./launchAEG’
           A window appears with the AEG output. The launch terminal becomes the OASIS CLI which can be
           used to control the AEG.
        3. Initialise the AEG. In the OASIS CLI enter: ‘init’ or ‘i’.
           The AEG Launcher window will appear. Initialisation will pause until the Run Test button is clicked,
           or the timeout period (default 2 minutes) expires.
        4. Complete initialisation of the OASIS timer server. In the Timer CLI enter: ‘connect’ and then
           ‘synchronize’.
        5. Tell the AEG that configuration is complete. In the OASIS CLI type: ‘cc’.
           The AEG will launch the eDEP Simulation Engine, and the proxy time server.
OASIS and the AEG are now ready. This can be verified as follows:
        1. For OASIS, in the Timer CLI enter: ‘status’.
           The timer should be “READY” and “FROZEN”.
        2. For the AEG, in the OASIS CLI enter: ‘show’ or ‘s’.
           The AceAEG should be “COMPLETED” and “READY”.
eDEP can now be launched on the PC as normal.
Once eDEP is ready the platform is ready for testing and can be controlled via the Timer CLI. To start, enter
‘unfreeze’.


The closing down procedures are as follows:


                                           Page 13 of 69
ACE / eDEP Gateway                                              Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


      1. For the AEG, enter the following in the OASIS CLI: ‘stop’ or ‘st’, ‘remove’ or ‘r’, ‘quit’ or ‘q’.
      2. For the OASIS time server, enter the following in the Timer CLI: ‘stop’, ‘remove’, ‘quit’.
      3. For eDEP: Press the stop button in the Console window.
      4. Finally, the basic platform can be stopped with the following command: ‘. ./oaStop’.
         The remaining OASIS windows should disappear.

4.3 ACE PLATFORM
The ACE platform is the full CORBA and OASIS infrastructure, configured to run whichever components are
required. For the majority of tests, this platform will be used with just standard ground components, plus the
AEG itself, running. For some, later, tests the ACE air system (MASS) and PWP are also required – additional
information for this configuration is detailed separately within the following sections.

4.3.1 Test environment
Ground
An instance of the ACE platform configured for running with the AEG and eDEP is installed under the user
account “runesc” on the machine “sebulba”.
For ACE5B:
All project specific data is held under the directory “INTEGR5B_mph”.
Delivered versions of all AEG executables and jars are installed in the directory
“/exercises/prepesc/Simulations/INTEGR5B/appli/EDEP/bin”. During development, latest versions for testing
purposes are stored in “/home/runesc/INTEGR5B_mph/bin”.
For ACE7A:
All project specific data is held under the directory “INTEGR7A_mhumphre”.
Delivered versions of all AEG executables and jars will be installed in the directory
“/exercises/prepesc/Simulations/INTEGR7A/appli/EDEP/bin”. During development, latest versions for testing
purposes are stored in “/home/runesc/INTEGR7A_mhumphre/bin/aeg”.
For ACE8A:
The machine used is “jabba”.
All project specific data is held under the directory “INTEGR8A_mhumphre”.
Delivered versions of all AEG executables and jars will be installed in the directory
“/exercises/prepesc/Simulations/INTEGR8A/appli/EDEP/bin”. During development, latest versions for testing
purposes are stored in “/home/runesc/INTEGR8A_mhumphre/bin/aeg”, and linked to from the ACE executable
directory.
The      Java     security      file,    “java.policy”,    will     be     installed   in     the       directory
“/exercises/prepesc/Simulations/INTEGR8A/appli/EDEP/config/aegapp”. A copy is likewise stored in the same
directory as above, for linking to from the ACE configuration directory, during deployment for initial testing.
Air
An instance of MASS configured for running with the AEG and eDEP is installed on the unix machine “pc-
cwp10” under the user account “runesc”.
An additional display is needed for the PWP HMI. This can be any machine, UNIX or PC, as long as remote
access is enabled. ACE and MASS are currently configured to display on the PC “supt5-mw”.




                                        Page 14 of 69
ACE / eDEP Gateway                                                 Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


4.3.2 Building
The build process can be found in the ‘EEC Onsite Activities’ section of the eDEP Software Configuration
Management Plan [Ref 6].

4.3.3 Configuration
All     configuration     files   are    held   in    a      project    and exercise specific    directory,
“/exercises/prepesc/Simulations/<project>/<Exercise>. For example, for the AEG running on ACE8A the
directory is “/exercises/prepesc/Simulations/INTEGR8A/BGDTL”. The following files are of particular interest
for testing the AEG and can be edited with any text editor if necessary:
         FLIGHT_FILE.DATA - defines the flights in the exercise, with flight-plan information.
         AIR_FLIGHT_FILE.DATA             - as above but for the Air system. The contents should be the same.
         TDM_PARAMETERS_FILE.DATA                 - contains configuration parameters for the TDM (FPM).

4.3.4 Running
Ground
In the home directory on the ACE ground machine, run the launch script “launch_spv” and then at the prompt
enter the username “mhumphre” (“mph” for ACE5B). This launches the ACE supervision component and the
Run Selection Tool.
For ACE5B:
In the Simulation column, select “INTEGR5B”. A list of Exercises is then displayed – these correspond to
different input parameters and/or scenarios. When an exercise is selected, a list of Runs for that exercise
appears. For all AEG tests, unless otherwise stated, select the Exercise “GRAFFICA” and the Run “Basic”. For
some tests, Run “MASS” will be required.
For ACE7A:
Select simulation“INTEGR7A”, Exercise “BGDTLMPH”, and Run “BGDTLMPH_HB_EC06EDEP” by
default.
For ACE8A:
Select simulation“INTEGR8A”, Exercise “BGDTL”, and Run “BGDTL_HJ_EC06EDEP” by default.
Alternative runs are “BGDTL_HJ_EC14EDEP2” when the Air system is also required, and
“EGSYSCO_HJ_EC13EDEP” for testing AEG Coordination.


After a short delay the Start button becomes active; click on it it start the simulation.
After a while the Supervisor window will appear, showing the current state of all the components running on
the platform; “AceAeg” appears at the bottom. As it initialises the AEG launcher window will appear – select
the required options according to the test and click on ‘Run Test’.
When the 4 lights next to a component are all green, the component is fully initialised and configuration is
complete. Once this is the case for “AceAeg”, if eDEP was not launched with the AEG in a combined scenario,
it can now be launched on the PC.
Once eDEP is ready on the PC the simulation is ready to be started. To do this click on the Unfreeze button in
the Simulation Time Control window.


Air



                                          Page 15 of 69
ACE / eDEP Gateway                                                Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


Before launching ACE, ensure that remote access to the display for the PWP is enabled. To do this for the
current configuration it is sufficient to log on to the PC and then start an Exceed session on a UNIX machine.
Note that the user/host combination for this session should be unique: if, for example, ACE is launched from an
eXceed session from another PC with the same user/host, the remote access authorisation seems to get confused
and the platform fails to launch completely.
If anything has been changed in the ACE scenario configuration, for example in the flight file, these changes
need to be reflected in the air system. To do this, select the “Do Air Preparation” option in the Run Selection
Tool, before clicking on Start in the launch sequence described above.
It is advised not to run a simulation any faster than 2 * realtime, when the air system is included, since it cannot
cope.
Closing Down
The closing down procedures are as follows:
      1. For ACE, including the AEG, click on the Exit.. button in the Supervisor window, then click Yes in
         the dialog box that appears to confirm. Click No in the next two dialog boxes unless the recorded log
         files need to be retained.
      2. For eDEP, if run separately: Press the stop button in the Console window.

4.3.5 Logging
The need for the ACE logging facility has mostly been superceded for the AEG by the addition of the CORBA
Data Browser (CDB). This displays a list of the events the AEG has received from the ACE platform, showing
the simulation time and actual times the event was received, the relevant flight and aircraft, and the event name.
Double-clicking on any line displays another window where the contents of the event (parameter names, types,
and values) can be browsed in a hierarchical manner, expanding and collapsing branches of the nested
structures as desired.
The CDB is turned on or off via a tickbox on the launcher when the AEG is run, and is on by default.
The ACE logging facility is described below for cases where the CDB is insufficient, e.g. for examining
CORBA requests sent by the AEG.
Ground
It is possible to record logs, or traces, of all communications – CORBA facets, receptacles, publishers, sinks for
ACE components while running. This can be setup once the platform is fully initialised and ready to be started,
or at any time following that. (It is probably best to freeze the simulation first though.) The setting of any
required traces is best done from the project working area mentioned previously, e.g.
“INTEGR7A_mhumphre”.
Within this directory there           is    a   sub-directory    for   each    of   the    available   runs,    e.g.
“BGDTLMPH_HB_EC06EDEP”.
During a run, there is a sub-directory in there, of the form “GSP_<username>_<process number>”, that
contains all the run data, component logs, etc. The name of this directory is known as the run number.
The tracing is set as follows:
      1. Source the environment for the simulation run: ‘. ./<run>/<run_number>/config/oasis.env’.
         e.g. ‘. ./BGDTLMPH_HB_EC06EDEP/GSP_mhumphre_1234/config/oasis.env’.
      2. Start the command line interface: ‘OaCcmInfra_Cli -r run_<username>_<run>’.
         e.g. ‘OaCcmInfra_Cli -r run_mhumphre_BGDTLMPH_HB_EC06EDEP’.
      3. To view the items that can be traced for the AEG, in the CLI enter: ‘s AceAeg’.
         For the AEG, this will list the receptacles (services used) and sinks (events consumed).


                                           Page 16 of 69
ACE / eDEP Gateway                                             Reference GL/AEG/TR/2/3.0 Draft 1
21 Feb 2008


      4. To turn on the tracing for a particular item, in the CLI enter:
         ‘tr <component name>.<receptacle name>’ or ‘ts <component name>.<sink name>’.
         E.g. to log all received radar track events, enter ‘ts AceAeg.opt_ace_asm_aceradartrack_event’.
      5. Alternatively, the required trace commands can be put in a text file which is used as input to the CLI
         instead of using it interactively.
         The format for this is ‘OaCcmInfra_Cli -r run_<username>_<run> -f <input file>’.


The log file can be found in <run>/runtime/<config>/AceAeg_corba.log, where <config> is the Escape
Configuration. By convention, this configuration name is normally incorporated as part of the run name, in this
case “EC06EDEP” (“EC01” for the ACE5B platform). The log file remains after the platform is shutdown but
will be overwritten by any subsequent runs.
Normal AEG component output is written to the file <run>/<run number>/log/appli/AceAeg_Server.log (e.g.
BGDTLMPH_HB_EC06EDEP/GSP_mph_1234>/log/appli/AceAeg_Server.log). This file is deleted (along
with the whole <run number> directory) when the platform is shutdown, unless the option to save the recorded
logs is taken.


Air
Output from MASS is written to files under the directory “/tmp/EDEP” and in a <run> directory under the
working area mentioned previously, e.g. “/home/runesc/INTEGR7A_mhumphre/<run>/log”, where <run> is
the same as for the ground system. These files remain after the platform is shutdown but will be overwritten by
any subsequent runs.




                                       Page 17 of 69
ACE / eDEP Gateway                                                                                                                   Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                    D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



5        TEST SCRIPTS

5.1       MISCELLANEOUS TESTS


Scenario ID                AEGT_MISC_A
Tested Functionality       Various
Objective                  Demonstrate correct standard behaviour for basic AEG functions.
Dependencies
Resource File              common_combined.gsdk, as for original test.


The first part of the miscellaneous tests (the CDB) is mostly covered in later tests. To complete the testing, replay the recording from one of those tests where the
CDB was used to check a value, e.g. AEGT_FM_C, or AEGT_CS_D.
    ID      TIME           Test Case                       Actions                                   Expectations                                    Observations

    1        N/A              -            Start the AEG Gateway launcher on          The eDEP Console, CDB, and one or more
                                           either a Unix machine or the PC (as long   CWPs are displayed.
                                           as the recorded file is available).
                                           Select the same combined scenario as
                                           was used for the recording, untick the
                                           MAFF option, browse and select the
                                           recorded file and click on Replay.

    2      Start time   AEGT_MISC_01       Press play on the Console to start the     The time increments on the Console.
                                           simulation
                                                                                      The same events appear in the CDB as
                                                                                      during the recording.

    3      As during    AEGT_MISC_02       Examine the same event/values as during    The event contents are the same.
           recording                       the recording.



                                        Page 18 of 69
ACE / eDEP Gateway                                                                                                             Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                              D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




Scenario ID              AEGT_MISC_B
Tested Functionality     The trajectory editor interface to ACE. MAFF data readers.
Objective                Demonstrate correct behaviour and interaction with ACE for trajectory editing
                         and subsequent orders, reading of MAFF data files, and separate launching of
                         AEG and eDEP parts..
Dependencies
Resource File            common_integrated.gsdk, common.gsdk, on_pc.gsdk, on_sun.gsdk, fdps.gsdk,
                         aeg_run_fdps.gsdk


  ID    TIME           Test Case                      Actions                                  Expectations                                Observations

  1a        N/A           -          Launch the ACE supervision on the Sun The ACE platform is launched and the
                                     machine (see 4.3.3), and select and start the AEG Gateway Launcher appears.
                                     EDEP simulation with the usual exercise
                                     and run.

  1b        N/A    AEGT_MISC_05 - Select the “componenttests/unix/ fdps”         The AEG is launched and starts the eDEP
                                     scenario,                                   simulation engine and proxy components.
                                     - ensure correct MAFF directory is shown,
                                     - tick the ‘Record Events’ option,
                                     - browse and enter the filename
                                     AEGT_MISC_B.log for the Record File
                                     - click on Run Test.

  2         N/A    AEGT_MISC_05 Start the AEG Scenario launcher on the PC, The eDEP Console, PVT, and CWP are
                                     select the correct ACE host, and run the displayed.
                                     “componenttests /windows/aeg_run_fdps”
                                     configuration.

  3         N/A    AEGT_MISC_03 Examine the AEG output.                          The AEG read the MAFF files without any
                                                                                 errors.
                                     Examine the PVT and CWP.                    The airspace is displayed correctly.

                                     Page 19 of 69
ACE / eDEP Gateway                                                                                                                     Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                      D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  4     16:40:00            -          Start the simulation by clicking on the The time increments on the Console and
                                       Unfreeze button in the Simulation Time flights begin to appear in the PVT.
                                       Control window

  5     16:45:00+   AEGT_MISC_04 In the CWP, if necessary request on The trajectory editing pop-up                   menu
                                       frequency, then assume a flight. Display appears, and the alternative flight-leg is
                                       the flight leg for an assumed flight and displayed in a different colour.
                                       click and drag a point on the trajectory to
                                       start a heading adjustment.

  6     16:45:00+   AEGT_MISC_04 Click on Accept.                                     The old flight-leg disappears and the new
                                                                                      one is displayed in green.

  7     16:45:00+   AEGT_MISC_04 In the CWP, display the flight leg for an            The trajectory editing pop-up menu and
                                       assumed flight and click on a point to start   the direct to pop-up menu appear.
                                       a direct order.
                                       Select a point from the pop-up menu.           The alternative flight-leg is displayed in a
                                                                                      different colour.

  8     16:45:00+   AEGT_MISC_04 Click on Accept.                                     The old flight-leg disappears and the new
                                                                                      one is displayed in green.

  9     16:45:00+   AEGT_MISC_04 In the CWP, display the flight leg for an The trajectory editing pop-up                 menu
                                       assumed flight and right-click on a point on appears, and the alternative flight-leg is
                                       the trajectory to delete it.                 displayed in a different colour.

  10    16:45:00+   AEGT_MISC_04 Click on Cancel.                                     The new flight-leg disappears and the
                                                                                      current one remains displayed in green.




5.2    TIME SERVER (TS)


Scenario ID               AEGT_TS_A
Tested Functionality      The AEG proxy Time Server.
Objective                 Demonstrate correct standard behaviour for time ticks.
                                       Page 20 of 69
ACE / eDEP Gateway                                                                                                                  Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                   D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



Dependencies
Resource File          aeg_ts_light.gsdk,    common_integrated.gsdk,            common.gsdk,      on_pc.gsdk,
                       on_sun.gsdk ts_light.gsdk




 ID     TIME         Test Case                      Actions                                    Expectations                                    Observations

  1      N/A            -         Launch the OASIS light platform and            Several windows appear, including the
                                  AEG on the Sun machine (see section            Timer Command Line Interface (CLI), the
                                  4.2.3 ).                                       AEG output, and the AEG Launcher.
                                  Deselect the “Combined Scenarios” and
                                  “Data Browser” options, and run the
                                  “componenttests/unix/ts_light” scenario.

  2      N/A            -         Start the eDEP AEG tests launcher on the       The eDEP Console is displayed.
                                  PC and run the “componenttests/windows
                                  /aeg_ts_light” configuration.

  3    10:35:20    AEGT_TS_01     Unfreeze the OASIS time server by typing       The time increments on the Console.            The first second increment is skipped.
                                  ‘unfreeze’ in the Timer CLI.

  4    10:35:20+   AEGT_TS_02     Change the time rate by entering e.g.          The time on the Console increments at the
                                  ‘setSimuRate 2.0’ in the Timer CLI.            new rate.

  5    10:35:40+   AEGT_TS_03     Freeze the OASIS time server by typing         The time on the Console pauses.
                                  ‘freeze’ in the Timer CLI.

  6    10:35:40+   AEGT_TS_02     Change the time rate again by entering e.g.    The time on the Console remains paused.
                                  ‘setSimuRate 0.5’ in the Timer CLI.

  7    10:35:40+   AEGT_TS_02 /   Unfreeze the OASIS time server.                The time on the Console increments at the
                   AEGT_TS_03                                                    new rate.

  8    10:35:50+   AEGT_TS_03     Freeze the OASIS time server.                  The time on the Console pauses.


                                   Page 21 of 69
ACE / eDEP Gateway                                                                                                Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                 D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  9   10:35:50+    AEGT_TS_03   Unfreeze the OASIS time server.   The time on the Console increments at the
                                                                  same rate as before it was paused.




                                 Page 22 of 69
ACE / eDEP Gateway                                                                                                                Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                 D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




5.3  INITIAL FLIGHT PLAN SERVER (IFPL)
Scenario ID          AEGT_IFPL_A
Tested Functionality    The AEG proxy Initial Flight Plan Server.
Objective               Demonstrate correct standard translation of the ACE events into eDEP IFPLs.
Dependencies
Resource File           pvt_ifpl.gsdk, common_combined.gsdk




 Id.     Time          Test Case                      Actions                                    Expectations                                  Observations

  1         N/A           -          Launch the ACE supervision on the Sun        The ACE platform is launched and the
                                     machine (see 4.3.4), and select and start    AEG Gateway Launcher appears.
                                     the EDEP simulation with the usual
                                     exercise and run.

  2         N/A           -          Select                                 the   The AEG is launched and starts the eDEP
                                     “componenttests/combined/pvt_ifpl”           simulation engine and proxy components.
                                     scenario, untick the MAFF option, tick the   The AEG Data Browser and PVT are
                                     ‘Record Events’ option, browse and enter     displayed.
                                     the filename AEGT_IFPL_A.log for the
                                     Record File, and click on Run Test.

  3    16:40:00           -          Start the simulation by clicking on the      Flights begin to appear in the PVT.
                                     Unfreeze button in the Simulation Time
                                     Control window




                                    Page 23 of 69
ACE / eDEP Gateway                                                                                                           Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                            D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  4    16:40:10    AEGT_IFPL_01   Examine NODL_1, a simple level flight,     Details are as follows:                       For AEG5B the relevant flight was
                                  in the PVT.                                                                              AEF5625.
                                                                             Start time, ETD: 16:44:50, Origin:
                                                                             LEAM, Destination: EDDL, RFL: 310,
                                                                             IFL: 310, CFL: 310, SSR code: 6251, SSR
                                                                             mode: A, Ac type: A320, Wake vortex:
                                                                             Medium, Cruise CAS: 285, Tail number
                                                                             & Airline: unknown.
                                                                             Route:  BIL, VADOM, TSU, BAU,
                                                                             XCLM, RINAX, MEDIX, ZEG, DIK.

  5    16:43:10    AEGT_IFPL_03   Examine ADS_2, a climbing flight, in the   Details are as follows:                       For AEG5B the relevant flight was
                                  PVT.                                                                                     AFR7220.
                                                                             Start time, ETD: 16:53:10, Origin: LFPG,
                                                                             Destination: EDDH, RFL: 350, IFL: 20,
                                                                             CFL: 250, SSR code: 1307, SSR mode: A,
                                                                             Ac type: B733, Wake vortex: Medium,
                                                                             Cruise CAS: 256, Tail number & Airline:
                                                                             unknown.
                                                                             Route: PGS, PERNO, RINAX, MEDIX,
                                                                             ZEG, DIK.
                                                                             Flight climbs up to its CFL.




                                  Page 24 of 69
ACE / eDEP Gateway                                                                                                         Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                          D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  6    16:43:10    AEGT_IFPL_04   Examine ADS3, a flight with a SID, in the   Details are as follows:                    For AEG5B no suitable aircraft was
                                  PVT.                                                                                   included in the scenario.
                                                                              Start time: 16:53:10, Origin: LFPG,
                                                                              Destination: EDDH, SID: PER1,
                                                                              RFL: 350, IFL: 20, CFL: 100,
                                                                              SSR code: 1307, SSR mode: A,
                                                                              Ac type: B733, Wake vortex: Medium,
                                                                              Cruise CAS 256, Airline:
                                                                              SONORAV_____
                                                                              Route: SID points : LFPG_09, CDG,
                                                                              REM, plus PGS, PERNO, RINAX,
                                                                              MEDIX, ZEG, DIK.
                                                                              Flight climbs SID.                         The flight cannot make the correct
                                                                                                                         altitude for all the SID points (but
                                                                                                                         neverthe less, it does try).

  7    16:51:20    AEGT_IFPL_02   Examine DWLK_01, a descending flight,       Details are as follows:                    For AEG5B a different flight was used:
                                  in the PVT.                                                                            DLH4980 at 16:40:40.
                                                                              Start time: 17:01:20, Origin: LEMD,
                                                                              Destination: EDDK, RFL: 310, IFL: 310,
                                                                              CFL: 310, SSR code: 1322, SSR mode: A,
                                                                              Ac type: CRJ1, Wake vortex: Medium,
                                                                              Cruise CAS: 277, Tail number & Airline:
                                                                              unknown.
                                                                              Route:  BIL, VADOM, TSU, BAU,
                                                                              XCLM, RINAX, MEDIX, ZEG, DIK.
                                                                              Flight descends to FL240 to meet an
                                                                              agreement at point DIK.




                                  Page 25 of 69
ACE / eDEP Gateway                                                                                                           Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                            D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  8     17:03:00   AEGT_IFPL_05      Examine SAS529, a flight with a STAR,    Details are as follows:                      For AEG5B no suitable aircraft was
                                     in the PVT.                                                                           included in the scenario.
                                                                              Start time: 17:13:00, Origin: ENFB,
                                                                              Destination: LFPG, STAR: SUN1, RFL:          The origin airport is not included in the
                                                                              330, IFL: 330, CFL: 330,                     AIRPORTS file. This causes the
                                                                              SSR code: 1333, SSR mode: A,                 remaining fields in the flight-plan pane
                                                                              Ac type: MD83, Wake vortex: Medium,          to remain blank too.
                                                                              Cruise CAS: 273, Airline:
                                                                              SCANDINAVIAN
                                                                              Route: NIK, CIV, NEBUL, TARIM,
                                                                              BIBOP, BSN, PGS plus STAR
                                                                              points:REM, CDG, LFPG_09.
                                                                              Flight descends STAR.




5.4    FLIGHT MANAGER (FM)

5.4.1 Phase 1
Scenario ID             AEGT_FM_A
Tested Functionality    The AEG proxy Flight Manager – various parts.
Objective               Demonstrate correct standard translation of the ACE events into eDEP trajectories
                        and constraints, and correct subsequent generation of Trajectory, System Flight
                        Plan, Sector Crossing List, Unit Crossing List, and Clearance events.
Dependencies
Resource File           pvt_ifpl_fm.gsdk, common_combined.gsdk




 Id.     Time          Test Case                     Actions                                 Expectations                                 Observations



                                     Page 26 of 69
ACE / eDEP Gateway                                                                                                           Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                            D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  1      N/A           -        Launch the ACE supervision on the Sun        The ACE platform is launched and the
                                machine (see 4.3.4), and select and start    AEG Gateway Launcher appears.
                                the EDEP simulation with the usual
                                exercise and run.

  2      N/A           -        Select                                 the   The AEG is launched and starts the eDEP
                                “componenttests/combined/pvt_ifpl_fm”        simulation engine and proxy components.
                                scenario, untick the MAFF option, tick the   The AEG Data Browser and PVT are
                                ‘Record Events’ option, browse and enter     displayed.
                                the filename AEGT_FM_A.log for the
                                Record File, and click on Run Test.

  3    16:40:00        -        Start the simulation by clicking on the
                                Unfreeze button in the Simulation Time
                                Control window

  4    16:44:50                                                              Flights begin to appear in the PVT.


  5   16:44:50+    AEGT_FM_01   Examine a selection of flights in the PVT.   The flights have correct speeds, times, and   The ACE FM does not generally
                                                                             have BCN/INI/COP/BOC/TOC/SOT/EOT              include SOT and EOT points in its
                                                                             etc. marked appropriately.                    trajectories, so these do not appear.

  6    16:46:40    AEGT_FM_06   Examine flight ADS_1 in the PVT.             Check the COP information for the sector      Currently, there are no flights that
                                                                             crossings.                                    include COP information in the ACE
                                                                                                                           event – all info is derived.
                                                                                                                           For AEG5B, flight BAW341 was used
                                                                                                                           at 16:54:00.

  7    16:53:10    AEGT_FM_03   Examine flight ADS3 in the PVT.              Agreement LFPG1 is shown against PGS.         For AEG5B, flight RAM871 was used
                                                                             A geographical point is included in the       at 16:45:10.
                                                                             trajectory with the same agreement and an
                                                                                                                           The agreement information is no
                                                                             altitude constraint at the RFL (350)
                                                                                                                           longer set at the geographical point
                                                                             applying to it.
                                                                                                                           (verified via CDB).




                                Page 27 of 69
ACE / eDEP Gateway                                                                                                    Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                     D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  8    16:53:10    AEGT_FM_02   Examine flight ADS3 in the PVT.       The SID is included in the trajectory with    The first SID fix is not included. (ACE
                                                                      the fixes marked appropriately.               FM feature.)
                                                                      The flights are at the correct altitudes at   The altitude constraint is not applied
                                                                      each SID fix.                                 on the first point. It is not present in the
                                                                                                                    ACE data (verified via CDB).
                                                                                                                    For AEG5B no suitable aircraft was
                                                                                                                    included in the scenario.

  9    16:53:10    AEGT_FM_04   Examine flights UPLK_01 and ADS3 in   Examine the sector and unit crossing          For AEG7A and AEG5B flight ADS_2
                   AEGT_FM_05   the PVT.                              details (vertical and horizontal).            was used, not ADS3.

 10    17:13:00    AEGT_FM_02   Examine flight SAS529 in the PVT.     The STAR is included in the trajectory        The last STAR fix is not included.
                                                                      with the fixes marked appropriately.          (ACE FM problem.)
                                                                      The flights are at the correct altitudes at   The altitude constraints are not met,
                                                                      each STAR fix.                                though it is tried – see note below.
                                                                                                                    For AEG5B no suitable aircraft was
                                                                                                                    included in the scenario.

 11    17:13:00    AEGT_FM_03   Examine flight SAS529 in the PVT.     The altitudes at points match those in        There is an unusual climb and re-
                                                                      Agreements: FL250 by 20Nm before              descent     after    the    mentioned
                                                                      TARIM      (TARIM_01),     FL80@BSN           agreements. This is due to bad route
                                                                      (BSN_01), FL20@PGS (PGS).                     construction     and    the  resulting
                                                                                                                    application of agreement REM_01 too.
                                                                                                                    For AEG5B flight DLH4980 was used
                                                                                                                    at 16:45:40.




                                Page 28 of 69
ACE / eDEP Gateway                                                                                                            Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                             D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




5.4.2 Phase 2
Scenario ID             AEGT_FM_B
Tested Functionality    The AEG proxy Flight Manager – various parts.
Objective               Demonstrate correct flying of trajectories, flight deletion, and controller orders
                        and subsequent changes to trajectories.
Dependencies
Resource File           aeg_edep_no_ias.gsdk, common_combined.gsdk




 Id.        Time       Test Case                      Actions                                Expectations                                  Observations

  1         N/A           -          Launch the ACE supervision on the Sun       The ACE platform is launched and the
                                     machine (see 4.3.4), and select and start   AEG Gateway Launcher appears.
                                     the EDEP simulation with the usual
                                     exercise and run.




                                     Page 29 of 69
ACE / eDEP Gateway                                                                                                       Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                        D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




  2      N/A           -        - Select the                              The AEG is launched and starts the eDEP
                                “componenttests/combined/aeg_edep_no_i    simulation engine and proxy components.
                                as” scenario,                             The AEG Data Browser, PVT and a CWP
                                - untick the MAFF option,                 are displayed.
                                - tick the ‘Record Events’ option,
                                - browse and enter the filename
                                AEGT_FM_B.log for the Record File
                                - in the Debug parameters field type:
                                  “-p AEG.CFL_VIA_IFPL FALSE”
                                - click on Run Test.

  3    16:40:00        -        Start the simulation by clicking on the   The time increments in the CWP toolbox.
                                Unfreeze button in the Simulation Time
                                Control window

  4    16:44:50    AEGT_FM_20                      -                      Flight NODL_1 appears on the PVD with        For AEG5B no suitable aircraft were
                                                                          a grey label (it is more than 10 minutes     included in the scenario.
                                                                          from sector entry).
                                                                          Flight NODL2 appears on the PVD with a
                                                                          grey label (it does not pass through our
                                                                          sector – UR).




                                Page 30 of 69
ACE / eDEP Gateway                                                                                                         Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                          D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  5    16:44:50    AEGT_FM_20                                            Flight NODL_1 appears on the PVD and            For AEG5B flight AEF5625 was used.
                                                                         in SIL WEST with a blue label.
                                                                         The details are correct and match those
                                                                         given in the PVT: flight enters sector from
                                                                         FS at BAU at 16:57 at FL310 and exits at
                                                                         ZEG.
                                                                         Time to sector entry is 12 minutes.
                                View the Extended Label Window and the   The details are correct and match those
                                Flight Legs.                             given in the PVT.
                                                                         ELW: Wake vortex: M, Speed: 460(T),
                                                                         RFL, PEL, CFL, XFL: 310, SSR: 6251,
                                                                         route: LEAM-EDDL, A320, Sector Exit:
                                                                         ZEG, next points: VADOM TSU.
                                                                         Times at points: 16:49, 16:54, 16:57,
                                                                         16:58, 17:05, 17:09, 17:13, 17:16               Speed, and consequently times,
                                                                                                                         differed for AEG7A (speed 450).

  6   16:46:20++   AEGT_FM_20                     -                      The flight moves along its trajectory.          The heading does not always match the
                                                                                                                         trajectory.
                                                                                                                         This is because is is interpolated
                                                                                                                         between the previous and next
                                                                                                                         trajectory points. The anomaly only
                                                                                                                         occurs when combining the AEG FM
                                                                                                                         and the standard eDEP IAS.




                                Page 31 of 69
ACE / eDEP Gateway                                                                                                 Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                  D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  7    16:52:30    AEGT_FM_14   Give DLPREAC a new PEL of 370.   The outbound co-ordination messge               The current delivery of eDEP has an
                                                                 appears in the Message OUT list and the         interim version of the new coordination
                                                                 proposed entry level is displayed in the        server, which does not generate the
                                                                 flight label in white.                          XFL order required for this test.
                                                                 After a few seconds, the trajectory updates     For AEG5B flight BAW745 was used
                                                                 with new levels at downstream waypoints         at 16:57:00.
                                                                 before the sector exit, and the flight climbs
                                                                 to the new level.
                                                                 The PEL in the flight label shows the new
                                                                 clearance, while the XFL remains
                                                                 unchanged. The VAW profile is updated.

  8   ~ 16:53:10   AEGT_FM_20                                    Flight ADS_2 appears in SIL WEST and            For AEG5B flight AFR7220 was used.
                                                                 on the PVD, flight ADS3 appears on the
                                                                 PVD. They have a conflict and an STCA
                                                                 alert is given.
                                View the PPD.                    The details, including conflict information,
                                                                 match those in the screenshot in Annex A.

  9   ~ 16:54:15   AEGT_FM_20                                    Flight ADS_1 becomes Assumable.                 For AEG5B flight RAM871 was used
                                                                                                                 at 16:51:20.
                                Assume ADS_1.                    The flight is assumed into the sector, is
                                                                 removed from the SIL, its label turns black
                                                                 on the PVD, and it can be given orders.

 10    16:54:30    AEGT_FM_12   Give ADS_1 a new CFL of 410.     The trajectory updates with new levels at       For AEG5B flight RAM871 was given
                                                                 downstream waypoints and the flight             a heading order at 16:52:00.
                                                                 climbs to the new level.
                                                                 The CFL and XFL in the flight label show
                                                                 the new clearance, and the VAW profile is
                                                                 updated.




                                Page 32 of 69
ACE / eDEP Gateway                                                                                                                Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                 D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 11    ~16:56:45                                     -                         Flight NODL_1 enters the sector without          For AEG5B flight TRA899 was used
                                                                               having been assumed.                             at 17:01:00.
                   AEGT_FM_20
                                Assume NODL_1 via the SIL                      The flight is assumed into the sector, is
                                                                               removed from the SIL, and its label turns
                                                                               black on the PVD.

 12    16:57:00    AEGT_FM_11   Give NODL_1 a heading order to leave its       The trajectory updates to reflect the order,     For AEG5B flight LXR4523 was given
                                current trajectory and rejoin at a later       the flight label includes the heading            a CFL order at 16:54:00.
                                point.                                         clearance, and the flight follows the new
                                                                               trajectory.
                                                                               The PVT shows the trajectory starting at
                                                                               ACPOS – the aircraft’s position at the time
                                                                               the order was given.

 13    16:59:00    AEGT_FM_13   Assume NODL_22.                                The trajectory updates to reflect the order,     For AEG7A flight ADS_2 was used at
                                                                               the flight label shows the heading               17:01:00.
                                Click on “ahdg” in the flight label and give
                                                                               clearance, and the flight follows the new
                                it an order to go direct to ZEG.                                                                For AEG5B flight DLH4980 was given
                                                                               trajectory.
                                                                                                                                a direct to BSN at 16:55:00.
                                                                               The PVT shows the trajectory starting at
                                                                               ACPOS – the aircraft’s position at the time
                                                                               the order was given.

 14    17:00:00    AEGT_FM_20   Release ADS_1.                                 The name of the next sector in the flight        For AEG5B flight LXR4523 was used
                                                                               label changes colour to dark red, and after      at 16:59:00.
                                                                               a few seconds so does the rest of the label.

 15    17:01:30    AEGT_FM_20                        -                         ADS_1 exits the sector.
                                                                               Its label goes grey.
                                                                               ADS_11 exits the sector.
                                                                               A “TRANSFER” reminder appears at the
                                                                               top of its label, but the rest doesn’t change
                                                                               colour.




                                Page 33 of 69
ACE / eDEP Gateway                                                                                                              Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                               D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 16   17:02:00     AEGT_FM_20   Click on the reminder to transfer ADS_11.     The name of the next sector in the flight       For AEG7A flight DLPREAC was
                                                                              label changes colour, and after a few           used at 17:11:30.
                                                                              seconds the whole label goes grey.
                                                                                                                              For AEG5B flight DLH4980 was used
                                                                                                                              at 17:03:15.

 17    17:02:30    AEGT_FM_14   Give NODL_1 a new XFL of 290.                 The outbound co-ordination messge               The current delivery of eDEP has an
                                                                              appears in the Message OUT list and the         interim version of the new coordination
                                                                              proposed exit level is displayed in the         server, which does not generate the
                                                                              flight label in white.                          XFL order required for this test.
                                                                              After a few seconds, the trajectory updates     For AEG5B flight AEF5625 was
                                                                              with new levels at the last two downstream      assumed and used at 16:56:30.
                                                                              waypoints and the flight descends to the
                                                                              new level before the sector exit.
                                                                              The XFL in the flight label shows the new
                                                                              clearance, and the VAW profile is
                                                                              updated.

 18    17:03:30    AEGT_FM_13   Assume DLPREAC.                               The trajectory updates to reflect the order,    For AEG5B flight LXR4523 was given
                                                                              the flight label shows the heading              a direct to BNE at 16:55:30.
                                Click on “CSU” in the flight label and give
                                                                              clearance, and the flight follows the new
                                it an order to go direct to MONUR.
                                                                              trajectory.
                                                                              The PVT shows the trajectory starting at
                                                                              ACPOS – the aircraft’s position at the time
                                                                              the order was given.

 19    17:05:00    AEGT_FM_16   Assume UPLK_01.                               The trajectory updates to reflect the order     For AEG5B flight BAW745 was used
                                                                              – the times on the points are updated.          at 16:59:30.
                                Give it a speed order.
                                                                              The flight label shows the speed clearance.




                                Page 34 of 69
ACE / eDEP Gateway                                                                              Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                               D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 20   ~ 17:12:30   AEGT_FM_21   -               ADS11 reaches the end of its flight - the     For AEG5B flight LXR4523 was used
                                                flight is deleted and disappears from the     at 17:10:00.
                                                PVD.
                                                                                              The flight will not currently be deleted
                                                                                              unless the AEG IAS component is also
                                                                                              present.
                                                                                              Flight remains in the PVT.

 21   17:13:00+    AEGT_FM_14   -               Verify that flight NODL_1 does indeed
                                                descend to the new level before the sector
                                                exit (from step 16).




                                Page 35 of 69
ACE / eDEP Gateway                                                                                                              Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                               D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




5.4.3 Phase 3
Scenario ID             AEGT_FM_C
Tested Functionality    The AEG proxy Flight Manager – CFL orders.
Objective               Demonstrate that CFL orders are implemented correctly when they don’t initiate
                        trajectory updates.
Dependencies
Resource File           aeg_edep_no_ias.gsdk, common_combined.gsdk




 Id.        Time       Test Case                     Actions                                   Expectations                                  Observations

  1         N/A           -         Launch the ACE supervision on the Sun       The ACE platform is launched and the
                                    machine (see 4.3.4), and select and start   AEG Gateway Launcher appears.
                                    the EDEP simulation with the usual
                                    exercise and run.

  2                                 - Select the                                The AEG is launched and starts the eDEP
                                    “componenttests/combined/aeg_edep_no_i      simulation engine and proxy components.
                                    as” scenario,                               The AEG Data Browser, PVT and a CWP
                                    - untick the MAFF option,                   are displayed.
                                    - tick the ‘Record Events’ option,
                                    - browse and enter the filename
                                    AEGT_FM_C.log for the Record File
                                    - click on Run Test.

  3     16:40:00          -         Start the simulation by clicking on the     The time increments on the Console and
                                    Unfreeze button in the Simulation Time      CWP toolbox.
                                    Control window

  4     16:45:30          -         Request flight NODL_1 on frequency.         The text “ROF” appears above the label
                                                                                for 10 seconds and then the flight becomes
                                                                                assumable.

                                    Page 36 of 69
ACE / eDEP Gateway                                                                                                      Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                       D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  5    16:45:45    AEGT_FM_12   Assume NODL_1.                                                                        For AEG5B flight RAM871 was used
                                                                                                                      at 16:52:00.
                                Give it a new CFL of 350.
                                Open the new InitialFPFullEvent for   The updated event shows the correct value
                                NODL_1 from the CORBA data browser.   of 350 for the initial conditions,
                                                                      ‘initial_cfl’, in place of the previous value
                                                                      of 310, but the flight’s trajectory has not
                                                                      changed.




                                Page 37 of 69
ACE / eDEP Gateway                                                                                                            Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                             D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




5.5  INTEGRATED AIR SURVEILLANCE (IAS)
Scenario ID        AEGT_IAS_A
Tested Functionality    The AEG proxy Integrated Air Surveillance.
Objective               Demonstrate correct standard translation of the ACE events into eDEP Track and
                        CAPData events.
Dependencies
Resource File           aeg_edep_standard.gsdk, common_combined.gsdk




 Id.     Time          Test Case                      Actions                                 Expectations                                 Observations

  1         N/A           -          Launch the ACE supervision on the Sun       The ACE platform is launched and the
                                     machine (see 4.3.4), and select and start   AEG Gateway Launcher appears.
                                     the EDEP simulation with the usual
                                     exercise and run.

  2                                  - Select the “componenttests/combined/      The AEG is launched and starts the eDEP
                                     aeg_edep_standard” scenario,                simulation engine and proxy components.
                                     - untick the MAFF option,                   The AEG Data Browser, PVT and a CWP
                                     - tick the ‘Record Events’ option,          are displayed.
                                     - browse and enter the filename
                                     AEGT_IAS_A.log for the Record File
                                     - click on Run Test.

  3    16:40:00           -          Start the simulation by clicking on the     The time increments on the Console and
                                     Unfreeze button in the Simulation Time      flights begin to appear in the PVT and
                                     Control window                              CWP.

  4    16:44:50->   AEGT_IAS_01      Examine and follow flight NODL_1.           The flight follows its trajectory with     For AEG5B flight AEF5625 was used
                                                                                 correct speed vectors and air speed.       at 16:45:00.



                                    Page 38 of 69
ACE / eDEP Gateway                                                                                                            Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                             D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  5   16:49:00->   AEGT_IAS_02   Examine and follow flight NODL_1            The flight follows its trajectory with         For AEG5B flight DLH4980 was used
                                 around the turn.                            correct speed vectors and air speed.           at 16:52:00.

  6   16:53:30->   AEGT_IAS_04   Examine and follow flight ADS31 as it       The flight follows its trajectory with         For AEG7A flight ADS_2 was used.
                                 climbs.                                     correct speed vectors.
                                                                                                                            For AEG5B flight AFR7220 was used
                                                                                                                            at 16:54:00.

  7   17:05:45->   AEGT_IAS_03   Examine and follow flight ADS31 as it       The climbing icon is displayed next to the     For AEG7A & AEG5B the flight was
                                 accelerates and climbs again, and becomes   AFL in the flight label.                       already advanced in the previous step.
                                 ‘Advanced’ in the sector.
                                                                             The speed value updates in the flight label,   For AEG7A flight ADS_2 was used.
                                                                             the length of the speed vector increases,
                                                                                                                            For AEG5B flight AFR7220 was used
                                                                             and the gap between the track history
                                                                                                                            at 17:02:35.
                                                                             markers increases (need to be zoomed in
                                                                             to notice).                                    Instant acceleration -> ACE problem!

  8   17:04:50->   AEGT_IAS_06   Examine and follow flight ADS31 as it       The flight follows its trajectory with         For AEG7A flight ADS_2 was used.
                                 turns while still climbing.                 correct speed vectors and air speed.
                                                                                                                            For AEG5B flight AFR7220 was used
                                                                                                                            at 17:04:50.

  9   17:21:15->   AEGT_IAS_05   Examine and follow flight SAS529 as it      The flight follows its trajectory with         For AEG5B flight DLH4980 was used
                                 descends.                                   correct speed vectors and the descending       at 16:59:00.
                                                                             icon appears next to the AFL in the flight
                                                                             label.




                                 Page 39 of 69
ACE / eDEP Gateway                                                                                                                 Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                 D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




5.6  FLIGHT PATH MONITOR (FPM)
Scenario ID        AEGT_FPM_A
Tested Functionality       The AEG proxy Flight Path Monitor.
Objective                  Demonstrate correct standard translation of the ACE events into eDEP
                           Sector/Unit Crossing, Waypoint Passed, and Deviation events.
Dependencies
Resource File              aeg_run_fpm.gsdk, common_integrated.gsdk, common.gsdk,                 on_pc.gsdk,
                           atcapp/resources/common/pvt_standalone_defaults.gsdk,                  on_sun.gsdk
                           fdps_ias_fpm.gsdk


For this test, ensure that the ACE TDM configuration file contains the following entries (see section 4.3.3 for details on how):
        TRACK_DEVIATION_COMPUTATION_PERIOD                                10
        TIME_DEVIATION_THRESHOLD_IS_ACTIVE                                TRUE
        TIME_DEVIATION_THRESHOLD                                          10
        ALTITUDE_DEVIATION_THRESHOLD_IS_ACTIVE                            TRUE
        ALTITUDE_DEVIATION_THRESHOLD                                      100
        LATERAL_DEVIATION_THRESHOLD_IS_ACTIVE                             TRUE
        LATERAL_DEVIATION_THRESHOLD                                       1.0
The ‘THRESHOLD_IS_ACTIVE’ item for all other deviation types should be set to FALSE.
Certain aircraft (notably AEF5625, BAW745, LXR4523), will not automatically appear in the MASS PWP. To transfer them to its control so they can be given
orders, perform the following steps using the Supervisor:
        -   Click ‘Flight_I’
        -   Select the current frequency of the flight – usually 126.11 – and click ‘OK’
        -   Select the required flight and click ‘Transfer’

                                         Page 40 of 69
ACE / eDEP Gateway                                                                                                                      Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                       D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



       -    Select the frequency to be transferred to – 135.61 – and click ‘OK’.


 Id.       Time          Test Case                        Actions                                    Expectations                                    Observations

  1        N/A              -           Launch the ACE supervision on the Sun       The ACE platform is launched and the
                                        machine (see 4.3.4), and select and start   AEG Gateway Launcher appears.
                                        the EDEP simulation with the usual
                                        exercise, and, to include the air system,
                                        run BGDTL_HJ_EC14EDEP.

  2        N/A                          - Select the                                The AEG is launched and starts the eDEP
                                        “componenttests/combined/aeg_edep_fpm       simulation engine and proxy components.
                                        ” scenario,
                                                                                    The eDEP Console, PVT, a CWP and two
                                        - untick the MAFF option,
                                                                                    Deviation Monitor windows are displayed.
                                        - tick the ‘Record Events’ option,
                                        - browse and enter the filename
                                        AEGT_FPM_A.log for the Record File
                                        - in the Debug parameters field type “-p
                                        FPM.DEBUG_APP TRUE”
                                        - click on Run Test.

  3    16:40:00             -           Start the simulation by clicking on the     The time increments on the Console and
                                        Unfreeze button in the Simulation Time      flights begin to appear in the PVT and
                                        Control window                              CWP.

  4    16:45:05             -                                  -                    The first flights start.
                                                                                    Deviations with null magnitudes appear in
                                                                                    the ‘Catch All’ Deviation Monitor
                                                                                    window.

  5    16:45:05     AEGT_FPM_02         Examine the AEG debug output.               A Waypoint Passed event             has been      For AEG7A and              earlier,   flight
                                                                                    generated and distributed          for flights    AEF5625 was used.
                                                                                    NODL2, NODL21, NODL22              passing the
                                                                                    first point on their trajectory:   BIL at 305
                                                                                    seconds.


                                        Page 41 of 69
ACE / eDEP Gateway                                                                                                            Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                             D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  6                     -        Transfer flight NODL_1 to the MASS                                                         For AEG7A and              earlier,   flight
                                 PWP.                                                                                       AEF5625 was used.
      ~16:46:00                  Using the MASS PWP, change the level of    The flight starts to climb.
                                 flight NODL_1 to FL330.

  7   ~16:46:30    AEGT_FPM_03                      -                       After NODL_1 has climbed more than 300          For AEG7A and earlier, flight
                                                                            feet a level deviation is shown for it in the   AEF5625 was used.In subsequent
                                                                            standard Deviation Monitor window.              updates the vertical deviation shown
                                                                                                                            varies randomly and is rarely the
                                                                                                                            expected 2000ft.
                                                                                                                            ACE issue: the values are used as
                                                                                                                            supplied.

  8                              Transfer flight NODL_21 to the MASS                                                        For AEG7A and              earlier,   flight
                                 PWP.                                                                                       LXR4523 was used.
      ~16:47:00                  Using the MASS PWP, put           flight   The flight turns to the new heading.
                                 NODL_21 on a heading of 360°.

  9   ~16:47:50    AEGT_FPM_04                      -                       After NODL_21 has strayed more than             For AEG7A and earlier, flight
                                                                            1nm from its planned trajectory a lateral       LXR4523 was used, for a deviation to
                                                                            deviation to the left is shown for it in the    the right.
                                                                            standard Deviation Monitor window.
                                                                            (Although the monitor’s filter is set to
                                                                            0.5nm, the ACE TDM threshold is set to
                                                                            1nm, so nothing below that is issued.)

 10                              Transfer flight NODL_22 to the MASS                                                        For AEG7A and              earlier,   flight
                                 PWP.                                                                                       BAW745 was used.
                                                                                                  -
      ~16:49:00                  Using the MASS PWP, increase the speed
                                 of flight NODL_22 to be Mach 0.85.

 11   ~16:50:00         -        Using the MASS PWP, decrease the speed                           -                         For AEG7A and              earlier,   flight
                                 of flight NODL_21 to be Mach 0.73.                                                         LXR4523 was used.




                                 Page 42 of 69
ACE / eDEP Gateway                                                                                                          Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                           D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 12   ~16:50:50    AEGT_FPM_05                      -                      After NODL_21 is more than 10s behind          For AEG7A and              earlier,   flight
                   AEGT_FPM_06                                             its planned trajectory a (negative)            LXR4523 was used.
                                                                           longitudinal deviation is shown for it, in
                                                                           addition to the lateral deviation, in the
                                                                           standard Deviation Monitor window.

 14   ~16:52:20    AEGT_FPM_05                      -                      After NODL_22 is more than 10s ahead of        For AEG7A and              earlier,   flight
                                                                           its planned trajectory a (positive)            BAW745 was used.
                                                                           longitudinal deviation is shown for it in
                                                                           the standard Deviation Monitor window.

 15   16:552:30    AEGT_FPM_01                                             Flight ADS11 crosses from sector FN to         For AEG7A and earlier, flight
                   AEGT_FPM_02                                             sector UR.                                     RAM781 was used, passing NEBUL at
                                                                                                                          750, from FS to UR.
                                                                           A Waypoint Passed event has been
                                 Examine the AEG debug output on the sun
                                                                           generated and distributed for flight
                                 machine.
                                                                           RAM871 passing ADS11 at 930 seconds.
                                                                           Sector and Unit crossing events have been
                                                                           generated and distributed for the crossing
                                                                           from FS to UR.

 16   ~16:54:00         -        Using the MASS PWP, turn flight ADS11                           -                        For AEG7A and earlier, flight
                                 10° to the right.                                                                        DLH4980 was used, turning to the left.

 17   ~16:54:30         -        Assume flight NODL21.                     The text “LAT DEV L” appears in its            For AEG7A and earlier, flight
                                                                           flight label.                                  LXR4523 was used, with a deviation to
                                                                                                                          the right.

 18   ~16:54:45         -        Assume flights ADS_1 & ADS11.                                   -


 19   ~16:55:00         -        Using the MASS PWP, change the level of   The flight starts to descend.                  For AEG7A and earlier, flight
                                 flight ADS_1 to FL360.                                                                   RAM781 was used, with FL320.




                                 Page 43 of 69
ACE / eDEP Gateway                                                                                                           Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                            D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 20   ~16:55:15    AEGT_FPM_04                      -                      After ADS_11 has strayed more than 1nm          For AEG7A and earlier, flight
                                                                           from its planned trajectory a lateral           DLH4980 was used, turning to the left.
                                                                           deviation to the right is shown for it in the
                                                                           standard Deviation Monitor window and
                                                                           “LAT DEV R” appears in its flight label.        The label text doesn’t always appear
                                                                                                                           immediately.

 21   ~16:55:20    AEGT_FPM_03                      -                      After ADS_1 has descended more than             For AEG7A and              earlier,   flight
                                                                           300 feet a (negative) level deviation is        RAM781 was used.
                                                                           shown for it in the standard Deviation
                                                                           Monitor window, and the text “FL BUST”
                                                                           appears in its flight label.

 22   ~16:56:00         -        Using the MASS PWP, change the level of   The flight starts to climb back up again.       For AEG7A and              earlier,   flight
                                 flight ADS_1 back to FL410.                                                               RAM781 was used.
                                                                                                                           FL BUST and FL DEV text appear in
                                                                                                                           flight label somewhat randomly due to
                                                                                                                           variations in the vertical deviation
                                                                                                                           value coming from ACE.

 23   ~16:57:00    AEGT_FPM_07                      -                      After ADS_1 had climbed back to within          For AEG7A and              earlier,   flight
                                                                           300 feet of its cleared level of 330, the       RAM781 was used.
                                                                           deviation for it disappears from the
                                                                           standard Deviation Monitor window.

 24   ~16:58:30         -        Using the MASS PWP, put flight                                                            For AEG7A and earlier, flight
                                 NODL22 on a heading direct to DIK and                                                     BAW745 was used, direct to PERNO.
                                 new level FL370.

 25   ~16:59:30    AEGT_FPM_06                                             The standard Deviation Monitor window           For AEG7A and earlier, flight
                                                                           shows a (negative) level deviation and a        BAW745 was used, with positive and
                                                                           lateral deviation to the left for NODL22.       right lateral deviations.
                                                                                                                           Deviation is shown to the right - ACE
                                                                                                                           data problem.

 26   ~17:00:00    AEGT_FPM_06   Assume flight NODL22                      The text “LAT DEV L FL BUST” appears            For AEG7A and              earlier,   flight
                                                                           in the flight label for NODL22.                 BAW745 was used.


                                 Page 44 of 69
ACE / eDEP Gateway                                    Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                     D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




                     Page 45 of 69
ACE / eDEP Gateway                                                                                                          Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                           D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




5.7    PILOT MANAGER (PM)


Scenario ID             AEGT_PM_A
Tested Functionality    The AEG proxy Pilot Manager.
Objective               Demonstrate correct translation of eDEP pilot orders to MASS pilot orders and
                        their successful execution.
Dependencies
Resource File           aeg_run_all.gsdk, common_integrated.gsdk, common.gsdk, on_pc.gsdk,
                        cwp_defaults.gsdk, atcapp/resources/common/cwp_defaults.gsdk,
                        atcapp/resources/common/fdps_defaults.gsdk,
                        atcapp/resources/common/pvt_standalone_defaults.gsdk, on_sun.gsdk
                        fdps_rdps.gsdk




 Id.     Time          Test Case                     Actions                                Expectations                                 Observations

  1         N/A           -         Launch the ACE supervision on the Sun       The ACE platform is launched and the
                                    machine (see 4.3.3), and select and start   AEG Gateway Launcher appears.
                                    the EDEP simulation with the usual
                                    exercise, and, to include the air system,
                                    run AEG_GND_RDPS_PWP.




                                    Page 46 of 69
ACE / eDEP Gateway                                                                                                            Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                           D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  2      N/A                    - Tick the ‘Combined Scenarios’ option     The AEG is launched and starts the eDEP
                                - select the                               simulation engine and proxy components.
                                “componenttests/combined/aeg_edep_all”     The PVT, and two CWPs are displayed.
                                scenario,
                                - untick the MAFF option,
                                - tick the ‘Record Events’ option,
                                - browse and enter the filename
                                AEGT_PM_A.log for the Record File
                                - in the Debug parameters field type “-p
                                AEG.CFL_VIA_IFPL FALSE”
                                - click on Run Test.

  3    16:40:00        -        Start the simulation by clicking on the    The time increments on the Console and
                                Unfreeze button in the Simulation Time     flights begin to appear in the PVT and
                                Control window                             CWPs.

  4    16:45:05        -                                                   The first flights start.


  5    16:46:00    AEGT_PM_01   In the hybrid CWP (unit FS) give flight    The trajectory updates to reflect the order,   For AEG7A and              earlier,   flight
                                NODL_1 an order to go direct to BAU.       and the flight follows the new trajectory.     AEF5625 was used.

  6    16:47:00    AEGT_PM_02   In the hybrid CWP give flight NODL2 a      The trajectory updates to reflect the order,   For AEG7A and earlier, flight
                                heading of 85 (the rejoin point is         and the flight starts following the new        BAW745 was used, with heading 320.
                                unimportant since only open heading        trajectory.
                                orders can be passed to ACE).

  7    16:48:00    AEGT_PM_03   In the hybrid CWP give flight NODL22 a     After a couple of radar updates the aircraft   For AEG7A and              earlier,   flight
                                new CFL of 370.                            begins to descend.                             LXR4523 was used.

  8    16:48:30    AEGT_PM_04   Assign NODL22 a ROCD of 1000fpm.           The label for the flight updates to show the   “         “
                                                                           clearance and its descent slows.
                                                                                                                          An AEG FM error message appears –
                                                                                                                          can’t send ROCD orders. This is ok.

  9    16:50:00    AEGT_PM_06   In the hybrid CWP give flight ADS11 a      The aircraft accelerates and after a few       For AEG7A and              earlier,   flight
                                speed order of 250 knots CAS.              scans its label shows an increased speed.      AEF5625 was used.



                                Page 47 of 69
ACE / eDEP Gateway                                                                                                           Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                            D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 10    16:51:00    AEGT_PM_07   In the hybrid CWP give flight ADS_1 a       The aircraft accelerates and after a few       For AEG7A and              earlier,   flight
                                speed order of 420 knots TAS.               scans its label shows an increased speed.      BAW745 was used.
                                                                                                                           The final speed value does not match
                                                                                                                           that expected – ACE reports 403 knots.

 11    16:52:00    AEGT_PM_05   In the hybrid CWP give flight NODL22 a      The aircraft decelerates and after a few       For AEG7A and              earlier,   flight
                                speed order of Mach 0.8.                    scans its label shows a reduced speed.         AEF5625 was used.

 12    16:53:00    AEGT_PM_08   In the hybrid CWP release flight ADS11.     The aircraft becomes assumeable in the         For AEG7A and              earlier,   flight
                                                                            main CWP and appears in the MASS               LXR4523 was used.
                                                                            PWP.

 13    16:53:30        -        In the main CWP assume flight ADS11.


 15    16:55:00        -        Give flight ADS11 a new CFL of 370 in       Both positions can now control the             For AEG7A and              earlier,   flight
                                the main CWP and in the MASS PWP.           aircraft.                                      DLH4980 was used.

 16    16:59:00    AEGT_PM_08   Release flight DLH4980 from the main        The aircraft becomes assumeable in the         For AEG8A no suitable aircraft exist.
                                CWP and transfer it to frequency 126.7 in   hybrid CWP and disappears from the
                                                                                                                           Consider adding a Hybrid CWP for
                                the MASS PWP.                               MASS PWP.
                                                                                                                           sector FN.
                                Assume the flight in the hybrid CWP.
                                                                            The flight becomes assumed in sector FS
                                                                            and can be given hybrid orders by the
                                Verify by giving the flight a new CFL of
                                                                            CWP.
                                200 in the hybrid CWP.
                                                                            The flight continues its descent to FL200.




                                Page 48 of 69
ACE / eDEP Gateway                                                                                                                Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




5.8   COORDINATION SERVER (CS)


Scenario ID                AEGT_CS_A
Tested Functionality       The AEG proxy Coordination Service.
Objective                  Demonstrate correct coordination functionality, interpretation and translation of
                           ACE SYSCO events into eDEP events, and conversion of eDEP coordination
                           actions into ACE SYSCO commands. Specifically looking at:
                                          -   Initialisation
                                          -   Standard Conditions Crossing
                                          -   Non-standard Conditions Crossing
                                          -   Counter-proposals
Dependencies
Resource File              EC04_plus_SYSCO.gsdk                      EC04_plus_SYSCO_3CWPs.gsdk
                           isa_sun.gsdk                              isa_pc.gsdk
                           isa_airspace_defaults.gsdk                isa_airspace_defaults.gsdk
                           isa_common.gsdk                           isa_cwp_defaults.gsdk
                           IPAS04_B_ISATST1_AIRSPACE.dat             isa_common.gsdk
                                                                     IPAS04_B_ISATST1_AIRSPACE.dat
                                                                     IPAS05_D_ISASYSCO_TRAFFIC.dat
                                                                     atcapp/resources/common/
                                                                     pvt_standalone_defaults.gsdk
                                                                     atcxapp/resources/common/
                                                                     scriptedevent_defaults.gsdk



The following table shows the expected initial values for various coordination data items, for each flight in each of the CWPs:


                                        Page 49 of 69
ACE / eDEP Gateway                                                                                                                       Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                        D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



                   Flight                       CWP:                    FS                                 UR                                   FN
                                State / Exit COP             Assumed              SEB                      n/a                    Not Concerned             n/a
                   FPL01        PEL / XFL                        n/a              200                                                     n/a                0
                                Prev / next sector               n/a               FN                                                     FS                n/a
                                State / Exit COP             Assumed              PIT            Inbound           MCG            Not Concerned             n/a
                   FPL02        PEL / XFL                        n/a              270               270                320                n/a                0
                                Prev / next sector               n/a               UR               FS                 n/a                FS                n/a
                                State / Exit COP             Assumed              PIT         Not Concerned            n/a        Not Concerned             n/a
                   FPL03        PEL / XFL                        n/a              270               200                 0                 n/a                0
                                Prev / next sector               n/a               UR               FS                 n/a                FS                n/a

                                                              Table 5-1 Expected Initial Coordination Values


 Id.    Time          Test Case                        Actions                                     Expectations                                       Observations

  1      N/A                -          Launch the ACE supervision on the         The ACE platform is launched and the AEG
                                       Sun machine (see 4.3.4), and select and   Gateway Launcher appears.
                                       start the EDEP simulation with the
                                       Exercise “EGSYSCO” and the Run
                                       “EGSYSCO_HB_EC13EDEP”.

  2      N/A                -          Select the “indra/combined/sysco”         The AEG is launched and starts the eDEP
                                       scenario, untick the MAFF option, tick    simulation engine and proxy components.
                                       the ‘Record Events’ option, browse and
                                                                                 The eDEP Console, PVT, and three CWPs are
                                       enter the filename AEGT_CS_A.log
                                                                                 displayed.
                                       for the Record File, and Run Test.

  4    15:00:00             -          Start the simulation by clicking on the   The time increments on the Console.
                                       Unfreeze button in the Simulation
                                       Time Control window

                                          Page 50 of 69
ACE / eDEP Gateway                                                                                                               Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  5    15:00:30    AEGT_CS_01                                           The first flights appear on the CWPs with no            This is expected behaviour due to the
                                                                        coordination information.                               synchronous nature of the ACE
                                                                                                                                components.

  6   15:00:30+    AEGT_CS_01                                           After a few seconds coordination information is
                                                                        displayed as detailed in Table 5-1 above.
                   AEGT_CS_03
                                An activation message is received for   In the FS CWP a change of XFL to 270 for FPL02
                                flight FPL02 into UR with non-          into UR appears in the message out window, and
                                standard conditions - a coordination    in the flightlabel the XFL is shown in white as
                                proposal is made.                       270.
                                                                        In the UR CWP a change of PEL from 310 to 270
                                                                        for FPL02 from FS appears in the message in
                                                                        window, FPL02 appears in the SIL entering from
                                                                        FS at 15:06 heading towards MCG and in the
                                                                        flightlabel the PEL is shown in white as 270.

  7    15:00:35    AEGT_CS_03   An ABI message for flight FPL02 into    No resulting changes to the displays.
                                FN is received.
                                                                        The event can be checked via the CDB, or a
                                                                        message in the AEG server log.

  8    15:01:30    AEGT_CS_03   In the UR CWP accept the proposed       The coordination messages disappear from the
                                level for flight FPL02 via the          Message In/Out windows, and the entry/exit levels
                                flightlabel.                            in the flightlabels are no longer white.
                                                                        No XFL order is sent to the ACE FM and there is
                                                                        no trajectory update.

  9    15:03:24    AEGT_CS_06   An activation message is received for   In the FS CWP a change of XFL to 270 for FPL03
                                flight FPL03 into UR with non-          into UR appears in the message out window, the
                                standard conditions - a coordination    flight is shown as releaseable, and in the
                                proposal is made.                       flightlabel the XFL is shown in white as 270.
                                                                        In the UR CWP a change of PEL from 250 to 270
                                                                        for FPL03 from FS appears in the message in
                                                                        window, FPL03 appears in the SIL entering from
                                                                        FS at 15:10 heading towards MCG, the flight is
                                                                        shown as inbound, and in the flightlabel the PEL is
                                                                        shown in white as 270.

                                  Page 51 of 69
ACE / eDEP Gateway                                                                                                               Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 10    15:03:45    AEGT_CS_06   In the UR CWP counter-propose a          In the FS CWP the message out for FPL03 is
                                level of 280 for flight FPL03.           replaced by a message in for a change of XFL
                                                                         from 270 to 280, and the XFL in the flightlabel is
                                                                         updated to 280.
                                                                         In the UR CWP the message in for FPL03 is
                                                                         replaced by a message out for a change of PEL to
                                                                         280, and the PEL in the flightlabel is updated to
                                                                         280.

 11    15:04:30    AEGT_CS_06   In the FS CWP accept the proposed        The coordination messages disappear from the
                                level for flight FPL03 via the Message   Message In/Out windows, the entry/exit levels in
                                In window.                               the flightlabels are no longer white, and in the UR
                                                                         CWP SIL the entry level for the flight updates to
                                                                         280.
                                                                         An XFL order is sent to the ACE FM and the
                                                                         trajectory is regenerated (events can be seen in the
                                                                         CORBA Data Browser).

 12    15:05:33    AEGT_CS_03   An activation message is received for    In the UR CWP a change of XFL to 320 for
                                flight FPL02 into FN with non-           FPL02 into FN appears in the message out
                                standard conditions - a coordination     windowand in the flightlabel the XFL is shown in
                                proposal is made.                        white as 320.
                                                                         In the FN CWP a change of PEL from 270 to 320          No COP information is given.
                                                                         for FPL02 from UR appears in the message in
                                                                         window, FPL02 appears in the SIL entering from
                                                                         FS at 15:12 heading towards MTD, the flight is
                                                                         shown as inbound, and in the flightlabel the PEL is
                                                                         shown in white as 320.

 13    15:05:40    AEGT_CS_03   Flight FPL02 starts to descend.          In the FS CWP the flight is shown as released.
                                In the FS CWP release the flight.        In the UR CWP the flight is shown as assumable.

 14    15:05:50    AEGT_CS_03   In the UR CWP assume the flight.         In the FS CWP the flight is shown as concerned.
                                                                         In the UR CWP the flight is shown as assumed,
                                                                         and its entry is removed from the SIL.


                                   Page 52 of 69
ACE / eDEP Gateway                                                                                                              Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                               D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 15    15:06:00    AEGT_CS_03   Flight FPL02 crosses from FS to UR.      In the FS CWP the flight is shown as not
                                                                         concerned.
                                                                         In the FN CWP FPL02 now appears in the SIL
                                                                         entering from UR.

 16    15:06:07    AEGT_CS_02   An ABI message for flight FPL01 into                             -
                                FN is received.

 17    15:07:00    AEGT_CS_03   In the FN CWP accept the proposed        The coordination messages disappear from the
                                level for flight FPL02 via the SIL.      Message In/Out windows, and the entry/exit levels
                                                                         in the flightlabels are no longer white.
                                                                         No XFL order is sent to the ACE FM and there is
                                                                         no trajectory update.

 18    15:10:45    AEGT_CS_06   After flight FPL03 has climbed up into   In the FS CWP the flight is shown as released.
                                sector UR, release it in the FS CWP.
                                                                         In the UR CWP the flight is shown as assumable.

 19    15:11:00    AEGT_CS_06   In the UR CWP assume flight FPL03.       In the FS CWP the flight is shown as not
                                                                         concerned.
                                                                         In the UR CWP the flight is shown as assumed,
                                                                         and its entry is removed from the SIL.

 20    15:11:10    AEGT_CS_03   In the UR CWP release flight FPL02.      In the UR CWP the flight is shown as released.
                                                                         In the FN CWP the flight is shown as assumable.

 21    15:11:20    AEGT_CS_03   In the FN CWP assume flight FPL02.       In the UR CWP the flight is shown as concerned.
                                                                         In the FN CWP the flight is shown as assumed,
                                                                         and its entry is removed from the SIL.

 22    15:15:06    AEGT_CS_02   An activation message is received for    In the FS CWP the flight is shown as releaseable.     Currently non-standard conditions, so
                                flight FPL01 into FN, with standard                                                            messages changing level from 200 to
                                                                         In the FN CWP FPL01 appears in the SIL entering
                                conditions.                                                                                    200, and need to accept level.
                                                                         from FS at 15:22 heading towards RUWER, and
                                                                         the flight is shown as inbound.                       No COP information is given.



                                  Page 53 of 69
ACE / eDEP Gateway                                                                                                           Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                            D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 23    15:17:00    AEGT_CS_02   In the UR CWP release flight FPL01.   In the FS CWP the flight is shown as released.
                                                                      In the FN CWP the flight is shown as assumable.

 24    15:17:15    AEGT_CS_02   In the FN CWP assume the flight.      In the FS CWP the flight is shown as concerned.
                                                                      In the FN CWP the flight is shown as assumed,
                                                                      and its entry is removed from the SIL.




                                  Page 54 of 69
ACE / eDEP Gateway                                                                                                          Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                           D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




Scenario ID            AEGT_CS_B
Tested Functionality   The AEG proxy Coordination Service.
Objective              Demonstrate correct coordination functionality, interpretation and translation of
                       ACE SYSCO events into eDEP events, and conversion of eDEP coordination
                       actions into ACE SYSCO commands. Specifically looking at:
                                     -   Standard Conditions Coordination (Automatic acceptance)
                                     -   Non-standard Conditions Coordination
                                     -   Reject Coordination
                                     -   Parallel Coordination
                                     -   Request On Frequency
                                     -   Force Activation
Dependencies
Resource File          EC04_plus_SYSCO.gsdk                      EC04_plus_SYSCO_3CWPs.gsdk
                       isa_sun.gsdk                              isa_pc.gsdk
                       isa_airspace_defaults.gsdk                isa_airspace_defaults.gsdk
                       isa_common.gsdk                           isa_common.gsdk
                       IPAS04_B_ISATST1_AIRSPACE.dat             isa_cwp_defaults.gsdk
                                                                 IPAS04_B_ISATST1_AIRSPACE.dat
                                                                 IPAS05_D_ISASYSCO_TRAFFIC.dat
                                                                 atcapp/resources/common/
                                                                 pvt_standalone_defaults.gsdk
                                                                 atcxapp/resources/common/
                                                                 scriptedevent_defaults.gsdk




                                    Page 55 of 69
ACE / eDEP Gateway                                                                                                                  Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                   D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 Id.     Time        Test Case                   Actions                                      Expectations                                       Observations

  1      N/A            -        Launch the ACE supervision on the         The ACE platform is launched and the AEG
                                 Sun machine (see 4.3.4), and select and   Gateway Launcher appears.
                                 start the EDEP simulation with the
                                 Exercise “EGSYSCO” and the Run
                                 “EGSYSCO_HB_EC13EDEP”.

  2      N/A            -        Select the “indra/combined/sysco”         The AEG is launched and starts the eDEP
                                 scenario, untick the MAFF option, tick    simulation engine and proxy components.
                                 the ‘Record Events’ option, browse and
                                                                           The eDEP Console, PVT, and three CWPs are
                                 enter the filename AEGT_CS_B.log
                                                                           displayed.
                                 for the Record File, and Run Test.




  4    15:00:00         -        Start the simulation by clicking on the   The time increments on the Console.
                                 Unfreeze button in the Simulation
                                 Time Control window

  5    15:00:30         -                           -                      The first flights appear on the CWPs.


  6    15:00:35+   AEGT_CS_08                       -                      In the FS CWP a change of XFL to 270 for FPL02
                                                                           into UR appears in the message out window, and
                                                                           in the flightlabel the XFL is shown in white as
                                                                           270.
                                                                           In the UR CWP a change of PEL from 310 to 270
                                                                           for FPL02 from FS appears in the message in
                                                                           window, FPL02 appears in the SIL entering from
                                                                           FS at 15:06 heading towards MCG, and in the
                                                                           flightlabel the PEL is shown in white as 270.

  7    15:00:35    AEGT_CS_08    An ABI message for flight FPL02 into                              -
                                 FN is received.



                                    Page 56 of 69
ACE / eDEP Gateway                                                                                                               Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 87    15:02:20    AEGT_CS_08   In the UR CWP counter-propose a           In the FS CWP the message out for FPL02 is
                                level of 300 for flight FPL02.            replaced by a message in for a change of XFL
                                                                          from 320 to 300, and the XFL in the flightlabel is
                                                                          updated to 300.
                                                                          In the UR CWP the message in for FPL02 is
                                                                          replaced by a message out for a change of PEL
                                                                          from 320 to 300, and the PEL in the flightlabel is
                                                                          updated to 300.

  9    15:03:24    AEGT_CS_07   An activation message is received for     In the FS CWP a change of XFL to 270 for FPL03
                                flight FPL03 into UR with non-            into UR appears in the message out window, the
                                standard conditions - a coordination      flight is shown as releaseable, and in the
                                proposal is made.                         flightlabel the XFL is shown in white as 270.
                                                                          In the UR CWP a change of PEL from 250 to 270
                                                                          for FPL03 from FS appears in the message in
                                                                          window, FPL03 appears in the SIL entering from
                                                                          FS at 15:10 heading towards MCG, the flight is
                                                                          shown as inbound, and in the flightlabel the PEL is
                                                                          shown in white as 270.

 10    15:03:20    AEGT_CS_11   In the UR CWP force activation of         In the UR CWP a change of XFL to 320 for
                                flight FPL02 (into FN).                   FPL02 into FN appears in the message out
                                                                          window, and in the flightlabel the XFL is shown in
                                The     crossing   has    non-standard
                                                                          white as 320.
                                conditions - a coordination proposal is
                                made.                                     In the FN CWP a change of PEL from 270 to 320         No COP information is displayed.
                                                                          for FPL02 from UR appears in the message in
                                                                          window, FPL02 appears in the SIL entering from
                                                                          FS at 15:13 heading towards MTD, the flight is
                                                                          shown as inbound, and in the flightlabel the PEL is
                                                                          shown in white as 320.

 11    15:03:30    AEGT_CS_08   In the FN CWP accept the coordination     The relevant coordination messages for FPL02
                                proposal for flight FPL02.                disappear from the Message In/Out windows in
                                                                          the UR and FN CWPs, and the relevant entry/exit
                                                                          levels in the flightlabels are no longer white.



                                   Page 57 of 69
ACE / eDEP Gateway                                                                                                               Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 12    15:03:40    AEGT_CS_08   In the UR CWP request an XFL of 300     In the UR CWP a change of XFL to 300 for
                                for flight FPL02.                       FPL02 into FN appears in the message out
                                                                        window, and in the flightlabel the XFL is shown in
                                                                        white as 300.
                                                                        In the FN CWP a change of PEL from 320 to 300
                                                                        for FPL02 from UR appears in the message in
                                                                        window, and in the flightlabel the PEL is shown in
                                                                        white as 300.

 13    15:03:50    AEGT_CS_08   In the FS CWP accept the coordination   The relevant coordination messages disappear
                                for flight FPL02 to UR.                 from the Message In/Out windows, and the
                                                                        relevant entry/exit levels in the flightlabels are no
                                                                        longer white.
                                                                        An XFL order is sent to the ACE FM and the
                                                                        trajectory is modified to descend to FL300 by the
                                                                        FS->UR boundary.

 14    15:04:00    AEGT_CS_08   In the FN CWP accept the coordination   The relevant coordination messages disappear
                                for flight FPL02 from UR.               from the Message In/Out windows, the relevant
                                                                        entry/exit levels in the flightlabels are no longer
                                                                        white, and in the FN CWP SIL the entry level for
                                                                        the flight updates to 300.
                                                                        An XFL order is sent to the ACE FM and the
                                                                        trajectory is modified to remain at FL300 after the
                                                                        FS->UR boundary.

 15    15:04:30    AEGT_CS_07   In the UR CWP reject the proposed       The coordination messages disappear from the            Flight can no longer be coordinated
                                level for flight FPL03.                 Message In/Out windows, and the entry level in          due to ACE SYSCO manual
                                                                        the UR CWP flightlabel is no longer shown white.        coordination phase.

 16    15:05:30        -        Transfer/Assume flight FPL02 from FS                              -
                                to UR.

 17    15:06:07        -        An ABI message for flight FPL01 into                              -
                                FN is received.



                                  Page 58 of 69
ACE / eDEP Gateway                                                                                                                Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                 D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 18    15:07:00        -        Transfer/Assume flight FPL03 from FS                            -                                Unable to transfer because of above.
                                to UR.
                                                                                                                                 (This step not valid in replay mode.)

 19    15:12:00        -        Transfer/Assume flight FPL02 from                               -
                                UR to FN.

 20    15:14:20    AEGT_CS_11   In the FS CWP force the activation of   In the FS CWP the flight is shown as releaseable.        (These steps can now be done earlier.)
                                flight FPL01.
                                                                        In the FN CWP FPL01 appears in the SIL entering          Currently non-standard conditions.
                                The crossing has standard conditions.   from FS at 15:18 heading towards RUWER, and
                                                                        the flight is shown as inbound.

 21    15:14:30    AEGT_CS_05   In the FN CWP request a PEL of 190      In the FN CWP a message to FS for a change of
                                for flight FPL01.                       PEL from 200 to 190 for FPL01 appears in the
                                                                        message out window, and in the flightlabel the
                                                                        PEL is shown in white as 190.
                                                                        In the FS CWP a message from FN for a change of
                                                                        XFL from 200 to 190 for FPL01 appears in the
                                                                        message in window, and in the flightlabel the XFL
                                                                        is shown in white as 190.

 22    15:14:40    AEGT_CS_05   In the FS CWP accept the coordination   The coordination messages disappear from the
                                for flight FPL01.                       Message In/Out windows, and in the FN CWP SIL
                                                                        the entry level for the flight updates to 190.
                                                                        An XFL order is sent to the ACE FM and the
                                                                        trajectory is modified to descend to FL190 by the
                                                                        sector boundary.

 23    15:15:00    AEGT_CS_04   In the FS CWP request an XFL of 200     The    coordination     request     is      accepted     Currently non-standard conditions so
                                for flight FPL01.                       automatically:                                           no automatic acceptance.
                                                                        No messages appear in the Message In/Out
                                                                        windows.
                                                                        In the FS CWP SIL the entry level for the flight
                                                                        updates to 200
                                                                        An XFL order is sent to the ACE FM and the
                                                                        trajectory is modified to remain at FL200.

                                   Page 59 of 69
ACE / eDEP Gateway                                                                                                            Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                             D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 24    15:15:30    AEGT_CS_10   In the FN CWP request flight FPL01     ROF appears in white above the flight label in
                                on frequency.                          CWPs FS and FN.

 25    15:15:40    AEGT_CS_10   In the FS CWP transfer flight FPL01.   In the FS CWP the flight is shown as released.
                                                                       In the FN CWP the flight is shown as assumable.

 26    15:15:50    AEGT_CS_10   In the FN CWP assume flight FPL01.     In the FS CWP the flight is shown as concerned.
                                                                       In the FN CWP the flight is shown as assumed,
                                                                       and its entry is removed from the SIL.




                                  Page 60 of 69
ACE / eDEP Gateway                                                                                                          Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                           D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




Scenario ID            AEGT_CS_C
Tested Functionality   The AEG proxy Coordination Service.
Objective              Demonstrate correct coordination functionality, interpretation and translation of
                       ACE SYSCO events into eDEP events, and conversion of eDEP coordination
                       actions into ACE SYSCO commands. Specifically looking at:
                                     -   Coordination Abrogation
                                     -   FM Direct Order causing time shift
                                     -   FM Direct Order causing change of crossing point
Dependencies
Resource File          EC04_plus_SYSCO.gsdk                     EC04_plus_SYSCO_3CWPs.gsdk
                       isa_sun.gsdk                             isa_pc.gsdk
                       isa_airspace_defaults.gsdk               isa_airspace_defaults.gsdk
                       isa_common.gsdk                          isa_common.gsdk
                       IPAS04_B_ISATST1_AIRSPACE.dat            isa_cwp_defaults.gsdk
                                                                IPAS04_B_ISATST1_AIRSPACE.dat
                                                                IPAS05_D_ISASYSCO_TRAFFIC.dat
                                                                atcapp/resources/common/
                                                                pvt_standalone_defaults.gsdk
                                                                atcxapp/resources/common/
                                                                scriptedevent_defaults.gsdk




                                    Page 61 of 69
ACE / eDEP Gateway                                                                                                                  Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                   D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




 Id.     Time        Test Case                   Actions                                      Expectations                                       Observations

  1      N/A            -        Launch the ACE supervision on the         The ACE platform is launched and the AEG
                                 Sun machine (see 4.3.4), and select and   Gateway Launcher appears.
                                 start the EDEP simulation with the
                                 Exercise “EGSYSCO” and the Run
                                 “EGSYSCO_HB_EC13EDEP”.

  2      N/A            -        Select the “indra/combined/sysco”         The AEG is launched and starts the eDEP
                                 scenario, untick the MAFF option, tick    simulation engine and proxy components.
                                 the ‘Record Events’ option, browse and
                                                                           The eDEP Console, PVT, and three CWPs are
                                 enter the filename AEGT_CS_C.log
                                                                           displayed
                                 for the Record File, and Run Test.




  4    15:00:00         -        Start the simulation by clicking on the   The time increments on the Console.
                                 Unfreeze button in the Simulation
                                 Time Control window

  5    15:00:30         -                                                  The first flights appear on the CWPs.


  6    15:00:30+        -        An activation message is received for
                                 flight FPL02 into UR with non-
                                 standard conditions - a coordination
                                 proposal is made.

  7    15:01:30         -        In the UR CWP accept the proposed
                                 level for flight FPL02.

  8    15:03:25         -        An activation message is received for
                                 flight FPL03 into UR with non-
                                 standard conditions - a coordination
                                 proposal is made.


                                    Page 62 of 69
ACE / eDEP Gateway                                                                                                            Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                             D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



  9    15:03:45    AEGT_CS_09   In the UR CWP counter-propose a
                                level of 190 for flight FPL03.

 10    15:04:00    AEGT_CS_09   In the FS CWP accept the proposed      The trajectory is updated and the flight no longer    The flight remains in the UR CWP
                                level for flight FPL03.                passes through sector UR.                             SIL (though Not concerned), and is
                                                                                                                             still releasable in the FS CWP.
                                                                       In the UR CWP the flight is now shown as Not
                                                                       concerned.                                            (This is the same behaviour as for
                                                                                                                             running eDEP standalone.)

 11    15:04:15        -        Transfer/Assume flight FPL02 from FS
                                to UR.

 12    15:04:30    AEGT_CS_14   In the UR CWP, order flight FPL02 to   The trajectory is updated and the exit time from
                                go direct to MCG.                      the sector (at MCG) is brought forward resulting
                                                                       in an activation message and coordination
                                                                       proposal for flight FPL02 into FN:
                                                                       In the UR CWP a change of XFL to 320 for
                                                                       FPL02 into FN appears in the message out
                                                                       window, and in the flightlabel the XFL is shown in
                                                                       white as 320.
                                                                       In the FN CWP a change of PEL from 270 to 320         No COP information is displayed.
                                                                       for FPL02 from UR appears in the message in
                                                                       window, FPL02 appears in the SIL entering from
                                                                       UR at 15:11 heading towards MTD, the flight is
                                                                       shown as inbound, and in the flightlabel the PEL is
                                                                       shown in white as 320.

 13    15:05:09    AEGT_CS_15   An ABI message for flight FPL03 into                            -
                                FN is received.

 14    15:06:00    AEGT_CS_15   In the FS CWP, order flight FPL03 to   The trajectory is updated and the flight now          ACE error?: flight no longer descends
                                go direct to LEQ.                      transits from FS to FN at a different point.          to agreed XFL 190.




                                  Page 63 of 69
ACE / eDEP Gateway                                                                                                               Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 15    15:06:00+   AEGT_CS_15    An activation message for flight FPL03   In the FS CWP the flight is shown as releaseable.     Currently non-standard conditions.
                                 into FN is received with standard
                                                                          In the FN CWP FPL03 appears in the SIL entering       No COP information is given
                                 conditions.
                                                                          from FS at 15:12 heading towards BNE, and the
                                                                          flight is shown as inbound.




Scenario ID            AEGT_CS_D
Tested Functionality   The AEG proxy Coordination Service.
Objective              Demonstrate correct coordination functionality, interpretation and translation of
                       ACE SYSCO events into eDEP events, and conversion of eDEP coordination
                       actions into ACE SYSCO commands. Specifically looking at:
                                     -   Coordination Timeout
                                     -   FM Direct Order causing abrogation
                                     -   Route coordination from downstream 18
                                     -   Route coordination from upstream 19
Dependencies
Resource File          EC04_plus_SYSCO.gsdk                       EC04_plus_SYSCO_3CWPs.gsdk
                       isa_sun.gsdk                               isa_pc.gsdk
                       isa_airspace_defaults.gsdk                 isa_airspace_defaults.gsdk
                       isa_common.gsdk                            isa_common.gsdk
                       IPAS04_B_ISATST1_AIRSPACE.dat              isa_cwp_defaults.gsdk
                                                                  IPAS04_B_ISATST1_AIRSPACE.dat
                                                                  IPAS05_D_ISASYSCO_TRAFFIC.dat
                                                                  atcapp/resources/common/
                                                                  pvt_standalone_defaults.gsdk
                                                                  atcxapp/resources/common/
                                                                  scriptedevent_defaults.gsdk

                                    Page 64 of 69
ACE / eDEP Gateway                                                                                                                  Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                   D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




 Id.     Time        Test Case                   Actions                                      Expectations                                       Observations

  1      N/A            -        Launch the ACE supervision on the         The ACE platform is launched and the AEG
                                 Sun machine (see 4.3.4), and select and   Gateway Launcher appears.
                                 start the EDEP simulation with the
                                 Exercise “EGSYSCO” and the Run
                                 “EGSYSCO_HB_EC13EDEP”.

  2      N/A            -        Select the “indra/combined/sysco”         The AEG is launched and starts the eDEP
                                 scenario, untick the MAFF option, tick    simulation engine and proxy components.
                                 the ‘SYSCO Interface’ and ‘Record
                                                                           The eDEP Console, PVT, and three CWPs are
                                 Events’ options, browse and enter the
                                                                           displayed.
                                 filename AEGT_CS_D.log for the
                                 Record File, and Run Test.




  4    15:00:00         -        Start the simulation by clicking on the   The time increments on the Console.
                                 Unfreeze button in the Simulation
                                 Time Control window

  5    15:00:30         -                                                  The first flights appear on the CWPs.


  6    15:00:30+   AEGT_CS_12    An activation message is received for     Do not accept or reject the proposal.
                                 flight FPL02 into UR with non-
                                 standard conditions - a coordination
                                 proposal is made.

  7    15:01:00    AEGT_CS_16    In the FS CWP, order flight FPL03 to      The trajectory is updated and the flight no longer
                                 go direct to BNE.                         passes through sector UR.

  8    15:01:00    AEGT_CS_16    An ABI message for flight FPL03 into      -
                                 FN is received.




                                    Page 65 of 69
ACE / eDEP Gateway                                                                                                              Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                               D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 98    15:02:35    AEGT_CS_12   The coordination proposal for flight     The event can be seen in the CORBA Data               The AEG does not handle timeouts –
                                FPL02 from FS to UR times out.           Browser and a message is output to the AEG log.       the flight can no longer be
                                                                                                                               coordinated.

 10    15:03:10    AEGT_CS_16   An activation message for flight FPL03   In the FS CWP the flight is shown as releaseable.     Currently non-standard conditions, so
                                into FN is received with standard                                                              messages changing level from 270 to
                                                                         In the FN CWP FPL03 appears in the SIL entering
                                conditions.                                                                                    270, and need to accept level
                                                                         from FS at 15:10 heading towards BNE, and the
                                                                         flight is shown as inbound.

 11   15:03:30->   AEGT_CS_17   Use the SIW to send coordination         The displays update as if the commands had been
                                commands to ACE SYSCO directly           entered via usual CWP interactions.
                                from the AEG rather than from a CWP,
                                e.g.
                                FPL03, Controller 21 FN,
                                Coordination Counter Proposal, Level
                                250, Send command from downstream
                                FPL03, Controller 22 FS,
                                Coordination Acceptance,
                                Send command from upstream


 12    15:04:10    AEGT_CS_18   In the FN CWP edit the trajectory for    Working trajectory is displayed along with menu
                                FPL03 so it significantly changes the    to Propose, Close, or Cancel the new trajectory.
                                crossing from FS.

 13    15:04:20    AEGT_CS_18   Propose the new trajectory.              In the FN CWP the proposed trajectory is
                                                                         displayed in white alongside the current system
                                                                         trajectory, and a TRAJ message to FS appears in
                                                                         the message out window.
                                                                         In the FS CWP the proposed trajectory is
                                                                         displayed in white alongside the current system
                                                                         trajectory, and a TRAJ message from FN appears
                                                                         in the message in window.




                                   Page 66 of 69
ACE / eDEP Gateway                                                                                                             Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                              D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



 14    15:04:40    AEGT_CS_18   In the FS CWP accept the new              In both CWPs the new trajectory is now displayed
                                trajectory.                               in green in place of the previous one, and the
                                                                          messages disappear from the message in/out
                                                                          windows.

 15    15:06:07    AEGT_CS_19   An ABI message for flight FPL01 into      -
                                FN is received.

 16    15:06:45    AEGT_CS_19   In the FS CWP force activation of         In the FN CWP a change of PEL appears in the
                                flight FPL01 (into FN).                   message in window.
                                The     crossing   has    non-standard
                                conditions - a coordination proposal is
                                made.

 17    15:07:00    AEGT_CS_19   In the FN CWP accept the level change
                                for FPL01.

 18    15:07:10    AEGT_CS_19   In the FS CWP edit the trajectory for     Working trajectory is displayed along with menu
                                FPL01 so it significantly changes the     to Propose, Close, or Cancel the new trajectory.
                                crossing into FN.

 19    15:07:15    AEGT_CS_19   Propose the new trajectory.               In the FS CWP the proposed trajectory is
                                                                          displayed in white alongside the current system
                                                                          trajectory, and a TRAJ message to FN appears in
                                                                          the message out window.
                                                                          In the FN CWP the proposed trajectory is
                                                                          displayed in white alongside the current system
                                                                          trajectory, and a TRAJ message from FS appears
                                                                          in the message in window.

 20    15:07:25    AEGT_CS_19   In the FN CWP accept the new              In both CWPs the new trajectory is now displayed
                                trajectory.                               in green in place of the previous one, and the
                                                                          messages disappear from the message in/out
                                                                          windows.

 21      ???       AEGT_CS_13                                                                                                 Re-entrant flights cannot currently be
                                                                                                                              tested as no suitable flight exists in the
                                                                                                                              ACE scenario.

                                   Page 67 of 69
ACE / eDEP Gateway                                    Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                     D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc




                     Page 68 of 69
ACE / eDEP Gateway                                                                                                                 Reference GL/AEG/TR/2/3.0 Draft 1
27 November 2011                                                                                                  D:\Docstoc\Working\pdf\ee095b73-e023-4b53-9442-ccb7a0eaf9f5.doc



A. ANNEX 1 – SCREEN CAPTURES
The following diagram shows the expected details for step 11 in the second phase of the FM testing (see 5.4.2).




                                        Page 69 of 69

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:5
posted:11/27/2011
language:English
pages:69