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


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


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 17 2011

GPS Insight saves my wife & daughter from 3 hours stranded in traffic

Category: Arizona,Google Earth,GPS Insight Employees,Safetyrdonat @ 6:21 pm

As my wife was driving back home after dropping my boys off for a week at sleep-away camp, she hit the worst traffic you can hit.  Cars were stopped dead on a divided mountain road, and people were getting out of their cars since no one was going anywhere.

She called me up to check traffic online through GPS Insight (since she has a device on her car (named “nav2″).

I got “directions” from our directions dashlet, then turned on Traffic :

Directions from my wife's car to mine

Directions from my wife's car to mine

I was able to instantly pull up the fact that there was an accident 3 miles ahead of her which had the road completely closed, and it was estimated to be closed another 3 hours.

Pulling up crash data from Google Traffic within GPS Insight's directions functionality

Pulling up crash data from Google Traffic within GPS Insight's directions functionality

Then I pulled up her location and recent 30 minutes of history within our 3D mapping (Google Earth):

Pull up Nav2's current status and recent history

Pull up Nav2's current status and recent history

She said people were turning around and driving on the shoulder of the road BACKWARDS to get to the nearest off-ramp.  I told her it was .5 miles.

My wife, .5 miles from the nearest offramp

My wife, .5 miles from the nearest offramp

She called me back and told me everyone was going the wrong way down the on-ramp to get over to the other side of the highway.

Within 3 minutes she had escaped a really bad traffic-jam, before it got jammed up too much behind her.

Then she needed alternate directions which I was able to get her instantly, as well as watch her progress on a route only about 20 miles out of the way.

Which sure beats waiting in traffic for 3 hours.

And a quick right-click “directions from/directions to” in Google Earth tells me she’ll be home in 39 minutes.

Directions/ETA and recent history

Directions/ETA and recent history

So I can fire up the grill and have dinner ready when they get home.  As I was typing this, she texted me the same thing:

Better go make dinner

Better go make dinner

Now I really better make dinner.

Rob.

 

Tags: , , , , , , , ,


Jan 09 2011

Now you can click through graphs to reports (then maps) in GPS Insight

Our new dashboard maps now allow you to click on individual items in order to instantly run a supporting report:

Click through on a graph item for supporting information

Click through on a graph item for supporting information

The report is then shown in a new Browser window or tab:

GPS Insight Idling Report from a graph click-through

GPS Insight Idling Report from a graph click-through

Then you can continue to click through and choose to view the data in a Google Earth (or standard map) window:

Google Earth view of Idling Report data for a vehicle

Google Earth view of Idling Report data for a vehicle

Zooming down to an individual idling incident to investigate

Zooming down to an individual idling incident to investigate

Having the ability to quickly zoom down from a high level graph to detailed, satellite-view specifics truly enables our customers (you) to find out what is going on with your fleet in minutes.  Just look for outliers on the graphs, and drill down to see the supporting activity.

Note that you can run the report for the entire group (vs. a single vehicle) by clicking elsewhere in most graphs:

Clicking on the legend usually runs the full summary report or a particular summary utilizing certain thresholds, such as all speeding incidents > 21 MPH over the posted speed limit, as shown below:

Click through for the report on all > 21 MPH over speeding incidents

Click through for the report on all > 21 MPH over speeding incidents

We are constantly providing new capabilities for our customers — be sure to ask us for whatever you can think may help you and your organization to get more Return On Investment from your GPS Insight GPS Fleet Tracking System.

Thanks,
Rob.

Tags: , , , , , ,


Nov 15 2010

$3 million legal verdict for not having GPS tracking

Well, to be accurate, if St. Louis had installed GPS in its vehicles, might not have lost a recent $3 million verdict in court.

Here’s the story:

A jury ordered St. Louis $3 MILLION to a woman who claims a municipal truck cut her off and led to a single vehicle crash.

She did not have any evidence about the vehicle, department, or employee other than the fact that “a municipal truck caused her to swerve and avoid a collision.”

The crash time and location were certainly determinable.

If St. Louis had GPS on its vehicles, it would be trivial to determine if (and/or who) was the truck in question.

You could run a landmark report for a 2 mile area around the crash location at the exact time (20 minutes between 14:50 and 15:10 near the landmark called “Mesa Riverview” in this example):

Check to see if any vehicles were near the accident at that time

Check to see if any vehicles were near the accident at that time

We quickly see there was no activity:

No activity near the crash at that time

No activity near the crash at that time

Then you can pull the entire day to see if ANY vehicles went nearby that landmark, and when:

Pull the full day's history into a map

Pull the full day's history into a map

Zooming in on our “pretend crash” landmark, we see that that there was NO ACTIVITY for that day, & the closest to that landmark was the “Scion” at 10:03 driving by on the freeway, and “Adam 4000″ at 12:20 several roads away from the incident.

Conclusive proof no city vehicle caused the accident

Conclusive proof no city vehicle caused the accident

Now it’s entirely possible that the vehicle DID in fact cause the accident — however, right now it is the word of an unfortunate accident victim against the City — and apparently that word is worth $3,000,000.

That $3,000,000 would buy a city of 1,500 vehicles GPS Tracking for every vehicle for 5 years based on my calculations.

Plus they would have the benefits of GPS Tracking instead of just a way to avoid a jury verdict.  And maybe if the drivers knew they were being tracked, the accident wouldn’t have occurred in the first place if it was in fact caused by a city worker.

Rob.

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


Aug 21 2010

$90 Parking Ticket is proven ridiculous (but we still have to pay it)

One of our employees who drives our GPS Insight Scion in a car pool took it Saturday morning to a remote area of the desert to go for a run.

He parked off the road, on a pull-out which was nowhere near where cars drive.

He came back to this $90 parking ticket (with my name on it since it’s my car officially…):

$90 ridiculous parking ticket

$90 ridiculous parking ticket

So here’s how you prove that Maricopa County Sheriff’s are scrounging around for money for our broke County, using GPS Insight:

Quickly run a 3D vehicle history for the Scion for that day

Quickly run a 3D vehicle history for the Scion for that day

Open the “Time Slider” to the first trip of the day & show just the dots (green) on the map corresponding to the drive to the first stop and 45 minute stop (yellow):

History shows the drive to go to an early AM run

History shows the drive to go to an early AM run

Then Zoom down & see the vehicle was parked off the road itself:

Parking off the road yields a $90 ticket

Parking off the road yields a $90 ticket

Then go to Street View mode & see that it’s a paved pull-off.  Why wouldn’t it be ok to park there to go for a run/ride/hike?

Did they pave it just to lure people in to give them $90 parking tickets?  Thanks Deputy Thompson.

Street View shows this is nowhere near the road

Street View shows this is nowhere near the road

I’ve paid it since it’s got my name on it, but I will definitely send a copy of the blog article to the Judge & see if we can get it refunded.

How ridiculous, though.

Even though politics and a County with financial issues trumps GPS evidence sometimes, at least you can clear the suspicion that your driver did the wrong thing.

Also, using our DriverID, you know which driver was in the vehicle at the time of the ticket so you know who to talk with, if the original got “lost.”

Rob.

Tags: , ,


Jul 18 2010

Always making things better

Category: Alerts,Google Earth,GPS Insight Employees,Mappingrdonat @ 3:10 pm

After our new “Late Arrival Alert” was launched last week, we got some feedback & changed it a bit to make it easier to read.  The time it SHOULD HAVE TAKEN is now shown (e.g. “…taken less than 6 min.” in this alert).

new alert additions

new alert additions

Additionally, a map is now shown for the start/end points which generated the alert, so you can easily see the context of the alert.  We embed maps in all location-based alerts (e.g. odd-hours, speeding, etc.).

This alert was generated because I took 18 minutes getting from my house to the office today, since I took “the long way” to stop by and pick up something at a convenience store.

This caused me to take 18 minutes vs. 6 to make it the 4.5 miles to the office from my home, and trip this alert.

Here’s a map of the “out of the way” route I took to get to work today (just to get a few things done before I head out of town for the week):

extra stop at a convenience store

extra stop at a convenience store

You can see the way the red line starts “thin and light” and gets “thick and dark” with the direction of travel, which makes it easy to see the activity at a  glance.  I clicked on the yellow “pin” which shows all stops less than 60 minutes.  It shows I stopped for 1 minute.

The red pin down at the bottom is my car stopped for > 1 hour.

It’s Sunday & I’m heading home now to hop in the pool & get ready for my trip, but wanted to show off this new alert functionality first.

By the way, here are the 2 alerts I got which now are “obsoleted” by this alert — I had one for every time I enter/exit either home or work — now I can see ONLY when I get to work when it’s too long of a trip. (not that I really need to track myself — it just makes for good examples when showing our functionality to customers):

RobHouse & GPS Insight Headquarters arrival alerts

RobHouse & GPS Insight Headquarters arrival alerts

Rob.

Tags: , , , ,


May 18 2010

Sneak peek at our new Trip Efficiency Report!

This is a REALLY exciting report, and is the culmination of months of work on top of years of getting ready for this report.

>>> REALLY — It’s A BIG DEAL <<<

This suite of reports will essentially pinpoint your inefficient drivers on an overall as well as a trip-by-trip basis.

Here’s a an early version (the final reports are on the way & will also include an overall vehicle-by-vehicle comparison/summary):

Run the Efficiency Summary Report:

New GPS Insight Trip Efficiency Report

New GPS Insight Trip Efficiency Report

Up comes a graph showing all your drivers’ trips for that period of time (a work week in this case) & how efficient they are relative to both SHORTEST and FASTEST routes which we determine WOULD HAVE BEEN IDEAL:

GPS Insight Trip Efficiency Graph

GPS Insight Trip Efficiency Graph

Then looking at the detail, we pick on the top “most inefficient” driver (sorting on # of unnecessary miles beyond the fastest route from A to B):

GPS Insight Trip Efficiency Detail

GPS Insight Trip Efficiency Detail

Then hovering over an entry, it tells us that the “James – Garmin” vehicle went 34.2 miles, but only needed to go 19.03.

Difference between actual and ideal fastest route

Difference between actual and ideal fastest route

By clicking on the 3 entries, we instantly pull up the actual (pink), shortest (red), and fastest (blue) routes for a visual comparison:

Visual Representation of Driver Inefficiency

Visual Representation of Driver Inefficiency

In reality, the “turnaround” out of the way is where several of our employees meet to car pool every day:

Reason for inefficient driving is a carpool drop-off

Reason for inefficient driving is a carpool drop-off

So this behavior is all right, since it saves a lot of miles and cars on the road.

But look at #2 and #3 on the list (and there are countless more inefficient trips):

Driving way out of way (in Purple) to get from A to B

Driving way out of way (in Purple) to get from A to B

Driving way out of way (in Purple) to get from A to B

Driving way out of way (in Orange ) to get from A to B vs. fastest/shortest routes in blue & red

These are our employees & our own cars, so it’s not exactly the end of the world that we’re sometimes driving all over the place inefficiently, & we have our reasons.

But if you run this against your fleet, you will find drivers who:

  • Get Lost
  • Make Wrong Turns
  • Intentionally Take the Long Way (padding hours)
  • Literally Drive In Circles (and should be probably be fired for fraudulent wasting of fuel/mileage and padding of hours)

This report will be available in late May, and is going to surprise a lot of customers.  And probably a lot of drivers too.

It will save our customers a HUGE amount of money on drivers they didn’t know were this inefficient, or were specifically defrauding them of labor hours.

Additionally, it will be available in June as a real-time alert to supervisors as well as drivers to “coach” them on better ways to complete their trips when they do so inefficiently.

Oh, and by the way, on a slow development server, for all 50 of our vehicles for a full work week, that report only took 1/3 of a second to run:

FAST (.36 second) Report

FAST (.36 second) Report

Look forward to it soon!

For more information on our main GPS Fleet Tracking Reports visit our website.

Thanks,

Rob.

Tags: , , , , ,


Next Page »