Few points of clarification:
[!--quoteo--][div class=\\\'quotetop\\\']QUOTE [/div][div class=\\\'quotemain\\\'][!--quotec--]Just to note, the DD stepped up and refused to implement a part of the GRP that didn't affect VATUSA in any way whatsoever. And such was explained. That section of the GRP (5.3 for those tuning in for the first time) is worded especially for Divisions whose FIRs/ARTCCs have no websites. You'll notice the "Division/Facility" meaning one or the other. Thinking that every local policy needed to appear on the Division website was a misconception.[/quote]
GRP 5.3:
[!--quoteo--][div class=\\\'quotetop\\\']QUOTE [/div][div class=\\\'quotemain\\\'][!--quotec--]Notwithstanding paragraphs 5.1 and 5.2, it is acceptable for Divisions to introduce Standard Operating Procedures to provide guidance to Controllers in respect of local arrangements such as runway configurations, clearance altitudes, handoff procedures etc. Such SOPs must be approved by the Division Director and must be published on Division/Facility websites for all controllers and pilots to read.[/quote]
How the heck is one supposed to make the connection that if an ARTCC has no website, only their policies have to be approved by the Division Director? Posting it on a website was not the problem, having to review them all was the problem. And no, such was not explained.
What you said to me on 1/11/10 was:
[!--quoteo--][div class=\\\'quotetop\\\']QUOTE [/div][div class=\\\'quotemain\\\'][!--quotec--]"I'm in complete agreement that the ridiculousness has to stop somewhere. The amount of oversight is indeed ridiculous and your example just shows that. Why the hell should you care about runway selection and such? ha ha! That's why I "think" applies to local procedures in general, but who the hell knows.[/quote]
You gave me your personal interpretation that it did not apply, but then followed it with the above, so I asked for a formal answer and pointed out the problems with the system.......
Refusal to implement part of the GRP was based on 2 things:
1) I did not want to have to approve or force the staff to approve airspace procedures like runway configs, etc. I felt it was overkill and the ARTCCs were capable of doing that on their own. Call me crazy, but the GRP is clear on that point. The contention is now that "well that didn't really apply to VATUSA"........ but it is a Global Policy so how is a DD supposed to know what rules in a network wide policy apply and which ones don't.............
Bruce, your understanding of the issue was dead correct.
2) I did not feel that it was the USA Division's job to invent an arbitrary meeting for C3 which is a global rating and is supposed to transfer across divisions. It would not have the same meaning between divisions and I could not understand why the GRP would address all of the other ratings but make that one subjective. It is in my opinion, 100% wrong to take a situation that has been a problem since GRP1 and ignore it by pushing it off on the divisions where it could easily be turned into a boys club elitist rating.
I never received any official response to the refusal. I actually told members of the USA Staff that I expected to be fired for it, and should have been. I would have had a ton of respect for VATSIM if they had fired me because at least then there would have been some accountability.
There has also been a lot of talk about my access to the GRP forum. I did not have it, but it didn't matter. The revisions and drafts of the GRP were not being circulated in that forum anyway, so access to it would not have accomplished anything. We did not see any draft after 9/1/09 or the final GRP until the day it was released, so my refusal to implement those provisions was necessary due to the fact that there was no opportunity to interject input prior to its codification.
Gary is more right that you guys can imagine. Rules seem to keep being created in response to things that have gone awry in the past. Rather than deal with the problem head on, rules are created to outlaw the problem. Thing is, no matter what the intent of the GRP is, the end result is more bureaucracy and administrative overhead. More webpages to develop, procedures to approve, tests to rewrite, blah blah blah. That was a big concern to me with any policy, "How much does this affect downstream workload?" For instance...GRP requires written exam AND OTS for every rating. Ok Fine. But VATSIM does not provide a central system for written exams, so every division is now REQUIRED to develop a testing center. Fortunately, USA already had one, but the point remains that it is more downstream workload. Major airspace creates another set of bureaucracy....signoffs, policies, training programs, etc.
Bryan, I am glad to hear that you are considering dumping 05/05, it is ridiculous, and that should be evidenced by the stack of policies that were submitted in October for approval. I wish you would have told me that before.
Why do VATUSA1's quit? Simple......the amount of frivolity you have to deal with and cannot do anything about is abundant. That alone would be fine, but when legitimate issues go unanswered, a person's ability to make decisions is diminished to a point where all that is left is fielding complaints from unhappy people..... so what is the point?
As it stands now, the DD's job (quote from my resignation letter) is mostly a "buffer for people to complain at". You cannot get involved in Conflict Resolution. You cannot mitigate a situation where someone is poisoning an ARTCC, controller or staff. And you really have to be careful about who you appoint to a position because it is a decision that pretty much cannot be undone. You cannot hold staff accountable for breaking the rules without becoming an internet lawyer to build a case (and there are no rules on how the case must be built, it is completely subjective depending on who the "judge" is).
[!--quoteo--][div class=\\\'quotetop\\\']QUOTE [/div][div class=\\\'quotemain\\\'][!--quotec--]What do we get? We get ATMs who blatantly announce that they will exploit every possible loophole they can to circumvent the policies. And they do it!! The BOG and EC be damned. In short, what we really have are ATMs saying they will exploit every possible loophole to get around the Founders' Vision. Think about that one for a minute.[/quote]
I do not remember that ever being said......I must have missed it. I don't remember a case of an ATM trying to maliciously subvert the rules (except one minor time, but I brought that to his attention and never had an issue after that), and certainly not one that was brought to my attention from above. I think that overall the ATMs do a fantastic job of managing their positions, and should be commended for it. The few bad apples that have existed over time should be dealt with individually rather than trying to choke them out via legislation, that doesn't work anyway. But with the history of what it takes to deal with getting rid of a bad apple and making it stick......who would want to even try?