Appendix A: VTR Modernization Requirements Traceability Matrix, Request for Proposal 5557 Z1

Instructions/Descriptions of Requirements Columns:

Bidders must complete all eight tables (Vehicle Registration, Vehicle Title, Fees and Taxes, Point of Sale, Inventory Management, Technical, Reporting, Interface Catalog) in Appendix A. If Bidders choose to provide costs for the Optional Licensing and Regulation of Dealerships, the corresponding table (Licensing and Regulation of Dealerships - OPTIONAL) will need to be completed. Bidder must place company name at the top of the first table where indicated.

Requirement #: This column contains the alpha-numeric number assigned to each requirement. Protected to restrict bidder from making changes.

Requirement Description: This column contains a description of the requirement. Protected to restrict bidder from making changes.

Current Environment: This column states whether the requirement addresses a currently existing business or technical function of the Nebraska Department of Motor Vehicles (State DMV) or one that doesn’t exist. Protected to restrict bidder from making changes.

·  Yes: Exists in current system.

·  No: Does not exist in current system.

·  In the Interface Catalog table, "Exists" or "Does Not Exist" replaces "Yes" or "No".

Delivery Method (all tables except Interface Catalog [INT]): Bidder shall select the appropriate response from the drop down menu provided (1, 2, 3, 4). Complete the Delivery Method column with one of the following responses:

·  4 – Base Product: Feature/Function is included in the proposed solution and available standard or "out of the box" and in the current software release.

·  3 – Custom: Feature/Function can be provided in some way. "Other" includes custom modifications, third party software, or another method.

·  2 – Future Release: Feature/Function will be available in the future or in a future release. Provide anticipated delivery date, version, and service release in the Explanation column.

·  1 - Not Proposed: Feature Function has not been proposed by the Bidder. Provide brief description of why this functionality is not proposed in the Explanation column.

Explanation (all tables except Interface Catalog [INT]): For all Delivery Method responses, Bidders must provide a brief explanation of how the proposed system meets this requirement. Free form text can be entered into this column. Bidder must ensure all information appears when printing Appendix A for submission.

Proposed Solution (Interface Catalog [INT] table only): Provide a narrative description of the technology used to construct the interface/data share/file share. Free form text can be entered into this column. Bidder must ensure all information appears when printing Appendix A for submission.

Description (Interface Catalog [INT] table only): Provide any additional narrative necessary to explain how the interface is constructed and a brief explanation of how the proposed system meets this requirement. Free form text can be entered into this column. Bidder must ensure all information appears when printing Appendix A for submission.

Identify Source (Interface Catalog [INT] table only): Identify the source (production or replicated database) for each interface. Free form text can be entered into this column. Bidder must ensure all information appears when printing Appendix A for submission.

