One of the first conferences I attended after 9/11 was a convention on food safety. The meeting had been planned in the pre-September days when viruses and other micro-pathogens were regarded as the main threats. But the terrorist attacks in New York and Washington hijacked the focus, shifting it to food security. Instead of discussing accidental restaurant poisonings from E. coli and other bugs, speakers spoke of the supply chain’s vulnerability to purposeful contaminations by fanatics looking for a stealth weapon of mass destruction.
In one memorable breakout session, two renowned safety experts worked with the audience to identify the greatest risks. They noted that common ingredients like spices and coffee lent themselves to tampering, and were often harvested in areas known to be at odds with the United States.
Sugar was cited as a particular vulnerability because it wasn’t very regulated and was used in so many processed foods. Poisoning that ingredient sounded so easy that I used a made-up name for the sweetener in a column covering the conference. As crazy as it sounds today, I didn’t want to give terrorists any ideas.
We were all worried about monsters under the bed back then. After awhile, that level of suspicion seemed almost hysterical. Life for the food business remained more normal than the conference might’ve suggested, and bacteria and viruses again emerged as the main threats.
Then came the CBS News report earlier this week that terrorists were planning to poison the salad bars of restaurants and hotels in a coordinated weekend attack. It said an anonymous intelligence official had confirmed the threat as “credible,” and noted that the U.S. Department of Homeland Security had gathered safety officials from the restaurant and lodging industries to brief them on the potential danger.
The report was exclusive to CBS. In the news business, that makes you suspicious. If the account was true, why couldn’t any other medium independently verify it? Certainly they would’ve tried with a story that big.
Nor have other authorities come forward to confirm it.
But they haven’t denied it, either.
Joe McInerney, the straight shooter who heads the American Hotel & Lodging Association, told USA Today that his group wasn’t invited to any security briefing by Homeland Security.
But he did shed some light on the matter. There was what he described as a standing meeting between Homeland and hospitality officials on the Friday before the CBS report. He also noted that the hotel industry has long been considered a “soft target” for terrorists.
And he said the lodging trade is taking precautions. The AH&LA is putting together a webinar for hotel employees on averting an attack on buffets, McInerney explained to USA Today.
It will also provide properties with info cards that can be inserted in employees’ paycheck envelopes, alerting them to say something if they see something suspicious.
The restaurant industry has so far been mute. But it’s just a matter of time until the issue gets a finer, more prodding point. What happens at a salad bar or buffet concept with employees who are believed to be Muslims? Will management try to hide them? Or just dismiss them? It's not a stretch to think buffet places could take a hit, regardless of who's working for them.
Similarly, how will employees and other customers react when they see a possibly Muslim patron head to the buffet?
Clearly there are two issues the industry has to address.
First, there’s the report itself. Is it true?
Second, and perhaps regardless of the answer to that first question, how is the industry going to deal with the suspicions? At the very least, the report poses a very real threat to places with salad bars and buffets, whether the story is accurate or not. Consumers may not be willing to undertake what they see as a risk.
Time extinguished a lot of fears after 9/11. But the restaurant industry shouldn’t count on that remedy this time around.
Wednesday, December 22, 2010
Is the restaurant industry really at risk?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment