Skip to content

Report a shutdown

Report an equipment or line shutdown — planned or emergency — from the field.

Required role

Technician, Mapper, Admin, PegotecUser (any mobile-enabled role with mobile.shutdown.report).

Overview

A shutdown report records that production has stopped or is about to stop on an asset or line. It's distinct from a repair request:

Situation Action
Something is broken but the line still runs Repair request
Line is stopped, or will stop imminently, or safety engaged Shutdown report (this page)
Both — broken equipment caused a line stop Both (shutdown report first, then repair request for the fix)

Shutdown reports go to Supervisors and Admins in real time. They feed the Shutdown Report, Asset Availability, and OEE reports — shutdown data is the single most important input for those metrics.

Prerequisites

  • You're at (or near) the affected equipment.
  • You know — or are able to identify — the reason for the shutdown.

Steps

1. Open the shutdown form

  1. Three-dot menu inside the task.
  2. Tap Report shutdown.
  3. The form pre-fills with the asset you're working on.
  1. Open the asset in the hierarchy browser.
  2. Tap Report shutdown.
  1. Menu → Shutdown.
  2. Tap Select asset to pick the affected equipment, or scan its NFC tag / barcode.

2. Fill in the form

Field Required Notes
Asset / Line Yes Scope — a single asset, or the whole line.
Reason Yes From the master list of shutdown reasons configured by your Admin.
Start time Yes When the shutdown began. Defaults to now but can be back-dated.
End time Optional Leave blank if still ongoing. Fill in later when production resumes.
Description Yes What happened. Specific: "Line 3 tripped on overload at conveyor 2, unclear cause, maintenance en route."
Priority / severity Yes Low / Medium / High / Critical. Most shutdowns are Medium or higher.
Photos Recommended Photos of the symptom, any warning lights, the affected area.
Safety concern? Yes / No If yes, prompts for additional safety details.

3. Priority guidance

Severity When to use
Low Minor stop, resolved quickly, no production loss worth flagging. Rare to use — if it's this low, consider a repair request instead.
Medium Production slowed or paused briefly. Routine recovery.
High Significant production loss expected. Customer commitments at risk.
Critical Safety incident, major equipment damage, extended outage anticipated. Escalate verbally and via the shutdown report.

Don't report casually

Shutdown reports drive OEE and capital-planning decisions. Reporting a 30-second stop as a 3-hour shutdown distorts the data. If you're not sure, note the actual observed stop time and let the Supervisor adjust.

4. Safety flag

If you tick Safety concern, additional fields appear:

  • Hazard type — electrical, chemical, mechanical, fall, etc.
  • Personnel affected — number of people who were in the area.
  • Injuries — yes / no, with details if yes.

Safety-flagged reports fan out immediately to the safety officer, Admin, and all Supervisors.

5. Photos

Strongly recommended. Specifically useful:

  • The warning light or alarm message.
  • The visible symptom (leak, smoke stain, tripped breaker).
  • The affected equipment in its stopped state.

See Photos and attachments.

6. Submit

Tap Submit.

  • Online: the report uploads immediately; your Supervisor receives a push notification within seconds.
  • Offline: queued in the outbox; uploads as soon as connectivity returns.

Don't wait for signal to submit a critical shutdown

Submit anyway. The app queues locally and escalates verbally while the upload is pending. If the report is critical and you're offline, also radio or call your Supervisor in parallel.

Updating a shutdown you submitted

Shutdowns are often open for hours. Update as facts change:

  1. Menu → Shutdowns → Mine.
  2. Open the one you submitted.
  3. Tap Update. Add notes, new photos, or set the End time when production resumes.
  4. Save.

Updates are visible in real time on the Supervisor's dashboard.

Closing a shutdown

Technicians can submit updates; only Supervisors and Admins mark a shutdown Resolved in the web portal. Your job from the field is to report accurately and keep the report current until someone closes it.

Relationship to repair requests

A shutdown and a repair request often go together:

  • The shutdown records that production stopped and for how long (feeds OEE).
  • The repair request records what needs to be fixed (feeds the maintenance backlog).

For the same incident, file both. They'll be cross-linked in reports.

Planned shutdowns

If you're shutting down intentionally for maintenance:

  • A Supervisor or Admin usually creates the shutdown on the web portal before the stop.
  • As the technician performing the work, you execute your tasks as normal.
  • The web portal flags the window as planned on the Shutdown Report so it doesn't inflate unplanned-downtime metrics.

If you need to report a planned shutdown from mobile (because nobody set it up in advance), set Reason to "Planned maintenance" and add a clear note.

Things to watch for

Report once, update often

Don't submit three shutdown reports for the same incident. File once. Update as facts change. Duplicate reports corrupt the OEE report.

Note the starting point exactly

If you're unsure when the line actually stopped, ask the operator. A ten-minute error on start time ripples through weekly and monthly OEE numbers.

End time matters more than you think

Forgetting to update the end time when production resumes leaves the shutdown apparently open for days. Supervisors follow up, but you can save everyone time by closing the loop from the field.

Common patterns

Emergency shutdown (line tripped)

  1. Ensure immediate safety — engage lock-out if needed, radio the line lead.
  2. Raise the shutdown report — priority Critical or High depending on cause.
  3. While the response team works, take photos.
  4. Raise a repair request for the underlying cause.
  5. When production resumes, update the shutdown with the end time.

Safety incident

  1. Immediate response per your site's safety protocol.
  2. Shutdown report with Safety concern ticked.
  3. Photos of the area (not of injured people).
  4. Critical priority.

Short technical stop

  1. Shutdown report, priority Low or Medium, start and end time.
  2. Optional repair request if there's underlying work to do.

Troubleshooting

Problem Fix
Can't submit — required field missing Check asset, reason, start time, description, priority are all filled
"Reason" list missing an option Ask your Admin to add it to Master data
Report submitted to wrong asset Open in Shutdowns → Mine and update
Supervisor didn't receive notification Check with them directly if Critical; otherwise their dashboard has the real-time feed