das.nebraska.govdas.nebraska.gov/materiel/purchasing/5557/5557 Z1 App… · Web viewThe system shall be able to forecast plate usage by office and suggest re-ordering volume. No

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.

1 Appendix A: VTR Modernization Requirements Traceability Matrix

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.


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.


VR.1.6 VIN Yes Choose an item.


VR.1.7 Plate Number Yes Choose an item.


VR.1.8 Historical Plate Number No Choose an item.


VR.1.9 Current Decal Number No Choose an item.


VR.1.10 Make, Model, Year of Vehicle No Choose an item.



VR.1.11 Title Number Yes Choose an item.


VR.1.12 Registration Number Yes Choose an item.


VR.1.13 In-Transit Number (Temporary Tag) No Choose an item.


VR.1.14 Permit Number No Choose an item.


VR.1.15 Driver’s License Number No Choose an item.


VR.1.16 SSN or EIN No Choose an item.


VR.1.17 County of issue No Choose an item.


VR.1.18 County of situs No Choose an item.


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.


VR.1.20 The system shall provide the functionality to link multiple lessees to a vehicle. Yes Choose an item.


VR.1.21 The system shall prohibit, via business rules, a lessee and a lessor being the same entity.

No Choose an item.


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.


VR.1.23 The system shall have the ability to establish multi-year registration periods based on business rules.

Yes Choose an item.


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.


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.


VR.1.26 The system shall have the ability to assign a DMV-defined status to a registration.

Yes Choose an item.



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.


VR.1.28 The system shall be able to record a period of non-operation of a vehicle. No Choose an item.


VR.1.29 The system shall have the capability to register untitled vehicles. Yes Choose an item.


VR.1.30 The system shall have the capability to assign a system generated, unique identifier to untitled trailers.

No Choose an item.


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.


VR.1.32 The system shall have the ability to electronically update status of previous registration upon transfer of title.

No Choose an item.


VR.1.33 The system shall have the ability to record odometer values at user defined timeframes.

No Choose an item.


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.


VR.1.35 The system shall enable the authorized user to make required changes to the registration record.

Yes Choose an item.


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.


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.


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.


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.



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.


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.


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.


VR.1.43 The system shall have the ability to calculate a duplicate registration fee according to the business rules.

Yes Choose an item.


VR.1.44 The system shall be able to register multi-stage vehicles based upon business rules.

No Choose an item.


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.


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.


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.


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.


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.


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.


VR.2.3 The system shall have the ability to associate proof of financial responsibility to a registration.

Yes Choose an item.



VR.2.4 The system shall have a process for registering fleets of vehicles. No Choose an item.


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.


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.


VR.2.7 The system shall allow a field for an owner-assigned operator or equipment number for fleet vehicles.

No Choose an item.


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.


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.


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


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.


VR.3.3 The system shall send and receive messages and data regarding registration transactions to Dealer Automated Service Providers.

No Choose an item.


VR.3.4 The system shall place inbound messages regarding registration transactions from Dealer Automated Service Providers into a work queue for review, update and production of registration document.

No Choose an item.


VR.4 Renewals (Including Notices of Renewals) VR.4.1 The system shall have the ability to renew a registration for a user-defined

period of time. Yes Choose an


VR.4.2 The system shall generate a registration renewal based on business rules. Yes Choose an item.


VR.4.3 The system shall generate a file(s) of all renewal notices on a user-defined basis. Yes Choose an Click here to enter text.


VR.4.4 The system shall provide the ability to automatically generate coded (e.g., bar, QR, etc.) renewal notices based on registration expiration period.

No Choose an item.


VR.4.5 The system shall designate the customer's preferred delivery method for receiving notice, e.g., mail, email, text, and use preferred method to deliver the notice(s).

No Choose an item.


VR.4.6 The system shall group renewals to create a notice for multiple vehicles/boats owned by same registered owner and the same registered expiration month.

Yes Choose an item.


VR.4.7 The system shall generate a file of those registered owners requesting electronic notification.

Yes Choose an item.


VR.4.8 The system shall initiate and transmit the electronic notification for those registered owners requesting electronic notification.

No Choose an item.


VR.4.9 The system should have the ability to assign or assess user-defined fees or penalties for a late registration.

No Choose an item.


VR.4.10 The system shall have the ability to indicate that a customer desires an electronic notice of renewal (e.g. email, text, or some other method).

Yes Choose an item.


VR.4.11 The system shall allow customers the ability to select which of their vehicles/boats to renew.

Yes Choose an item.


VR.4.12 The system shall have the functionality to process the same renewal action on a selected set of registrations.

No Choose an item.


VR.4.13 The system shall have the ability to calculate and process renewals for vehicles/boats in a fleet where the vehicles/boats may be located in more than one county.

No Choose an item.


VR.4.14 The system shall prohibit vehicle/boat registration renewal utilizing the title status of the vehicle/boat, based on business rules.

No Choose an item.


VR.5 Change, Correct, Duplicate VR.5.1 The system shall allow update(s) to a registration record anytime during the

registration period. Yes Choose an


VR.5.2 The system shall allow the fees and taxes to be credited to a different vehicle or refunded to the customer.

Yes Choose an item.



VR.5.3 The system shall allow the plates to be transferred to a different vehicle or returned.

Yes Choose an item.


VR.5.4 The system shall issue a duplicate registration receipt or document. Yes Choose an item.


VR.5.5 The system shall provide ability to change address at any time during the registration validity period.

No Choose an item.


VR.5.6 The system shall store a reason for change and proof an owner requested the address change.

No Choose an item.


VR.5.7 The system shall provide ability to change a name at any time during the registration validity period.

Yes Choose an item.


VR.5.8 The system shall store a reason for change and proof that an owner requested the name change.

No Choose an item.


VR.6 Issue Permits VR.6.1 The system shall be able to issue permits for operation of a titled or untitled

vehicle based on business rules, including workflow and integration for permit processing.

No Choose an item.


VR.6.2 The system shall be able to issue, track, and manage an in-transit permit that is used to allow temporary operation of a vehicle after purchase and prior to affixing permanent license plates after purchase from a dealer (aka, temporary tag).

No Choose an item.


VR.6.3 The system shall be able to issue, track, and manage an in-transit permit that is used to allow temporary operation of a vehicle after purchase and prior to affixing permanent license plates after purchase in a private party sale (aka, temporary tag).

No Choose an item.


VR.6.4 The system shall have explicit data field and screens defined for each permit type.

No Choose an item.


VR.6.5 The system shall be able to track and print, at a minimum, the following permits (decals):

VR.6.6 Camper Unit Yes Choose an item.


VR.6.7 Non-Residential Carnival Operator Yes Choose an Click here to enter text.


VR.6.8 Farm Truck/Tractor Semi-Trailer No Choose an item.


VR.6.9 Grain Hauling Yes Choose an item.


VR.6.10 Local Moving No Choose an item.


VR.6.11 Livestock Forage No Choose an item.

Click here to enter text.VR.6.12 Temporary Demonstration No Choose an


VR.7 Boats VR7.1 The system shall be able to register, titled and untitled, boats. Yes Choose an


VR7.2 The system shall allow for the renewal of boat registrations. Yes Choose an item.


VR7.3 The system shall have explicit data fields and screens defined for boats. Yes Choose an item.


VR7.4 The system shall have ability to assign system generated, unique boat number. No Choose an item.


VR7.5 The system shall be able to validate a Hull Identification Number (HIN) to comply with Coast Guard regulations.

No Choose an item.


VR7.6 The system shall have the ability to calculate and refund boat registration fees according to business rules.

Yes Choose an item.


VR.8 Financial Responsibility VR.8.1 The system shall have the ability to capture self-insurance information. No Choose an


VR.8.2 The system shall have the ability to record proof of insurance information. Yes Choose an item.


VR.8.3 The system shall permit real time access to insurance information. Yes Choose an item.



VR.8.4 The system shall be able to receive insurance coverage information from licensed insurance providers (please refer to Nebraska Insurance Reporting Guide which may be found at www.dmv.nebraska.gov/dvr/ins_index.html).

Yes Choose an item.


VR.8.5 The system shall be able to update vehicle records with insurance status as provided by the insurance providers.

Yes Choose an item.


VR.9 Registration Records Access VR.9.1 The system shall be able to process requests received from authorized third

parties for individual registration records.Yes Choose an


VR.9.2 The system shall be able to process requests received from authorized third parties for batch registration records.

Yes Choose an item.


VR.9.3 The system shall allow the DMV to configure or modify the fees charged for bulk record sales.

No Choose an item.


VR.9.4 The system shall have the ability to permit dealers and other third-party business partners to access information for vehicles in their inventory or to verify information for a pending transaction, according to business rules.

Yes Choose an item.


VR.9.5 The system shall allow dealers and other third party business partners to verify vehicle information for a pending transaction, according to business rules.

