Action Tracker - HOS
Download Action Tracker - HOS Version 2 on Android Device (Place Card Holder)
3
Fleet Complete® Action Tracker -HOS App End User License Agreement
4
Opening the Action Tracker - HOS Application
6
Logging into the Action Tracker - HOS Application
6
HOS
Dashboard 7
HOS
Dashboard
(continued)
8
Driver
Service
Detail
9
HOS
Dashboard
(continued)
10
Change
Duty
Status
11
Driver’s
Log
–
Canadian
Form
14
Driver’s Log – United States Form (Place Card Holder)
15
Pairing the Android Device to the equipment in a Power Unit.
16
HOS
Dashboard
Menu
Choices
17
Menu
Options
–
Internal
Note
18
Menu
Options
–
Drivers…
19
Menu
Options
Drivers…
-
Request
Co-Driver
20
Menu
Options
–
Manage
Assets 21
Manage
Assets
–
Power
Units
22
Manage Assets – Scan for units in range
23
Manage
Assets
–
Power
Unit
Connected 24
The
Driver’s
Vehicle
Inspection
Report
(DVIR)
25
The
Driver’s
DVIR
(continued)
26
The
Driver’s
DVIR
(continued)
27
The
Driver’s
DVIR
–
Process
Repair
28
The
Driver’s
DVIR
(continued)
29
The
Driver’s
DVIR
(continued)
30
DVIR
Report
-
Flexibility 31
Coming
in
next
phase
31
Daily
Logs
32
Driver
Request
Log
Edit 33
Driver Request Log Edit – Add Event (continued)
34
FMCSA
Rules
relating
to
Log
Edits
35
FMCSA
395.15
–
Performance
of
recorders
36
Roadside
Inspection
37
More
Menu
Selection
38
Fleet Complete
®Action Tracker - HOS App End User License Agreement
BY CLICKING THE “ACCEPT” BUTTON OR DOWNLOADING,
INSTALLING OR USING THE APPLICATION, YOU AFFIRM THAT YOU ARE FULLY ABLE AND COMPETENT TO ENTER INTO THE TERMS, CONDITIONS, OBLIGATIONS, AFFIRMATIONS, REPRESENTATIONS AND WARRANTIES SET FORTH IN THIS LICENSE AND TO ABIDE BY AND COMPLY WITH THIS LICENSE.
Please read this end user software license agreement (“License”) carefully before clicking the “Accept” button or downloading or using the Fleet Complete® Action Tracker - HOS App (the “Application”). As used herein, “Application” includes, without limitation, any services specific to the Application (excluding, however, Your applicable wireless service plan), software code, scripts, interfaces, graphics, displays, text, images, artwork, music or video clips, documentation and other components or content and any updates, modifications or enhancements to these items accompanying the Application or this License. These terms are an agreement between You and Complete Innovations Inc. and its affiliates (individually and collectively, “CI”). “You” and “Your” in this License refer to you, an individual, and/or to the company on whose behalf you accept this License.
This Application is licensed, not sold, to You by CI for use strictly in accordance with the terms and conditions of this License. By clicking the “accept” button or downloading or using the Application, You are entering into and agreeing to be bound by the terms of this License. If at any time after reviewing the Application You wish to terminate this License, You must notify CI, un-install and remove the Application from Your Device, and delete any copy in Your possession.
1. License Grant and Use Restrictions
1.1 License Grant. Subject to the restrictions set forth herein, CI grants You a personal, revocable, non-exclusive, non-transferable, limited right to install and use one copy of the Application on a single device owned and controlled by You (“Device”), and to access and use the Application on such Device solely for Your own internal business and personal use, strictly in accordance with the terms and conditions of this License and all applicable local, national, and international laws and regulations. You represent, warrant and agree that You are using the Application solely for Your own internal business and personal use and not for redistribution or transfer of any kind.
1.2 Safe and Lawful Use of the Application. You agree to comply with the following restrictions when using the Application:
(a) Do not use the Application while driving your vehicle; use of the Application while driving is not authorized or recommended as this may cause You to be distracted and result in unsafe conditions. (b) Use of the Application is not a substitute for complying with
Except for the license granted in Section 1.1 hereof, You are not granted any intellectual property rights in or to the Application by implication, estoppel or other legal theory. All rights in and to the Application not expressly granted in this License are hereby reserved and retained by CI.
1.4 Open Source Software. The Application may utilize or include third party software that is subject to open source license terms (“Open Source Software”). You acknowledge and agree that Your right to use such Open Source Software as part of the Application is subject to and governed by the terms and conditions of any applicable open source license, including, without limitation, any applicable acknowledgements, license terms and disclaimers contained therein (collectively, the “Open Source License Terms”). In the event of a conflict between the terms of this License and the Open Source License Terms, the Open Source License Terms shall control.
2. Disclaimer of Warranties
YOU ACKNOWLEDGE AND AGREE THAT THE APPLICATION, INCLUDING ALL CONTENT CONTAINED THEREIN OR ACCESSED THEREBY, IS PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS, AND THAT YOUR USE OF OR RELIANCE UPON THE APPLICATION IS AT YOUR SOLE RISK AND DISCRETION. CI AND ITS SUPPLIERS AND LICENSORS HEREBY DISCLAIM ANY AND ALL REPRESENTATIONS, WARRANTIES AND CONDITIONS REGARDING THE APPLICATION, WHETHER ORAL, EXPRESS, IMPLIED OR STATUTORY, AND WHETHER ARISING BY LAW, STATUTE, USAGE OF TRADE, CUSTOM, COURSE OF DEALING OR PERFORMANCE OF THE PARTIES, OR THE NATURE OR CONTEXT OF THIS
LICENSE, AND INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE. CI DOES NOT WARRANT THAT THE APPLICATION WILL BE COMPATIBLE OR INTEROPERABLE WITH YOUR DEVICE OR ANY OTHER PIECE OF HARDWARE, SOFTWARE, EQUIPMENT OR DEVICE INSTALLED ON OR USED IN CONNECTION WITH YOUR DEVICE.
3. Limitation of Liability
EXCEPT TO THE EXTENT PROHIBITED BY LAW, UNDER NO CIRCUMSTANCES SHALL CI, ITS SUPPLIERS OR LICENSORS, NOR THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES AND AGENTS, BE LIABLE FOR YOUR FAILURE TO COMPLY WITH APPLICABLE HOS LAWS OR REGULATIONS, ACCIDENTS, PROPERTY DAMAGE, PERSONAL INJURY, DEATH, OR FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, SPECIAL OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OR NON-PERFORMANCE, OR YOUR USE
After downloading the Action Tracker - HOS application to the
Android Device and placing the Action Tracker - HOS widget on the
desktop, you can start the application by tapping on the blue Action
Tracker - HOS widget.
You will see the Login screen.
Enter your 4-6 digit pin number in the PIN field. This PIN number has
to be setup in the Fleet Complete Desktop application.
The first time the Action Tracker - HOS application is used on an
Android Device, the application will request the Fleet’s Details; which is
the Client ID number.
Your Fleet Manager can provide this to you or enter it for you the first
time you use the Action Tracker - HOS application.
You will not need the Client ID number again unless you install the
Action Tracker - HOS application on this Android Device unless you
remove it and reinstall it.
Opening the Action Tracker - HOS
Application
Logging into the Action Tracker - HOS
Application
The driver’s HOS Dashboard screen is the home screen for the driver.
This screen provides the driver with much of the information they will
need during their duty shift.
1
Current Duty Status – Displays the current duty status of the driver.Duty Status Type
• (OFF) Off-Duty • (SB) Sleeper Berth • (D) Drive
• (ON) On-Duty
• (OW) Off-Duty Well Site (if using the Oilfield 5th line log)
2
The area below the Current Duty Status button contains up to the minuteinformation about the driver’s HOS rule. The driver’s available drive time is always up-to-the-minute. This information provides the driver with Sensor Loss Information should the Android Device not currently receiving the required information for a fully compliant ELD (Electronic Logging Device).
3
The driver can immediately see their Available Drive Time. If they haveexceeded their Available Drive Time, the little green button turns red.
4
There is a graph displaying the driver’s duty status time lines as well astotals for each duty status.
The HOS Dashboard is not meant to show the driver’s actual log, just
graphical information for the driver’s quick look. The driver can see
their actual log as well as a Roadside Inspection screen at any time
from the menu buttons (more on this a bit later).
5
The driver can see the time totals for this 24-hour duty shift just below thegraph. Their current duty status is highlighted in yellow.
6
At any time, the driver can press (and hold for a moment) in this area tosee a more detailed look at all the elements that relate to their Available Drive Time calculations based on the rule they are operating under.
HOS Dashboard
1
2
3
4
The driver can access the Driver Service Detail screen in two ways.
From pressing the lower portion of the HOS Dashboard screen (as
described on the previous page) or from the menu button at the top of
the HOS Dashboard screen.
• This screen shows the driver all the information relating to the HOS rule they are operating under.
• A driver won’t see a Time of last Reset or Restart period when they start using the system and don’t have any history. This information will appear when they have a Reset and Restart.
Driver Service Detail
7
Dashboard Icons – e icons indicate the status of the Action Tracker - HOS applicationa) GPS Indicator – Indicates that the Android Device is receiving a GPS position fix
b) Chain links – Indicates if your Android Device is connected to a Power Unit. If the center link is broken, your device is not communicating with the equipment in a Power Unit. When the Android Device is communicating with the equipment in a Power Unit, the links are not broken.
c) Broadcasting Antenna – Confirms that the Android Device is communicating with the Fleet Complete office servers.
HOS Dashboard (continued)
The first activity a driver would do is change their duty status from
Off-Duty to On-Duty.
1
The driver presses the Current Duty status button to change their dutystatus.
• NOTE: The Action Tracker HOS application will also change the driver’s current duty status automatically to Drive (if the Android Device is paired and in communications with a Power Unit) when the vehicle starts moving and reaches about 7 MPH (15kph).
• NOTE: the Action Tracker HOS application will also change the driver’s current duty status automatically to On-Duty from drive when the vehicle stops. The Action Tracker HOS application senses the vehicle has stopped and starts a 5 minute timer. If not movement is sensed during this 5 minutes, a popup screen appears on the HOS Dashboard screen alerting the driver that it is going to make an automatic duty status change from Drive to On-Duty in 30 seconds. The 30 second clock counts down to 0 and if the driver hasn’t cancelled this automatic change, the application will make the change EFFECTIVE when the 5 minute timer started. This way, no drive time is lost and the driver has complete control over whether this automatic duty status change will occur. This is useful when the driver is stuck on the road and can’t move the truck for a period of time longer than the 5 minutes and 30 seconds but doesn’t want to have the system make the change from Drive status to On-Duty status.
When the Current Duty status button is pressed on the HOS
Dashboard the driver sees the Duty Status Change screen.
• The driver would press the ON button to change their current duty status to On-Duty.
Change Duty Status
The driver will see the Duty Status Change screen.
1
This line will show what duty status change the driver is about to make.• The Location (City/State or Province) will come back from the server.
2
If the Android Device is not connected to the server, the GPS locationwill still be recorded. The driver can tap in the white field area and a keyboard will appear on the screen so the driver can enter the required location information.
3
The Odometer value will be displayed if the Android Device is paired witha Power Unit and in communication range of the equipment in that asset. • If the equipment is mounted in a Power Unit that doesn’t have a J-1708
or J-1939 ECM connection, the equipment mounted in the vehicle will provide the Odometer value based on the Life-To-Date Odometer value entered at installation to match the vehicle’s Odometer. The equipment’s GPS will capture the vehicle’s distance traveled and increment the Life-To-Date Odometer value to retain the synchronized value.
• Both methods are fully ELD (Electronic Logging Device) compliant with H. R. 4348—372; also known as MAP-21, Subtitle C – Driver Safety, Sec. 32301, Paragraph 31137, (b) – ELECTRONIC LOGGING DEVICE REQUIREMENTS (1)(A)(iv)
The information entered on this Duty Status Change screen will
appear on the driver’s log. There is also a method for the driver to enter
“internal” information that does not appear on their log but is available
for viewing/printing/exporting from the Fleet Complete office server.
4
The driver can enter shipping information, select Unladen, DefaultCommodity or leave this information blank if it isn’t necessary for this duty status change.
5
The driver can select a Sub-Code for this duty status change from alist of “duty-sensitive” descriptions. Fleet managers have the ability to customize these Sub-Codes. This entry is from a selection from a list rather than free form entry.
6
The driver can enter a Remark that will appear in the Remark section onthe driver’s log if they desire to show additional information about this duty status change.
7
The driver presses the Commit to Log button when they are finished withthe information related to this duty status change.
8
If the driver decides not to make a duty status change at this point, they simply press the “return” arrow to be returned back to their HOS Dashboard.3
2
1
4
5
6
7
8
Action Tracker - HOS has two log formats. One for
Canadian Rule drivers and one for US – FMCSA Rule
drivers. Action Tracker HOS determines the log format
cased on the Fleet’s default rule selection in Fleet
Complete office’s desktop application.
Below is an example of a Canadian Rule driver.
The driver’s enters in the Duty Status Change screen,
shown on the previous page, provides the information
for the log form. Much of the information is
automatically provided for the driver.
1
The driver has the ability to determine if they are using aDeferral Rule and the required information
2
Driver Sub-Codes selections are shown here.3
Location information is shown here.4
Ship/Invoice/Commodity is shown here.5
Any Remarks entered by the driver are shown here(enclosed in the parenthesis), these Remarks can be fairly long and will wrap down to the next line moving the information below down to make room.
The driver’s signature also appears at the bottom of their
daily log. They are given the opportunity to sign their
daily log when they log Off-Duty. They do not have to
sign their log if the Off-Duty status they are changing to
is not their End-of-Day duty status change.
• Signatures to Electronic Logs are not required however, if the driver’s log is printed at any time, then the paper version does require a signature. Thus we have provided for the driver’s signature to their daily log so management can print the driver’s daily log without having to worry about getting the driver to sign the printed log.
Driver’s Log – Canadian Form
1
Action Tracker - HOS has two log formats. One for
Canadian Rule drivers and one for US – FMCSA Rule
drivers. Action Tracker HOS determines the log format
cased on the Fleet’s default rule selection in Fleet
Complete office’s desktop application.
Below is an example of a Canadian Rule driver.
The driver’s enters in the Duty Status Change screen,
shown on the previous page, provides the information
for the log form. Much of the information is
automatically provided for the driver.
1
The driver has the ability to determine if they are using aDeferral Rule and the required information
2
Driver Sub-Codes selections are shown here.3
Location information is shown here.4
Ship/Invoice/Commodity is shown here.5
Any Remarks entered by the driver are shown here(enclosed in the parenthesis), these Remarks can be fairly long and will wrap down to the next line moving the information below down to make room.
The driver’s signature also appears at the bottom of their
daily log. They are given the opportunity to sign their
daily log when they log Off-Duty. They do not have to
sign their log if the Off-Duty status they are changing to
is not their End-of-Day duty status change.
• Signatures to Electronic Logs are not required however, if the driver’s log is printed at any time, then the paper version does require a signature. Thus we have provided for the driver’s signature to their daily log so management can print the driver’s daily log without having to worry about getting the driver to sign the printed log.
Driver’s Log – United States Form
1
2
3
4
The driver is returned to the HOS Dashboard screen after they have
pressed the Commit To Log button on their Duty Status Change
screen.
• The Current Duty Status button show their new duty status. • The information in the next part of the screen is continually being
updated.
• The graph reflects the change
• All the timers are continually being updated.
The driver would normally next go to their Power Unit and pair their
Android Device with the equipment fix mounted in the Power Unit. If
they last drove this Power Unit and didn’t drop it at the end of their
last shift, the pairing would still be retained and the “Chain Links” will
show as unbroken when the Android Device comes back in range of
the paired equipment mounted in the Power Unit.
1
If this Android Device is not paired with the equipment mounted ina Power Unit, the driver would select the menu button to select their Power Unit.
Pairing the Android Device with the equipment mounted in the Power
Unit is started from a Menu option.
Next we will review the Menu options in detail.
Pairing the Android Device to the
equipment in a Power Unit
1
The menu appears at the bottom of the HOS Dashboard screen. Themenu selections are:
• Internal Note
• Allows the driver to enter a Sub-Code and/or Remark that does not appear on their driver’s log but are available in the Fleet Complete office application.
• Drivers…
• Duty Status Details • Change Active Rule
• Add and Remove Co-Driver (for team drivers)
• Manage Assets
• To pair Power Unit and Towed Assets • Access to DVIR functionality
• Daily Logs
• View driver’s duty status events
• Access to Driver Edit Request functionality • View Paper Log for required number of days
• Roadside Inspection
• For Roadside Inspector to view driver log(s) and current DVIR. Entering the Roadside Inspection mode locks Inspector from any other access. Entry of the Driver’s PIN is required to re-enter.
• More
• Updating various Android Device’s databases • Driver’s logout from Action Tracker HOS application
HOS Dashboard
Menu Choices
1
The driver presses the Manage Asset button to pair their Android Devicewith a Power Unit’s equipment.
If the driver had previously assigned a Power Unit (and Towed unit or
units) from the previous shift and hadn’t dropped the Power Unit or
Towed Units, they will appear on this screen.
The Android Device reconnect with the assigned Power Unit when it
comes in range of the vehicle mounted equipment.
If the driver does not have a Power Unit already assigned, they will see
this Manage Assets screen to the right.
• The driver presses the Create New Assignment button located under the Power Unit
Menu Options – Manage Assets
1
The driver has several options from this screen.
2
The driver can Scan for units in range of the Android Device• They can do their HOS log in Manual mode. This mode is currently provided for in the FMCSA 395.15 rule (until the ELD mandate goes into effect). This mode would be used for vehicles that are not equipped with the required equipment.
Manage Assets – Power Units
2
The Android Device finds any Power Unit in range of the Bluetooth
radio (The Android Device filters out any Bluetooth equipment other
than the desired vehicle mounted equipment)
1
The equipment found during the scan is displayed. The driver selectsthe desired equipment (fleets use their normal Power Unit identification process).
2
The driver selects the desired Power Unit and presses the Connect toselected unit button.
Manage Assets – Power Unit Connected
The driver can now assign Towed Units. The application any type of
Towed Asset and handles multiple Towed Assets including Doubles,
Triples and even Dollys between the trailers.
The driver sees a list of Towed Units when they press the Create New
Assignment button under the Towed Units section.
The driver can also Add New Towed Unit to the database for tracking
Towed Units not in the dat
Manage Assets – Scan for units in range
1
The driver can proceed to generate a new DVIR for each unit. NOTE:
The DVIR functionality and report formats is extremely flexible.
The application includes 3 separate report forms that can be assigned
to associated equipment.
Additionally, a fleet can request Complete Innovations’ programmers
to program their own special DVIR Form(s) for a small one-time fee.
The Fleet can decide to a separate DVIR form for the Power Unit and
Towed Unit(s) or have a single one to cover all the equipment.
No matter which way a Fleet chooses to handle their DVIR report, the
DVIR report is displayed for a Roadside Inspector as one historical
report – the current DVIR inspection.
The driver starts their DVIR by pressing the Create Report button.
The driver will see the Inspection Schedule that is assigned to the unit
selected.
• The Unit description is displayed at the top of the screen.
• The driver selects the Inspection Type by pressing the Inspection Type field and selecting the choices from the popup box.
• The vehicle’s Odometer reading is displayed (if the reading is incorrect or not present, the driver can enter the Odometer reading.
• The driver can enter a value for the Engine Hours if desired • The driver can press the ALL OK box if all items are OK
1
(this will turn all the boxes in the first column of the form green)
The Driver’s Vehicle Inspection Report
(DVIR)
There are three columns of boxes
2
The first column (the left column) is the OK column3
The second column if the issue/defect column4
The third column is the N/A (Not Applicable) column5
The driver presses the N/A (the column under the blue dot – furthest tothe right) for an item that is not applicable to the inspection on this unit
6
If any category has an issue, the driver presses the white button in thesecond column to the right of the category with an issue. We will select the Hydraulic Brake System as an example.
The Driver’s DVIR (continued)
2
3
4
5
A popup box of both Major and Minor issue descriptions will appear.
The driver selects the one that best describes the issue they have
found.
7
The Red and Yellow circles to the left of the descriptionindicate Major (Red circle) or Minor (Yellow circle) severity for the issue
We will select the Minor “Brake fluid level is below indicated minimum
level” description
8
The description selected will be added to the report.9
The driver can add any Remarks to this issue (these will appear on theDVIR report)
10
The driver can take a photo of the issue (that will be attached to thereport) if the company has enabled the “Take Photo” functionality
11
The driver (or mechanic) can process the repair now or later and sign-offon the repair
12
The driver can commit this defect description to this report7
8
9
10
11
12
1
The driver can select the Is Repair Required box to turn the bar green2
The driver (or mechanic) can select the Has Repair Been Made box to turnthe bar green
3
The driver (or mechanic) can enter a Work Order number4
The driver (or mechanic) can enter any Shop Remarks they desire toappear on the DVIR
5
Swiping the screen upward will reveal the Sign Repair button6
The driver (or mechanic) signs off on this repair on the Android Device’sscreen and commits the repair to the DVIR report
The Driver’s DVIR – Process Repair
1
2
3
4
5
6
7
The defect is noted on the Inspection Schedule Screen8
When the driver has completed the DVIR, they return to the AssetManagement screen by pressing the return button on the Android Device
The driver sees a list of DVIR inspection reports that they have to sign
(in this case the Power Unit)
9
The driver selects the report(s) from this displayed listThe unsigned DVIR reports are shown with a red circle with an “X” in
the button.
10
The driver presses the Sign Inspection Report button to go to thesignature screen.
11
The driver (or non-driving inspector) signs the DVIR and Commits it tothe Report – completing the DVIR
An entry is made to the driver’s log when the report is finished
The Driver’s DVIR - Process Repair
(continued)
7
8
The DVIR functionality can accommodate:
• Drivers who inspect the equipment
• Non-Driving Inspectors with the driver’s sign-off before operating the equipment
• Defect recording
• Major or Minor defect with appropriate suggested descriptions • Ability for the inspector to make their own remarks
• Ability to take a photo of the defect (at the company’s discretion) • Driver, mechanic or other person conducting a repair sign-off • Any designated type of repair, such as Pre-Trip, Safety Check, Brake Check, Post-Trip or any other choice a company may desire
• One form per each inspection
• Or one form for the 24-hour shift with multiple drivers sign-off • Indicator of which inspector or mechanic signed-off on which item
Coming in next phase
Inspection reports can be archived to a Fleet’s designated server location for retention of records for the required 2 year period. Currently the Fleet Complete system keeps all data for 12 months from the generation of it, so this feature is not required for at least 12 months.
Fleet Managers can recall reports either as a historical report or as in an asset tracking of issues/defects mode.
1
The driver can view their current log and the required historical logs (7days +current day for the US and 14 days + current day for Canada) by pressing the Daily Logs selection from the menu selections.
The next screen shows the driver all the events on their log for the
current day.
From this screen the driver can:
• Request an Edit to any non-driving event be made by the supervisor authorized to make log edits
2
The driver selects the non-driving event they wish to have edited from thelist and presses the Edit Duty Status Change
• An email will be sent to the email address assigned to this activity in Fleet Complete
3
The driver can also select to Add a Duty Status Change. This would beused when a driver needs to have a non-driving duty status added to their log rather than having just the start or end of an event moved
4
The driver selects the day’s log using these buttons5
The drive can also select to view their daily log(s) in a paper view formatas shown in the Driver’s Log Form section of this document
Daily Logs
1
2
3
4
5
The driver selects an event from the Events – Date screen when they
wish to have that event edited.
In this example, we will select the 1:33 PM Off-Duty event
1
The lower portion of this screen is where the driver makes the
requested changes and then submits their edit request.
• When the supervisor makes the change, the original version is retained in the Fleet Complete office database as well as the last edited version for the event.
• Any reports that contain edited data is so noted
• The edited version is sent back to the Android Device’s database
The driver will see the Request Log Edit
screen
• The current Logged Duty Status, Logged Date/Time, Logged Location and Event Details will be displayed.
• The Actual Date/Time area is where the driver will select the Date/Time that they want this event
Driver Request Log Edit
The Add Event functionality is very similar to the Edit Event except
that it is a two-step process. The first step is to add the beginning of
the event and descriptions and the second step is to add the ending of
the event and descriptions.
Driver Request Log Edit – Add Event
(continued)
The FMCSA is very specific on how edits are to be made for drivers using an automatic on-board recording device.
Question 2: May a driver who uses an automatic on-board recording device amend his/her record of duty status during a trip? Guidance: No. Section 395.15(i)(3) requires automatic onboard recording devices, to the maximum extent possible, be tamperproof
and preclude the alteration of information collected concerning a driver’s hours of service. If drivers, who use automatic on-board recording devices, were allowed to amend their record of duty status while in transit, legitimate amendments could not be distinguished from falsifications. Records of duty status maintained and generated by an automatic on-board recording device may only be edited by a supervisory motor carrier official to accurately reflect the driver’s activity. Such supervisory motor carrier official must include an explanation of the mistake in the remarks section of either the original or amended record of duty status. Both the original and amended record of duty status must be retained by the motor carrier.
First, the driver is not allowed to amend his/her record of duty status during a trip and…
Second, “Records of duty status maintained and generated by an automatic on-board recording device may only be edited by a
supervisory motor carrier official to accurately reflect the driver’s activity”.
So, even if the “during a trip” is open to interpretation, the “only be edited by a supervisory motor carrier official” is very straight forward.
So the “No” answer in the Guidance leaves very little possibility open that a driver may edit their electronic log.
Additionally the FMCSA specifies parameters for the Performance of Recorders as outlined below.
(i) Performance of recorders. Motor arriers that use automatic on-board recording devices for recording their drivers’ records of duty status in lieu of the handwritten record shall ensure that: (1) A certificate is obtained from the manufacturer certifying that the design of the automatic on-board recorder has been sifficiently tested to meet the requireents of this section and under the
conditions it will be used;
(2) The automatic on-board recording device permits duty status to be updated only when the commercial motor vehicle is at rest except when registering the time a commercial motor vehicle crosses a State boundary;
(3) The automatic on-board recording device and associated support systems are, to the maximum extent practicable, tamperproof and do not permit altering of the information collected concerning the driver’s hours of service;
(4) The automatic on-board recording device warns the driver visually and/or audibly that the device has ceased to function. Devices installed and operational as of October 31, 1988, and authorized to be used in lieu of the handwritten record of duty status by the FMCSA are exempted from this requirement.
(5) Automatic on-board recording devices with electronic displays shall have the capability of displaying the following: (i) Driver’s total hours of driving today;
(ii) The total hours on duty today; (iii) Total miles driving today;
(iv) Total hours on duty for the 7 consecutive day period, including today;
(v) Total hours on duty for the prior 8 consecutive day period, including the present day; and
(vi) The sequential changes in duty status and the times the changes occured for each driver using the device.
(6) The on-board recorder is capable of recording separately each driver’s duty status when there is a multiple-driver operation;
(7) The on-board recording device/system indentifies sensor failures and edited data when reproduced in printed form. Devices installed and operational as of October 31, 1988, and authorized to be used in lieu of the hardwritten record of duty status by the FMCSA are exempted from this requirement.
(8) The on-board recording device is maintained and recalibrated in accordance with the manufacturer’s specifications; (9) The motor carrier’s drivers are adequately trained regarding the proper operation of the device; and
(10) The motor carrier must maintain a second copy (back-up copy) of the electronic hours-of-service files, by month, in a different physical location than where the original data is stored.
FMCSA Rules relating to Log Edits
1
The driver selects the Roadside Inspection selection when they have beenrequested to show their driver’s log(s) or current DVIR
2
The driver can then show the Roadside Inspector the required day’shistory of their logs and the current DVIR form. Both document types will only show the paper view as already shown.
Additionally, when the Roadside Inspector or driver selects the Return
button, the screen returns to the driver’s Login screen. This is to show
only the required information during a Roadside Inspection.
Roadside Inspection
1
1
The More menu selection contains additional tools plus the Driver’sLogout choice.
The Synchronization… choice provides for updating of Asset and Driver
Databases on the Android Device. The reason that this selection exists
is so the driver can update these Android Device databases while in
WiFi coverage to reduce data loads on the cellular data plan (if the
Android Device is equipped with a WiFi radio).
The Settings… button provides other support tools
The driver’s Logout button logs the driver out of the application and
returns to the Login screen.
2
If the driver wants to access other Android Device applications theywould press the Home button.
