35077 Attachment F_Verification Cross Reference Index~1.xlsx

CAM

BP shall provide proof of financial stability. This proof shall consist of a Dun & Bradstreet Rating (or equivalent) Classification of 1A or higher, and a Composite Credit Rating of “Good (2)” or “High (1)”.

The applicable data retention statutes will be provided by the Administrator.

Example: Compliance with Payment Card Industry Data Security Standards (PCI-DSS) is required for credit and debit card transactions.

SS.PP.2 The BP shall provide its information security policy for how payment security is addressed in these areas:

• Firewalls to protect financial data

• Protection for stored financial data

• Restrictions to financial data, physical or otherwise

• Tracking of access to financial data

• Regularly testing security systems and processes

The system shall include mechanisms for detection and notification about potential and realized viral and malware threats.

Level 3 data is any sensitive information intended for limited business use that may be exempt from public disclosure because such disclosure may jeopardize the privacy or security of individuals. Personally Identifiable Information (PII) qualifies as Level 3 data.

a) Social Security Number Validation

b) State Criminal Background Check (encompassing the past 7 years)

c) Federal Criminal Background Check (encompassing the past 7 years)

d) State & National Sex Offender Registry

e) State Records Locator If a U.S. based background check is unavailable, an equivalent background check format shall be provided to the Administrator for review and approval.

Access to daily metered use and location information will be restricted for the Administrator based upon limitations set forth in ORS 319.915.

BPP.6 The BP or any entity working with the BP shall not disclose personally identifiable information used or developed for reporting travel data by an enrolled vehicle, or for administrative services related to the collection of per-mile road usage charges to any person except:

• The registered vehicle owner or lessee;

• A financial institution, for the purpose of collecting per-mile road usage charges owed;

• Employees of the Administrator;

• An Administrator approved BP (e.g. certified service provider);

• A contractor for a certified BP, but only to the extent the contractor provides services directly related to the certified BP’s agreement with the Administrator;

• An entity expressly approved by the registered owner or lessee of the subject vehicle to receive the information; or

• A police officer pursuant to a valid court order based on probable cause and issued at the request of a federal, state or local law enforcement agency in an authorized criminal investigation involving a person to whom the requested information pertains.

• AMID – Business Partner Identification Number, to be assigned by the Administrator (as defined in the ICD)

• CertID – Certification Identification Number, to be assigned by the Administrator for each MRO certified for RUC mileage collection (as defined in the ICD)

• Request consent for this separate set of terms and conditions

• Request the consent as its own approval step PPM.PIA.4 If the BP requests the participant to expressly approve an entity to receive their PII, then the BP shall:

• Request this express approval as a separate step

• Provide this express approval request as a unique agreement with separate terms and conditions.

Note: The definition of PII can be found in ORS 319.915[3][a][F].

PPM.PIA.5 The BP shall capture and retain the electronic signatures and agreement information for all required agreements, and provide to the Administrator upon request.

Examples:

• Agreement to Terms and Conditions including the Participant Agreement

• Agreement to Participant PII disclosure, if expressly approved

• Agreement to BP retention of location based and daily metered use data, if consented to.

a) Participant Name and VIN

b) Participant Agreement Date/Time Stamp, at time of application submission

c) Participant Program Application

d) Participant Electronic Authorization (eSignature)

e) Version and content of Participant Agreement

f) Version and content of any other Terms & Conditions to which the participant consented at the time of application submission.

This information shall be provided through standard document and information formats (including pdf, MS Excel, MS Word and CSV) as specified by the Administrator.

See “MROConfigVersion” code block in section 2.2 and 3.10.1 of the Interface Control Document (ICD) for details.

The BP shall use the EPA fuel economy data (published at www.fueleconomy.gov) to determine the EPA combined MPG value for the vehicle. If the combined MPG value is not published by the EPA, the BP shall use the best available source to determine MPG. The BP shall determine MPG based on the following logic:

• If the vehicle is powered by gas, diesel or compressed natural gas (CNG), or is a standard hybrid, use the rounded combined MPG value

• If the vehicle is fully electric-powered or uses tax-exempt fuel, no MPG rating is to be used

• Remaining vehicles are plug-in hybrids, use the rounded combined MPGe (PHEVComb) value.

If the BP is unable to identify a value that meets the requirement, the BP must contact the Administrator for assistance.

PPM.PA.14 The Account Manager shall deliver an email upon receipt of the enrollment application submission containing the following information:

• Statement regarding conditional approval into the OReGO program

• Enrollment Application Date (the date the application was submitted)

• Applicant First and Last Name

• Enrolled Vehicle VIN

Example: If the BP is notified that the MRO has been lost, the BP shall be able to deactivate the MRO without discontinuing the vehicle on the participant's account.

See the RUC Rate Table in Appendix C.

FuelUseMethod as described in the ICD:

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

• 2 = Actual fuel use captured and used for calculation

