81DMV-S1466 - Drivers License Testing System - Final.docx

STATE OF NEVADA

DEPARTMENT OF ADMINISTRATION

Purchasing Division 515 East Musser Street, Suite 300 │ Carson City, NV 89701 Phone: 775-684-0170 │ Fax: 775-684-0188

Request for Proposal: 81DMV-S1466

For

DRIVER’S LICENSE TESTING SYSTEM

Release Date: March 4, 2021

Deadline for Submission and Opening Date and Time: April 13, 2021 @ 2:00 PM

Refer to Section 9, RFP Timeline for the complete RFP schedule

For additional information, please contact:

Heather Moon, Purchasing Officer II

State of Nevada, Purchasing Division

515 E. Musser Street, Suite 300

Carson City, NV 89701

Phone: 775-684-0179

Email address: hmoon@admin.nv.gov

Refer to Section 11 for instructions on submitting proposals

VENDOR INFORMATION SHEET FOR RFP 81DMV-S1466

Vendor Shall:

A) Provide all requested information in the space provided next to each numbered question. The information provided in Sections V1 through V3 shall be used for development of the contract;

B) Type or print responses; and

C) Include this Vendor Information Sheet in Section III of the Technical Proposal.

Street Address:

City, State, Zip Code:

Telephone:

Fax:

Toll Free:

including address if different than above

Name:

Title:

Address:

Email Address:

Telephone Number:

Fax:

Name:

Title:

TABLE OF CONTENTS

Prospective vendors are advised to review Nevada’s ethical standards requirements, including but not limited to NRS 281A, NRS 333.800, and NAC 333.155.

All applicable Nevada Revised Statutes (NRS) and Nevada Administrative Code (NAC) documentation can be found at: www.leg.state.nv.us.

PROJECT OVERVIEW

The State of Nevada Purchasing Division on behalf of the Nevada Department of Motor Vehicles (NV DMV) is seeking qualified vendors for Automated Driver’s License Testing System throughout the state of Nevada.

The awarded vendor shall provide all components to meet the specifications and requirements described in Section 4, Scope of Work, including conducting tests and retrieving/transmitting statistical information. The vendor will retain ownership of all components.

· Provide equipment and software for electronic knowledge testing for 114 testing stations and 18 examiner consoles.

· With the cooperation of NV DMV, establish a process to allow Drive Schools to perform in office, online drivers’ knowledge testing using contractor supplied test machines that are the same as the testing machines used in the NV DMV offices. These should allow for test results to be transmitted to or picked up by the NV DMV to be able to complete the transaction and issue a non-commercial learner’s permit.

· With the cooperation of the NV DMV, establish a web-based driver knowledge testing program.

· With the cooperation of the NV DMV, establish a program for driver test examiners to use electronic means to capture all aspects of the skills testing procedures.

· The contract start date will be July 1, 2022 and the end date will be June 30, 2026.

· Use a web-based browser system for all equipment.

· Perform all system updates, including program changes, new tests, new or changed test questions and answers, and any other modification required by the State as a result of federal, state or department mandates.

· Enable all exam results to be sent to the NV DMV application to update the NV DMV database. The awarded vendor and State will work together to determine the data that must be passed, programming, etc. Any programming cost incurred on the side of the vendor relating to design, testing, implementation, and/or updates to this interface will be the responsibility of the vendor. This includes any travel, lodging, and per diem that may be required to complete this part of the application.

· Maintain the system. Ensure all software, hardware, and networking is operating according to the service level agreement (SLA). Each workstation will be available for use Monday through Saturday 8:00 a.m. to 5:00 p.m., excluding all State holidays. In exchange for the placement of not cost spares at all offices, the State agrees to provide on-site technical support to physically replace equipment as needed.

· Vendor may use a Virtual Private Network (VPN) connection supplied by the DMV to connect to the equipment and provide upgrades and software support. Vendor must supply on-site technicians as needed for complex problem resolution. If vendor’s on-site technician is required, the State requires following the SLAs.

· The contract resulting from this Request for Proposal will be for a period of four (4) years. The contract would commence approximately July 1, 2022 and expire June 30, 2026, depending on the time period for transition from the current vendor’s system.

GOALS AND OBJECTIVES

To expand the test taking capabilities to the customer.

To improve the skills testing procedure to an electronic process.

Vendor will provide maintenance and support for new or existing hardware and software solutions.

Vendor will complete all software upgrades as new versions are made available.

Vendor will provide training for the software/hardware.

This section sets forth a sample of performance specifications for the Service Level Agreements (SLA) and Service Level Objectives (SLO) to be established between the NV DMV and the Contractor.

This section contains the SLA/SLOs that provide the NV DMV framework, expectations relating to meet the requirements and objectives as applicable. This section defines the NV DMV’s detailed performance, management, and reporting requirements to meet the SLAs/SLOs in this RFP.

