Contents

Driver Login

Choose Truck & Trailer

Driver Dashboard

Order Section

App Menu

Log Page

Daily Log

Certifying Records

Data tab

Data Transfer

ELD Authentication Value Validation

Malfunction & Diagnostic

Driver Manual

8

9

10

11

2

4

5

7

12

13

14

15

Driver Login

Driver Login (Part 1)

The driver is presented with a list of accounts when the tablet is turned on or activated. The driver must select their name from the list provided to complete login and change their duty status.

Notes

The company administration department is responsible for adding, editing and deleting all driver information. Once the driver has been added into the driver management system, their name will appear as shown on the left. Motor carriers are required to manage their ELD accounts, including creating, deactivating, and updating accounts and ensuring that individuals have

ELD accounts with appropriate rights. Each driver must have a unique ELD drivername.

Each driver account must include the driver’s name, license number, and licensing state.

Page 2

Driver Login (Part 2)

After selecting their name from the list, the driver will need to enter their 4 digit unique pin to log in. After login, the CLD creates a connection between the onboard GPS device and ELD application. There can only be one unique driver connection at a time.

Notes

The drivers pin should be confidential and should not be shared with any other employee.

Pin Generation

If the driver has not yet set a pin, they will be sent an SMS text message to their cell phone on on record. This message will contain a special code to validate their account. They will then be redirected to page where he should enter this verification code. After verifying their phone number, the driver will be given opportunity for setting their pin.

Page 3

Choose Truck & Trailer

Truck & Trailer Selection

Before proceeding to the dashboard page, the driver is asked to choose truck and trailer. These steps can be skipped, but the driver must select a truck & trailer before the beginning of each shift (overwise they are not allowed to change duty status).

Notes

The driver MUST log out after each shift to make the truck & trailer available for the next driver.

Page 4

information about their activity for that day.

As per the ELD mandate, the device will automatically change status between On

Duty and Driving as well as Driving and On

Duty. The driver will be presented with notifications to confirm the duty type status change.

Company personal must log all Yard Moves using the YM button shown on the dashboard. (See below for a definition of each button)

Driver Dashboard

The driver dashboard is where the employee will see

Off Duty – The driver is not working.

Sleeper Berth

Driving

– The driver is resting in the truck’s sleeper area. (Long distance)

– The driver is actually driving the vehicle.

On Duty Not Driving – The driver is doing work other than driving, such as fueling, inspection, unloading freight, etc.

YM (Yard Moves) property.

– Used for mechanics and drivers who move a truck around the motor carriers

On Duty status change, timer for each duty status is activated and the Hours of service rule is applied to those.

11-hour driving rule – A driver may drive up to 11 hours total before he is required to take a 10-hour break. The 11-hour clock only ticks while the truck is actually being driven.

14-hour on duty shift rule – As soon as a driver changes his status to On Duty or Driving to start his day, a 14-hour clock starts ticking. This clock DOES NOT STOP ticking, even if the driver switches to

Off Duty or Sleeper Berth. Once the 14 hours is up, the driver must take a 10-hour break before driving any more.

70-hour in 8 days rule (or 60 in 7) – Total time spent Driving and On Duty cannot exceed 70 hours in any 8-day period. So add up the time spent Driving and On Duty today, plus the prior 7 days. That total cannot be over 70 hours. A driver may “gain back” time at midnight when the oldest day in his 8-day

Page 5

window falls out of the time range. To completely reset the 70-hour clock requires a 34-hour restart

(see below). There is also a variation of this rule that works the same way, but limits work time to 60 hours in 7 days. Fleets can decide which of these two variations they want to use.

8-hour, 30-minute break rule – When the driver comes off a break and changes to On Duty or

Driving, an 8-hour clock starts ticking. Before the 8 hours is up, the driver must take at least a

30-minute rest break in Off Duty or Sleeper status. After the 30-minute break, the driver has at most other 8 hours to work before he is required to take another 30-minute break.

