Stops and microstops
The most evident form of machine shutdown occurs when a visible machine failure occurs. Consider scenarios like a stalled motor or a ball bearing damaged due to wear. Downtime materializes as the period during which the machine is not operational following the defect, the time required for component repair or replacement, and any subsequent scheduled maintenance or overhaul. A comprehensive problem analysis is essential in such cases. Understanding which component(s) caused the downtime enables proactive measures to prevent recurrence.
However, not all machine downtimes are equally conspicuous. Frequently, they manifest as microstops—brief and frequent interruptions in the machine cycle, often resolvable swiftly by an operator. These microstops typically last only a few seconds and can stem from various causes. Sometimes, they result from machine-related factors, such as a programmable logic controller (PLC) briefly halting a heated motor until it cools down.
Human error also plays a significant role in microstops. Configuration errors, misjudgments, distracted operators, or improperly loaded materials on the production line can all contribute to these interruptions.
Hidden impact
The problem is that these microstops are often not measured. Therefore, the impact of such short but frequent stops is often underestimated. Especially over the long term, and especially in high-volume companies, microstops can have a major impact on productivity and revenue.
Microstops are not easily measured in a manual way. In other words, you need an automatic measurement system that will chart your downtime. Fortunately, there are systems on the market that can help you monitor different types of downtime, including microstops, and visualize them in a clear way.
How to implement IIoT?
PLCs often already convey important information about the nature of downtime (time, duration, cycle, location of fault). Even older machines without PLCs can be modified with sensors to capture such information. The PLC on the machine then typically passes that information on to a communications platform, which is the bridge between machine control and the digital world, and then to an IIoT platform, such as PTC Thingworx, which provides easy management of all the data and information flows that your machines provide.
From then on, things get interesting. An IIoT platform gives you clear dashboards with all the necessary information about the performance and any downtime of your machines. Moreover, you can set alarms when downtime lurks around the corner, for example, when certain parameters are exceeded. This collected information allows you to optimize or intervene more quickly where necessary. Perhaps your downtimes occur mainly in the production of one particular product? Or at a specific step in the process?