DEI - Values used in the SSM/ASM messages (this is not a sub-message):

SSM - Standard Schedules Message

NEW - Insertion of New Flight Information

This sub-message inserts a new Flight Designator or adds new Periods of Operation and/or new Day(s) of Operation (at the Frequency Rate, if stated) for an existing Flight Designator. When used in conjunction with an SKD sub-message, the data contained in the NEW submessage supersedes the data, if any, for the period specified by its associated SKD sub-message.

Format of message:

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

CNL - Cancellation of Flight Information

This sub-message cancels (i.e. withdraws) the complete routing of a Flight Designator within the Period and on the Day(s) of Operation (and at the Frequency Rate, if stated).

Examples, one flight or several flights at the same time:

RPL - Replacement of Existing Flight Information

This sub-message replaces all existing information pertaining to a Flight Designator within the Period and on the Day(s) of Operation (at the Frequency Rate, if stated) by the new information. Other Periods and other Day(s) of Operation during the period stated (if existing) are not affected. The extension of periods and/or the addition of days of operation are not permitted using RPL sub-messages.

Examples, one flight or several flights at the same time:

TIM- Change of Time Information

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only the Timing information and/or the conditional data elements (if supplied) that can be transmitted in this type of message.

•Other Periods of Operation/Day(s) of Operation remain unchanged

•Data Elements previously transmitted and therefore already held in a recipients system and not included in the message remain unchanged.

Example:

FLT - Change of Flight Designator

This sub-message only changes the Flight Designator (and its associated data elements) and/or the Operational Suffix, for the Period and Day(s) of Operation (at the Frequency Rate, if stated).
Other data elements, Periods and Day(s) of Operation of the original Flight Designator and Operational Suffix are not affected.

Example:

SKD- Schedule Update

This sub-message cancels/deletes all existing information for the Flight Designator specified from the Schedule Validity Effective Date as specified to (and including) the Schedule Validity Discontinue Date, if stated. It indicates that revised schedule information, if any, will follow immediately in one or more associated sub-messages using Action Identifier NEW.

Example:

EQT- Change of Equipment Information

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only the Equipment information and/or the conditional data elements (if supplied) that can be transmitted in this type of message.

•Other Periods of Operation/Day(s) of Operation remain unchanged.

•Data Elements previously transmitted and therefore already held in a recipients system and not included in the message remain unchanged.

Example:

ADM- Change of Existing Information

Change of Existing Information Expressed by the Use of Data Element Identifier Only
For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only those data elements which are specified by the use of a Data Element Identifier.

•Other Periods of Operation/Day(s) of Operation remain unchanged

•When cancelling existing information the statement ‘NIL’ must be made

•If changes are leg related, replacement data need only be transmitted for legs where the data has changed. For example, in the case of Data Element Identifier 10, it is not necessary to transmit all legs that have Data Element Identifier 10 information, only those legs where DEI 10 needs changing

Example:

ASM - Ad-Hoc Schedules Message

NEW - Insertion of New Flight Information

This sub-message inserts a new Flight Designator or adds new Periods of Operation and/or new Day(s) of Operation (at the Frequency Rate, if stated) for an existing Flight Designator. When used in conjunction with an SKD sub-message, the data contained in the NEW submessage supersedes the data, if any, for the period specified by its associated SKD sub-message.

Format of message:

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

CNL - Cancellation of Flight Information

This sub-message cancels (i.e. declares as not operating), but retains as part of the basic schedule, one or more flights or parts of flight(s) defined by the Flight Identifier(s) (and Flight Leg Change Identifier, if applicable).
It is recommended that the facility to cancel part of a flight (using ASM/CNL with a Flight Leg Change Identifier) is confined to the operational phase of the flight only since a partial cancellation may lead to a Flight Designator duplication problem if the first leg or a middle leg of a flight is cancelled.
Partial cancellations would normally be communicated unambiguously using ASM/RPL.

Format of message:

Examples, single-leg (s-leg) and multi-leg (m-leg) flights:

RPL - Replacement of Flight Information

This sub-message replaces all information pertaining to an existing flight defined by a Flight Identifier by the new information.
If only specific information has to be replaced, the following Action Identifiers can be used instead of the complete RPL message.

Format of message:

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

RRT - Change of Routing

This sub-message changes only routing information (and its associated data elements) of a flight defined by a Flight Identifier.
The new routing must contain at least one Station from the previous routing. Stations common to both the previous and the new routings must appear in the same sequence.
The new routing, including timings, must be stated for all uncompleted legs of the flight. In order to avoid ambiguity regarding operational flights or flights scheduled to be in the operational phase, the Flight Leg(s) Change Identifier must be used to identify the flight leg(s) to be replaced by the schedule stated in the RRT message. If any of the above rules cannot be met then RPL must be used. For planning purposes, it is recommended that RPL be used.

Format of message:

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

TIM - Change of Time Information

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only the Timing information and/or the conditional data elements (if supplied) that can be transmitted in this type of message.

•Other Periods of Operation/Day(s) of Operation remain unchanged.

•Data Elements previously transmitted and therefore already held in a recipients system and not included in the message remain unchanged.

Format of message:

Examples:

RIN - Reinstate Flight

This sub-message reinstates (i.e. declares as now operating again in the form and with the data in existence prior to the issuance of the last appropriate ASM/CNL messages) one or more flights or parts of the routing defined by Flight Identifier(s) and previously cancelled by an ASM/CNL sub-message. Only flights cancelled within 12 months of operating can be reinstated.
Any subsequent changes to the flight (e.g. routing, times, equipment) must be handled by an appropriate sub-message.

Format of message:

Example:

ADM - Change of Existing Information

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only those data elements which are specified by the use of a Data Element Identifier.

•Other Periods of Operation/Day(s) of Operation remain unchanged

•When cancelling existing information the statement ‘NIL’ must be made

•If changes are leg related, replacement data need only be transmitted for legs where the data has changed. For example, in the case of Data Element Identifier 10, it is not necessary to transmit all legs that have Data Element Identifier 10 information, only those legs where DEI 10 needs changing

Note: When using multiple Action Identifiers, all formats for the combinations and, therefore, processing rules, are determined by the primary Action Identifier. Qualifying as secondary Action Identifiers are those that form a subset of the primary Action Identifier. Combinations with conflicting formats are not permitted, e.g. TIM-EQT. The secondary Action Identifier is intended for information purposes only i.e. human reading and understanding of changes.Consequently, the following combinations are permitted:

Primary     Secondary

RPL            ADM/CON/EQT/RRT/TIM
CON          ADM
EQT           ADM/CON
RRT           ADM/CON/EQT/TIM
TIM           ADM

Format of message:

Example:

FLT - Change Flight Designator

This sub-message only changes the Flight Designator (and its associated data elements), and/or the Operational Suffix, for the Flight Identifier Date (and part of the routing, if stated). Other data elements, dates, and parts of the routing of the original Flight Designator and Operational Suffix are not affected.

Format of message:

Example:

• ASM CON - Change of Aircraft Configuration/Version
• ASM EQT - Change of Equipment Information
• ASM FLT - Change of Flight Designator