Note: The MAESTRO plugin is WIP and may contain bugs, if you think you have found one, let the developer know via the VATSCA Forums.
#### 2.1 Implementation (and limitations) on VATSIM: The MAESTRO plugin emulates the AMAN tool with the same name, developed by Egis-Avia (now Thales), in use at EFHK, EKCH, ESSA among others. Its functionality is limited compared to the real systems, however it can be useful in helping virtual controllers monitor and manage inbound flows and delays to one or more airports. The calculations are based on the predictions provided by EuroScope and its programmed data, so to get useable results, it is important to keep the aircrafts’ data updated. The most common problems are: - Wrong landing runway: - the aircraft won’t be included in the correct runway’s sequence at all. - Old direct-to clearance stuck: - the aircraft’s position in the sequence will be based on the predicted ETA which will be off by hours in the worst case as it assumes the aircraft turns back to that point. - Calculated sequence not being followed: - the whole sequence behind the affected aircraft is delayed until the sequence is manually corrected or the situation resolves itself as aircraft arrive and are removed from the sequence.Note:The plugin can only be used for one airport group at a time. (If you select ESSA, also traffic to ESSB will be shown)
#### 2.2 Interpreting and acting on generated data: **Example:** - SAS904 is inbound ESSA via ELTOK (ETA at ELTOK 17:35). - AMAN with help of EuroScope estimates, via the programmed STAR, it will take him 11 minutes flying from ELTOK to touchdown (on the selected runway).Note: For actual operational procedures with AMAN in use: see 3.6 #### 2.3 Timeline and Glossary - **STA:** Scheduled time of arrival - *flow planned arrival time by AMAN*. - **ETA:** Estimated time of arrival - *estimated using the FLEG route within Euroscope*. - **FF:** Feeder fix - *the waypoint where the STAR begins*. - **Current delay:** How much delay is needed to reach RWY at STA - *Current ETA RWY-STA RWY*. - **Total delay:** Initial ETA RWY-STA RWY - (i.e. for holding traffic, the total delay will increase)
Some information is excluded or simplified for ease of understanding and use, for more detailed information on the inner workings of the plugin, see the included manual in the .zip package.
#### 3.1 Plugin installation ##### MAESTRO The Swedish GNG package contains the latest beta version of the MAESTRO plugin by Juha Holopainen. ##### TopSky The Swedish GNG package contains a version of TopSky that automatically receives MAESTRO data for ESSA/ESSB and EKCH when updated data is available. #### 3.2 Operation modes ##### 3.2.1 Standalone mode The plugin calculates its own data (can be useful for testing the plugin for the first time, not sharing any sequence data)Note: TopSky automatically receives MAESTRO data from the server to show in aircraft labels and traffic management lists without the need to connect in MAESTRO.
You only need to connect via MAESTRO if you want to view the data on the MAESTRO timeline.
Note: All three AMAN operation modes work regardless if you are connected as an active controller or OBS.
The relevant operation modes for live operation on VATSIM are:
• MASTER (Web+Local)
• SLAVE (Web+Local)
The persistent use of (Web+Local) should allow the planned sequence to be kept if MASTER is changed (see 3.8).
When using several instances of EuroScope, the secondary instances are to be connected as:
SLAVE (Local)
| View Mode | Timelines | A/C Position on Timeline |
|---|---|---|
| Runway | One for each active arrival runway | RWY STA |
| FLOW | One for each pre-defined feeder fix group One for flights not routing via any of the defined feeders |
|
| ACC (Feeder) | FF STA |
Recommended view mode:
• ACC: ACC mode
• APP: Runway mode
Note: The ACC view is new since v1.1b3, it shows FF STA on the timeline instead of RWY STA.
--- ##### **3.3.3 The Flight Information Window:** The Flight Information Window can be opened from the callsign menu (see **3.3.1 -> 12**), it displays flight related data. as follows:
Note: TopSky automatically receives MAESTRO data from the server to show in aircraft labels.
Note: TopSky automatically receives MAESTRO data from the server to show in the TMLs.
See [TopSky Profile - Traffic Management List 1 & 2](https://wiki.vatsim-scandinavia.org/books/general/page/topsky-profile#bkmrk-traffic-management-l) to see the data fields showing AMAN/MAESTRO data. --- #### 3.4 Flight states (and their colors) Flight labels are color-coded according to their states which are based on the time from the airport and the feeder fix, except for the delay items whose coloring depends on the amount of delay, - ** UNSTABLE **(More than 12 minutes from the FF - *The sequence is recalculated on every position update*) - ** STABLE** (Within 12 minutes from the FF - *No plugin-initiated changes to the sequence*) - ** SUPERSTABLE** (Within 8 minutes from the FF - No plugin-initiated changes to the sequence, except for missed approaches re-inserted into the sequence) - ** FROZEN** (Within 5 minutes from landing - *No plugin-initiated changes to the sequence, except for the detected actual order on final)* - ** LANDED** (Flights considered as landed)Note: An aircraft disconnecting will always initiate a resequencing by the plugin.
Note: A flight still in UNSTABLE state can not be manually manipulated until it is turns STABLE.
--- #### 3.5 Interacting with flight labels and the timeline ##### Terminology: - Slot - During a slot no arriving aircraft will be calculated to land. - A slot can either bound to a specific flight (by clicking on a flight label), or specified as a time period (by clicking on the time line when in runway view mode, see 3.3.8) - Slots can be useful for manually planning departure gaps, short runway closures, or runway changes.If managing a runway change using AMAN, it is recommended to set the planned arrival runway manually for each aircraft (to prevent problems when changing the runway set as active for arrivals in EuroScope)
Note: Recomputing or moving a flight may become necessary when it is no longer in the unstable state (so its position in the sequence is fixed) and can no longer meet its calculated time profile, starting to delay all the flights behind it in the sequence.
Note: Disconnected flights will stay in the sequence for 10 minutes unless manually removed
(If a flight that is still online is removed from the sequence, it will be automatically added again).
When manually adjusting the sequence, a confirmation window will always be opened, asking to confirm or cancel the operation.
A flight still in unstable state cannot be moved.
Note:
Moving/adding a flight in only changes position in the sequence. The exact time in the timeline where the flight is placed is calculated by the EuroScope FLEG
Note: Any controller not responsible for managing AMAN may receive data as SLAVE.
ESMM may receive data about the planned sequencing into Arlanda, they do however not act on it, unless requested to by adjacent ESOS sectors (probably as it is too early with a relatively unstable sequence, unless severe delays are indicated/expected). Mainly the ESOS-sectors adjacent to Stockholm TMA monitor and judge/act on the AMAN data.The position acting as MASTER shall keep manual changes to the sequence to a minimum
**Suggested procedures when AMAN is in use (ONLY after prior coordination):**When only parts of the sequence is indicating a delay, ESOS ACC does not have to act on that information.
If all inbounds show several minutes to lose, consider holding or delaying inbound traffic as appropriate
(Use common sense, TTL and TMA/TOT numbers may help in judging this)
At times of higher workloads in the TMA, it is preferable that ACC hands over traffic excactly according to FF STA (no more "current delay" remaining).
--- #### 3.7 Getting started So now you've read through the entire wiki page and the pdf documentation? Great! What's next? Open the Setup window (see 3.3.1), enter the airport identifier in the ICAO window, select the desired operation mode.\ After selecting operation mode, it should look like below:To receive the web password for acting as MASTER, send an Email to max.kuhla@vatsim-scandinavia.org
or contact me via Discord (199890517914288128 or maxlk96)
Note: You do not need to have the AMAN window open to keep receiving updates to the sequence.
(when working ACC, all the information you need is in the TopSky track label, if all is working as it should for the MASTER)
Runway rates:
The runway rate preset in the system is defined by enviromental factors (high speed exits, runway used for departure simultaneously).
The actual available rate might be limited by human factors, such as:
• Controller capacity and experience (how consistent spacing can be produced)
• Pilot reliability (how quickly do they react, and how compliant are they in following instructions )
If the outputted numbers make no sense:
Try checking the aircraft in front of (below) the delays. Is there a time gap in front of him?
Also check all relevant FLEGs to see if they are correct, as they are used for the sequencing calculations.
If the final keeps getting longer: Maybe the arrival rate has to be lowered (See 3.3.2).
Alternatively, you can manually put in a slot behind one of the arrivals, in an attempt to give DIR a chance to catch up, and shorten the final.
When planning a runway change: Use time based slots to facilitate a smooth runway change, preventing that arrivals are planned to land on both runways at the same time (unless that is allowable).
When relieving the MASTER:
1. The relieving controller connects as SLAVE, (to fetch the planned sequence).
2. The relieved MASTER disconnects by selecting Standalone or SLAVE.
3. The relieving controller connects as MASTER.