Software and Tools

Information about Software and Tools used by Controllers

vATIS

Since ES v3.2.2 it is possible to have up to 4 simultaneous ATIS-connections, however in Sweden we use vATIS. vATIS offers the same number of ATIS connections, but also easier addition of RWYCC (Runway condition codes) and NOTAMs as free text.

To use vATIS you need to download the software itself, and import a profile, both of which are linked below.


vATIS

vATIS Sweden Profile

The profile is updated automatically when a new version is found.


Documentation and more information available on the vATIS website.


https://wx.awos.se/ and VatIRIS shows real life AWOS/ATIS for many airports in Sweden.


ATIS formatting

We use vATIS to simulate as closely as possible both voice ATIS and D-ATIS (datalink ATIS in text format). Therefore it is important to use the correct text format to ensure that both the ATIS text looks reasonable, using plain language or common abbrevations (contractions in vATIS terminology), and that audio output is sensible.

Always check that the ATIS output is reasonable, especially when using free text in the ARPT COND or NOTAMS fields. vATIS may not recognise certain abbreviations. If this is the case use plain language instead. ATIS output can be checked by selecting "Get ATIS" for the relevant ATIS in the ES controller list. Audio output can be checked by using the sandbox feature in vATIS or by adding the relevant ATIS and listening to its frequency in AFV.

LVP:

When LVP is in force it can be added to the ARPT COND window with LVP as free text, or activated by clicking on the APT COND text above the text field, and selecting LVP in the list.

Adding free text:

For the most common reported contamination depth of 3 mm, the phrase 3MM (without space before MM) has been added for convenience. For other depths, make sure to add a space before MM as described above.

When adding or pasting free text to the ARPT COND or NOTAMS fields, take care to remove colon symbols ( : ) or double spaces ( ) where included, as the remaining text after will be ignored if the symbol/double space is not removed.

Note: Text added in the ARPT COND and NOTAMS fields is saved by clicking the save icon that appears in the text field when adding text. The text will remain in place for that preset until it is edited or deleted (including after closing and re-opening vATIS). Pre-defined airport conditions (such as LVP) will also remain in place until deselected. When setting up an ATIS, make sure that no old/irrelevant ATIS text is present.

ESSA ATIS set up and formatting:

In real life, the ATIS designator letter for DEP ATIS and ARR ATIS are usually different. This might be inconvenient on VATSIM as there is no practical way to display both ATIS letters in ES. Therefore it may be preferable to use the same letter for both DEP and ARR ATIS.

AMAN (MAESTRO)

1. Background information

The issue and its solution:

Aircraft enter the TMA at several FFs (feeder fixes, the waypoint where the STAR begins). For landing, all aircraft must be sequenced. Here, the problem is building the optimal sequence of aircraft as there are several constraints involved (e.g. wake turbulence, runway specific rates depending on high speed exits, departure gaps). AMAN can calculate this sequence and display it to the controllers, which in turn can act on it when deciding who is allowed inbound without (further) delays, or if holding, who may leave the hold and when.

An arrival manager (or AMAN) works as follows:

2. Introduction

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:

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:


Note: For actual operational procedures with AMAN in use: see 3.6

2.3 Timeline and Glossary

3. Plugin usage and procedures

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)
This mode can also be selected to disconnect from other previously selected modes.

3.2.2 MASTER mode

The plugin calculates its own data, and shares it as follows:

3.2.3 SLAVE mode

The plugin receives its data from an outside location depending on the settings:

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)


3.3 General Operation

The COTS and AMAN windows can be moved by dragging them from the title bar. Other windows are non-moveable.


3.3.1 The AMAN Window:

  1. The current airport (left-click to open the Setup Window)
  2. The runway rates (left-click to open the Change Rates Window)
  3. The measured actual rates during the past 30 minutes and deviation from set values
  4. The sequence in numbers: aircraft past the FF (TMA), and the total number of aircraft (TOT)
  5. The current operation mode, empty for standalone mode. (MASTER/SLAVE, the SI of the controller, local/web/web+local)
  6. The UTC time when the data was last refreshed
  7. Opens a menu to scroll between the FFs when in ACC and FLOW view mode, including an option to toggle visibility of the panels marked in red (1-6)
  8. Changing between the three view modes: (See 3.3.2)
  9. The “Desequenced” button displays the number of De-sequenced flights, (left-click to open the De-sequenced List).
  10. Current UTC time (left-click to open the Labels Window, changing what is displayed in the flight label)
  11. Scrollbar (Can be moved by dragging the bar itself, or by clicking on the background area next to the bar. Left-clicking changes the setting by one unit, right-clicking by 10 units, double-click to resume to default view)
  12. The flight label, from left to right (left-clict to open callsign menu)
           • Current delay (Color depending on how long the delay is)
           • Aircraft callsign (Color depending on flight state)
           • STA RWY or FF depending on view mode
             (When in holding: the time in which the FF shall be passed, inbound TMA.)
  13. The timeline, upwards on the scale indicates the future. defaulting to show current time at bottom. As time progresses, the scale automatically moves from top to bottom (To scroll, see 10.).

