BUILD

Once in the Setup Management mode (accessed from the CSST portlet, as explained here), the first step is to select from the SEASONS tab the IATA season for which the set ups are to be applied and click on the BUILD tab:

This opens the BUILD tab, featuring the Global Setups and AO Setups sections:

A third section View Setups is also available, when the CSS Edit Setup window has been opened from the Setups button featured in the Workflow window for a given View:

The SEASONS tab is not available in this case.

Global Setups

The Global Setups are managed by CSMC for the selected season. They comprise Environment Data, prifle catalogues and the global Detection rules and buffer times.

The CSST similarity detection results are known as Reference Detection conflicts.

AO Setups

Expand the AO Setups section to reveal the 6 options available:

ATC AO Designator
Leading zeroes policy
CFN Suffix policy
Call Sign Maps

ATC AO Designator

The ATC AO Designator is used to override the normal mapped ICAO 3 letter code which will appear in the CSST workflow and output.
Simply enter the code in the AO field and click on the Save button.

Individual Views can however ignore this when override is ticked (default).

Leading zeroes policy

This is where you determine the policy on using leading zero’s in the Flight Id by indicating the minimum length of the Flight Id (1-4).

Example: CFN 0009 becomes Flight ID 09 if leading zero policy ‘2’ is ticked. If the user does not want to use leading zeroes at all then ‘1’ should be ticked.

Here again, do not forget to save your settings.

CFN Suffix Policy

This setting determines whether or not CSST will use the CFN suffix in the Flight ID.

Example: if CFN 91 has suffix ‘P’ in the SSIM schedule, CSST will initialize 91 as Flight ID 91P.

The possible values are:

IGNORE
USE IF POSSIBLE (by default)
USE BY FORCE

Do not forget so save any changes made to the default setting.

Call sign Maps

This last setting allows you to upload Call Sign Maps and to designate one to be the active Call Sign Map, allowing the Tool to map pre-determined Flight Id’s during the initialisation.

This will be applied to all Views for that season, unless Override is used in View Setups.

The Call Sign Maps files must comply with the CSV format.

View Setups

ATC AO designator

Used to override the normal mapped ICAO 3 letter code which will appear in the CSST workflow and output.
Enter the code and click on Save. Individual views can however ignore this when override is ticked (default).

Leading zeroes policy

This is where you determine the policy on using leading zero’s in the Flight Id by indicating the minimum length of the Flight Id (1-4).

Example: CFN 0009 becomes Flight ID 09 if leading zero policy ‘2’ is ticked. If the user does not want to use leading zeroes at all then ‘1’ should be ticked.

CFN Suffix policy

Allows you to IGNORE, USE IF POSSIBLE or USE BY FORCE
The default USE IF POSSIBLE will add the suffix to the Flight Id. The USE BY FORCE will insert the suffix even if it means truncating the Flight Id.

For normal schedule Detection/De-confliction the suffix is not used.

Call Sign Maps

This allows the Tool to map pre-determined Flight Id’s during the initialisation. Typically this will be the case when the User wishes to use some Flight Id’s from a previous season. The User will upload a csv file containing this information.

Identical CFN resolution

This setup specifies if during deconfliction, all flights with the same CFN will be changed together.
CSST tries to group those flights with the same CFN into a ‘Same ID Set’.

The default setting ensures that if you change a Flight Id then all other occurrences of the same CFN will also be changed to the new Flight Id. This default setting applies only for flights with the same CFN and same city pair. If you override the default setting (the box ticked) then all same CFN will be changed to the new Flight ID irrespective of the city pair(for example 1012 EGBB-EGLL and 1012 EGLL-ENBO will be grouped together with the same Flight ID.

You also has the opportunity at a later stage to manually add flights or remove flights from a ‘same id set’ during de-confliction. This is done by selecting flights and accessing the Same ID set.

Initialisation Constraints

These apply to csv and xlsx format schedules. They allow you to dictate whether CSST will use the CFN or Flight ID for initialisation. The default setting is for CSST to use the Flight ID if present in the schedule and not the CFN.

This will ensure that CSST bases the initialisation using the Flight ID from the schedule file and not the CFN.