Number of Titles Issued 915,404 Number of Dealer Permits Issued 3,803 Number of Dealer Tags Issued 7,641 Number of Temporary and In-transit Tags 35,818 Number of County Tax Collector Offices 109 Number of District Offices 8 Annual Motor Vehicle Revenue $125,452,641 Annual Title Revenue $10,037,529 License Plate Types Currently license plates for vehicles under 10,000 pounds are issued in all 109 county tax collector’s offices. Certain plates are issued from the central location. The county tax collector’s offices issue county designated plates from their inventory. The county currently stocks approximately 16 different types of plates in their inventory. The plate manufacturer will mail the specialty and personalized plates directly to the customer from the plate manufacturer. Currently, we have 185 specialty plates in service as of June 30, 2015. License Plated Issued by each County Office County Code County Name Plates and Decals Issued Fiscal Year Ending June 30, 2014 01 Adams 29,725 02 Alcorn 33,605 03 Amite 16,224 04 Attala 19,183 05 Benton 8,361 06 Bolivar 26,777 07 Calhoun 16,945
The system must be able to support inquiries using the short VIN (last 6 characters of VIN) or any combination of the VIN. The system must notify the user if the VIN entered matches a VIN in the system. Furthermore, the system must validate VIN against any file of valid VINs provided by the vehicle manufacturers. The system must provide the ability to capture buyer and seller information for vehicle(s) transferred. The system must prepopulate the registration period based on defined business rules. The system must support multiple types of plates including, but not limited to standard passenger, truck, trailer, bus, and motorcycle plates. The system must provide the ability to have different renewal cycles for different plate types. The system must be able to determine which plate configurations and types of plates can be used on specific vehicle types. The system must provide the ability to easily add new license plate types and series into the system. The system must provide the ability to have configurable supporting documentation requirements that must be submitted/satisfied prior to completing the application transactions. The documents required for a title and registration transaction must be configurable within the system based on defined business rules. The system must allow transactions to be reversed and/or deleted based on user access rights. The system must maintain a history of corrected or canceled transactions. The system must support the ability to record and read “Comments” on each title and registration transaction. The system must provide the ability to disallow certain transactions based on a hold placed by defined business rules and user access rights. The system must provide the ability for each County Tax Collector’s office to place or remove a hold on a registration record but cannot remove another county’s hold. MDOR must have the capability to add or remove any hold.
All training materials and documentation are considered deliverables and must be submitted to the State with adequate time for the State to review and approve all such material prior to the beginning of the actual training. The State must be allowed to reproduce and/or edit, as needed and without incurring any additional cost, any training material provided, including electronic or printed form. This reproduction of training materials will be for the sole purpose of this project. The State will determine when training is sufficient for successful systems operations based on staff’s ability to operate the system following User Acceptance Test (UAT) systems training. If, after initial training session is completed, the State and Vendor determine that additional training is needed, the Vendor will be required to provide such additional training at no additional cost to the State. If there are system changes, upgrades, enhancements, or new releases to the software that require additional training, Vendor must provide the additional training needed for the successful operation of the software. At the request of the State, Vendor must provide additional training sessions. The cost for such additional sessions should be outlined as an hourly rate and a per session rate in the Section VIII, Cost Information Submission. Vendor must include in the proposal a description of the training provided new releases or upgrades to the system. Vendor must provide “end-user” and technical documentation on each module of the proposed solution. Additional Requirements ITS acknowledges that the specifications within this RFP are not exhaustive. Rather, they reflect the known requirements that must be met by the proposed system. Vendors must specify, here, what additional components may be needed and are proposed in order to complete each configuration. The Vendor must escrow the proposed solution. The Vendor must sign on to the ITS/NCC Group Three Party Escrow Agreement and maintain a current copy of the data dictionary, Documentation, object code, and source code in escrow. The escrow agreement shall authorize the NCC Group to release, at no cost to DOR, the data dictionary, Documentation, object code, and source code to DOR if and when DOR is deemed to have a right. DOR shall pay all costs of providing and maintaining the escrow agreement, including the fees of the NCC Group. Please refer to Article 49, Escrow of Source Code in Exhibit A, Standard