Motor diagnostics

Listening to the machines

Every motor on the line is monitored continuously. SB Connect builds a behavior history so you can spot a problem before it becomes a stop.

Operating hours

Each motor's running time is counted continuously. Maintenance can be planned on real usage, not on fixed calendar dates.

Torque peaks

Mechanical effort spikes are detected and logged. Recurring peaks reveal a developing fault before it stops the line.

Current trends

Absorbed current is tracked over time. A slowly rising baseline is the early signature of wear — visible here long before failure.

From a rising current to a planned intervention

A concrete example: how SB Connect turns a slowly rising motor current into a maintenance action — and avoids an unplanned stop.

Normal operation

The motor runs steadily, absorbed current within nominal range. Nothing seems off.

T+

Trend appears

Over weeks, the baseline current creeps up by a few percent. SB Connect flags the slow drift.

T++

Threshold reached

The trend crosses the configured warning threshold. An automatic notification is fired.

T+++

Planned intervention

Maintenance is scheduled in advance, during a planned stop — instead of as an emergency repair.

Maintenance

When the line stops — capturing the why

Every time the line stops, SB Connect asks the operator one question: why? Reason codes turn raw downtime into structured information.

Field

Machine state

PLC detects the stop

running → stopped

Operator UI

Reason declaration

Operator picks the cause

from a defined list

Database

Structured event

Stop + duration + reason

stored, queryable

Typical reason categories: Defined together during deployment, aligned with your existing maintenance taxonomy.

Motor trip Power / electrical Chain break User stop Missing truck Quality hold Planned stop Other

Stop time by reason — last 30 days

Minutes by reason + cumulative %

The 80 / 20 rule

A handful of causes is responsible for the majority of stop time. Once reasons are structured, SB Connect ranks them by impact.

In this example. The first 3 causes out of 6 account for almost 80% of total stop time. Acting on those three brings the biggest improvement — the others can wait.

MTBF & MTTR — reliability and recovery

Two indicators tell you almost everything about line reliability: how often it breaks (MTBF) and how quickly it gets back up (MTTR). SB Connect computes both automatically.

A typical day on the line

Running · Stopped

MTBF — uptime

Mean Time Between Failures

The average uptime between two stops. A higher MTBF means the line runs longer before failing — a sign of reliability.

MTTR — repair time

Mean Time To Repair

The average time it takes to get the line running again after a stop. A lower MTTR means quicker recovery — a sign of efficient maintenance.

OEE — today

87.4%

OEE · Overall Equipment Effectiveness

Overall efficiency & real-time alerts

Pareto, MTBF and MTTR fit into a broader maintenance view. SB Connect logs every intervention, computes line availability and OEE, and warns you when a stop drags on too long.

Downtime reasons — Every stop is qualified by the operator with a reason code — this feeds the Pareto analysis.
Intervention log — Every maintenance action — preventive, corrective, improvement — is recorded with date, duration and notes.
Prolonged-stop alerts — When a stop goes beyond a configurable threshold, an automatic notification is fired — react before the shift is lost.

Maintenance & OEE