Rfid Driven Database Tracks Contamination Possibilities

New RFID systems can more easily resolve common meat processing plant issues that

now come about because the extra handling of bar-code tags and handheld readers are more likely to become contaminated with E. coli on the slaughter floor.

The current scenario requires that bar-code tags be removed from the carcasses, put into plastic bags, and pinned onto the carcasses as soon as they enter the so called clean side of the manufacturing plant wherever the meat is cut and processed. Workers who handle bar-code tags plus the handheld scanners need to change clothes and shoes when moving to the clean side of the plant so they do not spread the contaminants.

The new scenario changes that since RFID tags do not have to be in a reader's line of sight, they're handled much less, reducing the number of workers required and also the potential for contamination.

If the new system were adopted, all of the carcasses could be split in two and inspected. From that point on, RFID readers and handheld computing devices can be employed to collect details about each and every single carcass half, including quality in the meat, any instances of degradation to a carcass, and weight. The method would allow any processing plant to generate invoices rapidly.

RFID tracking of carcass halves could continue as they go to the cutting method, in which they could be cut into any number of pieces. Each and every piece of meat could also be given a unique ID, in addition to the animal's original ID. Particular cuts of meats can then be shrink-wrapped, with identifying details printed onto additional RFID tags. The pieces could then become divided by cuts and packed into cases.

As soon as the meat is unpacked at a distribution point, the trail ends. At this point, regulatory agencies are fortified with the knowledge that they could issue a recall because users of this RFID system have a record in their database of wherever each and every situation of meat was sent, who bought it, and data on each and every animal that went into that situation.

The process can be frequently tested in mock recalls. Any designated inspector could walk into any plant at any time and ask for a recall record of all animals killed 15 days ago. The software interface associated with the database can now go to work. The required reports could be produced in a matter of minuets.

by: Tom Gruich

POST COMMENT

My 911, A Perfect System For Abduction Prevention And Recovery Assistance Commercial Fuel Cards Database 2010: Portugal What Data Cabling Provider In Toronto Offers? How To Recover Data From A Mac Os X System Crash? Benefits Of Genuine Data Entry Work Damaged System And Data Files Cause Data Loss In Mac Os X Introduction to Disaster Recovery Why Companies Should Choose A Michigan Data Center How To Get More Names In Your Client Database The American Recovery and Reinvestment Act of 2009 Approach Data Recovery Experts Immediately If Raid 0 Fails Advantages of Data Center for Server Colocation Understanding User Datagram Protocol