COHOR 17/01/06 15:56 SLOTIX

Transcription

1 SLOTIX MAINTENANCE OVERVIEW Page 1 of 47

2 1. INITIAL DEFINITION OVERVIEW COORDINATED AIRPORT MAINTENANCE SEASON MAINTENANCE SIMPLE DICTIONARY CODE MAINTENANCE SIMPLE DICTIONARY MAINTENANCE USER MAINTENANCE SERVER INSTANCE MAINTENANCE DATASETS OVERVIEW DATASET MAINTENANCE AIRCRAFT MAINTENANCE AIRLINE MAINTENANCE AIRPORT MAINTENANCE GROUP MAINTENANCE RESOURCES AND CONSTRAINTS OVERVIEW RESOURCE MAINTENANCE RESOURCE PROFILE MAINTENANCE CONSTRAINT MAINTENANCE RESTRICTION MAINTENANCE WORKED EXAMPLES PERSONALISATION OVERVIEW TEMPLATE MAINTENANCE FLIGHT ATTRIBUTE MAINTENANCE MERGE PARAMETER MAINTENANCE SSIM RELEVANCE MAINTENANCE 40 APPENDIX A SLOTIX FLIGHT ATTRIBUTES 41 Page 2 of 47

3 1. Initial Definition 1.1 Overview This section describes how the most general data are defined in SLOTIX, this includes: The coordinated airports, the seasons, the users of the system and the general dictionary data used throughout SLOTIX. Also covered in this section are the parameterisation of external processes (such as the XML Server and the SSIM Parser). Page 3 of 47

4 1.2 Coordinated Airport Maintenance Description This screen enables you to define the airports that you coordinate in SLOTIX. Fields! Airport The three-letter IATA code for the Airport.! Slot Granularity This field is used to define how the slot times are to be held in the airport. Normally this field will have the value 5 indicating that all times will be rounded to 5 minutes. If you set this field to a higher value (e.g. 10) then a 1205 flight will be held and displayed in SLOTIX as 1200.! Coordination Level Indicates whether the Airport is F-ully or C-oordinated. This field is purely informational field that is not actually used in SLOTIX.! Night Curfew Details These fields were originally designed to enable the easy definition of the night curfew for arrivals and departures. As SLOTIX was developed it was decided that this information would be better held using the resource map (see section 3). These fields are no longer used by SLOTIX but have been left here for informational purposes.! SITA Address The SITA address for incoming messages for this airport (this field MUST be entered correctly). Page 4 of 47

5 ! Copy Address You may require that every reply to an SCR be copied to other SITA addresses. These fields allow you to define such addresses.! Reply SI Footer These fields can be used to define the SI text that is to appear by default at the foot of every reply to an SCR message that is sent from this coordinated airport.! Pre-Coordination SI Footer During the submission period just prior to the IATA Scheduling Conference, the airport may require that a different SI test appears on reply to the submission SCR messages. These fields enable this SI text to be defined.! General Aviation Airport Sometimes general aviation flights operate to and from airports that do not have an associated 3-letter IATA code. This field represents the value that needs to be placed in the origin/destination or previous/next fields for the flight to indicate that the actual airport will instead be held in the associated 4-letter ICAO code fields.! General Aviation Aircraft Sometimes general aviation flights operate using aircraft that do not have an associated 3-letter IATA code. This field represents the value that needs to be placed in the aircraft field for the flight to indicate that the actual aircraft details will instead be held in the associated 4-letter ICAO code field. Page 5 of 47

6 1.3 Season Maintenance Description This screen allows you to define each new season as you require it. If you enter a new screen, the start and end dates are automatically calculated and cannot be modified by the user. Fields The remaining fields are maintainable but are not used explicitly by SLOTIX. This may be used by external applications to determine when certain external reports are produced etc! Pre-Coordination The date after which the airlines initial submissions are accepted.! SISC Conference Start/End The dates of the IATA Scheduling Conference for this season.! Slot Return The slot return date for this season. Page 6 of 47

7 1.4 Simple Dictionary Code Maintenance Description This screen (and the one described in section 1.5) are used to define codes that are used throughout the system but do not require a separate maintenance screen. Some examples currently in use are : Service Types Country Codes Wait List Reason Codes User Selectable SI Text Fields! Group The name of the group of dictionary codes being maintained.! Code Length The number of characters for the code (e.g. Service Types have a code length of 1).! Force Numeric Indicates that the code must have a numeric value.! Numeric Description Indicates that the description field for the code must be numeric.! User Maintained Some dictionary codes will be used internally and therefore cannot be changed by the user. These will have the value Y set in this field. Note Only the system Super-User (currently defined as ADP_MANAGER) can access this screen Page 7 of 47

8 1.5 Simple Dictionary Maintenance Description This screen is used to maintain all of the possible values for the dictionary codes. Fields! Item This is the value of the code (e.g. for the COUNTRY group the different items contain all of the possible 2-Letter codes for the different countries).! Description The associated description for the code.! Live Status This should always be set to L. It is used to indicate whether this code is still in operation or has been dropped or replaced. L indicates that the code is in operation ( Live ). Page 8 of 47