The Contractor shall be required to comply with the following performance management and reporting mechanisms for all services within the scope of this RFP.

On a monthly basis, the contactor shall provide the NV DMV with a written report (“Monthly Service Level Report”) which includes the following information:

Description of each individual SLA/SLO;

Contactor’s quantitative performance for each service level;

Amount of any monthly performance credit for each SLA/SLO;

Year-to-date total performance credit balance for each SLA/SLO;

Root cause analysis and corrective action plan with respect to any service levels where the individual SLA/SLO was missed; and

Trend or statistical analysis with respect to each SLA/SLO as requested by the NV DMV.

The monthly SLA/SLO report shall be due no later than the tenth (10th) business day of the following month.

BACKGROUND

PROJECT

The Nevada Department of Motor Vehicles (NV DMV) administers multiple types of testing to the public. In the past these were paper and scantron tests. The current tests have been available in a computerized fashion for well over 15 years and are essential for the business the Department provides. Being able to offer computerized testing helps retain the validity and integrity of the test along with streamlining the processes making the testing process more efficient. The vendor selected should be able to provide the same ease of use and efficiency the Department needs for each test. A new efficiency the NV DMV has identified is for a vendor solution to interface with NV DMV systems to add testing results to an individual’s record in the NV DMV database. This will enhance the user experience along with creating a quicker process. This process will also need to be able to be modified in the event testing has been added to an incorrect record.

AGENCY

The NV DMV is comprised of seven divisions encompassing six functional areas. A copy of the organizational chart is included in Attachment J - NV DMV Department Organizational Chart. Each division within the NV DMV administers several programs. The divisions and examples of programs are described below:

The Director’s Office includes public Information and Hearings Offices, establishes policy for the NV DMV. The Director’s Office is responsible for leading and controlling the agency’s operations and responding to all media inquiries through the Public Information Officers. NV DMV policies, information security, human resource management, and employee development units also fall under the responsibility of this office.

The Administrative Services Division (ASD) is responsible for providing services to include fiscal accounting, budgeting, travel arrangements, payroll, warehousing, inventory control, mail services, purchasing services, contract management, facilities management, revenue collection and distribution, and revenue recovery. ASD provides services to all divisions within the NV DMV.

The Central Services and Records Division (CSD) provides alternative processing methods for NV DMV customers regarding drivers’ licenses, identification cards, vehicle registrations, license plates, vehicle titles, and insurance verification. CSD ensures data integrity, applies driver’s license sanctions, manages records, operates call center services, administers the Off-Highway Vehicle program and processes customer information requests.

The License Plate Factory is responsible for designing, manufacturing, and distributing Nevada's vehicle license plates to NV DMV Offices, County Offices, and AAA partner locations for issuance to vehicle owners and operators in Nevada.

The Compliance Enforcement Division (CED) is the regulatory division of the NV DMV. Regulating the auto industry provides consumer protection through the licensing and regulation of businesses related to the manufacture, transport, sale, repair, and disposal of vehicles. This division also licenses and regulates schools for training drivers. The Division investigates all complex and criminal complaints filed against licensees and investigates fraudulent activities. CED performs audits, monitors, inspects, and provides investigative services on the internal and external entities related to the NV DMV’s core programs.

The Emissions Control Program ensures vehicles in Nevada comply with state and federal laws and regulations for emission standards. The Division licenses and regulates emissions stations. Emission inspectors are provided training and certification to perform emission tests.

The Field Services Division (FSD) provides direct customer service operations for both commercial and non-commercial driver licensing, identification, State issued credentials, voter registration, vehicle registration, vehicle titles, vehicle inspections, and fleet operations. Field Services assures safe and knowledgeable drivers receive the privilege to drive on the highways. Field Services Division also collects appropriate fees and taxes from the drivers, owners, and operators of vehicles.

The Office of Project Management (OPM) is a resource to help achieve the NV DMV’s strategic plan, goals, and ensure consistent uniform program delivery. OPM is responsible for managing projects, implementing new or improved business processes, creating and completing surveys, developing program related procedures, developing and managing requests for proposals, managing forms, developing regulations, drafting legislation, and preparing fiscal notes. OPM supports other divisions in the areas of research, coordination of project completion, regulation and statutory changes, and legislative interaction related to all NV DMV functions and business programs.

The Motor Carrier Division (MCD) is responsible for ensuring compliance with state laws, federal laws, and other governing documents applicable to its motor carrier customers. This includes administration of special fuel and motor fuel supplier programs to fairly collect and distribute over 1 billion dollars annually owed to Nevada and other entities (counties, cities, etc.). MCD is responsible for the licensing and fuel tax use collections for all commercial vehicles over 26,000 pounds based in Nevada. Motor Carrier also licenses commercial vehicles over 10,000 pounds with intrastate operations; collects revenue and revenue recovery payments; and conducts audits of motor carriers and fuel suppliers to provide customer education to ensure compliance.

