These applications were developed for the EVP (European Validation Platform) project.

The eDEP AMAN was built for:

• concept demonstration purposes
• pre-simulation training purposes
• integrated ground tool experiments using AMAN, DMAN, and EMAN

The eDEP AMAN includes the following functionality

• EATMP ACC CWP incorporating the AMAN time-to-lose information
• EATMP APP CWP incorporating the AMAN runway schedule information
• simple AMAN component
  • sequence list (first-come-first-served basis)
  • time-to-lose information
  • ability to change sequence order
  • ability to change minimum separation distance
• EATMP Compliant Landing List Window (LLW)
• Extended Elastic Vector functionality (with time-that-will-be-lost)

The EVP EMAN functionality was added to eDEP to:

• experiment with various algorithms for spreading the AMAN's time-to-lose across all the ATC sectors traversed by an aircraft
• experiment giving the Planning Controller down-stream vision of the traffic consequences of modifying an aircraft's sector exit conditions by:
• showing expected down-stream traffic information for an aircraft
• showing probe down-stream traffic information for varying exit times and flight levels for an aircraft
• showing probe down-stream traffic information for alternate route segments for an aircraft

The following documents are relevant to the AMAN and EMAN work (shown in separate windows):

• AMAN Operation Specification from Orthogon - the delay sharing ideas were taken from here
• The Eurocontrol Landing List Window Specification defined by Poul JORGENSEN (EHQ)
• The EVP EMAN Prototype Specification compiled by RTC/Steve Owen and IAA/Christie Costello
• The EVP EMAN Prototype HMI Guide compiled by RTC/Steve Owen

A Windows/HTML Help utility has also been produced which mixes text, images, and movie clips to provide the beginnings of a useful CBT (Computer Based Training) package. This package is available in PC or web format and is included on the installation CD. Click here to see the web version of the Help package.

CWP with AMAN Landing List Window Click to see full size image

AMAN DEMO The AMAN tool without EMAN functionality may be seen by starting the EVP demo and selecting an ARLANDA exercise: Exercise as1t1_0920.gsdk shows 2 CWPs (1 ACC and 1 APP), demonstrating the Landing List Window as specified by Poul Jorgensen, and the modified ACC/APP aircraft labels. Exercise ut1_2.gsdk shows 4 CWPs on the way to ARLANDA airport (Sweden). The user can choose various delay-sharing algorithms (in the demo launcher) and see how the AMAN delay is shared out across the en-route sectors. The APP CWP contains the Landing List which sequences the aircraft on a first-come-first-served basis. The user may modify the landing separation (menu activated by mouse AB on Min.Distance button in header), or re-sequence an aircraft (mouse AB on a sequence number). The AMAN time-to-lose is shared out across the en-route sectors so that each controller only sees how much time is to be absorbed in his/her sector. The EVP launcher allows the user to select one of three delay-sharing algorithms. It may also be left OFF, in which case each controller sees the total time-to-lose remaining. The user may modify the heading/speed in order to absorb the requested time-to-lose in order to get the aircraft to the Initial Approach Fix at the right time. Additional information is also presented in the APP CWP aircraft label (runway sequence number, aircraft type, and runway).

CWP with EMAN down-stream traffic visualisation Click to see full size image

EMAN DEMO The AMAN tool with EMAN functionality may be seen by starting the EVP demo and selecting a SIX_STATES exercise: Exercise six_states_EOM_lite shows 4 CWPs with aircraft LNX925 entering sector NTM from the south-east and then passing into sector MAAS. The Planning Controller in NTM may: visualise down-stream traffic; probe the aircraft's exit conditions to see the effect on down-stream traffic; and probe an alternate route to see the effect on down-stream traffic. Exercise six_states_EOM shows the same as the previous exercise but with sector MAAS split into it's normal sub-sectors LNO, LUX, and WESTU. The alternate route available to the Planning Controller in NTM now causes LNX925 to exit through a different down-stream sector (LUX instead of LNO). The user needs first of all to open the XFL menu in the FEEDE sector for LNX925 and click on the FL340 in order to complete the sector-exit planning in the FEED sector. Then, from sector NTM, the user may see the role of a Planning Controller who has early planning authority (30 mins before own sector exit) and who has down-stream vision of traffic load. The controller may probe the aircraft's expected traffic load for: a change of exit flight level; a change of exit-time; or a change of route. Completing the sector-exit planning by selecting an exit flight level will then put the aircraft label into a Tactical Controller's state, whereby the time-to-lose shown is the amount of time the Planning Controller agreed to lose (as deduced from the chosen sector-exit time).

Launch the EVP AMAN/EMAN demonstrator using Java Webstart (256mB CPU memory required)