Hardware. Firmware. Software. One engineering partner.Based in India · Working worldwide   Deutsch ↗
iTechGeeks engineering

Measure where the time and the energy actually go.

Measured machine availability, downtime reasons, utilisation and energy consumption per asset, built from real equipment data rather than from what the schedule assumes.

Two questions most operations cannot answer precisely

Where did production time actually go last week, and which assets consumed the energy. Both are usually answered from the schedule, from memory or from a spreadsheet maintained by someone who has other work to do. Measured answers are frequently different from assumed ones, and the difference is where the opportunity sits.

OEE, and what it hides

Overall Equipment Effectiveness combines three factors: availability, how much of the scheduled time the machine was actually running; performance, how close it ran to its capable rate; and quality, how much of what it produced was good.

The single OEE number is useful for tracking a trend and almost useless for deciding what to do, because three very different problems produce the same figure. A machine stopped half the time and a machine running constantly at half rate can report identically. The value is in the components and, more than that, in the reasons behind them.

A caution about benchmarks. Published OEE figures for “world class” performance are widely quoted and rarely comparable, because they depend entirely on what was counted as scheduled time and what was excluded. Your own trend against your own definition is worth far more than a comparison against someone else’s number.

What gets measured

  • Run state. Whether the machine is running, idle, stopped or in changeover, derived from motor current, cycle signals or controller data.
  • Cycle timing. How long each cycle takes, and how that distribution changes over a shift.
  • Downtime and its reasons. Duration is easy to measure automatically. The reason usually needs a quick operator input, and the system stands or falls on whether that input takes seconds rather than minutes.
  • Energy. Consumption per asset, per shift and per unit produced, measured at the supply.
  • Idle draw. What equipment consumes while producing nothing, which is often a surprise and often addressable without capital spend.

Energy monitoring specifics

Energy is frequently the easiest place to start, because it can be measured entirely externally with current clamps at the panel, requiring no cooperation from the machine and no change to the process.

What makes it useful is not the total, which the utility bill already provides, but the breakdown: which assets, which shifts, which products, and what is drawn when nothing is being produced. Energy per unit produced is usually the number that changes behaviour, because it connects consumption to output rather than to the calendar.

Whether operators will use it

These systems fail for human reasons more often than technical ones. If logging a downtime reason takes a minute, it will not happen during a bad shift, which is exactly when the data matters most. If the display is in an office rather than on the floor, it informs nobody who can act.

So the design questions that matter are how reason codes are entered, how short that interaction can be made, who sees the result and where, and whether the numbers are used to improve the process or to judge the people operating it. The last of those determines data quality more than any technical decision.

How we help

  • Scoping. Which assets to instrument, based on what their downtime and consumption actually cost.
  • Measurement design. What to sense and how, whether from the controller or externally. See sensor selection and signal conditioning.
  • Retrofit installation. External sensing on equipment that offers no interface. See legacy machine retrofit.
  • Data collection. Gateways, connectivity and storage sized for the rate you are committing to.
  • Reason capture. A floor interface fast enough that it gets used under pressure.
  • Dashboards and reporting. Views for the floor, for supervision and for management, each showing what that audience can act on. See cloud and dashboards.
  • Integration. Into MES, ERP or maintenance systems where the numbers need to join existing reporting. See SCADA and PLC integration.

What we will not claim

We will not quote an expected percentage improvement before seeing your operation. Figures of that kind are marketing rather than engineering. We will agree measurable criteria for a pilot and report against them honestly, including where the data showed less opportunity than hoped.

What you receive

Installed measurement, the collection and storage system, the dashboards and reports agreed in scope, integration into your existing systems, and documentation of exactly how each figure is calculated, so the numbers can be trusted and questioned.

Start a conversation

What would you measure first?

Tell us what the equipment is, whether you currently track downtime or energy at all, and what decision you would make differently if you had the numbers.

Prefer email? Write to info@itechgeeks.in

Common questions

What clients ask before starting

Is a single OEE number useful?

For tracking a trend, yes. For deciding what to do, not much, because three very different problems produce the same figure. A machine stopped half the time and one running constantly at half rate can report identically. The value is in the components and the reasons behind them.

Can you measure energy without modifying our machines?

Usually yes. Current clamps at the supply panel measure consumption externally, requiring no cooperation from the machine and no change to the process. This makes energy one of the easiest places to start.

How do you capture the reason for a stoppage?

Duration is measured automatically; the reason normally needs a short operator input. The design question that decides whether it works is how few seconds that interaction can be made to take, because a slow interface will not be used during the bad shifts when the data matters most.

How much improvement can we expect?

We will not quote a percentage before seeing your operation, because figures of that kind are marketing rather than engineering. We agree measurable criteria for a pilot and report against them honestly.

Should we compare our OEE to industry benchmarks?

With caution. Published figures depend entirely on what was counted as scheduled time and what was excluded, so they are rarely comparable. Your own trend against your own consistent definition is worth considerably more.