maintenance overview - cohor · the three-letter iata code for the airport.! ... reply to an scr...

COHOR 17/01/06 15:56

of 47

SLOTIXMAINTENANCE OVERVIEW

COHOR 17/01/06 15:56

of 47

1. INITIAL DEFINITION 3

1.1 OVERVIEW 31.2 COORDINATED AIRPORT MAINTENANCE 41.3 SEASON MAINTENANCE 61.4 SIMPLE DICTIONARY CODE MAINTENANCE 71.5 SIMPLE DICTIONARY MAINTENANCE 81.6 USER MAINTENANCE 91.7 SERVER INSTANCE MAINTENANCE 10

2. DATASETS 11

2.1 OVERVIEW 112.2 DATASET MAINTENANCE 122.3 AIRCRAFT MAINTENANCE 142.4 AIRLINE MAINTENANCE 162.5 AIRPORT MAINTENANCE 182.6 GROUP MAINTENANCE 20

3. RESOURCES AND CONSTRAINTS 21

3.1 OVERVIEW 213.2 RESOURCE MAINTENANCE 223.3 RESOURCE PROFILE MAINTENANCE 253.4 CONSTRAINT MAINTENANCE 293.5 RESTRICTION MAINTENANCE 313.6 WORKED EXAMPLES 32

4. PERSONALISATION 35

4.1 OVERVIEW 354.2 TEMPLATE MAINTENANCE 364.3 FLIGHT ATTRIBUTE MAINTENANCE 384.4 MERGE PARAMETER MAINTENANCE 394.5 SSIM RELEVANCE MAINTENANCE 40

APPENDIX A – SLOTIX FLIGHT ATTRIBUTES 41

COHOR 17/01/06 15:56

of 47

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 theSSIM Parser).

COHOR 17/01/06 15:56

of 47

1.2 Coordinated Airport Maintenance

DescriptionThis screen enables you to define the airports that you coordinate in SLOTIX.

Fields! Airport

The three-letter IATA code for the Airport.

! Slot GranularityThis field is used to define how the slot times are to be held in the airport. Normally this fieldwill 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 inSLOTIX as 1200.

! Coordination LevelIndicates whether the Airport is F-ully or C-oordinated. This field is purely informational fieldthat is not actually used in SLOTIX.

! Night Curfew DetailsThese fields were originally designed to enable the easy definition of the night curfew forarrivals and departures. As SLOTIX was developed it was decided that this information wouldbe 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 AddressThe SITA address for incoming messages for this airport (this field MUST be enteredcorrectly).

COHOR 17/01/06 15:56

of 47

! Copy AddressYou may require that every reply to an SCR be copied to other SITA addresses. These fieldsallow you to define such addresses.

! Reply SI FooterThese fields can be used to define the SI text that is to appear by default at the foot of everyreply to an SCR message that is sent from this coordinated airport.

! Pre-Coordination SI FooterDuring the submission period just prior to the IATA Scheduling Conference, the airport mayrequire that a different SI test appears on reply to the submission SCR messages. These fieldsenable this SI text to be defined.

! General Aviation AirportSometimes general aviation flights operate to and from airports that do not have an associated3-letter IATA code. This field represents the value that needs to be placed in theorigin/destination or previous/next fields for the flight to indicate that the actual airport willinstead be held in the associated 4-letter ICAO code fields.

! General Aviation AircraftSometimes general aviation flights operate using aircraft that do not have an associated 3-letterIATA code. This field represents the value that needs to be placed in the aircraft field for theflight to indicate that the actual aircraft details will instead be held in the associated 4-letterICAO code field.

COHOR 17/01/06 15:56

of 47

1.3 Season Maintenance

DescriptionThis 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 modifiedby the user.

FieldsThe remaining fields are maintainable but are not used explicitly by SLOTIX. This may be used byexternal applications to determine when certain external reports are produced etc…

! Pre-CoordinationThe date after which the airlines initial submissions are accepted.

! SISC Conference Start/EndThe dates of the IATA Scheduling Conference for this season.

! Slot ReturnThe slot return date for this season.

COHOR 17/01/06 15:56

of 47

1.4 Simple Dictionary Code Maintenance

DescriptionThis screen (and the one described in section 1.5) are used to define codes that are used throughout thesystem 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 LengthThe number of characters for the code (e.g. Service Types have a code length of 1).

! Force NumericIndicates that the code must have a numeric value.

! Numeric DescriptionIndicates that the description field for the code must be numeric.

! User MaintainedSome dictionary codes will be used internally and therefore cannot be changed by the user.These will have the value Y set in this field.

NoteOnly the system ‘Super-User’ (currently defined as ADP_MANAGER) can access this screen

COHOR 17/01/06 15:56