9 1.6 User Maintenance Description This screen is new to version 3 of SLOTIX and allows you to store data for every that is allowed to maintain flight data. Fields! Triptych A unique 3-Letter code for the user (usually the initials).! Last HS Ref Sequence (This is only relevant to fully coordinated airports). When a user adds or modifies a flight in such a way as to affect their historic status then that flight is assigned a unique reference number which is comprised of the users triptych and the next number in this sequence held as a hexadecimal number. When a user is initially created, this field should be set to 0. It is then maintained automatically by SLOTIX. Page 9 of 47

10 1.7 Server Instance Maintenance Description SLOTIX has a number of external Servers. These are programs that process incoming files from other systems and use them to update the SLOTIX database. This table is used to specify where the server can locate the incoming files, where the file should be copied to once processed and where the generated reply should be set. Examples of Servers are the SSIM Parser and the XML Server. The SSIM Parser takes files received from a SITA Gateway and converts them into XML Formatted files. The XML Server takes these converted files and uses them to update the data in SLOTIX. Fields! Username The username used by the server to connect to SLOTIX.! Incoming Directory The directory where the files are to be read from.! Output Directories Where the converted file (or the reply file) is to be placed. Two possible directories can be specified depending on the format of the file.! Error Directory If an incoming file is formatted incorrectly (e.g. it does not match chapter 6 standards), it will be copied into this directory.! Processed Directory Where the original file is copied to when the server has finished processing it. Note The drive used in the definition of these directories must be known to all SLOTIX users. If not, for example, the user will not be able to send replies to SCR messages. Page 10 of 47

11 2. Datasets 2.1 Overview SLOTIX allows you to vary the definition of static data across different airports and seasons. A group of flight data and all of its associated static data items is referred to as a Dataset. More than one dataset can be defined for each Coordinated Airport and Season. SLOTIX reserves two datasets that must be defined before flight data can be created for an Airport and Season. These are: OPERATED This dataset is used to hold the flights that the airlines intend to operate. HISTORIC This dataset is used for fully coordinated airports only, but is required to exist even for partially or non-coordinated airports. The flights that are intended to be granted for the next seasons SHL (if operated correctly). The following sections show you all of the screens needed to define the static data for a dataset. Page 11 of 47

12 2.2 Dataset Maintenance Description This screen enables you to define a Dataset. A dataset is defined by the Coordinated Airport, the Season and a unique (for that Airport and Season) dataset id. Fields! Critical Resource! Critical Constraint! Critical Hour! Critical Date Range These fields relate to the default values that are displayed on the Enquiry Summary screen. When you initially create the Dataset you will not be able to enter values in the Critical Resource and Constraint fields, as you will not yet have been able to define any resources and constraints. Therefore, you should initially leave these fields blank and return to this screen when the resources and constraints have been defined for the dataset.! Status Most of the time this field is purely an informational field that is used to indicate the current status of the OPERATED dataset (the field only has meaning for the OPERATED dataset). The user should keep this field up to date throughout the lifetime of the dataset, for example the status should be set to REGULATION once the Slot Return date has passed. External programs may make use of this field to describe when, for example, data for this dataset is to be transmitted to the airport. Two statuses are reserved by SLOTIX: CLOSED = No SCR messages are accepted for this dataset by the SSIM Parser. All messages are automatically placed by the SSIM Parser into its associated Error Directory. Page 12 of 47

13 PRE-COORDINATION = The SSIM parser will only accept SCR submission requests and no SIR requests.! Availability This field is currently an informational field not yet used by SLOTIX. It is intended to be used in the future to allow you to specify the types of users that can access this dataset.! Turnround Critical This flag is used to indicate that Turnround flight details may not be separated by users when using the merge facility (i.e. whether the Separate Turnrounds option is available on the Merge screen for this dataset). Note : All of the remaining fields on this screen relate to the OPERATED dataset only, for all other datasets these values have no meaning.! Automatic Message Handling This flag is reserved for use in a later version of SLOTIX. It will be used to indicate that SCR messages received for this dataset will be processed automatically as long as no limits are broken.! HS Addition Limit! HS Deletion Limit These fields are used for coordinated airports to decide when a change made to the OPERATED dataset should also be made to the HISTORIC dataset. For example: If a flight addition represents a number of weeks that is greater than the HS Addition Limit, then that flight will be added automatically to the HISTORIC dataset. For non-fully coordinated airports these fields should be both set to 99 to ensure that the HISTORIC dataset is never updated. Page 13 of 47

14 2.3 Aircraft Maintenance Description This screen is used to maintain all of the valid aircraft types for this Dataset. Fields! Aircraft The 3-Letter IATA code for the aircraft.! Parent If this is an Aircraft that belongs to a wider group of aircraft (e.g. a 744 is a sub-type of 747), then this field should be used to indicate the group of aircraft to which this aircraft code belongs.! ICAO Code The 4 Letter ICAO Code for the aircraft type.! Wide/Narrow Whether the aircraft is W-ide bodied or N-arrow bodied.! Stand Requirement The number of stands required at this airport to hold the aircraft. This field is only meaningful for airports where stand capacity is an issue. It can be set to 1 for all other airports.! Chapter The aircraft chapter number! Weight A numeric field that can be used to define constraints (e.g. only a certain number of aircraft exceeding a particular weight value can be accepted during a one-hour period). Page 14 of 47

