vIDS

Click on the tabs above to access relief briefings from the ATL ATCT SOP, Appendix H.

NOTE: There must be at least a 4 minute overlap during each position relief briefing: A minimum of 2 minutes prior to receiving the briefing and a minimum of 2 minutes at the end of the briefing. At the beginning of the 2 minutes prior to the briefing, the relieving controller must be monitoring the frequency. Upon completion of the briefing, the controller relieved must monitor the frequency for 2 minutes.

Appendix H-1: Flight Data/Clearance Delivery Checklist:

Status Information Area (SIA) on the IDS page. The relieving controllers acknowledges review of the SIA prior to the verbal briefing.
ATIS content (e.g. wind shear alerts).
Traffic Management Initiatives (mileage in trail, ground stops, call for release, etc).
Special operations.
Communication status and traffic (including):

IFR aircraft standing by for clearance.
VFR aircraft requesting/not requesting flight following.
Special problems, requests, or instructions.

If the IDS is not up to date, also brief: departure ATIS, runways in use, and A80 departure/satellite splits.

Appendix H-2: Ground & Local Control Checklist:

Status Information Area (SIA) on the IDS page. The relieving controllers acknowledges review of the SIA prior to the verbal briefing.
Runway status (verbally state if unavailable, closed, or occupied).
Weather (e.g., ILS critical areas to be protected, RVRs, etc).
Traffic Management Initiatives (mileage in trail, ground stops, call for release, etc).
Coordination agreements (e.g., arrivals to other than the designated arrival runways, departures from other than the designated departure runways, aircraft parked on the movement area due to ground stop, etc).
Communication status and traffic (including):

Special activity aircraft (e.g., emergencies, helicopter traffic).
Point outs (e.g., traffic landing inboard runway).
Aircraft holding on the movement area.
Aircraft standing by for service.
Special problems, requests, or instructions.

If the IDS is not up to date, also brief: departure ATIS, runways in use, and A80 departure/satellite splits.

Appendix H-2: Ground & Local Control Checklist:

Status Information Area (SIA) on the IDS page. The relieving controllers acknowledges review of the SIA prior to the verbal briefing.
Type of approach in use. (Visual, ILS, duals visual-ILS, trips ILS-ILS-visual, etc.)
Runway status (verbally state if unavailable, closed, or occupied).
Weather (e.g., departure headings, wind, wind shear, braking action, ILS critical areas to be protected, RVRs, tends, etc.)
Traffic Management Initiatives (mileage in trail, ground stops, call for release, etc).
Airport activities (RNAV OTG / non-ROTG ops, etc).
Coordination agreements (e.g., arrivals to other than the designated arrival runways, departures from other than the designated departure runways, etc).
Communication status and traffic (including):

