Loom and Machine Monitoring

Watch machine state across the floor and surface stoppages and faults as they happen.

What It Does

The agent reads controller and historian signals from every machine on the floor and alerts the floor team the moment one stops or reports a fault. Each event is written to the downtime log with its start time, duration, and fault code, attributed to machine and shift so the loss can be reconstructed later.Without it: Stoppages go unnoticed until output drops, and the cause is hard to reconstruct after the fact.

Planned changeovers and breaks are separated from unplanned stops
A stop arriving with no fault code is logged unattributed for a supervisor to code
A machine that stops reporting is flagged as signal loss, not as running
Micro-stops under the alert threshold are counted, not paged

Illustrative example

Loom 27 drops out mid-run at 11:42 with fault E-114, warp stop. The alert reaches the floor team and the downtime log opens an entry against loom 27 on B shift, holding the clock until the loom restarts at 11:58. The supervisor finds a 16-minute unplanned stop already coded to E-114 and adds the cause note.

Reads

Machine controllers

Stop, start, fault codes

Historian

Machine state signals

MES

Run, shift, changeovers

Downtime log

Open stop entries

Runs

Loom and machine monitoring

Watch