GeoFencing
The Loadman Meter in your Trucks has an option that allows it to send
GPS coordinates along with every LoadData record.
If you have this option, the GPS data can be used to identify the Customer
for each load.
The Driver does not have to select the account at the meter.
Setup:
In order for this to function, the following steps must be accomplished...
- GeoFence Loads must be enabled. This
will add a new account called "GEO-FENCE LOAD" to every Route (more on this
below).
- Go to Select Latitude/Longitude Mode and select the
difference that is tolerated when attempting to match latitude/longitude
to a Service, called the match range. At first one should
probably just keep the default. You can also select the way you want to
see latitude/longitude displayed.
- Each Service entry in the database must have a valid latitude and
longitude.
The first two steps are easy, the third is the challenge. Possible ways
to acquire this data include...
-
If you happen to have a database with the latitude/longitude of all of
your Customers, contact us and we can help you get the data imported into
your Loadman Fleet Manager database. Of course this is the easiest.
But, most of the time the data is not available.
-
Create a Route.
Have the Driver select Customers from a downloaded Route as she makes her
collections. This associates the Lat/Lon of the collection point with the
Route Stop. Then the Loadman Fleet Manager operator can assign the Lat/Lon
to the Services.
See assigning Service latitiude/longitude
by running a Route. This is probably the best choice if #1 is not possible.
-
Have the Driver just run the Route without having it in the meter and
then view each load location on a map and assign it to a Service.
For details,see assigning Service
latitude/longitude by viewing loads on a map.
This will give the same results as #2 if you know where each of
your Customers is located.
-
Use the maps software's geocoding to compute the
latitude/longitude from the address.
For details,see getting the
latitude/longitude from the address.
This may give a good starting point for some of your accounts but
will probably not succeed for all addresses. Problems include having an
address that the map software cannot process or a location where the GPS
coordinates of the address is significantly different than the coordinates
where the acutal loading takes place.
-
Directly indicate the location of each Service by clicking it's map
location.
For details,see indicating the
latitude/longitude by clicking the map.
This works good if you know the location of all of your accounts and
may be useful for correcting any problems with the above methods.
Operation:
After you have completed the setup, you need to (re)download a Route to
the meter. The content of the Route is will now contain a special account
named "GEO-FENCE LOAD". The Driver selects this account to cause
GeoFencing to occur when the data is received by the Loadman Fleet
Manager.
Their are several possible outcomes of GeoFencing as displayed
in the LoadData view and able to be searched for in filters. They are...
-
Not Detected (displayed as blank): This means that GeoFencing has
not been attempted on this entry.
-
No Lat Lon: GeoFencing was not possible because
latitude/longitude was not included in this record.
-
Detected OK: GeoFencing was a success. There was only one possible
match.
-
Used Best Match: Dectection was a success. There were multiple possible
matches within the match range. The closest was selected.
-
No Match Found: GeoFencing failed. There were no Services within the
match range.
Note: once the database is properly set up for GeoFencing. Loads
that were previously collected can still be GeoFenced.
Select one or more loads, open the
context menu, and select
Detect account using GeoFence.
Troubleshooting:
-
Loads are marked Not Detected (or blank): This is caused by...
- The Driver did not select the "GEO-FENCE LOAD" account when
collecting the load.
- The load has been edited and the Service was manually changed
since it was GeoFenced.
- The load was collected before you setup GeoFencing.
A possible remedy is to manually perform GeoFencing.
Select one or more loads, open the
context menu, and select
Detect account using GeoFence.
-
Loads are marked No Lat Lon: This means that the data being received
from the meter does not contain latitude/longitude data. See the LoadMan meter
users manual.
- Loads are marked No Match Found or the wrong account was detected.
This is caused by errors in the setup (the latitude/longitude assigned to each
Service) or bad data from the meter. To correct this, one
can view and/or change the load and assignment
to a Service.