A customer rings about a cracked bracket. They want to know which other brackets came from the same steel.
Say you make them. Mild steel bar arrives from the mill in bundles, each with a heat number on its test certificate. The bar gets cut, pressed, drilled and plated, and the brackets leave 200 to a crate. The question on the phone is short: which crates, sent to which customers, had brackets from heat 4471?
If you can answer that in ten minutes, you already know what you’re tracking. Most plants find out they don’t at about this point.
Pick the unit before the tag
“Traceability” gets said as if it were one thing. On a floor it’s at least three, and they behave differently.
The item is one bracket. Serialise it and you can follow that exact piece for its whole life. It’s also the most expensive answer, because every piece needs a mark and every mark needs reading.
The batch is everything made together from the same inputs: one heat of steel, one shift, one plating run. Recalls happen at this level. Nobody recalls a bracket. They recall the lot.
The container is the crate, bin, carton or pallet the stuff moves in. It’s what actually crosses your floor and your dock, so it’s the easiest thing to read. It also knows nothing about what’s inside it until somebody records that.
Most plants need two of these. A bracket maker probably tracks the batch and the crate and never marks a single bracket. A pump maker serialises every pump, because the warranty is per pump. Neither is wrong. They both answered the question before they bought anything.
So what’s the smallest thing you’ll need to name when the phone rings? That’s your unit. Everything below it can stay anonymous.
A tag answers one question
Put a UHF RFID label on that crate. What does it tell you?
Which crate it is. That’s all.
It doesn’t know there are 200 brackets in it, or 187 because QC pulled a few. It doesn’t know they’re from heat 4471. It doesn’t know it’s at the packing table, or that it left at ten past four on a truck to Pune.
A record you can trust needs three answers: which thing, how much of it, and where, when and for what. I’ve written about that before as Identity + Quantity + Context = Truth. The tag supplies identity. Quantity comes from a count or a scale. Context comes from where the reader is, when it heard the tag, and which work order was open at the time.
Automate the identity, leave the other two to someone with a pen, and you’ve spent money making the easy part automatic.
The number on the chip
What a reader hears from a tag is its EPC, the electronic product code. On most tags it’s 96 bits, which the reader shows you as 24 hex characters. There’s a standard way to lay those bits out, and a later issue takes one apart. For now the point is smaller.
It’s a number.
A plain UHF label costs ₹5 to ₹8. The chip on it has no battery and a few hundred bits of memory. The heat number doesn’t live there. Neither does the drawing revision, or the customer’s PO. Those live in software, in a table that says this EPC is crate 112, packed at 3:40 with 200 brackets from lot 2611-04, which was cut from heat 4471.
That table is the traceability system. The tags are how it gets told something happened without anyone typing it.
A tag nobody’s table knows about is a ₹6 sticker.
Where the rows come from
Each row gets written at a moment when two things meet.
Bar from heat 4471 is issued to the cutting job: a batch meets a work order. Brackets go into crate 112: a batch meets a container. Crate 112 goes through the dock door: a container meets a shipment.
Miss one of those moments and the chain breaks quietly. The crate still reads perfectly at the door. The software still shows a shipment. It just can’t say what was in it.
So walk the floor with a notebook and list the meetings. Every place where one thing goes into another, or one thing becomes another, is a place the system has to hear about. Whether it hears through a tag, a QR code or a person tapping a phone is the How question, and that comes later in the series.
One thing about range, because it bites here. A fixed reader’s spec sheet will say about 15 metres. On a real floor, with steel racking and people walking about, plan on 5. That’s plenty for a dock door. It’s also enough to hear the crates waiting on the packing table beside the door, so “which reader heard it, and should it have” is context the software has to get right too.
The crate will read every time. Whether it can tell you about heat 4471 depends on a row somebody wrote at the packing table.
The film: a tag with no battery
Part 1 of our RFID series is 80 seconds on how that number gets from the tag to the reader at all.
The tag has no battery. The reader sends out a steady wave at around 866 MHz and the tag’s antenna catches a sliver of it, enough to wake the chip. The chip has nothing to transmit with, so it switches its antenna between two states and the reflection flickers. The reader listens for that flicker while it’s still shouting.
In India the reader gets four channels between 865.7 and 867.5 MHz and up to 2 W ERP, under the 2021 rules (G.S.R. 853(E)). With a typical 6 dBi antenna that works out to about a watt from the reader into the antenna cable. Very little of it reaches the tag.
So a tag stops reading for one of two reasons. Not enough power reaches the chip to wake it, or it wakes and the reader can’t hear the reply. Whichever comes first is your range.
Try it: Wake the tag
Wake the tag puts a tag in front of a reader and lets you drag it away. Pick the chip, the reader and the power, and watch which link gives out first. The numbers are for free space, so knock 30 to 40% off for a real room.
For the question this issue is really about, the 5W2H requirements builder has six questions under What, including your unit of traceability and what’s missing or wrong in your ERP today. Answer those before anyone quotes you for readers.
Case study: at Sterlite Copper, the unit was the pallet
Sterlite Copper takes in blisters, ingots and imported cathodes on pallets, in bags and in bundles. For years the record of what went into a furnace was a security guard’s notebook and an operator’s, typed into SAP at the end of the day.
So the pallet is what they track. Each one carries an RFID tag. At receiving, a scale and a reader capture the weight and the tag together and the goods receipt posts to SAP. After that, fixed readers by the road hear the pallets as the forklift drives past, and every transfer posts itself.
Nobody keys anything in. Imported cathodes can still be traced to their supplier, and finished goods are tagged too, so a finished product traces back to the pallets it started as.
Raw material to finished goods at Sterlite Copper
Hardware update
Whichever unit you pick, something has to hear its tag. Our RFID reader is one platform ordered four ways. Long Range has a 9 dBi antenna for dock doors and gates, and it’s what you’d put by the road for forklift traffic. Short Range has a 3 dBi antenna for a desk or a point of sale. USB Desktop is the same engine in a 90 mm box on a bench. Multi-Antenna adds four switched ports, so it can tell which way a crate went through a wide opening.
It’s the same read event from all four, so the table behind it doesn’t care which one heard the tag.