Nedap brings the inventory intelligence conversation to Milan. The goal: From data to action
June 8


In my last blog, I wrote about the dream to replace RFID handhelds in retail stores with fixed infrastructure. Now it’s time to dive a little bit deeper, and to explain you some of the main concepts behind fixed infrastructure reading. After reading this article, you should have a good understanding on how fixed infrastructure RFID works.
People who are not familiar with a technology on a deep level, often create a ‘mental model’ of the technology. A mental model is a simplified explanation of how the technology works, that gives ‘good enough’ guidance to use the technology. For example, if the battery of your car has 50% left, you can assume that you can still drive 50% of the maximum range. However, the reality is a lot more complicated: it depends on the terrain you are driving on, the outside temperature, driving style and the exact battery depletion curve. However, the 50% is a good approximation of reality.
The same holds with RFID. If you walk around a store with an RFID handheld, the mental model is relatively simple: the handheld picks up items in a radius of a few meters, and somewhere between two hundred up to a thousand items per second. It is completely logical that it takes anywhere between tens of minutes to an hour to count a whole store, because you need to walk along all the shelves.
For overhead reading, this mental model is different: you have readers in the ceiling that are continuously reading, so you instantly know everything in the store and see all changes in real-time. Right? … right?
Unfortunately, the reality is a bit more complicated. Let me take you through this step-by-step.
The first challenge is that we still have the limitations of the RFID protocol: readers can only read approximately up to a thousand RFID labels per second - in ideal circumstances. With a typical store containing tens of thousands of items - that’s the first limitation. It will literally take tens of seconds to just read all the products once.
When two (or even more readers) try to read the same tag, it might yield to no reader being able to read the tag. There are multiple physical effects playing a role, but the main take-away is that you cannot simply assume that when you have two readers, you read twice as fast: in most fixed infrastructure systems readers read sequentially - causing even more delay.
And then there are some more complicating efforts:
“There is also a different approach to a cycle, where readers are reading continuously, focusing on reading items that move around - not the static ones. This has different trade-offs that will be addressed in a subsequent blog.”
Danny Haak
Head of Technology iD Cloud
Overall, it takes at least a few minutes to read a whole store in what we call a ‘cycle’ - and while the system is trying to read the store, items move around, get sold or might arrive to the store.
At Nedap, we are committed to helping retailers make the transition to fixed infrastructure with confidence. We support customers throughout the journey, from proof-of-concepts and deployments to large-scale rollouts, helping them unlock greater visibility, efficiency, and business value.

June 8
May 19