Proactive is better than reactive

Due to the nature of my current work environment, things can be a bit unique. In each classroom we currently employ AMX audio visual switches to power the AV needs of the classroom. Unfortunately, the age of these devices causes quite the headache. On an average month, 4 AMX switches PSU’s will “bite the dust”. Before I arrived here, it was a reactive “get it done as fast as you can” mentality. Which, given the prior technicians in my positions, is not to be unexpected. But, that’s not good enough. Myself and another coworker implemented Nagios Core on a virtual machine in order to get ahead. The first event occurred two days after the monitoring and notifications were implemented. An battery had died in the classroom’s UPS. This resulted in the instructor shutting of the equipment rack to prevent classroom interruptions. Rather than the next instructor coming into a dark classroom, we were able to replace the battery and bring the equipment back online before anyone noticed.  A week later during a regularly scheduled generator test, two separate rooms GFCI outlets were tripped. Thanks to Nagios, we restored power to both rooms before the next class. Since, we have had numerous failures, all of which have been resolved before a ticket was submitted.

One caveat to this “Ghost IT” is, there’s not longer a significant need to contact IT. This could be cause for budget cuts down the road and downsizing. As the general rule of thumb, document, document, document. Record interactions and situations where pro-activity has prevented end user interruptions. We have configured our Nagios instance to automatically generate a ticket once the issue has been acknowledged.

 

“Recast your current problems into proactive goals.” – Suze Orman