Use the tabs below to learn more. If you don’t find the answer to your question or would like additional information, please contact us.
The Road Usage Charge (RUC) Program, was created by Senate Bill 810, and authorizes the Oregon Department of Transportation to assess a per-mile charge for volunteer drivers. The OReGO program starts July 1, 2015.
The administrative rules for the program can be found here.
Here are the details:
Some vehicles may not be eligible for the program because the mileage reporting device cannot read messages from the vehicle. These vehicles include:
Some vehicles may not be eligible because the requirements of Senate Bill 810 restrict them from entering the program. These vehicles include:
If your vehicle is ineligible because it fits into one of the above categories, we would still like you to be part of our community. Please join the interest list to get program updates
OReGO account managers are keenly interested in developing the ability to reliably access program data to allow EVs to participate. One account manager is accepting EVs on a trial basis.
OReGO mileage reporting devices use the OBD-II port in the vehicle. This port was originally developed to help car manufacturers monitor engine performance to comply with Environment Protection Agency air quality standards. However, because EVs don’t use traditional fuels, they don’t report data in a standardized way. The manufacturers of OReGO mileage reporting devices are refining their methods to read the data supplied via the port so they can track miles and trips accurately. Currently there are several EVs enrolled in OReGO.
If you are interested in enrolling your EV in OReGO on a trial basis, please contact us at MyOReGO@odot.state.or.us.
Occasionally, participants in the OReGO program may experience mileage reporting issues with their Mileage Reporting Device, known as an MRD. Potential causes for these issues include:
ODOT and the OReGO account managers have procedures in place to manage these scenarios. The systems can detect when an MRD is unplugged and reinstalled. Sometimes the MRD can recover the mileage and report it. When that is not possible, the system won’t calculate the road usage charge and a fuels tax credit for that day (which means for those miles you pay the fuels tax at the pump, and not to OReGO).
If the disruption continues for more than 10 days, the road usage charge may be charged for every day until the device operates properly or is replaced. Assessed mileage will be based on the participant’s historic average driving methods.
If mileage reporting issues occur regularly on an account, the account manager will contact the participant to research and find a solution to the issue.
No, it’s just about the same. No matter what size or how loaded up a regular car, pickup truck or passenger van is, there is no measurable difference in the impact these vehicles have on a typical highway. Commercial trucks cause thousands of times more wear and tear because of their heavy loads, and this is accounted for in the amount they pay in weight-mile taxes in Oregon.
More about the damage and vehicle weightDamage to the pavement on our roads is the primary reason we have to maintain them regularly and repave as needed. This damage occurs for three main reasons:
The Federal Highway Administration has devised a way to tell how much damage vehicles cause due to vehicle weight. It is called a vehicle’s “equivalent single axle load,” or ESAL. The more weight, the more ESALs – and the more damage. As such, heavy trucks and buses are responsible for a majority of pavement damage. Considering that a typical automobile weighs between 2,000 and 7,000 pounds, even a fully loaded large passenger van will only generate about 0.003 ESALs while a fully loaded tractor-semi trailer can generate up to about 3 ESALs (depending upon pavement type, structure and terminal serviceability). To learn more about how pavement engineers use ESAL calculation, visit: http://www.pavementinteractive.org/article/equivalent-single-axle-load/. AASHTO also has a simplified chart (PDF) that shows the different impacts, based on ESALs.
To ensure ongoing security compliance, ODOT monitors account manager data for anomalies, which includes trend analysis. ODOT uses the following tools to ensure volunteer information is protected:
ODOT has the ability to audit the account managers, and any other companies working in conjunction with them on the OReGO project. Account managers submit weekly, monthly, and quarterly reports to ODOT to monitor for anomalies and ensure security measures are enacted. Security requirements apply to all subsystems and functions.
Before they are allowed to participate in the program, account managers must pass through a certification process where they must prove compliance using a combination of test results, policy and procedure documents, and external compliance certificates.
Here is an example of a security requirements: The account manager shall provide a system architecture diagram that illustrates the location and key security measures proposed for its RUC program system. ODOT staff confirms this by evaluating the System Architecture Diagram to ensure these features are included:
Contractually, account managers are required to protect personally identifiable information and are responsible for all costs associated with any losses due to a breach. Specifically, the contract requires: Contractor at all times shall comply with Agency’s security policies. Security Policies include but are not limited to: The federal Automobile Information Disclosure Act, ORS 319.915, ORS 802.179, and security requirements in the System Requirement Specifications document in the performance of this Price Agreement.
Account Managers must provide a SSAE-16 audit report annually, which ensures they are following best practices. These audits are required for service organizations that perform outsourced services that affect the financial statement of another entity. Because account managers are collecting road usage charges on ODOT’s behalf, and the revenues affect ODOT’s financial statement, these audits are required. These audit reports provide information and analysis on about the information technology general controls related to information security, access, environmental controls, physical security, system development and change management, and system monitoring and maintenance. It also includes an analysis on the account manager’s processing controls such as data receipt, data processes, data transmission, and data reporting. Security standards are confirmed through ODOT staff’s evaluation as well as through independent certified public accountant prepared reports.
Account managers contracted with ODOT collect unique information depending on the option you choose.
Commercial Account Managers collect location information to determine whether you are driving inside or outside Oregon, and for the purposes of administrating their value-added services. In the regular operation of the program, location information is not disclosed to ODOT. ODOT employees may review data for program audit purposes. All program-related data remains confidential based on Oregon Law and ODOT policy.
The ODOT Account Manager (Sanef) does not collect location information, only miles driven and fuel consumed.
All program data is destroyed on a set schedule per program policy.