1 / 12

TAXI [ taxiroute ]

Choice : Null Apron Crossing point Gate Stand Holding Bay Intersection Hangar Holding point Named point Platform Remote Deicing Position Runway Taxilane Taxiway Terminal Deicing Position Tower. TAXI [ taxiroute ]. Sequence : to location (O) Position Information (O)

billy
Download Presentation

TAXI [ taxiroute ]

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Choice: Null Apron Crossing point Gate Stand Holding Bay Intersection Hangar Holding point Named point Platform Remote Deicing Position Runway Taxilane Taxiway Terminal Deicing Position Tower TAXI [taxiroute] Sequence: to location (O) Position Information (O) Sequence 1..128 Taxi Route Elements (O) Hold Short Procedure(O) Choice: Null Location At Location Of Location On Location To Location To end of Location Abeam Direction of Location Via Location From Location Sequence: Runway Direction (M) Runway Configuration (M)

  2. TAXI TO HOLDING POINT B1 RUNWAY 25R VIA TAXIWAY A-1 A-2 C HOLD SHORT OF RUNWAY 02 WHEN REACHING CONTACT GROUND 119.25 • ------------------------------------------------------------- • WHEN REACHING CONTACT GROUND 119.25 HOLD SHORT OF RUNWAY 02 TAXI TO HOLDING POINT B1 RUNWAY 25R VIA TAXIWAY A-1 A-2 C • Concern: • Need for ”some” concatenation rule ++ • Resolution: • need coordinated meeting with the Interop group” • Airborne domain may need some display rules (e.g. “Location” to be displayed)

  3. Pairing tables for D-TAXI DM requests • Concern • NOT useful as such • Could be used to indicate 1st element of a response • Consistence with other services • Resolution proposal • Pairing table to present the normally expected responses possible • Consider this “logic” for all services of the ISPR

  4. Message set table structure • Keep table format • Delete “dialog type” column • Whenever possible fill only (1) column (primary purpose of the message)

  5. Example Exception

  6. G-O A-M Concern Most D-TAXI message elements are G-O A minimum is required to implement a sub-service Resolution Update table to indicate as “G-M” the minimum set of msg elements that are required (on ground) to implement a particular sub-service

  7. Down link of aircraft weight Issue to coordinate either in plenary or with the 4D TRAD sub-group.

  8. …after message set review The D-TAXI team is now Ready to support or integrate other groups

  9. ON operating method tables

  10. TAXI TO HOLDING POINT B1 RUNWAY 25R VIA TAXIWAY A-1 A-2 C TAXI TO B1 RUNWAY 25R VIA A-1 A-2 C TXI TO …HP B1 RWY 25R VIA TWY A-1 A-2 C TXI TO …HP B1 RWY 25R VIA A-1 A-2 C -------------------------------------------------------------------------- Concern: Need rules for msg set display Resolution Airborne domain may need “guidance material”

More Related