National Defense 1*1 Defence nationals Maritime Engineering Journal January 1992 Crisis in the Gulf Making Operation Friction Happen Canada Looking Back: DEMS at War! The real enemies were boredom, cold, wet, fear and fatigue. ...page 22 MARITIME ENGINEERING JOURNAL. JANUARY 1992 Maritime Engineering Journal January 1992 DEPARTMENTS Editor's Notes 2 Letters 3 Commodore's Corner 4 FEATURES Crisis in the Gulf— Making Operation Friction Happen b\ Imran Mirza.... 5 Flight of the Golden Bird —Athabaskan's AIM 7M Missile Upgrade Director General by LCdr "Rogie" Vachon 9 Maritime Engineering and Maintenance The CFR CSE — An Endangered Species Commodore M.T. Saker by Cdr Roger Cyr 13 Project Update: The Canadian Patrol Frigate Editor by LCdr Leo Mosley 15 Capt(N) David Riis, DMEE FORUM 17 Technical Editors Cdr Dave McCracken (Marine Systems) GREENSPACE: LCdr Boh Jones (Marine Systems) An Interim Blackwater System for HMCS Huron LCdr Bill Dziadyk (Combat Systems) by LCdr Richard B. Houseman 20 LCdr Imran Mirza (Combat Svstems) Cdr Boh Chanter (Naval Architecture) LOOKING BACK: LCdr Paul Brinkhurst (Naval Arch.) DEMS at War! From the book by Capt(N) Max Reid 22 Production Editor BOOK REVIEW: LCdr(R) Brian McCullough (819) 997-9355 by LCdr R.J. Summers 24 NEWS BRIEFS 25 Graphic Design Ivor Pontiroli, DPGS 7-2 INDEX TO 1991 ARTICLES 27 Word Processing by DMAS/WPRC 4MS Mrs. Terry Brown, Supervisor Translation Services by Secretary of State Translation Bureau Mr. Louis Mcirtineau, Director OUR COVER The Phalanx anti-missile galling gun was The Maritime Engineering Journal (ISSN 0713-0058) is an authorized, unofficial publication of the the major weapon upgrade for Canadian maritime engineers of the Canadian Forces, published four times a year by the Director General Maritime Engineering and Maintenance. Views expressed are those of the writers and do not necessarily warships sailing to the Gulf. With its radar- reflect official opinion or policy. Correspondence can be addressed to: The Editor, Maritime controlled 3,000-rounds-per-minute rate of Engineering Journal, DMEE, National Defence Headquarters, MGen George R. Pearkes Building, fire, the Phalanx offered reliable close-in Ottawa, Ontario, Canada K1A OK2. The editor reserves the right to reject or edit any editorial material, defence for the task group. (Base Halifax and while every effort is made to return artwork and photos in good condition the Journal can assume photo HSC 90-1069-572) no responsibility for this. Unless otherwise stated. Journal articles may be reprinted with proper credit. MARITIMK F.NGINHKRING JOURNAL. JANUARY 1W2 Editor's Notes Operation Friction: It was teamwork that won the day By Captain(N) David W. Riis, OMM, CD Director of Marine and Electrical Engineering From a Canadian naval engineering sea must understand how the Captain issues of the Journal we expect to perspective. Operation Friction will thinks and what the Captain needs to bring you more of the stories and the long be remembered as an outstanding know under each situation to allow the engineering lessons learned from success story of determination, resource- ship to work as a team. This is why Canada's naval contribution to the fulness and co-operation. In just two time spent on the bridge and in the ops United Nations effort in the Gulf. weeks, with the threat of war hanging room is always time well spent by an And we've got something new for over the Persian Gulf, two destroyers, engineer. The same requirement exists you. Starting with this issue we are a supply ship and five helicopters ashore in the support organization in opening up a little bit of greenspace were outfitted for operations with the order to establish the communication in the pages of our branch magazine. UN-sanctioned multinational force. In that makes teamwork possible. Operation When we ran our full-edition Journal the words of Commodore Ken Summers Friction, I believe, was a true success on maritime environmental protection (who we are delighted to welcome to story of the navy working as a team. a year ago, we didn't want to produce the Commodore's Corner in this issue) In our cover story, LCdr Inn an a "one-hit wonder" and then wash our it was "the finest example of Canadian Mirza chronicles the events behind hands of the subject. The navy is com- engineering excellence." the incredible undertaking of making mitted to becoming an environmentally Operation Friction was a great Operation Friction "Phase One" happen friendly force in our nation, and in opportunity for we engineers to hone from a DGMEM perspective. As the that regard there is a veritable host of our skills at clarifying the requirement, DGMEM co-ordinator for Op Friction, activity on the naval engineering scene. analyzing the options and then design- LCdr Mirza was in a good position to "Greenspace" will be a permanent ing and implementing change. For me it observe and abet the excellent team- feature of the Journal where we can once more underlined how important it work between the operations, engineer- showcase our environmental activities is for engineers to understand the oper- ing and logistics worlds. We will and concerns. ator's requirement, to understand how also follow the remarkable story of Finally, I want to take a couple of the operator thinks. As every Maritime Athabaskan's AIM 7M missile upgrade lines to express the appreciation I know Engineer officer knows, the engineer at during her deployment. In upcoming we all have for the efforts of LCdr Brian McCullough, our production editor. Over the past seven years Brian has laboured hard under often difficult conditions to develop the Maritime Engineering Journal into the high- quality publication it is today. It is indeed a journal all MAREs can be truly proud of. Brian, you've heard this before, but it's time you heard it again — thank you for your enthusiasm, your professionalism and especially for the personal interest you continue to bring to our Journal. HMCS Profecfeur entering Halifax Harbour upon her return from the Gulf last April. (Photo by Karen Blais) MARITIME ENGINEERING JOURNAL. JANUARY 1992 Maritime Engineering Journal Objectives Letters • To promote professionalism among maritime engineers and technicians. Who best to do software In any system, there is a need for • To provide an open forum where top- programming? people who have experience in the use ics of interest to the maritime engi- of that system. That is, people with neering community can be presented experience in the end-use of that sys- and discussed, even if they might be Having just read Cdr Cyr's article tem are needed to define the require- controversial. on software in the October '91 Journal, ments for the system and to test the I have concerns with his view that system to ensure that its performance • To present practical maritime engi- programming and analysis should be is acceptable. neering articles. left to civilian programmers in the For example, with the space shuttle, • To present historical perspectives on department or civilian contractors. This astronauts are consulted when the shut- view is short-sighted in that it fails to current programs, situations and tle system requirements are defined and take into account the experience and events. when the systems are tested. However, skills which the military programmer astronauts are not used to program the • To provide announcements of pro- brings to the problem. grams concerning maritime engineer- system. This technical function is left ing personnel. Although it would appear at first that to programmers. Similarly, for naval civilian programmers are the most cost- systems, the end-users (naval officers) • To provide personnel news not efficient method of developing and are needed to define the requirements covered by official publications. maintaining software, it does not take of these systems and to test the systems Writer's Guide into account the learning curve required to validate the performance of these to understand naval systems and the systems. They are not needed as pro- The Journal welcomes unclassified submissions, in English or French, on milieu in which the systems will be grammers. This is a technical function subjects that meet any of the stated employed. The military programmer that is best performed by technicians objectives. To avoid duplication of effort has attained the experience from back- trained in programming. — Cdr Roger and to ensure suitability of subject mat- ground training and previous military Cyr, DIAC(4), Ottawa. ter, prospective contributors are strongly employment. This experience would advised to contact the Editor, Maritime prevent programming errors and helps Engineering Journal, DMEE, National in the on-site analysis of programs as Defence Headquarters, Ottawa, Ontario, they are developed, which prevents K1A OK2, Tel. (819) 997-9355, before extra cost being incurred when errors submitting material. Final selection of have to be removed from the program articles for publication is made by the Journal's editorial committee. (or, in the worst case, from the system) after the fact. As a general rule, article submissions should not exceed 12 double-spaced Thus the best method for the pages of text. The preferred format is Canadian Forces, and the navy in par- WordPerfect on five-and-a-quarter-inch ticular, to develop and maintain its diskette, accompanied by one copy of software is to have a mix of civilian the typescript. The author's name, title, contractors with departmental civilian address and telephone number should and military programmers. The military appear on the first page. The last page programmers should be on-site, both should contain complete figure captions for all photographs and illustrations at the contractor's office and the Fleet accompanying the article. Photos and Software Support Centre, and should be other artwork should not be incorporated present at all levels of software produc- with the typescript, but should be pro- tion.