Deconfliction

Deconfliction is carried out from the de-confliction screen. The screen is accessible after detection via two buttons:

Modify ATC Flight ID - accessible in the conflict list once one or several flights have been selected.
Autodeconflict - accessible directly from the view after detection is completed.

Three modes are available in the screen:

Manual Solution
Semi-Manual
Automatic

Manual Solution

The Manual Solution mode is to be used for a single flight change.

The Deconfliction function can be invoked from either the Flight List or the Conflict List. To do so, select the desired item in the list and click on the Modify ATC flight list button:

This will bring up the Conflict List (TENTATIVE) window, featuring the Solution Area where you have the option of entering a Manual Flight ID or using the Range to instruct the tool propose solutions.

For this example, we have provided a manual entry (Solution '66Y') and clicked on the Go button:

As a result of this change, the numbers of conflicts is now zero:

The updated entry can now be selected again and saved, by use of the Confim button:

Semi-Manual

The Semi-Manual mode is engaged when a single flight is selected for deconfliction.

You can toggle between ATC Format and range preferences and Transformation Rule.

In this example, a first way is to opt for the Range approach, and enter the values 200A-888Z to specify the range of acceptable proposals. Clicking on the Go button returns a maximum of 20 conflict free proposals as below:

The Transformation Rule can be used aletrnatively, to remove first or last characters of the selected string:

After each of the confirmed deconfliction, the Deconfliction window will close - and you are requested to manually refresh the Conflict List by ticking the UNPROCESSED check box and clocking on the Go button:

Auto-Deconflict

The Automatic mode uses the same criteria as the Semi-Manual mode, but is engaged when several or all flights are selected. CSST will not propose changes but will modify ATC Flight Ids directly in the schedule. You can elect to automatically deconflict the complete schedule or select a set of flights for automatic deconfliction.

It is not recommended to perform autodeconfliction without assigning some minimum preferences.

You must have achieved all the workflow steps, up to and including Detection, before being able to use the autodeconfliction function. And prior to Detection, make sure that your local rules have been set up (e.g. preferences for letters or combinations to avoid need to be applied to be taken into accound during deconfliction).

Once the detection phase is complete, you then have two options:

Go to the conflict list to filter those flights to autodeconflict
Go directly to the deconfliction screen to autodeconflict all flights

Option 1- Filtering flights in the conflict list:

Open the filter screen:

This is where you will select conflicts and/or flights to autodeconflict, using the provided filters (CFN, Flight ID, ADEP, ADES, ...)

Note that wildcards(*) can be employed to select a range of flights. For example LF* used in ADEP will display all flights departing from LF aerodromes.
You can also select a range of flight numbers can be selected also: to select all CFN in range 100-199, simply enter 1??-1?? in the query filter.

The example below shows how to retrieve all conflicts concerning flights departing from LFPO:

Clicking on the GO button from the Query Conflicts section will display the flights having conflicts matching the filtering criteria.

Note that you can either hard check individual flights from the list, or use the Multiple Selection Mode check box to select all of the flights for autodeconflcition - and uncheck the flight you do not want to include in the deconfliction.

When this step is completed, you can click on the Modify ATC Flight ID button to launch the process and open the CSST Deconflict window

CSST Deconflict Window

This is what the CSST Deconflict window looks like:

At this stage, it is possible to directly click on the GO button from the Solution Area section to autodeconflict the flights that were selected. This is however not recommended, unless you happen to have no preference for the proposed Call Sign formats.

You are therefore advised to enter your preferred autodeconfliction formats in the form of piorities.

In the simple example below, you can see how to apply the format nnnA to those flights having a CFN of length 4 digits (just click in a table cell to switch to the Edit mode and create/edit content):

A more elaborate priority might use Ranges. In this new example, CSST will first try to deconflict using priority 1.
If it does not find all solutions it will then use priority 2. For those CFN with length 3 it will use priority 3.

For other possibilities within the priority options, please refer to the CSST User Guide.

Option 2 - Automatic

From the CSST Deconflict window, you may also use the autodeconfliction process. You launch it with the GO button from the Solutions Area section - Autodeconfliction takes into account any rule or format preferences that have been entered at the beginning of the workflow in AO or view setups.

Note that CSST does not allow automatic deconfliction using the format nnnAA (French Exception).

Type your Note Box content here.

CSST may not be able to fully deconflict the complete schedule due to limited solution space or constraints that have been introduced by the user (formats etc).

As a result, once the auto-deconfliction process is terminated there may still be remaining unresolved conflicts. These will be visible in the global flight list with qualification No Solution Automatic. You will need to unqualify these if you wish to change them manually.