Yes Choose an item.


VR.9.6 The system shall provide authorized law enforcement agencies the ability to construct a query to the registration and/or title information using any partial or complete data field.

No Choose an item.


VR.10 Temporary Tag VR.10.1 The system shall provide multiple points of access to authorized licensed

dealers for the purpose of recording temporary tags for vehicles sold by them. No Choose an


VR.10.2 The system shall provide the capability for a dealer representative organization (Dealer Automated Services Providers) to add, delete, or correct temporary tag data on behalf of their clients based on business rules.

No Choose an item.


VR.10.3 The system shall send and receive messages and data regarding temporary tag transactions to Dealer Automated Service providers.

No Choose an item.



Vehicle Registration Completed


Vehicle Title (VT)Requirements Section Bidder Response Section


Delivery Method

Explanation

VT.1 General VT.1.1 The system shall have the ability to issue titles for boats, ATVs, UTVs, minibikes,

trailers, motorcycles, and vehicles based on business rules. Yes Choose an


VT.1.2 The system shall provide for different vehicles types, including but not limited to: VT.1.3 B - Boat Yes Choose an


VT.1.4 M - Motorcycle Yes Choose anitem.


VT.1.5 P - Passenger Yes Choose anitem.


VT.1.6 T - Truck, Bus, Motorized Mobile Home Yes Choose anitem.


VT.1.7 O - Trailer, Non-Motorized Mobile Home, Camper Unit Permit Yes Choose anitem.


VT.1.8 V - All Terrain Vehicle, Minibike Yes Choose anitem.


VT.1.9 A - Autocycle Yes Choose anitem.


VT.1.10 The system shall provide the ability to add, modify, or delete vehicle types. Yes Choose anitem.


VT.1.11 The system shall have the ability to identify duplicate VIN/HINs as unique vehicles based on business rules.

Yes Choose anitem.


VT.1.12 The system shall use owner and vehicle information collected in the titling function to complete the registration function without having to re-enter the same data.

Yes Choose anitem.


VT.1.13 The system shall maintain a history of the title actions for a vehicle. The history shall be accessible by VIN, owner(s), title number, or plate number.

Yes Choose anitem.



VT.1.14 The system shall use business rules and system-defined validation to ensure only accurate vehicle and owner information is used to create a title record.

No Choose anitem.


VT.1.15 The system shall have the ability to electronically receive stolen vehicle information (add, update, and delete) from Nebraska State Patrol's switch (NCIC/NLETS).

Yes Choose anitem.


VT.1.16 The system shall have the ability to collect the sale price of vehicle in the title record.

No Choose anitem.


VT.1.17 The system shall provide customers with online access to information regarding their vehicle’s title and registration status including, but not limited to, insurance requirements, specialty plate status, and inventory assignments.

No Choose anitem.


VT.1.18 The system shall provide the ability to issue, store, print, transfer, and maintain motor vehicle titles electronically.

No Choose anitem.


VT.1.19 The system shall be able to print duplicate titles and reprint titles over the life of the vehicle.

Yes Choose anitem.


VT.1.20 The system shall be able to track the issuance of duplicate titles. Tracking should include identifying the user who issued the duplicate, reason, and a date stamp.

No Choose anitem.


VT.1.21 The system shall capture, for all title transactions, the title transaction type, the ID of the person performing the transaction, the location, etc. (e.g., who and where a title was printed).

Yes Choose anitem.


VT.1.22 The system shall, for all title transactions, capture and store the inventory control number from the blank title document which is used to create the title to be issued.

No Choose anitem.


VT.1.23 The system shall track the complete vehicle title history since it was entered into the system including all changes and transactions.

Yes Choose anitem.


VT.1.24 The system shall provide the capability for wildcard and Boolean searches of vehicle records, including but not limited to: current and previous owners, customer number, partial customer name, title number, full or partial plate number, full or partial VIN, lessee, lessor, lien holder, permit number, etc.

No Choose anitem.



VT.1.25 The system shall accept and retain the proper fuel type based on VIN. Yes Choose anitem.


VT.1.26 The system shall track all fuel types as well as vehicles with multiple fuel types (hybrid vehicles).

Yes Choose anitem.


VT.1.27 The system shall be able to override VIN-generated data fields with proper authorization and according to business rules.

Yes Choose anitem.


VT.1.28 The system shall provide the ability to retrieve vehicle valuation data from an external source (Automobile Red Book and Truck Blue Book by Price Digest).

Yes Choose anitem.


VT.1.29 The system shall provide the ability to manually enter vehicle valuation data, according to business rules and user-defined access permissions.

Yes Choose anitem.


VT.1.30 The system shall provide the ability to associate with, or remove a vehicle from, a fleet.

No Choose anitem.


VT.1.31 The system shall be able to update the title status to surrender the Nebraska title when a vehicle is titled in a new state (another jurisdiction). In addition, the system shall log the new state where the vehicle has been titled.

Yes Choose anitem.


VT.1.32 The system shall provide the ability to query on title and title application status. No Choose anitem.


VT.1.33 The system shall have the ability to issue a ‘corrected’ title (e.g., correct lien information, correct erroneous title information).

Yes Choose anitem.


VT.1.34 The system shall maintain a “Title Status” (e.g., Active, Assigned, Canceled, Duplicate, Surrendered, Withdrawn, Revoked, Pending, etc.).

No Choose anitem.


VT.1.35 The system shall maintain a history of vehicle ownership and associated registrations.

Yes Choose anitem.


VT.1.36 The system shall track the status of the title, registration and sales tax payments if the actions are completed at separate times or locations.

No Choose anitem.


VT.1.37 The system shall provide notifications or alerts to the DMV, County, Department of Revenue, and/or customer as appropriate.

No Choose anitem.


VT.1.38 The system shall print the boat number on boat titles. No Choose anitem.


VT.1.39 The system shall generate boat numbers based on business rules. No Choose anitem.



VT.1.40 The system shall have the ability to configure business rules to designate a title as an "e-title" and suppress the printing of a paper title for that vehicle.

Yes Choose anitem.


VT.1.41 The system shall have the ability to update a vehicle registration status when an applicable title action is taken (e.g., junk, surrender).

No Choose anitem.


VT.2 Original (Titled in Nebraska for the First Time) VT.2.1 The system shall create, manage and track a vehicle title record for each vehicle

eligible to be titled in Nebraska. Including but not limited to:

VT.2.2 Title status (e.g. title hold, junked, owner-retained salvage, cancelled real estate, surrendered, void, superseded, duplicate, corrected, and cancelled)

Yes Choose anitem.


VT.2.3 Title type (e.g. salvaged, bonded, original, non-transferable) Yes Choose anitem.


VT.2.4 Title Brand (e.g. previously salvaged, manufacturer buyback) Yes Choose anitem.


VT.2.5 The system shall allow creation, management, and tracking of a title based on business rules.

Yes Choose anitem.


VT.2.6 The system shall assign a system generated unique title number for each title issued.

Yes Choose anitem.


VT.2.7 The system shall be able to accept an electronic title transaction from a dealer or other authorized third-party processor.

No Choose anitem.


VT.2.8 The system shall have the ability to require and record a VIN inspection prior to authorizing the issuance of a title, when applicable.

Yes Choose anitem.


VT.2.9 The system shall be able to perform an instant VIN/HIN validation with current manufacturer data.

No Choose anitem.


VT.2.10 The system shall include VIN/HIN decoding capability to assess a VIN/HIN and decode all possible data from the VIN/HIN such as Make, Model, Year, and other relevant information.

Yes Choose anitem.



VT.2.11 The system shall allow users to create and assign VIN/HIN to vehicles, trailers, or other items. The system shall apply appropriate business rules, track available VIN/HIN assignments, and manage the process of creating and assigning VIN/HINs.

No Choose anitem.


VT.2.12 The system shall capture the Out-of-State Title Number and State abbreviation. Yes Choose anitem.


VT.2.13 The system shall capture the VIN inspection information, based on business rules. No Choose anitem.


VT.2.14 The system shall permit generated VIN data to be overridden according to business rules and with proper user defined roles.

No Choose anitem.


VT.2.15 The system shall have the ability to capture information from multiple Manufacturer Statement of Origin (MSO) and assign a single title to multi-stage vehicles. The VIN shall be the VIN from the first-stage manufacturer's MSO. The Make and Model Year shall be the information reflected on the final stage manufacturer's MSO.

No Choose anitem.


VT.3 Title Brands, including Junk and Salvage (Including Owner-Retained Salvage) VT.3.1 The system shall have the ability to designate a title status as "junk." Yes Choose an


VT.3.2 The system shall have the ability to assign a brand or multiple brands when issuing a title based on business rules.

Yes Choose anitem.


VT.3.3 The system shall have the ability to electronically receive owner retained and all other salvage information from insurance companies.

No Choose anitem.


