1 / 25

New Output Capabilities Enhanced Taxiway Movement Logic Gate Pushback / Powerback Flexibility

New Output Capabilities Enhanced Taxiway Movement Logic Gate Pushback / Powerback Flexibility Enhanced Gate Selection Improved Runway Exit Logic. Contents. 0. SIMU26. NI,0. ,1 IN,.0001000,1,0,UAL384#0,384.1_GORD.SFO,0,535,GNDACT AB,.0001000,1,0

drake-ayers
Download Presentation

New Output Capabilities Enhanced Taxiway Movement Logic Gate Pushback / Powerback Flexibility

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. New Output Capabilities Enhanced Taxiway Movement Logic Gate Pushback / Powerback Flexibility Enhanced Gate Selection Improved Runway Exit Logic Contents 0

  2. SIMU26 NI,0. ,1 IN,.0001000,1,0,UAL384#0,384.1_GORD.SFO,0,535,GNDACT AB,.0001000,1,0 IN,.0001000,2,0,NWA311#0,311.1_GMSP.SFO,0,532,GNDACT AB,.0001000,2,0 IN,.0001000,3,0,UAL383#0,383.1_GIAD.SFO,0,544,GNDACT AB,.0001000,3,0 IN,.0001000,4,0,TWA375#0,375.1_GSTL.SFO,0,544,GNDACT AB,.0001000,4,0 IN,.0001000,5,0,AAL1#0,1.1_GORD.SFO,0,532,GNDACT AB,.0001000,5,0 IN,.0001000,6,0,DAL145#0,145.1_GATL.SFO,0,535,GNDACT AB,.0001000,6,0 IN,.0001000,7,0,GCO213#0,213.1_GLAX.SFO,0,526,GNDACT EJ,.0800000,12,0,? REPORTS ~10 MB ~5 MB New Output Capabilities Background ANIMATION SIMMOD 2.3.1: Simulation RUN History 1 1 NM 9 145 A .9400000 .0358920 0.0 1 1 NM 8 143 A .9758920 .1136270 0.0 1 1 HA 7 -1 A 1.0895190 0.0 .0855623 1 1 NM 7 140 A 1.1750813 .0385706 0.0 1 1 HW 4 -1 A 1.2136519 0.0 .0010837 1 1 NM 4 138 A 1.2147355 .0147924 0.0 1 1 NM 12 137 A 1.2295279 .0127991 0.0 1 1 NM 1 136 A 1.2423270 .0298450 0.0 1 1 RL 1 78 D 1.2721720 .0032452 0.0 1 1 RL 2 20 D 1.2754171 .0133227 0.0 1 1 RL 3 20 D 1.2887398 .0123846 0.0 1 1 RL 4 20 D 1.3011244 .0077764 0.0 1 1 RL 26 20 D 1.3089008 .0071098 0.0 The size of the SIMU26 file may sometimes become too big for quick and easy extraction of useful data for reports SIMU26 data are recorded at the start of the delay and contain the engine’s estimate of the delay end time 1

  3. SIMU44 FORMAT: Item Code Iteration Number Aircraft Number Item ID Event / Item Parameters Simulation time In Simulation Time Out Same delimiter as for SIMU26 New Output Capabilities Implementation SOLUTION: Create another file for reports Runway records Runway Crossing records Add’l RWY Crossing records for intersecting runways Departure Queue records Gate records Wheel records Deicing records Route records TRACE 303 SIMU44 Data output occurs at the end of the delay, thus the actual simulation time is reported 2

  4. New Output Capabilities Implementation Item Code Convention. Comments RC is generated each time an AC exits RWY Crossing. Its time includes the entire time spent there, including all hold and engine spoolup times RR refers to situations where a runway crossing intersects another runway. The RWY name in the record corresponds to the name of the RWY that this RWY Crossing intersects. WH means Wheels ON if it precedes the RW record and Wheels OFF if it follows the RW record with the same Aircraft number. Item Parameter is another way to tell ON from OFF 3

  5. SIMU26 NI,0. ,1 IN,.0001000,1,0,UAL384#0,384.1_GORD.SFO,0,535,GNDACT AB,.0001000,1,0 IN,.0001000,2,0,NWA311#0,311.1_GMSP.SFO,0,532,GNDACT AB,.0001000,2,0 IN,.0001000,3,0,UAL383#0,383.1_GIAD.SFO,0,544,GNDACT AB,.0001000,3,0 IN,.0001000,4,0,TWA375#0,375.1_GSTL.SFO,0,544,GNDACT AB,.0001000,4,0 IN,.0001000,5,0,AAL1#0,1.1_GORD.SFO,0,532,GNDACT AB,.0001000,5,0 IN,.0001000,6,0,DAL145#0,145.1_GATL.SFO,0,535,GNDACT AB,.0001000,6,0 IN,.0001000,7,0,GCO213#0,213.1_GLAX.SFO,0,526,GNDACT EJ,.0800000,12,0,? ~9.5 MB New Output Capabilities Example SIMU44 NI,0.0,1 GE,1,12,GTE_A10,D,.0800000,.0800000 GE,1,25,GTE_D4,D,.1667000,.1667000 GE,1,33,GTE_B10,D,.2500000,.2500000 DQ,1,33,DAPT_01L_APT,.3069993,.3069993 GE,1,42,GTE_G2,D,.3173720,.3173720 RW,1,33,01L,D,.3069993,.3181726 WH,1,33,OFF,.3075505 RE,1,33,DAPT_01L_SW,19,.3181726,.4088987 RC,1,6,28L_D,1.0994327,1.1250320, .0327311 RR,1,6,28L_D,28L,1.0994327,1.1250320, .0327311 SPECIAL HANDLING: SIMU44 will be written only if TRACE 303 is set ON SIMU44 can only be used for Delay Reports ~ 0.82 MB Data for reports are now contained in a much smaller (an order of magnitude) and more manageable file 4

  6. AC 1 AC 2 GL_1 GN_3 GN_2 GL_2 GN_4 Enhanced Taxiway Movement Logic Background FIGURE 1: EXAMPLE: GN_1 In Figure 1, AC2 may have a higher ground link speed on GL_2 than AC1 has on GL_1. If the airfield layout is such that the wingspan of either or both aircraft would not allow passing, there is no method to prevent AC2 from arriving at GN_4 earlier than AC1 arrives at GN_2. This is a simple example of a class of situations where a different approach to taxiway movement logic would be appropriate 5

  7. Enhanced Taxiway Movement Logic Implementation GroundLink - GroundLink BLOCKING: FIGURE 2: GN_1 AC 1 GL_1 AC 2 AC2 @ GN_3 ? GN_3 GN_2 STOP GL_2 yes GN_4 GL_1 may block GL_2 ? AC1 on GL_1 ? yes yes AC1 will block AC2 on GL_2 ? no no no yes Proceed AC1 on GL_1 ( This logic will work for parallel, opposite, intersecting, etc. ground links. ) HOLD AC2 @ GN_3 until AC1 is @ GN_2 6

  8. AC Model MDL1 on AFLink1 AC Model MDL2 on AFLink2 AFLink1 AFLink2 Mdl1 Mdl2 BLOCKS Enhanced Taxiway Movement Logic Implementation SIMMOD inputs: New table in SIMU07: AFLINKBLOCKING It will include: & FIGURE 3: GN_1 AC 1 Reversible Blocking flag (T or F) GL_1 SPECIAL CARE: If AC1 is at GN_1 and AC2 is on GL_2 (see Figure 3), then, unless Reversible Blocking Flag is “T”, AC1 will go ahead GN_3 GN_2 AC 2 GL_2 GN_4 7

  9. Enhanced Taxiway Movement Logic Implementation AFLinkList1 First (blocking) list of Ground Links AFLinkList2 Second (being blocked) list of Ground Links MdlKyWd AC Model vs. Ground Group flag (“MDL” or “GRP”) Mdl1 AC Model or ground group, respectively, blocking while on AFLink1 Mdl2 AC Model or ground group, respectively, being blocked while on AFLink2 RevBlkFlg Indicator = “T” if blocking is reversible, “F” otherwise 8

  10. Background Gate Pushback/Powerback Flexibility SIMMOD 2.3.1: PPBACK table in SIMU07 file GATES table in SIMU07 file Lists models that only allow Pushback Gate type info referring to Pushback & Powerback (0, 1, or 2) Sometimes it is necessary to allow different pushback time distribution for a certain AC Model, even if it belongs to a ground group listed in PPTIME table PPTIME table in SIMU07 file Lists Pushback & Powerback time distributions for AC ground groups from TAMPS table This is a good approach to gate pushback / powerback, but it lacks some flexibility. 9

  11. Gate Pushback/Powerback Flexibility Implementation Figure 1 GL_2 GL_3 ACMDL3 ACMDL5 GL_1 GTE_1 (gate type 1 or 2) ACMDL1 ACMDL2 ACMDL3 New table in SIMU07: GATE_MDL_PP_TIME It will include: • Gate Identifier • List of Ground Links connected to the gate • for which power/pushback is allowed • List of AC models for which push and • powerback times are presented by the • distributions • Powerback Time • distribution • Pushback Time • distribution & 10

  12. Gate Pushback/Powerback Flexibility Implementation Gate Type = 0 ? Gate Type = 1 ? no yes yes no AC Model listed in PPBACK ? PUSH BACK Do NOT model PPBACK yes AC Model, Gate, AFLink listed in GATE_MDL_PP_TIME ? no POWER BACK yes Use time distribution from GATE_MDL_PP_TIME no Use time distribution from PPTIME 11

  13. Gate Pushback/Powerback Flexibility Implementation EXAMPLE 1 PPBACK 48 GATE_MDL_PP_TIME maximum 2 records 1 15 26 ; gate1 GL15 GL26 1 2 15 48 ; MDL1 MDL2 MDL15 MDL48 0.0 10.0 1.0 13.0 ; Powerback time distribution 0.0 12.0 0.97 14.0 1.0 15.5 ; Pushback time distribution 1 15 26 ; gate1 GL15 GL26 49 50 ; MDL49 MDL50 0.0 10.0 1.0 13.0 ; Powerback time distribution 0.0 12.0 0.5 14.0 1.0 15.0 ; Pushbacktime distribution PPTIME 1 ; GRG1 0.0 9.7 0.01 10.0 1.0 13.0 ; Powerback time distribution 0.0 11.5 0.2 12.0 0.5 14.0 1.0 15.0 ; Pushbacktime distribution SPECIAL CARE: If the gate type is 2 (powerback unless the AC is push back only), the powerback distribution in GATE_MDL_PP_TIME will NOT be used if the model is listed in PPBACK. (in Example 1, only pushback will always be used for model 48 coming out of gate 1 along link 15 or link 26.) 12

  14. Example 1 (Cont.) Gate Pushback/Powerback Flexibility Figure 2 Only GL_15 and GL_26 are listed in the GATE_MDL_PP_TIME table; for GL_137, PPTIME distribution will be used ACMDL48 ACMDL49 ACMDL50 ACMDL1 ACMDL2 ACMDL15 GL_15 GL_4 ACMDL48 ACMDL49 ACMDL50 ACMDL1 ACMDL2 ACMDL15 GL_137 GTE_1 GL_26 ACMDL48 ACMDL49 ACMDL50 ACMDL1 ACMDL2 ACMDL15 13

  15. Gate Assigned ? Gate Available ? yes no yes no Go to it Alternative gate available ? yes no Gate Selection Logic Background EXAMPLE 1: SIMMOD 2.3.1: Runway 9 AL 1 GTE_1 Assign a different airline @ random (subj. to constraints) 12 AL 1 space 12 AL GTE_4 9 AL GTE_2 12 AL GTE_5 GTE_3 4 spaces Select a random gate among adequate, based on its availability & “popularity” w /airlines Figure 1 1 GTE_5 has an 80% chance of being selected; GTE_1 has 20% This is a good approach to gate selection; but sometimes other considerations may force the analyst to need a different approach 14

  16. Gate Selection Logic Implementation Figure 2 If AL1 prefers GTE_3, but GTE_3 is also assigned to 11 other airlines, while GTE_1 is assigned only to AL1, GTE_3 has virtually no chance of being selected, unless GTE_1 has no space. GTE_5 GTE_1 GTE_4 GTE_2 GTE_3 Airline’s preferences need to be accommodated. SIMMOD inputs controlling gate selection logic: New table in SIMU07: AL_MDL_GATE_CHOICE It will include: • Airline Identifier • List of AC models that this entry covers • Prioritized grouping of • gates and respective • preference distribution • within each group & 15

  17. Gate Selection Logic Implementation Airline Identifier SIMMOD number of the airline List of AC Models Space delimited listing of aircraft models covered by this entry Prioritized grouping of Gates Group of gates to be considered first, second, etc. The gates are to be listed in the respective preference distribution. 16

  18. SPECIAL CARE: This table has effect only when the airline is assignedand the gate is not available. For the airlines and models listed in it, this table has priority over the standard gate selection logic. DO NOT list a model more than once for each airline Gate Selection Logic Implementation EXAMPLE 2: AL_MDL_GATE_CHOICE maximum 2 records 1 15 26 115 230 ; 2 1 0.01 1 1.0 3 ; 2 0.01 2 0.97 4 1.0 5 ; 1 25 30 24 17 ; 1 priority group 1 0.07 5 0.21 1 1.0 3 ; The situation described in Slide 2 (Figure 2) can be fixed as follows: Figure 3 GTE_5 GTE_1 GTE_4 GTE_2 GTE_3 Spacei Pi = Piassigned *  ( Spacej ) 17

  19. Gate Selection Logic Implementation EXAMPLE 3: Space at the gate Assigned distribution Space-based distribution Final distribution As for any independent random events, the probability of a gate being selected is the (normalized) product of assigned and space-based probabilities 18

  20. Min Roll 14 GTE_2 124 15 121 123 GRN9 RC GRN3 16 GRN2 GRN1 122 38 GTE_1 Runway Runway Exit Logic Background Figure 1 EXAMPLE: If an arrival aircraft is heading for GTE_1, but its minimum landing roll length is greater than the distance from touchdown at GRN1 to GRN2, it will take the next possible exit link # 123. In this case, the AC will then take link 1415RC and only then is it on the proper side of the runway. Exit link 16 would have been the logical choice... This is a simple example of a class of situations where a different approach to runway exit would be advantageous 19

  21. Figure 1 Min Roll 14 GTE_2 124 15 121 123 GRN9 RC 16 GRN3 GRN2 GRN1 122 38 GTE_1 Runway Runway Exit Logic Implementation SIMMOD inputs controlling runway exit operations New table in SIMU07: RWY_GATE_ACMDL It will include: • Runway Identifier • Destination Flag • Destination Identifier • List of AC models that this entry covers • A way to indicate links • to take and / or not & 20

  22. Runway Exit Logic Implementation Runway Identifier Name of the runway either in primary or opposite direction; the logic will work for both directions of the runway Destination Flag An indicator = “G” if the record is for a gate = “C” if the record is for a concourse Concourse number or Gate number from SIMU07 Destination Identifier List of AC Models Space delimited listing of aircraft models covered by this entry A way to indicate exit links for aircraft of model from the list going to the gate or concourse on the runway: Distribution of ALLOWED exit links List of PROHIBITED exit links 21

  23. Runway Exit Logic Implementation Distribution of ALLOWED exit links List of PROHIBITED exit links In this case, the engine will sample from the distribution, and the selected link will be the one to be taken, unless it is listed as prohibited for this AC model / gate / runway. In this case, the engine will proceed the usual way, with the exception that it will check the exit link for being in list of prohibited exit links. If it is, then the engine will select the next non-prohibited exit. SPECIAL CARE: If the final runway exit link is prohibited, the engine may terminate with an error, if no other exit link is feasible. Ifthe randomly picked exit is listed as prohibited for this AC model / gate / runway, then the sampling will continue until a non-prohibited exit is found. 22

  24. Runway Exit Logic Implementation TABLE FORMAT: List of Prohibited links TABLE FORMAT: Distribution of Allowed Links TABLE RULES: 1 Either Distribution or Prohibited Links in each record 2 If Distribution, then MaxNumProhib = 0 3 If a link is listed with non-zero probability in one record but is prohibited in another, then another link will be randomly picked until a non-prohibited link is selected. 23

  25. Figure 1 Min Roll GTE_2 14 124 15 121 123 GRN9 RC 16 GRN2 GRN3 GRN1 122 38 GTE_1 Runway APT_01L Runway Exit Logic RWY_GATE_ACMDL_P Maximum Number: 1 1 APT_01L ; G 1 ; 114 115 116 117 ; 1 123 ; OR... RWY_GATE_ACMDL_D Maximum Number: 1 1 APT_01L ; G 1 ; 114 115 116 117 ; 0 0.02 124 1.0 16 ; In this case, even if links 124 and 15 are parts of the taxipath for this ARRIVAL event, once 16 has been selected, it will be taken. In either case, link 123 will not be taken, and the aircraft will proceed to link 16 or to link 124. 24

More Related