99 replies to this topic

[Matthew Hardman]

Thanks Dave

[Matthew Hardman]

Stansted, Luton, Cambridge and Cranfield Panel - NOTE - EGSC corrected now to be Radar and Director

Attached Files

•  SS GW SC TC.PNG   141.84K   63 downloads

Edited by Matthew Hardman, 05 February 2012 - 11:20 PM.

[Harry Williams VATUK9]

Looks fantastic Matt!

Thanks for the work you've put in so far.

[Oliver Parker]

Keep going Matt, nearly there!x

[Matthew Hardman]

Deleted due later post...

Edited by Matthew Hardman, 21 February 2012 - 02:12 PM.

[Chris Pawley]

Quick suggestion. On the 123.900 panel - change EURI, KOK and EBBU_W around - so they are top to bottom as the sectors appear geographically.

Thankies :)

C

[Matthew Hardman]

Hi Chris

Thanks for the suggestion. What I had done is try to put the new MAAS sectors next to our high level LACC sectors (so DELTA next to CLN and KOKSY next to DVR) and the low level EHAA/EBBU next to our low level TC sectors (so EHAA next to TC-NE and EBBU next to TC-SE) and the EURI was just fitted in where it could.

If people think it would work better your way then I will swap it around.

Opinions on a postcard please!

For info - this was just a first iteration of the area panel for 123.9. I foresee quite a lot of switching around.

Another question... for 123.9, would it be better to have these area positions on the default INT COM panel like we have on this picture, or would it be better to have the main approach and delivery positions here and the area ones on one of the DA panels? I was thinking that if you were controlling 123.9 it is more likely that you will need to call APP etc than other area sectors. Thoughts again please.

[Adam Arkley]

I'm in two minds, Matt. I tend to co-ordinate quite a lot with other sectors for shortcuts or aircraft that wont meet agreements or any number of things. On the other hand, like you say, co-ordination with approach is (more) frequent and also needs considering.

What I would say (to throw a spanner in the works) is that I tend rarely to co-ordinate with external facilities, especially with GVCCS. Is it plausible to remove the external positions and add the approach positions to have both on the same page?

Thanks,
Adam

[Matthew Hardman]

Plausible yes... realistic, not sure.

Each area panel set will have different characteristics because of the number of APP and AIR and GMP positions I need to fit in. So using the 123.9 example (the biggest obviously) I'm never going to fit all the aerodrome buttons on to the INT COM panel anyway.

I totally see what you are saying about the external facilities and I am interested in other peoples views. I put them in there in the hope that our neighbours will end up using GVCCS (certainly when the next, much more user friendly version goes public). At the moment we don't co-ordinate with external facilities much because they are not on TS and we can't be bothered on text (my opinion), but perhaps if we can convert them onto GVCCS this will change? Each a/c coming in or out of our FIR should technically be co-ordinated fully, but I do also understand that we have the ability to do that using ES's functions.

In short, I'm not sure and I'm open to debate about the area panels (and with all of them, of course). I like the idea of keeping the external facilities, partly because removing them will not add any benefit in terms of being able to fit all the APP, AIR and GMP facilities in anyway.

Discuss!

Edited by Matthew Hardman, 06 February 2012 - 03:27 PM.

[Adam Arkley]

Matt,

Apologies, my previous post was short and almost ambigious; I had meant that only the Major APP positions would be available; Heathrow, Gatwick, Essex, Cardiff, Manchester, Liverpool.

[Matthew Hardman]

I knew what you were getting at.

I am not yet onto the area panels proper, so we will see how it goes when I get there.

For the time being, I will keep the external facilities (to avoid having to make them again later if opinions prove we want them!)

Thank you for your suggestion. Noted.

[Matthew Hardman]

The Aldergrove and Belfast City panel.

Again, I know very little about this area, so please give feedback.

Attached Files

•  AA AC.PNG   126.59K   21 downloads

Edited by Matthew Hardman, 15 February 2012 - 10:30 PM.

[Matthew Hardman]

Glasgow, Edinburgh, Prestwick, Aberdeen panel.

Again, I know little, so please do inform!

Attached Files

•  PF PH PK PD.PNG   109.15K   23 downloads

[Matthew Hardman]

A re-jigged LACC ALL (designed for LON_CTR 123.9)...

1) Swapped MACC EAST and LACC NORTH so that the two MACCs are together.
2) Swapped MAAS KOKSY and EBBU WEST so they imitate the Amsterdam and DELTA buttons above by being high level on top of low level.
3) Left EURO ISLES where it is due not having another suitable place without shifting other buttons from their most efficient spot.

All aerodrome panels are done now, so now on to the area panels! This one will have the major approach position(s), air position and position responsible for GMP for each aerodrome, in alphabetical order, on it's DA panels.

Edit.... deleted picture due next post...

Edited by Matthew Hardman, 21 February 2012 - 02:13 PM.

[Matthew Hardman]

Here is the full LACC ALL panel (designed for use by LON_CTR 123.900). All 4 panel subs are shown. The idea here is that every button that LON_CTR would need is available, i.e. they have a way of contacting approach, air and whoever is responsible for GMP (some places delivery, some places ground) but no other buttons (so for example, there are no buttons for Heathrow Ground, as they have no reason to ever want to contact them).

Attached Files

•  LACC ALL DA1.PNG   88.09K   66 downloads
•  LACC ALL INTCOM.PNG   84.68K   78 downloads
•  LACC ALL DA2.PNG   79.03K   66 downloads
•  LACC ALL DA3.PNG   85.15K   43 downloads

Edited by Matthew Hardman, 21 February 2012 - 02:17 PM.

[Johan Grauers]

Why does bb have gmc rather than gmp?

Otherwise it looks brilliant!

[Matthew Hardman]

That's my mistake. It will have a GMP :D

[Colin Holden]

looks alot better,

when this version out?

[Matthew Hardman]

These pictures are from the pack that will be released once the new GVCCS version is released (as yet in Beta testing and while away from release). They utilise a number of new functions that will become available with this new version and so are not compatible with the current public version of GVCCS.

Watch this space, but it will be a while! The idea of me making these well in advance is to have them well tested and consulted and immediately available upon public release of GVCCS 2.

[Matthew Hardman]

The LACC Clacton Panel...

Attached Files

•  CLNINTCOM.PNG   86.01K   35 downloads
•  CLNDA1.PNG   75.83K   35 downloads