15 ! Arrival Noise! Departure Noise The noise rating allocated to the aircraft for its arrival and departure at the airport. Every airport may have different methods for calculating the noise rating for an aircraft, or may have none at all, in which case these fields can be set to 9999.! Item Id Used internally. Should initially be set to zero.! User Attr 1! User Attr 2! User Attr 3 These fields are simply memo fields that can be used to store airport specific information for this aircraft type. This information can then be displayed in SLOTIX against the flight data on the main screen and can be used in reports and retrievals. Page 15 of 47

16 2.4 Airline Maintenance Description This screen is used to maintain all of the valid airlines for this Dataset. Fields! Airline The code (2-Letter or 3-Letter) that you wish to display for this airline on the SLOTIX main screen.! Alternative Code If the 2-Letter code has been used to populate the Airline field then the 3-Letter code should be used here (or vice-versa). If the airline only uses one code then it should appear in both fields.! SSIM Code The code that the Airline normally uses on SCR messages.! Country The base country for the airline, using the 2-Letter IATA country codes (use XX if the country is not known or is not considered important).! Alliance The alliance that the airline is a member of. The list of valid alliances can be maintained using the dictionary screens (see 1.4 and 1.5). Use NONE if the airline does not belong to any alliance.! Default Terminal The default terminal for the Airline. This field is often used when specifying the terminal allocation rules on the resource profile maintenance screen (see section 3.3). Page 16 of 47

17 ! Operation Limits! Night Quotas These fields were originally intended to be used to specify online quota constraints, but it was felt that this could be achieved more accurately using resource and constraint maintenance (see section 3). Therefore these fields are no longer used by SLOTIX but are retained for informational purposes only.! Allowed To Operate Should be always set to Y. SLOTIX no longer checks this field.! Responsible The triptych (see section 1.6) for the person who is responsible for this airline. This field can be used in SLOTIX retrievals and reports. If the airport does not allocate portfolios to airlines to individual coordinators then you can just set this field to XXX.! User Attr 1! User Attr 2! User Attr 3 These fields are simply memo fields that can be used to store airport specific information for this airline. This information can then be displayed in SLOTIX against the flight data on the main screen and can be used in reports and retrievals. Page 17 of 47

18 2.5 Airport Maintenance Description Maintains the valid airport codes for the dataset. Fields! Airport The 3-Letter IATA code for the airport.! ICAO Code The 4-Letter ICAO code for the airport! Latitude! Longitude Optional informational fields that could be used in reporting. If this information is not relevant to the airports being coordinated then these fields can be left to zero.! Country The country for the airport, using the 2-Letter IATA country codes (use XX if the country is not known or is not considered important).! Domestic/Int/Schengen Whether the airport is considered D-omestic, I-nternational or S-chengen.! Long/Short Haul Whether the airport is considered L-ong or S-hort haul.! Default Terminal Some airports allocate terminals based on the destination for the flight (for example CDG allocates the terminals for Air France flights within terminal 2 based on their destination). This field can be used to hold this information.! Item Id Used internally. Should initially be set to zero. Page 18 of 47

19 ! User Attr 1! User Attr 2! User Attr 3 These fields are simply memo fields that can be used to store airport specific information for this airport. This information can then be displayed in SLOTIX against the flight data on the main screen and can be used in reports and retrievals. Page 19 of 47

20 2.6 Group Maintenance Description This screen is used to group like values of flight data attributes. These can then be used as the basis of retrievals (e.g. a find of all Charter flights can be performed by finding all flights with a service type in the group SVCE-CHTR) Groups can also be used be define Resource Profile rules (see section 3.3) or to define restrictions (see section 3.5). Fields! Group Name The name of the group! Group Base The flight attribute used as the basis for the group! Type This can either be : I-tem In this case the associated value must be a valid value for the group base (e.g. if the group base is AIRLINE then all item values must be valid airlines) G-roup In this case the associated value must represent a previously defined group. This enables groups to be defined that are in fact groups of groups. Page 20 of 47

21 3. Resources and Constraints 3.1 Overview SLOTIX stores an internal map of an airports resources. This map can be varied by dataset. The map represents all of the resources for the airport. A resource can be an actual attribute of the airport (such as the Runway, Terminals, Stands or Check-In Desks); or an artificial total (such as Airport Night Flights). In fact, a resource can be anything relating to the airport that you wish to maintain totals for. Each resource can have one or many associated profiles Profiles. They are used to determine which flights can affect the totals for the resource and in what manner. Constraints can then be defined against each resource defining the maximum values that the resource totals can reach over a specified time period. These limits can be varied by time, day of week or date range. SLOTIX allows you to grant a slot to a flight with an associated restriction that must at all times be met by that flight (the OSP allocations at ORY are an example of such a restriction). Page 21 of 47

22 3.2 Resource Maintenance Description This screen enables you to define the resource map for an airport. SLOTIX holds a different resource map for every dataset. Buttons When first opened the dataset is assumed to be the last dataset that you accessed. Therefore, when you first open the screen, if the displayed dataset is not the one that you require, you will need to access any of the maintenance screens described in section 2 to set the dataset correctly. Pressing this button will create a new resource as a child of the currently selected resource. Pressing this button will delete the current selected resource from the resource map. Pressing this button takes you to the Resource Profile Maintenance screen described in section 3.3 Page 22 of 47