of 47

1.5 Simple Dictionary Maintenance

DescriptionThis 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 ofthe possible 2-Letter codes for the different countries).

! DescriptionThe associated description for the code.

! Live StatusThis should always be set to L. It is used to indicate whether this code is still in operation orhas been dropped or replaced. L indicates that the code is in operation (“Live”).

COHOR 17/01/06 15:56

of 47

1.6 User Maintenance

DescriptionThis screen is new to version 3 of SLOTIX and allows you to store data for every that is allowed tomaintain 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 thatflight is assigned a unique reference number which is comprised of the users triptych and thenext 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 automaticallyby SLOTIX.

COHOR 17/01/06 15:56

of 47

1.7 Server Instance Maintenance

DescriptionSLOTIX has a number of external “Servers”.

These are programs that process incoming files from other systems and use them to update the SLOTIXdatabase.

This table is used to specify where the server can locate the incoming files, where the file should becopied 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 receivedfrom a SITA Gateway and converts them into XML Formatted files. The XML Server takes theseconverted files and uses them to update the data in SLOTIX.

Fields! Username

The username used by the server to connect to SLOTIX.

! Incoming DirectoryThe directory where the files are to be read from.

! Output DirectoriesWhere the converted file (or the reply file) is to be placed. Two possible directories can bespecified depending on the format of the file.

! Error DirectoryIf an incoming file is formatted incorrectly (e.g. it does not match chapter 6 standards), it willbe copied into this directory.

! Processed DirectoryWhere the original file is copied to when the server has finished processing it.

NoteThe drive used in the definition of these directories must be known to all SLOTIX users. If not, forexample, the user will not be able to send replies to SCR messages.

COHOR 17/01/06 15:56

of 47

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:

OPERATEDThis dataset is used to hold the flights that the airlines intend to operate.

HISTORICThis dataset is used for fully coordinated airports only, but is required to exist even for partiallyor 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.

COHOR 17/01/06 15:56

of 47

2.2 Dataset Maintenance

DescriptionThis 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 CriticalResource and Constraint fields, as you will not yet have been able to define any resources andconstraints. Therefore, you should initially leave these fields blank and return to this screenwhen the resources and constraints have been defined for the dataset.

! StatusMost of the time this field is purely an informational field that is used to indicate the currentstatus 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 examplethe 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 thisdataset 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. Allmessages are automatically placed by the SSIM Parser into its associatedError Directory.

COHOR 17/01/06 15:56

of 47

PRE-COORDINATION =The SSIM parser will only accept SCR submission requests and no SIRrequests.

! AvailabilityThis field is currently an informational field not yet used by SLOTIX. It is intended to be usedin the future to allow you to specify the types of users that can access this dataset.

! Turnround CriticalThis flag is used to indicate that Turnround flight details may not be separated by users whenusing the merge facility (i.e. whether the ‘Separate Turnrounds’ option is available on theMerge screen for this dataset).

Note : All of the remaining fields on this screen relate to the OPERATED dataset only, for all otherdatasets these values have no meaning.

! Automatic Message HandlingThis flag is reserved for use in a later version of SLOTIX. It will be used to indicate that SCRmessages received for this dataset will be processed automatically as long as no limits arebroken.

! HS Addition Limit! HS Deletion Limit

These fields are used for coordinated airports to decide when a change made to theOPERATED dataset should also be made to the HISTORIC dataset. For example: If a flightaddition represents a number of weeks that is greater than the HS Addition Limit, then thatflight will be added automatically to the HISTORIC dataset.

For non-fully coordinated airports these fields should be both set to 99 to ensure that theHISTORIC dataset is never updated.

COHOR 17/01/06 15:56

of 47

2.3 Aircraft Maintenance

DescriptionThis 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 codebelongs.

! ICAO CodeThe 4 Letter ICAO Code for the aircraft type.

! Wide/NarrowWhether the aircraft is W-ide bodied or N-arrow bodied.

! Stand RequirementThe number of stands required at this airport to hold the aircraft. This field is only meaningfulfor airports where stand capacity is an issue. It can be set to 1 for all other airports.

! ChapterThe aircraft chapter number

! WeightA numeric field that can be used to define constraints (e.g. only a certain number of aircraftexceeding a particular weight value can be accepted during a one-hour period).

COHOR 17/01/06 15:56

of 47

! Arrival Noise! Departure Noise

The noise rating allocated to the aircraft for its arrival and departure at the airport. Everyairport may have different methods for calculating the noise rating for an aircraft, or may havenone at all, in which case these fields can be set to 9999.

! Item IdUsed 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 forthis aircraft type. This information can then be displayed in SLOTIX against the flight data onthe main screen and can be used in reports and retrievals.

