Use casesMachine downtime log

Build your machine downtime log.

Record machine stops, restarts and reviewed downtime reasons in one log.

How to build your machine downtime log

  1. Describe the job

    Record machine stops, restarts and reviewed downtime reasons in one log.

  2. Review the first version

    Choose how the production planner records the machine and how the engineering reviewer reviews the next step.

  3. Refine the views

    Ask First to adjust the fields and views for the people who will use the app.

  4. Test before sharing

    Walk through the process with a sample record and check who owns the next action.

A machine downtime log example

A restart time is earlier than the recorded stop.

Illustrative workflowMachine downtime log

Machine downtime log example

Record
Machine downtime log · 01
Owner
Production planner

Current stage · Production planner

Open the work record

A restart time is earlier than the recorded stop.

Read the full walkthrough
  1. Open the work record

    A restart time is earlier than the recorded stop.

    Record:
    Machine downtime log · 01
    Owner:
    Production planner
  2. Review the required input

    Flag the inconsistent timestamps and request correction before calculating a downtime total.

    Stage:
    Review pending
    Owner:
    Engineering reviewer
  3. Record the next production action

    Keep an unverified duration separate from the reported stop and restart times.

    Next action:
    Keep an unverified duration separate from the reported stop and restart times.
    Owner:
    Stores coordinator

What to include in your machine downtime log

  • Keep the machine in context

    Keep machine, reported stop, reported restart, reason source, review owner and verified duration together so the next person can understand the request or record.

  • When the next step needs a decision

    A restart time is earlier than the recorded stop. Flag the inconsistent timestamps and request correction before calculating a downtime total.

  • Keep verified duration visible

    Keep an unverified duration separate from the reported stop and restart times.

  • Choose what each person needs

    Give the production planner a working view and the engineering reviewer a review view. Keep machine and reported stop attached to the decision as the work moves between them.

Questions about machine downtime log

Start with machine, reported stop, reported restart, reason source, review owner and verified duration. Describe who enters the information and who reviews the next step.

Build your machine downtime log.

Start with your workflow and make it yours.

Get started