Table of Contents

IvAc1

Sectors are not recognised.

IvAc2 - first stage

The user is presented with a list of sectors, for example the London TMA

Sector IDFSD loginRemarks
TC LAMEGTL_NE_CTRLambourne / NE DEPS
TC BNNEGTL_NW_CTRBovingdon / NW DEPS
TC BIGEGTL_SE_CTRBiggin
TC OCKEGTL_SW_CTROckham / SW DEPS

Each sector is assigned an upstream sector, for example:

SectorTC LAMTC BNNTC BIGTC OCK
Upstream SectorTC LAMTC OCKTC 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 sectorTO sectorSector & frequency displayed
EGTT S20TC BIGTC BIG - 120.525The correct sector defined in the LOA is displayed
Only TC LAM sector online
FROM sectorTO sectorSector & frequency displayed
EGTT S20TC BIGTC LAM - 118.825As 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 IDFSD loginRemark
TC BNNEGTL_NW_CTRBovingdon / NW DEPS
TC BIGEGTL_SE_CTRBiggin
TC OCKEGTL_SW_CTROckham / SW DEPS
LL INT-NEGLL_N_APPHeathrow INT North
LL INT-SEGLL_S_APPHeathrow INT South
LL FINEGLL_F_APPHeathrow FIN
LL AIR-NEGLL_N_TWRHeathrow AIR North
LL AIR-SEGLL_S_TWRHeathrow AIR South
LL GMC-NEGLL_N_GNDHeathrow GMC North
LL GMC-SEGLL_S_GNDHeathrow GMC South
LL GMC-WEGLL_W_GNDHeathrow GMC West
LL GMPEGLL_DELHeathrow 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.

IvAc2 - later stage

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 sectorTC LAM
Auto combineTC BNNTC BIGTC OCK
Optional combineEGLLEGSSEGKK

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 SectorRemarks
TC LAMFrequency: 118.825
TC BNNFrequency: 119.775
TC BIGFrequency: 120.525
TC OCKFrequency: 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.