• 3 = Fuel use calculated by using EPA

• 4 = Fuel not taxable

For FuelUseMethod value 1 or 3, use this for the fuel usage calculation:

Count of Miles / EPA combined MGP Rating = Fuel Usage

• Communications address of the Transaction Processor subsystem

• Data Storage period

• Rule ID/SubRule ID mapping

Disconnect The DC has received information from the MRO, directly or indirectly, that indicates the MRO is not able to send data to the DC. This is to communicate the discovery by the DC that an MRO cannot report required data.

DC.HEE.3 The Data Collection subsystem shall store and transmit any Reconnect events with MRO Health Code 4 to the Transaction Processor subsystem via the mileage message, and associate any such events with the applicable vehicle and MRO ID.

Reconnect After receiving a disconnect event (defined above), the DC received information, directly or indirectly, that indicates the MRO has re-established the ability to report data to the DC. All Reconnect events must be preceded by a Disconnect event. This is to communicate the resolution of the disconnect event.

DC.HEE.4 The Data Collection subsystem shall store and transmit any reporting for New Vehicle Health Code 5 to the Transaction Processor subsystem via the mileage message, and associate any such events with the applicable vehicle and MRO ID.

New Vehicle The DC received the first indication, directly or indirectly, from the MRO that data is being collected and sent to the DC. This is the activation of the MRO, or the first mileage message received with an MROStatus of 1 (activated).

These validations failures shall be reported as Error Event Codes 100-107 in the ICD.

Total taxable miles x RUC Rate = Road Usage Charge

FuelUseMethod as described in the ICD:

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

• 2 = Actual fuel use captured and used for calculation

• 3 = Fuel use calculated by using EPA

• 4 = Fuel not taxable

For FuelUseMethod value 1 or 3, use this for the fuel usage calculation:

Count of Miles / EPA MGP Rating = Fuel Usage TP.C.6 The Transaction Processor subsystem shall calculate the Fuel Tax Credit using the RUC Rate Table and applicable Rule ID/SubRule ID logic provided by the respective participating administrator.

Fuel Usage x Fuel Tax Rate = Fuel Tax Credit Amount TP.C.7 The contractor shall accurately calculate the Net RUC Balance:

Count of Taxable Miles x RUC Rate = RUC (A) Total Taxable Gallons of Fuel Used x Fuel Tax Rate = Fuels Tax Credit (B) Where A + B = Net RUC Balance (C) [with exception, see below] Definitions A: Owed Road Usage Charge Amount B: Fuels Tax Credit Amount (always a credit [negative number]) C: Net Road Usage Charge Balance

The Net Road Usage Charge Balance calculation is:

A + B = C unless C is negative (meaning a credit or refund), then C = zero.

If the Net RUC Balance is less than zero, the Transaction Processing subsystem shall adjust the Net RUC balance to zero.

• Miles Traveled 0.00 Nearest 1/100 of a mile

• Fuel Usage 0.00 Nearest 1/100 of a gallon

• Road Usage Charge $0.00 Nearest whole cent

• Fuel Tax Credit $0.00 Nearest whole cent

• Net RUC Balance $0.00 Nearest whole cent

Account closure is defined as an account with no active vehicles, no account balance, no open disputes or noncompliance investigations.

• AM Customer Number

• Payment Records

• Billing Adjustments to Account

For each vehicle on the account:

• Vehicle Identification Number (VIN)

• License Plate

• Fuel Use Method

• EPA Rating

• Enrollment Status

• VIN Status

• Pilot ID Code

• MRO Type

• MRO Status

• MRO Configured Reporting Period

• MRO ID

• MRO Certification Identification Number “CertID”

• MRO Configuration Version Details

• Rule ID/SubRule ID for which travel data was collected

• Mileage messages, up to data retention limit

• Current RUC Due

• AMID – Business Partner Identification Number

• CertID – Certification Identification Number AM.RD.11 The Account Management subsystem shall store the reports sent to the Administrator. This includes:

• Errors and Events message

• VIN Summary message

• Mileage and RUC Revenue message

• Account and VIN Update message

• VIN Summary message

• Mileage and RUC Revenue message

• Errors and Events message

• Account and VIN Update message

• Quarterly Tax Report

Errors and events subject to this requirement are: DC.HEE.x and TP.HEE.x and includes all those requirements within this naming convention.

• For the amount equal to or greater than $0.005, round up to the nearest whole cent.

• For the amount with less than $0.005, round down to the nearest whole cent Example: $0.0524 would be rounded to $0.05

• Description of the vehicle

• MRO Option

• For each applicable Rule ID/Sub Rule ID, list:

o Taxable Miles o Non-taxable Miles o Amount of RUC o RUC Rate o Fuel usage for taxable miles o Fuel usage for non-taxable miles o Amount of Fuel Tax Credit o Fuel Tax Rate

• Incentives Applied (if applicable)

• Penalties Applied (if applicable)

• Adjustments to the account