3.3.2 The view modes:
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

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:


3.3.4 The De-sequenced List:

The “De-sequenced” can be opened from the main AMAN window (see 3.3.1 -> 9), it contains flights temporarily removed from the sequence. They are presented in the same order as they were entered into the list. Left-clicking one or more callsigns highlights them. The “Resume” and “Remove” buttons can then be used to either re-enter the highlighted aircraft back into the sequence or remove them from it permanently.


3.3.5 The TopSky track label:

Note: TopSky automatically receives MAESTRO data from the server to show in aircraft labels.

When AMAN is active for an airport, for arrivals having a predicted sequencing, the current delay is displayed in line 0 of the track label in minutes, with one of the following prefixes:


3.3.6 The Traffic Management Lists

Note: TopSky automatically receives MAESTRO data from the server to show in the TMLs.

See TopSky Profile - Traffic Management List 1 & 2 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,

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:

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)


3.5.1 Callsign menu

Left-clicking on a flight label opens the callsign menu with the following options:

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).

3.5.2 Timeline menu

Left-clicking a timeline opens a menu with the following options:

3.5.3 Manually adjusting the sequence

Changing the generated sequence can be done in the AMAN window in following different ways:

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


3.6 Roles, responsibilities and procedures

In real life. Stockholm (ESOS) receives (and transmits) AMAN data for ESSA. Malmö (ESMM) ATCC additionally receives AMAN data for EKCH also. The MAESTRO tool is managed by APP-C for the arrivals into Arlanda.

The following positions may be responsible managing the arrival sequencing to Arlanda using AMAN as MASTER, beginning with the highest and progressing to the lowest priority:

  1. ESSA_C_APP (No active frequency)
  2. ESOS_PLN_CTR (Separately approved frequency. 123.975)
  3. ESSA_E_APP (When no separate planner is online. 126.650)
  4. ESOS_1_CTR (When ARR-E is not separately manned)

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)

MASTER:

SLAVE:

Click "Ok", and get to work, sequencing, or observing the sequencing!

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)

3.8 Tips and Tricks

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.

TS VCCS (Ground to Ground Coordination)

1. Introduction

Euroscope has an integrated voice coordination tool, called VCCS (voice communication control system), it can be used for ground to ground communication between controllers as an alternative/supplement to Discord.

To enhance the coordination between controllers, VCCS can be used to solve the problem of controllers muting the Discord channel, with VCCS they are still reachable despite being muted on Discord.

Discord is to be used as the main tool for voice communication, VCCS can be used in parallell to enhance the experience. It does hover require both parts to have it correctly configured.

2. Setup Instructions

  1. Open the TS VCCS mini control box using the Quick SET-menu. The VCCS mini box can be moved around, drag with the left mouse button.

  1. Right-click the VCCS mini box to open up the VCCS main window, then click EDIT to bring up the settings window.

  1. Verify the marked fields are filled in as follows:

    • Server name: any valid TS VCCS server, either ts.intor.fi or ukvccs.vamsys.io.
    • Server port: 9988
    • Nickname: Suggest you use your CID, THIS NAME MUST BE UNIQUE
    • G2G (ground to ground) PTT: SELECT A UNIQE PTT, NOT the same as your AFV or Discord PTT.
    • Devices: Select the desired input and output devices
  2. Click okay to save the settings

Note: Do not forget to save the settings when closing Euroscope after the initial setup has been made.

For further information, see the Euroscope doccumentation

3. Usage Instructions

Position frame colours

If coordinating via VCCS is not successful/suitable, revert to using Discord or Euroscope PM.

4. Known Issues

AFV (Audio for VATSIM)

Since 2018 VATSIM is using a new voice codec, reducing latency and increasing voice quality.

Euroscope has not yet been updated to natively integrate and support the audio client, therefore requiring one of the following standalone audio clients to be able to communicate via radio:

Crosscoupling

When manning positions covering large areas with the use of several tranviecers (i.e. ESOS_1_CTR) controllers are urged to cross-couple (XC) their frequency, even if using a single frequency, this helps pilots hear each other even when outside of their local radar range.

Relieving positions

When relieving positions, make sure to manually add and select the correct position callsign in the audio client, as this is the only way to ensure the correct trancievers are being loaded. (See picture below)

VatIRIS

Overview

VatIRIS is an interpretation of its real-world counterpart:
IRIS - Integrated Real-time Information System,
adapted and extended for use by VATSIM controllers in Sweden.

