Leonsoftware Wiki

User Tools

Site Tools

You are here: start » mobile
mobile:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
mobile:start [2021/11/04 14:20]
rafal [Crew] 		mobile:start [2024/03/19 18:56]
rafal [Requests]
Line 24: Line 24:
  
 ===== My Schedule ===== ===== My Schedule =====
 +<box tutorial>[[videos:leon-buddy:mobile-crew-app-basics|Mobile Crew app: Basics]]</box>
  
-[{{ :mobile:new-app:my schedule view.png?200|'My Schedule' panel}}]+[{{ :mobile:new-app:updated_my_schedule_-bt.png?200|'My Schedule' panel}}]
  
 This section is designed to view flights, positionings and duties of the person logged in. This section is designed to view flights, positionings and duties of the person logged in.
  
 Flights and positionings that are not assigned or assigned to a different crew or scheduled Maintenance **will not show** in this view. Flights and positionings that are not assigned or assigned to a different crew or scheduled Maintenance **will not show** in this view.
 +
 +Next to the calendar date, accumulated **Block time** for this month is presented. 
  
 If you click on a particular flight in this panel, Leon shows a clock-icon - click it to view **Roster history** made on that day. You can also click the same icon on the menu bar and Leon will show roster changes (as on screenshot below). If you click on a particular flight in this panel, Leon shows a clock-icon - click it to view **Roster history** made on that day. You can also click the same icon on the menu bar and Leon will show roster changes (as on screenshot below).
Line 37: Line 40:
 In the filter, it is possible to switch between **IATA/ICAO** codes and **UTC/BT** times. All other functions, with little exceptions, are the same as in the 'Calendar' section. In the filter, it is possible to switch between **IATA/ICAO** codes and **UTC/BT** times. All other functions, with little exceptions, are the same as in the 'Calendar' section.
  
 +=== CREW MOBILE APP - Clock In / Clock Out feature ====
 +
 +With this feature, a crew member is able to register the time of start and end of the duty, to which he/she is assigned. 
 +
 +The data registered are: 
 +  *   Duty start time
 +  *   Duty start location
 +  *   Duty end time
 +  *   Duty end location
 +
 +To record the duty start/end time and location, in [[mobile:start|Leon mobile app]]: 
 +  - Go to My Schedule
 +  - Open a duty you are assigned to
 +  - Tap the "Clock in" or "Clock out" button
 +
 +<box>**To have the location recorded, the user should allow the Leon app to access geolocation data.**</box>
 +
 +The details recorded using this feature are available in [[leon:report-wizard|Report Wizard]], "Crew Roster" scope. The columns available are: 
 +  * Clock in localization
 +  * Clock in time [UTC]
 +  * Clock out localization
 +  * Clock out time [UTC]
 +
 +[{{:mobile:new-app:clock_in_empty.png?nolink&350|Duty details before clocking in}}][{{:mobile:new-app:clock_out_empty.png?nolink&350|Duty details after clocking in, before clocking out}}][{{:mobile:new-app:clock_in_out_details.png?nolink&350|Duty details with complete clock in/out data visible}}]
 +
 +It is also possible to **set up fixed Clock-in/clock-out locations**. More information in the [[leon:general-setup|General Settings]] section of Leon.
  
 ------------------- -------------------
Line 43: Line 72:
 'Weekly Rest' for this purpose is considered as 36h free of duties including two local nights in 168h period. Click the **filter** to enable showing weekly rest in the roster calendar. 'Weekly Rest' for this purpose is considered as 36h free of duties including two local nights in 168h period. Click the **filter** to enable showing weekly rest in the roster calendar.
  
-**'Weekly Rest'** in 'My Schedule' view indicates where the weekly rest actually takes place.+**'Weekly Rest'** in 'My Schedule' view indicates where the weekly rest actually takes place.  
 + 
 +**Caution:** The weekly rest has a slightly different role in Crew mobile application than in [[leon:crew-panel|CREW TIMELINE]]. In Crew Timeline it appears at the latest time when it should be applied, while on the Crew mobile application it applies always when conditions are met. That's why indicated weekly rest may not match in both applications.
  
 'Weekly rest' is marked with the light-blue colour and is applied only after a flight, positioning, Simulator or any other duty included by definition in the FTL calculations. 'Weekly rest' is marked with the light-blue colour and is applied only after a flight, positioning, Simulator or any other duty included by definition in the FTL calculations.