VT.3.4 The system shall have the ability to require and record a VIN inspection prior to authorizing the issuance of a previous salvage title.

Yes Choose anitem.


VT.3.5 The system shall maintain brand history associated with the title including brand and state.

Yes Choose anitem.


VT.3.6 The system shall provide for the removal of brands recorded in error by an authorized user with the proper system security role and interface with NMVTIS.

No Choose anitem.


VT.3.7 The system shall use AAMVA standard brand designations and allow for entry of Nebraska specific brands if needed.

No Choose anitem.



VT.3.8 The system shall be able to be modified to add additional vehicle brand types. Yes Choose anitem.


VT.3.9 The system shall generate a notice to the owner when an insurance company submits an owner-retained notice to the DMV based on business rules.

No Choose anitem.


VT.3.10 The system shall have the ability to electronically receive junk and salvage information from salvage dealers.

No Choose anitem.


VT.4 Used Vehicle Transfer VT.4.1 The system shall have the ability to transfer a title (record of ownership) between

owners. Yes Choose an


VT.4.2 The system shall have the ability to assign the new owner(s) name and address information as retrieved from the customer record (rather than requiring the user to manually enter the information in the transfer transaction).

No Choose anitem.


VT.4.3 The system shall verify the eligibility of the transfer transaction based on business rules (specifically the status of the title and lienholder information).

No Choose anitem.


VT.4.4 The system shall include title transfer policies and rules accessible via a help or display function to inform users the policies and rules regarding vehicle transfers.

No Choose anitem.


VT.4.5 The system shall allow the seller in a private sale to declare a vehicle as sold regardless of the title transaction being completed.

No Choose anitem.


VT.4.6 The system shall mark the title record as "reported sold" along with the information from the reporting entity, when a notice of transfer is received.

No Choose anitem.


VT.4.7 The system shall provide confirmation of electronic title transfer to the owner or previous owner.

No Choose anitem.


VT.4.8 The system shall allow for electronic reassignment of titles between dealers and auctions.

No Choose anitem.


VT.4.9 The system shall have the capability to allow a temporary tag to be printed and displayed on the vehicle following a private party transfer, according to the business rules.

No Choose anitem.


VT.5 Correct or Duplicate Title VT.5.1 The system shall have the ability to issue a duplicate title. Yes Choose an Click here to enter text.


VT.5.2 The system shall have the ability to issue a no-fee title or no-fee duplicate title based on business rules.

Yes Choose anitem.


VT.5.3 The system shall have the ability to mark the title record with the title number, issuance date and status of duplicate or corrected titles.

Yes Choose anitem.


VT.5.4 If the correction of the title affects the registration information, the system shall guarantee a new registration be issued reflecting the corrected information.

No Choose anitem.


VT.5.5 The system shall include the capability to void a title based on business rules. Yes Choose anitem.


VT.5.6 The system shall support online processing of online duplicate title using electronic notarization.

No Choose anitem.


VT.6 Lien Processing (Including ELT) VT.6.1 The system shall have the ability to associate one or more liens with a title. Yes Choose an


VT.6.2 The system shall have the ability to differentiate between a lien filed by an ELT participating lender and a lien filed by a non-participating lender.

Yes Choose anitem.


VT.6.3 The system shall record a lien notation fee. Yes Choose anitem.


VT.6.4 The system shall have the ability to transfer or reassign an ELT from one ELT lienholder to another ELT lienholder for individual and batch records.

No Choose anitem.


VT.6.5 The system shall have the ability to issue a confirmation to the ELT lienholder of all ELT actions/record changes.

No Choose anitem.


VT.6.6 The system shall maintain a file of all authorized ELT lienholders and notify ELT service providers of any changes to the file.

Yes Choose anitem.


VT.6.7 The system shall allow lienholders to establish separate ELT participating lender ID for each branch operation.

Yes Choose anitem.


VT.6.8 The system shall allow lienholders to associate multiple branch operation addresses with the same participating lender ID.

No Choose anitem.


VT.6.9 The system shall have the ability to produce a paper title for any vehicle that has an ELT status.

Yes Choose anitem.



VT.6.10 The system shall have the ability to edit lien entry to ensure lienholder and owner are not the same.

No Choose anitem.


VT.6.11 The system shall have a file which contains a list of possible lien holders as accumulated through the ELT enrollment and lien notation processes with user defined information regarding the lienholders and ELT status.

Yes Choose anitem.


VT.6.12 The system shall require users to utilize the file containing a list of possible lien holders when noting a lien based on business rules.

Yes Choose anitem.


VT.6.13 The system shall permit a lienholder representative organization (ELT providers) to manage, e.g., add, delete, correct, lienholder information on behalf of their client (please refer to Nebraska Electronic Lender Guide which may be found at www.dmv.nebraska.gov/dvr/ELT.html).

No Choose anitem.


VT.6.14 The system shall permit authorized lienholders to search and view lien information for vehicles associated with their entity.

No Choose anitem.


VT.6.15 The system shall send and receive messages regarding errors in title information to ELT providers.

No Choose anitem.


VT.6.16 The system shall place inbound messages regarding errors from ELT providers into a work queue for review.

No Choose anitem.


VT.6.17 The system shall be able to change the status of single or multiple titles from paper to electronic upon receipt of an electronic notification from the lienholder, and should send a confirmation to the service provider upon conversion.

Yes Choose anitem.


VT.6.18 The system shall be able to release the lien on an electronic title, record the date the lien was released, and print a title to be mailed to the customer when electronic notification is received that a lien on an electronic title has been released.

Yes Choose anitem.


VT.6.19 The system shall be able to release the lien and record the date the lien was released when a title is presented with a lien release noted on the title.

Yes Choose anitem.


VT.6.20 The system shall be able to release the lien on an electronic title, record the date the lien was released, and print a title to be provided to the customer when a lien on an electronic title has been manually released.

Yes Choose anitem.



VT.6.21 The system shall capture mail-to address information if the title is to be mailed to a different address then the customer's address of record.

Yes Choose anitem.


VT.7 NMVTIS VT.7.1 The system shall have the ability to electronically provide data of titles issued and

titles surrendered to the National Motor Vehicle Title Information System (NMVTIS) in real time.

No Choose anitem.


VT.7.2 The system shall have the ability to electronically notify NMVTIS of salvage and junk status when title records are updated with those status conditions.

Yes Choose anitem.


VT.7.3 The system shall have the ability to electronically provide brand data associated with titles issued to the National Motor Vehicle Title Information System (NMVTIS) in real time.

Yes Choose anitem.


VT.7.4 The system shall have the ability to electronically provide junk and salvage information received from salvage dealers to NMVTIS.

No Choose anitem.


VT.7.5 The system shall have the ability to, in real time, undo an update to NMVTIS when a title transaction is voided.

No Choose anitem.


VT.7.6 The system shall perform an interactive NMVTIS inquiry prior to title issuance based on the business rules defined in the system, without a separate action by the user.

No Choose anitem.


VT.7.7 The system shall return a response from NMVTIS that requires a user action to the user along with the literal English description of the action to be taken.

No Choose anitem.


VT.8 Master Customer Record VT.8.1 The system shall provide for "transfer upon death" owner(s) to be included as a

part of the title.Yes Choose an


VT.8.2 The system shall have a mailing indicator that points to which owner address(es) the title and renewal notifications are to be mailed.

No Choose anitem.


VT.8.3 The system shall permit multiple owners in the title record. Yes Choose anitem.


VT.8.4 The system shall permit the designation of lessor/lessee in the customer record. Yes Choose anitem.



VT.8.5 The system shall provide the ability to identify the owner of a vehicle by Customer ID and/or Driver License ID.

Yes Choose anitem.


VT.8.6 The system shall provide the ability to validate an address. Yes Choose anitem.


VT.8.7 The system shall capture the address the customer has designated where the vehicle is domiciled for tax and fee purposes.

No Choose anitem.


VT.8.8 The system shall provide the means to document what corrections were made to a record, including but not limited to audit fields with time date stamp, user information, and before and after record information.

No Choose anitem.


VT.8.9 The system shall be able to redact personal information from printed or displayed data, based on business rules.

No Choose anitem.


VT.8.10 The system shall support the data requirements related to entities in the master customer record, in addition to the business rules for individuals.

No Choose anitem.


VT.8.11 The system shall include the driver’s license number or other assigned customer number in the master customer record.

No Choose anitem.


VT.8.12 The system shall capture customer data based on a business rules associated to customer types (e.g., lessor, individual, business, etc.).

No Choose anitem.


VT.9 VIN Inspection VT.9.1 The system shall allow authorized VIN inspectors to enter the results of VIN

inspections to the title record.No Choose an


VT.9.2 The system shall record the result details of a VIN inspection not updated by the inspector.

No Choose anitem.


VT.9.3 The system shall provide a mechanism for collecting VIN inspection fees based on local office business rules.

