CDM Server ‐ Calculate restrictions

Calculate restrictions

Airspace calculations

First, the planes are ordered by connection time.

For each aircraft that we have in the DB, we check each airspace checking entry/exit time to make sure the capacity os not over the max defined for each airspace.

In case the calculating plane goes over the capacity over an specific sector, then the plane will start to get delayed by 5 minutes to 5 minutes until a gap is found where the capacity is below the maximum.

Destination calculations

Without considering the modifications done for the airspace calculations we calculate again. For each airspace we make sure that the arrival time is not less than +/- arrival capacity defined for the arrival airport.

In case of being less, then we increase 1 minute by 1 minute the ETA until we find a gap. Note: If the delay is less than 5 minutes, a CTOT will not be considered.

Final calculation

At the end, we evaluate both result:

• If both returned a delay, the most restrictive delay is selected.
• If only one of them returned a delay, this delay is used.
• If none of them returns a delay, nothing happens.
• In case of worst delay than previous calculations, worst delay will apply only if cdmSts is NOT "PRIO" or "REA". All the other cases would get a worst delay.

Finally, after having a delay, we move airspace and ETA times to sync with the delay.

Notes:

• SUSP planes will NOT be taken into account to trigger a calculation and to consider them in the airspace.
• PRIO planes will be in the top of the list (To only compare with PRIO and REA planes) to be able to get less delays and try to avoid as much as possible restrictions.

When?

Automatic complete calculations run every 5 minutes or when triggered for an specific plane by a local ACDM.