Phase 1 - BUILD

The BUILD phase consists in building the initial schedule from various building blocks, and ensuring that the resulting schedule has the minimal quality required to go to the next workflow use case .

Assembling Schedule

The first step - Assembling Schedule - consists in the upload of one or more Schedule File, and the optional specification of custom Settings.

If not already done so, please make sure you have correctly uploaded a valid Schedule file (please refer to the Upload Schedule File and Setup Management sections for detailed instructions).

Initialise Schedule

When done, go to the Initialising Schedule tab:

The schedule has not yet been initialised - click on the Initialise Schedule to do so.

The Initialisation process will map the Flight ID to the CFN, taking into account any of the Setups. It will also map IATA aerodrome codes and aircraft types into the ICAO equivalent.

In cases where this step is not fully achieved, you will be presented with a list of those flights which have failed Initialisation, inviting you to correct non-initialised individual flights manually - or contact CSMC to update the mapping tables.

When done, you will get the following confirmation message:

Checking Schedule

The next step will be to open the Checking Schedule tab:

Quality checking aims to have the schedule in the best state for detection and deconfliction. In particular if the schedule contains days of operation which do not match the period of operation this could affect the ability of CSST to fully deconflict a schedule automatically. 

The quality Check area consists of 6 collapsible result sets. Three of these areas must be corrected if necessary before continuing the workflow (1, 4 and 6).

Click on the Check Schedule button to initiate the process:

The check returns variable results, depending on the context. In this example, areas 2 and 3 need attention:

Results Sets

The six result sets are collapsible and those sets where possible anomalies have been detected are highlighted in bold:

1. Sets of flight duplicates
   Duplicate data detected in the view. For example, same CFN and same Validity periods. You must delete duplicates before continuing with the workflow.
2. Sets of flights with the same commercial flight designator and overlapping periods of operation
   Same Airline designator and CFN but with overlapping periods of operation. City Pair could be different.
3. Flights with the same Call Sign (potential duplicates)
   Flags up for example different CFNs using the same  ATC Call Sign (Ex. 1235  235A  / 3356  235A)
   Note however that the check does not take into account different days or periods of operation
4. Incomplete flights
   Flights not completely initialized e.g. unknown aerodrome, Aircraft Type, AO.
   This is considered an error and the User cannot continue.
   5. FLIGHTS NOT FLYING IN THE IATA SEASON
   Flags up flights in the loaded schedule with a period of operation outside the IATA season. The User would then decide if this is a typo error otherwise he may delete them from the original schedule file. The parts outside the season will not be taken into account for detection.
   6. FLIGHTS USING FRENCH EXCEPTION BUT NOT ALLOWED
   Checks for breaches of the French exception rule (Flight ID format AAnnnAA).
   If the AO has an exception to the rule then CSMC will enter the AO as allowed in the CSST rules
   This is considered an error and the User cannot continue.

Incomplete flights and Flights using French exception require correction before continuing with the workflow. This can be done by deleting the flights directly from the checking area or from the schedule option in the view. If this is the case then the schedule must be re-initialised.  

Other anomalies can also be updated/corrected manually at this stage by clicking on ‘update’ then re-initialising to refresh any manual changes.