The Motor Vehicle Information Technology Division (MVIT) supports technology involved in the development and maintenance of computer systems for the NV DMV. MVIT is responsible for the maintenance of application systems, testing, and the development of new programs, and enhancements of existing programs. They provide network support and installation necessary for the infrastructure of systems data. MVIT provides technical and operational support, and is responsible for hardware, software, network, and security in NV DMV operations. Additionally, MVIT provides Desk Top Support and User Support both internal and external customers.

The functional areas are: fiscal, vehicle registration/title/insurance verification, driver’s license, motor vehicle industry regulation, motor carrier and fuel tax collection. There are 18 field offices statewide with the largest metropolitan offices in the Las Vegas valley and in Reno. There are approximately 1,200 employees statewide with the majority within Field Services. In addition, the NV DMV serves Nevada Citizens, other State agencies, Federal agencies, external, and internal customers by providing driver identification credential, vehicle ownership, registration, vehicle insurance and other historical data based on qualified records requests.

CONCURRENT IMPACTS/PROJECTS

Automated Testing Machines are a vital part of our ability to process driver’s licenses and instructions permit for both commercial and non-commercial drivers.

Statewide these machines process an average of 17,500 tests per month.

The Automated Testing Machines provide drivers with the tools to navigate NV roads safely.

The web service built for use with these machines is specific to Nevada and aids in tracking testing statistics such as pass and fail rate, average testing time, language and the average type of card tested for each month.

These statistics are used by other agencies as well.

This contract would be a detriment to the NV Department of Motor Vehicles as well as Nevada citizen as whole.

The impact to customer to wait any further length of time to conduct a knowledge test could impact not only their quality of life, but their financial stability, job status and their ability to provide for their families.

The NV DMV is undergoing a modernization project with focus on alternate services using virtual transactions sites via the internet, mobile apps and/or offsite kiosks.

This project will impact all aspects of the NV DMV as it is a large shift in its current service system.

CURRENT COMPUTING ENVIRONMENT

Current Department environments is a mixture of physical and virtualized hosts running Microsoft Server 2012, 2016 & 2019, Microsoft SQL Server 2014, 2016 & 2017 and IBM DB2. Virtualization of hosts utilizes VMWare/ESX software operating on hyper-converged infrastructure. Department is considering future cloud-based progression, electronic entitlements and future SaaS product.

PROJECT SOFTWARE

All software used for project management shall be approved by the State. Current desktop tools utilized by the DMV include:

Desktop PC’s with Windows 10

Microsoft Office Suite 2013

Office 365

Modern Web Browser (e.g. Chrome, Firefox & Edge)

Visual Studio 2015 & 2019

Microsoft SQL Server

Microsoft Visio

Microsoft Project

Adobe Acrobat including programing languages/ frameworks/Platforms such as:

Microsoft NET

C#

VB. NET

Mainframe COBOL

DB2

TSO/ISPF

CICS & JCL

PowerBuilder (PowerScript)

DEVELOPMENT SOFTWARE

All proposed software used in the design, development, testing and implementation of the deliverables outlined in this RFP shall be approved by the State.

If the application software is not public domain, the awarded vendor shall provide a licensing strategy.

The State shall procure licenses for all base components and third party equipment (operating system, data base, etc.) based upon specifications provided by the awarded vendor.

The awarded vendor shall provide software licenses and formal training as necessary for all Department users.

STATE RESOURCES

The following paragraphs describe the resources the State has committed to this project.

Project Sponsor

The Nevada Department of Motor Vehicles is the project sponsor. All project activities shall be conducted under the authority of the Nevada Department of Motor Vehicles.

Project Manager

A Project Manager has been appointed to coordinate the activities of all individuals and organizations involved in the project. The Project Manager shall provide on-going daily direction and oversight to the State project staff and the contractor and report progress and problems to the Steering Committee. The Project Manager shall coordinate all organizations involved in the project and ensure resource requirements are identified and addressed. The Project Manager sets priorities when choices of alternatives are required.

State Project Staff

The awarded vendor shall be expected to work closely with the State project staff assigned to this project.

State project staff shall be available to attend meetings, interviews and assist assigned staff in reviewing functions with the awarded vendor.

State project staff shall be assigned to the project on an as-needed basis, as determined by project and technical management to represent the various functional and technical areas.

State project staff shall report to the Project Manager who shall act as a conduit to the awarded vendor.

Quality Assurance Monitor

A Quality Assurance (QA) monitor may be utilized and shall act as technical assistant to the State. The QA monitor shall report to the State Project Manager. Major functions shall include, but not be limited to the following.

