See the defect before the guest does.
Industrial cameras over the ironer or folder. Stains, holes and marks, classified at line speed, the way your laundry works.
Book a demoThreadscan
Quality control over the ironer line.
A custom gantry sits on the finishing line. Cameras and lights inspect every piece as it passes, without slowing the plant.
01 · Detection
Defects, classified the way your laundry works.
Stains, holes, marks. Threadscan scores what it sees against your categories and thresholds, not a generic demo set. Near-misses stay visible when you want them.
02 · Fit
Width built around the folder, not the other way around.
The frame spans about 3700 mm to 4600 mm. Legs and extension bays slide so the same design fits most flatwork ironers and folders. Watch it run out to maximum width.
03 · Optional RFID
Read the piece as it passes through the line.
Optional antennas turn the portal into a read zone. Tag the linen as it runs the ironer, then join that identity to the defect record in Threadscan.
04 · Line
The same cameras time the line.
Producing hours, stoppages and utilisation, not just defects. When the line pauses, you see it.
See how a laundry improved efficiency by 13.5% when they turned on Threadscan. Case study
What it does
A camera over the ironer that stops a bad product reaching the hotel.
Threadscan sits on the finishing line. It looks at every piece, names the defect, and tells the folder where to eject it, so the pack that leaves the plant is the one you meant to send.
-
01
Fed through the ironer
The product leaves the ironer on the finishing belt. No extra handling, no slower line speed.
-
02
Defect detected
Cameras and lights on the Threadscan gantry inspect every piece as it passes underneath.
-
03
Type classified
Threadscan decides what it is (stain, hole, mark) against the classes and thresholds you set.
-
04
Folder ejects the product
A signal goes to the folder. The defective piece is dropped at the lane you configured.
-
05
Remedial treatment
That piece goes to rewash, rag-out or repair. It does not go into a hotel pack.
Clean pieces stay on the belt and stack as usual. Only the product Threadscan rejected leaves the line at the eject, ready for rewash, rag-out or whatever treatment you run.
The console
The camera sees the product. The console is where the plant runs quality.
Every detection, stoppage and tag read lands in Threadscan. Review, measure, train and deploy from one place, or pull the same records into the systems you already run.
Operators do not have to guess what the camera saw. The defect gallery shows the full product, the class, a confidence score and when it ran, filterable by facility, machine, date and near-misses.
- · Flag a false call so it does not train the next model
- · Find similar detections across the day
- · Queue confirmed examples into labelling and datasets
Line statistics
Pieces, utilisation and why the belt stopped.
The same cameras that score defects also time the line: feeding gaps, machine stops and power-off, against the gap you call ideal.
Statistics splits into Pieces, Utilisation and Defects. Filter by organisation, facility, machine and date. Chart settings set the time window and the ideal gap (for example 500 mm = 100%).
- · Feeding gaps: belt running, unfed for more than 60 seconds
- · Machine stops and power-off hours
- · Average, longest and shortest gap between pieces
What a plant measured
Quality credits down. Same output in fewer hours.
Observational results from one finishing plant after Threadscan and line reporting were live. Not a guarantee. You can request the case.
−23.6%
Product credit rate
Credits ÷ delivered products, on vs off period.
+13.5%
Pieces per producing hour
Same plant, after line reporting went live.
9 hrs
Fewer producing hours
Comparable piece volume across five-day windows.
Closed loop
The model should get better on your floor, not a stock set.
Label, train and deploy stay in the same console the quality team already uses.
01
Label
Confirm or correct detections on your linen and lighting.
02
Dataset
Build plant-specific examples, not a generic demo set.
03
Train
Run a new model in the trainer, then inspect evaluation.
04
Deploy
Push the model to edge devices on the ironer or folder.
Optional
RFID when you need to know which item it was.
Vision tells you what was wrong. RFID tells you which piece it was. Antennas on the portal read the tag as the product passes, then Threadscan joins that identity to the defect record.
Each pass records the EPC, the device, first and last seen, and the linked stock item and customer from Bundle. Open a tag to see its full history. If a tag shows up on many different item sizes, Threadscan flags it as a possible stray.
Open data
Threadscan is not a dead end. Your other software can read it.
Detections, line statistics and RFID sit in one system. They also leave it. Laundry management apps, ERPs and plant software get the same records through the Threadscan API.
Quality
Detections, classes, confidence, near-misses and review flags. Push a reject into the LMS the same way the folder already heard it.
Production
Pieces, utilisation, feeding gaps, machine stops and power-off. Let the ERP see the line, not a spreadsheet the next morning.
Identity
RFID passes, EPCs, Bundle item and customer master data, first and last seen. Join the piece to the hotel account you already bill.
No second login for the quality clerk. No re-keying rejects into the LMS. If a system can call an API, it can see what Threadscan saw.
Next step
Want the API in the walkthrough?
We will map detections, production and RFID to the laundry systems you already run.