Traceable Quality®
Talk to us
Menu

Insight

QR first, RFID where it pays

Full batch genealogy on a production floor with a label printer and the phones you already have, and the three places it breaks, which is where RFID starts.

A crate of steel strip comes in at receiving. The mill certificate says heat 2318. Before anyone moves it, someone prints a label with a QR code that says batch 2318 and sticks it on the crate.

At cutting, the operator scans it with his phone. That scan is one line: batch, step, time, who. At bending he scans it again. Then plating, inspection and packing. Five scans, five lines.

A label printer and the phones on the floor buy you full genealogy. Someone still has to scan.

Six weeks later a customer rejects a bracket. You scan the carton and the lines come back in order. Which coil, which press, which shift, which plating bath. And every other carton that came off the same coil, so you can hold them before they ship too.

That’s genealogy. Most plants that want it think they need RFID to get it. They don’t.

What it costs

A desktop thermal label printer of the TSC TE244 kind lists at about ₹11,000 to ₹18,000 in India, depending on the seller and whether GST is in. Call it twelve thousand. A printed paper label is well under a rupee. The phones are already in your people’s pockets, and every one of them reads a QR code with the camera app.

A QR code isn’t the only choice. A DataMatrix holds the same batch number in a smaller square, which matters on a small part or a narrow tube, and phones read those too. On a crate or a job card, a QR code is fine.

The phone has to send the scan somewhere. For one line and a handful of batches, the code can open a form and the form can fill a sheet. Past that you want something that knows your steps and refuses a scan out of order. That part is software, not hardware, and it’s the same software whether the scan comes from a phone or a reader.

So where does it break?

Someone has to scan.

On a busy night shift a step gets skipped. Nobody notices, because the parts are fine. The record now has a hole, and it’s exactly where you’ll need it the day a customer calls. A scan that depends on someone remembering is a scan that sometimes doesn’t happen.

One at a time.

Forty crates on a dispatch pallet is forty scans. The ones at the front get done. The one at the back, wedged against the next pallet, is the one that gets missed. At forty that’s an annoyance. At four hundred it’s a job.

The code has to be seen.

A camera needs a clear view of the label. Under cutting oil, behind a stack, on the side facing the wall, or painted over at the plating line, the code is gone. A torn corner is fine; QR codes carry error correction for that. A label you can’t see isn’t.

That’s where RFID starts

Those three are the same three cases part 2 makes for RFID, turned around. No line of sight. Many at once. Nobody scanning. A UHF tag answers through cardboard, a reader hears a pallet of them in one pass, and a reader on the dock door counts what goes through without anyone lifting a phone.

It costs more. A plain paper UHF label runs ₹5 to ₹8 in India at volume, and an on-metal tag for a die or a steel crate is closer to ₹60. Then there are the readers. So spend it at the step where the scanning breaks, and leave the QR label everywhere it doesn’t.

Most plants have one or two of those steps, not ten. Dispatch, often. A wash or paint line, sometimes. Start with the label everywhere, watch where the holes in the record turn up, and put a reader there.

The label designer draws a batch label for a Zebra, TSC or Datamax printer and writes the printer code for you. Bind the batch number to a field and one design prints every batch. If you only need the code itself, to paste onto a job card template you already have, the QR code generator makes one and lets you download it.

For what else goes on the label, see choosing the right label for your product. For why a QR code survives a torn corner, see how QR codes work.

Heat 2318 is a made-up number. Your first real one is probably on a mill certificate in a file somewhere, waiting for a label.

Next step

Tell us what you are trying to trace.

Describe the flow: what arrives, what happens to it and what leaves. We will tell you what it takes to capture it.