10-hour break – If time on the 11-hour or 14-hour clock has expired, the driver must take at least 10 consecutive hours in Off Duty and/or Sleeper Berth status to reset those clocks.

34-hour restart – If a driver is running low on time on his 70-hour in 8 days clock (or 60-hour in 7 days), he can complete a 34-hour restart to reset the 70-hour clock. A restart must be 34 consecutive hours of Off Duty and/or Sleeper Berth time. (Note: there used to be some additional rules placed on the 34-hour restart. These old rules dictated that it could only be used once every 7 days and that it had to include two mornings from 1am-5am. These rules were suspended in 2014 and are no longer in effect)

The ELD automatically records the date, time, geographic location (accurate to a one-mile radius), engine hours, vehicle miles, driver or driver ID, vehicle ID, and motor carrier ID. The data is recorded at power-up and shutdown, at every change in duty status, at least every hour while the vehicle is moving, whenever a driver logs in or out, and when an ELD detects or clears a malfunction or diagnostic event.

Page 6

Order Section

Once clocked in, the timer and orders section for that driver becomes activated. The driver can see their clock-in time located in menu available located in left upper corner of the app. In the orders section of the menu the driver can see all of the information about the orders assigned to them. The driver should log all information of each order and information can be changed later if needed.

Page 7

App Menu

The menu is used for navigating through the application. Drivers can change their truck or trailer, check when they clock in/out, access their logs, access the dashboard, and transfer data using the menu.

Page 8

Log Page

This page lets you see the daily driver logs for the last 8 days. The log chart will be shown for the current day by default but the driver has the ability to change the day. If the log is not certified a notification about that is shown. The driver can certify records for that day by going to daily log page by clicking on

VIEW button. Before logging out the driver is forced to certify the records for the day if they have not been certified yet (otherwise it is certified automatically). If someone operates an ELD-equipped vehicle without logging in, the ELD data that gets collected has to be stored in an “unidentified driver” account. When a driver logs in to that ELD, the driver will be prompted to review any unassigned driving time and must indicate whether that time belongs to that driver.

Motor carriers have to make sure that “unidentified driving” records are reviewed and must assign the time to the correct driver or add notes to explain why the time is unassigned.

If there are unidentified records the driver will be able to see the “unidentified records” tab next to their logs.

The driver can assign unidentified logs to themselves by going to daily log page for that unidentified logs.

Page 9

Daily Log

The daily log page contains records for specific date and displays a chart for that day logs.

Record include the following:

● Records Automatically Logged by ELD

● Driver Edits

● Driver Change Duty Status

● Driver Entries

● Driver's Assumption of Unidentified

Driver Logs (from APP)

● Assign Unidentified Driver Logs (from

OTIS)

● Motor Carrier Edit Suggestions

● Driver's Actions Over Motor Carrier Edit

Suggestions

● Malfunction and Data Diagnostic Events

An ELD must monitor and be compliant with the ELD mandates technical requirements and detect malfunctions and data inconsistencies related to power, data synchronization, missing data, timing, positioning, data recording, data transfer, and unidentified driver records requirements. The ELD output will identify these data diagnostic and malfunction events and their status as either “detected” or “cleared.” Typically, a driver can follow the ELD provider’s and the motor carrier’s recommendations to resolve the data inconsistencies that generate an ELD data diagnostic event, while a motor carrier must correct a malfunction

“Power data diagnostic events” occur when an ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power and does not remain powered for as long as the vehicle’s engine stays powered.

“Power data diagnostic events” occur when an ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power and does not remain powered for as long as the vehicle’s engine stays powered.

“Power compliance malfunctions” occur when an ELD is not powered for an aggregated in-motion driving time of

30 minutes or more over a 24-hour period across all driver profiles .

Page 10

Certifying Records

Drivers can review their ELD records, edit and correct inaccuracies, enter any missing information, and certify that the information is accurate for that day. Drivers must also submit their ELD records to the motor carrier within

8 days. If any edits are needed after an ELD record has been submitted, the driver has to make the edits through the ELD and then re-certify the record. Changes or additions to a record have to be explained. After reviewing a driver’s submitted logs (but not before they have been submitted), the motor carrier can request edits to ensure accuracy.