COHOR 17/01/06 15:56

of 47

2.4 Airline Maintenance

DescriptionThis 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 mainscreen.

! Alternative CodeIf the 2-Letter code has been used to populate the Airline field then the 3-Letter code should beused here (or vice-versa). If the airline only uses one code then it should appear in both fields.

! SSIM CodeThe code that the Airline normally uses on SCR messages.

! CountryThe base country for the airline, using the 2-Letter IATA country codes (use XX if the countryis not known or is not considered important).

! AllianceThe alliance that the airline is a member of . The list of valid alliances can be maintained usingthe dictionary screens (see 1.4 and 1.5). Use ‘NONE’ if the airline does not belong to anyalliance.

! Default TerminalThe default terminal for the Airline. This field is often used when specifying the terminalallocation rules on the resource profile maintenance screen (see section 3.3).

COHOR 17/01/06 15:56

of 47

! Operation Limits! Night Quotas

These fields were originally intended to be used to specify online quota constraints, but it wasfelt that this could be achieved more accurately using resource and constraint maintenance (seesection 3). Therefore these fields are no longer used by SLOTIX but are retained forinformational purposes only.

! Allowed To OperateShould be always set to ‘Y’. SLOTIX no longer checks this field.

! ResponsibleThe triptych (see section 1.6) for the person who is responsible for this airline. This field canbe used in SLOTIX retrievals and reports. If the airport does not allocate portfolios to airlinesto individual coordinators then you can just set this field to XXX.


These fields are simply “memo” fields that can be used to store airport specific information forthis airline. This information can then be displayed in SLOTIX against the flight data on themain screen and can be used in reports and retrievals.

COHOR 17/01/06 15:56

of 47

2.5 Airport Maintenance

DescriptionMaintains the valid airport codes for the dataset.

Fields! Airport

The 3-Letter IATA code for the airport.

! ICAO CodeThe 4-Letter ICAO code for the airport

! Latitude! Longitude

Optional informational fields that could be used in reporting. If this information is not relevantto the airports being coordinated then these fields can be left to zero.

! CountryThe country for the airport, using the 2-Letter IATA country codes (use XX if the country isnot known or is not considered important).

! Domestic/Int/SchengenWhether the airport is considered D-omestic, I-nternational or S-chengen.

! Long/Short HaulWhether the airport is considered L-ong or S-hort haul.

! Default TerminalSome airports allocate terminals based on the destination for the flight (for example CDGallocates the terminals for Air France flights within terminal 2 based on their destination). Thisfield can be used to hold this information.

! Item IdUsed internally. Should initially be set to zero.

COHOR 17/01/06 15:56

of 47


These fields are simply “memo” fields that can be used to store airport specific information forthis airport. This information can then be displayed in SLOTIX against the flight data on themain screen and can be used in reports and retrievals.

COHOR 17/01/06 15:56

of 47

2.6 Group Maintenance

DescriptionThis 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 byfinding 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 (seesection 3.5).

Fields! Group Name

The name of the group

! Group BaseThe flight attribute used as the basis for the group

! TypeThis 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-roupIn this case the associated value must represent a previously defined group.This enables groups to be defined that are in fact “groups of groups”.

COHOR 17/01/06 15:56

of 47

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 (suchas the Runway, Terminals, Stands or Check-In Desks); or an artificial total (such as Airport Night Flights). Infact, 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 canaffect 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 canreach 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 thatflight (the OSP allocations at ORY are an example of such a restriction).

COHOR 17/01/06 15:56

of 47

3.2 Resource Maintenance

DescriptionThis screen enables you to define the resource map for an airport. SLOTIX holds a different resourcemap for every dataset.

When first opened the dataset is assumed to be the last dataset that you accessed. Therefore, when youfirst open the screen, if the displayed dataset is not the one that you require, you will need to access anyof the maintenance screens described in section 2 to set the dataset correctly.

Buttons

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

COHOR 17/01/06 15:56

of 47

Fields! Resource Type

This field can have two possible values to indicate the way in which the resource is evaluated:

HierarchicalA hierarchical resource is one that can only be used by flights that also usethe resource’s parent (e.g. in the above example resource 2A can only be usedby flights that also use resource 2).

Also, if a hierarchical resource is used by a flight, then that flight cannot useany of the associated “sibling” resources. (e.g. if the flight uses resource 2Athen it cannot use resources 2B, 2C etc.)

PrimaryPrimary resources can be used by any flight irrespective of whether it usesthe parent resource. Hierarchical resources cannot have “primary” children.

Initially when you first create a dataset you are automatically allocated two resources for thedataset, the AIRPORT and TERMINALS resource.

