Skip to main content
Omnitracs Knowledge Base

Vehicle Inspection Report 2.0 Release Notes

These release notes describe the new features and enhancements for Vehicle Inspection Report, scheduled for release early 2017.

For previous release notes, click here.

For patch notes, click here.

Requirements

To use VIR, you need Internet Explorer 10, 11, or Edge, Chrome, or FireFox. The VIR application adapts to your monitor's resolution.

A new version of the mobile application that supports features mentioned here is available on MCP50s with firmware release 13x, anticipated in early 2017. Platforms other than MCP100 will support new features in later firmware releases.

Enhancements

In addition to a complete overhaul of the host user interface, VIR 2.0 includes the following enhancements.

Regulatory Changes

On December 18, 2014, the FMCSA rescinded the requirement that commercial motor vehicle (CMV) drivers operating in interstate commerce (except drivers of passenger-carrying CMVs) submit and retain VIRs when the driver has neither found nor been made aware of any vehicle defects or deficiencies. U.S. carriers that travel into Canada will still be required to complete a post trip VIR whether or not defects exist. Canadian regulations still require CMV drivers submit and retain one VIR each day. This affects both drivers and administrative personnel that manage the HOS host. Each will see new options in their respective interfaces.

Location Information

To insure driver compliance, the VIR application has been updated to include the location where a vehicle inspection was performed.

Multiple VIR

Prior to version 2.0, a fault identified by a VIR had to be fixed, the fix verified by the driver, and that acknowledgement returned to the host before the system would allow a new VIR to be entered. If a driver performed VIR inspections at the beginning and end of the shift, this posed problems. Now drivers are able to enter multiple VIRs per day, without the prior VIRs being closed.

Driver Approval

Prior to version 2.0, VIR host administrators had to approve the repair of a fault recorded by a driver. In the world of the owner/operator, the approving authority for a defect once it is corrected may be solely the driver (who is also the owner of the vehicle). This new option will allow owner/operators to be the approving authority for repairs in their truck. This feature will affect the driver, who will now be required to do the approval and the host administrator who will no longer be in the loop.

Through Settings, VIR administrators identify UAs for drivers that can close a VIR from their Omnitracs in-cab device.

Maintenance Approval

With the release of VIR 2.0, third-party maintenance personnel can be granted restricted access to record and update a repair in the application. Users at maintenance shops can be set up in Services Portal Administration with limited access to VIR.

Report Enhancements

In prior versions, the missing VIR report and the VIR Home page showed the past 24 hours of information, making it difficult for fleet managers to identify trends and potential problem areas. With VIR 2.0, fleet managers can sort, filter, and interact more efficiently with historical VIRs.

Canadian Rules

VIR has been updated to ensure compliance with MOT requirements for Canadian carriers. These changes include adding additional items to check and information to be reported and retained. Additionally, U.S. carries whose business requires them to cross into Canada are operating as less-than compliant. This change affects all Canadian carries and some US carriers.

Fixes

Many of these fixes were corrected by virture of the complete rework of the VIR UI and are no longer applicable.

  • Units that are removed from Op Profile with the VIR application no longer show missing VIR on host.
  • Due to the UI overhaul, the color of the text in the popups is corrected and consistent.
  • VIR details now display quickly.
  • The error log is now accurately displaying errors related to resending VIRs.
  • The driver's last name now displays correctly in the Driver Name column in the VIR table.
  • The description in the VIR details report now displays up to1024 characters.
  • The application no longer hangs when quickly switching among various global groups.
  • Navigation has been completely reworked and fully supports Firefox.
  • VIRs with special characters in comments are being processed.
  • VIR times are no longer off by one hour in Service Portal (DOT audits are unaffected).
  • Missing VIR reports does now have a consistent time format.

Known Issues

  • Shaw customers are being directed to the US version of VIR. Impact: The customer is unable to use the email links to navigate directly to VIR links and must search for them manually within the application and they’re receiving Omnitracs-branded emails.
  • VIR runs slowly using IE. Impact: Customers may want to use FireFox or Chrome.
  • The VIR email link only takes you to the application not the VIR record. Impact: Customers have to search for the VIR.

Patch 2.0.30

Patch released March 2017.

Tutorial

A tutorial is provided upon login to guide users through the new interface.

Fixes

