When end users ask how to best manage and maintain their new Edge computing systems, the answer is not always straightforward. Unlike data centers, most applications at the Edge are deemed non-critical. If a system or network fails at a chain restaurant, and people can no longer access the automated option to view menus, the level of convenience drops, but business is not dramatically disrupted.

However, if the local food preparation systems or billing systems won’t work and customer meals cannot be delivered, the restaurant will need to temporarily close and those downtime costs are significant. As a result, each location that hosts an Edge computing system is faced with different elements that impact their cost of unplanned downtime.

Lost business is an example of the direct cost of downtime. In other types of Edge computing environments, indirect cost associated with unplanned downtime can also be substantial.

Consider the example of a wind turbine located in a remote area of Scandinavia. If an on-site $300 router fails, a technician will need to spend at least a day to access the location, repair or replace the faulty unit, and then return. A helicopter may be needed, and, if the winter weather is severe, the risk to human safety increases. Replacement of that single router could end up costing tens of thousands of dollars in maintenance fees alone.

Three approaches for managing Edge computing system maintenance

Although issues such as human error and insufficient power protection contribute to instances of Edge computing systems downtime, the biggest cause of downed systems at the Edge is lack of maintenance. Devices such as basic Uninterruptible Power Supplies (UPS), will emit an audible alarm if they encounter a problem such as a spent battery or a power sag. If no one is on site to hear the alarm and to address the issue, power protection is lost and the system is exposed to both blackouts, brownouts and power surges.

End users who invest in Edge computing systems generally choose one of three different approaches to manage and maintain their Edge computing sites:

• Reactive (run-to-fail) approach - This is an extreme approach that discount retailers, for example, often implement. Systems are allowed to deteriorate until a breakdown occurs that interrupts the flow of business. Response crews are brought in to rectify the situation as quickly as possible so that the resulting downtime can be kept to a minimum.
• Preventive approach - This is a marginally proactive approach where an on-site, non-technical, staff member - for example, a real estate manager - periodically monitors the Edge locations. Based on how old the assets are and the historical failure rates, regularly scheduled maintenance is performed (a technician may stop by once a week and only tweak the equipment or perform any necessary, obvious maintenance).
• Predictive approach - In this fully proactive maintenance model, assets are actively managed (often remotely) and monitored in real-time ensuring that minimal unplanned downtime occurs. Automatic alerts are generated based on signs of abnormal equipment behavior. These alerts are quickly acted on, and repairs are performed before any downtime occurs.

Field data indicates that, although the run-to-fail and preventive maintenance models at first appear to be less costly than the predictive approach, the opposite is true. Run-to-fail and preventive costs manifest themselves in small increments over time but add-up to a substantial amount each year. In addition, stakeholders who manage these environments live with a higher degree of fear, uncertainty and doubt regarding the uptime of their Edge computing systems.

Downtime mitigation methods

Regardless of the nature of the Edge computing site in question and the management and maintenance approach selected, Edge system downtime will always be perceived as a necessary evil that drives up cost. The question is, “how much cost?” Each installation will answer that question differently based on budgets and adversity to risk.

Today, a number of options exist for improving Edge solutions. One approach is to invest in monitoring software which provides visibility to the remote assets in the field. A second approach is to make certain the Edge solution is equipped with robust hardware so that instances of downtime are less frequent. The third option is to mitigate downtime risk through service contracts. In this case, qualified 3rd party partners manage the monitoring and maintenance of Edge computing assets at a reasonable cost.