This post is part of a series in which we will explain different service/employment models. In this particular post, we will take a closer look at the run-to-failure model. As the name already describes, this model is used with the intention that the product is operated until it fails. Therefore, the product does not get serviced within its lifetime or replaced. This model is employed when replacement and downtime costs are low compared to inspection or servicing costs, leading to the most cost efficient product usage. However, when a failure requires experts and/or special components, the downtime is unschedulable and long. 

An example of a product which is operated with the Run-to-Failure model is a light bulb. During the operation of the light bulb no servicing is needed and when it fails, the bulb can be exchanged in seconds. For more complex products  this model is generally sub-optimal.  An example of a complex product using Run-to-Failure is the dishwasher. Whenever it fails, it often takes time till a service technician (expert) can check, repair or replace components. This causes extensive frustration to the owner as they experience a long and unnecessary downtime in which they can not use the dishwasher, and therefore may lose the trust in the reliability of it. 

Amplo can reduce the downtime and therefore the frustration significantly. The data generated by sensors in the product would be monitored by Amplo algorithms which can discover early signs of a potential failure. Anticipating failures enables the operator to preemptively schedule maintenance and avoid potential downtime. In the case of the dishwasher, Amplo’s algorithms predict a potential failure before it occurs and schedules a service technician.