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: , , , , , , ,


Oct 02 2011

Send driver alerts in THEIR time zone now

Since alerts are sent in the USER’s time zone, and can be “copied” to the driver him or herself, there is sometimes a time zone conflict with the alert.

We have enhanced GPS Insight to ensure that alerts are sent to the driver in the time zone they are associated with in the system.

Here is a typical alert which has been set to send straight to the driver when they idle for more than 15 minutes:

Copy a driver with a generated alert

Copy a driver with a generated alert

Here is the driver admin screen, where you can set the time zone:

Set a driver's time zone

Set a driver's time zone

And when the alerts come in, they will adjust depending on which time zone the driver or user (depending on who is receiving it) prefers:

Time zone adjusted alerts

Time zone adjusted alerts

Bear in mind that our choices ALSO compensate for daylight savings time (DST) which is why Arizona and Indiana are choices, as they do not celebrate DST.

This will help to ensure that when drivers receive data, it isn’t an hour or two “off” from the time they actually were idling/speeding/entering landmarks/etc.

Learn more about our fleet tracking alerts.

Rob.

Tags: , , , , , , , ,


Oct 02 2011

Determine how much fuel and C02 idling is actually costing you and the environment

We have a customer that really needed to precisely measure how much fuel and CO2 emissions their idling was costing them.

Not all vehicles are created equal, so at the individual vehicle level, we made the fuel type and estimated number of gallons consumed per hour idling something our customers can set.

Here’s how you get there:

Open Vehicle Administration

Open Vehicle Administration

There is a new option in vehicle admin called “Update fuel and emissions info”:

Update fuel and emissions info

Update fuel and emissions info

We have a “liters engine size to gallons idled per hour” converter which allows you to plug in your engine size and determine a fairly accurate number of gallons idled away per hour:

compute and override the # of gallons per hour spent idling

compute and override the # of gallons per hour spent idling

Here I am editing a SALES vehicle driven by KEVINJS:

update fuel type and gallons per hour idling

update fuel type and gallons per hour idling

Once you have overridden any defaults necessary (we default to unleaded and .4 gallons per hour spent idling), then you can run your report:

Run an idle report with fuel usage/CO2 emissions

Run an idle report with fuel usage/CO2 emissions

I ran it for the September for the Albuquerque group (ALB) which contains the newly changed 5.0 liter F-150 which burns .55 gallons per hour of diesel:

How much fuel / emissions is idling costing me?

How much fuel / emissions is idling costing me?

In this case, KEVINJS had roughly 7 hours and 3.863 gallons of idling, which we compute (based on the properties of the different types of fuels) to equate to .034 tons of emissions.

Together, the ALB group idled 512 hours, costing 209.6 gallons of fuel and 1.846 tons of CO2.

Now by using GPS Alerts, you can notify your drivers that they’re idling and ask them to shut down the vehicle with a text message or email (and since they’re idling and not actually driving, there are no distracted driving issues).

Then later on, you can easily determine your fuel and CO2 savings by running this or other idling reports available within GPS Insight.

Enjoy!

Rob

Feel free to contact us if you are interested in seeing a more in-depth demonstration of our GPS fleet tracking solution.

Tags: , , , , , , , , ,


Aug 16 2011

BEWARE! – Not all idling calculations are created equal!

We have been in the GPS Tracking industry for almost 7 years now. Enough to learn and FIX the limitations of GPS to ensure the highest quality data possible (e.g. 99.x% — if anyone tells you they’re 100%, well, guess what, they’re not).

So, today I found a perfect example to show the lengths to which we go to make your data 100% reliable (well, 99.x%…).

I had a 7:30 AM phone call and an 8:30 offsite meeting.

I had to get to my meeting by 7:30 so I could sit in my car and get on the call, then be there for my meeting & the breakfast prior.

So I had to idle for almost 40 minutes in order to avoid baking in my car in the hot Phoenix heat.

Here’s my stop report for 2 separate devices installed in my vehicle, both showing a ~37 minute idle stop:

GPS Insight Stop Report

GPS Insight Stop Report

One device (Rob) gets its speed data from the engine’s computer, and is more expensive because of that.  One device is less expensive but has to “interpolate” its speed from GPS Satellites traveling 9 THOUSAND miles per hour at over 12 THOUSAND miles in space.  And it’s remarkably accurate, but there is unfortunately what we call “positional GPS drift” of up to 20 feet typically.