AIRPORT is a primary resource as all flights use the airport, any other “general” resourcesshould be defined as “descendants” of the AIRPORT resource . As a flight can only use oneterminal the “terminal” based resources should be defined as “hierarchical” descendants of theTERMINALS 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 inwhich the resources will be verified. (e.g. in the above example resource 1 will be checkedbefore resource 2 and if the flight is found to use resource 1, then resource 2 will not bechecked 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 onthe main SLOTIX screen and reports etc.

This value is determined as the first resource allocated to the flight that has this flag switchedon.

COHOR 17/01/06 15:56

of 47

! 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 Indicates that the total that is maintained is the total of actual flights that usethe resource.

Noise Indicates that the total maintained is the total of the noise points for theflights that use the resource.

Seats Indicates that the total maintained is the total of the seats for the flights thatuse the resource.

! Granularity

This field is used to indicate the length of the interval for which the resource total ismaintained. For example a granularity of 5 means that a separate total is maintained for every 5minutes

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).

COHOR 17/01/06 15:56

of 47

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 mannerin which the flight uses the resource.

These are known as “Resource Profiles”. Many different profiles can be held for a resource indicatingthe ways that the resource can be used.

Resource Profiles are maintained using the Resource Profile maintenance screen which can be accessedby pressing the ‘Resource Profile Maintenance’ button on the Resource Maintenance screen describedin section 3.2.

The resource profile maintenance screen is divided into two parts. The first half of the screen indicatesthe rules determining the types of flight that can use the profile (the “Profile Rules”). The second half ofthe 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 thecase you will need to specify the sequence in which each profile is checked by using the sequencenumber at the top of the screen.

COHOR 17/01/06 15:56

of 47

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 TypeThis 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 The specified field value on the line must be inside the specified range or group forthe clause to be met.

Outside The specified field value on the line must be outside the specified range or group forthe clause to be met.

All 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 thetable 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 NameThe 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 theService Type). SLOTIX also allows “derived attributes” to be used such as the Alliance for theairline or whether the next airport is a long or short haul airport.

! Value TypeWhether 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 beused.

Some Examples1) To specify that the resource is to be used by departure flights.

Rule Type = InsideField Name = ArrdepValue Type = RangeStart Range = DEnd Range = D

2) To specify that Charter Flights cannot use this profile.

Rule Type = OutsideField Name = Service_typeValue Type = GroupGroup = SRVC-CHTR

COHOR 17/01/06 15:56

of 47

Profile Detail Maintenance

This table is used to show the way in which the flight will be used to increase the total for the resourceif this profile is adopted.

You can vary the resource usage details based on the dates that the flight operates on or by the day ofthe 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 monthof 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 foris based on the scheduled time of the flight. For example, the RUNWAY resource is normally usedat the scheduled time for the flight, whereas a “terminal” resource could be used for a period sometime 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 setto normal. The value should be entered as an offset in minutes from the scheduled time (e.g. –120represents 2 hours before the flight arrives/departs).

Entering –9999 in this field is used to mean that the utilisation total is to be incremented startingfrom 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 tonormal. The value should be entered as an offset in minutes from the scheduled time (e.g. –120represents 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 tomidnight at the end of the day of operation.

! Qty / Load Factor

The two fields are used to determine the amount by which the total is to be incremented for theperiod and dates specified. The values in these fields are combined with the Multiplier value for theresource (see section 3.2) using the following formula :

Resource Muliplier x Qty x Load Factor 100

Stands

If the user has set the Method field to have the value “Stand” then the utilisation for the resourcewill be incremented based on the flights time on the ground (i.e. the time between the flights arrivaland its departure).

The “Stand” method should only be associated with Arrival flights that have a defined turnroundtime.

COHOR 17/01/06 15:56

of 47

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 timefor 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 timefor the flight (i.e. the departure time for the turnround flight).

COHOR 17/01/06 15:56

of 47

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 hourRunway 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 zeromeaning that the first slot considered will begin at midnight.

COHOR 17/01/06 15:56

of 47

However, if, for example, you would like to define a constraint that runs for 60 minutes starting at 30minutes 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 ofwhether 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 RedAmber The text will be displayed in AmberNone 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 aconstraint 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 thatcolour 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 wereavailable, 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 squareswill 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 arrivalsand departures (Total)

• The actual value of each limit

COHOR 17/01/06 15:56

of 47

3.5 Restriction Maintenance

Description

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.

Fields

! Operating Days

The first restriction is based on the days of the week that the flight must operate on. If a flight has beenallocated 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 theService Type). SLOTIX also allows “derived attributes” to be used such as the Alliancefor 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 orgroup for the clause to be met.

· Outside The specified field value on the line must be outside the specified range orgroup 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 tobe used.

COHOR 17/01/06 15:56

