Architecture – DAVIS FMS 3.9.3 DriveRight (8186) User Manual

Page 23

DriveRight FMS Help

 Improved viewing and printing of reports.

 New ”r;usage” report to help trace night and weekend driving.

 Improved exception reports for Excessive Speed, Hard Braking, and Night Driving.

 A ”r;Relationship” report that shows a list of all DriveRights, which vehicles they are

assigned to, along with a default driver if one has been assigned.

 Improved browser with user-configurable colors, fonts, and field widths.

 Simplified filter support to make it easier to select what you want.

 Use of standard calendar control for specifying dates.

 Email support for all Excel generated reports.

 Supports Palm PDA download of DriveRight consoles.

Operational differences between DriveRight 3.0 and earlier versions

The operation of DriveRight 3.0 is very similar to 2.x, but there are some fundamental changes
that you should be aware of.

 In 2.x the vehicle table contained all the information about a particular DriveRight, in

addition to information on the vehicle. However, in 3.0 a new table was introduced, the
DriveRights table, which stores DriveRight console information. Vehicle information is
stored in the vehicle table, and DriveRight information is stored in the new DriveRights
table. In 3.0 , a DriveRight must be ”r;assigned” to a vehicle. When your old data is
converted, for each vehicle in 2.x a new DriveRight and vehicle is created in the 3.0
database.

Note: A DriveRight is identified using it’s DriveRight ID, and a particular vehicle is identified
using it’s Vehicle ID.

Note: A ”r;relationship” report was added to the program to help clarify the relationship
between vehicles, DriveRights, and drivers.

 The ”r;Set DriveRight” option in 2.06/2.6.1 appears as ”r;View/Set” in the

”r;DriveRight/DriveRight Settings” menu. Unlike 2.06/2.6.1, when changes are made to a
DriveRight using this option, they are also stored in the DriveRight table.

 Adding a new DriveRight to the program can now be done more easily using the Add

New DriveRight wizard which steps you through the process and helps clarify where you
stand with respect to the calibration of the DriveRight.

 You will also notice that every table now has a ”r;location” field. The location field was

added to facilitate ”r;rolling up” of data from many locations so they can be managed in
one database.

Back to

Architecture