Review of project tasks;

Validation of results;

Provide recommendations, as required;

Review of deliverables; and

Project plan monitoring.

SYSTEM REQUIREMENTS

VENDOR RESPONSE TO SYSTEM REQUIREMENTS

Vendors shall explain in sufficient detail how the vendor shall satisfy the Nevada Department of Motor Vehicle’s project requirements described below. If subcontractors shall be used for any of the tasks, vendors shall indicate what tasks and the percentage of time subcontractor(s) shall spend on those tasks.

COMPUTING PLATFORM

All system requirements will be performed by the vendor. The vendor must be able to communicate with the DMV application(s).

The awarded vendor shall be expected to work closely with the State project staff assigned to this project.

State project staff shall be available to attend meetings, interviews and assist assigned staff in reviewing functions with the awarded vendor.

A Quality Assurance (QA) monitor may be utilized and shall act as technical assistance to the State. The QA monitor shall report to the State Project Manager. Major functions shall include, but not limited to the following:

Review of projects tasks;

Validation of results;

Provide recommendations as required;

Review of deliverables; and

Project plan monitoring.

All proposed software used in the design, development, testing and implementation of the deliverables outlined in this RFP shall be approved by the State.

If the application software is not public domain, the awarded vendor shall provide a licensing strategy.

The State shall procure licenses for all base components and third-party equipment (operating system, database, etc.) based upon specifications provided by the awarded vendor.

The awarded contractor shall provide software licenses and formal training as necessary for all Department users.

The Nevada Department of Motor Vehicles (DMV) is the project sponsor. All project activities shall be conducted under the authority of the DMV.

TECHNICAL REQUIREMENTS

Vendor shall explain in sufficient detail how the vendor shall satisfy the Nevada Department of Motor Vehicles project requirements describe below. If subcontractors shall be used for any of the tasks, vendors shall indicate what task and the percentage of time subcontractor(s) shall spend on those tasks.

System Requirements and Application Software Interface

The Driver’s License Testing System shall include all necessary software, which shall meet all the following requirements:

Any software provided with or produced by the awarded contractor as part of the Driver’s License Testing System must allow for programmatic integration with the testing process via a software interface.

A REST API should be available for transmission of knowledge test data and results.

There should also be a mechanism in place for secure communication with a DMV REST API for the same purpose.

The transmission of data must be done on the basis of a uniquely identified individual.

This may or may not include individual ID, SSN, DLD, among others.

The data must be transmitted through a secure channel, such as VPN.

The awarded contractor shall provide all rights necessary to grant to the Department unlimited licensure for use of the Driver’s License Testing System, excluding sale or lease, during the entire resulting contract term; including any renewal or extension period.

The awarded contractor solution will be Service Oriented Architecture compatible. Hosted software or service may be cloud based. Cloud based solutions must demonstrate strong two (2) factor authentication provided by either the awarded vendor or Department, role-based access controls, FIPS grade encryption of data at rest and in transit, and align with the State of Nevada Cloud Hosting security requirements. Contractor Service Level Agreements (hereinafter “SLA”) must conform to FEDRAMP and NIST 800-53 compliance controls.

Software and applications shall be continuously maintained throughout the contract term using qualified personnel to ensure that it operates as contemplated by this RFP, and in compliance with the contract.

Meetings between the awarded contractor and Department will be held to discuss new and upcoming equipment, hardware, software, updates or any other advancement in technology, at no cost to the Department. These meetings shall be conducted once per calendar year, at a minimum, and used to plan future implementation or installation of updates, patches, hardware, equipment or other advancements in technology.

Prior to installing any upgraded equipment not part of the original installation during the term of the Contract, the Awarded Contractor shall obtain approval from the Department. The Awarded Contractor shall begin installing the upgraded equipment in a mutually agreed time, after the Department’s approval (for all installations), under the same terms and conditions of the resulting Contract, at no cost to the Department.

If awarded contractor-supplied software needs to be updated to support upgraded equipment, the software must be able to support the upgraded equipment and all previous equipment supplied under this contract. The Awarded Contractor will work with the Department to establish an Implementation Plan for the software in all Agency Sites/Field Offices. The installation of new software shall be at no cost to the Department.

Schedules and roll-out plans must be developed mutually between both/all parties involved for all technology upgrades. All technology upgrades must be tested by both parties thoroughly in UAT region before implementation as detailed in this RFP, Test Environment, User Acceptance Testing (UAT) Environment, and implemented with Department’s approval and involvement. Failure to schedule, plan and test technology upgrades may result in liquidated damages as defined in this RFP.

Any off-premise storage of applications or data must be located within the United States.