Yes Choose anitem.


VT.10 Dealer Automated Services VT.10.1 The system shall provide multiple points of access to authorized licensed dealers

for the purpose of submitting title application and/or lien data for vehicles sold by them.

No Choose anitem.


VT.10.2 The system shall provide the capability for a dealer representative organization (Dealer Automated Services Providers) to add, delete, or correct title application and/or lien data on behalf of their clients based on business rules.

No Choose anitem.



VT.10.3 The system shall send and receive messages and data regarding title and lien transactions to Dealer Automated Service providers.

No Choose anitem.


VT.10.4 The system shall place inbound messages regarding title application and lien transactions from DAS providers into a work queue for review, update and production of title document.

No Choose anitem.


Vehicle Title Completed


Fees and Taxes (FT)Requirements Section Bidder Response Section


Delivery Method

Explanation

FT.1 General FT.1.1 The system shall have the ability to refund registration fees and taxes to the owner. Yes Choose

an item.Click here to enter text.

FT.1.2 The system shall have the ability to refund boat registration fees to the owner either at the county level or from a central location.

Yes Choose an item.


FT.1.3 The system shall be able to provide reports and data extracts, which detail the collection and distribution of funds.

Yes Choose an item.


FT.1.4 The system shall have the functionality to allow for full administration of sales tax. No Choose an item.


FT.1.5 The system shall have the ability to calculate correct fees and taxes based upon the effective date and/or expiration date of the respective fee or tax.

Yes Choose an item.


FT.1.6 The system shall have the ability to calculate correct fees and taxes on a renewal notice based on the future effective date or future expiration date of the respective fee or tax.

No Choose an item.


FT.1.7 The system shall have the capability to allow authorized users to manage the fee schedules to create, copy, delete fee schedule entries; create different versions; and, assign effective (start and stops) dates as necessary.

No Choose an item.


FT.1.8 The system shall generate a breakdown of the fees and taxes associated with the transaction performed and whether they were collected or exempted.

Yes Choose an item.


FT.1.9 The system shall support the summarization and reporting of DMV fund-level financial activity to the appropriate agencies and offices.

Yes Choose an item.


FT.1.10 The system shall maintain a table of fee distributions which will associate moneys received on each transaction to distribution of funds to other agencies or all appropriate groups/entities.

Yes Choose an item.



FT.1.11 The system shall be able to generate reports on revenues and distributions. Yes Choose an item.


FT.2 Calculate Fees and Taxes FT.2.1 The system shall calculate taxes for all motor vehicle transactions based on business

rules (Please refer to www.dmv.nebraska.gov/dvr/mvreg/fees_taxes.html for more detailed information).

Yes Choose an item.


FT.2.2 The system shall calculate all fees for all motor vehicle transactions based on business rules (Please refer to www.dmv.nebraska.gov/dvr/mvreg/fees_taxes.html for more detailed information).

Yes Choose an item.


FT.2.3 The system shall have the ability to associate a registration with the following geographic data elements:

FT.2.4 City Yes Choose an item.


FT.2.5 County Yes Choose an item.


FT.2.6 School District Yes Choose an item.


FT.2.7 The system shall allow fees and taxes to be exempted from collection based upon business rules.

Yes Choose an item.


FT.2.8 The system shall have the capability to record the fee and tax exempt reason. Yes Choose an item.


FT.2.9 The system shall be able to calculate fees and taxes based on MSRP/GVWR data retrieved from an external data source.

No Choose an item.


FT.2.10 The system shall allow for sales tax–only transactions. Yes Choose an item.


FT.2.11 The system shall be able to assess late fees for motor vehicle transactions based on business rules.

No Choose an item.


FT.2.12 The system shall have the ability to register a motor vehicle upon collection of a partial fee based on business rules.

Yes Choose an item.


FT.2.13 The system shall calculate and provide a report for distribution of All Terrain Vehicle (ATV) sales tax based on business rules.

No Choose an item.



FT.2.14 The system shall be able to calculate, collect and provide a report for the distribution of taxes assessed to car rental agencies based on business rules.

No Choose an item.


FT.2.15 The system shall be able to calculate and prorate the difference between the fees and taxes, when a customer requests a credit of previously paid fees and taxes toward a newly purchased vehicle.

Yes Choose an item.


FT.2.16 The system shall be able to adjust the sales tax due based on credit from a trade in vehicle.

Yes Choose an item.


FT.2.17 The system shall be able to record sales tax paid at the point of sale. No Choose an item.


FT.2.18 The system shall be able to recognize that sales tax has been previously paid in a sales tax only transaction.

No Choose an item.


FT.3 Fee and Tax Accounting and Distribution FT.3.1 The system shall be able to calculate the distribution of fees and taxes to different

funds based on business rules.Yes Choose


FT.3.2 The system shall have the ability to generate a sales tax remittance document, either for print or electronic signature capture (Nebraska Department of Revenue Form 6).

Yes Choose an item.


FT.3.3 The system shall have the ability to produce a notification and/or report to customers who have not met statutorily required deadlines.

No Choose an item.


FT.3.4 The system shall have the ability to produce a notification to customers who have not paid their sales tax according to business rules.

No Choose an item.


FT.3.5 The system shall allow for a VIN inspection fee to be collected as a part of the transaction and account for the funds according to the business rules established for the VIN inspection fee.

Yes Choose an item.


FT.4 Reporting FT.4.1 The system shall provide transaction summary reports for batch entered work. Yes Choose


FT.4.2 The system shall be able to provide transaction and revenue reports by cash drawer, location, county, transaction, and tender type.

Yes Choose an item.



FT.4.3 The system shall have the ability to generate a consolidated master report over a defined time period showing payments received and listing forms of payment including check, cash, credit and debit card payments, etc.

Yes Choose an item.


FT.4.4 The system shall create a transaction report that includes the breakdown by cash drawer or location and transaction type details.

Yes Choose an item.


FT.4.5 The system shall be able to display a running total of fees when entering more than one transaction from the same customer.

No Choose an item.


FT.4.6 The system shall generate required reports to the Department of Revenue regarding sales tax.

No Choose an item.


FT.5 Dealer Automated Services FT.5.1 The system shall provide the capability for a dealer representative organization

(Dealer Automated Services Providers, DAS) to add, delete, or correct tax and fee data on behalf of their clients when collecting taxes and fees from the vehicle purchaser based on business rules.

No Choose an item.


FT.5.2 The system shall send and receive messages and data regarding tax and fee transactions to DAS providers.

No Choose an item.


FT.5.3 The system shall place inbound messages regarding tax and fee transactions from DAS providers into a work queue for review and update.

No Choose an item.


Fees and Taxes Completed


Point of Sale (POS)Requirements Section Bidder Response Section

Req # Requirement Description CurrentEnvironment

Delivery Method

Explanation

POS.1 General POS.1.1 The system shall have a 'shopping cart' capability to calculate total fees and

taxes due for one or more transactions. The shopping cart capability means payments for more than one transaction can be accumulated and paid for in a single payment process.

No Choose an item.


POS.1.2 The system shall be able to accept the following forms of tender: POS.1.3 Cash Yes Choose


POS.1.4 Check Yes Choose an item.


POS.1.5 Credit Card No Choose an item.


POS.1.6 Debit Card No Choose an item.


POS.1.7 Electronic Check No Choose an item.


POS.1.8 Other forms of electronic payment (Bidder shall list all payment types available)

No Choose an item.


POS.1.9 The system shall allow a customer to pay for a transaction or group of transactions via any service channel using one or more payment methods.

Yes Choose an item.


POS.1.10 The system shall provide the ability to receive and record payment verification for debit, credit and cash cards.

No Choose an item.


POS.1.11 The system shall be able to print a refund check to a customer when a refund is due in compliance with business requirements.

Yes Choose an item.


POS.1.12 The system shall be able to print a receipt. Yes Choose an item.



POS.1.13 The system shall be able to reprint a receipt after the transaction has been completed.

Yes Choose an item.


POS.1.14 The system shall be able to generate and deliver an electronic receipt. No Choose an item.


POS.1.15 The system shall comply with all Payment Card Industry (PCI) standards. No Choose an item.


POS.1.16 The system shall have the ability for an authorized user to set a business date for cashiering purposes which may be different from the calendar date.

Yes Choose an item.


POS.1.17 The system shall have the ability to manage returned or not-honored forms of payment based on business rules, including cancelation of registration, collection of payment plus service charge, and partial payments.

No Choose an item.


POS.2 Internet Collection POS.2.1 The system shall support processing of on-line transactions and payments based

on business rules. No Choose


POS.2.2 The system shall be able to accept payments from an electronic payment service provider.

No Choose an item.


POS.2.3 The system shall be able to accept payments from Electronic Funds Transfer (EFT)/Automated Clearinghouse (ACH).

No Choose an item.


