Dec 26 2011

Be sure you pick the right cellular coverage for GPS tracking!

Not all companies who track their vehicles need to worry about which cellular provider they use.  Most don’t even know they may have a choice.

But if you do work in remote areas, you should pay attention and work with your GPS provider to ensure you get the right network.

I went to see ‘Mission Impossible’ today with my son and drove into town (Flagstaff) from our house which is in EXTREMELY bad AT&T coverage.

On the way home, I drove a couple miles around in our neighborhood to try to compare the reliability between AT&T and Verizon coverage.

My vehicle has both a Verizon-based device (labeled Rubicon) and an AT&T device (labeled Rubicon PNP).

We have a couple of internal mechanisms for determining how good the coverage ACTUALLY by:

  • Viewing purported AT&T or Verizon coverage
  • Showing ACTUAL cellular “lag” on a map
  • Generating a report of ACTUAL cellular “lag” with a graph

Below is an actual AT&T coverage map showing the area where I typically lose coverage in “light blue” which is not ideal coverage.  In the “dark blue” area, you can see there are very few places where the time for the device to report through the cellular network is more than a few seconds.  In my area, you can see some “tall” pins which visually represent how long it took the device to report (which is really a measure of how far the vehicle had to move before forwarding that data once it recovers cellular coverage):

AT&T coverage vs. time it took for a device to report

AT&T coverage vs. time it took for a device to report

Note that the Verizon device (Rubicon) has a “pink” line and the AT&T device (Rubicon PNP) is in white.  Verizon shows perfect coverage throughout (not pictured).

Here is how I pulled up the “lag report” version of the 3D map within GPS Insight:

Choosing both Rubicon devices once at a time

Choosing both Rubicon devices once at a time

Choose the "Lag Report" option for a 3D History Map

Choose the "Lag Report" option for a 3D History Map

[note this functionality is internal to GPS Insight support staff and is only available to end-customers upon special request]

Here is the display of my drive WITHOUT the coverage map.  Notice that there are very few “tall” pins meaning very few “lagged” points:

Slight lag (24 seconds to 3 minutes) for remote AT&T device

Slight lag (24 seconds to 3 minutes) for remote AT&T device

Next I will run a quantitative analysis of today’s data, for just the 2 devices in this vehicle, after quickly creating a “Rubicons” vehicle group containing them both:

Create a "Rubicons" Vehicle Group containing both devices

Create a "Rubicons" Vehicle Group containing both devices

I can then run this (internal use) “Lag Report” on the “Rubicons” for today:

Cellular "Lag Report" between AT&T and Verizon

Cellular "Lag Report" between AT&T and Verizon

Note there is a “landmark” option where we could restrict the report to ONLY data within a certain area we define, such as a mine, or wherever a customer may be concerned about coverage.  Also note above, that GPS Insight still thinks I am driving, since when I pull into my bad coverage and put the car in the garage, sometimes the final ignition off event doesn’t get transmitted until I drive back into coverage the next time I leave.  This is normal behavior for poor coverage areas, and is unavoidable (unless you know enough to choose Verizon when purchasing in these cases, which is the point of this article).

Here is the output, showing 100% coverage for Verizon and 95.8% coverage for AT&T for today’s drive:

Verizon 100%, AT&T 95.8%

Verizon 100%, AT&T 95.8%

The AVERAGE time to report for Verizon is 2 seconds, whereas AT&T averages 7 seconds.  The max for Verizon is 4 seconds, and for AT&T, the max times are 51 seconds and 3 minutes, for when the report reports within 1 minute or 10 minutes (we break it out into 1, 10, 30, 30+ minute “bands”).

Here is the past week, since I drove up to Flagstaff for vacation from Scottsdale, driving through notoriously bad AT&T coverage in the mountains (I know this because my iPhone is AT&T & worthless for that drive) — note that the percentage of < 1 minute reports is 100% for Verizon and only 83.7% for AT&T:

Poor AT&T Performance in mountains between Scottsdale and Flagstaff