Software maintenance must include up-to-date 3rd party security patches and version upgrades. Critical vulnerabilities must be patched within thirty (30) calendar days of vendor release; High and medium patches applied within (90) calendar days of vendor release. Failure to resolve vulnerabilities in the respective thirty (30) or ninety (90) days may result in liquidated damages.

Any operating systems used throughout the life of the contract must be kept up to date with the most current version; and all updates and patches must be performed monthly, at a minimum. If these conditions are not met, liquidated damages may be applied as defined in Performance Standards and Liquidated.

Awarded contractor must have a UAT region to test all patches and software updates before moving any changes to the Production region. Environment needs to be active Monday through Friday 8:00am to 5:00pm Pacific Time. The UAT infrastructure must be separate from the production infrastructure.

Awarded contractor shall develop a process flow and provide a schedule of all software updates and patches. Preferred advanced notice should be given at least thirty (30) calendar days, if possible, on all updates and patches. All updates and patches must follow the Department’s change control process from development to production.

During the contract term, if updates to awarded contractor-supplied software and equipment are required as a result of operating system patches, the awarded contractor-supplied software and equipment must be updated at no cost to the Department.

Software updates must be provided to the Department whenever they become available, and must be meet the following:

Software documentation shall be provided upon delivery of updated software releases.

If functionality is changed as a result of any updates, the awarded contractor must provide training within software documentation.

Updated software will be compatible with all application software and equipment installed at any time during the contract term.

The awarded contractor shall provide a system for acceptance and non-acceptance, by the Department of any software updates.

Awarded contractor must provide at least thirty (30) calendar days for notification, or another mutually agreed upon period, before any software updates are performed, at no additional cost to the Department. Failure to properly communicate with the Department may result in liquidated damages as define in this RFP Performance Standards and Liquidated Damages.

The awarded contractor shall, at least annually, review and update technical bulletins, user guides, and provide any updates to the Department’s Contract Manager or designee, in a mutually agreed-upon format.

The awarded contractor shall correct, remedy, and produce a detailed report of any programming error attributed to the awarded contractor, in a time-frame agreed to by the Department.

The awarded contractor’s engineering team and technical leads assigned to the Contract shall have sufficient expertise to make recommendations for awarded vendor-supplied software configurations. All awarded vendors accessing DMV data, systems, or remote management, must pass DMV background checks, which includes Federal Bureau of Investigation fingerprint and REAL ID clearance.

Documentation will include a system security plan design document (following Federal Risk and Authorization Management Program (hereinafter “FEDRAMP”) templates), used to identify, describe, and define the system security baseline, and include NIST 800-53 control test cases, with current vulnerability scans and defined Plan Of Action and Milestones (hereinafter “POAM”) as necessary.

In meeting the above specifications, as well as any other requirements of the Contract, additional software (i.e., software that was not included in Awarded vendor’s reply or Best and Final Offer (hereinafter “BAFO”) and software incorporated in the Contract, or that was not known or identified at the time of Contract finalization, or otherwise referenced in the Contract) is required during the contract term. All such software shall be supplied and updated by the awarded contractor at no additional cost to the Department.

The Driver’s License Testing System shall include all necessary software, which shall meet all of the following requirements:

Any software provided with or produced by the awarded contractor as part of the Driver’s License Testing System must allow for programmatic integration with the testing process via a software interface.

The awarded contractor shall provide all rights necessary to grant to the Department unlimited licensure for use of the Driver’s License Testing System, excluding sale or lease, during the entire resulting contract term including any renewal or extension period.

The awarded contractor solution will be Service Oriented Architecture compatible. Hosted software or service may be cloud based. Cloud based solutions must demonstrate strong two (2) factor authentication provided by either the awarded vendor or Department, role-based access controls, FIPS grade encryption of data at rest and in transit, and align with the State of Nevada Cloud Hosting security requirements. Contractor Service Level Agreements (hereinafter “SLA”) must conform to FEDRAMP and NIST 800-53 compliance controls.

Software and applications shall be continuously maintained throughout the contract term using qualified personnel to ensure that it operates as contemplated by this RFP, and in compliance with the contract.

Meetings between the Awarded Contractor and Department will be held to discuss new and upcoming equipment, hardware, software, updates or any other advancement in technology, at no cost to the Department. These meetings shall be conducted once per calendar year, at a minimum, and used to plan future implementation or installation of updates, patches, hardware, equipment or other advancements in technology.

Prior to installing any upgraded equipment not part of the original installation during the term of the Contract, the Awarded Contractor shall obtain approval from the Department. The Awarded Contractor shall begin installing the upgraded equipment in a mutually agreed time, after the Department’s approval (for all installations), under the same terms and conditions of the resulting Contract, at no cost to the Department.