Bidder Name: / Click here to enter text.
Vehicle Registration (VR)
Bidder Response Section
Req # / Requirement Description / Current Environment / Delivery Method / Explanation
VR.1 / General
VR.1.1 / The system shall provide the ability to maintain vehicle records such that a vehicle may have multiple owners and an owner may have multiple vehicles. / No / Choose an item. / Click here to enter text.
VR.1.2 / The system shall provide methods to prevent unintentional duplication of transactions (e.g., registration renewal in a specific time period). / No / Choose an item. / Click here to enter text.
VR.1.3 / The system shall have the ability to assign multiple plates and registrations to a single vehicle for the same registration period. (e.g. farm plate and commercial plate for a dual-use vehicle). / Yes / Choose an item. / Click here to enter text.
VR.1.4 / The system shall provide various ways to retrieve vehicle by any of the data fields or combination of data fields listed below, including but not limited to:
VR.1.5 / Owner Name / Yes / Choose an item. / Click here to enter text.
VR.1.6 / VIN / Yes / Choose an item. / Click here to enter text.
VR.1.7 / Plate Number / Yes / Choose an item. / Click here to enter text.
VR.1.8 / Historical Plate Number / No / Choose an item. / Click here to enter text.
VR.1.9 / Current Decal Number / No / Choose an item. / Click here to enter text.
VR.1.10 / Make, Model, Year of Vehicle / No / Choose an item. / Click here to enter text.
VR.1.11 / Title Number / Yes / Choose an item. / Click here to enter text.
VR.1.12 / Registration Number / Yes / Choose an item. / Click here to enter text.
VR.1.13 / In-Transit Number (Temporary Tag) / No / Choose an item. / Click here to enter text.
VR.1.14 / Permit Number / No / Choose an item. / Click here to enter text.
VR.1.15 / Driver’s License Number / No / Choose an item. / Click here to enter text.
VR.1.16 / SSN or EIN / No / Choose an item. / Click here to enter text.
VR.1.17 / County of issue / No / Choose an item. / Click here to enter text.
VR.1.18 / County of situs / No / Choose an item. / Click here to enter text.
VR.1.19 / The system shall provide the ability to validate an address against an external source of data (e.g., Experian QAS). / No / Choose an item. / Click here to enter text.
VR.1.20 / The system shall provide the functionality to link multiple lessees to a vehicle. / Yes / Choose an item. / Click here to enter text.
VR.1.21 / The system shall prohibit, via business rules, a lessee and a lessor being the same entity. / No / Choose an item. / Click here to enter text.
VR.1.22 / The system shall capture and track all required vehicle registration information based on the business rules defining the vehicle registration record. / Yes / Choose an item. / Click here to enter text.
VR.1.23 / The system shall have the ability to establish multi-year registration periods based on business rules. / Yes / Choose an item. / Click here to enter text.
VR.1.24 / The system shall have the ability to create a partial-year registration or user-defined period of registration. / Yes / Choose an item. / Click here to enter text.
VR.1.25 / The system shall allow authorized users to create user-defined registration statuses (e.g., "valid", "expired", "suspended", "inactive", "canceled"). / No / Choose an item. / Click here to enter text.
VR.1.26 / The system shall have the ability to assign a DMV-defined status to a registration. / Yes / Choose an item. / Click here to enter text.
VR.1.27 / The system shall have the ability to exempt a vehicle from registration based on business rules (as described in the Current Environment Report Section 3.3.4, vehicles eligible for permits are exempt from registration). / Yes / Choose an item. / Click here to enter text.
VR.1.28 / The system shall be able to record a period of non-operation of a vehicle. / No / Choose an item. / Click here to enter text.
VR.1.29 / The system shall have the capability to register untitled vehicles. / Yes / Choose an item. / Click here to enter text.
VR.1.30 / The system shall have the capability to assign a system generated, unique identifier to untitled trailers. / No / Choose an item. / Click here to enter text.
VR.1.31 / The system shall have the ability to conduct registration transactions via an electronic, customer facing mechanism. (e.g. registration renewal, address change, request duplicate, create temp tag). / No / Choose an item. / Click here to enter text.
VR.1.32 / The system shall have the ability to electronically update status of previous registration upon transfer of title. / No / Choose an item. / Click here to enter text.
VR.1.33 / The system shall have the ability to record odometer values at user defined timeframes. / No / Choose an item. / Click here to enter text.
VR.1.34 / The system shall be able to place transactions on “hold” to suspend processing, or assign the transaction to another user. All data and notes about the transaction will be retained in the transaction record. The transaction may be retrieved and completed at a later time. / No / Choose an item. / Click here to enter text.
VR.1.35 / The system shall enable the authorized user to make required changes to the registration record. / Yes / Choose an item. / Click here to enter text.
VR.1.36 / The system shall maintain a historical record of the changes to include who performed the transaction, when the transaction was performed and where the transaction occurred. / Yes / Choose an item. / Click here to enter text.
VR.1.37 / The system shall be able to recognize whether a vehicle requires registration and which type it is eligible for, based on business rules. / No / Choose an item. / Click here to enter text.
VR.1.38 / The system shall be able to recognize whether a vehicle is currently titled when a new registration transaction is initiated. / Yes / Choose an item. / Click here to enter text.
VR.1.39 / The system shall be able to create a new registration using the information from the vehicle’s title record. / Yes / Choose an item. / Click here to enter text.
VR.1.40 / The system shall have the ability to register a vehicle in any county, not restricted to where the vehicle has situs. / No / Choose an item. / Click here to enter text.
VR.1.41 / Based on business rules, the system shall be able to prevent a vehicle from being registered outside of that vehicle's county of situs. / Yes / Choose an item. / Click here to enter text.
VR.1.42 / The system shall have validation rules to prevent the assignment of an invalid plate type to a vehicle. For example, the system shall prevent a passenger plate from being assigned to a commercial vehicle. / No / Choose an item. / Click here to enter text.
VR.1.43 / The system shall have the ability to calculate a duplicate registration fee according to the business rules. / Yes / Choose an item. / Click here to enter text.
VR.1.44 / The system shall be able to register multi-stage vehicles based upon business rules. / No / Choose an item. / Click here to enter text.
VR.1.45 / The system shall allow electronic registration processing of fleets, rental and lease fleets, auctions, salvage, etc., by third party business partners and their servicing entities. / No / Choose an item. / Click here to enter text.
VR.1.46 / The system shall allow the DMV's title registration policies and rules to be accessible via a help or display function to inform users of the policies and rules regarding vehicle registration requirements. / No / Choose an item. / Click here to enter text.
VR.1.47 / The system shall include registration transfer policies and rules accessible via a help or display function to inform users the policies and rules regarding vehicle transfers. / No / Choose an item. / Click here to enter text.
VR.1.48 / The system shall have the ability to store multiple addresses for same registered owner (e.g. residence, mailing, and domicile). / No / Choose an item. / Click here to enter text.
VR.1.49 / The system shall have the ability to assign system generated, unique registration numbers. (other than a plate/permit number). / No / Choose an item. / Click here to enter text.
VR.2 / Original Registration
VR.2.1 / The system shall allow for the creation of an original (new to Nebraska, or new owner) vehicle registration. / Yes / Choose an item. / Click here to enter text.
VR.2.2 / The system shall generate a registration document or receipt. / Yes / Choose an item. / Click here to enter text.
VR.2.3 / The system shall have the ability to associate proof of financial responsibility to a registration. / Yes / Choose an item. / Click here to enter text.
VR.2.4 / The system shall have a process for registering fleets of vehicles. / No / Choose an item. / Click here to enter text.
VR.2.5 / The system shall have the ability to assign a registration type and associated plate type to a vehicle based on business rules. / No / Choose an item. / Click here to enter text.
VR.2.6 / The system shall be able to create a fleet indicator for a group of registered vehicles owned by the same entity or person. / No / Choose an item. / Click here to enter text.
VR.2.7 / The system shall allow a field for an owner-assigned operator or equipment number for fleet vehicles. / No / Choose an item. / Click here to enter text.
VR.2.8 / The system shall limit the number of dealer registrations and plates issued to a specific dealer based on business rules. / No / Choose an item. / Click here to enter text.
VR.2.9 / The system shall provide for the issuance of registrations and plates without specific vehicle information (e.g. boat dealer trailer, dealerships, transporter, repossession). / Yes / Choose an item. / Click here to enter text.
VR.3 / Dealer Automated Services
VR.3.1 / The system shall provide multiple points of access to authorized licensed dealers for the purpose of registering vehicles sold by them. / No / Choose an item. / Click here to enter text.
VR.3.2 / The system shall provide the capability for a dealer representative organization (Dealer Automated Services Providers) to add, delete, or correct registration data on behalf of their clients based on business rules. / No / Choose an item. / Click here to enter text.