-
Notifications
You must be signed in to change notification settings - Fork 19
Dashboard Documentation
Airports can be:
- Added:
- Modified:
- Deleted:
Each airport has:
-
ICAO: Non-editable field (Main key to identify the airport).
-
Base Rate: Default Arrival Rate (per hour).
-
TAXITIME: Default Taxi Time used when no CDM System Active.
-
CDM airport: This enables or disables the CDM field in the pilot's VDGS Panel (CDM: TSAT and TOBT, non-CDM: EOBT).
-
Report ready at TOBT: This enabled a new handling in the VDGS Panel which advises pilots to report ready for start-up earlier than TOBT+5 and thereafter TSAT is used as a reference.
-
When ASRT set, disable VDGS updates: Edit TOBT and relevant actions to modify TOBT are disabled in the VDGS panel after ASRT being set for the airports with this checkbox checked.
-
Progressive Regulate: By enabling this functionallity, ETFMS system will start regulating at 80% of the maximum capacity at the destination airport. This will create a progressive delay for the affetcted flights.
-
Regulate Threshold: Percentage to define when the airport should start to regulate. It will be regulating with a delay 0 CTOT until the maximum capacity is exceed (Or in case "Progressive Regulate" is enabled, at 80% will start to delay) - Default is 100% (not regulating until 100%).
-
Use ATIS Config: Enables/Disables to be used the ATIS config.
-
Keep latest ATIS Config: Maintain latest known configuration from ATIS after the ATIS/ATC is disconnected.
-
Selected Config: Selection of which configuration to be used (based on CAD config). Note: If designator is selected, the system will only look for the procedures for the specified runway (This means, that requires to setup correctly the procedures.txt).
-
Latest ATIS Config: Displays latest provided VIFF config from ATIS (to be used, "Use ATIS config" must be enabled).
Additional remarks:
- ICAO can have exception LE** to define a default taxiTime and/or arrival rate for all LE starting airports (If not defined by the complete ICAO code).
After each modification, we should:
![]()
We can delete the airport by pressing:
![]()
To create restrictions, we can use the lower part of the dialog:

We can enter the following values:
- Capacity: Rate to be used (per hour).
- Reason: Reason to create a restriction.
- Type: ARR for arrival rate or DEP for departure rate (Departure rate is only relevant to change the CDM rate if CDM Plugin in use).
- Runway: Set runway to apply the departure rate (If applicable, empty is ALL runways). It will sync directy with CDM Plugin (Starting with 2.2.8.26)
- Restriction ID: By default ICAO + day + 2 letters. Can be modified if required.
- Start time: Start of the regulation (max 5h between start and end).
- End time: End of the regulation (max 5h between start and end).
- Delete after 24h: The restriction will be automatically removed after 24h of creation. In not checked, needs to be manually removed after application.
When finished, press:
Traffic Volumes are seperated by:
- Activated: Traffic Volume is Activated and regulating.
- Disabled: Traffic Volume is disabled, can be monitored and ready to be activated at any moment. Therefore, is not regulating.
- Invisible: Traffic Volume is completely disabled and can't be monitored. To be used when TV not planned to be used in long term.
Additional remarks:
- When Disabled Traffic Volumes have restrictions, are considered as ACTIVE during the restriction applicable period.
- When planning to move a TV from Invisible to Active, set it the day before to allow some time to fetch all traffic.
Create or edit a new TV:
- ID: Identification of the Traffic Volume. Must be unique and starting with 2 letters of your FIR. Example LE-TEST
- Notes: Additional Information for your own clarifications. Generally for explanation of what the TV covers or its activation.
- Status: Status to be set (Active/Disabled/Invisible).
- Progressive Regulate: By enabling this functionallity, ETFMS system will start regulating at 80% of the maximum capacity at the selected Traffic Volume. This will create a progressive delay for the affetcted flights.
- Regulate Threshold: Percentage to define when the Traffic Volume should start to regulate. It will be regulating with a delay 0 CTOT until the maximum capacity is exceed (Or in case "Progressive Regulate" is enabled, at 80% will start to delay) - Default is 100% (not regulating until 100%).
- Entries: Default threshold of Entries per hour in the Traffic Volume.
- Occupancy: Default threshold of Flights at the same time in the Traffic Volume.
- Departure Airports:
- ALL: Flights departing from any airport and crossing this Traffic Volume will be included in this TV.
- NONE: Same as "not-applicable".
- Airports: Select specific airports where planes can depart to be included.
- Arrival Airports:
- ALL: Flights arriving to any airport and crossing this Traffic Volume will be included in this TV.
- NONE: Same as "not-applicable".
- Airports: Select specific airports where planes can arrive to be included.
- No Departure airports:
- NOT APPLICABLE: Filter is not applicable.
- Airports: Select specific airports where planes can NOT depart to be included.
- No Arrival airports:
- NOT APPLICABLE: Filter is not applicable.
- Airports: Select specific airports where planes can NOT arrive to be included.
- Airblocks: Selected Airblocks that compose the Traffic Volume (Can be seen in the right side map for further reference).
When finished, press the lower button to Save:
By selecting several Traffic Volumes, a new TV can be created:

An scenario requires the following values:
- Scenario ID: Identification of the Scenario. Must be unique and starting with 2 letters of your FIR. Example LE-SCE1
- Time Frames: Selection of days and time-frames for the activation of the scenario. Several periods can be created. (To create a simple non-recurrent interval, times can be set without the selection of days)
- Positions (MUST): All the positions here MUST be booked to automatically activate the scenario based on the official VATSIM booking system.
- Positions (ONE OR MORE): One or more positions here should be booked to automatically activate the scenario based on the official VATSIM booking system.
- NO Positions (MUST NOT): All the positions here MUST NOT be booked to automatically activate the scenario based on the official VATSIM booking system.
- Use bookable positions: Bookable positions functionallity enabled/disabled.
- Description: Internal description of what the Scenario does or other relevant notes/remarks.
- Traffic Volumes:
- Check the required Traffic Volumes to be used for the scenario with the left checkbox.
- Set required Entries/Occupancy capacities values or disable them.
- Airports:
- Add scenarios with they required ICAO, Type, Runway (If applicable, empty is ALL) and capacity.
When finished, Save the scenario by pressing: