Page 36 - ITU-T Focus Group on Aviation Applications of Cloud Computing for Flight Data Monitoring - Use cases and requirements
P. 36
ITU-T Focus Group on Aviation Applications of Cloud Computing for Flight Data Monitoring
Use cases and requirements
Amount of data Nominal payload.
Transmission interval When required – based on triggered events and transmissions.
Transmission technologies VHF, satellite, WiFi, WGL, GSM. The protocols are typically ACARS, SatCom and IP based.
4.11 Flight crew techniques
Description Collect, analyse and store (tamper-proof collection of flight data) aircraft data to improve
flight crew processes.
Scenario Data from real flights can be used to develop and enhance flight procedures.
User groups • Flight safety;
• Flight operations and re-training;
• Maintenance/MRO.
Benefit Flying techniques optimization – better practices adoption, fuel savings, and maintenance savings.
Required data All fuel-related data, APU-related data, engines-related data – fuel consumption, OOOI times,
flight controls, slat/flap data, etc.
Data sources • QAR;
• DFDR.
Special considerations Data security, integrity and reliability.
Amount of data Nominal payload.
Transmission interval When required – based on triggered events and transmissions.
Transmission technologies VHF, satellite, WiFi, WGL, GSM. The protocols are typically ACARS, SatCom and IP based.
4.12 Approach statistics
Description Collect, analyse and store (tamper-proof collection of flight data) aircraft data for
approach statistics.
Scenario Creating and evaluating approach statistics is an essential activity in an airline to optimize the
operation costs. These are mainly defined by fuel costs, maintenance costs, and landing fees.
User groups • Flight operations;
• Maintenance/MRO;
• Finance.
Benefit • Data can be used to optimize approaches on every airport. Traffic management, fuel man-
agement, and traffic separation, etc.
Required data All fuel-related data, APU-related data, engines-related data – fuel consumption, OOOI times,
flight controls, slat/flap data, etc.
Data sources • QAR;
• DFDR.
Special considerations Data security, integrity and reliability.
Amount of data Nominal payload.
Transmission interval When required – based on triggered events and transmissions.
26