Line 204: Line 235:
  
 ------- -------
 +
 +===== Push Notifications =====
 +
 +[{{ :mobile:new-app:push:mobile_push_3.png?300|'My Schedule' with duty changes indicators}}]
 +
 +Any roster changes, including flight crew changes, are indicated in the 'My Calendar" view by red underline (screen on the right).
 +
 +Additionally, a crew member for whom the roster is changed will have the push notification displayed on the mobile device:
 +[{{ :mobile:new-app:push:mobile_push_4.png?300|Roster history with 'Acknowledge' button}}]
 +{{:mobile:new-app:push:mobile_push_1.1.png?nolink|}}
 +
 +Clicking either on the notification or on the roster changes history tile in 'My Calendar' will display the roster changes history in the Crew Mobile App (presented in the screenshot on the right), as well as the option to, **acknowledge** changes. 
 +
 +**Option to acknowledge roster changes** can be activated in the [[leon:mobile-notifications-tab-in-general-settings|Mobile Notifications]] by selecting the 'Enable crew roster changes acknowledgements in Crew app' checkbox.
 +
 +Once the duty is amended, it is also **indicated in the OPS section** tab 'CREW' in the 'ACKNOWLEDGEMENTS' subsection.
 +
 +The **'ACKNOWLEDGMENTS'** subsection indicates whether the crew member has familiarized himself/herself with the changes to flight duties.
 +
 +The 'ACKNOWLEDGEMENT' for each crew displays **3 statuses**:
 +
 +  * {{:leon:schedule-crew:acknowledgement:acknowledgement_red.png?nolink|Unordered List Item}} - notification not sent
 +  * {{:leon:schedule-crew:acknowledgement:acknowledgement_orange.png?nolink|}} - push notification received by crew but not familiarized with
 +  * {{:leon:schedule-crew:acknowledgement:acknowledgement_green.png?nolink|}} - familiarization confirmed
 +
 +
 +Additionally, the **duty acknowledgement** status is indicated by the colour of the lower bar in the CREW Timeline & [[leon:crew-calendar|CREW CALENDAR]] sections:
 +
 +  * {{:leon:crew-calendar:cc_-_ack_not_sent.png?nolink|}} - acknowledgement not sent to crew
 +  * {{:leon:crew-calendar:cc_-_awaiting_ack.png?nolink|}} - acknowledgement sent but not familiarized with
 +  * {{:leon:crew-calendar:cc_-_acknowledged.png?nolink|}} - acknowledgement familiarized with by the crew
 +
 +
 +
 +--------
 ===== Flight details ===== ===== Flight details =====
  
Line 237: Line 303:
  
 ---- ----
-<html><!--</html>+
 **Viewing OPS documents** **Viewing OPS documents**
  
Line 243: Line 309:
  
 {{:mobile:new-app:ops docs w appce.png?nolink|}} {{:mobile:new-app:ops docs w appce.png?nolink|}}
-<html>--></html>+ 
 +It is possible to print the documents for the flights ending within 24h before 'now'.
  
 **HIL** **HIL**
Line 254: Line 321:
 ==== Pax List ==== ==== Pax List ====
  
-[{{ :mobile:new-app:nowa pax list.jpg?150|Pax list in Leon mobile application}}]+[{{ :mobile:new-app:pax_-_mobile_tab_updated.png?150|Pax list in Leon mobile application}}]
  
  
 Tab PAX section displays the PAX number as well as the list of passengers added to a flight. If additional details were added to the passenger's profile, ie. preferences, they can be found by clicking on a passenger's name.  Tab PAX section displays the PAX number as well as the list of passengers added to a flight. If additional details were added to the passenger's profile, ie. preferences, they can be found by clicking on a passenger's name. 
  
-If the passport number is expired, it will be displayed in red. +If the passport number is expired, it will be displayed in red. Additionally, if the DoB of the PAX falls on the day of the flight, the date will be presented in bold and the gift icon will appear next to the DoB: 
 + 
 + 
 +{{:mobile:new-app:pax_-_dob_birthday.png?nolink|}}
  
  
-[{{:mobile:new-app:preferences.jpg?|Pax details}}]+PAX data is not available on past flights.
  
 ----- -----
Line 378: Line 448:
  
 ---- ----
 +==== MVT ====
 +[{{ :mobile:new-app:mvt_-_fw_view.png?150|'MVT' tab in Crew App}}]
  
 +**MVT** tab allows the pilots to insert the Flight Watch details.
 +
 +This tab contains all the fields that are available in the desktop version of the 'Flight Watch'.
 +
 +The **timeframe** details are split into the date and the time value.
 +
 +Clicking on the **date field** will open a calendar pop-up where the specific date can be selected, if other than suggested.
 +
 +Clicking on any of the **timeframe fields** (CTOT, ETD, BLOFF, etc) will open a pop-up identical to the one in the 'JL', where the time value can be inserted as well as one of the 3 options selected:
 +
 +  * **CANCEL** - cancelling the input and closing the pop-up
 +  * **CONFIRM** - saving the inserted value and closing the pop-up
 +  * **NEXT** - saving the inserted value and moving to the next FW field
 +
 +Flight Watch inserted and saved in the 'MVT' tab will automatically appear in the desktop version of Leon and vice-versa.
 +
 +---------------
 ==== Journey Log ==== ==== Journey Log ====
 [{{ :mobile:new-app:nowy JL.jpg?150|Journey Log data in Leon mobile application}}] [{{ :mobile:new-app:nowy JL.jpg?150|Journey Log data in Leon mobile application}}]
