Features and Enhancements

Omnitracs Weigh Station Bypass Provided by Drivewyze™ PreClear

This version of Weigh Station Bypass has many new fixes including an enhancement allowing drivers to receive Weigh Station Bypass information without logging in to the MCP.

Mobile Data Capture (MDC)

Mobile Data Capture is supported on the MCP50 and enables drivers to easily capture documents on approved Android devices, synchronize, and view the documents in the Scanning application. MDC works with the Workflow application to ensure drivers are capturing necessary documents to send back to the host. MDC is currently available in the US only (not Canada).

Vehicle Inspection Report (VIR)

Vehicle Inspection Report has been reworked to make it easier to use both on the host and mobile applications. More information can be found in the What’s New Video and the latest VIR release notes. Canada compliance was added to this version of VIR.

ELD Enhancements

Most of the features and enhancements listed here are related to the ELD mandate and are viewable when using ELDs, units that have the ELD firmware and have toggled ELD on for those units. Additionally, there may be:

AOBRDs – The unit doesn’t have the ELD firmware and application functions as it did before the upgrade

AOBRD Mode – The unit has the ELD firmware, but hasn’t enabled ELD for the unit; the unit has some ELD-features enabled

ELD - The unit was upgraded to ELD-compatible firmware and full ELD features are toggled on.

Be aware that the driver may not edit previously certified logs.

In all instances, when referring to an “authenticated” driver, that is a driver who has successfully logged in to the AOBRD/ELD. A driver can tell if they’re authenticated if their user ID resolves to their full name.

Feature/Function

AOBRD

ELD-capable, running as AOBRD

ELD

Unassigned Driving reconciled

Host only

Mobile; if rejected then returned to the host

Mobile; if rejected then returned to the host

Mobile Edits can be disabled

Yes

Yes

No

Driver must approve/decline edits from carrier

No

No

Yes

Auto on-duty/off-duty at login/logout

Yes

No

No

Events timed to seconds

No

Yes

Yes

Capture VIN from ECM

No

Yes

Yes

Capture Engine Hours from ECM

No

Yes

Yes

Complete edit audit history visible on host

No (original and last only)

No (viewable in ELD Driver Log Report if running a mixture of ELD units +/- AOBRD mode units or AOBRDs)

Comparison – How ELD Firmware Affects AOBRDs

Please note that how Hours of Service and log in/log out functions on the IVG is directly affected by the firmware version. Some features that are implemented for the ELD mandate are exposed to the driver even if ELD is not turned on for the unit.

Login/Log out (duty status) – Upon login or log out, drivers are prompted to select a duty status. See Driver Login Changes for details.

Certification (not approve) – Drivers now go to the Certify tab (not Approve) to review and certify their logs in 24 hour increments, not multiple days at a time. Additionally, drivers must approve their logs daily.

Driver Log Edits – Drivers are prompted to approve driver log edits performed by the carrier. Additionally, how log edits are handled differs between AOBRDs and ELDs. See Carrier-Initiated Driver Log Edits for details.

Security password prompt – If there are two drivers logged in to the IVG, the co-driver is required to provide their password to access their logs.

Durations to seconds – All driver hours are now recorded to the second, not to the minute.

Drive time – All drive time is now collected and must be allocated to a driver. If the drive time was generated by a non-ELD driver, like a mechanic, you should create that driver in Hours of Service and indicate that they are ELD-exempt. See ELD Exempt Drivers for details.

Driver edits – AOBRDs are not required to allow drivers to edit their logs although they are permitted per regulation guidance. ELDs, however, are required to provide that function. There is no longer an option to toggle that permission on/off for ELDs in the Hours of Service host application, and if a driver is not granted permission to edit logs on an AOBRD, when the driver logs into an ELD, it will ignore the host application’s setting and permit the driver to edit his logs.

Sending ERODS

With Hours of Service release 5.1, an ERODS file can be generated by and transferred from both the in-cab device and the host application to Omnitracs’ internal EDS (ERODS Delivery Service) server. Because the FMCSA servers are not yet setup to receive ERODS submissions, the file transfer will fail.

Mobile – Upon receiving the ERODS file from the mobile device, the EDS displays a notification on the mobile via the Alert Manager. Until the FMCSA is ready to receive ERODS files, this notification indicates a failure.

Host – In the Admin section, there are two new tabs, ERODS (Request) and ERODS (Status). Until the FMCSA is ready to receive ERODS files, these pages will only display failures.

