35077 Attachment C_Interface Control Document~1.pdf

Road Usage Charge Program

Interface Control Document

For Road Usage Charge Implementation

Version 2.2

Last Updated: September 17, 2021

ATTACHMENT C

This page intentionally left blank.

Table of Contents 1 Introduction

1.1 Document Overview

1.2 Definitions, Acronyms, and Abbreviations

1.3 Context

1.4 Documents

1.5 Open Architecture with Standardized Communication Objective

1.6 Applicable Standards and Preferences

1.7 Scope and Identification of Systems

1.7.1 Mileage Reporting Option

1.7.2 Data Collection Subsystem

1.7.3 Transaction Processor Subsystem

1.7.4 Account Management Subsystem

1.7.5 Administrator Subsystem

2 Interface between the Data Collection to the Transaction Processor subsystems ... 11

2.1 Data Collection Overview

2.1.1 Data Transfer

2.1.2 Transactions and Responses

2.1.3 Interface Requirements and Security

2.1.4 Communication Methods

2.1.5 Interface Initiation

2.2 Mileage Message Overview

2.2.1 Mileage Message JSON Structure

2.2.2 Mileage Message Definitions

2.2.3 Mileage Message Failure JSON Structure

2.2.4 Mileage Message Failure Definitions

3 Interface between Account Management subsystem and the Administrator subsystems

3.1 Program Monitoring Overview

3.1.1 Data Transfer

3.1.2 Transactions and Responses

3.1.3 Interface Requirements and Security

3.1.4 Interface Initiation

3.2 Mileage and RUC Revenue Message Overview

3.2.1 Mileage and RUC Revenue Message JSON Structure

3.2.2 Mileage and RUC Revenue Message Definitions

3.2.3 Mileage and RUC Renenue Message Response JSON Structure

3.2.4 Mileage and RUC Revenue Message Response Definitions

3.3 VIN Summary Message Overview

3.3.1 VIN Summary Message JSON Structure

3.3.2 VIN Summary Message Definitions

3.3.1 VIN Summary Message Response Data JSON Structure

3.3.2 VIN Summary Message Response Data Definitions

3.4 Errors and Events Message Overview

3.4.1 Errors and Events Message JSON Structure

3.4.2 Errors and Events Report Definitions

3.4.3 Errors and Events Report Response Data JSON Structure

3.4.1 Errors and Events Report Response Data Definitions

3.5 Account and VIN Update Message Overview

3.5.1 Account and VIN Update Message JSON Structure

3.5.2 Account and VIN Update Definitions

3.5.3 Account and VIN Update Response Data JSON Structure

3.5.4 Account and VIN Update Return Data Definitions

3.6 Quarterly Tax Report Overview

3.6.1 Data Transfer

3.6.2 Interface Requirements and Security

3.6.3 Interface Initiation

5 Oregon Department of Transportation

Revision History

Date Of Revision

Reason For the Change and Short Summary of the Revisions Made

Version Number

05/12/14 Procurement Document Released 1.0 07/16/14 Updates to definitions and fields 1.1 08/05/14 Corrections for Adjustments and Error codes

Added return message for Daily report 1.1

09/17/14 Corrected minor errors 1.2 12/19/14 Corrected minor errors 1.3 02/23/15 Update timestamp fields to use UTC 1.4 06/05/15 Identify optional fields 1.5 12/01/15 Revisions for general cleanup and mutually agreed upon changes during development and implementation 1.6

03/01/19 Added AMCustomerNumber as required in the VIN Summary and Errors and Events reports

1.7

08/22/19 Added requirements related to HB 2881 1.8 11/06/19 Removed the (if less than 0, then 0) note from the ADJBalance definition.

1.9

08/16/21 Added requriements from research and development projects.

New fields, removed fields, changed field names. Introduced max number of records per message and the 206 Partial Content response.

2.0

08/30/21 Account and VIN Update Response Message: revised fields 2.1 09/16/21 Mileage Message Response: Replaced FailedDate with

FailedReportingPeriodStart and FailedReportingPeriodEnd 2.2

Road Usage Charge Program 6

1 Introduction

Purpose The purpose of this document is to describe the specifications for interfaces between subsystems of the Oregon Road Usage Charge System.

The introduction section presents a brief overview of the system and interfaces to which this Interface Control Document (ICD) applies to help the reader understand the document organization and how to interpret the document.

System Name: Oregon Road Usage Charge (RUC) System System Acronym: RUC System System Owner: Administrator Interfaces Described: This ICD covers the interfaces between

• the Data Collection subsystem and Transaction Processor subsystem

• the Account Management subsystem and the Road Usage Charging Administrator subsystem A diagram of the architecture is included below.

ODOT00

Business Partner(s)OO

• Collect RUC tax

• Analyze reports/data

• Audit program participants

• Audit AMs

• Exception process refunds/payments

• RUC calculation

• Error checks Data

ParticipantO

BANK

Funds

• Record miles traveled

• Record fuel usage

Data Business Partner(s)O

• Provide and aggregate RUC data

Data Collection

Data

• Communication to volunteers

• Recruiting

• Validation/eligibility/maintenance

Data

Mileage Reporting Option

Transaction Processor Tax Reconciliation

Manage Volunteers• Dashboard/interface

• Technical system monitoring

• Process AM monitoring reports

Monitor & Reporting

