Preventive Maintenance Tracking Without Buying a Separate CMMS

Preventive maintenance tracking does not have to live in its own software. For many manufacturers, the simplest working version is a maintenance record inside the system that already runs jobs and schedules, so the next service window shows up right next to the work it will interrupt.

Picture the second-shift lead on a Thursday night. The spindle on the older horizontal mill starts to whine. The service sticker is faded, the clipboard by the machine stops in June, and the tech who keeps it all in his head is on vacation. Friday’s hot job is scheduled on that mill.

That is the problem this post is about. Not a missing app. A missing record.

Paper and memory fail at the worst possible moment

Most shops already do preventive maintenance. The trouble is that the record lives in three places: a sticker on the machine, a binder in the office, and one experienced person’s memory.

Someone has to remember the interval. Someone has to find the binder. Someone has to notice that a machine running double shifts hits its hour-based service twice as fast as the calendar suggests. When any link breaks, preventive maintenance quietly becomes reactive maintenance, and that always lands on the busiest week.

What does a minimum maintenance record need?

A useful preventive maintenance record answers five questions:

• Asset: which machine, press, compressor, or fixture, with a unique ID you can put on a tag.
• Interval: how often the task is due, by calendar days, run hours, or cycles.
• Last done: the date (or meter reading) of the most recent completed service, and who did it.
• Next due: calculated from the interval, not typed by hand, so it cannot drift.
• Parts and supplies: the filters, belts, or lubricants the task consumes, so they are on the shelf before the window opens.

Add a checklist per asset and a notes field, and you have a history that survives vacations and retirements.

Maintenance windows belong on the production schedule

When the next-due date for the mill lives in the same place as the jobs booked on the mill, the conflict is visible before it happens.

A basic flow might look like this:

Asset reaches its interval (date, hours, or cycles)

↓

Maintenance task appears as “due soon” with a target window

↓

Scheduler sees the window beside the jobs booked on that machine

↓

Planned downtime is placed between jobs, not in the middle of one

↓

Completed task resets the next-due date automatically

If your system already captures run time or cycle counts, as described in Kyo’s post on gathering real-time production statistics, usage-based intervals can be driven by actual machine use instead of a guess. Overdue tasks can then surface the same way other problems do, on an exception view for orders and inventory that shows only what needs attention today.

Check-offs should happen at the machine, not at the desk

If the tech has to walk back to an office PC after every task, entries get batched at the end of the shift and details get lost.

Mobile check-off fixes that. The tech scans a tag on the machine, the right task list opens, they tick off each step, snap a photo of the worn belt, and sign. No paper form. No photo hunt. No duplicate entry.

This works on several platforms. If you run Claris FileMaker, it is one practical option: Claris documents that FileMaker Go’s Insert from Device script step can capture photos, scan barcodes, and collect signatures on an iPhone or iPad. Kyo’s post on mobile capture with photos, signatures, and QR codes walks through what that looks like in practice.

When is a standalone CMMS worth it?

A CMMS (computerized maintenance management system) is software built specifically to plan, track, and document maintenance work. For some operations it is exactly the right call.

A dedicated CMMS often makes sense when:

• You have a full maintenance department with its own planners and a large, complex asset base.
• You need deep spare-parts inventory management, vendor service contracts, and maintenance cost accounting.
• Regulators or customers require formal maintenance documentation and reporting that a purpose-built package already handles.
• Maintenance runs largely independent of production scheduling.

It is often more than you need when a couple of techs handle maintenance alongside other work, the asset list fits on a page or two, and the real pain is visibility rather than planning depth. Then a separate system adds another login and another set of data that does not talk to your schedule. The better fit is usually extending what already works.

How do you know it is paying off?

Track these from the record itself:

• Unplanned stops per month on the machines you put on a schedule.
• Percent of tasks completed on time versus overdue.
• Jobs rescheduled because of a breakdown.

Give it a quarter and watch the trend move from surprise to plan.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We help shops put maintenance records next to the production schedule so planned downtime stops colliding with promised work.

Frequently asked questions

Can we track preventive maintenance in a spreadsheet?

You can start there, but spreadsheets struggle with usage-based intervals, mobile check-offs, and per-asset history. Most shops outgrow them once more than one person updates the file.

Should intervals be based on calendar time or machine hours?

Use whatever the equipment manufacturer recommends for each task. Many machines need both: some tasks by calendar, others by run hours or cycles. Your record should support either.

What if we already have some maintenance history on paper?

Enter the most recent completed service per asset to set accurate next-due dates. Scan and attach older history later if audits or warranty claims need it.

Not sure what your current data can support? Book a free 20-minute Data Health Check and we will take a look together.