Omnitracs Hours of Services 4.5 External Release Notes

Transcription

1 Omnitracs Hours of Services 4.5 External Release Notes Table of Contents Overview... 1 ELD Features Available if Running the IVG ELD Firmware... 2 Features and Enhancements... 2 Time Resolution Format... 2 Carrier-Initiated Driver Log Edits... 3 Driver-Initiated Driver Log Edits (ELD Only)... 3 Unassigned Vehicle Movement (ELD Only)... 4 Vehicle Identifier (VIN) Capture... 4 Engine Hours Capture... 4 Web Services... 4 Changes and Additions to Web Services Exposed in the Prior Releases... 6 IVG User Interface Changes (ELD Only)... 6 Initial Login... 6 Logging Out... 7 Overview This release covers changes related to FMCSA ELD compliance. For more information on the FMCSA ELD mandate and Omnitracs plans for compliance, please see our ELD Facts website: The ELD changes defined here are available to customers participating in ELD beta on IVG. If you would like to participate in the ELD beta on IVG, please us at: eldbeta@omnitracs.com. 1

2 ELD Features Available if Running the IVG ELD Firmware Feature/Function AOBRD Running ELD (IVG) Unassigned Driving reconciled Host Only Mobile; if rejected then host Mobile Edits can be disabled Yes No Driver can approve/decline edits from carrier Auto on-duty/off-duty at login/logout No Yes Yes No Events timed to seconds No Yes Capture VIN from ECM No Yes Capture Engine Hours from ECM No Yes Complete edit audit history visible on host No (original and last only) Yes Features and Enhancements Time Resolution Format Times now display with a resolution to seconds. For vehicles with ELD software, the time is accurate to the second and displays the true values. For vehicle with AOBRD software, the time is accurate to the minute and displays 00 for the seconds. With ELD software, violations are reported when the driver is in violation for one second. For AOBRD software, violations are still reported when the driver is in violation for one minute. For information on how web services were affected, see Web Services. The example below shows the new time resolution format for duty statuses reported from ELD software. FIGURE 1 DRIVER DETAILS SHOWING NEW TIME FORMAT 2

3 Carrier-Initiated Driver Log Edits Edits made to drivers logs by the carrier through the Hours of Service application function differently and display differently within the Hours of Service application, depending on if the in-cab software is ELD compliant or an AOBRD. The look and function of carrier-initiated edits to logs for a driver using AOBRD software are unchanged. Edits to logs for a using ELD software are not automatically accepted, but remain in a Pending state until reviewed and accepted by the driver through the in-cab software. The edited record for the driver with ELD software displays as italic and is flagged as Pending within the Hours of Service host application until the driver accepts or rejects the proposed changes. Pending duty status changes cannot be edited. FIGURE 2 PENDING ELD CARRIER EDITS In summary: If the software in the cab is an AOBRD, carrier-initiated log updates are still automatically accepted and are never shown as Pending within the Hours of Service host application. If the software is ELD-compliant, the driver is prompted upon login to the in-cab software to accept reject those changes. Until they re acknowledged by the driver, the edited log record shows as Pending within the Hours of Service host application. The original, unedited logs display on reports until the driver accepts the proposed carrierinitiated edits. Driver-Initiated Driver Log Edits (ELD Only) To meet the requirements of the ELD mandate, all drivers may now edit their logs from the in- cab software and driver- initiated edits can no longer be disabled from the Hours of Service host application. 3

