← Back to the chapter · Next detail →

Technical detail · RFID System Components

Duplicate windows and event identity

A useful diagnostic ledger keeps four identifiers separate: object identifier, tag memory value, reader/antenna identifier, and business event identifier. Suppose tag EPC-A is seen by antenna door-2-left at 10:00:01, 10:00:02, and 10:00:04. Those three raw observations may become one accepted event if a fixed duplicate window starts at the first observation and lasts 5 seconds and the zone rule says door-2-left belongs to receiving. If that window is accidentally set to 1 second and its end is exclusive, the same raw evidence could become three events. If door-2-left is mapped to returns instead of receiving, the raw radio evidence is still true, but the business state is wrong.

The handoff arithmetic is small but important. With a 5-second duplicate window, observations at 0.0 s, 0.8 s, and 3.9 s collapse into one event because each is inside the same window. An observation at 7.2 s may start a new candidate event. That candidate should not automatically become a second receiving event unless the workflow allows repeated entries and the direction or zone evidence supports it. The same principle applies to missed mates: if a kit expects 12 tags and the reader accepts 11, middleware should create an exception, not silently mark the kit complete. Component reviews fail when these rules live only in code or reader presets instead of in an acceptance record that operations can retest.

← Back to the chapter · Next detail →