POS.2.4 The system shall support the attachment of supporting documents for online transactions.

No Choose an item.


POS.2.5 The system shall have the ability to suspend an online transaction for staff review, approval, or denial based on business rules.

No Choose an item.


POS.2.6 The system shall have the capability for authorized licensed dealers to register vehicles sold by them via an online service based on business rules.

No Choose an item.


POS.2.7 The system shall have the capability for authorized licensed dealers to record temporary tag information for vehicles sold by them via an online service based on business rules.

No Choose an item.


POS.2.8 The system shall have the capability for authorized licensed dealers to submit title application and/or lien data for vehicles sold by them via an online service based on business rules.

No Choose an item.


POS.3 Cashier Closeout


POS.3.1 The system shall keep track of the cashier's starting bank and each of the cashier's sessions and all transactions belonging to that session. Once a cashier is closed out a new session begins with the first transaction after closeout. The POS system shall:

POS.3.2 Link each cashier's starting bank to the cashier, which shall be configurable so it can be changed by the POS Administrator when necessary.

No Choose an item.


POS.3.3 Automatically deduct the cashier's starting bank at closeout and for purposes of calculating over and short situations.

No Choose an item.


POS.3.4 Allow for automatic closeouts and supervisor reporting for cashiers which do not take in any cash, checks or credit vouchers.

No Choose an item.


POS.3.5 Allow the supervisor to perform a cash count without closing out in order to settle customer discrepancies or audit inquiries.

No Choose an item.


POS.3.6 Create a unique session number for each cashier's sessions. No Choose an item.


POS.3.7 Allow a cashier to move between different customer service representative’s stations within the same branch/office.

No Choose an item.


POS.3.8 Keep track of which transactions were completed at which workstations. No Choose an item.


POS.3.9 The system shall permit business rules to allow the capability to give cash back for cash or check based on business rules.

Yes Choose an item.


POS.3.10 The system shall have the capability to perform an automated reconciliation: POS.3.11 All discrepancies from the automated reconciliation process shall be reported as

alerts to the authorized accounting staff for review and corrections. No Choose


POS.3.12 A capability for the authorized staff to review and correct the reported discrepancies.

No Choose an item.


POS.3.13 A capability to complete the reconciliation process after all discrepancies have been corrected.

No Choose an item.


POS.3.14 After the reconciliation process is complete, designating the transaction records as reconciled.

No Choose an item.


POS.3.15 The system shall track collections by the following parameters:


POS.3.16 By Payment Methods No Choose an item.


POS.3.17 By Transaction Type No Choose an item.


POS.3.18 By Customer – Information such as Name, Title, Plate Number, Customer Number

No Choose an item.


POS.3.19 No Fee Transactions (i.e. no fees are charged for these transactions) No Choose an item.


POS.3.20 By Cashier Session – which may further be tracked by parameters listed above and consolidated totals for the POS station.

No Choose an item.


POS.3.21 For each location – which may further be tracked by parameters listed above and consolidated totals for each location.

No Choose an item.


POS.3.22 Collections shall also be tracked on a daily basis for consolidation. No Choose an item.


POS.3.23 The system shall allow for one cashier to log off and another person to easily be reassigned to the same workstation.

No Choose an item.


Point of Sale Completed


Inventory Management (IM)Requirements Section Bidder Response Section


Delivery Method

Explanation

IM.1 General IM.1.1 The system shall be able to recognize non-alpha-numeric plate characters (e.g.,

dashes, currency signs, and ampersands). Yes Choose


IM.1.2 The system shall be able to issue and track registration decals. No Choose an item.


IM.1.3 The system shall be able to issue and track one-plate decals including associated inventory control number.

Yes Choose an item.


IM.1.4 The system shall provide the ability to request a replacement plate based upon business rules.

No Choose an item.


IM.1.5 The system shall have the ability to assign a status to a plate issued or in inventory (e.g., available, issued, lost, damaged, not returned, stolen, surrendered, etc.)

Yes Choose an item.


IM.1.6 The system shall have the capability to manage inventory for law enforcement undercover purposes and restrict user access.

No Choose an item.


IM.1.7 The system shall have the ability to add or remove plates from inventory. Yes Choose an item.


IM.1.8 The system shall have the ability to print on demand decals. No Choose an item.


IM.1.9 The system shall support replacement of all or specific plate types and decals based on user-defined selection criteria, including other vehicle types as appropriate.

Yes Choose an item.


IM.1.10 The system shall have the ability to reserve or set aside specific plate numbers/configurations according to business rules.

Yes Choose an item.


IM.1.11 The system shall have the ability to scan bar coded information on inventory items or shipping information and utilize data in lieu of the operator keying the information.

Yes Choose an item.


IM.1.12 The system shall have the ability to add, modify, or delete an unlimited number of license plate types.

Yes Choose an item.



IM.1.13 The system shall accommodate multiple plate number configurations. Yes Choose an item.


IM.1.14 The system shall allow plates to be transferred from one vehicle to another based on business rules.

Yes Choose an item.


IM.2 Issue Original IM.2.1 The system shall have the ability to issue and track license plates. Yes Choose


IM.2.2 The system shall have the ability to track license plate inventory. Yes Choose an item.


IM.2.3 The system shall have the ability to assign a plate from inventory based on business rules.

No Choose an item.


IM.2.4 The system shall have the ability to assign a single plate or double set of plates to a vehicle based on business rules.

Yes Choose an item.


IM.3 Reissuance IM.3.1 The system shall have the ability to denote a series of plates (i.e., associate a plate

with a specific statutorily-mandated reissuance). Yes Choose

an item. Click here to enter text.

IM.4 Order Specialty Plates IM.4.1 The system shall have the ability to accept a customer request for a specialty plate. Yes Choose


IM.4.2 The system shall have the ability to retain an inventory of plate numbers or configurations which are deemed unacceptable or not allowed for issuance.

Yes Choose an item.


IM.4.3 The system shall have the ability to allow customers to check the status of ordered plates.

No Choose an item.


IM.4.4 The system shall be able to issue specialty plates based on business rules and workflow, including assignment to a customer record prior to designating the vehicle assignment.

Yes Choose an item.


IM.4.5 The system shall have the ability to allow online customer inquiry of plate availability.

Yes Choose an item.


IM.4.6 The system shall have the ability to define the valid options for specialty plate eligibility and configuration based on the business rules for each plate type.

No Choose an item.



IM.4.7 The system shall have the ability to mail specialty plate orders directly to customers based on business rules.

No Choose an item.


IM.4.8 The system shall have the ability to process specialty plate recertification transactions.

Yes Choose an item.


IM.4.9 The system shall have the ability to generate a notice to specialty plate holders which require recertification.

Yes Choose an item.


IM.4.10 The system shall have the ability to process specialty plate order based on successful completion of the recertification.

Yes Choose an item.


IM.5 Manage Inventory Assignment IM.5.1 The system shall have the ability to receive and monitor inventory of plates, decals,

and any other registration or title consumables by office location. No Choose


IM.5.2 The system shall have a user-configurable inventory re-order threshold (i.e., min/max).

No Choose an item.


IM.5.3 The system shall be able to forecast plate usage by office and suggest re-ordering volume.

No Choose an item.


IM.5.4 The system shall be able to forecast plate usage by plate type and suggest re-ordering volume.

No Choose an item.


Inventory Management Completed


Technical (T) Bidder Response SectionReq # Requirement Description Current

EnvironmentDelivery Method

Explanation

T.1 General T.1.1 The system shall allow for entry of data or completion of transactions

through the use of network attached devices, mobile devices, etc. (Bidder shall provide list of acceptable devices).

Yes Choose an item.


T.1.2 The system shall allow for online services access through a smartphone to be rendered correctly for the device being used.

Yes Choose an item.


T.1.3 The system shall provide the capability to generate test data with the same attributes of production data. The test data may not be an exact duplicate copy of production records.

No Choose an item.


T.1.4 The system shall allow the user to add a comment to a transaction at any point in the process (e.g. any field or screen).

No Choose an item.


T.1.5 The system shall have the ability to utilize XML-based standards, delimited file format, fixed file format, and custom transaction formats for communication and integration with other environments.

Yes Choose an item.


T.1.6 The system shall have a uniform "look and feel" throughout all applications (e.g. similar color scheme, table/form layout, button placement, function keys, shortcuts, etc.).

Yes Choose an item.


T.1.7 The system shall have the ability to function across multiple platforms. No Choose an item.


T.1.8 The system shall have the ability to restrict service availability by user type. Yes Choose an item.


T.1.9 The system shall provide diagnostic information to the support team on the type and source of system errors.

Yes Choose an item.


T.1.10 The system shall be capable of supporting production test, training, and development environments.

Yes Choose an item.



T.1.11 The system shall be open and non-proprietary where possible, with options available without additional costs outside of Contract terms (third-party hardware and software components).