IRIS is designed to provide real-time information to various aviation facilities. It integrates and displays critical information such as air traffic data, weather conditions, and navigational aids into one flexible, role-based presentation.

Purpose of VatIRIS

VatIRIS can be used to:

User Interface

The different modules in VatIRIS are contained in a GUI similar to Windows or MacOS with resizable windows for each module.

Window snapping is enabled by default but can be disabled under SYSTEM -> SETTINGS if desired.

Modules

Below are some examples of the different types of information that the different modules can show:

  1. Dynamic Information

    • Real time weather data (METAR, TAF, Weather sensor values, Weather map).
    • ECFMP Flow measures.
    • Airspace Occupancy data.
    • PLS data.
  2. Static Information

    • AIP (Aeronautical Information Publications).
    • Pushback procedure maps.
    • Manuals and regulations (LOP, GOP etc. from Wiki)
    • Tactical directs (DCT)

Data timestamps

Most modules show a timestamp in the top right corner of each window.

The timestamp is not shown at all if not relevant (e.g. for data from Wiki and AIP).

Sometimes the timestamp only shows (in red) when the data is outdated (METREPORT and METSENSOR).

Logging in using VATSIM Connect is required to access most features, saved presets etc are also stored connected to your account, this manual assumes you are logged in to IRIS.

Saving/"Installing" VatIRIS an app

Using IRIS as a standalone "app" (PWA - progressive web application) instead of within a browser is recommended. Below you can find guides on how to for the most common web browsers.

The Menu Row

All modules/windows can be opened using the menu row,

A short description of the first level of buttons are shown below, modules that can be opened using a button are described in their entirety under Module Descriptions.

System Menu

To the left in the menu bar you'll find the following buttons, affecting the general behaviour of IRIS system-wide.

Main Toolbar

The buttons to the right of SYSTEM are connected to their specific modules, each button opens their own window or a submenu, see Module Descriptions for a full description of each module.

The global search function can be used to quickly find the module you are looking for.

The global search can be accessed by pressing the search icon in the menu row, alternatively with the button combination Shift+Space or Shift+Enter

Module Descriptions

MET - Meteorological information

AIRPORT

Showing a combined view of SUN, METREPORT, TAF and METSENSOR.


METREPORT

Showing decoded weather data parsed from one of the selected data sources depending on view mode.

View modes:

Only available sources for the respective airport is shown. The data source is automatically switched to the preferred source when one becomes available (A>W>M).

Updated data (blue flash):

When new data is available for the selected data source:

  1. The window for that airport flashes in blue.
  2. All text turns blue after the window has flashed.

Left click anywhere in the window to reset the "blue flash" to indicate that you have seen the update.

This is enabled by default but can be disabled under SYSTEM -> SETTINGS if desired.

Legend

image.png

Runway mismatch indicator in ATIS view mode - Compares the RWY in use between VATSIM ATIS and WX.AWOS data and highlights the runway in use as follows:

At Stockholm Arlanda (ESSA), both arrival and departure runways are monitored. A warning is shown if one or both mismatches.

Greyed out information in WX.AWOS view mode - the ATIS letter and RWY designator are greyed out from AWOS view mode when a VATSIM ATIS is available:


METSENSOR

Showing weather data in real time (updated every minute, or more frequently).

Updated data (blue flash):

When new data is available the data field that was updated flashes in blue.

This is disabled by default but can be enabled under SYSTEM -> SETTINGS if desired.

Legend

The data is displayed in three separate columns, depending on which sensor and where it is located (03  M  21), below an example for ESGG.

image.png


WINDROSE

Showing a wind rose, indicating wind direction, speed, cross/head/tail-wind component etc.

AWOS data is used for airports where it is available, METAR data will be used where no AWOS data is available, there is no way to manually select which data source to use.

Everything in the middle of the circle shall be read out to the pilot, what is shown is automatically filtered.

Legend

The module will default to display the runway with the highest headwind component.

  1. Runway selector, choses which wind anemometer (wind sensor) to use if several are available, this also affects the wind components shown in 5.
  2. Mean wind direction and speed (2-minute average, MEAN02 in metsensor).
    • Values shown in the circle shall be read to the pilots!
      • ≤60 degrees direction span (250-320 degrees in the example above) are shown.
      • ≤180 degrees shown as VRB.
      • ≤10 knot difference between mean wind speed and MIN/MAX speeds are shown.
  3. The compass rose
    • The red line indicated the mean wind, coming from 280 degrees in the example above (2-minute average, MEAN02 in metsensor).
    • The yellow arc indicates the variable wind (10-minute average), variable between 250 and 320 degrees in the example above.
    • The dark grey thick line indicates the selected runway and its direction, 08/26 in this case
  4. MIN/MAX (GUST if METAR data) wind shows the minimum and maximum winds.
    • The MIN/MAX/GUST wind is shown in bold if it shall be read to the pilots (≤10 knots difference between 2-minute and 10-minute min/max wind speed).
  5. The head/tail-, and crosswind component indicators, this is affected by the runway selected in the top right corner. The example shows 2 knots headwind component and 1 knot crosswind component from the right for runway 26.