4 Unassigned Vehicle Movement (ELD Only) What was previously referred to as Unknown driving, e.g. when a driver s credentials are rejected upon login or a driver logs out before being authenticated, is no longer reported as such by the mobile. Drive time recorded by a mobile without an authenticated driver is reported as Unidentified Driving. This means that no Driving duty status records display for an ELD vehicle in the Vehicle Details page of the Hours of Service application when the Unknown filter is selected. When unidentified driving is recorded on an ELD, the next driver that logs in to that mobile is required to accept or reject the unassigned driving records that have been saved by the mobile. A host user will not be able to assign these Unidentified Driving records unless a driver has rejected them or an 8-day period has passed with no action taken on the mobile. Vehicle Identifier (VIN) Capture To meet the requirements of the ELD mandate, the VIN is captured from the JBus and displayed on the mobile interface and in reports. Engine Hours Capture To meet the requirements of the ELD mandate, engine hours are captured and displayed on the mobile interface and in reports. The engine hours are displayed for duty statuses, and elapsed (accumulated) engine hours are displayed for non-duty statuses. Web Services For more information on web services in this and prior releases, go here: The following web services include the new parameter TimeResolutionInSeconds that specifies whether certain values in the response are returned in seconds or minutes (false: minutes; true: seconds). CanadaDriverLogReport CanadaDriverLogReport2 DriverLogQueue DriverLogQueueByGroup DriverLogQueueEx DriverLogQueueByGroupEx DriverViolations DriverViolationsByGroup ExportDriver 4

5 ExportDriverByDepotId ExportDriverClock ExportDriverClockByDepotId ExportDriverLog GetLogExceptions GetLogExceptionsByDepot LogEvents USDriverLogReport USDriverLogReport2 The following chart shows what web services have modified time-related parameters. Web Service Parameter Meaning GetDataRanges FirstStatusChange Earliest status change for the driver in GMT GetDataRanges LastStatusChange Latest status change for the driver in GMT (truncated to the minute) GetRestBreakExemptionUsage RbeUsageStartTime Time when rest break exemption started GetRestBreakExemptionUsage RbeUsageEndTime Time when rest break exemption ended GetRestBreakExemptionUsageByDepot RbeUsageStartTime Time when rest break exemption started GetRestBreakExemptionUsageByDepot RbeUsageEndTime Time when rest break exemption ended GetViolationEvents EventTime Time that driver crossed the threshold causing the event (truncated to the minute) GetViolationEvents CaculationTime Time calculated that the driver crossed the threshold 5

6 Changes and Additions to Web Services Exposed in the Prior Releases The web services AddVehicle, UpdateVehicle, and Get were updated in a prior release to include the parameter PlateNumber: the license plate number for the vehicle. This parameter is now required under ELD. The web services AddEx, AddWithCarrierName, UpdateDriverEx, and UpdateEx have the following new fields. Parameter CDL CDLState ELDExempt ELDExemptReason Meaning Commercial driver's license Issuing state or province Flag indicating driver is exempt from ELD requirements Reason for exemption Parameter CDL CDLState ELDExempt ELDExemptReason Meaning Commercial driver's license Issuing state or province Flag indicating driver is exempt from ELD requirements Reason for exemption Other web service changes are as follows. Web Service Parameter Meaning Get ELDExempt Flag indicating driver is exempt from ELD requirements ELDExemptReason Reason for exemption Get USDotNumber US DOT Number of the carrier Add USDotNumber US DOT Number of the carrier Update USDotNumber US DOT Number of the carrier IVG User Interface Changes (ELD Only) Drivers with companies participating in the IVG firmware beta will see the following login/log out screens. Drivers are now required to identify a duty status upon login and log out. Initial Login When logging in to the IVG, drivers are no longer On Duty by default. They are prompted to identify their duty status immediately after they enter their ID and password. 6

7 Logging Out There s a logout prompt that parallels the login prompt for drivers forcing them to identify their duty status when they log out. 7

8 Omnitracs, LLC 717 N. Harwood Street, Suite 1300 Dallas, TX U.S.A Omnitracs, LLC. All rights reserved. Omnitracs is a trademark of Omnitracs, LLC. All other trademarks are the property of their respective owners. Omnitracs endeavors to ensure that the information in this document is correct and fairly stated, but Omnitracs is not liable for any errors or omissions. Published information may not be up to date, and it is important to confirm current status with Omnitracs. This technical data may be subject to U.S. and international export, re-export or transfer (export) laws. Diversion contrary to U.S. and international law is strictly prohibited. March