No Choose an item.


T.1.12 The system shall report performance metrics for use in capacity provisioning and diagnostics.

No Choose an item.


T.1.13 The system shall assign a unique, searchable, number to each transaction. Yes Choose an item.


T.1.14 The system shall change the application status to “in progress” when a user begins to work on the transaction.

Yes Choose an item.


T.1.15 The system shall permit another user to view, but not make changes, to a record which is "in progress", until the record has been released.

Yes Choose an item.


T.1.16 The system shall support workflow-triggered correspondence (electronic or paper) to individuals and/or groups, with both content and attachments derived from system data. For example, correspondence addressed to a customer with a salutation including the user’s full legal name and vehicle registration information.

No Choose an item.


T.1.17 The system shall use NCIC codes and descriptors. Yes Choose an item.


T.1.18 The system shall provide the ability to validate an address against an external source of data (e.g., Experian QAS).

No Choose an item.


T.1.19 The system shall auto-populate address field with correct information as it is being entered into the customer record utilizing an external source of data (e.g., Experian QAS).

No Choose an item.


T.2 Software T.2.1 The system shall allow authorized users to remotely end unresponsive

applications or unfreeze system operations. Yes Choose an


T.3 System Security T.3.1 The system shall provide access control by a role-based security

component with user-defined roles and authorities.No Choose an



T.3.2 The system shall allow authorized user to determine the security level of all users.

Yes Choose an item.


T.3.3 The system shall allow authorized user to grant security level permissions to a user.

Yes Choose an item.


T.3.4 The system shall allow authorized users to grant security level permission only up to, but not including, their own level.

Yes Choose an item.


T.3.5 The system shall log all user access information (sign-on, sign off, source IP) and include date and time references.

No Choose an item.


T.3.6 The system shall log all information accessed by users to provide audit trails.

No Choose an item.


T.3.7 The system shall provide the administrator with the ability to specify the level of audit to be set for users.

No Choose an item.


T.3.8 The system shall provide users access to the system and any peripheral applications using a single, authenticated sign-on credential.

No Choose an item.


T.4 Reports T.4.1 The system shall allow users to generate and retrieve reports based on

user defined roles. No Choose an


T.4.2 The system shall allow users to generate and retrieve predefined reports. Yes Choose an item.


T.4.3 The system shall allow users to generate and retrieve reports based on system activity captured user access information (sign-on, sign off, source IP) and include date and time references.

No Choose an item.


T.4.4 The system shall retain ad-hoc and customizable queries as determined by the user.

Yes Choose an item.


T.4.5 The system shall: T.4.6 Provide "Executive Dashboard" reporting with drill-down capabilities. No Choose an


T.4.7 Provide the choice of whether to view, print, or send reports via electronic means.

No Choose an item.


T.4.8 Provide for local printing of documents at any authorized locations. Link to a web page, spreadsheet file, or text file directly from a report.

No Choose an item.



T.4.9 Generate print files of forms, and other documents that can be sent to third-party.

No Choose an item.


T.4.10 Provide for electronic archival and reprinting of system-generated reports. No Choose an item.


T.4.11 The system shall allow reporting and inquiry-only application components without impact or dependence on the availability of the production database.

No Choose an item.


T.4.12 The system shall be able to report on performance metrics to meet the recommended best practices of the National Highway Traffic Safety Administration (NHTSA) available at: http://www.roads.nebraska.gov/media/6270/traffic-records-assessment-nebraska.pdf

No Choose an item.


T.4.13 The system shall be able to set NHTSA designated performance metrics. http://www.roads.nebraska.gov/media/6270/traffic-records-assessment-nebraska.pdf

No Choose an item.


T.5 Alerts T.5.1 The system shall allow for the creation of user-defined alerts. No Choose an


T.5.2 The system shall allow for system-generated alerts, on security violations. No Choose an item.


T.6 Business Rules Management T.6.1 The system shall have the ability for an authorized user to capture and

maintain (add, modify, and delete) business rules.No Choose an


T.6.2 The system shall have the ability for an authorized user to record reasons for changes to business rules.

No Choose an item.


T.6.3 The system shall utilize the business rules component as the primary means for determining processes and workflow.

No Choose an item.


T.6.4 The system shall provide one single rules repository where DMV business rules will be defined, updated and maintained while maintaining role based access. Once defined, the business rules can be deployed at multiple locations or used by multiple components, if needed.

No Choose an item.



T.6.5 The system shall allow a business rule to contain an effective date and, if applicable, an end date.

No Choose an item.


T.6.6 The system shall have the ability to configure business rules to ensure standardization of vehicle, owner and address information.

No Choose an item.


T.7 Backup, Recovery, and Disaster Planning T.7.1 The system shall be available no less than 99.9% as measured on a monthly

basis.No Choose an


T.7.2 The system shall provide audit log files capturing before and after images for all database systems.

No Choose an item.


T.7.3 The system shall have point-in-time recovery capabilities for all databases. This means upon any failure, the database can be recovered to the last point of consistent state.

No Choose an item.


T.8 System Performance Metrics T.8.1 The system shall have the ability to view, print and export a dashboard of

key performance indicators, with user-defined parameters, showing graphical information on business and technical performance against service-level objectives.

No Choose an item.


T.9 Hardware and Network T.9.1 The system shall support Simple Network Management Protocol (SNMP)

and the Web-based tool set for centralized control of the system using an enterprise management platform.

No Choose an item.


T.9.2 The system shall use the existing State of Nebraska network which is used for all DMV traffic.

Yes Choose an item.


T.9.3 The system shall have self-service password reset capabilities. No Choose an item.


T.9.4 The system shall allow system administrators the ability to configure and update user roles while the system is online.

Yes Choose an item.


T.9.5 The system shall automatically log off users which have been inactive for a specified period of time. Users can simply sign back on to system to resume activity from the point of timeout.

No Choose an item.



T.9.6 The system shall support the use of pointing devices, hot keys, key combinations, buttons, touch screens, and hyperlinks.

No Choose an item.


T.9.7 Field and screen validation: T.9.8 The system shall provide a visual distinction between mandatory and non-

mandatory fields.No Choose an


T.9.9 The system shall do field validation of data upon entry. Yes Choose an item.


T.9.10 The system shall display errors on the appropriate screen for the user. Yes Choose an item.


T.9.11 The system shall have printable user application screens configurable to local or networked printers, using print commands provided by the browser.

Yes Choose an item.


T.9.12 The system shall allow user application screens to be captured using commands provided by the browser.

Yes Choose an item.


T.10 User Interface T.10.1 The system shall include a browser-based user interface. No Choose an


T.10.2 The system shall display browser pages on mobile devices within the size and orientation of the device.

No Choose an item.


T.10.3 The system shall be capable of working in a kiosk-based touch screen environment.

No Choose an item.


T.10.4 The system shall be configurable to allow for adding/updating items in the drop-down menu without requiring programmer changes.

No Choose an item.


T.10.5 The system shall support “auto complete” functionality for code table lookups as the user begins to enter data in the code table lookup field.

No Choose an item.


T.10.6 The system shall support pre-fill fields in appropriate pre-formatted screens, eliminating redundant data entry and without impacting the usability.

No Choose an item.


T.10.7 The system shall provide help menus with information specific to the user role.

No Choose an item.



T.10.8 The system shall allow users to move forward and backward to complete data fields without the loss of data entered.

No Choose an item.


T.10.9 The system shall allow users to correct spelling errors without having to retype the entire field.

Yes Choose an item.


T.10.10 The system shall provide users with standard form navigation and allow movement from one work area to another via mouse and keyboard.

No Choose an item.


T.10.11 The system shall provide default, configurable values for fields based on previous input, or other mechanisms. It should incorporate currently used defaults.

Yes Choose an item.


T.10.12 The system shall provide lookup tables for valid values for fields. No Choose an item.


T.10.13 The system shall allow authorized users to configure tables. No Choose an item.


T.10.14 The system shall translate codes to U.S. English-language words or phrases on the output screen and reports for all codes used.

No Choose an item.


T.10.15 The system shall support editing and validation routines for all mandatory fields, clearly indicating data which fail validation.

Yes Choose an item.


T.10.16 The system shall be able to support control key shortcuts for save, copy, cut, paste, etc.

No Choose an item.


T.10.17 The system shall provide operators with a summary screen for vehicle and customer information verification.

No Choose an item.


T.10.18 The system shall support, where applicable, the ability to execute multiple transactions in the same screen and session.

Yes Choose an item.


T.10.19 The system shall allow an authorized user to find, enter and update customer record with additional customer types (e.g., lien holder, lessor, business). A customer may have multiple customer types (e.g., business/lessor, lien holder/driver, lien holder/lessor).

No Choose an item.