Line 386: Line 475:
 **Journey Log** tab shows flight schedule data on top of the screen. Below all there are all post-flight data inserted into Leon. The screen is divided into **2** parts: **Journey Log** tab shows flight schedule data on top of the screen. Below all there are all post-flight data inserted into Leon. The screen is divided into **2** parts:
  
-**Full JL mandatory fields**:  +Both, **Full JL mandatory fields** as well as the **Optional fields** can be selected in the [[leon:checklist-configuration|Checklist Configuration]] settings.
-  *Date  +
-  *ADEP & ADES codes  +
-  *BLOFF  +
-  *T/O  +
-  *LDG  +
-  *BLON  +
-  *MAX FL  +
-  *Block fuel  +
-  *Fuel remaining+
  
-**Optional fields** - all other details enabled in Leon section Settings, i.e.: uplift, pilot flying, delay code, PAX, cargo, etc...+**Confirmation of data correctness** checkbox can only be selected by the CPT who certifies that all above details are inserted correctly
  
 === Handover data === === Handover data ===
  
-It is important for the crew - once they have finished their duty - to inform crew assigned to the next leg, on the same aircraft, about remaining fuel on board and other details. For this purpose, we have added 2 new fields to the Journey Log panel (to be enabled in Settings > Flight Editing section).+It is important for the crew - once they have finished their duty - to inform the crew assigned to the next leg, on the same aircraft, about remaining fuel on board and other details. For this purpose, we have added 2 new fields to the Journey Log panel (to be enabled in Settings > Flight Editing section).
  
 +------------------
 ===== Fuel before uplift ===== ===== Fuel before uplift =====
  
Line 501: Line 582:
 ===== Requests ===== ===== Requests =====
  
-[{{ :mobile:new-app:adding requests1.jpg?100|Adding new request}}] +[{{ :mobile:new-app:crew_app_-_new_request_with_timeframes.png?100|Adding new request}}] 
-[{{ :mobile:new-app:List of requests.png?100|The list of requests}}]+[{{ :mobile:new-app:mobile_requests_-_statuses.png?100|The list of requests}}]
  
 In order to **request** a duty, select the menu "Requests" and use the icon {{:mobile:new-app:plus.jpg?30|}}  In order to **request** a duty, select the menu "Requests" and use the icon {{:mobile:new-app:plus.jpg?30|}} 
  
-Select a start date, end date, and the duty, ie.: day off/holiday/training. +Select a start date, end date, start time, end time and the duty, ie.: day off/holiday/training. 
  
 The list consists of all duties defined by the operator in Settings > Duties Setup. It is also possible to enter a note, ie.: with the reason for the request. This note will be viewed along with the request by the person planning duties.  The list consists of all duties defined by the operator in Settings > Duties Setup. It is also possible to enter a note, ie.: with the reason for the request. This note will be viewed along with the request by the person planning duties. 
Line 514: Line 595:
  
 Once the duty is requested, the person/dept responsible for planning duties will see the request in the roster - the requested duty will appear in brackets {{:leon:icons:duty-request.png|}} - if the request is approved, will be able to remove the request and assign the requested duty instead. In such case, the request will be removed from the list of requests in the Mobile App and replaced with the actual duty in the Mobile App calendar.  Once the duty is requested, the person/dept responsible for planning duties will see the request in the roster - the requested duty will appear in brackets {{:leon:icons:duty-request.png|}} - if the request is approved, will be able to remove the request and assign the requested duty instead. In such case, the request will be removed from the list of requests in the Mobile App and replaced with the actual duty in the Mobile App calendar. 
 +
 +Additionally, in this section, the crew can preview the **status** of the request.
 +  
 +It is possible to select which **duties can be requested** by selecting the 'Can be requested' checkbox in the [[leon:duties-setup|Duties Setup]] section.
 +
  
 ------------------- -------------------
mobile/start.txt · Last modified: 2024/04/19 08:40 by rafal

Page Tools

© 2021 LEON SOFTWARE ALL RIGHTS RESERVED | Leon Software