of 47

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 valuesfor 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.


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 forthe time range should be –40 and the ‘To’ value for the time range should be zero, the multiplier shouldbe 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 previoustwo slots. This results in the totals for each slot representing the number of flights that operate in thatslot 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.


A single resource profile should be defined for the resource. This profile will only be affected by flightsfor the airline.

The Profile detail should consist of a single line representing the whole season. The from and to valuesfor 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.

COHOR 17/01/06 15:56

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 profilewill have a method of ‘Stand’ and from and to times of 0. Thus the flight will utilise the resourcefrom 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 turnroundflight. This profile will have a method of ‘Normal’, the from time will be zero but the end time willbe 9999. Thus the flight will increase the resource from the flights arrival time until the end of theday (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 butthe end time will be 9999. Thus the flight will reduce by one the total for the resource from theflights 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 bedefined. 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 ofpassengers who have checked into the terminal for the flight. Different arrival rates will be defined fordomestic 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 theterminal 120 minutes before departure. 50% can be assumed to be in the terminal 90 minutesbefore 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 beassumed 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%

of 47

-120 -90 -60 -30 0

Seconds before Departure Time

COHOR 17/01/06 15:56

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 theterminal 240 minutes before departure. 50% can be assumed to be in the terminal 120 minutesbefore departure. 100% can be assumed to be in the terminal 60 minutes before departure. Allpassengers can be assumed to be on the flight and out of the terminal 20 minutes before theflight.

The load factor for domestic flights will be 80%.

i.e.

The limultip

100%

of 47

-240 -180 -120 -60 0

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

mit for the associated constraint will need to be set to be 100 times the actual limit due to theliers used in the profile.

Seconds before Departure Time

COHOR 17/01/06 15:56

of 47

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 theMerge Button.

COHOR 17/01/06 15:56

of 47

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 islikely 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 inthe same group) can access.

For the moment these fields have no meaning.

! Screen NameThe 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

COHOR 17/01/06 15:56

of 47

• 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 TemplateThis button should be used to indicate that the template is the default that is displayed whenthe user first enters the screen. You may only specify one template for each screen name.

! Template DetailsThe list on the left-hand side of the screen represents the attributes of the flight that areavailable to be defined to the template.

The list on the right-hand side of the screen represents the columns already defined for thetemplate. The sequence that the items appear in this list represent the order that they willappear on the screen.

The buttons between the two lists allow you to Add, Remove and cahnge the order of theattributes held for the template on the right-hand side list.

Copy Button

This button allows you to create a new template that is a copy of the current template.

COHOR 17/01/06 15:56

of 47

4.3 Flight Attribute Maintenance