So when the devices move 5-10 feet due to this “drift,” we interpolate a speed of 1-3 MPH typically.  But that means the device doesn’t look like it’s stationary, therefore it’s not idling.

Thankfully GPS Insight has a formula (which can be tweaked for different types of fleets, e.g. slow-moving street sweepers) which “consolidates” multiple drift points into a single idle event and position.

Our customers would never see this “inaccurate” GPS data, but here’s a picture of the REAL LOCATION REPORTS to include the drift for both the 3500 (talks to the engine for speed but not as accurate with GPS) and the 3900 (much more accurate GPS which it derives speed/distance/acceleration from):

175' of drift for the diagnostic device (we fix that)

175' of drift for the diagnostic device (we fix that)

The “drift” in the picture above is corrected over long idle stops to the “center” point which typically has the most reports.

 

175' of drift which we "correct" for diagnostic GPS device
15′ of drift for the more accurate 3900 GPS device

For the 3900, the drift is MUCH smaller — only 15′, and again, we “consolidate” that into a single 38 minute idle stop with a single “pin.”

The corrected map looks 100% accurate (well, 99.x%…):

"Fixed" stop location and idle time

"Fixed" stop locations and idle time

This shows my 2 devices in my car both stopped for ~38 minutes, and 29 feet apart (vs. the 175′ we saw above on the 3500).

And my car is 12′ long, with antennas in the front/back of the vehicle, so that’s not too bad (they show in the right locations +5′ or so each).

We consolidated the GPS drift into a single “valid” point, both in terms of position and time spent idling.

This is a HUGE distinction between GPS Insight and other companies who will either show you that your vehicle was someplace it really wasn’t, or far worse, show you that it wasn’t actually idling when it was.

Without doing all of the processing on “drift points” at 1-3 MPH, you wouldn’t know that the vehicle was actually idling, and you would lose a HUGE component of your potential ROI using GPS Insight.

This is fairly low-level, but I wanted to make sure the extent to which our product validates and consolidates data to make it actionable and insightful (and ACCURATE) isn’t lost.

There’s a big difference between this type of product and a typical “dots on a map” product.  You should know there are major differences OTHER than price when it comes to GPS Fleet Tracking.

Thanks,
Rob.

 

Tags: , , , , , , , , ,


Aug 14 2011

I got caught speeding to Sedona

Thankfully not by the police, but by GPS Insight.

I was heading to Sedona this afternoon with my family and got this alert by email, showing that I was doing 61 in a 35 MPH zone, along with a map showing I’m coming up on a curve:

Posted Speed Limit alert for me

Posted Speed Limit alert for me

I thought there was no way I would go that fast over the speed limit so when I got home from my trip, I checked GPS Insight to see if we had the right posted speed for that area.

We have an internal-use-only “pincushion” tool we use which shows the various speed limits based on which direction you’re traveling, relative to the roads nearby and some reasonable assumptions.

The pin says it changes from a 55 to a 35 a little way before my vehicle location was sent with instantaneous speed of 61:

GPS Insight "pincushion" posted sped limit tool

GPS Insight "pincushion" posted sped limit tool

I thought that was unlikely, so I went down to street view, and found a 35 MPH speed sign right there (above, it’s the yellow pushpin):

Proof that it's a 35 MPH zone

Proof that it's a 35 MPH zone

I guess I was speeding.

So what’s my defense?  I didn’t see the sign?  At least I can measure the distance until the turn and see that there was LOTS of room to slow down before the curve that 35 MPH zone was put there for:

Rob speeding (61 in a 35)

Rob speeding (61 in a 35)

You can see I measured 600 feet before the BEGINNING of the curve, which is plenty of time to get from 61 to 35.  That’s 2 football fields.  And since my prior max was 65 (in the info bubble) I was slowing — just not fast enough for the speed limit…  But at least you can drill down and get some better context for the posted speed alert.  That’s ideal — without the ability to easily drill down for more information, you don’t know the context of the speeding alert, and can’t make good decisions on how to approach (or not to approach) your drivers about these alerts.

So even GPS tracking company owners speed.  Maybe it was so I had some good material for a blog article?  Yeah, that was it.

