Skip to content

Shutdown maintenance

Plan the work that should happen while equipment is stopped — repairs you've chosen to defer to the next shutdown, and maintenance tasks that can only be done during a stop. A shutdown becomes a work container: you decide what work it carries.

Required role

Supervisor or Admin manage the shutdown work list and defer repairs. Technicians perform the work from the mobile app.

The two ideas

Concept What it is
Defer to next shutdown A non-urgent repair on a machine you don't want to stop now. Park it; it waits for the next planned shutdown of that machine/line.
Shutdown task A recurring task that can only be done while the equipment is stopped (internal inspection, alignment, overhaul). It never appears on the normal calendar — it's pulled into a shutdown when you activate the plan.

Both come together in a shutdown's work list: the set of work to perform during that stop. Activating the plan is your choice — a short shutdown can carry no extra work at all.

Defer a repair to the next shutdown

When a repair request doesn't warrant stopping the machine now but should be fixed at the next opportunity:

  1. Open Reports → Repair Request Report.
  2. Find the request. Alongside Convert to Work Order and Dismiss, click Defer to Shutdown.
  3. The request leaves the open queue, its status becomes Deferred, and it is tagged to its machine's line/asset.

The deferred request now waits in the backlog. Filter the report by Status → Deferred to see everything parked. To pull a request back out, it returns to the open queue automatically when you un-defer it (or it's picked up by a shutdown).

Let criticality guide you

Set an asset's criticality (Mapping → asset editor) to critical / important / standard / minor. It's a reminder of which faults are safe to defer and which need fixing now — shown next to deferred items in the work list.

Set up a shutdown-only task

For work that requires the equipment to be stopped:

  1. In Mapping, open the task point and add or edit a task.
  2. Turn on Shutdown task (only during shutdowns).
  3. Optionally set Ideally every N shutdowns (e.g. an overhaul every 3rd stop) — a hint shown when you build the work list; it isn't enforced.
  4. Save.

The task immediately drops off the normal calendar. It will only ever appear in a shutdown's work list.

Activate a shutdown's maintenance plan

When you create or open a planned shutdown (Shutdowns):

  1. On the Shutdowns page, click the clipboard (Manage maintenance plan) button on the shutdown's row.
  2. The Shutdown Work List opens. It has two parts:
    • In this shutdown's plan — work already pulled in. Remove any pending item with the ✕ button.
    • Available to add — the candidate shutdown tasks for this scope (with a "last done" hint) and deferred repairs targeting it (with criticality and how long they've been waiting).
  3. Tick the items you want, then click Add selected to plan.

The chosen work is scheduled inside the shutdown window. For a short shutdown, simply add nothing.

You're in control

Nothing is pulled in automatically. The person planning the shutdown decides exactly what work it carries, and can add or remove items any time before or during the stop.

What the technician sees

Once activated, each work item appears in the assigned technician's task list in the mobile app for the shutdown days, marked with a Shutdown work badge. They perform it exactly like any other task. Shutdown work is kept out of the normal calendar-compliance and overdue counts, so it never distorts on-time metrics.

When the shutdown ends

  • Work that was done is recorded normally and shows in the Shutdown Report.
  • A shutdown task that wasn't done is set aside (not counted as overdue) and becomes due again at the next shutdown.
  • A deferred repair that wasn't done returns to the backlog, ready to be pulled into a later shutdown.