T.10.20 The system shall comply with: Section 508 of the U.S. Rehabilitation Act, or at minimum, be compatible with screen readers (both the site and any downloadable artifacts), capable of displaying large fonts, and content context which does not rely on color alone.

No Choose an item.


T.11 Printing T.11.1 The system shall have the capability to print credentials and documents in

County Treasurer and State DMV offices.Yes Choose an


T.11.2 The system shall have the capability to print forms on demand from County Treasurer and State DMV offices.

Yes Choose an item.


T.11.3 The system shall have the capability to print credentials and documents in more than one output size and on pre-formatted security paper (e.g. titles).

Yes Choose an item.


T.11.4 The system shall have the ability to reprint credentials and documents in the event the document print is spoiled or does not print.

Yes Choose an item.


T.11.5 The system shall have the ability to select a printer, other than the default printer for the workstation, if the user selects it.

Yes Choose an item.


T.11.6 The system shall be able to format for printing on letterhead and envelopes.

No Choose an item.


T.11.7 The system shall have the ability to print identifying information on any output document that may include: date, time, operator, location, etc.

Yes Choose an item.


T.12 Document Management T.12.1 The system shall have the ability to capture a signature, via electronic

device, and assign the signature image to a specific document. No Choose an


T.12.2 The system shall have the ability to utilize the State of Nebraska's OnBase Enterprise Content Management (ECM) System for storage and management of document images.

No Choose an item.


T.12.3 The system shall provide front-facing application for use of State's ECM. No Choose an item.


T.12.4 Utilization of ECM :


T.12.5 The system shall support the scanning and importing of documents to be included in the record.

No Choose an item.


T.12.6 The system shall support scanning and coding (e.g., bar, QR, etc.) all documents at the time of transaction, for electronic tracking.

No Choose an item.


T.12.7 The system shall support the scanning of documents to be included in the record in a batch process after the transaction is completed.

No Choose an item.


T.12.8 The system shall support image retrieval from within a transaction. No Choose an item.


T.12.9 The system shall provide the capability for creation of outbound electronic forms combining data from the production VTR database and image database (signature image).

No Choose an item.


T.12.10 The system shall allow an operator to pick from table driven lists of authorized source documentation that may be submitted by an applicant for a DMV product (e.g., titling, registration, or permit).

No Choose an item.


T.12.11 The system shall be able to create, print, electronically transmit, and track all outgoing correspondence (letter, e-mail, text message, fax).

No Choose an item.


T.12.12 The system shall transmit document images to a central image database. No Choose an item.


T.12.13 The system shall provide the option for image transmission in real time, or during off-peak periods to accommodate bandwidth and response time, and other network constraints.

No Choose an item.


T.12.14 The system shall provide the ability to re-scan a document if the quality of a scan is not acceptable.

No Choose an item.


T.12.15 The system shall provide a flexible set of indices which can be defined for the documents. After capturing, the documents shall be indexed prior to storing.

No Choose an item.


T.12.16 The system shall store document images at a business practice defined minimum resolution.

No Choose an item.



T.12.17 The system shall provide the ability to retrieve all documents within the business defined retention period using one of the indices that are defined and entered for the document.

No Choose an item.


T.12.18 The system shall allow only authorized users to access documents and all transactions should be logged.

No Choose an item.


T.12.19 The system shall display document images inside a browser. No Choose an item.


T.12.20 The system shall support multi-page and double-sided documents, and different document sizes.

No Choose an item.


T.12.21 The system shall allow the user to add free form text comments to a document or image.

No Choose an item.


T.12.22 The system shall generate a unique identifier which can be used to identify the customer, type of document, and variable data contained within the document. This information shall be stored in a character sequence and in a machine readable information (e.g., bar code, QR code, etc.) format.

No Choose an item.


T.12.23 The system shall be able to manage multiple versions of the same form, with indicators identifying current versions, prior versions, and expired versions.

No Choose an item.


T.12.24 The system shall have a central database for forms, with functions for indexing, storage and retrieval of forms.

No Choose an item.


T.12.25 The system shall store forms in standard document formats (e.g., Word, PDF).

No Choose an item.


T.12.26 The system shall allow for the retrieval and reviewing of all documents by a non-proprietary image viewer e.g. PDF, JPEG, etc.

No Choose an item.


T.12.27 The system shall retrieve these forms as overlays for printing. The retrieved form should be merged with data from the integrated operation database and/or document image database (e.g., signatures and photos), to be incorporated as part of outbound notices/correspondences to customers.

No Choose an item.



T.12.28 The system shall have the ability to access electronic documents and/or image information stored in the central database.

No Choose an item.


T.12.29 The system shall retain images of documents produced as part of the defined business process.

No Choose an item.


T.12.30 The system shall provide for the input and retention of supporting documents.

No Choose an item.


T.13 Barcode Scanning T.13.1 The system shall be designed to accommodate the reading/scanning of

machine readable information (e.g., bar code, QR code, etc.) technology on documents that meet AAMVA standards for coding and content.

No Choose an item.


Technical Completed


Reporting (R)Requirements Section Bidder Response Section


Delivery Method

Explanation

R.1 General R.1.1 The system shall have the capability to produce reports documenting financial

activities.Yes Choose


R.1.2 The system shall provide a help desk function for accessing user logs. No Choose an item.


R.1.3 The system shall provide a help desk function for replaying transactions. No Choose an item.


R.2 Reporting R.2.1 The system shall provide the capability to monitor performance of work activities at

the employee, work unit, office, administration, and agency levels.No Choose


R.2.2 The system shall provide desktop reporting tools for authorized end users supporting predefined, parameterized and ad hoc query reporting.

No Choose an item.


R.2.3 The system shall provide the capability for authorized end users to create dashboards.

No Choose an item.


R.2.4 The system shall capture transaction information, including but not limited to, processing time, approvals, user interactions, and modifications, for performance evaluation, auditing and workload analysis.

No Choose an item.


R.2.5 The system shall support rendering reports in formats are compatible with all delivery channels including mobile devices. Formats include, but are not limited to, PDF, HTML, XML, RTF, Microsoft Word, and Microsoft Excel.

No Choose an item.


R.2.6 The system shall support annotation and format editing of system-generated reports.

No Choose an item.


R.2.7 The system shall prevent users from degrading the operational performance of the system as a result of performance intense or miswritten queries.

No Choose an item.


R.2.8 The system shall provide the capability to manage standard report creation, modification, and publishing with role-based access.

No Choose an item.



R.2.9 The system shall provide the capability to drill down into system information to view the details of a specific transaction, employee action, inventory items, or customer record initially displayed as summary information.

No Choose an item.


R.2.10 The system shall provide the capability for authorized end users to render data in graphical formats including, but not limited to, bar charts, pie charts, heat maps, and scatter plots (without programming).

No Choose an item.


R.2.11 The system shall highlight anomalies in reported data based upon pre-set thresholds in standard reports, according to business rules.

No Choose an item.


R.2.12 The system shall provide wizard-style tools for both authorized end users and developers to develop reports and dashboards.

No Choose an item.


R.2.13 The system shall provide the ability to schedule generation of reports based on specified time periods (e.g., real-time, hourly, daily, weekly, monthly, year-to-date, and annually).

No Choose an item.


R.2.14 The system shall support impact analysis so when changes in source data are made, downstream reports will be highlighted.

No Choose an item.


R.2.15 The system shall provide the capability to search the report repository, individual reports, and central information repository by keywords.

No Choose an item.


R.2.16 The system shall provide tools for impact analysis for proposed or possible program changes. The tools shall allow for determining the impact on customer interactions, transaction times, transaction volumes, and staffing, among other items.

No Choose an item.


R.2.17 The system shall provide tools for forecasting budget, revenue, and staffing needs. No Choose an item.


R.2.18 The system shall provide the capability for data mining capabilities to uncover correlations or patterns which may suggest fraud or other system abuses.

No Choose an item.


R.2.19 The system shall track report usage. No Choose an item.


R.2.20 The system shall provide a tool to assist users in identifying logical groups in which to place similar objects (cluster analysis).

No Choose an item.



R.2.21 The system shall provide a tool to assist users in predicting the value of an unknown continuous variable and which variables have the biggest impact on a dependent variable (regression analysis).

No Choose an item.


R.2.22 The system shall be able to monitor trends on customer behavior and create customized product offers for customers based on their needs and historic behavior and profile.

No Choose an item.


R.2.23 The system shall provide the capability to create and maintain a report distribution list for each report and group of reports.

No Choose an item.


R.2.24 The system shall provide the capability for field masking on reports, such that only designated staff can see certain columns or rows on a report.

No Choose an item.


R.2.25 The system shall provide the capability to replicate a report as it was first prepared on an earlier date.

No Choose an item.


R.2.26 The system shall provide for alerts, at pre-established time intervals, for any system activity, including customer record access, based on business rules. Time intervals could include immediate notification, end-of-day notification, or some other set time frame.

No Choose an item.


