To access the Slot Functionality & General Slot Setup, click this icon:

General

Slots are separate objects in the system, which means that they are completely independent and can exist without the need to first create a schedule. However, slots can be linked to an existing schedule. This can be considered a reference stating that a slot belongs to a specific schedule.

Note: A slot can belong to no schedules at all, one, or two schedules depending on how it is created. 

Unlinked

 If the slot is created in the slot wizard, it will belong to zero schedules. 

One Schedule

If it is a Departure or an Arrival slot, it belongs to one schedule.

Two Schedules

If it is a called Turnaround slot, it belongs to two schedules.

Example: How a slot is displayed in the Schedule Gantt

The semicircular yellow displays on the left side of the leg. It indicates that the schedule is linked with a slot for the coordinated airport ARN. 

On the right side, there is no such display. It is indicating that no slot for RIX as required (as it is not a coordinated airport).

Schedules without slots

Schedules can also exist in N-OC without a slot in the system, even if the schedule has coordinated stations. If checked in the slot wizard it would not display the slot at all.

This is rectified by generating slots required (based on the loaded schedule). The system will run a check for all coordinated stations, and if any schedules are missing slots , the Slot Wizard will create them. 

Example

The schedule is missing a slot for the coordinated airport CPH, but there is a slot for the same schedule for the coordinated airport EDI.

Slot indication

Click the “eye” and toggle “Slot” in order to view the slot status on the respective flights / legs.

Colored circles	Description	Example
White	Not created
Yellow	Created, but status not sent.
Orange	Created and waiting for a response. Status sent.
Green	Confirmed and status sent.
Red Half Circle	Departure Slot, created, and status sent.

Here are examples when the cursor is moved over the slot half circles.

General Slot Setup

Stations

1. To access Stations, click this tab:
2.  You must specify the Slot level. This is mandatory to do. There are three types of airport slot levels:
   • Level 1 - 'Non-Coordinated'
   • Level 2 - 'Schedules Facilitated' (will generate SMA messages)
   • Level 3 - 'Coordinated' (will generate SCR messages)
     
3. The Header is the main difference between Level 2 and Level 3 Slot requests.Note: At a 'Scheduled Facilitated' airport, a schedules facilitator assists the operations of airlines who propose to operate to or from that airport. At a 'Coordinated' airport, an airline may not operate there unless a slot has been approved by the airport coordinator.
   
   Note: Flights imported from a SSIM file will not generate slots automatically. You have to run the Slot Wizard (see designated topic)
   
   Refer to Stations for more details.

Station Period Slot Level

To access Station Period Slot Level, click this tab:

Some airports have different slot levels depending on the season or for special events (i.e. Olympic games, political events, etc.).

These seasons can be selected in the Station Period Slot Level function.

1. Select the airport.
2. Define the period
3. Select the slot level (slot level 2 or slot level 3). Alternatively by using a template, the upgraded or downgraded slot level can be linked to a specific season.
   • Level 1 - 'Non-Cooordinated'
   • Level 2 - 'Schedules Facilitated' (will generate SMA messages)
   • Level 3 - 'Coordinated' (will generate SCR messages).
     

Setup

To access Setup, click this tab:

(A) SlotCreationFilter

Values come from Slot filters. With the SlotCreationFilter, you select for what flights you want to create slots in general.

Note: No slots messages will be generated if these flights are not included in the SlotCreationFilter.

Filter for creation of slot

An example would be a filter for only allowing a certain airline prefix.

• API - Application Programming Interface
• COM - Communications
• SCH - Schedule
• SYS - System
• VEH - Vehicle
  

(B) DefaultEmailSlotSender

Default sender email for outgoing Slot messages. This email address is also used for receiving the responses from the respective slot coordinator.

Note: Empty = disabled.

(C) ActivitySlotCreationFilter

Filter for creation of slots. For example, a filter for only allowing a certain airline prefix.

(D) SlotLightLoad

If you want to load slot transactions without history data.

Slot Filters

To access Slot Filters, click this tab:

1. It is good practice to have a slot filter that covers all flights. This filter should be used in the setup parameter SlotCreationFilter.
2. Use DepFlightDesignator or ArrFlightDesignator combined with an asterisk (*), such as SRR.*. This will find all flights.
3. Choose the Data Element or you can do a manual creation (copy and paste).
   
4. Now, define the Filters.
   
   Note: It is recommended to have filters for the ActionCodes as this will make the work easier when you work in the wizard.
   
   
5. Choose a Filter option.
   
6. Test-run the script to see if it is functional.
   
7. Here is an explanation of Symbols to help.
   
8. You will now see the results in a message.
   
9. The Slot Filters is now created.
   

10. You can add or delete Action Code parameters.

User Preferences

To access User Preferences, click this tab:

SlotGIText

This will be added to the message ending of the slot request to the slot coordinator (Message Footer).

It is not mandatory, but the Coordinators expect this line in the message.

1. Enter in the parameters of the Message (SlotList None).
   

   Field	Parameters to select
   Event	SLT
   Filter	Filter the messages that shall be sent to the receiver. The filter name will be the name used in the slot list. From Slot filters Note: The SlotCreationFilter must include the flights you want to send to the receiver.
   Stations	None
   Bounce	None
   DataType	Slot

   
   
2. Select the System Message template.
   

   Field	Parameters to select
   Template Type	System Message
   Template	Defaults to ADM, but it isn't used.
   Criteria	None
   Header Template	None

   
   
   
3. Specify the COM Channel and the email account for the receivers. Note: The Active function must be checked.
   A user group may also be defined and created in Receiver Groups.
   Note: Receiver Groups is indicated by this tab:
   
   Multiple email addresses may be added to a certain receiver group. These users are indicated by this tab:
   
   Note: For the email addresses to the added, they must be created in the Receiver Groups.