23 Fields! Resource Type This field can have two possible values to indicate the way in which the resource is evaluated: Hierarchical A hierarchical resource is one that can only be used by flights that also use the resource s parent (e.g. in the above example resource 2A can only be used by flights that also use resource 2). Primary Also, if a hierarchical resource is used by a flight, then that flight cannot use any of the associated sibling resources. (e.g. if the flight uses resource 2A then it cannot use resources 2B, 2C etc.) Primary resources can be used by any flight irrespective of whether it uses the parent resource. Hierarchical resources cannot have primary children. Initially when you first create a dataset you are automatically allocated two resources for the dataset, the AIRPORT and TERMINALS resource. AIRPORT is a primary resource as all flights use the airport, any other general resources should be defined as descendants of the AIRPORT resource. As a flight can only use one terminal the terminal based resources should be defined as hierarchical descendants of the TERMINALS resource.! Sequence Number This field is used to indicate the order in which sibling resources are displayed on the screen. This field is particularly important for Hierarchical resources as it determines the order in which the resources will be verified. (e.g. in the above example resource 1 will be checked before resource 2 and if the flight is found to use resource 1, then resource 2 will not be checked at all).! Terminal This flag is used to indicate whether the resource represents an actual terminal. When a flight is added it is always assigned a 3-Letter terminal code that can be displayed on the main SLOTIX screen and reports etc. This value is determined as the first resource allocated to the flight that has this flag switched on. Page 23 of 47

24 ! Multiplier This field is used to indicate the flight usage total that is to be maintained for the resource. The field has 3 possible values : One Noise Seats Indicates that the total that is maintained is the total of actual flights that use the resource. Indicates that the total maintained is the total of the noise points for the flights that use the resource. Indicates that the total maintained is the total of the seats for the flights that use the resource.! Granularity This field is used to indicate the length of the interval for which the resource total is maintained. For example a granularity of 5 means that a separate total is maintained for every 5 minutes A granularity of zero means that a single total is maintained for the entire season. The granularity value must be a multiple of the granularity for the airport (or zero). Page 24 of 47

25 3.3 Resource Profile Maintenance Description For each resource, you will need to define the rules as to which flights use the resource, and the manner in which the flight uses the resource. These are known as Resource Profiles. Many different profiles can be held for a resource indicating the ways that the resource can be used. Resource Profiles are maintained using the Resource Profile maintenance screen which can be accessed by pressing the Resource Profile Maintenance button on the Resource Maintenance screen described in section 3.2. The resource profile maintenance screen is divided into two parts. The first half of the screen indicates the rules determining the types of flight that can use the profile (the Profile Rules ). The second half of the screen is used to maintain details of the way in which the resource is used (the Profile Detail ). As it may be possible for a flight to match more than one set of Profile Rules for a resource. If this is the case you will need to specify the sequence in which each profile is checked by using the sequence number at the top of the screen. Page 25 of 47

26 Profile Rules Maintenance Each line in the table at the top part of the screen represents a rule. A flight must match every one of the defined rules if it is to adopt the profile. Fields! Rule Type This field is used to indicate how the condition is to be evaluated to see if the rule is met. It has 3 possible values: Inside Outside All The specified field value on the line must be inside the specified range or group for the clause to be met. The specified field value on the line must be outside the specified range or group for the clause to be met. This rule type is used for specific resources that are always used by all flights (e.g. the RUNWAY resource). By setting the rule type to All on the first line in the table means that the profile will be adopted by every flight record. No other values need to be specified on the line in this case.! Field Name The attribute of the flight that is to be tested. Any attribute of a flight can be used as a basis for a profile rule (such as the Airline or the Service Type). SLOTIX also allows derived attributes to be used such as the Alliance for the airline or whether the next airport is a long or short haul airport.! Value Type Whether the evaluation is based on a range of possible values or on a group. The remaining fields allow you to specify the rage of values or the name of the group to be used. Some Examples 1) To specify that the resource is to be used by departure flights. Rule Type = Field Name = Value Type = Start Range = End Range = Inside Arrdep Range D D 2) To specify that Charter Flights cannot use this profile. Rule Type = Field Name = Value Type = Group = Outside Service_type Group SRVC-CHTR Page 26 of 47