If Awarded Contractor-supplied software needs to be updated to support upgraded equipment, the software must be able to support the upgraded equipment and all previous equipment supplied under this contract. The Awarded Contractor will work with the Department to establish an Implementation Plan for the software in all Agency Sites/Field Offices. The installation of new software shall be at no cost to the Department.

Driver’s License Testing System Test Environment, User Acceptance Testing Environment and Compliance Review.

The awarded contractor will begin integration with the Department’s network and program test environment.

The awarded contractor’s engineering team shall be available to work with the Department to integrate the awarded contractor’s Driver’s License Testing System, to include any equipment and software interface(s). This integration will precede the required Compliance Review. Driver’s License Testing System Integration must be completed within forty-five (45) business days from being granted access into the Department system for integration.

The awarded contractor must be ready to submit and pass the Test Environment Compliance Review within forty-five (45) business days after access into the Department’s system for integration is granted. If the awarded contractor has not successfully passed the Test Environment Compliance Review at the expiration of the Test Environment Compliance Review period, the awarded contractor may request an extension for up to an additional thirty (30) business days in writing to the Department. The written extension notice will identify all deficiencies and requirements that must still be met. The awarded contractor must notify the Department in writing of readiness for re-evaluation within twenty-four (24) hours of the last-noted deficiency correction. If the awarded contractor cannot thereafter pass the Test Environment Compliance Review, within the stated time frame, the contract with the awarded contractor may be terminated.

Driver’s License Testing System will be subject to and must pass a Department conducted Test Environment Compliance Review. The Test Environment Compliance Review must verify the Awarded vendor’s Driver’s License Testing System solution successfully operates and functions with the Department’s System (CARRS), and is in accordance with all of the following:

The specifications set forth in the RFP; all specifications and operational requirements established by the respective manufacturers;

The awarded contractor’s Reply and BAFO, as incorporated in the Contract;

All requirements set forth in the resulting Contract are fulfilled; and

Within five (5) business days after the successful Driver’s License Testing System integration, the awarded contractor must contact the Department’s Contract Manager, IT designee, Contract Monitor and ISO to request Test Environment Compliance Review. The Department will begin the review within five (5) business days of receiving this request and complete the Compliance Review within ten (10) business days. Results of the Test Environment Compliance Review will be provided to the Awarded vendor in writing; stating a “pass” or “fail” result, listing any deficiencies, if there are any.

Within fifteen (15) calendar days after successfully passing the Test Environment Compliance Review, the awarded contractor must notify the Department it is ready to move to the Department’s UAT environment.

Driver’s License Testing System User Acceptance Testing (UAT)

Upon notification to the Department of Driver’s License Testing System UAT integration readiness, the Awarded vendor’s engineering team shall be available to work with the Department to integrate the awarded contractor’s Driver’s License Testing System, to include any equipment and software interface(s), with the Department’s Driver’s License Testing System. This integration will precede the required Driver’s License Testing System UAT Compliance Review. Driver’s License Testing System integration must be completed within twenty-five (25) business days of Driver’s License Testing System UAT Integration Compliance Review readiness notification. Integration is deemed complete by demonstrating the ability and returning the required information to the Department’s System (CARRS).

The awarded contractor must be ready to submit and pass the Driver’s License Testing System UAT Compliance Review within twenty-five (25) business days after the Department allows integration access into the Department’s UAT environment. If the awarded contractor has not successfully passed the Driver’s License Testing System UAT Compliance Review at the expiration Driver’s License Testing System UAT Compliance Review period, and the review period falls outside of the twenty-five (25) business day period, the Department, at its discretion, may extend the UAT period for up to an additional thirty (30) business days with a written extension notice. The written extension notice will identify all deficiencies and all UAT requirements that must still be met with a time-frame for corrections and compliance with UAT requirements. The awarded contractor must notify the Department in writing of readiness for re-evaluation within twenty-four (24) hours of the last-noted deficiency correction. If the awarded contractor cannot thereafter pass the Driver’s License Testing System UAT Compliance Review, within the stated time-frame, the contract with the awarded contractor may be terminated.

The UAT site will be subject to and must pass a Department conducted Driver’s License Testing System UAT Compliance Review. The Lab and Development sites are excluded from the Driver’s License Testing System UAT Compliance Review requirement. The Driver’s License Testing System UAT Compliance Review must verify the installed equipment has been successfully integrated, operates, and functions in accordance with the following:

The specifications set forth in the RFP; all specifications and operational requirements established by the respective manufacturers;

The awarded contractor’s Reply and BAFO, as incorporated in the Contract;

All requirements set forth in the resulting contract are fulfilled; and

Within five (5) business days after the successful integration of the Driver’s License Testing System, the awarded contractor must contact the Department’s Contract Manager, IT Designee, Contract Monitor and ISO to request Driver’s License Testing System UAT Compliance Review. The Department will begin and complete the review within five (5) business days of receiving this request. Results of the Driver’s License Testing System UAT Compliance Review will be provided to the awarded contractor in writing; stating a “pass” or “fail” result, listing any deficiencies.

