A pallet of 40 cartons goes out through a dock door. It’s in front of the reader for about four seconds.
The reader doesn’t report “40 cartons went out”. It reports this tag, this antenna, this signal strength, this millisecond. It does that every time it hears a tag, and in our simulated pass that came to 3,028 rows.
Nobody wants 3,028 rows in the ERP.
Why so many
A tag in the field gets read over and over. The IoTReady reader can report up to 700 tags a second, and Impinj rates the E710 chip it’s built on at anywhere from 50 to more than 1,000 a second depending on reader mode. Nothing on a dock moves that fast. In the demo each carton is reported between 43 and 99 times in one pass, and that’s the reader working properly.
The standard reader protocol is built the same way. GS1’s LLRP has the reader send tag reports as it goes, each with a timestamp in microseconds. Our reader sends JSON with milliseconds. Neither of them decides what a pallet leaving means. That’s somebody else’s job, and if you don’t do it at the edge, it lands in the ERP.
Four things
Filter. Drop reads below a signal floor. Drop reads from antennas that face somewhere else. In the demo, a tagged carton sits on a staging shelf all day, in view of antenna 2, and a parked pallet behind the door throws the odd faint read at antenna 1. With a floor of -65 dBm and antenna 1 only, 2,859 of the 3,028 rows survive.
Deduplicate. The same tag inside two seconds is one sighting. That takes it down to 40.
Aggregate. One line per tag: first seen, last seen, how many reports, how loud at best. The count is worth keeping. A tag reported 99 times went through the middle of the door. One reported 43 times was fainter the whole way.
Decide. The gate is open from the first read. When nothing has been heard for three seconds, whatever was seen is gone, and that’s the event. In the demo it closes at 6.4 seconds.
What leaves
One record. In EPCIS 2.0 it’s an ObjectEvent: a list of 40 EPCs, an event time, a read point and a business step, shipping. EPCIS describes every event along five dimensions, what, when, where, why and how, and this one fills in the first four. An ERP connector turns it into a delivery note.
The settings are where it goes wrong
Switch antenna 2 on and the shelf carton keeps the gate open for as long as you like. The event never closes.
Lower the floor to -70 dBm and three tags from the parked pallet join the shipment. They were never on it.
Shorten the quiet timeout and the event closes sooner, with a risk. On a real dock the forklift turns, there’s a gap of a few seconds, and one pallet becomes two events. Lengthen it and you wait longer to hear anything. A door sensor or light curtain fixes most of this, because it tells you when the pallet has gone instead of making you guess from silence.
Read filter lets you move all of it. The stream is simulated, with signal levels I chose to look plausible, so don’t read the numbers as a measurement. Read what happens when you change them.
When you talk to a vendor, ask what the reader sends and what the edge sends. If both answers are “tag reads”, the filtering ends up in your ERP. For how IoTReady does this step, see how the platform receives, processes and dispatches and the reader.
The pallet was one event. The reader said it 3,028 times.