Use case
The machine's history shouldn't retire with the mechanic.
Timill keeps every machine's schedule, faults, and repairs in one place — with reminders that fire on time and a fault-reporting flow anyone on the floor can use from a phone.
Maintenance by memory
- The service schedule is a wall calendar or an Excel sheet nobody opens until something breaks.
- The machine's real history lives in one veteran's head and a greasy binder by the compressor.
- Faults get reported verbally — "the lathe is making that sound again" — and evaporate.
- Preventive maintenance slips, because urgent always beats important when nothing reminds you.
- CMMS software exists, but most of it targets big plants and maintenance departments, not a shop where maintenance is two people and everyone else.
The configuration
How it works in Timill
Item types
Machine / Equipment
ID, location, manufacturer, model, serial, install date, criticality, documents (manuals, certificates), service interval(s), full linked history.
Maintenance Task
Type (preventive / repair), machine, description, assigned to, due date, status, hours, parts used, photos.
Fault Report
Machine, description, photo, reported by, severity, status (Reported → Assessed → Scheduled → Fixed).
Links that create the trail
Every task and fault attaches to its machine. Open the machine, see its whole life: services done, faults, parts, costs, photos, and every discussion.
Automations
Service interval due → maintenance task created and assigned. Critical-machine fault reported → maintenance lead notified immediately. Task overdue → escalation.
From the floor
Anyone reports a fault from their phone in under a minute — photo, machine, description. No "I told someone on Tuesday."
What each role sees
Everyone (mobile)
Report a fault; see machine info by opening its item.
Maintenance lead (dashboard)
This week's preventive tasks, open faults by severity, overdue work.
Production / owner (dashboard)
Machine downtime patterns, repeat offenders, maintenance load.
A day with it
- 06:50
Operator hears the bad bearing sound. Fault report from the phone with a 10-second video. One minute.
- 07:05
Maintenance lead sees it, checks the machine's history — same symptom 4 months ago — schedules the fix for tonight's break, orders the part.
- Next month
The preventive service for that line pops up on schedule, assigned, with the manual attached to the machine item.
- Next year
The veteran mechanic retires. The history stays.
Who this fits
Common in: manufacturing shops, property and facility maintenance teams, energy and utilities contractors, logistics fleets, food production — any team where equipment uptime matters and maintenance is tracked on paper, Excel, or memory. Also strong paired with work orders for contractors maintaining customers' equipment.
Why Timill and not…
Excel + wall calendar
No reminders, no history at the machine, no photos, no accountability.
Full CMMS
Built for maintenance departments; heavy for a team where maintenance is a role, not a department.
Generic task tools
The machine is the center of this process, not the task. Timill lets the machine be a first-class object with its own life story.
Open a machine and see its whole life — services, faults, parts, and photos — instead of a binder nobody can find.
From the floor
Live on every dashboard
Questions
We have 300 machines in a spreadsheet.
Import them. That spreadsheet becomes the machine register, upgraded.
Multiple service intervals per machine?
Yes — configure the intervals your equipment actually has.
Can operators report faults without full accounts?
Access is role-based; reporters can have a deliberately simple view. Exact setup depends on your structure — ask us on the call.
Manuals and certificates?
Attach them to the machine item; they're on every technician's phone at the machine.
On-premises?
Yes — Docker-automated on-prem deployment for teams that keep data in-house.
Put your machine park in one place
Bring your equipment list — we'll show it as a live register with schedules and fault reporting, in 30 minutes.