Here is a picture from Sedona, by the way:

Sedona, Arizona

Sedona, Arizona

And I didn’t speed on the way home, as evidenced by the alerts report I ran for today for my vehicle (Nav2):

Run an alert history for my vehicle for today

Run an alert history for my vehicle for today

But I did idle for 8 minutes while we stopped for snacks for the ride home (and my device went out of range when I pulled into the garage, since I live in the middle of nowhere, and my oil change and rotate tires maintenance items never got updated…):

My alerts for today

My alerts for today

This is the point of having a GPS fleet tracking solution — set the alerts, and wait for your drivers to do something you want to be alerted to.

I’m paying for my own tickets and gas, and I know I’ve got a 4×4 and 600 feet to slow down before a curve in a pretty desolate area, so no real issues here.  But you certainly want to know these types of things about your drivers.

Especially if it’s your money for fuel, drivers’ licenses at stake, and your liability should they be driving too fast.

Rob.

Tags: , , , , , , ,


Aug 06 2011

GPS Tracking (and using) the Branson MO “Downtown Trolleys”

I am on a Summer trip with my 2 boys for their vacation to Branson, MO.  It’s like Disneyland for kids in the Ozarks in Missouri.

As we were getting onto the Trolley which shuttles you around “Old Town” Branson, I realized they were a customer of GPS Insight’s, and asked a support person to send me the GPS Mobile Map link to their vehicles so I could “track myself” and see how close the trolley was later when it was time to get back on. [Mobile Mapping is a free capability within GPS Insight under the "Mapping/Mobile Mapping" menu.  You just need to retrieve the unique, secure link and you can view your vehicles from any smart phone or tablet]

Here is a picture of the boys on the Trolley:

 

My boys on the Branson Downtown Trolley

My boys on the Branson Downtown Trolley

So within a minute or so my support person was able to text me the link to use from my smartphone to see the Trolley position:

Where the Trolley is according to GPS Insight

Where the Trolley is according to GPS Tracking

Then quickly I clicked on Street View to see where Google thinks it looks like out my Trolley Window:

Google street View from Trolley Location

Google street View from Trolley Location

And quickly I took a picture with my iPhone to show it was EXACTLY like that at the moment:

Actual picture I took from the Trolley window

Actual picture I took from the Trolley window

Not bad, Google (or GPS Insight)!

The Branson "Downtown Trolley"

The Branson "Downtown Trolley"

I got off at the Bass Pro Shop stop so my kids could look around in advance of their big fishing trip the next morning.  I’ll talk about how I was able to minimize my wait for the Trolley (it was 111 degrees and HUMID) in the next article.

I’m glad we’re able to help Branson with their GPS tracking initiative.  Great town to visit with your family.  For more information click here!

Thanks,

Rob.

 

Tags: , , , , , , , , , , , , , ,


Jul 29 2011

New Timestamps in Garmin Dispatch/Messaging Module

With our new timestamp functionality you can now check the time a Garmin Message or Dispatch Item (stop) was:

  • Sent by Dispatch or GPS Insight automatically or via text
  • Delivered to the Garmin
  • Viewed by the Driver
  • Accepted by the Driver
  • Marked as complete by the driver

Here’s how:

The other day I Dispatched myself by texting “gps rob dis robhouse” which is short for “gps [rob 4000] [dispatch] [landmark named robhouse].”

Here are the timestamps of each of the status changes (available under the “Custom->Garmin” menu):

View Garmin Dispatch Status Change Timestamps in GPS Insight

View Garmin Dispatch Status Change Timestamps in GPS Insight

Note all I need to do is “hover over” the “Done” status at the end of the Message field, and the date-stamped statuses are visible.

After dispatching myself at 4:09, it instantly appeared as a stop on my Garmin.

I saw it, but then drove a bit so it would have a different timestamp when it became “active”, at 4:10, as I was about to turn North onto Scottsdale Road.  Note the change to “Active” at 4:10.  Here is where everything happened, after running a 3D history like this:

Run a 3D Map History for a day for my vehicle

Run a 3D Map History for a day for my vehicle

Leaving Work, accepting a stop to go home

Leaving Work, accepting a stop to go home

It took me until 16:18, and 5.8 miles to get home, where I was prompted by the Garmin to mark that stop as “complete” (we shorten it to “Done”):

