The following outlines the process the airline would go through to capture aircraft flight log details via the merlot.pda.
- The merlot.aero back office database is populated with the airline's schedule via SSIM file. This is updated at a suitable time on a daily basis for all flights due to be flown in the next 24 hours. The merlot.aero database is also populated with the technical crew applicable for each flight for the next 24 hours.
- merlot.pda's are synchronised with the merlot.aero back office database at a suitable time and location. This could occur via standard communications protocols or hard wire link (depending on the airlines specific deployment).
- merlot.pda's are allocated on a per tail basis. These are collected by individual flight crews who operate the first flight out in the morning. Other arrangements are required for aircraft that remain out overnight.
- The specific airline crew member responsible for the merlot.pda then logs into the application via the screen below. The user selects the tail (pre-populated) and the relevant password.
This walkthrough illustrates how the merlot.aero FlightLog mobile application captures details for update to the back-office via standard communication methodologies.
On opening we are presented with the FlightLog List.
Figure 1. The merlot.aero FlightLog List
Search for Flights using the Find Flights screen.
Figure 2. The merlot.aero FlightLog Find Flights Screen.
The following four screens show the FlightLog Detail.
Figure 3. The merlot.aero FlightLog Detail - Cabin Screen.
Figure 4. The merlot.aero FlightLog Detail - Flight Information Screen.
Figure 5. The merlot.aero FlightLog Detail - Fuel Information Screen.
Figure 6. The merlot.aero FlightLog Detail - Tech Information Screen.
Figure 7. The merlot.aero Flight Log Pax/Cargo screen.
Figure 8. The merlot.aero FlightLog Summary screen.