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 on each title and registration transaction. “Comments” 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 office to place or remove a hold on a Collector’s registration record but cannot remove another county’s hold. MDOR must have the capability to add or remove any hold.
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.
3830rfp.docx