Special activity aircraft (e.g., emergencies, helicopter traffic).
Point outs.
Holding aircraft (e.g., traffic held out of sequence).
Aircraft handed off but still in the airspace (e.g. prop turn-outs, 270 over the top).
Aircraft released but not yet airborne (e.g., if LC-3 was being relieved, they would brief any of LC-2's cross-complexes that are not yet airborne).
VFR advisory aircraft.
Aircraft standing by for service.
Special problems, requests, or instructions.

If the IDS is not up to date, also brief: departure ATIS, runways in use, and A80 departure/satellite/final splits.

Click on the tabs above to access relief briefings from the A80 SOP, Appendix 3.

Conduct position relief briefings IAW FAAO 7110.65 using the following checklists.

3-1. Position Relief Briefing for DR

Status information area (A80 IDS page).
Weather impact (e.g. impact of winds aloft, PIREPs, etc).
ZTL split for all sectors bordering DR airspace (arrival and departure sectors).
Special operations.
Coordination agreements (e.g., departure airspace delegated to another position, etc).
Traffic. (Including RNAV aircraft on radar vectors, speed assignments).
If the IDS is not up to date, the following information must be briefed:

DEP split (NW/SE, FTD, RNAV OTG / Vectors - etc).
SAT, Outers, TAR, and DR airspace split.
Traffic Management initiatives (e.g., miles-in-trail restrictions, etc).

3-2. Position Relief Briefing for SAT-P/F/G-X

Status information area (A80 IDS page).
Weather impact (e.g. deviations, impact of winds aloft, etc).
ZTL split for all sectors bordering SAT airspace (arrival and departure sectors, Rome).
Special operations.
Traffic.
If the IDS is not up to date, the following information must be briefed:

ATL Arrival ATIS code, type of approaches/runways in use, latest ATL weather.
For PDK/FTY/MGE/RYY/LZU, if open, ATIS code, runway in use, latest weather.
SAT, Outers, AR, TAR, and DR split.

3-3. Position Relief Briefing for TAR

Status information area (A80 IDS page).
Weather impact (e.g. winds aloft impact on aircraft speed/track, deviations, downwind heading, RVR, etc).
ZTL split for all sectors bordering TAR airspace (arrival and departure sectors).
Traffic Management initiatives (e.g., speed restrictions at the outer fix, aircraft flowed on the downwind or base leg side, etc).
Special operations.
Coordination agreements (e.g. approaches other than advertised, arrivals to departure runways, airspace, etc).
Traffic. (Including RNAV aircraft on radar vectors).
If the IDS is not up to date, the following information must be briefed:

ATL Arrival ATIS code, type of approaches/runways in use, latest ATL weather.
SAT, Outers, AR, and DR split.

3-4. Position Relief Briefing for AR

Status information area (A80 IDS page).
Weather impact (e.g. winds aloft impact on aircraft speed and track, deviations, RVR, etc).
Special operations.
Coordination agreements (e.g. approaches other than advertised, arrivals to departure runways, airspace, etc).
Traffic. (Including speed assignments).
If the IDS is not up to date, the following information must be briefed:

Type of approach and runways in use.
Latest ATL weather.

3-5. Position Relief Briefing for CSG/MCN/SAT-E

Status information area (A80 IDS page).
Weather impact (e.g. winds aloft, etc).
Special operations.
ZTL split for all sectors which border the sector(s) being briefed.
ZJX split for all sectors which border the sector(s) being briefed (CSG and MCN only).
Montgomery/Cairns Approach split (CSG only).
Augusta Approach split (MCN and Athens only).
Traffic.
If the IDS is not up to date, the following information must be briefed:

As appropriate for sector being briefed and if the tower is open, ATIS letter/approaches and runways in use/latest weather for CSG/LSF/MCN/WRB/AHN.
Outers, SAT, DR, and TAR airspace split.

Overview

vIDS is a collaboration and information sharing tool. Data entered on your display will populate on the displays of all other users logged in within 15 seconds. Any user that did not make the change will see a change advisory with the updated item highlighted in red and a button asking the user to acknowledge the change. Although all users logged into the system can make changes to the data in vIDS, only the facility CIC should make changes.

The vIDS system contains multiple display formats, some of which are user-customizable. Critical data is automatically-shared between the different display elements (for example, the A80 display uses live data elements from the ATL local display). Because of this feature, all users benefit from the same data despite viewing different displays.

The local display

Local view is optimized for use by controllers working the ATL tower cab (CIC, LC, GC, CD, GM, FD). The countdown in the upper right corner displays the remainder of the 15-second auto-refresh interval. When this count expires, the system pulls the most current data from sync files and the VATSIM network and refreshes all data on the user's display. Clicking the "refresh" button in your web browser will not speed this process up, as the network limits pulls to 15 seconds in order to manage traffic. Please allow the page to auto-refresh.

The top line of the grid displays the current ATIS code (or -- if no ATIS), the current METAR, direction of traffic flow, and critical departure and arrival information. The next set of grids display controller combinations - the position is in static text in the top row followed by the controller that the position is combined to in a drop-down menu in the second row. The departure positions also contain a box for the display of departure gates underneath the controller combinations. Clicking on these boxes allows entry of assigned departure gates.

Located to the right of the controller position combinations, there are display areas for the current airfield configuration and traffic management information. This data can be entered using menus launched via the AFLD and TMU buttons below. At the bottom of the grid, there are display boxes for pilot weather reports (PIREPs) and controller-in-charge (CIC) messages. Similar to the previous displays, this information can be changed through use of the PIREP and AFLD buttons below.

Menu buttons

At the bottom of the grid, there is a row of buttons that each launch a unique pop-up with additional information or settings.

HOME: return to landing menu. Also used to submit a bug report.
WX: button displays local ATL METAR, TAF, and NEXRAD.
RECAT: displays the current consolidated wake turbulence guidance.
FREQS: displays the facility frequency map.
ARSPC: depiction of facility/position airspace.
ROTG: shows the current RNAV-off-the-ground cheat sheet.
SOP: launches the facility SOP.
LOA: displays applicable LOAs.
PIREP: allows a controller to enter a PIREP.
ACFT: displays the FAA JO7360.1E Aircraft Type Designators.
RELIEF: displays a position relief checklist.
AFLD: allows the CIC to set airfield parameters.
TMU: allows entry of traffic management information.
EMER: displays an emergency checklist.
HELP: launches the help information you are reading.

vIDS is currently in development. If you notice a bug, please file a bug report.

If you have additional questions or would like to interact with the development team, feel free to join us on Discord.

Overview

vIDS is a collaboration and information sharing tool. Data entered on your display will populate on the displays of all other users logged in within 15 seconds. Any user that did not make the change will see a change advisory with the updated item highlighted in red and a button asking the user to acknowledge the change. Although all users logged into the system can make changes to the data in vIDS, only the facility CIC should make changes.

The vIDS system contains multiple display formats, some of which are user-customizable. Critical data is automatically-shared between the different display elements (for example, the A80 display uses live data elements from the ATL local display). Because of this feature, all users benefit from the same data despite viewing different displays.

The A80 display

A80 view is optimized for use by controllers working the A80 Atlanta Large TRACON. The countdown in the upper right corner displays the remainder of the 15-second auto-refresh interval. When this count expires, the system pulls the most current data from sync files and the VATSIM network and refreshes all data on the user's display. Clicking the "refresh" button in your web browser will not speed this process up, as the network limits pulls to 15 seconds in order to manage traffic. Please allow the page to auto-refresh.

The top line of the grid displays the current ATIS code (or -- if no ATIS), the current METAR, direction of traffic flow, and critical departure and arrival information. The next set of grids display controller combinations - the position is in static text in the top row followed by the controller that the position is combined to in a drop-down menu in the second row. The departure positions also contain a box for the display of departure gates underneath the controller combinations. Clicking on these boxes allows entry of assigned departure gates.

Located to the right of the controller position combinations, there are display areas for the current airfield configuration and traffic management information. This data can be entered using menus launched via the AFLD and TMU buttons below. At the bottom of the grid, there are display boxes for pilot weather reports (PIREPs) and controller-in-charge (CIC) messages. Similar to the previous displays, this information can be changed through use of the PIREP and AFLD buttons below.

Satellites & outer fields

Below the PIREPs and CIC notices, there is a display containing information for the A80 satellite and outer fields. Each section contains normal tower operating hours, the ATIS code, open/closed status, active runways, and the current METAR. If a local controller is staffing one of these fields, all information will be displayed. If no local controller is online and no ATIS is posted, the field will show "closed" and most of the information will appear as double-dashes.

Menu buttons

At the bottom of the grid, there is a row of buttons that each launch a unique pop-up with additional information or settings.

HOME: return to landing menu. Also used to submit a bug report.
WX: button displays local ATL METAR, TAF, and NEXRAD.
RECAT: displays the current consolidated wake turbulence guidance.
FREQS: displays the facility frequency map.
ARSPC: depiction of facility/position airspace.
ROTG: shows the current RNAV-off-the-ground cheat sheet.
SOP: launches the facility SOP.
LOA: displays applicable LOAs.
PIREP: allows a controller to enter a PIREP.
ACFT: displays the FAA JO7360.1E Aircraft Type Designators.
RELIEF: displays a position relief checklist.
CIC: allows the CIC to enter notes to controllers.
TMU: allows entry of traffic management information.
EMER: displays an emergency checklist.
HELP: launches the help information you are reading.

vIDS is currently in development. If you notice a bug, please file a bug report.

If you have additional questions or would like to interact with the development team, feel free to join us on Discord.

Overview

vIDS is a collaboration and information sharing tool. Data entered on your display will populate on the displays of all other users logged in within 15 seconds. Any user that did not make the change will see a change advisory with the updated item highlighted in red and a button asking the user to acknowledge the change. Although all users logged into the system can make changes to the data in vIDS, only the facility CIC should make changes.

The vIDS system contains multiple display formats, some of which are user-customizable. Critical data is automatically-shared between the different display elements (for example, the A80 display uses live data elements from the ATL local display). Because of this feature, all users benefit from the same data despite viewing different displays.

Multi-airfield TRACON/ARTCC display

Multi-airfield view is optimized for use by controllers that require situational awareness of multiple airfields (typically, TRACON and ARTCC). Approximately every 15 seconds, the system pulls the most current data from sync files and the VATSIM network and refreshes all data on the user's display. Clicking the "refresh" button in your web browser will not speed this process up, as the network limits pulls to 15 seconds in order to manage traffic. Please allow the page to auto-refresh.

Templates

Users have the option to select a pre-built template or create a custom template. Templates consist of a list of airfields that the user wants vIDS to display. On most display devices, vIDS will show 6 airfields without the need to scroll. To create a new template list of airfields, click on the TRACON/ARTCC IDS button and use the drop-down to select "Create Template." Enter a name for the template (ex. June FNO). Enter ICAO airfield IDs (ex. KATL), click Add, and then use the controls to order the airfields in your desired display sequence. Click Save. Your template is now available for your use and any other user.

Airfield grid

After selecting or creating a template, you will see a grid of airfields and associated data. Each airfield is displayed in a similar format for ease of use. The 3-letter FAA ID is displayed vertically on the left side to identify the airfield. Next, the ATIS code is displayed when an ATIS is active for the airfield. If ATIS is offline, double-dashes are displayed. The advertized approach type is displayed in yellow directly above the reported winds and altimeter setting in green. The middle of the display contains the most current METAR in white text. On the far right, the active runway visual range (RVR) is displayed, where available. This display was created to closely replicate what is used in a real TRACON facility.

vIDS is currently in development. If you notice a bug, please file a bug report.

If you have additional questions or would like to interact with the development team, feel free to join us on Discord.

Use the controls below to configure the runway departure split. Checkboxes turn on/off departure gates. Text boxes can be used to enter SIDs/RNAV fixes.

Information We Collect

To help enhance the virtual air traffic control experience, we collect information across a series of products and services all to enhance the end user's experience. We collect information in the following ways:

Information you give us. When you register an account with VATSIM and use that account to sign-in on vIDS, information that is generally considered personal is given to us from you and VATSIM to include, but is not limited to: your name and email address.
Information we get from you. Some other information is passed by your computer or electronic device, web browser, and VATSIM client. Information can include: your IP address, web browser type and version, device specific information (such as operating system, unique device identifiers and mobile network information). This information may be linked to your account.
Log Information. Each time you perform an action on vIDS, your action is logged. Information logged can include: type of action, data being sent and received, IP address the request originated from, software used to make the request, identification cookies, and the results of the request.
Location Information. Your location information may be associated with each request through geolocation against the originating IP address, information given to us by you or given to us by you through VATSIM.
Storage Location. Data is stored and encrypted on services owned or leased by vIDS within the United States.

Information Usage

To help enhance the virtual air traffic control experience, we collect information across a series of products and services all to enhance the user experience.
We use the information collected to provide, maintain, protect and improve our services.
The information we collect is maintained with confidentiality to the extent possible. The following information is shared with vIDS associated facilities:

VATSIM CERT Identification Number (CID)
Your name
Your VATSIM achievements and ratings
Your VATSIM associated email address
ARTCC facility associations, VATSIM region and division associations

vIDS does not make any personal information available to the public, however the following information may be seen by users logged into the system:

VATSIM CERT Identification Number (CID)
Your name
ARTCC staff associations and ARTCC staff email addresses
ARTCC facility associations, VATSIM region and division associations
VATSIM achievements and ratings

The following information is collected and may be used to protect our services, up to and including cooperation with legal requests for information from law enforcement agencies:

The above listed public information,
All IP addresses used and associated with your account
Geolocation against aforementioned IP addresses
Activities performed with vIDS web services

We may store identification tokens and other limited information on your electronic device through web storage or cookie usage.

Who We Share With

The information we collect may be shared, in limited capacities, with the following:

Virtual Air Traffic Simulation Network (www.vatsim.net)
VATUSA (www.vatusa.net)
Other Virtual ARTCC partners
Law enforcement agencies

For more information on what is shared with whom, please see "Information Usage".

Cookie Usage

We use various technologies to collect and store information when you visit and use a vIDS service. This may include a cookie or other similar technologies to identify your browser or device.
Our cookies are mainly used as a means of tracking virtual users across vIDS services. This allows us to know who is requesting and using our services, provide authentication and authorization checks to restricted areas.
You may choose to disable cookie usage via your browser, but know that doing so will prevent access and use across restricted areas of the website and severely degrade your experience.

Opt Out

Given the nature of our services, it is not possible to opt out of data collection and use our services. But if you desire to opt out and no longer desire to use our services, we will purge all information we have collected upon written request.
The first step is to deactivate and request VATSIM to purge your data. Please head to https://membership.vatsim.net to do so.
After VATSIM has purged your data, please send a written request to your virtual ARTCC's Air Traffic Manager via email. It is a manual process, so please allow up to 30 days for information to be purged. You will receive an email response once the data has been purged.
Note vIDS cannot guarantee that information collected by parties outside of vIDS will be purged in the process.

Disclaimer!

All information on this website is for flight simulation use only and is not to be used for real world navigation or flight. This site is not affiliated with ICAO, the FAA, any actual ARTCC, or any other real world aerospace entity.

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

Please wait... vIDS can take up to 15 seconds to initialize

ZTL vIDS - Virtual Information Display System

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

Please wait... vIDS can take up to 15 seconds to initialize

Controller tools

A80 top-down

ZTL vIDS - Virtual Information Display System

RECAT

SOP

SOP

LOA

LOA

Aircraft Types

ATL Weather & Forecast

ATL Terminal Wx

ZTL Pre-Duty Video Wx Brief

A80 Convective Gates

ZTL Weather Radar

ZTL Weather Satellite

ATL RVR

ZTL Active SIGMETs

National Prognostic Chart

ATL Tower Frequency List

Clearance Delivery

Ground Control

Local Control

A80 Facility Frequency List

Terminal Arrival Radar (TAR)

Arrival Radar (AR)

Departure Radar (DR)

Satellite (SAT)

Outer Sectors

ATL Tower Airspace

ATL East Ops

ATL West Ops

A80 Airspace Diagrams

ATL Class B

A80 TAR East Ops

A80 TAR West Ops

A80 AR Final East Ops

A80 AR Final West Ops

A80 DR Duals East Ops

A80 DR Trips East Ops

A80 DR Duals West Ops

A80 DR Trips West Ops

A80 Satellite East Ops

A80 Satellite West Ops

A80 PDK Final (SAT-Q)

A80 Macon Sector

A80 Columbus Sector

A80 Athens Sector

RNAV Off The Ground

Relief Briefings

Appendix H-1: Flight Data/Clearance Delivery Checklist:

Appendix H-2: Ground & Local Control Checklist:

Appendix H-2: Ground & Local Control Checklist:

Relief Briefings

3-1. Position Relief Briefing for DR

3-2. Position Relief Briefing for SAT-P/F/G-X

3-3. Position Relief Briefing for TAR

3-4. Position Relief Briefing for AR

3-5. Position Relief Briefing for CSG/MCN/SAT-E

Emergency Procedures

ATL Airfield Config

Add Pilot Weather Report (PIREP)

TMU Information

A80 CIC Information

vIDS Help - Local Display

Overview

The local display

Menu buttons

vIDS Help - TRACON Display

Overview

The A80 display

Satellites & outer fields

Menu buttons

vIDS Help - Multi-Airfield

Overview

Multi-airfield TRACON/ARTCC display

Templates

Airfield grid

Assign A80 Departure Gates

Configure Runway Departure Split

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--

	N1	N2	W2	W1	S2	S1	E1	E2
--
--