Automatic MTTA, MTTR and MTBF
The clock starts when the machine stops, not when someone opens a ticket. The indicators come from the real event, so nobody has to defend their number.
← The whole platform
KINNIL MTTO
Production and maintenance stop arguing when they look at the same data
“Maintenance and production keep blaming each other.”
MTTA, MTTR and MTBF calculated from the machine's actual event, not from what somebody remembered while filling in the log. Recurring failures surface on their own.
What it actually does
Maintenance measured with the same yardstick as production
A log tied to the event
Every intervention is linked to the stop that caused it, who handled it and what was replaced. The log stops being a notebook running parallel to reality.
Recurring failures made visible
The same failure mode repeating on the same machine groups itself. That's the input for deciding what to redesign instead of what to repair again.
A plan fed by condition
When Kinnil CM is on, the machine's deviation feeds straight into the maintenance plan: work gets scheduled by real state and not only by calendar.
How it gets switched on
It runs on the signal you're already measuring
MTTO needs no separate install: if the machine is already connected for OEE or for condition, the module switches on over that same data. It's a software decision, not a new project.
If it's the first module you turn on, the install is the same as any other — 1 day per machine, without stopping production, with a 120 V outlet as the only physical requirement.
- 01We define what counts as a stop and what as a micro-stop
- 02We load the catalogue of machines, causes and owners
- 03History starts accumulating from the very first shift
- 04The indicators enter the weekly meeting with evidence behind them
The other modules
They all run on the same data and the same hardware. Turn on one, turn on six — the bill grows per machine, not per module.
KINNIL OEE
Production in real time
KINNIL CMEquipment condition
KINNIL DAQData acquisition
KINNIL PLANNINGPlanning
KINNIL ENERGYEnergy and sustainability
Where it's being usedManufacturingMining
Already in operation
See the manufacturing case →15–20% more productivity
Plants where OEE and maintenance run together and production data feeds the maintenance plan.
Frequently asked questions
What people ask about maintenance
Does Kinnil MTTO replace my CMMS?
It can, or it can coexist. What Kinnil contributes is the hard data of the event — when the machine stopped, how long until it was attended and how long until it produced again — which is exactly what a CMMS usually receives keyed in by hand.
Do the indicators depend on someone logging correctly?
Not for starting and stopping the clock: the machine measures that. What people contribute is the cause and the description of the intervention, which is where their judgement does add value.
Can it integrate with the ERP?
Yes. The platform exposes PDF and Excel reports and ERP integration so the data also lives where the operation is already administered.
The next stepIt's not about buying anything.
It's not about buying anything.
It's about measuring your most problematic machine.
Kinnil Pilot · 30 days
We install on 1–2 machines, measure your real baseline and present the findings with your own data. Success criteria agreed from day one.