CDT modifications

[rpuig2001]

• Yellow when a CDT is set and TTOT >= CTOT (if set).

• Red if the manual set TTOT (CDT) < CTOT (Must be a CTOT).

• Add external "click" and dropdown options.

[rpuig2001]

Include -> #96

[kusterjs]

I would handle a CDT like a "manually" edited time, similar to TOBT. There is no specific colouring for an edited TOBT, so I wouldn't use an additional colour when the TTOT has been manually changed. However keep in mind that these manually TTOTs are of higher priority than "regular" TTOTs. This means specifically that a delay gap won't affect these slots. Manually set TTOTs should fixed and not be subject to dynamic sequence changes. Maybe it is easier to implement a sort of indicator/flag (also in the backend for calculations) which indicates that a slot won't be changed because it has been manually set or fixed (there should be an option to activate/deactivate the fixation). But also then, a CDT (manual TTOT) needs to be within the CTOT window (if a CTOT has been generated). A CDT before the CTOT window is unrealistic (because you would disregard downstream restrictions), and a later TTOT needs to be coordinated with a corresponding new CTOT (that is also accepted by downstream sectors). It is a little bit of a ping-pong situation. But simplified you could say: if a CTOT is active, the CDT needs to be within the CTOT window. Otherwise you need to change the TOBT in order to trigger a new slot (possibly with another CTOT). If no CTOT is active, the TTOT should correspond with the expected departure time. Other flights will get penalized in return. However this might be overall beneficial for the entire airport, especially when there are dependencies between arrivals and departures (which cannot be reflected by parameters).

So to sum up, a colouring shouldn't be required. Instead, the setting of an "unrealistic" manual TTOT should be prevented already while giving an input. The corresponding restrictions would be that a manual TTOT can be set:

• only before start-up/push back
• only within the CTOT window (-5 to +10 MIN, https://skybrary.aero/articles/calculated-take-time-ctot), if a CTOT has been issued
• at the earlierst at present time + EXOT (estimated taxi out time) according stand position, to avoid unrealistic start-up and taxi time assumptions

[rpuig2001]

Checked. I will proceed removing coloring for CDT and apply the following restricions to set a CDT:

• only before start-up/push back
• only within the CTOT window (-5 to +10 MIN, https://skybrary.aero/articles/calculated-take-time-ctot), if a CTOT has been issued
• at the earlierst at present time + EXOT (estimated taxi out time) according stand position, to avoid unrealistic start-up and taxi time assumptions