Skip to content

Downtime Log

The Downtime Log is a stopwatch. You start it when a machine stops, and stop it when the machine runs again. Everything Availability is based on comes from here.

Logging a stoppage

  1. Choose the Machine and Shift — the Shift list only shows the shift set up under Shift Mapping, picked for you automatically. The Machine list shows the machines assigned to the selected shift in your Shift settings, or every machine if none have been assigned — see Which machines appear in the Machine list.
  2. Optionally pick the Work Order being run and Logged By — the person recording it. The Logged By list shows the people rostered onto that shift, so it's a short list rather than everyone in the organisation.
  3. Add Notes if there's something worth saying beyond the reason.
  4. Click Log Downtime.

The stoppage is now running, and the page shows how long it's been going.

Because the stopwatch always uses the current moment, there's nothing to pick for the Shift Row here — Enture shows a read-only "Currently in" line naming which row the current time falls into (see A shift can have more than one row), so you can confirm you're logging against the row you expect. If the current time doesn't fall within any row, Enture says so — worth checking Shift settings if that's unexpected.

Ending a stoppage

When the machine runs again:

  1. Click Resume on the open stoppage. If it's listed in the Open Downtime panel at the top of the page, use the Resume button on that row — it opens the dialog with that machine and shift already filled in.
  2. The dialog shows a panel naming how long the stoppage has been running, with the reason selectors inside it. Reasons narrow in three steps — choose the Category, then the Subcategory it narrows to, then the specific Reason — rather than one long list, so finding the right one stays quick even once you've set up a lot of them.
  3. Add Notes if useful, then click Resume.

If the dialog offers you Log Downtime instead of that panel, it hasn't recognised the open stoppage — check that the Machine shown is the one with the stoppage running. Starting a new one won't work: Enture refuses a second stoppage on a machine that already has one open.

A reason is required to end a stoppage. That's deliberate: a stoppage with no reason still counts against Availability but tells you nothing about why, and reasons are what the Summary groups by. The list comes from Reason Codes.

One stoppage at a time per machine

A machine can only have one stoppage running at once. If you try to start a second, Enture refuses it and points you at the one already open — which is almost always the real situation: the first one was never ended.

Finding a stoppage you left open

Open stoppages are listed at the top of the page for every machine, not just the one currently selected. This matters because a stoppage you started, then navigated away from, is otherwise easy to lose track of — and it keeps counting the whole time.

The machine you have selected shows its own open entry in the main panel; every other machine's open stoppages appear in the list above it.

Tip

If a stoppage has been running far longer than seems plausible, it was probably never ended. End it with the right reason rather than deleting it — the time genuinely was lost, and deleting it just moves the problem into Availability.

Logging a stoppage you missed at the time

If a stoppage happened but nobody logged it live — a past shift that was never recorded, say — switch to Reconcile from the Log Downtime dialog instead of starting a new live stopwatch.

  1. Choose the Machine, Shift and Shift Date the stoppage happened on, and optionally the Work Order.
  2. Choose the Shift Row — which of that shift's rows the stoppage belongs to (see A shift can have more than one row). If there's only one row for that date, it's picked for you.
  3. Enture shows that row's actual start and end time for the date you picked, so you know the window you're backdating into.
  4. Enter the Start Time and End Time — these must fall within the shift row's window shown; Enture won't let you backdate a stoppage outside the row it's meant to belong to.
  5. Pick a reason the same way as ending a live stoppage — Category, then Subcategory, then Reason — and click Reconcile Entry.

Switch back to Back to Live to return to the normal start/stop flow.

Finding an entry

Search — the box beside the buttons at the top of the page searches by machine name and work order number. It narrows the entries already listed, so it works alongside the date and reason filters rather than replacing them.

Filters — the funnel icon beside Log Downtime shows or hides the filter row above the table:

  • From / To — the date range. By default the list shows the last 7 days. Both dates are inclusive, so a To date of today includes everything logged so far today.
  • Category, Sub-category and Reason — narrow to one kind of stoppage. The three narrow each other in order, and each only offers values that actually appear in the entries listed, so you can't pick a combination that returns nothing. Choosing a broader level clears the narrower ones.

Clear resets the dates, the reason filters and the search box together.

The filters apply to the table of past entries only. The Open Downtime panel always shows every stoppage still running, however the filters are set, so one can't be hidden by a filter.

Past entries

The table shows recent stoppages with their Machine, start and end times, duration, reason and notes.

Machine is listed because the table isn't limited to one machine — until you pick one, it covers every machine in the organisation.

There is no product column

A stoppage records that a machine stopped, not what it was making. The only product link is the optional Work Order picked when the stoppage was logged, so for most entries there is nothing to show — which is why the table doesn't carry an SKU column. Where a work order was chosen, the Downtime Pareto and the work order's own OEE figures are the places that use it.

Correcting a stoppage

Engineers see Correct and Delete actions on each row.

Correct lets you change the reason and the notes. Start and end times are deliberately not editable: those are what the stopwatch actually observed, and Availability is measured from them. If the times themselves are wrong — a stoppage left running for hours after the machine restarted, say — delete the entry and log it again with the real times.

Delete removes the entry entirely. Use it for a stoppage that never happened; don't use it to hide time that genuinely was lost.

Note

Because every figure is worked out from these entries rather than stored, a correction takes effect immediately and everywhere — the Summary, the work order's OEE and the job card's alike. Nothing has to be recalculated by hand.

Tip

Operators can't correct entries; only engineers can. So it's still worth getting it right at the time — start the stopwatch when the machine stops, and end it with the right reason when it restarts. Never work around a mistake with a compensating entry: that leaves two wrong entries instead of one.