METAR/TAF

Shows raw METAR/TAFs.

Buttons:

Aerodromes not listed can be manually added using the text field.


SMHI

Shows SMHI "weather radar" from https://portaler-lfvradar.smhi.se/sverige

The map displays precipitation intensity, along with lightning strikes detected by lightning sensors.

New images are available every 5 minutes.

Legend

image.png


SWC NORDEN

Nordic significant weather chart.

Legend available here.

VFR

VFR analysis chart - This chart provides a quick and clear overview of weather conditions relevant to Visual Flight Rules (VFR).


SUN

Shows sunset/sunrise and day/night times.

NOTAM - Notice To Airmen

Shows information about facility/service/procedure availability and hazards, such as taxiway/runway closures etc.

The NOTAMs can be filtered by aerofrome.

ECHARTS - LFV eCharts

Shows (a custom version of) LFV eCharts, where you can view airspace/waypoint information etc.

FLIGHT - Flight List

ARR DEP

Shows a list of flights to/from the selected aerodromes.

ATFM - Air Traffic Flow Management

ECFMP

Shows flow measures from ECFMP - European Collaboration & Flow Management Project.

Legend

image.png

The measures are displayed in three different colours depending on the state of the flow measure:

  1.  Active  - This flow measure is presently in effect.
  2.  Expired/Withdrawn  - This flow measure is no longer in effect.
    • Expired=The end time has passed.
    • Withdrawn=The flow measure was cancelled before the end time has passed. (End time column shows withdrawal time)
  3.  Notified  - This flow measure will become active within the next 24 hours.


"ID" and "Filters" columns can be filtered using the text fields

Enter " ES" in filters so see all measures mentioning any Swedish airport.

When hovering the mouse over a measure type a description is shown.


DOCUMENTS - Wiki/AIP and other operational information.

CHECKLISTS

Shows checklist for controllers, (to be used as reference, not necessarily "read and do") the following are available:


QUICKREF

Shows Quick References/Appendices as available from Quick References/Appen... | Wiki

The runway configuration in use is automatically selected but can also be manually chosen.


GOP/LOP/LoA

Shows Wiki pages as available from ATC Sweden | Wiki


AIP

Shows AIP pages as available from IAIP – AD 2 Aerodromes


OTHER

Shows other operational information.

Note that pilots may not follow the IRL pushback procedures, depending on usage of tools such as GSX, also depending on updated profiles etc etc...


CODES (ICAO)

Shows a searchable list of


REGIONAL AD

Shows the "Regional Aerodromes Overview" created by Thomas Ljung, from VATSIM Scandinavia Forum


TEXT ALIAS

Shows a searchable quick reference to the text alias included in the Swedish GNG package.


NOTEPAD

Shows a notepad to write notes, such as non-standard agreements with adjacent positions etc.

TRAFFIC

Shows sector occupancy for the selected sector combination.

The X-axis shows time, the Y-axis shows number of aircraft in the selected airspace volume.

ATS

Shows ATC bookings for the coming two days.

SECTORS

Shows Otto Tuhkunen's dynamic ACC sectorisation map.

DCT

Shows tactical directs (quick reference to LoA, shown at TopSky-map).


PLS (only shown when PLS integration selected.)

There is a SIMPLE logic mode available, this is completely independent of the actual PLS system and will only show a timer of your time online (using the CID which you are logged in with in IRIS).

Configuring/activating PLS
  1. Activate PLS Integration under SYSTEM -> SETTINGS
    • This displays the PLS timer and PLS icon in the menu bar
  2. Select your PLS logic mode.
    • SIMPLE -  Independent of the acual PLS system, showing the online session length automatically using your CID from VATSIM Connect.
    • CID - To be used when controlling from home, the PLS timer will show no matter the status.
    • POSITION - Only to be used when controlling at location during real live events etc.
  3. Enter CID/POSITION if needed (normally not needed if using VATSIM Connect).
Using PLS + Legend

Legend (timer suffixes, only shown in CID logic mode):



Postface

Changelog

There is no specific changelog available, however all changes can be viewed on Github - Commits.

Significant changes are normally also announced in the VatIRIS forum thread

Contributing

Contributions of any kind are most welcome.

Credits

To get in contact with the developers of VatIRIS (contact via Github might be preferred):