When the FMCSA’s servers can accept ERODS files, the ERODS file transfer statuses will be: Success, Failure, or Pending.

Host Edits of Driver Logs

When a driver is using a unit in AOBRD Mode, and that driver’s duty status that is not part of a driver’s current duty cycle is edited through the host system, those dates are sent to the driver and presented for recertification.

Be aware that days in the driver’s current duty cycle that were not edited are not uncertified (reverted to uncertified).

Tab Changes

The Carriers tab should display the carrier information as entered in the Hours of Service back office application. The carriers tab and carriers set up in Hours of Service does not identify separate companies the driver may haul for, just divisions of a single company like bulk versus refrigerated or hazmat versus DTTS (defense transportation tracking system). If your company has multiple divisions that are their own carrier entities, you would enter those in the Hours of Service back office application and the driver would select the carrier here.

ELD Exempt Drivers

You can identify drivers as ELD exempt, meaning that they’re not subject to the ELD requirements. This difference allows you to create ELD exempt drivers like mechanics who can perform yard moves or longer road tests, short haul drivers using an ELD-equipped vehicle, or test drive vehicles.

When an ELD exempt driver logs in or out of the IVG, the driver is alerted of their exempt status. While in exempt mode, the IVG records automatic transitions to and from Driving Duty Status.

Exempt driver mode is available when running ELD firmware in AOBRD mode and full ELD-capable devices. If the driver’s exempt status changes while driver is logged, the mobile will notify them of this change.

While in exempt driver mode, the ELD:

Does not prompt the driver to accept or reject carrier edits or unidentified driving time

Does not prompt the driver for missing load info or to certify logs

Does not show or enforce rest break rules

Does not show the eRODS transfer button

Displays collected exempt driver data in header for all days in that duty cycle

While in exempt mode, the mobile follows AOBRD personal conveyance and driver edit rules, if configured by the carrier for the driver.

Unassigned Driving Time (Unassigned Vehicle Activity – UVA)

If any unassigned driving time (drive time without an associated driver ID) is generated on an ELD-equipped vehicle, that UVA stays with the IVG and must be assigned to one of the following:

A driver

An ELD-exempt driver (like a mechanic)

“No Driver” or a category such as Fuel Dock, OEM Maintenance, etc.

When a non-exempt driver logs in to an IVG that has UVA, the driver is prompted to review and confirm that this is their drive time. If a driver:

Confirms that the UVA is theirs, that time is transferred to their logs on the IVG and notification is sent to the Hours of Service host application.

Rejects the UVA, they must enter a comment about why they are rejecting the time and a notification is sent to the host.

Accumulated UVA is not presented to a non-exempt driver until that driver’s logs have been pulled down from the host application.

On the host application, UVA continues to show on the Vehicle Details page as it accumulates on the IVG (same as it does today). However, the host user cannot take any action against that UVA until one of the following occurs:

The UVA is Rejected by a non-exempt driver on that IVG

Eight days pass without a non-exempt driver logging into that IVG

Beginning of Trip/End of Trip

For AOBRDs or units running in AOBRD mode, the beginning of trip (BOT) and end of trip (EOT) thresholds are still set in the Hours of Service back office application on the Administration > HOS Setup tab.

For ELDs, BOT is triggered when the vehicle’s speed is equal to or greater than 5 MPH (8 KPH) at any time. There is no distance threshold (how far a vehicle must travel while at speed).

For ELDs, EOT is triggered after five minutes of no movement, the driver sees a popup asking, “Vehicle stopped for five minutes, switch to On Duty?” When stopped for five minutes, the driver is prompted by the ELD to indicate that driving has ended. If the driver responds:

YES – The driver is put into ON DUTY and the activity is recorded as the time when the wheels stopped moving.

NO – The driver remains in DRIVE.

No response – After one additional minute, the driver is transitioned to ON DUTY, and the activity is reported as the time when the wheels stopped moving (6 minutes).

No Minimum Duty Status

Minimum duty status for AOBRDs or units running in AOBRD mode is set on the Administration > HOS Setup page in the Hours of Service back office application. For ELDs, there is no minimum duty status and all time is recorded.

Yard Move and Personal Conveyance

Yard move is a driver-initiated event that identifies when an ELD-equipped vehicle is moved in a private yard, without public access. Settings for Yard Move and Personal Conveyance are defined on the Administration > HOS Settings page in the Hours of Service back office application. After the fleet settings are enabled, individual drivers may be enabled to use Yard Move and Personal Conveyance via Driver Administration.