The driver must confirm or reject any proposed changes, make the appropriate edits, and re-certify the record. No one may alter or erase the original information collected about driver’s hours of service

Page 11

Data tab

During an inspection, drivers must be able to display or print their logs for inspection.

For that driver must go to the data tab of the daily log page. Upon request, drivers must also transfer their

ELD records electronically to the enforcement official for on-the-spot auditing, including logs for today and the prior seven days. There are two ways for doing this: either with email or via web service.

For Data transfer driver must go to menu/dashboard and go to data transfer page.

Page 12

Data Transfer

Clicking on the Data Transfer button from the Menu or from header in dashboard page, will display the list of supported data transfer options. The ELD provides a standardized single-step compilation for the driver’s

ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection.

The safety official can fill in a routing code to reference in the email in “Comment” field.

By clicking “Send Email” electronic data transfer file will be generated on the server and then sent as an attachment to an official email. This email address is pre programmed in the ELD by the vendor.

By clicking “Send Via Web Service” file will be generated on the server and file transfer will be initiated to FMCSA server.

Page 13

ELD Authentication Value Validation

Description : An alphanumeric value that is unique to an ELD and verifies the authenticity of the given

ELD.

Purpose : Provides ability to cross-check the authenticity of an ELD used in the recording of a driver’s records during inspections.

Source : ELD provider-assigned value; includes a certificate component and a hashed component; necessary information related to authentication keys and hash procedures disclosed by the registered ELD provider during the online ELD certification process for independent verification by

FMCSA systems.

Used in : ELD outputs.

Data Type : Calculated from the authentication key and calculation procedure privately distributed by the ELD provider to FMCSA during the ELD registration process.

Data Range : Alphanumeric combination.

Data Length : 16-32 characters.

Data Format : <CCCC………CCCC>.

Disposition : Mandatory.

Example : [D3A4506EC8FF566B506EC8FF566BDFBB].

Procedure to validate:

1. Concatenate the driver license number, ELD identifier and ELD registration ID together. If there is no driver license number (for "non-driver" account), use the empty string for the driver license number.

2. Hash the value from Step 1 using sha-256

3. Take the first 32 characters bytes from the string from Step 2. This is the authentication value.

Page 14

Malfunction & Diagnostic

At Each instance when an ELD malfunction or data diagnostic event is detected or cleared by the ELD, the ELD records the event. The recorded malfunctions and data diagnostic events are inconsistencies found while monitoring the app/ELD against FMCSA compliance requirements. These instances are indicated in the application header with 2 icon indicators (Diagnostic and Malfunction). If an Diagnostic or Malfunction Event occurred appropriate indicator will become red and Record will be created and saved in ELD. To know more info about the event occured, click on the red indicator and it will show popup with the event message. If event has been cleared by the ELD indicator it will then go back to a normal state.

Here is the list of messages and codes for Diagnostic and Malfunction Events:

Table 4

Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection

Malfunction Events

Malfunction/ Diagnostic Code

P

E

T

S

O

L

R

Malfunction Description

“Power compliance” malfunction

“Engine synchronization compliance” malfunction

“Timing compliance” malfunction

“Positioning compliance” malfunction

“Data recording compliance” malfunction

“Data transfer compliance” malfunction

“Other” ELD detected malfunction

Page 15

Diagnostiс Events

Malfunction/ Diagnostic Code

1

2

3

4

5

6

Data Diagnostic Event

“Power data diagnostic” event

“Engine synchronization data diagnostic” event

“Missing required data elements data diagnostic” event

“Data transfer data diagnostic” event

“Unidentified driving records data diagnostic” event

“Other” ELD identified diagnostic event

Page 16

Before Logout

● Driver’s duty status is set to off duty

● Driver’s daily records must be certified. (Only the driver can view and certify them or they will be certified automatically)

● Orders must be confirmed for correctness of data

● Driver is clocked out

Page 17