652
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
m
Stand Alone ATC Control Development (view source)
Revision as of 04:49, 27 September 2010
, 27 September 2010beauty job
m (Major add by user -- must be revisited the next days by me jomo) |
m (beauty job) |
||
| Line 15: | Line 15: | ||
*operated by highly educated and paid professionals | *operated by highly educated and paid professionals | ||
*ATC must be able to handle 100 targets an hour | *ATC must be able to handle 100 targets an hour | ||
* | *customers are Pilots with valid Pilot-licenses, approved by government authorities | ||
*is highly specialized for unique jobs, like Center, APR, TWR, GND, Planning | *is highly specialized for unique jobs, like Center, APR, TWR, GND, Planning | ||
*unique positions at big airports may be executed in parallel by multiple ATC,s (i.e. one Airport, several TWR- and several APR- and several GND-ATCs) | *unique positions at big airports may be executed in parallel by multiple ATC,s (i.e. one Airport, several TWR- and several APR- and several GND-ATCs) | ||
| Line 28: | Line 28: | ||
*uses only black-radar screens (but suggests to use additional Map-overview screens) | *uses only black-radar screens (but suggests to use additional Map-overview screens) | ||
*uses different Radar-images per ATC-function (CTR, APR, TWR, GND) | *uses different Radar-images per ATC-function (CTR, APR, TWR, GND) | ||
* | *communication is based on a very useful, complex Radio-operation via a complex switchboard | ||
*can also use predefined text-messages per number-code-selection (difficult to memorize) | *can also use predefined text-messages per number-code-selection (difficult to memorize) | ||
*uses own central Servers to control who may do what | *uses own central Servers to control who may do what | ||
| Line 43: | Line 43: | ||
**but also may discourage potential customers! | **but also may discourage potential customers! | ||
*there is no possibility to enforce any code of conduct and/or skills, neither for pilots nor for ATC | *there is no possibility to enforce any code of conduct and/or skills, neither for pilots nor for ATC | ||
*is mostly used by casual "just passing by pilots" or preplanned MP-events (e.g. TGA or Virtual-Airlines) | *is mostly used by casual "just passing by pilots" or preplanned MP-events (e.g. TGA or Virtual-Airlines) | ||
*does not require nor can handle flight-plans | *does not require nor can handle flight-plans | ||
*Acceptability/Usage by pilots still very poor (based on amount of all MP-users) | *Acceptability/Usage by pilots still very poor (based on amount of all MP-users) | ||
* | *'''needs "low skill borders" to achieve increased acceptability | ||
''' | ''' | ||
==Proposed Positioning for FGFS-ATC== | ==Proposed Positioning for FGFS-ATC== | ||
*'''make FGFS-ATC to a very popular | *'''make FGFS-ATC to a very popular ATC-tool also for beginners''' | ||
*do not try to compete with VATSIM, we do not have and will never have enough trained ATCs nor enough trained and/or willing pilots | *do not try to compete with VATSIM, we do not have and will never have enough trained ATCs nor enough trained and/or willing pilots | ||
*keep FGFS and FGFS-ATC open for all: From "Kids-Stuff" over "Flying just for fun" up to "highly professional training" | *keep FGFS and FGFS-ATC open for all: From "Kids-Stuff" over "Flying just for fun" up to "highly professional training" | ||
| Line 57: | Line 56: | ||
**offer them opportunities to develop "controlled flying skills" in stages: | **offer them opportunities to develop "controlled flying skills" in stages: | ||
***learn to watch/control altitude, heading, speed, etc. by advise and supervising | ***learn to watch/control altitude, heading, speed, etc. by advise and supervising | ||
***learn | ***learn to plan flights (e.g. not to arrive at 20.000 ft over the destination-airport) | ||
***communication with ATC (in English!) | ***communication with ATC (in English!) | ||
*enable | *enable use of VATSIM for "totally planed and controlled flights" | ||
=Minimum set of required features= | =Minimum set of required features= | ||
| Line 67: | Line 64: | ||
* display a radar-like screen | * display a radar-like screen | ||
* display data tags (altitude, callsign, course, sqwk code etc) | * display data tags (altitude, callsign, course, sqwk code etc) | ||
<br> | |||
=Features to be provided by the future Full-Screen FGFS-ATC= | =Features to be provided by the future Full-Screen FGFS-ATC= | ||
The following "wanted features" may become prioritized together with the designers, based on available resources: | The following "wanted features" may become prioritized together with the designers, based on available resources: | ||
==The Radar== | ==The Radar== | ||
*must show the target and navigation data | *must show the target and navigation data in an easy and quick to read fashion (e.g.: colored labels on Black) | ||
*must show the terrain (water, land, hills, mountains) in color (like e.g. MPmap or ATLAS) . The terrain does not need to be very detailed but should indicate when ground-altitude raises above pattern altitude | *must show the terrain (water, land, hills, mountains) in color (like e.g. MPmap or ATLAS). The terrain does not need to be very detailed but should indicate when ground-altitude raises above pattern altitude | ||
It may be difficult to find a “perfect match” of above 2 items, | It may be difficult to find a “perfect match” of above 2 items, | ||
so we need a button to switch between different backgrounds: “Simple Black” or “scenery ” | so we need a button to switch between different backgrounds: “Simple Black” or “scenery ” | ||
and the targets and navigation-labels must be on an extra layer – thus they remain the same on both backgrounds. | and the targets and navigation-labels must be on an extra layer – thus they remain the same on both backgrounds. | ||
* | *Target-Labels MUST NOT just use black boxes underlying the text (as e.g. in MPmap) - that gets very unreadable when many labels (target and/or navigation) overlay each other. | ||
*The Radar range must be (at least) 100 mi (like MPmap and FGCOM) and easily zoomed | *The Radar range must be (at least) 100 mi (like MPmap and FGCOM) and easily zoomed | ||
even on a Full-Screen application there must be a centered compass-scale in the background | *even on a Full-Screen application there must be a centered compass-scale in the background | ||
==Target-Infos== | ==Target-Infos== | ||
| Line 86: | Line 84: | ||
**Selecting a target out of the scope should be possible – but first priority would be the next item: | **Selecting a target out of the scope should be possible – but first priority would be the next item: | ||
*on an additional GUI-list must be listed all targets, including: (compare now ATC-ML) | *on an additional GUI-list must be listed all targets, including: (compare now ATC-ML) | ||
**call-sign of target | **'''call-sign''' of target | ||
**distance from airport | **'''distance''' from airport | ||
**altitude of target | **'''altitude''' of target | ||
**speed (may be selectable between TAS and IAS – otherwise pilots get blamed if ATC advises a speed that | **'''speed''' ''(may be selectable between TAS and IAS – otherwise pilots get blamed if ATC advises a speed that is shown different to pilot and ATC)'' | ||
**heading of target | **'''heading''' of target | ||
**Model | **'''Model''' | ||
**planned destination: An empty field for ATC to insert either: direction (N,E,S,W), SID/STAR, Pattern, ICAO, or similar) | **'''planned destination''': An empty field for ATC to insert either: direction (N,E,S,W), SID/STAR, Pattern, ICAO, or similar) | ||
** | **'''flying-modus''': May be a pull-down to select: IFR, VFR, SID/STAR, Uncontrolled | ||
:'''the last two items acting as a very minimized flight/handling-plan for ATC purposes''' | |||
*that list must display all targets inside todays MPchat/FGCOM reach: 100 mi – independent of RADAR zoom settings! | *that list must display all targets inside todays MPchat/FGCOM reach: 100 mi – independent of RADAR zoom settings! | ||
*the listing should be sortable by distance (e.g. nearest has highest priority during APR) and call-sign (e.g. for easy finding) | *the listing should be sortable by distance ''(e.g. nearest has highest priority during APR)'' and call-sign ''(e.g. for easy finding)'' | ||
*that GUI-list should be able to be moved outside the Scope – better even onto anther screen or even PC | *that GUI-list should be able to be moved outside the Scope – better even onto anther screen or even PC | ||
*ATC must be able to mark the lines according to who controls: CTR, APR, TWR, GND, not yet assigned, control rejected (either by pilot or ATC) | *ATC must be able to mark the lines according to who controls: CTR, APR, TWR, GND, not yet assigned, control rejected (either by pilot or ATC), especial needed if several ATC's work together (e.g. APT and TWR) | ||
**do not delete unwanted targets from list – otherwise ATC might search and search for targets | **do not delete unwanted targets from list – otherwise ATC might search and search for targets that call in and are visible for others – but are not on ATC-Radar | ||
**on the reverse provide possibility to address a plane not shown in the ATC-MPserver (e.g. todays problem with overloaded MPserver02) | **on the reverse provide a possibility to address a plane not shown in the ATC-MPserver (e.g. todays problem with overloaded MPserver02) | ||
*All that added data should be buffered to be recalled in case the Target jumps in/out of Radar-List (may be pilot uses “p” (pause), MP-delays, restart because of crash (ATC or target), etc) | *All that added data should be buffered to be recalled in case the Target jumps in/out of Radar-List (may be pilot uses “p” (pause), MP-delays, restart because of crash (ATC or target), etc) | ||
| Line 106: | Line 104: | ||
on radar must be shown the type, ID, frequency (similar to MPmap – but again not with labels inside black boxes) | on radar must be shown the type, ID, frequency (similar to MPmap – but again not with labels inside black boxes) | ||
*if all of them are displayed all the time – we might not be able to see any more what we want to see → that is one reason why VATSIM uses different images for their radar! Try VATSAM-radar on image “Tower” and zoom out (e.g. "Central") – and try to pick any Fixpoint! | *if all of them are displayed all the time – we might not be able to see any more what we want to see → that is one reason why VATSIM uses different images for their radar! Try VATSAM-radar on image “Tower” and zoom out (e.g. "Central") – and try to pick any Fixpoint! | ||
*So ATC needs to define which ones he/she needs for the planned job and only | *So ATC needs to define which ones he/she needs for the planned job and only place those onto the scope. That could be done in 2 ways: | ||
##either by manually typing in the NAV-IDs one by one that ATC wants/needs (similar like in todays MPmap) | |||
##or show all available ID's (on scope or GUI) and let ATC select the ones to be removed | |||
: | : #2 being faster and easer to use by ATC and thus preferred | ||
*The Nav-points must not be selected at each startup again and again - but may be saved by ATC for different jobs and or different locations under different conditions (e.g. approaches for wind from west or east, etc.) | *The Nav-points must not be selected at each startup again and again - but may be saved by ATC for different jobs and or different locations under different conditions (e.g. approaches for wind from west or east, etc.) | ||
** | **Airways do not need to be shown because they are usually not controlled by FGFS-ATC – they should remain the pilots-responsibility. | ||
*All settings should be saved in a file to be called up on request. It can be a real pain if the ATC-PC crashes and after reboot the ATC has to remember and reconfigure certain settings under stress. Those settings are also very nice for e.g. ATC "jumping to different airports" in between. e.g. during MP events – he then could just very fast load different “settings”! We should try to reduce the amount of ATC's needed and rather have more pilots participating and thus giving the ATC something to do! | *All settings should be saved in a file to be called up on request. It can be a real pain if the ATC-PC crashes and after reboot the ATC has to remember and reconfigure certain settings under stress. Those settings are also very nice for e.g. ATC "jumping to different airports" in between. e.g. during MP events – he then could just very fast load different “settings”! We should try to reduce the amount of ATC's needed and rather have more pilots participating and thus giving the ATC something to do! | ||