This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ivac2:manual:workflows:sectors [2014/05/12 16:58] splendor.bouman added IvAc2.0 detail |
ivac2:manual:workflows:sectors [2017/04/08 14:27] (current) |
||
|---|---|---|---|
| Line 50: | Line 50: | ||
| ====== IvAc2 - later stage ====== | ====== IvAc2 - later stage ====== | ||
| - | At a later stage the same upstream/downsteam logic will apply however it will be | + | At a later stage the same upstream/downsteam logic will apply however it will be server based and there will be a degree of flexibility in the choice of assumed sectors. |
| + | |||
| + | The user will connect as a console using VID and will then have a list of sectors to choose from. Some sectors will be automatically combined, others would be an option. | ||
| + | |||
| + | ^Selected sector|TC LAM||| | ||
| + | ^Auto combine|TC BNN|TC BIG|TC OCK| | ||
| + | ^Optional combine|EGLL|EGSS|EGKK| | ||
| + | The EGLL, EGSS & EGKK groups would be shortcuts to the top level sector in each unit and would assume all auto-combine sectors linked within. | ||
| + | |||
| + | |||
| + | Combined sectors will remain visible and appear online as separate sectors however the communication and co-ordination will be linked back to the primary sector. | ||
| + | |||
| + | Example: | ||
| + | ^Only TC LAM sector online^^ | ||
| + | ^Visible Sector^Remarks^ | ||
| + | |TC LAM|Frequency: 118.825| | ||
| + | |TC BNN|Frequency: 119.775| | ||
| + | |TC BIG|Frequency: 120.525| | ||
| + | |TC OCK|Frequency: 134.125| | ||
| + | |||
| + | All communications are routed to the console (VID) of the user. Sectors can be added and removed without reconnecting and if a second controller takes over, for example **TC OCK** all aircraft on frequency 134.125 and all co-ordination to **TC OCK** will be routed to the new controller. The reverse happens when a sector is combined into another sector. | ||