The new process works as follows:
- First determine where in the object structure unplanned downtime has to be registered. Not all downtime leads to a loss of production, so it is important you first identify the bottlenecks in your process.
- Unplanned downtime is registered with the objects, by production or operations instead of the technical service.
- From there, either a job is reported for the technical service or the downtime is reported as having been resolved. In both cases a job is registered, in which it is recorded which object or part caused the downtime and what the failure cause was.
This way, you have high-level insight into the downtime that leads to loss of production, and you can analyse what parts cause the most or the longest downtime. By adjusting your maintenance plan accordingly, loss of production can be reduced more effectively!
This new process is available in Ultimo version 2021 and higher in the module ‘ Technical Service’.
More insight into the downtime
Our set of Power BI dashboards has been expanded with an additional set that enables a powerful, visual analysis of downtime! Aren’t you using BI dashboards (yet)? No problem! In that case, you can very easily export the downtime data including the causes to Excel, where you can do your own analyses.
Integration with the module ‘Shift Handover’
In version 2021 and higher, the downtime functionality is seamlessly integrated with the module ‘Shift Handover’. By using clear and simple dialog boxes, the number of actions and screen switches is limited to a minimum. This assures you of an even more accurate registration and the best possible communication between production and technical service!