User manual for "INTELELOGS"
Below you will find the vendor-provided user manual for the ELD product "INTELELOGS".
For vendor contact details and additional devices from the same company, see their page
Intelligent Telematics Inc..
Manual text preview
Rev. 1.15 Hours of Service (HOS) Mobile APP Drivers Guide Booklet INTRODUCTION AND COMPLIANCE The latest HOS Mobile APP, released on the first half of 2015, is complaint with US Federal FMCSA title 49 part 395 AOBRD 395.15, 395.16 and the latest modifications to the rule including the current suspension of the two 1am to 5am OFF duty periods for the 34 hours restart. There is Certification menu option that indicates that the mobile APP, mobile device used were self-certified according to federal requirement. The driver's log file exported by the mobile APP is generated according to the latest ELD data element dictionary released by FMCSA. Contents page - Introduction and compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - Self-certification ................................. 3 - Account types (driver, support personnel, non-authenticated) . . . . . . 3 LOGGING ON - Driver login and Support Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - Bluetooth device discovery and pairing. ELD diagnostic . . . . . . . . . . . . 4 DRIVERS ACTIVITIES - BEFORE CHANGING DRIVER STATUS - Vehicle profile ................................. 5 - Drivers profile. Team drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - Creating shipments ................................. 7 - Assumption of unidentified records . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - Malfunction/Diagnostic indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 WORKING WITH THE APP AND CREATING DRIVER LOGS - Personal use, yard moves and exemptions . . . . . . . . . . . . . . . . . . . . . . 8 - Changing drivers status and Principal screen . . . . . . . . . . . . . . . . . . . . 8 - Remaining times ................................. 9 - Violations (proactive notifications and occurrence) . . . . . . . . . . . . . . . 9 - Reviewing, editing and certifying drivers logs . . . . . . . . . . . . . . . . . . . 10 - Creating annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 - Logs chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 - LogBook and Exporting Drivers Logs (Print/Display and . . . . . . . . . . . 11 Data file transfer) p.1 Regulations the mobile APP is compliant with: - 60-hour/7 days or 70-hour/8 days Rules - 34 hour week restart with latest suspension of two periods 1-5am - 11 hours driving for the day - 14 hours on duty for the day - Sleeper Berth provision - Passenger Seat provision - Personal Conveyance provision - 30 minutes break provision - Canada Cycle 1 and 2 Regulations - Location recording for vehicles engine turned on and off, and location recording every 60 minutes if vehicle is moving - Mobile device permits duty status changes only when the vehicle is at rest - The mobile device warns the driver, visually and/or audibly of any malfunction - When the vehicle is stationary for 5 minutes or more, the mobile device will default to on-duty not driving and the driver must enter the proper status - The mobile device (ELD) performs self-test, as well as a self-test at any point upon request of an authorized safety assurance official The HOS Mobile APP is not compliant for (exclusions): - Passenger-carrying vehicles - States of Hawaii and Alaska p.2 FMCSA REGISTRATION As a substitution to an exterior faceplate, a Certification menu item will display the certification image as evidence that the mobile device has been tested, certified and approved as meeting the performance requirements. SUPPORT PERSONNEL Bluetooth discovery and pairing. ELD Diagnostic When an ELD is installed, support personnel must do the initial configuration and diagnostic of the ELD. From the login screen select the Support option from the menu (top right corner). The support personnel will scan for ECM-Link devices. Once the ECM-Link device shows in the screen, tap on it and a diagnostic will be performed on the EDL to make sure all necessary functionality is available. Once the diagnostic passes, the ELD is ready for driver operation. In order for the ELD to be compliant several parameters must be acquired from the vehicles Engine Control Module (ECM) and other internal systems have to be verified. During the diagnostic, the mobile APP will begin collecting the necessary engine data. Support personnel can only release the ELD for driver use after all ELD diagnostics were successfully performed: ACCOUNT TYPES Driver: Unique, per-driver account used by drivers under 49 CFR Parts 385, 386, 390, and 395 regulations (hereon HOS). This account records duty status changes (RODS) and allows the export of drivers records for display, print and agent output file generation. Support: Account used by the carrier and ELD manufacturer to setup, configure, update and troubleshoot the ELD. No duty status changes are recorded with this account and no access to drivers record of duty status changes is permitted under the support account. Non-authenticated: All operation of a commercial motor vehicle (CMV) is recorded under this account (a.k.a Unidentified Driver) if no driver has logged into the ELD. Non-authenticated records (vehicle movement and on-duty time) are stored on the ELD as well as the carrier and should be assumed by a driver account. p.3 DRIVER LOGIN Each driver using the system will have a unique login ID. This login name and password is for the specific drivers use only and must not be shared with any other person (driver or not). The login name belongs to the driver and is linked to the drivers personal information (e.g. drivers license, etcetera). If the driver changes carrier and is now driving for a different carrier, the login name will remain the same and is the drivers obligation to ask the home base carrier to update carrier name and DOT number on the system. p.4 The driver is restricted to be logged on to only one mobile device at any time. In order for the driver to logon on a diffe