Definition:
In general there are two definitions for down time. From the patients
point of view and for machine performance. For the patient it is
important to be treated every day without long delays. Lets say one
linac breaks down but the patient can be treated on an other linac
(witch for example was just be serviced). In this case production is
not inhibited and from this point of view there is now down time. On
the other hand it is useful to have an impression of the performance
of the linac itself. How many times does it break down. How long does
it take to repair. Does one particular part of the linac give trouble
(for example MLC). etc.
A point of discussion is if maintenance must been seen as down time or
not. From the patients point of view the linac is not available so it
would be down time. On the other hand when a linac is purchased it is
known that maintenance must be carried out at regular intervals to
ensure safe and trouble free operation. Seeing this maintenance as
down time appears to me as bad management.
Administration:
We make extensive use of the debug terminal. All errors are registered
automatically and at the end of the month my colleague edits the debug
files and counts the number of interrupts. This is multiplied by a
standard time factor of 5 min. When we replace lets say a light bulb
we use a text editor available in the debug program to record the time
we used. You can imagine that these manual entrees are sometimes not
very accurate or even forgotten.
The definition we use is:
Down time is the time when a linac can not be used for treatment due
to electrical, mechanical or physical faults during normal working
hours. (This implies that maintenance during working hours and repairs
in the evening or at weekends are not registered as down time).
|
Some remarks.
Courtesy of Cees Imhof