Preventive maintenance that actually gets done

Why it matters

Preventive maintenance fails quietly. Nobody decides to skip the quarterly inspection; it simply never becomes anyone's job on any particular day, and the sheet that says it was due is in a drawer. A PM system has one job: to make the schedule produce a concrete work order, for a named person, with the checklist attached, early enough to plan, and to show plainly what was done late or not at all.

How it works in LK Up

1. A schedule names the work. Under PM, a manager presses New schedule: a title, the asset, the priority, an assignee or a team. The checklist comes from items you build (pass/fail, text, a number with limits, a photo, a signature, sections) or from a Procedure in the library.
2. The trigger: calendar or meter. By calendar: every N days, weeks, months or years, with a Fixed calendar (the next date counts from the planned one) or Floating (from when the work was actually done) and a Lead time in days. By meter: every so many running hours or cycles of a meter on the machine; the meter's page forecasts the next due from the rate of the last 30 days.
3. Preview, then create. The form shows the Next five due dates before you save, so a wrong interval is caught in the office, not on the floor.
4. The server makes the work order. When the lead time begins, a work order appears under Work orders with the checklist, the assignee and the due date; the technician sees it under My work, and it shows outlined on the calendar with Show PM. Nobody has to remember to create it.
5. Rounds and batches. One schedule can cover several machines in the order to visit (a lubrication round); Select on the asset tree creates one schedule for many machines at once; Import CSV brings in a hundred schedules from your existing sheet.
6. Keep it honest. Postpone by changing the Next due date, Pause a schedule for a machine in storage, and read PM on time in Reports: on time, late, still open past due, based on the PM work orders done in the period.

Why we built it this way

• Fixed and floating are both offered because both are right. A monthly safety inspection is fixed: it is due on the date whether or not the last one was late. A lubrication interval is floating: greasing late and then again on the old date wastes grease and time.
• Lead time is a planning tool, not a reminder. The work order exists for the whole lead time, so the manager can move it on the calendar, reserve parts for it and assign it in the Monday meeting. A reminder on the due date is already too late to order the filter.
• A monthly PM absorbs the weekly one in the week they coincide. Doing the weekly check on Monday and the monthly one, which contains it, on Tuesday is how technicians learn that PM is paperwork.
• A failed item opens the repair. An inspection that finds a problem should not end with a note. Create a work order when this item fails on a pass/fail item makes the corrective work order at once, linked to the inspection.
• The import never changes an existing schedule. Re-importing a sheet must not silently rewrite the intervals a manager tuned by hand; it adds, and you change the rest on their pages.

What it does not do

LK Up does not read meters from the machine by itself; readings are typed or scanned in by a technician (the planned link to LK On would bring machine events in). It does not reschedule a late PM for you: a late one stays late in the report, on purpose. The procedures library, versions and the rest: chapter 8 of the user manual.