Automated schedules. Zero missed maintenance windows.
Usage- and calendar-based schedules with parts, procedures, and sign-offs attached. Missed windows escalate before they become findings.
PM schedules on paper fail quietly: the checklist taped to the analyzer gets initialed in batches on Friday, the monthly task slides into next month, and the freezer that needed a coil cleaning becomes the freezer that failed over a weekend with forty thousand dollars of reagents inside.
In an inspection, the missed PM converts every result the instrument produced into a question. Was the analyzer within specification that week? The maintenance log is the only witness — and it was signed in batches.
Part 820.70(g) requires scheduled adjustment, cleaning, and maintenance with documented conduct and dates. CAP checklists require function checks and maintenance at defined frequencies, with records reviewed. AABB standards require equipment maintenance per manufacturer specification for everything touching blood products — with the schedule itself a controlled document.
Paper checklists document compliance in batches, after the fact. Kintavo issues each task at its moment, captures completion with a signature at the instrument, and escalates the miss while it is still recoverable.
Monday 6 a.m.: the chemistry analyzer’s daily maintenance task is on the tech’s tablet — seven checklist items, two with acceptance criteria. Item five fails: a fluid line shows wear. The failed criterion opens an event, the line is replaced from inventory, and the task completes with both signatures. The weekly review is four minutes: one exception, already handled, already documented.
Preventive Maintenance shares the same data model, AI engine, and audit trail as the other eighteen modules — so its records see, and are seen by, everything else in your quality system.
Yes — cycles, runtime hours, or event counts, per manufacturer specification, alongside calendar schedules on the same asset.
Escalation the day the window closes: supervisor notification, dashboard visibility, and — if configured — instrument restriction until the task and a documented risk decision are complete.
Yes, from a tablet or phone at the instrument, with the checklist, acceptance criteria, and signature captured in the moment. Batch initialing disappears because the workflow replaces it.
A failed acceptance criterion opens an event immediately — linked to the asset and the task — so the wear you found on Monday does not become the failure you explain in March.