The best way to answer this question may not be necessarily to call out specific applications that may (or may not) need high memory – for example, asset tracking, etc. Rather, a better way to determine if an application needs high memory RFID tags, is to determine if the application will be able to have reliable access to a database (as needed) in order to pull up relevant information about the tagged object.
Because a database can theoretically store as much information as required about any given tagged object, as long as the user has access to that database, the only thing a tag really needs is a unique ID within that application. In such a case, the user would simply read the RFID tag and then be able to pull up as much information as needed (assuming the user interface is designed accordingly). The database access could occur in real-time if the RFID reader is connected to a network, but can also occur if, for example, a user has a mobile RFID handheld reader that has a local copy of the database. (In this example, the local database would need to periodically sync with the master database.)
In the event that reliable database access isn’t possible and the user must store data about the tagged item, then storing data on the tag itself may be the best option and this is when high memory RFID tags would be needed.
To learn more about gen2 RFID tag memory banks, read Types of Memory in Gen2 RFID Tags.
If you have any additional questions about high memory RFID tags, please comment below or contact us for more information.