Preventive Maintenance

A Maintenance Schedule is a recurring plan that defines what maintenance to do, when to do it next, and whether the system should auto-generate a maintenance event when it comes due. A schedule fires repeatedly over the life of the asset; each firing creates a MaintenanceEvent row that captures the actual work.

This page covers PM scheduling — the planned, recurring side. For unplanned breakdowns and event logging, see Maintenance Events.

Where it lives

• Create / list: Maintenance Hub at /equipment/maintenance → PM Schedule tab → + New PM Plan.
• Edit: click any schedule row.
• One-click complete: any schedule whose next_due_at is within 7 days appears on the Equipment Hub's "Today's PM Schedule" widget with an inline Mark Done popover.
• Permissions: maintenance_read to view, maintenance_write to create/edit/mark done.

The PM form

Basics

Trigger configuration

A Schedule Type segmented control picks one of three trigger modes. The fields below it change based on the choice.

CALENDAR

Recurs on a fixed time cadence.

Example: "Weekly Press Inspection" → Interval 1, Unit Weeks. After each completed event, next_due_at rolls forward 7 days.

RUNTIME_HOURS

Recurs based on the asset's total_operating_hours counter.

Example: "500hr Oil Change". If the asset is at 1023 hours and the interval is 500, set trigger_at_value = 1500. The cron checks daily; when asset.total_operating_hours >= 1500, it generates the event. On completion, trigger_at_value advances to 2000.

v1 limitation: total_operating_hours is manually updated. Until MFI/PLC integration ships, runtime-based PM is only as accurate as the meter readings the operators enter.

CYCLE_COUNT

Same pattern as RUNTIME_HOURS but counted in production cycles instead of hours. Use this when wear is more closely correlated with shots / sheets / strokes than wall-clock running time.

Tasks (checklist)

Optional list of discrete steps the technician should complete. Each row has:

• seq — display order
• label — what to do ("Inspect belt tension", "Replace filter A")
• done — checkbox the technician ticks during the event
• notes — free-text observations per step

The checklist is stored as JSON on the schedule and copied onto each generated MaintenanceEvent so the technician's checkboxes are scoped to that occurrence. Edits to the schedule's task list don't retroactively change in-progress events.

Use task lists for procedures that have multiple steps; skip them for "go inspect the thing" entries.

Notification

auto_generate_event

When true, the daily 08:00 cron auto-creates a SCHEDULED MaintenanceEvent for any schedule whose next_due_at falls within the next 7 days. When false, the schedule shows up in alerts but a human has to manually create the event from the schedule row.

Most teams want this on — it surfaces the work as a real task in the events tab rather than just an alert that gets dismissed.

One-click Mark Done

For routine PMs, the full event-logging modal is too much friction. The Equipment Hub's "Today's PM Schedule" widget gives each due schedule a Mark Done popover with just two fields:

• Optional notes (e.g. "Replaced filter; belt tension fine")
• Save

Clicking Save does all of this in one round-trip:

1. Creates a MaintenanceEvent (type PM, status COMPLETE, started_at = ended_at = now).
2. Posts an AssetTransaction of type MAINTENANCE linked to the event.
3. Updates the schedule's last_done_at to now and advances next_due_at by the configured interval.
4. Fires a maintenance_completed SSE event so the hub updates instantly.

For non-routine maintenance (root cause analysis, parts used, real downtime to record), use the full event modal — see Maintenance Events.

Cron behavior

maintenance_due / maintenance_overdue events appear in the Equipment Hub's Alerts Feed and (when configured) notify the assigned_workforce.

Setup recipe

A pragmatic starter set for a press line:

Add task checklists to the longer-running ones (full service); skip checklists for one-step PMs (daily startup).

Troubleshooting

Related

• Maintenance Events — what happens when a schedule fires (or unplanned work occurs)
• Asset Management — where total_operating_hours lives
• Equipment Hub — Today's PM Schedule widget
• Spare Parts — link parts the PM will consume