Software and Tools

• vATIS
• AMAN (MAESTRO)
• TS VCCS (Ground to Ground Coordination)
• AFV (Audio for VATSIM)
• VatIRIS

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.

Note: Whenever a new update is released for the vATIS profile, you have to re-import it into vATIS, just replacing the .json with a newer one is NOT enough.

---

vATIS can be downloaded here.

vATIS Profile - ESAA (Last updated 2025-01-17)

---

Documentation and more information available on the vATIS website.

---

https://wx.awos.se/ and VatIRIS shows 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:

• SCCs (surface condition codes) can be added as free text to the ARPT COND window. In the real life AWOS, the text is manually entered as free text, which means there are some variations to the formatting and abbrevations used. For the text to work correctly in vATIS, you may need to edit certain phrases or formatting. Examples:
  • Generic format, as used by most ATIS where a single runway is in use: SURFACE CONDITION CODE 3 3 3. DOWNGRADED. ISSUED AT 1944 RWY 100 PCT 3 MM WET SNOW. TWY AND APRON POOR
  • The format used by ESSA AWOS (see below): RWY 01L SCC 5 5 5. ISSUED AT 1800. RWY 100 PCT WET. CHEMICALLY TREATED. Note that the contraction SCC is recognised by vATIS only at ESSA. For other ATIS, use plain text.
  • SNOWTAM format: ESNN 02291436 16 5/5/5 100/100/100 NR/NR/NR WET/WET/WET.
    • The "raw" SNOWTAM text in the example above would have to be formatted as free text to be properly interpreted by vATIS, like this: SURFACE CONDITION CODE 5 5 5 RWY 100 PCT WET
• NOTAMs can be added as free text to the NOTAMS window:
  • e.g. TWY Y3 CLSD or GLIDE PATH RWY 17 OUT OF SERVICE
• vATIS interprets certain phrases and abbrevations differently depending on context.
  • Y3 will be read out as "why three" whereas TWY Y3 will be read out as "taxiway Yankee three".
  • Runway designators will only be interpreted correctly if preceded by RWY, i.e. write RWY 01L instead of just 01L.
  • When a contamination depth is included, make sure there is a space before MM (i.e. make sure it says "1 MM", not "1MM").

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.

• Use punctuation as needed where a pause is desired in the spoken output.

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:

• AWOS for ESSA which shows real life runways in use as well as runway surface conditions is available at https://wx.awos.se/?siteId=ESSA.
• In vATIS, there are one or more presets for each runway combination. Some runway combinations have separate presets for IMC and VMC conditions (the phrase "additional spacing on final due to runways in use" is added to the IMC preset). Take care to select the relevant preset!
• Runway surface conditions can be added by pasting the info from AWOS. For the text to be displayed and read out correctly by vATIS, it needs to be in the correct format:
  • The "raw" text from AWOS might look like: 01R: SCC 5 5 5. ISSUED AT 18:57. RWY 100PCT DRY SNOW 2MM. TWY P APN P.
  • This needs to be edited to the correct format for vATIS. Include RWY before the runway designator, remove any colons and make sure there are spaces and punctuation where needed. Some abbreviatons may need to be changed into plain language. The above example when edited to suit vATIS should look like this: RWY 01R SCC 5 5 5. ISSUED AT 1857. RWY 100 PCT DRY SNOW 2 MM. TAXIWAYS POOR. APRONS POOR.
  • For DEP ATIS, include surface conditions for the departure runway only, as well as taxiway and apron conditions.
  • For ARR ATIS, include surface conditions for the arrival runway only, as well as taxiway and apron conditions.
  • AWOS lists the runway conditions based on the lowest runway designator, e.g. the conditions for RWY 01L/19R, 01R/19L and 08/26 will always be listed for RWY 01L, 01R and 08. In the ATIS, this needs to be adjusted to reflect the runway direction in use so you may need to manually change it to RWY 19R, 19L and 26.

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:

• An aircraft approaches a horizon of 150-200 nautical miles, AMAN captures it, calculates its ETA and inserts it in the sequence along with the others already there.
• In the ATCC, the TMA supervisor receives and validates the sequence provided by the AMAN and makes the necessary changes as needed.
• The advisories (Time to lose/Time to gain) that AMAN provides for each aircraft are transmitted to the en-route controllers, which they communicate with the aircraft and apply the appropriate delays or time savings.

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:

• 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).
  Without delays, SAS904 would land at 17:46