Getting home and marking the stop as "complete"

Getting home and marking the stop as "complete"

Even if I didn’t mark the stop as complete, we still have the timestamp of when I reach that landmark available in the landmark report, and will eventually incorporate all of this information into a single “dispatch report” which allows our customers to get a single-stop summary of all their Garmin dispatch activity.

Here’s how to run that landmark report:

Running a GPS Insight Landmark Report

Running a GPS Insight Landmark Report

Note that our “1 day” landmark report extends backward and forward automatically to show you how long the vehicle was there prior to LEAVING (if it started the day in that landmark) and how long it stayed there through the end of the stop, if it was parked there at the end of the day.  These are the kind of “nice to have” features our customers (and we) insist on, so we provide it.

You can easily tell I left (late for the day, really…), then forgot something, came back, then left, and eventually came back, precisely at the same 4:18 PM time I marked the stop complete via the Garmin interface:

Times in and out of my house, matching the Garmin "Done" timestamp

Times in and out of my house, matching the Garmin "Done" timestamp

At least I left early the next day to make up for it — 6:22 AM.

This new capability is very helpful for proving service to a customer, determining how quickly your drivers react to dispatch items, and other investigations about your drivers’ daily activity.

Enjoy!

Thanks,
Rob.

Tags: , , , , , , ,


Jul 23 2011

New Dashboard Available and demo here

Category: dashboard dashlets,New Features,New Featuresrdonat @ 10:46 pm

We made the new GPS Insight Dashboard available last week to customers (in Beta).

Here is the new demo!:

New GPS Insight Dashboard Demo

New GPS Insight Dashboard Demo

Click on the image to watch the video and enjoy the new GPS Insight Dashboard.  It’s several months of hard work and REALLY good.  Enjoy!

Thanks,
Rob.

 

Tags: , , , , , , , , ,


Jul 19 2011

GPS Insight customer satisfaction survey

We recently hired a dedicated representative to proactively contact all our customers regularly.

She will:

  • Determine customer satisfaction
  • Take note of (free) training requests
  • Inform customers of new functionality
  • Review the account for where there is potential for more usage/ROI
  • Be the customer’s dedicated resource for things non-support-oriented

Her name is Shelly, and she’s at extension x8060 (877-477-4321 is our toll free #).

I was pleased with the initial results of our customer satisfaction:

Initial GPS Insight customer satisfaction survey results

Initial GPS Insight customer satisfaction survey results

Of 59 customers surveyed, 39% were Extremely Satisfied, 54% were Satisfied, and only 5% were Dissatisfied.

One customer stated they want to cancel their service.  When asked why, they stated that it was too expensive.

This particular customer has been threatening to quit unless we reduce their price since they became a customer in June of 2006.

Over 5 years later, we haven’t reduced (or raised) their price, and they’re still a customer.

In any case, over 93% of our customers asked are satisfied or extremely satisfied.

Maybe we should count that customer as satisfied, since they have remained a customer over 5 years.

That makes us 95%, which I think you’ll find is as good as it gets in this industry.

Even so, we now have someone to ask those 5% of customers why they aren’t satisfied, and I hope we can get that up to 100% by following up and fixing their complaints.

Rob.

Tags: , , , , , , ,


Jul 18 2011

GPS Insight makes the Inc. 500/5000 again!

Category: PURCHASING CONSIDERATIONSrdonat @ 4:34 pm

GPS Insight is happy to hear that we’ll be making the Inc. Magazine Inc. 500/5000 list again this year.

Last year, we made the Inc. 500 list of fastest growing privately held companies in the U.S. at #281.

This year I’ll be happy to make the Inc. 5000 list at a position around 1000-1500, since it’s based on growth, not income, and our 3 year growth was down from 1,076% last year to roughly 200% 3 year growth this year.  As even Google found out, you can only keep crazy huge growth up for so long before it begins to taper off.

GPS Insight makes the Inc. list again

GPS Insight makes the Inc. list again

Thanks to all our customers, employees, vendors, partners, and families for their help making GPS Insight the success it has become.

Rob.

[P.S., don't tell the folks at Inc. Magazine that we let this out before they told us we could...]

Tags: , , , , , , , , ,


Next Page »