Oklahoma DPS Desperately Seeking Automated Enforcement

Nov. 28, 2009

Shedding some light on the recent news about automated enforcement of mandatory insurance law

link

 

October 16, 2009
To: All Interested Vendors
Re: Request for Information
The State of Oklahoma, Department of Public Safety, is requesting information regarding a system of automated enforcement of vehicle insurance

Project Description
DPS envisions a system of automated enforcement of vehicle insurance which incorporates, at a minimum, the following processes:
• capture vehicle license plate data from stationary locations along selected highways using: cameras
barcode scanners. Oklahoma’s new license plates include a barcode. All license plates will be replaced with the new license plate by December 31, 2009. It should be noted that some license plate mounts or surrounds obscure, partially or in whole, the barcode.
• other technology proposed by the responder

The Department of Public Safety (DPS) has developed, created, and currently administers, in cooperation with insurance carriers licensed to sell personal lines vehicle insurance in Oklahoma, a dynamic system for verification of vehicle insurance by motor license agents of the Oklahoma Tax Commission (OTC) at the time of vehicle registration, law enforcement when making a roadside vehicle stop, and courts when allowing a person to provide proof of the existence of vehicle insurance on the date a citation was written for no insurance.

The current system is called the Oklahoma Compulsory Insurance Verification System (OCIVS).
Obviously, this type of enforcement of vehicle insurance laws, by its natures, is limited to personal contact with the individual. DPS is now interested in expanding the verification process to include a system of automated enforcement of vehicle insurance that will encompass a larger target group without expending manpower.

 

  • use the captured data to obtain registration data from OTC. Basically, the license plate number would be used to obtain the VIN and the owner’s name and address from OTC. The VIN is necessary for the insurance verification process.
  • use the VIN to inquire against OCIVS to verify whether vehicle insurance exists for the vehicle. OCIVS would reply to the inquiry with a “Confirmed” or “Unconfirmed” response.
  • In some cases, the insurance company would provide a reason along with an “Unconfirmed” response notification to the owner of a vehicle for which an “Unconfirmed” response is received. The notification would be by first-class mail to the owner’s address provided by OTC. T

The notification would include:

  • • vehicle information
  • • the date and time insurance was unable to be confirmed for the vehicle
  • • a statement of violation of state law, including the statutory citation
  • • a fine or administrative penalty (to be determined later) to be paid by the owner as directed on the notification
  • • a statement of the consequences of failure to pay (to be determined later)
  • • record keeping that would provide DPS with daily statistics and related data on vehicles:
  • • for which license plate data was captured
  • • for which registration data was obtained from OTC
  • • for which insurance verification inquiries were made, and the results of those inquiries
  • • for which notification was mailed to the owner

This system would be limited to vehicles covered by personal lines vehicle insurance policies; vehicles covered by commercial policies are not part of OCIVS and therefore would be exempt from this system. While this system of automated enforcement of vehicle insurance only considers application to
vehicles registered in Oklahoma with inquiries against OCIVS, responses which include vehicles registered in any or all other states will be considered. It will be each responder’s responsibility to determine how to access registration and insurance information from a state other than Oklahoma.

RFI Response Instructions
The State is asking all interested parties to submit a response containing the following information:
• Your interest in providing the services/supplies.
• A brief description of past experience providing similar services/supplies.

• Your opinion, based on your past experience, on whether the State has identified all the major components necessary to complete this project? If not, please provide information on other necessary components.
• A list of potential problems/risks that the State may encounter during this project, and any ideas or suggestions about how such problems/risks should be addressed in a solicitation.
• Your best estimated information on how each process would be accomplished, including specific methodology, software, hardware, connectivity, security, etc., and the estimated time frame in which each process would be accomplished.
• Your best estimated time frame for completing the project.
• The State of Oklahoma and DPS would not provide any funding for this system; all costs would be the responsibility of the successful bidder, should the system be bid and awarded.
The method of payment to the successful bidder would be reimbursement from funds received from fines or administrative penalties. With this in mind, please provide an estimate of income your company would find necessary and sufficient to provide the services/supplies required to implement, administer and support this system. This estimate should be given in monthly increments.

See Document;

http://www.dps.state.ok.us/…/RFI%20automated%20insurance%20enforcement%20OKLAHOMA.pdf

About these ads

One response to “Oklahoma DPS Desperately Seeking Automated Enforcement

  1. Pingback: Bar Codes on our License Plates?! « Radio Free Oklahoma Blog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s