Machine Log is a feature that allows you to see machine incidents and downtime alongside longitudinal data so that incidents can be correlated with other factors and eventually down time can be predicted. This allows for preventative maintenance and other corrective actions to prevent down time. Machine Log was modeled after a successful program at University of California at San Diego where down time was reduced by 47% and patient treatment cancellations were reduced by 68%. Other benefits include reduced time to initial response by machine vendor support staff, more machine down events being resolved by clinic staff, and fewer on-site calls by the vendor service engineers. For more information see the "Improving linear accelerator service response with a real-time electronic event reporting system" article in the Journal of Applied Clinical Medical Physics, Volume 15, Number 5, 2014. The article can also be downloaded from: Hoisak et al Machine Log.
Machine Log allows users to record issues, downtime, and track resolution of machine and equipment incidents. QA report longitudinal data can be compared to Machine Log incidents. The intent is to monitor trends to predict potential downtime and prevent it.
Machine Log also provides the capability to automatically notify vendors in the event of an incident. The aim is to simplify the creation of service tickets, help the vendor plan for preventative maintenance, and ultimately reduce down time.
Incidents can be updated or viewed by anyone with the appropriate permissions. This means that when a service engineer has resolved an issue he or she can update the incident rather than rely on a verbal message or the infamous sticky note and that anyone associated with the incident is immediately up to date.
Machine Log must be enabled for your account by Image Owl Support. If you are interested in this feature or have any questions, please contact us at email@example.com.
Please sign in to leave a comment.