Poor AT&T Performance in mountains between Scottsdale and Flagstaff

However, the week PRIOR to me leaving for vacation, driving around the more populated Scottsdale/Phoenix area, shows a much better 95.1% performance for AT&T vs. a 99.9% availability percentage for Verizon:

AT&T vs. Verizon coverage in Phoenix/Scottsdale

AT&T vs. Verizon coverage in Phoenix/Scottsdale

The moral of the story here is threefold:

BEFORE you purchase GPS Tracking devices for your fleet, make sure to determine A) if you have coverage issues in the areas your vehicles travel and B) whether or not you can afford to wait the minutes, hours, or sometimes overnight before the device reports in these areas.

If you may be affected, and aren’t sure, then make sure your GPS Tracking provider can provide not just multiple coverage options, but ALSO the tools to determine if there is a need for one coverage or another, as shown above.

As a point of reference, Verizon devices cost roughly $50 more than AT&T devices (due to additional modem and CDMA licensing costs).  But that’s a onetime cost and will probably amount to less than 5% over the life of the device and service.

If that $50 keeps you from experiencing occasional cellular delays due to poor (typically) AT&T coverage, then it, and finding a company which provides the right coverage (e.g GPS Insight…), is certainly worth considering.

Thanks,

Rob.

 

 

 

Tags: , , , , , , ,


Dec 13 2010

GPS Insight adds new servers to keep the site fast — with no downtime

Category: Availability,Miscellaneousrdonat @ 11:48 pm

GPS Insight is very fast, and we never hear complaints from our customers about the site speed, the time it takes to run a report, wait for map refreshes, etc.

But as we add customers and vehicles under management, we always ensure we add as well as migrate to newer and better hardware.

When we do maintenance and server upgrades, our customers never see the impact — we have redundancies in place to ensure we can “cut over” while replacing/upgrading any particular part of the system.

We have spent the past few days migrating a few “old” servers which were still being used to newer ones.

I took a quick look before we finished up this process, and saw that our oldest web server had been up without being rebooted for almost 3 YEARS STRAIGHT:

GPS Insight web server up for 2.9 years without a reboot

GPS Insight web server up for 2.9 years without a reboot

Another key server was up for 800 days exactly before being “put out to pasture”:

GPS Insight server up without a reboot for 800 days straight

GPS Insight server up without a reboot for 800 days straight

Don’t try this with Microsoft operating systems… (sorry Bill).

Rob.

Tags: , , , , ,


Apr 20 2010

Why I hate Microsoft (or why resetting your Ford Sync GPS is a bad idea)

Obviously I am pretty dependent on GPS for just about everything when it comes to getting around [also for money...].

I have 3 GPS Navigation devices with me when I drive my car (factory installed, Garmin, & my iPhone) so I never print directions any more.

So, on the way out to Long Beach a couple weeks ago, my family and I took our 3 month old car with Ford’s/Microsoft’s “Sync” system (with GPS Navigation).  No directions, just our factory installed GPS navigation unit.

Just outside of town it crashed on us.  I figured out how to do a factory reset and get it back up & running.

Here’s the point:  AFTER RESETTING IT, I FORGOT TO TELL IT “FASTEST” & NOT “SHORTEST” when optimizing our route.  DOH!

We took the 10 out to LA area, but then it took me through some really sketchy, slow-moving areas.

On the way home, I thought about it, & realized I needed to change my GPS setting to FASTEST from SHORTEST.

I was curious how much longer it took me time-wise to get there than to get back, so I ran a 3D history report & saw very quickly that it was twice as long (60 vs. 30 minutes):

Run a week long history for our trip to/from Long Beach

Run a week long history for our trip to/from Long Beach

Slow, direct route vs. Fast, indirect route

Slow, direct route vs. Fast, indirect route

All I had to do is look at the 2 points where the route deviates then converges again, and compare times and distances:

Where I took a GPS dictated "dumb turn"

Where I took a GPS dictated "dumb turn"