27 Profile Detail Maintenance This table is used to show the way in which the flight will be used to increase the total for the resource if this profile is adopted. You can vary the resource usage details based on the dates that the flight operates on or by the day of the week (frequency). For example, you could specify different load factors for a passenger ( seats ) resource so that the flight uses a lower load factor at weekends but a higher load factor during the month of August. The remaining fields that can be entered are described below Fields! Method This field is usually set to Normal, which means that the time period that the resource is used for is based on the scheduled time of the flight. For example, the RUNWAY resource is normally used at the scheduled time for the flight, whereas a terminal resource could be used for a period some time before the flights departure. The alternative value for the Method field is Stand which is explained in detail below.! Start Range This value defines the time that the resource utilisation begins for lines with the Method value set to normal. The value should be entered as an offset in minutes from the scheduled time (e.g. 120 represents 2 hours before the flight arrives/departs). Entering 9999 in this field is used to mean that the utilisation total is to be incremented starting from midnight at the beginning of the day of operation.! End Range This value defines the time that the resource utilisation ends for lines with the Method value set to normal. The value should be entered as an offset in minutes from the scheduled time (e.g. 120 represents 2 hours before the flight arrives/departs). Entering 9999 in this field is used to mean that the utilisation total is to be incremented up to midnight at the end of the day of operation.! Qty / Load Factor Stands The two fields are used to determine the amount by which the total is to be incremented for the period and dates specified. The values in these fields are combined with the Multiplier value for the resource (see section 3.2) using the following formula : Resource Muliplier x Qty x Load Factor 100 If the user has set the Method field to have the value Stand then the utilisation for the resource will be incremented based on the flights time on the ground (i.e. the time between the flights arrival and its departure). The Stand method should only be associated with Arrival flights that have a defined turnround time. Page 27 of 47

28 The meaning of the Start and End Range fields are different for profile details using the Stand method. The Start Range is used to represent the utilisation start time as an Offset from the scheduled time for the flight (i.e. the arrival time for the turnround flight). The End Range is used to represent the utilisation start time as an Offset from the turnround time for the flight (i.e. the departure time for the turnround flight). Page 28 of 47

29 3.4 Constraint Maintenance Description This screen is used to define the limits on the utilisation of resources. Fields! Slot Length The length in minutes of the period over which the constraint is to be evaluated. For example, a one hour Runway constraint will have a slot length of 60.! Base Time The start time of the first slot in the day for this constraint. Normally this field will have the value of zero meaning that the first slot considered will begin at midnight. Page 29 of 47

30 However, if, for example, you would like to define a constraint that runs for 60 minutes starting at 30 minutes past each hour, you would need to set the slot length to 60 and the base time to 0030.! Check Deletions By default, constraints are only checked when the resource totals have been increased by the modification. Sometimes it is preferable to check a constraint whenever it is affected by a flight modification regardless of whether the total is increased or decreased. Setting the Check Deletions flag will ensure that the constraint is checked at all times.! Colours When a constraint is exceeded this is reported at the foot of the main screen. This field determines the colour that the text will be displayed in. Possible Values: Red The text will be displayed in Red Amber The text will be displayed in Amber None Setting the value to None means that the constraint will not be reported at the foot of the screen when the limit is broken. This option should be used when you wish to define a constraint that is to be used for reporting purposes only.! Availability These four fields determine the colour that the squares will appear on the enquiry detail screen. Up to 5 colours can be used on the screen, these are (in increasing order of importance): Blue, Green, Yellow, Amber and Red. The numbers entered in these four fields represent the number that the availability must be below for that colour to be used for a square on the enquiry detail screen. In the above example, the associated enquiry detail screen would show blue when 2 or more slots were available, green when 1 slot is available, yellow when the limit has been exactly reached (zero availability) and red when the constraint is broken. Because the Amber and Red values are the same, no amber squares will be displayed on the enquiry detail screen as Red would take priority.! Constraint Details The table at the foot of the screen allows you to separately specify every limit that exists for the constraint. The individual fields allow you to specify: The resource that the limit applies to The date range that each limit applies to The days of the week (frequency) that each limit applies to The times of day that each limit applies to Whether the limit applies to the Arrivals total, the Departures total or the combined totals of arrivals and departures (Total) The actual value of each limit Page 30 of 47

31 3.5 Restriction Maintenance Description Fields This screen allows you to define the restrictions that can be applied to a flight. When a flight is allocated a restriction code, the details for that flight (and any subsequent amendments) must conform to the rules specified for the restriction. If the flight fails to match all of the specified rules, the flight will be rejected by SLOTIX.! Operating Days The first restriction is based on the days of the week that the flight must operate on. If a flight has been allocated this restriction code then it may only operate on the days indicated in the Operating Days field.! Restriction Details Any additional rules are specified in the table at the foot of the screen. The fields that can be maintained by the user are: Field Name The attribute of the flight that is to be tested. Any attribute of a flight can be used as a basis for a profile rule (such as the Airline or the Service Type). SLOTIX also allows derived attributes to be used such as the Alliance for the airline or whether the next airport is a long or short haul airport. Rule Type This field is used to indicate how the condition is to be evaluated to see if the rule is met. It has 2 possible values: Inside The specified field value on the line must be inside the specified range or group for the clause to be met. Outside The specified field value on the line must be outside the specified range or group for the clause to be met. Value Type Whether the evaluation is based on a range of possible values or on a group. The remaining fields allow you to specify the rage of values or the name of the group to be used. Page 31 of 47