DescriptionThis screen allows you to define the descriptions that appear in column headings (such as on the mainscreen 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 DescriptionThe text that should appear at the head of the column for this attribute.

! Long DescriptionThe 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.

COHOR 17/01/06 15:56

of 47

4.4 Merge Parameter Maintenance

DescriptionThis screen is used to specify the columns that are to be used when checking to determine whether theflight 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 detailsfor.

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.

COHOR 17/01/06 15:56

of 47

4.5 SSIM Relevance Maintenance

DescriptionThis screen is used to specify the columns that are to be used when checking D and C lines on SSIMmessages.

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 detailsfor.

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.

COHOR 17/01/06 15:56

of 47

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 SSIMrelevance parameters.

The long and short descriptions for these attributes can be personalised using the flight attributes maintenancescreen.

The Item names associated with each attribute are those that are used on the resource profile and restrictionmaintenance 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 ‘AddChange Screen’ column.

Some attributes are only relevant for the OPERATED dataset, these are marked with a ‘*’ in the ‘OPERATEDdataset only’ column.

COHOR 17/01/06 15:56

of 47

Long Description Short Desc Item Code Description Add ChangeScreen

OPERATEDDataset Only

Adjusted Frequency Adj.Freq ADJ_FREQUENCY Not currently used NAdjusted Period End Adj.Pd.End ADJ_PERIOD_END Not currently used NAdjusted Period Start Adj.Pd.St. ADJ_PERIOD_START Not currently used NAdjusted Total Ops Adj.Ops ADJ_TOTAL_OPS Not currently used NAge Age AGE The number of years for which the flight has been

operatingY

Aircraft A/c AIRCRAFT_TYPE The aircraft for the flight YAircraft Chapter Ac Chapt. AIRCRAFT_CHAPTER The chapter number of the aircraft for the flight NAircraft ICAO Code Ac ICAO AIRCRAFT_ICAO The ICAO code of the aircraft for the flight YAircraft Parent Ac Parent AIRCRAFT_PARENT The parent airacraft of the aircraft for the flight NAircraft Stand Requirements Ac Stands AIRCRAFT_STANDS The stand requirements for the aircraft for the flight NAircraft User1 Ac User1 AIRCRAFT_USER1 The first user field value for the aircraft for the flight NAircraft User2 Ac User2 AIRCRAFT_USER2 The second user field value for the aircraft for the

flightN

Aircraft User3 Ac User3 AIRCRAFT_USER3 The third user field value for the aircraft for the flight NAircraft Weight Ac Wt. AIRCRAFT_WEIGHT The weight of the aircraft for the flight NAircraft Wide/Narrow Ac W/N AIRCRAFT_WIDTH The wide/narrow flag value for the aircraft for the

flightN

Airline CIE AIRLINE The airline for the flight record YAirline Alliance CIE All'nc AIRLINE_ALLIANCE The alliance for the airline NAirline Alternative Code CIE Alt.Cd AIRLINE_ALT_CODE The alternative code for the airline NAirline Country CIE Cntry AIRLINE_COUNTRY The country for the airline NAirline Default Terminal CIE <Term> AIRLINE_DEF_TERM The default terminal for the airline NAirline Responsible Rsp AIRLINE_RESPBL The coordinator responsible for the airline NAirline SSIM Code CIE SSIM AIRLINE_SSIM The code used on SSIM messages for the airline NAirline User1 CIE User1 AIRLINE_USER1 The first user field for the airline NAirline User2 CIE User2 AIRLINE_USER2 The second user field for the airline NAirline User3 CIE User3 AIRLINE_USER3 The third user field for the airline NAirport Apt AIRPORT The coordinated airport NAmend User Amd by AMEND_USER The name of the user that last amended the flight

recordN

Amended Amended DATE_LAST_MOD The date on which the flight record was last amended NArr. Prev/Next Arr P/N ARR_PN_STN The previous/next airport code for arrival flights (this

field is blank for departure flights)N

ArrDep A/D ARRDEP Arrival or Departure YCall Sign Call Sign CALL_SIGN The call sign for the flight Y

COHOR 17/01/06 15:56

of 47



Claimed Historic? HS? CLAIMED_HS Not currently used NClient Reference Client Ref CLIENT_REF The airlines reference for this flight record YCode Share Cd.Share CODE_SHARE_ID Not currently used NCode Share Memo CS.Memo CODE_SHARE_MEMO Not currently used NCode Share Type C/s Tp CODE_SHARE_TYPE N=no code share, C=code share, F=franchise YCreate User Cre. CREATE_USER The user that first created the flight record NCreated Created DATE_CREATED The date on which the flight record was first created NDataset Dataset DATA_SET The Data Set for the flight record NDep. Prev/Next Dep P/N DEP_PN_STN The previous/next airport code for departure flights

(this field is blank for arrival flights)N

Destination Dst DEP_OD_STN The origin/destination airport code for departureflights (this field is blank for arrival flights)

N

Flexibility End Flex.End FLEXIBILITY_END The end time of the airlines requested flexibility timerange

Y

Flexibility Flag Flex? FLEXIBILITY_FLAG Whether the airline has specified a flexibility timerange

N

Flexibility Start Flex.St. FLEXIBILITY_START The start time of the airlines requested flexibility timerange

Y

Flight Flight FLT_NO The flight number of the flight YFlight number Flt FLIGHT_COMPOSITE The combined airline code, flight number and suffix

(e.g. AF123X)N

Frequency Freq. FREQUENCY The frequency of the flight YHeld By User Held by USER_HELD_NAME If the flight is currently locked by another user - this

field contains the users nameN

Hist. Airline HS CIE HS_AIRLINE The airline code for the flight record as it appears onthe HISTORIC dataset

N *

Hist. Suffix HS Sfx HS_SUFFIX The suffix for the flight record as it appears on theHISTORIC dataset

N *

Hist.Flight HS Flt HS_FLT_NO The flight number for the flight record as it appears onthe HISTORIC dataset

N *

Historic Flight number Hist FltHS_FLIGHT_COMPOSITE

The combined airline code, flight number and suffix(e.g. AF123X) for the flight record as it appears onthe HISTORIC dataset

N *

Historic Reference HS Ref HS_REFERENCE The historic reference for the flight (linking it to theassociated record on the HISTORIC dataset)

N *

HS Time HS Tm HS_TIME The time for the flight record as it appears on theHISTORIC dataset

N *

COHOR 17/01/06 15:56

of 47



Maximum TR Time Max TR MAX_TR_TIME The maximum turnround time accepted for this flight YMerge Key Mge Key MERGE_KEY Used Internally NMessage 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 YMsg Block No Msg BlK MSG_BLOCK_NO The block number within the message that last

modified the flightY *

N/A N/A FEM_REQ_ID Used Internally NNew Entrant NE NEW_ENTRANT Whether the flight can claim new-entrant status YNoise Level Noise NOISE_LEVEL The noise rating for the flight YNon SSIM relevant SSIM N/Rel NON_SSIM_RELEVANT Used Internally NNorm Pd End Nm P/End NORM_PERIOD_END In reporting, this field is used to adjust the end date

on the flight record to fit the parameters of the reportN

Norm Pd Start Nm P/St NORM_PERIOD_START In reporting, this field is used to adjust the start dateon the flight record to fit the parameters of the report

N

Norm Total Ops Norm Ops. NORM_TOTAL_OPS In reporting, this field is used to adjust the totaloperations for the flight record to fit the parameters ofthe report

N

Norm. Frequency Nm Freq NORM_FREQUENCY In reporting, this field is used to adjust the frequencyfor the flight record to fit the parameters of the report

N

Num DoW #DoW NUMBER_DOW The number of days of the week operated by theflight.

N

Num Weeks #Wks NUMBER_WEEKS The number of weeks operated by the flight. NOffer Expires Off Exp OFFER_EXPIRES For offer records, the date that the offer will expire YOffer Identification Off Id OFFER_ID For offer records, the unique id for the offer Noffer Ind Off? OFFER_IND Whether an unaccepted offer exists for the flight NOp Airline Op CIE OPERATING_AIRLINE The operating airline (i.e. the code for the airline that

will actually operate the slot rather than the airlinethat owns the slot)