Acronyms AM Account Manager DMV Driver and Motor Vehicles MRO Mileage Reporting Option ODOT Oregon Dept of Transportation RUC Road Usage Charge

• Collect RUC tax, reports and data

Tax Collection

• Vehicle Registration• Account payable

• Accounts receivable

• General ledger

DMVAccounting

• Certification

• Compliance

• Accounts payable

Manage Account Managers

• Setup/Manage accounts

• Claims management

• Billing / refunds to RPs

• Report data to ODOT

• Online RUC account

• RP notifications

Account Management

• Setup/manage account

• Register Vehicle

• Pay RUC, collect Credits

• Install / Activate MRO

Account Management

Industry Provided Legacy Systems

RUC Specific

Entity

BUSINESS PARTNER SUBSYSTEMS ADMINISTRATOR SUBSYSTEMS

Data

Funds

Data

Data

Data

1.1 Document Overview

This document provides the specifications for the standardized interfaces between the subsystems of the RUC system. The interface specifications may change over time. Changes will be managed through an ODOT led Change Management process.

Definitions, Acronyms, and Abbreviations

7 Oregon Department of Transportation

1.2 Definitions, Acronyms, and Abbreviations

Administrator – A government agency administering a RUC Program. For example, ODOT would be considered the Administrator for the OReGO Program.

AM – Account Manager, A type of business partner specifically responsible for participant service, account management, and account operations BP – Business Partner, An entity that provides a service that supports the RUC system. An entity providing account management services is an Account Manager. An Account Manager is a type of business partner. A Transaction Processor and Data Collector are also types of business partners DC – Data Collection Subsystem, A system that is operated by a business partner that receives and stores raw travel data from the MRO and sends the travel data to the Transactions Processor subsystem FIPS – Federal Information Processing Standard, which includes two-digit numerical codes for each U.S. state/territory GPS – Global Positioning System, provides vehicle location details to the system HTTP – HyperText Transfer Protocol.

ICD – Interface Control Document, provides technical specifications for communication interfaces within the RUC system IP – Internet Protocol JSON – JavaScript Object Notation MRO – Mileage Reporting Option, an interface with the vehicle to collect travel data ODOT – Oregon Department of Transportation PRD – Program Requirements Document REST – Representational State Transfer RUC – Road Usage Charge STSFA – Surface Transportation Systems Funding Alternatives TCP – Transmission Control Protocol TP – Transaction Processor Subsystem, A system that is operated by a business partner receives and stores the raw travel data sent from the DC. The RUC is also calculated in this system.

Travel data – Total miles traveled and, if available, total fuel used. May include vehicle location for location-based MROs.

VIN – Vehicle Identification Number

Road Usage Charge Program 8

1.3 Context

The OReGO Program, ODOT’s operational road usage charge (RUC) program, was enacted by Senate Bill 810 (2013). This system will allow for automatic collection of road use charges from subject vehicles.

1. This automatic collection uses a Mileage Reporting Option (MRO) and a Data Collection subsystem, that sends a standardized “mileage message” to the Transaction Processor subsystem.

2. The Transaction Processor subsystem sends the travel data to the Account Management system to administer customer accounts and invoice customers.

3. The Account Management subsystem administers customer accounts, collects information from vehicles, invoice customers, and sends revenue to the Oregon State Treasury.

4. The Account Managment subsystem reports the aggregated data to the Administrator subsystem

These subsystems are administered by business partners.

5. The Administrator subsystem audits and reconciles accounts from business partner reports required to monitor the program. Administrator functions include audits and account reconciliations of Account Manager reports required for financial operation and monitoring of the entire system.

The purpose of this document is to define all interfaces between the various systems and maintain standardized messaging. These interfaces are:

• Data Collection subsystem to the Transaction Processor subsystem

• Account Management subsystem to the Administrator subsystem

1.4 Documents

The technical aspects of the work are documented primarily in the following documents:

• Data Reporting Process Flow Document that describes the data flow between subsystems at a high level.

• This ICD that provides the specifications necessary to support the required communications between system interfaces.

• The data validations are included in 21Q3_AppendixC_Data_Validations_Table.docx

The business and administrative aspects of the program are documented in:

• Program Requirements Document (PRD)

1.5 Open Architecture with Standardized Communication Objective The Administrator designed this system to be fully open. Business partners will be eligible for certification to provide hardware or services. No hardware or service that is certified shall contain proprietary content that would limit the use of other hardware or services in the system.

The Administrator will certify any technology or service providing the business partner complies with the specifications. Conformance to the interface standards specified in this document is mandatory for any technology and any business partner. Vendors can use proprietary components to meet the requirements of the systems (as defined in the PRD) but they must stay open at the system level by using the defined interfaces in the ICD which standardizes the connections between the systems.

Utilizing standardized interfaces is vital to operating a system with open architecture. It allows for MROs from various technology providers to operate with various Data Collectors, Applicable Standards and Preferences

9 Oregon Department of Transportation

Transaction Processors, and Account Managers. It also will allow multiple Account Managers to operate with the Administrator.

The communications approach may employ any communications medium permitting an internet connection. This ICD provides a robust communications standard. Within internet communications, this ICD indicates usage of JSON messages.

1.6 Applicable Standards and Preferences

• REST

• JSON

• HTTP

• TCP

• IP