Personal conveyance replaces off duty drive time and can be set to be unlimited, meaning the driver can operate for any length of time in personal conveyance, or limited, meaning you identify how many minutes a driver may be in personal conveyance before receiving an alert on the ELD.

For ELDs with drivers in in personal conveyance, Omnitracs no longer reads the truck’s ECM and no odometer readings are recorded during this driver-initiated event. While in personal conveyance, position accuracy is reduced to 10 miles (16 kilometers). The finer resolution GPS and engine data are captured for duty statuses that precede and follow personal conveyance.

The ELD does not automatically transition the driver to Drive when the customer-defined personal conveyance threshold is met (number of minutes). Instead, the driver is alerted that the Personal Conveyance threshold established by the customer was exceeded, but the driver’s duty status is NOT changed to Drive. The driver must manually terminate the personal conveyance duty status.

Because personal conveyance is triggered when selected by the driver, not when the wheels are in motion, you may see a decrease in the number of personal conveyance events and an increase in the total time in personal conveyance in your logs.

When drive time accumulates as personal conveyance or yard move, it’s indicated on the Graph tab as a different color, not on a separate line. Yard move accumulates on the on-duty line and personal conveyance accumulates on the off-duty line

Load Information Form and Manner Changes

Load information must be entered for each day or the driver incurs a form and manner violation. If the load/trailer information is missing, drivers are now prompted to enter it for any days in the driver’s current duty cycle upon logout.

If load information isn’t entered, the driver is prompted to enter is while logging out.

Duty Status Splits

Internal duty status splits at midnight and at state crossings are no longer recorded on an ELD or AOBRD-mode units.

Enhanced Sensor Failure Logic

When an error occurs or is cleared, the driver is notified on the MCP and the Hours of Service host application is updated with that information. These errors are viewable in the Hours of Service back office application and on the Sensor Failure report.

In addition to the legacy speedometer and odometer Omnitracs Sensor Failures, the ELD mandate introduces additional diagnostic and malfunction reporting requirements. Both ELDs and units running in AOBRD-mode incorporate events. The existing Sensor Failure report is being replaced with a Diagnostics and Malfunctions Report that shows both the existing AOBRD sensor Failures and the new ELD diagnostics and malfunctions on a single report.

Odometer Sensor Failure

The odometer sensor validates both that the odometer is working correctly and that the physical connection among the ELD, odometer, and ECM is active. The ELD detects the sensor status by querying the ECM when one of three states is detected:

Immediately after vehicle movement

Immediately after stopped (0 MPH/KPH for 3+ consecutive seconds)

When a driving status is split (when the driver accepts a split or creates an edit to split a status)

An error is recorded when any of the following verification criteria is met:

When the odometer reading is less than 0

When the odometer reading is over 10 million

When the odometer decreases by 1.0 mi (1.6 km) between readings

When the ELD records an error, it uses alert manager to send the driver an odometer sensor failure event and the error is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the eRODS file transmitted to enforcement.

The error state is cleared when, during the next triggering event, the ELD determines that the trigger is no longer active. When the ELD clears the error, it uses alert manager to send the driver an odometer sensor failure clear event and the “error clear” is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the eRODS file transmitted to enforcement

The odometer sensor failure query/recording is suspended during when the driver is in the personal conveyance duty status.

In a later release, there will be a report that can be run from the HOS host app to aggregate these errors.

Road Speed Sensor Failure

The road speed sensor validates the ECM’s speedometer data by comparing it to GPS data. The road speed sensor data is validated every 60 seconds the ELD records an error when any of the following verification criteria is met:

The ECM reports that road speed is 0 and GPS speed exceeds 10 MPH (16 KPH) for 5 or more minutes

The ECM reports that road speed is static and the GPS speed exceeds 10 MPH (16 KPH) for 5 or more minutes

The road speed from the ECM is fixed at 1 MPH (1.6 KPH) or greater and the GPS speed reads 0 for 5 or more minutes

When the ELD records an error, it uses alert manager to send the driver a road speed sensor failure event and the error is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the eRODS file transmitted to enforcement.

The road speed sensor error is cleared when the verification criteria is no longer met. When the ELD clears the error, it uses alert manager to send the driver an odometer sensor failure clear event and the “error clear” is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the eRODS file transmitted to enforcement

The road speed sensor failure query/recording is suspended during when the driver is in the personal conveyance duty status.