R.2.27 The system shall support an audit program, including the ability to identify in-progress transactions for manager audit, randomly or based on other criteria. The system shall allow for the transaction to be suspended pending manager review and approval.

No Choose an item.


R.2.28 The system shall provide the capability to capture and report meta-data related to any transaction.

No Choose an item.


Reporting Completed


Interface Catalog (INT)Requirements Section Bidder Response Section

Req ID Description Function Type Method of Transmission

Existing Interface

Technology

Responsible to Build

Proposed Solution

Description Identify Source

(Production or

Replicated Database)

INT.1.1 County Ledger Systems

Reports requested from the County VTR system provide a data file which may be imported into standalone county financial systems.

File Share Pull from the county system (data file is transferred between libraries on the AS 400)

Exists Contractor Click here to enter text.


Choose an item.

INT.1.2 Nebraska.gov Online Nebraska.gov is the online payment portal for all online Nebraska Department of Motor Vehicles (State DMV) transactions, provides online services for title lookup to any user, and provides Vehicle Title Registration (VTR) lookup services to subscribers.

Read Terminal Exists Contractor Click here to enter text.


Choose an item.


INT.1.3 Nebraska.gov Online AS400, online renewal and specialty plate.

Interactive Terminal Exists Contractor Click here to enter text.


Choose an item.

INT.1.4 Nebraska.gov Online File share for insurance database and batch records for registration information providers.

File share SFTP Exists Contractor Click here to enter text.


Choose an item.

INT.1.5 National Law Enforcement Telecommunications Service (NLETS)

NLETS is an interstate justice and public safety network. Law enforcement queries for vehicle-specific information are received and returned via NLETS. Stolen vehicle information used to update the State Mainframe is received via NLETS.

Real time Web services Exists Contractor Click here to enter text.


Choose an item.

INT.1.6 Vehicle Registration Inventory Management System (VRIMS)

VTR creates files of general issue and specialty plates to be ordered for transfer to the Department of Corrections for manufacturing and delivery. This interface resides on the State VTR System version only.

File Share SFTP Exists Contractor Click here to enter text.


Choose an item.


INT.1.7 State Mainframe IBM mainframe hosted by the OCIO. This is the system of record for title, lien, and driver license information and contains the current registration information for each county.

Real time SNATCP/IPAPPC



Choose an item.

INT.1.8 AS400/VTR State and county registration and title application running on the 91 virtual and two physical AS400 servers.

Real time SNATCP/IPAPPC



Choose an item.

INT.1.9 AS400/MCS State registration application used for Motor Carrier Services (MCS).

File Share and real time

CICS and SFTP



Choose an item.

INT.1.10 Data Clients (Monthly, Weekly, and Daily)

Data Clients are entities which provide payment to the State DMV for selected VTR system data. Current clients include Experian (weekly and monthly—national vehicle databases), and Polk (weekly—national vehicle databases).



Choose an item.

INT.1.11 Douglas County Cashiering System (Open Invoice File)

Point-of-Sale (POS)/cash drawer application used and supported by Douglas County.

Data Share and real time (transactional)

SFTP Exists Contractor Click here to enter text.


Choose an item.


INT.1.12 Electronic Lien and Title (ELT)

Providers receive daily updates from the State Mainframe of lien activity that is used by their lender customers. The providers also return daily lien record updates to the State Mainframe.



Choose an item.

INT.1.13 National Motor Vehicle Title Information System (NMVTIS)

NMVTIS receives daily updates from the State Mainframe about titling activity in Nebraska. The State Mainframe receives daily updates from NMVTIS regarding change state of title transactions.

Real time Interactive Exists Contractor Click here to enter text.


Choose an item.

INT.1.14 Nebraska Criminal Justice Information System (NCJIS)

NCJIS is Nebraska’s consolidated data source for law enforcement, which receives information from the State Mainframe regarding vehicle and owner information.

Real time CICS Exists Contractor Click here to enter text.


Choose an item.

INT.1.15 Nebraska Department of Health and Human Services (DHHS)

DHHS accesses the Vehicle Title Registration (VTR) system to obtain vehicle owner information which is used for some social service programs.

Real time Formatted query



Choose an item.


INT.1.16 Nebraska Department of Roads (NDOR)

NDOR pulls vehicle information for accident records from the VTR system.

Real time Formatted query / within the State Mainframe



Choose an item.

INT.1.17 State Treasurer’s Web-based reporting system

This is a new interface which will send financial information on a monthly basis from VTR to the State Treasurer.

TBD TBD Does not Exist

Contractor Click here to enter text.


Choose an item.

INT.1.18 VIN Verification Service

Interactive. Real time Web services Exists (Batch)



Choose an item.

INT.1.19 MSRP/GVWR Data Provider

Interactive. Real time Web query Exists (Batch)



Choose an item.

INT.1.20 HIN Verification Service

Interactive. TBD TBD Does not Exist



Choose an item.

INT.1.21 Dealer Automated Services (DAS)

Providers submit daily title, lien, registration or temporary tag updates. Providers receive daily messages of activity to be used by their clients.




Choose an item.

INT.1.22 Enterprise Content Management (ECM)

This is the States enterprise content management service for storing and managing documents for the VTR.

System to system API

N/A Does not Exist



Choose an item.

INT.1.23 Wrecker/Salvage Dealers and Insurance

Submission of junk and salvage information to the




Choose an item.


Companies VTR. Wrecker/salvage information will be submitted to NMVTIS.

INT.1.24 Secretary of State Corporate Records

Validation of business names for the creation of customer record.




Choose an item.

INT.1.25 Address Validation Method to validate against USPS data hosted by OCIO.

Direct query

TCP/IP Does not Exist



Choose an item.

INT.1.26 State Print Shop File share for renewal notice data utilized to print and mail monthly renewal notices.



Choose an item.

INT.1.27 JD Edwards (E1) The State's financial system managed by the Department of Administrative Services.




Choose an item.

INT.1.28 City of Lincoln Provide extract of entire book of registration transactions for Lancaster County on a daily basis.



Choose an item.

Interface Catalog Complete


Licensing and Regulation of Dealerships (DL) (OPTIONAL)

Bidder complete the following spreadsheet IF providing costs in Appendix C, Cost Sheet for Licensing and Regulation of Dealerships System Functionality

Requirements Section Bidder Response SectionReq # Requirement Description Current

EnvironmentDelivery Method

Explanation

DL.1 General DL.1.1 The system shall support the issuance and ongoing management of a motor vehicle

dealer license based on business rules.No Choose an


DL.1.2 The system should support, at a minimum, the following dealer license types:

DL.1.3 Franchise Dealer No Choose an item.


DL.1.4 Used Vehicle Dealer No Choose an item.


DL.1.5 New Vehicle Dealer No Choose an item.


DL.1.6 Manufacturer Branch No Choose an item.


DL.1.7 Motorcycle Dealer No Choose an item.


DL.1.8 Trailer Dealer No Choose an item.


DL.1.9 Wrecker/Salvage Dealer No Choose an item.


DL.1.10 Finance Companies No Choose an item.


DL.1.11 Distributor No Choose an item.


DL.1.12 Manufacturer No Choose an item.



DL.1.13 Salesman No Choose an item.


DL.1.14 The system shall support the creation of new, user-defined dealer license types. No Choose an item.


DL.1.15 The system shall have the ability to attach complaints or investigation information to dealer license records.

No Choose an item.


DL.1.16 The system shall have the ability to issue and print dealer licenses and dealer license certificates.

No Choose an item.


DL.1.17 The system shall have a process to renew a dealer license. No Choose an item.


DL.1.18 The system shall have the ability to attach documents and associate them with a licensee.

No Choose an item.


DL.1.19 The system shall have the ability to track and record dealer inspections. No Choose an item.


DL.1.20 The system shall have the ability to track and record dealer bonds. No Choose an item.


DL.1.21 The system shall be able to record and update dealer license status (e.g., "valid", "expired", "under investigation", "suspended", "missing").

No Choose an item.


DL.1.22 The system shall utilize the master customer record for licensing and regulation of dealerships.

No Choose an item.


DL.1.23 The system shall record a salesperson's license information in the master customer record for the individual and the entity record for the dealership.

No Choose an item.


DL.1.24 The system shall support the online processing of licensing and regulation of dealerships.

No Choose an item.


DL.1.25 The system shall support the online processing of consumer complaints. No Choose an item.


DL.1.26 The system shall have the ability to calculate the parameters for the quantity of plates the dealer qualifies for.

No Choose an item.


Licensing and Regulation of Dealerships (OPTIONAL) Complete56 Appendix A: VTR Modernization Requirements Traceability Matrix

Documents

das.nebraska.govdas.nebraska.gov/materiel/purchasing/5557/5557 Z1 App… · Web viewThe system shall be able to forecast plate usage by office and suggest re-ordering volume. No