1.7 Scope and Identification of Systems

This ICD specifies the interface between:

1. The Data Collection subsystem and the Transaction Processor subsystem

2. The Account Management subsystem and the Administrator subsystem

DATA COLLECTION

ADMINISTRATING JURISDICTIONACCOUNT MANAGER(S)

BANK

Funds

Data

Reporting

Mileage Reporting

Transaction Processing

Tax Collection

DMV

Accounting

Manage Account ManagersAccount

Management

Inquiries & Issue Resolution

Manage Volunteers

Tax Reconciliation

Monitor & Reporting

Evaluation

Outreach

Transaction Processing

Mileage Message

Account and VIN Update Message VIN Summary Message Errors and Events Message Mileage and RUC Revenue Message

Road Usage Charge Program 10

1.7.1 Mileage Reporting Option

The Mileage Reporting Option (MRO) interfaces with vehicles that are subject to the Road Usage Charge to collect raw travel data. The travel data is reported by the MRO to the Data Collection subsystem for communications formatting.

1.7.2 Data Collection Subsystem

The Data Collection subsystem is designed to collect travel data from multiple types of MRO technology and store the data for later communication and audits. The Data Collection subsystem also creates and transmits a standardized formatted mileage message to the Transaction Processor subsystem.

1.7.3 Transaction Processor Subsystem

The Transactions Processor subsystem receives and stores mileage messages from the Data Collection subsystem, calculates the RUC, and transmits this information and the mileage message to the Account Management subsystem.

1.7.4 Account Management Subsystem

The Account Management subsystem receives and stores all travel data and associated RUC data sent by the Transaction Processor subsystem. The Account Manager is responsible for communicating the reported information to the Administrator subsystem through the defined system reports, with specifications defined below. The Account Management subsystem develops four required reports:

• Mileage and RUC Revenue message

• VIN Summary message

• Errors and Events message

• Account and VIN Update message

• Quarterly Tax Report

1.7.5 Administrator Subsystem

The Administrator uses the RUC Administrator subsystem (RUCAS) to oversee operations of all RUC subsystems (Account Managers and the Administrator). The Administrator audits, edits and verifies the completeness and correctness of the mileage and revenue data. The Administrator confirms revenue transfers to the appropriate state treasurer and provides accounting posting information. The Administrator develops operational and statistical reports for verification of monthly operations, revenue forecasting and for program evaluation.

Data Collection Overview

11 Oregon Department of Transportation

2 Interface between the Data Collection to the Transaction Processor subsystems

2.1 Data Collection Overview

The interface between the Data Collection subsystem and the Transaction Processing subsystem has one defined report that is used transfer the travel data.

1. Mileage Message: The mileage message contains the details for travel data per reporting period for each VIN/MRO.

2.1.1 Data Transfer

Data will be sent from the Data Collection subsystem to the Transaction Processor subsystem using REST and JSON, utilizing the format as defined in this document. The frequency of transmission is parameterized in the Data Collection subsystem, and set per the Administrator requirements.

2.1.2 Transactions and Responses

Transactions are comprised of one mileage message moving from the Data Collection subsystem to the Transaction Processor subsystem. Transactions are acknowledged by the Transaction Processor subsystem with a standard responses from a REST transaction. The processor shall execute the following validations:

1. Model Validation: The message can be parsed

2. Data Validation: The elements have valid values and are in the expected type and format

3. Validation Rules: The values pass any additional validation rules detailed in the definitions below

HTTP 200 – OK: Returned to the Data Collection subsystem when the message passes all validations.

HTTP 400 – Bad Request: Returned to the Data Collection subsystem when the message fails one or more validations types listed above. A failure message accompanies all HTTP 400 responses, containing validation details as specified in the Mileage Message Failure section below.

2.1.3 Interface Requirements and Security

The mileage message is a means of transmitting mileage data from the Data Collection subsystem to the Transaction Processor subsystem.

Application Layer: HTTP over TLS/SSL Transport Layer: TCP Internet Layer: IP Web-services protocol: REST Message definition: JSON

The REST endpoint is the URL of the Transaction Processor subsystem server provided by the business partner.

2.1.4 Communication Methods

Road Usage Charge Program 12

Any communications method that can employ the protocols specified above is appropriate. For example, Wi-Fi, 3G, 4G, and fixed-line Internet are all appropriate communication methods.

2.1.5 Interface Initiation

The mileage message is a push message from the Data Collection subsystem to the Transaction Processor subsystem. The Transaction Processor subsystem accepts the message at all times, whenever the Data Collection subsystem transmits it.

The message is sent by the Data Collection subsystem at an interval programmed into the Data Collection subsystem, as specified in the PRD.

Mileage Message Overview

13 Oregon Department of Transportation

2.2 Mileage Message Overview

The mileage message is sent from the Data Collection subsystem to the Transaction Processor subsystem. It is independent of communication channel, and specific hardware or software.

The mileage message shall contain a record of the start and end times of a period, list all the Rule IDs in which travel was recorded.

2.2.1 Mileage Message JSON Structure

