User manual for "CoreHub"
Below you will find the vendor provided user manual for the ELD product "CoreHub".
For contact information and additional devices produced by the same vendor see their page
Coretex.
Driver Guide Driver Guide Coretex DRIVE: ELD Driver Guide OPIN Product: Version: Release Type: Release Date: Coretex DRIVE/Coretex 360 Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use Jun 2019 Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 1 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Contents About this guide 4 Coretex ELD solution 5 Overview of Coretex DRIVE 7 Mobile device hardware .................................................................................................................... 8 Mobile device procedures 9 Starting your trip with Sign In ............................................................................................................ 9 Sign Out at the end of your trip ...................................................................................................... 14 Looking at the dashboard 16 Main features .................................................................................................................................. 16 Driver duty status ............................................................................................................................ 17 Driver in charge ............................................................................................................................... 18 Information Cards ........................................................................................................................... 19 Dashboard menu (off main dashboard) ........................................................................................ 20 Changing your vehicle/trailer for the trip ...................................................................................... 20 Driver Logs 21 Driver Log View ................................................................................................................................ 21 Driver Log Edits ............................................................................................................................... 25 Violations and Warnings (for Hours of Service) ............................................................................ 30 Supervisor Proposed Edits ............................................................................................................. 32 Unidentified driving records ........................................................................................................... 33 Resolving missing data ................................................................................................................... 34 Certify your logs ............................................................................................................................... 35 Data diagnostics and malfunctions ............................................................................................... 36 Emailing your logs to yourself......................................................................................................... 37 Reviewing resources used .............................................................................................................. 38 Burndown gauge on your dashboard............................................................................................. 39 Available Drive time ........................................................................................................................ 40 Gain time on the dashboard........................................................................................................... 40 Roadside Inspections 41 Unidentified Driving Records .......................................................................................................... 44 DATA TRANSFER initiated by Safety Officer .................................................................................. 45 Rules and Availability 49 Selecting a current ruleset ............................................................................................................. 49 Dealing with ruleset exceptions ..................................................................................................... 50 Preview Availability screen ............................................................................................................. 52 Co-drivers 53 Driver in focus ................................................................................................................................. 53 Add a new co-driver......................................................................................................................... 53 Switch a co-driver to be the current driver in charge.................................................................... 53 Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 2 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Accessing Apps 54 Loading installed apps.................................................................................................................... 55 Dashboard Quick Apps ................................................................................................................... 56 DVIR Inspection History .................................................................................................................. 56 Removing tile associations ............................................................................................................. 56 Appendix:A - Dealing with connection and Data Diagnostic/Malfunction events 57 Problems with internet connection ................................................................................................ 57 Data Diagnostic events................................................................................................................... 58 Malfunction events ......................................................................................................................... 60 Appendix:B - Dashboard menu 63 Off the main dashboard screen ..................................................................................................... 63 Appendix:C - ELD DRIVER PORTAL in Coretex 360 66 ELD DRIVER PORTAL ....................................................................................................................... 66 DRIVER PORTAL Driver Hours ..................................................................................................... 67 DRIVER PORTAL Driver Log View/Edit ........................................................................................ 69 ELD Glossary 80 Index 86 Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 3 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide About this guide This Coretex DRIVE: ELD Driver Guide is a reference to using the Coretex DRIVE application with integrated ELD and Vehicles Inspections (DVIR) on an Android mobile device (tablet or suitable smartphone), and is intended to allow drivers to follow the most common step-by-step procedures they need to do. Intended audience This Coretex DRIVE: ELD Driver Guide is for Coretex customers (drivers) making use of Coretex DRIVE on their mobile devices in cab with their delivery trips. North America customers only ELD and Driver Hours functionality, as described in this guide is specific to North America. Related documentation This guide is intended to be used in conjunction with the following documents: Guide Title Coretex 360: ELD Administration Guide Category Admin Coretex 360 - DVIR: Administration Guide Admin Coretex DRIVE: DVIR User Guide User Quick Reference Coretex DRIVE: Driver In-cab Guide (General Operations) Quick Reference Coretex DRIVE: Driver In-cab Guide (Data Diagnostics/Malfunctions) Quick Reference Coretex DRIVE: ELD Visor Card Coretex DRIVE: TMU Installation Guide User (Driver) User (Driver) User (Driver) Install Description Administration guide for supervisors/administrators configuring the Coretex ELD solution in Coretex 360. Administration guide for supervisors/administrators using Coretex 360 to configure DVIR for drivers and users More detailed User Guide for use of Vehicle Inspections or DVIR (Driver Vehicle Inspection Reports) within Coretex DRIVE Quick Reference guide for drivers to keep in their vehicles for use of the Coretex ELD Solution with Coretex DRIVE Spanish version available also Summary user guide to refer to Data Diagnostic and Malfunction codes that can be encountered with Coretex ELD solution (content is also in this guide). For drivers to refer to summary dashboard features, Roadside Inspection procedures and Data Diagnostics/Malfunctions Installation Guide for installers pairing vehicle and TMU for use with Coretex 360/Coretex DRIVE. Revision history This following table provides the revision history of this guide: Guide Version Date Description v1.0 v1.2 v1.3 v1.4 v1.5 v1.6 v1.7 Dec 2017 Jan 2018 Mar 2018 Jul 2018 Oct 2018 Dec 2018 Apr 2019 First release. Latest release with new features. Latest release with new features. Revisions for violations for HOS and ELD for Canada. Minor enhancements and provisions for customer device integration/support Revisions for release of Coretex 360 v18.4 Revisions for release of Coretex 360 v19.1 Contact Coretex Local in-country support is available within Australia, New Zealand and North America. Please visit coretex.com for support and contact details. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 4 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Coretex ELD solution ELD mandate The USA ELD mandate was published by the FMCSA in 2015 with a goal to increase safety and accountability in the trucking industry. It is a set of detailed guidelines on operation of trucks for trucking companies and their fleets and drivers. It was legislated for all drivers in the USA to comply by Dec.2017 or face prosecution. The Canadian ELD mandate was published as a final draft by the CCMTA in 2017. It adopts many of the provisions of the USA regulations, but with some differences and it is expected a compliance date in the fourth quarter of 2019 will be instigated. Organizations can choose to see ELD as a tax and attempt to minimize the cost, or they can see it as an opportunity to drive competitive advantages. Coretex has built its ELD solution from the ground-up and created one of the few fully integrated solutions on the market today. For organizations that want a fully featured, fully integrated ELD solution Coretex is best in class! The Coretex ELD solution is tightly integrated with the Coretex 360 application suite. The easy-to-use interface has been developed in partnership with a number of large fleet operators in North America. The Coretex ELD solution supports: all North America driver rulesets, including interstate rules team, exempt and short haul drivers permanent and temporary vehicles installations ELD compliance for rental vehicles the Coretex ELD solution is in full compliance with USA ELD mandate defined by the Federal Motor Carrier Safety Administration (FMCSA) the Coretex ELD solution is in full compliance with Canada ELD mandate defined by the Canadian Council of Motor Transport Administrators (CCMTA) Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 5 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide ELD functionality --- For drivers The Coretex ELD solution allows drivers to: set their driver duty status during a trip and interact with co-drivers process Information Cards on their Coretex DRIVE dashboard for dealing with tasks like Vehicle Inspections (DVIR) and Shipment number entry display/edit their daily driver logs and the vehicles unidentified driving records certify their daily logs deal with Data Diagnostic/Malfunction events review and accept/reject edits proposed by their supervisor change ruleset when appropriate to comply with applicable jurisdiction allow a Roadside Inspection to be performed on their mobile device, and for uploads of driver log data to FMCSA For drivers, compliance couldnt be easier all they need to do is log in at the beginning of the day, even outside cellular coverage. They can also view their drive time availability in multiple rulesets prior to log in. For Supervisors/Administrators The Coretex ELD solution allows a supervisor/administrator to: review the daily logs of all drivers under their administration propose edits to drivers daily logs and unidentified driving records to be sent down to a drivers mobile device for them to consider configure drivers for ELD via Driver Manager upload drivers log data to FMCSA analyse drivers daily logs with a suite of Driver Hours reports Dispatchers or supervisors/administrators can readily track and manage compliance in Coretex 360 via a dashboard which offers easy access to driver availability data, and interactive graph and multi-edit features for easy log editing. Coretex ELD: its your path to increased efficiency, slashing paperwork for drivers by up to 63 percent and for office staff by 14 percent. Manual logging is so yesterday! Access to ELD functionality is determined by: account is configured for use of the Coretex ELD solution a hierarchy of carrier, divisions and terminals is configured at least one carrier and division must be setup and a driver/user assigned to that division the Android mobile device operating Coretex DRIVE must be configured for use of the same division in order to be able to select from vehicles in that division Full details of ELD administration for supervisors/administrators via Coretex 360 can be found in: Coretex 360: ELD Administration Guide Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 6 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Overview of Coretex DRIVE Coretex DRIVE is primarily a purpose-built, mobile device (tablet/mobile smartphone)based in-cab system that links drivers to vehicles, and vehicles to dispatchers. Working in harmony with Coretex 360, Coretex DRIVE gives drivers the information they need to do their jobs efficiently and safely. Built around a familiar modular app framework, Coretex DRIVE offers single pane of glass access to turn-by-turn trucking navigation, messaging, jobs, vehicle inspections (DVIR), checklists, fatigue information, the Coretex ELD solution, real time driver feedback as well as your choice of custom applications. Coretex DRIVE makes it easy to roll out Android-based mobile apps to drivers quickly and securely; and is optimized to run on Coretex-approved mobile devices. With Coretex DRIVE the user interface is the mobile device used by the driver of the vehicle and functionality is integrated into a backend Coretex system (e.g. Coretex 360). Coretex DRIVE features: integrates all your apps in one place on one screen in an easy-to-use format for drivers -- the driver sees important information on a single screen and is alerted with notifications called Information Cards links any third party applications, such as email or Google Maps features single sign-on for integrated applications displays driver messages, directed job workflows, driver initiated forms, Electronic Logging Devices (ELD functionality), Driver Vehicle Inspection Reports (DVIR) and much more device home button can take you back to the dashboard - this can be configured to happen just while working Example with driver friendly single dashboard view on an in-cab Android tablet (shown together with telematics unit): Not only a mobile app Coretex DRIVE (or DRIVE) is also: a cloud of online services, the so called microservices and comes with complete API access and a portal is available for administrators to configure functionality and view the data providing access to a Coretex installation application for installers to use to pair and configure a vehicle to its TMU Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 7 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Mobile device hardware Coretex DRIVE is installed onto an Android mobile device with the intended use being for drivers to manage their delivery schedules (from within their vehicles during their trips). This example is with an Android tablet, but mobile smartphones that meet the minimum requirements are also supported. Some common access keys: Home key takes you to the Coretex DRIVE dashboard wakes up the mobile device Back key takes you to the previous window removes keyboards from the screen closes dialog boxes Refer to the mobile device manufacturers documentation for detailed information about the device you are using It is recommended you keep your mobile device connected to the in-cab charger to ensure it does not run out of battery power during the trip. Mobile device minimum system requirements Tablet and mobile smartphone devices for running Coretex DRIVE need to comply with the minimum hardware and operating system specifications needed to support the operation of the system. From 2019 Coretex will support customers BYOD (bring your own device) which will greatly broaden the make/model base of devices employed with Coretex DRIVE. For compliance with using Coretex DRIVE, all devices should meet the following minimum requirements: Google Android operating system, version: level 22, version 5.0 Wi-Fi and 3G (or higher) (Android official version or a customised Android build that has available been assessed by Coretex) CPU: Quad-core 1.3 GHz or similar RAM: 1 GB Screen: 5" HDPI (720 x 1280) or 7" MDPI (600 x 1024) Coretex DRIVE v1.7+/Coretex 360 v19.1 Internal storage: 8 GB External Use (Confidential to Coretex Limited) 8 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Mobile device procedures Typical workflow will be: powering your mobile device on/off starting and Sign In to Coretex DRIVE setting your driver duty status setting your vehicle/trailers for the trip performing any DVIR tasks (if configured) entering any Shipment numbers Sign Out of Coretex DRIVE understanding safety lockdown and co-driver features Starting your trip with Sign In At the start of every trip you need to ensure the mobile device is up and running, Coretex DRIVE is started, and that you sign in to the application. Power On To turn the mobile device on: press and hold the Power button the mobile device will vibrate briefly when power up starts Dependent on your actual mobile device. Some models may behave slightly differently. Sign In normal Sign In procedure described here (variations include skipping selection of a vehicle, deferring DVIR inspections etc.) your administrator will allocate you a PIN to sign in with, and, if applicable, a Sign In password At the start of every trip, after powering the mobile device on you will need to: 1 Start up Coretex DRIVE Start the Coretex DRIVE app on your mobile device by clicking the Dashboard tile/icon (installed and available from your installed apps). 2 PIN entry The Coretex DRIVE Sign In PIN screen will be displayed enter your PIN number (4 to 8 digits) this will sign you in to Coretex DRIVE and the Coretex DVIR app For sites configured for keypad access this PIN corresponds to your Driver ID code on your driver entry in Coretex 360. 3 Password entry For sites configured for password access, the Sign In Password screen appears: enter your Sign In password If you have been allocated an initial password, you will be prompted to change it after first time use. If you have not been allocated a password, click Sign In to proceed (i.e. access without a password allowed) Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 9 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Your Sign In Password can be changed by: your administrator in Coretex 360 yourself via this screen, or via the DRIVER PORTAL in Coretex 360 3a If your password has been reset by someone other than yourself, you are allowed a one time use of it. Then you are prompted to enter a new password of your choosing. enter a new password confirm the password on the line below tap Reset You cannot manually change your password within Coretex DRIVE, other than this automatic facility. If you wish to explicitly change it please request your supervisor/administrator to do so via Coretex 360. 4 You new password will be synchronised with Coretex DRIVE and Coretex 360. This allows you to use it for: signing in to Coretex DRIVE on your mobile device/s signing in to the DRIVER PORTAL in Coretex 360 (first time use here is triggered also and will prompt you to change your password in Coretex 360) select a status from Preview Availability screen by tapping a status bar (e.g. On Duty) The purpose of this it to assess your current status with respect to available driving time to see if you have enough time left to embark on your trip! If not, perhaps your co-driver can do most of the driving today. For details refer to section Preview Availability section under Rules and Availability. 5 Selecting a Vehicle If no vehicle is already selected, you are prompted to specify one: tap the Set Vehicle tile to select your vehicle for the trip if you have no assigned vehicle as yet, tap SKIP on the toolbar (and you can select it later) some sites have a mobile device tied to a vehicle by policy, hence the vehicle will be pre-selected in this situation tap Continue Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 10 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide type in characters from the vehicle ID or Vehicle Name in the Search Vehicles filter textbox to present a filtered list of vehicles to choose from (to speed up finding the vehicle you want) tap a vehicle from the list to select it and it appears as a tile on the Select Vehicle screen Selecting Trailer/s 6 (optionally) add one or more trailers by tapping Add Trailer (another type of vehicle) search and select from a list of vehicles/trailers they appear as tiles on the Select Vehicle screen tap Continue or Save to use the selected vehicle/trailer combination Set by policy will be the maximum number of trailers you can attach (e.g. 3 in North America). Deselect a trailer simply by tapping on its tile. Selecting a trailer already assigned If the selected trailer is already assigned to another vehicle, you can return to select another trailer; or you can take over the assignment of your selected trailer. When an assigned trailer is selected, a prompt appears inviting you to change or confirm: tap Change Trailer to return tap Confirm Trailer to take over the trailer Taking over a trailer If you confirm then the prior assignment of this trailer needs to be disconnected by: having an automatic notification sent to the prior driver and alerting them that the trailer has been reassigned presenting a message informing them who has taken it and inviting them to select another trailer Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 11 of 88 Driver Guide 7 Coretex DRIVE: ELD Driver Guide Driver Vehicle Inspection Reports (DVIR) If you are configured for automatically instigating Pre-trip DVIR inspections this will activate at this point (for the currently selected vehicle and for each trailer attached). Summary of steps below, but for full details of using DVIR refer to separate Coretex DVIR: User Guide. You can defer performing the DVIR inspection/s by tapping LATER. The required inspections will appear as Information Cards. attend to any Coretex DVIR Information Cards on your dashboard tap on each inspection in turn to process Any previous inspections left in an unsatisfactory state must be dealt with before proceeding with todays inspection/s they are displayed when you tap on the first inspection card. Tap each inspection card in turn: perform your vehicle inspection by checking each inspection item and process the checks and defects with tapping on response options upon completion of all inspections, tap the COMPLETE INSPECTION menu bar link a certification screen appears inviting you to determine if the overall inspection is or 7 Shipments (or Manifest) Shipments are a specific consignment of goods associated with an asset (e.g. the contents of the trailer). Some sites are configured to call these Manifest throughout Coretex DRIVE. They are assigned a Shipment number and this number should be: entered as a Shipment number whenever the shipment is being carried by the asset removed as a Shipment number whenever the shipment is removed from the asset you may be configured (by account/carrier/division) to have a Shipment number automatically determined and assigned to your vehicle by default you may be configured to receive notifications to enter Shipment numbers, and these will appear as an Information Card on your dashboard Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 12 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide tap on any Shipments cards on your dashboard Optionally, one or more Shipment numbers may be entered: enter Shipment number tap Add tap Save to save changes and return to the dashboard you can defer entry of Shipment numbers until later in the day, but note that at least one Shipment number should be entered per trip in addition to access from tapping a Shipments Information Card you can explicitly access shipments from your ELD MENU Add Shipment number/s (or Manifest numbers) In addition to access from tapping a Shipments Information Card you can explicitly access shipments from the ELD MENU. To add shipment number/s: in normal operation, simply tab the Home key to return to the dashboard tap MENU to present the ELD MENU tap Shipments to present your Shipment numbers entry screen (as above) Remove Shipment number/s You should remove selected Shipment number/s when they are no longer valid as being associated with the vehicle, e.g. you change trailer, or sign out at the end of a trip. To remove shipment number/s: in normal operation, simply tab the Home key to return to the dashboard tap MENU to present the ELD MENU tap Shipments to present your Shipment numbers entry screen (as above) tap X to the right of the shipment number to be removed tap Save to save deletion changes When you Sign Out, all Shipment numbers are automatically removed. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 13 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Sign Out at the end of your trip At the end of every trip you need to ensure that you sign out of Coretex DRIVE, and (optionally) that you power down the mobile device. Sign Out There are two links to sign out of Coretex DRIVE from: the SIGN OUT USER option from the Dashboard menu here you can sign out any currently signed in users the SIGN OUT link at the bottom of the CHANGE STATUS menu here you can only sign yourself out! At the end of every trip, the current driver and signed-in co-drivers will need to sign out: 1 Dashboard menu in normal operation, simply tap the Home key to return to the dashboard tap the action link (top right of dashboard) called SIGN OUT USER - this presents a list of all currently signed in users tap Sign Out against the user you wish to have signed out (either yourself or one of the codrivers) ~ or ~ CHANGE STATUS menu tap SIGN OUT below the CHANGE STATUS menu to directly sign yourself out 2 if you have any uncertified logs (for days prior to today) you will be prompted to review and certify them 3 signing out will force a change of your duty status to a status of Off Duty confirm that that is your intention 4 Depending on your current status and if you are configured for Coretex DVIR Post-trip inspections, the first post-trip inspection will activate: perform each inspection in the same manner as for Pre-trip inspections detailed earlier this will be done for the vehicle (and all attached trailers) before deselecting the vehicle and any trailers Your status is changed to OFF DUTY 5 You are returned to the Coretex DRIVE Sign In screen. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 14 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Power Off To power down your mobile device: follow the Sign Out procedure to sign out of Coretex DRIVE press and hold the Power button tap Power Off from the Options dialog that appears tap OK from the confirmation dialog to confirm power off the mobile device will power off and shut down Safety Lockdown The Coretex DRIVE application on your mobile device is designed to operate when the vehicle is stationary. This is for safety concerns to help ensure the driver is just driving! A tablet is a mobile device and, as with a mobile phone, should not be used by the driver in charge of the vehicle while driving. If you have been using Coretex DRIVE and you start to drive the vehicle: an automatic sensor on the mobile device will detect this and present a lockdown screen when the vehicle stops, the application returns to the previous screen that was active A motion sensor is tied to the TMU in the vehicle (if connected to a TMU) and any vehicle motion will trigger it. If not connected to a TMU, motion is determined from the mobile device motion and GPS readings. Co-driver usage Any co-drivers that are signed in to Coretex DRIVE are allowed to use the application whilst the vehicle is in motion (because they are not in charge of driving the vehicle). When the driver is about to start driving they can hand the mobile device over to a co-driver and if the vehicle is moving the lockdown screen will be active. The codriver can tap on the padlock icon and enter their PIN ID to unlock the screen. A co-driver can use the application with the following restrictions: a driver duty status can not be changed, and the dashboard will display a VEHICLE IN MOTION status Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 15 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Looking at the dashboard In this section: examining the Coretex DRIVE dashboard available driver duty statuses changing your driver duty status changing the current driver in charge Information Cards card types Sample Coretex DRIVE dashboard screen (on an Android tablet): : Main features Dashboard option Description Dashboard tiles Vehicle Driver Burndown gauge ELD MENU Dashboard menu bar Dashboard menu Co-driver and app tiles to tap on appear on left hand side. Currently signed in vehicle. Current driver in charge of the vehicle. Burndown gauge of driving time left for the driver before a break is due. Access to current drivers logs, adding of remarks and shipping numbers. Tap menu bar links to change vehicle. Dropdown menu of system menu options (including Sign Out User). Co-driver/s Add to Dashboard apps Currently signed in co-drivers listed as tiles. Commonly used other apps can be added to dashboard and appear as tiles here on dashboard and spilling over to popup screen. Tap on this tile to manage other Coretex and Android apps on popup screen. Tap on this bar to change drivers duty status, and signing yourself out. View and set rulesets and availability. Access to Apps CHANGE STATUS menu Access to Rules & Availability Information Cards Card type Scrollable list on the right of incoming ELD alert notifications, called Information Cards. Every Information Card is defined under a Card type Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 16 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Driver duty status There are four standard driver or duty status options in Coretex DRIVE for drivers to select from. These are applicable for the current driver in charge and for any signed in co-drivers: ON On Duty SB Sleeper Berth OFF Off Duty D Driving What actually is available for driver duty statuses is dependent on the ruleset applicable. For example, some rulesets define a Break status. This is used to indicate a temporary break during the day rather than signing off as Off Duty at the end of the day. Other rulesets may allow drivers simply to select OffDuty for breaks and stops. Additional driver duty statuses There are two additional driver or duty status options. These become available only if: one driver is signed in to Coretex DRIVE you, as a driver, are configured by your supervisor/administrator to make use of them YM Yard Move PC Personal Conveyance When you change status to YM (Yard Move) or PC (Personal Conveyance) you are prompted to enter an annotation or comment about it. It is mandatory for PC and optional for YM. Refer to the section Remarks: Adding a remark or annotation for details. Changing your driver duty status What options that are presented on the CHANGE STATUS menu varies and is dependent on: what you are configured to have by your Coretex DRIVE administrator whether you are the driver in charge of the vehicle, or a co-driver what driver duty status you are currently at tap on your CHANGE STATUS bar on the dashboard to see the status selection screen: The options that appear depend on whether you are the first or subsequent drivers to sign on, but will include applicable duty status selection bars. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 17 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Forced duty status changes You change your duty status through the day as you drive, take a break and go off duty at the end of the day. In some situations, there are forced status changes that occur automatically, and will show in your driver logs with an Auto origin. For example: 1. You are driving the vehicle with duty status: Driving and you stop the vehicle for 5 minutes (as detected by vehicle motion from the TMU). A banner Information Card will appear to ask you if you wish to remain in Driving status. Tap the card to dismiss and continue in Driving status. If you do not respond for one minute, then you are automatically changed to a duty status of On-Duty. 2. You are in On-Duty or a non-working duty status and the vehicle starts in motion. Coretex DRIVE will detect this and change the duty status to Driving. Driver in charge Multiple drivers may be signed-in to Coretex DRIVE during a trip, but only one may be designated as the driver in charge at any one time. Only the driver in charge can change their driver duty status to Driving. When you sign in as the first driver, you are the designated driver in charge of the vehicle (by default) and you choose your initial driver duty status. The steering wheel icon indicates you are the designated driver in charge. Co-drivers may then sign in also and select their driver duty status in the same way. Taking over as driver in charge Co-drivers can change their driver duty status and have an additional option available to select from: In Charge of Vehicle Taking charge of the vehicle is a prerequisite if you are about to start driving (as the status Driving is only available if you are in charge). tap In Charge of Vehicle if you are taking over as the driver in charge Your driving duty status is automatically changed to On-Duty when you select In Charge of Vehicle. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 18 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Information Cards Information Cards are to be displayed on the right of your dashboard. This is a scrollable list of cards for drivers to tap in turn, and attend to. they will also pop up over any app that is on the screen tapping on an Information Card will take you to the appropriate app, or display more information, or remove the card Sorting and priorities When ELD Information Cards are displayed they are inserted according to the following sort criteria: 1 Priority of the ELD Information Cards (refer to section 2 below) high priority cards appear uppermost Date/time the card was issued most recently generated cards appear uppermost Information Card Types: ELD ELD card types appear with the following bar colors and priorities: Card Type Description Card Type Priority Malfunctions Searching for ELD Assign Vehicle ELD ELD ELD HIGH HIGH HIGH Card Type bar color RED RED RED ECM Not Connected ELD Exemption Confirm Driving ELD ELD ELD HIGH HIGH HIGH RED RED RED Data Diagnostics Unidentified Driver ELD ELD MEDIUM MEDIUM ORANGE ORANGE Certify Logs ELD LOW YELLOW Proposed Edits Shipping/Manifest Personal Conveyance ELD ELD ELD LOW LOW LOW GREEN GREEN GREEN Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 19 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Information Card Types: Other All ELD Information Card types have an ELD tag shown in the Information Card, but there are many other types of cards that can appear on your dashboard, for general operation, DVIR and other purposes. Some of the other card types that are important and relevant to operating Coretex DRIVE are: System errors (mostly relating to communication errors) Sign In cards For example: If you tap SKIP when selecting a vehicle, during the Sign In process, then you are immediately notified via a Vehicle/Trailer Sign In Information Card. Dashboard menu (off main dashboard) Coretex DRIVE provides a number of options from a Dashboard menu. This can be activated by tapping the vertical ellipsis icon in the top right of the main dashboard or Home screen. They are mainly options to examine diagnostics and useful in investigation of connection and other problems. details of use of the Dashboard menu is provided in Appendix:B Coretex DRIVE Dashboard menu a different menu is presented when accessed from the Driver Logs screen (details in above appendix) Changing your vehicle/trailer for the trip If you did not set your registered vehicle (and/or trailer/s) during Sign In, or if you wish to change your registered vehicle (and/or trailer/s) for the imminent trip then you can by: tapping the VEHICLE / TRAILER menu bar link at the top of the dashboard screen tap on the existing registered vehicle to deselect that and proceed to select another vehicle if you are configured for DVIR you may be prompted for Post-trip and Pre-trip inspections for each asset you deselect and select Refer to Sign In section for details of vehicle/trailer section. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 20 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Driver Logs In this section: Viewing your driver logs from the dashboard: o examining the logs in list and graph formats o driver log edits o adding a new status entry to your log o adding remarks and shipment numbers supervisor proposed edits sent to your logs dealing with unidentified driving records certifying your driver logs data diagnostic and malfunction events roadside inspection procedures co-driver functions Your driver logs are a list of events from your driving activity and are available from the Driver Logs screen. Driver Log View This displays log information for a single day from midnight to midnight (in 24-hour format) as: a graph of driver duty status through the day showing the total time the driver was in each status (e.g. On Duty, Sleeper Berth) view a list of all driver events for the day Access from ELD MENU At any time, you can access your driver logs from your ELD MENU. To access your Driver logs: in normal operation, simply tab the Home key to return to the dashboard tap MENU to present the ELD MENU tap View Logs to present your Driver Log View screen Your driver logs can also be accessed from the DRIVER PORTAL in Coretex 360. For details refer to Appendix:C ELD DRIVER PORTAL in Coretex 360. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 21 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Driver Logs screen From the Driver Log View screen, you can: view a days logs as a duty status graph and as a list view your driver logs for today and any of the previous seven days view resources used on this trip toggle SHOW ALL EVENTS button to show all events, or filter and only show status events (i.e. entries with an Event Type of On Duty or Off Duty) Driver Log Menu bar links: access your Unidentified Driving Records screen certify your logs access the Driver Log Edit screen access the Roadside Inspection screen For details of the menu bar links refer to Driver Logs menu bar links. Driver Log graph Each days log of entries is presented in a graph with: x-axis showing the 24 hours of the current day y-axis is split into four segments, one for each of the standard driver duty statuses The line in green shows the amount of time the current driver has spent time on that status. To the right of each segment is a total time (hh:mm) spent in that status. Sample Driver Log screen graph: Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 22 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Additional status displays if a driver has spent time in YM (Yard Move) status, this is displayed in yellow in the ON (On Duty) segment if a driver has spent time in PC (Personal Conveyance) status, this is displayed in yellow in the OFF (Off Duty) segment Driver Log list data The list of driver log records has a header clearly stating if the days logs have been certified or not yet. Entries in red/brown indicate mandatory data cannot be verified at time of loading (e.g. Location) The Driver Logs list presents the following fields of data: Field Description Time Location Vehicle Odometer Engine Hours Local time the event occurred Most recently recorded location when the event occurred Vehicle ID of vehicle that recorded the event Odometer reading at the time of the event (if available) Engine Hours reading at the time of the event (if available) Event/Status Event icon and the Drivers duty status Origin The origin of the event is shown with an icon: Driver Auto generated Auth.User (submitted by an administrator, supervisor or authorized user) Assumed (origin is unidentified) Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 23 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Remarks: Adding a remark or annotation You can add a remark or comment into your driver log whenever you feel like an explanation is needed during your working day. To add a remark: in normal operation, simply tab the Home key to return to the dashboard tap MENU to present the ELD MENU tap Remarks to present your Annotation Comment entry screen refer to example of use in the Sign In section for details add a remark (annotation/comment) of between 4-60 characters The entry will appear in your driver log list for current day. Sometimes an annotation is mandatory (e.g. changing status to Personal Conveyance), sometimes it is optional (e.g. changing status to Yard Move) Shipments: Adding shipment number/s Shipment numbers are usually entered during the Sign In procedures but you can enter them later on during the working day. You may be configured to have a shipment number automatically assigned, but if not and if you have your shipment number/s to hand, tap the Shipments Information Card to access the Shipment number entry screen. For details of shipments refer to example in the Sign In > Shipments section. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 24 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Driver Log Edits You can make changes to your driver log entries (e.g. where you wish to make a comment, or change your status for a period of time) via the Driver Log Edit screen. Drivers Logs menu bar links: UNIDENTIFIED access unidentified driving EDIT edit the driver logs. records for the current vehicle. CERTIFY certify any previous days logs for the ROADSIDE INSPECTION provide access to the current vehicle. driver logs for an FMCSA agent. EMAIL LOGS have your daily logs sent directly from your mobile device to your email InBox for further review. RESOURCE examine a trail of Vehicles, Trailers, Shipments and Co-Drivers that have used the mobile device on the currently selected day. From your Driver Logs screen: tap EDIT to present your Driver Log Edit Listing screen This is a list of the current days driver log entries with: an Edit button to the right to allow a Driver Log record to be edited an ADD STATUS link to allow a new status event entry to be generated by the driver Adding a new log entry for a change in driver status is the only ELD event you can create. Editing a log entry In normal circumstances driver log entry fields will only be editable for the Annotation field. All other fields will be pre-filled from information from the TMU To edit one of your log entries: tap the Edit button to the right of the log entry to present a Driver Log Edit screen To edit one of your log entries: tap EDIT to present your Driver Log Record Edit screen update the status, odometer or other relevant fields (if they are enabled) enter a note or annotation describing why it was edited tap OK to update the entry Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 25 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Adding a status log entry If your logs for a particular day are missing one or more entries (to cover a specific time period) then you can add these events from your Driver Logs Edit screen. You may need to do this for a different vehicle than for the one you are driving today. Adding a new log entry for a change in driver status is the only ELD event you can create. From your Driver Logs Edit Listing screen: tap ADD STATUS You need to specify the start of the period of time when the driving event occurred. You are prompted with a time selection control that defaults to show the current time. Any time in the day that is already lodged against driving time (i.e. time when driver in charge was in duty status Driving) will be disabled on the entry field. All fields that are greyed out are ones that can not be edited. Setting the start time of the event You need to specify the start time of the event when you changed your driver duty status. A clock control is used as a quick way to easily select the HH:MM of the start of the event. It defaults to todays current time and date. In most cases you will be wanting to add a log entry for a previous days trip hence, ensure you have set the correct date on the Driver Log View screen before drilling down to add a new status log entry. Setting the hour of the day drag the hours clock hand to select the hour of the start of the event, or tap on a minute setting tap OK or anywhere on control to proceed to minutes Coretex DRIVE v1.7+/Coretex 360 v19.1 Setting the minutes of the day drag the minutes clock hand to select the minutes of the start of the event tap OK to proceed to ADD STATUS screen External Use (Confidential to Coretex Limited) 26 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide You are presented with the ADD STATUS screen: tap Copy Previous or Copy Next to copy fields from the previous or next log entry, and edit as appropriate or enter the following fields manually (if they are enabled): select the driver duty Status from a dropdown of available standard driver duty statuses the Location of the vehicle at the time of the event any relevant Shipment numbers an Annotation or comment about the event the Vehicle ID of the vehicle whose event is being described the Odometer reading of the vehicle at the time of the event the Engine Hours reading of the vehicle at the time of the event a comment about one, two or three trailers that may have been attached to the vehicle at the time of the event tap OK to save the new status entry in your drivers log Often you will be entering log entries for a different vehicle than the one you are using today. Hence all relevant fields need to be entered. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 27 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Reassigning automatically assigned driving time A common situation is where a driver has one or more co-drivers and they are on a daily trip. After a break a co-driver swaps with the driver to drive the vehicle on the next leg. The driver should always register this in Coretex DRIVE to ensure the driving time is lodged against the right person (and before the vehicle sets off with a different driver in charge). However, if they simply drive off then the driving time is automatically lodged against the first driver (signed in as the driver in charge) and not the co-driver (who is now actually driving the vehicle). This needs to be rectified at the next stop, by reassigning that portion of driving time from, say, Driver:A to Driver:B. To reassign a portion of driving time from Driver:A to Driver:B: Driver:A takes the mobile device to access their Driver Logs, and finds the entry that has a portion of the daily trip that needs reassigning to Driver:B Such entries are always auto-generated and indicate a status change of On Duty Driving Driver:A taps EDIT on their action links toolbar: The Driver Log screen is refreshed into Edit mode, with the yellow pencil to the right of the log entries: Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 28 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Driver:A taps the yellow pencil on the log entry to edit the entry and the log edit screen appears with a Reassign button Reassign only appears for log entries for automatically assigned driving time and when one or more co-drivers are signed in. Driver:A must enter an annotation, a short note as the purpose of the reassignment (e.g. Wrong Driver!) Driver:A taps Reassign to present a popup menu of all co-drivers currently signed in to the mobile device Driver:A taps the appropriate co-driver option Driver:A explains the situation to Driver:B and passes the mobile device over to Driver:B, for them to enter their Sign In PIN In doing this Driver:B is authorising this reassignment of driving time from Driver:A to Driver:B. the log entry disappears from Driver:A logs and now appears as an entry in Driver:Bs logs. Ideally, this should be fixed up as soon as the error is detected but can be done at a subsequent session (e.g. the next day). However, it has to occur at a session where both Driver:A and Driver:B are signed into the same mobile device. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 29 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Violations and Warnings (for Hours of Service) The Coretex ELD Solution has been enhanced to incorporate violations and warnings. These present as Information Cards to drivers and supervisors to help improve safety and ensure compliance with driving time rules and limits. they are only issued to drivers with a status of Driving only Hours of Service (HOS) violations and warnings are provided in this release Scenario of operation A driver is operating a vehicle under a ruleset that determines that a driver can drive for no longer than 14 hours and the drivers ELD dashboard is displaying the burndown gauge of On Duty Remaining (Shift) time. Refer to following sections for details on violations and warnings. An example of how violations/warnings will operate: When the driver started his journey the burndown gauge started with 14 hours and as the day progresses burns down gradually towards zero hours when 13 hours have been exceeded this generates a Warning Information Card on their dashboard to alert them to the fact they are 1 hour away from a drive time violation when 13 hrs 30 mins have been exceeded this generates a Warning Information Card on their dashboard to alert them to the fact they are 30 mins away from a drive time violation, and this replaces the previous warning (if the driver hasnt already dismissed it) when 13 hrs 45 mins have been exceeded this generates a Warning Information Card on their dashboard to alert them to the fact they are 15 mins away from a drive time violation, and this replaces the previous warning (if the driver hasnt already dismissed it) when 13 hrs 55 mins have been exceeded this generates a Warning Information Card on their dashboard to alert them to the fact they are 5 mins away from a drive time violation, and this replaces the previous warning (if the driver hasnt already dismissed it) when 14 hrs have been exceeded, and the driver is still driving, this generates a Violation Information Card on their dashboard to alert them to the fact they are violating the driving time ruling, and this replaces the previous warning (if the driver hasnt already dismissed it) Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 30 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Warning Information Cards Prior to issuing violation cards you will be issued with warning cards alerting you to the fact that a particular timeframe is getting close to being exceeded. For each of the current US, Canada, AU and NZ rulesets, warning thresholds are configured and warning cards issued at defined times before a violation is due. Warning cards are of HOS (Hours of Service) type and can be tapped on to dismiss. Warning time thresholds may be configured, and include several timed warnings for each output. e.g. 1 hour, 30 min, 15 min, 5 min warnings. A warning card is issued and if an existing card for the same issue exists on your dashboard it is replaced by the new one. When the violation threshold is exceeded the warning card is replaced with a violation card. Violation Information Cards Drivers operate Coretex DRIVE and ELD under a particular ruleset. Rulesets are configured by Coretex to comply with legislation at a federal or national level, or intrastate (for USA). When you are operating a vehicle and a particular rule time threshold is exceeded then this generates a violation Information Card that appears on your dashboard. Violation cards are of HOS (Hours of Service) type and can be tapped on to dismiss. A violation card replaces any existing warning card for the same issue. Violations are generated and seen by you and your supervisor. They are not visible to Roadside Inspections. For example: if a ruleset states a driver cannot be on duty for more than 14 hours then any driving time exceeding this limit is flagged as a violation. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 31 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Drivers Logs Violation entries When you examine your own logs any violation entries are listed, with an alert icon. tap SHOW ALL EVENTS to see violation entries in the list. Any notes made against the violation by a supervisor will also appear here. If you believe a violation is in error, you must edit your logs, or contact your supervisor should it need to be deleted. Violation entries are shown in the logs but are not shown in Roadside Inspection mode. Supervisor Proposed Edits In addition to you being able to make edits to your own driver logs your administrator or supervisor can review the logs of drivers under their administration. If they think that one or more driving events should be assigned to you they can create proposals in the backend Coretex 360 system that will come down to your mobile device. You are alerted to a Supervisor Proposed Edits with an Information Card on your dashboard: tap on the card to proceed to present the Supervisor Proposed Edits listing screen Review the log entry proposals for a particular day and: tap ACCEPT to have all proposed entries assigned to you (as the driver in charge of the vehicle at the time) tap REJECT to have all entries for the day rejected for the supervisor to further assess No individual log entry selection is permissible. A driver must either ACCEPT or REJECT all log proposals for the current day. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 32 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Unidentified driving records The ELD automatically records all driving time in the vehicle, and regulations require that all ELD driving events must be assigned to a driver. Any periods of time that the vehicle is driven without a signed in driver, will generate an unidentified driving event. If a period of unidentified driving time is detected this presents as an Information Card (to alert you to review it). tap on the card to proceed to present the Unidentified Driving Records screen Only when all periods of unidentified driving time have been accepted or rejected will the card be cleared. Accessing unidentified driver records from your dashboard At any time, you can review the unidentified driver records (associated with your current vehicle) from your Driver Logs View screen: tap UNIDENTIFIED to present your Unidentified Driving Records screen: Reviewing your unidentified driving records These events can be viewed as records in a list on the Unidentified Driving Records screen. Here you can review your periods of unidentified driving time. Claiming time Some periods of time you can claim, if, for example you forgot to sign-in at the start of your daily trip: tick the time entries under the Select column (or tick next to column header to select all entries) tap Assign Selected To Me to have those entries assigned as driving time to you (as the driver in charge of the vehicle at the time) Rejecting time Some periods of time another driver (e.g. a co-driver) was driving at the time and so you can reject these entries: leave all such time entries unselected under the Select column tap Back to have those entries rejected Your supervisor will assess these records later on (from the DRIVER PORTAL in Coretex 360), and assign to the appropriate driver. You only need to accept Unidentified Driving Records that are applicable to you. When you sign out of Coretex DRIVE, any outstanding unidentified driving records will automatically be rejected and sent back for the supervisor/administrator to assess. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 33 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Resolving missing data Generally, the drivers log list is a trail of events that have occurred, although a driver can highlight an entry and tap the EDIT link to edit certain details. If an important field of data is missing from an entry this is displayed in a highlight color with a link Tap to resolve missing data: tap on the colored entry to present the Resolve Missing Data screen: with this example, the drivers location at the time of the event is missing so you can enter a description of the location at that time tap Save to return to your Drivers Log screen with the completed field displayed: Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 34 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Certify your logs During a daily trip your driver logs are recorded and these must be certified by yourself as a true record of the driving activity for that day. You are required to certify your logs on a day by day basis. When you sign in to Coretex DRIVE if there are any previous days logs that have not been certified you will be alerted to the fact with an Information Card on your dashboard. tap on the card to dismiss it and present your Drivers Log screen for review of your historical drivers logs (your logs are available for the current date and the previous seven days) Reviewing your logs From your Driver Logs screen: navigate to one or more of the previous days that requires certification for the days log entries There is a Not Certified bar showing at the top of the days log entries. tap CERTIFY to confirm the current days logs are a true record of driving activity tap AGREE to certify the days logs All driver logs for a particular day that have been certified are clearly marked on the Driver Log Edit/View screen: Your driver logs can also be certified from the DRIVER PORTAL in Coretex 360. For details refer to Appendix:C ELD DRIVER PORTAL in Coretex 360. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 35 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Re-certifying your logs If you have already certified your logs for a particular day and then you make a change you will need to re-certify. The Driver Logs Edit/View screen will detect this and change the CERTIFY menu bar link to appear as RE-CERTIFY. From your Driver Logs screen: navigate to one or more of the previous days that has already been certified for the days log entries make one or more changes to the entries, save and the menu bar link changes to RECERTIFY re-certify in the same way as certification Data diagnostics and malfunctions ELD functionality in Coretex DRIVE caters for a number of error conditions that are flagged as data diagnostic or malfunction events. You are alerted to them with cards that appear on your dashboard. For example: If your vehicle is driven without being signed-in (for more than 30 mins.of driving in a 24 hour period) then this is recorded as a period of unidentified driving. It is recorded as an unidentified driving record data diagnostic event. It shows up as a card or alert on your dashboard. For details refer to Appendix:A - Dealing with connection and Data Diagnostic/Malfunction events These events are also available in the separate: Quick Reference: ELD Data Diagnostics/Malfunctions In-cab Guide ELD Visor Card (for reference in-cab by drivers) Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 36 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Emailing your logs to yourself Drivers can access and print their own daily logs from the DRIVER PORTAL within Coretex 360. However, it is useful for drivers to be able to directly access a trail of their daily logs by having them sent directly from their mobile device to their email InBox for further review. To email your daily driver logs to yourself: from your Drivers Log screen tap the menu bar link EMAIL LOGS to present a date range popup (defaults to the currently selected date) tap the From or To date bar selection to present a calendar control to allow selection of any other date Once the date range is selected tap OK to generate the sending of the email event. A report of your daily logs is prepared in PDF format and emailed to your registered email address. This appears as an entry in your daily logs. Sample Email Logs event generated: The email address used to send the PDF of the logs is the address set up against your Driver entry in Coretex 360 Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 37 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Reviewing resources used The current driver in focus using the mobile device can examine their drivers log entries and then access an audit trail of the other resources that have been used. These are the vehicles, trailers, co-drivers and shipment numbers that have been used, showing when they were selected or specified and when they were removed. These are listed, grouped by resource type with respect to the current selected date on the Drivers Log screen and the current driver in focus (whose details are not listed). To access your Resource trail screen: from your Drivers Log screen tap the Resource button to present your Resource screen: This presents a summary page of the resources used for the trip grouped by Vehicles and trailers used, co-drivers that logged in and all Shipment numbers. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 38 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Burndown gauge on your dashboard While on duty, your dashboard displays a burndown gauge showing the rule that is most limiting to your duty status. In the example here the driver has exceeded their On Duty Remaining (Shift) time and so the burndown gauge highlights this showing zero time left! Beneath, is the link to your AVAILABILITY screen. Gauges showing core metrics of duty status (AVAILABILITY) Determination of the most limiting rule is calculated by examining the various rules that are active in the CURRENT RULESET. From the drivers dashboard a driver can tap on AVAILABILITY to access the Rules and Availability screen. This is used to select a CURRENT RULESET and in addition to view the various timeframes available from applying rules from the selected ruleset. In this example, the rule for On Duty Remaining (Shift) gauge has reached zero and this is the most limiting for the driver as it directly tells them they cant drive at present! Hence this is the one selected to show on the main dashboard. For details refer to section Rules and Availability. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 39 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Available Drive time The dashboard burndown gauge displays in green what their remaining available driving time is. In this example, a driver has been working (but not driving) and has set their duty status to On-Duty. The green portion of their dashboard burndown gauge winds down and indicates there is 59 mins left before a break must be taken. For a definition of what driver duty statuses are working duty statuses refer to the ELD Glossary. Gain time on the dashboard A contrasting blue Gain Time burndown gauge will be displayed whenever a driver is in a non-working status. Gain time is displayed and is the combination of time consumed when the driver is in a nonworking status. As soon as a driver sets their status to a non-working status the dashboard burndown gauge will switch to show in blue and display the Gain time winding down. For a definition of what driver duty statuses are non-working duty statuses refer to the ELD Glossary. A countdown will indicate how long they must remain in this status to gain additional driving time. For example: Driver changes to Break status and the blue gauge winds down from 30 to 0 minutes. Here 29 mins of their break are remaining. In the USA this will automatically cycle from a 30-minute break, a 10-hour restart, and a 34-hour cycle restart (depending on the next available gain time and the current rule set assigned). Details of drive time remaining on a burndown gauge can be seen (without changing status) by tapping on AVAILABILITY. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 40 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Roadside Inspections From time to time you may be approached by an FMCSA agent (safety officer) and asked to present your driver logs. You need to be prepared to assist to allow the safety officer to operate the mobile device to examine and/or transfer the logs directly (in bespoke FMCSA format) to FMCSA for further analysis. From time to time you may be approached by an CCMTA agent (safety officer) and asked to present your driver logs. You need to be prepared to assist to allow the safety officer to operate the mobile device to examine and/or transfer the logs in PDF format via email to an email recipient of the safety officers choosing. The Safety Officer is only required to see log data as displayed via the ROADSIDE INSPECTION screen and logs cannot be edited during this process. To access your Driver logs: in normal operation, simply tab the Home key to return to the dashboard. tap MENU to present the ELD MENU tap View Logs to present your Driver Log View screen Driver Logs screen A graph of your status through the current day is drawn on the default graph (by status/hour). Log data is presented in a scrollable list (below the graph), and is available for todays date and the seven days prior to today. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 41 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide To access your Roadside Inspection screen: tap ROADSIDE INSPECTIONS to present your Roadside Inspection screen hand the mobile device over to the safety officer for them to use the mobile device (to perform the inspection) The Safety Officer can examine all the required statistics from the Roadside Inspection screen. This displays data for the current driver and their available logs (covering todays date and the previous number of days available. What information they need to see is determined by the ELD mandate and this is different for USA and Canada. The Drivers Log list lists the same fields but the headers have different requirements: In the USA, FMCSA safety officers need to see this information on the Roadside Inspection header: In Canada, CCMTA safety officers need to see this information on the Roadside Inspection header: USA or Canadian ELD requirements will be met, dependent on the current ruleset selected. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 42 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Viewing different days Sample Roadside Inspection (USA) screen: the safety officer can navigate to the log date/s they want to inspect using the Previous Day or Next Day buttons How many days of data is available? FMCSA Safety Officers can review a drivers logs for today and the previous 6 days. CCMTA Safety Officers can review a drivers logs for today and the previous 13 days. Driver log records are shown as in the Driver Log View screen but with the addition of the Origin column. Origin of Drivers Log entry The Origin column shows how the log entry was submitted i.e. by the driver, autogenerated, by an authorized user or assumed. For details refer to section Driver Log list data. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 43 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Menu bar links A Safety Officer can access the Roadside Inspection screen and tap the following menu bar links: Roadside Inspection menu bar links: UNIDENTIFIED safety officer can access unidentified driving records for the current vehicle. DVIR safety officer can view DVIR (Driver Vehicle Inspection Report) inspections submitted by current vehicle in last 10 days. DATA TRANSFER safety officer can have all available driver logs (for today and previous seven days) sent to the FMCSA organization for analysis. END INSPECTION safety officer can complete inspection and hand mobile device back to driver Unidentified Driving Records From the Roadside Inspection screen the safety officer has the option to view any unidentified driving records. The option UNIDENTIFIED only appears if there are unidentified driving records detected for the current vehicle. tap UNIDENTIFIED to view the UNIDENTIFIED DRIVING RECORDS listing screen By default the safety officer is presented with a listing for the latest day, in the last week for which unidentified driving records were found for the vehicle. tap Previous Day to step back to an earlier date in the previous week (if records are available to view) Driver log records are specific to and listed by driver. Unidentified Driving records are linked to the vehicle. Hence here are listed all unidentified driving records by the driver and any co-drivers on the selected day. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 44 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide DATA TRANSFER initiated by Safety Officer During a Roadside Inspection a safety officer can request to have an output file of a drivers logs prepared and sent electronically to the regulatory agency or appropriate recipient. The safety officer has the option to have all available driver logs (for today and previous available days) submitted electronically for the purposes of further analysis. The methods of dispatch and recipient are different in the USA and Canada. Via the Roadside Inspection screen: In the USA the output file prepared will automatically gather the drivers logs data: for today and the previous 6 days send them in bespoke FMCSA format (either by Web Service or email) to the predetermined recipient at the FMCSA FMCSA Federal Motor Carrier Safety Administration are the lead federal government agency responsible for regulating and providing safety oversight of commercial motor vehicles (CMVs), FMCSA's mission is to reduce crashes, injuries, and fatalities involving large trucks and buses. For details refer to: https://www.fmcsa.dot.gov/ In Canada the output file prepared will automatically gather the drivers logs data: for today and the previous 13 days send them in PDF format to an email address specified by the CCMTA Safety Officer CCMTA Canadian Council of Motor Transport Administrators (CCMTA) coordinates all matters dealing with the administration, regulation and control of motor vehicle transportation and highway safety in Canada. Membership includes representation from provincial and territorial governments as well as the federal government of Canada. For details refer to: http://www.ccmta.ca/en/ Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 45 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide To access the Roadside Inspection screen (for the Safety Officer to view): tap ROADSIDE INSPECTIONS to present the Roadside Inspection screen hand the mobile device over to the safety officer to proceed they will tap DATA TRANSFER to present the EXPORT DATA FILE dialog: USA:To export and transfer the drivers log data, the safety officer: taps either Web Service or Email as the preferred delivery protocol enters a relevant comment for inclusion in the output file taps SEND to export and transfer the file The export and transfer is done and you are returned to the Roadside Inspection screen. Destination address is configured into the application so tapping SEND will send the export file (and comment) to the correct recipient at FMCSA. Canada: To export and transfer the drivers log data, the safety officer: enters the valid recipient email address (where the Safety Officer sends their submitted output files to) enters a relevant comment for inclusion in the output file taps SEND to submit the file by email Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 46 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide END INSPECTION the Safety Offier taps END INSPECTION to complete examination and return the mobile device to you, the driver DRIVER PIN re-entry For security purposes you are now required to re-entry your Sign In PIN in order to return to the access you had before. This returns you to the current drivers Driver Log View screen. DVIR inspection history From the Roadside Inspection screen the safety officer has the option to view any vehicle inspections or DVIR (Driver Vehicle Inspection Reports) submitted by the driver/s of the vehicle over the last ten days. tap DVIR to view the DVIR history trail for the current vehicle Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 47 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide This screen serves two purposes: a history of the submitted inspections of the current vehicle; essentially an audit trial of the vehicles pre-trip and/or post-trip DVIR inspections allows an ad hoc or explicit run of either a Pre-trip or Post-trip inspection, by your tapping on the + Perform Inspection link in the left panel any inspection entry can be tapped to present details of the inspection in the right pane scroll down in the right pane to view the defect details Coretex DRIVE may be configured to access this directly by tapping a tile Inspection History on your Installed Apps page a history trail of DVIR inspections provides access to inspections done in the last 10 days for details on performing a DVIR inspection refer to Coretex DRIVE: DVIR User Guide Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 48 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide RELOAD The display of DVIR information can be refreshed to ensure you are looking at the most up to date data: tap the menu bar link RELOAD to refresh the vehicle inspection or DVIR display Rules and Availability Rulesets will be applied to a driver for determining parameters for rules to comply with and for calculating break intervals, drive time and methods of data transfer. On the Coretex DRIVE dashboard: tap Availability to present the Rules and Availability screen From the Rules and Availability screen you can: easily view your CURRENT STATUS, TOTAL TIME IN STATUS select a different ruleset to activate as your CURRENT RULESET view the timeframe gauges of the rules in the current ruleset (that are then used to determine the gauge to display on your dashboard). For details refer to section Gauges showing core metrics of duty status perform rule based functions like adding an ADVERSE CONDITIONS comment to your log, or DEFER OFF DUTY time (Canada rulesets only) If you always drive under a single jurisdiction, e.g. always in the same state or country you may not need to change ruleset. Your administrator will instruct you if you need to change ruleset, e.g. if you drive in different intrastate you may need to change ruleset if you drive over the border between Canada and the USA (or vice versa) you will need to change ruleset Selecting a current ruleset select a ruleset to work from by tapping the dropdown under CURRENT RULESET The primary rule limits are displayed as Duty Limits underneath for your information. Various action links will appear on the toolbar. These provide access to functionality dependent on the particular ruleset selected. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 49 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Dealing with ruleset exceptions Having selected a ruleset to work with the driver must from time to time choose options, dependent on the currently active ruleset. The following describes functions that may be available, if the following action links appear in the toolbar (top right). ADVERSE CONDITIONS Drivers can add an annotation comment to their log to explain for delays and adverse conditions affecting their daily trip. tap ADVERSE CONDITIONS menu bar link enter a free format comment to document the adverse conditions you want to add to your log tap OK to save the comment The Adverse Condition event is added as an entry to your daily log: Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 50 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide DEFER OFF DUTY (Canada only) In Canada only, drivers can have the option to defer up to 2 hours of Off Duty time from today to tomorrow. When a Canadian ruleset is selected a new menu bar link option appears in the top right DEFER OFF DUTY tap this link to specify the period of time to defer from today to tomorrow Once specified, Hours of Service calculations are revised automatically An Information Card called Off-Duty Time Deferral will be displayed to the driver. It confirms off-duty time was deferred to tomorrow. A driver taps the card to dismiss and shown the Rules and Availability screen to review the available hours for tomorrow. Note that a subsequent attempt to defer Off-Duty hours on tomorrow will not be allowed. A message is displayed if the driver attempts to defer Off-Duty time when it is not permitted. In addition to DEFEER OFF DUTY other menu items may appear on the Rules and Availability toolbar dependent on the ruleset selected. When this occurs for a ruleset, selecting the new option will present a self explanatory dialog. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 51 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide 16-HOUR EXCEPTION If a driver meets certain criteria (e.g. driving more than 100 miles a day on a daily route and returning to base) then they are allowed to start up to two hours late for one day in every four. For USA federated rulesets the 16-HOUR EXCEPTION link will appear in the toolbar. The driver must take this option in order for their Duty limits to be re-calculated. a confirmation prompt appears and you should click APPLY if the big day exception ruling needs to be applied Preview Availability screen During a drivers Sign In procedure the driver is presented with the Preview Availability screen: The purpose of this it to assess your current status with respect to available driving time to see if you have enough time left to embark on your trip! If not, perhaps your codriver can do most of the driving today. to proceed with you as the driver for this upcoming trip tap on your current status (e.g. On Duty) There are two menu bar links available from this screen: HISTORY tap HISTORY as a short cut to access your Driver Log View screen DETAILS tap DETAILS as a short cut to your Rules and Availability screen Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 52 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Co-drivers Coretex DRIVE allows for one driver to be in charge of the vehicle and for any number of co-drivers to be signed in at the same time. A co-driver can: operate the mobile device whilst the driver in charge is driving the vehicle (and the driver in charge is locked out of using the mobile device) switch to take charge of the vehicle (and the previous driver in charge is set to be a co-driver) On the left hand side of the Coretex DRIVE dashboard are tiles to tap to: switch to make a signed-in co-driver be the driver in focus of the dashboard add a new co-driver to be signed in Driver in focus When a driver is in focus on the dashboard: the central section (with the burndown gauge) has their name shown prominently the ELD MENU and CHANGE STATUS options are relevant to the driver in focus the Information Cards on the right are relevant to the driver in focus This does not affect the status of the current driver in charge of the vehicle. Add a new co-driver To add a co-driver to todays session: tap the Add Driver tile to present the Sign In screen the co-driver signs in by entering their PIN number (if configured for password entry) the co-driver signs in by entering their password the co-driver selects their initial status and the dashboard presents with them as a co-driver tile on the left tap the new driver tile to make them the driver in focus Switch a co-driver to be the current driver in charge When the co-driver is ready to take over as the current driver on trip: tap on the co-drivers tile on the left panel (to take focus of the dashboard) tap CHANGE STATUS select In Charge of Vehicle from the CHANGE STATUS menu the co-driver becomes the current driver in charge (along with display of the steering wheel icon) and their details shown to the right Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 53 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Accessing Apps Coretex DRIVE is packaged with some separate applications and you can also configure shortcuts to launch independent apps installed on the mobile device. To access apps: tap the Apps icon to access the Loaded Apps shortcut screen: Sample Loaded Apps shortcut screen: Coretex DRIVE is installed with the following applications: Jobs Message Forms Change Vehicle Inspection History Access to manage your list of jobs in Coretex DRIVE Access to the Message Center Access to design interactive forms for use with Coretex DRIVE Access to change the vehicle or trailer for use in the next trip Access to your history of DVIR submitted inspections. Refer to section Roadside Inspections > DVIR inspection history for details. By default, no applications are loaded on the dashboard so you have to perform a one off exercise to install them on your personal dashboard. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 54 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Loading installed apps Your Coretex DRIVE dashboard can be configured to present app tile shortcuts to any other apps installed on the mobile device (to provide easy access from Coretex DRIVE). These apps can be customized apps designed for Coretex DRIVE (as above) or independent apps. For example: Camera Calculator To add a new shortcut to the Loaded Apps shortcut screen: tap any vacant app tile to present a scrollable list of installed mobile device apps: tap selected app to have a shortcut added to the Loaded Apps shortcut screen Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 55 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Dashboard Quick Apps Provision is made for two apps to be accommodated with shortcut tiles on the main dashboard. Simply tap either of the two quick app tiles on the left panel of the dashboard and then load up to two of your most useful apps to have them accessible directly with a single tap. These can be Coretex DRIVE supplied apps or independent apps (e.g. the camera built in to the mobile device). DVIR Inspection History One of the most useful of the Coretex DRIVE apps available is access to your DVIR Inspection History. You can inspect your submitted DVIR inspections by tapping on the Inspection History tile on the Loaded Apps shortcuts screen. This will present the view screen of DVIR (Driver Vehicle Inspection Report) inspections submitted over the last ten days. for details refer to section Roadside Inspections > DVIR inspection history for full details of using DVIR refer to separate Coretex DVIR: User Guide Removing tile associations To remove any tile association: remove any tile association by tapping on it for a second or more after the removal confirmation message appears tap the X to remove it Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 56 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Appendix:A - Dealing with connection and Data Diagnostic/Malfunction events In this section: Problems with internet connection Data Diagnostic codes Malfunction codes Problems with internet connection An internet connection is required for Coretex DRIVE to function correctly. No internet detected If this is not detected an Information Card will appear on your dashboard. This will be dismissed automatically when internet connection is restored. Airplane mode detected If the mobile device is placed into Airplane mode then this affects connectivity and a card to this effect appears on your dashboard. This will be dismissed automatically when internet connection is restored. An ELD connection between your Coretex DRIVE mobile device and the vehicles TMU must be able to monitor full compliance with requirements defined by the Federal Motor Carrier Safety Administration (FMCSA). It will ensure that all events relating to data inconsistencies and malfunctions are detected, recorded and submitted. ELD functionality in Coretex DRIVE caters for a number of error conditions that are flagged as data diagnostic or malfunction events. These are detailed here describing the codes, their descriptions, likely causes and response or resolution. Refer to Subpart B, Section 4.6 of the FMCSA regulations. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 57 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Data Diagnostic events These events are when your ELD detects a data inconsistency. You must follow the recommendation of the motor carrier and ELD provider (i.e. Coretex) to resolve the inconsistency. Refer to Section 49 CFR 395.34(c) of the FMCSA regulations. In this section: 1 - Power data diagnostic 2 - Engine synchronization data diagnostic 3 - Missing required data elements data diagnostic 4 - Data transfer data diagnostic 5 - Unidentified driving records data diagnostic Data Diagnostic codes Code Event Description 1 Description Causes Troubleshooting Corrective Action Power data diagnostic ELD is not fully functional within one minute of turning the engine on, or within one minute of selecting a vehicle in Coretex DRIVE. Code ELD was unable to connect to vehicle within 60 seconds The vehicle has ignition off and the TMU is in sleep mode Bluetooth is not enabled or Airplane mode is enabled verify correct vehicle is selected and ignition shows ON verify Bluetooth is enabled from the Coretex DRIVE dashboard, tap the Dashboard Menu > Diagnostics and verify the TMU is configured AND connected on the Diagnostic screen, verify ignition shows ON tap on the Information Card to dismiss verify your logs are complete and correct for the current and previous seven days if error persists contact Coretex Support Event Description 2 Description Causes Troubleshooting Corrective Action Engine synchronization data diagnostic An ELD is required to establish a link to the engine ECM, and must record an engine synchronization diagnostic event (when it loses that link for more than five seconds). TMU is not correctly configured to read ECM data there is an ECM malfunction from the Coretex DRIVE dashboard tap the Dashboard menu > Diagnostics and verify the TMU is configured AND connected on the Diagnostic screen, verify ignition shows ON and Odometer is displayed If the error persists, contact Coretex Support. There may be a Bluetooth issue, or a wiring/configuration issue related to the TMU/ECM connection. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 58 of 88 Driver Guide Code Coretex DRIVE: ELD Driver Guide Event Description 3 Description Causes Troubleshooting Missing required data elements data diagnostic An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type. It must record a missing required data element data diagnostic event for you (if any required fields are missing at the time of recording). GPS antenna failure ELD Sign In attempt while in a building and unable to get a GPS lock TMU recorded a status event while the vehicle was selected but is unable to read the Odometer or Engine Hours Go to ELD menu > View Logs and verify that recent events show a Location, an Engine Hours and an Odometer value. Corrective Action tap on the card to navigate to event with missing data (the event will be highlighted in a different color) tap on the event to add the missing information and resolve the event Code Event Description 4 Description Data transfer data diagnostic The ELD will automatically test the data transfer mechanism every seven days. A data transfer data diagnostic event is triggered when the automatic test fails. Corrective Action Code Event Description Causes Troubleshooting 5 Description Causes Troubleshooting Corrective Action poor or no cellular coverage when on a trip Airplane mode is enabled verify the cellular signal is available verify that Airplane mode is disabled enable Bluetooth disable Airplane mode restart the mobile device Sign out and Sign in if the error persists contact Coretex Support Unidentified driving records data diagnostic If more than 30 mins. of driving in a 24 hour period shows as unidentified driver on the ELD, it must detect and record an unidentified driving record data diagnostic event. The data diagnostic indicator must be turned on for all drivers logged into that ELD for the current 24 hour period and the following seven days. vehicle was used by driver without the driver signing into Coretex DRIVE Bluetooth connection failed Coretex DRIVE app failed Always sign in and select the vehicle in Coretex DRIVE before using the vehicle. tap on the Unidentified Driver card to review accept all records that belong to you The Information Card will clear when all records have been either accepted by yourself, or rejected (outstanding unidentified driving records will automatically be rejected after you Sign Out). Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 59 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Malfunction events Malfunction events are when the ELD detects technical compliance issues. You must: notify the motor carrier within 24 hours if the malfunction persists, reconstruct a paper record duty status for the current 24 hours and the last seven days keep paper logs until the ELD is serviced and brought back into compliance The motor carrier MUST repair, replace, or service the ELD unit within eight days. Refer to Section 49 CFR 395.34(c) of the FMCSA regulations. In this section: P Power compliance E Engine synchronization compliance T Timing compliance L Positioning compliance R Data recording compliance S Data transfer compliance Malfunction codes Code Event Description P Description Causes Troubleshooting Corrective Action Code Power compliance An ELD must monitor the data it receives from the engine ECM and set a power compliance malfunction event to identify instances when it may not have complied with the power requirements. Loose or faulty TMU connection to vehicle power TMU was disconnected for vehicle maintenance Before leaving the yard, ensure the TMU is connected by: from the Coretex DRIVE dashboard, tapping Dashboard menu > Diagnostics and verify the TMU is configured AND connected Contact Coretex Support. The TMU is likely to be offline or was unplugged for service. Event Description E Description Causes Troubleshooting Corrective Action Engine synchronization compliance An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 mins during a 24 hour period (aggregated across all driver profiles). TMU not correctly configured to read ECM data vehicle does not support CAN protocols from the Coretex DRIVE dashboard tap the Dashboard menu > Diagnostics and verify that the TMU is configured AND connected. on the Diagnostic screen, verify that Ignition shows ON and that Odometer is displayed verify Airplane mode is disabled verify Bluetooth is enabled restart the mobile device if the error persists, contact Coretex Support Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 60 of 88 Driver Guide Code Coretex DRIVE: ELD Driver Guide Event Description T Description Causes Troubleshooting Corrective Action Code Timing compliance The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 minutes of time deviation. mobile device is not set to automatic time synchronization GPS signal is unavailable always set the mobile device to use automatic time synchronization from the Coretex DRIVE dashboard tap the Dashboard menu > Diagnostics and verify that the TMU is configured AND connected on the Diagnostic screen, valid Latitude and Longitude co-ordinates are displayed for Position (indicating GPS signal) go to the mobile device Android Settings and ensure that date/time is set to automatic time synchronization if the error persists, contact Coretex Support Event Description L Description Causes Positioning compliance An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the vehicles movement (when such elapsed time exceeds a cumulative 60 mins over a 24 hour period, the ELD must set and record a Positioning compliance malfunction). Antenna failure. Corrective Action from the Coretex DRIVE dashboard tap on Dashboard menu > Diagnostics from the ELD dashboard and verify Position shows valid Latitude/Longitude co-ordinates Replace the antenna or contact Coretex Support. Code Event Description Troubleshooting R Description Causes Troubleshooting Corrective Action Data recording compliance An ELD must monitor its storage capacity and integrity, and must detect a data recording compliance malfunction, if it can no longer: record or retain required events retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier Memory or ELD performance issues Contact Coretex Support Contact Coretex Support Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 61 of 88 Driver Guide Code Coretex DRIVE: ELD Driver Guide Event Description S Description Causes Troubleshooting Corrective Action Data transfer compliance After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24 hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect and record a data transfer compliance malfunction. This fault auto-resolves when the device begins to communicate successfully. poor or no cellular coverage when on a trip Airplane mode is enabled Verify that: cellular signal is available Airplane mode is disabled disable Airplane mode. restart mobile device if the error persists, contact Coretex Support Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 62 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Appendix:B - Dashboard menu The Dashboard menu refers to a dropdown menu that is available by tapping the vertical ellipsis icon in the top right of the screen. The Dashboard menu is available from the: main Coretex DRIVE dashboard or Home screen Off the main dashboard screen Coretex DRIVE provides a number of options from a Dashboard menu. This can be activated by tapping the vertical ellipsis icon in the top right of the Home screen. They are mainly options to examine diagnostics and useful in investigation of connection and other problems. As a driver you may be asked by your supervisor to look and report on some of the information in these diagnostic screens. Options on this Dashboard menu are subject to change and also configurable on an account basis (policy setting) and so some options described may not be available for you. Help (configurable by policy) Not shown on the example menu above. Help is an option configurable by policy and can be customised to point to a URL of your choice, for customised online documentation and/or video training. At present, built in online help documentation is not provided by default. Add User Provides access to add a co-driver into the current session. An alternative access to tapping the Add Driver tile. Settings (System) System settings: GENERAL Default navigation system Non-ELD setting for specifying default application to use in Jobs module address identification function. Capture Home button Non-ELD setting to set when you tap the Home key where it directs flow. It can return you to the main mobile device desktop screen under conditions you specify here. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 63 of 88 Driver Guide System settings: NOTIFICATIONS Show popup card over other apps Play sound when connected or disconnected Notification access Show unidentified driving alert (ELD specific) Coretex DRIVE: ELD Driver Guide Set this slider control on to: allow Information Cards when issued, to popup in a window, above any other running apps Set this slider control on to: have a sound be emitted when connecting/ disconnecting to/from the TMU Accesses Android settings and the following notification access needs to be enabled in a one off procedure: enable Coretex DRIVE to access notifications from 3rd party applications Set this slider control on to: ensures that Information Cards are issued to the mobile device during periods of unidentified driving Diagnostics Tap on Dashboard menu > Diagnostics to present a view screen with: recorded useful telemetric connection data with regards to the vehicle and TMU (incl. GenX and V301) currently accessible status of the ECM, Ignition, Odometer and other useful settings tap SHOW LOGS menu bar link to present a window feeding the raw logs coming from the TMU Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 64 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Connection Latest useful diagnostics current connection status tells you: Vehicle ID Unique Vehicle ID Vehicle Display Registered name of the vehicle Telematics Configuration State If a Bluetooth 48-bit MAC address is detected as being configured and ready for use with the TMU, this entry highlights Configured in green. Conversely, it highlights Not Configured in red to alert you to connection problems to resolve. Telematics Connection Type Type of TMU connection detected (make/model of TMU). Overall connection status with regards to the Bluetooth Telematics Connection State communications from the TMU. When connected and transmitting readings it displays Connected in green. Conversely, it highlights Disconnected in red when a connection is not operating. Status Latest useful diagnostics status readings being received: ECM Status Latest status of the Engine Control Module unit in the vehicle, On/Off/Unknown. Position Latest Longitude/Latitude co-ordinates received from vehicle. Ignition Status Latest status of ignition received from vehicle, On/Off/Unknown. Odometer reading Latest odometer reading submitted. Odometer Derived If the vehicle supports derived odometer readings the latest received is displayed here. Engine Running Latest On/Off/Unknown status of the operation of the engine. Engine Running Time Latest Overall Engine Hours determined for the vehicle. Engine Speed Latest recorded speed (RPM) of the vehicle. Vehicle Speed Latest recorded speed (mi/hr or km/hr) of the vehicle. Motion Latest recorded motion status. Moving/Stationary/Unknown. About Coretex DRIVE Tap on Dashboard menu > About to present a view screen with: a page listing useful system information on the account used, version and build numbers of the Coretex DRIVE application, when it was installed and the storage capacity and serial number of the mobile device Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 65 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Appendix:C - ELD DRIVER PORTAL in Coretex 360 Driver access to ELD DRIVER PORTAL For customers configured for use of ELD (Electronic Logging Device) then drivers use Android mobile devices and the Coretex DRIVE application to manage their daily trips, with two-way integration with Coretex 360. Some drivers may also wish to sign in to Coretex 360 directly to work with their daily driver logs. Drivers signing in to Coretex 360 Drivers have the facility to sign in to Coretex 360 itself and access a DRIVER PORTAL. This provides restricted access to the system with the objective of: allowing a driver to view and report on only their own driver logs allowing a driver to certify their previous days logs allowing a driver to make driver edits in their own driver logs From the Sign-in screen for Coretex 360: sign-in with your Driver credentials to directly present the DRIVER PORTAL ELD DRIVER PORTAL For customers configured for use of ELD (Electronic Logging Device) then drivers use Android tablets and the Coretex DRIVE application to manage their daily trips, with two-way integration with Coretex 360. Some drivers may also wish to sign in to Coretex 360 directly to work with their daily driver logs. Drivers access Drivers have the facility to sign in to Coretex 360 itself and access a DRIVER PORTAL. This provides restricted access to the system with the objective of: allowing you to view and report on only your own driver logs allowing you to certify your previous days logs allowing you to make driver edits in your own driver logs From the Sign-in screen for Coretex 360: sign-in with your Driver credentials to directly present the DRIVER PORTAL You can only access your own driver logs. Supervisor/Administrator access Supervisors/Administrators can access daily logs for all drivers under their administration via a facility in Coretex 360. This is for the purposes of examining the logs and making Supervisor Proposed Edits. These get sent down to the driver for their consideration. A Supervisor/Administrator accesses ELD functionality only in Coretex 360. For details refer to: Coretex 360: ELD Administration Guide Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 66 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide DRIVER PORTAL Driver Hours After sign-in you are presented with the DRIVER PORTAL Driver Hours screen: These are your daily logs for your recent trips and by default are sorted with the most recent first. Here you can filter by date range and toggle the date sorting from descending to ascending date. Toolbar - Driver Logs The main screen can fill with hundreds of drivers log entries and so, as an administrator you will want to filter to narrow down to the entries you want to work with. Search for Word(s) You can search and filter on the list to narrow down the selection to find a specific drivers records. Search for specific log entries for drivers by: specifying characters from their Driver ID, Driver name/s and/or Vehicles in Search for Word(s) Filter by Log Event Filter drivers logs displayed in the list by: selecting event types (using the multi-select dropdown) for all events you want to filter for Filter by Date From/To Filter drivers logs displayed in the list by: selecting entries with event dates in your specified range Sample filter toolbar: Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 67 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Some log entries may require urgent attention (such as violations). Violations in Driver Logs For both drivers accessing their drivers logs in the DRIVER PORTAL and for supervisors reviewing drivers logs, violations come through and are indicated for a particular driver/date with a Violation (awaiting review) icon in a column called Violations: Violation icons in Driver Logs Icon Description Violation (awaiting review) is outstanding and requires attention by supervisor and driver. Violation (reviewed) has been reviewed by a supervisor. Sample Driver Log list screen (with unreviewed violation entries): Appearance of the violation icon (for a given driver/date) indicates that one or more of the daily entries beneath it, are unreviewed violation entries. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 68 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide DRIVER PORTAL Driver Log View/Edit To access the Driver Log View/Edit screen: double-click on one of your log entries (or single-click and click View/Edit Log button) Sample Driver Log View/Edit screen: The DRIVER PORTAL allows you to: examine your driver log entries for the current day, and clicking on the blue arrows to allow you to navigate to the previous seven days worth of entries (or select a date from the Date calendar control) use the Event Filter dropdown to apply filters on the display in the graph use the Show All Events checkbox to filter the events list and more easily find events you want to edit editing your existing driver log status entries and add new ones (if needed to add to a days records) certify a days logs as being true and correct for the currently selected day Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 69 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Violations in the Driver log View/Edit Violations in your drivers log require special attention from a supervisor and yourself! Double-click on the violation list entry to present the detail Driver Log View/Edit for the date: to present the Drivers Log View/Edit screen violation entries are listed with a red dot icon to the left Sample Driver Log View/Edit screen: Supervisor changes to violation entries Supervisors have access to make the following changes to a drivers violation daily log entry: review the entry by selecting it and adding an annotation or comment delete the entry if it is not relevant to the driver Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 70 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Reviewing the violation Supervisors can click on a drivers violation entry to present an edit panel to the right: enter a comment (4 characters or more) click Save to register it has been reviewed Supervisors will want to comment on drivers violations as evidence of managing their behaviour with comments such as: Short term one off. Spoke to driver about it 3rd warning given to driver Sample edit screen for a violation entry: Deleting the violation To delete the violation from the drivers log: click the Delete Violation checkbox click Save to remove it from the list Deleting a violation entry: Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 71 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Reviewed violations When all violation entries have been reviewed or deleted then upon return to the Driver Log list screen the Violation (awaiting review) icon is replaced with an Violation (reviewed) icon: Sample Driver Log list screen (with violations all reviewed or deleted): Reporting violations Violations are reported in the following two Coretex 360 reports and available from the Reports Manager: REPORTS > Driver Hours Reports > Driver ELD Log REPORTS > Driver Hours Reports > Violations For details refer to the Coretex 360 Reports: User Guide Driver log events listing All status events for you (as the driver) and currently selected day are sorted by time of day starting from midnight. Each entry has a status icon to the left: Active event entry generated by you the driver, or was auto-generated, or generated by a supervisor/administrator and accepted by you Your supervisor may assign periods of unidentified driving and other events to you (these are supervisor proposed edits). You need to consider them and determine if they are applicable to you or not. If not, you can reject them and the supervisor can look at them again, and perhaps, assign them to a different driver. You can accept or reject these proposed edits (depending on whether they are applicable to you or not) by: clicking to accept the proposed edit clicking to reject it Two meanings at present: a status event entry you have rejected it will be reviewed by your supervisor later (for possible reassignment) it is a violation event Filtering the events graph and list Separate filters are provided for filtering and simplifying the graph and events list. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 72 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Graph filter by event status All your driver log entries, for events in the currently selected day are listed in the table, and displayed on the graph. To simplify the graph display, these can be filtered by event status using the Event Filter dropdown. This does not filter the status events in the list. Status Active Inactive Proposed Rejected Description Your log entries that are active and were generated today or in the previous seven days Your log entries that are inactive and older than today and the previous seven days Your log entries that have been edited, either by you yourself, or by a supervisor Log entries that have been sent to you but you rejected them (for the supervisor to then decide on) Events list filter by event status Your events list can soon fill up with multiple screens worth of entries and so it can be useful to filter out all events that are not On Duty or Off Duty. tick Show All Events checkbox to show all events, or untick to filter and only list entries with an Event Type of On Duty or Off Duty Driver Edits When you sign in with a Coretex 360 Driver sign in, this presents just your driver event status entries. You are free to make changes to the entries in the list, if you wish to amend details (for example, a change of event status, adding a co-driver). You can also add a new status entry. Supervisor Proposed Edits When a supervisor/administrator edits a drivers log entries then this creates Supervisor Proposed Edits that are sent to the assigned drivers logs for their consideration. You (as the assigned driver) can review the proposed changes: on your tablet in Coretex DRIVE, or review and respond to them in the DRIVER PORTAL in Coretex 360 If you accept a proposed edit, then that status event entry is added to your daily log. If you reject a proposed edit, then they are returned for further review by the supervisor/administrator who, perhaps, may reassign them to another driver. Adding a new status event Add mode is the default mode of the screen and this ensures the Add New button is displayed under the graph. If this is not showing, then the screen is in Edit mode and you are in the middle of an edit of an existing event entry. To exit Edit mode and return to Add mode: click Save or Cancel (under the Annotation field) to finish working with the existing event entry being edited Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 73 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide To add a new event entry: click Add New to refresh the screen and enter required fields for new status event ensure you enter an annotation or comment (between 4-60 characters) to explain the need for the new entry You can use the graph to define the time period of the event. To specify the time period: drag the vertical start and end vertical bars to define the accurate period of time ~ or ~ enter the start and end times in the time period entry boxes below the graph select the driver status (from Status dropdown) to apply the correct status to the new event Editing a status event You can now edit Driver Log entries that are in in motion statuses (Driving, Yard Move, Personal Conveyance) and change their status, and the time span they cover. To make a Driver Edit: click on the event in the list to be edited and the fields to the right are populated with the current event entry make the required changes to the event fields optionally you can change the driver duty status for the period by clicking on one of the valid statuses listed in the Status dropdown ensure you enter an annotation or comment (between 4-60 characters) to explain the need for the Driver Edit Log entries with Event Type: Driving and Origin: Auto-(i.e. auto-driving events) cannot have their timespan shortened, and can have their status changed only to On Duty (Yard Moves) or Off Duty (Personal Conveyance) Support is provided for secondary statuses of: Yard Move Personal Conveyance Waiting, Off Duty (Break) these are custom statuses, required for some rulesets and enabled by the prevailing one active Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 74 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide The list of statuses available to the driver will only be ones applicable, that are: enabled under their current ruleset enabled for the driver (e.g. the driver is enabled for Yard Move, Personal Conveyance etc.) are allowed by business rule, when editing a particular event Auto-driving events with an Event Type: Driving present a status menu, such as the example shown here. Other driving events (e.g. On Duty, Off Duty) present a different range of statuses you can choose to change the entry to. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 75 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide To save changes: click Save to save and the edited entry will be sent down to your tablet You cannot accept unidentified driving events; this must be done from your tablet in Coretex DRIVE. However, if you have previously rejected such events on the tablet, a supervisor/administrator can assign them as proposed edits (and assigned to another driver). Certifying your driver logs You can review your driver logs, day by day for the current day and any previous day. Once you have checked that a days logs are true and correct you are required to certify them which signs them off as being completed. From the DRIVER PORTAL you can certify for any previous day, whereas on the tablet in Coretex DRIVE you are limited to the previous seven days. Most drivers will perform this on their tablets in Coretex DRIVE but you can do it from the DRIVER PORTAL by clicking on Agree: Once certified that days log will show with a green tick stating and stamped with the date it was done. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 76 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Printing your daily drivers log view You can output a report of the drivers log for the currently selected driver and day by clicking the Print button on the Driver Log View/Edit screen. Printing the Driver ELD Log Summary description: Driver ELD Log report outputs all ELD event log details to a report with a bar graph and a list of the events each page shows the logs for a particular driver and day. Business benefit allows a driver to print off their own logs for review allows a supervisor/administrator to print a report of the logs from drivers under their administration and to allow decisions to be made (e.g. proposed edits to assign driving time to another driver) lists a drivers violation entries (highlighted in sample report shown here) Usage for Drivers: from the DRIVER PORTAL > Print button for Supervisors/Administrators: click on Reports > Create > Driver Hours Reports > Driver ELD Log also available from DRIVERS > Driver Hours/ELD > (select driver) > Driver Log View/Edit (Print button) for a supervisor/administrator you can create a hard copy, export to Word and output to your printer, or print directly from the browser Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 77 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide To print a report of the currently selected days logs: Running the report presents a Driver ELD Log Report selection screen. This defaults to the: currently selected driver a time period of the 24 hours of yesterday ELD country of US (can change to Canada), determines the regulatory format of report header not to include reporting on days with no ELD events not to include inactive events (e.g. audit copies of originals of edited entries) not to include internal ELD events (e.g. violations) not to include Geofence names Hence, you may run the report with these defaults or change them as required. Selection criteria Make the following selections on the Driver ELD Log Report selection screen: Driver Group Driver A Start Date and End Date date/time to select from Include NO ELD Event Day can be run for a single or all available driver groups (default: All) restrict the dropdown list of drivers to select from by specifying a driver group and then choosing one or more drivers NOT AVAILABLE for Drivers printing from the DRIVER PORTAL select one, multiple or all drivers (default is All) restrict the dropdown list of drivers to select from by specifying a driver group and then choosing one or more drivers (using the multi-select feature) NOT AVAILABLE for Drivers printing from the DRIVER PORTAL defaults to a Start Date of yesterday defaults to a Start Date time of midnight defaults to an End Date of today defaults to an End Date time of midnight tick to include output for days with no ELD events Include Inactive Events tick to include inactive event entries Include Internal ELD tick to include internal ELD event entries Include Geofence Name tick to suppress the printing of Geofence names Report notes: only displays Driver Edits (not Supervisor Proposed Edits) this is the only report that drivers themselves can access when they sign in to Coretex 360 and access their daily logs in the DRIVER PORTAL Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 78 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Sample Driver ELD Log Report: This sample report highlights the appearance of violation entries that require urgent attention. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 79 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide ELD Glossary This glossary contains a list of many terms (including acronyms and abbreviations) that are used in dealing with the ELD functionality within Coretex DRIVE and Coretex 360. To be used in conjunction with the Coretex 360 Glossary. Coretex Platform Our flagship application is the single point of operational truth for fleet operators. Running on any modern web browser, it incorporates all of the tracking, maintenance scheduling, job management and driver management tools required to run an efficient fleet. From Coretex 360, operators can track location and speed, replay trips, define and manage geofences, control assets, interrogate triggered events, monitor driver behaviour, maintain service records, allocate jobs and much more. Coretex 360 can be accessed via Android and iOS apps, and supports a broad range of security and permission-management features that make it suitable for both small and enterprise organisations. This is a purpose-built, mobile device-based in-cab application that links drivers to vehicles and vehicles to dispatchers. Working in harmony with Coretex 360, Coretex DRIVE gives drivers the information they need to do their jobs efficiently and safely. It is built around a familiar modular app framework: Coretex DRIVE offers single pane of glass access to turn-by-turn trucking navigation, messaging, jobs, DVIR, checklists, fatigue information, ELD, real time driver feedback as well as your choice of custom applications Coretex DRIVE makes it easy to roll out Android-based mobile apps to drivers quickly and securely Coretex DRIVE is optimized to run on Coretex approved Android mobile devices Coretex ELD Solution The Coretex ELD Solution provided to customers entails: Coretex DRIVE application operating on Android mobile devices; this is configured to operate ELD functionality for the appropriate jurisdiction (e.g. USA, Canada) seamless communication via the internet with the vehicles TMU seamless connection to the Coretex 360 system supervisor access to ELD management and reports in Coretex 360 driver access to limited ELD functionality called the DRIVER PORTAL in Coretex 360 Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 80 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Generic terms CCMTA The Canadian Council of Motor Transport Administrators (CCMTA) coordinates all matters dealing with the administration, regulation and control of motor vehicle transportation and highway safety in Canada. Membership includes representation from provincial and territorial governments as well as the federal government of Canada. For details refer to: http://www.ccmta.ca/en/ CMV Commercial Motor Vehicle DVIR Driver Vehicle Inspection Reports application within Coretex DRIVE ELD In its simplest form, an Electronic Logging Device is used to electronically record a drivers Record of Duty Status (RODS), which replaces the paper logbook some drivers currently use to record their compliance with Hours of North America customers only Service (HOS) requirements (in North America). the ELD or the ELD unit For Coretex, both these terms refer to the combination of the 2 components, a telematics device and an Android mobile device that together make up the hardware components of the Coretex ELD solution. the ELD can also refer to the connection between the mobile device/TMU/Coretex DRIVE, internet access through to Coretex 360. FMCSA Federal Motor Carrier Safety Administration are the lead federal government agency responsible for regulating and providing safety oversight of commercial motor vehicles (CMVs), FMCSA's mission is to reduce crashes, injuries, and fatalities involving large trucks and buses. For details refer to: https://www.fmcsa.dot.gov/ FSMA FOOD SAFETY MODERNIZATION ACT (FSMA). Carriers of food may need to comply with regulations to become preferred FSMA carriers. This comprises contract documentation, monitoring and control of environmental conditions, plus ELD and the full suite of fleet management features. GPS Global Positioning System IoT Internet of Things. This term is used for IoT platforms and refer to the connection of hardware, (sensors/devices), internet transmission of data, software for analyzing the data and a user interface (e.g. web-based or device app with a dashboard and controls such as Coretex DRIVE). Mobile Tablets and mobile smartphones (that meet the minimum system requirements) device A hardware device with a touch screen (often GPS-enabled such as TomTom or Garmin, Android tablets or certain mobile phones). The driver uses the mobile device in-cab to operate the Coretex DRIVE application during their delivery trips. PIN Personal Identification Number (used for signing in to Coretex DRIVE) for sites configured for key pad PIN entry (to access Coretex DRIVE) this PIN corresponds to the Driver ID set up against the driver in Driver Manager. Password for sites configured for password entry, this is in addition to PIN entry and drivers will be required to enter their Sign In Password, after entering their PIN for sites configured for first time use of passwords, any password reset by anyone other than the driver themselves, will trigger a change of password process (either in the DRIVER PORTAL in Coretex 360 or on the mobile device when signing in to Coretex DRIVE) Tablet See Mobile device. TMU Telematics Unit Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 81 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide ELD related terms ADVERSE CONDITIONS Available Drive time 60Hrs/&days CMV Co-Driver DEFER OFF DUTY Driver certification event Driver log in event Driver log out event DRIVER PORTAL Drivers can add an annotation comment to their log to explain for delays and adverse conditions affecting their daily trip. A driver can only drive for a certain period of time in a day before they must stop or take a break. This is their available drive time and is displayed in green on their dashboard burndown gauge. This is used up when the driver is in a working duty status (and not only when driving). Also referred to as Drive time, Shift Time or Cycle Time. HOS rule set that specifies that a driver may be on duty for max of 60 hours in a 7 day cycle. Commercial Motor Vehicle (Truck). Driver who shares the responsibility for being in charge of a vehicle with another driver, only 1 driver can have a status of driving. Drivers in Canada can tap a menu bar link to present a dialogue to specify the period of time to defer from Day 1 to Day 2 (i.e. tomorrow, always the next day) Once specified calculations are revised and the driver is recommended to check their changed daily limits for drive and on duty time for the two days affected. Drivers are required to certify their record of duty. ELD event recorded to capture when a driver logs into the ELD. ELD event recorded to capture when a driver logs out of the ELD. Facility for allowing drivers to directly use Coretex 360 with a LOG IN in that allows them only to access the DRIVER PORTAL. This is the Driver Log View/Edit screen and is to allow them to access only their daily logs and report on them and perform some functions. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 82 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Driver record All events between engine power-up and engine power-down inclusive. More applicable for unidentified driving. Driving limit Maximum number of hours a driver may driver in a 24 hour period, typically 11 hours. Duty status event Identifies driver's duty status of either driving, on duty, sleeper berth, and off duty. May be manually selected by the driver or set automatically using vehicle interface. ELD An ELD is an electronic logging device that enables professional truck drivers and commercial motor carriers to collect and process a drivers Hours of Service (HOS) data compliance by connecting directly to the engines ECM. Employing an ELD and doing away with paper based logs provide extensive benefits and safety improvements. USA fleets are required to implement certified ELDs to record HOS by Dec.2017 ELD compliance USA fleets already equipped with electronic logging technology have until Dec.2019 to ensure compliance with the published specifications Canadian fleets are required to implement certified ELDs to record HOS by a date in the fourth quarter of 2019 (yet to be published) ELD event A discrete instance in time when ELD records data, where the events relates to driver activity, vehicle function, diagnostics, etc. ELD mandate The USA ELD mandate was published by the FMCSA in 2015 with a goal to increase safety and accountability in the trucking industry. It is a set of detailed guidelines on operation of trucks for trucking companies and their fleets and drivers. It was legislated for all drivers in the USA to comply by Dec.2017. The Canadian ELD mandate was published as a final draft by the CCMTA in 2017. It adopts many of the provisions of the USA regulations, but with some differences; and it is expected a compliance date in the fourth quarter of 2019 will be instigated. ECU generic term for Electronic Control Unit, a piece of hardware in a vehicle for ECU, ECM, EMS controlling actuators or the engine to ensure optimal performance ECM Engine Control Module (alternative acronym for ECU) EMS - Engine Management System unit - an ECU or EMS with access to the fuel lines is then referred to a EMS Engine power-down event ELD event required to be recorded when the engine is switched off. Engine power-up event ELD event required to be recorded when the engine is switched on. Hour limit Maximum number of hours a driver may be on duty in a 24 hour period, typically 14 hours. Gain time Whenever a driver sets their duty status to a non-working status their dashboard burndown gauge turns blue to display the amount of time they must wait in order to gain additional drive, shift or cycle time. HoS (Hours of Service) Rules that specify daily and cycle limits on duty and driving time. Intermediate event ELD event required when a vehicle is in motion and a duty status event there hasnt been a duty status event recorded in an hour. USA: a Safety Officer may request logs be submitted from a driver with data Logs Period Available for today and the previous 6 days they may also view this range of days on the Roadside Inspection screen Canada: a Safety Officer may request logs be submitted from a driver with data for today and the previous 13 days they may also view this range of days on the Roadside Inspection screen Motor Carrier A company that employs large trucks, buses, etc. Motor Carrier Number Number assigned to a motor carrier when they are granted an operating authority. Operating Authority Assigned by USDOT, required when a company operates inter-state. Dictates the type of business operations a motor carrier may run or cargo it may carry. Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 83 of 88 Driver Guide Output file Passenger carrying Personal conveyance Property carrying Roadside Inspection Status (Working) [Driver duty status] Status (Non-Working) [Driver duty status] Team Drivers Telematics device Unidentified driving USDOT Vehicle in motion Vehicle interface Vehicle motion status Vehicle stationary Yard moves Coretex DRIVE: ELD Driver Guide A drivers logs may be exported for further analysis by a safety officer during a Roadside Inspection. USA: a Safety Officer may request from a driver a record of their driving logs. These can be generated and submitted to FMCSA with logs prepared for a period described under Logs Period Available Canada: a Safety Officer may request from a driver a record of their driving logs. These can be generated and submitted as a PDF to an email address supplied by the officer. The logs are prepared for a period described under Logs Period Available Indicates that the HOS rule set for drivers who driver buses, etc. Instances where a driver is using a company vehicle for private use. Indicates that the HOS rule set for drivers who driver CMV's for transporting freight. From time to time a driver may be approached by a FMCSA/CCMTA agent (safety officer) and asked to present their driver logs. A driver is prepared to assist to allow the safety officer to operate the mobile device to examine and/or transfer the logs electronically for further analysis. When a driver is working he is set to one of the following driver duty statuses: Driving On-Duty Yard Move Dashboard burndown gauge will display in green an indication of the factor most critical to their available driving time. When a driver is not working he is set to one of the following driver duty statuses: Break Off-Duty Sleeper Berth Personal Conveyance Dashboard burndown gauge will display in blue an indication of the Gain time remaining before they are entitled to additional cycle drive time. Instances where there is more than one driver. Device or TMU installed in a vehicle which is typically connected to the engine management system & usually has GPS functionality (TMU1500, V301, GenX). Instances where a CMV is being driven and a driver hasn't logged into the ELD. United States Department of Transportation. Vehicle is considered in motion when the speed is greater than or equal to 5mph. Integration to the Engine Management System to receive vehicle data, such as engine hours, elapsed distance, speed, etc. Indication of whether a vehicle is in motion or stationary based on the FMCSA specification. Vehicle is considered stationary when the speed is 0 for at least 3 seconds. Instances where a driver is moving vehicle around in a depot (and not on the open road). Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 84 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Copyright Notice Copyright 2019 Coretex Limited (All Rights Reserved) The software contains proprietary information of Coretex Limited; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. Every effort has been made to ensure the accuracy of the material in this guide at time of publication, however not all features are supported by all systems and feature enhancements will occur from time to time changing some of the features that are mentioned in this guide. You may need to refer to your separately supplied User Guides for further information on the use of the product. The information and intellectual property contained herein is confidential between Coretex Limited and the client and remains the exclusive property of Coretex Limited. If you find any problems in the documentation, please report them to us in writing. Coretex Limited does not warrant that this document is error-free. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise without the prior written permission of Coretex Limited. Reproduction and use of and title to this documentation are subject to the Terms and Conditions of the relevant End User License Agreement. Microsoft Office, Windows, Azure, Word and Excel are trademarks of the Microsoft Corporation Google Maps is a web mapping facility licensed from Google LLC for use in Coretex products Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 85 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Index A About this guide 4 Accessing Apps Dashboard Quick Apps 56 DVIR Inspection History 56 Loading installed apps 55 Removing tile associations 56 Adding a status log entry Setting the start time of the event 26 Additional driver duty statuses 17 B Burndown gauge on your dashboard Available Drive time 40 Gauges showing core metrics of duty status (AVAILABILITY) 39 C Certify your logs Re-certifying your logs 36 Reviewing your logs 35 Changing your driver duty status Forced duty status changes 18 Co-drivers 53 Add a new co-driver 53 Co-driver usage 15 Driver in focus 53 Switch a co-driver to be the current driver in charge 53 Contact Coretex 4 Copyright Notice 85 Coretex ELD solution 5 ELD functionality 6 D Dashboard menu 63 Off the main dashboard screen 63 Data Diagnostic codes 1 Power data diagnostic 58 2 Engine synchronization data diagnostic 58 3 Missing required data elements data diagnostic 59 4 Data transfer data diagnostic 59 5 Unidentified driving records data diagnostic 59 Data Diagnostic events 58 Data diagnostic codes 58 Dealing with connection and Data Diagnostic/Malfunction events 57 Diagnostics Connection 65 Status 65 Driver access to ELD DRIVER PORTAL 66 Drivers signing in to Coretex 360 66 Driver in charge Taking over as driver in charge 18 Driver Log Edits Coretex DRIVE v1.7+/Coretex 360 v19.1 Adding a status log entry 26 Editing a log entry 25 Reassigning automatically assigned driving time 28 Driver Log graph Additional status displays 23 Driver Log View Adding a remark or annotation 17, 24 Adding shipment number/s 24 Driver Log Edits 25 Driver Log graph 22 Driver Log list data 23 Driver Logs screen 22 Driver Logs 21 Access from ELD MENU 21 Accessing unidentified driver records from your dashboard 33 Burndown gauge on your dashboard 39 Certify your logs 35 Claiming time 33 Data diagnostics and malfunctions 36 Driver Log View 21 Emailing your logs to yourself 37 Gain time on the dashboard 40 Rejecting time 33 Resolving missing data 34 Reviewing resources used 38 Reviewing your unidentified driving records 33 Roadside Inspections 41 Supervisor Proposed Edits 32 Unidentified driving records 33 Violations and Warnings (for Hours of Service) 30 DVIR Driver Vehicle Inspection Reports (DVIR) 12 DVIR Inspection History 56 Post-trip inspections 14 RELOAD of DVIR data 49 Roadside inspection of DVIR 47 DVIR inspection history RELOAD 49 E ELD DRIVER PORTAL 66 External Use (Confidential to Coretex Limited) 86 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Adding a new status event 73 Certifying your driver logs 76 Deleting the violation 71 Driver Edits 73 Driver log events listing 72 DRIVER PORTAL Driver Hours 67 DRIVER PORTAL Driver Log View/Edit 69 Drivers access 66 Editing a status event 74 Filtering the events graph and list 72 Printing from your daily drivers log view 77 Reporting violations 72 Reviewed violations 72 Reviewing the violation 71 Supervisor changes to violation entries 70 Supervisor Proposed Edits 73 Supervisor/Administrator access 66 Toolbar - Driver Logs 67 Violation icons in Driver Logs 68 Violations in Driver Logs 68 Violations in the Driver log View/Edit 70 ELD functionality for Drivers 6 for Supervisors/Administrators 6 ELD Glossary 80 ELD mandate 5 F Filtering the events graph and list Events list filter by event status 73 Graph filter by event status 73 G Glossary of terms 80 I Information Cards Information Card Types ELD 19 Other 20 Sorting and priorities 19 Intended audience 4 O L Looking at the dashboard 16 Accessing Apps 54 Additional Driver duty status 17 Changing your driver duty status 17 Changing your vehicle/trailer for the trip 20 Dashboard menu (off main dashboard) 20 Driver duty status 17 Driver in charge 18 Information Cards 19 Main features 16 M Malfunction codes Coretex DRIVE v1.7+/Coretex 360 v19.1 E Engine synchronization compliance 60 L Positioning compliance 61 P Power compliance 60 R Data recording compliance 61 S Data transfer compliance 62 T Timing compliance 61 Malfunction events 60 Malfunction codes 60 Menu bar links for Dashboard 14, 20 for Diagnostics 64 for Driver Logs 22, 25, 36 for DVIR 12 for Preview Availability 52 for Roadside Inspections 44 for Rules and Availability 50, 51, 52 Mobile device hardware 8 Mobile device minimum system requirements 8 Mobile device procedures 9 Password entry 9 PIN entry 9 Power Off 15 Power On 9 Safety Lockdown 15 Selecting a trailer already assigned 11 Selecting a Vehicle 10 Selecting Trailer/s 11 Sign In 9 Sign Out 14 Sign Out at the end of your trip 14 Start up Coretex DRIVE 9 Starting your trip with Sign In 9 Taking over a trailer 11 Mobile phone hardware 8 Motion sensor to detect moving vehicle 15 Off the main dashboard screen About Coretex DRIVE 65 Add User 63 Diagnostics 64 Help (configurable by policy) 63 Settings (System) 63 Overview of Coretex DRIVE 7 Not only a mobile app 7 P Preview Availability screen 10 DETAILS 52 HISTORY 52 Problems with internet connection 57 Airplane mode detected 57 No internet detected 57 R Reassigning automatically assigned driving time 28 Related documentation 4 Reports Manager (Categories) Printing the Driver ELD Log 77 Resources 38 External Use (Confidential to Coretex Limited) 87 of 88 Driver Guide Coretex DRIVE: ELD Driver Guide Revision history 4 Roadside Inspections DATA TRANSFER initiated by Safety Officer 45 DRIVER PIN re-entry 47 DVIR inspection history 47 END INSPECTION 47 How many days of data is available? 43 Menu bar links 44 Origin of Drivers Log entry 43 Unidentified Driving Records 44 Viewing different days 43 Rules and Availability 49 16-HOUR EXCEPTION 52 ADVERSE CONDITIONS 50 Dealing with ruleset exceptions 50 DEFER OFF DUTY (Canada only) 51 Preview Availability screen 52 Selecting a current ruleset 49 Viewing rule gauges for current ruleset 39 S Safety Lockdown Co-driver usage 15 Shipments Add Shipment number/s 13 Adding a Shipment at Sign In 12 Adding a Shipment number later 24 Remove a Shipment number 13 Remove Shipment number/s 13 Sign In Driver Vehicle Inspection Reports (DVIR) 12 Shipments (or Manifest) 12 T Tablet hardware 8 V Violations and Warnings (for Hours of Service) Drivers Logs Violation entries 32 Scenario of operation 30 Violation information cards 31 Warning information cards 31 Coretex DRIVE v1.7+/Coretex 360 v19.1 External Use (Confidential to Coretex Limited) 88 of 88