32 3.6 Worked Examples 1) A 60 minute runway constraint The granularity of the resource must be less than or equal to 60. The multiplier for the resource must be 1 A single resource profile should be defined for the resource. The Profile detail should consist of a single line representing the whole season. The from and to values for the time range should both be zero, the multiplier should be 1 and the load factor should be 100. The constraint should be defined with a slot length of 60. 2) A 60 minute rolling constraint, with a step length of 20 minutes A separate resource is required with a granularity of 20. The multiplier for the resource must be 1 A single resource profile should be defined for the resource. The Profile detail should consist of a single line representing the whole season. The From value for the time range should be 40 and the To value for the time range should be zero, the multiplier should be 1 and the load factor should be 100. This means that each flight will affect not only the slot that the flight operates in, but also the previous two slots. This results in the totals for each slot representing the number of flights that operate in that slot plus the number of flights that operate in the following two slots. The constraint should then be defined with a slot length of 20. 3) A whole season quota for an airline. A separate resource is required with a granularity of 0. The multiplier for the resource must be 1 A single resource profile should be defined for the resource. This profile will only be affected by flights for the airline. The Profile detail should consist of a single line representing the whole season. The from and to values for the time range should both be zero, the multiplier should be 1 and the load factor should be 100. The constraint should be defined with a slot length of 0. Page 32 of 47

33 4) Stand Constraints The granularity of a stand resource should be equal to the airport slot length (normally 5 minutes). Three profiles will need to be created for the resource: The first will be adopted by all arrival flights that have an associated turnround flight. This profile will have a method of Stand and from and to times of 0. Thus the flight will utilise the resource from the time of the flights arrival until it s departure. The second will be adopted by all arrival flights that do not have an associated departure turnround flight. This profile will have a method of Normal, the from time will be zero but the end time will be Thus the flight will increase the resource from the flights arrival time until the end of the day (as the turnround details are unknown). The third will be adopted by all departure flights that do not have an associated turnround flight. This profile will have a multiplier of 1 and a method of Normal, the from time will be zero but the end time will be Thus the flight will reduce by one the total for the resource from the flights departure time until the end of the day (as the turnround details are unknown). A simple constraint (with the same slot length as the resource) can then be created. 5) Terminal Constraints The granularity of a terminal resource should be equal to the length of the constraint that is to be defined. The multiplier should be set to Seats. For the sake of this example we will define a 10 minutes terminal constraint based on the total of passengers who have checked into the terminal for the flight. Different arrival rates will be defined for domestic or non-domestic flights. Profile 1 Domestic Departures For this example, 25% of the total passengers for the flight can be assumed to be in the terminal 120 minutes before departure. 50% can be assumed to be in the terminal 90 minutes before departure. 75% can be assumed to be in the terminal 60 minutes before departure. 100% can be assumed to be in the terminal 30 minutes before departure. All passengers can be assumed to be on the flight and out of the terminal 10 minutes before the flight. The load factor for domestic flights will be 80%. i.e. 100% Seconds before Departure Time Page 33 of 47

34 The rules for the profile will be: Arrdep in range D-D Prev Next Airport Domestic/Int/Schengen in range D-D Orig Dest Airport Domestic/Int/Schengen in range D-D The profile detail for the profile will consist of 4 lines: Time Range = 120 to 100, Multiplier 25, Load Factor 80 Time Range = 90 to 70, Multiplier 50, Load Factor 80 Time Range = 60 to 40, Multiplier 75, Load Factor 80 Time Range = 30 to 10, Multiplier 100, Load Factor 80 Profile 2 Non-Domestic Departures For this example, 25% of the total passengers for the flight can be assumed to be in the terminal 240 minutes before departure. 50% can be assumed to be in the terminal 120 minutes before departure. 100% can be assumed to be in the terminal 60 minutes before departure. All passengers can be assumed to be on the flight and out of the terminal 20 minutes before the flight. The load factor for domestic flights will be 80%. i.e. 100% Seconds before Departure Time The only rule for this profile will be: Arrdep in range D-D as all domestic departure flights will have already adopted the first profile. The profile detail for the profile will consist of 3 lines: Time Range = 240 to 130, Multiplier 25, Load Factor 80 Time Range = 120 to 70, Multiplier 50, Load Factor 80 Time Range = 60 to 20, Multiplier 100, Load Factor 80 The limit for the associated constraint will need to be set to be 100 times the actual limit due to the multipliers used in the profile. Page 34 of 47

35 4. Personalisation 4.1 Overview The remaining screens allow the user to modify how details are displayed on the SLOTIX screens for the users. Special screens are also available to allow the user to customise the functionality of the SSIM parser and the Merge Button. Page 35 of 47

36 4.2 Template Maintenance Description This screen is used to specify the fields that can appear on many of the screens in SLOTIX. The user can create a number of different templates for one screen. Fields! Table Name This field is not currently used by SLOTIX. The contents are not validated an any way. It is likely that this field will be used in a future version of SLOTIX! Owner! Group Access! World Access In the future users will be able to specify Private templates that only they (or other users in the same group) can access. For the moment these fields have no meaning.! Screen Name The name of the screen to which the template applies, possible values: Main The columns on the main SLOTIX screen Add The additional fields at the foot of the Flight Addition screen Change The columns on the Flight Amendment screen Delete The columns on the Flight Deletion screen Detail The fields on the Flight Detail screen Page 36 of 47