• Because of a peak in arrivals to Arlanda, the first available landing slot is at 18:00
• AMAN calculates the difference between SAS904s present ETA at ELTOK (17:35) and his STA (scheduled time or arrival) [18:00 - 11 minutes = 17:49].
• The difference between his ETA and STA over ELTOK is calculated [17:49 - 17:35 = 14 minutes].
• SAS904 has 14 minutes to lose (to fit into the sequencing calculated by AMAN), this is called his current delay, or TTL (time to lose).

---

• Depending on the TTL, delaying vectors, speed restrictions, or holdings may be given, to comply with the STA overhead the FF.
• 14 Minutes is aproximately 3 or 4 patterns in a holding, depending on the outbound time.
  
  
• The time to lose (or to gain, when shortcuts are beneficial for the sequencing) is presented to the controller, and continously updated, freeing him from all manual calculations.
  (This allows the controller to inform the pilot in holdings when to expect further clearance, which is the same as his STA (17:49))

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)

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:

• Web - Data is uploaded to a server
• Local - Data is saved to the local computer to be used by other EuroScope instances
• Web+Local - Both of the above

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.

• Web - Data is downloaded from a server
• Local - Data is read locally
• Web+Local - Data is downloaded from the server, and then saved to the local computer to be used by other EuroScope instances

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.

• Left-clicking on the button above AMAN in the COTS Window opens the AMAN Window.
• Windows are closed by left-clicking the box in the top right corner.
• Windows are resized by dragging the box in the bottom right corner.

---

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

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:

1. 
2. 
3. 
4. 

---

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:

• L (Lose) for time to lose (Delay)
• G (Gain) for time to gain (FF ETA is later than the FF STA)

---

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,

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

3.5.1 Callsign menu

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

• Recompute Recomputes the flight’s data
• Change Runway - Opens the EuroScope menu to set the arrival runway
• Insert Slot - Opens the slot submenu (a value of 0 minutes removes the slot)
• Remove - Removes the flight from the sequence
• (The rest of the options are not implemented)

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:

• Insert/Modify Slot Opens the Slot Modification Window (only available in the Runways view)
• Insert Flight Allows to type in a callsign already in the sequence to move into that position

3.5.3 Manually adjusting the sequence

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

• By dragging a flight label to the wanted position in the sequence
• Left-click on a time in the timeline, select "add flight" (can be done to already existing flights)
• Left-double click a flight label (the label becomes boxed), then select another another flight label, the two will swap its positions in the sequence

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.

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

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

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

• To test the functionality press TEST in the VCCS window, then use PTT, you should hear yourself.

• To call someone:

  • left-click on a green position in the VCCS window, or
  • right-click on a position in the controller list, Call on VCCS

  then use PTT like in Teamspead/Discord when you want to talk.

• To answer an incoming call:

  • left click where it flashes (and shows which position is calling)
    • in the VCCS mini-control, or
    • in the large window

• To hang up, click where you clicked to answer, or END in the large VCCS window.

Position frame colours

• Green: Position online, using VCCS (not necessarily correctly configured).
• Yellow: Position online, old Euroscope version without VCCS.
• Blue: Position not recognised due to incorrect SI, call via right click->Call on VCCS in thecontroller list.
• Red: You guessed it. Position offline.

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

4. Known Issues

• Calling the same position several times using VCCS may crash your Euroscope, if this is the case, use Discord.

AFV (Audio for VATSIM)

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

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

• Audio for VATSIM standalone client
• TrackAudio client
• VectorAudio client (now replaced by TrackAudio)

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,
but 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:

• Provide situational awareness for air traffic controllers by combining previously separate data into one interface.
• Improve safety and operational efficiency for airports by allowing seamless communication between controllers and other operational systems.

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)

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.

• Chrome
• Edge
• Firefox

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.

• Reload arrows Reload Button - Reloads the data in all open windows.
• SYSTEM
  • SETTINGS - Open personal options view.
  • PRESET - Create/manage window presets, default presets are also available here.
  • RESET - Reset settings.
  • LOGIN/LOGOUT - VATSIM Connect: log in/out.

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.

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

• ESGG - Airport designator (Göteborg Landvetter).
• YAN - ATIS letter (YAN=Yankee).
• 241125 - Date YYMMDD (2024-11-25).
• M W A - View modes (show above).
  • M for METAR.
  • W for WX.AWOS.
  • A for VATSIM ATIS.
• RWY 21 - Runway in use.
  