Within fifteen (15) calendar days after successfully passing the Driver’s License Testing System UAT Compliance Review, the Awarded Contractor must notify the Department it is ready for Driver’s License Testing System integration (i.e., awarded contractor’s Driver’s License Testing System is prepared to successfully integrate with the Department’s System (CARRS).

Within fifteen (15) calendar days after successfully passing the Driver’s License Testing System UAT Compliance Review, the Awarded Contractor must notify the Department it is ready to move to the Department’s Production environment.

Disaster Preparedness; Disaster Recovery Plan; And Return to Service

The awarded vendor need a disaster preparedness plan in the event of catastrophic failures.

Return to Service Plan

The awarded vendor need a return to service plan in the event of catastrophic failures.

Test Environment, Driver’s License Testing System Integration, User Acceptance Testing Environment and Compliance Review

The awarded contractor will begin integration with the Department’s network and programs in a TEST environment.

The awarded contractor’s engineering team shall be available to work with the Department to integrate the awarded contractor’s Driver’s License Testing System, to include any equipment and software interface(s). This integration will precede the required Compliance Review. Driver’s License Testing System Integration must be completed within forty-five (45) business days from being granted access into the Department system for integration.

The awarded contractor must be ready to submit and pass the Test Environment Compliance Review within forty-five (45) business days after access into the Department’s system for integration is granted. If the awarded contractor has not successfully passed the Test Environment Compliance Review at the expiration of the Test Environment Compliance Review period, the awarded contractor may request an extension for up to an additional thirty (30) business days in writing to the Department. The written extension notice will identify all deficiencies and requirements that must still be met. The awarded contractor must notify the Department in writing of readiness for re-evaluation within twenty-four (24) hours of the last-noted deficiency correction. If the awarded contractor cannot thereafter pass the Test Environment Compliance Review, within the stated time frame, the contract with the awarded contractor may be terminated.

The UAT site will be subject to and must pass a Department conducted Driver’s License Testing System UAT Compliance Review. The Lab and Development sites are excluded from the Driver’s License Testing System UAT Compliance Review requirement. The Driver’s License Testing System UAT Compliance Review must verify the installed equipment has been successfully integrated, operates, and functions in accordance with the following:

The specifications set forth in the RFP; all specifications and operational requirements established by the respective manufacturers;

The awarded contractor’s Reply and BAFO, as incorporated in the Contract;

All requirements set forth in the resulting contract are fulfilled; and

Within five (5) business days after the successful integration of the Driver’s License Testing System, the awarded contractor must contact the Department’s Contract Manager, IT Designee, Contract Monitor and ISO to request Driver’s License Testing System UAT Compliance Review. The Department will begin and complete the review within five (5) business days of receiving this request. Results of the Driver’s License Testing System UAT Compliance Review will be provided to the awarded contractor in writing; stating a “pass” or “fail” result, listing any deficiencies.

Within fifteen (15) calendar days after successfully passing the Driver’s License Testing System UAT Compliance Review, the Awarded Contractor must notify the Department it is ready for Driver’s License Testing System integration (i.e., awarded contractor’s Driver’s License Testing System is prepared to successfully integrate with the Department’s System (CARRS).

FUNCTIONAL REQUIREMENTS

This section outlines the processes, workflows and functions of the overall Driver’s License Testing System.

Customer comes into the Department of Motor Vehicles (DMV) for a driver’s license transactions.

DMV technician determines what tests, if any, needs to be taken.

If a knowledge test is needed, technician will send customer to the testing examination room.

In the testing examination room, the technician sets up any test customer needs to be taking.

Customer proceed to the STS knowledge test machines or if the system is down, the customer will take the test on a scantron paper.

Once customer completed the knowledge test, the technician will process and complete the transaction.

If the technician is too busy to complete the transaction, customer will be put back in the que to be process at a window.

By executing a contract resulting from this RPF, the awarded contractor agrees to be held responsible for providing, and shall ensure successfully installation, implementation, operation, updating and maintenance of all equipment, software, applications, patches and updates associated with, and contemplated by this RFP during the term of the resulting contract, including any optional renewal or extension term.

The Vendor must be able to seamlessly integrate with the DMV’s Modernization project. The Modernization project is an ongoing project that will affect all aspects of the DMV. All qualified vendors must be capable of interacting with both the Department and any Modernization project to assure that the vendor’s product and services can operate in unison with the new DMV system. The vendor must provide a solution that will work with our current system and future system that Modernization project will deliver, whether the system is implemented in phases, all at once, or parallel.

SECURITY STANDARDS

System must meet State security standards for transmission of personal information as outlined in NRS 205.4742 (defines “encryption) and NRS 603A.040 (defines “personal information”).

All information technology services and systems developed or acquired by agencies shall have documented security specifications that include an analysis of security risks and recommended controls (including access control systems and contingency plans).

Security requirements shall be developed at the same time system planners define the requirements of the system. Requirements must permit updating security requirements as new threats/vulnerabilities are identified and/or new technologies implemented.

Security requirements and evaluation/test procedures shall be included in all solicitation documents and/or acquisition specifications.

Systems developed by either internal State or contracted system developers shall not include back doors or other code that would cause or allow unauthorized access or manipulation of code or data.

Security specifications shall be developed by the system developer for approval by the agency owning the system at appropriate points of the system development or acquisition cycle.

All system development projects must include a documented change control and approval process and must address the security implications of all changes recommended and approved to a particular service or system. The responsible agency must authorize all changes.

Application systems and information that become obsolete and no longer used must be disposed of by appropriate procedures. The application and associated information must be preserved, discarded or destroyed in accordance with Electronic Record and Record Management requirements defined in NRS and NAC 239, Records Management.

Software development project must comply with State Policy 4.100000, section 4.7, Software Development and Maintenance. Reference to Sate Policy 4.100000 can be found https://it.nv.gov/uploadedFiles/ITnvgov/Content/Governance/dtls/Standards/4.100000StateConsolidatedPolicy.pdf

SCOPE OF WORK

The scope of work is broken down into tasks, activities and deliverables. The tasks and activities within this section are not necessarily listed in the order that they shall be completed. Vendors shall reflect within their proposal and preliminary project plan their recommended approach to scheduling and accomplishing all tasks and activities identified within this RFP.

All tasks performed by the awarded vendor may be reviewed by the QA monitor as well as State staff.

VENDOR RESPONSE TO SCOPE OF WORK

Within the proposal, vendors shall provide information regarding their approach to meeting the requirements described within Sections 4.5 through 4.25.

If subcontractors shall be used for any of the tasks, vendors shall indicate what tasks and the percentage of time subcontractor(s) shall spend on those tasks.

Vendor's response shall be limited to no more than five (5) pages per task not including appendices, samples and/or exhibits.

DELIVERABLE SUBMISSION AND REVIEW PROCESS

Once the detailed project plan is approved by the State, the following sections detail the process for submission and review of deliverables during the life of the project/contract.

General

The contractor shall provide one (1) master (both hard and soft copies) and four (4) additional hard copies of each written deliverable to the appropriate State Project Manager as identified in the contract.

Once a deliverable is approved and accepted by the State, the contractor shall provide an electronic copy. The State may, at its discretion, waive this requirement for a particular deliverable.

The electronic copy shall be provided in software currently utilized by the agency or provided by the contractor.

Deliverables shall be evaluated by the State utilizing mutually agreed to acceptance/exit criteria.

Deliverable Submission

Prior to development and submission of each contract deliverable, a summary document containing a description of the format and content of each deliverable shall be delivered to the State Project Manager for review and approval. The summary document shall contain, at a minimum, the following:

Cover letter;

Table of Contents with a brief description of the content of each section;

Anticipated number of pages; and

Identification of appendices/exhibits.

The summary document shall contain an approval/rejection section that can be completed by the State. The summary document shall be returned to the contractor within a mutually agreed upon time frame.

Deliverables shall be developed by the contractor according to the approved format and content of the summary document for each specific deliverable.

At a mutually agreed to meeting, on or before the time of delivery to the State, the contractor shall provide a walkthrough of each deliverable.

Deliverables shall be submitted no later than 5:00 p.m., per the approved contract deliverable schedule and shall be accompanied by a deliverable sign-off form (refer to Attachment F) with the appropriate sections completed by the contractor.

Deliverable Review

General

The State’s review time begins on the next working day following receipt of the deliverable.

The State’s review time shall be determined by the approved and accepted detailed project plan and the approved contract.

The State has up to five (5) working days to determine if a deliverable is complete and ready for review. Unless otherwise negotiated, this is part of the State’s review time.

Any subsequent deliverable dependent upon the State’s acceptance of a prior deliverable shall not be accepted for review until all issues related to the previous deliverable have been resolved.

Deliverables determined to be incomplete and/or unacceptable for review shall be rejected, not considered delivered and returned to the contractor.

After review of a deliverable, the State shall return to the contractor the project deliverable sign-off form with the deliverable submission and review history section completed.

Accepted

If the deliverable is accepted, the original deliverable sign-off form signed by the appropriate State representatives shall be returned to the contractor.

Once the contractor receives the original deliverable sign-off form, the State can then be invoiced for the deliverable (refer to Section 7, Financial).