Skip to content
Workflow · People · Opening soon

Machine downtime report

Export your downtime log and planned production hours from Excel, then upload both files. Mammoth totals month to date downtime by machine and reason, and calculates the share of planned production time lost for the current month to date.

Early access opens shortly. Check back soon.

Someone typed

“total machine downtime by machine and reason for the month, with the share of planned production time lost”

The agent read it as

total machine downtime by machine and reason for the month, with the share of planned production time lost, from Downtime log and Planned production hours, counting each calendar day as 24 hours, for the current month to date.

What the agent built

4 steps, each one an ordinary Mammoth step you can open and change.

  1. File
    Downtime log
    CSV export · 45 rows
  2. File
    Planned production hours
    CSV export · 6 rows
  3. Step
    Count month-to-date downtime
    Step 1
  4. Step
    Make planned machine key
    Step 2
  5. Join
    Add planned production hours
    44 of 45 paired
  6. Step
    Total downtime by machine and reason
    Step 4
  7. Result
    Machine Downtime Summary
    23 rows
  8. Schedule
    Runs when you say
    Proposed

Checked on the sample files: every step ran, 23 rows came out, and the join paired 44 of 45 rows.

What you get back

The result of that run, the rows to look at first.

Machine Downtime SummarySample data23 rows
1,080 downtime hours
MachineReasonDowntime hoursShare of planned production time lost (%)Planned production hours
cutter_01Changeover7242.9168
filler_01No material2414.6164
cutter_01Breakdown7242.9168
oven_01Changeover4827.9172
filler_01Changeover4829.3164
press_01Maintenance4828.2170
filler_01Breakdown4829.3164
oven_01No material2414172
oven_01Breakdown7241.9172
mixer_01Maintenance2414.5166
press_01Breakdown7242.4170
mixer_01Changeover4828.9166
23 rows in the result · 12 shown, problems first. Sample data: illustrative figures, not business results.

How it works

How to use the Machine Downtime Summary workflow

  1. 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and checked on the sample files.
  2. 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
  3. 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.

Machine Downtime Summary: questions

How do you build a downtime tracking report from Excel exports?
Export your downtime log and planned production hours from Excel, then upload both files. Mammoth totals month to date downtime by machine and reason, and calculates the share of planned production time lost for the current month to date.
Which Excel export should you use?
Use the exported downtime log and the exported planned production hours file. The files should include the fields needed to match machines, dates, downtime reason, and planned hours.
What happens to rows that do not match?
Rows that do not match a rule or key are not grouped into that result. They stay out of the matched totals, so you can see what needs fixing in the source export or rules.
How do you change the rules?
Edit the rule in words, such as the date window, the match fields, or the grouping level. Then run the workflow again with the updated wording.

Get early access to this workflow

It will open already built and checked on the sample files. Swap in your own exports and see your result.

Early access opens shortly. Check back soon.

Workflows like this

Match payroll to time sheets, track headcount and hiring, and see what changed since last month.

All people and payroll workflows →