Y

Op Hist Corresp OH Corr OP_HIST_CORRESP Whether the flight has an associated record on theHISTORIC dataset

N *

Op_CIE Alliance OpC All'nc OP_CIE_ALLIANCE The alliance for the airline operating the flight NOp_CIE Alternative Code OpC Alt.Cd OP_CIE_ALT_CODE The alternative code for the airline operating the flight NOp_CIE Country OpC Cntry OP_CIE_COUNTRY The country for the airline operating the flight NOp_CIE Default Terminal OpC <Term> OP_CIE_DEF_TERM The default terminal for the airline operating the flight NOp_CIE Responsible OpC Respbl OP_CIE_RESPBL The coordinator responsible for the airline operating

the flightN

COHOR 17/01/06 15:56

of 47



Op_CIE SSIM Code OpC SSIM OP_CIE_SSIM The code used on SSIM messages for the airlineoperating the flight

N

Op_CIE User1 OpC User1 OP_CIE_USER1 The first user field for the airline operating the flight NOp_CIE User2 OpC User2 OP_CIE_USER2 The second user field for the airline operating the

flightN

Op_CIE User3 OpC User3 OP_CIE_USER3 The third user field for the airline operating the flight NOp_Status St OP_STATUS The operating status for the flight (e.g. OP, NO, OF,

PG, HS, RV)Y

Operations Ops TOTAL_OPS The number of operations represented by the flightrecord

N

Orig/Dest O/D ORIG_DEST_STN The Origin/Destination airport YOrig/Dest Country O/D Cntry ORIG_DEST_COUNTRY The country of the origin/destination airport NOrig/Dest Default Terminal O/D <Term> ORIG_DEST_DEF_TERM The default terminal for the origin/destination airport NOrig/Dest Dom/Int/Schen O/D D/I/S ORIG_DEST_DIS Whether the origin/destination airport is

domestic/international or schengenN

Orig/Dest ICAO Code O/D ICAO ORIG_DEST_ICAO The ICAO code of the origin/destination airport YOrig/Dest Latitude O/D Lat. ORIG_DEST_LATITUDE The Latitude of the origin/destination airport NOrig/Dest Long/Short Haul O/D Haul ORIG_DEST_HAUL Whether the origin/destination airport is considered

long or short haulN

Orig/Dest Longitude O/D Long.ORIG_DEST_LONGITUDE

The longitude of the origin/destination airport N

Orig/Dest User1 O/D User1 ORIG_DEST_USER1 The first user field for the origin/destination airport NOrig/Dest User2 O/D User2 ORIG_DEST_USER2 The second user field for the origin/destination airport NOrig/Dest User3 O/D User3 ORIG_DEST_USER3 The third user field for the origin/destination airport NOrigin Org ARR_OD_STN The origin/destination airport code for arrival flights

(this field is blank for departure flights)N

Original Record Id Orig.Id ORIG_RECORD_ID Internal Use NOvernight O/Nt OVERNIGHT_IND The overnight indicator for turnround flights YPd. End Pd End PERIOD_END The start date for the flights operating period YPd. Start Pd St. PERIOD_START The end date for the flights operating period YPrev/Next (via) Via PREV_NEXT_STN The Previous/Next airport YPrev/Next Country P/N Cntry PREV_NEXT_COUNTRY The country code for the previous/next airport NPrev/Next Default Terminal P/N <Term>

