Difference between revisions of "Publication of Shedule to External Systems"
| Line 33: | Line 33: | ||
|- | |- | ||
|Formation of a new flight schedule period | |Formation of a new flight schedule period | ||
| − | |NEW | + | |style="text-align: center;" NEW |
|— | |— | ||
|- | |- | ||
Revision as of 04:37, 21 July 2021
A schedule formed in the System may be published into external systems. In this case, a part of parameters reflecting commercial components of a flight schedule might be partially changed without any change in basic schedule.
Messages are published in the form of TTY SSIM4/5 format (SSM messages are formed in compliance with basic periods, ASM messages are formed in compliance with Ad-hoc periods). For more information about TTY format, see SSIM standard, Chapters 4-5.
Flight schedule publication can be carried out in automatic and manual (forced) modes.
Automatic flight schedule publication is carried out after saving any schedule changes if rules of publication are formed. The schedule publication parameters are managed by the following business rules:
Formed messages contain tags of the actions that correspond to performed operations on schedule updating.
In manual mode, it is possible to send a flight schedule for a specified period by SSIM 4/5 format message.
Message format and conditions are defined by conditions of the Flight publication business rules.
When a message about a schedule is sent, a recipient system forms and sends a NAC response message (if such function is available) which contains information about receiving of the sent messages and processing status.
NAC incoming messages are added to system queue.
If the message is not processed by the recipient system then the NAC message contains information about processing failure cause. In this case, intervention of an operator is supposed: to change the schedule in accordance with the message information or edit the sent message about the schedule and resend it.
The messages are formed with tags of the actions that correspond to processed operations of schedule correction.
Table “Messages about schedule change”
| Operation | SSM | ASM |
|---|---|---|
| Formation of a new flight schedule period | style="text-align: center;" NEW | — |
| Formation of a new Ad-hoc period | — | NEW |
| Modification of a flight schedule period without Ad-hoc period change | SKD + NEW | — |
| Modification of a flight schedule period with deleting Ad-hoc period | SKD XASM + NEW | — |
| Deleting Ad-hoc period | RPL XASM | — |
| Cancellation of a date with its further restoration | — | CNL |
| Restoration of a cancelled date | — | RIN |
| Cancellation of a flight schedule period without Ad-hoc period change | CNL | — |
| Cancellation of a flight schedule period including Ad-hoc periods | CNL XASM | — |
| Change of sales or physical configuration of an aircraft for basic period |
|
— |
| Change of sales or physical configuration of an aircraft for Ad-hoc period | — | CON |
| Change of an aircraft type for basic period |
|
— |
| Change of aircraft type for Ad-hoc period | — | EQT |
| Change of departure/ arrival time for basic period
without changing Ad-hoc periods |
|
— |
| Change of departure/ arrival time for basic period
with deleting Ad-hoc period |
|
— |
| Change of departure/ arrival time for Ad-hoc period | — | TIM |
| Flight delay | — | TIM |
| Change of data elements transmitted by DEI for basic
period not affecting Ad-hoc periods |
|
— |
| Change of data elements transmitted by DEI for
Ad-hoc period |
— | ADM |
| Change of flight status for basic period and Ad-hoc periods |
|
RPL |
| Change of a flight schedule for basic period
not including Ad-hoc periods |
|
— |
| Change of a flight schedule for Ad-hoc period | — | RPL |
| Cancellation of a part of a route for basic period
not including Ad-hoc periods |
|
— |
| Cancellation of a part of a route for basic period
including Ad-hoc periods |
|
|
| Cancellation of a part of a route for Ad-hoc period | — | CNL |