37 Find The available columns on the Flight Retrieval screen (not yet implemented) History The columns on the History screen Message The fields displayed on the right hand side of the Message Detail screen Offers The columns on the offer screen Reporting The columns displayed on the flight detail reports Sort The available columns on the Sort screen (not yet implemented) Usage The columns on the Resource Flight Usage screen.! Default Template This button should be used to indicate that the template is the default that is displayed when the user first enters the screen. You may only specify one template for each screen name.! Template Details The list on the left-hand side of the screen represents the attributes of the flight that are available to be defined to the template. Copy Button The list on the right-hand side of the screen represents the columns already defined for the template. The sequence that the items appear in this list represent the order that they will appear on the screen. The buttons between the two lists allow you to Add, Remove and cahnge the order of the attributes held for the template on the right-hand side list. This button allows you to create a new template that is a copy of the current template. Page 37 of 47

38 4.3 Flight Attribute Maintenance Description This screen allows you to define the descriptions that appear in column headings (such as on the main screen etc.) and as field descriptions (for example on the right-hand side of the Message Detail screen). Fields! Item The SLOTIX internal name for the attribute.! Short Description The text that should appear at the head of the column for this attribute.! Long Description The text that should appear as a field description for this attribute. All of the other fields are used internally by SLOTIX and should not be modified by the user. Page 38 of 47

39 4.4 Merge Parameter Maintenance Description This screen is used to specify the columns that are to be used when checking to determine whether the flight details can be merged when the user presses the Merge button on the main SLOTIX screen. You will be first asked to specify the Coordinated Airport and Season that you wish to maintain details for. The display shows all of the datasets that exist for this Coordinated Airport and Season. You can select the relevant columns by ticking the appropriate squares. Page 39 of 47

40 4.5 SSIM Relevance Maintenance Description This screen is used to specify the columns that are to be used when checking D and C lines on SSIM messages. This facility has not yet been fully implemented in SLOTIX. You will be first asked to specify the Coordinated Airport and Season that you wish to maintain details for. The display shows all of the datasets that exist for this Coordinated Airport and Season. You can select the relevant columns by ticking the appropriate squares. Page 40 of 47

41 Appendix A SLOTIX Flight Attributes The following pages list all of the attributes that can be used throughout SLOTIX in Templates and Retrievals, for specifying the rules for the utilisation of resources, the definition of restrictions, merge parameters and SSIM relevance parameters. The long and short descriptions for these attributes can be personalised using the flight attributes maintenance screen. The Item names associated with each attribute are those that are used on the resource profile and restriction maintenance screens. All other screens use the long descriptions for flight attributes. Only certain attributes should appear on the Add and Change screens, these are marked with a Y in the Add Change Screen column. Some attributes are only relevant for the OPERATED dataset, these are marked with a * in the OPERATED dataset only column. Page 41 of 47

42 Long Description Short Desc Item Code Description Add Change OPERATED Screen Dataset Only Adjusted Frequency Adj.Freq ADJ_FREQUENCY Not currently used N Adjusted Period End Adj.Pd.End ADJ_PERIOD_END Not currently used N Adjusted Period Start Adj.Pd.St. ADJ_PERIOD_START Not currently used N Adjusted Total Ops Adj.Ops ADJ_TOTAL_OPS Not currently used N Age Age AGE The number of years for which the flight has been Y operating Aircraft A/c AIRCRAFT_TYPE The aircraft for the flight Y Aircraft Chapter Ac Chapt. AIRCRAFT_CHAPTER The chapter number of the aircraft for the flight N Aircraft ICAO Code Ac ICAO AIRCRAFT_ICAO The ICAO code of the aircraft for the flight Y Aircraft Parent Ac Parent AIRCRAFT_PARENT The parent airacraft of the aircraft for the flight N Aircraft Stand Requirements Ac Stands AIRCRAFT_STANDS The stand requirements for the aircraft for the flight N Aircraft User1 Ac User1 AIRCRAFT_USER1 The first user field value for the aircraft for the flight N Aircraft User2 Ac User2 AIRCRAFT_USER2 The second user field value for the aircraft for the N flight Aircraft User3 Ac User3 AIRCRAFT_USER3 The third user field value for the aircraft for the flight N Aircraft Weight Ac Wt. AIRCRAFT_WEIGHT The weight of the aircraft for the flight N Aircraft Wide/Narrow Ac W/N AIRCRAFT_WIDTH The wide/narrow flag value for the aircraft for the N flight Airline CIE AIRLINE The airline for the flight record Y Airline Alliance CIE All'nc AIRLINE_ALLIANCE The alliance for the airline N Airline Alternative Code CIE Alt.Cd AIRLINE_ALT_CODE The alternative code for the airline N Airline Country CIE Cntry AIRLINE_COUNTRY The country for the airline N Airline Default Terminal CIE <Term> AIRLINE_DEF_TERM The default terminal for the airline N Airline Responsible Rsp AIRLINE_RESPBL The coordinator responsible for the airline N Airline SSIM Code CIE SSIM AIRLINE_SSIM The code used on SSIM messages for the airline N Airline User1 CIE User1 AIRLINE_USER1 The first user field for the airline N Airline User2 CIE User2 AIRLINE_USER2 The second user field for the airline N Airline User3 CIE User3 AIRLINE_USER3 The third user field for the airline N Airport Apt AIRPORT The coordinated airport N Amend User Amd by AMEND_USER The name of the user that last amended the flight record N Amended Amended DATE_LAST_MOD The date on which the flight record was last amended N Arr. Prev/Next Arr P/N ARR_PN_STN The previous/next airport code for arrival flights (this N field is blank for departure flights) ArrDep A/D ARRDEP Arrival or Departure Y Call Sign Call Sign CALL_SIGN The call sign for the flight Y Page 42 of 47

