Runtime Parameters¶
OEE → Configuration → Runtime Parameters
Most machines already measure how long they ran — a running-hours meter, a run-time counter on the PLC. If you tell Enture which parameter that is, the Downtime Log can work out how much of a shift the machine was stopped, instead of leaving you to estimate it:
downtime = how long the shift row lasted − how long the machine actually ran
Setting it up¶
- Open OEE → Configuration → Runtime Parameters.
- Pick a shift at the top. The machines listed are the ones added to that shift (Shift settings → add machine), so you are configuring the same machines the rest of OEE works with.
- Find the machine and click Map (or Change if it already has one).
- Choose the parameter that measures its runtime. The list shows every parameter attached to that machine, with its unit.
- Click Save.
Each machine has one runtime parameter. Choosing a different one replaces the old choice — there is nothing to tidy up afterwards. Use the bin icon to remove a mapping entirely.
The unit matters¶
Runtime has to be turned into minutes to be compared against the shift, so the parameter's unit must be
a duration. Enture understands hours, minutes and seconds (hrs, hours, min, minutes, sec,
seconds, and the usual short forms).
If the unit is anything else — or blank — the screen shows a warning next to the machine, and no downtime figure will be worked out for it. Fix it by setting the parameter's unit on the parameter itself.
Why it isn't guessed
A meter reading 27000 is 7.5 hours if it counts seconds, or over three years if it counts hours. There
is no safe guess, so Enture asks rather than assumes.
What you'll see in the Downtime Log¶
Once a machine is mapped, open Downtime Log, switch to Reconcile, and pick that machine, a date and a shift row. A panel appears above the time fields, led by the one figure you can act on — how many minutes of that shift row are still unexplained — with a Fill in start & end button beside it.
Below that, a bar shows where the shift row actually went, to scale:
| Ran | What the meter says the machine was running for |
| Already logged | Downtime you have already recorded for that row, with the number of entries |
| Unexplained | What is left over — the figure above |
The three add up to the length of the shift row, which is stated at the right-hand end. So you can see at a glance whether a shift was mostly running, mostly stopped, or mostly unaccounted for, without doing the subtraction yourself.
Fill in start & end puts those minutes into the Start and End time fields — you still choose the reason code and save.
The panel only appears in Reconcile mode. In Live mode you are timing a stoppage as it happens, so the shift row isn't finished and there is no settled figure yet.
Why it doesn't just create the entry¶
A shift's downtime is usually several separate stoppages with different causes — a changeover, a breakdown, a material wait. Recording 75 minutes as one unexplained block would be worse than what you would have typed yourself. So Enture works out the number and fills in the times; the reason stays your call.
You can click Fill in start & end more than once. Each click starts from the end of what is already logged, so you can split the time across several entries with different reasons — and the bar's Already logged segment grows as you do.
When no figure is shown¶
The panel explains itself rather than showing a misleading zero:
| What it says | What it means |
|---|---|
| No runtime reading for this shift row yet | The meter has no data for that row — usually the shift hasn't been processed yet |
| The unit can't be read as a duration | Fix the parameter's unit (see above) |
| The meter went backwards | The counter reset or rolled over mid-shift, so the reading can't be trusted |
| More runtime than the shift row is long | The meter and the shift disagree — nearly always the wrong unit |
If the machine has no runtime parameter mapped at all, no panel appears and the Downtime Log behaves exactly as it always has. Mapping one is optional — you can always log downtime by hand.
Letting Enture log it for you¶
Once machines have runtime parameters mapped, you can go a step further and have Enture record the unaccounted downtime itself, once a day, without anyone clicking Fill in start & end. See Automation — it uses exactly the figure described above, and needs a reason code chosen in advance to stamp on what it generates.