Machine Downtime and Run Hours Recording
Running, idle and stopped time is worked out from the machine’s own readings. When a stop runs past a set number of minutes, the operator picks a reason at the panel from a short list.
Counted from the machine, not a register
Running, idle and stopped are derived from readings the machine already produces. Nobody writes a time down, so nothing is filled in later from memory. The count is the same whether or not the supervisor is present.
What gets recorded
Who uses which number
Frequently asked questions
How reliable are the stoppage reasons?
They depend on the operator choosing correctly, which is why the list is kept short. The duration itself is measured from the machine and is not typed in. It cannot be edited by hand.
Can it tell running from idle?
Yes, where the machine gives a signal that separates them, such as current draw, a run contact or a cycle pulse. What is available differs by machine. It is checked during the site visit.
Will these figures reach our ERP?
Yes. Run hours, downtime and consumption can be pushed into an ERP or maintenance package so that production planning reads them. Tally holds books and not machine logs, so a link there carries only the figures your accountant asks for.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements