This is an old revision of the document!
Sectors are not recognised.
The user is presented with a list of sectors, for example the London TMA
Sector ID | FSD login | Remarks |
---|---|---|
TC LAM | EGTL_NE_CTR | Lambourne / NE DEPS |
TC BNN | EGTL_NW_CTR | Bovingdon / NW DEPS |
TC BIG | EGTL_SE_CTR | Biggin |
TC OCK | EGTL_SW_CTR | Ockham / SW DEPS |
Each sector is assigned an upstream sector, for example:
Sector | TC LAM | TC BNN | TC BIG | TC OCK |
---|---|---|---|---|
Upstream Sector | — | TC LAM | TC OCK | TC LAM |
This signifies that TC LAM is considered the master sector in the TC group. If a controller logs on as TC LAM and no other sector is online, IvAc will forward co-ordination for all TC sectors to TC LAM and the TC LAM sector will be displayed to other controllers instead of the geographically correct sector.
Co-ordination example:
All sectors online | |||
---|---|---|---|
FROM sector | TO sector | Sector & frequency displayed | |
EGTT S20 | TC BIG | TC BIG - 120.525 | The correct sector defined in the LOA is displayed |
Only TC LAM sector online | |||
FROM sector | TO sector | Sector & frequency displayed | |
EGTT S20 | TC BIG | TC LAM - 118.825 | As TC BIG and TC OCK are offline the next available sector is displayed |
This logic applies to all positions provided there is an upstream sector defined. There is no direct user control over which downstream sectors are assumed, so if a controller connects as TC LAM all downstream stations will automatically be assumed. In this practical case with no other controller online it would be:
Sector ID | FSD login | Remark |
---|---|---|
TC BNN | EGTL_NW_CTR | Bovingdon / NW DEPS |
TC BIG | EGTL_SE_CTR | Biggin |
TC OCK | EGTL_SW_CTR | Ockham / SW DEPS |
LL INT-N | EGLL_N_APP | Heathrow INT North |
LL INT-S | EGLL_S_APP | Heathrow INT South |
LL FIN | EGLL_F_APP | Heathrow FIN |
LL AIR-N | EGLL_N_TWR | Heathrow AIR North |
LL AIR-S | EGLL_S_TWR | Heathrow AIR South |
LL GMC-N | EGLL_N_GND | Heathrow GMC North |
LL GMC-S | EGLL_S_GND | Heathrow GMC South |
LL GMC-W | EGLL_W_GND | Heathrow GMC West |
LL GMP | EGLL_DEL | Heathrow GMP |
etc. etc. etc. |
If, for example a controller would connect as LL-GMC-N the next sector for all departures would automatically be TC LAM and vice versa.
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.
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.