Difference between revisions of "Alarms Designations"
Jump to navigation
Jump to search
(Created page with "{|class="wikitable" !Alarm message !Designation |- |<span style="color:rgb(127 4 38); font-weight:bold;">! No cabin assigned</span> |Configuration is not assigned to the fligh...") |
|||
Line 5: | Line 5: | ||
|<span style="color:rgb(127 4 38); font-weight:bold;">! No cabin assigned</span> | |<span style="color:rgb(127 4 38); font-weight:bold;">! No cabin assigned</span> | ||
|Configuration is not assigned to the flight | |Configuration is not assigned to the flight | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Inbound telegrams</span> | ||
+ | |There is a incorrect input telegram on the flight (the Telegram module) | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Outbound telegrams</span> | ||
+ | |When forming output telegrams, one of the telegrams contains incomplete data format (the Telegram module) | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">!Configurations differ</span> | ||
+ | |Transit flight, along the entire flight route, there is a difference in the configurations. | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Special service</span> | ||
+ | |There are passengers on the flight who demand attention!!! (select remarks to display this alarm in the "Administration" module, the "Remark setting" table | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Payload exceeded</span> | ||
+ | |Payload is assigned to the flight, a number of checked-in passengers and baggage is exceeds it | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! No access to the ETS</span> | ||
+ | |Disruption has occurred, flight check-in changed to the ETL mode, interactive confirmation of ET is absent | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Manually entered APIS data</span> | ||
+ | |APIS data control mode is set on the flight, data on the passenger were entered manually and not using the scanner | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! APIS data differ from booking data</span> | ||
+ | |Data on documents/ visa of the passenger were changed at the check-in desk | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">!Boarding</span> | ||
+ | |There are passengers who have not checked boarding | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Number of crew members missing</span> | ||
+ | |Sending output telegrams requiring a number of crew members are adjusted on the flight | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Crew check-in</span> | ||
+ | |Sending data requiring data on the crew are adjusted on the flight | ||
+ | |- | ||
+ | |<span style="color:rgb(127 4 38); font-weight:bold;">! Not associated transfer baggage</span> | ||
+ | |There is an inbound transfer but not all transfer baggage managed to be associated with passenger/passengers | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Other sections:== | ==Other sections:== |
Revision as of 15:50, 22 August 2021
Alarm message | Designation |
---|---|
! No cabin assigned | Configuration is not assigned to the flight |
! Inbound telegrams | There is a incorrect input telegram on the flight (the Telegram module) |
! Outbound telegrams | When forming output telegrams, one of the telegrams contains incomplete data format (the Telegram module) |
!Configurations differ | Transit flight, along the entire flight route, there is a difference in the configurations. |
! Special service | There are passengers on the flight who demand attention!!! (select remarks to display this alarm in the "Administration" module, the "Remark setting" table |
! Payload exceeded | Payload is assigned to the flight, a number of checked-in passengers and baggage is exceeds it |
! No access to the ETS | Disruption has occurred, flight check-in changed to the ETL mode, interactive confirmation of ET is absent |
! Manually entered APIS data | APIS data control mode is set on the flight, data on the passenger were entered manually and not using the scanner |
! APIS data differ from booking data | Data on documents/ visa of the passenger were changed at the check-in desk |
!Boarding | There are passengers who have not checked boarding |
! Number of crew members missing | Sending output telegrams requiring a number of crew members are adjusted on the flight |
! Crew check-in | Sending data requiring data on the crew are adjusted on the flight |
! Not associated transfer baggage | There is an inbound transfer but not all transfer baggage managed to be associated with passenger/passengers |
Other sections:
- Boarding module
- Seasonal Schedule Management Module
- Check-in Preparation Module
- Check-in module
- Documentation module
- Statistics module
- History module
- EMDA Module
- Messages Module
- Access Module
- Baggage Payment Module
- Transportation Module
- Weight and Balance Module
- Web Check-in at a Cost Service
- Self Check-in Kiosk Software
- Administration module