PREV_NEXT_DEF_TERM

The default terminal for the previous/next airport N

COHOR 17/01/06 15:56

of 47

Prev/Next Dom/Int/Schen P/N D/I/S PREV_NEXT_DIS Whether the previous/next airport isdomestic/international or schengen

N

Prev/Next ICAO Code P/N ICAO PREV_NEXT_ICAO The ICAO code of the previous/next airport YLong Description Short Desc Item Code Description Add Change

ScreenOPERATEDDataset Only

Prev/Next Latitude P/N Lat. PREV_NEXT_LATITUDE The Latitude of the previous/next airport NPrev/Next Long/Short Haul P/N Haul PREV_NEXT_HAUL Whether the previous/next airport is considered long

or short haulN

Prev/Next Longitude P/N Long.PREV_NEXT_LONGITUDE

The longitude of the previous/next airport N

Prev/Next User1 P/N User1 PREV_NEXT_USER1 The first user field for the previous/next airport NPrev/Next User2 P/N User2 PREV_NEXT_USER2 The second user field for the previous/next airport NPrev/Next User3 PN User3 PREV_NEXT_USER3 The third user field for the previous/next airport NRecord Id RecId RECORD_ID Internal Use NRegistration Reg'n REGISTRATION The registration number for the flight YRel_Field Rel_Fld REL_FIELD Internal Use NRel_Table Rel_Tab REL_TABLE Internal Use NRequested Hour Req.Hr REQUESTED_HOUR The requested time for the flight rounded down to the

nearest hour.N

Requested Slot Req.Slot REQUESTED_SLOT The requested time for the flight rounded down to thenearest slot.

N

Requested Time ReqT REQUESTED_TIME The requested time for the flight YRestr'n Code Rstrct Cd RESTRICTION_CODE The restriction code associated with the flight YScheduled Hour Sch.Hr SCHEDULED_HOUR The scheduled time for the flight rounded down to the

nearest hour.N

Scheduled Slot Sch.Slot SCHEDULED_SLOT The scheduled time for the flight rounded down to thenearest slot.

N

Scheduled Time Schd SCHEDULED_TIME The scheduled time for the flight YSeason Ssn SEASON The season code NSeat Count Sts SEAT_COUNT The number of seats for the flight YService Svc SERVICE_TYPE The service type YSlot Return Date Reference SRD Ref SRD_REFERENCE Internal Use NSuffix Sfx SUFFIX The suffix for the flight record YTerminal Term TERMINAL_ID The terminal that the flight will use NTR Airline TR CIE TR_AIRLINE The airline code for the associated turnround flight

record.Y

TR AOG (mins) TR AOG TR_AOG_MINS The number of minutes that a turnround flight is onthe ground

N

COHOR 17/01/06 15:56

of 47

TR Flight TR Flt TR_FLT_NO The flight number for the associated turnround flightrecord.

Y

TR Suffix TR Sfx TR_SUFFIX The suffix for the associated turnround flight record. YLong Description Short Desc Item Code Description Add Change

ScreenOPERATEDDataset Only

TR Time TR Tm TR_TIME The scheduled time for the associated turnroundflight record.

Y

Turnround Flight TR FlightTR_FLIGHT_COMPOSITE

The combined airline code, flight number and suffix(e.g. AF123X) for the turnround flight record

N

Turnround Flight Id Tr Id TR_ID Internal Use NUser 1 User 1 USER1 The first user field for the flight record YUser 2 User 2 USER2 The second user field for the flight record YUser 3 User 3 USER3 The third user field for the flight record YUser 4 User 4 USER4 The fourth user field for the flight record YUser 5 User 5 USER5 The fifth user field for the flight record YUser 6 User 6 USER6 The sixth user field for the flight record YUser 7 User 7 USER7 The seventh user field for the flight record YUser 8 User 8 USER8 The eigth user field for the flight record YUser 9 User 9 USER9 The ninth user field for the flight record YUser Held Held? USER_HELD_FLAG Whether this flight record is currently being modified

by another userN

Wait List Date WL.Date WAIT_LIST_DATE The date that the flight record was first placed on thewait list.

N

Waiting List Wt.Lst WAITING_LIST Whether the flight is on the wait list YWkly Freq WF WEEKLY_FREQ The weekly frequency for the flight YWL Reason Rsn WL_REASON The Wait List reason code for the flight YYear Round YrRnd YEAR_ROUND Whether the flight operates the whole year at the

same time.Y

maintenance overview - cohor · the three-letter iata code for the airport.! ... reply to an scr...

Documents