43 Long Description Short Desc Item Code Description Add Change OPERATED Screen Dataset Only Claimed Historic? HS? CLAIMED_HS Not currently used N Client Reference Client Ref CLIENT_REF The airlines reference for this flight record Y Code Share Cd.Share CODE_SHARE_ID Not currently used N Code Share Memo CS.Memo CODE_SHARE_MEMO Not currently used N Code Share Type C/s Tp CODE_SHARE_TYPE N=no code share, C=code share, F=franchise Y Create User Cre. CREATE_USER The user that first created the flight record N Created Created DATE_CREATED The date on which the flight record was first created N Dataset Dataset DATA_SET The Data Set for the flight record N Dep. Prev/Next Dep P/N DEP_PN_STN The previous/next airport code for departure flights N (this field is blank for arrival flights) Destination Dst DEP_OD_STN The origin/destination airport code for departure N flights (this field is blank for arrival flights) Flexibility End Flex.End FLEXIBILITY_END The end time of the airlines requested flexibility time Y range Flexibility Flag Flex? FLEXIBILITY_FLAG Whether the airline has specified a flexibility time N range Flexibility Start Flex.St. FLEXIBILITY_START The start time of the airlines requested flexibility time Y range Flight Flight FLT_NO The flight number of the flight Y Flight number Flt FLIGHT_COMPOSITE The combined airline code, flight number and suffix N (e.g. AF123X) Frequency Freq. FREQUENCY The frequency of the flight Y Held By User Held by USER_HELD_NAME If the flight is currently locked by another user - this N field contains the users name Hist. Airline HS CIE HS_AIRLINE The airline code for the flight record as it appears on N * the HISTORIC dataset Hist. Suffix HS Sfx HS_SUFFIX The suffix for the flight record as it appears on the HISTORIC dataset N * Hist.Flight HS Flt HS_FLT_NO The flight number for the flight record as it appears on N * the HISTORIC dataset Historic Flight number Hist Flt The combined airline code, flight number and suffix N * HS_FLIGHT_COMPOSIT E (e.g. AF123X) for the flight record as it appears on the HISTORIC dataset Historic Reference HS Ref HS_REFERENCE The historic reference for the flight (linking it to the N * associated record on the HISTORIC dataset) HS Time HS Tm HS_TIME The time for the flight record as it appears on the HISTORIC dataset N * Page 43 of 47

44 Long Description Short Desc Item Code Description Add Change OPERATED Screen Dataset Only Maximum TR Time Max TR MAX_TR_TIME The maximum turnround time accepted for this flight Y Merge Key Mge Key MERGE_KEY Used Internally N Message Id Msg Id MSG_ID The id for the message that last modified the flight Y * Minimum Tr Time Min Tr MIN_TR_TIME The minimum turnround time accepted for this flight Y Msg Block No Msg BlK MSG_BLOCK_NO The block number within the message that last Y * modified the flight N/A N/A FEM_REQ_ID Used Internally N New Entrant NE NEW_ENTRANT Whether the flight can claim new-entrant status Y Noise Level Noise NOISE_LEVEL The noise rating for the flight Y Non SSIM relevant SSIM N/Rel NON_SSIM_RELEVANT Used Internally N Norm Pd End Nm P/End NORM_PERIOD_END In reporting, this field is used to adjust the end date N on the flight record to fit the parameters of the report Norm Pd Start Nm P/St NORM_PERIOD_START In reporting, this field is used to adjust the start date N on the flight record to fit the parameters of the report Norm Total Ops Norm Ops. NORM_TOTAL_OPS In reporting, this field is used to adjust the total N operations for the flight record to fit the parameters of the report Norm. Frequency Nm Freq NORM_FREQUENCY In reporting, this field is used to adjust the frequency N for the flight record to fit the parameters of the report Num DoW #DoW NUMBER_DOW The number of days of the week operated by the N flight. Num Weeks #Wks NUMBER_WEEKS The number of weeks operated by the flight. N Offer Expires Off Exp OFFER_EXPIRES For offer records, the date that the offer will expire Y Offer Identification Off Id OFFER_ID For offer records, the unique id for the offer N offer Ind Off? OFFER_IND Whether an unaccepted offer exists for the flight N Op Airline Op CIE OPERATING_AIRLINE The operating airline (i.e. the code for the airline that Y will actually operate the slot rather than the airline that owns the slot) Op Hist Corresp OH Corr OP_HIST_CORRESP Whether the flight has an associated record on the N * HISTORIC dataset Op_CIE Alliance OpC All'nc OP_CIE_ALLIANCE The alliance for the airline operating the flight N Op_CIE Alternative Code OpC Alt.Cd OP_CIE_ALT_CODE The alternative code for the airline operating the flight N Op_CIE Country OpC Cntry OP_CIE_COUNTRY The country for the airline operating the flight N Op_CIE Default Terminal OpC <Term> OP_CIE_DEF_TERM The default terminal for the airline operating the flight N Op_CIE Responsible OpC Respbl OP_CIE_RESPBL The coordinator responsible for the airline operating the flight N Page 44 of 47