Have you ever signed up for an email that was nice at first, but came so often it became annoying - sort of like a pesky neighbor? You know the type; the one who’s always trying to hang out even though your spouses don’t get along and you’re tired of their dog digging up the flowerbed.
You might push away such a neighbor, or unsubscribe from such an email. But when alarms become an annoyance we tend to ignore them, write them off, or even turn them off. Don’t let your remote tank level alarms become this annoying.
Remote tank level alarms, when set up right, are important and should never be ignored. If you’re experiencing alarm overload, it’s time to re-evaluate. When creating a new alarm, ask yourself if the notice is valuable, actionable, and directed to the right personnel.
An alarm is valuable if it helps meet your goal for monitoring a remote tank. It may not be valuable if you’re simply curious. Before you set up an alarm, decide on a goal and ensure that it lines up with the reason you’re monitoring the tanks in the first place.
For example, if you’re monitoring a battery of remote tanks to know when to fill them up, the only alarms you need are those that help you schedule the shipment of product. It may be tempting to set up a confirmation alarm to notify you that the tank was filled. It’s not a bad idea if the confirmation is usable, or if the peace of mind is valuable enough.
Ideally, an alarm will trigger a vital action. Passive alarms are often the culprits behind alarm overload and annoyance. In our previous example, an alarm that notifies us that the tank is 80% empty would probably help in scheduling a delivery, which is tied directly to the goal of remote monitoring.
If there isn’t an action required by an alarm, question its validity. Take a hard look at the purpose behind the alarm, and if it has merit. Passive notifications can be valuable in the right circumstances, but avoid using them just because you can.
Finally, an alarm must be delivered to the right people. You might feel the need to have one person who receives all alarms. In smaller organizations, this might be a smart idea. However, the more tanks you have, the more aggravating this will be to the recipient.
A good rule of thumb is to send the alarm to those who are responsible for responding to the notification. These could be dispatchers, drivers, managers, engineers, or technicians. Make sure the right people get relevant alarms and save everyone else the hassle.
Contact us if you have any questions about remote tank level monitoring or alarms. We'll help you assess your remote monitoring goals and find the best solution.
> !function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(window, document,'script', 'https://connect.facebook.net/en_US/fbevents.js'); fbq('init', '2241001876219184'); fbq('track', 'PageView');
> !function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(window, document,'script', 'https://connect.facebook.net/en_US/fbevents.js'); fbq('init', '2996670937328619'); fbq('track', 'PageView');