MileageMessage {

VIN

MsgID

MsgType

TransmittedTimestamp

FuelUseMethod

MROID

MROIssuer MROManufacturer

MROConfigVersion {

HWModel HWMainRelease

HWSubRelease

SWMainRelease

SWSubRelease

MapMainRelease

MapSubRelease

The following block of code is the mileage reporting period record. For each mileage message, include a record for each full reporting period collected by the Data Collection component not yet transferred to the Transactions Processing component. All full reporting periods shall be included, even if miles driven are 0 (zero).

MileageDetails [ {

ReportingPeriodStart ReportingPeriodEnd TotalMilesInPeriod

AccumMilesInPeriod

FuelUsageInPeriod

FuelAddedInPeriod

The following block of code is the mileage Rule record. For each reporting period, include one instance of this block for each Rule ID in which the vehicle has traveled.

Road Usage Charge Program 14

{MileageRuleDetails [ {

RuleID MsgMileageInRuleID

MsgFuelUsageInRuleID MsgFuelAddedInRuleID

The following block of code is the mileage SubRule record. For each reporting period, include one instance of this block for each SubRule ID in which the vehicle has traveled.

MileageSubRuleDetails [ {

SubRuleID

MsgMileageInSubRuleID

MsgFuelUsageInSubRuleID MsgFuelAddedInSubRuleID

The following block of code is the MRO Health error code for each error that occurs during a mileage reporting period record.

MROHealthDetails [ {

MROHealth

MROHealthTimestamp

15 Oregon Department of Transportation

2.2.2 Mileage Message Definitions

Data Element Meaning Mileage Message • Required

• Description: Segment name

• Does not repeat

VIN • Required

• Description: The VIN of the vehicle reporting information through the MRO is installed

• Data Type: String

• Format: VARCHAR (20)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

MsgID

• Required

• Description: Message identification number for sequencing of mileage messages

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

MsgType • Required

• Description: A value to indicate the type of message from the MRO

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values:

o 1 = Normal message o 2 = First Message from vehicle o 3 = Last Message from vehicle

• Conditional Rules: N/A

• Validation Rules: Must be valid value from list above.

Road Usage Charge Program 16

Data Element Meaning TransmittedTimestamp • Required

• Description: Timestamp of when the mileage collection subsystem sent the mileage message to the transaction processor.

• Data Type: String

• Format: The date / time is specified in the following form "YYYY-MM-DDT hh:mm:ss" where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

• Values: N/A

• Conditional Rules: UTC

FuelUseMethod • Required

• Description: A value indicating which fuel consumption method is used to calculate fuel usage

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values:

o 1 = Actual fuel use expected but not captured, calculated by using

EPA

o 2 = Actual fuel use captured and used for calculation o 3 = Fuel use calculated by using

EPA

o 4 = Fuel not taxable

• Conditional Rules: N/A

• Validation Rules: Must be valid value from list above.

MROID • Required

• Description: Unique identifier for MRO (such as serial number)

• Data Type: String

• Format: VARCHAR(64)

• Calculation: N/A

• Values: N/A

17 Oregon Department of Transportation

Data Element Meaning MROIssuer • Required

• Description: Name of entity issuing MRO

• Data Type: String

• Format: VARCHAR(50)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

MROManufacturer • Required

• Description: Name of MRO Manufacturer

• Data Type: String

• Format: VARCHAR(50)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

MROConfigVersion • Required

• Description: Segment name

• Does not repeat

HWModel • Required

• Description: HW Model number

• Data Type: String

• Format: VARCHAR(15)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

HWMainRelease • Required

• Description: HW primary release number

• Data Type: String

• Format: VARCHAR(15)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

HWSubRelease • Required

• Description: HW secondary release number

• Data Type: String

• Format: VARCHAR(15)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

SWMainRelease • Required

• Description: SW primary release number

• Data Type: String

• Format: VARCHAR(10)

• Calculation: N/A

Road Usage Charge Program 18

Data Element Meaning SWSubRelease • Required

• Description: SW secondary release number

• Data Type: String

• Format: VARCHAR(10)

• Calculation: N/A

• Values: N/A

MapMainRelease

• Description: Map primary release number

• Data Type: String

• Format: VARCHAR(3)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

MapSubRelease • Required

• Description: Map secondary release number

• Data Type: String

• Format: VARCHAR(3)

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

MileageDetails • Required

• Description: Segment name

• Optionally repeats

ReportingPeriodStart • Required

• Description: The start date and time, in

UTC, of the period during which the miles being reported were traveled in.

• Data Type: String

• Format: The date / time is specified in the following form, "YYYY-MM-DDT hh:mm:ss", where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

19 Oregon Department of Transportation

Data Element Meaning ReportingPeriodEnd • Required

• Description: The end date and time, in UTC, of the period during which the miles being reported were traveled in.

• Data Type: String

• Format: The date / time is specified in the following form, “YYYY-MM-DDT hh:mm:ss”, where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

TotalMilesInPeriod • Required

• Description: Total Miles Reported for the

VIN/MRO for a given reporting period.

• Data Type: Number

• Format: One decimal place - Miles to nearest tenth of a mile [0,0.1,0.2…10,000,000.0]

• Calculation: Must reconcile with the following:

SUM of “MsgMileageInSubRuleID” for all SubRule IDs in reporting period

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must be equal to the sum of “MsgMileageInRuleID” for all RuleIDs

AccumMilesInPeriod • Required

• Description: Cumulative miles of the MRO since activated to report for the VIN

• Data Type: Number

• Format: One decimal place - Miles to nearest tenth of a mile [0,0.1,0.2…10,000,000.0]

• Calculation: N/A

• Values: N/A

• Conditional Rules: If no miles accumulated, set this field value to 0 (zero).

Road Usage Charge Program 20

Data Element Meaning FuelUsageInPeriod • Required

• Description: Accumulated fuel usage during the reporting period for the

VIN/MRO

• Data Type: Number

• Format: Two decimal places - Gallons to hundredth of a gallon [0.01, 0.02, 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “MsgFuelUsageInSubRuleID” for all SubRule IDs in reporting period

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must be equal to the sum of “MsgFuelUsageInRuleID” for all RuleIDs

FuelAddedInPeriod

• Optional

• Description: The amount of fuel added during a given period for the VIN/MRO

• Data Type: Number

• Format: Gallons to hundredth of a gallon

[0.01, 0.02, 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “MsgFuelAddedinSubRuleID” for all SubRule IDs in reporting period

• Values: N/A

• Conditional Rules: Calculating fuel added to vehicle is not a required functionality at this time – if no data for this field, set field value to blank.

• Validation Rules: Must be equal to the sum of “MsgFuelAddedInRuleID” for all RuleIDs

MileageRuleDetails • Required

• Description: Segment name

• Optionally repeats

21 Oregon Department of Transportation

Data Element Meaning RuleID • Required

• Description: An identifier associated with a geographic area in which a specific rate per mile will be assessed for miles traveled. FIPS codes are used to identify states.

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values: Rule ID codes and definitions are defined in the Administrator provided RUC Rate Table

• Conditional Rules: N/A

• Validation Rules: Must be a valid RuleID from RUC Rate Table.

MsgMileageInRuleID • Required

• Description: Miles Traveled in given VIN/MRO Rule ID in the given period

• Data Type: Number

• Format: Miles to nearest tenth of a mile

[0,0.1,0.2,10,000.0]

• Calculation: Sum of

“MsgMileageInSubRuleID” for all SubRuleIDs within the given RuleID, for the given period, for the VIN/MRO.

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“MsgMileageSubRuleID” for all the SubRuleIDs for the given RuleID

MsgFuelUsageInRuleID • Required

• Description: Amount of fuel consumed based on Fuel Use Method in given VIN/MRO Rule ID in the given period.

• Data Type: Number

• Format: Gallons to hundredth of a gallon

[0.01, 0.02, 99,999,999.99]

• Calculation: Sum of

“MsgFuelUsageSubRuleID” for all SubRuleIDs within the given RuleID, for the given period, for the VIN/MRO.

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“MsgFuelUsageSubRuleID” for all the SubRuleIDs for the given RuleID

Road Usage Charge Program 22

Data Element Meaning MsgFuelAddedInRuleID • Optional

• Description: Amount of fuel added in given VIN/MRO Rule ID in the given period.

• Data Type: Number

• Format: Gallons to hundredth of a gallon

[0.01, 0.02, 99,999,999.99]

• Calculation: Sum of

“MsgFuelAddedSubRuleID” for all SubRuleIDs within the given RuleID, for the given period, for the VIN/MRO.

• Values: N/A

• Conditional Rules: Calculating fuel added to vehicle is not a required functionality at this time – if no data for this field, set field value to blank.

• Validation Rules: Must equal the sum of “MsgFuelAddedSubRuleID” for all the SubRuleIDs for the given RuleID

MileageSubRuleDetails • Required

• Description: Segment name

• Optionally repeats

SubRuleID • Required

• Description: Numerical index for region of travel within given Rule ID.

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values: Assigned by The Administrator as necessary, provided in RUC Rate Table

• Conditional Rules: N/A

• Validation Rules: Must be a valid

SubRuleID for given RuleID from RUC Rate Table.

MsgMileageInSubRuleID

• Description: Miles Traveled in VIN/MRO

Sub Rule ID in the given period

• Data Type: Number

• Format: Miles to nearest tenth of a mile

[0,0.1,0.2, 10,000.0]

• Calculation: N/A

23 Oregon Department of Transportation

Data Element Meaning MsgFuelUsageInSubRuleID • Required

• Description: Amount of fuel consumed based on Fuel Use Method in given VIN/MRO Sub Rule ID in the given period.

• Data Type: Number

• Format: Gallons to hundredth of a gallon

[0.01, 0.02, 99,999,999.99]

• Calculation: N/A

• Values: N/A

MsgFuelAddedInSubRuleID

• Optional

• Description: The amount of fuel added in given VIN/MRO Sub Rule ID in the given period.

• Data Type: Number

• Format: Two decimal places - Gallons to hundredth of a gallon [0.01, 0.02, 99,999,999.99]

• Calculation: N/A

• Values: N/A

• Conditional Rules: Calculating fuel added to vehicle is not a required functionality at this time – if no data for this field, set field value to blank.

MROHealthDetails • Optional

• Description: Segment name

MROHealth

• Required (if MRO error or event occurs during reporting period)

• Description: Coding of each error and event that occurred for the given MRO during the given period, when the error was detected by the MRO.

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values:

3. Disconnects

4. Reconnects

5. Connected to new vehicle

• Special Rules: N/A

Road Usage Charge Program 24

Data Element Meaning MROHealthTimestamp • Required (if MRO error or event occurs during reporting period)

• Description: Reporting period that an

MRO error or event occurred

• Data Type: String

• Format: The reporting period is specified in the following form "YYYY-MM-DDT hh:mm:ss" where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

• Special Rules: UTC

2.2.3 Mileage Message Failure JSON Structure

Note that the Failure Message shall only be transmitted by the Transaction Processor subsystem if the mileage message fails data validation checks.

{MileageMessageResults

FailureTimestamp MsgID

FailedReportingPeriodStart FailedReportingPeriodEnd MsgFailedCode msgErrorsDetail

25 Oregon Department of Transportation

2.2.4 Mileage Message Failure Definitions

Data Element Meaning MileageMessageResults • Required

• Description: Segment name

• Does not repeat

FailureTimestamp • Required

• Description: Timestamp provided by transmitting entity when message sent

• Data Type: String

• Format: The date/time is specified in the following form

"YYYY-MM-DDT hh:mm:ss" where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

• Values: N/A

• Conditional Rules: When message send fails, the

Timestamp is updated to the current time (in UTC) when the message is resent

MsgID

• Description: Message identification number for sequencing of mileage messages

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

FailedReportingPeriodStart • Required

• Description: The ‘ReportingPeriodStart’ from the mileage message. Used to match message to error.

• Data Type: String

• Format: The date / time is specified in the following form, "YYYY-MM-DDT hh:mm:ss", where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

Road Usage Charge Program 26

Data Element Meaning FailedReportingPeriodEnd • Required

• Description: The ‘ReportingPeriodEnd’ from the mileage message. Used to match message to error.

• Data Type: String

• Format: The date / time is specified in the following form, "YYYY-MM-DDT hh:mm:ss", where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

MsgFailedCode • Required

• Description: A value indicating the reason that the message was not processed.

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values:

1. Failed Authentication

2. Duplicate message (a mileage message with identical MROID and MsgID has already been received)

3. Data Inconsistency (other data consistency check failed)

• Conditional Rules: Additional failure codes will be determined by the Administrator msgErrorsDetail • Optional

• Description: validation errors for the associated VIN

• Data Type: Array

• Format: VARCHAR(100)

• Calculation: N/A

Program Monitoring Overview

27 Oregon Department of Transportation

3 Interface between Account Management subsystem and the Administrator subsystems

3.1 Program Monitoring Overview

The interface between Account Management subsystem and the Administrator subsystem has five defined messages that are used for program monitoring.

1. Mileage and RUC Revenue message: A summary Mileage and RUC Revenue (MRR) message sent to the Administrator on a regularly scheduled basis.

2. VIN Summary message: A summary of all VINs and RUC data managed by Account Managers sent to the Administrator on a regularly scheduled basis.

3. Errors and Events message: A summary of errors and events sent to the Administrator provides exception and/or health codes on travel data collection and validation across the business partner systems. This is used to monitor system performance.

4. Account and VIN Update message: A report of all account attribute changes and status updates regarding participant status in the program sent to the Administrator.

This flow also returns data (from the Administrator subsystem to the Account Management subsystem to indicate enrollment status of the participant(s).)

5. Quarterly Tax Report: A report that combines the three travel data summaries mentioned above into a single report: the Mileage and RUC Revenue message, the VIN Summary message, and the Errors and Events message. This is submitted to the Administrator by a person-initiated interface, submitted through the Administrator’s commercially developed tax revenue management system website.

3.1.1 Data Transfer

Program Monitoring is initiated by the Account Management subsystem, by calling a REST/JSON interface implemented by the Administrator subsystem.

3.1.2 Transactions and Responses

Transactions are comprised of one message moving from the Account Management subsystem Administrator subsystem. Transactions are acknowledged by the Administrator subsystem with a standard responses from a REST transaction. The processor shall execute the following validations:

1. Model Validation: Checks that the message can be parsed as all required fields are present, struction is complete, and the parent level data elements validate against defined format and if defined, have valid values

2. Data Validation: Checks that the data elements have valid value and are in the expected type and format

3. Validation Rules: Checks that the data element values pass any additional validation rules detailed in the definitions below

HTTP 200 – OK: Returned to the Account Management subsystem when the message passes all validations.

HTTP 206 – Partial Content: Returned to the Account Management subsystem when the message passes all the model and data validations, but doesn’t pass one or more of the defined data validations or validation rules for a particular MRO/VIN. In this case, the message is accepted but is considered incomplete as some of the data provided didn’t pass validation.

Note, this response applies only to VIN Level records as are provided in the VIN Summary message, Errors and Events and the Account and VIN Update message. Since the Mielage and

Road Usage Charge Program 28

RUC Revenue message doesn’t report data by VIN, the 206 response doesn’t apply. A partial content message accompanies all HTTP 206 responses, containing validation details. The BP shall investigate and/or resolve errors and resubmit the message to ensure proper processing for account and travel data.

HTTP 400 – Bad Request: Returned to the Account Management subsystem when the message fails the model and/or data validations. A failure message accompanies all HTTP 400 responses, containing validation details. The BP shall investigate and/or resolve errors and resubmit the message to ensure proper processing for account and travel data.

3.1.3 Interface Requirements and Security

This interface is a means of transmitting data from the Account Management subsystem to the Administrator subsystem.

Application Layer: HTTP over TLS/SSL Transport Layer: TCP Internet Layer: IP Web-services protocol: REST Message definition: JSON

Each message has its own endpoint. The URLs will be provided by the Administrator.

3.1.4 Interface Initiation

Each of these message are a push message from the Account Manager subsystem to the Administrator subsystem. The Administrator subsystem accepts the message at all times, whenever the Account Manager subsystem transmits it.

Mileage and RUC Revenue Message Overview

29 Oregon Department of Transportation

3.2 Mileage and RUC Revenue Message Overview

The Mileage and RUC Revenue message contains the reported data from recurring periods. It is important that all monitoring reports are based on the data reported during the period and not the date traveled. The business partners are required to ensure all required data is sent, and none are skipped because of date filtering issues. The Mileage and RUC Revenue message shall contain a record of the start and end times of the period, a list of all Rule IDs in which travel was recorded and a list of Road Usage Charge due and fuel tax credit for that travel.

3.2.1 Mileage and RUC Revenue Message JSON Structure

The following lists the totals for the message. All totals are for the period defined.

MileageAndRUCRevenueMessage {

AMID

TransmittedTimestamp PeriodStartDate

PeriodEndDate

The following lists the totals for the message. All totals are for the period defined.

TotalMileage

TotalRevenue

TotalFuelUsage

TotalCalculatedFuelTaxCredit TotalAppliedFuelTaxCredit TotalADJMileage TotalADJRevenue TotalADJFuelUsage TotalADJFuelTaxCredit TotalADJBalance TotalBalance

The following is the Rule ID totals. Include one for each Rule ID in the message.

MRRMRuleDetails [ {

RuleID

TotalMileageInRuleID

TotalADJMileageInRuleID

TotalADJRevenueInRuleID TotalADJFuelUsageInRuleID TotalADJFuelTaxCreditInRuleID

Road Usage Charge Program 30

TotalADJBalanceInRuleID TotalRevenueInRuleID TotalFuelUsageInRuleID TotalCalculatedFuelTaxCreditInRuleID TotalAppliedFuelTaxCreditInRuleID TotalBalanceInRuleID

The following is the Sub Rule ID totals. Include one for each Sub Rule ID in the message. All totals are for the period defined.

MRRMSubRuleDetails { [

SubRuleID

TotalMileageInSubRuleID

RateInSubRuleID TotalADJMileageInSubRuleID

TotalADJRevenueInSubRuleID TotalADJFuelUsageInSubRuleID TotalADJFuelTaxCreditInSubRuleID TotalADJBalanceInSubRuleID TotalRevenueInSubRuleID TotalFuelUsageInSubRuleID FuelRateInSubRuleID TotalCalculatedFuelTaxCreditInSubRuleID TotalAppliedFuelTaxCreditInSubRuleID TotalBalanceInSubRuleID

3.2.2 Mileage and RUC Revenue Message Definitions

Data Element Meaning MileageAndRUCRevenueMessage • Required

• Does not repeat

31 Oregon Department of Transportation

Data Element Meaning AMID • Required

• Description: The account manager identifier number which is provided by the Administrator

• Data Type: Number

• Format: Integer

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

TransmittedTimestamp • Required

• Description: Time and date, in UTC, that the message is sent to the Administrator.

• Data Type: String

• Format: The date / time is specified in the following form "YYYY-MM-DDT hh:mm:ss" where:

o YYYY indicates the year o MM indicates the month o DD indicates the day o T indicates the start of the required time section o hh indicates the hour o mm indicates the minute o ss indicates the second

• Calculation: N/A

• Values: N/A

• Conditional Rules: N/A

PeriodStartDate • Required

• Description: The start date, in UTC, of the reporting period

• Data Type: String

• Format: The date is specified in the following form

"YYYY-MM-DD" where:

o YYYY indicates the year o MM indicates the month o DD indicates the day

• Calculation: N/A

• Values: N/A o Conditional Rules: N/A

PeriodEndDate • Required

• Description: The Reporting period end date, in UTC

• Data Type: String

• Format: The date is specified in the following form

"YYYY-MM-DD" where:

o YYYY indicates the year o MM indicates the month o DD indicates the day

• Calculation: N/A

Road Usage Charge Program 32

TotalMileage • Required

• Description: Total Miles reported for all Rule IDs for given period

• Data Type: Number

• Format: One decimal place - Miles to nearest tenth of a mile [0,0.1,0.2…10,000,000.0]

• Calculation: Must reconcile with the following:

SUM of “TotalMileageInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalMileageInRuleID” for all RuleIDs TotalRevenue • Required

• Description: Total RUC Revenue for all Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalRevenueInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalRevenueInRuleID” for all RuleIDs TotalFuelUsage • Required

• Description: Total fuel usage reported for all Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Gallons to hundredth of a gallon: [0.01, 0.02, 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalFuelUsageInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalFuelUsageInRuleID” for all RuleIDs TotalCalculatedFuelTaxCredit • Required

• Description: Total Calculated Fuel Tax Credit for all Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01,

0.02 … 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalCalculatedFuelTaxCreditInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalCalculatedFuelTaxCreditInRuleID” for all RuleIDs

33 Oregon Department of Transportation

TotalAppliedFuelTaxCredit • Required

• Description: Total Applied Fuel Tax Credit for all Rule

IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01,

0.02 … 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalAppliedFuelTaxCreditInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalAppliedFuelTaxCreditInRuleID” for all RuleIDs TotalADJMileage • Required

• Description: Total adjusted miles reported for all Rule IDs for given period

• Data Type: Number

• Format: One decimal place - Miles to nearest tenth of a mile [0,0.1,0.2…10,000,000.0]

• Calculation: Must reconcile with the following:

SUM of “TotalADJMileageInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalADJMileageInRuleID” for all RuleIDs TotalADJRevenue • Required

• Description: Total adjusted RUC revenue for all Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJRevenueInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalADJRevenueInRuleID” for all RuleIDs

Road Usage Charge Program 34

TotalADJFuelUsage • Required

• Description: Total adjusted fuel usage reported for all

Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Gallons to hundredth of a gallon [0.01, 0.02, 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJFuelUsageInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalADJFuelUsageInRuleID” for all RuleIDs TotalADJFuelTaxCredit • Required

• Description: Total adjusted Fuel Tax Credit for all Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJFuelTaxCreditInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalADJFuelTaxCreditInRuleID” for all RuleIDs TotalADJBalance • Required

• Description: Total adjusted Balance for all Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJBalanceInRuleID” for all Rule IDs

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalADJBalanceInRuleID” for all RuleIDs

35 Oregon Department of Transportation

TotalBalance • Required

• Description: Total Amount to invoice to the participant for all Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalBalanceInRuleID” for all Rule IDs in reporting period

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

“TotalBalanceInRuleID” for all RuleIDs MRRMRuleDetails • Required

• Description: Segment

• Optionally repeats

RuleID • Required

• Description: Rule Identification. An identifier associated with a geographic area, in which a specific rate per mile will be assessed for miles traveled. FIPS codes are used to identify states

• Data Type: Number

• Format: Integer

• Values: Rule ID codes and definitions are defined in the Administrator provided RUC Rate Table

• Conditional Rules: N/A

• Validation Rules: must be a valid RuleID in the RUC

Rate Table.

TotalMileageInRuleID • Required

• Description: Total Miles reported in given Rule ID for given period

• Data Type: Number

• Format: One decimal place - Miles to nearest tenth of a mile [0,0.1,0.2…10,000,000.0]

• Calculation: Must reconcile with the following:

SUM of “TotalMileageInSubRuleID” for all Sub Rule IDs in Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalMileageInSubRuleID for each SubRuleID within the given RuleID

Road Usage Charge Program 36

TotalADJMileageInRuleID • Required

• Description: Total adjusted miles reported in Rule ID for given period

• Data Type: Number

• Format: One decimal place - Miles to nearest tenth of a mile [0,0.1,0.2…10,000,000.0]

• Calculation: Must reconcile with the following:

SUM of “TotalADJMileageInSubRuleID” for all Sub Rule IDs in given Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalADJMileageInSubRuleID for all SubRuleIDs within the given RuleID

TotalADJRevenueInRuleID • Required

• Description: Total adjusted RUC revenue in Rule ID for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJRevenueInSubRuleID” for all Sub Rule IDs in given Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalADJRevenueInSubRuleID for all SubRuleIDs within the given RuleID

TotalADJFuelUsageInRuleID • Required

• Description: Total adjusted fuel usage reported in Rule

ID for given period

• Data Type: Number

• Format: Two decimal places - Gallons to hundredth of a gallon [0.01, 0.02, 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJFuelUsageInSubRuleID” for all Sub Rule IDs in given Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalADJFuelUsageInSubRuleID for all SubRuleIDs within the given RuleID

37 Oregon Department of Transportation

TotalADJFuelTaxCreditInRuleID • Required

• Description: Total adjusted Fuel Tax Credit in Rule ID for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJFuelTaxCreditInSubRuleID” for all Sub Rule IDs in given Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalADJFuelTaxCreditInSubRuleID for all SubRuleIDs within the given RuleID

TotalADJBalanceInRuleID • Required

• Description: Total adjusted Balance in Rule ID for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalADJBalanceInSubRuleID” for all Sub Rule IDs in given Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalADJBalanceInSubRuleID for all SubRuleIDs within the given RuleID

TotalRevenueInRuleID • Required

• Description: Total RUC Revenue in all taxable Sub

Rule IDs for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01, 0.02, … , 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “MRORevenueInSubRuleID” for all taxable Sub Rule IDs in given Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalRevenueInSubRuleID for all SubRuleIDs within

Road Usage Charge Program 38

TotalFuelUsageInRuleID • Required

• Description: Total fuel usage reported in given Rule ID for given period

• Data Type: Number

• Format: Two decimal places - Gallons to hundredth of a gallon: [0.01, 0.02, 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalFuelUsageInSubRuleID” for all Sub Rule IDs in Rule ID

• Values: N/A

• Conditional Rules: N/A

• Validation Rules: Must equal the sum of

TotalFuelUsageInSubRuleID for all SubRuleIDs within the given RuleID

TotalCalculatedFuelTaxCreditInR uleID

• Required

• Description: Total Calculated Fuel Tax Credit in all taxable Sub Rule IDs in given Rule ID for given period

• Data Type: Number

• Format: Two decimal places - Dollars and cents: [0.01,

0.02 … 99,999,999.99]

• Calculation: Must reconcile with the following:

SUM of “TotalCalculatedFuelTaxCreditInSubRuleID” for all Sub Rule IDs in Rule ID

• Values: N/A

• Conditional…