Many of these fixes were corrected by virtue of the complete rework of the VIR UI and are no longer applicable.

  • Trailer and truck reports now show correct and consistent data on both PDF and CSV exports.
  • The Create Report button is disabled when there is no content to report.
  • Missing VIRs are no longer generated for vehicels with no movement.
  • The odometer field was removed from trailer PDF and CSV reports.

Known Issues

Some known issues are scheduled to be fixed in Patch 2, scheduled for release this Spring.

  • Response XML from the VIR Web Service does not always include the "ID" tag. Impact: Integration that uses this field will generate flawed data.
  • VIR runs slowly using IE. Impact: Customers may want to use FireFox or Chrome.
  • The VIR email link only takes you to the application not the VIR record. Impact: Customers have to search for the VIR.
  • If the administrator tunrs off the in-application notifiactions, the notification is not arriving with Mechanic Role. Impact: Mechanics may not see defects, no workaround.
  • Users cannot filter by trailer ID. Impact: users cannot search by trailer ID, no workaround – scheduled to be corrected in Patch 2.
  • When running a report against a search, trailer and truck reports display more data than anticipated in both PDF and CSV exports. Imact: Search returns too many items, no workaround – scheduled to be corrected in Patch 2.
  • During DST change, when selecting a drivers VIR to print time is off 1 hour. Impact: Printed inspection reports may be an hour off, no workaround.
  • When filtering by a global group, users can select a group without selecting “Filter By The Groups Below.” Impact: Until Filter By The Groups Below is selected, the group filter is not applied.
  • Missing VIR Reports are not accurately reporting Duty Status, Time Started, Distance, or Location Fields. The data is collected, but not displayed on the report. Impact: Reports are inaccurate, no workaround.

Patch 2.0.31

Patch released April 2017.

Enhancements

This patch of VIR includes the following enhancements:

TrailerID Search

Ability to search by TrailerID added to searchable criteria. Criteria now includes search by VehicleID, TrailerID, DriverID, Driver Name, UA, and type of defect.

Fixes

Many of these fixes were corrected by virtue of the complete rework of the VIR UI and are no longer applicable.

  • Search by number populates all reports with that series including VIR number, populating unintended additional results.
  • The time is now displaying correctly when selecting a driver’s VIR to print during DST change.
  • The report columns “VIR Last Reported” and “Time Started” no longer just show the date, they also show the time. The Column “Time Started” is wider so it can display the date and time on one line.

Known Issues

  • Response XML from the VIR Web Service does not always include the "ID" tag. Impact: Integration that uses this field will generate flawed data.
  • VIR runs slowly using IE. Impact: Customers may want to use FireFox or Chrome.
  • The VIR email link only takes you to the application not the VIR record. Impact: Customers have to search for the report.
  • If the administrator turns off the in-application notifications, the notification is not arriving with Mechanic Role. Impact: Mechanics may not see defects, no workaround.
  • When filtering by a global group, users can select a group without selecting “Filter By The Groups Below.” Impact: Until Filter By The Groups Below is selected, the group filter is not applied.
  • Missing VIR Reports are not accurately reporting Duty Status, Time Started, Distance, or Location Fields. The data is collected, but not displayed on the report. Impact: Reports do not display all data, no workaround.

Patch 2.0.35

Patch released May 2017.

Fixes

  • The Missing VIR report was updated to include a "Date Missed" column that replaces the "Classification" column.
  • Email addresses for notifications may now include a period in the user ID. This is now valid: firstname.lastname@email.com

Known Issues

  • Response XML from the VIR Web Service does not always include the "ID" tag. Impact: Integration that uses this field will generate flawed data.
  • VIR runs slowly using IE. Impact: Customers may want to use FireFox or Chrome.
  • The VIR email link only takes you to the application not the VIR record. Impact: Customers have to search for the report.
  • If the administrator turns off the in-application notifications, the notification is not arriving with Mechanic Role. Impact: Mechanics may not see defects, no workaround.
  • When filtering by a global group, users can select a group without selecting “Filter By The Groups Below.” Impact: Until Filter By The Groups Below is selected, the group filter is not applied.
  • Missing VIR Reports are not accurately reporting Duty Status, Time Started, Distance, or Location Fields. The data is collected, but not displayed on the report. Impact: Reports do not display all data, no workaround.

 


© 2018 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. 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.

 

  • Was this article helpful?