User Tools

Site Tools


leon:flight-watch

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
leon:flight-watch [2016/05/27 09:43]
bartek [Take off/Landing reports]
— (current)
Line 1: Line 1:
-====== Flight Watch ====== 
  
-Flight watch allows you to monitor current status of active flights. By moving the mouse over the column 'FW' you can track flight details such as: BLOFF, T/O, ETA etc...  
- 
-[{{ :leon:flight-flight-watch:flight watch.png?300|Flight Watch window - possibility of adding flight times and sending takeoff/landing reports}}] 
- 
-Once you have added BLOFF you can go to [[leon:timeline|Timeline]] to see the realization of the flight strip. 
- 
-You can enter all required flight movements manually or you can have them downloaded automatically into 'Flight watch' by customizing the copy of movement email from @@SITA@@, @@SATCOM@@, @@ARINC@@, and @@EUROCONTROL@@ to be re-directed to [[mvt@leon.aero]]. This way flight movements are being also sent out automatically to clients/brokers. 
- 
-Once you have entered data into 'Flight Watch', in the 'Flights list' screen - column 'FW' appropriate letters will appear: 
- 
-  * **A** - airborne 
-  * **S** - slot 
-  * **D** - delay when delay code entered 
-  * **d** - delay when ETD entered 
-  * **+** - trip completed 
- 
-<box> **You can enter multiple delay codes in the 'Delay' field. The format of delay codes is: AA/MM BB/MM CC/MM .... where AA, BB, CC etc. are delay codes and MM is the delay in minutes.**</box> 
- 
-Entering data into some of fields will trigger sending of [[leon:notifications|notifications]] if they have been set up. 
- 
-It is also possible to generate 'Take off' and 'Landing Reports' that can be sent to selected email addresses upon enetering appropriate data in the Flight Watch. The reports can be sent out via two different methods (see below).  
- 
-=====Take off/Landing reports ===== 
- 
-[{{ :leon:flight-flight-watch:MVT emails.png?300|Sending aircraft movement emails - method 1}}] 
- 
-'Flight Watch' details can be used for sending out **aircraft movement messages** called '__Take off report__' and '__Landing report__' to clients, brokers or persons concerned. There are two methods of generating and sending such reports. 
- 
-  * **Method 1**: 
- 
-Go to Quotations section of [[leon:operator-settings|Operator Settings]] and tick 'Enable' box so that this option can be activated. In the space 'Email From' add email address from which messages should be sent. You can also add an  'Bcc' email address if you want to receive a copy of the message. 
- 
-In a tab **Trip Info** you can add an email address where the MVT email should be sent - that email address appears in a tab Quotation > General of Planned Flights flight edition screen. 
- 
-Another step requires adding details to the 'Flight Watch' movement: T/O (Take Off) and/or ETA (Estimated Time of Arrival). 
-Once you have clicked 'Update' in 'Flight Watch' screen, details will appear in the "@@Take Off Report@@" sent to a client/broker". 
- 
-**Takeoff Report** FLIGHT NO: MAN 
- 
-Departure Airport: UUWW - VNUKOVO 
-Destination Airport: EPWA - FREDERIC CHOPIN 
-ETA: 24-Apr-2013 1300 UTC / 24-Apr-2013 1500 LCL 
- 
-After the aircraft has landed, you can add LDG (Landing) time to 'Flight Watch' - new movement message will be sent titled: "@@Landing Report@@": 
- 
-**Landing Report** FLIGHT NO: MAN 
- 
-Landing time: 24-Apr-2013 1312 UTC / 24-Apr-2013 1512 LCL 
-Departure Airport: UUWW - VNUKOVO 
-Destination Airport: EPWA - FREDERIC CHOPIN 
- 
-In case of a situation where two sectors are on the same day but are two separate quotations that come from  __different__ clients/brokers, Leon will send 'Takeoff Report' to both of them. Let's assume that client **John Smith** has bought a flight WAW-VKO and client **Ian Davis** has bought a flight VKO-WAW – we have one trip but two different clients/brokers. In this case John Smith will receive 'Takeoff Report' as usual, however, Ian Davis will receive that report without 'Departure Airport' details as to him the most important  information is T/O and ETA: 
- 
-**Takeoff Report** FLIGHT NO: MAN 
- 
-Takeoff time: 24-Apr-2013 1110 UTC / 24-Apr-2013 1510 LCL 
-Destination Airport: EPWA - FREDERIC CHOPIN 
-ETA: 24-Apr-2013 1300 UTC / 24-Apr-2013 1500 LCL 
- 
-Similar situation is with 'Landing Report' -  client John SMith will get usual message, however, client Ian Davis will receive only information about the landing time at VKO, as this information concerns his flight VKO-WAW: 
- 
-**Landing Report** FLIGHT NO: MAN 
- 
-Landing time: 24-Apr-2013 1312 UTC / 24-Apr-2013 1512 LCL 
-Destination Airport: EPWA - FREDERIC CHOPIN 
- 
-<box> Reports are **not** being sent out for **empty legs**. </box> 
- 
----- 
-  * **Method 2**: 
- 
-[{{ :leon:flight-flight-watch:MVT report - method 2.png?300|Aircraft movement report - method 2}}] 
- 
-Go to [[leon:fleet|Fleet]] section and select aircraft to create a default message that will be included in the reports. Select **MVT Emails** tab and tick '__Enable sending MVT e-mail messages__'. This opens a form that needs to be filled in with the appropriate data. Mandatory fields are marked by red asterix. It is possible to enter several email addresses (separated by comma) to which the reports should be sent. In the content field of the reports use '**Patterns**' available below to get the desired data filled in automatically by the system and to create the entire message.  
- 
-For example, type in: "Takeoff report: Flight no. [FLIGHT_NO], Departure on  [DAY] [MONTH] [YEAR], Acft Reg.  [REGISTRATION], ADEP: [APT_DEP], ADES: [APT_DES], Block off time: **[BLOFF], [BLOFF_L]**, Take off time: **[TAKE_OFF], [TAKE_OFF_L]**, Pax no. [PAX]". All info in the square brackets [ ] will be automatically inserted in the report by the application. As you can see in the screnshot below, you can include both LT and UTC.  Click 'Show sample message' to preview the email that will be used to send reports (see below). 
- 
-{{:leon:flight-flight-watch:MVT sample.png?nolink|}} 
- 
-In the field **CC** you can add manually email address (one or more, separated by comma) where a **copy of MVT message** should be sent out. You can also add a **specific CC email address for a particular airport** in 'Planned Flights' screen, by clicking on the white envelope:  {{:leon:icons:koperta.png?nolink&20|}} 
-By default, there is always a **handling agent's email address** added to CC emails, selected previously in **Legs Info** > **Handling**.  
- 
-Once you complete the entire message do not forget to click 'Update' at the bottom of the page to save the default message. 
- 
-The same set up needs to be done for **each aircraft** requiring reports to be sent. 
- 
-When the set up is completed the reports are ready to be generated and sent off to appropriate persons specified earlier. Once the **Flight Watch** data is entered you can select 'Send Takeoff Report' and/or 'Landing Report' and automatically generated message will be sent out. If you do not want the message to be sent - unselect the appropriate fields. 
- 
-You will notice, that in the field 'CC' all email addresses will show up: handling agent's email address (added by default) plus those added manually either in 'Planned Flights' or 'Fleet edit > MVT Emails' sections (see below). 
- 
-{{:leon:flight-flight-watch:emails and cc emails.png?nolink&600|}} 
- 
-===== Importing movement messages ===== 
- 
-**Movement messages** can be imported to Leon if they are being sent to email address [[mvt@leon.aero]] and if they are in one of the below formats: 
- 
-  * SITA format message 
-  * SATCOM format message 
- 
- 
-==== SITA format ==== 
- 
-  * **Departure message** 
- 
-{{:leon:flight-flight-watch:sita dep msg.png?nolink|}} 
- 
- 
- 
-  * **Arrival message** 
- 
-{{:leon:flight-flight-watch:sita arr msg.png?nolink|}} 
- 
-You can also add delay code/codes to the MVT email and they will appear in the **Flight Watch**. Delay codes need to be input in a proper format: 
- 
-**Code/Time** **Code/Time** (a space between the 1st and the 2nd code is necessary) 
- 
-{{:leon:flight-flight-watch:MVT delay codes.png?nolink|}} 
-==== SATCOM format ==== 
- 
-__Takeoff Report__ and __Landing Report__ messages imported to Leon need to be in **specific formats**. Once such messages are received they will be automatically added to '**Flight Watch**' in Leon (**BLOFF when Takeoff Report sent and BLON when Landing Report sent**). See the example of the flight below. 
- 
-<html> 
-<span style="color:red;font-size:150%;">Takeoff Report format</span> 
-</html> 
- 
-**subject**:  
- 
-Takeoff Report for AC-REG 
- 
-**message**: 
- 
-Takeoff Report 
- 
-Off Time: 11-Jun-2013 0700 UTC / 11-Jun-2013 0900 LCL 
- 
-Departure Airport: LIML - LINATE 
- 
-Destination Airport: LIRA - CIAMPINO 
- 
-ETA 11-Jun-2013 0800 UTC / 11-Jun-2013 1000 LCL 
- 
-<html> 
-<span style="color:red;font-size:150%;">Landing Report format</span> 
-</html> 
- 
-**subject**:  
- 
-Landing Report for AC-REG 
- 
-**message**:  
- 
-Landing Report 
- 
-On Time: 11-Jun-2013 1000 UTC / 11-Jun-2013 1200 LCL 
- 
-Departure Airport: LIML - LINATE 
- 
-Destination Airport: LIRA - CIAMPINO 
- 
-==== ACAR format ==== 
- 
-**ACAR** movement emails can be sent out in the same way as SATCOM or SITA - to the email address mvt@leon.aero and Leon will update **Flight Watch** with details input in the mvt email. 
- 
-Below you can find appropriate formats which should be used. 
- 
-  * **OFF REPORT extended version** 
- 
-Subject: A-BCDE OFFRP (where A-BCDE is acft reg number) 
- 
-To: mvt@leon.aero 
- 
-**Content** 
- 
-10-JUN-2015 15:00:00 
- 
-OFF EVENT REPORT 
- 
-ORIGIN: WAW 
- 
-DESTINATION: AMS 
- 
-OUT TIME: 1456 
- 
-OFF TIME: 1500 
- 
-FUEL ON BOARD: 0430 
- 
-ETA: 1554 
- 
-  * **OFF REPORT simplified version** 
- 
-Subject: A-BCDE OFFRP (where A-BCDE is acft reg number) 
- 
-To: mvt@leon.aero 
- 
-**Content** 
- 
-A-BCDE OFF REPORT 
- 
-ORIG: WAW 
- 
-DEST: AMS 
- 
-TIME: 1456 
- 
-  * **IN REPORT extended version** 
- 
-Subject: A-BCDE INRP (where A-BCDE is acft reg number) 
- 
-To: mvt@leon.aero 
- 
-**Content** 
- 
-10-JUN-2015 16:00:00 
- 
-IN EVENT REPORT 
- 
-ORIGIN: WAW 
- 
-DESTINATION: AMS 
- 
-ON TIME: 1600 
- 
-IN TIME: 1610 
- 
-FUEL ON BOARD: 0470 
- 
-  * **IN REPORT simplified version** 
- 
-Subject: A-BCDE INRP (where A-BCDE is acft reg number) 
- 
-To: mvt@leon.aero 
- 
-**Content** 
- 
-A-BCDE IN REPORT 
- 
-ORIG: WAW 
- 
-DEST: AMS 
- 
-TIME: 1600 
- 
-FOB: 0470 
- 
- 
- 
-<box> The format of the 'subject' & 'message' **MUST** be always the same, which means, that if you add anything to the text in either 'subject' or 'message' format, the message **WILL NOT** get imported into the 'Flight Watch'.</box> 
- 
-==== Eurocontrol ==== 
- 
-[{{ :leon:flight-flight-watch:Eurocontrol.png?250|Flight Watch from Eurocontrol}}] 
- 
-It is possible to receive Flight Watch times automatically to Leon from Eurocontrol servers. 
- 
- 
- 
-Integrating with Eurocontrol is very simple. You have to go to Admin > Operator Settings and in tab "General" tick **Import MVT from Euroconrol servers** checkbox. Finally click {{:leon:icons:update.png?nolink&50|}} to save changes. 
- 
- 
-It is possible that you will receive the following message: 
-<html>  
-<span style="color:red;font-size:100%;">Operator ICAO code error - the code stored in Leon was not recognised by Eurocontrol servers. Please consult Leon support. </span> 
-</html> 
- 
-This means that Operator ICAO code in "Handling Requests" tab in Admin > Operator Settings is not recognised by Eurocontrol. In this case you need to contact Eurocontrol and provide them with the correct ICAO code for your Operator. Once this is updated, you should be able to integrate with no further problems.. 
- 
-When the integration is completed, Flight Watch in Leon will start receiving flight times from Eurocontrol Servers. You will recognise them by opening a Flight Watch and hovering the mouse over the time value, as shown in the screenshot. 
leon/flight-watch.1464342197.txt.gz · Last modified: 2016/08/30 13:06 (external edit)