The Revolution Blog

Hamilton’s Torture Track: A Caster House of Horrors

Friday, Oct 31, 2014

Deep below our factory, the concrete basement rumbles and deafening thuds echo against the foam-padded doors.

This isn’t an insane asylum. Instead, it’s home to Hamilton’s infamous torture track, where we pit our ultra-durable casters against the competition.

“Shock loading, uneven floors, abusive forklift drivers, debris – the list goes on. We simulate it all.”

How It Works: Prove Your Mettle

For starters, we hook casters up to a circular track that’s lined with common factory obstacles, like uneven surfaces and debris. Next, we overload them – up to 20% over their load rating. Finally, we run them around the track to see how they perform under the kinds of pressures you would find in heavy industry.

“We know that in the real world, casters take one heck of a beating way beyond their rated specs,” said Mark Lippert, Hamilton’s vice president of marketing. “Shock loading, uneven floors, abusive forklift drivers, debris – the list goes on. We simulate it all.”

 

The Mercy Rule in Full Effect

Our testing results continue to shock even the most seasoned engineers.

“Just last week we tested a competitor’s latest model at about 200 pounds over its rated capacity,” said Jeff Spektor, Hamilton’s engineering manager. “It lasted 22 minutes before it began to break apart.”

By comparison, our casters ran for two days before we purposely stopped the test. As for why Hamilton still uses the torture track, while many manufacturers consider it dated?

“It’s just one of many tests we run to make sure we continue to build the absolute toughest casters,” said Lippert. “And frankly, we’re not afraid to see how we stack up to our competitors. That’s how we make smarter, safer and even more durable products.”

Want to see the torture track in action? Email or call Mark Lippert (513-454-2642) to schedule a tour. Just be sure to bring ear plugs. Loud is an understatement.

Leave a comment

Add Comment Cancel

Comments

An error has occurred. Error: View_Blog is currently unavailable.