Power Compliance Monitoring

The ELD mandate requires that the ELD monitors ECM data to ensure that the unit becomes “fully functional” within one minute of CMV engine receiving power.

If the ELD is not fully functional within one minute of engine power up, the ELD triggers a power data diagnostics event, logs it in both the eRODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the diagnostic to the driver.

If the aggregate time that the ELD spends with an active power data diagnostics event exceeds 30 minutes within a continuous 24-hour logging period, across all drivers for that vehicle, including unidentified drivers, the ELD triggers a power compliance malfunction event, logs it in both the eRODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when a diagnostic or malfunction event is triggered, the diagnostic or malfunction event is recorded under the unidentified driver profile.

When the 24-hour logging day ends, the ELD clears the diagnostic or malfunction, updates the eRODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

Engine Synchronization Compliance Monitoring

The ELD mandate requires that the ELD mobile unit monitor the data it receives from the ECM and other onboard sensors to ensure continued operation of the ELD and to record/monitor Engine hours, odometer, and speed. The following data requirements are monitored and maintained to ensure that the ELD:

Remains powered on when the commercial motor vehicle (CMV) engine is powered on

Accurately detects the vehicle motion status

Accurately logs vehicle miles over the course of an ignition power cycle, and the total operating time of the vehicle

Accurately logs elapsed engine hours over the course of an ignition power cycle, and the total operating time of the vehicle

Accurately detects the CMV’s vehicle identification number

If the ELD cannot acquire updated values for the previous parameters within five seconds of the need, the ELD triggers an engine synchronization data diagnostics event, logs it in the eRODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the diagnostic to the driver.

If the aggregate time that the ELD is not connected to any of the required data sources exceeds 30 minutes within a continuous 24-hour logging period, across all drivers for that vehicle, including unidentified drivers, the ELD triggers an engine synchronization compliance malfunction event, logs it in the eRODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when a diagnostic or malfunction event is triggered, the diagnostic or malfunction event will be recorded under the unidentified driver profile.

When the 24-hour logging day ends, the ELD clears the diagnostic or malfunction, updates the eRODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

Timing Compliance Monitoring

The ELD mandate requires that the ELD obtain and record date and time information automatically without external input or interference from a motor carrier, driver, or any other person. This test is currently performed when the MCP boots and drift typically never exceeds two seconds.

If the ELD detects a deviation from Coordinated Universal Time (UTC) of more than 10 minutes, it records a timing compliance malfunction, logs it in the eRODS and driver log detail for the current authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when the malfunction event is triggered, the malfunction event is recorded under the unidentified driver profile.

When the deviation from UTC is less than 10 minutes, the ELD clears the malfunction, updates the eRODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

Positioning Compliance Monitoring

The ELD mandate requires that the ELD determine the CMV’s GPS position at least once every 5 miles (8 km) of driving. The following data requirements are monitored to ensure that the ELD:

Acquires an accurate GPS position at least every 5 miles (8 km) of driving

Accurately records the position information in standard latitude/longitude coordinates, to a hundredths of a degree precision

Verifies that the position information is recorded with a maximum of 0.5 miles (0.8 km) deviation from position of the CMV

Reports the position information to within 1 mile (1.6 km) of the position of the CMV

Reduces reporting precision to tenths of a degree when in personal conveyance mode

Includes distance travelled since last location query for any ELD events that require location information

If the ELD is unable to acquire a valid position measurement while the vehicle is in motion for 60 minutes or more within a continuous 24-hour logging period, the ELD sets a positioning compliance malfunction event, logs it in the eRODS and driver log detail for the current authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when the malfunction event is triggered, the malfunction event is recorded under the unidentified driver profile.

When the authenticated driver’s 24-hour logging day ends, the ELD clears the malfunction, updates the eRODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

If a duty status change ELD event requiring position information occurs, and the ELD is unable to collect such data, and the ELD has not set a positioning compliance malfunction, the ELD prompts the driver to manually enter position information via alert manager. The driver is required to enter the missing data as an edit.

If the driver does not enter position information when prompted, the ELD sets a missing required data element diagnostic event, logs it in the eRODS and driver log detail for the current authenticated driver, and provide a continuous visual indicator of the malfunction to the driver. The ELD will remove the missing required data element diagnostic visual indicator when the authenticated drivers logs out.

Data Recording Compliance Monitoring

The ELD mandate requires that the ELD monitor its storage capacity, both integrity of the stored information and to verify that there is sufficient data storage space, and record the appropriate malfunctions if any of those capabilities stop functioning properly.

