Bringing up the engineering & maintenance side interfacing. My last real job which was almost 4 years ago, I was on the maintenance side. We worked with many engineering groups such as data, Fire Station Alerting System, voice radio, microwave radio, power plant, building engineers, etc. From what I've seen is the engineering and maintenance side communicated well. I've also seen engineering doing maintenance type of work and the maintenance side doing engineering work. Most of the engineers were very good at what they did but they seem to forget about the maintenance or didn't have the time to put together procedures. We were constantly asking for drawings, test & alignment procedures, training, test equipment, vehicles included in the vendor contracts, etc. I took it upon myself to create test & alignment procedures for the Fire Station Alerting System 2nd generation infrastructure and fire house equipment. When I was promoted to another crew, I noticed that the techs were spending a lot of time dialing in to the various equipment such as DAC's, T-1 muxes, TenSR's, routers, etc. So I made an Aspect script in ProComm that automated the procedure and created a web page showing all the critical and major alarms, and page the person on standby. When I was promoted to Field Service Manager, the AGM and the CFO were asking for all kinds of info and reports such as how much time is spent on site maintenance versus systems or why so much time is spent at a certain site. We didn't have a ticket system that I could pull up the info or reports so I made a client-server database system using MYSQL that was used for several years. Once I made a detailed manual on reconfiguring DDS circuits to the Disaster Recovery system (back in 87) that I learned in a class. The only document I got from the class was a one page login document.
This may sound strange but one of my pet peeves at work was the techs. not communicating correctly with other groups. There were times when I heard a tech. on the phone with a customer talking about bit errors or T1#24. They don't know what that means. If a tech is talking to a field unit then it should be layman's terms. If a tech is talking to a department communications liaison then it may be a little bit more technical talk. There were times, I needed to secure funding for test equipment from the admin. section. I wouldn't say I need service monitors with the APCO25 P2 option. I would use layman's terms. Now if a person is in a "scanner forum" then it should be the same lingo and terminology. If a person is a beginner then it's up to him or her to learn the subject.
This is not an internal company type situation. This is a customer situation, a much different situation than different departments in the same company. Here on Radio Reference there is quite a bit of Wiki information to take a beginner up to some level of knowledge.
Another thing to consider is the amount of time a hobbyist has to learn a hobby. In my case I have long distance bicycling (and associated bicycle mechanics), car maintenance, ham radio, photography, backpacking, cross country skiing, peak bagging (climbing peaks with or without technical rock climbing gear), woodworking, gardening, writing and maybe a couple I've forgotten. My Canon digital camera has some pretty good instructions and that company spent a great deal of time writing the manual before selling the first unit. I learned a lot about these by reading books. In fact, I wasn't learning much about telemark skiing (a cross country or mountaineering skiing method to get down slopes) with instructors, so I took a few key copies of pages from a book about cross country skiing and taught myself.
Last edited: