Tagging Data Crunch

February 17th, 2005

From Java, GIS, & Logistics:

Let’s Put Data on Tags! I think this is the worst idea imaginable, especially when it’s considered an answer to integration…just imagine an Intermec tag with only 108 bytes and a bunch of companies fighting over what data should be on the tag and what the format will be. A tag should simply contain an ID. A VAN or proprietary system can then enable organizations to attach data to that tag. Permissions and security can then protect that data and control visibility. The only reason to ever put data on tags is when they won’t need to be read by other companies and you don’t have access to the net (think military). Also, there are already people out there hacking data on tags and that even furthers my argument.

Amen to that. RFID tags should only contain an ID. The underlying system should manage the data associated with the tag. It highlights the bigger problem in the logistics – the failure to interconnect vendor’s supply chain systems and leverage their data. Which highlights the even bigger issuess a) a lot of logistics software is just plain awful and b) a lot of logistics executives are ignorant of how to use technology to create reductions in cost.

One Response to “Tagging Data Crunch”

  1. Michael Connor Says:

    A agree with you on both a) and b). With respect to integration, it’s one of the biggest challeges today. It reminds me of high school sex, everyone’s talking about it but few people are really doing it. People get excited about RFID and other tech because they think it will solve their integration woes without much cost or effort. Integration really isn’t that tough if you take the time to do the analysis and then follow it up with the right tools.