• 251520Z - Date of the met report DDHHMM (25th 15:20z).
• WIND - Wind.
• VIS - Visibility.
• -RA - Precipitation, ("-RA" meaning light rain might also be shown as "FBL RA").
• CLD - Clouds.
• T09 DP08 - Temperature and dewpoint in Celsius, (minus shown as "MS"=TMS12=Temperature minus 12).
• QNH 0995 ⯈ HPA

  • QNH Trend Arrow - Shown to the right of the QNH value.

    The trend arrow indicates if the QNH has changed since the last update or not. Sometimes this arrow appears after the first time data is changed/updated.

    • QNH increased: ⯅
    • QNH same: ⯈
    • QNH decreased: ⯆
• TRL 70 - Transition level (calculated from QNH or loaded from ATIS/WX.AWOS, depending on view mode).
• SURFACE CONDITION CODE(...) - Used entered NOTAM / Airport conditions, shown only in WX.AWOS and ATIS view modes.

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:

•  RWY 21  - No mismatch (ATIS runway matches WX.AWOS)
•  RWY 21  - Mismatched runway (ATIS runway differs from WX.AWOS)

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:

•  YAN  and  RWY 21  - VATSIM ATIS available, no mismatch (ATIS runway matches WX.AWOS)
•  YAN  and  RWY 21  - VATSIM ATIS available, mismatched runway (ATIS runway differs from WX.AWOS)
•  YAN  and  RWY 21  - VATSIM ATIS not available.

Stockholm/Arlanda ESSA

For ESSA there are three menu options ATIS view mode is only available for ESSA ARR and ESSA DEP.

---

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.

• MEAN02 - Mean wind, this is the wind given to the pilot at takeoff and landing clearance.
• VRB - Wind variable between
  • only given to pilots when present in METREPORT.
• MIN/MAX - Minimum/maximum wind
  • only given to pilots when present in METREPORT.
• COMP - Wind component.
  • +08/L03 shows 8 knots tailwind component and 3 knows crosswind component from the left.
• RVR - Runway visual range
  • given to pilots on request or during LVP.
• VIS - Visibility.
• PRW - Precipitation.
• CLD - Clouds.
• QNH - QNH
  • rounded down when given to pilot/shown in met report.
• TRL - Transition level.
• QFETHR - QFE for the respective threshold.
• T SURF/BODY - Temperature at surface/body of respective runway 
• QFE - QFE for airport elevation.
• T - Temperature in Celsius
  • minus shown as "MS"=TMS12=Temperature minus 12.
• DP - Dewpoint in Celsius.
• HUM - Relative humidity, indicated in percent
  • 100% if T and DP are the same.

---

METAR/TAF

Shows raw METAR/TAFs.

Buttons:

• METAR - Toggles visibility of METARs
• TAF - Toggles visibility of TAFs
• AERODROMES - Selects which aerodromes are shown

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

---

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.

• "Separation VFR" is shown during nighttime when VFR needs to be separated.

ATFM - Air Traffic Flow Management

ECFMP

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

Legend

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.

• Expired/Withdrawn - Toggles visibility of expired/withdrawn measures.
• Notified - Toggles visibility of notified measures.
• Reason - Toggles visibility of "Reason" column.
• New - Opens ECFMP website to add new measure (requires login and flow manager roles).
  

"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:

• Open position - For when opening position.
  • When not taking over any airspace from already open positions.
• Close position - For when closing position.
  • When no relieving controller is taking over position.
• Handover/takeover - For when other controller/position is relieving (taking over) your airspace/position.
• Runway change - For planning and coordinating a runway change.

---

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.

---

WIKI

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.

• ESSA PUSH - Pushback procedure charts
• ESGG PUSH - Reference to which pushback direction is available from which stand, and information regarding which stands are blocked when pushing back for the respective stand (shown as tooltip when hovering stand number)

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

---

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.

• Auto - Toggle visibility of "Auto" aliases.
• FSS - Toggles visibility of "FSS" aliases.

---

AIRCRAFT TYPES

Shows a searchable list of aircraft types, showing ICAO type code, wake turbulence category, wingspan, MTOW etc.

---

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.

•           - Indicates airborne aircraft.
•           - Indicates aircraft on ground and pre-filed flight plans.

DCT

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

---

PLS (only shown when PLS integration selected.)

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 (CID or POSITION)
   • 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

• To "go on position": press the PLS icon and enter the position/callsign you are connecting with/as.
• To "go on break": press the PLS timer and confirm you want to go on break.
  

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

• None - On position
• P - On break
• Ö - On break (Övrigt/other)

---

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 thread on Discord.

Contributing

Contributions of any kind are most welcome.

• If you find a bug or have a feature request/suggestion, please check that it doesn't already exist, if not, add an issue on Github.
• Github Pull requests are welcome.

Credits

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

• Martin Insulander - 814118
  • Discord @mumrikki
• Max Kuhla - 1157125
  • Discord @maxlk96
• Among others.