Open becas22 opened 2 months ago
For the CTOTs, the new version already does something similar :) For local created CTOTs and TTOTs, a partly rework of the actual implementation. will be needed. I will keep it on the list as it is a very good idea to have the real-time waiting status.
A function to edit TTOT to a certain time or to set TTOT for now would be good enough already :D
Once departed, TTOT/CTOT is no longer relevant. These times are used for planning and the target is to match these times. If you are within the tolerance, you are good. If you are outside, you technically need to wait or replan flights. If your parameters result in an inaccurate planning, you need to change the parameters, and not "fake" your planning.
The particular CDM implementation I'm familiar works as a DMAN and allows you to edit the TTOT to fine tune the planning. This fine tuning is essential because the airport has limited capacity.
Currently the TTOT is calculated and you cannot adjust it anymore.
So is it rather overwritting TTOTs that were initially set automatically? This would correspond to what I know as a CDT (coordinated departure time), which behaves kind of like a CTOT (it's fixed and other slots will need to move around it) but is only local. The plugin implements this as a manual CTOT. Can you check if this satisfies your needs?
The TTOT is calculated automatically based on the TOBT, EXOT and other TTOTs. The controller can then adjust the flight in the departure timeline at anytime to adjust the sequence and enhance departure time estimates. I will check the manual CTOT function
In order to maintain TTOTs and CTOTs relevant, it would be nice if they were automatically updated to the airborne time when the flight is detected airborne. Otherwise, if flights depart earlier than TTOT, the system will not improve subsequent flights.