DEI - Values used in the SSM/ASM messages (this is not a sub-message):
Number | Description | Example |
---|---|---|
DEI 1 | Joint Operation Airline Designators | 1/KL/LH |
DEI 2 | Operating Airline Disclosure Code Share | 2/DL |
DEI 3 | Aircraft Owner | 3/DY |
DEI 4 | Cockpit Crew Employer | 4/WF |
DEI 5 | Cabin Crew Employer | 5/LX |
DEI 6 | Onward Flight | 6/SK345/15 |
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:
The format of an SSM NEW message is as follows: Standard Message Identifier |
Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):
S-leg dom | M-leg dom past midnight | M-leg dom to non-s past midnight | M-leg non-s to sch to dom | Several flights in one message | Different flights and types | M-leg with return to same airport |
---|---|---|---|---|---|---|
SSM | SSM | SSM | SSM | SSM | SSM | SSM |
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).
The format of an SSM CNL message is as follows: Standard Message Identifier |
Examples, one flight or several flights at the same time:
One Flight in period specified | Several flights in one message | Flight less then 24h in future | Including ASM created flight |
---|---|---|---|
SSM | SSM | SSM SI FLIGHT IS SET TO CNL NOT DELETED | SSM |
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.
The format of an SSM RPL message is as follows: Standard Message Identifier |
Examples, one flight or several flights at the same time:
Description | S-leg dom | M-leg dom past midnight | M-leg dom to non-s past midnight | M-leg non-s to sch to dom inkluding XASM |
---|---|---|---|---|
Examples | SSM | SSM | SSM | SSM |
Comment | If changing airport on date of operation, old legs will be marked as cancelled | XASM must be included if ASM message has created flights in the same period. |
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.
The format of an SSM TIM message is as follows: Standard Message Identifier |
Examples:
Description | S-leg dom |
---|---|
Examples | SSM |
Comment |
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.
The format of an SSM FLT message is as follows: Standard Message Identifier |
Examples:
Description | Affects day 6-7 bi-weekly |
---|---|
Examples | SSM |
Comment | Changes from TEF9999 to TEF8999 |
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.
The format of an SSM SKD message is as follows: Standard Message Identifier |
Examples:
Description | S-leg Domestic |
---|---|
Examples | SSM |
Comment | All flights in period specified are deleted in the Avinor systems. |
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.
The format of an SSM EQT message is as follows: Standard Message Identifier |
Examples:
Description | S-leg Schengen |
---|---|
Examples | SSM |
Comment |
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
The format of an SSM ADM message is as follows: Standard Message Identifier |
Examples:
Description | S-leg Schengen |
---|---|
Examples | SSM |
Comment |
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:
The format of an ASM NEW message is as follows: Standard Message Identifier |
Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):
S-leg dom | M-leg dom past midnight | M-leg dom to non-s past midnight | M-leg non-s to sch to dom | Several flights in one message | Different flights and types | M-leg with return to same airport |
---|---|---|---|---|---|---|
ASM | ASM | ASM | ASM | ASM | ASM | ASM |
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:
The format of an ASM CNL message is as follows: Standard Message Identifier |
Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):
S-leg dom | Several flights in one message | Different flights and types |
---|---|---|
ASM | SSM | SSM |