If the ELD is unable to record or retain required events or retrieve logs that are not available via the host component, the ELD sets a data recording compliance malfunction, updates the eRODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

The ELD does not record power data diagnostic events while a data recording compliance malfunction is active.

If there is no authenticated driver logged in when the malfunction event is triggered, the malfunction event is recorded under the unidentified driver profile.

When the ELD resumes recording or retaining required events or retrieving logs, the ELD clears the malfunction, updates the eRODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

If any required fields are missing from an event record, the ELD sets missing required data elements data diagnostic, log it in the eRODS and driver log detail for the current authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when the diagnostic event is triggered, the diagnostic event is recorded under the unidentified driver profile.

When required fields are no longer missing from the specific event records, the ELD clears the malfunction, updates the eRODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

GPS Sensor Failure – Removed

Because new, ELD required sensor validation tests provide more information than the old GPS sensor failure, the MCP no longer checks for GPS sensor errors using the standard GPS Sensor Failure.

Diagnostics and Malfunctions Report

When there’s a malfunction on the MCP, that error and the error correction are displayed to the driver in the Alert Manager and are recorded at the host. The new Diagnostics and Malfunctions report shows any errors and error corrections.

Driver Log Edits

When a unit is running ELD, all drivers, regardless of host settings, are permitted to edit logs on the MCP. Please keep in mind that drivers cannot shorten drive time or change personal conveyance or yard move to a non-driving activity. For AOBRD-mode driver edit permissions are controlled by host settings.

Driver Login Changes

There must always be an active driver. When a single driver logs in, that driver is by default the active driver. When a co-driver logs in, that driver can be identified as inactive or the active driver.

To ensure driver security, the co-driver is prompted to reenter a password to view or edit logs. The active driver can access logs without providing a password.

Time Resolution Format – ELD and AOBRD-mode

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.

Carrier-Initiated Driver Log Edits

When a driver’s logs are edited by the carrier (back office personnel at your company), ELDs handle changes differently than AOBRDs and AOBRD Mode units. AOBRDs and AOBRD Mode units function the same way: host application edits are accepted immediately upon receipt by the mobile unit.

Edits made to driver logs through the Hours of Service host application for ELD software are not automatically accepted, but remain in a Pending state until reviewed and accepted by the driver through the in-cab hardware. The edited record is pending within the Hours of Service host application until the driver accepts or rejects the proposed changes. Additionally, the driver must review and accept or reject those changes upon login to the Hours of Service mobile application.

Pending duty status changes cannot be edited after they are sent to the driver.

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.

Edits made to a driver’s logs while the driver is not logged into a vehicle remain Pending until the driver logs into a vehicle. If the driver logs into a vehicle using an AOBRD, the Pending edits immediately become active.

In summary:

If the software in the cab is an AOBRD or AOBRD Mode, 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 carrier-initiated edits.

When a driver logs in to a mobile running ELD software, the driver is prompted to review and accept or reject the changes.

Approve

To comply with ELD requirements, the Approve tab is renamed Certify and certifications are done per 24 hour period, not for multiple days at a time.

If certifications are pending, the driver is notified on the Hours of Service home screen by a pop up (to certify carrier initiated edits) or by on-screen text that the driver should be familiar with today. To review and certify logs, the driver goes to Certify tab and scrolls to the date requiring certification.

Old

New

Certifying

Certified

Unassigned Vehicle Movement

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 on the mobile running ELD software 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.

Screen Changes

In addition to the previously stated functional changes, all screens in Hours of Service were updated to be easier to read. Below are the details of the screens that have changed features or are new to this release.

Initial Login

When logging in to the MCP, drivers are no longer On Duty by default. They are prompted to identify their duty status immediately after they enter their ID and password.

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.

Change Duty Status

The Change Duty Status screen has changed to make it easier to use. The duty status DRIVE cannot be manually selected by drivers with ELD firmware.

Today, the driver is automatically placed into various duty status when location, distance, or time thresholds are met. With this firmware release, the only automatically assigned duty status is driving activity.

Old

New

Day Log

Be aware that, while logs are synchronizing with the server, drivers may see a “Loading Log Data” notification on the Day Log tab. This message usually displays for fewer than five seconds and is not an error.

Known Issues

Critical Event Reporting (CER)

FCW/FTV data source did not show correctly if type is different from previous device. This has been fixed.

