Got 4G-LTE Coverage? The Cradlepoint Suitcase Tells All

As I mentioned in my last post on 4G LTE, businesses have been adopting 4G LTE as an enterprise-grade network. One issue that should still be considered prior to rollout is coverage. Enterprises with distributed networks want to know if network access is available where their branch offices are located. It’s great that the carrier companies are aggressively building out their 4G LTE networks. But at the end of the day, is there coverage where the company needs it?

One way to find out is by requesting a Cradlepoint CradleCare Site Survey and we’ll send out a “suitcase.” These suitcases are really toolboxes filled with sophisticated network measuring equipment. Cradlepoint’s nationwide network of technical staff members physically bring the suitcase to a business location and run tests to measure the signal strength, quality and speed of multiple carriers’ networks.

It seems like an obvious precaution to make sure you have signal before you implement a solution. But what happens in the real world is that a company will go online and look at a carrier’s coverage map. The carrier shows that if the business location is near such and such cross streets, then coverage will be good. So the company deploys that carrier’s solution only to discover that the coverage is, in fact, not optimal for a variety of reasons such as being blocked by a hill, or blocked before it gets into the wiring closet deep in a building.

When enterprises can know ahead of time which carrier provides the best signal at any given location, it can save time and money by installing the right carrier’s equipment the first time. Otherwise, it will waste time and money installing one carrier’s equipment only to have to uninstall and move or replace it later on.

The fact is that the only way to be sure you will get good signal strength is by testing the signal at the precise location you need it. Cradlepoint's suitcases have been doing a lot of traveling lately as more and more of our customers choose to test first, implement later.