Skip to content

Shutdown Reasons

The master catalogue of causes that technicians pick from when reporting a shutdown.

Required role

Mapper or Admin.

Overview

When a technician reports a shutdown from the mobile app, they choose a reason from a dropdown. This page manages that dropdown.

Shutdown reasons drive the Shutdown Report, Asset Availability, and OEE Report — getting the taxonomy right directly affects the quality of those reports.

Open the page

Configuration → Safety Standards → Shutdown Reasons.

The table shows:

Column Meaning
Label Display name on the mobile dropdown.
Category Planned / Unplanned / Force Majeure / Other.
Active On / off toggle.
Usage count How many shutdowns in the last 30 days cited this reason.

Create a reason

  1. New shutdown reason.

  2. Fill in:

    Field Notes
    Label Concise. "Equipment failure", "Planned maintenance", "Power outage".
    Category Planned (pre-arranged maintenance, change-over), Unplanned (breakdowns, safety stops), Force Majeure (utility outages, external supply issues), or Other.
    Description (optional) Help text.

  3. Save.

Category matters for OEE

The category you assign drives whether the shutdown counts against availability:

  • Planned → excluded from unplanned-downtime metrics. Availability unaffected.
  • Unplanned → counts against availability. Drives the main OEE signal.
  • Force Majeure → often excluded from operational metrics (your installation's OEE Report may handle this differently).
  • Other → counts toward unplanned unless configured otherwise.

Miscategorising a reason (marking "Equipment failure" as Planned, for example) hides real downtime. Review quarterly.

Edit, deactivate, delete

Same pattern as Repair Request Types.

Good catalogue design

  • Short labels — fit on mobile.
  • Clear categories — when in doubt, Unplanned.
  • 10–20 reasons total — cover 95% of real shutdowns.
  • "Other" present but watched — >10% usage means your catalogue is missing common reasons.

Typical starter catalogue

For a new installation:

Label Category
Equipment failure Unplanned
Safety trip Unplanned
Tooling change Planned
Planned maintenance Planned
Quality issue Unplanned
Material shortage Unplanned
Power outage Force Majeure
Change-over / product changeover Planned
Operator absence Unplanned
Other Unplanned

Tune from actual usage patterns in the first 1–2 months.

Things to watch for

Don't relabel historical shutdowns via category changes

Changing a reason's category changes how new shutdowns are attributed. Historical shutdowns stay with the category they had at reporting time unless you re-run them (which is a support escalation).

Planned shutdowns are usually logged on the web

Most planned shutdowns are created by a Supervisor on the web portal before the stop. Technicians use the mobile reason list primarily for unplanned events.