Previously, the overspeed event was not persisted after a reset. This has been fixed.

Hours of Service

The Hours of Service graph tab supports the FMCSA exemptions from the existing rest break rule.

There had been issues where the Hours of Service UI crashed when mobile users were trying to change/submit an inspector name on a report. This has been fixed.

Hours of Service Rest Break Exemption is now supported.

Mobile Data Capture (MDC)

No images will show as greyscale.

There is an improvement to the way Scanning talks to the Workflow application.

MDC software version is not persisted upon reboot.

Omnitracs Weigh Station Bypass provided by Drivewyze™ PreClear

To support Weigh Station Bypass customers who do not use Driver Login, there is a new build from Drivewyze that does not require Driver ID.

Performance Monitoring

Performance Monitoring previously reported only 80% of miles driven in some instances where drivers set in-cab units to km but the units were set differently in the host. This has been fixed.

The Metric Flag variable was reporting inconsistently between the mobile and host. The type of unit (Imperial or metric) submitted to the host through extracts are chosen by the driver, not host.

System

In addition to Canada, Enhanced International Roaming includes Mexico for GSM support.

OMNI API was enhanced to expose vehicle attributes (such as Vehicle ID, license plate and jurisdiction, and VIN) to third-party apps. At this time, we will allow VIN to be supplied by the customer since not all trucks are equipped to read VIN from the engine.

Vehicle Inspection Report (VIR)

Vehicle ID now pre-populates based on the unit’s current UA, but the field is editable so the driver can enter the Vehicle ID.

There is now the option to remove a Vehicle ID or Trailer ID (by selecting the Remove button at the end of the Vehicle ID/Trailer ID row) so drivers can submit a report for the vehicle or trailer only.

When Canadian rule set is enabled, drivers will be prompted to indicate a severity for each selected defect.

There can be up to 500 characters entered into the comment text box when describing vehicle defects.

Users can now click a VIR from the main page and view detailed information on existing reports.

Users are able to select and reject a repairs that are satisfactory or unsatisfactory, and resubmit a new report with defects.

There is now a confirmation screen to inform drivers that their vehicle inspection report was successfully submitted.

Newly submitted reports appear at the top of the list on the main screen.

Drivers will now see a Response Required cue to indicate that a response is required in order to close a report.

Enabled units are able to close their own reports, confirm closure or return to the review screen, and enter repair comments.

A section was added to show users where they are in the submission process and how much more they have to complete. The current or completed screens appear in white, and screens yet to be completed appear grey.

Drivers are able to submit up to five open vehicle reports at a time.

Drivers are able to have unlimited open trailer reports at a time.

There is now a message that displays when a user reaches the maximum allowed number of open vehicle reports.

Drivers are limited to submitting up to seven tractor or trailer defects so that reports aren’t filled with too many issues.

Mobile users are now able to review license plate and jurisdiction information to ensure correct reports (Canada).

Driver help files have been updated to reflect VIR 2.0.

The VIR homepage will now display “Maintenance Response Required” when the initial Vehicle/Trailer contains no defects but subsequent trailers indicate defects.

The “Response Needed” notification on the Vehicle Inspection button on the mobile unit’s home screen will only disappear after the appropriate responses have been submitted.

The full location information is displayed on mobile review screens for roadside enforcement.

Inspection reports are no longer erased after OTA firmware upgrades.

To be compliant with Canadian rules, the full, legal company name now displays and the company name field is editable at all times.

The input for Vehicle Jurisdiction is now a 2-character minimum (Canada).

The wording in the vehicle inspection summary is now fully compliant (Canada).

The compliance statement has been updated on the completed Driver Vehicle Inspection Report to accurately convey product compliance to Canadian law enforcement. The previous compliance statement is shown on the driver submission screen both statements convey correct compliance information (Canada).

Canadian ruleset is now the default when the driver is detected in Canada, even if the unit is configured to use both US and Canadian rules.

The vehicle ID now auto-populates and the driver may edit the field.

Updating from CA1312R to CA1316R will result in pre-existing vehicle inspection reports to be deleted. As a result, drivers will need to re-enter VIRs after the unit upgrades to version CA1316R. Omnitracs support will work directly with impacted fleets to resolve this issue.

Workflow

Exception errors were found after cancelling auto arrival and the unit was restarted while the GPS:Prearrived. This has been fixed.

The Document Type is no longer left blank when navigating to Scanning View from Workflow.

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. Specifications subject to change without notice.

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.