The times/mileages are:

Going there: 17:47 & 4571.6 miles to 18:53 & 4602.5 miles

Coming back: 10:26 4618.8 miles & 10:58 & 4656.3 miles

Doing the quick math, it took 31 miles & 66 minutes there the “short” way, & 37.5 miles & 32 minutes (half as long) the “long way.”

So to save 6.5 miles, I wasted 34 minutes of my life, praying we didn’t get car-jacked.  At least if we did, I would know where the car went…

Anyway, I thought of this the other day & was curious just how much extra time it took us because of that one GPS setting on my (Factory Installed — not GPS Insight…) navigation device.

Because I track that vehicle, it took me about a minute to figure it out using GPS Insight.

Oddly enough, while I was writing this, my new Microsoft Windows 7 box crashed Google Earth as well.  It knew I was badmouthing Microsoft.  Sooner or later, all things Microsoft eventually crash.

I’m really glad we don’t run our systems on Microsoft products.

I just checked and our two “primary” servers which our customers rely upon (with lots of auxiliary and backup servers, of course) have been up for two years to two years & 3 months:

GPS Insight servers run for years without incident

GPS Insight servers run for years without incident

I’m glad most of our competitors run Microsoft though…

Rob.

Tags: , , , , ,


Aug 31 2008

GPS Insight is there for you — 24 x 7 x 365 !

Category: Availability,GPS Insight Employees,Miscellaneousrdonat @ 11:11 am

This Labor day weekend, we’re still taking calls from new customers who are installing their first units, forgot how to run a particular report, etc. We get our support calls 24×7, no matter what day it is.

I thought I would write a blog article and quantify just how available our service and support is to our customers.

First, I’ll run a Tech Support phone Queue report for all of 2008:

GPS Insight Tech Support Phone Queue Report

We see our average hold time at 14 seconds (up from 12 seconds last year, but we just hired 2 more tech support representatives to help that!):

GPS Insight Support Hold time average is 14 seconds in 2008

We answer 96.8 % of all tech support calls, and of those which we don’t get to in time, the customer’s average hold time is only 31 seconds, a max of 2.1 minutes. When’s the last time you sat on hold for ONLY 31 seconds and thought that was too long?…

But what about our servers and systems availability?

It’s not quite 100%, but pretty close. Here is a report I ran for all of 2008. I have to blur the names of the servers, due to security, but it should help give you an idea for just how much time our systems are available to you. An average of 99.594% availability, but really, the few servers which “bring us down” from 99.97-100.00% for most of our important servers are “expendible” such as the one called “olap-02″ (shown in the picture below with a 96.021% availability rate). These servers are “extras” which we use to speed your experience during peak traffic, for large report requests like state mileage for a full quarter Sometimes we take them offline to make changes, but ensure that your reports are always available to you, or better yet, delivered to your email every day automatically.

GPS Insight server availability

The other server you see is “web-01″ which had an availability of 99.989% for the year so far.

That is only 58 minutes of “unavailability” in the entire year (and generally due to unavoidable “other carrier” network problems between our office and the secure facility where we run GPS Insight).

Here you can see that it hasn’t been rebooted for over a year — 343 days, and it’s barely breaking a sweat (it’s Labor Day Sunday, no one is really using the product):

GPS Insight server availability

We go to GREAT LENGTHS to make sure our product and our support staff are available to our valued customers 100% of the time. There is tremendous redundancy built in, so we can make sure that no matter what happens to a hard drive or network card, our customers will never see an interruption of service.

Plus, we have the tools and processes in place to help quantify it for our customers. If you’re not a customer, but considering GPS Insight vs. another vendor — ask them for this information and see if they can provide it. Call THEIR tech support to see how long you’re on hold & if they drop you to a voice mail box or offshore? Then call ours & see how quickly we answer — 866-477-4321, press 2 for tech support, & 1 to bypass the recording detailing our online http://support.gpsinsight.com tools.

Thanks,

Rob.

Tags: , ,