Chief Gunner said:
Occam - I will attempt to address both yours and Jenerator's comments in this post. So in no particular order . . .
1. This is not MORPs. I am not aware of any person involved in this project that believes that MORPS is a viable present day construct.
You missed the smiley, Chief. Changing the trade name now is similar to MORPS in that it was widely disliked, viewed as unnecessary by many, and was a long painful process.
2. No offence but, it is highly unlikely that your opinions are based on a comprehensive knowledge of the reasons for the present restructuring of the existing CS Tech Occupations (which does not include an occupation called 'Sonar Tech' that name change has never been approved). However that means that your opinions are also not influenced by that comprehensive knowledge and thus are likely to include gems we may not have considered. Continously offering that opinion as the only viable solution or only offering criticism without solutions is counter productive.
No offence taken; however, it would be appreciated if you would kindly stick to addressing the points raised and refrain from raising straw man arguments like "you don't have the comprehensive knowledge of the reasons for restructuring", attributing bitterness to my comments, and accusations of being confrontational and insulting. Issues were raised with the change in the trade name; you didn't ask for solutions and I would submit that's the responsibility of the working group. The issues raised were given in good faith and without malicious intent. My experience is sufficient to be able to make educated (but not comprehensive) comment on matters relating to the trade(s). Very few get that comprehensive experience, as you know already.
3. Being involved in any decision making process that includes more than one person or organizations whether as an active participant or consultant does not mean that you are necessarily in control of that process.
True, but I'm not sure what relevance your statement has on the discussion at hand.
4. I do not believe that I at any point stated that the Canadian Navy would be making policy decisions based solely on the input of anonymous members of an online public forum. However, your opinions are valued and considered in the decision making process of this CS Tech OAG. I personally ensure that all opinions, comments and questions posted within this thread are made known to the Occupation Advisory Group.
I don't believe anyone suggested that the Navy would be making policy decisions based solely on the input of anonymous members of an online public forum.
5. Three of the five new occupations will have direct hands on maintenance responsibility for what are traditionally considered hard-kill weapons systems. One of the two remaining will have direct hands on maintenance responsibility for what are traditionally considered soft-kill weapons systems i.e. electronic warfare systems. The fifth occupation will be responsible for maintenance of communications systems that support all aspects of naval operations. Clearly the majority of the new occupations are in fact weapons technicians. This is not simply a case of renaming the existing occupations. The new occupations will have new equipment responsibilities. Thus the requirement for a name change that accurately reflects what the actual job is.
Now we're getting somewhere. If the reallocation of equipment responsibilities is the driving force behind the name change, then my opinion remains that it is unnecessary, although more information relating to how the equipment would be reallocated might persuade me to change my opinion. For example, if we're turning a NET(T) who was formerly responsibile for CANEWS, RAMSES, the SRD, etc into a "Weapons Engineering Specialist Sensors" solely because he'll be given the added responsibility of the chaff launchers (your soft-kill weapon, along with RAMSES), then the "weapons" spin on his employment is tenuous at best. He's still primarily a sensors tech. Similarly, a NET(A) who was formerly responsible for the active and passive sonars, all the NAV equipment and horizon bars who will now be renamed to something else because of the addition of the torpedoes and launchers to the mix is still less a weapons tech and more a nav and sonar tech. This isn't NWT bashing, because all these weapons systems do need to be maintained, but selling a recruit on a job as a weapons tech that has little to do with weapons is deceptive at the very least.
6. There is absolutely no solution that will please everyone. The ideal solution is one that offends the fewest while meeting the requirements of the service. The Occupation Advisory Group, DMARPERs, DMTE and DGPR are working hard to find to an optimal solution. Various oversight organizations within the Navy, the CF and DND ensure that all regulations are adhered to throughout the restructuring process, and that the final solution meets departmental requirements.
* The present CS occupations (at all ranks, coasts, class of ship etc) have spent literally thousands of hours on rectifying a very real and complicated problem.
* Continuously suggesting that these changes are not required, are arbitrary or dictatorial in nature is not only incorrect and presumptuous, I personally find it to be unnecessarily confrontational, counter productive and insulting. Not only personally insulting but also insulting to the hundreds of Canadian Forces members and DND employees that are presently or have, in the past, been involved in this project.
I know it's not a simple process, and that it takes huge amounts of manpower to address changes like this. My experience has been that the Navy tends to overcomplicate things and use a sledgehammer when a tweaker will do. Is the answer a reallocation of equipment amongst the trades, or is it simply that one trade is understaffed on the ships? In reallocating more equipment to a particular trade, will a commensurate amount of additional training be given, or will the training become more "watered down" in order to fit more in the same period of time? If it's watered down, what effect would that have on the certification process by TechNova? Is the Navy even concerned about certification anymore?
Lots of questions, Chief. Someone is going to have to take the hard sell to the members of the CSE trades to make this fly, or it'll become as unwelcome as MORPS was.